Search Results okc_rep_contract_access_pk

Overview

OKC_REP_CONTRACT_ACCESS is a Contracts Core (OKC) table that stores the access control list (ACL) information for contracts managed within Oracle E-Business Suite. In Oracle EBS 12.1.1 and 12.2.2, the Contracts repository (often grouped under the ETRM / Contracts Intelligence framework) uses OKC_REP_CONTRACTS_ALL as the primary contract repository table. The OKC_REP_CONTRACT_ACCESS table complements it by defining which resources — typically JTF resources such as employees, users, or groups — are granted access to a specific contract record, and, by extension, to its associated documents, deliverables, and terms.

Each row in the table represents a single access-control entry: the pairing of a contract and a resource that is permitted to view, edit, or otherwise act upon it. This supports the security and authorization requirements of contract management, including multi-party contract collaboration where visibility must be limited to authorized personnel.

Based on the foreign-key structure — two references (CONTRACT_ID to OKC_REP_CONTRACTS_ALL and RESOURCE_ID to JTF_RS_RESOURCE_EXTNS) combined with a surrogate ACCESS_ID primary key — the heuristic Data Vault classification for this object is a link table. Modeled in Data Vault terms, it would represent an associative (many-to-many) relationship between the contract hub and the resource hub, capturing the access-assignment events between the two. This is a modeling suggestion derived from the FK topology rather than a documented data-warehouse designation.

Key Information Stored

The documented metadata identifies the following key elements:

• ACCESS_ID — The surrogate primary key. It is enforced by the constraint OKC_REP_CONTRACT_ACCESS_PK and uniquely identifies each access-control entry. It carries no business meaning and is populated by sequence.
• CONTRACT_ID — A foreign key referencing OKC_REP_CONTRACTS_ALL. It identifies the contract to which the access entry applies and, together with RESOURCE_ID, forms the natural business key (the contract–resource pair).
• RESOURCE_ID — A foreign key referencing JTF_RS_RESOURCE_EXTNS (the resource extension table). It identifies the individual resource (user or resource) granted access to the contract.

The documented metadata presents ACCESS_ID as the only declared primary-key column, and CONTRACT_ID and RESOURCE_ID as the two foreign-key columns. Additional descriptive or audit columns may exist in the physical table but are not confirmed in the source metadata. The business-key candidate is the composite of CONTRACT_ID and RESOURCE_ID, which should be treated as the unique identifier of an access assignment when the table is used for integration or reconciliation.

Note that the ETRM metadata records this table as "Not implemented in this database" for the referenced environment, meaning the structure is documented but the object is not present (or not populated) in that particular instance. Confirm object existence against the target EBS environment before relying on the table at runtime.

Common Use Cases and Queries

Because the table governs contract-level authorization, typical use cases center on security auditing and access reporting.

• Access enumeration: listing all resources with access to a given contract by joining to OKC_REP_CONTRACTS_ALL on CONTRACT_ID.
• Resource-centric review: identifying all contracts a given resource can access by joining RESOURCE_ID to JTF_RS_RESOURCE_EXTNS.
• Security/compliance reporting: detecting contracts with no access entries, or resources with unusually broad access, to support SOX or internal-control audits.
• Migration and reconciliation: using CONTRACT_ID and RESOURCE_ID as the business key when comparing access grants across environments.

A representative query pattern follows:

• SELECT a.ACCESS_ID, c.CONTRACT_NUMBER, a.RESOURCE_ID FROM OKC_REP_CONTRACT_ACCESS a, OKC_REP_CONTRACTS_ALL c WHERE a.CONTRACT_ID = c.CONTRACT_ID;

Related Objects

• OKC_REP_CONTRACTS_ALL — joined via CONTRACT_ID; the parent contract repository record.
• JTF_RS_RESOURCE_EXTNS — joined via RESOURCE_ID; the resource/user definition.
• OKC_REP_CONTRACT_ACCESS_PK — the primary-key constraint on ACCESS_ID.
• OKC_REP_CONTRACTS_ALL_PK / contract search views — used alongside this table for contract lookups.
• Contracts Core PL/SQL APIs — access-security packages that read and write ACL entries for contract display and authorization.