Search Results purchase_order_date




Overview
Explore in AI Chat

Overview

The AR_XML_PO_INFO_V view is a Receivables (AR) module object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes purchase order reference information associated with customer transactions, drawing from the RA_CUSTOMER_TRX table and rendering derived values through the AR_XML_VIEW_FUNCTIONS package. The view is part of Oracle's XML-based data extraction framework used to generate structured documents — such as invoices, credit memos, and related business communications — that must include purchasing references supplied by trading partners.

In EBS, many tasks are fulfilled by XML Publisher (BI Publisher) templates that require specific columns to be exposed in a queryable, predictable format. AR_XML_PO_INFO_V serves that role for purchase order data. It presents the transaction identifier alongside the purchase order number, revision, and date, and then augments that core set with five derived USER columns whose values are computed at runtime by dedicated functions in the AR_XML_VIEW_FUNCTIONS package. Because these USER columns are function-generated, the view is not a simple projection of stored columns; it is a calculated presentation layer intended for report generation and outbound data feeds rather than for transactional data entry.

Underlying Base Objects

The view definition references two documented base objects:

  • RA_CUSTOMER_TRX (SYNONYM) — The core Receivables transaction table. The view selects CUSTOMER_TRX_ID, PURCHASE_ORDER, PURCHASE_ORDER_REVISION, and PURCHASE_ORDER_DATE directly from this source. It also applies a filter restricting results to rows where PURCHASE_ORDER IS NOT NULL, so only transactions with a recorded purchase order are returned.
  • AR_XML_VIEW_FUNCTIONS (PACKAGE) — A PL/SQL package supplying the PO_FUNCTION1 through PO_FUNCTION5 functions. Each is invoked once per qualifying row, receiving CUSTOMER_TRX_ID as its input, and returns the value mapped to USER1 through USER5 respectively.

The relationship to RA_CUSTOMER_TRX makes the view transaction-centric: every returned row corresponds to a single Receivables transaction that carries a purchase order reference. The package dependency introduces a procedural dimension, meaning view performance and behavior are influenced by the logic inside AR_XML_VIEW_FUNCTIONS.

Key Columns

  • CUSTOMER_TRX_ID — Primary identifier of the Receivables transaction; also the argument passed to each PO_FUNCTIONn call.
  • PURCHASE_ORDER — The customer's purchase order number associated with the transaction. The view returns only rows where this value is populated.
  • PURCHASE_ORDER_REVISION — The revision level of the referenced purchase order.
  • PURCHASE_ORDER_DATE — The date associated with the purchase order reference.
  • USER1 through USER5 — Derived columns whose values are returned by AR_XML_VIEW_FUNCTIONS.PO_FUNCTION1 through PO_FUNCTION5. These typically carry supplementary or formatted purchase order attributes required by specific XML templates, and their precise semantics depend on the package implementation.

Common Use Cases and Queries

The view is most often consumed by XML Publisher data definitions that must print purchase order details on invoices and related documents, by outbound interfaces exchanging order-to-cash data with customer or EDI systems, and by diagnostic queries confirming which transactions carry PO references.

A basic retrieval joining the view back to the transaction header:

  • SELECT v.CUSTOMER_TRX_ID, v.PURCHASE_ORDER, v.PURCHASE_ORDER_REVISION, v.PURCHASE_ORDER_DATE, v.USER1, v.USER2 FROM APPS.AR_XML_PO_INFO_V v WHERE v.CUSTOMER_TRX_ID = :p_trx_id;
  • SELECT t.TRX_NUMBER, v.PURCHASE_ORDER, v.PURCHASE_ORDER_DATE FROM APPS.AR_XML_PO_INFO_V v, APPS.RA_CUSTOMER_TRX_ALL t WHERE t.CUSTOMER_TRX_ID = v.CUSTOMER_TRX_ID AND v.PURCHASE_ORDER = :p_po_number;

Because USER1 through USER5 are function-generated, use of these columns in high-volume queries should be evaluated for performance impact, and callers should confirm the expected return semantics against the AR_XML_VIEW_FUNCTIONS package body for the specific EBS release in use.