MISSING_TRAN_BIG_GAP Error Occurs in ReSA After Rollover of Transactions Number Sequence (Doc ID 1622676.1)

Last updated on MARCH 07, 2017

Applies to:

Oracle Retail Sales Audit - Version 13.2.3 and later
Information in this document applies to any platform.
Checked for relevance on 29 Aug 2015

Goal

In Oracle Retail Sales Audit (ReSA), transaction numbers are maintained in the SA_STORE_POS table from 1 to 9999, and the point of service (POS) system generates them in this same range.  When the range reaches 9999 and resets to 1, note an SA_ERROR update with a MISSING_TRAN_BIG_GAP error.

Why is this happening after the transaction sequence rollover?

Solution

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