Step 4: Territory Hierarchy - Define Catch Alls - Oracle Territory Management Implementation Manual

Sales Territory Planning Example
4.2.4 Step 4: Territory hierarchy – Define Catch Alls
We have separate sales forces for US and Canada so we will create 2 child territories
underneath FY2004 Sales; one called US Catch All with a transaction qualifier rule
COUNTRY = 'UNITED STATES' and another called Canada Catch All with a
transaction qualifier rule COUNTRY = 'CANADA'. The COUNTRY qualifier rules
will be inherited by all child territories, easing maintenance. These 2 territories will
also serve as "Catch Alls" for exceptions of the assignment process. These are
important because customers, leads or opportunities that do not find matching leaf
node territories will fall into these "Catch All" territories based on their country
qualifier and can be assigned to a designated owner (e.g., typically the territory
administrator) for resolution. The territory administrator should have customer,
lead and opportunity access.
Catch Alls are used to "catch" business transactions that fall through the cracks (leaf
node territories) and usually are assigned to territory administrators. To be more
exact, they "catch" all business transactions that fall into the catchall territory itself
or any territory below it in the hierarchy that does not have a resource.
It is recommended that you use the term "Catch All" in the naming of these
territories to help visually distinguish this type of territory.
Phase I: Territory Planning 4-7