Results for “partner_access_id”

50+ results




Overview
Explore in AI Chat

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

Overview

The PV_TAP_ACCESS_TERRS table in the Oracle E-Business Suite Partner Management (PV) module stores the association between partner access records and the territory definitions to which those access records are granted. It functions as the intersection table that resolves the many-to-many relationship between partner access assignments and territory hierarchies, ensuring that each partner user is scoped to the correct set of territories for lead, opportunity, and channel activity visibility.

Under the heuristic Data Vault classification derived from the foreign key structure, this table is modeled as a link table. It carries no descriptive attributes of its own beyond the intersection identifiers; its purpose is to record the association (link) between a partner access entity and a territory entity. The link is keyed by the composite business key (PARTNER_ACCESS_ID, TERR_ID), which is also enforced by unique index PV_TAP_ACCESS_TERRS_U1.

Key Information Stored

The table contains 13 documented columns in the 12.2.2 physical schema. The columns of primary business significance are:

  • PARTNER_ACCESS_ID — The identifier of the partner access record; part of the composite primary key and the primary linkage to the partner access entity.
  • TERR_ID — The territory identifier; the second component of the composite primary key, referencing the territory definition granted to the access record.
  • SECURITY_GROUP_ID — The foreign key to FND_SECURITY_GROUPS, providing multi-tenant security group partitioning across the data.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications framework to prevent concurrent update conflicts.
  • CREATED_BY / CREATION_DATE — Audit columns recording the creating user and timestamp.
  • LAST_UPDATED_BY / LAST_UPDATE_DATE — Audit columns recording the most recent modifying user and timestamp.
  • LAST_UPDATE_LOGIN — The login identifier associated with the last update.
  • REQUEST_ID / PROGRAM_APPLICATION_ID / PROGRAM_ID — Concurrent program context columns identifying the batch process that last touched the row.
  • PROGRAM_UPDATE_DATE — Timestamp of the concurrent program update.

The surrogate/primary key is PV_TAP_ACCESS_TERRS_PK on (PARTNER_ACCESS_ID, TERR_ID). The unique index PV_TAP_ACCESS_TERRS_U1 mirrors the same column pair as the business-key candidate. The user search term "pv_tap_access_terrs_pk" refers directly to this primary key constraint. Note that the primary key here is a composite business key rather than a system-generated surrogate; the two constituent columns are themselves foreign-key-style references into the partner access and territory domains.

Common Use Cases and Queries

Typical usage centers on resolving which territories a given partner access record can see, and conversely which access records are granted a given territory.

  • Territories for a partner access record: SELECT TERR_ID FROM PV_TAP_ACCESS_TERRS WHERE PARTNER_ACCESS_ID = :access_id;
  • Access records granted a territory: SELECT PARTNER_ACCESS_ID FROM PV_TAP_ACCESS_TERRS WHERE TERR_ID = :terr_id;
  • Audit of recent territory grants: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY.
  • Security group scoping: join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to reconcile multi-org visibility.
  • Reconciliation reports identifying access records with no territory assignment (orphan detection via outer join).

Related Objects

  • FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID (documented FK).
  • PV_TAP_ACCESS_TERRS_PK — the primary key constraint on (PARTNER_ACCESS_ID, TERR_ID).
  • PV_TAP_ACCESS_TERRS_U1 — the unique index enforcing the composite business key.
  • Partner access definition table referenced by PARTNER_ACCESS_ID (the master access entity).
  • Territory definition table referenced by TERR_ID (the territory master).
  • Related PV territory and partner management views/APIs that consume the territory-to-access mapping for partner visibility.

The table is classified as standalone in the Data Vault heuristic, meaning it does not itself anchor a downstream FK chain, but it participates in the partner access and territory relationship structure through its composite key columns.