My Oracle Support Banner

Incorrect Last Approved Count Dates Recorded For 3rd Party Unit&Amount Counts For Certain Items (Doc ID 2466159.1)

Last updated on FEBRUARY 27, 2019

Applies to:

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


On : 16.0.1 version, Stock Movement (Inv Control)

SIM is recording incorrect last approved count dates for certain item scenarios related to 3rd party unit and amount Auto-Authorise counts with Daily Processing in place.

These are causing an impact when these items have transactions posted the next day while count is still active.

Non-ranged items added to a 3rd party count file and items which were extracted for a unit and amount count but not submitted within the 3rd party count file are receiving a last approved date = count auth date instead of matching the stock count date -- this needs to happen because their last approved dates, for Daily processing, need to align to an "after store close" scenario purely based on date.

If transactions for these items are applied and dated for count date + 1, while the count is still active the next day, after the count is authorized these items are treated as late sales/returns and their transaction quantities are reversed in SIM incorrectly.

The issue can be reproduced at will with the following steps:

  1. Create a 3rd party unit and amount count set to auto-authorize. All variance values in the group are set to 0, all statuses checked, all SOH compares are checked, breakdown: Department and all departments will be counted.
  2. During the day of the scheduled stock count trigger a SIM snapshot for all child counts and ensure “AFTER STORE CLOSE” is the option used.
  3. Prepare a 3rd party count file include an item expected on the count, an item not expected (valid non-ranged item), and do not include an item expected on stock count line (in our example we chose an item with an item which already had stock on hand = 0, so the outcome of the count would be zero on hand with no variance followed by a next-day return of +10).
  4. On the morning after the scheduled count date, submit sales/return transactions for the items but date them for count date + 1. The transactions are applied to stock on hand.
  5. Process the 3rd party count file and review results. Items included on 3rd party file and already expected on the count receive an approval date = count date.
    - Items included on 3rd party file and not expected (non ranged) initially on the count receive an approved date = count authorization even though they should have been considered counted after store close on the count date.
    - Items expected on the count but not counted also receive an approved date = count authorization.
    Even though they were not included in the 3rd party file, because the count was to have happened “after store close” and because the system is set to Daily Processing, their approval dates should have also been set to the count date.
  6. Review final stock on hand balances. Items added to the count or not provided by the third party have incorrect stock on hands.
  7. Review results in Retail Merchandising System (RMS) after it’s final processing – RMS has the proper results.


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

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