Understanding Data Retrieval from HR
This topic discusses how data in HR is retrieved and used in Absence Management using these elements:
Database system elements
Arrays
Rate codes
Frequency
Triggers
Database system elements contain payee-related data that is retrieved from HR and commonly used in absence calculations. You don’t have to set up these elements or do anything special to resolve them. They are resolved when they’re used in a calculation.
These HR tables populate database system elements:
PERSON.
PERS_DATA_EFFDT (personal data effective date).
PER_ORG_ASGN_VW.
JOB (including fields from country-specific sub records).
PER_ORG_ASGN (person organizational assignment).
PER_ORG_INST (person organizational instance).
ADDRESSES.
CONTRACT_DATA.
WKF_CNT_TYPE (workforce contract type).
An array is an element that retrieves data from any table or view that database system elements do not retrieve. For example, you can use an array to retrieve data from the Benefit table or the Company table in HR for further processing in Absence Management.
You use rate codes to retrieve multiple components of pay data from HR and bring into Absence Management. The system calculates the values in Absence Management, rather than transferring the data directly from HR, so that currency conversions can be calculated for every absence run. In Absence Management, you define a rate code element and link it to the corresponding rate code defined in a HR table.
HR has an effective-dated Frequency table, where you enter the annualization factor for each frequency. Defining the annualization factor is important for absence processing in Absence Management.
Absence Management accesses the same Frequency table as HR and uses it throughout Absence Management for annualization and deannualization. When you set up a frequency in HR, you associate a factor with it. For example, an annual factor can be equal to one, a monthly factor can be equal to 12, and a weekly factor can be equal to 52.
The frequency formulas used for annualization and deannualization are the same for both HR and Absence Management:
(Annualized Amount) = (Amount) × (Frequency Factor).
(Deannualized Amount) = (Annualized Amount) / (Frequency Factor).
Important! If you change the effective status, frequency type, or annualization factor of an existing frequency on the Frequency Table page in HR, you get a warning message saying that previous calculations using this frequency are out of sync with the new values of the frequency.
When defining absence elements in Absence Management, the system obtains the frequency factor from HR. The system annualizes the absence element, according to the specified frequency factor, and denationalize the absence element, according to the specified calendar period frequency. The only exception to this rule is when you’ve specified a generation control frequency. Then, the system annualizes the absence value according to the specified frequency factor, but denationalize it according to the generation control frequency.
In Absence Management, frequency is used with:
Element definition.
Generation control.
Calendar periods (when defining the frequency that’s being processed).
Rate code elements.
System elements.
You can create triggers in Absence Management to detect changes made to data in HR. This enables Absence Management to identify payees automatically who need to be recalculated during an absence run. You can set up retro, segmentation, or iterative triggers. For example, you might want to create a retro trigger that detects changes to job data, thus telling the system that retroactivity should occur for this event.
Triggers can respond to field-level and record-level data changes.
With Absence Management, you can also create mass triggers. Mass triggers enable you to generate payee triggers based on changes to setup tables. Mass triggers can be established for specific records on specific components.
See .