Overview of Loading Workers

The Worker object includes these person details: name, address, and picture, and these employment details: assignment, work relationship, contract, global transfer, tax reporting unit, working hours, and seniority dates and hours. This topic describes the considerations for loading workers using HCM Data Loader (HDL).

The Worker Hierarchy

Select the Worker object on the View Business Objects page to review its component hierarchy:

Using Source Keys

You can't update most components of the worker hierarchy if you supply only a user key. This restriction exists because the attribute that you want to change is the attribute that's used to identify the record. For example, in the Person Address component, the AddressLine1 attribute is used both to identify the address to update and to supply the new value. Therefore, you're recommended always to supply source keys when creating workers and use them when updating worker records.

Multiple Instances of a Component

A person can have multiple instances of some components, such as Person Address, Person Phone, and Person Email. When you load multiple instances of a component for a person, you must:

• Identify one of the records as primary using the PrimaryFlag attribute of the component.

• Process the occurrences together and include the parent Worker component in the file. If the worker already exists in Oracle HCM Cloud, then you can include just the primary-key attributes of the worker.

The Employment Model

You must understand the employment model in the legal employer to which you're loading work relationships and assignments. In any legal employer, the Employment Model option can be set to one of these values:

• 2 Tier - Single Assignment

• 2 Tier - Multiple Assignment

• 2 Tier - Single Contract - Single Assignment

• 2 Tier - Multiple Contract - Single Assignment

Regardless of the employment model, an employment terms record is always created for an assignment. Therefore, you must include an Employment Terms component in the .dat file. When loading multiple work relationships or assignments for a person, you must identify which is primary using the PrimaryFlag attribute. A person must have only one primary work relationship at a time and only one primary assignment in each work relationship.

Defining Referenced Values

Many components of the Worker object include values, such as person type and assignment status, that must exist in the target environment. Perform the tasks shown in this table to define relevant values before you load data.

Task	Description
Manage Actions	Defines the actions used to classify changes to employment data
Manage Person Types	Defines subcategories of the predefined person types, such as Employee and Nonworker
Manage Assignment Status	Defines status values, such as active, inactive, or suspended, for assignments

In addition, you must have reviewed and updated lists of values, such as address types, phone types, ethnicity, and marital status, before loading workers. You may have performed this step during implementation. If you're synchronizing assignments from positions, then you must enable position synchronization before you load assignments.

Worker Termination

You terminate work relationships, not workers. When you terminate a work relationship using HCM Data Loader, its child components, such as Assignment components, are terminated automatically. Don't try to terminate other child components of the worker object, such as Person Name. The person record must continue to exist and be returned in search results, for example.

Loading the Person Attributes Descriptive Flexfield

The Person Attributes (PER_PERSONS_DFF) descriptive flexfield isn't date-effective, and a person can have only one context value at a time. If you load a new context value, then it overwrites any existing context value.