Transactions with Credit Applied and SLA Link R12
Accounting Data Model – Transaction With Credit Applied
•Where postable <> ‘N’
•Distributions stored in AR_DISTRIBUTIONS_ALL (source_table=RA)
•Debit and credit amounts should match
•Amount prorated for each Invoice line
•No extra row in XLA.XLA_TRANSACTION_ENTITIES
Important columns in the AR_RECEIVABLE_APPLICATIONS table include:
RECEIVABLE_APPLICATION_ID column
AMOUNT_APPLIED column
STATUS column
PAYMENT_SCHEDULE_ID column
CODE_COMBINATION_ID column
CASH_RECEIPT_ID column
APPLIED_PAYMENT_SCHEDULE_ID column
APPLIED_CUSTOMER_TRX_ID column
The AR_RECEIVABLE_APPLICATIONS table stores account distributions for receipt and credit memo applications and maps the application transaction to the applied transaction. Each accounting distribution is stored as a unique record, based on the primary key receivable_application_id. The payment_schedule_id column links the receipt or credit memo to its payment schedule in the AR_PAYMENT_SCHEDULES table. The cash_receipt_id column stores the receipt ID of payment transactions, while the cust_trx_id column, which is not shown, stores the transaction ID for credit memo transactions. The applied_payment_schedule_id and applied_customer_trx_id columns reference the transaction to which this record applies.
The status column describes the state of the application transaction. For credit memos, the status is always APP to identify the credit memo as applied. For receipt transactions, valid status values are APP, UNAPP, UNID, REV, NSF, and STOP. The code_combination_id column stores the general ledger account for the application transaction, based on the status. The amount_applied column stores the amount of the receipt or credit memo as a positive value.