Print transport docs by delivery : ComActivity

TABLE OF CONTENTS

Internal Jira reference
Process flows
M3 settings
MA settings
Instructions

Internal Jira reference

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

Process flows

This function supports printing of these M3 documents:

912 - transport label

913 - address label

900 - delivery document

901-913 all outbound delivery based documents like proforma invoice and bill of lading etc.

Additional functionality:

Add packages here if the delivery is configured for simple packing
Update certain values of a package: LWH, Weight, External track no etc.
Update freight accessorials: if freight assroarials are configured in M3 - then we can update the values here
Confirm the pick - checks if the delivery consists of more than one picklist
Unpack a package

Business rule:

When a package has been printed the packaging code in MWS423/E is updated to P. (MPTRNS.ORGRTP)

This makes it easy for the dispatch office to see the progress of the packages on the shipments, (if something is not printed it will not be loaded etc)

Pick confirm: If many picklist suffixes exists we confirm all of them in one go after a warning. So if we use this function in conjunction with multiple picklist suffixes some coordination is required.

There are 3 more variants of this function which is

Print by

Package - M3 unique package number created at pick release or during picking
SSCC - Same but the corresponding SSCC
Tote - The definition of the pick tote is a recyclable package number that lives when the picklist is between status 40 and 89 (once above 90) Issued) we can reuse the same package to pick goods into (like a plastic tote with a fixed barcode on).

The settings in Mobile Action are shared between all these functions

M3 settings

Documents needs to be attached to the delivery so CMS017/MWS250 should be set up.

Packages needs to be set up in MMS050 etc.

Simple or advanced packing in MWS010

Freight accessorials - MWS010 and CMS017/MWS280 to preselect values to be able to update.

CustomAPI: CMS100MI_LstMPTRNS_Z02 - this is only required for the print by tote function

MA settings

Settings\System\PrintTransportDoc

	These settings can be set up by warehouse or as a blank catch all warehouse. The warehouse on the user session will be matched with these records and the flags fetched from the appropriate level.
	Address label this mimics MWS423 option 47 - Address label (document number 913) MMS486PF Transport label this mimics MWS423 option 48 - Transport label MMS485PF (if 912 00 is set up) MWS485PF if (912 01 and or 912 02) is set up Note: these API's work with MWS250/MWS260 set up and if I have for example both 912_01 and 912_02 linked to my delivery I will get 2 labels for each package - one for each layout if I set up 1 copy - 2 copies will generate 4 labels. Other document: this typically A4 printing of delivery dockets etc. the syntax is docno:variant:nocopies\|next doc Note: If labels are also on A4 printer and done at the same time that doc no can also be added in the sting and generated on the same button in the flow to save one button press. ex 900:00:1\|912:01:2 (one D/D and 2 labels variant 01) Auto Print: this is for the label print option when we scan a package label and it can print it automatically to make the process more efficient. Allow confirm all: This mimics MWS420 option 16 confirm the pick: Logic: we warn if the delivery contains more than one picklist suffix and M3 will not allow to pick confirm if not fully packed anyway.
	These printers will be used Address label printer for MMS486PF Transport label printer for MWS485PF, MMS485PF Document printer for the other documents.
	Data grid config all these grids are needed to be configured to only see the desired data. The most important one is the "package details" where we can update the data so we only want to show the right field(s) to update

Instructions

Print by delivery


	You can scan delivery on its own or picklist: delivery/sufix it will just suppress the suffix since the packages are on delivery level not pick lis header level Note the scan package/sscc to select is not used at this stage.
	Remove input fields to save realestate
	Select a line or all Print label to send off transport and or address labels (x copies) and Docket to send of x copies of the list of those docs. This will update the package type with a P:

Look up content

	This drills into the items in the package (not into the package details)

Update freight accessorial


	Edit directly in the subfile then

Add packages (manual simple packing)

	Note: if this is the fist package since we add the packages at the end when the delivery is entered it will be a message: Nothing to show but that is OK since we need to add at least one package.
	Add as many packages as you need of the same type
	Select the type (the list is group by allowed packages in package masks.) then confirm

Update package details


	Only the fields configured will show here
	to update

Print by Package/SSCC/Tote


	If auto print it will print as soon as it is retrieved Note: if the same package number exists on more than one delivery the API will not return any package at all: This is a feature of M3 Standard API but good to know if we have issues with non unique packages (that is a prerequisite for this function) Note:in by TOTE: It will pint the first package if the same package exists on same status
	Same logic for all 3 functions