Search Results as_territory_accesses




Overview
Explore in AI Chat

Overview

The AS_TERRITORY_ACCESSES table is a core data object within the Oracle E-Business Suite Sales Foundation (AS) module, specifically under the OSM schema. Its primary function is to define and manage the relationship between territory definitions and access records. In the context of Oracle EBS 12.1.1 and 12.2.2, this table serves as a critical junction table, enabling the complex territory management and resource assignment capabilities that underpin the sales force automation and territory-based access control features. It acts as the structural link that associates a specific territory with one or more access entities, thereby governing which resources or data sets are accessible within a defined sales or service territory.

Key Information Stored

The table's structure is centered around two primary foreign key columns that form its composite primary key. The ACCESS_ID column references a unique access record, which typically defines a specific privilege, resource, or data object. The TERRITORY_ID column references a unique territory definition from the standard JTF territory tables. The combination of these two columns (AS_TERRITORY_ACCESSES_PK) ensures that a given access privilege is uniquely assigned to a specific territory. This design prevents duplicate assignments and is fundamental for maintaining data integrity in the territory-access relationship model.

Common Use Cases and Queries

A primary use case is reporting and auditing which access privileges are assigned to specific sales territories. Administrators may run queries to validate territory setups or troubleshoot access issues for sales representatives. A common reporting pattern involves joining to the related territory and access master tables to produce a human-readable list. For example, a query to list all accesses for a given territory would filter on TERRITORY_ID and join to JTF_TERR_ALL for the territory name and AS_ACCESSES_ALL for the access details. Conversely, identifying all territories granted a particular access right would involve filtering on ACCESS_ID. Data maintenance operations, such as provisioning a new access right to multiple territories, would involve inserting multiple records into this table, each with the same ACCESS_ID but different TERRITORY_ID values.

Related Objects

The AS_TERRITORY_ACCESSES table is intrinsically linked to two key master tables via foreign key relationships, as documented in the ETRM metadata:

  • JTF_TERR_ALL: This is the primary territory definition table. The AS_TERRITORY_ACCESSES.TERRITORY_ID column references JTF_TERR_ALL, ensuring that every territory referenced in an access assignment is a valid, existing territory.
  • AS_ACCESSES_ALL: This is the master table for access definitions. The AS_TERRITORY_ACCESSES.ACCESS_ID column references AS_ACCESSES_ALL, ensuring that every assigned access privilege is defined in the central access catalog.

These relationships enforce referential integrity, meaning a territory or access record cannot be deleted if active assignments exist in the AS_TERRITORY_ACCESSES table. Any comprehensive data retrieval or modification involving territory accesses will necessarily involve joins to these parent tables.