Moving sets across SAP allows for flexibility of data across the entire system. Creating a set uses the transaction code GS01 with each set having allowances for substitution and validation. The SAP transport system supports using sets optionally to move content from one node to another node within the system. The thing that you need to remember is that migrating sets to new nodes may mean that the existing data that overlaps with those sets may be annihilated and replaced with the moved data. Here are a few ways to ensure that this unfortunate circumstance doesn’t befall you when being transported from one node to another.
1. Export – Import Option
By combining the data to be moved into a single file, you make it more compact and less likely to cause interference on the system to which it’s being moved. The Export-Import system included in SAP can be accessed via transaction code GS02. In the screen that pops up, you will open the Utilities menu and select Transport -> Export. A window will pop up that will allow you to select the sets which you want to store within this file. At the bottom of this screen is an input field where you can specify where you want the file to be stored. Once the criteria have been selected, you can run the report. This leads you another screen that offers you options based on which sets (if any) meet the criteria. There may be multiple sets appearing on this screen, but you will only select the ones you are interested in exporting. Selecting the set and running the report creates the file which you can then move around to other systems. Importing the file is as simple as running transaction code GS02 again and going to Utilities->Transport->Import. In the following popup, you will have to specify the location of the file you want to import. The sets will be imported and you’ll be notified with a confirmation dialog box.
2. Copying from Client
The option to copy sets across from a development to a test client exists with the copy from client functionality. Once again you will run transaction code GS02 and hit Utilities -> Transport -> Copy from Client. The steps that you go through are similar to the steps you went through for the Export – Import option. Simply repeat the steps specified above until the confirmation dialog box informs you that the copy is completed successfully.
3. Moving with Transport
This method utilizes the built-in functionality of the SAP system – specifically the transport system – to move data between clients. Once again you run transaction code GS02. We open the menu Utilities -> Transport -> Transport Request. The system used by IT support Toronto, will ask you to specify between Variables and Sets. Select Sets and execute the command. The selection screen that follows is similar to the one we have seen already in the previous methods, but there is no input field for a filename. After selecting the criteria you want in your included sets, the next page presents you with the sets that fit those criteria, if any. You can select the ones you intend to move to other systems of your choice, and run the report a second time. A popup window will show up prompting you for a transport request number. When you’re finished with that, the transport request is ready to be moved over to another system.
Getting used to how the transport system works is a bit more complex than simply understanding a file system. SAP uses the transport system to make sure that data sent over the system gets to where it’s going in a secure and concise manner. The unorthodox movement of the data might take a little while to get used to but generally, once you figure out how the transport system gets data across the network, it’s easy to do specific set updates without needing to deal with the rest of the data contained in each system.