Results for “as_territory_accesses”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AS_TERRITORY_ACCESSES is a Sales Foundation (AS) table owned by the OSM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the association between a sales territory and the access records that govern which resources within that territory are permitted to view or act upon a given business object. In ETRM (Territory Manager) terms, this table is the physical junction that binds territory membership to the access-control definitions maintained in AS_ACCESSES_ALL_ALL.

Under the heuristic Data Vault classification derived from the foreign-key topology, this table behaves as a link: it resolves a many-to-many relationship between territories (JTF_TERR_ALL) and access definitions (AS_ACCESSES_ALL_ALL) and carries descriptive and auditing attributes rather than serving as a standalone hub. This classification is a modeling suggestion based on the two inbound FK references and the composite unique business key, not an Oracle-published designation.

Key Information Stored

The table contains 14 documented columns. The most significant are:

• ACCESS_ID — Identifier of the access definition from AS_ACCESSES_ALL_ALL. Part of the composite primary key and the unique business key.
• TERRITORY_ID — Identifier of the territory from JTF_TERR_ALL. Second component of the composite primary key and unique business key.
• USER_TERRITORY_ID — Reference to the specific user-level territory context within which the access applies; this adds the "who" dimension beyond the parent territory.
• SECURITY_GROUP_ID — Multi-org/multi-tenant security grouping, resolving to FND_SECURITY_GROUPS. Critical for data isolation in shared environments.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program provenance columns tracking which request inserted or updated the row.
• OBJECT_VERSION_NUMBER — Optimistic locking token used by the OAF/BC4J layer.

The surrogate primary key is AS_TERRITORY_ACCESSES_PK, defined over (ACCESS_ID, TERRITORY_ID). A unique index, AS_TERRITORY_ACCESSES_U1, enforces the same pair as the business-key candidate. Because the PK and business key coincide, the row is a pure association record with no independent surrogate identity.

Common Use Cases and Queries

Typical uses include resolving which users can see a given territory's opportunities, resources, or customers, and auditing access grants by territory. A common reporting pattern joins all three referenced tables:

• List all accesses for a territory: SELECT a.ACCESS_ID, a.TERRITORY_ID FROM AS_TERRITORY_ACCESSES a WHERE a.TERRITORY_ID = :tid
• Expand access metadata: join AS_ACCESSES_ALL_ALL on ACCESS_ID and JTF_TERR_ALL on TERRITORY_ID to retrieve access names and territory names alongside the link row.
• Security-group scoping: add WHERE SECURITY_GROUP_ID = :sg to restrict results in multi-org configurations.
• Change tracking: filter on LAST_UPDATE_DATE or PROGRAM_ID to identify rows touched by a specific concurrent request.

Because the table is exposed through the Territory Manager administrative UI, ad-hoc queries should be read-only. For inserts and updates, the supported path is the ETRM forms and APIs rather than direct DML, since OBJECT_VERSION_NUMBER and the concurrent-program columns must remain consistent.

Related Objects

• JTF_TERR_ALL — Parent territory table; joined on TERRITORY_ID.
• AS_ACCESSES_ALL_ALL — Access definition table; joined on ACCESS_ID.
• FND_SECURITY_GROUPS — Security group definitions; joined on SECURITY_GROUP_ID.
• AS_TERRITORY_ACCESSES_PK / _U1 — Primary key constraint and unique index over (ACCESS_ID, TERRITORY_ID).
• Territory Manager (ETRM) concurrent programs — referenced via PROGRAM_ID, PROGRAM_APPLICATION_ID, and REQUEST_ID.