Search Results to_supplier




Overview
Explore in AI Chat

Overview

APPS.ITG_SP_PO_HEADERS_V is a VALID Oracle E-Business Suite view owned by the APPS schema. As documented in the ETRM metadata (FND Design Data: ITG.ITG_SP_PO_HEADERS_V), the view exists to generate XML at the purchase order header level for use in the Sync PO message. It therefore functions as an integration-facing projection rather than a general-purpose transactional view: its column set combines native purchasing attributes with a set of distribution or routing columns (the TO_* columns) that identify the intended recipients of the outbound message. Because the view is APPS-owned and uses public synonyms for its base purchasing table, it is accessible to any responsibility or concurrent program with standard APPS access, making it a convenient read-only source for both interface programs and ad hoc reporting. The metadata notes that the view is referenced by no other database object, confirming that it is a terminal publishing layer consumed by external or middleware processes rather than an internal dependency of other EBS code.

Underlying Base Objects

The documented dependency list is concise and centers on Purchasing and HR:

  • PO_HEADERS_ALL (SYNONYM) — the primary source of purchase order header data, supplying PO_HEADER_ID and the buyer, status, type, and amount attributes.
  • PER_PEOPLE_F (VIEW) and HR_PERSON_NAME (PACKAGE) — used to resolve buyer identity and formatted person names.
  • HR_GENERAL (PACKAGE) — utility routines for HR lookups and value resolution.
  • HR_LOCATIONS_ALL (SYNONYM) — supplies delivery location and address information for the DELIVERTO element.
  • HR_SECURITY (PACKAGE) — enforces HR organizational security when resolving person and location data.
  • ITG_X_UTILS (PACKAGE) — the integration utility package that supports XML generation and message formatting.

The presence of HR_SECURITY indicates that buyer and location values may be filtered according to the querying user's HR security profile, a behavior that should be anticipated when results differ between users.

Key Columns

  • PO_HEADER_ID (NUMBER) — the unique purchase order header identifier, the join key back to PO_HEADERS_ALL.
  • POID (VARCHAR2 20) — the formatted purchase order number used in the outbound message.
  • BUYERID (VARCHAR2 240) — the buyer identifier or name as resolved through the HR person objects.
  • DATETIME_DOCUMENT (DATE) — the document date of the purchase order.
  • OPERAMT_EXTENDED / OPERAMT_CURRENCY — the extended operating amount and its currency code.
  • POSTATUS, POTYPE, PORELEASE, POENTITY — status, document type, release information, and operating unit or entity context.
  • DELIVERTO (VARCHAR2 60) — the delivery destination derived from the HR location objects.
  • NOTES (VARCHAR2 240) and TAXWHEXMPT — header notes and tax exemption indicator.
  • TO_PO_INTERNAL, TO_MISC, TO_APPROVER, TO_BUYER, TO_PAYABLES, TO_RECEIVER, TO_SUPPLIER — routing flags identifying the intended recipients of the Sync PO message. TO_BUYER, the column associated with the user's search, governs whether the buyer is included as a message recipient.

Common Use Cases and Queries

Typical uses include tracing which buyers are routed on outbound Sync PO messages, validating header amounts and currency before transmission, and extracting PO header extracts for reconciliation. A basic projection follows:

SELECT PO_HEADER_ID, POID, BUYERID, TO_BUYER, POSTATUS, POTYPE, OPERAMT_EXTENDED, OPERAMT_CURRENCY, DATETIME_DOCUMENT FROM APPS.ITG_SP_PO_HEADERS_V WHERE TO_BUYER IS NOT NULL;

To isolate messages targeting the buyer by status, add a predicate such as WHERE POSTATUS = 'APPROVED' AND TO_BUYER = 'Y'. Because buyer and location resolution flows through HR_SECURITY, results may be constrained by the executing user's security profile; testing under the intended integration account is advisable.