How To Fix FDT_WD_TOOLS126 - Objects are locked in different transport requests (&1 and &2)

FDT_WD_TOOLS126 - Overview

• Message type: E = Error

• Message class: FDT_WD_TOOLS - Message Class for tools

• Message number: 126

• Message text: Objects are locked in different transport requests (&1 and &2)

What causes this issue?

You are about to save the changes that you have applied to the selected
objects. For that, you have chosen transport request &v1&. However, the
system has determined that one or more of the affected objects has
already been recorded in another transport request (&v2&), which has
not yet been released. Therefore, the changes cannot be saved.

System Response

The changes cannot be saved.

How to fix this error?

Make sure transport request &v2& is released. After that, reapply the
desired changes to the selected objects and save the changes to a new
transport request.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FDT_WD_TOOLS126 - Objects are locked in different transport requests (&1 and &2) ?

  The SAP error message FDT_WD_TOOLS126 indicates that there are objects that are locked in different transport requests. This typically occurs when multiple transport requests are trying to modify the same object, leading to a conflict. Here’s a breakdown of the cause, potential solutions, and related information:
  
  Cause:
  
  Concurrent Modifications: Two or more developers are trying to modify the same object (like a Web Dynpro component, for example) at the same time, and each has their changes in different transport requests.
  Transport Request Locking: When an object is locked in a transport request, it cannot be modified in another request until the lock is released.
  Incomplete Transport Management: Sometimes, if a transport request is not properly released or is still in a "locked" state, it can lead to this error.
  
  
  Solution:
  
  
  Identify the Transport Requests: Check the transport requests mentioned in the error message (&1 and &2). You can do this by using transaction code SE09 or