TABLE OF CONTENTS
Internal Jira reference
https://globalomnichannel.atlassian.net/browse/WA2-5
Process flows
Item Move - preferred if no containers are used. If containers are used: then if the quantity is less than all then the to container must be <> from container. If the qty = all then it can be the same container.
Container Move - moves inhouse packages as well.
Scan Count - Scan count is a function that can move multiple items from Location A to Location B. You can randomly scan barcodes of items in location A (will be validated) into a work file – quantities will be accumulated. And can be amended manually as well too by editing the grid.
Move All - moves all stock on the one location to another location
Additional validations on top of M3 API validations
Warning message:
Status 1 - under inspection and status 3 - rejected balance ID moves
Expiry date controlled items with expiry date or priority date in past time (even if status is 2 - approved)
If a reclassification is to be made as part of a move.
Block message:
Destination stock zone is not the same one as in MMS002/G for the item
This includes StockMove, Container Move, Scancount, MoveAll
All these functions uses the same validation rules
MA features
We cannot move less than the full quantity and use the same from and to container (that will split the container to 2 locations instead a new container number is needed.
If more than one balance ID exits on the container we cannot move the full quantity to the same container either
for these processes use Container Move instead.
M3 settings
See general M3 set up as well
Panel | Flag | Comment |
MMS002/F | ABCF -Frequen | General M3: Used in SystemDirectedPutaway and used MMS060MI_ListPutaway transactions (using MMS160 logic) |
MMS002/G | Location | General M3: Used in soft allocation and also in special SystemDirectedPutawy logic in combo with PickFaceReplen |
MMS002/G | ContainerManage | Supports all methods (Recommends method 1 and 7) |
MMS002/G | StockZone | Controls by configuration in MA/WA2.0 if an item can be moved into a stock zone or not. (this is to be able to control ex allergen items to only be allowed in a certain stock zone) |
| MMS010/E | Interim reclass location | This location is used to move stock to while doing a reclassification on the fly when moving from a balance ID with a different status than the destination balance ID or destination location's status proposal (if no stock in the destination location yet of the same lot) We need a reclassification location set up in M3 in each warehouse we intend to transact in: This is to be used if reclassification is to be made on the fly. This location should be having container management turned on. And allow multiple balance ID’s:
|
| MMS025/E | Alias code | The quantity associated with the alias code will be used in stock move functions as a scan to count function. |
| MMS860 | Qualifier 92 | This flag determines what is allowed to move without warning message. If stock is to be moved while on picklist it is recommended to set this to 2. |
MA settings
See separate sections for
- Set up zone configuration to check destination zones
- Set up alternative rules for directed putaway
- Set up automatic expiry date reclassification upon stock move into a zone
See Infor documentation on how to set up system directed putaway (SDP) in M3
 | |
 | We can control the flags on BLANK warehouse level or on warehouse level. Minimum is to set up a blank catch all record if all warehouses works the same way. Then add any exceptions. |
 | Lst PutAwayLoc Will activate system directed put-away (MMS160MI) and a location will be suggested at in the To Location field as a place holder. Note: This happens on enter on the quantity field so the skip quantity input is recommended to be off if Lst PutAway Loc is on Move – Reclassify - Move Enabled Enable MA to be able to move a balance ID from one status to another by doing a move: So if you move from Status 2 ex FLOOR location to REJECT (Status 3) it will reclassify the balance ID on the fly. Note: If stock of the same item and lot already exists in the to location the status of that balance ID will take precedence over the status proposal in MMS010/E. If there is no Balance ID in the destination the MMS010/E status proposal for the destination location will be used. Interim location This location needs to be set up in all Warehouses in M3 that we intend to do this for. It needs to correspond to the one set up in M3. Default move qty Zero,One or All (stock on hand) Skip quantity input (not recommended to have turned on if directed putaway is enabled) Reset from location This means if not on the from location will be kept under the assumption we will keep moving from the same location. Focus on the balance ID filter instead of the From location (recommended when using unique barcoded like containers to minimize inputs required. |
Instructions
Simple move
 | |
 | if the cursor is defaulted to this field by settings but we are not sure of where we are moving from we can skip this input by [enter] or just by tap in the field (from location is not mandatory until we submit the whole transaction) |
 | |
 | The quantity to the right is the stock on hand. |
 | To location is calculated upon [enter] in the Quantity field (compare tap does not give a to location (possible improvement). If Loc override reason codes are set up they will pop up here if the choosen location <> the suggested one. |
 | |
Scan count move
 | If a barcode with a quantity is scanned in the item field instead of just an item no the scan count functionality kicks in. Note: the trigger is that the barcode needs a qty linked in MMS025/E or in the barcode itself (GS1 AI 30/37) 021443456700322237240 (02)14434567003222(37)240  |
Example of warning messages in StockMove
 | |
 | |
 | Shows the expiry date on the expiry dated items if passed date even if not rejected stock yet. |
 | highlights the status too |
 | |
 | ZONE CHECK |