You are on page 1of 59

TMS(1)

Why Transport Management System


Within the R/3 System Landscape customizing & development changes performed
in a development client , has to transfer to QAS client & PRD client .
SAP R/3 enables user to record changes to a CHANGE REQUEST ,which is
distributed to other client or other R/3 system .
When changes to either customizing or repository objects are made,the changed
objects are recorded to a TASK in a Change Request corresponding to a specific
user .
Change Requests & Tasks provide a complete history of all changes made during
R/3 implementation .
If TMS is not configured properly (ie inconsistent) then we may not be able to
create transportable change request .
After SAP R/3 installation we have to configure TMS for the following reasons :
To create transportable change request
To import transport request
To setup Global Transport System between R/3 systems
To transport clients between R/3 systems

TMS(2)
Why Transport Management System
The R/3 change management system, also known as the Change and Transport
System (CTS), provides options for data transfer between and within R/3 Systems.
The tool can be used, to transport tuned and tested customizing settings between
systems and clients.
Using transport requests and customizing settings, development work created in a
separate development system (DEV) can be automatically recorded in change requests
and then transported into a quality assurance client, and finally into a production client.
Once the change request has been released from the source system, it becomes a
transport request.
Development / Correction
Most changes are recorded to development/correction tasks which contain changes to
objects that originated in the current R/3 system .
Repair
A repair is a change to an R/3 repository object that originated on an r/3 system other
than the current R/3 system .The object be an sap delivered object or customer
developed object.

TMS(3)
To activate customizing changes permitted in a particular client ,and whether these
Customizing changes are automatically recorded to a change request ,have to set
Changes and transports for client-specific objects using the transaction code SCC4

TMS(4)
To permit or disallow create or changes to R/3 repository objects from any client ,
have to set Client independent object changes using the transaction code SCC4

Change Request (1)

Types of CHANGE REQUEST


Customizing Change Request
Used for record only client dependent changes using IMG .And after completion
of customizing , the changes can be transport to other r/3 system .
To manage the customizing change request we use transaction code SE10 .
Workbench Change Request
Used for client independent (cross-client) customizing objects and all repository
objects created or maintained through the ABAP workbench .
To manage the workbench change request we use transaction code SE09 .
Transportable Change Request
The change requests which are transported to other R/3 systems after release .
Local Change Request
A change to an R/3 repository object in a development system but not
transportable to quality or production system will be recorded to a local change
Request .
Local change request can be released but not transportable .

Change Request (2)


Example of a change request : SCMK900210
The ID number of a change request or tasks begins with the three
character system-ID SCM . Followed by K9 . Then five digit
number
00210 .
Next task will be SCMK900211 .
If project leader assign another user to the change request then another task will
create with ID SCMK900215.
A change request is a collection of tasks .

Change Request (3)


To release the Change Request ,each separate task in the change request must be
documented & released separately .using the button

Releasingthe
thetask
task
Releasing
SCMK900212
SCMK900212

Followthe
themessage
message
Follow

Exporting change request


This is the physical copying of the recorded objects from the database of the R/3
system to files at the operating system level .
This files are located in the transport directory .
Operating system level file K900210.scm created on directory /usr/sap/trans/cofiles
& the file R900210.scm created on directory /usr/sap/trans/data & the file
SCME900143.SCM created on directory /usr/sap/trans/log .
The file extension will be the source system sid name .

Transport
directory(1):
Transport directory
is a file system located on OS level where the objects in change
requests that were released and exported from that R/3 system are physically copied so
that they can subsequently be imported to a target R/3 system.
/usr/sap/trans is the parent transport directory
Often in a system landscape there is only one common transport directory .
All R/3 systems that share the same transport directory make up a TRANSPORT
GROUP.
If the transport directory is not shared with other systems ,it is called the Private transport
directory .

DEV
DEV

QAS
QAS

Common
Common
transportdirectory
directory
transport

Transport Group 1

