Results for “okc_ebiz_kheaders_v”

24 results




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

Overview

OKC_EBIZ_KHEADERS_V is a reporting and integration view owned by the APPS schema within the OKC — Contracts Core product of Oracle E-Business Suite. Its documented purpose is to serve as the "Find grid for eBusiness Integration," meaning it supplies the flattened, language-resolved contract header data that integration and inquiry screens consume when presenting a searchable list of contracts to end users or external systems. The view consolidates header-level contract attributes with their translated lookup meanings, textual descriptions, and operating unit names so that a single query returns a fully human-readable result set without requiring the caller to perform additional joins.

The object is defined as a VIEW with VALID status in both Oracle EBS 12.1.1 and 12.2.2. The column list is identical across releases, and the referenced base objects are consistently listed as synonyms over the underlying OKC and HR tables. Because it is a view rather than a table, it holds no data of its own and imposes no storage or index maintenance overhead; its cost is the join and function-call work required at query time.

Underlying Base Objects

The view is defined over the following documented base objects:

Every translated join carries a LANGUAGE = USERENV('LANG') predicate, so the view automatically returns descriptions, meanings, and organization names in the session's current language.

Key Columns

The view exposes the contract header identity and lifecycle in a single row per contract:

Common Use Cases and Queries

Typical usage includes building contract search grids, feeding integration extracts, and producing signed-contract reports. A representative query filtering on the searched column follows:

  • Contracts signed within a period: SELECT contract_number, date_signed, status_meaning, operating_unit FROM okc_ebiz_kheaders_v WHERE date_signed BETWEEN :p_from AND :p_to ORDER BY date_signed DESC;
  • Listing active contracts for an operating unit: SELECT contract_number, short_description, contract_amount, currency_code FROM okc_ebiz_kheaders_v WHERE operating_unit = :p_ou AND status_meaning = 'Active';
  • Verifying a user's access: SELECT contract_number, user_access_level FROM okc_ebiz_kheaders_v WHERE contract_id = :p_id;

Because USER_ACCESS_LEVEL is computed per row by OKC_UTIL, queries should be filtered as narrowly as possible to avoid excessive function invocations. All joins in the view are equijoins on the respective ID/CODE columns with language predicates, so results are deterministic for the session language. The view is read-only in practice and should be used for inquiry rather than DML.