How To Fix TR737 - & marked for import in &

SAP Error Message - Details

• Message type: E = Error

• Message class: TR - Change and Transport System

• Message number: 737

• Message text: & marked for import in &

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 TR737 - & marked for import in & ?

  The SAP error message TR737 typically indicates that a transport request is marked for import but cannot be imported due to certain issues. This error can occur in various scenarios, such as when there are inconsistencies in the transport request or when the transport request is not properly released.
  Cause:
  
  Transport Request Not Released: The transport request may not have been released properly, which means it cannot be imported into the target system.
  Missing Objects: The transport request may reference objects that are missing or not available in the target system.
  Dependencies: There may be dependencies on other transport requests that have not been imported yet.
  Transport Directory Issues: There could be issues with the transport directory or the transport management system.
  Authorization Issues: The user attempting to import the transport request may not have the necessary authorizations.
  
  Solution:
  
  Release the Transport Request: Ensure that the transport request is released in the source system. You can do this by going to the Transport Organizer (SE09 or SE10) and releasing the request.
  Check for Missing Objects: Verify that all objects referenced in the transport request are available in the target system. If any objects are missing, you may need to transport them separately.
  Check Dependencies: Make sure that any dependent transport requests have been imported before attempting to import the current request.
  Review Transport Directory: Check the transport directory for any inconsistencies or issues. You can use transaction code STMS to manage transport requests.
  Authorization Check: Ensure that the user has the necessary authorizations to import transport requests. You may need to consult with your SAP security team if there are authorization issues.
  Consult SAP Notes: Look for any relevant SAP Notes that may address specific issues related to the TR737 error message.
  
  Related Information:
  
  Transaction Codes: 
  
  SE09 / SE10: Transport Organizer
  STMS: Transport Management System
  
  
  SAP Notes: Search for SAP Notes related to transport issues and the TR737 error message in the SAP Support Portal.
  Documentation: Review SAP documentation on transport management for best practices and troubleshooting steps.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.