Search Results po_lines_all




Overview
Explore in AI Chat

Overview

The view ITG_CPO_PO_LINES_V is an APPS-owned, valid database view registered within the ITG — Internet Procurement Enterprise Connector product module in Oracle E-Business Suite. As its description states, it is a "simple view of PO_LINES_ALL table," meaning it provides a deliberately narrowed, integration-oriented projection of the purchasing line entity rather than a full relational presentation. The view is designed to expose purchase order line data to external or internal procurement integration flows — notably the Internet Procurement Enterprise Connector, which historically acts as a bridge between Oracle EBS Purchasing and external procurement platforms or punch-out/requisition systems.

Because the view restricts its output to three columns, its role is not general-purpose reporting but targeted data exchange. Consumers of this view receive only the identifiers needed to correlate a purchase order line with its parent header and its human-readable line number. This makes it suitable for lightweight lookups, key resolution, and integration handoffs where the entire breadth of PO_LINES_ALL would be unnecessary or undesirable.

Underlying Base Objects

The documented base object referenced by this view is the synonym PO_LINES_ALL, which resolves to the core Purchasing table APPS.PO_LINES_ALL. The view is a straight, unfiltered selection — its view text is:

There are no joins, no WHERE predicates, no unions, and no aggregation. Consequently, the view returns exactly one row per row in PO_LINES_ALL, preserving the base table's cardinality. The only transformation applied is a column alias: LINE_NUM is exposed as POLINENUM. This aliasing aligns the output with the naming conventions expected by the consuming ITG integration interface.

Key Columns

The view exposes three columns, each carrying a specific meaning within the Purchasing data model:

  • PO_LINE_ID — The unique system-generated primary key for the purchase order line. This is the join key used to link to other line-level tables such as PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, and PO_ATTRIBUTE_VALUES.
  • PO_HEADER_ID — The foreign key identifying the parent purchase order header in PO_HEADERS_ALL. It enables the line to be correlated to its owning document.
  • POLINENUM — The alias of LINE_NUM, representing the line's ordinal position within the purchase order as visible to users. It is the display-facing line number rather than a surrogate key.

Common Use Cases and Queries

The view is most valuable when an integration must retrieve line identifiers and line numbers without incurring the overhead of selecting from PO_LINES_ALL directly. Typical scenarios include reconciling externally created PO lines back to their EBS counterparts, or supplying minimal reference data to the ITG connector.

A representative query retrieving all lines for a given header:

  • SELECT po_line_id, po_header_id, polinenum FROM apps.itg_cpo_po_lines_v WHERE po_header_id = :p_header_id ORDER BY polinenum;

Joining to the header for document context:

  • SELECT v.polinenum, h.segment1, v.po_line_id FROM apps.itg_cpo_po_lines_v v, apps.po_headers_all h WHERE v.po_header_id = h.po_header_id AND h.segment1 = :p_po_number;

Because the view is unfiltered over PO_LINES_ALL, queries should always constrain on PO_HEADER_ID, PO_LINE_ID, or join to a header to avoid full-table scans. It should be treated strictly as an integration interface, with comprehensive purchasing line attributes retrieved from the base table when required.