RA_CUSTOMER_TRX_ALL table overview

RA_CUSTOMER_TRX_ALL
customer_trx_id	trx_number	bill_to_customer_id	trx_date

The RA_CUSTOMER_TRX_ALL table stores invoice, debit memo, commitment and credit memo header information. Each row includes general invoice information such as customer, transaction type, and printing instructions.

Invoices, debit memos, credit memos, and commitments are all distinguished by their transaction types stored in RA_CUST_TRX_TYPES_ALL (cust_trx_type_id).

COMPLETE_FLAG stores ’Y’ for Yes and ’N’ for No to indicate if your invoice is complete. When you complete an invoice, Oracle Receivables creates your payment schedules and updates any commitments against this invoice. Before an invoice can be completed, it must have at least one invoice line, revenue records must exist for each line and add up to the line amount, and a sales tax record must exist for each line.

Each of the transactions is stored as a unique record, based on the primary key, customer_trx_id. The transaction number, transaction date and billing customer are stored in the trx_number, trx_date and bill_to_customer_id columns, respectively.

Additional information stored in this table includes ship-to customer, document sequence number, currency code and a transaction complete flag.

SOLD_TO_CUSTOMER_ID, SOLD_TO_SITE_USE_ID, BILL_TO_CUSTOMER_ID, BILL_TO_SITE_USE_ID, SHIP_TO_SITE_USE_ID, PRINTING_OPTION, PRINTING_PENDING, TERM_ID, REMIT_TO_ADDRESS_ID, PRIMARY_SALES_REP_ID, and INVOICE_CURRENCY_CODE are required even though they are null allowed.