Search Results ra_customer_trx_u3

Overview

The AR.RA_CUSTOMER_TRX_ALL table is the master header table for Oracle Receivables transactions in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores invoice, debit memo, credit memo, commitment, and bills receivable header information. One row exists for each transaction created in Receivables, distinguished by its transaction type stored in RA_CUST_TRX_TYPES_ALL. The table is defined with 187 columns in the AR schema and is classified as VALID in ETRM. According to the Data Vault classification heuristic mined from the foreign key structure, this object is modeled as a hub, reflecting its role as the central business key anchor around which satellite and link structures are organized.

Key Information Stored

The primary key is CUSTOMER_TRX_ID, enforced by the unique index RA_CUSTOMER_TRX_U1. Two additional unique indexes represent business-key candidates: RA_CUSTOMER_TRX_U2 on REVERSED_CASH_RECEIPT_ID and RA_CUSTOMER_TRX_U3 on the composite (DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE), which governs document sequencing. The most significant columns include:

• TRX_NUMBER — the user-visible transaction number.
• CUST_TRX_TYPE_ID — foreign key to RA_CUST_TRX_TYPES_ALL, determining transaction classification.
• TRX_DATE and GL_DATE-related accounting context via SET_OF_BOOKS_ID.
• SOLD_TO_CUSTOMER_ID, BILL_TO_CUSTOMER_ID, SHIP_TO_CUSTOMER_ID, PAYING_CUSTOMER_ID — customer role references to HZ_CUST_ACCOUNTS.
• SOLD_TO_SITE_USE_ID, BILL_TO_SITE_USE_ID, SHIP_TO_SITE_USE_ID — site use references to HZ_CUST_SITE_USES_ALL.
• TERM_ID — payment terms referencing RA_TERMS_B, with TERM_DUE_DATE.
• INVOICE_CURRENCY_CODE — currency referencing FND_CURRENCIES, with EXCHANGE_RATE, EXCHANGE_RATE_TYPE, and EXCHANGE_DATE.
• COMPLETE_FLAG — Y/N indicator; completion creates payment schedules and updates commitments.
• PREVIOUS_CUSTOMER_TRX_ID — links a credit memo to the invoice it credits; null for on-account credits.
• INITIAL_CUSTOMER_TRX_ID — links an invoice to its originating commitment.
• PRIMARY_SALESREP_ID — references RA_SALESREPS_ALL.
• DOC_SEQUENCE_ID and DOC_SEQUENCE_VALUE — document sequencing assignment.
• BATCH_SOURCE_ID — references RA_BATCH_SOURCES_ALL.

Several columns including SOLD_TO_CUSTOMER_ID, BILL_TO_CUSTOMER_ID, TERM_ID, PRINTING_OPTION, PRINTING_PENDING, REMIT_TO_ADDRESS_ID, PRIMARY_SALESREP_ID, and INVOICE_CURRENCY_CODE are documented as required even though they are null-allowed at the database level.

Common Use Cases and Queries

Typical reporting queries retrieve transaction headers joined to lines, distributions, and payment schedules. A common pattern joins RA_CUSTOMER_TRX_ALL to RA_CUSTOMER_TRX_LINES_ALL on CUSTOMER_TRX_ID, and to AR_PAYMENT_SCHEDULES_ALL for open balance analysis. Document sequencing queries leverage the RA_CUSTOMER_TRX_U3 index to retrieve transactions by sequence range. Credit memo traceability queries use the self-referencing PREVIOUS_CUSTOMER_TRX_ID relationship. Commitment-to-invoice linkage queries use INITIAL_CUSTOMER_TRX_ID. Common reporting includes aging by customer, revenue by sales representative, tax reporting by legal entity, and bills receivable status via BR_AMOUNT, BR_UNPAID_FLAG, and BR_ON_HOLD_FLAG.

Related Objects

• RA_CUSTOMER_TRX_LINES_ALL — child table via CUSTOMER_TRX_ID.
• AR_PAYMENT_SCHEDULES_ALL — child table via CUSTOMER_TRX_ID; holds installment and balance data.
• RA_CUST_TRX_LINE_GL_DIST_ALL — accounting distributions via CUSTOMER_TRX_ID.
• AR_RECEIVABLE_APPLICATIONS_ALL — references both CUSTOMER_TRX_ID and APPLIED_CUSTOMER_TRX_ID.
• RA_CUST_TRX_TYPES_ALL — parent via CUST_TRX_TYPE_ID.
• HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES_ALL — customer and site use parents.
• RA_TERMS_B — payment terms parent via TERM_ID.
• RA_SALESREPS_ALL — sales representative parent.
• AR_ADJUSTMENTS_ALL — child for adjustments against transactions.
• RA_CUST_TRX_LINE_SALESREPS_ALL — child for sales credit allocation.