In the last tip of this series we decribed how to get development objects out of the system. This tip focuses on how to get a transport into a system.
In SP11 (SP = Service Pack) the transport system is preconfigured. That means you no longer have to distribute the transport environment with the transaction 'STMS'. The only thing that you have to do is to share the SAP folder on the installation level. This was described at the beginning of the previous tip.
The two files for the RFC communication in the 'bin' directory are there. This was done as part of the preconfiguration.
The output of the export from the last tip must be copied to the corresponding directory in the new installation. The 'cofiles' directory is for the header of the transport (beginning with 'K'), the 'data' directory is for the data of the transport (beginning with 'R').
Now we come to the actual import. Start the Transport Management System (transaction 'STMS') and click the truck icon in the menu bar.
This is the Import Overview.
Select the NSP queue with a double-click.
Open the context menu of 'Extras' and choose 'Other Requests >> Add'. A dialog box prompts you to specify a transport request.
Click the input help icon.
Select the request you'd like to import and choose 'Enter'.
Select the transport request and click the small truck icon in the menu bar.
Enter '000' as the Target Client and leave the rest unchanged. Choose 'Enter'.
The import is now running. Click the 'Refresh' button in the menu bar to find out when the import is finished.
Start the ABAP workbench and have a look for the migrated component 'Z_MY_QUIZ' from the package 'Z_MY_PACKAGE'.
Activate the new component. To make the new component run you have to create a Web Dynpro Application for it. Select the new component, open the context menu and choose 'Create' >> 'Web Dynpro Application'. Now you can run the migrated object. Open the 'Web Dynpro Applications' folder, select 'Z_MY_QUIZ', open the context menu and choose 'Test'.
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.