My Oracle Support Banner

SAEXPGL Batch Aborts Leaves Behind Locking Record In sa_store_day_read_loc Table (Doc ID 2742900.1)

Last updated on APRIL 14, 2021

Applies to:

Oracle Retail Merchandising Foundation Cloud Service - Version NA and later
Information in this document applies to any platform.

Symptoms


SAEXPGL batch when it aborts it leaves behind locking record in SA_STORE_DAY_READ_LOCK table.

Steps To Reproduce:

  1. Make sure sa_fif_gl_cross_ref table is missing a mapping records (store/total_id) on a month end.
  2. Fully audit and close the store so that totals can be exported to GL.
  3. Run saexpgl and notice that saexpgl aborts due to missing mapping.
  4. Check the locked records in sa_store_day_read_lock table.

 

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.