My Oracle Support Banner

Cancelled Timeout Transaction Remains in the InProcess Directory Until Next Transaction Is Burned (Doc ID 1932952.1)

Last updated on NOVEMBER 02, 2017

Applies to:

Oracle Retail Point-of-Service - Version 14.0.1 to 14.0.2 [Release 14.0]
Information in this document applies to any platform.

Symptoms

In Oracle Retail Point of Service (ORPOS) 14.0.x, when a transaction times out on the Store Order shipping information screen, a .wip file gets created in the pos/bin/archives/inprocess directory and remains there until the next transaction is burned.


Steps to Reproduce:

      Pre-Requisite:  Set the following in the domain.properties on POS server and client.

TransactionIDBarcodeDateFormat=yyyyMMdd
  1. Select F3 POS.
  2. Enter item 1234.
  3. Select F4 Item.
  4. Select F9 More and F7 Shipping.
  5. Leave the application to timeout on the Store Order Shipping Item Info screen for 15 mins. 
  6. Note that a *.wip file is created in the Client/pos/bin/archives/inprocess directory.  This does not get processed to the database until the next transaction is burned in POS.

 

Cause

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.