Transport at Os Level

8/3/2019 Transport at Os Level

1/14

Transporting SAP Objects at the OS LeveTransporting SAP Objects at the OS Leve

OverviewOverview

1996 SAP Technology, Inc. 661

Chapter 66:Chapter 66: Transporting SAP Objects at the OS LevelTransporting SAP Objects at the OS Level

ContentsContents

OverviewOverview................................................................................................................................................................................................................................................................................................................................................................661661Checking Your Transport Parameter File (TPPARAM)Checking Your Transport Parameter File (TPPARAM)..............................................................................................................................................................................................................................662662

Using the TP.EXE ExecutableUsing the TP.EXE Executable....................................................................................................................................................................................................................................................................................................666666

Transporting SAP Objects to Another R/3 SystemTransporting SAP Objects to Another R/3 System..........................................................................................................................................................................................................................................668668

OverviewOverview

In the chapters Using the Customizing Organizer for IMG Customization and Usingthe WorkbenchOrganizer to Modify an ABAP/4 Program ,we discussed modifying or customizing SAP Objects, as wellas how to Export and Releasethem. After exporting and releasing a change request, a Project Leader cantransport 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 upgradeof R/3 is used. TP is a C program running independently of the R/3 System that reads and writes variousfiles. By file we mean a file in the operating system's sense, not a database table. All the files TP workswith are located in a special transport directory. TP starts special programs, some of which are Cprograms, some of which are special operating system commands, and some of which are ABAP/4programs.

System Landscape Transport PathSystem Landscape Transport Path (logical)(logical)

IntegrationIntegration DeliveryDelivery

Production

ConsolidationConsolidation

DevelopmentQuality

Assurance

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 downstreamsystems. In addition to the common system names, SAP has provided more technical transporting termsfor a standard system landscape.

Development takes place in the integration system. The integration system is used to integrate additionalfunctionality to the SAP standard software and adapt the existing functionality to your specificrequirements through customizing. Therefore, the integration system assumes the role of development.


2/14

Transporting SAP Objects at the OS LevelTransporting SAP Objects at the OS Level

Checking Your Transport Parameter File (TPPARAM)Checking Your Transport Parameter File (TPPARAM)

662 1996 SAP Technology, Inc.

Once the developments are stable, they are transported from the integration system into the consolidationsystem. Here, extensive and final testing occurs. The changed objects are tested and verified in theconsolidation system. This system is commonly known as the quality assurance system.

After testing, all development and customizing transports that enter the consolidation system are alsotransported to one or more delivery systems. The production system is a delivery system.

System Landscape Transport Path (physical)System Landscape Transport Path (physical)

IntegrationIntegration DeliveryDelivery

Production

ConsolidationConsolidation

DevelopmentQuality

Assurance

Export Import Import

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 databaseto 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 deliverysystems.

In order to take advantage of all transport capabilities, all systems within the system landscape must sharea common transport directory. This directory contains all released change requests and exported data, aswell 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, andsaploc which is used as local share. Both sapmnt and saploc are the share name of directory:\usr\sap.

Checking Your Transport Parameter File (TPPARAM)Checking Your Transport Parameter File (TPPARAM)The TPPARAM is manually created by an R/3 installer as part of post installation activities. SAP deliversa template for TPPARAM called TPPARAM.NT. It is located in directory:\usr\sap\\SYS\exe\run. The TPPARAM.NTis later copied to directory:\usr\sap\trans\binand renamed to TPPARAM. The process of modifying the TPPARAM isdescribed in chapter Completing and Checking R/3 Version 3.0 E with Oracle on Windows NTof this book.


3/14


