Global Absence Plan Use Rate
The Global Absence Plan Use Rate fast formula can be used to dynamically specify the rate definition associated with the qualification plan depending on custom conditions.
If the rate definition associated with the same qualification plan varies depending on the location of the worker being evaluated, a Global Absence Plan Use Rate can be composed to associate the corresponding rate definition to the Worker.
Configuration Point in HCM Cloud
If you have created this formula, you can attach this formula to the absence plan definition.
Navigation
- In the Absence Administration work area, click Absence Plans to open the Absence Plans page.
- On the Search Results section toolbar, click Create to open the Create Absence Plan dialog box.
- In the Plan Type field, select Qualification.
- Click Continue.
- On the Edit Absence Plan page Entries and Balances tab, Rates section, choose Formula in the Absence Payment Rule field.
- Select the defined formula in the Formula field.
Contexts
The following contexts are available in this formula type:
| Context Name | Data Type |
|---|---|
| ABSENCE_CATEGORY_ID | Number |
| ABSENCE_ENTRY_ID | Number |
| ABSENCE_MATERNITY_ID | Number |
| ABSENCE_REASON_ID | Number |
| ABSENCE_TYPE_ID | Number |
| ACCRUAL_PLAN_ID | Number |
| DATE_EARNED | Date |
| EFFECTIVE_DATE | Date |
| END_DATE | Date |
| ENTERPRISE_ID | Number |
| HR_ASSIGNMENT_ID | Number |
| HR_RELATIONSHIP_ID | Number |
| HR_TERM_ID | Number |
| JOB_ID | Number |
| LEGAL_EMPLOYER_ID | Number |
| LEGISLATIVE_DATA_GROUP_ID | Number |
| ORGANIZATION_ID | Number |
| PAYROLL_ASSIGNMENT_ID | Number |
| PAYROLL_ID | Number |
| PAYROLL_RELATIONSHIP_ID | Number |
| PAYROLL_TERM_ID | Number |
| PERSON_ID | Number |
| START_DATE | Date |
Input Values
| Variable Name | Data Type | Description |
|---|---|---|
| IV_ATTRIBUTE_CATEGORY | Text | Context of the DFF row for Absence Recordings DFF |
| IV_ATTRIBUTE_1* | Text | First text segment of the Absence Recordings DFF |
| IV_ATTRIBUTE_NUMBER1* | Number | First number segment of the Absence Recordings DFF |
| IV_ATTRIBUTE_DATE1* | Date | First date segment of the Absence Recordings DFF |
| IV_ATTRIBUTE_ARR | Text_Number | Array of text segments of the Absence Recordings DFF. The index indicates the segment number. Eg: IV_ATTRIBUTE_ARR[1] holds the value of segment ATTRIBUTE1 in ANC_PER_ABS_ENTRIES table. The index begins at 1 and ends at 30. If a particular index is used and data does not exist, the application would throw an error. Hence it is a good practice to first check if data exists before using the input value. This can be done using the “exists” command. Eg: if(IV_ATTRIBUTE_ARR.exists(1)) |
| IV_ATTRIBUTE_NUMBER_ARR | Number_Number | Array of number segments of the Absence Recordings DFF. The index indicates the segment number. Eg: IV_ATTRIBUTE_NUMBER_ARR[1] holds the value of segment ATTRIBUTE_NUMBER1 in ANC_PER_ABS_ENTRIES table. The index begins at 1 and ends at 30. If a particular index is used and data does not exist, the application would throw an error. Hence it is a good practice to first check if data exists before using the input value. This can be done using the “exists” command. Eg: if(IV_ATTRIBUTE_NUMBER_ARR.exists(1)) |
| IV_ATTRIBUTE_DATE_ARR | Date_Number | Array of date segments of the Absence Recordings DFF. The index indicates the segment number. Eg: IV_ATTRIBUTE_DATE_ARR[1] holds the value of segment ATTRIBUTE_DATE1 in ANC_PER_ABS_ENTRIES table. The index begins at 1 and ends at 30. If a particular index is used and data does not exist, the application would throw an error. Hence it is a good practice to first check if data exists before using the input value. This can be done using the “exists” command. Eg: if(IV_ATTRIBUTE_DATE_ARR.exists(1)) |
| IV_INFORMATION_CATEGORY | Text | Context of the DDF row for ANC_PER_ABS_ENTRIES DDF |
| IV_INFORMATION_1* | Text | First text segment of the ANC_PER_ABS_ENTRIES DDF |
| IV_INFORMATION_NUMBER1* | Number | First number segment of the ANC_PER_ABS_ENTRIES DDF |
| IV_INFORMATION_DATE1* | Date | First date segment of the ANC_PER_ABS_ENTRIES DDF |
| IV_INFORMATION_ARR | Text_Number | Array of text segments of the ANC_PER_ABS_ENTRIES DDF. The index indicates the segment number. Eg: IV_INFORMATION_ARR[1] holds the value of segment INFORMATION1 in ANC_PER_ABS_ENTRIES table. The index begins at 1 and ends at 30. If a particular index is used and data does not exist, the application would throw an error. Hence it is a good practice to first check if data exists before using the input value. This can be done using the “exists” command. Eg: if(IV_INFORMATION_ARR.exists(1)) |
| IV_INFORMATION_NUMBER_ARR | Number_Number | Array of number segments of the ANC_PER_ABS_ENTRIES DDF. The index indicates the segment number. Eg: IV_INFORMATION_NUMBER_ARR[1] holds the value of segment INFORMATION_NUMBER1 in ANC_PER_ABS_ENTRIES table. The index begins at 1 and ends at 30. If a particular index is used and data does not exist, the application would throw an error. Hence it is a good practice to first check if data exists before using the input value. This can be done using the “exists” command. Eg: if(IV_INFORMATION_NUMBER_ARR.exists(1)) |
| IV_INFORMATION_DATE_ARR | Date_Number | Array of date segments of the ANC_PER_ABS_ENTRIES DDF. The index indicates the segment number. Eg: IV_INFORMATION_DATE_ARR[1] holds the value of segment INFORMATION_DATE1 in ANC_PER_ABS_ENTRIES table. The index begins at 1 and ends at 30. If a particular index is used and data does not exist, the application would throw an error. Hence it is a good practice to first check if data exists before using the input value. This can be done using the “exists” command. Eg: if(IV_INFORMATION_DATE_ARR.exists(1)) |
| IV_PAYMENT_DTL_BAND | Number | Identifier of the payment band chosen for the absence linked to an agreement |
| IV_NOTIFICATION_DATE | Date | Date of Illness/Injury notification |
| IV_MATCHING_DATE | Date | Date on which child is matched with the worker for adoption |
*The sequence for this input value can be extended up to 5
Return Variables
| Variable Name | Data Type | Description |
|---|---|---|
| RATECODE | Text | Rate code for rate associated with qualification plan |
| DEBUG_MESSAGE | Text | Text passed into this output variable would get logged if application logging is enabled. Useful for debugging |
Sample Formula
Requirement: The organization has an absence payment rate rule for the qualification plan that depends on the hourly/salaried nature of the Worker. Separate rate definition rules exist for each category of workers.
Solution: A Global Absence Plan Use Rate formula such as the one below can be used.
FORMULA NAME: ANC_PLN_RATE
FORMULA TYPE: Global Absence Plan Use Rate
DESCRIPTION: This formula returns the rate code for the rate definition that needs to be associated with the qualification plan
DEFAULT FOR PER_ASG_HOURLY_SALARIED_CODE IS 'H'
IF (PER_ASG_HOURLY_SALARIED_CODE = 'H')
THEN
(
RATECODE = 'HOURLY_RATE'
)
ELSE
(
RATECODE = 'ANNUAL_RATE'
)
RETURN RATECODE