The last part of this series was about the CTS (Change and Transport System), where you got a brief overview of the transport mechanism on the ABAP Application Server. This tip explains what you have to do to get a package with your development objects out of a system. For our purposes, exporting a package means to get it out of the ABAP universe to the installation level.
Let's assume that you have created some programs or Web Dynpro components in the old (SP8) Trial Version and you want to upgrade the Trial Version to SP11. You use the transport system to save your programs and components and make them availiable in the new system.
You first need to set up the Transport System for the export.
On the installation level, the 'SAP' directory must be shared to the 'System' user. Open the MS Explorer, select the 'SAP' directory and choose 'Sharing and Security...' from the context menu. Select the 'Share this folder' option, and enter 'sapmnt' as the share name.
Add a new user 'SYSTEM' with full control.
Choose 'Apply' and then 'OK'.
Now the changes on installation level are complete. To set up the transport environment, you need to start the Transport Managment System (Transaction STMS).
Choose 'System Overview' (red rectangle) and select 'CL5' from the table. Open the context menu, and choose 'Extras'. Then, choose 'Distribute and Activate Configuration'.
Leave the distribution options as the default. Choose 'Enter'.
After you have successfully distributed the transport environment, there are two files in the 'bin' directory of the 'trans' tree on the installation level. These files are required by the RFC (Remote Function Call) to retrieve information about the receiver side.
The tree should look like this. Now the setup of transport system is complete.
In our example, we assume that there is a development object 'Z_MY_QUIZ' in an old Trial Version (SP8) that you need to migrate to the new Trial Version (SP11), since you can have only one ABAP Trial Version on your PC. This object is a copy of the 'WDT_QUIZ' Web Dynpro ABAP component in the Trial Version.
To export an object, it must belong to a package.
How to create a package is shown in the previous tip in this series. The package for migration in this tip is 'Z_MY_PACKAGE'.
Let's assume that the object you want to migrate is created as a local object. (new users do not normally concern themselves with packages and workbench orders.)
You first need to reassign the object to a package. Go to the ABAP workbench (SE80) and select the component you want to reassign.
This would be the right way to reassign the object, but be careful: there is a bug in the current version. Mime objects will not be written to the export. For that you need to copy the component to a new object that is related to a package.
The system prompts you with the workbench request to create the package. This request will comprise all the objects from the package, and will be the basis of the transport.
There may be another dialog step - confirm this in the same way.
Now the package Z_MY_PACKAGE which contains all the objects in the Web Dynpro Component/Application Z_MY_QUIZ is linked to the workbench order NSPK900044. In the following steps, this order and the related tasks will be released.
Open the transport organizer (transaction SE09). You will find the virtual system 'CL5' as the destination of our transport.
Select the correction (NSPK900045) for our workbench order, and click the truck icon in the menu bar. This releases the correction. A released correction cannot be changed. To release a workbench order, all the related corrections must be released first. After releasing the correction, an OK icon appears right to the correction.
You process the workbench order in the same way. Place the cursor on the workbench order and click the truck icon in the menu bar. This starts the physical transport.
To find out when the transport is finished, you will have to refresh a couple of times.
Now the transport is complete. On the level of the intallation, there is data written to two files.
The 'cofiles' directory contains the header information in a file beginning with 'K' followed by the workbench order number and ended with the system ID.
The transport data can be found in the 'data' directory beginning with 'R' followed by the workbench order number and ended with the system ID.
These two files can be copied to the corresponding directories in any other SAP system in order to be imported. This will be the topic of the next tip.
Manfred Lutz is in Netweaver Product Management with focus on Application Servers.
This content is reposted from the SAP Developer Network.
Copyright 2007, SAP Developer Network
SAP Developer Network (SDN) is an active online community where ABAP, Java, .NET, and other cutting-edge technologies converge to form a resource and collaboration channel for SAP developers, consultants, integrators, and business analysts. SDN hosts a technical library, expert blogs, exclusive downloads and code samples, an extensive eLearning catalog, and active, moderated discussion forums. SDN membership is free.