MISSING_TRAN_BIG_GAP Error Is Raised When POS Tran_no Recycle Back To 1 (Doc ID 2857390.1)

Last updated on DECEMBER 12, 2023

Applies to:

Goal

MISSING_TRAN_BIG_GAP error is raised when POS tran_no recycle back to 1.

For example, when POS transaction number recycles from 9999 to 1 then MISSING_TRAN_BIG_GAP error is raised with the range between 1 and 9999 missing.

This will be a lot of overhead to verify the range of each missing transaction range.

This should be a common issue for all retailer which POS tran no has limit and recycle often.

Please provide a solution or workaround to not raise the MISSING_TRAN_BIG_GAP error when POS tran no recycle back to 1.
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.