Search Results oke_k_headers_v




Overview
Explore in AI Chat

Overview

OKE_K_HEADERS_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, classified under the OKE – Project Contracts product family. It presents consolidated contract header information, combining columns drawn from the core contract header table, its translation table, and the Project Contracts extension table. The view is reported as VALID in both EBS 12.1.1 and 12.2.2, and its definition is consistent across those releases.

The view functions as a reporting and integration surface for contract header data. Because it flattens the multilingual header record, the descriptive attribute table, and the OKE-specific extension columns into a single row per contract, it allows reporting tools, concurrent programs, custom forms, and external interfaces to retrieve contract metadata without joining the underlying base tables explicitly. The presence of ROWID and OBJECT_VERSION_NUMBER in the SELECT list also makes the view usable in contexts where row identity and optimistic locking semantics are required.

Underlying Base Objects

The ETRM metadata documents four referenced base objects, all exposed to the view through APPS synonyms:

  • OKC_K_HEADERS_ALL_B – the base contract header table, supplying operational contract attributes such as CONTRACT_NUMBER, dates, status codes, currency, and template indicators.
  • OKC_K_HEADERS_TL – the translation table, supplying language-dependent descriptive fields such as COGNOMEN, SHORT_DESCRIPTION, DESCRIPTION, and COMMENTS.
  • OKE_K_HEADERS – the Project Contracts extension table, supplying OKE-specific attributes including Prime K numbers, award and authorization dates, compliance flags, and financial control fields.
  • PA_TASKS – referenced in the documented dependency list, consistent with the OKE product's integration with Oracle Projects structures.

The view text confirms aliases CH for the header table, CHT for the translation table, and EH for the extension attribute table. Columns such as K_HEADER_ID, K_TYPE_CODE, and PRODUCT_LINE_CODE originate from the extension, while core identifiers and status fields originate from the base header, and descriptive text originates from the translation table.

Key Columns

Common Use Cases and Queries

Typical uses include contract header reports, data extraction for interfaces, and validation queries during implementation. The view is convenient where a single-row, denormalized representation of the contract header is required.

Listing active, booked contracts for an operating unit:

  • SELECT K_HEADER_ID, CONTRACT_NUMBER, COGNOMEN, START_DATE, END_DATE, ESTIMATED_AMOUNT FROM APPS.OKE_K_HEADERS_V WHERE BUY_OR_SELL = 'S' AND BOOKED_FLAG = 'Y' AND STS_CODE = 'ACTIVE';

Retrieving a specific contract by number:

  • SELECT K_HEADER_ID, CONTRACT_NUMBER, K_TYPE_CODE, CURRENCY_CODE, SIGN_DATE, AUTHORIZE_DATE FROM APPS.OKE_K_HEADERS_V WHERE CONTRACT_NUMBER = :contract_number;

Joining to project structures for task-level reporting:

  • SELECT h.CONTRACT_NUMBER, h.PROJECT_ID, t.TASK_NUMBER FROM APPS.OKE_K_HEADERS_V h, APPS.PA_TASKS t WHERE h.PROJECT_ID = t.PROJECT_ID;

Because the view is defined over base tables with no documented aggregation or DISTINCT, its performance characteristics follow those of the underlying header, translation, and extension tables; queries should filter on indexed columns such as K_HEADER_ID or CONTRACT_NUMBER.