Search Results as_territory_values_uk




Overview
Explore in AI Chat

Overview

The AS_TERRITORY_VALUES_ALL table is a core data object within the Oracle E-Business Suite (EBS) Sales Foundation (AS) module. Its primary function is to store the specific values or criteria that define the membership of a sales territory. These values act as the qualifying rules, linking territories to entities such as customers, addresses, inventory items, or interest codes. Crucially, the official ETRM documentation explicitly marks this table as "Obsolete To JTF Terr Core," indicating its functional replacement by newer territory management objects within the JTF (Java Toolkit Framework) core in releases 12.1.1 and 12.2.2. While it remains present in the OSM schema for backward compatibility, new territory definitions and assignments are managed through the successor JTF architecture.

Key Information Stored

The table's structure centers on linking a territory to its qualifying values. The primary identifier is the TERRITORY_VALUE_ID. The TERRITORY_ID column links the value to its parent territory definition. The table's significance is demonstrated by its foreign key relationships, which reveal the types of data it stores. Key columns include CUSTOMER_ID and ADDRESS_ID for defining territories based on customer or site attributes, INVENTORY_ITEM_ID and ORGANIZATION_ID for product-based territories, and PRIMARY_INTEREST_CODE_ID and SECONDARY_INTEREST_CODE_ID for territories defined by customer interest classifications. Additional descriptive columns, such as LAST_UPDATE_DATE and CREATED_BY, provide standard EBS audit trail information.

Common Use Cases and Queries

In a legacy or migration context, this table is central to queries analyzing historical territory composition or validating data during an upgrade to JTF-based territory management. A common reporting use case is to list all criteria for a specific territory. A sample SQL pattern for this would be: SELECT territory_id, customer_id, inventory_item_id, primary_interest_code_id FROM as_territory_values_all WHERE territory_id = :p_territory_id; Another critical scenario involves identifying all territories that contain a specific customer, which is essential for understanding historical assignment rules: SELECT DISTINCT t.territory_id, t.name FROM as_territories_all t, as_territory_values_all v WHERE t.territory_id = v.territory_id AND v.customer_id = :p_customer_id; Given its obsolete status, direct transactional use or modification of this table in standard EBS operations is strongly discouraged.

Related Objects

The AS_TERRITORY_VALUES_ALL table maintains documented foreign key relationships with several fundamental EBS tables, defining its integration points. These relationships, as per the provided metadata, are:

  • RA_CUSTOMERS: Joined via the CUSTOMER_ID column to associate territory values with specific customers.
  • RA_ADDRESSES_ALL: Joined via the ADDRESS_ID column to associate territory values with customer sites.
  • MTL_SYSTEM_ITEMS_B: Joined via the INVENTORY_ITEM_ID and ORGANIZATION_ID columns to associate territory values with inventory items.
  • AS_INTEREST_TYPES_ALL: Joined via the INTEREST_TYPE_ID column to categorize the interest codes used.
  • AS_INTEREST_CODES_ALL: Joined via the PRIMARY_INTEREST_CODE_ID and SECONDARY_INTEREST_CODE_ID columns to define territories based on customer interests.
The table's primary key, AS_TERRITORY_VALUES_ALL_PK, is on TERRITORY_VALUE_ID, and a unique key (AS_TERRITORY_VALUES_UK) exists on TERRITORY_ID, enforcing the relationship with the parent AS_TERRITORIES_ALL table.