Here is the link for Part 2 before you go through this Part3.
The blog post is to explain how SAP EWM MFS handles the exceptional scenarios during material flow.
Exceptions can be reported to SAP EWM MFS by two ways:
1) User reports the exception
2) PLC reports the exception
For the first one, warehouse supervisor can assign the exception code to the MFS element via Warehouse Monitor.
For the second one, PLC should communicate the exceptional situation as error code in the telegram message sent to MFS.
In this blog, the second one is explained with configuration and document flow.
Let us consider the same use case explained in the part 2 of this blog. Assume that PLC noticed the destination bin as physically occupied as an exception and cannot complete the putaway in that bin.
Process flows as shown in the flowchart below.
Configuration Steps :
1) Configure Exception Codes.
2) Assign Internal Process Code to Exception Code.
3) Maintain Follow-Action for the Exception Code.
4) Assign PLC errors to Exception Codes.
5) Define EWM Exception for PLC Access Control Errors.
6) Maintain the Error Bin for MFS Resource or use BAdI ‘/SCWM/EX_MFS_GET_EMPTY_BIN’.
1) Configure Exception Codes
SPRO --> IMG --> SCM Extended Warehouse Management --> Extended Warehouse Management --> Cross-Process Settings --> Exception Handling --> Define Exception Codes
2) Assign Internal Process Code to Exception Code.
3) Maintain Follow-Action for the Exception Code.
4) Assign PLC errors to Exception Codes.
SPRO --> IMG --> SCM Extended Warehouse Management --> Extended Warehouse Management --> Material Flow System (MFS) --> Exception Handling --> EWM Exceptions --> Define EWM Exception for PLC Errors
5) Define EWM Exception for PLC Access Control Errors.
SPRO --> IMG --> SCM Extended Warehouse Management --> Extended Warehouse Management --> Material Flow System (MFS) --> Exception Handling --> EWM Exceptions --> Define EWM Exception for PLC Access Control Errors
6) Maintain the Error Bin for MFS Resource or implement BAdI ‘/SCWM/EX_MFS_GET_EMPTY_BIN’.
Let us run the Inbound proc in the exceptional situation.
Document Flow Steps:
1) Check the Inbound delivery in EWM.
2) Create the Putaway task w.r.to Inbound delivery.
3) Confirm the task for manual flow from GR-Zone to ID-Point..
4) Check the MFS task auto generated to move across Communication Points.
5) Check the MFS telegram WT sent to PLC and WTCO sent from PLC.
6) Check the final task telegram with error.
7) Check the error code assignment to Handling Unit.
8) Check the destination bin (Error bin) of the final task.
9) Check the follow-on action (Putaway block for bin) of the exception.
10. Check the Inbound delivery status update.
1) Check the Inbound delivery in EWM.
2) Create the Putaway task w.r.to Inbound delivery.
3) Confirm the task for manual flow from GR-Zone to ID-Point.
4) Check the MFS task auto generated to move across Communication Points.
5) Check the MFS telegram WT sent to PLC and WTCO sent from PLC.
6) Check the final task telegram with error.
PLC sends error code in the telegram to MFS since the destination bin of task is physically occupied.
7) Check the error code assigned to Handling Unit.
8) Check the destination bin of the final confirmed task.
HU Stock moved to Error bin assigned to the MFS resource master data in configuration step 6.
9) Check the follow-on action of the exception.
10. Check the Inbound delivery status update
Status completed for Goods Receipt and Putaway.
very nice document with in detail process.
Awesome ..scenarios which you explained MFS inbound and exception error . Appreciate if you can explain steps for MFS outbound picking scenarios to outbound feed pallet conveyor to final staging bay
Final step when you remove the block from the bin is there not a WT to move from PI02-CPER to the final bin?