SAP ERDC STMS

8/18/2019 SAP ERDC STMS

1/59

TMS(1)

Why Transport Management SystemWithin the R/3 System Landscape customizing & deveopment changes per!ormed

in a deveopment cient " has to trans!er to #$S cient & %R cient '

S$% R/3 enaes user to record changes to a *$+,- R-#.-ST "hich is

distriuted to other cient or other R/3 system '

When changes to either customizing or repository o0ects are made"the changed

o0ects are recorded to a T$S in a hange Re2uest corresponding to a speci!ic

user '

hange Re2uests & Tass provide a compete history o! a changes made during

R/3 impementation '

If TMS is not configured properly (ie inconsistent) then we may not be able to

create transportable change request .

$!ter S$% R/3 instaation e have to con!igure TMS !or the !ooing reasons 4 To create transportae change re2uest To import transport re2uest To setup ,oa Transport System eteen R/3 systems

To transport cients eteen R/3 systems


2/59

TMS(5)

Why Transport Management System

The R/ change management system! also "nown as the #hange and TransportSystem (#TS)! pro$ides options for data transfer between and within R/ Systems.

The tool can be used! to transport tuned and tested customi%ing settings between

systems and clients.

&sing transport requests and customi%ing settings! de$elopment wor" created in a

separate de$elopment system (') can be automatically recorded in change requestsand then transported into a quality assurance client! and finally into a production client.

*nce the change request has been released from the source system! it becomes a

transport request.

eveopment / orrectionMost changes are recorded to de$elopment/correction tas"s which contain changes to

ob+ects that originated in the current R/ system .Repair

, repair is a change to an R/ repository ob+ect that originated on an r/ system other

than the current R/ system .The ob+ect be an sap deli$ered ob+ect or customer

de$eloped ob+ect.


3/59

TMS(3)

To activate customizing changes permitted in a particuar cient "and hether these

ustomizing changes are automaticay recorded to a change re2uest "have to set

6#hanges and transports for client-specific ob+ects using the transaction code S7


4/59

TMS(7)

To permit or disao create or changes to R/3 repository o0ects !rom any cient "

have to set 6#lient independent ob+ect changes using the transaction code S7


5/59

hange Re2uest (1)

Types o! *$+,- R-#.-ST

ustomizing hange Re2uest&sed for record only client dependent changes using IM .,nd after completion

of customi%ing ! the changes can be transport to other r/ system .

To manage the customi%ing change request we use transaction code S-18 '

Worench hange Re2uest

&sed for client independent (cross-client) customi%ing ob+ects and all repository

ob+ects created or maintained through the ,0,1 wor"bench .

To manage the wor"bench change request we use transaction codeS-89 '

Transportae hange Re2uest

The change requests which are transported to other R/ systems after release .

Loca hange Re2uest

, change to an R/ repository ob+ect in a de$elopment system but not

transportable to quality or production system will be recorded to a local change

Request .

2ocal change request can be released but not transportable .


6/59

hange Re2uest (5)

3ample of a change request 4 SM988518

The ID number of a change request or tasks begins with the three

character system-ID S#M . Followed by K9 . Then e digitnumber55675 .

!e"t task will be S#M8955677 .

If pro+ect leader assign another user to the change request then another tas" willcreate with I' S#M895567:.

# change request is a collection of tasks .


7/59

hange Re2uest (3)

To release the #hange Request !each separate tas" in the change request must be

documented ; released separately .using the button

Releasing the tas"

S#M8955676

Releasing the tas"

S#M8955676


8/59

-:porting change re2uest

This is the physical copying of the recorded ob+ects from the database of the R/

system to files at the operating system le$el .

This files are located in the transport directory .

*perating system le$el file 988518'scm created on directory /usr/sap/trans/co!ies

; the file R988518'scm created on directory /usr/sap/trans/data ; the file

SM-988173'SM created on directory /usr/sap/trans/og '

The file e3tension will be the source system sid name .


9/59

Transport directory(1)4 Transport directory is a file system located on *S le$el where the ob+ects in change

requests that were released and e3ported from that R/ system are physically copied so

that they can subsequently be imported to a target R/ system.

/usr/sap/trans is the parent transport directory

*ften in a system landscape there is only one common transport directory .

,ll R/ systems that share the same transport directory ma"e up a TR$+S%;RT

,R;.%.

If the transport directory is not shared with other systems !it is called the %rivate transport

directory '

DEVDEV QASQAS

Common

transport directory

Common

transport directoryPrivate

transport directory

Private

transport directory

PRDPRD

Transport Group 1 Transport Group 2


10/59

Transport directory(5)4

;ne or Many Transport irectory 4

The networ" connection to an R/ system is not fast enough .

There is no permanent networ" connection between the different R/ systems of thesystem landscape .

There are security reasons that pre$ent direct access to an R/ system (li"e 1R').

There are different hardware platforms that do not allow a common transport

directory.

#ommon transport directory is standard practice .

=hen more than one transport directory !then manual transfer the operating system

le$el file from ser$er to ser$er.

$ery computer of the transport group on which an R/ instance is installed should

ha$e write access ; read access to the transport directory.


11/59


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

bin

data

cofiles

buffer

logtmp

actlog

sapnames

olddata

eps


12/59


eps 4 This is download directory for S,1 support pac"ages from S,1>T .

in 4 This directory contains [email protected]


13/59

Transport directory(T domain or if domain differs create >T trusted relationship between

them.

Set a global share sapmnt to point the directory DusrDsap files .

Then DusrDsapDtrans files can be access as DsapmntDtrans .

Set >T access type SE*ST .


14/59

Transport directory(>)4

%reparing ;perating System .sers4

If we want to install tp$ the o%erating system users must fulll the

following&'ach user that wants to use the trans%ort system requires read

and write authori(ation in the trans%ort directory.

If you call a trans%ort %rogram directly from the o%erating

system leel$ only use the o%erating system user ADM $

)#*)erice+)#*)ID,


15/59


16/59


17/59

on!igure Transport Management System

Before starting work with the Transport Management System (TMS),

We must configure it in a S!P Systems in system andscape"

#n $onfiguring t%e transport domain we define which S!P systems in

system andscape form a transport domain, and which S!P system is to

$e the transport domain controller "

#n $onfiguring t%e transport routes the transport routes are used to

define in which target system we want to consoidate change re%uests,

and which S!P Systems are forwarded this information automaticay"

#n transport domain, the S!P System that is configured as the domain

controller is of specia significance" #f this S!P System fais, we cannotmake changes to the TMS configuration during this time" Therefore if

transport domain contains more than three S!P Systems, S!P

recommend configuring a bac&up domain controller "#f domain controer

fais, the $ackup controer can assume the function of the domain

controer"


18/59


19/59

$onfiguring t%e Transport Domain'2(

" *og on in client 000 in the S!P System that we want to configure as

the transport domain controer"

+" nter Transaction STMS" The diaog $o- TMS: Configure Transport

Domain appears"

." nter the name and a short description of the transport domain"

/" Save your entries" The foowing actions are performed automaticay in

S!P System0 The user T/SAD/ is created" The R,$ destinations re%uired for the TMS are generated" The TMS configuration is stored in the transport directory"

The transport profie for the transport contro program tp is

generated" The S!P System is configured as a single sstem


20/59


21/59

$onfiguring t%e Transport $ontrol Program tp

The transport control program tp re%uires a transport profie that

contains information a$out esta$ishing the data$ase connection for

a S!P Systems in the transport domain" TMS generates andmanages this transport profile as a part of the transport domain

configuration"

Must enter the necessary profie parameters for this S!P System in

the transport profie TPPARA/ using a te-t editor"


22/59

tp / r3trans /tpparam (1)

Transport ontro %rogram tp

Trans%ort control %rogram t% is an utility to trans%orts ob/ectsbetween the sa% system 0 1%grading the sa% release.

t% is called by the other %rograms

2hange 0 Trans%ort )ystem 32T)4

Trans%ort 5anagement )ystem 3T5)4

