My Oracle Support Banner

Creditnoteautomatch Not Matching Credit Note With Credit Note Request From Which it Was Created (Doc ID 2690812.1)

Last updated on JULY 15, 2020

Applies to:

Oracle Retail Invoice Matching - Version 16.0.1 and later
Information in this document applies to any platform.

Symptoms

Creditnoteautomatch batch is not matching credit note with credit note request from which it was created.
This happens when there are other standalone credit note requests for the same match key say PO/Location etc.

Steps to Recreate:

1. Ensure that IM_MATCH_POOL_CONFIG table has the following setup:
    MATCH_TYPE              PRIORITY              KEY_ATTRIBUTES
    ---------------------------------------------------------------------------------------------------------------------------
    CRDNT-CRDNRQ              1                 CREDIT_NOTE_REQUEST_ID
    CRDNT-CRDNRQ              2                 ORIGINAL_INVOICE_ID
    CRDNT-CRDNRQ              3                 PO_LOCATION

2. Create multiple credit note requests for the same Purchase Order (PO) / Location.

3. Create a credit note from one of the above credit note requests and notice that REF_CNR_EXT_DOC_ID is populated for credit note.

4. Run reimcreditnoteautomatch batch and notice that credit note is not matched with the credit note request from which it was created.

Cause

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
Symptoms
Cause
Solution
References


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