Update journal category, journal description

When you transfer payroll cost from Payroll to General Ledger using Transfer to GL process, there is no option to tell that these journal should be created with this category or description or change accounting date.

These payroll cost will be inserted in GL_Interface table once transferred to GL from where you can import these into journal batch using Journal --> Import. Normally these journal with be created with journal category Payroll and description like Payroll: request id (of transfer to gl process).

Because these journal doesn't automatically get imported you have option to write a custom process where you can update information about journal. Here is information about columns of GL_INTERFACE

REFERENCE1 Batch name.

REFERENCE2 Batch description

REFERENCE4 Journal entry name

REFERENCE5 Journal entry description

REFERENCE6 Reference or journal number

REFERENCE7 Reverse Journal Flag

REFERENCE8 Reverse Journal Period

REFERENCE10 Journal line description

So you can update these columns with information what you want on Journal. e.g. if you want to make journal with description payroll cost (including bonus) then you can update REFERENCE5.

Please let me know if you have any questions on this post.

Customize Partial Period Accruals Calculation

Recently my client has a requirement to post result of partial period accruals calculation (estimated costing) after removing some of accounts (one of segment of cost allocation keyflex) in GL. Because Oracle doesn't give any parameters by which you can remove some estimated cost based on criteria of Account (element or element classification) so you have 2 options

1) Customize partial period accruals calculation process and filter result

2) write your own custom process

As Partial Period Accruals Calculation is a standard oracle process and pyugen based so there is no good in customizing this process. Writting your own custom process to do whole job of calculating estimated cost will be very tidious.

But there is a catch here which is that oracle process only calculate estimated cost and don't automatically post the results to GL or submit transfer to GL automatically. So a custom process can be written which accepts account number as parameter and then scanning result from Partial Period Accruals calculation process one by one using account number. If it found a match it will set transfer to gl flag in pay_costs to N and estimated cost will not be transferred to GL.

You need to remember here that you not only have to remove costing part of estimated cost but balancing part as well. If your client has fixed costing or simple costing then it will match one to one but in case of distributed costing you can get more than one costing part of estimated cost but balancing is a single value.

Please let me know if you have any questions regarding above article.

Partial Payroll Accruals to GL

Most of times your payroll periods date doesn't match with GL periods so your cost shown in GL will not be correct because it doesn't has cost for days between GL period end date and payroll period end date.

Oracle payroll provides a process named Partial Payroll Accrual Calculation to estimate cost for days missing in GL period. e.g. payroll period end date is 28-Feb but your GL period is ending on 21-Feb. In this case 7 days (28-Feb - 21-Feb) cost will be missing. The process provided by Oracle Payroll will calculate an estimate cost based on difference between payroll period end date and GL period end date divided by total number of days in payroll period multiply by actual cost for some pervious periods.

Vertex Tax Interface

Tax interface tells Oracle Payroll engine what vertex elements will be used while running payroll processes. There are 3 options

1) Standard - uses old vertex element and not recommended by Oracle

2) Enhanced - uses new vertex element and recommended by Oracle

3) Enhanced + Wage accumlation - This option uses new vertex element as well as accumulate wages for locality where tax are not calculated. e.g. A person lives in A city and works in B city. According to reciprocity rule, he is required to pay taxes only in B city but A city tells him to report his wages. In such cases this option is really helpful.

There is a process given by Oracle payroll named Select Tax interface by which you can set what option will be used. This is a package based concurrent program

Invalid or Processing status records - Generate Run Balances

There can be following reasons for processing status

1) Generate run balances process is still running

2) You had PROCESS_TIMEOUT for this process and that limit is reached so process was gracefully terminated.

3) Generate run balances process has been terminated or killed due to some reason

so you can wait till process complete sucessfully in case of process still running.

You can find what are all balances which are in invalid or processing status with following SQL

SELECT * FROM PAY_BALANCE_VALIDATION;

Now you have two options in case of PROCESS_TIMEOUT or termination/killed

OPTION 1: Retry the GRB (Preferred Solution as it starts back up where it left off)

Resp: Responsibility Generate Run Balance was Submitted Under

Nav: Process & Reports > Submit Process & Reports > Single Request

Name: Retry US Payroll Process (US Legislation)

Parameters:

- Process Year: 4712

- Process Type: Magnetic Report

- Process: LOV

The LOV should show the Generate Run Balance process that have executed.

Select the process to retry.

OPTION 2: Start the process over (Note: All previous will be lost)

In order to get the status to change from Processing - you must manually switch the status flag (Contact Support for information concerning how to perform this) from P (Process) to I (Invalid).

Then the process can be submitted again with the MODE parameter set to ALL INVALIDS.

NOTE: That running the ALL BALANCES or ALL INVALIDS (if there is a large quantity) for ASSIGNMENT Level will process for a long time.

Please note that it is recommended that when ever executing the GRB or ARDB for ALL BALANCES or ALL INVALID (if a large amount exist) that the PROCESS_TIMEOUT parameter should be set on the Pay_Action_Parameters table to control the execution time of the process.

Future Dated balance Adjustment

You can't run payroll or quickPay for employees if a future dated balance adjustment exists for this employee.

Does Transfer to GL Process rollback remove rows from GL_INTERFACE table

Yes. If you rollback Transfer to GL Process, it will remove records from GL_INTERFACE table unless they have been imported.

Check Oracle Application version for Specific Module

Following query can be used to find module version

select to_number(substr(product_version,1,2))

from fnd_product_installations

where APPLICATION_ID = 800

reference column details :GL_INTERFACE

reference21 :payroll_action_id -- payroll action ID for Transfer to GL process

reference22 :cost_allocation_keyflex_id

reference23 :run_date -- payroll run check date

reference24 :run_date_earned -- payroll run date earned

reference25 :run_action_id -- payroll action ID for payroll run process

The package called by Transfer to GL process : pay_trgl_pkg.trans_pay_costs

Transfer to GL Process transfer on date earned

If you want to set the accounting date for the transfer to date earned, then change the TGL_DATE_USED pay action parameter to "E".

If you do not do this then the accounting date of the transfer defaults to the check/cheque date of the originating payroll

Due to the fact that employees need to have distributed labor costs as per the time period derived from date earned , instead of the time period that payroll populates in payroll tables. Utilizing the parameter TGL_DATE_USED set to the value of ‘E’, will send transactions to GL based on date earned (when switch is enabled), Labor Distribution will also pick up only on the basis of date earned. The get_payroll_assig actions was modified to pick on the basis of date earned for regular run, quick pay and reversals.

Not Set - Normal costing will be transferred with an Accounting Date of the payroll run's effective date. Reversal of Estimate Costing will be transferred with an Accounting Date of the payroll periods Pay Advice Date + Payroll Offset Days.

'E' - Normal costing will be transferred with an Accounting Date of the payroll run's Date Earned. Reversal of Estimate Costing will be transferred with an Accounting Date of the payroll period's end date.

'EVE' - Normal costing will be transferred with an Accounting Date of the payroll run's effective date. Reversal of Estimate Costing will be transferred with an Accounting Date of the payroll period's end date.

Values Null, E or EVE

Default Value Null

Parameter Type Costing

Processes Used In TRANSFER TO GL

Modules Used In PACKAGES

PAY_TRGL_PKG (pytrangl.pkb)