1%grade control %rogram 67u% 31%grade control %rogram4

R3trans %rogram

This sa% %rogram uses to trans%ort data between the sa% systems0 the migration between the di8erent sa% release.

5ainly 67trans is called by the %rograms t% 0 r7u%

Transport pro!ie (tpparam)

This is a global %arameter le used by t% 0 administrated by )#* T5).


23/59


24/59

tp ommands(1) tp connect @sapsidA

This informs connection with the )ID system is successful or not .It logson to database 0 then logs o8 3If successful then T5) will work4 .

tp addtobuffer @requestA @sapsidA This adds the trans%ort request to the bu8er of the +)ID,system. 0%laces it as the last request to be im%orted.If it is already in thebu8er $modies the order0 %laces at last .

tp showbuffer @sapsidA This dis%lays the trans%ortable change requests ready for im%ort to the+sid,

tp cleanbuffer @sapsidA This deletes successfully im%orted change requests from the list ofrequests that are marked for im%ort into the )#* )ystem +)#*)ID,.

tp count @sapsidA This dis%lays the number of requests in the +sid, bu8er waiting forim%ort

tp delfrombuffer @requestA @sapsidAIf the s%ecied request is marked for im%ort into the s%ecied )#*

)ystem$ this ag isdeleted from the im%ort list.

