11/26/2021

Peoplesoft Workflow Transaction Tables

We have created a custom AWE for Contractor Onboarding transaction to be approved from fluid Approval Tile (in PS 9.2). We are successfully able to route the approval of this transaction to Approval Tile using the Page Composer functionality. The transaction summary is also correctly getting displayed in Approval Tile. The issue is that the transaction request is in the header table and in the XREF table. Keys populated correctly. But the thread ID from that xref table does not exist in eoawstepinst; consequently, not in eoawuserinst. This particular transaction should have a step to approve, and that step is not there. Every transaction should insert/update a row in this table. For the Workflow we are about to setup, it should be record in which every time a request for the Asset/Amount is submitted for approval, corresponding one row is affected in this table.

TablesI was thinking of writing a short yet extremely useful post and the first thing that came to my mind is Application Tables....For a table driven product like peoplesoft, getting to know the main records and their function is a huge plus.

Peoplesoft Tables. October 14, 2015. This record is a child of EPAPPR and is used to store data about each step of the workflow approval process for a Performance.


So here is a very quick list of important tables in Absence Management.
1. PS_GP_PIN - Table that stores the pin details of all elements in GP/AM. Use to retrieve the Pin Name or Pin Code corresponding to a pin number.
2.

Peoplesoft Approval Workflow

PS_GP_ABS_EVENT - Major transaction table in Absence Management. All absences reported get stored in this table. The data in this table the raw reported absence. This table is analogous to the TL_RPTD_TIME table in Time and Labor.Peoplesoft approval workflow
3. PS_GP_RSLT_ABSTables - Table containing the calculated result of reported absence takes. The source for this table is GP_ABS_EVENT. This table is analogous to the TL_PAYABLE_TIME table. This table will contain one row for each day of the absence event. For example, an employee might report sick leave from the 1st to 5th of a month. GP_ABS_EVENT will have a single entry for the above event with a start date and end date. But, GP_RSLT_ABS will have five rows with each row containing the number of hours or days of absence.
4.

Peoplesoft Workflow Tables

PS_GP_RSLT_ACUM - Table containing the results of the accumulators in GP/AM. Accumulators can be used to track absence balances, cumulative takes, cumulative paid hours etc. This table is populated only after the absence calculation COBOL is run.
5. PS_GP_CAL_RUN - Table containing details regarding the Calendar Group ID. The Calendar Group ID is the major run control parameter used for running the absence processes and is a collection of various calendars.
6. PS_GP_PI_GEN_DATA - Any absence event that need to be sent to payroll will require a positive input (in terms of an Earning Code) to be defined. The positive input can be attached to a take in the Absence Take setup page. This table contains the corresponding positive input for the processed absences.Emails
Peoplesoft workflow configuration

Peoplesoft Workflow Template

7.

Peoplesoft Workflow Transaction Tables Examples

PS_GP_ABS_SS_STA

Peoplesoft Workflow Transaction Tables Template

- This table is coupled with the GP_ABS_EVENT table and is a workflow table. This table can be used to know the workflow status of an absence event. A separate entry is created for each workflow actions like Submit, Approval etc. This table can be very useful to track details regarding the approval/workflow status of an absence event.