Retry Mechanism Was Missing For Processing Lock Records
(Doc ID 2704264.1)
Last updated on AUGUST 31, 2020
Applies to:Oracle Retail Merchandising Foundation Cloud Service - Version 19.0 and later
Information in this document applies to any platform.
Retry mechanism was missing for processing lock records.
Steps To Recreate:
While loading sales , some of the POSU files rejected with “Table STAKE_SKU_LOC with key values, %s3 is locked by another user”.
1. Ensure that there is an active stock count for the item/return warehouse to be used on the POSU sales file at STAKE_SKU_LOC where the stock take date is less than current vdate.
2. Upload OMS returns POSUs file for item on step 1 where the return warehouse is equal to previous step. The selling stores should be non-stockholding where the "no inventory return indicator is set to Y".
3. Lock STAKE_SKU_LOC record for the item/return warehouse.
4. Run uploadsales and then salesprocess batch. Whilst the lock is not release, the batch will not retry to acquire lock .
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