POS Transactions Are Not Being Processed for Repeated Transaction Numbers for Serial Items (Doc ID 1916155.1)

Last updated on NOVEMBER 18, 2016

Applies to:

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

Symptoms

NOTE: The issue described in this note was observed in multiple SIM versions. This note provides solutions for SIM versions 13.2.X, 14.0.X and 14.1.X. Please download and apply the correct solution based on your SIM version.

 
In Store Inventory Management (SIM) , find that when Oracle Retail Point-of-Service (ORPOS) sends two transactions containing a serialized item with the same TransactionID across different business days, the serial number's status is not getting updated to "Sold" in SIM.  This results in the reflection of an incorrect UIN Inventory status.  The same UIN can be sold again in POS.


Steps to Reproduce:

  1. Complete a sale of a serialized item in ORPOS.
  2. Complete another sale of the same serialized item using a different serial number on ORPOS such that the transaction number is the same as the first sale.
  3. Transactions are sent to SIM via WebServices.
  4. Note that the UIN of the serial item is not updated to 'Sold' status, even though the message is processed from the STAGED_MESSAGE table in SIM.

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