This table stores all transactions except adjustments and miscellaneous cash receipts. Oracle Receivables updates this table when activity occurs against an invoice, debit memo, chargeback, credit memo, on account credit, or receipt.
Oracle Receivables groups different transactions by the column CLASS. These classes include invoice (INV), debit memos (DM), guarantees (GUAR), credit memos (CM), deposits (DEP),
chargebacks (CB), and receipts (PMT).
When a receipt is applied, Oracle Receivables updates AMOUNT_APPLIED, STATUS
and AMOUNT_DUE_REMAINING. STATUS changes from OP to CL for any transaction that has an AMOUNT_DUE_REMAINING value of 0.
ACTUAL_DATE_CLOSED and GL_DATE_CLOSED are populated with the date of the latest transaction. Oracle Receivables stores debit items such as invoices, debit memos, chargebacks, deposits, and guarantees as positive numbers in the AMOUNT_DUE_REMAINING and AMOUNT_DUE_ORIGINAL columns. Credit items such as credit memos and receipts are stored as
If you create a debit memo reversal when you reverse a receipt, Oracle Receivables creates a new
payment schedule record for the debit memo and fills in REVERSED_CASH_RECEIPT_ID with the CASH_RECEIPT_ID of the receipt that was reversed.
This table stores records for cash and credit memo applications. The APPLICATION_TYPE column stores CASH for receipt applications and CM for credit memo applications. Each row in this table includes the amount applied, status (APP or UNAPP), and account code combination information.
When a cash receipt is initially created, Receivables creates a row in this table for the cash receipt amount with a status of UNAPP. For each subsequent application, Receivables creates two rows: one row with a status of APP for the amount that is applied to the invoice, and one row with status of UNAPP for the negative of the amount that is applied. If a cash application is reversed, Receivables creates two new rows: one row with status of APP for the original application's inverse amount (the negative of the original application amount), and one row with a status of UNAPP for the positive amount of the application that is reversed.
Credit memo applications do not have rows with a status of UNAPP, and use only rows with a status of APP.
The sum of the AMOUNT_APPLIED column for cash applications should always equal the amount of the cash receipt. A negative value in the AMOUNT_APPLIED column becomes a debit when this application is posted to General Ledger.
The CUSTOMER_TRX_ID and PAYMENT_SCHEDULE_ID columns also identify the transaction that is actually applied. The APPLIED_CUSTOMER_TRX_ID and APPLIED_PAYMENT_SCHEDULE_ID columns identify the invoice or credit memo that receives the application.
Post a Comment
Note: Only a member of this blog may post a comment.