Results for “credit_memo_reason”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ARBPA_CUSTOMER_TRX_HEADER is a reporting view owned by the APPS schema in Oracle E-Business Suite, registered under the FND – Application Object Library product. It presents a denormalized, report-ready representation of Accounts Receivable transactions, combining receivables transaction header data with customer, party, address, tax, receipt method, payment method, terms, salesperson, and first-party legal entity information. The view is part of the ARBPA (Receivables Business Process Accelerator / Bill Presentment and Analysis) family of objects used to drive invoice print, bill presentment, and receivables analysis.

Its purpose is to flatten the complex normalized relationships across RA_CUSTOMER_TRX_ALL, HZ_CUST_ACCOUNTS, HZ_PARTIES, HZ_LOCATIONS, ZX tax tables, and XLE legal entity tables into a single row per transaction header. This makes the view particularly suitable for reporting layers, BI Publisher templates, and outbound integration interfaces where consumers require transaction header detail alongside formatted customer and vendor addressing and computed tax rates without having to reproduce EBS's internal joins.

A returned user search for "vendor_state" is directly satisfied by this view: it exposes VENDOR_STATE, VENDOR_CITY, VENDOR_COUNTY, VENDOR_POSTAL_CODE, VENDOR_ADDRESS, and a concatenated VENDOR_COMPLETE_ADDRESS, allowing reporting of the vendor (supplier/first-party) location on a customer transaction — a common requirement in tax and legal-document reporting.

Underlying Base Objects

The view is defined over a substantial set of base objects. The transaction backbone comes from RA_CUSTOMER_TRX_ALL (with RA_CUSTOMER_TRX as a synonym), RA_CUSTOMER_TRX_LINES_ALL, RA_CUST_TRX_TYPES_ALL, RA_TERMS, RA_TERMS_LINES, RA_BATCH_SOURCES_ALL, RA_SALESREPS_ALL, RA_PAYMENT_SCHEDULES_ALL, and AR_RECEIPT_METHODS for receipt/payment method names. Customer and party information is sourced from HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNTS_ALL, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_CUST_ACCOUNT_ROLES, HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, HZ_RELATIONSHIPS, HZ_ORGANIZATION_PROFILES, and HZ_FORMAT_PUB for address formatting.

Tax data is drawn from ZX_LINES, ZX_PARTY_TAX_PROFILE, ZX_RATES_B, ZX_REGISTRATIONS, ZX_REPORTING_TYPES_B, and ZX_REPORT_CODES_ASSOC. First-party / legal-entity context comes from XLE_ENTITY_PROFILES, XLE_ETB_PROFILES, XLE_REGISTRATIONS, XLE_CONTACT_GRP, XLE_FIRSTPARTY_INFORMATION_V, XLE_LEGALAUTH_V, XLE_JURISDICTIONS_VL, and FND_TERRITORIES_TL / FND_TERRITORIES_VL. Supporting infrastructure includes FND_GLOBAL, FND_CURRENCY, FND_MESSAGE, FND_ACCESS_CONTROL_UTIL, AR_BPA_UTILS_PKG, AP_AMOUNT_UTILITIES_PKG, HR_GENERAL, and HR_LOCATIONS. The presence of RA_TERMS and AR_INVOICE_COUNT_TERMS_V confirms it supplies structured installment/term information.

Key Columns

• Transaction identity: TRANSACTION_ID, TRANSACTION_NUMBER, TRANSACTION_DATE, TRANSACTION_TYPE, DOCUMENT_SEQUENCE_NUMBER, WAYBILL_NUMBER, and TRANSACTION_TERM_DUE_DATE.
• Customer/party: CUST_ACCOUNT_ID, PARTY_ID, PARTY_SITE_ID, CUST_ACCT_SITE_ID, ACCOUNT_NUMBER, ACCOUNT_NAME, CUSTOMER_PARTY_NAME, and CUSTOMER_ATTR_COMPLETE_ADDRESS.
• Customer address: CUSTOMER_ADDRESS, CUSTOMER_CITY, CUSTOMER_STATE, CUSTOMER_COUNTY, CUSTOMER_POSTAL_CODE, and CUSTOMER_COMPLETE_ADDRESS.
• Vendor / first-party address: VENDOR_PARTY_NAME, VENDOR_ADDRESS, VENDOR_CITY, VENDOR_STATE, VENDOR_COUNTY, VENDOR_POSTAL_CODE, and VENDOR_COMPLETE_ADDRESS.
• Tax and registration: CUSTOMER_TAX_REFERENCE, CUSTOMER_TAX_REG_NUMBER, VENDOR_TAX_REFERENCE, VENDOR_TAX_REG_NUMBER, CUSTOMER_TAX_AUTHORITY, REP_REG_NUMBER, and CUSTOMER_TAX_PAYER_ID.
• Payment/terms: RECEIPT_METHOD_NAME, PAYMENT_METHOD_NAME, TERM_NAME, TERM_DESC, and the RCT_GLOBAL_ATTRIBUTE3 through RCT_GLOBAL_ATTRIBUTE15 flexfields.
• Amounts and derived rates: LINE_TOTAL_AMOUNT, TAX_TOTAL_AMOUNT with TAX_RATE, VAT_TAX_TOTAL_AMOUNT with VAT_TAX_RATE, EXCISE_TAX_TOTAL_AMOUNT with EXCISE_TAX_RATE, and EXEMPT_TAX_TOTAL_AMOUNT with its corresponding rate — each computed as amount times 100 divided by LINE_TOTAL_AMOUNT.
• Origin: ORIGINAL_COPY and USER_NAME identify whether the row is an original or copied transaction and which application user created it. SALES_PERSON_NAME and TRANSACTION_CURRENCY_CODE round out the header.

Common Use Cases and Queries

Typical use cases include tax and legal-document reporting, invoice print templates that require vendor or first-party state information, and BI Publisher dashboards summarizing receivables by customer state or vendor state. The view's precomputed tax rates eliminate the need to join ZX tables directly.

Example — retrieve header detail for a transaction including vendor state:

• SELECT transaction_number, transaction_date, customer_party_name, customer_state, vendor_party_name, vendor_state, transaction_currency_code, line_total_amount, tax_total_amount, tax_rate FROM apps.arbpa_customer_trx_header WHERE transaction_id = :p_transaction_id;

Example — summarize transaction totals by vendor state for a date range:

• SELECT vendor_state, transaction_currency_code, COUNT(*) transaction_count, SUM(line_total_amount) total_lines, SUM(tax_total_amount) total_tax FROM apps.arbpa_customer_trx_header WHERE transaction_date BETWEEN :p_from_date AND :p_to_date GROUP BY vendor_state, transaction_currency_code ORDER BY vendor_state;

Example — locate transactions by customer state and tax registration:

• SELECT transaction_number, customer_party_name, customer_state, customer_tax_reg_number FROM apps.arbpa_customer_trx_header WHERE customer_state = :p_state AND customer_tax_reg_number IS NOT NULL;

Because the view aggregates data across AR, HZ, ZX, XLE, and FND, queries should always be qualified with APPSCONNECT or APPS credentials and, where possible, filtered on TRANSACTION_ID or TRANSACTION_DATE to bound the join cost. The view is read-only and is not intended for transactional updates to receivables data.