Examples of Loading HCM Position Hierarchies

An HCM position hierarchy is derived from the relationships between positions and their parent positions. You can identify a position's parent position on the Manage Positions page if the Use HCM Position Hierarchy option is enabled for the enterprise.

This topic provides examples of how to load Position Hierarchy objects using HCM Data Loader. Each Position Hierarchy object identifies a position and its parent. All positions must exist in the target environment.

Position EVP at the top is the parent of position VP, which is the parent of position PM_DIR. Position PM_DIR is the parent of two positions, PM_MGR_SALES and PM_MGR_ACCESS. PM_MGR_SALES is the parent of two positions, SNR_PM_SALES and PM_SALES. PM_MGR_ACCESS is the parent of two positions, SNR_PM_ACCESS and PM_ACCESS. — This figure shows the position hierarchy that these examples load.

Loading HCM Position Hierarchies Using Source Keys

This example PositionHierarchy.dat file loads Position Hierarchy objects using source keys.

METADATA|PositionHierarchy|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|ParentPositionId(SourceSystemId)|PositionId(SourceSystemId)
MERGE|PositionHierarchy|Vision|1|2015/01/01|4712/12/31|PM_MGR_ACCESS|PM_ACCESS
MERGE|PositionHierarchy|Vision|2|2015/01/01|4712/12/31|PM_MGR_ACCESS|SNR_PM_ACCESS
MERGE|PositionHierarchy|Vision|3|2015/01/01|4712/12/31|PM_MGR_SALES|PM_SALES
MERGE|PositionHierarchy|Vision|4|2015/01/01|4712/12/31|PM_MGR_SALES|SNR_PM_SALES
MERGE|PositionHierarchy|Vision|5|2015/01/01|4712/12/31|PM_DIR|PM_MGR_ACCESS
MERGE|PositionHierarchy|Vision|6|2015/01/01|4712/12/31|PM_DIR|PM_MGR_SALES
MERGE|PositionHierarchy|Vision|7|2015/01/01|4712/12/31|VP|PM_DIR
MERGE|PositionHierarchy|Vision|8|2015/01/01|4712/12/31|EVP|VP

Loading HCM Position Hierarchies Using User Keys

This example PositionHierarchy.dat file loads Position Hierarchy objects using user keys.

METADATA|PositionHierarchy|EffectiveStartDate|EffectiveEndDate|ParentBusinessUnitName|ParentPositionCode|BusinessUnitName|PositionCode
MERGE|PositionHierarchy|2015/01/01|4712/12/31|VisionBU|PM_MGR_ACCESS|VisionBU|PM_ACCESS
MERGE|PositionHierarchy|2015/01/01|4712/12/31|VisionBU|PM_MGR_ACCESS|VisionBU|SNR_PM_ACCESS
MERGE|PositionHierarchy|2015/01/01|4712/12/31|VisionBU|PM_MGR_SALES|VisionBU|PM_SALES
MERGE|PositionHierarchy|2015/01/01|4712/12/31|VisionBU|PM_MGR_SALES|VisionBU|SNR_PM_SALES
MERGE|PositionHierarchy|2015/01/01|4712/12/31|VisionBU|PM_DIR|VisionBU|PM_MGR_ACCESS
MERGE|PositionHierarchy|2015/01/01|4712/12/31|VisionBU|PM_DIR|VisionBU|PM_MGR_SALES
MERGE|PositionHierarchy|2015/01/01|4712/12/31|VisionBU|VP|VisionBU|PM_DIR
MERGE|PositionHierarchy|2015/01/01|4712/12/31|VisionBU|EVP|VisionBU|VP

Running the Flatten HCM Position Hierarchy Process

Changes to the parent position on the Manage Positions page automatically trigger a process to update the position hierarchy. This process is also triggered automatically when you load position hierarchies using HCM Data Loader. You can prevent the Flatten HCM Position Hierarchy process from running automatically by including a SET instruction in the PositionHierarchy.dat file.