tp loc"sys @sapsidA The s%ecied )#* )ystem is locked to %reent users other than )#*: andDDI2 from

logging on. ;hen a user other than )#*: or DDI2 tries to log on to thes stem the


25/59

tp ommands(5)

tp/ R3trans Return Codes

R3trans sets a return code that shows whether or not the trans%ort

has succeeded.84 !o errors or %roblems hae occurred.

74 ;arnings hae occurred but they can be ignored. 8: Trans%ort could not be nished com%letely. *roblems occurred withcertain ob/ects. 12: Fatal errors hae occurred$ such as errors while reading or writing ale or

une"%ected errors within the database interface$ in %articulardatabase %roblems. 16: )ituations hae occurred that should not hae. '"am%les& = 2onstants in the %rogram are too small = !ot enough aailable memory

= Internal R3trans error >ther return codes are not set by R3trans itself but %oint to errors$such as segmentation

faults.


26/59

/aintaining and /onitoring t%e Transport Domain

4nce we have configured the transport domain controer and incuded

S!P Systems in the transport domain, there wi $e situations in which

the configuration of the transport domain has to $e ad5usted" We must change the configuration, for e-ampe when0

!n S!P System moves to another host

! virtua system is repaced with a rea system

!n S!P System is deeted from the transport domain

!n S!P System is inked to another transport directory

The settings for the transport contro program have to $e changed


27/59

$onfiguring t%e 3ac&up Domain $ontroller

The S!P System that we want to use as the $ackup controer must

have the same reease version as the domain controer" 4therwise,

configuration information may $e ost when changing the transport

domain controer"

To configure a $ackup domain controer0

" *og on to the S!P System functioning as the transport domain

controller+" nter Transaction ST/S

." Choose Overview Systems" The system overview appears"

/" Position the cursor on the domain controer"

2" Choose SAP System Change" The $rings you to the screen

Change TMS Configuration: System "

3" #n the fied Backup, enter the S!P System you want to use as the$ackup controer of your transport domain"

6" Sae your entries and distribute the configuration change"


28/59


29/59

$onfiguring Transport Routes

Before configure the transport routes, the foowing prere%uisites must $e

met0The transport domain has $een configured

! S!P Systems invoved were incuded in the transport domain"

The configuration of the transport routes is managed in the S!P System

that serves as the transport domain controller and can $e distributed to

and actiated in a other connected S!P Systems in the transport domain"

The transport route configuration consists of0System attri$utesConsoidation routes7eivery routes

S!P provides two editors for configuring transport routes0Grap%ical editor

The S!P Systems and their transport routes are dispayed graphicay"8ou can position and ink the S!P Systems together $y cicking and hoding

the mouse"4ierarc%ical list editor

The S!P Systems and their transport routes are dispayed in a tree

structure"


30/59

Maintain Transport Management system(1)

We can maintain transport management system using ST/S

We can add anothersstem using this option

We can add anothersstem using this option


31/59

Maintain Systems to a transport domain (1)

Choose S.STE/ or S4-,T ,5 then we get the screen "

The ist of systems connectedwith the Transport Domain

The ist of systems connectedwith the Transport Domain

We choose this option to createa irtual Sstem

We choose this option to createa irtual Sstem

Specify the virtua system nameas DEV

Specify the virtua system nameas DEV


32/59

Maintain Systems to a transport domain(5)

System DEV attached to the system ist

9ewy created system

DEV attached aready

9ewy created systemDEV attached aready


33/59

Maintain Transport Route to a Transport omain(1)

We can maintain transport management system using ST/S

We can add anotherTransport Route using

this option

We can add anotherTransport Route using

this option


34/59


We can maintain(add:change) Transport 6aer from this screen

Choosedispla7$%ange toedit:change thetransport routes

Choosedispla7$%ange toedit:change thetransport routes

Choose to create new Transport 6aer

Choose to create new Transport 6aer

;ive name 8DEV ofthe new Transport 6aer

;ive name 8DEV ofthe new Transport 6aer


35/59


Then the newy created transport laer added to the system

Transport ayer 8DEVadded to the system

