Oracle Accounts Receivables (AR) - key Tables

AR_RECEIVABLES_TRX_ALL
This table links accounting information with your Receivables
Activities. Possible types of activities include Adjustment,
Miscellaneous Cash, and Finance Charges. If your type is Miscellaneous
Cash, you can associate either a distribution set or a standard
accounting flexfield to your Receivables Activity. Oracle Receivables
uses one row for each activity. You use your receivables activities to
speed receipt entry and generate finance charges. The other types of
activities that were valid in release 9 and no longer valid in Release 10
were converted (as part of the upgrade) such that the actual accounting
flexfield CODE_COMBINATION_ID is stored in the table instead of the
RECEIVABLES_TRX_ID. In Release 9, all of these references were in
AR_BATCH_SOURCES; they are now in
AR_RECEIPT_METHOD_ACCOUNTS_ALL. The primary key for this
table is RECEIVABLES_TRX_ID.

 

AR_RECEIVABLE_APPLICATIONS_ALL
This table stores all accounting entries for your cash and credit memo
applications. Each row includes the amount applied, status, and
accounting flexfield information. Possible statuses of your applications
include APP, UNAPP, ACC, and UNID. You use this information to
determine the applications of your payments or credit memos.
CONFIRMED_FLAG is a denormalization from
AR_CASH_RECEIPTS_ALL.

 If the cash receipt is not confirmed, the
applications of that receipt are not reflected in the payment schedule of
the transaction it is applied against. There are two kinds of applications:
CASH and CM (for credit memo applications). This is stored in the
column APPLICATION_TYPE.

CASH applications represent applications of a cash receipt. When a cash receipt is initially created, a row is created in this table that has a status of UNAPP for the amount of
the cash receipt. Each subsequent application creates two rows – one
with a status of APP for the amount being applied to the invoice and
one with status UNAPP for the negative of the amount being applied. If
you reverse a cash application, a row with status APP with the inverse
amount of the original application (i.e. the negative of the original
application amount) is created. The corresponding UNAPP rows is also
created which will have a positive amount (the same amount as the
application being reversed). For example: UNAPP 100 creation of a
$100 cash receipt APP 60 application of $60 of this cash receipt
UNAPP –60 this row takes away (debits) unapplied APP –60
reversal of the $60 application UNAPP 60 this rows puts back
(credits) unapplied The sum of the AMOUNT_APPLIED column for
CASH applications should always equal the amount of the cash receipt.
CM applications, on the other hand, do not have rows of status UNAPP.
They only use rows with a status of APP. CASH_RECEIPT_ID stor es
the cash receipt identifier of the receipt you entered. Oracle Receivables
concurrently creates a record of this receipt in the
AR_CASH_RECEIPTS_ALL table.

This column is null for a credit memo application. CODE_COMBINATION_ID stores valid Accounting Flexfield segment value combinations that will be credited in the
General Ledger when this application is posted. A negative value in
AMOUNT_APPLIED becomes a debit. The STATUS of a receivable
application determines which flexfield account Oracle Receivables uses.
For example, if you enter a cash receipt of $500 as Unidentified, Oracle
Receivables creates a record in the
AR_RECEIVABLE_APPLICATIONS_ALL table with
AMOUNT_APPLIED = 500 and STATUS = ’UNID’. Oracle Receivables
uses the foreign key CODE_COMBINATION_ID to associate this
payment with the Unidentified flexfield account. CUSTOMER_TRX_ID,
CASH_RECEIPT_ID, and PAYMENT_SCHEDULE_ID identify the transaction that you are actually applying.
APPLIED_CUSTOMER_TRX_ID and APPLIED_PAYMENT_SCHEDULE_ID identify the invoice or credit memo that receives the application. For example, if you apply a receipt
against an invoice, Oracle Receivables creates a record in the
AR_RECEIVABLE_APPLICATIONS_ALL table. The CASH_RECEIPT_ID and the PAYMENT_SCHEDULE_ID of this record identify the receipt you are applying.
APPLIED_PAYMENT_SCHEDULE_ID and APPLIED_CUSTOMER_TRX_ID for this record belong to the invoice that is receiving the application. If you apply a credit memo against the invoice, Oracle Receivables creates a record in the AR_RECEIVABLE_APPLICATIONS_ALL table that has the
CUSTOMER_TRX_ID and the PAYMENT_SCHEDULE_ID of the credit
memo you are applying. The APPLIED_PAYMENT_SCHEDULE_ID
and the APPLIED_CUSTOMER_TRX_ID of this record belong to the
invoice that is receiving the application. If you combine an on account
credit and a receipt, Oracle Receivables creates a record in t he
AR_RECEIVABLE_APPLICATIONS_ALL table.

The PAYMENT_SCHEDULE_ID and the CASH_RECEIPT_ID of this record
identify the receipt. The APPLIED_PAYMENT_SCHEDULE_ID and the
APPLIED_CUSTOMER_TRX_ID of this record identify the on account
credit that you are combining with the receipt. The primary key for this
table is RECEIVABLE_APPLICATION_ID, which uniquely identifies the
transaction that created the row.