Convert Local Objects to Transportable Objects


Many times we face an 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 cofiles and data files, TR can not be moved to the next system. So how to handle this situation? In this post, let’s check out, how to Convert Local Objects to Transportable Objects.

Pre-requisite to Convert Local Objects 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 a package as ZBASIS by yourself or with the 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 the owner of the local objects, by checking the local TR.

Convert Local Objects to Transportable Objects

To convert local objects, we will use transaction SE03.

Execute SE03 => Expand the “Object Directory” entry => Double click on “Change Object Directory entry”

SE03

Enter the owner name of a object in the field “Person Responsible” and package as $TMP => Hit execute.

SE03

You will get a list of objects with the mentioned user under package $TMP.

SE03

Also Read

How to Validate Entries for Certificate CSR

Select the entry you want to convert => Click on the “Object Directory” button with the pencil icon. You will get the below screen with Object details and its package.

SE03

Here change the package name from $TMP to the Z-Package as per requirement. Please note the prerequisite section mentioned at the top is fulfilled. Once you change the package, it will ask for TR. Capture the changes in the 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.


You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!
Exit mobile version