Search Results unordered_flag




Overview
Explore in AI Chat

Overview

The OKX_PO_LINES_V view is a Contracts Integration object shipped within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 technical reference model (ETRM). It exposes purchase order line attributes in a normalized, single-row-per-line format suitable for integration and reporting workflows that bridge Oracle Purchasing and Oracle Contracts. The view is documented in the OKX - Contracts Integration product module, which handles the movement of contract and sourcing data between the purchasing and contracting schemas.

The view projects a consistent set of PO line columns so that downstream consumers — interfaces, concurrent programs, and custom reports — can query purchase order line details without joining the full PO_LINES_ALL table and its related lookup structures. It also supplies the standard Name/Description header columns (here both NULL) to satisfy a generic integration contract that expects a uniform column layout across the OKX family of views.

Per the ETRM metadata, the view is not physically implemented in the reference database; the definition is supplied for documentation purposes only. The identifier columns ID1 and ID2 are returned as PO_LINE_ID and the literal '#' respectively.

Underlying Base Objects

The view is defined over a single base table:

  • PO_LINES_ALL — aliased as POL, this is the multi-organization base table storing purchase order line records in Oracle Purchasing. Every column exposed by OKX_PO_LINES_V maps directly to a column on PO_LINES_ALL with no join, aggregation, or expression.

Because the view selects directly from PO_LINES_ALL, its row count and filter behavior mirror the underlying table. The metadata lists "none documented" for referenced base objects beyond this direct reference. No other tables, views, or synonyms are involved in the definition.

Key Columns

Common Use Cases and Queries

This view is typically used to extract purchase order line data for contract integration, hold analysis, and status reporting. A typical query isolating lines under a user hold would resemble:

  • SELECT PO_HEADER_ID, PO_LINE_ID, LINE_NUM, ITEM_DESCRIPTION, USER_HOLD_FLAG FROM OKX_PO_LINES_V WHERE USER_HOLD_FLAG = 'Y';

Other practical uses include auditing closed and cancelled lines by date range, extracting unit price and quantity for contract value reconciliation, and driving interface programs that populate contract repositories. Because the view is not implemented in the reference database, organizations must confirm the view exists in their environment before relying on it for integration queries.