Search Results okc_k_headers_v




Overview
Explore in AI Chat

Overview

OKC_K_HEADERS_V is an Oracle E-Business Suite view owned by the APPS schema within the OKC – Contracts Core product. It exposes contract header information by joining the base contract header entity table with its translation table, presenting a denormalized, reporting-friendly projection of the core contract header data. In Oracle EBS 12.1.1 and 12.2.2, the view carries a VALID status and is a documented, supported object for querying contracts core header details without the need to manually join the underlying _B and _TL tables or apply translation-language filtering logic. Its primary role is to support reporting, integration extracts, and lightweight programmatic access to contract header attributes, including contract number, status, dates, parties-related identifiers, and descriptive text.

Underlying Base Objects

According to the ETRM metadata, OKC_K_HEADERS_V is defined over the following documented objects:

The view text confirms this structure: every column is prefixed either CHRB (aliased to OKC_K_HEADERS_B) or CHRT (aliased to OKC_K_HEADERS_TL), demonstrating a direct B-to-TL join keyed on the contract header ID. These synonyms resolve to the actual OKC tables in the APPS schema.

Key Columns

The view exposes identity, status, classification, and descriptive attributes. Notable columns include:

Common Use Cases and Queries

Typical scenarios include contract register reporting, integration extracts into downstream systems, and data validation queries. A representative query retrieving active contract headers for a given operating unit:

  • SELECT contract_number, contract_number_modifier, sts_code, currency_code, start_date, end_date, short_description FROM okc_k_headers_v WHERE authoring_org_id = :p_org_id AND deleted_yn = 'N' AND archived_yn = 'N';
  • SELECT contract_number, buy_or_sell, estimated_amount, date_signed FROM okc_k_headers_v WHERE chr_type = :p_type AND date_signed BETWEEN :p_from AND :p_to;
  • SELECT id, document_id, template_yn, governing_contract_yn, scs_code FROM okc_k_headers_v WHERE template_yn = 'Y';

Because the view supplies translation text and the base attributes in a single projection, it is well suited for reporting layers and interfaces that must avoid duplicated B/TL join logic. Queries should always constrain by organization or status to limit cost, and consumers should treat ID and DOCUMENT_ID as the reliable keys for joins to contract lines and related entities.