How To Fix RSM2016 - InfoIdocs missing; external system

SAP Error Message - Details

• Message type: E = Error

• Message class: RSM2 - Monitor assistant help texts

• Message number: 016

• Message text: InfoIdocs missing; external system

What causes this issue?

InfoIDocs are missing. The IDocs are created in BI with non-SAP systems
as source systems that transfer the data and metadata to BW using BAPIs.
Since the IDocs are missing, a short dump in BW probably occurred.

System Response

&V1&

How to fix this error?

Check the short dumps in BW.
Check the data in the InfoCube.
Error correction
If the data was correctly updated in the InfoCube, then it is possible
that no InfoIDocs were generated. In this case, manually set the entire
status of the data request to "ok" (green traffic light) in the monitor
in the Status tab page.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSM2016 - InfoIdocs missing; external system ?

  The SAP error message RSM2016 indicates that there are missing InfoDocuments (InfoIdocs) in the context of an external system. This error typically arises in scenarios involving the integration of SAP with other systems, such as when using IDocs (Intermediate Documents) for data exchange.
  Cause:
  
  
  Missing IDocs: The primary cause of this error is that the expected IDocs are not present in the system. This could be due to various reasons, such as:
  
  The IDocs were not generated or sent from the external system.
  There was a failure in the communication process between SAP and the external system.
  The IDocs were deleted or archived before they could be processed.
  
  
  
  Configuration Issues: Incorrect configuration settings in the IDoc processing or in the communication setup between SAP and the external system can also lead to this error.
  
  
  Data Issues: If the data being sent does not meet the required format or structure, it may lead to the IDocs not being created or processed correctly.
  
  
  Solution:
  
  
  Check IDoc Status: Use transaction code WE02 or WE05 in SAP to check the status of IDocs. Look for any IDocs that should have been generated and see if they are in error status.
  
  
  Reprocess IDocs: If IDocs are found in error status, you can attempt to reprocess them. Use transaction code BD87 to reprocess IDocs.
  
  
  Verify External System: Ensure that the external system is functioning correctly and that it is configured to send the necessary IDocs to SAP. Check logs in the external system for any errors or issues.
  
  
  Check Configuration: Review the configuration settings for IDoc processing in SAP. Ensure that the partner profiles, message types, and other relevant settings are correctly configured.
  
  
  Monitor Communication: If the issue is related to communication, check the communication logs (e.g., using transaction SM58 for asynchronous RFC) to identify any communication failures.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to IDoc processing and the specific message type you are working with for additional troubleshooting steps.
  
  
  Related Information:
  
  IDoc Types: Familiarize yourself with the specific IDoc types and message types being used in your integration scenario.
  Transaction Codes:
  
  WE02 / WE05: Display IDocs
  BD87: Reprocess IDocs
  SM58: Monitor asynchronous RFC
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to the specific IDoc type or message processing.
  
  If the problem persists after following these steps, it may be beneficial to engage with your SAP Basis team or consult SAP support for further assistance.