How To Fix 42737 - Error &1 when creating the request

SAP Error Message - Details

• Message type: E = Error

• Message class: 42 - Information Workbench

• Message number: 737

• Message text: Error &1 when creating the request

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 42737 - Error &1 when creating the request ?

  The SAP error message 42737 typically indicates an issue related to the transport request creation process. This error can occur in various scenarios, often when there are problems with the transport directory, authorization issues, or inconsistencies in the transport management system.
  Cause:
  
  Transport Directory Issues: The transport directory may not be correctly set up or may have permission issues.
  Authorization Problems: The user may not have the necessary authorizations to create transport requests.
  Transport Management Configuration: There may be inconsistencies or misconfigurations in the transport management system.
  System Lock: The system might be locked for transport requests due to ongoing processes or maintenance.
  Missing Transport Layer: The transport layer might not be defined or properly configured.
  
  Solution:
  
  
  Check Transport Directory:
  
  Verify that the transport directory is correctly configured and accessible.
  Ensure that the user has the necessary permissions to access the transport directory.
  
  
  
  Review Authorizations:
  
  Check the user’s authorizations using transaction code SU53 or SUIM to ensure they have the necessary roles and permissions to create transport requests.
  
  
  
  Transport Management Configuration:
  
  Use transaction code STMS to check the transport management system configuration.
  Ensure that the transport routes and layers are correctly defined.
  
  
  
  System Status:
  
  Check if the system is locked for transport requests. You can do this by checking the system status in transaction ST22 or SM21 for any related errors.
  
  
  
  Check Transport Layer:
  
  Ensure that the transport layer is defined for the development system. You can check this in transaction SE03 under "Transport Organizer Tools".
  
  
  
  Consult SAP Notes:
  
  Look for any relevant SAP Notes that might address this specific error. You can search for notes in the SAP Support Portal.
  
  
  
  Restart Transport Management:
  
  If the issue persists, consider restarting the transport management system or the SAP system itself, if feasible.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  STMS (Transport Management System)
  SE03 (Transport Organizer Tools)
  SU53 (Authorization Check)
  SM21 (System Log)
  ST22 (Dump Analysis)
  
  
  
  SAP Notes: Always check the SAP Support Portal for the latest notes related to transport issues and error messages.
  
  
  If the problem continues 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.