Search Results vendor_quote_num




Overview
Explore in AI Chat

Overview

APPS.PO_LINES_CHANGE_PRINT is a reporting view in Oracle E-Business Suite (documented for 12.1.1 and 12.2.2) that presents archived purchase order line data in a print-ready, denormalized form. It is the data source behind the "Purchase Order Lines Change" report, whose purpose is to show the state of PO lines at a specific revision so that changes made through the revision/change-order process can be reviewed and printed. Because it reads from PO_LINES_ARCHIVE rather than PO_LINES_ALL, the view captures historical line snapshots rather than only currently effective lines.

The view is owned by the APPS schema and is exposed to reporting tools such as Oracle Reports, BI Publisher, and custom concurrent programs. It joins a line to its parent header and line type, then decodes several attributes so the printed output reflects the correct quantity, price, and amount behavior for the underlying order type. The user search term "type_lookup_code" is central to this view: PH1.TYPE_LOOKUP_CODE (from PO_HEADERS_ALL) distinguishes STANDARD from PLANNED orders, and PLT.ORDER_TYPE_LOOKUP_CODE (from PO_LINE_TYPES) distinguishes QUANTITY, AMOUNT, RATE, and FIXED PRICE lines, driving the conditional value logic.

Underlying Base Objects

The view is defined over the following documented base objects:

  • PO_LINES_ARCHIVE — the archived PO lines, aliased POL; the primary driver of the query.
  • PO_HEADERS_ALL — aliased PH1 (the archived line's header) and PH2 (the original/related header); supplies TYPE_LOOKUP_CODE, SEGMENT1, and quote vendor information.
  • PO_LINES_ALL (PL2) — supplies the current line number for reference (PL2.LINE_NUM).
  • PO_LINE_TYPES (PLT) — supplies LINE_TYPE_ID and ORDER_TYPE_LOOKUP_CODE, which determines how quantities and amounts are interpreted.
  • MTL_UNITS_OF_MEASURE (MUM) — supplies the translated unit of measure description.
  • PO_UN_NUMBERS (PUN) — supplies the UN number and description for hazardous material lines.
  • PO_HAZARD_CLASSES (PHC) — supplies the hazard class code.
  • PO_LINE_LOCATIONS_ALL, PO_RELEASES_ALL, and PO_COMMUNICATION_PVT — documented as referenced objects, used in the broader print/communication flow.

The central join predicate is POL.LINE_TYPE_ID = PLT.LINE_TYPE_ID, with POL.PO_HEADER_ID = PH1.PO_HEADER_ID, restricted to headers whose TYPE_LOOKUP_CODE is STANDARD or PLANNED.

Key Columns

Common Use Cases and Queries

Typical usage is to print or audit archived PO lines, filter by revision, or extract change data for a specific order type. Example queries include:

  • Lines for a given archived header: SELECT line_num, item_description, unit_price, quantity FROM apss.po_lines_change_print WHERE po_header_id = :p_header_id ORDER BY line_num;
  • Isolating quantity-based lines: SELECT line_num, quantity, unit_price FROM apss.po_lines_change_print WHERE order_type_lookup_code = 'QUANTITY';
  • Revision audit across types: SELECT revision_num, line_num, type_lookup_code, order_type_lookup_code FROM apss.po_lines_change_print WHERE po_header_id = :p_id;
  • Multi-org scoping: add AND org_id = :p_org_id to any of the above.

Because the view reads archive tables, results reflect the revision snapshot, making it suitable for change-history reporting rather than live transactional queries.