How to make objects in $TMP transportable

[Former Member]

Hi Guys,

I have created a lot of variants & Z-Transactions for customizing AIS (audit information system).

When i created variants for reports i saved them as local objects $TMP(which are not transportable).

Now i want to change the development class of the variants from $TMP to a development class through which i can transport this objects in other system.

Can anybody help me on doing this.

Thanks

Alam.

[Former Member]

Hi Alam,

This question is appropriate for ABAP forum but here is your answer.

1. Got to transaction SE38

2. Type your program name

3. Click on menu : Goto->Object Directory Entry

4. A dialog box will pop up. Click on the pencil icon (change icon).

5. Change the package to your new development class.

[Former Member]

Hi Prakash,

Thanks a lot for your quick response.

As you suggested i will post this question on abap forum too but the steps you gave where to change the development class for a program.

I didnt create any program but i have created lot of z-variants for report RSUSR002 and z-transaction for tables based on the databrowser SE16.

Then i created roles and attached that report with z- variants.

I saved all the variants as local objects ($TMP) and now i want to change the development class for z-variants and z-transportable to another development class through which they will be transportable.

Can it done from SE80 or do i need to recreate these variants and z-transactions.

Please help me out on this.

Thanks in Advance.

Alam.

[nablan_umar]

Hi Mohammed,

How did you save your variant as $TMP. Normally it does not prompt you for transport since variants are not considered as transportable unless you manually want it transported using program RSTRANSP.

[Former Member]

Hi Mohammed,

When you save variants, they are always saved as local objects and are also client specific. If you want the variants to be automatically transported you can follow the naming convention as defined here. Alternatively you can use the program RSTRANSP to transport the variants.

"Names of variants: Names can consist of up to 14 alphanumeric characters. The "% " character is not allowed. If you want the variant to be transported automatically with its program, you must create a system variant. The name of a system variant starts "CUS&" for customers, and "SAP&" for SAP system variants. You can only use the "&" character within this prefix in the name of a system variant. It may not occur in any other context. System variants are administered by the Workbench Organizer. Although you can create and access variants from any client, they are always stored in client "000"."

As far as the transaction codes are concerned, you can go into change mode for the transaction, and in the menu, choose "Go to-->Object Directory Entry" and change the development class in the pop-up box that comes up.

Hope this helps,

Srinivas

[Former Member]

Hi Umar & Srinivas,

Thanks a lot

I was able to use the report RSTRANSP to transport the variants.

Thanks

Alam.