Extract Components

The HCM Extracts feature is a flexible tool for generating data files and reports. This topic covers how you can use the extract components to define what information you want the application to extract and report on.

It also explains how the application displays, formats, and delivers the information.

Extract Definitions

An extract definition refers to the complete setup of an extract, that consists of extract data groups, criteria, records, attributes, advanced conditions and output delivery options. An extract definition consists of:

  • One or more extract data groups, depending on how many logical entities you want to extract.

  • One or more extract records depending on how many groups of information you want to collect.

  • One or more attributes depending on how many individual fields of data you want to collect.

You use HCM extracts to extract, archive, transform, report, and deliver high volumes of HCM data from the Oracle Fusion HCM database. You can generate the output in the following formats:

  • CSV

  • XML

  • Excel

  • HTML

  • RTF

  • PDF

You can distribute the extracted information by email, FTP and other delivery modes. Some common examples of extracts are: PDF payslips delivered to employees' mailboxes, payroll or benefits data transferred to third-party service providers, HR and talent data exchange between Oracle Fusion and legacy applications, for example in a coexistence scenario.

Data Groups

Extract data groups represent a business area or logical entity, for example person, assignment, or benefits. The application uses this information to retrieve the database item groups. You define one data group as the primary or root data group and this data group is the starting point of the data extraction.

Extract data group connections capture the association details between the current data group and the parent data group. The data group connections form the hierarchical relationship among the data groups.

You can define a set of filtering conditions the application must perform on an extract data group using the extract data group criteria. You specify the criteria conditions using an expression or fast formula.

Extract Records

Extract records represent a grouping of related data or a physical collection of all fields required in the extract. For example, the Employee data group can have records such as Basic Details, Pay Details, Location Details, and Primary Contact. An extract record is a collection of attributes which you can organize in a required sequence. For example, if a data group has 3 records, then you can specify the sequence in which the application processes the records. You can also select the next data group to identify which data group the application processes next.

Attributes

Attributes are the individual fields inside the extract record. An attribute is the lowest attribute level of a HCM extract and represents a piece of information, for example, person first name, person last name or person date of birth.
This figure shows the hierarchy of information within a data group definition.
Hierarchy of data objects within an extract definition.

Threading Database Item

A threading database item is a unique identifier for a given user entity to uniquely identify an extracted record. Configuring threading database items makes the comparison and identification of changes in Changes Only extract runs more efficient . You can define one threading database item at the root data group or at any child data group level.

Conditional Actions

A conditional action identifies the action to perform, and optionally, print a message based on the outcome of a conditional expression or a predefined fast formula. Conditional actions are applied on the extracted data similar to criteria conditions that are applied before extraction. Actions and messages are predefined in lookups, and you can add your own messages by creating new values for the lookup.

When a condition is satisfied, you can use this feature to perform certain predefined actions. For example, you can exclude employees that satisfy a condition, such as all employees from a predefined country. You can also configure this feature to raise a warning when an employee's salary is blank or beyond a specific level.

Note: We strongly recommend users to avoid using conditional actions which can adversely impact the runtime performance of an extracts run.

Exclusion Rules

You can exclude or override a record that doesn't suit your requirements with your own record by using an exclusion rule. The extract process doesn't process excluded records based on the legislative data group.

Note: We strongly recommend not using exclusion rules as these are extremely difficult to troubleshoot when records get excluded. Alternatively, use BI Publisher templates to handle the processing of conditional actions and exclusion rules.