New WMS Design

[red1]

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.

[red1]

From here we are branching into integrative points but separate plugins for sanity. First is the way to have some sort of 'cheat-sheet' to simplify some of the many steps as shown here for a Project Order Contract (PM_Contract) that works on a standard quota for its purchasing, warehousing and eventually manufacturing - viewtopic.php?f=45&t=1842

For the eventual manufacturing, i am thinking of a similar (to PM_Contract above) where an 'encapsulation' plugin governs the overall user experience (which is always plus minus particularly minus the over cluttered wide ERP system). The plugin will take the vital information or intent of the user and then issue out Sales Order/s, BOM Drop instances (in this case i want to improve it further to allow incremental or partial droppings (more on this in here viewtopic.php?f=45&t=1843)

[red1]

The WMS can now handle Locators with alphabetical symbols. Generate Locators and Generate EmptyStorage also tested fine manually and under FitNesse:

Screen Shot 2017-09-15 at 12.24.23 PM.png (42.44 KiB) Viewed 6577 times

Thus, you can define anyhow with numerical values or a single alphabetical letter. The last been Z. Setting of Types is also updated to work with this. Leaving blank space is taken as a 'Z' last char.

[red1]

The use of alphebetical Locator values has impact on Putaway/Picking sorting. It is solved with the Order By Warehouse, X, Y, Z.

Screen Shot 2017-09-16 at 10.31.03 AM.png (48.8 KiB) Viewed 6571 times

[red1]

Now we have properly instituted a BackOrder feature during Order to Delivery Schedule creation. The code that checks for BackOrder is better placed in DeliveryScheduleLine.beforeSave routine:
1. Check if its reference C_OrderLine.QtyDelivered is more than zero (means it has Material Receipt completed and MatchPO done), then it will subtract the OrderedQty from the QtyDelivered.
2. Otherwise check if a previous DeliveryScheduleLine exists where it IsBackOrder thus throw Error Exception as show below.
3. Passing above two will allow normal process of saving the new DeliveryScheduleLine.

Screen Shot 2017-09-27 at 8.26.06 AM.png (85.76 KiB) Viewed 6479 times

After completing the Putaway document by zooming into it and run process Complete, then click on its ShipmentLine link to get to the main Material Receipt window and also run process Complete, the user can then issue a BackOrder as shown here, the remaining BackOrder which picks up from Sales Order's QtyDelivered (subtracting from QtyOrdered).

Screen Shot 2017-09-27 at 7.10.12 PM.png (57.13 KiB) Viewed 6473 times

You can then issue a new Delivery Schedule which will by Qty (to receive and putaway) = 2.