Last updated on DECEMBER 01, 2016
Applies to:PeopleSoft Enterprise HCM Time and Labor - Version 8.9 to 8.9 [Release 8.9]
Information in this document applies to any platform.
Interface TL to PC - using the standard EIP called ACTUAL_TIME_BATCH_ADD
We’re using the standard EIP called ACTUAL_TIME_BATCH_ADD sending those messages from HR 8.9 to FSCM 8.8. Recently we did a PeopleTools upgrade from 8.47 to 8.52 and we have the following issue:
- The message ACTUAL_TIME_BATCH_ADD call the Application Engine PC_TL_TO_PC and in our old 8.47 database always the Message and the Application Engine was executed with a generic PeopleSoft user called PAM.
- After the upgrade the messages ACTUAL_TIME_BATCH_ADD came from HR with a PUBLISHER_ID different to PAM user and the Application Engine is executed with that user. That user is the user that originated the transaction in HR but not always that PUBLISHER_ID exists in FSCM so the Message stays in error. In other situations the Message run Success but the Application Engine is not executed with the generic user as was in 8.47.
The message ACTUAL_TIME_BATCH_ADD call the Application Engine PC_TL_TO_PC and in our old 8.47 database always the Message and the Application Engine should be executed with a generic PeopleSoft user called PAM.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms