Results for “okl_cs_header_version_uv”

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

Overview

The OKL_CS_HEADER_VERSION_UV view is a reporting and integration object owned by the APPS schema within the OKL – Leasing and Finance Management product of Oracle E-Business Suite. Its documented purpose is to present a "List of Header Versions." In practice, the view exposes one row per processed contract header version, combining header-version identity, contract numbering, version dating, and lease term attributes into a single flattened structure. This makes it a convenient source for downstream reporting, integrations, and reconciliations that would otherwise require joining multiple TCA/OKC/OKL base tables manually.

The view sits in the contract authoring and versioning area of the OKL/OKC data model. Because Oracle retains historical header versions in the _BH (history) table, this view is typically used when a report or interface must surface the lifecycle of a contract rather than only its current active state. In the context of a search for okc_k_headers_bh, this view is directly relevant: OKC_K_HEADERS_BH is one of its three documented base objects, so OKL_CS_HEADER_VERSION_UV is a common way to access that history table without querying it directly.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over the following three base objects (all accessed through APPS synonyms):

• OKC_K_HEADERS_BH – the contract header history/version table, providing header identity, contract number, major version, and start/end dates.
• OKL_K_HEADERS_H – the leasing header history table, supplying lease-specific attributes such as term duration.
• OKL_TRX_CONTRACTS_ALL – the transactions table linking contracts to transaction records, used here to derive the version date.

The view joins these as follows: the leasing header history is matched to the contract header history on both ID and MAJOR_VERSION; the contract header history is then matched to the transaction record on KHR_ID. A filter restricts results to transactions where TSU_CODE = 'PROCESSED', and the SELECT DISTINCT clause eliminates duplicate rows introduced by the transaction join. The result is a deduplicated list of processed header versions. Notable view columns include CONTRACT_ID, CONTRACT_NUMBER, MAJOR_VERSION, VERSION_DATE, TERM_DURATION, START_DATE, and END_DATE.

Key Columns

• CONTRACT_ID – The internal identifier of the contract, corresponding to the header ID shared between the OKL and OKC header tables.
• CONTRACT_NUMBER – The user-facing contract number from the header history record.
• MAJOR_VERSION – The major version indicator of the header, distinguishing successive versions of the same contract.
• VERSION_DATE – The transaction date (truncated to day) on which the version was processed, derived from OKL_TRX_CONTRACTS_ALL.
• TERM_DURATION – The lease term duration taken from the leasing header history.
• START_DATE and END_DATE – The effective start and end dates of the header version.

Common Use Cases and Queries

Typical uses include auditing contract version history, extracting processed versions for downstream systems, and reconciling header versions against their associated transactions. Because the view already enforces the 'PROCESSED' transaction status, it is well suited to feeds that must exclude unprocessed or draft transactions.

A basic listing of versions for a given contract:

• SELECT contract_number, major_version, version_date, term_duration, start_date, end_date FROM okl_cs_header_version_uv WHERE contract_number = :p_contract_number ORDER BY major_version;
• SELECT contract_id, contract_number, major_version, version_date FROM okl_cs_header_version_uv WHERE version_date >= :p_from_date;

These queries return only processed header versions, reflecting the view's built-in filtering and its role as a read-only reporting layer over the OKC and OKL versioning tables.