Transporting SAP Objects at the OS Level Overview

Chapter 66: Transporting SAP Objects at the OS Level

Contents
Overview ................................................................................................................................................................................661 ................................................................................................................................................................................661 Checking Your Transport Parameter File (TPPARAM) ...............................................................................................................662 ...............................................................................................................662 Using the TP.EXE Executable..................................................................................................................................................666 Executable..................................................................................................................................................666 Transporting SAP Objects to Another R/3 System.....................................................................................................................668 System.....................................................................................................................668

Overview
In the chapters Using the Customizing Organizer for IMG Customization and Using the Workbench Organizer to Modify an ABAP/4 Program , we discussed modifying or customizing SAP Objects, as well as how to Export and Release them. After exporting and releasing a change request, a Project Leader can transport the changes for testing or saving in another client. The activity of transporting from a client in one R/3 System (for example, the Development R/3 System) to another client in a different R/3 System (e.g., the Quality Assurance R/3 System) by using transport tool TP is described in this chapter. In order to transport SAP objects, the TP executable delivered by SAP during the installation or upgrade of R/3 is used. TP is a C program running independently of the R/3 System that reads and writes various files. By file we mean a file in the operating system's sense, not a database table. All the files TP works with are located in a special transport directory. TP starts special programs, some of which are C programs, some of which are special operating system commands, and some of which are ABAP/4 programs.

System Landscape Transport Path (logical)

Integration Consolidation Delivery

Development

Quality Assurance

Production

To facilitate the synchronization of multiple R/3 Systems, SAP provides transport capabilities. Transporting it simply moving changes that originated in the development environment into downstream systems. In addition to the common system names, SAP has provided more technical transporting terms for a standard system landscape. Development takes place in the integration system. The integration system is used to integrate additional functionality to the SAP standard software and adapt the existing functionality to your specific requirements through customizing. Therefore, the integration system assumes the role of development.

1996 SAP Technology, Inc.

661

Transporting SAP Objects at the OS Level Checking Your Transport Parameter File (TPPARAM)

Once the developments are stable, they are transported from the integration system into the consolidation system. Here, extensive and final testing occurs. The changed objects are tested and verified in the consolidation system. This system is commonly known as the quality assurance system. After testing, all development and customizing transports that enter the consolidation system are also transported to one or more delivery systems. The production system is a delivery system.

System Landscape Transport Path (physical)

Integration Consolidation Delivery

Development
Export

Quality Assurance
Import

Production
Import

Common Transport Directory

Physically, changed objects in a three-system landscape are transported in three steps: First, all the objects for a change request to be released are exported from the source systems database to a file in the common transport directory. Secondly, the objects are imported into the target system's database. Once testing and verification take place, the objects may then be imported into any defined delivery systems.

In order to take advantage of all transport capabilities, all systems within the system landscape must share a common transport directory. This directory contains all released change requests and exported data, as well as log files that indicate the success of every export and import. By default, R/3 installation creates the shared directory called sapmnt which is used as a global share, and saploc which is used as local share. Both sapmnt and saploc are the share name of directory <drive>:\usr\sap.

Checking Your Transport Parameter File (TPPARAM)

The TPPARAM is manually created by an R/3 installer as part of post installation activities. SAP delivers a template for TPPARAM called TPPARAM.NT It is located in directory . <drive>:\usr\sap\<SAPSID>\SYS\exe\run The TPPARAM.NT is later copied to directory . <drive>:\usr\sap\trans\binand renamed to TPPARAM. The process of modifying the TPPARAM is described in chapter Completing and Checking R/3 Version 3.0 E with Oracle on Windows NT this book. of

662

1996 SAP Technology, Inc.

Transporting SAP Objects at the OS Level Checking Your Transport Parameter File (TPPARAM)

1. Follow the path <drive>:\usr\sap\trans\bin to locate the TPPARAM file.

2. To view the TPPARAM, follow the path File Run... .

3. Enter sappad TPPARAMinto the Command Line field. 4. Click OK.

3

1996 SAP Technology, Inc.

663

