Search Results cancel_reason




Overview
Explore in AI Chat

Overview

APPS.PO_LINES_PRINT is a reporting-oriented database view in the Oracle E-Business Suite Purchasing (PO) module. Its name and structure indicate that it was designed to supply the data set consumed by the standard Purchase Order Print program (and related document-printing utilities) that render purchasable document lines for output. The view consolidates header-level, line-level, and reference-table attributes into a single denormalized result set, so that a printing or reporting process does not need to traverse the full normalized purchasing schema itself.

The ETRM metadata records the object as VALID with owner APPS, and describes it tersely as "Retrofitted," a designation commonly applied to objects that were re-pointed or re-created during an upgrade or patch cycle. The view is relevant in both 12.1.1 and 12.2.2, where the underlying purchasing tables remain largely compatible. Its principal value lies in shielding callers from the complexity of joining PO_LINES, PO_HEADERS_ALL, and PO_LINE_TYPES while still exposing the descriptive, quantity, pricing, and hazard information required on a printed order.

Underlying Base Objects

The documented base objects for the view are MTL_UNITS_OF_MEASURE, PO_HAZARD_CLASSES, PO_HEADERS_ALL, PO_LINES, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_LINE_TYPES, PO_RELEASES_ALL, and PO_UN_NUMBERS. These are referenced through public synonyms in the APPS schema.

The view text confirms that the core driving table is PO_LINES (PL1), joined to PO_HEADERS_ALL (PH1, PH2), PO_LINES_ALL (PL2), and PO_LINE_TYPES (PLT) on their respective identifiers. Reference lookups are resolved through MTL_UNITS_OF_MEASURE (MUM) for unit-of-measure descriptions, PO_UN_NUMBERS (PUN) for United Nations hazard identification, and PO_HAZARD_CLASSES (PHC) for hazard class. The presence of PO_LINE_LOCATIONS_ALL and PO_RELEASES_ALL in the documented dependency list reflects the broader join graph used for shipment- and release-level sourcing, even where the excerpted text does not show those predicates explicitly.

Key Columns

The view exposes a broad mix of descriptive and computational columns. Notable ones include:

Common Use Cases and Queries

The view is most often queried where a report or custom print layout needs purchasing line data without re-implementing the standard join logic. A query to retrieve print detail for a specific order would resemble:

SELECT line_num, item_description, unit_price, quantity, unit_meas_lookup_code
FROM apps.po_lines_print
WHERE po_header_id = :p_header_id
ORDER BY line_num;

Because the user search term was from_line_id, a frequent second use case is tracing a line back to its originating document line — for example, linking a release line to the blanket agreement line it consumes:

SELECT pl.line_num, pl.from_header_id, pl.from_line_id, pl.item_description
FROM apps.po_lines_print pl
WHERE pl.from_line_id IS NOT NULL;

Other common scenarios include generating hazard and UN number labels for dangerous-goods shipments, extracting descriptive flexfield attributes for downstream interfaces, and feeding BI Publisher or Oracle Reports layouts that mirror the seeded PO Print output. When using the view, note that pricing and quantity columns may legitimately return NULL depending on order_type_lookup_code, and queries should always be scoped by org_id or po_header_id to maintain multi-org security and acceptable performance.