Summary

Payroll does not deal with a lot of tables, in comparison with other modules like Benefits / Core-HR. So the idea was to go through the functional set ups first and then look at the technical aspects, and peep through the tables.

PAY_ELEMENT_TYPES_F: No need to say, that this is a date track enabled table. This table stores the details about all the elements in the system. The Primary key is ELEMENT_TYPE_ID and the two date fields. This is usually used to get the name of the element, as ELEMENT_TYPE_ID is used in a lot of places to refer to the element.

PAY_ELEMENT_LINKS_F: This one is date track enabled as well. This one stores the details on the links. The primary key is: ELEMENT_LINK_ID and the two date tracked columns, stores the ELEMENT_TYPE_ID as the foreign key.

PAY_INPUT_VALUES_F: This table stores the Input values for each element. This is the Date track enabled table. The primary key is INPUT_VALUE_ID and the two date tracked columns. This table also holds the ELEMENT_TYPE_ID as a foreign key to PAY_ELEMENT_TYPES_F. This can be used to pull in the Element input value name.

PAY_ELEMENT_ENTRIES_F: This is another Date tracked table. This one stores the details about the element entries. The table stores the Entries with the ASSIGNMENT_ID and the ELEMENT_LINK_ID as foreign key. The Primary key is ELEMENT_ENTRY_ID. This table also links itself to PAY_ELEMENT_TYPES_F with storing ELEMENT_TYPE_ID as a foreign key.

PAY_ELEMENT_ENTRY_VALUES_F: This date track enabled table stores the values for each entry. This table has only 6 columns. Out of which, the Primary key is: ELEMENT_ENTRY_VALUE_ID and the two date tracked columns, it stores the ELEMENT_ENTRY_ID as the foreign key to PAY_ELEMENT_ENTRIES_F and the SCREEN_ENTRY_VALUE stores the actual value of the Input Value. The INPUT_VALUE_ID column links the table to the Input values table (PAY_INPUT_VALUES_F).

PAY_PAYROLL_ACTIONS: This table logs all the actions taken by the Payroll Engine. Primary key is PAYROLL_ACTION_ID, and it logs in each and every activity. The Table is capable enough to store a lot of information as it has got columns to store all kind of data used in Payroll; although it does not populate all the columns / row. However it logs in only the ones those are needed.

PAY_RUN_RESULTS: This table stores the status related to the elements against the assignment actions. The primary key is RUN_RESULT_ID. ELEMENT_TYPE_ID and ASSIGNMENT_ACTION_ID are the two other important foreign keys.

PAY_RUN_RESULT_VALUES: This table takes the RUN_RESULT_ID and the INPUT_VALUE_ID and stores the Value obtained by the Payroll Engine.

So these were the important tables in Payroll. However here is a list of few others, which are use very frequently.

• In the table below, if the Date tracked column is marked as Yes, assume the Primary key to be Composite. The given Primary with bind with the two date tracked columns to make the Composite Primary key.
• The below table is in Alphabetical order.
• Some of the values in the column Table could be a view / synonym. However they pull data. That's what we want right? :)