1. HCM Data Loading Business Objects
  2. Guidelines for Loading Organizations

Guidelines for Loading Organizations

An organization can be any organizational unit, such as a department or division, in your enterprise. Organizations provide the framework for performing legal reporting, financial control, and management reporting.

This topic describes aspects of the Organization object that you must understand to load organizations successfully.

Organization Components

A single organization can have multiple classifications. For example, a division can also be a department. Therefore, you can load multiple Organization Classification components for a single Organization object.

Note: You must load any Organization Extra Information component with the parent Organization component in the same Organization.dat file. You can't load Organization Extra Information components independently of the parent Organization component. You can load other child components either when creating the organization or once the organization exists.

Loading Referenced Objects

Before you load organizations, referenced objects must exist in the target environment. In particular:

  • If you plan to associate locations with your organizations, then you must load the locations before you load the organizations.

  • To associate a reporting manager with your organization, you must:

    1. Load the organization without identifying the reporting manager.

    2. Load the worker information for the reporting manager.

    3. Update your organization to add the reporting manager.

    Tip: As a worker is hired into a legal employer, business unit, and department, you can't load workers before you load organizations.
Note: Departments are set enabled. You must ensure that relevant reference data sets exist before you load departments. Other types of organizations aren't set enabled.

Organization Classification Codes

An organization can have one or more classifications. You can supply either the code or its name. Valid classifications are shown in this table.

Classification Name

Classification Code

Department

DEPARTMENT

Disability Organization

HCM_DISABILITY_ORGANIZATION

Division

HCM_DIVISION

Reporting Establishment

HCM_REPORTING_ESTABLISHMENT

Union

PER_WORKER_UNION

You load an Organization Classification component for each of the organization's classifications, including the one identified on the Organization component.

Creating Departments Using Source Keys

This example Organization.dat file creates a department that is identified by source keys.

METADATA|Organization|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Name|ClassificationCode
MERGE|Organization|VISION|SALES|1980/01/01|Sales|DEPARTMENT
METADATA|OrgUnitClassification|SourceSystemOwner|SourceSystemId|OrganizationId(SourceSystemId)|EffectiveStartDate|ClassificationCode|SetCode|Status
MERGE|OrgUnitClassification|VISION|SALES_DEP|SALES|1980/01/01|DEPARTMENT|COMMON|A

Loading Translated Organization Names

Supply organization names in the language of the user who's loading them. You supply an OrganizationTranslation.dat file to translate organization names into other enabled languages once the organizations exist. This example OrganizationTranslation.dat file translates the name of an existing organization. It identifies the organization by its source key.

METADATA|OrganizationTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Language|Name
MERGE|OrganizationTranslation|VISION|MRKT|2000/01/01|FR|Marketing

Changing the Logical Start of Organizations

You can't change the end date for an organization, instead make it inactive. However, you can change the earliest start date for an organization. This example Organization.dat file adjusts the earliest start date of a department that is identified by source keys.

METADATA|Organization|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Name|ClassificationCode|ReplaceFirstEffectiveStartDate
MERGE|Organization|VISION|SALES|1950/01/01|Sales|DEPARTMENT|Y
METADATA|OrgUnitClassification|SourceSystemOwner|SourceSystemId|OrganizationId(SourceSystemId)|EffectiveStartDate|ClassificationCode|SetCode|Status|ReplaceFirstEffectiveStartDate
MERGE|OrgUnitClassification|VISION|SALES_DEP|SALES|1950/01/01|DEPARTMENT|COMMON|A|Y
Note: You must supply the classification record. Your organization can't pre-date its classification.

Deleting Organizations

You can't delete Organization objects using HCM Data Loader, nor can you make them inactive. However, you can make an organization classification inactive, provided that it's no longer used. For example, for an organization that's classified as both a department and a division, you could:

  • Make the division inactive but leave the department active, so that you can still continue to use the department.

  • Deactivate the whole organization by making both classifications inactive.

This example Organization.dat file inactivates an existing organization classification. The organization is identified by its source key. 

METADATA|Organization|SourceSystemOwner|SourceSystemId|EffectiveStartDate
MERGE|Organization|VISION|CLARITY|2015/01/01
METADATA|OrgUnitClassification|SourceSystemOwner|SourceSystemId|EffectiveStartDate|OrganizationId(SourceSystemId)|Status
MERGE|OrgUnitClassification|VISION|CLARITY_DIS|2015/01/01|CLARITY|I
Note: The file must include an Organization component with an effective start date equal to the date on which the classification becomes inactive.

Prevent Inflight Department Updates

You can prevent inflight department updates when it's updated using the update and correct flows, or when a date effective department record is deleted, when approvals are pending. You need to create and set the HR_DISABLE_PENDING_APPROVALS_CHECK_IN _HCM_DATA_LOADER profile option to No, if it's not already created to prevent inflight department updates.

Related Topics