SAP Knowledge Base Article - Public

2547679 - Internal Error Occurred Check MPL ID XXXXXX in C4C Message Monitoring


An Outgoing message has failed in the Cloud for Customer Webservice Message Monitoring with the following error message:
Error: An internal error occurred. For error details check MPL ID XXXX in message monitoring or use the URL directly access the error information.
***Where XXXX represents the message ID in Cloud Integration and YYYY represents the Cloud Integration tenant number***


  • SAP Cloud for Customer Integration via Cloud Integration

Reproducing the Issue

  1. Change master or transactional data to trigger an update which will exchange data with an ERP system integrated with Cloud for Customer.
  2. Navigate to the Administrator work centre and select Webservice Message Monitoring.
  3. You will notice that the outbound replication for the data you have changed has failed with the following error 'An internal error occurred. For error details check MPL ID XXXX in message monitoring or use the URL directly access the error information.'
  4. When you select the error details of this message the following is displayed: org.apache.cxf.transport.http.HTTPException: HTTP response '401: Unauthorized' when communicating with http://host:port/sap/bc/srt/idoc?sap-client=ZZZ 
    *** Where ZZZ represents the Client Number ***


This integration scenario has failed within your Cloud Integration tenant due to an issue with the authorization check.


Please ensure the below three settings have been checked:

  1. Ensure the username and password/client certificates maintained in the Cloud Integration's Integration Flow are maintained correctly for the authorization check to succeed.
  2. Ensure the Cloud Integration client certificates are correctly maintained in STRUST on your ERP system.
  3. Map the client certificates to the Integration user in ERP.

If all the above settings are correct, please collect an ICM trace to find the real root cause of the issue, to do so, please carry out the following steps:

  1. Execute transaction RZ11.
  2. Adjust parameter icm/trace_secured_data to the value TRUE (this parameter is dynamic and no downtime or restart is required for its adjustment).
    *This is only applicable to HTTPS, for all other traffic please skip to step 6*
  3. Execute transaction SMICM.
  4. You are advised to reset the ICM trace file, to do so, select Goto > Trace File > Reset.
    *It is not mandatory to reset the ICM trace file ,however it is recommended to do so to prevent the ICM trace file you are about to generate from being unnecessarily large.*
  5. Set the ICM trace level to 3, to do so, select Goto > Trace > Level > 3.
  6. Reproduce the issue once more.
  7. Execute transaction SMICM.
  8. Set the ICM trace back to level 1, to do so,  select Goto > Trace > Level > 1.
  9. Display the newly generated ICM trace, to do so , select Goto > Trace File > Display All.
  10. Save the ICM trace file to a local file, to do so , Type '%pc' or navigate to System > List > Save > Local File > Unconverted.
  11. As per step one , readjust parameter icm/trace_secured_date to the value FALSE.

The Purpose of carrying out an ICM trace is to analyse the data stream to and from the SAP Web Application Server. The HTTP data traffic is regulated by the Internet Communication Manager (ICM).The resulting trace file will enable you to categorically identify the exact issue , as it will display the exact certificate which is causing the problem within the flow of traffic. Following this you will be able to compare and contrast the certificate chain maintained by your basis team on the onpremise system and also on the Cloud Integration tenant.


MPL, MPL ID, Certificates, 401, 401 error, HCI, CPI, integration , ERP , C4C , Cloud for custmer , certificate , 401, 403, ECC , Integration , failed , adminsitrator , inbound , outbound , error , tenant, , KBA , LOD-CRM-INT-ERP , Integration of C4C with ERP , How To


SAP Cloud for Customer core applications all versions