The following table shows the predefined elements for payroll runs.
| Element Name | Description |
|---|---|
| GOSI | This is a recurring element that is attached to each assignment and initiates GOSI processing. It has a formula attached to it, which returns the calculated values to the indirect elements. |
| Employer GOSI Hazards | This is a non-recurring element that contains the value of the employer's liability for GOSI Hazards. |
| Employer GOSI Annuities | This is a non-recurring element that contains the value of the employer's liability for GOSI Annuities. |
| Employer GOSI Subsidy | This is a non-recurring element that contains the value of the additional employer's liability for GOSI Annuities. |
| Employee GOSI Annuties | This is a non-recurring element that contains the value of the employee's liability for GOSI Annuities. |
| GOSI Reference Salary | This is a non-recurring element that contains the value of the employee's reference salary for GOSI deductions. |
| Employee GOSI Arrears | This is a non-recurring element that contains the value of the employee's outstanding GOSI liability. |
| Employee GOSI Arrears Payment | This is a non-recurring element and contains the value of the employee's payment to reduce the GOSI arrears. |
| GOSI Reference Salary Adjustment | This is a non-recurring element and contains the value of the salary adjustment for GOSI. |
| Setup GOSI Reference Salary | Use this non-recurring element if you want to specify a pay value as the base for calculating GOSI deductions throughout the year. Otherwise the payroll run calculates GOSI deductions using the formula attached to the GRE. |
| PPA | Non-recurring indirect element triggered by GOSI/PPA element depending on the organization classification set at the organization level. This element triggers the PPA related calculations by calling the SA_PPA_CALCULATION formula. |
| Setup PPA Reference Salary | Non-recurring direct element that contains the employee's contributory salary for the current year. |
| PPA Reference Salary Adjustment | Non-recurring direct element to modify the reference salary anytime in between the year, since you can set up the Setup PPA Reference Salary element only once a year, during the start of the year. |
| PPA Reference Salary | Non-recurring indirect element that displays the value for the reference salary (contributory salary). |
| Employee PPA Annuities | Non-recurring indirect element that displays the value for the employee PPA contributions. |
| Employer PPA Annuities | Non-recurring indirect element that displays the value for the employer PPA contributions. |
| Employee PPA Arrears | Non-recurring indirect element that stores the excess amount in case the PPA annuities value for a particular payroll period is more than the net payment during the payroll run. |
| Employee PPA Arrears Payment | Non-recurring direct element that you must attach to pay the arrears. |
| Employer PPA Hazards | Non-recurring indirect element that displays the value for the employer occupational hazards contributions. |
| Group Decision Information | Use it to capture the Group Decision number |
The following table shows the two predefined element sets for earnings and deductions. You can use these element sets to view the information in SOE report.
| Element Set Name | Description |
|---|---|
| SA_SOE_EARNINGS_ELEMENTS | Use this element set to hold the earnings elements. |
| SA_SOE_DEDUCTIONS_ELEMENTS | Use this element set to hold the deductions elements. |
The survey of the classifications identifies:
The processing priority range, default priority, and cost type for each classification
A list of the predefined secondary classifications within each primary classification
Primary element classifications are supplied as startup data, and you cannot delete or update them as they are designed to meet legislative requirements.
| Classification | Meaning |
|---|---|
| Information | Information elements can be used to represent information items that are not used in payroll processing. They can also be set up to hold information for use in other elements, and to trigger the processing of other elements, for example, loan details. |
| Earnings | Earnings elements represent most payments made to an employee. These payments are usually subject to deductions of tax and Social Insurance, and are normally processed in the regular payroll run each period. |
| Absence | Absence elements represent the absence. |
| Supplemental Earnings | Supplemental Earnings element includes special earnings paid in addition to the earnings for time worked. |
| Taxable Benefits | Taxable Benefits elements represent the taxable benefits. |
| Pre-Statutory Deductions | Pre-Statutory Deductions elements represent the deductions that are applicable before the statutory deductions. |
| Statutory Deductions | Statutory Deductions elements are for mandatory GOSI deductions. |
| Direct Payment | Direct Payment elements are for expenses or loans made through the payroll that are not subject to tax. They are included in gross or net pay balances. |
| Employer Charges | Employer Charges element represent payments such as contribution made to any statutory bodies by the employer for the employee. |
| Involuntary Deductions | Involuntary Deductions elements are compulsory deductions. |
| Voluntary Deductions | Voluntary Deductions are those deductions that the employee authorizes the employer to make on their behalf. |
The following table shows the default processing priority and costing details for the primary classifications supplied.
| Primary Classification | Priority Range | Default Priority | Cost Type |
|---|---|---|---|
| Information | 0-12000 | 500 | Debit |
| Earnings | 1001-2000 | 1500 | Debit |
| Absence | 2001-3000 | 2500 | Debit |
| Supplemental Earnings | 3001-4000 | 3500 | Debit |
| Taxable Benefits | 4001-5000 | 4500 | Debit |
| Pre-Statutory Deductions | 5001-6000 | 5500 | Credit |
| Statutory Deductions | 6001-7000 | 6500 | Credit |
| Direct Payment | 7001-8000 | 7500 | Debit |
| Employer Charges | 8001-9000 | 8500 | Debit |
| Involuntary Deductions | 9001-10000 | 9500 | Credit |
| Voluntary Deductions | 10001-11000 | 10500 | Credit |
This table shows the predefined secondary classifications supplied. You cannot update or delete these predefined classifications.
An element is automatically given any default secondary classifications defined for its primary classification.
| Primary Classification | Secondary Classification | Default |
|---|---|---|
| Information | Subject to GOSI: Information | N/A |
| Earnings | Subject to GOSI: Earnings | N/A |
| Absence | Subject to GOSI: Absence | N/A |
| Supplemental Earnings | Subject to GOSI: Supplemental Earnings | N/A |
| Taxable Benefits | Subject to GOSI: Taxable Benefits | N/A |
| Pre-Statutory Deductions | Subject to GOSI: Pre-Statutory Deductions | N/A |
Oracle HRMS provides a convenient way to maintain information about the various absence types your enterprise recognizes. To facilitate reporting and analysis of employee absences, you can distinguish between absence types and absence categories. An absence category is a group of related absence types.
Some absence categories may be predefined for your legislation. The table below contains examples of absence categories and types, for illustration purposes only. You can extend the list of predefined categories and define your own absence types, as required.
Example Absence Categories and Types:
| Absence Category | Absence Type |
|---|---|
| Medical Leave | Illness or Injury |
| Work-related Injury | |
| Work-related Illness | |
| Medical Appointment | |
| Family Leave | Paid Maternity/Paternity |
| Unpaid Maternity/Paternity | |
| Dependent Care | |
| Personal Leave | Compassionate Leave |
| Personal Business | |
| Professional Leave | Certification Classes |
| Meeting Attendance |
Also, to assist with absence reporting and analysis, you can provide reasons to select from when recording employees' time taken for an absence type. For example, if you need information to analyze the particular family-related responsibilities that cause employees to miss work, you can define reasons for absence types as follows:
Example Absence Category, Types and Reasons:
| Absence Category | Absence Type | Absence Reasons |
|---|---|---|
| Family Leave | Paid Maternity/Paternity | Birth of a child |
| Adoption of a child | ||
| Dependent Care | Child Care | |
| Elder Care | ||
| Disabled Care |
Setting up each absence type is essentially a two-step process. One step involves defining the type, that is, entering its name, and optionally selecting a category and reasons for it. The other step involves defining an element to associate with the type. This element serves two important purposes:
It provides a way to maintain a running total of time taken for the absence type. The Absence Detail window shows the running total of absences with an end date before the effective date, and with an absence duration on record. Each absence can add to, or subtract from, the running total, depending on how you define the absence type.
It provides a way to restrict employee eligibility for the absence type. The links you build for the element establish which employees are eligible to use the type.
For example, if the absence type compassionate leave is available only to full time employees, you link its element to the assignment category Full Time.
To hold a single running total of time taken for two or more absence types, you associate all the types with the same absence element. For example, your absence category Personal Leave may include two absence types you need for certain reporting purposes, Compassionate Leave and Personal Business. However, you require just one running total to be kept of employees' time taken for both types of personal leave. In this case you simply associate both absence types with the same absence element.
Note: If you want to use absence types without recording accrued totals or eligibility rules, you can define the type with no associated element.
You can associate each absence type with a recurring or nonrecurring absence element. Each element has an input value with either hours or days as its unit of measure.
Nonrecurring element entries are valid for one payroll period. When you enter an absence of a type associated with a nonrecurring element, the application creates an element entry for the period in which the absence start date falls. For example, if you enter an absence that starts on 4 May for someone on a monthly payroll, the entry is dated 01 May to 31 May.
The entry is only created when you enter the absence end date, and you must enter the absence duration at the same time. The duration can be defaulted if you set up an absence duration formula. The full value of the absence duration is recorded in the absence element entry, even if the end date falls outside of the payroll period.
Important: This option is only available if you use Oracle Payroll and the Proration functionality is enabled in your localization.
UK Users: If you use the Statutory Absence Payments feature you must continue to use nonrecurring elements to record long term sick leave.
Use this approach if you want to begin processing absences before end dates are recorded. You do not enter absence duration on the recurring element entry. Instead, you use a payroll formula to calculate the absence duration to be processed in each payroll period. Use the absence duration formula to calculate the duration displayed on the Absence Detail window. This value is deducted from the current PTO accrual when you enter an end date for an absence type that is associated with a PTO accrual plan.
Recurring element entries start on the absence start date and end on the absence end date (if there is an end date). If the absence ends in the middle of a payroll period, the payroll run detects and processes the absence using the proration functionality.
When you define an absence type, you specify whether the application should maintain an increasing balance, a decreasing balance, or no balance of time off. The balance is a running total of the hours or days an employee has taken for the absence type, as recorded in the Duration field.
As you would expect, an increasing balance for an absence type starts with no time entered, and increases as you enter employees' hours or days absent. For example, if the absence type Compassionate Leave has an increasing balance, the balance starts from zero for each employee and increases by the number of hours entered for each absence of this type.
Increasing balances are appropriate for most absence types. For absence types for which your enterprise sets a maximum time allowed, the system issues a message when an entry of time absent exceeds this maximum, or Oracle Alert can notify you when an employee reaches the maximum time or takes excess time.
See: Oracle Alert User's Guide
When defining an absence type for a PTO accrual plan, you give it an increasing balance that shows the employee's accrued time taken. When you record an absence using the Absence Detail window, you can see the amount of accrued time a plan participant has available for use as vacation or sick leave.
If your enterprise sets a maximum time allowed for an absence type, you have the option of setting up a decreasing balance for this type, instead of an increasing balance. (If the absence type is used for a PTO accrual plan, it is simpler to use an increasing balance and an accrual formula that records an up-front accrual amount.)
For example, suppose your enterprise allows certain employees 32 hours leave per year for professional development. The Professional Leave absence type can have a decreasing balance, and an initial entry of 32 hours.
If you record an employee absence of 4 hours for this absence type, the decreasing balance shows 28 hours still available to be taken.
Decreasing absence balances require more maintenance than increasing balances. They need a prorated initial balance entry for all eligible new hires throughout the year, and require resetting each year for all eligible employees.
Notice that an absence type cannot have both a decreasing and an increasing balance; it has one or the other.
You can initialize or adjust an absence balance using the Element Entries window, or the Element Entry API. You can also initialize a decreasing balance by entering a negative value using BEE. For example, if you enter -16 hours using BEE, a decreasing balance starts at 16 hours. However, be aware that using BEE creates an absence record that will show on employees' absence history.
You can define an absence element as an Information element or an Earnings element.
If you define an Information absence element, you can use a recurring Earnings element to manage the calculation and payment of vacation and sick pay. When you define the absence element, you check the Database Item box for the input value that holds the absence balance. Entries to this input value then become database items that formulas for payroll calculations can access.
US Users: You will typically set up your absence elements in the Information classification for employees who do not submit timecards (Timecard Required = No on the Statutory Information tab of the Assignment window). If you are using the seeded Regular Salary or Regular Wages elements, the payroll run creates indirect results for the seeded Vacation Pay or Sick Pay elements when it finds absence entries in the Vacation or Sickness categories. These elements appear on the Statement of Earnings, but the Information elements do not. You do not need to set up any additional absence Earnings elements for these employees.
Other localizations: Typically, you define an Earnings element to have a skip rule that triggers processing when it finds an entry for the absence element. The element's payroll formula uses the database item for the entry value so that it automatically gets the sum of all the entries in the pay period. Then, using the salary database item to get the salary or hourly rate, it calculates the total absence pay for the period. You can also use the formula to reduce regular earnings for the period so employees do not get paid twice.
The advantage of this approach is that it simplifies the processing of absence payments into one calculation.
Select the Earnings classification for absence elements if you want to process absences individually in each payroll period. You can use these elements with Oracle Time and Labor. This approach creates a one-line entry on the statement of earnings for each absence type. Typically, you would create nonrecurring Sick and Vacation Pay earnings elements. You can also create different absence elements for each rate or multiple of pay if the element must appear on the statement of earnings as a different line item.
US Users: For employees who do submit timecards (making entries in BEE to the Time Entry Wages element), you can create your absence elements as Earnings. This also applies if you do not use the seeded Regular Salary and Regular Wages elements, and you want your absence payment to show on the Statement of Earnings. Use the Earnings window to initiate the element. Select the Category Regular and check the Reduce Regular box.
Oracle Payroll users: If you enter or update an absence retrospectively, or you delete an absence that started in the past, these changes are listed in the Retro Notification report the next time you run this report. This enables you to use RetroPay to correct any payroll processing.
Oracle HRMS provides a convenient way to maintain information about the various absence types your enterprise recognizes. To facilitate reporting and analysis of employee absences, you can distinguish between absence types and absence categories. An absence category is a group of related absence types. The following list contains the predefined absence categories available for Saudi government sector absences. You can extend the following list of predefined categories and define your own absence types, as required:
Saudi Accompaniment Leave
Saudi Pilgrimage Leave
Saudi Sick Leave
Saudi Edda Leave
Saudi Education Leave
Saudi Extended Maternity Leave
Saudi Literature Activity Leave
Saudi Marriage Leave
Saudi Maternity Leave
Saudi Cultural Activity Leave
Saudi Relief Work Leave
Saudi Death Leave
Saudi Emergency Leave
Saudi Exams Leave
Saudi Social Activity Leave
Saudi Unpaid Leave
Saudi Annual Leave
Saudi Dialysis Leave
Saudi Sports Activity Leave
Saudi Serious Sick Leave
Saudi Compensatory Leave
Oracle HRMS enables you to record the absence information for public sector employees to receive the applicable absence benefits.
To set up public sector absences
Create information element for each absence category; for example, Accompaniment Leave element for Saudi Accompaniment Leave absence category.
Create element links for the elements that you create.
Create absence type and select applicable predefined Saudi government sector absence category from the list. While defining the absence type, specify the element in the Associated Element field to link it with the absence.
For absences with accruals such as annual leave, create an accrual plan and specify the accrual band for the absence
Create a formula that the application triggers for your absence to do the payroll calculations, for example, SA_ABSENCE_FORMULA. The application uses the formula that you create to perform all the payroll calculations and return the results to applicable absence category element. You can use the sample formula text to create your formula:
/* ------------------------------------------------------------------------ SA_ANNUAL_ABSENCE_CALCULATION ---------------------------------------------------------------------*/ INPUTS ARE Start_Date (date), End_Date (date) Max_Carryover = 36 /* Calculations to be defined here */ RETURN Start_Date, End_Date, Max_Carryover
Create formula results for your absence formula and pass on the results to the user defined absence element and other payroll elements for pay calculations.
Create a new element with classification as Absence for all the absences that would hold the results returned from the formula, for example, Marriage Leave Formula element. For employees with age 50 years and above, create a separate element using the same steps as discussed in this topic and define the accrual plan for it with carryover days as 120.
Create required balances and attach the balance feeds to the Absence elements and other elements as required.
Record the absence information for an employee using the Absence window. See Entering Absences, Oracle HRMS Compensation and Benefits Management Guide.
Enter additional information for each of these absences using the Further Information field:
Enter the absence location for the following absences
Cultural activity leave
Sports activity leave
Social activity leave
Enter the Edda leave reason for Edda leave.
If you want to skip the validation for number of days inside and outside of the Kingdom of Saudi Arabia, then select Saudi Days Exception as the absence reason to override the days validation for the following absence categories:
Death Leave
Marriage Leave
Dialysis Leave
Emergency Leave
Edda Leave
Extended Maternity Leave
Maternity/Paternity Leave
Serious Sickness Leave
Sick Leave
Relief Work Leave
Pilgrimage Leave
Literature Activity Leave
Social Activity Leave
Sports Activity Leave
Cultural Activity Leave
Use the following steps to set up absence management.
If you want to associate recurring elements with absence types, you must set up proration and retro notifications. This ensures that absences that end in the middle of a payroll period are detected and processed by the payroll run, and that retrospective changes to absences are recorded in the Retro Notifications report.
Note: Proration is available to Oracle Payroll users in selected localizations only.
To set up proration and retro notifications, you must:
Find all the dynamically generated triggers for the table PAY_ELEMENT_ENTRIES_F in the Dynamic Trigger Definition window. (You must deselect the Insert triggering action so that all the triggers are returned by the Find.) Make sure the Generated and Enabled check boxes are checked for all the continuous calculation triggers.
Query the Incident Register functional area in the Functional Area Maintenance window, and enter the business groups for which you want to enable proration on the Business Group tab. Optionally, you can further secure the proration functionality by selecting payrolls on the Payroll tab.
Use the Table Event Group window to group the two events that you need to detect to prorate absences - datetracked updates to absence start date and absence end date. Select Proration for the event group type, and Payroll Period for the proration period. In the Datetracked Events region, select DateTrack Update as the update type, PAY_ELEMENT_ENTRIES_F as the table, and EFFECTIVE_START_DATE and EFFECTIVE_END_DATE as the columns.
Use the Table Event Group window to group the datetracked events on the PAY_ELEMENT_ENTRIES_F table you want to track in the Retro Notifications report. The event group type is Retro.
See: Setting Up Proration and Retro Notifications, Oracle HRMS Payroll Management Guide
Define an absence element, with at least one input value, for each absence type. Link this element to define who is eligible.
See: Defining and Linking an Absence Element
Note: Omit this step if you are setting up an absence type for which you do not need to maintain a running total of time taken or remaining, and you do not need eligibility rules.
US and Canada Payroll only: If you want to process the absence element in the payroll run, generate it using the Earnings window.
Mexico only: If you want to process the absence element in the payroll run, generate it using the Element Design Wizard.
Define categories of absence types as values for the Lookup Type ABSENCE_CATEGORY, and your absence reasons as values for the Lookup Type ABSENCE_REASON. In some legislations there are predefined categories and reasons.
You can select the same reason for different absence types.
See: Adding Lookup Types and Values, Oracle HRMS Configuring, Reporting, and System Administration Guide
Define each absence type, and associate it with an absence element.
Note: To keep a single record of employees' time taken for two or more different absence types, you can associate the same element with several types.
For an absence type with a decreasing balance, use BEE or the Absence Detail window to initialize the absence balances for employees eligible for the type.
If you want to make batch entries, see Making Batch Element Entries Using BEE, Oracle HRMS Configuring, Reporting, and System Administration Guide.
If you defined a recurring element, create a payroll formula that handles proration to process the element and calculate the appropriate absence duration in each pay period (taking into account the number of days or hours in a month, working and shift patterns, public holidays, and so on).
Sample Proration Formulas, Oracle HRMS FastFormula User Guide
If you want to set up the application to calculate the duration of an absence automatically, you have two options:
Set the HR: Schedule Based Absence Calculation profile option to Yes, if you want the application to use the worker's schedule and calendar events from their primary assignment to calculate absence durations. To use this option, you must first define schedules and calendar events that are relevant to your enterprise and assign them to various levels in your work structures.
See: Setting Up Availability , Oracle HRMS Workforce Sourcing, Deployment, and Talent Management Guide
To calculate absence duration from the absence start and end dates without using the schedules and calendar events information of an employee, create a basic formula. If you want the absence duration calculation to update automatically each time you change the absence dates, you must set the profile option HR: Absence Duration Auto Overwrite to Yes.
See: Writing Formulas to Calculate Absence Duration, Oracle HRMS FastFormula User Guide
Define an absence element in the Element window.
US and Canada Payroll only: If you want to process the absence element in the payroll run, initiate it on the Earnings window instead of using the Element window.
Mexico only: If you want to process the absence element in the payroll run, initiate it with the Element Design Wizard instead of using the Element window.
Spain only:If you want to compute the social security earnings you must use the predefined elements for Sickness Details, Maternity Details, Part-time Maternity Details, Pregnancy-at-Risk Details and Adoption Details.
To define an absence element
Set your effective date to a day on or before the start of the first payroll period for which you want to enter absences.
Enter a name for the element, and select the classification Information or Earnings.
Tip: Give the absence element and its absence type the same name, or coordinate the element name with the type name. For example, for the absence type Compassionate Leave, name the element Compassionate Leave or Compassionate Leave Absence.
Enter a reporting name, for display on reports.
If you are creating a recurring absence element, select your absence element event group in the Proration Group field. This field is only available to Oracle Payroll users in certain localizations.
Select the processing type.
Select Recurring if you want to be able to process absences that do not have an end date and you want to apportion absence time correctly across payroll periods.
Note: You can only select Recurring if you use Oracle Payroll and the Proration functionality is enabled for your localization. (In this case, you should see the Proration Group field on the Element window)
Select Nonrecurring if it is acceptable to record the full duration of the absence in the payroll period in which the absence starts.
Select the termination rule. This is normally Actual Termination.
Check the Multiple Entries Allowed box if you want to enable employees to have:
(Nonrecurring) More than one instance of the absence type within a pay period.
(Recurring) Overlapping entries of the absence.
If this is an absence element for a PTO accrual plan, do not select Process in Run. Uncheck this box if necessary.
If the element is recurring, ensure that the Process in Run box is checked so that the absence duration can be calculated by the payroll run.
If employees must be a certain age or have served for a certain number of years to be allowed this absence, enter this information in the Qualifying Conditions region.
Note: If this is an absence element for a PTO accrual plan, the plan setup relates length of service to accrued time off. Do not make an entry here for length of service.
Save the element, then choose the Input Values button.
In the Input Values window, create an input value to hold the amount of time taken. Select units of Day, Hours in HH format, or Hours in Decimal Format (to one, two, or three decimal places).
If you are defining an absence element for a PTO accrual plan, give the input value the name Hours or Days, to accord with the unit of measure of the plan. When you define the plan using the Accrual Plan window, this input value name appears in the Units field of the Absence Information region.
Important: If you select Required for an input value, you must select this input value on the Absence Attendance Type window. Do not select Required for more than one input value.
New Zealand users only: You must also create the following input values:
Seasonal Shutdown - for Annual Leave and Annual Leave Termination elements
Number of complete weeks - for the Special Leave and Protected Voluntary Service Leave elements.
You can define minimum and maximum days or hours that can be entered in an absence record. If you do this, select what happens if these limits are breached:
Select Warning for the system to warn users but allow them to breach the limits.
Select Error for the system to issue an error message and prevent users from saving an entry that breaches the limits.
Save your work.
To link the absence element
Set your effective date to a day on or before the start of the first payroll period for which you want to enter absences.
In the Element Link window, select the absence element you defined.
Select eligibility criteria for this absence element, if appropriate. If you want to make the element available to all employees, do not select any criteria.
Save the link. Then define the absence type associated with this absence element.
Use the Absence Attendance Type window to define an absence type and associate it with an element.
To define an absence type
Enter a name and category for the absence type.
Tip: Give the absence type and its associated element the same name, or coordinate the type name with its element name. For example, name the absence type for a PTO accrual plan Salaried Sick PTO Plan, and its associated element, Salaried Sick PTO Absence.
Select Allow Absence Overlaps if absences of this type can overlap other absences. If you deselect this option, the application warns you if you enter an absence that overlaps another absence of any type.
In the Associated Element region, select the element defined for this absence type. Select the element's input value that holds days or hours. The unit of measure for the input value appears in the Units region.
In the Balance region, select Increasing if you want each absence entry to add to a running total of time taken to date. The running total covers all absence types associated with the selected element. Select increasing balances for absence types for PTO accrual plans, and for most other absence types.
For absence types that have a set maximum amount of hours or days allowed, you may select Decreasing. In this case, each absence recorded reduces an initial balance to show time remaining to be taken for the type.
Note: Decreasing balances require more maintenance. You must enter an initial balance amount for each new hire eligible for the absence type, and must initialize the balance for all eligible employees at the start of each year.
Optionally, select reasons that are valid for entries of this type of absence.
Save the absence type.
To make attachments mandatory for an absence type
Complete the following steps to make supporting documents mandatory for absences requests for an absence type.
Note: The mandatory attachment rule is enforced only for self-service users when they enter absences for that specific absence type using the Manager Self-Service and the Employee Self-Service responsibilities. These mandatory rules are not applicable to the OTL absence integration.
In the Name field, enter the name for the absence.
Select the appropriate absence type in the Category field.
Click Further Information.
In the Require Attachment field, select Yes.
You can set up absence benefit plans so that the Participation process checks employee eligibility for the plans when it processes absence life events. You set up participant eligibility profiles to determine which absence categories or types are valid for each plan. Both Standard and Advanced Benefits users can set up absence benefit plans.
Tip: Use the same effective date, such as 01 Jan 1951, for all your definitions
UK Users only: There are sample plans provided for Occupational Sick Pay and Occupational Maternity Pay, called PQP OSP Plan and PQP OMP Plan. You can copy these plans using Plan Design Copy and configure them to meet your needs. If you are not using the sample plans, see: Creating Your Own Absence Plan.
To set up an absence benefit plan using a sample plan
Set the BEN:Enable Absence Plans Functionality profile option to Yes for the users or responsibilities who will enter absences for absence benefit plans, if you want them to run the Participation Process to process the absence life events. This displays the Enroll Absences button on the Absence Detail window.
See: System Profile Values Window, Oracle Applications System Administrators Guide
In the Submit Requests window, select the process Plan Design Copy - ImportIn the Data File parameter, enter the file pqgbgapl.ldt, which is located at patch/115/import/us in Product Top: PQP.
See: Importing a Plan Design From a File, Oracle HRMS Compensation and Benefits Management Guide
Use Plan Design Copy to copy the imported plan. In the Process Name field, enter PQP GB OSP/OMP Absence Plan.
See: Copying a Program or Plan, Oracle HRMS Compensation and Benefits Management Guide.
Tip: First make a copy of the seeded plan in your business group without entering any prefix or suffix for your copy. Select the first option on the Enter Target Details page, which is "Reuse existing objects if current name exists in the target." Then you can make further copies of this copy to configure your plans. When you make further copies, you can select the same option if you want plans to share objects, such as eligibility profiles, or you can select the option "Reuse existing objects if new name exists in target".
Write or configure any formula rules you require, such as the following:
Important: The formulas attached to the sample plans are for UK users only. In other legislations, you must create your own formulas.
| Rule | Formula Type | Supplied Examples (UK Only) |
|---|---|---|
| Eligibility rule | Participation Eligibility | PQP_OSP_PARTICIPATION_ ELIGIBILITY_PROFILE_OTHER_RULE PQP_OMP_PARTICIPATION_ ELIGIBILITY_PROFILE_OTHER_RULE |
| Person Change | Person Change Causes Life Event | PQP_GB_BEN_ABSENCE_START_LER_ PERSON_CHANGE_RULE, PQP_GB_BEN_ABSENCE_END_LER_ PERSON_CHANGE_RULE, PQP_GB_BEN_ABSENCE_DELETE_LER_ PERSON_CHANGE_RULE |
| Extra Input Rule | Extra Inputs | PQP_OSP_STANDARD_RATES _GENERAL_EXTRA_INPUT_RULE PQP_OMP_STANDARD_RATES _GENERAL_EXTRA_INPUT_RULE |
| Length of service rate | Length of Service Calculation | PQP_OSP_STANDARD_RATES _CALCULATION_METHOD_VALUE_RULE PQP_OMP_STANDARD_RATES _CALCULATION_METHOD_VALUE_RULE |
See: Total Compensation Formula Types, Oracle HRMS FastFormula User Guide
Ensure you have Program/Plan years set up.
See: Defining a Program or Plan Year Period, Oracle HRMS Compensation and Benefits Management Guide
Select the appropriate Person Changes for the three absence life event reasons, created by the Plan Design Copy process. There is one life event reason for each Life Event Operation Code: Start Event, End Event, Delete Event.
Note: You only perform this step once. You use the same life event reasons for all your absence plans.
The Start Absence life event reason must detect changes to any columns except the end date. Use the Person Change formula rule you created in step 4 to define the columns you want to use to trigger this life event.
UK users: You must attach the PQP_GB_BEN_ABSENCE_ START_LER_PERSON_CHANGE_RULE formula to the absence start life event
You can also use formula rules to define the person changes that trigger the End Absence and Delete Absence life events too.
See: Life Event Definition, Oracle HRMS Compensation and Benefits Management Guide
Query the absence plan in the Plans window, and change the status from Pending to Active. Choose the Details button and select your plan periods.
See: Defining a Benefits Plan, Oracle HRMS Compensation and Benefits Management Guide
You have completed the plan setup based on a seeded plan, but make sure you complete the Next Steps.
To set up an absence benefit plan without using the sample plans
Set the BEN:Enable Absence Plans Functionality profile option to Yes for the users or responsibilities who will enter absences for absence benefit plans, if you want them to run the Participation Process to process the absence life events. This displays the Enroll Absences button on the Absence Detail window.
See: System Profile Values Window, Oracle Applications System Administrators Guide
Write or configure any formula rules you require, such as the ones shown in the following table.
Note: UK users: If you want to use the supplied formulas, you must run the following scripts:
PQPGBLER.SQL script to create the life event formulas
PQPGBOSP.SQL script to create the OSP formulas
PQPGBOMP.SQL script to create the OMP formulas
| Rule | Formula Type | Supplied Examples (UK Only) |
|---|---|---|
| Eligibility rule | Participation Eligibility | <base name>_OSP_PARTICIPATION_ ELIGIBILITY_PROFILE_OTHER_RULE <base name>_OMP_PARTICIPATION_ ELIGIBILITY_PROFILE_OTHER_RULE |
| Person Change | Person Change Causes Life Event | PQP_GB_BEN_ABSENCE_START_LER_ PERSON_CHANGE_RULE, PQP_GB_BEN_ABSENCE_END_LER_ PERSON_CHANGE_RULE, PQP_GB_BEN_ABSENCE_DELETE_LER_ PERSON_CHANGE_RULE |
| Extra Input Rule | Extra Inputs | <base name>_OSP_STANDARD_RATES _GENERAL_EXTRA_INPUT_RULE <base name>_OMP_STANDARD_RATES _GENERAL_EXTRA_INPUT_RULE |
| Length of service rate | Length of Service Calculation | <base name>_PQP_OSP_STANDARD_RATES _CALCULATION_METHOD_VALUE_RULE <base name>_PQP_OMP_STANDARD_RATES _CALCULATION_METHOD_VALUE_RULE |
See: Total Compensation Formula Types, Oracle HRMS FastFormula User Guide
Define a new plan type, selecting Absences as the Option Type.
See: Defining Plan Types, Oracle HRMS Compensation and Benefits Management Guide
Ensure you have Program/Plan years set up.
See: Defining a Program or Plan Year Period, Oracle HRMS Compensation and Benefits Management Guide
Create a participant eligibility profile for each absence benefit plan.
Important: Ensure that these profiles are exclusive: participants must only be eligible for one plan at a time.
Ensure that your eligibility profile checks that the absence is for the appropriate absence category, such as sickness. You can further restrict eligibility to one or more absence types.
UK users: Choose the Others tab and select Rule. Select the supplied rule <base name>_OSP_PARTICIPATION_ ELIGIBILITY_PROFILE_OTHER_RULE for an OSP scheme, or <base name>_OMP_PARTICIPATION_ELIGIBILITY_PROFILE_ OTHER_RULE for an OMP scheme, or another formula that you have created.
See: Defining an Eligibility Profile, Oracle HRMS Compensation and Benefits Management Guide
Create three life event reasons, all of type Absence, and one for each Life Event Operation Code: Start Event, End Event, Delete Event.
Note: You only perform this step once. You use the same life event reasons for all your absence plans.
Select the Person Changes that trigger these life events. The table is PER_ABSENCE_ATTENDANCES. Select columns and values as follows:
| Life Event | Column | Old Value | New Value |
|---|---|---|---|
| Start Absence | DATE_START | any value | any value |
| End Absence | DATE_END | any value | any value |
| Delete Absence | DATE_START | any value | no value |
The Start Absence life event reason must detect changes to any columns except the end date. Use the Person Change formula rule you created in step 2 to define the columns you want to use to trigger this life event.
UK users: You must attach the PQP_GB_BEN_ABSENCE_ START_LER_PERSON_CHANGE_RULE formula to the absence start life event
You can also use formula rules to define the person changes that trigger the End Absence and Delete Absence life events too.
See: Life Event Definition, Oracle HRMS Compensation and Benefits Management Guide
Define the absence plan.
Select your plan type.
Select May Not Be In Program for the Plan Usage.
See: Defining a Benefits Plan, Oracle HRMS Compensation and Benefits Management Guide
On the Eligibility Rates tab, check all the check boxes. Select Participant in the Eligibility Check field.
See: Defining Eligibility and Activity Rate Requirements for a Plan, Oracle HRMS Compensation and Benefits Management Guide
On the Not in Program tab, enter a Sequence number and the activity rate details.
UK users: Select Per Pay Period for the Enrolment Rate/Frequency and select a value, such as Monthly, for the Activity Reference Period.
See: Defining a Plan Not in a Program, Oracle HRMS Compensation and Benefits Management Guide
Choose the Details button and select your plan periods. Return to the Plans window.
See: Maintaining Plan Related Details, Oracle HRMS Compensation and Benefits Management Guide
Choose the Plan Eligibility button then the Eligibility button. Select your eligibility profile on the Profile tab. Close this window.
See: Defining Participant Eligibility Criteria for a Compensation Object, Oracle HRMS Compensation and Benefits Management Guide
Choose the Life Event button. Select your End Absence life event and select Ineligible in the Eligible/Ineligible field.
See: Associating a Life Event Reason With a Compensation Object, Oracle HRMS Compensation and Benefits Management Guide
Define the plan enrollment requirements.
Choose the General tab, the Plan tab, then Enrollment. Select Automatic in the Method field.
Select Current Can Keep or Choose; New Can Choose as the Enrollment Code.
See: Defining an Enrollment Method for a Plan, Oracle HRMS Compensation and Benefits Management Guide
Choose Coverage. Select Event as the Enrollment Coverage Start Date Code and End Date Code.
See: Defining Enrollment Coverage Requirements for a Plan , Oracle HRMS Compensation and Benefits Management Guide
Choose Rates. Select Event as the Rate Start Date Code and End of Pay Period as the Rate End Date Code.
Choose the Timing tab and the Life Event tab. Select Life Event as the Enrollment Type. Select your Start Absence life event in the Life Event column and select When Elections are Made as the Close Enrollments Date to Use.
See: Defining Requirements for a Life Event Enrollment for a Plan, Oracle HRMS Compensation and Benefits Management Guide
Click on General and choose the Periods region. Select As of Event Date for the Enrollment Period Start Date, and End of Pay Period for the Enrollment Period End Date.
Define or generate the elements required for the plan, then define a standard rate for the plan to calculate values for the absence element entry.
UK Users: Use the Absence Scheme Creation template, then set up the generated user-defined tables, and define a standard rate for the absence plan (or configure the copied rate if you are using a copy of the seeded plans).
Balances show the positive or negative accumulation of particular values over periods of time. They are fed either by the direct run results (that is, Pay Values) of elements processed in the payroll run, or by input values. For example, in North American installations, the input value Hours of the element Time Entry Wages feeds the balance Regular Hours Worked.
Balances exist for various time dimensions, such as current run, period to date, month, quarter to date, and year to date.
Balances also exist at different levels, such as assignment level or person level. Balances for individual employee assignments are at the assignment level (in North America, they can be at the assignment level within a GRE). If your enterprise permits employees to hold more than one assignment at the same time, you can hold balances at the person level. For example, a person level Gross Earnings balance is the sum of an employee's assignment level Gross Earnings balances.
You can select elements to feed a balance in three ways:
Select a primary classification. The run results of all elements in the classification feed the balance. However, you must have an input value of Pay Value if you want to create a feed between an element and a balance.
Select a secondary classification. You choose which elements from a primary classification (such as Earnings) are to feed the balance by giving these elements a secondary classification. Again it is the run results of the elements that feed the balance.
Note: Secondary classifications are not used in the North American versions of Oracle Payroll at this time.
Select an individual element. You can select either the run result or an input value to feed the balance. The input value must have the same unit of measure (such as hours or number) as the balance.
You can choose any number of classifications or any number of elements to feed a balance. However you cannot use a mixture of classifications and individual elements to feed a balance. When you select an element or classification as a balance feed, you specify whether the run results (or input values) should add to or subtract from the balance.
The balances and balance feeds for the elements supplied with Oracle Payroll are present in the system when you receive it. For North American users, when you initiate earnings types, deductions and other items that process in the payroll run, the system generates the appropriate balances and balance feeds together with the necessary elements.
You can define any additional balances your enterprise requires. For example, you may require a Pensionable Earnings balance for a pension plan your enterprise offers employees.
Important: You cannot have two or more elements with the same primary balance. This setup will cause incorrect elements to show up on reports or Statement of Earnings when the process uses balance reporting architecture.
You define primary balance using the following navigation:
Balance window (Total Compensation > Basic > Balance):
You define primary balance by selecting an element and an input value in the Primary Balance region in the Balance window. This type of balance is fed by a single element and can only be inserted if no balance feeds exist for the balance, with the exception of Balance Initialization feeds. When you create a primary balance, the associated feed is created automatically. No other feeds can be created for the balance. Note that if the Primary Balance region is disabled, then the primary balance functionality is not enabled for that localization.
Earnings or Deductions window:
When you create a balance, the balance gets created with name same as that of the element and the element input "Pay Value" gets added as a feed to this balance. This balance is considered as a Primary Balance for this element and can be seen from the Primary Balance field in the Element Description, Further Information window. Changing this Primary Balance in the Further Element Information will result in incorrect values to be reported. For example, Statement of Earnings (SOE) is designed to display the values based on the Primary Balance associated with the elements that are processed.
Oracle HRMS provides the following predefined balance dimensions.
The following table provides the balance dimensions that you can use to sum values for single assignments:
| Database Item Suffix | Description |
|---|---|
| _ASG_MONTH_NO_LEAVERS | Since the start of the month to date for the employees who are neither joiners nor leavers. |
| _ASG_MONTH_NEW_JOINERS | Since the start of the month to date for the employees who are new joiners. |
| _ASG_MONTH_LEAVERS | Since the start of the month to date for the employees who are leavers. |
| _ASG_TU_MONTH_NO_LEAVERS | Since the start of the month to date for the employees who are neither joiners nor leavers within the tax unit (Legal Employer). |
| _ASG_TU_MONTH_NEW_JOINERS | Since the start of the month to date for the new joiners within the tax unit (Legal Employer). |
| _ASG_TU_MONTH_LEAVERS | Since the start of the month to date, who are leavers within the tax unit (Legal Employer). |
| _ASG_TU_ITD | Since the start of the month to date for the assignment within the tax unit (Legal Employer). |
| _ASG_TU_PTD | Since the start of the processing period to date for the assignment within the tax unit (Legal Employer). |
| _ASG_TU_MONTH | Since the start of the calendar month to date for the assignment within the tax unit (Legal Employer). |
| _ASG_TU_QTD | Since the start of the calendar quarter to date for the assignment within the tax unit (Legal Employer). |
| _ASG_TU_YTD | Since the start of the calendar year to date for the assignment within the tax unit (Legal Employer). |
| _ASG_TU_FQTD | Since the start of the fiscal quarter to date for the assignment within the tax unit (Legal Employer). |
| _ASG_TU_FYTD | Since the start of the fiscal year to date for the assignment within the tax unit (Legal Employer). |
| _PER_TU_ITD | Since the start of the month to date for a person within the tax unit (Legal Employer). |
| _PER_TU_PTD | Since the start of the processing period to date for a person within the tax unit (Legal Employer). |
| _PER_TU_MONTH | Since the start of the month to date for the person within the tax unit (Legal Employer). |
| _PER_TU_QTD | Since the start of the calendar quarter to date for the person within the tax unit (Legal Employer). |
| _PER_TU_YTD | Since the start of the calendar year to date for the person within the tax unit (Legal Employer). |
| _PER_TU_FQTD | Since the start of the fiscal quarter to date for the person within the tax unit (Legal Employer). |
| _PER_TU_FYTD | Since the start of the fiscal year to date for the person within the tax unit (Legal Employer). |
| _PER_TU_TQTD | Since the start of the statutory quarter to date for the person within the tax unit (Legal Employer). |
| _PER_TU_TYTD | Since the start of the statutory year to date within the tax unit (Legal Employer). |
| _ASG_TU_TQTD | Since the start of the statutory quarter to date for the assignment within the tax unit (Legal Employer). |
| _ASG_TU_TYTD | Since the start of the statutory year to date for the assignment within the tax unit (Legal Employer). |
| _ASG_RUN | during one payroll run |
| _ASG_ITD | Since the start of the assignment Inception to date. |
| _ASG_PTD | Since the start of the assignment Processing Period To Date |
| _ASG_MONTH | Since the start of the assignment calendar month to date. |
| _ASG_QTD | Since the start of the assignment calendar quarter to date. |
| _ASG_YTD | Since the start of the assignment calendar year to date. |
| _ASG_TQTD | Since the start of the assignment tax quarter to date. |
| _ASG_TYTD | Since the start of the assignment tax year to date. |
| _ASG_FQTD | Since the start of the assignment fiscal quarter to date. |
| _ASG_FYTD | Since the start of the assignment fiscal year to date |
| _PER_ITD | Since the start of the person inception to date. |
| _PER_PTD | Since the start of the person processing period to date. |
| _PER_MONTH | Since the start of the person calendar month to date. |
| _PER_QTD | Since the start of the person calendar quarter to date. |
| _PER_YTD | Since the start of the person calendar year to date. |
| _PER_TQTD | Since the start of the person tax quarter to date. |
| _PER_TYTD | Since the start of the person tax year to date. |
| _PER_FQTD | Since the start of the person fiscal quarter to date |
| _PER_FYTD | Since the start of the person fiscal year to date. |
| _ENTRY_ITD | Since the start of the element entry inception to date |
| _ENTRY_PTD | Since the start of the element entry processing period to date. |
| _ENTRY_MONTH | Since the start of the element entry calendar month to date. |
| _ENTRY_QTD | Since the start of the element entry calendar quarter to date. |
| _ENTRY_YTD | Since the start of the element entry calendar year to date. |
A special dimension which aggregates results from payroll runs that have been picked up in a particular pre-payments run.
| Database Item Suffix | Description |
|---|---|
| _PAYMENTS | For a set of payroll runs. |
Oracle Payroll provides the elements, balances, formulas, and other components required to process GOSI deductions. When the payroll run encounters an entry of the GOSI element, it runs the predefined formula SA_GOSI_CALCULATION. This formula processes GOSI Annuities and GOSI Hazards if you have specified these deductions for your employees (on the GOSI Details tab of the Assignment window).
If an employee has an entry of the Setup GOSI Reference Salary element, the formula uses this element's pay value as the base for calculating the GOSI deductions, subject to any adjustment entered on the GOSI Reference Salary Adjustment element.
If there is no entry of the Setup GOSI Reference Salary element, the formula uses the base value returned by the GOSI Reference formula, if you have written this formula and attached it to your GRE.
Note: This formula must return the variable, GOSI_REFERENCE.
If you do not define a GOSI Reference formula, Oracle Payroll calculates the GOSI base from the elements having the secondary classification Subject to GOSI.
If there are no elements with this secondary classification, Oracle Payroll calculates the GOSI deductions on the lower limit of the base value provided for the GOSI deductions.
GOSI payroll processing assesses the employee's total earnings. If an employee's earnings exceeds Employee GOSI Annuities, then GOSI calculations automatically process and deduct from the employee's earnings. However, if the employee's earnings are less than the Employee GOSI Annuities, then the employer pays on behalf of the employee, and this accrues as arrears for the employee.
Oracle Payroll provides the elements, balances, formulas, and other components required to process PPA deductions. When the payroll run encounters an entry of the PPA element, it runs the predefined formula SA_PPA_CALCULATION. This formula processes PPA Annuities and PPA Hazards if you have specified these deductions for your employees (on the GOSI/PPA Details tab of the Assignment window). If an employee has an entry of the Setup PPA Reference Salary element, the formula uses this element's pay value as the base for calculating the PPA deductions, subject to any adjustment entered on the PPA Reference Salary Adjustment element.
If there is no entry of the Setup PPA Reference Salary element, then the formula uses the base value returned by the PPA Reference formula, if you have written this formula and attached it to your GRE/Legal Entity. If you do not define a PPA Reference formula, then Oracle Payroll calculates the PPA base from the elements having the secondary classification Subject to PPA. If there are no elements with this secondary classification, then Oracle Payroll calculates the PPA deductions on the lower limit of the base value provided for the PPA deductions.
PPA Processing
PPA payroll processing assesses the employee's total earnings. If an employee's earnings exceed Employee PPA Annuities, then PPA calculations automatically process and deduct from the employee's earnings. However, if the employee's earnings are less than the Employee PPA Annuities, then the employer pays on behalf of the employee, and this accrues as arrears for the employee.
Oracle HRMS enables you to process General Office of Social Insurance (GOSI) contributions for employees using predefined GOSI elements.
Before you start to process GOSI contributions, you need to do the following:.
To set up GOSI processing
Define the GOSI address as a location within the application. See: Setting Up Locations , Oracle Enterprise and Workforce Management Guide
Create an external organization for the General Office of Social Insurance (GOSI). See:Business Groups: Entering Saudi GOSI Office
Enter GOSI details of the legal entities in your enterprise. See GREs/Legal Entities: Entering Saudi GOSI Details
Link the predefined elements GOSI, Setup GOSI Reference Salary, and GOSI Reference Salary Adjustment. You can also link other user defined elements.
See: Predefined Elements
See: Defining Element Links, Oracle Compensation and Benefits Management Guide
Link the formula SA_GOSI_CALCULATION to GOSI element in the Formula Result Rules window.
See: Defining Formula Processing and Result Rules, Oracle FastFormula User Guide
Optionally write a formula to return a base value for the calculation of GOSI deductions. This formula must return the variable GOSI_REFERENCE. You can override this formula for some or all employees by entering a pay value for the Setup GOSI Reference Salary element. For more information on writing formulas, See: Writing or Editing a Formula, Oracle FastFormula User Guide
If you have created your own formula with a return variable GOSI_REFERENCE, attach your formula at the GRE level. See: GREs/Legal Entities: Entering GOSI Reference Formula
Optionally use the Subject to GOSI secondary classification to classify the elements that form the base for GOSI deductions. Oracle Payroll uses these elements to calculate the base once each year in January if you have not defined a GOSI Reference Formula, nor entered a pay value in the Setup GOSI Reference Salary element for an employee.
You can enroll an employee assignment to General Office of Social Insurance (GOSI) deductions using the Element Entries window.
To enroll an employee assignment for GOSI deductions
Set your effective date to the date on which you want the GOSI deductions to come into effect.
Note: For New Hires, this should normally be the hire date. Deductions begin in the payroll period. This payroll run retrospectively calculates employee and employer deductions for GOSI.
Choose New Record to enter a new element entry.
Select the element GOSI to initiate the GOSI processing. You can enter costing information and a reason for entering this element for the assignment. The element has no input values.
Choose New Record and select the element Setup GOSI Reference Salary if you want to specify a base value for calculating GOSI deductions. If you do not enter this element for the employee, the payroll run calculates the GOSI base using the GOSI Reference formula attached to the GRE.
Enter costing information and a reason, if required. See:Data Costed at the Element Entry Level., Oracle Compensation and Benefits Management Guide
To enter a pay value for the element Setup GOSI Reference Salary, choose the Entry Values button to open the Entry Values window. In the pay value field, enter the base value for the GOSI calculations to use in the current year.
In the Element Entries window, choose New Record and select the element GOSI Reference Salary Adjustment if you want to change the base value for GOSI calculations.
Choose the Entry Values button to open the Entry Values window.
Enter an amount in the Pay Value field, for the element GOSI Reference Salary Adjustment. You can use this amount to adjust the base value for GOSI deductions. This value can be a positive or negative. For example, suppose you have set the pay value for the element Setup GOSI Reference Salary as 1000 (thousand dinar). If you want to decrease or increase the base for the GOSI deductions by 100 (hundred dinar) in the current pay period only, enter +100 or -100 in the pay value field for the element GOSI Reference Salary Adjustment.
Save the Element Entry details.
Oracle HRMS enables you to process Public Pension Agency (PPA) contributions for employees using the predefined PPA elements.
To set up PPA processing
Create the PPA organization. See: Creating Public Pension Agency Organization
Define PPA office. See: Business Groups: Defining PPA Office
Enter PPA office details of the legal entities in your enterprise. See GREs/Legal Entities: Entering PPA Office Details.
Link the predefined elements PPA, Setup PPA Reference Salary, and PPA Reference Salary Adjustment. You can also link other user defined elements. See: Predefined Elements and Defining Element Links, Oracle Compensation and Benefits Management Guide
Link the formula SA_PPA_CALCULATION to PPA element in the Formula Result Rules window. See: Defining Formula Processing and Result Rules, Oracle FastFormula User Guide
Optionally write a formula to return a base value for the calculation of PPA deductions. This formula must return the variable PPA_REFERENCE. You can override this formula for some or all employees by entering a pay value for the Setup PPA Reference Salary element. For more information on writing formulas, See: Writing or Editing a Formula, Oracle FastFormula User Guide
If you have created your own formula with a return variable PPA_REFERENCE, then attach your formula at the GRE/Legal Entity level. See: GREs/Legal Entity: Entering PPA Office Details
Optionally use the Subject to PPA secondary classification to classify the elements that form the base for PPA deductions. Oracle Payroll uses these elements to calculate the base once each year in January if you have not defined a PPA reference formula, nor entered a pay value in the Setup PPA Reference Salary element for an employee.