When Employees are Not Associated to Trees

If an employee cannot be associated to any of the tree nodes based on the hierarchical basis value that is set by the user, the employee is placed into a default node called Comp Admin Group. For example there could be employees that have department IDs other than any of those found in the tree.

Because the selection criteria for the Tree Creation process and the Group Build process could be different, there is an implied connection via the hierarchical basis value.

The assumption is that the user is aware of the relationship between the two processes and has made efforts to ensure that they are both compatible. This may not always be the case, however:

• The selection criteria for the population may be too broad and pick up more employees than expected.

• The tree structure that has been defined may not have all of the appropriate nodes that were expected to be included.

• There is bad or incorrect data in either the organization or employee's attributes that causes a mismatch.

• The employee being processed resides at the root node of the tree.

The Compensation Cycle Build process highlights these potential data anomalies by creating a special node and labeling it as a Comp Admin Group. This node is positioned so it reports directly to the root node. This enables the compensation administrator associated to the root node to view it as part of their setup and administrative activities.

For example, if the root node represented the president of the company, that person will then have access to update his or her own data. Therefore, the president is assigned to the Comp Admin Group and can be managed directly by the compensation administrator. The compensation administrator will have access to this node and will be able to determine if adjustments need to be made to the tree or if they will personally manage the employees that were placed in this node.