TABLE OF CONTENTS

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

Internal Jira reference

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

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

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

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

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

Process flow

In MA we can configure our stock movex to pick up a location based on M3 standard directed putaway rules via API MMS160MI if we turn on a flag in the StockMove settings (see stock move section)

See infor documentation on how to set up M3 for this (MMS002/MMS040/MMS010/MMS011/MMS057 etc)

However, sometimes customers need a different logic to let the system suggest locations by. In Mobile Action we offer an alternative way to retrieve locations. 

General Business Rules:

The first rule - ZONE/ABC/Fillrate:

We select locations based on a combination of StockZone in MMS002/G and the ABC (Frequency) class in MMS002/F matched with the  same in MMS010/E/F. This could have been achieved with standard too but we have changed the fill rate logic: we count one balance ID as 1 (ex a lot on a container) and the max fill rate is then say ex 45.00 meaning 45 balance ID's can fit - 45 containers. This in combination with looking at storage method (single item, lot or multi) can in simpler way determine if a blockstack location is full nor not. 

The second rule - Putaway by Attribute values  

We can link link each location to one attribute key and list corresponding attribute values that should match with this location. What this means is that we will only suggest this location if the stock moved has any of those attribute values 

This makes it possible to pick up on for example 2nd grade product not export worthy and have it directed to a separate area. If fruit is putaway and attribute values like moist or mould has been recorded as part of the grading process upon receipt, these recorded attributes on the specific lots and containers can be picked up in the put away routine and directed to the right places in the warehouse.

M3 settings

CMS100MI_LstMITPCE_Z01 custom API - see other article

CMS100MI_LstMIATTR_Z01 custom API - see other article

CMS080 - Customer defined fields

MMS002/F - Abc class (frequency)

MMS002/G - Stock zone

MMS010 - E Storage method can be any but it will be used: if 3 we will only look at locations with no stock or the same item. Stock zone is matched with MMS002/G

Max fill rate 10 means 10 balance ID's ABC class frequency is matched with the item's in MMS002/F

The attribute code: can only "listen" one at the time but can be different for different locations Multiple attribute values to "listen" to separated by ; NOK;NO

MA settings

	Settings\System\StockMove
	This will make a little magnifying glass appear in the right hand side of the To location in StockMove and Container Move. for this warehouse
	Settings\System\StockMove
	Suggest to maybe turn off the standard putaway logic for the warehouses that has this alternative putaway logic on. This way no To location will be suggested so it make more sense to query on via the magnifying glass - see instructions below.
	Settings\DataGridConfig\StockMove
	The columns and the sorting is important here. we like to sort on no of balance ID's in descending order to fill up the full ones first etc.

Instructions 

	LOT56 HAS EXPORT STATUS NOK GOES TO OVERFLOW SINCE THE LOGIC ONLY FINDS ONE AVALIABLE LOCATION IT IS SUGGESTED AS SOON AS MAGNIFYING GLASS IS TAPPED.
	LOT55 WHEN TAP MAGNIFYING GLASS
	2 LOCS AVAIL
	THE ONE SELECTED NEEDS TO BE VERIFIED REASON CODES ETC PLAYS IN IF THIS IS ALLWED TO CHANGE
	NEXT ONE SUGGESTED AT TOP ONCE MORE THAN 10 BALANCE ID ON LOCATION THE LOCATION WILL DROP OFF