You are on page 1of 11

STMS

What is STMS?
The expansion for STMS is SAP Transport Management System. STMS is being used to transport all your customization and workbench work from Development to QA and then to production.

SAP System Landscape:


The system landscape contains all the SAP Systems that you have installed. It can consist of several system groups, whose SAP systems are linked by transport routes. The recommended landscape by SAP is three system landscape there you will be having a separate R/3 System for development and separate R/3 System for quality (testing purpose) and likewise for the production there will be separate R/3 System. Another two more types of landscape is there but it is not recommended by SAP the two types are namely two system landscape and single system landscape. A twosystem landscape is an alternative for smaller SAP implementations where little Workbench development takes place. The two-system landscape does not include a separate quality assurance system QAS. The quality assurance client is also in the development system DEV. The last type of landscape is what single system landscape and in this all the development, quality and production will present in the same system. Once the system landscape is fixed and then we have to fix the domain controller.

Domain Controller:
The transport domain contains all SAP systems whose transports are to be administrated jointly. One of these SAP systems among the landscape is chosen as the transport domain controller. Since all activities relevant to the entire transport domain, such as configuring transport routes or RFC connections, can only be carried out on the domain controller, the SAP system selected to be the domain controller should have: High availability. A high level of security. A high level of maintenance. The domain controller is normally configured on a production system or a quality assurance system. Out of several reasons you may choose to set up an SAP System dedicated to tasks that may be carried out CENTRALLY. This includes the task of the TMS domain controller. The system load on the

SAP system that is chosen as the domain controller is low, and only increases for a short period when the TMS configuration is changed.

Configuration Of Domain Controller:


To activate the TMS on an SAP system, run transaction STMS in client 000 with user authorization S_CTS_ADMIN. If the SAP system is already assigned to a transport domain, the TMS initial screen shows the systems status, either as a domain controller, or as a SAP system within a domain. If the SAP system is not yet assigned to a transport domain, the system tries to locate an existing transport domain within the current transport group by reading the file DOMAIN.CFG in the directory bin of the common transport directory. If no transport domain exists, a new transport domain is created, and the current SAP system is assigned as the transport domain controller. When a transport domain controller is first created, the TMS generates: A transport domain and a transport group. User TMSADM. The RFC destinations required for the TMS. File DOMAIN.CFG in directory bin.

The name of the transport domain may not contain blanks and may not be changed afterwards without reconfiguring the domain controller. By default, a transport domain will have the name DOMAIN_, where is the system ID of the domain controller. The name of the transport domain cannot be changed afterwards. After configuring domain controller we have set the transport routes. Note: If the domain is already configured then we can execute a transaction code DICO to delete the existing TMS configuration. It can be executed from the STMS and also the RFC connections.

Creating Virtual Systems:


It is a standard practice in the industry to create virtual systems as the real systems could not be available during the initial configuration (DEV server is procured during implementation, QAS will be procured after 3 to 4 months from kickoff date and the PRD is procured before 2 months of GoLive). Virtual Machines/ Systems can be replaced by real systems and the configuration now points to the real system. To configure the virtual system we have to follow the below steps.

Go to STMS (Domain Controller) > Menu Overview > Systems > SAP System > Create Virtual System While creating virtual system we have to give the virtual system name and we have to give a short description.

Uses of Virtual System:


Virtual Systems help us to address the changes that are performed in DEV to QAS and PRD. If virtual systems are not defined or the virtual system name differs with real system name, then the entire addressing of changes has to be performed manually which is referred to Add To Buffers The changes that are performed in the DEV are added to the buffers of the virtual systems.

Replacing the virtual Systems with real systems:


