Search Results okc_governances_pk

Overview

OKC.OKC_GOVERNANCES is an intersection entity within the Oracle Contracts Core (OKC) module, introduced to model governance relationships between contract headers and contract lines in Oracle E-Business Suite 12.1.1 and 12.2.2. The object carries a heuristic Data Vault classification of link, indicating that it primarily resolves many-to-many associations between business entities rather than acting as a hub or satellite. In practice, this table records the governance linkage that binds a governing contract (or a governing line) to a governed contract (or governed line), enabling hierarchical and cross-referencing contract structures such as master agreements, sub-agreements, and referring clauses. The table is owned by the OKC schema and is currently VALID in the data dictionary.

Key Information Stored

The table contains fifteen documented columns. The most significant are summarized below:

• ID – Surrogate primary key, enforced by unique index OKC_GOVERNANCES_U1 and the OKC_GOVERNANCES_PK constraint.
• CHR_ID and CLE_ID – Foreign keys to OKC_K_HEADERS_B and OKC_K_LINES_B respectively, identifying the governing contract header and line. Together with CHR_ID, CLE_ID, these form the business-key candidate GVE_GVE_2_UK.
• CHR_ID_REFERRED and CLE_ID_REFERRED – Foreign keys to OKC_K_HEADERS_B and OKC_K_LINES_B, identifying the governed (referred) contract header and line.
• DNZ_CHR_ID – Denormalized contract header identifier used to optimize query performance for header-level governance lookups.
• ISA_AGREEMENT_ID – Associates the governance row with an ISA (Internal Sales Agreement) context where applicable.
• COPIED_ONLY_YN – Flag indicating whether the governance record exists only as a copy artifact during contract duplication.
• OBJECT_VERSION_NUMBER – Optimistic locking column used by the Oracle Application Framework (OAF) to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard WHO audit columns.
• SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS, supporting Multi-Org Access Control (MOAC) and data security partitioning.

Common Use Cases and Queries

Typical usage includes identifying all governance relationships for a given contract, tracing the chain of governing agreements, and reporting on master–sub agreement hierarchies. A representative query extracts all governance pairs for a contract header:

• SELECT g.ID, g.CHR_ID, g.CLE_ID, g.CHR_ID_REFERRED, g.CLE_ID_REFERRED FROM OKC.OKC_GOVERNANCES g WHERE g.CHR_ID = :header_id;
• Reporting on referred agreements: join OKC_K_HEADERS_B twice, once on CHR_ID and again on CHR_ID_REFERRED, to display governing and governed contract numbers side by side.
• Audit and duplicate detection: filter on COPIED_ONLY_YN = 'N' to exclude copy artifacts from operational reports.
• Security-scoped extraction: constrain by SECURITY_GROUP_ID to satisfy MOAC policies in multi-org deployments.

Because of the dual foreign keys to both headers and lines, API-driven maintenance (for example through the Contracts Core PL/SQL APIs that manage governance) is preferred over direct DML to preserve the integrity of the header/line pairings.

Related Objects

The following objects are the most significant dependencies for OKC_GOVERNANCES:

• OKC_K_HEADERS_B – Referenced through CHR_ID and CHR_ID_REFERRED; provides governing and governed contract headers.
• OKC_K_LINES_B – Referenced through CLE_ID and CLE_ID_REFERRED; provides governing and governed contract lines.
• FND_SECURITY_GROUPS – Referenced through SECURITY_GROUP_ID for MOAC enforcement.
• OKC_K_HEADERS_TL and OKC_K_LINES_TL – Translation tables used alongside the base tables for descriptive reporting.
• OKC_CONTRACT_UTILS and the Contracts Core PL/SQL APIs – Inclusive procedural layer that maintains governance records during contract creation, copy, and amendment.