Late Sales Integrated After Count Date are Not Correctly Accounted For when Using Daily Sales Processing and After Store Close
(Doc ID 2987320.1)
Last updated on FEBRUARY 20, 2024
Applies to:
Oracle Retail Enterprise Inventory Cloud Service - Version 23.2 and laterInformation in this document applies to any platform.
Goal
On : 23.2 version, Inventory Management
ACTUAL BEHAVIOR
---------------
Late Sales integrated after Count Date are not correctly accounted.
In a Unit & Amount 3rd Party Stock Count, which is uploaded and approved after the count date, it was noticed that Late Sales are not accounted correctly in the count snapshot.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
0. Configuration: Daily Sales Processing and After Store Close
1. EICS
a. Create a Unit & Amount Product Group and its components (all store).
b. Schedule the Product Group for the next possible date (e.g.: sysdate+1).
2. Take snapshot on the scheduled count date (e.g.: 1AM) and do nothing else
a. Wait 2 days - counting is occurring on 3rd party app.
3. Upload Results from 3rd party file with timestamp count date as the day of the count
4. Integrate a sale for the item with transaction date the day of the count date but before the item count timestamp
5. Integrate a sale for the counted item with a timestamp greater than the item count timestamp
6. Verify count results in EICS Authorize Count screen. No update is done to the snapshot
7. Authorize the Count
8. Check Stock in SIOCS:
- Item Stock was discounted with all sales from the counted quantity (handled as late sales after count),
- As Count is "After Store Close", sales on the day of the count should not be considered and not affect SOH, as they happened before the count (e.g.: 92928411).
In the case of item 92928411, there was a snapshot, then a sale, then a count and then another sale on the day of the count. Only sales registered after the count date should decrement stock.
In summary, all sales on the day of the count should affect the snapshot and not SOH as sales after the count. SOH for item 92928411 should have been 4 and not 2.
Solution
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
Goal |
Solution |
References |