Guidelines for Loading Organization Trees

An organization tree is a hierarchy of organizations of any classification. For each tree, you can define multiple versions. However, only one version can be active on any date.

This topic describes aspects of Organization Tree objects that you must understand to load them successfully using HCM Data Loader.

How Organization Trees Are Implemented

Organization trees are implemented using two HCM Data Loader objects. This table introduces those objects.

Object

Description

Organization Tree

The definition of a tree and the versions of the tree. A tree version is empty until you load organization tree nodes for the tree version.

Organization Tree Node

The organization tree nodes for a tree version. Each node represents an organization.

Preparing Organization Trees for Use

After loading organization tree nodes, you must flatten, audit, and activate your tree version. You can't reference your tree version from other objects, such as Area of Responsibility, until it's active. You can activate your tree version on the Manage Organization Trees page in the Workforce Structures work area. In summary, you:

  1. Search for and select your organization tree.

  2. Expand the hierarchy and select the version to activate.

  3. Select Actions > Set Status > Active to activate the tree version. The tree flattening and audit occur automatically.

For more information about managing hierarchy trees, see the Implementing Global Human Resources guide.

Loading Organization Trees

You supply organization-tree data in the OrganizationTree.dat file for processing by HCM Data Loader. The TreeStructureCode attribute of both the organization tree and the organization tree version must be set to PER_ORG_TREE_STRUCTURE for an organization tree.

Note: When you load a new organization tree version for an existing organization tree, you must include the organization tree component in the OrganizationTree.dat file. You can't load a new organization tree version in isolation.
METADATA|OrganizationTreeNode|OrganizationTreeNodeId|TreeStructureCode|TreeCode|TreeVersionName|OrganizationId(SourceSystemOwner)|OrganizationId(GUID) |OrganizationName |ClassificationCode|ReferenceTreeVersionName|ReferenceTreeCode|ParentOrganizationId(SourceSystemOwner) |ParentOrganizationId(GUID)|ParentOrganizationName|ParentClassificationCode|SourceSystemOwner|SourceSystemIdMERGE  |OrganizationTreeNode||PER_ORG_TREE_STRUCTURE |ApprovalHierarchy|ApprovalHierarchy_January2021|HRC_SQLLOADER|B104F5BF20E83097E053334CF70A512F ||DEPARTMENT||||||||
MERGE|OrganizationTreeNode||PER_ORG_TREE_STRUCTURE|ApprovalHierarchy |ApprovalHierarchy_January2021 |HRC_SQLLOADER|B14F66EC9CC8DF14E053334CF70A71FF||DEPARTMENT|||HRC_SQLLOADER|B104F5BF20E83097E053334CF70A512F||DEPARTMENT||

Deleting Organization Trees

You can delete Organization Tree and Organization Tree Version components using HCM Data Loader. When you delete an organization tree, the tree and all of its versions and nodes are deleted.

Note: The organizations themselves aren't deleted. Only the relationships defined in the tree structure are deleted.

This example OrganizationTree.dat file deletes an organization tree:

METADATA|OrganizationTree|TreeStructureCode|TreeCode
DELETE|OrganizationTree|PER_ORG_TREE_STRUCTURE|Organization Tree Code

If you delete an organization tree version, then only the specified version and its nodes are deleted. The tree and its other versions are retained. This example OrganizationTree.dat file deletes an organization tree version:

METADATA|OrganizationTreeVersion|TreeStructureCode|TreeCode|TreeVersionName
DELETE|OrganizationTreeVersion|PER_ORG_TREE_STRUCTURE|Organization Tree Code|Tree Version Feb