PRD
PRD

Private
Private
transportdirectory
directory
transport

Transport Group 2

Transport directory(2):
One or Many Transport Directory :
The network connection to an R/3 system is not fast enough .
There is no permanent network connection between the different R/3 systems of the
system landscape .
There are security reasons that prevent direct access to an R/3 system (like PRD).
There are different hardware platforms that do not allow a common transport
directory.
Common transport directory is standard practice .
When more than one transport directory ,then manual transfer the operating system
level file from server to server.
Every computer of the transport group on which an R/3 instance is installed should
have write access & read access to the transport directory.

Transport directory(3):

\usr\sap\trans
\usr\sap\trans
eps

bin
data
cofiles

olddata
sapnames

buffer
log

tmp

actlog

Transport directory(4):
bin : This directory contains TP_<domain>.PFL (e.g. TP_DOMAIN_SCM.PFL) file
which is the mainly transport parameter file .
data : This directory contains actual data file of the related change requests with the
customizing & development changes . (e.g. R900210.scm ) .
cofiles : This directory contains control files or change request information files used by
the transport tools on the OS level (e.g. K900210.scm ) .
buffer : This directory contains an import buffer for each R/3 systems in a transport
group.which contains the info of which change requests are to be imported in which system .
log : This directory contains all types of log files about the export , import of change
requests (e.g. SCME900143.SCM ) .
actlog : This directory stores the log of user actions in R/3 for all change requests & tasks
like date/user of creation & release of CR (e.g. SCMZ900143.SCM ).This directory is
accessed by CTO only.
olddata : This directory is needed when we clean up the transport directory.Old exported
data that is to be archived or deleted is stored in this directory .
eps : This is download directory for SAP support packages from SAPNET .

Transport directory(5):
Technical info about transport directory
Every computer of the transport group on which an R/3 instance is installed should
have write access & read access to the transport directory.
Estimate 100 MB per R/3 instance that will be using the transport directory .
To share common transport directory ,all application & database servers must be in the
same windows NT domain or if domain differs create NT trusted relationship between
them.
Set a global share sapmnt to point the directory \usr\sap files .
Then \usr\sap\trans files can be access as \sapmnt\trans .
Set NT access type Full Control for Everyone on this transport directory .
Must define the transport host using the alias SAPTRANSHOST . For this have to
make an entry on file c:\winnt\system32\drivers\etc\hosts
92.83.18.149 scma SAPTRANSHOST .

Transport directory(7):
Preparing Operating System Users:
If we want to install tp, the operating system users must fulfill the
following:
Each user that wants to use the transport system requires read
and write authorization in the transport directory.
If you call a transport program directly from the operating
system level, only use the operating system user <SAPSID>ADM ,
SAPService<SAPSID>

Performing import
Imports are normally not performed by the developer who requested
an export, but by the system administrator.
For import the administrator must log onto the operating system of
a host in the target
system as the user <sapsid>adm.
we can start a complete import with the following command:
cd \usr\sap\trans\bin
tp addtobuffer SCMK900211 PRD
tp import SCMK900211 PRD client100 --- Importing one change request
tp import all PRD client100

--- Importing all change requests

In the SAP System, there are 2 background events that are triggered
by tpat
the beginning and/or end of an import with tpimportalland with
tpput:
SAP_IMPORT_START , SAP_IMPORT_STOP

The Route of a Request into the Target System

1.

2.

3.

The
The transport
transport of
of aa request
request begins
beginswhen
whenthe
the owner
ownerof
of the
the request
requestreleases
releasesitit

After
Afterreleased
released ,, itit isisunlocked
unlockedand
and the
the data
dataisisexported
exportedto
to OS
OSlevel
level

tp
tpregisters
registers that
thatthe
the request
request has
hasto
to be
be imported
imported into
intothe
the target
target system.
system.

4.

Perform
Perform import
importto
to the
the target
target system
systemusing
using the
the STMS
STMSwhich
whichcalls
callstp
tp

