Jira ticket for the development epic (internal CA use) WA2-520

TABLE OF CONTENTS

• Process flows
• M3 settings
• MA settings
• Instructions

Process flows

Supports:

M3

• Lot control
• Container management 1-7
• Catch weight

MA special enhancements:

• Predefine X pos of MO number to be able to key only last Y (save time and better accuracy)
• Unique lot number for each receipt as an additional option
• To container auto generated or manually entered (validated via package mask)
• Auto generate a pallet label per receipt based on M3 package rules in MMS050/DRS080/MMS044 and the items packing instructions in MMS053 on a specific warehouse or on the generic record.
• Separate config/process flows for each MO type if needed (catch all record for the generic ones)
• Lot ref 1&2 input based on config options
• To location logic based on hierarchy
• Print label copied configurable

Future enhancements:

• Overissue validation (catch key error) 
• Enter expiry date on first lot receipt 
• If above is on then validate entered date vs STD to vs tolerance % to catch key error 
• Sublot receipts & GS1 decoding
• Attribute recording during receipts

M3 settings

Specific to this function

MA settings

Screen	Comments
	Catch all record with blank ordertype
	Preset MO number (must be done on blank"catch all" record) if you like to manually enter the MO number (no ability to scan from a box or from a MO paper work etc). It can then be set up to only need to enter the last 3 or 4 digits and change the leading 6 or 7 every so often when the MO number series ticks over. Note: This assumes we use the same number series for all MO types.
	Set up a specific record for an order type if the receipt process is different - else set everything up on the blank catch all level.
	This flag is about how we handel lot numbers in MA for MO Receipt M3Std - M3 Standard - (if auto generated it will sit in PMS100/E before the first receipt BUT not yet in MMS235 - lot master (only when the first receipt is done will it be added). M3StdLotM - Mandatory - the lot must be loaded into MMS235 prior to the receipt. This can force a QA process where for example the expiry date of the production batch is set prior to receipt etc. Note this MA flag can be combined with the new flag in M3 PMS120/G Create lot number at MO release (meaning first lot no is created automatically in MMS235 and any subsequent are then done manually etc. UniqueLotPerReceipt - this calls an API (MMS235MI_RtvNxtLotNo) to get the next lot number for the items lot number method: Note: the item must have an automatic lot numbering method for this to work.
	If this is turned on we can change the lot number manually (and if not mandatory to be stored in lot master any number can essentially be created as a second lot no (typically LOTA, LOTB, or LOT., LOT.. etc.
	Future enhancements: (not used today) Over and under receipt tolerance to catch keying errors Expiry date tolerances based on the shelf life no of days in MMS002/I to catch keying errors. Note: Allow expiry date input is activated on the front end but is not updating the dates during MO receipt so the recommendation is to not use this flag at the moment
	These Lot reference field 1 & 2 can be configured to be added in and be mandatory or not.
	Receipt location hierarchy: 1.MA: Use the Default Receipt Location value, (we can have different by ordertype) if blank: 2. PMS100/E (can be added manually in PMS001/E or possibly by config in product structures and workcenters) if blank: 3. MMS002/G - Inspection location (we use this field (and it does not need to be a status 1 location) to allow a unique receipt location for each item while keeping the Main location available for other things like soft allocation main etc. 4. MMS002/G - Main location Receipt loc. override: No - means if none of the above is populated the user can still add a location manually Yes - means even if populated the user can change it and put in another location
	This flag only applies to item/location combinations where there will be a container requested upon receipt (if not container managed item or location the field will always be closed). Mandatory - means we don't use any logic to create a container on the fly. Insead we use a pre-printed container or fixed barcode on a pallet or similar. Optional - means if entered we don't create a container on the fly if we enter it manually but create it if we leave it blank (more about this logic below) No - means we create a container number for the receipt and use it as part of the receipt transaction Note: all containers used as manual input needs to adhere to the package mask logic set up in Package Masks (see general settings) (if no package masks are set up any container can be used)
	These 2 flags are very important in the MA set up. these 2 flags are used to control how we create the container numbers on the fly. Note even if we don't use containers for our receipt or if we do but we key them manually this is still required. The system will (always) try to retrieve packing instruction (Package type and quantity) from MMS053 using API MMS053MI_GetItemConnPkg where we first test on the WHS of the session and then with no warehouse (meaning different pallet configurations can be managed over different sites) we always try to find the largest package: so that means the quantity: needs to ALWAYS be 9 digits (if no decimals): 999999999 99999999.0 9999999.00 999999.000 99999.0000 9999.00000 999.000000 for MA to find the record on WHS level or on blank level in MMS053. Note: If a record is found here for the item to receive or the add package type flag is populated in MA settings we are good to proceed to receive: if not we will get this error message: If the flag "Default add package" is turned OFF: If a record is found in MMS053 we will use that PACT instead of the default one to generate the container number. If no record is found we will not use the STD Default package instead we get this error: If the flag "Default add package" is turned ON: We will always use the Default Add Package as the PACT value. If different type of items are to generate different number series for their containers MMS053 should be used and default package be left unpopulated.
	Moreover, from the Package instructions It is the STD quantity from the details in MMS053 that is used in the flag MO Default Quantity Input Option. No - just leave it blank Yes - just populate with remaining qty to receive if no standard pack quantity from MMS053 then that is used until the last pack that will give the remaining quantity. (so we have a gap if we need MMS053 for other reasons but we like the full MO quantity to populate here: workaround use a quantity in MMS053 of less than 999999999 ex 999999998 (if no  RoundUp - Populate with MMS053 standard qty for the item (so these flags assumes MMS053 exists) it will round up to STD qty RoundDown - Populate with MMS053 standard qty for the item (so these flags assumes MMS053 exists) it will round down to 0 once the remaining quantity is less than the standard qty (to assume the user will adjust to the actual remaining quantity).
	Printing: 1. The printer used will be the one from the user (the putaway printer) 2. The no of default copies can be set here. If allowed an additional step to let the user override the no of copies can be added. Example: we use the same order type for WIP and FG and WIP needs one label and FG 2 labels then we can add this step and maybe default to 2 labels and when we produce WIP we change to 1 label. A better way is to configure these process flows using separate order types that can then be tuned in MobileAction

Instructions

	Short entry possible if configured or by any other input or just browse using magnifying glass
	Just follow the steps and press enter to go to next step Use the back button to change values
	these are the steps required for this MO
	Last step enter and this receives the stock