27/07/2022
Summary of issue/request/query
WHID : CBT01
Customer : MAP
Order MAPSO000002647
SKU ACR88G00900100555#
Cubic did not capture on allocation detail
Those issue happened also on order#
SO MAPSO000002657
SKU SSO34N009013005001
Please be informed this issue already solved before
Attachment
(none)
T/ 1st Line Support Investigation Comment
Check for cubic on allocation detail
This is a separate issue than before. In the previous issue, the cubic information exists in both orderdetail and allocation detail just that the billing rate is not calculated and we fixed that.
For the above case, it is due to overallocation.
Cubic turn into 0 after allocate.
The “over allocation” config is on.
If the stock still in the storage, it still on the way to PickFace, Yes it will
be 0.
Because the stock is don’t reach to PickFace yet.
The cubic is always on SKU that is correct. The question
here is more towards the transactional records. Because when the SKU is
received into inventory, it is received with cubic information.
That information will be stored in inventory table. Once it is in, we no longer refer back to SKU on information unless it is on checking and etc.
So usually the information on cubic in inventory that will be used.
What happens during overallocation is… when the stock is being overallocated, the information is still not in the location for that stock therefore in allocation detail, it is still zero.
When replenishment happened, by right it should bring along the cubic but it does not and we understand that is it base designed.
During the calculation on cubic, I understand that billing already taken the cubic from transaction record instead of allocation detail.
Therefore in this case, what is the business requirement?
We may need to engage project team to study this if it is effect bigger change.
Files | ||
---|---|---|
|
DataImage20.png
127 KB
|
|
|
DataImage68.png
115 KB
|
|
|
DataImage84.png
279 KB
|
|
|
DataImage20[1].png
110 KB
|