Search Results as_territory_types_all




Overview
Explore in AI Chat

Overview

The table AS_TERRITORY_TYPES_ALL is a core data object within the Oracle E-Business Suite (EBS) Sales Foundation (AS) module. Its primary function is to define and store the master list of territory types used to classify sales territories within the application. As indicated in the official documentation, this table is flagged as "Obsolete To JTF Terr Core," signifying a migration path to the JTF Territory Core definitions in later architectural versions. In releases 12.1.1 and 12.2.2, it remains a critical reference table that supports the hierarchical and categorical organization of sales territories, enabling structured territory management, assignment, and reporting.

Key Information Stored

The table's structure centers on the unique identification and description of a territory type. The most critical column is TERRITORY_TYPE_ID, which serves as the primary key and unique numeric identifier for each territory type record. Another essential column is NAME, which holds the descriptive name of the territory type (e.g., "Sales Region," "Industry Vertical," "Geographic Zone") and is enforced as a unique key. The table also includes a TERRITORY_GROUP_ID column, which acts as a foreign key linking the type to a parent grouping defined in the AS_TERRITORY_GROUPS_ALL table, allowing for further categorization. Standard Oracle EBS audit columns, such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY, are also present to track record history.

Common Use Cases and Queries

This table is primarily used for setup, validation, and reporting. Administrators query it to maintain the list of available territory types during application configuration. A common reporting use case involves joining this table to territory details to analyze coverage or performance by type. For instance, to retrieve all active territory types with their associated group names, a typical SQL query would be:

  • SELECT atta.NAME AS TERRITORY_TYPE, atga.NAME AS TERRITORY_GROUP
  • FROM OSM.AS_TERRITORY_TYPES_ALL atta
  • LEFT JOIN OSM.AS_TERRITORY_GROUPS_ALL atga ON atta.TERRITORY_GROUP_ID = atga.TERRITORY_GROUP_ID
  • WHERE atta.NAME LIKE '%Sales%'
  • ORDER BY atta.NAME;

Another frequent operation is validating a specific TERRITORY_TYPE_ID during data loads or integration processes to ensure referential integrity before inserting records into child tables like AS_TERRITORIES_ALL.

Related Objects

AS_TERRITORY_TYPES_ALL maintains defined foreign key relationships with several other tables in the Sales Foundation schema, as documented in the ETRM. These relationships are crucial for data integrity:

  • Parent Table (Foreign Key Reference): AS_TERRITORY_GROUPS_ALL, linked via the column AS_TERRITORY_TYPES_ALL.TERRITORY_GROUP_ID.
  • Child Tables (Referenced by Foreign Key):
    • AS_TERRITORIES_ALL, which references AS_TERRITORY_TYPES_ALL.TERRITORY_TYPE_ID in its TERRITORY_TYPE_ID column. This is the primary relationship where territory instances are classified by type.
    • AS_TERR_TYPE_QUALIFIERS, which references AS_TERRITORY_TYPES_ALL.TERRITORY_TYPE_ID in its TERRITORY_TYPE_ID column, linking types to specific qualification rules.

The table's primary keys (AS_TERRITORY_TYPES_ALL_PK, AS_TERRITORY_TYPES_PK on TERRITORY_TYPE_ID, and AS_TERRITORY_TYPES_UK on NAME) enforce uniqueness for these critical identifiers.