TABLE OF CONTENTS

M3 General Settings

MMS005 – Warehouse

 

MMS005/H

Note: 

Picking lists: can sit at 1 or 3 depending on if we want picklist printed too.

We only need this flag turned on if we want text from customer orders to show in Mobile Action - if not important we don't need to download picklists (and text) to MHS810


CRS165 – Number series

 

 

There are a few number series involved in M3 transactions that are executed on the warehouse action system. The main ones to mention here are 16 & 17 they are the numbers that are used in MMS850 and MHS850 in the WHI staging table records: 

Both the wave number and the reporting number for MO’s are behaving differently in different versions of M3 and the best practice is to “fill” up so all characters are used from the beginning so leading zeros or trim is required etc.

Pro tip: These numbers can get corrupted during an ENV copy IF the copy happens DURING transacting in PRD… ex during the night… what tends to happen is that the CRS165 is not swapping over to the same number as is in MMS850 and or MHS850 so the number in MHS850 is higher than the last no in the CRS165 (since number series is copied first then the table…) this results in duplicated key when trying to process a transaction and trying to use the same message no as already exists…) this can easily be resolved by 1. Not copy while transacting …. If possible or just update the CRS165 last number used to what is in MMS850/MHS850 and it will start working.

 


MMS865 – Partners and filing of staging file records settings

I - Inbound: (Pick reports and Moves etc)

 


This enables us to use F10 in MMS850 and MHS850 to file the staging records these interfaces creates to archive or delete.

Note: We run some statistics on these table so 180 days means we can look at 6 months stats

Note: Need to use both the tick (235) and the number of days (240)

O - Outbound: Picklists  Panel sequence EF



This enables us to use F10 in MMS850 and MHS850 to file the staging records these interfaces creates to archive or delete.

Note: We run some statistics on these table so 180 days means we can look at 6 months stats

Note: Need to use both the tick (235) and the number of days (240)


This is important: Picking lists = 1 if we are to get the text from order headers and lines to show in MA (All texts and Picklist texts) 


Example of Purge/Archive

 

Archived records will appear in MHS890, MMS890.

This maintenance should be done on a regular basis to keep the performance of the warehouse integration interfaces.

Note: There is no program to schedule so this needs to be part of a manual maintenance schedule

MHS090 – Delete download data

This program should be scheduled if any of the below programs are populated

 

With the partner set up for WA (this relates to inbound messages so often we do not need these files populated when running warehouse action)   

 

MMS860 – Qualifiers

F14 to generate latest

Amend qualifier 92:

 

Mov net calc:

Recommendations: 

IF 13.4 BE then use 2 this means we can move quantity on picks list as long as we move the whole balance ID, this assumes we pick using RF guns since any printed paper will not be updated.

In earlier versions of M3 the option to use 2 is not available in this case use 1… 

Note: in WA1.0 we allowed a pop-up question and reprocess using MMS175MI (that works like option 2) but this will not be implemented in WA2.0 unless it is requested.

 

Pro tip: When pressing F14 any configuration changed from standard will be reset so that is important to consider when pressing F14.

 

MHS860 – Qualifiers

F14 to generate standard (this will pick up any new interface not yet been used since delivery by Infor development)

MMS010 – Location Master

All standard flags like multi storage, allocable, container management, are used as in standard M3.

Below are listed flags that are involved in enhancements in WA

Panel

Flag

Comment

MMS010/E

Stock zone

Used in Pick&Pack filter as well as Stock move validations

MMS010/E

Location type

Used in Pick face replenishment

MMS010/E

Location group

Used in Pick face replenishment

MMS010/E

Create phys inv

Used in Pick&Pack to initiate stocktake on the fly

MMS010/E

Check code loc

On roadmap in Pick&Pack (voice pick)

MMS010/E

Container mng

Combined with container mng in MMS002/G turns on/off the container field in the application.

MMS010/F

Equipment

