Hi @Shou ,

I agree with you. The issue was experienced by me in the latest UPD of APP10. I have checked in APP9 latest version and issue was there as well.

However I have found a previous RnD explanation on this (SOLUTION ID: 230879).

“Help text says that the standard putaway quantity is the quantity of a part that will be
kept intact and will not be split into smaller quantities.

It would be clearer with following example.

• Have an inventory purchase part with standard put away quantity 2.

• Capacity requirement for part is 5m x 5m x 5m (width, height, depth). Quantity per volume is 0.008

• You have 5 bins with bin cubic capacity 5m x 25m x 5m (width, height, depth) in a bay. Volume per bin is 625 m3.

• A bay is set as inventory part’s highest priority putaway zone.

Now, when you have a purchase order for quantity 5 of above parts with receive case Receive into Arrival, Perform Putaway, system would create a transport task line to move all 5 parts to one of the bins above. This is correct as one bin can hold all 5 parts. If you have a purchase order line for quantity 6 instead, upon receipt you would have two transport task lines for quantity 4 for one bin and quantity 2 for another. It will not be 5 and 1 even though the bin is capable of having 5 parts since your standard put away quantity is 2.

Quantity in transport task lines are depended on putaway zone’s carrying capacity, part’s capacity requirements and standard putaway quantity as explained above.”

I think this is how the application behaves. Hope this will help you some way.

/Anushka

@Anushka B 

Thanks for your answer.

After read you answer , I tried again with larger number:

“StdPutaway Qty”: 100

“PO Receive Qty”:  260

then IFS do divide it into 3 transport task:

1 - 100   ,  2 - 100,    3 - 60

So, seems this function considering more than what I thought.

Thanks,

@Shou It is my pleasure to be able to help you at least some way.