Results for “chr_id_referred”

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

Overview

The OKC_GOVERNANCES_HV view is a history view within the Oracle E-Business Suite Contracts Core (OKC) module, owned by the APPS schema. It is defined over the history table OKC_GOVERNANCES_H, which stores the versioned, auditable records of governance relationships established between contracts in Oracle Contract Terms Management (also referred to as ETRM). In Oracle EBS 12.1.1 and 12.2.2, "history" objects such as this one support the Contracts Core versioning and audit framework, where each business change to a governance record generates a distinct historical row identified by a versioning key.

The view exposes the same column set as its underlying history table, prefixed with a ROW_ID column derived from GVEB.ROWID. This makes the view suitable for reporting, integration, and audit queries where the current or historical state of governance links between contract headers and contract lines must be examined. It does not implement the "current" filtering logic that some product views apply; rather, it surfaces the full set of historical rows available in the underlying table.

Underlying Base Objects

The documented base object for this view is the synonym OKC_GOVERNANCES_H, which resolves to the APPS-owned history table of the same name. The view is a simple projection: it selects all business columns from the base history table and adds a ROW_ID pseudo-column via GVEB.ROWID. Because the view is defined over a single table with no joins, it inherits no additional filtering, aggregation, or derivation logic.

The _HV naming convention denotes a history view, distinguishing it from the operational (non-history) views and tables in the OKC schema. Related base structures include the governance table itself and the contract header (OKC_K_HEADERS) and contract line (OKC_K_LINES) entities referenced through identifier columns.

Key Columns

• ROW_ID — The physical ROWID of the underlying history row, useful for direct row addressing.
• ID — The unique identifier of the governance record in the history table.
• MAJOR_VERSION — The version number of the governance record, supporting the OKC versioning model.
• DNZ_CHR_ID / ISA_AGREEMENT_ID — Identifiers linking the governance record to its associated contract/agreement context.
• OBJECT_VERSION_NUMBER — Optimistic locking token used by the framework for concurrency control.
• CHR_ID — Contract header identifier that owns the governance relationship.
• CLE_ID — Contract line identifier associated with the governance record.
• CHR_ID_REFERRED — The contract header identifier being referenced by the governance link.
• CLE_ID_REFERRED — The contract line identifier being referenced; this is the column most directly associated with the search term cle_id_referred.
• COPIED_ONLY_YN — Flag indicating whether the governance record was created only as a copy (e.g., during contract duplication).
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard EBS who-column auditing.

Common Use Cases and Queries

Typical usage involves auditing governance relationships between contracts and tracing which contract lines reference other contract lines across versions. A query filtered on the referred line identifier, for example, locates all governance records that point to a given contract line:

• SELECT ID, CHR_ID, CLE_ID, CHR_ID_REFERRED, CLE_ID_REFERRED, MAJOR_VERSION FROM APPS.OKC_GOVERNANCES_HV WHERE CLE_ID_REFERRED = :p_cle_id;
• SELECT * FROM APPS.OKC_GOVERNANCES_HV WHERE DNZ_CHR_ID = :p_chr_id ORDER BY MAJOR_VERSION;
• SELECT * FROM APPS.OKC_GOVERNANCES_HV WHERE COPIED_ONLY_YN = 'Y';

Such queries are useful in data reconciliation, historical reporting, and integration extracts where governance lineage must be preserved across contract versions. Because the view is a thin projection, standard EBS security and folder-based reporting tools can be applied without additional view-level filtering.