SAP Knowledge Base Article - Public

3439908 - An internal error occurred. For error details check MPL ID XXXX In 3PL Business Communication Monitoring

Symptom

- A technical error is displayed when executing 3PL outbound delivery requests.
- No further details are visible under the Message Details section.

Environment

SAP Business ByDesign

Reproducing the Issue

1. Navigate to the Third-Party Logistics work center.
2. Go to the Common Tasks view and select the Business Communication Monitoring sub-view.
3. Under the section Messages with Errors, observe the Standard outbound 3PL Requests with Status technical Error.
4. Note that no further details are visible under the Message Details section.

The error message : An internal error occurred. For error details check MPL ID XXXX in message monitoring or use the URL https://eYYYY-tmn.hci.eu1.hana.ondemand.com directly access the error information. can be identified at SAP side
***Where XXXX represents the message ID in Cloud Integration and YYYY represents the Cloud Integration tenant number*** 

Cause

This integration scenario has failed due to an issue with the authorization check.

Resolution

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 analyze 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  system and also on the Cloud Integration tenant.

See Also

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

- SAP Business ByDesign Documentation
- SAP Cloud Tenant Documentation

Keywords

3PL, Outbound Delivery, Technical Error, SAP Business ByDesign, Business Communication Monitoring, Message Details, BYD INSTALLATION) , KBA , AP-SLP-REQ , Site Logistics Request , Problem

Product

SAP Business ByDesign all versions