Search Results supplier_description

Overview

AR_XML_INVOICE_V is a denormalized reporting view owned by the APPS schema in Oracle E-Business Suite Receivables. As its name implies, it presents a flattened, XML-integration-oriented projection of Receivables invoice data suitable for outbound document generation, third-party interfaces, and ad hoc reporting. The view is marked VALID in ETRM and is available in both 12.1.1 and 12.2.2. It is not a transactional object; no DML is supported against it. Instead, it consolidates header attributes from RA_CUSTOMER_TRX, line aggregation from RA_CUSTOMER_TRX_LINES, customer and location descriptors, salesperson information, and descriptive flexfield values resolved through the AR_XML_VIEW_FUNCTIONS package. Because the view crosses the AR boundary into HR and OE objects, it is primarily used where a single flat record per invoice is required, rather than the normalized parent-child structure of the underlying tables.

Underlying Base Objects

The view is defined over the following documented base objects: AR_DOCUMENT_TRANSFERS, AR_RECEIPT_METHODS, HR_ALL_ORGANIZATION_UNITS, HR_LOCATIONS, ORG_FREIGHT, RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES, RA_CUST_TRX_TYPES, and RA_SALESREPS, together with the packages AR_XML_VIEW_FUNCTIONS, HR_GENERAL, HR_SECURITY, and OE_SYS_PARAMETERS. Functionally, RA_CUSTOMER_TRX supplies the invoice header (TRX_NUMBER, TRX_DATE, CURRENCY_CODE, SHIP_DATE_ACTUAL, PURCHASE_ORDER, and the ship-to, bill-to, and remit-to identifier columns). RA_CUSTOMER_TRX_LINES provides line-level amounts, which are aggregated in scalar subqueries to produce AMOUNT and TAX_AMOUNT. AR_DOCUMENT_TRANSFERS links the invoice to an outbound transmission record, and its DOCUMENT_TRANSFER_ID is concatenated with CUSTOMER_TRX_ID to form the REFERENCE_NUMBER. RA_CUST_TRX_TYPES supplies DOCUMENT_TYPE, and AR_RECEIPT_METHODS supplies the payment method code. Supplier or organization attributes are drawn from HR_ALL_ORGANIZATION_UNITS joined to HR_LOCATIONS, while RA_SALESREPS (a view) supplies the salesperson name and e-mail address. The HR_GENERAL and HR_SECURITY packages are referenced for organizational security, and OE_SYS_PARAMETERS / ORG_FREIGHT appear in the fully expanded view text.

Key Columns

• DOCUMENT_TRANSFER_ID and CUSTOMER_TRX_ID — primary linkage keys to the transfer record and the invoice header.
• AMOUNT — sum of EXTENDED_AMOUNT across all lines of the invoice.
• TAX_AMOUNT — sum of EXTENDED_AMOUNT for lines where LINE_TYPE equals 'TAX'.
• CURRENCY_CODE, TRX_DATE, TRX_NUMBER — header-level invoicing attributes.
• PO_NUMBER — PURCHASE_ORDER value, defaulted to 'N/A' when null via NVL.
• DOCUMENT_TYPE, PAYMENT_METHOD — transaction type and receipt method code.
• REFERENCE_NUMBER — concatenation of DOCUMENT_TRANSFER_ID and CUSTOMER_TRX_ID used as a unique external reference.
• SUPPLIER_NAME, SUPPLIER_CODE, SUPPLIER_DESCRIPTION, SUPPLIER_ADDRESS_LINE_1..3 — organization and location attributes for the supplier or issuing entity.
• SALESREP, SALESREP_EMAIL — salesperson name and e-mail from RA_SALESREPS.
• USER1 through USER10 — header descriptive flexfield values resolved through AR_XML_VIEW_FUNCTIONS.HEADER_FUNCTION1 through 10.
• SHIP_TO_* / BILL_TO_* / REMIT_TO_ADDRESS_ID — party, site use, and contact identifiers for address resolution.

Common Use Cases and Queries

Typical scenarios include generating XML invoice payloads for EDI or custom integrations, reconciling transferred invoices against AR_DOCUMENT_TRANSFERS, and producing flat reporting extracts for downstream analytics. The following query returns recent invoices with their aggregated totals and salesperson information:

• SELECT trx_number, trx_date, currency_code, amount, tax_amount, salesrep, salesrep_email, po_number FROM ar_xml_invoice_v WHERE trx_date >= :from_date ORDER BY trx_date;
• SELECT reference_number, document_type, payment_method, supplier_name, user1 FROM ar_xml_invoice_v WHERE customer_trx_id = :trx_id;
• SELECT document_transfer_id, customer_trx_id, reference_number, amount FROM ar_xml_invoice_v WHERE document_transfer_id IS NOT NULL;

Because scalar subqueries and packages execute per row, the view can be expensive on large result sets; filtering by DOCUMENT_TRANSFER_ID, CUSTOMER_TRX_ID, or TRX_DATE before aggregation is recommended. Descriptive flexfield values exposed through USER1–USER10 depend on the AR_XML_VIEW_FUNCTIONS customization being present in the instance; on installations where this package has not been extended, those columns may return null.