http://www.saptraininghub.

com/transport-management-system-tms/
introduction to Transport Management
System (TMS)
Why do we need a Transport System?
The CTS components play an important role in the overall development and customization environment.
CTS is an instrument for
!dministering " controlling new development re#uests.
Managing transports
$ecording of where and %y whom changes are made
Configuring systems landscape
&verview of CTS Components
CTO (Change and Transport Organizer) 't(s the main tool for managing) %rowsing) and registering the
changes done on the repository and customizing o%*ects. 't(s the central point for organizing the development
pro*ects. S+,- is the transaction with new e.tended view.
(TMS) Transport Management System 's used to move) manage) control) copy development o%*ects and
customizing settings in an orderly fashion across S!/ systems in a landscape through pre0defined transport
routes ($1C Connections). The transport process %asically consists of e.porting of o%*ects out of the source
S!/ system and importing them into the target S!/ system2s.
Transport Tools The actual transports happen in the %ac30end at the &S level using transport tools) which
are part of S!/ 4ernel and includes the program R3trans and the transport control program tp.
S!/ System05andscape
The system landscape (also 3nown as SAP System Group) is the arrangement of S!/ servers. 'deally) in an S!/
environment) a three0system landscape is recommended. 't consists of the
-. 6evelopment Server 7 6+8
9. :uality !ssurance Server 7 :!S
;. /roduction Server 7 /$6.
Transport cycle in a very %asic sense) is the release of new 6evelopments2 Customizing Changes from 6+8 which
are imported in %oth :uality and /roduction systems. <owever) import in /$6 can happen only once integration
testing and #uality chec3 has %een performed in :!S (and mar3ed as chec3ed).
What is Customizing? <ow does TMS help in Customizing
Customizing is a process to adapt the S!/ system according to the customer(s need. To perform the
customizing) users and consultants ta3e help of S!/ $eference 'mplementation =uide ('M=)) which is
accessi%le through transaction S/$&.
Customizing is ideally done in 6+8. The Transport &rganizer (S+,-) is used in con*unction with 'M= to
record and transport customized changes further.
Most of the Customizing changes (though) not all) are client-specific) i.e.) the changes are supposed to %e reflected
in a particular client only and not intended for all the system clients. When the Transport $e#uest is e.ported) it
e.tracts the relevant ta%le entries from the data%ase of the S!/ system and copies them to the transport directory.
$elevant ta%le entries are loc3ed when the customizing transaction is %eing used. <owever) they are unloc3ed as
soon as the changes are saved to a Transport $e#uest.
$epository and 6evelopment Changes
!part from customizing already e.isting o%*ects) new developments are also re#uired in most of the cases.
6evelopment o%*ect is any o%*ect that is created (developed) %y you in S!/ system.
Collection of all such o%*ects (client0specific or cross0client) is called Repository.
6evelopment is mostly done with the help of !>!/ Wor3%ench (S+?,)) therefore such changes are also
3nown as Wor3%ench Changes.
+.amples
!>!/ 6ictionary &%*ects Ta%les) 6omains) 6ata elements) etc.
!>!/ /rograms) function modules) menus) screens
6ocuments) !pplication defined transport0o%*ects) etc.
Wor3%ench is also fully integrated with TMS) to record and transport the changes.
Most of the Wor3%ench changes (though) not all)) are cross-client) i.e. changes will %e reflected in all the system
clients of the target system. &%*ects transported from the source system overwrite o%*ects in the target system that
has the same names.
Clients and the type of 6ata in S!/ System
Conceptually) client is a technical and organizational independent unit) that contains its own set of data
(Master 6ata) !pplication2 &perational data) Customizing 6ata)
Clients create separate environments for users from different user groups or with a different purpose) within
same S!/ system) without actually using different data%ase.
1rom Technical point of view) client is specified using ;0digit numeric '6) which also acts as the value for the
ta%le field @M!A6T() in case of client0specific *o%s.
!mong client specific data) there are ; types of data
User Master Data contains the user login information) including the username) the password and the user
defaults) the authorization profiles or roles) and the other useful information such as user groups)
communication and so on. This data is physically present in a specific set of ta%les (the BS$C ta%les).
Cstomizing Data contains the configuration settings to customize organizational structure and the
%usiness processes for the companies implementing S!/. This data is client dependent and is stored in ta%les
3nown as customizing ta%les.
!pplication Data are also client dependent and normally users distinguish two types( master data and
transactional data.
-. Master 6ata such as vendor master) material master (ta%les such as M!$!)
9. Transactional data such as sales order) financial documents) /roduction &rders (/&s)
and so on.
Client Cstomization Options

