Search Results bill_address_line1




Overview
Explore in AI Chat

Overview

The APPS.PO_HEADERS_CHANGE_PRINT view is a reporting and integration construct in Oracle E-Business Suite Purchasing. Its purpose is to consolidate the data required to render, print, or transmit a purchase order document — the standard printed PO, a change order, or an electronic communication to a supplier. It assembles header-level attributes of the purchase order together with resolved agent and buyer names, supplier identification, supplier site address details, currency and rate information, and fully formatted ship-to and bill-to address blocks.

Because Oracle stores location information in a normalized, multi-table structure, generating a human-readable address requires the Purchasing communication API rather than a simple join. PO_HEADERS_CHANGE_PRINT performs this resolution at query time, which is why it is the preferred source for report definitions, custom print programs, and interface extracts that need complete order documentation in a single result set. It shields the developer from the complexity of the underlying address model and from the packaged functions that format addresses for display.

Underlying Base Objects

The view is defined over a substantial set of documented base objects. Purchase order content is drawn from the PO_HEADERS synonym, with archive counterparts PO_HEADERS_ARCHIVE and PO_HEADERS_ARCHIVE_ALL supporting historical and change-order printing, and PO_RELEASES_ARCHIVE / PO_RELEASES_ARCHIVE_ALL providing release-level history. Supplier data is sourced from PO_VENDORS, PO_VENDOR_SITES, PO_VENDOR_SITES_ALL, and AP_SUPPLIER_CONTACTS. Employee and agent information is resolved through HR_EMPLOYEES, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY, which enforces the security profile of the reporting user. Lookup values for ship-via, hold, and cancel reasons are joined from PO_LOOKUP_CODES and AP_TERMS supplies payment terms. Currency and rate information come from FND_CURRENCIES_VL, and territory naming from FND_TERRITORIES_TL. Critically, FND_GLOBAL, FND_PROFILE, and the PO_COMMUNICATION_PVT package provide the session context and the address-formatting logic that produces the ship-to and bill-to columns.

Key Columns

Document identity columns include TYPE_LOOKUP_CODE, SEGMENT1 (the PO number), REVISION_NUM, and the PRINT_COUNT, CREATION_DATE, PRINTED_DATE, and REVISED_DATE fields used to track document lifecycle and change-order generation. Agent columns (AGENT_ID, FIRST_NAME, LAST_NAME) identify both the current and prior buyer through the POH and POH2 aliases. Supplier columns include VENDOR_NAME, CUSTOMER_NUM, and SEGMENT1 from PO_VENDORS, alongside the vendor site address fields ADDRESS_LINE1 through ADDRESS_LINE3, CITY, VENDOR_STATE, ZIP, and a formatted VENDOR_PHONE.

The address columns most relevant to the search for ship_address_line1 are generated through PO_COMMUNICATION_PVT.GETLOCATIONINFO and the package's GETADDRESSLINE1, GETADDRESSLINE2, GETADDRESSLINE3, GETTOWNORCITY, GETSTATEORPROVINCE, GETPOSTALCODE, and GETTERRITORRYSHORTNAME functions. These produce SHIP_ADDRESS_LINE1, SHIP_ADDRESS_LINE2, SHIP_ADDRESS_LINE3, SHIP_CITY, SHIP_STATE_PROVINCE, SHIP_POSTAL_CODE, and SHIP_COUNTRY, with the parallel BILL_* columns covering the bill-to location. Additional columns expose currency code, name and rate, blanked total amount as AMOUNT_AGREED, approval and cancel flags, confirming-order and acceptance flags, and the note to vendor.

Common Use Cases and Queries

Typical uses include custom purchase order print and change-order output, supplier notification extracts, and reporting on order addresses. A representative query retrieving ship-to addressing for a given PO number is:

  • SELECT segment1, revision_num, ship_address_line1, ship_city, ship_state_province, ship_postal_code, ship_country FROM apps.po_headers_change_print WHERE segment1 = :po_number;
  • Filtering by printed_date or print_count to identify change orders not yet printed.
  • Joining to PO_LINES or PO_DISTRIBUTIONS for line-level extracts, using SEGMENT1 as the linking key.
  • Reporting on vendor site addressing where the vendor's own ADDRESS_LINE1 is required rather than the resolved ship-to block.

Note that the SHIP_* columns depend on session context established by PO_COMMUNICATION_PVT; running the view outside an applications session, or without the correct org and location identifiers in scope, may return null address values. Consumers should therefore execute the view from within an Oracle Applications responsibility rather than from a generic SQL client.