Transporting SAP Objects at the OS Level Checking Your Transport Parameter File (TPPARAM)

A typical example of 3.0 E TPPARAM is shown in the screen. This particular R/3 System has the following attributes: It is probably a Development System. The SAPSID is DEV. It is a central instance with a database that is located in host name pnsfo36. The host name is pnsfo36. The Computer Name is PNSFO36.

664

1996 SAP Technology, Inc.

Transporting SAP Objects at the OS Level Checking Your Transport Parameter File (TPPARAM)

For a landscape configuration with two or more systems (refer to the chapter Overviewing R/3 Architecture regarding System Landscapes), you will find other R/3 System specifications defined in the TPPARAM. This particular R/3 System has the following attributes: It is probably a Consolidation System. The SAPSID is CNS. It is a central instance with a database that is located in host name hpls3. The Computer Name is HPLS3.

5. Follow the path File Exit to end the session.

1996 SAP Technology, Inc.

665

Transporting SAP Objects at the OS Level Using the TP.EXE Executable

Using the TP.EXE Executable

TP.EXE is delivered by SAP during the installation or upgrade of an R/3 System on Windows NT. TP.EXE is used for transporting SAP objects between R/3 Systems. By default, it is located in the <drive>:\usr\sap\<SAPSID>\SYS\exe\run directory. The following examples introduce you to the TP.EXE command. 1. To locate TP.EXE executable, follow the path <drive>:\usr\sap\<SAPSID>\SYS \exe\run.

2. Normally TP.EXE is executed at the command prompt level. Start the MS-DOS prompt by doubleclicking its icon in the Program Manager. 3. If the current directory is not located in <drive>:\usr\sap\trans\bin,the additional parameter pf=<drive>:\usr\sap\trans\bin\tppa ram is needed in order to let the TP.EXE know where to find the TPPARAM. 4. If the current directory is located in <drive>:\usr\sap\trans\bin,then the additional parameter can be omitted.

5. tp help displays list of tp commands which can be used with TP.EXE.

666

1996 SAP Technology, Inc.

Transporting SAP Objects at the OS Level Using the TP.EXE Executable

The commands are divided into six categories: Exporting, Importing, Buffer Actions, Special Actions, Disk Space, and Information.

To view the argument for a tps command, you can execute tp <command>. For example, execute tp import | more.

6. This screen shows you the usage of the tp import command, which is tp IMPORT <TR>|ALL <SAPSID> [options ...], as well as a description of each component.

<TR> represents transport request. Press Enter to go the next screen...

1996 SAP Technology, Inc.

667

Transporting SAP Objects at the OS Level Transporting SAP Objects to Another R/3 System

Press Enter to go to the next screen...

Transporting SAP Objects to Another R/3 System

After releasing and exporting the SAP Object using the Customizing Organizer or the Workbench Organizer (see the chapter Using The Customizing Organizer for IMG Customization , and Using Workbench Organizer to Modify an ABAP/4 Program ), a project leader can transport the exported objects located at the Operating System level to another R/3 System based on the defined System Landscape. In a three system landscape environment, after the release and export of a change request from the Development System, a project leader can transport the exported data from the Operating System level to a Consolidation System for testing purposes. The following steps show you how to transport the change request K900002.DEVfrom DEV (Development System) to CNS (Consolidation System) by using TP.EXE command. Start the File Manager of the DEV (R/3 Development Server) Using the DEV (R/3 Development Server), you can locate ...

1. The cofile, which should be located in <drive>:\usr\sap\trans\cofiles (for example f:\usr\sap\trans\cofiles\K900002.D EV).

668

1996 SAP Technology, Inc.

Transporting SAP Objects at the OS Level Transporting SAP Objects to Another R/3 System

Using the DEV (R/3 Development Server), you can locate ...

2. The data file, located in <drive>:\usr\sap\trans\data\R9<se quence nr.>.<SAPSID> (for example f:\usr\sap\trans\data\R900002.DE V).

Start the File Manager of the CNS (R/3 Consolidation Server) Using the CNS (R/3 Consolidation Server), you can ...

