Processing of PAR Actions

The PeopleSoft Human Resources USF functionality has separate tables for managing PAR, and these tables hold data until each action has been approved and completed by human resources. Any records held in the separate tables haven't completed the PAR process and don't exist to the rest of the system. After completion, the data is automatically updated to system tables to enable other processes, such as those in PeopleSoft Payroll, Benefits Administration, and Time and Labor.

To support the PAR processing concept, all of these records have been effective-dated and have been tied together with common keys. Because the three records (GVT_JOB, GVT_PERS_DATA, and GVT_EMPLOYMENT) work as one, a row is inserted into all three records when a user inserts a row on the Data Control page.

Once a PAR has successfully worked its way through the approval process, is processed by human resources as completed, and has become an actual event, it is ready to be copied into the three counterpart records (JOB, PERS_DATA_EFFDT, and EMPLOYMENT). The process is accomplished instantly, and the user is unaware of the updates to the other tables.

However, if the PAR action has an effective date that is later then the system date, only JOB is updated when the action is saved. PERSONAL_DATA and EMPLOYMENT are updated only when the date of the action is equal to the system date. This is because the counterpart to GVT_JOB, which is JOB, is effective-dated. Therefore, it receives the future effective-dated action and ignores it until that date.