How To Fix /FTI/SERV_BUSN_ERROR072 - Failed to create trask in transport &1

SAP Error Message - Details

• Message type: E = Error

• Message class: /FTI/SERV_BUSN_ERROR -

• Message number: 072

• Message text: Failed to create trask in transport &1

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 /FTI/SERV_BUSN_ERROR072 - Failed to create trask in transport &1 ?

  The SAP error message /FTI/SERV_BUSN_ERROR072 Failed to create task in transport &1 typically indicates an issue related to the transport management system (TMS) in SAP, specifically when trying to create a transport request or task. This error can occur for various reasons, and here are some common causes, potential solutions, and related information:
  Causes:
  
  Authorization Issues: The user may not have the necessary authorizations to create a transport request.
  Transport Directory Issues: There may be issues with the transport directory or configuration.
  Transport Layer Configuration: The transport layer may not be correctly configured or may be missing.
  Transport Request Lock: The transport request may be locked by another user or process.
  System Configuration: There may be inconsistencies in the system configuration related to transport management.
  Network Issues: If the transport is being created across systems, network issues may prevent the task from being created.
  
  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 SU53 or SU01.
  Verify Transport Directory: Check the transport directory configuration in transaction STMS. Ensure that the transport directory is correctly set up and accessible.
  Review Transport Layer: Use transaction STMS to check the transport layer configuration. Ensure that the transport layer is correctly defined and that the system is included in the correct transport route.
  Unlock Transport Request: If the transport request is locked, you may need to unlock it. This can be done using transaction SE09 or SE10, where you can check the status of the transport request and unlock it if necessary.
  Check System Configuration: Review the transport management configuration in transaction STMS. Ensure that all systems are correctly configured and that there are no inconsistencies.
  Network Troubleshooting: If the transport is being created across systems, check for any network issues that may be affecting connectivity between the systems.
  
  Related Information:
  
  Transaction Codes:
  
  STMS: Transport Management System
  SE09/SE10: Transport Organizer
  SU53: Authorization Check
  SU01: User Maintenance
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error. You can search for notes in the SAP Support Portal.
  Logs: Review the system logs (transaction SM21) for any additional error messages or warnings that may provide more context about the issue.
  
  If the problem 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.