Search Results oke_k_vers_numbers_h_pk

Overview

The OKE_K_VERS_NUMBERS_H table is a core data object within the Oracle E-Business Suite Project Contracts (OKE) module. It serves as the central repository for storing versioning information for contract headers. In the context of contract management, a single contract can undergo multiple revisions or amendments throughout its lifecycle. This table systematically tracks each major version of a contract, enabling a complete audit trail and historical analysis. Its role is critical for maintaining data integrity, supporting change management processes, and facilitating reporting on contract evolution across versions 12.1.1 and 12.2.2 of Oracle EBS.

Key Information Stored

The table's structure is designed to uniquely identify and describe each contract version. The primary key is a composite of K_HEADER_ID and MAJOR_VERSION, which together enforce uniqueness for each version record of a specific contract. The K_HEADER_ID column is a foreign key that links the version record back to its master contract definition in the OKE_K_HEADERS table. The MAJOR_VERSION column stores the sequential version number (e.g., 1, 2, 3). A significant column is CHG_REQUEST_ID, which is a foreign key to the OKE_CHG_REQUESTS table. This relationship explicitly ties a contract version to the formal change request that authorized its creation, providing a direct link between the change control and versioning processes within Project Contracts.

Common Use Cases and Queries

A primary use case is generating a version history report for a specific contract. This is essential for auditors and contract administrators to understand the sequence of changes. A typical query would join OKE_K_VERS_NUMBERS_H with OKE_K_HEADERS to retrieve contract details and list all versions in descending order. Another critical scenario involves impact analysis for a change request; users can query which contract versions were generated as a result of a specific CHG_REQUEST_ID. For performance and data integrity reporting, a common pattern is to identify contracts with an unusually high number of versions, which may indicate a volatile agreement or potential process issues.

• Retrieve Version History: SELECT k_header_id, major_version FROM oke_k_vers_numbers_h WHERE k_header_id = :p_contract_id ORDER BY major_version DESC;
• Link Version to Change Request: SELECT v.*, c.request_number FROM oke_k_vers_numbers_h v, oke_chg_requests c WHERE v.chg_request_id = c.chg_request_id AND v.k_header_id = :p_contract_id;

Related Objects

The OKE_K_VERS_NUMBERS_H table maintains defined foreign key relationships with other central tables in the Project Contracts schema, as documented in the ETRM metadata.

• OKE_K_HEADERS: This is the master contract header table. The relationship is established via the column OKE_K_VERS_NUMBERS_H.K_HEADER_ID, which references OKE_K_HEADERS. Every version record must belong to a valid contract header.
• OKE_CHG_REQUESTS: This table manages the formal change request process. The relationship is defined through the column OKE_K_VERS_NUMBERS_H.CHG_REQUEST_ID, which references OKE_CHG_REQUESTS (noted twice in the metadata, likely indicating the same column can be joined). This links a contract version to its originating change authorization.

The primary key constraint OKE_K_VERS_NUMBERS_H_PK ensures data uniqueness and is likely referenced by other dependent objects or child tables not explicitly listed in the provided excerpt.