Search Results oke_k_vers_numbers_v




Overview
Explore in AI Chat

Overview

The OKE_K_VERS_NUMBERS_V view is an Oracle Applications (APPS) database object that belongs to the OKE – Project Contracts product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented as the "Contract Version Number View" and carries a VALID status in the ETRM metadata. Its purpose is to expose version-numbering attributes associated with contract records so that reporting, extensions, and integration components can consume a presentation-ready projection of the underlying version data rather than querying the base entity directly.

Because the view is defined over a contract version basis table, it participates in the contracts data model that supports version-controlled contract authoring. Each contract version is distinguished by a major and minor version pair, and the view provides the increment logic required to render the effective version number. This makes it suitable for display in concurrent programs, Oracle Reports, OAF pages, and custom SQL used by implementation teams.

Underlying Base Objects

According to the documented metadata, the view references a single base object: OKC_K_VERS_NUMBERS, which is exposed to the APPS schema as a SYNONYM. The view body selects from this table and applies a calculated transformation to one of the version columns, specifically presenting MAJOR_VERSION + 1 under the MAJOR_VERSION column name. All other columns are passed through unchanged, including the ROWID pseudo-column and the standard Who columns used across EBS tables.

The relationship is therefore a straightforward one-to-one projection: one row in OKC_K_VERS_NUMBERS yields one row in OKE_K_VERS_NUMBERS_V. No joins, unions, or aggregations are present in the documented view text, which means the view is best understood as a convenience layer for version numbering rather than a consolidated or denormalized reporting structure.

Key Columns

  • ROW_ID – The physical row identifier (ROWID) of the underlying base row.
  • CHR_ID – The contract header identifier linking the version record to its parent contract.
  • OBJECT_VERSION_NUMBER – The optimistic locking version number used for concurrent update control in the EBS framework.
  • MAJOR_VERSION – Exposed as the stored major version incremented by one, reflecting the effective contract version number presented to users.
  • MINOR_VERSION – The minor version component of the contract version pair.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS audit (Who) columns recording creation and last modification details.
  • SECURITY_GROUP_ID – The security group identifier supporting multi-org and data partitioning behavior.

Common Use Cases and Queries

Typical use cases include retrieving the current or next contract version number for a given contract header, building version history reports, and validating version sequences during data migration or integration testing. The following example lists version numbers for a specific contract:

SELECT chr_id,
       major_version,
       minor_version
FROM   apps.oke_k_vers_numbers_v
WHERE  chr_id = :p_contract_id
ORDER  BY major_version, minor_version;

A second common pattern joins the view to contract header data to present a human-readable version label alongside the contract name, and a third uses the view to reconcile the maximum version stored against the incremented major version to detect sequencing gaps. Because the view exposes ROWID and OBJECT_VERSION_NUMBER, it is also used defensively in extensions that must respect optimistic locking semantics. Wherever the delivered ETRM UI presents a contract version number, this view is the logical source for reproducing that value in custom reporting.