Used in Pick&Pack filter

MMS010/F

Editing pos 1

Future Use

MMS010/F

Editing pos 2

Future Use

MMS010/F

Editing char 1

Specific customer logic

MMS010/F

Editing char 2

Mandatory scan in pick and pack? Y/N (blank means Y in picking) Blanks means suggested but not forced in PO receiving

MMS010/F

Pkg length

Future use in custom system directed putaway logic by cube

MMS010/F

Pkg width

Future use in custom system directed putaway logic by cube

MMS010/F

Pkg height

Future use in custom system directed putaway logic by cube

MMS010/FTransport flowUsed for listing order or pick lines (if MMS040/E is set to list by transport flow code)
MMS010/ELocation= User
MMS010/ELocation characteristicsAll methods supported: Lot blending = 3 then a different API is called in stock move.

 

Note: All users are recommended to be set up as LOCATIONS in MMS010 as well since the user can be used as a pack location in MA. Meaning when pick and pack the pack location becomes the packer, until moved to dock, loaded, or issued out.

 

MMS001 – Item Master

Panel

Flag

Comment

MMS001/E

Lot control

Supports all lot control methods

MMS001/E

Lot number method

Supports all lot number methods including 8 & 9

MMS001/E

Alt UoM

Supported in stocktake to count and add in multiple UoM

MMS001/F

Exp Date method

Supports all expiry dates methods, Recommend 1 & 2
(3 & 4 generally creates issues in M3 with unwanted date changes)

MMS001/F

Sublot cntrl

Supports sublots

MMS001/G

CW

Supports catch weight & Location based Catch weight

MMS001/G

Potency

No extra support for Potency developed in WA 

MMS001/G

Attributes

Support view of attributes and update of attributes

MMS001/H

PO UoM

Support alternative UoM in Purchasing

MMS001/I

Storage Requirement

This field controls any custom mapping of AI's (alias identifier) in the GS1 barcode to the balance ID in M3 as well as if cumulative scanning is used for the item

 MMS001/G

Location characteristics

Supports all methods (if lot blending - 3 is used a different API is called in stock move)

 

 

 

 

 

 

 

 

 

 

MMS002 – Item Warehouse

All M3 Std rules:

  • Directed put-away (MMS057, MMS001/F Distgroup, MMS002/G Fill part empty etc)
  • Allocation
  • Are supported and used

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

Pack&Dock

Will be used in Pick&Pack if no other location is used

MMS002/G

ContainerManage

Supports 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. 

MMS002/G

Scan Required

Will demand item scan or not in Pick&Pack (1/0)

MMS002/G

Alt UoM

Is not used in WA2.0/MA

MMS002/G

Inspect Location

Used in PO Receivng Location logic

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)

MMS002/I

Shelf life

This value is used to calculate deviations to manually inputs of Expiry date upon PO receipt and Reclassification. Any date that is outside of a set % tolerance will be issued a warning message.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

MMS025 – Alias Numbers

All alias numbers can be used and will be retrieved. Any ambiguous result will be show and user needs to select line.

Panel

Flag

Comment

MMS025/E

Quantity

If quantity is not = 0 then the qty will be used in scan counts in Stock move, Stocktake, Pick&Pack, Receiving etc. Note: the storage requirement for the item in MMS001/I needs to be set up in Mobile Action and have the Scan count flag ticked for the scan count to work as wel

MMS025/E

UoM

Best kept not populated (enhancement to ensure UoM from MITPOP is used on the ongoing transaction) ex Move or Pick.

Current feature: if UoM is populated ex OUT and there is 24 in an outer: in M3 when ordering in OIS300 on the outer barcode (ex via EDI) say 1 OUT (it will place an order for 24) if you have the qty in MMS025 to say 24 it will order 24 outers = 576 in WA we will use the qty regardless and as a basic UoM. So if scan one outer barcode it will pick 24 basics UoM’s