TABLE OF CONTENTS

• Internal Jira reference
• Process flows
• M3 settings
• MA settings
• Instructions

Internal Jira reference

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

Process flows

This function generates the API call: MMS200MI_PrtItemLabel which generates the stream file of MMS501PF.

This stream file contains the basic values of the item: ITNO - Item number , ITDS - Name, FUDS - Description

It is then possible to use the CMS005 functionality to fetch more item information into the xml file or use ODBC calls if on the on prem and MOM/stream servesolution. 

Use case

• This function can be used to print additional product information upon receipt for items that are missing for example item barcodes or serial barcodes etc.
• The MO label is related to the MO number and retrieves the Product via the MO. these labels can be used as part of a MO issue process flow where we like to prepare the stock to issue by moving to a MO = unique pallet ID/Label using stock move or MO - Issue Move to Prepare functions.
• Workaround: to do something completely ad Hoch we can use a dummy item in M3 and then just type in the user defined data to produce labels
• Finish product enrichment to print a serial label or other spec label that goes on the product as part of production and can be printed out of MobilAction prior to the receipt is done. 

There are 3 main types of labels

• Carton Label
• MO Label
• Product Label

Within each type  we allow for custom configuring of the Layout value (to drive logic in the IDM/MOM area) as well as the input labels of the user defined fields and we do some basic validation (Number only or upper case only etc).

There is very little difference between the carton label and the Product label, more than that they can be associated with different printers in the user settings so they label stock can be different if that is required.

The output file also contains 5 user defined fields that can be passed in the API call.

This development utilises these fields:

The type is hard coded while the layout is the configurable drop down code.

Limitations

• The names of these functions are hardcoded in Mobile Action.
• The printers is associated with each label type and not by layout.
• The user defined fields are ony 15A long so we cannot add in large values  

M3 settings

This function uses a user defined API to find the product number based on the MO number. This could possibly be replaced by MWSLWMMI_LstMOHead or LstMOHead2.

MA settings

	Settings\Datagrid
	User Settings Printer These 3 printers determines the printers used for these 3 type of labels
	Settings\System\Print\Adhoc label configuration
	Layout (this number will be passed in the USD2) this is a 2 digit numeric value Default (select one layout to be default and selected if mostly used, else have no default and make the user have to select one layout) If only one layout that one will be defaulted.
	User defined fields 3-5 note for MO label 4-5 Optional or mandatory or not used. Upper Case only valid id String2. Input field name: this controls the the name of the label in the function. Different values of the field to use as the input validation.

Instructions

	Scan in the item to relate this print to (Alias number or GS1 AI 01, 02 and gtin works too) and no of copies required
	The enter the required data
	Last name mandatory
	Print