1. Execute STMS delete the virtual Systems from Transport Domain Controller . 2. Login to 000 client of the Real systems (WSQ,WSP). 3. Execute STMS -on the pop-up window select use other configuration option to include the systems in the domain. 4. Specify the Domain name, Target host (Hostname of TDC(Domain)) save. 5. A request is sent to transport domain controller to include the system in the landscape. 6. Login to TDC (Transport Domain Controller OverviewSystemsselect the system which is waiting for inclusion in the domain. 7. Click on approve to include in the Domain. 8. Domain.CFG i.e., Domain Configuration file is updated. TMSADM is the user that is created to communicate with TDC.

RFC Connections with name TMSADM, TMSSUP communicate with Transport Domain Controller

are

created

to

Buffer directory is created to host all the transport definitions (address of the change requests) i.e. transport Request number, name of the owner and time stamp. Note: Virtual System name and Real system name should be same If they differs then all the change requests has to be added manually

Configuring Transport Routes:


After establishing a transport domain: 1. Model transport routes from the domain controller using: Default standard configurations Hierarchical list editor. Graphical editor. Transport routes for the standard system groups are generated automatically. You can choose from the following standard system groups: Single system. Development system and production system. Development system, quality assurance system, and production system.

If you use the standard configuration function, the current configurations for all R/3 Systems are replaced by the standard settings. Existing development classes, transport layers, or objects created in the R/3 System are not deleted. For complex system groups, define additional consolidation and delivery routes after setting up the standard transport route configuration on the basis of one of the standard system groups. If you modify and save an active configuration, the version counter increases. To activate a stored version, from the R/3 initial screen choose STMSOverview Transport RoutesConfiguration Get other version.

Transport Routes:
There are two types of route Consolidation Routes and another Delivery Routes.

Consolidation Routes:
To make your changes transportable, set up a consolidation route for each transport layer. Specify your development system as the starting point (source) of these consolidation routes. Specify the quality assurance system as the transport target (in a two-system landscape, specify the production system as the transport target). Any modified objects that have a consolidation route set up for their transport layer are included in transportable change requests. After the request has been released the objects can be imported into the consolidation system. If you make changes to objects which have no consolidation route defined for their transport layer, then the changes are made automatically in local change requests (or in Customizing requests without a transport target). You cannot transport them into other SAP Systems. You can set up one consolidation route only for each SAP System and transport layer. When you define consolidation routes, note the additional functions available when you use Extended Transport Control.

Delivery Routes:
After you have imported your development work into the quality assurance system, you then want to transport it into your production system. You may even want to transport it into several SAP Systems (for example, additional training systems). To do this, you have to set up delivery routes. Delivery routes have a source system and a target system. When you set up a delivery route, you are making sure that all change requests that are imported into the routes source system are automatically flagged for import into the routes target system. You can set up several delivery routes with the same source system and different target systems (parallel forwarding). You can also set up delivery routes in sequence (multilevel forwarding).

CTS transport control makes sure that all requests from the development system are flagged for import into all other SAP Systems in the same order in which they were exported. This is important, since different requests can contain the same Repository object or the same Customizing setting at different development levels, and you must avoid overwriting a more recent version with an older version.

Transport Directory:

The folders present in the usr\sap\trans are bin, data, cofiles, buffer, tmp, log, Eps, sap names. These are the folders which will present inside the trans folder. Bin: This directory contains two files namely TP_<domain>_SID.PFL and DOMAIN.CFG the PFL file is the transport parameter file and the File

DOMAIN.CFG in this directory contains the common transport directory, for storing the TMS configuration. 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). EPS: This is download directory for SAP support packages from SAPNET. SAP NAMES: This SAP NAMES contains the user name of the person who created the change request.

Significance of Transport Management System:


Within the R/3 System Landscape customizing & development changes performed in a development client, has to be transferred 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 then we may not be able to create a transportable change request.

Types of Change request:


The change request entry is maintained in the table name TRBAT by TP. For every request entry will be made in the table and if we want to see the entry means we can execute TRBAT in se11 transaction code.

Customizing change request: Used for record only the client dependent changes using IMG. And after completion of customizing, the changes can be transported to another R/3 system. The t-code used for managing this type of request is SE10. Work-bench change request: Used for client independent (cross-client) customizing objects and all repository objects created or maintained through the ABAP workbench. The t-code used for managing this type of request is 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. A local change request can be released but not transportable.

The Transport Management System (TMS) enables you to:


Define an R/3 System's role within a system landscape or transport domain. Configure the transport routes using either a graphical editor or hierarchical editor. Configure the transport tool transport control program tp. Display the import queues of all R/3 Systems in the transport domain. Decide whether the quality assurance testing was successful in the QA System. Start the import of change requests in an import queue. Perform transports between R/3 Systems without a common transport directory. Handle transport proposals of developers.

To configure STMS:
To configure STMS three steps are involved after the installation.

Step1 Go for T-Code SE06 In 000 client you will be getting the screen like this.

Step2 Click on the button namely Perform Post-Installation Actions. It will take some time to get configured. Step3 Then go for STMS T-Code in the same 000 client. Then you will be getting screen like this.

Step4 Then in the system type the system name and give the description and in the domain give the domain name give the domain name in which the system belongs after giving that save it you will be getting the below screen.

After configuring STMS we can use the following transactions for accessing TMS
Transaction code STMS STMS_QUEUES STMS_IMPORT STMS_INBOX STMS_QA STMS_DOM STMS_PATH STMS_ALERT STMS_TCRI STMS_FSYS Function Initial screen of the Transport Management System Displays the import queue Import queue of the current SAP System TMS worklist (transport workflow) QA worklist (TMS quality assurance) TMS system overview TMS transport routes CCMS Alert Monitor Display/change critical transport objects Create/change TMS system list