How To Fix /SAPCND/DD_CUSTOMIZE018 - Transport request could not be created

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/DD_CUSTOMIZE -

• Message number: 018

• Message text: Transport request could not be created

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /SAPCND/DD_CUSTOMIZE018 - Transport request could not be created ?

  The SAP error message /SAPCND/DD_CUSTOMIZE018 indicates that a transport request could not be created for customizing objects. This error typically arises in the context of the SAP Change and Transport System (CTS) when there are issues related to the transport request creation process.
  Causes:
  
  Missing Authorization: The user may not have the necessary authorizations to create transport requests.
  Transport Directory Issues: There may be issues with the transport directory or the transport management system configuration.
  Transport Layer Configuration: The transport layer may not be correctly configured, or the target system may not be defined properly.
  Object Locking: The object you are trying to transport may be locked by another user or process.
  Transport Request Limitations: The system may have reached a limit on the number of transport requests that can be created or processed.
  System Configuration Issues: There may be inconsistencies in the system configuration or issues with the transport routes.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to create transport requests. This can be done by checking the user's roles and authorizations in transaction SU01.
  Review Transport Directory: Check the transport directory settings in transaction STMS to ensure that they are correctly configured and that the transport directory is accessible.
  Verify Transport Layer: Use transaction STMS to verify that the transport layer is correctly set up and that the target system is defined properly.
  Unlock Objects: If the object is locked, identify the user or process that has locked it and resolve the locking issue. You can use transaction SM12 to check for locks.
  Check Transport Request Limits: Review the system settings to ensure that there are no limitations on the number of transport requests. This can be checked in the transport management settings.
  System Configuration: Ensure that the transport routes are correctly configured and that there are no inconsistencies in the system configuration. You can check this in transaction STMS.
  
  Related Information:
  
  Transaction Codes:
  
  STMS: Transport Management System
  SU01: User Maintenance
  SM12: Display and Delete Locks
  
  
  SAP Notes: Check for relevant SAP Notes that may address specific issues related to this error message. You can search for notes in the SAP Support Portal.
  Logs and Traces: Review system logs and traces for additional error messages or warnings that may provide more context about the issue. Use transaction SM21 for system logs and ST22 for dumps.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.