Search Results ar_xml_invoice_line_v




Overview
Explore in AI Chat

Overview

The AR_XML_INVOICE_LINE_V view is a public synonym owned by the APPS schema in Oracle E-Business Suite Receivables. It exposes invoice line data in a flattened, XML-oriented layout intended for outbound invoice generation, e-invoicing integrations, and print/BI Publisher data extraction. The view is registered as a VALID object in both EBS 12.1.1 and 12.2.2 and draws exclusively from the Receivables transaction line tables, so it remains stable across the two releases.

The view is designed to feed e-invoicing and XML delivery processes for open receivables transactions. Its column list includes customer identifiers, transaction identifiers, line attributes, item descriptions, and a set of ten user-defined extraction columns populated by calls to the AR_XML_VIEW_FUNCTIONS package, which allows customers to attach custom line-level attributes to XML payloads without modifying base tables.

Underlying Base Objects

The view is defined over RA_CUSTOMER_TRX_LINES, MTL_SYSTEM_ITEMS, AR_MEMO_LINES_VL, and OE_SYSTEM_PARAMETERS. Documented referenced objects in ETRM include AR_MEMO_LINES_VL (VIEW), AR_XML_VIEW_FUNCTIONS (PACKAGE), FA_RX_FLEX_PKG, HR_GENERAL, HR_SECURITY, MO_GLOBAL, MTL_SYSTEM_ITEMS (SYNONYM), OE_SYSTEM_PARAMETERS (SYNONYM), OE_SYS_PARAMETERS (PACKAGE), and RA_CUSTOMER_TRX_LINES (SYNONYM).

The join logic restricts the result set to invoice lines only: L.LINK_TO_CUST_TRX_LINE_ID IS NULL excludes lines that reference a parent line, and L.LINE_TYPE = 'LINE' excludes tax, freight, and other non-line rows. The item description is resolved either from the memo line (AR_MEMO_LINES_VL) or from MTL_SYSTEM_ITEMS depending on whether INVENTORY_ITEM_ID is populated, and the master organization context is enforced by joining OE_SYSTEM_PARAMETERS.MASTER_ORGANIZATION_ID.

Key Columns

Common Use Cases and Queries

Typical use cases include generating invoice XML for print or e-invoicing, BI Publisher data extracts, and reconciliation reports that require line-level amounts. A representative query is:

  • Retrieve all lines for a given transaction:
    SELECT customer_trx_line_id, line_number, line_amount, unit_selling_price, quantity, item, item_description, uom FROM ar_xml_invoice_line_v WHERE customer_trx_id = :p_trx_id ORDER BY line_number;
  • Extract user-defined attributes for XML payload generation:
    SELECT customer_trx_id, reference_number, user1, user2, user3 FROM ar_xml_invoice_line_v WHERE customer_trx_id = :p_trx_id;

Because the USER1..USER10 columns call PL/SQL functions, queries should limit row counts when possible. The view is read-only and inherits security from its base tables, so access depends on APPS schema privileges or grants to the querying user.