Guidelines for Loading Department Tree Nodes
A department is an internal organization to which workers are assigned. You can add any organization that has the Department classification as a tree node to a department tree version.
This topic describes aspects of Department Tree Node objects that you must understand to load them successfully using HCM Data Loader.
Preparing to Load Department Tree Nodes
Before you load department tree nodes:
-
You must create the department tree and department tree version to which the nodes belong. You can either load them using HCM Data Loader or create them using the Manage Department Trees task in the Workforce Structures work area.
-
The departments that the tree nodes refer to must exist on the start date of the tree hierarchy version. Simply adding a department to the department tree hierarchy doesn't create the department. Similarly, removing a department reference from a department tree hierarchy doesn't delete the department record.
Loading Department Tree Nodes
The department tree node records the relationship between a parent department and a child, which can be either a department or another department tree version. When the child is another department tree version, the department nodes of that version are included by reference. When you load department tree nodes, these rules apply:
-
You must supply a parent department for all nodes except the top-level node of your department tree version. The parent departments must exist.
-
The TreeStructureCode attribute must be set to PER_DEPT_TREE_STRUCTURE.
-
To avoid circular relationships, a department can appear only once in each tree version.
-
Each tree version can have only one top node. If you need multiple peer departments at the top, then consider using a dummy department as the top node.