Results for “chg_request_num”

50+ results




Overview
Explore in AI Chat

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

Overview

The APPS.OKE_K_HISTORY_ORGNZR_V view is a reporting construct within the Oracle E-Business Suite Project Contracts (OKE) module. It presents contract header version history in a form suitable for display within an Organizer (folder-style) window or for query-driven reporting. The view consolidates version numbering data from the contract header version table and enriches it with descriptive lookup meanings and change-request identifiers, allowing users and integrations to see not only which version of a contract header exists but also why that version was created and whether a change request drove it.

Because contract versioning in OKE captures a dated audit trail of header modifications, this view functions as a convenient, pre-joined read model. Rather than forcing a report author to join the version history table, the FND lookup framework, and the change request table manually, the view delivers those relationships in a single object. It is defined with STATUS = VALID in the ETRM 12.2.2 documentation and is deployed in the APPS schema, which is the conventional location for seeded, end-user-facing database objects. The presence of VERSION_REASON_CODE as a documented column is significant: that column answers the exact search term of interest (version_reason_code), which classifies each historical contract header version by its originating reason.

Underlying Base Objects

The view text joins three objects:

The join to the lookup values is an inner join, enforcing that every returned row has a defined reason code. The join to OKE_CHG_REQUESTS is an outer join (CR.CHG_REQUEST_ID (+) = VH.CHG_REQUEST_ID), so versions without an associated change request are still reported, with CHG_REQUEST_NUM left null.

Key Columns

  • K_HEADER_ID — foreign key identifying the contract header whose history is being reported.
  • MAJOR_VERSION — the sequential version number of the contract header.
  • VERSION_DATE — the effective date of the version; note the view select list maps CREATION_DATE a second time into this position, so VERSION_DATE reflects the row creation timestamp of the version record.
  • VERSION_REASON_CODE — the lookup code describing why the version was generated.
  • VERSION_REASON — the translated MEANING of that code from FND_LOOKUP_VALUES_VL.
  • CHG_REQUEST_ID / CHG_REQUEST_NUM — the change request that generated the version, present only when applicable.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN for traceability.

Common Use Cases and Queries

Typical uses include displaying contract version history in an Organizer window, auditing why a contract header changed, and tracing versions back to change requests. A representative query returns the full history for one contract header:

SELECT major_version, version_date, version_reason_code, version_reason, chg_request_num
FROM apps.oke_k_history_orgnzr_v
WHERE k_header_id = :p_header_id
ORDER BY major_version;

A second pattern profiles version activity by reason across a portfolio:

SELECT version_reason_code, version_reason, COUNT(*) version_count
FROM apps.oke_k_history_orgnzr_v
GROUP BY version_reason_code, version_reason
ORDER BY version_count DESC;

A third joins the view to contract header data to link versions to specific agreements, filtering on CHG_REQUEST_NUM where change-request traceability is required. Because the object is a view, it should be queried read-only; the underlying history tables remain the system of record.