SAP Transport Variant – Best Practices

A SAP transport variant is necessary for  transporting reports. One can do this manually by selecting the variant you want to transport and entering the details LIMU VARX program name and variant name in the exact order. Variants are important when the selections being used for reports of programs are similar.

SAP Transport Variant – Best Practices

Before the variants can be transported across systems, they will have to undergo conversion. Variants are therefore converted before they are transported to another system and after they have been transported.

Driving Business Value Through UC - Sap-ebook-banner

Conversion before transportation involves opening the screen for mass maintenance tool and selecting the Extras option. Select Variant Transport from the options and choose Prepare. Enter the type of object you want converted on the screen then select the exact variant you want and press Execute.

The converted variant then needs to be included in the transport request. To do this, select Extras, then Variant Transport and choose the option to Include in Transport Request. A dialogue box will appear where you have to give details of the request and press Enter. A screen will come up and one will need to choose the necessary variants in the table provided. When complete, select the option Include in Request.

One can delete some of the variants that had been converted from the transportation list by selecting Extras, then Variant Options. From the Mass Maintenance Tool screen, select Maintain Transport Table. The converted variant will not be eliminated, just the copy meant for transport.

After transporting the variant, convert it back using the Mass Maintenance Tool screen from the target system. Select Extras, then Variant Transport and choose the Import Option. A screen will appear where you will specify the type of object and variant and select to execute.

There are quite a number of simple ways in which one can transport a variant. One involves running RSTRANSP report with the use of SE38.

Another way is still using SE38 and selecting the variants button which will open the variant screen. Highlight the variant option and choose transport from the menu provided.

Using SE16 to transport variant and the layout set will need one to open the ALV reports and go to the settings. From the settings, select Layout and from the options, choose Manage Layout then select the variant lines layout. From here, just choose transport to complete the process.

Variants can be moved from the program or the report to a different system in SAP. One can in addition simply transport the entire system and the variants will shift with it. Transporting the report will also have the variants transported but not all. Those that begin with CUS will be the only ones shifting together with the report.

In the transport request, variants can be added using a few steps. This includes entering the name of the program which is RSTRANSP in the code of transaction SE38. Enter the name of the program and that of the variant after running the program. A screen will emerge asking you to select the variant you want transported. Choose the variants you want to transport and press continue then enter.

Variants can also be copied between different clients in SAP

Upon making a request for transporting variants in SE38, one can then copy the changes they have made between different clients. This will be possible using SCC1.

Copying the change to the new client will include logging in to the target client option and selecting the SCC1 transaction. Key in details of the client you want to copy from and modify the request number. Once you’re done, click on Execute.

SAP Transport for an ALV variant

This will involve running the ALV ABAP report and select setting from the menu choices. Select Layout and then choose Layout Management.

Make a selection from the listed variants, the variant from ALV ABAP you intend to transport. From the menu layout choice above, select Transport.

To enable the perfect transportation of objects and data between clients and systems, SAP has a tool referred to as the SAP Transport Management System (STMS).

Best Practices

  • Keep records of the transport log to remain updated on the status of the transport being carried out.
  • Wait for the stabilization of the development before beginning the transportation process. The objects once they have been created will need time before they are ready to be transported.
  • When transporting variances, ensure that you are following the correct steps. Poor sequence of transporting variables will result to mistakes. When transporting multiple objects, ensure to do it a set at a time. Give the system time to ensure that the variables are fully transported before transporting the following set. Transport them in the correct sequence as well without importing sets together.
  • BW transports should not be made before the importation of ECC transports which are needed by BW transports. BW transport should also not be started before replication of the ECC Data Sources.
  • Avoid making changes in QA or PROD directly. These clients should not be free for manual changes as they will cause the DEV QA PROD sync to break.

Once you change your mind about making the transport, do not delete the request from the DEV system. This will make it harder to manage the items transported and have a negative effect on the process of control. Instead, change the name to DO NOT TRANSPORT and request BASIS to stop the importation of the transport request.

On the transaction SE38, open the variants screen. Form the Utilities menu, choose The Information About Maintaining Variants option. This will provide you with the details you need for knowledge on how to maintain the variables.

Using the RSTRANSP program by SAP documents, entries for the transportation of the variants are generated. This allows for the generic entry of the variables that you want to transport.

RSTRANSP is a program used for the transportation of variants in SAP ABAP. It is executed through the transaction SE38. One can also choose to transport multiple variants from a program and they will need to execute the RSTRANSP program. This is by entering the name of the program, that of the variant or both. Using this method it is possible to move more than one program at the same time.

For all the development classes, SAP transport variant can be done but not for the $TMP development class.

Marissa Hart is the Lead Author & Editor ShareMe. ShareMe is a blog focused on SharePoint Online. SharePoint Online delivers the powerful features of SharePoint without the associated overhead of managing the infrastructure.