Siebel Territory Management Guide > Activating and Maintaining Territory Alignments >

Removing Territory Nodes from Hierarchies

Only active territory nodes are considered in territory alignments. Because of this, you need to exercise care in how you set nodes to expire; you need to make sure that the rules associated with expired nodes also expire as planned.

Example

Consider the case where a territory, say T3, contains rules with effective end dates of December 31st and where you set the end date for the node to be September 30th. Because T3 is removed from the hierarchy on September 30th, the rules associated with the hierarchy are ignored after September 30th. This means that the rules are not dropped after December 31st and any assignments made by those rules persist after December 31st (no matter how many times the alignment for the hierarchy is activated—as long as T3 remains inactive).

To avoid this type of problem, before removing nodes from a hierarchy, you should explicitly expire the associated rules, as outlined in the procedure below.

Procedure

This task is a step in the Process of Activating and Maintaining Territory Alignments.

To remove territory nodes from a hierarchy and expire the associated rules

1. Identify the nodes that you want to remove from the hierarchy.
2. Create, run, and activate a minor alignment for the hierarchy in order to drop rules from the territories that you no longer want:
   1. Copy the current alignment.
   2. For each node you want to remove, change the add rules to drop rules.
   3. Run the alignment.
   4. Activate the alignment.

      (Using the dates of the example, this alignment would be scheduled to run early in the day on September 30th.)

      This has the effect of expiring all rules in the territories that you want to remove.

3. Edit the Effective End Date for the nodes that you want to remove from the hierarchy.
4. Create, run, and activate a new alignment for the hierarchy.

   This alignment is the alignment you want, without reference to the territory nodes identified in Step 1.

   (Using the dates of the example, this alignment would be scheduled to run late in the day on September 30th.)