Guidelines for Using Different Modes for HCM Extracts
You can create an extract to output data in different modes in the Extract Definitions page. Use modes to extract data that has changed since the previous extract runs.
For example, you can extract employee details whenever there's a change in the employee's location. The processing engine generates the current status of the data, compares it with the base-lined data of the previous runs, and identifies the new and any modifications. The output from such changes-only extract has the incremental data only.
You can manipulate the output in a changes-only extract to either exclude or include certain attributes, regardless of whether the attribute has changed or not. For example, by selecting an option to exclude an attribute from comparison, you can ensure that attribute isn't compared while identifying changes to include in the generated output of the next extract run. Therefore, even if the attribute has changed since the previous extract run, it will not be included in the output. You can also select an option to always include an attribute in the generated output of an extract run, even if the attribute hasn't changed.
Extract Modes
To enable different modes in an extract, you include the CHANGES_ONLY parameter and set up threading details in the extract definition. While running the extract you can use the CHANGES_ONLY parameter to control the extract mode. For example, to find out if the job name has changed on a person's assignment, set up multithreading database items at assignment level and include the CHANGES_ONLY parameter. When you run the extract in the ATTRIBUTE mode, the extract compares data from the multithreading level and outputs the incremental changes. You can link the PER_EXT_CHANGES_ONLY lookup or the ORA_HRY_CHANGES_ONLY lookup to the CHANGES_ONLY parameter so that you can select a mode when you submit the extract.
The following table describes the different extract modes, their lookup values and descriptions.
Mode |
Lookup Value |
Description |
---|---|---|
N |
All attributes |
Includes all data in the extract. A full extract is run which produces the full data output at that point of time. The archived data is used as a baseline. Note: The Changes Only extracts that ran only in full
extract mode but never ran in Changes Only modes will be automatically
converted to full extracts after applying the release patch.
|
Y |
Changed attributes |
Compares this extract run with the previous extract runs and by comparing against the baseline (to identify the incremental data), displays the data that has changed only. |
ATTRIBUTE |
Changed and marked attributes |
Includes elements that have changed or marked as required |
ATTRIB_OLD |
Changed and marked attributes with previous values |
Displays elements that have changed or marked as required plus their previous value |
BLOCK_OLD |
Changed, marked attributes, previous data under threading group |
Displays the following data under threading data group: Changed data Data marked as required Previous values Parent data group values |
BLOCK |
Changed and marked attributes under threading group |
Displays the following data under threading data group: Changed data Data marked as required Parent data group values |