Payroll Costing and Transfer to General Ledger

Thought to have this post , and tried to cover some of the vital information which purely focus on
Payroll to GL transfer Process.
What is purpose of Payroll Costing and Transfer to General Ledger ?
In Payroll area, the Costing process basically allocates payroll run which results to cost segments.

The Transfer to the General Ledger process transfers cost information to Oracle General
Ledger interface tables.
At the installation - setting up segments of the Cost Allocation key flexfield to determine the
windows in which users can select cost codes.
Oracle Costing you use a postpayroll run process to accumulate payroll costs.
For Oracle General Ledger you can map the segments of the Cost Allocation key flexfield to
the corresponding segments of the General Ledger Accounting flexfield.
If you do not using GL in same product, you may consider how to relate information on labor
costs entered in Oracle Human Resources to your financial systems.

Who drives the payroll costing :Its Cost Allocation Flex field Segments

Define a structure for your Cost Allocation Flex field which contains the segments you want to
use for your Business Group. You will use this structure to enter your payroll costing details in
Oracle HRMS.
You use Segment Qualifiers to control the level at which costing information can be entered to
the system. Each Qualifier determines the level at which costing information can be entered

How it works
The costing process picks up 'run
results'. The specific 'payroll actions'
that will be picked up by the costing
process are in
PAY_ACTION_CLASSIFICATION table
and have a CLASSIFICATION_NAME
of 'COSTED".
So the process will create an
assignment_action for every
assignment that has a run result
from one of the 'costed'
classifications.
The process then populates the

PAY_COSTS table with the run result value (costed value). The actual cost code is stored on the
PAY_COST_ALLOCATION_KEYFLEX table in the 'concatenated_segments' column, this is referenced
using the 'cost_allocation_keyflex_id' from PAY_COSTS. (Adopted - Source metalink)
When the Payroll costing results are transferred to Oracle General Ledger only the mapped segments
and the costing amounts are transferred. The data is transferred from the PAY_COSTS table into the
GL_INTERFACE table by running the Oracle Payroll process Transfer to GL. After the transfer from
Payroll is complete, the batch will need to be imported into GL. This is done by running the Oracle
General Ledger standard GL Import process .
Transfer Program to GL process populates the following columns:

status
set_of_books_id
accounting_date : This is effective date of payroll run
currency_code
date_created
created_by :801...which is the application id for Payroll
actual_flag
user_je_category_name :hard-coded as Payroll
user_je_source_name :hard-coded as Payroll
entered_dr :the dollar amount to be debited
entered_cr :the dollar amount to be credited
reference21 :payroll_action_id of the transfer to GL process from pay_payroll_actions
reference22 :cost_allocation_keyflex_id from pay_cost_allocation_keyflex

Which program take care of payroll cost transfer.

It is pytrangl.pkb, located in $PAY_TOP/patch/115/sql/pytrangl.pkb
What data is mapped from Payroll to General Ledger when information
Similar to other Application transfer program, Payroll transfer populates the following reference
columns in GL_INTERFACE:

Reference21 :Payroll_action_id of Payroll Transfer to GL process

Reference22 :Cost_allocation_keyflex_id of Payroll cost flexfield for this entry
Reference23 :effective date of the Payroll Run this entry is derived from
Reference24 :Date_earned of the Payroll Run this entry is derived from
Reference25 :Payroll_action_id of Payroll Run this entry is derived from

Journal import is then placed these in reference1, reference2, reference3, reference4 and reference5
in GL_IMPORT_REFERENCES table.
The GL_IMPORT_REFERENCES columns are actually populated during the GL Journal Import process.
Although these are mapped from the columns in the GL_INTERFACE table, the 'Transfer to GL' process
does not actually populate the GL_IMPORT_REFERENCES table
Technical Tables Involved

pay_assignment_actions
pay_action_interlocks
pay_assignment_actions
pay_gl_interface
pay_cost_allocation_keyflex
gl_import-refrence
gl_interface