Search Results oke_contract_header_id




Overview

APPS.PO_LINES_RELEASE_ITEMS_V is a supplementary view owned by the APPS schema in Oracle E-Business Suite, released under FND Design Data PO.PO_LINES_RELEASE_ITEMS_V. Its stated purpose is to simplify forms coding within the Purchasing module; Oracle explicitly warns that the view is not intended for direct query or data manipulation by customers, because its definition may change significantly across minor or major releases. In practice, the view presents purchasing document line and release information joined to item master and category attributes, giving a denormalized row per purchase order or release line. It is commonly encountered when reporting on committed amounts, negotiated pricing, and supplier-facing item details in the Procurement (PO) module on both EBS 12.1.1 and 12.2.2. The presence of the OKE_CONTRACT_HEADER_ID column links purchasing lines to Oracle Contracts (OKE) agreements, which is the reason this view surfaces in searches involving the term "oke_contract_header_id."

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is defined over the following objects, all referenced through APPS synonyms:

The dependency list also references APPS.FINANCIALS_SYSTEM_PA, indicating the view joins to financials system parameter data to resolve operating unit context for the returned lines.

Key Columns

Common Use Cases and Queries

Typical uses include reviewing committed versus negotiated pricing on purchase lines, tracing lines back to their originating contracts through OKE_CONTRACT_HEADER_ID, and building item-level procurement reports. Although Oracle advises against querying the view directly, developers and analysts frequently do so in a read-only, reporting context.

A representative query retrieving contract-linked purchase lines is:

SELECT line_num, item, item_description, unit_price,
       quantity_committed, committed_amount,
       oke_contract_header_id, expiration_date, org_id
FROM   apps.po_lines_release_items_v
WHERE  oke_contract_header_id IS NOT NULL
AND    org_id = :p_org_id;

A second query profiles pricing and commitment by category:

SELECT category, line_item, unit_price, committed_amount
FROM   apps.po_lines_release_items_v
WHERE  po_header_id = :p_po_header_id
ORDER BY line_num;

Because the view is subject to change and is documented as forms-only, production integrations should prefer the underlying PO_LINES, MTL_SYSTEM_ITEMS_KFV, and MTL_CATEGORIES_KFV objects when stable, supported interfaces are required.