7.

The
Theobject
objectwill
willtransferred
transferredto
totarget
targetsystem
system

Configure Transport Management System


Before starting work with the Transport Management System (TMS),
We must configure it in all SAP Systems in system landscape.
In Configuring the transport domain we define which SAP systems in

system landscape form a transport domain, and which SAP system is to


be the transport domain controller.
In Configuring the transport routes the transport routes are used to
define in which target system we want to consolidate change requests,
and which SAP Systems are forwarded this information automatically.
In transport domain, the SAP System that is configured as the domain
controller is of special significance. If this SAP System fails, we cannot
make changes to the TMS configuration during this time. Therefore if
transport domain contains more than three SAP Systems, SAP
recommend configuring a backup domain controller.If domain controller
fails, the backup controller can assume the function of the domain
controller.

Configuring the Transport Domain(1)


To configure and maintain the transport domain we need the
authorization S_CTS_CONFIG contained in the profile S_A.SYSTEM.
First, we must decide which SAP System we want to configure as the
transport domain controller
We can only carry out all the activities relevant to the entire transport
domain, such as configuring transport routes or configuring RFC
connections, in the domain controller.
The transport domain controller should normally be configured in a
production system or quality assurance system.

Configuring the Transport Domain(2)


1.

Log on in client 000 in the SAP System that we want to configure as


the transport domain controller.

2. Enter Transaction STMS. The dialog box TMS: Configure Transport


Domain appears.
3. Enter the name and a short description of the transport domain.
4. Save your entries. The following actions are performed automatically in
SAP System:
The user TMSADM is created.
The RFC destinations required for the TMS are generated.
The TMS configuration is stored in the transport directory.
The transport profile for the transport control program tpis
generated.
The SAP System is configured as a single system

Configuring Virtual SAP Systems


We may not want to install all the SAP Systems we have planned for
system landscape at the same time. However, we can use TMS to
configure SAP Systems as virtual systems in the transport domain so
that we can model the transport routes of our whole system landscape.
To configure a virtual system:
1. Log on to the SAP system (In transport domain controller)
2. Call Transaction STMS.
3. Choose Overview Systems. The system overview appears.
4. Choose SAP System Create Virtual system.
The dialog box TMS: Configure Virtual System appears.
5. Enter the name and a short description of the SAP System.
The domain controller is proposed as the communications system.
The communications system is required to act as a substitute for
accessing the transport directory.
6. Save entries and confirm that we want to distribute the configuration
change to all real SAP Systems.

Configuring the Transport Control Program tp


The transport control program tp requires a transport profile that
contains information about establishing the database connection for
all SAP Systems in the transport domain. TMS generates and
manages this transport profile as a part of the transport domain
configuration.
Must enter the necessary profile parameters for this SAP System in
the transport profile TPPARAM using a text editor.

tp / r3trans /tpparam (1)


Transport Control Program tp
Transport control program tp is an utility to transports objects
between the sap system & Upgrading the sap release.
tp is called by the other programs
Change & Transport System (CTS)
Transport Management System (TMS)
Upgrade control program R3up (Upgrade control program)
R3trans Program
This sap program uses to transport data between the sap systems
& the migration between the different sap release.
Mainly R3trans is called by the programs tp & r3up
Transport profile (tpparam)
This is a global parameter file used by tp & administrated by SAP TMS
.
For each transport group there are one transport profile .The transport profile contains
the settings needed to configure the transport control program tp & transport program
r3trans .
Transport profile file stores in the directory sapmnt/trans/bin directory with names
TP_DOMAIN_SCM.PFL. .
The line in this file preceded by # is a comment line .

tp / r3trans /tpparam (2)


