TABLE OF CONTENTS

Jira Internal reference

https://globalomnichannel.atlassian.net/browse/WA2-306

Process flows

This function moves a package from status 50 or 60 - Pack or Dock to status 65 – Loaded.

M3 packing and load building is a prerequisite.

Routes and shipments are not a prerequisite but will help if a "To Location" is to be directed by the function.

The "To Location" is essential in this function since it consolidates all the staged packages for a delivery or shipment/route in an area controlled by M3 executed by MA instead of just relying on printed labels and manual staging management  or similar.


Note: This function is shared with Load building by package: Where load building by package is moving packages to status 65 instead.  


Limitation:

Does not handel Pack in Packed packages (the outers but they are part of the count and should really be the only ones to have to validate) (investigation pending on if this is a M3 limitation or something we can work around)


Note: Load shipment" handel packed in packed packages (will only deal with the top level packages)

M3 settings

If load building is used and a loading dock is assigned the shipment that will be used to determine the To location. 

We set up a one to one relation between Dock location in MMS010 and loading platforms in DRS016.

MWS423MI_ListPackage_TWSL – This is a field that is returned in list package: Unclear how this is populated.

The logic is: If not populated then the loading platform (from DRS005=>DRS100) is used in DRS100 as the to location - hence the one to on setup.


Note: The if the status of the package is 50 or 60 the TWSL is not populated 

(assumed the MWS420/P F13 settings for to  location logic is set to 0 on the M3 API user (the service account user - typically MAADMIN but never got this to work - M3 got complex logic to determine dock locations). 

However, once the package been loaded to status 65 the TWSL location is populated (as the location it was loaded from - ready for reverse one would assume). This is why sometimes you see a "dock" type location and sometimes a ex pack type location (if already loaded).   This location is also visible in MWS422 for the pick line


DRS005/F - Link a default load platform to each route (can be one per Site or one per route)
Load building ticked here as well as in CRS728 (transport settings)
DRS016 - Loading platform: note you may need to set up in sort order 1 too on both blank and WHS level.
Set up all the actual load platforms too - typically dock doors
MMS010 - Set up the load platforms as locations too.
Trick if the default one is not to be possible to use (user must choose one) then do NOT set it up as a location AND the shipment must be updated with a real loading platform before it can be moved to DOCK:


MA settings

Configurable detailed view in the grid view section to include valid info.


Settings\DataGrigConfig
this is shared with Move to Dock so the screens needs to be the same
Plenty of fields to choose from here. Shipment and closed and invoice status etc.





Instructions




The to location is based on the loading platform in DRS100. The output field are from the Configurable data grid (the and the order)

the shipment must be ready for loading:


The number or loaded packages is packages in status 65 so progress is shown after each scan. (multiple users can work on the same shipment/route)
Scan last package to load


This closes the shipment and puts all non packed orders on a new shipment with its original delivery numbers so the goods that was not picked and packed yet stays on its original delivery number (M3 standard
Report shipment means all loaded packages 
This pick reports the whole shipment (if loadbuilding all pick reporting needs to happen once shipment it closed so the most efficient way is to do it just after packages are loaded from the dock)

This can then trigger invoices and delivery dockets and manifests to print automatically by M3 STF functionality/