Page 1 of 1

WMS Enchancements

PostPosted: Mon Mar 11, 2019 11:03 am
by red1
In a large user case here in Thailand, i come across couple of things to improve the WMS with. I am doing it under a new plugin called WMSext that rides on top of the present WMS plugin.

1. Returns. There are both Customer as well as Vendor Returns. Those should generate DeliverySchedules for Putaway or Picking operations.

2. I made the above automatically. That means whenever such documents are completed, their DS will be generated as shown for a case below:

AutoDeliverySchedule.png (55.06 KiB) Viewed 2709 times

3. I also included Purchase and Sales to be auto generated. This is done in the WMSext plugin. Just stop the plugin and it won't do the auto-generate. When you refresh or start the plugin, a terminal message will appear to give you visibility of the plugin:

Code: Select all
osgi> refresh 303
osgi> *** WMS EXTRA PLUGIN **** MOrder and MInOut Model Events registered to generate DELIVERY SCHEDULES.

4. The InfoWindow and WMS models will persist AttributeSetInstance throughout, as can be seen in screenshot above.

5. DS will thus has DocType as one of its column and criteria. Again in same screenshot. Putaway/Picking windows too, but at WM_InOutLine level because there can be multiple DS merged into a single InOut. This allows multi document management during Warehouse operations. When you select singularly a DS line, you can zoom and view the link to its underlying document i.e. Order or Returns.

DeliveryDocType.png (73.16 KiB) Viewed 2708 times
a. Process buttons for 'Set Gate/PromisedDate
(Note: in process for Generate Putaway/Picking already has Merge to other active Putaway/Picking)

Re: WMS Enchancements

PostPosted: Tue Mar 12, 2019 10:24 am
by red1
DONE. Set Gate and PromisedDate to DeliverySchedule record. Note that all within same Delivery Schedule must be selected first (see right side of Info-Window). After setting, you may split into different Putaway/Picking Lists. You may also merge during that.

SetGateDatePromised.png (56.57 KiB) Viewed 2697 times
Below we view the traditional Orders to Delivery generation passes on the DocType of whether it is Purchase or Sales as the source.

DeliveryInfoDocType.png (92.52 KiB) Viewed 2694 times
Note i have begun to code the next process Divide By Pallet Size, where the delivery lines qtys are limited to the pallet size as stated in Product window or by this process parameter.

Re: WMS ENchancements

PostPosted: Tue Mar 12, 2019 6:03 pm
by red1
Now, the user can divide the qty per line by pallet size so that the DeliveryScheduleLines are limited for each pallet. The HandlingUnit can then tag to each or collective as the user desires. In the example below, a pallet can only take 4. If left 0 the process will take the Product.UnitsPerPallet.

BeforePalletize.png (35.95 KiB) Viewed 2692 times
PalletChoice.png (13.62 KiB) Viewed 2692 times
Palletized.png (32.41 KiB) Viewed 2692 times
Plugins uploaded to ... rehousing/
The metadata 2Pack is reissued to be a single for both plugnis metadata. The WMSExt is just the code. Stop it and it won't affect particularly DocType Events auto generation of DeliverySchedule.