My Oracle Support Banner

Saexpgl - Processing Same Store/day Over And Over And Creating Duplicate IF_ERRORS (Doc ID 2830857.1)

Last updated on JANUARY 04, 2022

Applies to:

Oracle Retail Sales Audit - Version 16.0.2 and later
Information in this document applies to any platform.

Symptoms

Saexpgl - Processing same store/day over and over and creating duplicate IF_ERRORS

When saexpgl is set for multi-threading (64 threads) and there are any store/total/rollup values not mapped to G/L (i.e no record in SA_FIFL_GL_CROSS_REF) this results in a store/day record being processed by many of the threads during the same run and duplicates of errors in the IF_ERRORS table.

Steps To Recreate:

1) Setup saexpgl to be multi-threaded ( 64 threads).
2) Make sure certain store/total/rollups values have no corresponding G/L mapping in SA_FIF_GL_CROSS_REF.
3) Load sales for a day.
4) Run satotals/sarules.
5) Run saexpgl.

Changes

 

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!


In this Document
Symptoms
Changes
Cause
Solution
References


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