Bookshelf Home | Contents | Index | PDF |
Siebel Territory Management Guide > Setting Up and Running Territory Alignments > About Conditions in Siebel Territory ManagementIf you use indirect rules, you can also use conditions to limit the pool of objects (accounts, contacts, and assets) that are available for assignment by indirect rules. Table 4 describes the types of conditions. This topic presents some important points and some examples of how conditions can be used in Siebel Territory Management. Because conditions cannot be explicitly grouped, the conditions that you can create for territory alignments are somewhat limited, and you need to understand these limitations in order to use conditions effectively. What Is a Scope?For global conditions, a scope is a set of conditions for the same object type. For local conditions, a scope is a set of conditions for a given object type, territory, postal code, and geo code combination. Figure 2 shows five scopes, some global and some local. Condition Evaluation Within a Given ScopeOne important difference between conditions in Siebel Territory Management and ordinary Boolean conditions is that, for a given scope, you must: You cannot put OR conditions between AND conditions. You cannot put AND conditions between OR conditions. See Figure 3. These grouped conditions are evaluated as follows:
Condition Evaluation Between ScopesThe AND operator is always automatically applied between global and local conditions. All subconditions must evaluate as true for the entire condition to be true. You cannot use the AND and OR operators between scopes, only within the same scope. Local conditions for different scopes are handled separately. For example, consider the condition: where A and B are global conditions, c is a local condition, and d and e are also local conditions but in a different scope from c. [(A AND B) AND c] OR [(A AND B) AND (d OR e)] About Using Dates as Attributes for ConditionsWithout configuration, Siebel Territory Management has three condition attributes for dates: If you create conditions using any of these attributes, be aware of the following:
About Using Divisions as Attributes of ConditionsTo define alignments with different business rules that apply to different sales forces, use the Divisions field of the Conditions list applet. This allows you to create conditions that apply to one sales force, since divisions represent sales forces. NOTE: You cannot combine division conditions with other types of conditions in a single condition record. For example, you cannot specify Division = Primary Care AND Territory = XYZ in a single condition. About Renumbering and Inserting ConditionsTo allow you to insert conditions in the list, if you change the sequence number of a condition, Siebel Territory Management automatically renumbers all conditions that follow. This allows you to insert new conditions in the sequence by renumbering only one condition. For example, you have defined ten global conditions for contacts, with sequence numbers from 1 to 10. You change the sequence number of the seventh condition from 7 to 15. Siebel Territory Management changes 8 to 16, 9 to 17, and 10 to 18. This allows you to insert new conditions with sequence numbers between 7 and 14. When you renumber conditions, Siebel Territory Management checks that no overlap occurs. In this example, if there were already a condition with sequence number 17, this existing number would overlap with the new sequence numbers that are created automatically. Siebel Territory Management displays an error message so you cannot make this change until you have corrected the condition that causes the overlap. About Copying Conditions from Another AlignmentConditions are not incremental. You must define the entire set of conditions for each alignment. You can click the Copy From Alignment button in the Alignment Administration screen, Conditions view to copy conditions from a previous alignment. Then you can use them as the basis of the conditions for a new alignment and modify them as needed for the new alignment. When you click the Copy From Alignment button, it displays a dialog box that allows you to choose among conditions that have been created for the same territory hierarchy. NOTE: When you copy conditions from a multidivision alignment into a single-division alignment, do not copy division local conditions in this way. CAUTION: When you copy conditions in this way, they overwrite any existing records in the Conditions list. |
Siebel Territory Management Guide | Copyright © 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |