My Oracle Support Banner

VOID_LATE_CREDIT_NOTE_REQUESTS Option is Not Available in From ReIM 13.2 (Doc ID 1609447.1)

Last updated on JANUARY 28, 2021

Applies to:

Oracle Retail Invoice Matching - Version 13.2.6 to 13.2.7 [Release 13.2]
Information in this document applies to any platform.


The VOID_LATE_CREDIT_NOTE_REQUESTS option is not available in from ReIM 13.2. Due to this issue, credit note requests are not getting converted into debit memos.

Steps to Reproduce:

  1. Create a purchase order (PO); ship and receive it. 
  2. Create an invoice such that it has either Qty or Cost higher than that of the order. 
  3. Resolve the discrepancy and run the rollup batch. (Ensure that the supplier’s send debit memo option is set to “Late” such that a credit note request is created during rollup). 
  4. Move the VDATE such that VDATE is later than due_date - DEBIT_MEMO_SEND_DAYS of SYSTEM_OPTIONS. 
  5. Run the Posting batch. 
  6. Notice that a new debit memo is created for the Credit Note Request, and the status of the credit note request moves to VOID status.  This makes it unavailable for matching if a credit note is sent by the supplier later.


Background on the VOID_LATE_CREDIT_NOTE_REQUESTS functionality introduced in ReIM 13.1:

Originally,  there was code in the application that when a supplier was flagged as 'Create Debit memo only when the Credit Note is Late', we would generate the ‘Debit Memo’ when the credit note was deemed late (when the routing date was passed), and we would void the Credit Note Request with the expectation that the Credit Note would never come in.   

Certain customers wanted to use the Credit Note Matching functionality but also create a Debit Memo immediately after the Credit Note Request was created.    This would mean that we would now be accepting both a Debit Memo and a Credit Note, which would mean a double deduction from the supplier.   The solution for this would be to void the debit memo automatically when the Credit Note Request is matched to the credit note.

So, we added the VOID_LATE_CREDIT_NOTE_REQUESTS .properties file setting to allow the retailer to select which process they wanted to follow.   If the VOID_LATE_CREDIT_NOTE_REQUESTS setting is set to ‘TRUE’, we execute the original code assuming that when the routing date passes, the system will generate a Debit Memo and void the Credit Note Request, anticipating that no Credit Note will come in.

Alternatively, if VOID_LATE_CREDIT_NOTE_REQUESTS is set to ‘FALSE, then when the routing date passes we still generate the Debit Memo but leave the CNR as 'Approved', expecting the Credit Note to be entered and matched.  When the Credit Note is matched to the Credit Note Request, we also will automatically reverse the Debit Memo with a Credit Memo.





To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.