How to create “transport of copies” related transport request in SAP?

This article answers following queries:

How to take backup of Printer settings, processing groups, logon groups, logical systems, operation mode settings, RFCs, AL11(sap directories), SE03 (transport organizer tools), SM69, oaco(archive related) settings?

How to create “transport of copies” related transport request in SAP?

What is the use of “transport of copies” related transport request in SAP?

Which transaction is used to create transport request in SAP?

-----------------------------------------------------------------------------------

SE01 transaction is used to create transport request in SAP.

As part of pre-refresh steps, we need to take backup of target system’s

• Printer settings (SPAD)
• Processing groups (RZ12)
• Logon groups(SMLG)
• Logical systems (BD54)
• Operation mode settings(RZ03/RZ04)
• RFCs related information(SM59)
• AL11(sap directories)
• SE03 (transport organizer tool settings)
• Batch processing relation information (SM61)
• Customer entries information (SM69)
• Archive related settings (OAC0)

If we have backed them up in a transport request, it is easy for us to import them later in the target system. If we haven’t backed them up, we may have to manually create all these entries which will be a tedious and time consuming task. So, we have to backup all these entries.

In the backend, all the above configurations will be stored in specific tables. If we can identify and include those tables in a transport request and export, then we can import it back whenever these settings are required during post refresh.

 We need to create a transport request of type “Transport of Copies” to serve this purpose

To create the same, Go to SAP transaction SE01 à Create Request à select Transport of Copies

Click on Green Check Mark in the above screen.

This will prompt you to create a transport request as seen below

Please provide Short Description for the transport request (in the above screen) and input the appropriate client in Target. Other fields will get populated automatically.

This will create a transport request as shown below.  

Double Click the transport number and add the tables information (highlighted in yellow in the below paragraph) in the respective columns of the transport request. After that, these configurations can be imported in post refresh stage.

          AL11  – User Directory Entries are contained in the following tables

          R3TR TABU USER_DIR                    Keys   *

          SE03 – System Change Options are contained in the following tables

          R3TR TABU TRNSPACEL     Keys   *

          R3TR TABU DLV_SYSTC      Keys  *

          SMLG/RZ12 – Logon Groups and Processing Groups are contained in the   

          following table.

          R3TR TABU RZLLITAB         Keys   *

         SM59 Connections – RFC connections are contained in the following tables

          R3TR TABU RFCATTRIB      Keys  *

          R3TR TABU RFCDES           Keys  *

          R3TR TABU RFCDOC          Keys  *

          SALE – Logical Systems are contained in the following tables

          R3TR TABU TBDLS          Keys   *

          R3TR TABU TBDLST        Keys    *

          SM69 – Export Customer Entries contained in the following table

          R3TR TABU SXPGCOSTAB  Keys   Y* & Z*

          Oca0 – Archive Settings

          R3TR TABU CREP_HTTP     Keys   *

          SPAD – Printer Settings

          R3TR TABU TSPSV               Keys   *

          SM61 – Batch Processing    

          R3TR TABU TSRVGRP          Keys   *

          R3TR TABU TSRVLST           Keys   *

          RZ03/RZ04 – Operation Modes  & RZ20 settings

          R3TR TABU TPFBA               Keys   *

          R3TR TABU TPFHT               Keys   *

          R3TR TABU TPFID               Keys   *

           

Include all the above tables details in the transport request and save.   

NOTE:  Please make sure to release this transport before the refresh starts.  Otherwise the cofile and datafile will not generated and you will not be able to import this transport later. If we can’t import request, then we may have to create/maintain all these configurations manually which will be tedious and complex task.