SAEXPGL Batch Extracts More Stores Than Expected

(Doc ID 1617273.1)

Last updated on MAY 01, 2017

Applies to:

Oracle Retail Sales Audit - Version 13.2.5 and later
Information in this document applies to any platform.
Checked for relevance as on 18-AUG-2015

Symptoms

The Sales Audit to General Ledger Export (SAEXPGL) batch extracts more stores than expected.

Steps to Recreate:

  1. In System Options:
    1. SA_SYSTEM_OPTIONS.UNIT_OF_WORK = 'S'        
  2. Create store day:
    1. Run sastdycr batch
  3. Import data into Retail Sales Audit (ReSA) through RTLOG for auditing.
    1. Run sagetref batch
    2. Run saimptlogi batch        
    3. Run saimptlogfin batch
  4. Calculate totals.
    1. Execute satotals batch
    2. Execute sarules batch
  5. Close store with Audit status as 'HQ' (errors pending) and Data status as 'Fully Loaded'.
    1. Go to ReSA Error List page and check store override checkbox.  Do not check HQ override checkbox, and do not fix errors.             
    2. Manually update Data status to Fully Loaded            
    3. Close Store           
  6. Export audited data   
    1. Execute saexpgl batch
  7. Validate actual result with expected result


Observations:  When there are errors in the SA_ERROR table and SA_ERROR.HQ_OVERRIDE='N' and SA_SYSTEM_OPTIONS.UNIT_OF_WORK='S', record should not export.    However, we see data in STG_FIF_GL_DATA and SA_EXPORTED table for this condition, which is not expected.   

 

Cause

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