Application Restart in the Middle of Retrieval of Suspended Transaction Results in Missing Transaction in Database (Doc ID 1961174.1)

Last updated on AUGUST 19, 2015

Applies to:

Oracle Retail Point-of-Service - Version 13.3 and later
Information in this document applies to any platform.

Symptoms

In Oracle Retail Point of Service (ORPOS), a transaction goes missing in the database if the application is restarted in the middle of a transaction in which a suspended transaction is being retrieved.


Steps to Reproduce:

  1. Log in to ORPOS
  2. Scan an item on Sell Item screen and suspend this transaction
  3. Log in to ORPOS again
  4. Retrieve the suspended transaction (Do not complete this transaction)
  5. Restart ORPOS
  6. Log in to ORPOS again
  7. Perform a sale transaction tendered with cash
  8. Note that transaction # from step 4 goes missing in the database

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