Enhancements Made to Oracle Retail Point of Service to Minimize Transaction Sequence Number Gaps in the Store Database
Last updated on APRIL 25, 2017
Applies to:Oracle Retail Point-of-Service - Version 13.3 and later
Information in this document applies to any platform.
The purpose of this article is to provide details on product enhancements that have been made to the transaction persistence feature. There have been cases in which transaction sequence numbers are skipped in the Transaction Table due to application crashes, timeouts on a few workflows, logical errors in the code when a user escapes back from one screen to the previous one, etc.
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