Results for “vendor_address_line4”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO_HEADERS_PRINT is a reporting view owned by the APPS schema within the Oracle E-Business Suite Purchasing (PO) module. It is catalogued as a VALID database object and is classified in the ETRM repository with the notation "Retrofitted," indicating that it was adapted or re-created to preserve backward compatibility for the Oracle Purchasing document printing and approval infrastructure across release 12.1.1 and 12.2.2.

The view presents a denormalised, print-ready projection of purchase order header information. Rather than exposing the transactional PO_HEADERS structure directly, it joins header data to vendor, vendor site, vendor contact, employee, currency, terms, territory, and lookup information so that a single query returns everything a printed purchase order document requires. Because printing programs must exclude documents that are on hold, the view filters out any header where NVL(USER_HOLD_FLAG,'N') = 'N' evaluation gates the row out. The view also supplies derived columns such as the approved-flag normalisation (DECODE on APPROVED_FLAG returning 'Y' or 'N'), a formatted phone number combining area code and number, and country-aware address derivation using DECODE over state, province, and county. Its role is therefore both presentational and semantic: it shields report writers and concurrent programs from the underlying multi-table join logic.

Underlying Base Objects

The documented view text draws upon a defined set of base objects. The central table is PO_HEADERS (referenced through the PO_HEADERS_ALL synonym family), with PO_HEADERS_ARCHIVE_ALL joined for archived header information. Vendor data is sourced from PO_VENDORS and PO_VENDOR_SITES_ALL, with PO_VENDOR_CONTACTS supplying the primary contact. Employee names come from HR_EMPLOYEES and the PER_PEOPLE_F date-tracked view. Supporting reference data includes FND_CURRENCIES_TL for currency code and name, FND_TERRITORIES_TL for territory short names, PO_LOOKUP_CODES for displayed lookup fields, and AP_TERMS for payment terms. The ETRM metadata further records dependencies on PO_RELEASES and PO_RELEASES_ARCHIVE_ALL, together with the FND_GLOBAL, FND_PROFILE, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages, which supply session context, profile-option evaluation, and name/security formatting. The joins are largely outer joins (notably vendor contact, archived agent, and territory), reflecting the fact that not every purchase order carries every attribute.

Key Columns

• SEGMENT1, REVISION_NUM, TYPE_LOOKUP_CODE – the purchase order number, its revision, and whether the document is a standard, blanket, or contract order.
• PRINT_COUNT, PRINTED_DATE, CREATION_DATE, REVISED_DATE – printing and lifecycle audit columns used to control reprint behaviour.
• START_DATE, END_DATE, CANCEL_FLAG – effective dating and cancellation state, relevant for blanket agreements.
• NOTE_TO_VENDOR, CONFIRMING_ORDER_FLAG, ACCEPTANCE_REQUIRED_FLAG, ACCEPTANCE_DUE_DATE – terms communicated to the supplier on the printed document.
• AGENT_ID, HRE.FIRST_NAME, HRE.LAST_NAME – the buyer associated with the order.
• VENDOR_NAME, VN.SEGMENT1, CUSTOMER_NUM – supplier identification and number.
• ADDRESS_LINE1–3, CITY, STATE/PROVINCE/COUNTY, ZIP, TERRITORY_SHORT_NAME – the formatted vendor site address.
• CURRENCY_CODE, RATE, AP_TERMS name – currency and payment terms context.
• ATTRIBUTE1 through ATTRIBUTE15 – the DFF descriptive flexfield segments exposed for printed output.
• PO_HEADER_ID, VENDOR_ID, VENDOR_SITE_ID, ORG_ID – primary and foreign key identifiers supporting drill-down and multi-org filtering.

Common Use Cases and Queries

The view is most commonly consumed by custom purchase order print programs, supplier-facing extracts, and audit reports. A typical query retrieves printable header detail for a specific order:

SELECT segment1, revision_num, vendor_name, agent_id, currency_code, note_to_vendor FROM apps.po_headers_print WHERE po_header_id = :header_id;

A multi-org aware listing filters by operating unit and excludes cancelled documents:

SELECT segment1, vendor_name, printed_date FROM apps.po_headers_print WHERE org_id = :org_id AND NVL(cancel_flag,'N') = 'N' ORDER BY creation_date DESC;

Reprint monitoring uses the print audit columns to locate orders that have been issued multiple times. Because the view already embeds the hold filter and the approved-flag decode, callers should be aware that rows on hold will not appear, and that approved_flag is returned as a normalised 'Y'/'N' rather than the raw database value.