SAP MDG · ABAP FOUNDATIONS

How can I move objects of one TR to another if the task is already released ?

How to Unrelease a Task and a TR

There are two different scenarios depending on whether the main Transport Request (TR) or only its task has been released.

Moving Objects to Another Transport Request After Task Release

There are two different scenarios depending on whether the main Transport Request (TR) or only its task has been released.

--- ## 1. Main Transport Request Is Released

Once the main TR is released, the objects are released from that transport and can subsequently be captured in another Transport Request.

Normally, you should not face any issue assigning the same objects to a new TR.

However, if the new transport depends on changes contained in the earlier transport, ensure that the transports are imported into the target system in the correct sequence.

CODE
1TR1 - Original changes 2 | 3 v 4TR2 - Subsequent changes

Import TR1 before TR2 if TR2 depends on objects or changes transported through TR1.

--- ## 2. Only the Task Is Released

Releasing a task does not release the objects from the main Transport Request.

When the task is released:

CODE
1Main Transport Request 2 | 3 +-- Task - Released 4 | 5 +-- Objects

The task becomes released, but the objects remain associated with and locked under the main Transport Request.

Therefore, SAP will normally not allow the object to be moved to another Transport Request.

--- # Unreleasing the Task

Important: Changing transport status directly through table debugging is not a standard SAP transport-management procedure. Perform this only when you understand the impact and have the required authorization. Ideally, coordinate with the SAP Basis team.

Step 1 — Open Table E070

Go to:

CODE
1Transaction: SE11

Enter:

CODE
1E070

Open the table contents.

--- ## Step 2 — Find the Released Task

Enter the Task Number and execute.

Make sure you enter the subtask number, not the main Transport Request number.

Example:

CODE
1Main TR : DE9K903090 2Task : DE9K903091

--- ## Step 3 — Change the Task Status

Select the relevant row.

Display the record and switch to edit mode using debugging, as permitted in your system.

Change:

CODE
1TRSTATUS

from:

CODE
1R

to:

CODE
1D

Where:

CODE
1R = Released 2D = Modifiable

Save the change.

The task is now unreleased / modifiable.

--- # Why the Object Still Goes to the Same Main TR

Unreleasing the task alone is not sufficient.

Once the task was released, the object remains locked or associated with the main Transport Request.

Therefore, if you modify and save the object again, SAP may still assign it to the same parent Transport Request.

You must remove the object from the main TR as well.

--- # Remove the Object From the Main Transport Request

Step 1 — Open SE01

Go to:

CODE
1Transaction: SE01

Enter the main Transport Request number.

Make sure you are on the Display tab and execute.

--- ## Step 2 — Open the Transport Request

Double-click the main Transport Request.

Go to the Objects tab.

Click Edit at the top.

SAP Screen Representation

--- ## Step 3 — Delete the Object Entry

Select the required object from the Objects tab.

Click the Delete / Minus (-) button.

CODE
1Objects 2 | 3 +-- Select Object 4 | 5 +-- Delete (-)

Save the Transport Request.

Confirm the relevant SAP popup messages by choosing Yes / OK after verifying that the correct object is being removed.

--- # Final Process

CODE
1Task Released 2 | 3 v 4Object remains associated with Main TR 5 | 6 v 7Change Task status in E070 8R -> D 9 | 10 v 11Task becomes Modifiable 12 | 13 v 14SE01 15 | 16 v 17Open Main TR 18 | 19 v 20Objects Tab 21 | 22 v 23Edit 24 | 25 v 26Select Object 27 | 28 v 29Delete (-) 30 | 31 v 32Save 33 | 34 v 35Modify / Save Object again 36 | 37 v 38Assign Object to New TR

--- ## Key Point

Releasing the task and releasing the main Transport Request are not the same thing.

A released task may still leave the object associated with the parent Transport Request. Making the task modifiable again does not by itself free the object.

The relevant object entry must also be removed from the parent TR before it can be cleanly captured in another Transport Request.

SE11

SE11

Open transaction SE11.

SE01

SE01

Open transaction SE01.

Referenced tables

ObjectPurpose
E070Open table E070.

The remaining configuration, implementation details, and testing guidance continue from this answer more…

Related questions and keywords

Alternative questions

  • If the TR is already released, can I remove objects from the TR ?
  • How can I unrelease a TR Transport?
  • How can I unrelease a Task ?
  • I have removed the object from the task, but it keeps going to the same TR .

Possible questions

  • If the TR is already released, can I remove objects from the TR ?
  • How can I unrelease a TR Transport?
  • How can I unrelease a Task ?
  • What configuration is required for How to Unrelease a Task and a TR?
  • How can this SAP MDG scenario be tested?

Keywords

TRTransportTaskUnreleaseTransport RequestSE01SE09Move Objects