Search Results ar_xml_invoice_tp_v




Overview
Explore in AI Chat

Overview

AR_XML_INVOICE_TP_V is a Receivables (AR) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name follows the AR_XML_* naming convention, which identifies objects built to supply data to the Oracle Receivables e-invoicing and XML invoice generation framework. The suffix "TP" denotes a trading partner perspective, meaning the view assembles the party, account, site, address, and contact information required to render the trading partner (bill-to/customer) block of an outbound XML invoice document.

The view resolves the customer hierarchy model introduced with the Oracle Trading Community Architecture (TCA) and flattens it into a single denormalized row per customer account site use. Rather than exposing raw TCA identifiers alone, it derives formatted address strings and contact display names, making the output directly consumable by XML publishing templates, BI Publisher reports, and custom outbound interfaces. It is a read-only reporting and integration object; no DML is possible against it.

Underlying Base Objects

The view is defined over TCA entity and relationship synonyms, supplemented by two PL/SQL packages and a territory lookup view. The documented base objects are:

Key Columns

  • CUST_ACCOUNT_ID, SITE_USE_ID, CUST_ACCOUNT_ROLE_ID — surrogate keys identifying the account, site use, and role.
  • PARTY_NAME, ACCOUNT_NUMBER — the trading partner's name and Receivables account number.
  • LOCATION — the location identifier associated with the account site.
  • ADDRESS — a formatted address string built from ADDRESS1–ADDRESS4 only, returned as NULL when no CUST_ACCT_SITE_ID exists.
  • COMPLETE_ADDRESS — the same formatting logic extended to include CITY, COUNTY, STATE, PROVINCE, POSTAL_CODE, and TERRITORY_SHORT_NAME.
  • ADDRESS1–ADDRESS4, CITY, COUNTY, STATE, PROVINCE, POSTAL_CODE, TERRITORY_SHORT_NAME — the individual address elements.
  • NAME, EMAIL_ADDRESS, PRIMARY_PHONE_* — the contact person's derived display name, email, and phone components.
  • TAX_REFERENCE — the party tax registration reference.
  • USER1–USER5 — party-site flexfield values returned by TP_FUNCTION1–5.

Common Use Cases and Queries

Typical uses include supplying trading partner blocks to XML invoice templates, validating bill-to address and contact data, and extracting formatted addresses for customer-facing output.

Retrieve the trading partner block for a specific account:

  • SELECT party_name, account_number, complete_address, name, email_address FROM ar_xml_invoice_tp_v WHERE cust_account_id = :p_account_id;
  • SELECT site_use_id, address, city, state, postal_code, territory_short_name FROM ar_xml_invoice_tp_v WHERE cust_account_role_id = :p_role_id;
  • SELECT cust_account_id, party_name, tax_reference FROM ar_xml_invoice_tp_v WHERE tax_reference IS NOT NULL AND territory_short_name = 'US';
  • SELECT party_name, account_number, name, primary_phone_number FROM ar_xml_invoice_tp_v WHERE email_address IS NULL;

Because the view joins only base TCA entities and calls package functions on each party site, performance is directly related to the volume of customer sites queried. Filtering on CUST_ACCOUNT_ID, SITE_USE_ID, or CUST_ACCOUNT_ROLE_ID is recommended before applying formatting-level filters.