My Oracle Support Banner

ER: Sales Integrated After Store Close/Snapshot Taken Should Update The Snapshot (Doc ID 3005627.1)

Last updated on FEBRUARY 20, 2024

Applies to:

Oracle Retail Enterprise Inventory Cloud Service - Version 23.2 and later
Information in this document applies to any platform.

Goal

DESCRIBE HOW THE CURRENT PRODUCT FUNCTIONALITY IS INSUFFICIENT
==============================================================
Currently After Store Close is specifically designed for the snapshot and activation of the stock count to occur right after the store closes on the day in question. From that time forward, any sales processing becomes late. So sales on the day of the count are very specifically pulled out and processed as late sales by design. In order to properly perform an After Store Close, you should a) close the store, b) take the snapshot to start the count, c) upload the count.

The new scenario can be reproduced at will with the following steps:

This is our scenario:
a) Close the store,
b) Take the snapshot to start the count
c) Count the Store in 3rd party
c.1) Sales integrated for count day which were already counted
c.2) Returns integrated for count day which were already counted
c) Upload/Authorize the count on the next day

There is nothing that can be done process wise to handle this as sales integration is not disabled when a store is closed for counting. Sales keep coming into SIOCS as they are being processed by external systems and that processing time could take more than the end of day, that is perfectly normal.
With this in mind, SIOCS will use the counted quantity which already included the sale (because the item was physically taken by the customer) and double counts by doing an inventory shift again.



PROVIDE A DETAILED DESCRIPTION OF THE ENHANCEMENT REQUEST
=========================================================
The count process needs to handle when sales are still being processed for the already closed day after the snapshot has been taken, these sales will need to be updating the snapshot to avoid potentially double counting.

1. Close the store (will not stop integration of sales to SIOCS)
2. Take the snapshot to start the count
3. Count the Store in 3rd party
3a. Integration running: more sales/returns are integrated for Count Day which should have been included in the Snapshot
4. On the next day (where they are open and trading), Upload/Authorize the count with the Count Day stock positions After Store Close

So, what we are asking is that ALL sales for the Count Day are considered on the Count Snapshot, even if they are integrated later (e.g.: on the next day).
Keep in mind that sales could still be coming in to the system the entire time between the snapshot and the upload of the 3rd party file as they have said some of their sales will be processed on the following day.



DESCRIBE HOW THIS ENHANCEMENT WILL BENEFIT YOUR BUSINESS
========================================================
If sales from the closed day prior to counting are integrated after the snapshot they should be accounted for by the snapshot updating with the correct figures. This will prevent double counting or returns being unaccounted for if the sales are integrated after the count and before the count is uploaded on the next day after trading has started.
 

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.