I am doing the WMS Guide PDF in progress uploaded here http://sourceforge.net/projects/red1/files/Warehousing/
I like to include another closing feature that was picked up from another SAP WMS expert here in Thailand:
That user scan in SKU code while putting away in Warehouse. So therefore i am creating a sub table under the WM_InOutLine as Qty is Putaway/Picked at a Locator, the user may scan each of the SKU at a normal sub window which will contain basically only one input field - SKU number.
The beauty is that its parent is already locked as WM_InOutLine_ID containing M_Locator_ID and HandlingUnit_ID.
Then at the parent model, perhaps at during WM_InOut CompleteIt(), the process shall check the existence of such grandchild records and transmit them to M_InOutLINE_MA which is part of the ERP core ASI (Attribute Set Instance) under M_InOutLine.
We can even add a control to check if Qty balance is exceeded during scanning. Or the Qty is updated from the 'WM_InOutLineSKU'.
I will create an Android app in release 2.0 (when next project sponsors this) for direct scanning into WM_InOutLineSKU via a temporal SQLite table in the mobile which then updates iDempiere's.