How To Fix TN572 - The transport request &1 was marked as modification adjustment transport

SAP Error Message - Details

• Message type: E = Error

• Message class: TN - Support Package Manager (SPAM) Messages

• Message number: 572

• Message text: The transport request &1 was marked as modification adjustment transport

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 TN572 - The transport request &1 was marked as modification adjustment transport ?

  The SAP error message TN572 indicates that a transport request has been marked as a "modification adjustment transport." This typically occurs when there are changes in the system that need to be adjusted or reconciled with the transport request. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Modification Adjustment: This error usually arises when a transport request is created for objects that have been modified in the development system, and those modifications need to be adjusted in the target system.
  Inconsistent State: The transport request may be in an inconsistent state due to changes made directly in the target system or due to missing objects that were not included in the transport.
  Transport Layer Issues: There may be issues with the transport layer configuration or the transport directory.
  
  Solution:
  
  
  Check Transport Request: Review the transport request in question. Ensure that all necessary objects are included and that there are no inconsistencies.
  
  Use transaction code SE09 or SE10 to check the transport request.
  
  
  
  Adjust the Transport Request: If the transport request is marked for modification adjustment, you may need to adjust it:
  
  Go to the transport request and check the objects included.
  If necessary, add or remove objects to ensure that the transport request accurately reflects the changes made.
  
  
  
  Release the Transport Request: After making adjustments, try to release the transport request again. This can be done in the same transaction (SE09 or SE10).
  
  Ensure that the transport request is in the correct status (e.g., "Modifiable" or "Released").
  
  
  
  Check Transport Logs: Review the transport logs for any additional error messages or warnings that may provide more context on the issue.
  
  
  Consult Basis Team: If the issue persists, it may be necessary to involve your SAP Basis team. They can check for any underlying issues with the transport directory or transport layer configuration.
  
  
  Related Information:
  
  Transport Management System (TMS): Understanding how TMS works can help in managing transport requests effectively.
  Transport Request Types: Familiarize yourself with different types of transport requests (e.g., workbench requests, customizing requests) and their purposes.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to transport requests and modification adjustments. You can search for notes in the SAP Support Portal.
  
  By following these steps, you should be able to resolve the TN572 error and successfully manage your transport requests.