Results for “okc_k_headers_all_v”

50+ results




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

Overview

OKC_K_HEADERS_ALL_V is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2, delivered as part of the OKC – Contracts Core (Oracle Contracts / Enterprise Contracts) product family. The view exposes the header-level attributes of contract documents stored in the Contracts repository, consolidating the language-independent columns of the base header table with the language-dependent descriptive columns held in the translation table. Its object status is VALID in the ETRM metadata, indicating that the underlying definition has compiled successfully and is queryable in a standard installation.

The view functions as the principal reporting and integration surface for contract headers. Because it joins the base and translation layers, it returns exactly one row per contract header per installed language (the language determined by the session's NLS environment), and it presents both transactional control fields — status, dates, currency, amounts — and descriptive fields such as short description, cog-nomen, and comments. Application forms, concurrent programs, and customer-developed extracts that reference contract header information commonly target this view rather than the underlying tables, since the view encapsulates the mandatory translation join and guarantees the ROWID-based identity of the base row through the ROW_ID column.

Underlying Base Objects

The view is defined over three documented objects:

The aliases CHRB and CHRT in the view text correspond to the base and translation sources respectively. Columns prefixed by CHRB are drawn from OKC_K_HEADERS_ALL_B; columns prefixed by CHRT are drawn from OKC_K_HEADERS_TL. The view does not itself store data; all rows are resolved at query time from these objects.

Key Columns

Common Use Cases and Queries

Typical usages include contract repositories and dashboards, validation and reconciliation reports, and integration extracts that feed downstream systems with contract master data.

  • Active contract listing.

    SELECT contract_number, short_description, sts_code, start_date, end_date FROM okc_k_headers_all_v WHERE deleted_yn = 'N';

  • Contract header by number.

    SELECT id, contract_number, contract_number_modifier, currency_code, estimated_amount FROM okc_k_headers_all_v WHERE contract_number = :p_contract_number;

  • Expiring contracts.

    SELECT contract_number, end_date FROM okc_k_headers_all_v WHERE end_date BETWEEN SYSDATE AND SYSDATE + 90 AND deleted_yn = 'N' ORDER BY end_date;

  • Join to lines. The ID column is used to correlate headers with OKC_K_LINES_ALL_V or the base line tables for contract-level detail reporting.

Because the view reads from the translation table, queries should always run under the intended NLS language setting to obtain the correct descriptive text.