Header Level Invoices Are Being Incorrectly Flagged As Cost Pre-match
(Doc ID 2421807.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Retail Invoice Matching - Version 16.0.1 and later
Information in this document applies to any platform.
Header level invoices are being incorrectly flagged as cost pre-matched when they should not be.
As per Cost pre-match logic :
1. Only if invoice detail is available;
2.Invoice unit costs compared to PO costs;
3.Executed prior to receipt of goods
4.Imported goods – verify costs before receiving.
Steps to Reproduce:
1.Set the Match key to PO for the supplier you want to create Invoice
2.Create a header level invoice for a PO whose supplier is same for which Match key is set mentioned in step 1.
3.Execute Auto match job and check cost pre-match flag in IM_DOC_HEAD table for the same Invoice created in step 2.
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