My Oracle Support Banner

Third Party Stock Count Item Not Counted in File Receives Inventory Adjustment (Doc ID 2479349.1)

Last updated on NOVEMBER 01, 2021

Applies to:

Oracle Retail Store Inventory Management - Version 16.0 and later
Information in this document applies to any platform.


Although the sale transaction date for an authorized Third Party Stock Count item (not counted in file) was later than the scheduled count date, Oracle Retail Store Inventory Management (SIM) is treating incorrectly the sale transaction as late sale and applying unit and amount adjustments against it.

Steps to Recreate:

Configure SIM for:

1.  Schedule a 3rd party Unit and Amount Count - Auto Authorize - All Departments.
2.  On the scheduled count date, trigger the 3rd party count snapshot as AFTER STORE CLOSE.
3.  Review the STOCK_COUNT_LINE data and choose two items which were extracted to be included for the unit and amount count process.
4.  Prepare a third party count file and do not include the two items from step (3).
5.  On the morning of Count Date + 1 , process the third party count file through SIM which should auto authorize and complete without any issues.
6.  Review the STORE_ITEM_STOCK.  

  LAST_STK_CNT_APPROVE_DATE = Count Authorization Date/Time

7.  Prepare a sale for one of the items from step (3) and a return for the other.  The transaction date in the THEAD rows must equal count date + 1  and will have a timestamp value of 000000.
8.  Process the sales data through RetailSaleAuditImport.
9.  After the sales have processed, review STORE_ITEM_STOCK again.  
Notice that SIM is treating these Sales transactions as late Sales and applying unit and amount adjustments against them.   




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

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