Fusion CST: Why System Is Not Picking And Processing The Sales Order Transactions In Correct Sequence For Actual Costing (Doc ID 2869148.1)

Last updated on JULY 25, 2024

Applies to:

Goal

When the item is picked , an existing receipt layer is depleted and a new receipt layer ‘Sales Order Pick’ is created . This new layer which got created happens to be the latest layer instead of following FIFO rule . So

now for the SO issue event instead of depleting this SO pick layer it is following FIFO logic and picks up the next layer cost

EX: let's say we have 3 receipt layers

1.1.22 - Rec#1 -2qty@ 5 $
2.1.22- Rec#2 - 1Qty@4$
3.1.22 -Rec#3 - 2qty@2$
Now on 4.1.22 if user create a SO of 3 qty,
SO pick - Rec#1 and #2 will be depleted . so cost = 2 * 5(rec#1) + 1 * 4(rec#2) , so total becomes 14$
Now a new receipt layer is being created
4.1.22 - SO pick receipt layer - 3 QTY @ 4.666$ (14/3)
Now in SO issue event , instead of taking this 4.66 as the cost , it follows the FIFO logic and picks up the cost from the next Layer which is available for depletion
SO issue - 3qty@2$ ( It is referencing from Rec#3 which is the next layer available for depletion)

Solution

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