IM_RECEIVER_COST_ADJUST Not Storing Timestamp,while Settingup Data From Summary Match UI
(Doc ID 2962914.1)
Last updated on JULY 24, 2023
Applies to:
Oracle Retail Invoice Matching Cloud Service - Version 23.1 and laterInformation in this document applies to any platform.
Symptoms
IM_RECEIVER_COST_ADJUST not storing timestamp,while settingup data from Summary Match UI
Steps To Recreate:
1. Have an Unresolved Merchandise invoice with cost discrepancy(Invoice cost and Receipt cost are not same).
2.To resolve the discrepancy do a Summary match for the invoice(FROM UI) - IMCS>>go to Summary match Screen>> Order no details >> Select both invoice & receipt>> Click Detail Match >> Resolve >> Select Invoice Unit Cost >> Select 500 (Receiver Cost Adjustment) as the Reason_code and click on done.
3. Check table IM_RECEIVER_COST_ADJUST respective to the ORDER_NO and ITEM.
4.Check the below query
SELECT TO_CHAR(IMR.CREATION_DATE, 'YYYY-MM-DD HH24:MI:SS') AS CREATION_DATE, TO_CHAR(IMR.LAST_UPDATE_DATE, 'YYYY-MM-DD HH24:MI:SS') AS LAST_UPDATE_DATE,IMR.* FROM IM_RECEIVER_COST_ADJUST IMR
5. The CREATION_DATE and LAST_UPDATE_DATE does not give timestamp.
.
Changes
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 |
Changes |
Cause |
Solution |
References |