How to Deal with the Case the Transaction Date of Credit Memo Is Cleared After Autoinvoice Rejects the CM. (Doc ID 2131402.1)

Last updated on AUGUST 11, 2017

Applies to:

Oracle Receivables - Version 12.1.3 and later
Information in this document applies to any platform.

Goal

 When Autoinvoice rejects Credit Memo(CM) due to the error like the target invoice has already been applied to receipt, in the interface table(RA_INTERFACE_LINES_ALL), the Transaction date of CM is set to null and RESET_TRX_DATE_FLAG is set to Y.

This is intended behavior by <Bug 16185803> THE SYSTEM IS NOT DOING THE ROLLBACK OF THE TXN DATE WHEN THE AUTOINVOICE.
  - <Document 1547621.1> Autoinvoice Issue: No Rollback Of The Transaction Date When The Autoinvoice Fails

Once the cause of the error gets fixed and run Autoinvoice again, the original TRX_DATE of CM is not roll-backed and the same date as GL date will be set to TRX_DATE automatically.
Therefore, another unexpected error can occur in some cases.

For example, check the TRX_DATE in RA_INTERFACE_LINES_ALL and cross-check against the Invoice's TRX_DATE and ensure the CM's TRX_DATE comes on or after the TRX_DATE of the invoice. If CM's TRX_DATE (set from CM' GL date) < TRX_DATE of the invoice, the error below is thrown and Autoinvoice fails again.

AR_RAXTRX-1771: CM date cannot precede the date of the transaction being credited.
   Reference to <Document 1138254.1> Listing of AutoInvoice Error Messages and Troubleshooting Tips to Resolve each Error

How can this situation be dealt with?

 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms