Results for “rac_bill_to_customer_name”

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

Overview

The APPS.JAI_AR_TRX_DETAILS_V view is a reporting and integration object supplied with the JA — Asia/Pacific Localizations product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It consolidates Oracle Receivables transaction header data with receivable distribution, transaction type, batch source, and Trading Community Architecture (TCA) party information into a single denormalized result set. The view is designed to expose completed Receivables records alongside the receiving-side accounting distribution, so that downstream localizations (notably Japanese and other Asia/Pacific statutory extracts) can report on revenue transactions without re-joining the base Receivables schema.

Because it is a view rather than a table, it carries no independent storage and reflects the state of the underlying Receivables and TCA tables at query time. Its role is primarily read-only reporting, ad-hoc extraction, and as a data source for localization programs and concurrent request outputs. When a user searches for CTT_CLASS, they are typically tracing a Receivables transaction type classification, which the view surfaces directly from RA_CUST_TRX_TYPES_ALL into the CTT_CLASS column. Note that the documented column list also includes RAC_BILL_TO_CUSTOMER_NAME, which is a legacy-named column originally derived from RA_CUSTOMERS but sourced from HZ_PARTIES/HZ_CUST_ACCOUNTS in current releases.

Underlying Base Objects

The view definition joins six documented base objects, all referenced through APPS synonyms:

• RA_CUST_TRX_LINE_GL_DIST_ALL (alias GD) — the receivable distribution table, filtered on ACCOUNT_CLASS = 'REC' and LATEST_REC_FLAG = 'Y', so only the current receivable-account distribution line is retained.
• RA_CUSTOMER_TRX (alias CT) — the Receivables transaction header, providing transaction number, date, currency, batch, and customer references.
• RA_CUST_TRX_TYPES_ALL (alias CTT) — the transaction type definition, supplying CTT_TYPE_NAME and CTT_CLASS.
• RA_BATCH_SOURCES_ALL (alias BS) — the batch source, supplying BS_BATCH_SOURCE_NAME and BATCH_SOURCE_TYPE.
• HZ_CUST_ACCOUNTS (alias HZCA) — the TCA customer account, joined to the transaction's bill-to customer.
• HZ_PARTIES (alias HZP) — the TCA party, supplying PARTY_NAME.

Joins are performed on CUSTOMER_TRX_ID, CUST_TRX_TYPE_ID, BATCH_SOURCE_ID, BILL_TO_CUSTOMER_ID/CUST_ACCOUNT_ID, and PARTY_ID, with organizational consistency enforced by matching GD.ORG_ID to CTT.ORG_ID and BS.ORG_ID. This makes the view multi-org safe with respect to the transaction type and batch source, though the caller must still supply the appropriate operating unit context.

Key Columns

• CTT_CLASS — the class of the Receivables transaction type (for example Invoice, Credit Memo, Debit Memo, Chargeback, Deposit, Guarantee), exposed from RA_CUST_TRX_TYPES_ALL.TYPE.
• CTT_TYPE_NAME — the descriptive name of the transaction type (RA_CUST_TRX_TYPES_ALL.NAME).
• TRX_NUMBER / TRX_DATE / COMPLETE_FLAG — transaction identifier, transaction date, and the completion indicator for the Receivables header.
• INVOICE_CURRENCY_CODE / GD_GL_DATE — the transaction currency and the GL date of the receivable distribution.
• BS_BATCH_SOURCE_NAME / BATCH_SOURCE_TYPE / BATCH_SOURCE_ID — the originating batch source and its type.
• PARTY_NAME / RAC_BILL_TO_CUSTOMER_NAME — the bill-to customer party name from TCA.
• Customer, batch, term, and salesrep references — CUSTOMER_TRX_ID, CUST_TRX_TYPE_ID, BATCH_ID, CT_TERM_ID, CT_SHIP_TO_CUSTOMER_ID, CT_PRIMARY_SALESREP_ID; plus audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), ROW_ID (RA_CUSTOMER_TRX ROWID), and SHIP_TO_SITE_USE_ID.

Common Use Cases and Queries

Typical usages include Asia/Pacific statutory reporting, transaction-type summary reporting grouped by CTT_CLASS, and reconciliation of the receivable distribution to the transaction header. A representative query filtering on the class of interest is:

SELECT trx_number, trx_date, ctt_class, ctt_type_name, party_name, invoice_currency_code, gd_gl_date, bs_batch_source_name FROM apps.jai_ar_trx_details_v WHERE ctt_class = 'INV' AND trx_date BETWEEN :p_from AND :p_to ORDER BY trx_date, trx_number;

To summarize transactional value by class and batch source:

SELECT ctt_class, bs_batch_source_name, COUNT(*) trx_count FROM apps.jai_ar_trx_details_v WHERE complete_flag = 'Y' GROUP BY ctt_class, bs_batch_source_name;

Because the view already restricts to the latest REC-account distribution and performs the requisite joins, it eliminates repeated construction of the Receivables-to-TCA join logic and is commonly used as a base query in JA localization reports and data conversions in both 12.1.1 and 12.2.2.