ppt

STMS

SAP TRANSPORT MANAGEMENT SYSTEM

TOPICS• SAP system landscape overview• CTS (Change and Transport System)• Introduction of STMS• Configuration of STMS• Transport routes• Architecture of STMS• Mechanism of STMS• Types of change request• Types of transports• Modification/corrections and repairs• Import and export of TRS• TP command usage• Important tables in STMS• Log files • Important STMS Jobs• Trouble shooting export/import related problem

SYSTEM LANDSCAPE• A system landscape is a set of systems that

share customizing and repository objects via transported change requests.

• The typical landscape is made up of, but not limited to, a development, a quality assurance, and a production system.

• In most cases, the system landscape and the transport domain are made up of the same systems but it is not uncommon to have multiple landscapes within one transport domain.

SAP SYSTEM LANDSCAPE

• The system landscape should enable you to: Protect application data using• . Client roles• . Authorization concepts• . Perform development, quality assurance, and

production activities in separate environments to ensure consistency of repository objects secure and stable production environment

SYSTEM LANDSCAPE• The minimum SAP-recommended system landscape

consists of three SAP systems: • Production system where users perform their business

functions;• Quality assurance system, that is virtually identical to

production, where data owners perform quality assurance testing of changes; and a

• Development system, where all changes originate from users performing customizing, developers creating or changing ABAP code, or system administrators performing maintenance or upgrade functions.

SYSTEM LANDSCAPE

SAP System Landscape

SAP System Landscape Each system in SAP Landscape has different

clients. • DEV system contains CUST and UTST SND ( sandbox) clients.• QAS system contains TST (testing) and TRN

(training) client.• PRD system contains PRD(production client).

SYSTEM LANDSCAPE

Data Types in SAP Systems

SYSTEM LANDSCAPE

Standard Client Roles

CTS• SAP provides the tools required for the creation,

documentation, and distribution of changes within a system landscape. These tools enable you to:

• Audit changes made in all SAP systems by• Recording changes to change requests• Documenting changes• Control by whom and where changes are made

with Client change options• System change options• User authorizations.

CTS

Establish where and when changes are distributed by

• Setting up the Transport Management System (TMS)

• Setting up a clientusing client tools• Managing the import process• Support SAP system changes and

upgrades

CTS

• The physical programs that deliver these controls are collectively known as the Change and Transport System (CTS). The CTS is made up of three distinct areas:

• . The Change and Transport Organizers (CTO)

• . The Transport Management System (TMS)

• . The Transport Tools

CTS

Change and Transport System (CTS)

CTS• The CTO is a set of transactions (SE09, SE10, and

SE01) used mainly by project leaders for customizing or development, customizing or development team members and system administrators responsible for transports. The functions of CTO are designed to address the management of change requests, excluding any capability to perform imports.

• Common tasks would include creating change requests, assigning users to change requests, attaching documentation, displaying objects contained within change requests, attaching objects to change requests and releasing change requests.

INTRODUCTION

• STMS stands SAP transport management system.

• STMS is used to create,release and import change requests.

• STMS is used to manage all sort of transport activities in system landscape.

• STMS is a tool to move changes across system landscape.

INTRODUCTION

The purpose of the TMS, accessed via

transaction STMS, is to centrally control the movement of changes through the system landscape based on predefined paths.

STMS FEATURES Important Features of TMS:

• Define an SAP systems role within a system landscape or transport• Domain Configure the transport routes using either a graphical

editor, hierarchical editor, or delivered standard configurations• Configure the transport tool program parameter profile• Display the import queues of all systems in the transport domain• Define quality assurance acceptance procedures in the QA system• Schedule the import of change requests in an import queue• Perform transports between systems without a common transport

directory.• Handle transport proposals of developers

INTRODUCTION• STMS Configuration is a part of post installation

activities.• STMS works with same OS or different OS

systems across the system landscape.• Transporting, from a logical standpoint, is the

movement of changes from the development system to the quality assurance system and, once tested and approved, to the production system.

• This logical movement, known as the transport route, is the predefined path that a change follows through the landscape.

INTRODUCTION• The TMS is transaction STMS and is used

primarily by the system administrator to schedule, manage, and monitor the import process.

• The process of exporting change requests from a system or importing change requests into a system is performed by programs (tp and r3trans ) that exist at the operating system level.

• These programs are called by the CTO when performing exports or by the TMS when performing imports.

INTRODUCTION Business Example• An SAP system administrator needs to

understand the roles of different systems and clients in the SAP system landscape before making decisions on how to configure the Transport Management System (TMS).

• After you install the first SAP system but before you make changes, you need to configure the TMS so that it will record, track and control Customizing and development changes for the subsequent transports to other systems in the SAP system landscape.

INTRODUCTION

• During implementation customization and configuration activity is carried out in DEV systems and recorded in change requests.

• It is not necessary to have QAS and PRD systems with DEV together.

• Customization and Configuration can be started without QAS and PRD systems and later on QAS and PRD systems can be installed and included in the system landscape.

OVERVIEW• Depending on the size of an organization and

the scope of its SAP implementation, there can be many different individuals responsible for carrying out customizing and development projects.

• Some will be involved in customizing specific application areas, others may be involve in development of new ABAP programs, others in the QA testing and acceptance of changes.

• There can be hundreds or even thousands of change requests that have to be transported through the systems in the landscape.

• After system installation post installation activities has to be carried out.

• STMS is a post installation activity.

• Initially only DEV system is installed but at this point of time STMS can be configured

using virtual systems.

STMS OVERVIEW

Depending on the requirement we can go for One system landscapeTwo system landscapeThree system landscape or even more than

3 system landscapeDEV--VIRTUAL SYSTEMDEV-- QASDEV------------>QAS--------------->PRD

STMS OVERVIEW

STMS OVERVIEW

CONFIGURATION OF TRANSPORT SYSTEM The process of configuring from scratch the

transport system for a group of SAP systems include the following activities:

1. Initialize the Change and Transport Organizer2. Setting up the transport directory and the tp

program.3. Configuring the TMS, which includesa) Configuring the domain controllerb) Adding systemsc) Setting up systems groups4. Setting the system Change option.

STEP-1. Initialize the Change and Transport Organizer

The initialization is known as installation follow-up-work or processing after installation because it has to be performed as one of the first activities after the R/3 installation is finished.

Transaction Code: SE06This step is accomplish by executing

transaction SE06.

• Select standard Installation if your system is not a copied system.• In Standard Installation the system assumes that it has been installed using

SAP software kits. In this case the program will initialize some basic option CTO tables, and there is no need to adjust requests or repairs, because no changes exist.

• This option should not be used if the system was originated from a copy ,because the option will create many problems with the change and Transport Organizer when transports or even upgrades are performed.• When the selection is Database Copy or Database migration, it means that

the SAP system has been created from a copy.In this case it is very important that the system name doesnot match any other system within the SAP system group.

• When this option is executed the sytem will request the name of the source system and will ask wether the objects are to be kept as original (new role)

• Or changed to the new system ( assuming role from copied system).


STEP-2 Setting up the transport directory and the tp program

Creating a Transport Directory

STEP-2 Setting up the Transport Directory and the tp program

• The second step consists of ensuring that the transport directory (/usr/sap/trans) is shared among a SAP system group.

• All systems taking part in the group are included in the global configuration file TPPARAM(transport parameter file),located under the bin subdirectory of usr/sap/trans

• Edit this file and make sure all systems have a corresponding entry.• If a system is missing ,copy another system’s entry and change the values

( instance , the parameter <sid>/dbhost=<hostname>.• The transport directory can be shared using NFS on UNIX systems, or using file

shares and the alias SAPTRANSHOST or SAPGLOBALHOST on Windows NT systems.

• The installation program creates the transport directories and subdirectories with the needed files ,including an initial configuration or a TPPARAM file.

• This file must be correctly configured for the transport control tp to function properly.

Prerequistes. 1> COMMON TRANSPORT DIRECTORY• Standard practice is to have one common transport directory in a

system landscape. • Therefore, as each additional system in the landscape is installed, it

would require a network connection to the common transport directory and the appropriate operating system permissions.

• Define SAPTRANSHOST system in the landscape for common transport directory

• Edit the host file of the SAPTRANS HOST add SAPTRANSHOST in the etc file.• For example, in a Windows environment the corresponding file

name is %WINDIR%\system32\drivers\etc\hosts.


INDIVIDUAL TRANSPORT DIRECTORIES

INDIVIDUAL TRANSPORT DIRECTORIES• Possible scenarios for utilizing multiple transport

directories:• . Slow network connection between systems• . No permanent network connection between the

different SAP• systems of the system landscape• . Security reasons that prevent direct access to an SAP

system• . Different hardware platforms that do not allow a

common transport• directory

INDIVIDUAL TRANSPORT DIRECTORY

Prerequisites.• Check for entry in host/etc file for

hostname and ip address is properly maintained.

• All systems are connected in network and are accessible from each other.

• Check by doing ping from all the servers and by sharing folders .

• The SAP system parameter DIR_TRANS has to point to the path of the transport directory.

• For Unix, the default path is /usr/sap/trans. For Windows NT, the default path is \\$(SAPTRANSHOST)\sapmnt\trans and you must define the transport host with the alias SAPTRANSHOST on operating system level of the domain name server.

STEP2- Setting up the Transport Directory and the tp program

• Most customers choose the development system as the transport host because it is typically the first system installed.

• When you run the install program, the transport directory and its subdirectories are automatically created.

2) Setting up the transport directory and the tp program

a) Configuring the domain controllerb) Adding systemsc) Setting up systems groups

STEP-3 TMS CONFIGURATION


DEFINE DOMAIN CONTROLLER.• Decide the domain controller role .• Transport domain controller is generally

the DEV system as it is the first system installed in the System Landscape.

• Depending on the scenario you can also define a backup transport domain controller for SAP landscape.

A) Configuring the domain controller

a) Configuring the transport domain controller.Transaction code: STMS

Step-1 : Login to the SAP System in client 000 with ddic user and password.

Step 2 : System will prompt you to configure transport domain controller.If there is no domain controller system automatically prompts you to create one.

Step 3: Accept the system as a Domain controller.


Configuring the transport domain controller.Transaction code: STMS


Select Old standard password.You can select this option as per your scenario.

b) Adding systems1> Login to other system in 000 client with ddic

user and password2> Run transaction STMS 3> Select other configuration 4> Enter the IP Address of the transport domain

controller and save.


STEP-3 TMS CONFIGURATIONb) Adding systems

ppt

Documents