Results for “oke_k_vers_numbers_h”

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

Overview

OKE_K_VERS_NUMBERS_H is a Project Contracts (OKE) module table that stores version information for contract and project deliverable records. In Oracle E-Business Suite 12.1.1 and 12.2.2, the OKE schema underpins the Project Contracts application, which manages customer contracts, funding, deliverables, and billing relationships tied to Oracle Projects. This table acts as the version registry for contract header records, tracking major version numbers and the change request context that produced each version.

Because it records the association between a contract header and its change request lineage, the table is best understood as a link-style object under a Data Vault classification heuristic. That is a modeling suggestion rather than an Oracle-imposed constraint: structurally, it connects a contract header (K_HEADER_ID) to the change control workflow (CHG_REQUEST_ID) and captures which major version resulted from the change.

Key Information Stored

The table contains nine documented columns. The most significant include:

• K_HEADER_ID — Foreign key to OKE_K_HEADERS, identifying the contract or deliverable header whose version is being tracked. Part of the composite primary key.
• MAJOR_VERSION — Sequence number identifying a specific major version of the header. Together with K_HEADER_ID, this forms the primary key (OKE_K_VERS_NUMBERS_H_PK) and the unique index OKE_K_VERS_NUMBERS_H_U1, making it the business-key candidate.
• VERSION_REASON_CODE — Lookup code describing why the version was created (for example, a change order or renewal).
• CHG_REQUEST_ID — Foreign key to OKE_CHG_REQUESTS linking the version to the change request that triggered it.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording when and by whom the version record was created and last modified.

There is no separate surrogate identifier; the composite (K_HEADER_ID, MAJOR_VERSION) serves as the primary key, and the unique index reinforces that no two rows can exist for the same contract header at the same major version.

Common Use Cases and Queries

Typical scenarios include tracking contract version history, auditing how many versions a contract has accumulated, and tracing each version back to its originating change request. A representative query lists versions for a contract header:

• SELECT k_header_id, major_version, version_reason_code, chg_request_id FROM oke.oke_k_vers_numbers_h WHERE k_header_id = :header_id ORDER BY major_version DESC;

Reporting use cases include version-count reporting by contract, change-impact analysis joining to OKE_CHG_REQUESTS, and reconciliation of contract revisions during billing or revenue recognition. Because the table is primarily a history/version registry, it is also useful in data migration and archival routines.

Related Objects

• OKE_K_HEADERS — Parent table; joined on K_HEADER_ID, holds the contract/deliverable header.
• OKE_CHG_REQUESTS — Change request table; joined on CHG_REQUEST_ID to identify what triggered each version.
• OKE_DELIVERABLES and related entity tables — downstream consumers of contract header versions.
• Project Contracts forms and APIs that create and query version records.

Because the object is a link between header and change request, the two FK paths (to OKE_K_HEADERS and OKE_CHG_REQUESTS) are the primary join routes for any query or integration involving this table.