Skip to Content

Over the last few months, I have been facing an issue whenever I try to create a TR request. All of us know that for most of our SAP configurations, SAP automatically prompts for a TR number and includes all the relevant data on the TR request.

SAP best practice says that we should not tamper with the TR request contents, meaning, no manual changes to be done to the TR. But, I have seen people have issues with this. They are never ready to leave the poor TR request contents alone, the reasons may be different.

SAP expects that the configuration in our Production client is the same as the one in our Configuration client. This is to be 100% adhered and so does not encourage manual tampering of TR’s. The reason being, when the set up is same, irrespective of the TR contents, the config remains same throughout the landscape once the TR reaches production.

People have reservations because, they are not sure that Prod and Dev configuration is the same or in case of substitutions and validations, where a whole lot of other data along with your changes are also included in the TR (since TR is not created at the step level).

There may be other reasons for manual TR need. Say, a Z table does not prompt for TR when changed. In such a case also you would need a manual TR.

I have heard different approaches for creating this manual TR with the desired entries only. But, recently I came across the easiest one.

In case of say transporting fields to be restricted to be not used in Validation or substitution creation as explained in my document (Restricting/Unrestricting Fields for Substitutions and Validations), the TR SAP prompts for has only the changed entries. So, if we say we have changed or created 2 entries in the table, even if the table has 100 entries, only the 2 are included in the TR.

But, in some cases like OBYC settings, the TR created by SAP tends to include all the entries present for that transaction. Say, for BSX, we have 20 entries and we have added 2 more, all the 22 entries are included in the TR which SAP creates. In such cases, to get people off your back who are concerned about the TR contents, you can easily create a manual TR using SE16 or SE16N.

CATCH: To create a manual TR, you should be aware of all the underlying tables for the config to move correctly. Also, you need to take a call which tables are required and which are not. For OBYC, both T030 and T030R are included in an SAP TR. But, T030R is not required unless you make changes in rules for that transaction. To know the underlying tables, one way is to let SAP create a TR and then you can look at what tables are being included and take the call.

Go to SE16 transaction code and enter the table name.

Hit enter. Then input the relevant criteria to get the desired entries.

In the output screen, select the required entries by clicking on the first column(Use Ctrl + Click for multiple separate entries as shown in the screenshot or use select all button). Go to Table Entry -> Transport Entries

The next screen prompts you for a TR number. Create a TR from here or enter an already existing TR number.

The resulting TR from here has only the 4 entries we selected from the table to transport.

The same process can be done from SE16N as well.

Go to SE16N transaction code and enter the table name.

Hit enter. Then input the relevant criteria to get the desired entries.

In the output screen, select the required entries by clicking on checkbox in the first column (Use Ctrl + Click for multiple separate entries as shown in the screenshot or use select all button). Go to Table Entry -> Transport

The next screen prompts you for a TR number. Create a TR from here or enter an already existing TR number.

The resulting TR from here has only the entries we selected from the table to transport.

P.S: The intent of this blog was to make aware if someone is not aware of the process. I still recommend SAP created TR’s without manual intervention wherever possible

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply