Global Payroll & Absence Mgmt Process (GPPDPRUN) Runs To Success Where It Should Not Have.
(Doc ID 2195693.1)
Last updated on OCTOBER 04, 2017
Applies to:PeopleSoft Enterprise HCM Global Payroll Core - Version 9.1 and later
Information in this document applies to any platform.
On: 9.1 PeopleSoft Enterprise HCM Global Payroll Core, COBOL
Global Payroll & Absence Mgmt process (GPPDPRUN) runs to success where it should not have.
An issue has been found with the GP Payroll & Absence Calculation process when a pay calc is run for an entire Calendar Group ID.
If the pay calc is being run by a user and another user kicks off another pay calc with the same parameters, the second pay calc is terminated, but the process monitor run status shows it successfully ran.
Reviewing the log output(The Calendar Group (and Stream) is in process by user %1 using Run Control %2. Run terminated), the log states the run terminated.
The issue can be reproduced with the following steps:
1. Run pay calc for a calendar group
2. Run another pay calc for the same calendar group id using a different Run Control ID, when the first pat calc is still processing
3. Once the two processes have completed review the process monitor details. The second pay calc process instance indicates it ran to success
4. However reviewing the associated instance log it states the following
This Calendar Group (and Stream) is in process by user %1 using Run Control %2. Run terminated.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document