Wednesday, February 9, 2011

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.

Thursday, February 3, 2011

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.

Wednesday, January 26, 2011

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.



Friday, January 14, 2011

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