Scribd
Upload
197 views1 page

Understanding PeopleSoft Global Payroll Identification

Employees selected for PeopleSoft Global Payroll processing are identified based on certain criteria. The identification reason for each employee is stored in the GP_PYE_PRC_STAT table and indicated by a SEL_RSN code, which can be 01-0B depending on factors like whether the employee is active, included in a payee list, or has a positive input or retroactive calculation associated with them. Understanding the identification reasons allows users to know why each employee is selected for payroll processing.

Uploaded by

Alex
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
197 views1 page

Understanding PeopleSoft Global Payroll Identification

Employees selected for PeopleSoft Global Payroll processing are identified based on certain criteria. The identification reason for each employee is stored in the GP_PYE_PRC_STAT table and indicated by a SEL_RSN code, which can be 01-0B depending on factors like whether the employee is active, included in a payee list, or has a positive input or retroactive calculation associated with them. Understanding the identification reasons allows users to know why each employee is selected for payroll processing.

Uploaded by

Alex
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

Understanding PeopleSoft Global Payroll Identification

The first stage in PeopleSoft Global Payroll processing is the identification of


the employees to be calculated. Several criteria are used to determine which em
ployees should be selected. Understanding why an employee is selected is not alw
ays evident to users. In this post I'm sharing how I normally determine the iden
tification reason.
Once you run the identification stage, the employees to be processed are stored
in the GP_PYE_PRC_STAT table. This table not only shows which employees are goin
g to be calculated, but also indicates which calendars will be considered. This
is particularly important when running retroactive calculations, as it allows yo
u understanding the impact of this type of calculations.
In any case, going back to the identification, in this table you will find the S
EL_RSN field, which contains a code that translates into the reason behind the e
mployee identification. The valid values that this field may take are:
01: The employee is active during the calendar period and included in the Payee
List associated to the calendar.
02: The employee is inactive (but was active before the start of the calendar pe
riod) and included in the Payee List associated to the calendar.
03: The employee is active during the calendar period and has a positive input a
ssociated to him/her.
04: The employee is active during the calendar period and has a retro trigger as
sociated to him/her.
05: The employee is active during the calendar period and associated to the cale
ndar pay group.
06: The employee is inactive during the calendar period and associated to a posi
tive input in the current calendar.
07: The employee is inactive (but still associated to the calendar pay group) an
d has a retro trigger associated to him/her.
08: The employee is inactive but has a retroactive calculation delta from a prev
ious calendar which has not been picked yet.
09: The employee is inactive but has a retroactive calculation correction from a
previous calendar which has not been picked yet.
0A: The employee is active and linked to the calendar using an override.
0B: The employee is inactive and linked to the calendar using an override.
From a technical standpoint, you can check the SQL used to select each reason by
check the stored statement under the name GPPIDNT2_I_PRCnn, when nn is the SEL_
RSN

You might also like