Search Results purchase_order_date




Overview
Explore in AI Chat

Overview

APPS.AR_XML_PO_INFO_V is a reporting and integration view in the Oracle E-Business Suite Receivables (AR) module, present in releases 12.1.1 and 12.2.2. It exposes purchase order (PO) reference information captured on customer transactions in Oracle Receivables, together with up to five derived "USER" attribute columns produced by PL/SQL functions in the AR_XML_VIEW_FUNCTIONS package. The view is primarily consumed by Oracle Receivables' eXtensible Markup Language (XML) publishing and outbound document generation infrastructure, where purchase order data is required on printed or electronically delivered invoice documents, credit memos, and related customer-facing output.

The view is named with the AR_XML_ prefix, indicating it is one of a family of XML-oriented views that flatten and transform Receivables transaction data into a format suitable for XML Publisher (BI Publisher) templates and other integration consumers. Because it derives additional columns dynamically through function calls, it provides a presentation-layer abstraction rather than a purely relational projection of base tables.

Underlying Base Objects

According to the ETRM metadata, AR_XML_PO_INFO_V is defined over two referenced objects:

  • RA_CUSTOMER_TRX (SYNONYM) — the core Receivables transactions table, accessed through its APPS synonym. This supplies the transaction identifier and the purchase order columns, filtered with the predicate PURCHASE_ORDER IS NOT NULL so that only transactions carrying a PO reference are returned.
  • AR_XML_VIEW_FUNCTIONS (PACKAGE) — a PL/SQL package whose functions PO_FUNCTION1 through PO_FUNCTION5 are invoked once per row, each returning a value aliased as USER1 through USER5.

Because the view joins a synonym to a package rather than to another table, row cardinality is preserved at one row per qualifying RA_CUSTOMER_TRX record, assuming each function returns a scalar value. The view is owned by APPS and is therefore typically granted to Receivables and reporting responsibilities through standard APPS schema privileges.

Key Columns

  • CUSTOMER_TRX_ID — the primary key of the underlying Receivables transaction; the join key back to RA_CUSTOMER_TRX and related AR tables.
  • PURCHASE_ORDER — the customer's purchase order number associated with the transaction. This is the driving filter column and the object of the user's "purchase_order" search.
  • PURCHASE_ORDER_REVISION — the revision level of the referenced purchase order, where supplied by the customer.
  • PURCHASE_ORDER_DATE — the date of the purchase order, typically used for display on invoice output and for reconciliation.
  • USER1 through USER5 — derived descriptor columns computed by AR_XML_VIEW_FUNCTIONS.PO_FUNCTION1..5. Their semantics are determined by the package body rather than by stored columns, and they are intended to carry supplementary PO-related or transaction-related values required by XML document templates.

Common Use Cases and Queries

The view is most commonly queried for document generation and reporting on PO-referenced Receivables transactions, and for validation of PO data prior to invoice delivery.

  • Retrieving PO details for a specific transaction.
  • Listing all transactions with PO references for a given date range.
  • Feeding XML Publisher templates with PO information.

Illustrative SQL:

SELECT customer_trx_id,
       purchase_order,
       purchase_order_revision,
       purchase_order_date,
       user1,
       user2
  FROM apps.ar_xml_po_info_v
 WHERE purchase_order = :p_po_number;

SELECT customer_trx_id,
       purchase_order,
       purchase_order_date
  FROM apps.ar_xml_po_info_v
 WHERE purchase_order_date BETWEEN :p_from AND :p_to
 ORDER BY purchase_order_date;

Because USER1 through USER5 are computed by function calls executed for every row, queries should filter aggressively on CUSTOMER_TRX_ID or PURCHASE_ORDER to limit function invocation overhead. The view should be treated as read-only and consumed through the APPS synonym in custom reports and XML templates.