Search Results po_lines_all_v




Overview
Explore in AI Chat

Overview

PO_LINES_ALL_V is an Oracle E-Business Suite view owned by the APPS schema and registered as VALID in the ETRM repository. It belongs to the PO - Purchasing product family and is classified in the ETRM documentation under the description "10SC ONLY," indicating that its documented scope is restricted to a specific implementation or configuration context rather than being a general-purpose object across all releases. The view presents purchase order line information enriched with inventory item concatenated segment values, exposing a denormalized, reporting-friendly projection of PO line data alongside flexfield key flexfield segments from the item master.

Functionally, PO_LINES_ALL_V serves as a lightweight read layer for reporting and integration scenarios in Oracle EBS 12.1.1 and 12.2.2. Rather than requiring report authors to join PO_LINES to MTL_SYSTEM_ITEMS_KFV and resolve organization context manually, the view encapsulates that join logic. Its role is therefore primarily analytical and interface-oriented, giving downstream queries a single object from which line number, item identity, item description, unit of measure, and header/line keys can be retrieved together.

Underlying Base Objects

The documented ETRM metadata identifies three referenced base objects, each exposed through a synonym in the APPS schema: FINANCIALS_SYSTEM_PARAMS_ALL, MTL_SYSTEM_ITEMS_KFV, and PO_LINES. The view definition joins these objects as follows:

  • PO_LINES POL is the driving table, supplying line-level purchase order attributes such as LINE_NUM, ITEM_ID, ITEM_REVISION, UNIT_MEAS_LOOKUP_CODE, ITEM_DESCRIPTION, PO_HEADER_ID, PO_LINE_ID, and ORG_ID.
  • MTL_SYSTEM_ITEMS_KFV MIS is joined with an outer join (POL.ITEM_ID = MIS.INVENTORY_ITEM_ID (+)) to retrieve the CONCATENATED_SEGMENTS key flexfield value for the item. The outer join ensures lines that reference no inventory item, or items not defined in the item master, are still returned.
  • FINANCIALS_SYSTEM_PARAMS_ALL FSP is used to resolve the operating unit's inventory organization. The predicate NVL(MIS.ORGANIZATION_ID, FSP.INVENTORY_ORGANIZATION_ID) = FSP.INVENTORY_ORGANIZATION_ID forces item resolution against the inventory organization defined for the operating unit, and FSP.ORG_ID = POL.ORG_ID links system parameters to the line's operating unit.

This three-table structure means the view is organization-aware through FINANCIALS_SYSTEM_PARAMS_ALL rather than through a multi-org view clause on the item master. Consequently, the row returned for an item reflects the concatenated segments valid in the inventory organization configured for that line's operating unit.

Key Columns

The view exposes nine columns, each documented in the ETRM metadata:

  • LINE_NUM — the purchase order line number, sourced from PO_LINES.
  • CONCATENATED_SEGMENTS — the item key flexfield concatenated segments from MTL_SYSTEM_ITEMS_KFV, providing the human-readable item identifier.
  • ITEM_REVISION — the revision of the item on the line.
  • ITEM_ID — the inventory item identifier used for the join to the item master.
  • UNIT_MEAS_LOOKUP_CODE — the unit of measure lookup code for the line quantity.
  • ITEM_DESCRIPTION — the description of the item as recorded on the purchase order line.
  • PO_HEADER_ID — foreign key to the purchase order header, enabling linkage to PO_HEADERS_ALL.
  • PO_LINE_ID — the unique identifier of the purchase order line, the primary joining key to distributions and other line-level child records.
  • ORG_ID — the operating unit identifier from the line, used in multi-org filtering.

Common Use Cases and Queries

Typical usage centers on procurement reporting and interface extraction where item flexfield segment values are required next to PO line detail. A representative query filtering by operating unit and header is:

  • SELECT line_num, concatenated_segments, item_description, unit_meas_lookup_code, po_line_id FROM apps.po_lines_all_v WHERE org_id = :org_id AND po_header_id = :header_id ORDER BY line_num;
  • Joining to PO_HEADERS_ALL on PO_HEADER_ID to obtain supplier, document number, and status for a consolidated line-level report.
  • Feeding interface or staging tables where the item's concatenated segments must accompany each line for downstream validation or validation against the item master.

Because the view resolves item segments through FINANCIALS_SYSTEM_PARAMS_ALL, queries should always constrain ORG_ID to the intended operating unit; omitting that predicate can produce cross-operating-unit results or ambiguous item resolution. Given the "10SC ONLY" classification, implementers should confirm whether the view is deployed and relied upon in their specific instance before building dependencies on it, and should treat the base tables PO_LINES and MTL_SYSTEM_ITEMS_KFV as the authoritative sources where full column coverage is needed.