Transport Directory and "ts configration
S!# Transport Directory$
't is the glo%al transport directory (2usr2sap2trans)) which is actually a shared location (residing in the 6omain
Controller System) among all the mem%er systems of a landscape (system group) .'t also contains certain
su%directories) that are created automatically during the installation of the S!/ system. This is mandatory for
setting up the Transport Management System.
>asically) Transport 6irectory is the location where all the changes are saved (in the form of files) after they
are released from 6+8. Therefore) it acts as a source for the changes to %e eventually imported in 6+8 and
/$6. <ence) we have to ma3e sure that the transport directory is shared properly among all the systems in a
landscape.
!s an e.ample) in Windows AT) the shared directory location can %e accessed using the following
address %&S!#TR!'S(OST)sapmnttrans where S!/T$!AS<&ST (6omain Controller System(s address) is
defined in hosts file in Windows 6irectory of all S!/ systems in the landscape. 6omain Controller 7 is one of the
systems in a landscape that act as an overall controller for change management and transport process in the
landscape. 6omain Controller is chosen (out of 6 2 : 2 /) %y the team of system administrators) on the %asis of
system availa%ility and the time of installation.
Main Su%directories
Cofiles$ Contains Change $e#uest 'nformation files with complete details and commands.
Data *iles$ Contains the actual values and data to %e used in implementing the change.
+og$ Contains Transport logs) traces or statistics) used for trou%le0shooting) in case any error occurs in the
transport process.
,#S$ 6ownload directory for advanced corrections and support pac3ages
Other S-directories are$
-in$ Configuration files for tp (Transport /rogram) and TMS
olddata$ &ld +.ported 6ata for archival or deletion
actlog$ !ction logs for all re#uests and tas3s
-ffer$ Transport %uffer for each system declaring the transports to %e imported
sapnames$ 'nformation regarding transport re#uests made %y respective users
tmp$ Temporary and data log files
Setting up of Transport 6irectory and T//!$!M
While configuring TMS) one of the main pre0re#uisite is to setting up the Transport 6irectory and the
Transport /arameter file.
't ensures that the 6irectory is shared properly among all the systems in a 5andscape) for that all the
systems ta3ing part in the group2landscape are to %e included in the glo%al configuration file T//!$!M
(transport parameter file)) located under the -in su%directory of 2use2sap2trans. We have to ma3e sure that the
entries for all the participating systems are made in this file.
'n case) any entry is missing) copy another system(s entry and change the values (for instance) System '6)
<ost name)
!t the time of installation) transport directory " the su%0directories are created automatically) including an
initially configured template of T//!$!M file.
Operating System Tools TP and R3trans
tp The Transport Control #rogram$
tp is the S!/ program that administrators use for performing and planning transports %etween systems and
also in upgrades of the S!/ systems. This is used %y the CT& and TMS.
!ctually) tp uses other special tools2programs and utilities to perform its functions. Mainly) it
calls R.trans utility program. <owever) it also offers a more e.tensive control of the transport process) ensuring
the correct se#uence of the e.ported2imported o%*ects) to avoid severe inconsistencies in the system) which
may arise due to wrong se#uence.
tp is located in the standard runtime directory of the S!/ system /sr/sap/S0S/&S"D)/e1e/rn. 't is
automatically copied in the installation process.
!s a pre0re#uisite) the tp glo%al parameter file (T##!R!M)) must %e maintained) specifying at least)
hostnames of the systems ta3ing part in the transport process.
tp is mainly used for performing imports in target systems. 't uses utilities called 'mport 6ispatchers
7 RDD"M#D# " RDD"M#D2C+",'T2&nnn)) these are ought to %e scheduled as %ac3ground *o%s in every
system where imports will %e performed. 'f for any reason they are deleted) we can schedule these *o%s %y
running reportRDD',3##.
These *o%s are actually Devent triggered) meaning that tp sends a signal (an event) to the $2; system and
the *o% starts. These events are named
as S!#2TR"44,R2RDD"M#D# and S!#2TR"44,R2RRD"M#D#2C+",'T.
$;trans 7 The Transport Control /rogram
R.trans is the S!/ system transport program that can %e used for transporting data %etween different S!/
systems. 't is normally not used directly) %ut called from the tp control program or %y the S!/ upgrade utilities.
tp controls the transports and generates the r;trans control files) %ut does not connect to the data%ase itself.
!ll the Dreal wor3E is done from R.trans.
't supports the transporting of data %etween systems running on different &S and even different 6>.
$ead more at http22www.saptraininghu%.com2transport0management0system0tms2F:TGy1BdB?mHayTB+.II