Bookshelf Home | Contents | Index | PDF |
Siebel Territory Management Guide > Activating and Maintaining Territory Alignments > Maintaining Territory HierarchiesThe following tasks describe how to work with territory Hierarchies:
Viewing All Hierarchies for a TerritoryOne territory can be in several hierarchies, as described in About Territory Hierarchies and Divisions. You can view all the hierarchies that a given territory is in. To view all hierarchies that a territory is in
Copying Territory HierarchiesWhen you copy a hierarchy, the application does a deep copy, copying all active nodes within the hierarchy. You enter a new name for the copied hierarchy, and the application includes all the active nodes from the original hierarchy under the new copy of the hierarchy. If you are creating a new hierarchy that is similar to an existing hierarchy, you can copy the existing hierarchy and then modify the copy. Copying Only Active NodesBy default, when you copy hierarchies, the copy includes only the active nodes of the original hierarchy. You can configure the application so the copy includes all the nodes of the original hierarchy. You can copy all nodes by changing the user property Copy All Territory Nodes in the buscomp Territory Hierarchy. The default value is N. Copying the HierarchyUse the following procedure to copy the hierarchy.
Deleting Territory HierarchiesWhen you delete a territory hierarchy, the application performs a cascade delete, which deletes all the nodes in the hierarchy as well as deleting the hierarchy record. The application will not delete hierarchies with active nodes. Before you can delete a hierarchy, you must make sure that none of its nodes is active.
Removing Territory Nodes from HierarchiesOnly 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. 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, explicitly expire the associated rules, as outlined in the procedure below. To remove territory nodes from a hierarchy and expire the associated rules
|
Siebel Territory Management Guide | Copyright © 2008, Oracle. All rights reserved. | |