In time of setting up transport profile the file TPPARAM.TPL copy to subdirectory
\usr\sap\trans\bin directory as a file name tpparam .
All SAP Systems should have unique names. Transport only possible
between SAP systems that have different names.
If we have several SAP Systems with the same names, transporting is
impossible because the target system of a transport is not unique.
Do not use any of the following names as the system name:
ADD, ALL, AND, ANY, ASC, COM, DBA, END, EPS, FOR, GID, INT, KEY, LOG,
MON, NOT, OFF, RAW, ROW, SAP, SET, SGA, SH0, SID, UID, VAR
Transport profile parameters :
SID /DBHOST

= scma (hostname of the database server )

SID /DBNAME

= SCM (name of the database instance)

SID /DBTYPE

= ora (database type)

SID /TP_VERSION = 266 (tp version )


TRANSDIR

= \\scma\sapmnt\trans (path of the transport directory on network )

tp Commands(1)

tp connect <sapsid>
This informs connection with the SID system is successful or not .It logs
on to database & then logs off (If successful then TMS will work) .

tp addtobuffer <request> <sapsid>


This adds the transport request to the buffer of the <SID>system. &
places it as the last request to be imported.If it is already in the
buffer ,modifies the order& places at last .

tp showbuffer <sapsid>
This displays the transportable change requests ready for import to the
<sid>

tp cleanbuffer <sapsid>
This deletes successfully imported change requests from the list of
requests that are marked for import into the SAP System <SAPSID>.

tp count <sapsid>
This displays the number of requests in the <sid> buffer waiting for
import

tp delfrombuffer <request> <sapsid>


If the specified request is marked for import into the specified SAP
System, this flag is
deleted from the import list.

tp locksys <sapsid>
The specified SAP System is locked to prevent users other than SAP* and
DDIC from
logging on. When a user other than SAP* or DDIC tries to log on to the
system, the

tp Commands(2)
tp/ R3trans Return Codes
R3transsets a return code that shows whether or not the transport
has succeeded.
0: No errors or problems have occurred.
4: Warnings have occurred but they can be ignored.
8: Transport could not be finished completely. Problems occurred with
certain objects.
12: Fatal errors have occurred, such as errors while reading or writing a
file or

unexpected errors within the database interface, in particular


database problems.
16: Situations have occurred that should not have.
Examples:
Constants in the program are too small
Not enough available memory
Internal R3transerror
Other return codes are not set by R3transitself but point to errors,
such as segmentation
faults.

Maintaining and Monitoring the Transport Domain


Once we have configured the transport domain controller and included
SAP Systems in the transport domain, there will be situations in which
the configuration of the transport domain has to be adjusted.
We must change the configuration, for example when:
An SAP System moves to another host
A virtual system is replaced with a real system
An SAP System is deleted from the transport domain
An SAP System is linked to another transport directory
The settings for the transport control program have to be changed

Configuring the Backup Domain Controller

The SAP System that we want to use as the backup controller must
have the same release version as the domain controller. Otherwise,
configuration information may be lost when changing the transport
domain controller.
To configure a backup domain controller:

1.
2.
3.
4.
5.
6.
7.

Log on to the SAP System functioning as the transport domain


controller.
Enter Transaction STMS.
Choose Overview Systems. The system overview appears.
Position the cursor on the domain controller.
Choose SAP System Change. The brings you to the screen
Change TMS Configuration: System <SID>.
In the field Backup, enter the SAP System you want to use as the
backup controller of your transport domain.
Save your entries and distribute the configuration change.

Activating the Backup Domain Controller


If domain controller failed and we have to make changes to the TMS
configuration, we can activate the backup controller.
To activate the backup domain controller:
1. Log on to the SAP System functioning as the backup domain controller.
2. Enter Transaction STMS.
3. Choose Overview Systems. The system overview appears.
4. Choose Extras Activate backup controller.
5. Confirm the prompt.

Configuring Transport Routes