Transport ayer 8DEVadded to the system


36/59


Transport route 8DEVadded for the systemDEV

Transport route 8DEVadded for the systemDEV


37/59

Maintain Transport Route to a Transport omain(


38/59

-/P*RTA+T TRA+SA$T-*+ $*DES ,*R T/S9

STMS #nitia screen of the Transport Management System

STMS>?P!T1 TMS transport routes

STMS>74M TMS system overview

S@ Transport 4rgani&er (-tended)

S@A ,S@ Transport 4rgani&er


39/59

reate hange Re2uest(1)

We can create Change e%uest of a roe using P'C; to

transporting one roe to another server "

7ou$e cick tomake changere%uest

7ou$e cick to

make changere%uest

Cick hereCick here


40/59


We can create a new Change e%uest or assign to od Change

e%uest "

Create a re%uestcick here"

Create a re%uestcick here"

nterDES$R-PT-*+ =target SERVER

nterDES$R-PT-*+ =target SERVER

9ew Changere%uest wi $e

generated

9ew Changere%uest wi $e

generated


41/59


Then the roeo$5ect >9W>!CT#D#T8>;4

assigned to

the change re%uest SCMEA@@./

Cick hereCick here

This messageconfirms the creationof change re%uest



42/59

hec hange Re2uest(1)

9ow we can check the change re%uest using the T$ SE01

Cick hereCick here




43/59


9ow we can check the change re%uest using the T$ SE01nter the change re%uest S$/:;00!1"

!fter entering thechange re%uest ,useDispla Button

!fter entering thechange re%uest ,useDispla Button

nter the

change re%uest

nter the

change re%uest


44/59


We get the detais of the change re%uest

Type of the

Change re%uest

Type of the

Change re%uest

Customi&ing taskcorresponding to the C

Customi&ing taskcorresponding to the C


45/59

$ a ne T$S to a hange Re2uest(1)

To create new task for another user to a change re%uest press '6

Press ,# to add new taskfor a new user

Press ,# to add new taskfor a new user

nter user name toattach a new task

nter user name toattach a new task


46/59


9ew task created with the name of user , TST


47/59


9ow *ogin as a TST


48/59

$ a ne o0ect to a change Re2uest(1)9ow *ogin as a TST


49/59

$ a ne o0ect to a hange Re2uest(5)

We get the message ofconfirmation

We get the message ofconfirmation

$ a ne o0ect to a hange Re2uest (3)


50/59


9ow *ogin as a SAP3AS-S


51/59


9ow we get the foowing screen "

The roe o$5ect 8)P,$G aready attached with the

task S$/:;00!2#

The roe o$5ect 8)P,$G aready attached with the

task S$/:;00!2#

$ a ne o0ect to a hange Re2uest (


52/59

$ a ne o0ect to a hange Re2uest (?SER1 "*ogin as a TEST>?SER1

9ow we attach the roe o$5ect8)+E=)AG)SPR* to the$R S$/:;00!2#

9ow we attach the roe o$5ect8)+E=)AG)SPR* to the$R S$/:;00!2#

$ a ne o0ect to a hange Re2uest (?)


53/59

$ a ne o0ect to a hange Re2uest (?)

*ogin as a SAP3AS-S


54/59

hange the oner o! the tas in a hange Re2uest (1)

We can change the o@ner of the change re%uest "

By this option we canchange the owner of thetask

By this option we canchange the owner of thetask

hange the oner o! the tas in a hange Re2uest (5)


55/59

g g 2 ( )

Then the owner of the task have $een changed to SAP3AS-S

4wner of the task have$een changed toSAP3AS-S

4wner of the task have$een changed toSAP3AS-S

Reease a hange Re2uest (1)


56/59

g 2 ( )

We have to reease the change re%uest after competion the work

To reease the tas& usethis $utton or ,;

To reease the tas& usethis $utton or ,;



57/59

g 2 ( )

Then the owner of the task have $een changed to SAP3AS-S

FS$/:;00!2# Taskreeased = get themessage ike this"

FS$/:;00!2# Taskreeased = get themessage ike this"

But S$/:;00!1 notreeased

But S$/:;00!1 notreeased



58/59

g 2 ( )

We get the message in time of reease the change re%uest S$/:;00!1"

-port is going on-port is going on



59/59


We get the message in time of reease the change re%uest S$/:;00!1"

!fter reeasing two tasksthe change re%uest can$e reease"

!fter reeasing two tasksthe change re%uest can$e reease"

Documents

SAP ERDC STMS