Last updated on SEPTEMBER 05, 2017
Applies to:Oracle Fusion Global Payroll Cloud Service - Version 220.127.116.11.0 and later
Oracle Fusion Global Payroll - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
The business requirement is to handle the mid-month transfers.
Oracle confirmed that there is no standard process and suggested to go with manual work around wherein we need to end all the element entries as on transfer date and re-create all the element entries on transfer date +1.
Customer has denied the work around mentioning that every month there will minimum 400 transfers and it will be huge maintenance for them.
User needs to change now PER_EXT_PAY database items to TERM_PAYROLL_ID with a CHANGE_CONTEXTS statement to set EFFECTIVE_DATE context
By using those DB items, user is not able to achieve the result as expected for the elements where the amount has to be paid in full.
Example, the customer has an information element where no proration exists.
For mid-month transfers, the total amount of that month should split to two payrolls based on the number of days in that payroll.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms