– STMS

sapbasis.home.blog/stms

January 16,
2019

Transport – To move the object from one sap system to another sap system in the
landscape. Export the change request and import transport request

Transport object divided into 2 types – Export & Import

DEV —>(export) Central TP Delivery at OS level

Domain Control – Control all the systems in the landscape. It is used to manage all the
transport parameters in the landscape. Most of environment there will be only one
domain controller

Transport Domain Controller – Created as part of post installation activity.

Transport Domain – All the sap level

Configure the Domain Controller

Login to the sap system with DDIC in client 000

Go to SE06 – Click the post installation activity

Go to STMS – It will ask for domain controller

Enter System ID of the domain controller

Enter domain_<SID> as domain controller name and enter the description

Click save button

Steps to add the other system with domain controller

Logon domain controller system

Approve the added system

Landscape – Arrangement of group of system to flow the objects.

ECC DEV——->QAS——>PRD

1/6
EP DEV——->QAS——>PRD

BI DEV——->QAS——>PRD

Based on the customer requirements we can define the single, two, three and multi
systems in the landscape

In order to define landscape we need systems

Transport layer
Transport root
Transport group
Transport target group

Transport Layer – Used to moving the object path from one system to another system
within the landscape. Transport layers are 2 types

Z<SID> – customizing object move the Z<SID> layer

SAP – repository objects move the sap layer

Transport Routs – shows the transport direction to the target system

In three system Landscape

DEV ——> Integrated system

QAS ——> Consolidated system

PRD ——> Delivery system

Transport routs are 2 types

Consolidate route – Route between development system and quality system

Delivery route – Route between quality system to production system

Note – In a two system landscape delivery route is not possible

Transport Group – The system which are shared a Trans Directory.

Transport target group – more than 3 systems & multiple clients it works on extended
transport controller.

Extended transport controller – used to transport objects within the client & system.

Backup Domain Controller – whenever primary domain controller failed. In that time it
will care of the transportation.

Workflow – To set off the automatic process & responsibility of quality system.
2/6
Transport Background Jobs – RDDIMPDP, RDDNEWDP

Transport request are stored in TRBAT & TRJOB

All the change requests are stored table is E070

E070 – Change request headers

E071 – change request object lists

E071k – object key contained within transports

At end of the import, transport specific the return codes

000 – import finished with successfully

004 – import finished with warnings

008 – some objects are not transported

0012 – critical transport errors

change request – whenever we can create a request

transport request – Whenever we will release the change request

In Development system we can configure the domain controller

Development system is transport domain / integrated system

RSTPTEST – can be extended if there are any problems with TP (or) R/3 instance.

Checking the consistence of STMS – Using SA38 (or) SE38 and run the report is
RSTPTEST (it will check if any errors in STMS or not)

User locks at sap level Tcode – EWZ5 and lock the system at OS level by using #tp
lock sys<SID> (or) tp unlock sys<SID>

Naming convention of transport request – <SID>k9<5 digits>

Types of Editions – Graphical , Hierarchical Editor

Transports are OS and DB independent but R/3 system dependent.

r3 trans -d – used to check R3 trans connecting to DB (or) not.

Trans directory path – usr\sap\trans

Trans requests are 3 types

k type – with change in integrated system (DEV) to consolodated system(QAS)

T type – move one system to another system

Trans directory structure

Bin – it consists of domain configuration files and transport profile parameters.

Buffer – buffer contains transport request ready to import

Transport request are 2 types

Cofiles – A cofiles contains control information of the transport request. cofiles start with
K.

Date files – A date files contains data information of the transport request. Data files
start with R.

EPS [Electronic panel service] – used to store support packages

Log – it rides the log files during the change request

A log – It contains the information about the transport request. who is the transport
request and name of the consultant?

S log – S log files are stored in transport request of specific system.

U log – it contains transport command that are executed at OS level.

Sapnames – Owner of the change request is documented here

Disable fully loaded truck –

STMS –> overview –> system –>doubleclick system(Ex: dev) –> go to transport tool tab –>
insert row –> No_IMPORT ALL=1

Create STMS –

login system with DDIC in client 000

go to Tcode STMS –> configured –> standard configured –> single system, development
system, three system in group

(or) STMS –> overview –> systems –> sap systems –> external system –> then we have to
give the system name, <SID>

Create Transport route –

4/6
overview –> transport route –> change button –> click the DEV, QAS & PRO –> click add
transport route tab –> then we have to give the <SID>, transport layer, system name.

Create change request – using Tcode – SE01, SE09 & SE10

import change request – STMS –> overview –> import (or) import overview – button

Types of change request – 4

Customizing request – it contains client specific object.

Workbench request – it contains cross client objects & repository objects.

Transport copies – Used for more tables for user date. Used for DB refresh & Client
refresh

Relocation – Used for changing the location of object from one system to another
system.

Steps for importing command level –

Login to target system at OS level using <SID>adm.

Type #Add to buffer <transport request number><SID> (enter)

It should provide you return code 0

Type #import<request number>CLNT<client number><SID> UI

Now look for return codes 0,4,8,12

If RC>8 then look for problems with data files & cofiles. Check permissions, check data
creation, size.

Transport at OS level –

Requesting add to buffer: #tp add to buffer<transport request no><sap SID>

Import request : #tp import<transport request no><SID>

Tp clean the buffer : #tp clean buffer<SID> –> to delete the request after completed
successfully

delete the particular request : #tp del from buffer<tp request no><SID>

display the buffer request : #tp show buffer<SID>

Import transport request at OS level : #tp import <tp request no><SID>CLNT = <client
no> pf = usr\sap\trans\bin\Tp_domain_<SID>.pfl

5/6
Types of transport request types – 2

One is releasing and another one is locked

Transport request – DEV system to QAS, QAS system to PRD

Transport copies – PRD system to QAS, QAS system to DEV

SE01 – used for transport organization.

SE09 – Workbench request

SE10 – customized transport request

Transport request naming conventions –

<Sid>k9<5 digits>

<Sid>k9<5 digits>

6/6