Common Considerations for Migrating Absences
A few important points need to be considered before migrating statutory absences.
Prerequisites
You can load absence records using the HCM Data Loaders (HDL). For further information, refer to the Oracle Help Center, Integrating with HCM Loading Absence Topics section.
When loading absence records using HDL, the application processes absences in the same way as when they are entered using the Absence Management user interface: the entitlement is calculated based on the plans associated to the absence type, and the corresponding calculation card generated in Global Payroll. It is therefore important that, before the migration of any absence records, you must have completed the absence setup. This includes:
- Creating the absence types
- Associating the predefined certifications to the absence types
- Creating the statutory and occupational absence plans
- Creating payroll elements and associating them with the corresponding absence plan
Otherwise, the application might not create the migrated absence records accurately.
Absence Processing Start Date
To stop calculation cards being processed in payroll for the portion of absence that has already been paid in your legacy application, you need to set the Absence Processing Start Date to the date you want to start processing absences in Oracle Global Payroll. No payment will be made before this date.
To edit the payroll formula:
- Select the Fast Formula task from Payroll Calculation work area.
- Search for formula name <Element Name> Entitlement Result,
- Select Edit to edit the formula.
- In line 84, update the following: l_migration_date = ‘2018/01/01 00:00:00’ (date) with the date payments should start.
- Click Save.
- Compile the formula.
- Repeat for all the Entitlement Result formula.