ERP Error transfer

Error messages generated in SAP ECC/S4 for objects modified in SAP FSM can be communicated to the cloud and unblock the locked object.

1 Prerequisites
2 Further insight
3 Example 1 - service call update fails because of service order being locked in SAP ECC/S4

Prerequisites

Errors occurring on the SAP ECC/S4 side for a given object will be transferred to FSM only if this functionality is enabled for the relevant message type in transaction /PACG/ECM_CLSASSIGIN - FSM Connector's Incoming Messages Configuration, field ‘Error Conf’:

Further insight

Error messages are communicated using idocs of type /PACG/ECM_ITYPE_OBJERROR:

MESTYPE	Type of the message which couldn’t be processed correctly, e.g. SERVICECALL.
EXTGUID	GUID of the object which failed to be processed correctly.
ERRORCODE	An error code consists of a message type, message ID and message number, e.g. E/PACG/ECM_MAIN 378.
ERRORMESSAGE	Message description, e.g. Creation of service order for comp 0008: No default type could be found.
MSGID	ID of the message which failed to be processed correctly.

Idoc /PACG/ECM_ITYPE_OBJERROR remains in status 18.

The related object becomes unblocked in SAP FSM after transferring an object error idoc.

Example 1 - service call update fails because of service order being locked in SAP ECC/S4

The example below illustrates an error communicated to SAP FSM when the modified service call’s service order was being blocked by a user in SAP ECC/S4.

Ensure that ‘Error conf’ is enabled for the relevant message type in transaction /PACG/ECM_CLSASSIGIN - FSM Connector's Incoming Messages Configuration:

Block a service order in SAP ECC/S4 and modify the related service call in SAP FSM:

The service call idoc cannot be processed successfully.

An object error idoc is transferred to SAP FSM. It contains information about the order being locked.

The service call becomes unblocked in SAP FSM. The message is stored as an Event in the System Monitoring tab.