My Oracle Support Banner

STKUPLD Does Not Update STAKE_SKU_LOC.PHYSICAL_COUNT_QTY Properly (Doc ID 2009975.1)

Last updated on FEBRUARY 18, 2019

Applies to:

Oracle Retail Merchandising System - Version 13.2.5 to 13.2.9 [Release 13.2]
Information in this document applies to any platform.

Symptoms

When the volume of stock count records to be processed is more than 4.5 times the value set in RESTART_CONTROL.COMMIT_MAX_CTR, STKUPLD is updating different values to the STAKE_SKU_LOC and STAKE_CONT tables.


Steps to Reproduce:

  1. Suppose the value of RESTART_CONTROL.COMMIT_MAX_CTR is 3000.
  2. Set up a stock count for 20 stores with about 700 items in each store (14,000 records).
  3. Execute STKXPLD, STKUPD batches and upload a count file using STKUPLD.
  4. Note that for some store items, tables STAKE_SKU_LOC and STAKE_CONT have different values.

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
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.