Search Results po_line_num




Overview
Explore in AI Chat

Overview

The view APPS.PO_LINES_AP_V is a Purchasing (PO) module database object owned by the APPS schema and registered as VALID in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its documented description is explicitly stated as "10SC ONLY," indicating that the object was originally introduced to support a specialized or restricted deployment context rather than the general Purchasing data model. Despite that narrow origin, the view is exposed through the APPS schema and can be referenced by custom reports, concurrent programs, and integration interfaces that require a flattened, Accounts Payable-oriented projection of purchasing line data.

Functionally, PO_LINES_AP_V presents a denormalized join between purchase order headers and their corresponding lines, surfacing a small, curated column list suitable for reporting and downstream processing. It answers the common need to retrieve, for each purchasing line, the parent header attributes (vendor, approval status, currency) alongside line-level descriptive data (line number and item description). Because it is a view rather than a table, it carries no independent storage and always reflects current committed data in the underlying base tables.

Underlying Base Objects

The documented ETRM 12.2.2 metadata records two referenced base objects: PO_HEADERS_ALL (SYNONYM) and PO_LINES_ALL (SYNONYM). The view text confirms this relationship explicitly, joining PO_LINES PL to PO_HEADERS_ALL PH on the condition PL.PO_HEADER_ID = PH.PO_HEADER_ID. This is an inner join keyed on the purchase order header identifier.

Both underlyling objects are accessed through APPS-schema synonyms. PO_LINES_ALL stores the individual line records of a purchase order, while PO_HEADERS_ALL stores the header-level records that own those lines. The view therefore inherits the transactional integrity, multi-organization behavior, and access controls of those base tables. Any insert, update, or delete performed against the base tables is immediately visible through the view; the view itself is not updatable through the documented definition because it is a multi-table join.

Key Columns

  • PO_HEADER_ID — Foreign key to the purchase order header; the join key between the view's two source tables.
  • PO_LINE_ID — Unique identifier of the purchase order line; the primary line-level key.
  • VENDOR_ID — Supplier identifier sourced from the header, used to associate the line with a trading partner.
  • APPROVED_FLAG — Header-level approval status indicator; identifies whether the purchase order has been approved.
  • CURRENCY_CODE — Currency of the purchase order as recorded on the header.
  • PO_LINE_NUM — The user-visible line number (aliased from PL.LINE_NUM). This is the column most directly relevant to searches for "po_line_num" and is the human-readable line sequence within a purchase order.
  • ITEM_DESCRIPTION — Description of the item on the line (aliased from PL.ITEM_DESCRIPTION).
  • ORG_ID — Operating unit / organization identifier inherited from the line, supporting multi-org filtering.

Common Use Cases and Queries

The view is most commonly used where a lightweight, AP-facing extract of purchasing lines is required without exposing the full width of PO_LINES_ALL. Typical scenarios include reconciliation of approved purchase orders to payables, supplier-facing line listings, and custom reports filtered by operating unit. The following query retrieves line details for a specific purchase order, ordering by the visible line number:

SELECT po_header_id, po_line_id, po_line_num, item_description, vendor_id, approved_flag, currency_code, org_id
FROM apps.po_lines_ap_v
WHERE po_header_id = :p_header_id
ORDER BY po_line_num;

To list approved lines for a given operating unit and vendor, the view supports direct filtering on header-derived attributes:

SELECT vendor_id, po_header_id, po_line_num, item_description
FROM apps.po_lines_ap_v
WHERE org_id = :p_org_id
AND approved_flag = 'Y';

Because the definition is fixed and narrow, consumers requiring additional line attributes (item, quantity, price, uom) must join PO_LINES_ALL or PO_HEADERS_ALL directly rather than relying on this view. Given the "10SC ONLY" designation, implementers should confirm applicability to their specific EBS configuration before standardizing on it.