Results for “oke_k_headers_lov_v”

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

Overview

OKE_K_HEADERS_LOV_V is an Oracle E-Business Suite view owned by the APPS schema within the OKE – Project Contracts product family. It is a lightweight, list-of-values (LOV) oriented view whose purpose is to expose the identifying attributes of contract headers in a compact form suitable for use as a value list source in Oracle Forms, OAF pages, and concurrent reporting. The view centers on the K number, which is the user-facing contract number assigned to a Project Contracts header record (the "K" designation derives from the historical Oracle Contracts terminology). The user search term "k_number" maps directly to the CONTRACT_NUMBER and K_NUMBER columns defined on this object, confirming that this view is the primary lookup surface for retrieving contract numbers and their identifiers.

The view is documented as VALID and presents the K number, its display representation, the underlying primary key, and a short description. Because it filters only to header-level information and omits line, party, and financial detail, it is well suited to populating LOV windows and to joining against transactional tables where the contract number is required as a descriptor.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, OKE_K_HEADERS_LOV_V is defined over a single referenced base object: OKE_K_HEADERS_V (VIEW). The view text is a straightforward projection:

• SELECT EH.K_HEADER_ID
• EH.K_NUMBER_DISP
• EH.K_HEADER_ID
• EH.K_NUMBER_DISP
• EH.SHORT_DESCRIPTION
• FROM OKE_K_HEADERS_V EH

Notably, the base object is itself a view rather than a table. This nesting means OKE_K_HEADERS_V carries the security and business-rule logic (such as organization or operating unit filtering, and derived display formatting for the K number), while OKE_K_HEADERS_LOV_V simply reshapes and renames that output for LOV consumption. No direct base table is documented for this object in the provided metadata; the physical tables (OE_ORDER_HEADERS_ALL and related contract tables in the OKE schema) are abstracted behind OKE_K_HEADERS_V.

Key Columns

• K_HEADER_ID — The unique primary key of the contract header. This is the join key used to relate the LOV selection back to OKE header tables. It is exposed twice in the projection, an artifact of the view definition.
• K_NUMBER — The contract number attribute listed in the documented column set. This is the value users typically search on when entering "k_number".
• K_NUMBER_DISP — The display-formatted version of the contract number, used for presentation in LOV lists. It may differ from the raw K_NUMBER via concatenation or formatting.
• CONTRACT_NUMBER — The documented column alias representing the contract identifier as presented to the end user; functionally aligned with the K number semantics.
• SHORT_DESCRIPTION — A brief textual description of the contract, included to give users context when selecting from the list of values.

Common Use Cases and Queries

The primary use case is as an LOV source: a form or page field binds to K_HEADER_ID while displaying K_NUMBER_DISP, allowing users to search by contract number and store the numeric identifier. A typical query is:

• SELECT k_header_id, k_number_disp, short_description FROM apps.oke_k_headers_lov_v WHERE k_number_disp LIKE :search_term;
• SELECT k_header_id, contract_number, short_description FROM apps.oke_k_headers_lov_v ORDER BY contract_number;
• SELECT l.k_header_id, l.k_number_disp FROM apps.oke_k_headers_lov_v l, apps.oke_headers_all h WHERE l.k_header_id = h.k_header_id;

Secondary use cases include validation routines that confirm a user-entered contract number exists, and lightweight reporting that requires only header-level contract identification. Because the view derives from a secured base view, query results are automatically constrained by the same access rules, making it safe for use in both interactive and batch contexts without additional filtering.