3. Share the DEV (R/3 Development Server) by following the path Disk Connect Network Drive...

1996 SAP Technology, Inc.

669

Transporting SAP Objects at the OS Level Transporting SAP Objects to Another R/3 System

4. You can specify any unused drive letter as the shared drive name. Our example uses the T drive, for transport. 5. Enter the DEV machine name and the share name of DEVs <drive>:\usr\sap(e.g. \\pnsfo36\sapmnt ) The purpose of sharing is to be able to access to the defined <drive>:\usr\sap\trans\bin TPPARAM, directory <drive>:\usr\sap\trans\cofiles , and directory <drive>:\usr\sap \trans\data. After sharing, the T: drive should have the shown directories ...

4 5

Invoke the MS-DOS prompt by double clicking the icon.

6610

1996 SAP Technology, Inc.

Transporting SAP Objects at the OS Level Transporting SAP Objects to Another R/3 System

6. Go to the shared directory (e.g., T:). 7. If you wish not to use additional parameter pf=<drive>:\trans\bin\tpparam you , enter cd \trans\binwhere the TPPARAM is located. 8. To test the TPAPARAM file from CNS (R/3 Consolidation Server), enter tp go <SAPSID of Development machine>(e.g., tp go DEV ). 9. Enter tp go < SAPSID of Consolidation machine>( .g. tp go e CNS) also. Notice that we have set up the system landscape schema by defining the transport path from DEV to CNS earlier. Therefore, the CNS buffer is automatically updated whenever you execute the Release and Transport of transaction code SE09 or SE10. 10. To show the current buffer of CNS, enter tp showbuffer <SAPSID>( .g. e tp showbuffer CNS ). As it was shown earlier, the format of the tp import command is tp IMPORT <TR>|ALL <SAPSID> [options ...]. This command should be used to import the change request/transport order K900002.DEV of DEV into CNS. 11. The change request was released and exported from client 080 of DEV. This example shows you how to import to other client (e.g., client 010) into the CNS. Enter tp
import DEVK900002 CNS client=010 to start the import 11 10 6 7 8 9

process.

1996 SAP Technology, Inc.

6611

Transporting SAP Objects at the OS Level Transporting SAP Objects to Another R/3 System

Using the Quick Slice (QSLICE.EXE) tool, delivered by the Windows NT Resource Kit software, allows you to monitor the activities of import process.

12. Notice that the disp+work.exe of background job RDDIMPDP (invoked by the TP) and oracle72.exe (which is busy inserting the SAP objects) are active.
12

12

13. After finishing the import process, the screen should display R3trans.exe finished.

13

6612

1996 SAP Technology, Inc.

Transporting SAP Objects at the OS Level Transporting SAP Objects to Another R/3 System

14. If you wish to view the Log files of the import activity, open the files by using sappad.exe or notepad.exe.

14

15. To view one of the log files, open the file <source SAPSID>K9<Sequence No.>.<target SAPSID> (e.g. DEVK900002.CNS ). 16. Follow the path File Run.
15

16

17. Enter sappad DEVG900002.CNS into the Command Line field. 18. Click OK.
17

18

1996 SAP Technology, Inc.

6613

Transporting SAP Objects at the OS Level Transporting SAP Objects to Another R/3 System

19. The information is displayed. The most important item to see is the exit code (0 in this case). Return code 0 indicates that the import has been performed successfully. Return code 4 means warning (you should identify the error that has occurred). Return codes 8 and 12 mean error and severe error has occurred it is necessary for the problems to be resolved before executing the tp import again.
19

For further details refer to R/3 System Administration Made Easy Using the Customizing Organizer for IMG Customization (Ch. 63) Using the Workbench Organizer to Modify an ABAP/4 Program (Ch.64) Viewing the Transport Log of the Workbench and Customizing Organizer (Ch. 65) R/3 Basis Knowledge Products Software Logistics CD R/3 System Online Help Basis Components System Administration Transport Control Program Basis Courses Workbench Organizer, Transport System & Upgrade (BC325) Reference Implementation Workbench Development OS-level Transports

6614

1996 SAP Technology, Inc.