TABLE OF CONTENTS

• Internal Jira reference
• Process 
• M3 configuration
• MA configuration
• Instructions

Internal Jira reference

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

Process 

This function mimics M3's MMS105 container move function. However it does not use the MMS105MI to move containers. Instead it uses the MMS850MI_AddMove API, unless the container is an inhouse package then the AddPackMove is used. 

Business rules

If a container contains more than one item and MA is set up to  suggest a putaway location the  location will be retrieved using the first item in the container.  

Auto reclassification based on 

• Thawing days in MMS002/I (custom extension)

and checks on 

• Status/Expiry date/To Zone 

are all implemented to work on the container move as well as individual stock move.

Container method 7 - in-house packages are included in this function 

Custom rules for directed putaway are also included in this program and if activated a magnifying glass will occur next to the to location where we can browse to find a location based on defined rules see this section: 

• Set up alternative rules for directed putaway

Limitations:

The Move - Reclassify - Move function is not activated in the container move - only in stock move.

M3 configuration

The MMS002/G stock zone will have an impact if it is filled in. - we will only be allowed to move stock to locations within that zone with this function.

The setting in MMS860 (to allow to move stock on picklist if the full balance ID is moved) is recommended to be on if this function is to be used:

MMS002Supports all methods that allows a container to be placed on 2 locations at once (if more than one balance ID in the container) so method 1, 2, 3 (not 4, 5, 6, 7) UNLESS only one balance ID in the container then Any method works.  (Recommends method 1)

Reason: in Container move we use MMS850MI_AddMove and not MMS105MI since MMS105MI got some issues with moving sublots (from experience) so we use MMS850MI_AddMove multiple times instead to that is not allowed since the container will be on 2 locations momentarily during the move.

MA configuration

	Both Stock Move and Location Browse are used in container move.
	These settings can be set up by warehouse. For container move the Lst PutAway Loc is the only relevant flag.  All other flags are related to the StockMove function
	Under location browse all warehouses are listed and if a tick is made on the warehouse this icon will appear in Container move as well as in StockMove: See more details on how to set up the logic to retrieve locations using this alternative method in a different section.

Instructions

	Scan/input the contiainer ID + [enter] To location + [enter] and the move will happen
	The last location will linger on the screen but can be scanned typed over when in focus The last transactions are at the top of the subfile to keep a little history in the session Possible to jump out to stock toolbox and back if needed. The magnifying glass is there if custom/alternative putaway rules are set up