Rotation Rule usage

Creation date: 22/02/2023 09:31 Updated: 22/02/2023 09:31 #rotationrule

Question:

NEO – Unable to make allocation by order for Order Number SO20230106000015

Affected Environment:

WMS Production

Affected warehouse:

WH88

Screenshots of error messages:

Time when issue occurred:

06/01/2023 15:00 and now this problem still exists.

Affected module:

WMS – Allocation by order

Detailed description of issue:

When I click on sub menu named “Allocation by order” for Order number SO20230106000015 but SO Status is still “Create SO”, not change to be “Allocated”.

First level investigation/troubleshooting taken:

I found that Order Number SO20230106000015 that its status is “00” but why is value of oprSeqFlag field is as long as Order Number SO20230106000010 is which was already closed. I think that it is possible that user maybe make something wrong such as clicking on close order accidentally or something.

Case replication in original warehouse:

You can try to test on Production

*7/1/2023

Dear CSO.HLS

Because this order number SO20230106000015 had been taken on date December 3, 2023 and I am afraid of Lazada SLA breached, so I tried to continue to find the way to workaround this problem. I can remember about “Partial Allocated” for some orders in the past. It was unable to allocate stock for some lines item in sales order although stock was available in Piece FWD Loc. Because expiration date for product in reserve location was less than piece FWD Location is. It made program to try to allocate stock from reserve location

at first that it is impossible. I think that event and for this order number are maybe almost the same. I queried to view data for this product in all locations to see the expiration date.

I found that the expiration date in all locations are the same. In my opinion, program must allocate stock from reserve to be the same as “Partial Allcation” event. So I tried to hold

Stock in all reserve locations for this product and to make allocation by order again. Ok, it works but I don’t know that why program allocate stock from reserve location prior to

Piece fwd location.

Thank you very much.

Answer:

Investigation:

For this issue of allocation , it is related about Rotation Rule. The rotation rule set up that system will consider prioritized by

Then when the available stock of the SKU has same Expiration date at both of Pickface and Reserved location.

After operator confirms SO allocation. System will not generate the allocation because of system will consider

Stock Condition - System see that all location has same data
The expiry date – System see that all location has same data
The warehouse date - System see that the smaller date is stamp at reserved location.

Then system cannot generate allocation at reserve location.

For this case , NEO business confirms that for outbound they focus on the expiry date only

I try to re-config on Rotation Rule and testing on TEST (Ref. Attached File)

Investigation:

The case that is given by customer is not setup properly.

We have responded as below:

Has this SKU able to allocate before? We are not checking your configuration on the SKU but on the issue.

Can you use the SKU that can be allocated before and show us the reason it cannot be allocated.

As for the SKU that you setup in the order – the configuration is not as per original.

Investigation:

Advise customer to setup the package information properly and not just change the UOM Description.

Also ask customer to replicate this issue in the TEST environment and inform them the steps we think will replicate the issue.

Files		Sort by Name Sort by Date
	DataImage48.png 87 KB
	DataImage16.png 25 KB
	DataImage21.png 116 KB
	DataImage85.png 364 KB
	DataImage55.png 264 KB
	DataImage4.png 73 KB
	DataImage44.png 96 KB
	DataImage2.png 55 KB
	DataImage39.png 48 KB

Rotation Rule usage

Contents