Cost Pre-Match Sets Invoice Status To ‘unresolved Match’ When There Are No Discrepancies
(Doc ID 2933383.1)
Last updated on MARCH 07, 2023
Applies to:
Oracle Retail Invoice Matching Cloud Service - Version 19.3 and laterInformation in this document applies to any platform.
Symptoms
On : 19.3 version, Document Matching
ACTUAL BEHAVIOR
---------------
Cost Pre-Match sets invoice status to ‘unresolved match’ when there are no discrepancies
EXPECTED BEHAVIOR
-----------------------
Cost Pre-Match should status to ‘ready for match’ when there are no discrepancies
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create PO, 1 item in it
2. Create an invoice for that PO, same qty, same unit cost
3. Run automatch batch with cost pre-match on
4. Observe the invoice status changes to ‘unresolved-match’
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 |