Late Poll Wrong Store Receipt on a Processed Count Incorrectly Posts TC22 (Doc ID 3073413.1)

Last updated on FEBRUARY 26, 2025

Applies to:

Symptoms

On: MFCS/RMS 19.3.006.21 version

Actual Behavior
-----------------------

The late poll wrong store receipt on an already processed stock count posts an extra TC22 to offset the TC30 transaction at both intended and actual receiving locations. This additional TC22 does not update the ITEM_LOC_SOH (as expected). However, it results in an extra STOCK_ADJ_COST in stock ledger WEEK_DATA and MONTH_DATA tables causing variance between stock ledger and Item-on-hand net cost.

Expected Behavior
-----------------------
The TC22 should ideally be posted only on receipt, i.e., to offset the TC44 transaction.

Steps to Reproduce
-----------------------
1. Create/Ship a transfer from Warehouse (WH) #1 to store #2.
2. Create a Stock count for all units - Unit and Value, on Store #3 (different from the transfer receiving location), for tomorrow’s date.
3. Run the nightly jobs to ensure the snapshots are completed on the stock count (STKUPD).
4. Upload the count results (STOCKCOUNTUPLOAD/STOCKCOUNTPROCESS)
5. Advance the VDATE (DTESYS).
6. Process the count variance (STKVAr). You will either have to manually process or setup auto-processing with CYCLE_COUNT_LAG_DAYS = 1.
7. Receive the transfer at store #3 (wrong store receipt). Receive date should be back-dated prior to the stock count date. Ensure that wrong store receiving is enabled in SYSTEM_OPTIONS.
8. Observe the TRAN_DATA created during receiving. There will be duplicate TRAN_CODE 22, one with PGM_NAME=STOCK_ORDER_RCV_SQL.PROC_STK_CNT_TD_WRITE, one with UPDATE_SNAPSHOT_SQL.PROC_STK_CNT_TD_WRITE.

Cause

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