Search Results exempt_tax_total_amount

Overview

ARBPA_CUSTOMER_TRX_HEADER is a reporting view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as FND.ARBPA_CUSTOMER_TRX_HEADER. It is part of the Bills Presentment Architecture (BPA) framework delivered within Oracle Receivables, and its purpose is to denormalize transactional header data from RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX together with customer, party, address, tax registration, and payment channel attributes drawn from the Trading Community Architecture (TCA) and E-Business Tax models. The view produces a wide, flat, presentation-ready row per transaction header, which makes it suitable for billing presentment layouts, customer-facing invoice rendering, and ad hoc operational reporting where a single row must carry both invoice and customer context. In ETRM documentation the object is listed as VALID in both 12.1.1 and 12.2.2 environments, and its column set is highly stable across those releases. The view is not a transactional interface: it is a read-only projection intended for query and display, and it does not participate in the Receivables transaction validation or accounting flow.

Underlying Base Objects

The documented dependency list confirms that ARBPA_CUSTOMER_TRX_HEADER is built from a layered set of base tables, views, and PL/SQL packages. Transactional data is sourced from RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES_ALL, RA_CUST_TRX_TYPES_ALL, RA_TERMS, RA_TERMS_LINES, RA_PAYMENT_SCHEDULES_ALL, and AR_INVOICE_COUNT_TERMS_V. Customer and party information is resolved through HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNTS_ALL, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, HZ_CUST_ACCOUNT_ROLES, HZ_ORGANIZATION_PROFILES, HZ_RELATIONSHIPS, and HZ_FORMAT_PUB. Tax and registration attributes are derived from ZX_LINES, ZX_REGISTRATIONS, ZX_PARTY_TAX_PROFILE, ZX_RATES_B, ZX_REPORTING_TYPES_B, ZX_REPORT_CODES_ASSOC, XLE_REGISTRATIONS, XLE_JURISDICTIONS_VL, XLE_LEGALAUTH_V, and XLE_ENTITY_PROFILES. Receipt method and payment channel values come from AR_RECEIPT_METHODS and IBY_FNDCPT_PMT_CHNNLS_VL, while batch and salesrep context is obtained from RA_BATCH_SOURCES_ALL and RA_SALESREPS_ALL. Supporting packages such as AR_BPA_UTILS_PKG, AP_AMOUNT_UTILITIES_PKG, FND_GLOBAL, FND_CURRENCY, FND_MESSAGE, HR_GENERAL, and XLE_CONTACT_GRP supply derivations, formatting, and localization logic rather than row data. The join topology is anchored on the transaction header and fans outward to customer, site, address, and tax registration, which is why the view exposes attributes that would otherwise require several correlated subqueries.

Key Columns

The view exposes a consolidated set of identifiers and descriptive attributes. Transaction identifiers include TRANSACTION_ID, TRANSACTION_NUMBER, DOCUMENT_SEQUENCE_NUMBER, TRANSACTION_DATE, TRANSACTION_TERM_DUE_DATE, TRANSACTION_CURRENCY_CODE, and TRANSACTION_TYPE. Customer and party identification is provided by CUST_ACCOUNT_ID, PARTY_ID, PARTY_SITE_ID, CUST_ACCT_SITE_ID, ACCOUNT_NUMBER, ACCOUNT_NAME, and CUSTOMER_PARTY_NAME. Address information is presented both in structured form (CUSTOMER_ADDRESS, CUSTOMER_CITY, CUSTOMER_STATE, CUSTOMER_COUNTY, CUSTOMER_POSTAL_CODE, CUSTOMER_COMPLETE_ADDRESS) and in attribute form (CUSTOMER_ATTR_COMPLETE_ADDRESS, CUSTOMER_NAME_ATTR, CUSTOMER_ADDRESS_ATTR). A significant cluster of tax columns supports fiscal reporting: CUSTOMER_TAX_REFERENCE, CUSTOMER_TAX_PAYER_ID, CUSTOMER_TAX_REF_NUMBER, and notably REP_REG_NUMBER, which carries the reporting registration number associated with the customer or first-party legal entity for the applicable jurisdiction. Users searching for rep_reg_number are typically locating the reporting registration identifier used on tax-compliant invoice and report output. Payment and receipt context is exposed via RECEIPT_METHOD_NAME, PAYMENT_METHOD_NAME, and the RCT_GLOBAL_ATTRIBUTE3 through RCT_GLOBAL_ATTRIBUTE15 descriptive flexfield columns. Shipping and logistics details appear in WAYBILL_NUMBER, SHIPPING_BILL, and SHIPPING_DATE, while VENDOR_PARTY_NAME, VENDOR_ADDRESS, VENDOR_CITY, VENDOR_STATE, VENDOR_COUNTY, VENDOR_POSTAL_CODE, and VENDOR_COMP support third-party or vendor-presented billing scenarios. ORIGINAL_COPY indicates whether the row represents an original or a copy rendition of the document.

Common Use Cases and Queries

Typical usage includes building Bills Presentment templates, generating tax-compliant invoice extracts, and producing receivables aging or customer statement reports that require a single-row header image. A basic query retrieving a transaction with its reporting registration number is shown below.

• SELECT transaction_number, transaction_date, account_number, customer_party_name, rep_reg_number FROM apps.arbpa_customer_trx_header WHERE transaction_id = :p_transaction_id;
• SELECT transaction_number, customer_tax_reference, customer_tax_ref_number, rep_reg_number FROM apps.arbpa_customer_trx_header WHERE customer_tax_reference IS NOT NULL ORDER BY transaction_date DESC;
• SELECT transaction_number, receipt_method_name, payment_method_name, rct_global_attribute3 FROM apps.arbpa_customer_trx_header WHERE transaction_type = 'INV' AND transaction_date BETWEEN :p_from AND :p_to;
• SELECT transaction_number, waybill_number, shipping_date, vendor_party_name FROM apps.arbpa_customer_trx_header WHERE shipping_date IS NOT NULL;

Because the view applies TCA and tax resolution logic through its underlying packages, queries should be filtered on indexed transactional columns such as TRANSACTION_ID or TRANSACTION_NUMBER rather than on formatted address or tax registration columns. Where only a small number of attributes are needed, querying RA_CUSTOMER_TRX_ALL directly is more efficient; ARBPA_CUSTOMER_TRX_HEADER is best reserved for scenarios where the denormalized customer, address, tax, and payment context must be returned together.