Oracle Oracle Territory Management, Implementation Manual

Page: 68 / 98

Creating Individual Territories
5-10 Oracle Territory Management Implementation Guide
3.
Enter a name and description for the territory.
4.
To limit the time the territory is effective, enter the Start and End Dates. By
default the territory become effective on the date that you create it.
5.
(Optional) Verify that the parent territory is the territory you selected in the
Navigator. If this is not the parent territory, then use the LOV to select the
appropriate parent territory.
6.
Enter an appropriate rank in the Rank field.
7.
Enter an appropriate number in the Number of Winners field.
8.
(Optional) If you have created an escalation territory for this territory, then
enter it using the LOV in the Escalation field.
9.
(Optional) If you want to use an existing territory type to create this territory,
then use the LOV to enter it in the Type field.
10.
Use the Transaction Types LOV to select one or more types of transactions
based on the territory usage. Note that some application types allow you only
one transaction type.
11.
Leave the Freeze check box unchecked.
12.
Click Save from the toolbar to save the territory overview information.
Guidelines
Relationship Between Usage, Transaction Types, and Transaction Qualifiers
The territory usage is tied to the application, such as Sales and TeleSales, Service, or
Trade Management. Each application uses its specific sets of transaction qualifiers
for their unique business needs and these transaction qualifiers are grouped by
transaction type.
For example, a territory created for Sales and TeleSales usage has three seeded
transaction types: account, lead, and opportunity. While a territory created for
Service usage can only see task, service request, as well as “task and service
request” shown in the Transaction Type field.
Note: If you use a territory type, then you are restricted to using
the qualifiers set up in that territory type.