Introduction
Error messages generated in SAP ECC/S4 for objects created/modified in SAP FSM can be communicated to the cloud.
FSM UI supporting such messages is not yet available. As of now, error messages are stored but not displayed in SAP FSM.
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. |
A /PACG/ECM_ITYPE_OBJERROR idoc remains in status 18 and unblocks the related object.
Example
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.