Before configure the transport routes, the following prerequisites must be
met:
The transport domain has been configured
All SAP Systems involved were included in the transport domain.
The configuration of the transport routes is managed in the SAP System
that serves as the transport domain controller and can be distributed to
and activated in all other connected SAP Systems in the transport domain.
The transport route configuration consists of:
System attributes
Consolidation routes
Delivery routes
SAP provides two editors for configuring transport routes:
Graphical editor
The SAP Systems and their transport routes are displayed graphically.
You can position and link the SAP Systems together by clicking and holding
the mouse.
Hierarchical list editor
The SAP Systems and their transport routes are displayed in a tree
structure.

Maintain Transport Management system(1)


We can maintain transport management system using STMS

Wecan
canadd
addanother
another
We
systemusing
usingthis
thisoption
option
system

Maintain Systems to a transport domain (1)


Choose SYSTEM or SHIFT F6 then we get the screen .

Wechoose
choosethis
thisoption
optiontotocreate
create
We
virtualSystem
System
aavirtual
Thelist
listofofsystems
systemsconnected
connected
The
withthe
theTransport
TransportDomain
Domain
with
Specifythe
thevirtual
virtualsystem
systemname
name
Specify
asDEV
DEV
as

Maintain Systems to a transport domain(2)


System DEV attached to the system list

Newlycreated
createdsystem
system
Newly
DEVattached
attachedalready
already
DEV

Maintain Transport Route to a Transport Domain(1)


We can maintain transport management system using STMS

Wecan
canadd
addanother
another
We
TransportRoute
Routeusing
using
Transport
thisoption
option
this

Maintain Transport Route to a Transport Domain(2)


We can maintain(add/change) Transport Layer from this screen

Choosetotocreate
createnew
new
Choose
TransportLayer
Layer
Transport

Choose
Choose
display/Changetoto
display/Change
edit/changethe
the
edit/change
transportroutes
routes
transport

Givename
nameZDEV
ZDEVofof
Give
thenew
new
the
TransportLayer
Layer
Transport

Maintain Transport Route to a Transport Domain(3)


Then the newly created transport layer added to the system

Usedthis
thisoption
optiontoto
Used
createaanew
new
create
transportroute
route
transport
Transportlayer
layerZDEV
ZDEV
Transport
addedtotothe
thesystem
system
added

Specifythe
thesystems
systems&&
Specify
transportlayers
layers
transport

Maintain Transport Route to a Transport Domain(4)

Transportroute
routeZDEV
ZDEV
Transport
addedfor
forthe
thesystem
system
added
DEV
DEV

Maintain Transport Route to a Transport Domain(5)


Graphical Presentation of the Transport Domain

IMPORTANT TRANSACTION CODES FOR TMS:


STMS

Initial screen of the Transport Management System

STMS_QUEUES

Displays the import queue

STMS_IMPORT

Import queue of the current SAP System

STMS_PATH

TMS transport routes

STMS_DOM

TMS system overview

SE01

Transport Organizer (Extended)

SE09 ,SE10

Transport Organizer

Create Change Request(1)


We can create Change Request of a role using PFCG to
transporting one role to another server .

Doubleclick
clicktoto
Double
make
change
make
change
request
request

Clickhere
here
Click

Create Change Request(2)


We can create a new Change Request or assign to old Change
Request .
Createaarequest
request
Create
clickhere.
here.
click

Enter
Enter
DESCRIPTION&&
DESCRIPTION
targetSERVER
SERVER
target

NewChange
Change
New
requestwill
willbe
be
request
generated
generated

Create Change Request(3)


Then the role-object Z_NEW_ACTIVITY_GROUP_1 assigned to
the change request SCMK900314

Thismessage
message
This
confirmsthe
thecreation
creation
confirms
changerequest
request
ofofchange

Clickhere
here
Click

Check Change Request(1)


Now we can check the change request using the TC SE01

Thismessage
message
This
confirmsthe
thecreation
creation
confirms
changerequest
request
ofofchange

Clickhere
here
Click

Check Change Request(1)


