How To Fix TR347 - &1 does not belong to request &2: Check the entry

SAP Error Message - Details

• Message type: E = Error

• Message class: TR - Change and Transport System

• Message number: 347

• Message text: &1 does not belong to request &2: Check the entry

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 TR347 - &1 does not belong to request &2: Check the entry ?

  The SAP error message TR347 indicates that there is a problem with the transport request in the SAP system. Specifically, it means that the object (e.g., a program, function module, or other development object) you are trying to transport does not belong to the specified transport request. This can happen for several reasons, and here are some common causes, solutions, and related information:
  Causes:
  
  Incorrect Transport Request: The object you are trying to transport was not included in the specified transport request.
  Object Not Released: The object may not have been released or is still in a development state.
  Transport Directory Issues: There may be issues with the transport directory or the transport management system.
  Development Class Issues: The object might belong to a different development class than the one associated with the transport request.
  Manual Changes: Manual changes to the transport request or the object might have caused inconsistencies.
  
  Solutions:
  
  
  Check Transport Request: Verify that the object you are trying to transport is indeed included in the specified transport request. You can do this by checking the transport request in the Transport Organizer (transaction SE09 or SE10).
  
  
  Include Object in Request: If the object is not included, you can add it to the correct transport request. Use the transaction SE80 or SE11 to include the object in the appropriate transport request.
  
  
  Release the Transport Request: Ensure that the transport request is released. You can release it using transaction SE09 or SE10.
  
  
  Check Development Class: Make sure that the object belongs to the correct development class that corresponds to the transport request. If not, you may need to change the development class of the object.
  
  
  Recreate the Transport Request: If the transport request is corrupted or has issues, consider creating a new transport request and including the necessary objects.
  
  
  Consult Transport Logs: Check the transport logs for any additional error messages or warnings that might provide more context about the issue.
  
  
  Related Information:
  
  Transaction Codes: SE09 (Transport Organizer), SE10 (Transport Organizer - Modifiable Requests), SE80 (Object Navigator).
  Transport Management System (TMS): Ensure that the TMS is properly configured and functioning.
  SAP Notes: Check for any relevant SAP Notes that might address specific issues related to transport requests and error TR347.
  
  If the problem persists after trying the above solutions, it may be helpful to consult with your SAP Basis team or refer to SAP support for further assistance.