Receive Elsewhere Functionality "RE" In SHIPSKU Causing Invalid WAC & Intransit Quantities (Doc ID 3012885.1)

Last updated on MARCH 27, 2024

Applies to:

Symptoms

Receive Elsewhere functionality "RE" in SHIPSKU causing invalid WAC & In-transit quantities .

1) Transfer - XXX was created against PACK item - pack_item
2) this transfer was shipped on 01-JUL-2022 Originally against location LOC1 (ORIGINAL transfer location)
3) however, on 31-OCT-2023 the receipt was created against RE "Receive Elsewhere" location that is for location 10898
4) between these two dates (01-JUL-2022 & 31-OCT-2023) we had cycle count at both the locations.
5) Ideally we should see the reversal of TC 30 for the quantity shipped for location LOC1 in TRAN_DATA_HISTORY
and then the corresponding new entries of TC 30 and TC 44 for location LOC1 should be registered and since there was stock count completed at the time of receipt TC 22 should be posted to make the adjustment to align the stock.
6) At the moment we are seeing unexpected TC30 and TC 70 posted multiple times as positives for location LOC1 and reversals for location LOC2.
7) Apart from this the intransit quantity in ITEM_LOC_SOH is updated with abnormal quantity in ITEM_LOC_SOH for both the locations LOC1 & LOC2.
8) With the abnormal intransit quantity in ITEM_LOC_SOH we also see that the AV_COST values is updated higher than the actual expected. Ideally there should not be any change in WAC or very minimum variation.

Cause

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