SIM Stock Counts Snapshot Time Saved in Store Timezone and Not GMT (Doc ID 1903936.1)

Last updated on AUGUST 17, 2016

Applies to:

Oracle Retail Store Inventory Management - Version 13.1.6 to 13.1.9 [Release 13.1]
Information in this document applies to any platform.

Symptoms

When performing a unit stock count in Store Inventory Management (SIM) 13.1.x, snapshot time is saved in the database using the store timezone, which is different from the physical count timestamp which is saved in Greenwich Mean Time (GMT).  This issue could impact the sales integration process while stock counts are occurring.

This same behavior does not occur in ad-hoc stock counts, where the snapshot is taken for each item when they are scanned/counted; the physical count timestamp and snapshot are both saved in GMT.


Steps to Reproduce:

  1. On a PC that has a timezone different from GMT, schedule/extract a unit stock count.
  2. Using the PC, take the snapshot and count a few items.  Alternatively, count some items using the handheld terminal (HHT; the snapshot will be taken when the first item is scanned).
  3. Check the snapshot and physical count timestamp information in the database.  The snapshot has the store's timezone, which the count is saved in GMT.  This does not happen in ad-hoc counts; all dates are saved in GMT.

 

Cause

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 hundreds of Community platforms