Now we can check the change request using the TC SE01
Enter the change request SCMK900314

Enterthe
the
Enter
changerequest
request
change

Afterentering
enteringthe
the
After
changerequest
request,use
,use
change
DisplayButton
Button
Display

Check Change Request(1)


We get the details of the change request

Typeofofthe
the
Type
Changerequest
request
Change

Customizingtask
task
Customizing
correspondingtotothe
theCR
CR
corresponding

ADD a new TASK to a Change Request(1)


To create new task for another user to a change request press F7

PressF7
F7totoadd
addnew
newtask
task
Press
foraanew
newuser
user
for

Enteruser
username
nametoto
Enter
attachaanew
newtask
task
attach

ADD a new TASK to a Change Request(2)


New task created with the name of user , TEST-USER1

Newtask
taskcreated
createdon
onaa
New
samechange
changerequest
request
same
Withname
nameSCMK900327
SCMK900327
With

ADD a new TASK to a Change Request(3)


Now Login as a TEST-USER1

Newtask
taskcreated
createdon
onaa
New
samechange
changerequest
request
same
Withname
nameSCMK900327
SCMK900327
With

ADD a new object to a change Request(1)


Now Login as a TEST-USER1
Now assign one role-object Z_PFCG to the previously created
task SCMK900327 which belongs to the task SCMK900314

Nowtransport
transportthe
therole
role
Now

Nowattach
attachthe
thechange
change
Now
requestSCMK900314
SCMK900314
request

ADD a new object to a Change Request(2)

Weget
getthe
themessage
messageofof
We
confirmation
confirmation

ADD a new object to a Change Request (3)


Now Login as a SAPBASIS .
Use transaction code SE01, we get the following screen .

Weselect
selectthe
thechange
change
We
requestSCMK900314
SCMK900314
request

Nowuse
usethe
thebutton
buttonDisplay
Display
Now

ADD a new object to a Change Request (4)


Now we get the following screen .

Therole
roleobject
objectZ_PFCG
Z_PFCG
The
alreadyattached
attachedwith
withthe
the
already
taskSCMK900327
SCMK900327
task

ADD a new object to a Change Request (5)


Now we add another object Z_NEW_AG_SPRO to a task
SCMK900327 using the user TEST-USER1 .
Login as a TEST-USER1

Nowwe
weattach
attachthe
therole
roleobject
object
Now
Z_NEW_AG_SPROtotothe
the
Z_NEW_AG_SPRO
C.R. SCMK900327
SCMK900327
C.R.

ADD a new object to a Change Request (6)


Login as a SAPBASIS
Use the TC SE01 to find the details .

Twoobjects
objectsattached
attachedwith
withthe
the
Two
taskSCMK900327
SCMK900327
task

Change the owner of the task in a Change Request (1)


We can change the owner of the change request .

Bythis
thisoption
optionwe
wecan
can
By
changethe
theowner
ownerofofthe
the
change
task
task

Change the owner of the task in a Change Request (2)


Then the owner of the task have been changed to SAPBASIS

Ownerofofthe
thetask
taskhave
have
Owner
beenchanged
changedtoto
been
SAPBASIS
SAPBASIS

Release a Change Request (1)


We have to release the change request after completion the work

Torelease
releasethe
thetask
taskuse
use
To
thisbutton
buttonor
orF9
F9
this

Release a Change Request (2)


Then the owner of the task have been changed to SAPBASIS

SCMK900327Task
Task
SCMK900327
released&&get
getthe
the
released
messagelike
likethis.
this.
message

ButSCMK900315
SCMK900315not
not
But
released
released

Release a Change Request (3)


We get the message in time of release the change request SCMK900314

Exportisisgoing
goingon
on
Export

Release a Change Request (4)


We get the message in time of release the change request SCMK900314

Afterreleasing
releasingtwo
twotasks
tasks
After
thechange
changerequest
requestcan
can
the
berelease.
release.
be