How To Fix CM_CBESCOM_INB013 - Import request was not created

SAP Error Message - Details

• Message type: E = Error

• Message class: CM_CBESCOM_INB - Message Class for ESComXML Inbound Processing

• Message number: 013

• Message text: Import request was not created

What causes this issue?

The system could not create the import request for the ESComXML file.

System Response

The import request is not created.

How to fix this error?

Note other messages in the <LS>Processing Log</>.
INCLUDE NA_SYSADMIN1 OBJECT DOKU ID TX

Procedure for System Administrators

Check the ESComXML file that is to be uploaded.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CM_CBESCOM_INB013 - Import request was not created ?

  The SAP error message CM_CBESCOM_INB013: Import request was not created typically occurs during the import of transport requests in the SAP system. This error can arise due to various reasons, and understanding the cause is essential for finding a solution. Here are some common causes, potential solutions, and related information:
  Causes:
  
  Missing Authorization: The user may not have the necessary authorizations to create import requests.
  Transport Directory Issues: Problems with the transport directory or transport management system (TMS) configuration can lead to this error.
  Transport Request Status: The transport request may be in a status that does not allow it to be imported (e.g., it might be released but not yet imported).
  System Configuration: Incorrect configuration of the transport routes or the transport layer can prevent the import request from being created.
  Network Issues: Connectivity issues between the systems involved in the transport process can also lead to this error.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to perform the import. This can be done by checking the user roles and authorizations in transaction SU01.
  Review Transport Directory: Verify that the transport directory is correctly configured and accessible. You can check the transport directory settings in transaction STMS.
  Check Transport Request Status: Use transaction SE09 or SE10 to check the status of the transport request. Ensure that it is released and ready for import.
  Verify Transport Routes: Check the transport routes and layers in transaction STMS. Ensure that the configuration is correct and that the systems are properly connected.
  Check System Logs: Review the system logs (transaction SM21) for any additional error messages or warnings that might provide more context about the issue.
  Network Connectivity: Ensure that there are no network issues between the source and target systems. You can test connectivity using ping or other network tools.
  
  Related Information:
  
  Transaction Codes:
  
  SE09/SE10: Transport Organizer
  STMS: Transport Management System
  SU01: User Maintenance
  SM21: System Log
  
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps. You can search for notes in the SAP Support Portal.
  Documentation: Review SAP documentation related to transport management for best practices and configuration guidelines.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.