Search Results ship_postal_code




Overview
Explore in AI Chat

Overview

The PO_HEADERS_CHANGE_PRINT view is an APPS-owned, VALID database object within the Oracle E-Business Suite Purchasing (PO) module. Its description in the ETRM repository is recorded simply as "Retrofitted," indicating that the object was migrated or re-created as part of an upgrade or retrofit exercise and is not accompanied by extensive functional commentary. Functionally, the view consolidates the header-level attributes of purchase orders and related documents so they can be consumed by the change and print processing flows in Purchasing — most notably the Print Purchase Orders and Change Order printing programs. Rather than joining dozens of base tables at runtime, these concurrent programs and any dependent reporting or integration layer can query a single denormalized row per document revision.

Because the view is exposed under the APPS schema, it is available to standard EBS responsibilities, custom reports, and interfaces without requiring direct access to the underlying transactional tables, which is consistent with Oracle's recommended practice of building customizations over supported views rather than base tables.

Underlying Base Objects

The ETRM metadata records the following referenced objects for PO_HEADERS_CHANGE_PRINT:

The view therefore sits at the intersection of Purchasing, Payables supplier data, HR employee data, and FND reference data, resolving them into a flat, print-ready projection.

Key Columns

Columns exposed by the view include document identification (TYPE_LOOKUP_CODE, SEGMENT1, REVISION_NUM), print and revision tracking (PRINT_COUNT, PRINTED_DATE, REVISED_DATE, CREATION_DATE, START_DATE, END_DATE), and commercial terms (NOTE_TO_VENDOR, AMOUNT_AGREED from BLANKET_TOTAL_AMOUNT, APPROVED_FLAG, CANCEL_FLAG, CONFIRMING_ORDER_FLAG, ACCEPTANCE_REQUIRED_FLAG, ACCEPTANCE_DUE_DATE). Buyer information appears through FIRST_NAME/LAST_NAME pairs derived from HR_EMPLOYEES and the AGENT_ID columns. Currency data is exposed via FCC.CURRENCY_CODE, FCC.NAME, and RATE. Vendor details include POV.SEGMENT1 (supplier number), VENDOR_NAME, CUSTOMER_NUM, address lines, state, zip, territory short name, and phone, plus contact name and phone from AP_SUPPLIER_CONTACTS. Ship-to and bill-to locations are populated dynamically through PO_COMMUNICATION_PVT, yielding SHIP_ADDRESS_LINE1-3, SHIP_CITY, SHIP_STATE_PROVINCE, SHIP_POSTAL_CODE, SHIP_COUNTRY, and the equivalent BILL_* columns. Lookup decoding is applied to CANCEL_FLAG (mapping 'I' to 'Y') and SHIP_VIA.

Common Use Cases and Queries

The most frequent use is supporting the Change Order print program and ad-hoc reporting on purchase order revisions. A typical query retrieves the latest revision for a document:

  • Identifying documents pending print (PRINT_COUNT = 0 or PRINTED_DATE IS NULL).
  • Reporting document revision history across PO_HEADERS and its archive tables.
  • Extracting ship-to/bill-to address blocks for supplier communication or integration files.
  • Auditing approval and cancellation flags for a given date range.

Illustrative SQL:

SELECT segment1, revision_num, type_lookup_code, vendor_name, ship_city, ship_country, approved_flag, printed_date FROM apps.po_headers_change_print WHERE segment1 = :p_po_number AND NVL(cancel_flag,'N') = 'N';

Because address columns are produced by PO_COMMUNICATION_PVT function calls, each row carries the overhead of package execution, so queries should be filtered tightly by SEGMENT1, dates, or AGENT_ID rather than scanned in full.