Search Results okc_k_vers_numbers_v




Overview
Explore in AI Chat

Overview

OKC_K_VERS_NUMBERS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, belonging to the OKC (Contracts Core) product family. As documented in the ETRM metadata for release 12.2.2 (and equally applicable to 12.1.1), the view is described simply as a "View for table OKC_K_VERS_NUMBERS." It exposes the version numbering attributes maintained against a contract or contract line (the CHR_ID), together with standard Oracle EBS Who columns. The view is not a transactional form object; rather it is a reporting and integration convenience layer that presents the version-number records in a stable, queryable shape for SQL*Plus, BI Publisher, OAF-based custom pages, and inbound/outbound interfaces that need to read contract version metadata without depending on the physical table name.

Underlying Base Objects

Per the documented metadata, the view is defined over a single base object: the table OKC_K_VERS_NUMBERS, which is referenced through a SYNONYM. The view text confirms this one-to-one relationship:

The alias CVMB is applied to OKC_K_VERS_NUMBERS, and the view performs no join, aggregation, or filter. It is therefore a straightforward projection: every row in the base table is surfaced through the view with the same cardinality. Because the view is a simple SELECT, it remains updatable in principle for the base columns, although OKC functionality is expected to be exercised through the Contracts application rather than direct DML.

Key Columns

The documented column list comprises ten columns, mapped directly from the base table:

  • ROW_ID — the ROWID of the underlying OKC_K_VERS_NUMBERS row; useful for de-duplication, debugging, and rapid lookups.
  • CHR_ID — the identifier of the contract header/line to which the version-number record belongs; the primary join key to other OKC contract objects.
  • OBJECT_VERSION_NUMBER — the OAF/ADF optimistic locking token, incremented on each update to detect concurrent modification.
  • MAJOR_VERSION — the major version counter for the contract document.
  • MINOR_VERSION — the minor version counter, subordinate to the major version.
  • CREATED_BY, CREATION_DATE — audit columns recording the user and timestamp of row creation.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit columns recording the most recent modification user, timestamp, and login session.

Collectively these columns allow reporting on how many versions a contract has, when they were created or last revised, and by whom.

Common Use Cases and Queries

The view is typically used when reporting on or integrating with contract versioning activity. A common pattern joins the view to contract header information via CHR_ID.

  • Listing versions for a specific contract:
    SELECT chr_id, major_version, minor_version, creation_date, last_updated_by
    FROM okc_k_vers_numbers_v
    WHERE chr_id = :p_chr_id
    ORDER BY major_version, minor_version;
  • Auditing recent version-number changes in a period:
    SELECT chr_id, major_version, minor_version, last_updated_by, last_update_date
    FROM okc_k_vers_numbers_v
    WHERE last_update_date >= TRUNC(SYSDATE) - 7;
  • Extracting distinct version counts per contract for a dashboard:
    SELECT chr_id, COUNT(*) version_rows, MAX(major_version) max_major
    FROM okc_k_vers_numbers_v
    GROUP BY chr_id;

Because the view simply wraps OKC_K_VERS_NUMBERS, its use is appropriate wherever the base table would be queried, while honoring the APPS schema and the documented ETRM object name recommended for supported reporting.