Create a Separate HCM Export File

The HCM data needs to be exported in the following three separate files:

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

  • Terminated Workers File: It should include terminated person details within the offset.

  • Future Workers File: It should include export of all the future hires and active person future employment details within the offset.

Export of the data in these three separate files enables the connector to differentiate between the new hires and rehires. It also provides a mechanism to populate data points which will enable to trigger the Joiner, Mover, and Leaver workflow more effectively.

For Example:

  1. If a person is currently terminated as contractor and is getting rehired to full time employee in future.
    File Content: Terminated Workers File will include the entry of current employment information and Future Workers File will include the entry of future employment information.
    Aggregation Behaviour: The person will be aggregated as Terminated Contractor with the following additional attribute being fetched:

    Attribute

    Value

    FUTURE_WORKRELATIONSHIP_START_DATE

    Future Hire date will be fetched

    FUTURE_ASSIGNMENT_ACTION

    The future action of the person becomes “Rehire”

  2. If a person is active but his employment is scheduled to get terminated in future.
    File Content: Active Workers File will include information of current active employment and Future Workers File will include the entry of contract end date.
    Aggregation Behaviour: The person will be aggregated as active employee with following additional attribute being fetched:

    Attribute

    Value

    FUTURE_WORKRELATIONSHIP_START_DATE

    Future terminated date will be fetched

    FUTURE_ASSIGNMENT_ACTION

    The future action of the person becomes “Termination”

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.

Best Practices for Creating the File

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

  2. All these three files must be PGP encrypted and signed using single public and private key.

  3. All these three files must include the following mandatory attributes listed as headers.

    Note
    The following listed schema attributes are case-sensitive.

    4. 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

  4. WORKER_TYPE attribute must be mapped to include the following possible values:

    Note
    The attribute values are case-sensitive.

    Attribute Value

    Definition

    E

    Employees

    P

    Pending Workers

    C

    Contingent Workers

    N

    Nonworkers

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