Convert Local Objects ($TMP) to Transportable Objects
Many times we face issue that the objects which are required for the configuration move to higher systems i.e. QAS or PRD are locked in Local Transport Request. As local transport request’s objects are part of package $TMP, these can not be moved, and hence when you even release the local transport request or TR, you will not get cofiles and data files. Without coffees and data files, TR can not be moved to next system. So how to handle this situation? In this post, let’s check it out, how to Convert Local Objects ($TMP) to Transportable Objects.
Before starting with this exercise, make sure you have a Z-package created to capture your objects. Generally packages are created based on the area or entity you are working on. For example, if you are only responsible for BASIS configuration and objects, then you can create package as ZBASIS by yourself or with help of your development team. Capture the package in TR and make sure this TR moves first in higher systems, so that the package is available there.
Also make sure to note down owner of the local objects, by checking the local TR.
Convert Local Objects ($TMP)
To convert local objects, we will use transaction SE03.
Execute SE03 => Expand the “Object Directory” entry => Double click on “Change Object Directory entry”
Enter the owner name of object in field “Person Responsible” and package as $TMP => Hit execute.
You will get list of object with the mentioned user under package $TMP.
Select the entry you want to convert => Click on “Object Directory” button with pencil icon. You will get below screen with Object details and its package.
Here change the package name from $TMP to the Z-Package as per requirement. Please note the prerequisite section mentioned at the top is fullfilled. Once you change the package, it will ask for TR. Capture the changes in new TR and save.
You are done. You can now safely release this new TR once all required objects are added and then move this TR to higher systems.