Internal Exceptions (SAP Library - SAP Extended Warehouse Management (SAP EWM))

Internal Exceptions

The system sets an internal exception if an error occurs (if a scanner has reported an unknown HU, for example). The system sets the following exceptions internally. You must supplement these internal exceptions by external ones in Customizing. The external exception then specifies:

● The wording of the error message that appears in the alert monitor

● How the system reacts (for example, diversion of HU to clarification bin)

● Whether a further follow-on action takes place (for instance, notification of a remote control station via mail or text message)

Internal exception	Error situation	Context/step	Use
MFS1	The PLC confirms a warehouse task: The destination does not correspond to the expected position. (There is no open warehouse task for the relevant communication point.)	MF3 / A0	The system reposts the HU to the point reported by the PLC. If you want to log this variance, assign an external exception (such as MLOC) to the internal exception MFS1 and activate the follow-on action alert for it. If you want such "strays" to be diverted to the clarification bin, assign the internal process code CRCL to the external exception.
MFS2	Release conveyor segment: The PLC reports a conveyor segment or conveyor segment group as ready again. This exception facilitates the option of logging the event and triggering possible follow-on actions.	MF2 / A0	If you want this event to be logged in the alert monitor, assign an external exception to this internal exception, define the text Conveyor segment ready for the former, and activate the follow-on action alert.
MFS3	- Not used -
MFS4	Release resource: The PLC reports that a resource is ready again. This exception facilitates the option of logging the event and triggering possible follow-on actions.	MF4 / A0	If you want this event to be logged in the alert monitor, assign an external exception to the internal exception, define the text Resource ready for the former, and activate the follow-on action alert.
MFS5	Release communication point: The PLC reports that a communication point is ready again. This exception facilitates the option of logging the event and triggering possible follow-on actions.	MF5 / A0	If you want this event to be logged in the alert monitor, assign an external exception to the internal exception, define the text Communication point ready for the former, and activate the follow-on action alert.
MFS6	Release communication channel This exception facilitates the option of logging the event and triggering possible follow-on actions.	MF1 / A0	If you want this event to be logged in the alert monitor, assign an external exception to the internal exception, define the text Communication channel ready for the former, and activate the follow-on action alert.
MFS7	Unknown HU reported: The PLC has reported an HU that is unknown to the EWM system.	MF3 / A0	If you want to have the unknown HU automatically diverted, define the external exception - Unknown HU reported. Assign the internal process code HUNO to this exception. The system then creates a new empty HU and diverts it to the clarification bin.