Go to main content

Oracle Territory Manager Implementation Guide

Contents

Title and Copyright Information

Send Us Your Comments

Introduction

Overview of Oracle Territory Manager

Sales Territories

Non-Sales Territories

Oracle Territory Manager Features

Dependencies and Integration Points

Oracle Territory Manager Mandatory Dependencies

Oracle Territory Manager Optional Integrations

Implementation Overview

Process Description

Territory Planning

Planning Your Territories

Sales Territory Planning Example

Step 1: What business objects are we assigning?

Step 2: What matching attributes should we use?

Step 3: Territory hierarchy - Define date effectivity and number of winners

Step 4: Territory hierarchy – Placeholder territories

Step 5: Implement Self Service

Step 6: Territory hierarchy – Define Catch Alls

Step 7: How to implement named account territories

Step 8: How to implement geographic territories

Step 9: How to support overlays

Step 10: What is an appropriate territory hierarchy for overlays?

Step 11: What rank should each territory have?

Step 12: Have you met all your business requirements?

Leverage Territory Hierarchies and Inheritance

Leverage Territory Ranking and Number of Winners

Choosing Appropriate Matching Attributes

Migrating Territories

Implementation Tasks

Setting Up User Security

Setting Up Multiple Organization Access Control

If You Have Value Added Tax (VAT)

Creating Custom Matching Attributes

Enabling Matching Attributes

Sales Matching Attributes

Running Concurrent Programs

Setting Up Territory Assignment Program

Setting Up to Use Dun & Bradstreet Data

Setting Up Territory Alignment

Setting Up Export

Loading Postal Codes

APIs

Verify and Troubleshoot

Verification Tasks

Profile Options

Prerequisites for Using Web ADI

Troubleshooting Export to Excel

Party, Party Site, and Account Merge

Tips for Fine-tuning Territory Assignment Performance

If the Synchronize Territory Assignment Rules Fails

Frequently Asked Questions (FAQs) about Transaction Matching Attributes

Creating Custom Matching Attributes

CMA for Account: Party Type

CMA for Lead: Lead Status

CMA for Quote: Quote Source

CMA for Proposal: Proposal Status

CMA for Opportunity: Budget Status

CMA for Oracle Collections, Customer: Customer Party Type