Oracle Territory Management B10553 01 Users Manual Implem

2015-02-05

• Contents
• Send Us Your Comments
• Preface
  • Intended Audience
  • How To Use This Guide
  • Documentation Accessibility
  • Other Information Sources
  • Do Not Use Database Tools to Modify Oracle Applications Data
  • About Oracle
• Part I Getting Started
• 1 Introduction
  • 1.1 The Oracle E-Business Suite
    • 1.1.1 The Applications in the E-Business Suite
  • 1.2 Oracle Territory Management Overview
    • 1.2.1 Components
    • 1.2.2 Named Accounts
    • 1.2.3 Oracle Territory Management Features
  • 1.3 New in this Release
• 2 Before You Begin
  • 2.1 Related Documentation
  • 2.2 Installation Verification
    • 2.2.1 Create a Territory
    • 2.2.2 Run Concurrent Programs
    • 2.2.3 Test with a Lead
  • 2.3 Oracle Territory Management Dependencies
• Part II Implementing Oracle Territory Management
• 3 Implementation Overview
  • 3.1 Process Description
    • 3.1.0.1 Phase I: Territory Planning
    • 3.1.0.2 Phase II: Setting Up Territories
    • 3.1.0.3 Phase III: Creating Named Account Territories
    • 3.1.0.4 Phase IV: Managing Territories
  • 3.2 Implementation Task Sequence
  • 3.3 Multi-Org
• 4 Phase I: Territory Planning
  • 4.1 Planning Your Territories
  • 4.2 Sales Territory Planning Example
    • 4.2.1 Step 1: What business objects are we assigning?
    • 4.2.2 Step 2: What qualifiers should we use?
    • 4.2.3 Step 3: Territory hierarchy - Define date effectivity and number of winners
    • 4.2.4 Step 4: Territory hierarchy – Define Catch Alls
    • 4.2.5 Step 5: Territory hierarchy – Placeholder territories
    • 4.2.6 Step 6: How to implement named account territories
    • 4.2.7 Step 7: How to implement geographic territories
    • 4.2.8 Step 8: How to support overlays
    • 4.2.9 Step 9: What is an appropriate territory hierarchy for overlays?
    • 4.2.10 Step 10: What rank should each territory have?
    • 4.2.11 Step 11: Have you met all your business requirements?
    • 4.2.12 Leverage Territory Hierarchies and Inheritance
    • 4.2.13 Leverage Territory Ranking and Number of Winners
    • 4.2.14 Appropriate Choice of Qualifiers
    • 4.2.15 Qualifier Rules
    • 4.2.16 Migrating Territories
  • 4.3 Sales Territory Qualifiers
  • 4.4 Service Territory Qualifiers
• 5 Phase II: Setting Up Territories
  • 5.1 Overview of Creating Territories
  • 5.2 Qualifiers
    • 5.2.1 Transaction Qualifiers
      • 5.2.1.1 Sample List of Seeded Transaction Qualifiers
      • 5.2.1.2 Customer Name and Customer Name Range,
    • 5.2.2 Resource Qualifiers
      • 5.2.3.1 Seeded Qualifiers
  • 5.3 Territory Hierarchies
  • 5.4 Territory Winning Rules
  • 5.5 Enabling Existing Qualifiers
  • 5.6 Creating Individual Territories
  • 5.7 Entering Transaction Qualifiers
  • 5.8 Entering Resource Qualifiers
  • 5.9 Specifying Resources for a Territory
  • 5.10 Adding Subterritories
  • 5.11 Running Concurrent Programs
• 6 Phase III: Creating Named Account Territories
  • 6.1 Overview of Creating Named Account Territories
    • 6.1.1 Components of Self-Service Named Accounts
    • 6.1.2 Ongoing Maintenance
    • 6.1.3 Annual Maintenance
    • 6.1.4 Territory Autogeneration Mechanics
  • 6.2 Named Account Territory Process
  • 6.3 Migrating from Existing Territories to Named Account Territories
  • 6.4 Enabling Qualifiers
  • 6.5 Creating a Parent Territory
  • 6.6 Creating Territory Groups
  • 6.7 Defining Named Account Rules
  • 6.8 Assigning the Sales Team to Named Accounts
  • 6.9 Running Concurrent Programs
  • 6.10 Usage Implementation
• Part III Post Implementation Tasks
• 7 Verify the Implementation
  • 7.1 Verification Tasks
• 8 Troubleshooting
  • 8.1 Tips for Fine-tuning Territory Assignment Performance
  • 8.2 If the Generate Territory Packages Fails
  • 8.3 Frequently Asked Questions (FAQs) about Transaction Qualifiers
  • 8.4 Diagnostic Reports