Checking Your Transport Parameter File (TPPARAMChecking Your Transport Parameter File (TPPARAM


1. Follow the path:\usr\sap\trans\bin tolocate the TPPARAM file.

2. To view the TPPARAM, follow the

path File Run... .

3. Enter sappad TPPARAMinto theCommand Line field.

4. Click OK.

1

2

3

4


4/14


Checking Your Transport Parameter File (TPPARAM)Checking Your Transport Parameter File (TPPARAM)


A typical example of 3.0 E TPPARAMis shown in the screen. This particularR/3 System has the followingattributes:

It is probably a Development

System.

The SAPSID is DEV.

It is a central instance with adatabase that is located in hostname pnsfo36.

The host name is pnsfo36.

The Computer Name is PNSFO36.


5/14


Checking Your Transport Parameter File (TPPARAMChecking Your Transport Parameter File (TPPARAM


For a landscape configuration with twoor more systems (refer to the chapterOverviewing R/3 Architectureregarding System Landscapes), youwill find other R/3 System

specifications defined in theTPPARAM. This particular R/3System has the following attributes:

It is probably a ConsolidationSystem.

The SAPSID is CNS.

It is a central instance with adatabase that is located in hostname hpls3.

The Computer Name is HPLS3.

5. Follow the path File Exit to endthe session.

5


6/14


Using the TP.EXE ExecutableUsing the TP.EXE Executable



TP.EXE is delivered by SAP during the installation or upgrade of an R/3 System on Windows NT. TP.EXEis used for transporting SAP objects between R/3 Systems. By default, it is located in the:\usr\sap\\SYS\exe\rundirectory. The following examples introduce you to the

TP.EXE command.

1. To locate TP.EXE executable,follow the path:\usr\sap\\SYS\exe\run.

2. Normally TP.EXE is executed atthe command prompt level. Startthe MS-DOS prompt by double-clicking its icon in the ProgramManager.

3. If the current directory is notlocated in:\usr\sap\trans\bin,theadditional parameterpf=:\usr\sap\trans\bin\tpparamis needed in order to let theTP.EXE know where to find theTPPARAM.

4. If the current directory is located in:\usr\sap\trans\bin,then

the additional parameter can beomitted.

5. tp helpdisplays list of tpcommands which can be used withTP.EXE.

1

2

3

4

5


7/14




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

To view the argument for a tpscommand, you can execute tp

.For example, executetp import | more.

6. This screen shows you the usage ofthe tp importcommand, which is tpIMPORT |ALL [options ...],as well as a descriptionof each component.

represents transport request.

Press Enter to go the next screen...

6


8/14


Transporting SAP Objects to Another R/3 SystemTransporting SAP Objects to Another R/3 System


Press Enter to go to the nextscreen...


After releasing and exporting the SAP Object using the Customizing Organizer or the WorkbenchOrganizer (see the chapter Using The Customizing Organizer for IMG Customization , and UsingWorkbench Organizer to Modify an ABAP/4 Program ), a project leader can transport the exportedobjects 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 requestfrom the Development System, a project leader can transport the exported data from the OperatingSystem 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 DevelopmentServer), you can locate ...

1. The cofile, which should be locatedin :\usr\sap\trans\cofiles(for examplef:\usr\sap\trans\cofiles\K900002.DEV).

1


9/14




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

2. The data file, located in:\usr\sap\trans\data\R9.(for example

f:\usr\sap\trans\data\R900002.DEV).

Start the File Manager of the CNS

(R/3 Consolidation Server)

Using the CNS (R/3 ConsolidationServer), you can ...

3. Share the DEV (R/3 DevelopmentServer) by following the path Disk

Connect Network Drive...

2

3


10/14




4. You can specify any unused driveletter as the shared drive name.Our example uses the T drive, fortransport.

5. Enter the DEV machine name andthe share name of DEVs:\usr\sap(e.g.\\pnsfo36\sapmnt)

The purpose of sharing is to be ableto access to the defined:\usr\sap\trans\binTPPARAM,

directory:\usr\sap\trans\cofiles,

and directory :\usr\sap

\trans\data. After sharing, the T: drive should

have the shown directories ...

Invoke the MS-DOS prompt bydouble clicking the icon.

4

5


11/14




6. Go to the shared directory (e.g., T:).

7. If you wish not to use additionalparameterpf=:\trans\bin\tpparam, youenter cd \trans\binwhere theTPPARAM is located.

8. To test the TPAPARAM file fromCNS (R/3 Consolidation Server),enter tp go (e.g., tp go DEV).

9. Enter tp go < SAPSID ofConsolidation machine>(e.g. tp goCNS) also.

Notice that we have set up thesystem landscape schema bydefining the transport path fromDEV to CNS earlier. Therefore, theCNS buffer is automaticallyupdated whenever you execute theReleaseand Transport of transactioncode SE09 or SE10.

10. To show the current buffer of CNS,enter tp showbuffer (e.g.tp showbuffer CNS).

As it was shown earlier, the format

of the tp import command is tpIMPORT |ALL [options ...]. This command shouldbe used to import the changerequest/transport orderK900002.DEV of DEV into CNS.

11. The change request was releasedand exported from client 080 ofDEV. This example shows youhow to import to other client (e.g.,client 010) into the CNS. Enter tp

import DEVK900002 CNSclient=010to start the importprocess.

6

7

8

9

10

11


12/14




Using the Quick Slice(QSLICE.EXE) tool, delivered bythe Windows NT Resource Kitsoftware, allows you to monitor theactivities of import process.

12. Notice that the disp+work.exeofbackground job RDDIMPDP(invoked by the TP) andoracle72.exe(which is busy insertingthe SAP objects) are active.

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

12

12

13


13/14




14. If you wish to view the Log files ofthe import activity, open the filesby using sappad.exeor notepad.exe.

15. To view one of the log files, openthe file K9. (e.g. DEVK900002.CNS).

16. Follow the path File Run.

17. Enter sappad DEVG900002.CNSinto the Command Linefield.

18. Click OK.

14

15

16

17

18


14/14




19. The information is displayed. Themost important item to see is theexit code(0 in this case).

Return code 0 indicates that theimport has been performed

successfully.

Return code 4 means warning (youshould identify the error that hasoccurred).

Return codes 8 and 12 meanerrorandsevere error has occurredit isnecessary for the problems to beresolved before executing the tpimport again.

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 Reference Implementation Workbench Development OS-levelTransports

R/3 System Online Help

Basis Components System Administration Transport Control Program

Basis Courses

Workbench Organizer, Transport System & Upgrade (BC325)

19

Documents

Transport at Os Level