Create HCM Export Files for Account Aggregation

To support proper account aggregation with the Oracle HCM source, you must first export the account data into three CSV files. These files should then be saved into an FTP server that both the source and the connector can access. These files and the FTP server they reside in serve as the middleware required for entitlement management in the Oracle HCM system.

The data in these three files enables the connector to differentiate between new hires and rehires. It also enables the source to populate data points which enable it to trigger the Joiner, Mover, and Leaver workflows more effectively.

For more information, refer to Fusion Cloud HCM Integration with External Entitlement Management Systems in the Oracle documentation.

Note
The linked document is not maintained by SailPoint and is subject to change without notice.

You need to export HCM account data into the following three files, depending on the account type:

• Active Workers File – It should include an export of all the active person details from the HCM system.

• Terminated Workers File – It should include terminated person details that are within the Past Termination Offset setting.

  For more information, refer to Aggregation Settings.

• Future Workers File – It should include an export of all the future hires and active person future employment details that are within the Future Offset setting.

  For more information, refer to Aggregation Settings.

Important
The export files must be saved to an FTP server in which the connector has read/write permissions.

Export File Requirements

This section lists specific requirements that each generated aggregation file must meet to support account aggregation operations. If any of the requirements aren't met, you may experience in unexpected results during account aggregation or the aggregation process may fail.

1. All three generated files must be in CSV-format with a comma delimiter (,).

2. If a value in any of the three CSV files is a special character, such as a comma (,), enclose it with double quotes (").

3. All three files must be PGP-encrypted and signed using a single public and private key.

4. All three files must use UTF-8 encoding.

5. All three files must include the following attributes listed as headers.

   Caution
   The following schema attributes are case-sensitive, and must contain only capital letters. Lower-case letters are not accepted.

   Warning
   Do not edit or delete any of the default schema attributes listed below from any file. Removing or editing these fields will cause aggregation processes to fail.

   Sr. No	Schema Attribute Name
   1	PERSON_NUMBER
   2	HIRE_DATE
   3	TERMINATION_DATE
   4	PERIOD_OF_SERVICE_ID
   5	WORKER_TYPE
   6	WORKRELATIONSHIP_PRIMARY_FLAG
   7	ASSIGNMENT_ACTION_CODE
   8	ASSIGNMENT_EFFECTIVE_START_DATE
   9	ASSIGNMENT_EFFECTIVE_END_DATE
   10	ASSIGNMENT_PRIMARY_FLAG
   11	ASSIGNMENT_STATUS
   12	WORK_EMAIL

   Additionally, the WORKER_TYPE attribute must be mapped to include the following possible values:

   Caution
   The configured attribute value is case-sensitive, and it must use capital letters. Lower-case letter values are not accepted.

   Attribute Value	Definition
   E	Employees
   P	Pending Workers
   C	Contingent Workers
   N	Non-workers

   For example:

   WORKER_TYPE="E"

Note
Refer to the Oracle HCM Cloud Export File guide for more information and similar examples on the export of HCM data.

Example Use Cases

These examples are used to describe how additional attributes are fetched by the connector. For more information on additional attributes, refer to Additional Account Attributes.

Note
In both of the example FUTURE_WORKRELATIONSHIP_START_DATE and FUTURE_ASSIGNMENT_ACTION can act as data points which can be configured to trigger Joiner, Leaver, and Mover workflows.