Oracle Oracle Territory Management, Руководство по внедрению

Страница: 54 / 98

Sales Territory Qualifiers
4-18 Oracle Territory Management Implementation Guide
4.2.15 Qualifier Rules
Best practices around qualifier rules are the simplest to follow because they are very
concrete. Qualifier rules are converted to SQL and are subject to the same
performance constraints. Always avoid the use of the following:
■
The use of the NOT operand forces full table scans and in the context of
Territory Manager includes:
NOT =
NOT LIKE
NOT BETWEEN.
To aid our best practices, we will be decommissioning the NOT operand and a
diagnostic test exists within Oracle Diagnostic Framework.
■
The use of the % wildcard as the first character of the qualifier value prevents
the use of indexes.
4.2.16 Migrating Territories
For how long are your territories active? Your sales organization may migrate to
new territories yearly or quarterly and you want to use the existing territory
hierarchy as a starting baseline. By following best practices, it will be easier to
migrate territories to the next period. The trick is to define a territory start date at
the top level territory, since all those below it will be gated by the start date
property. Copy the top-level territory, which will automatically copy all the child
territories as well. Rename the top-level territory and give it a new start date. Don’t
forget to go back to the old territory hierarchy and end date the top-level territory.
4.3 Sales Territory Qualifiers
The following table maps the sales qualifiers to their Sales Online and Telesales
counterparts.
Table 4–2 Sales Qualifiers
Transaction
Type
Territory Qualifier Sales Online/TeleSales Attribute
Account Account Classification Interest of "party site"
Account Account Code Customer Name + Address (party
site ID)