Mass Fixing SKU_NOT_FOUND Errors Leaves Unaudited Out-of-Balance Transactions
(Doc ID 2853682.1)
Last updated on JANUARY 11, 2024
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version NA and laterInformation in this document applies to any platform.
Symptoms
Mass fixing SKU_NOT_FOUND errors leaves unaudited Out-of-Balance transactions.
Steps to reproduce:
---------------------------
1. Import sales files with non-existing items, resulting on SKU_NOT_FOUND error.
2. Audit Store.
3. Fix the SKU_NOT_FOUND using an existing RMS item that has a different selling unit retail.
4. Observe the error disappears from the Store Day Audit screen.
5. Go to the fixed transaction - notice the Out-of-Balance amount.
6. Click on Refresh Errors.
7. Save and go back to the Store Day Audit Screen.
8. Observe the TRAN_OUT_BAL error.
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 |