Set up Statutory Absences

To enable statutory absence calculations with your current implementation, perform the following steps:

1. Identify the period for which the statutory payment history needs to be created.

   For sickness absences, it is advisable to create at least 6 weeks of history before the Absence Processing Start Date, that is, the date when you want to start processing absences in Fusion. This is because sickness absences are linked if they fall within 6 weeks of any previous absences. You can create more statutory payments history, if required. For maternity, paternity, adoption absences, you can evaluate only those absences that are ongoing on the Absence Processing Start Date. Hence, at the most it would be 52 weeks before the Absence Processing Start Date.

   You must create all the setup objects on or before that date.

2. Create Placeholder Rate Definitions
3. Create Absence Elements
4. Edit the Entitlement result formula to add the Absence Processing Start Date.

   To stop calculation cards being processed in payroll for the portion of absence that has already been paid, set the Absence Processing Start Date to the date you want to start processing absences in Oracle Global Payroll. No absences will be processed before this date.

   Note: The Absence Processing Start Date is stored in the payroll formula attached to your absence element. Copy and edit this formula to enter the Absence Processing Start Date.

   To edit the payroll formula:

   1. Select the Manage Fast Formula task from Payroll Calculation work area.
   2. Search for Formula name <Element Name> Entitlement Result.
   3. Select Edit, and Correct from the Edit menu.
   4. In line 84, update the code as shown here:

   l_migration_date = ‘2018/01/01 00:00:00’ (date)
   In line 97, insert the following lines:
   IF (l_abs_comp_date < l_migration_date) THEN
         (
           l_stop ='Y'
           l_log = PAY_INTERNAL_LOG_WRITE('$$$%%%% - Migration Date is greater than absence date  ::::' || to_char(l_migration_date) )
           pay_value = 0
           unit = 0
           deduction = 0
           net_pay = 0
           RETURN unit ,reduce_type , pay_value ,deduction , net_pay , dir_comp_id,dir_card_id , rate,ded_amount_rate,factor
         )

5. Click Save.
6. Compile the formula.
7. Repeat for all the Entitlement Result formulas.

Optionally, if the Qualifying Days for Statutory Sick Pay purposes are based on a work schedule different from the employee work schedule, ensure that you set up an alternate statutory sick pay schedule, as shown in the topic:Overview of Setting Up Plan and Type for Statutory Sick Pay.

1. Create the absence statutory plans. Refer to these sections:
   • Create Maternity Absence Plans
   • Create Adoption Absence Plans
   • Create Paternity Absence Plans
   • Create Sickness Absence Plans
2. Modify the existing absence types (as of the date identified) using these steps:
   1. Add the validation formula
   2. Select the legislative grouping code
   3. Attach the newly created statutory plan to the absence type
   4. For Sickness absence type, add the linking rule (SSP only)
   5. Associate the certifications
   For further information on how to set up the absence type, refer to these sections:

   • Create Maternity Absence Types
   • Create Adoption Absence Types
   • Create Paternity Absence Types
   • Create Sickness Absence Types

Prepare the Data

After the setup is complete, ensure that the Statutory Payment history is created for existing absence records. You can do that by running the Evaluate Absence process that automatically processes statutory payment for existing absences.

Based on the statutory plans created, it identifies that a new plan was added to the absence type, and generates entitlement to that plan.

If the employee is found ineligible for payment, a certification is automatically created. It results in the same SSP entitlement calculation that the employee received for SSP in your legacy application.

Note: The process also generates the absence calculation cards. Only those calculation cards with an effective date after the absence processing start sate will be processed in payroll. Hence, the date prevents any previously paid absences to be paid again in the Oracle Fusion application.