The Transport Management System (TMS) SAP BASIS

The TMS is the transport tool that complements the Change and Transport Organizers for central management of all transport functions. The TMS is used for performing the following functions:

  • Defining a central transport domain controller for managing transport configuration in a group of related SAP systems
  • Configuring the SAP system landscape by assigning roles
  • Defining the transport routes among systems within the landscape
  • Displaying and managing import queues on each of the systems
  • Performing imports of request queues or specific requests
  • Performing transports between systems that do not share a common transport directory
  • Distributing a configuration
  • Testing the configuration
  • Displaying the transport logs and parameter files

Within a SAP transport domain, all systems share a common or reference configuration held in the transport domain controller. Other SAP systems contain a copy of this reference configuration. Normally all systems within a transport domain share a common transport directory (usr/sap/trans), although there are situations where this directory is not shared, such as in slow WAN connections, in heterogeneous hardware platforms, or for security reasons. Because of this possibility, there is the concept of the transport group, which indicates a group of SAP systems that share the common transport directory. A transport domain can have more than one transport group. The next sections explain the main functions and options of the TMS in configuring systems or domains and defining transport routes. The functionality related to managing imports and transport using the TMS is explained in the next section.

Configuring Systems and Domains

The transport domain will contain the SAP system landscape whose transports are being managed jointly. One of the systems will have the role of domain controller and will hold the main reference configuration. For availability and security reasons, this system is normally the production system.When transaction STMS is started in client 000 on a SAP system, the following happens:

  • If the system is already assigned to a transport domain, the initial screen shows the system's role in the domain.
  • If the system has not yet been assigned to a transport domain, it will look for file DOMAIN.CFG in the transport directory to locate an existing transport domain.
  • If a domain exists, the system will prompt to join the domain.
  • If a domain does not exist, a new transport domain is created and the current SAP system is assigned as the transport domain controller.

When a transport domain is first created, the TMS system performs several configuration actions:

  • Creating the user TMSADM
  • Generating RFC destinations required for R/3 communications
  • Creating the file DOMAIN.CFG in the bin directory of the common transport directory

This file contains the TMS configuration and is used by systems joining groups and domains for checking existing configurations.

Transport Management System initial screen

Transport Management System initial screen

The TMS allows the definition of a backup domain controller that can take over the functions of the transport domain controller in case of failures. To define a backup domain controller, select the main transport domain controller system, change its definition (SAP System | Change), then select the Communication tab and enter the system to be used as backup domain controller. Save your entries and distribute your configuration (Extras | Distribute and Activate Configuration). When configuring the TMS on a SAP system consisting of several application servers, you can specify the application server to be used for TMS functions. Normally you should select the application server with the highest availability, such as the central instance (the one running the message and/or enqueue server).

Adding SAP Systems to a Transport Domain

Once the transport domain controller is configured, you have to add other SAP systems within the landscape. TMS allows the definition of the following:

  • Regular SAP systems sharing the common transport directory. To include these systems, log on to the system to be included in client 000 and start transaction STMS. The TMS will check for the configuration file DOMAIN.CFG and will automatically propose to join the domain. Select the proposal and save your entries. The system status will be waiting to be included in the transport domain.

    For security reasons, inclusion of systems still needs to be accepted by the transport domain controller. So, log on to the domain controller and go to Systems. The screen will display the new system. Select this new system, and choose from the menu SAP System | Approve.

  • SAP systems without common transport directory. To include these systems, log on to the system to be included in client 000 and start transaction STMS. In the Configure Transport Domain dialog box, select Other Configuration | Include System in Domain, then enter the hostname and system number. Save your entries. The system status will be waiting to be included in the transport domain. As in the previous case, this system must be accepted by the transport domain controller to be active.
  • Virtual systems. The TMS includes the functionality of adding virtual systems for the purpose of defining SAP systems that have not yet been installed or are not yet available. These systems are defined in the transport domain controller. In the system overview screen, select SAP System | Create | Virtual System. Enter the system ID and description and save your entries.
  • External systems. These are like virtual systems but are used for sending transport information or exchanging it with other systems using exchangeable data media. External systems have a transport directory that is different from the transport domain controller's. To create external systems, select SAP System | Create | External System. Enter the system ID and description, and the path and description of the transport directory.

Displaying Transport System Status

At any time you can check the systems and the current status of the transport domain configuration in the TMS systems overview. To do this, enter transaction STMS in the command field. In the initial TMS screen, select Overview | Systems.

TMS systems overview

TMS systems overview

The systems overview shows the current status of each of the systems in the Status column. You can see whether the configuration is up to date and active or whether there was any error in distributing the configuration.
You can display the meaning of the icon symbols by selecting Extras | Legend or by clicking on the Legend icon on the application toolbar.

STMS icon legend

STMS icon legend

Configuring Transport Routes

Once the domain and systems are configured, you have to specify the transport routes that will be used by the systems. Because many customers' systems landscapes fall into the same categories, the TMS provides some standard system groups that can be used for easily defining routes. When standard system groups are used, the system automatically generates the transport routes. You can select the following standard system groups:

  • Single system
  • Two-system landscape: development and production
  • Three-system landscape: development system, quality assurance system, and production system

Transport routes are configured by selecting Overview | Transport Routes from the initial TMS screen. To define transport routes or use a standard configuration, you have to be in change mode. If you are in display mode, switch by clicking on the Display/Change icon. If you select the standard configuration, the current configuration of the SAP systems will be replaced by these standard settings, although existing objects or packages will not be deleted. To define a standard configuration, select Configuration | Standard Configuration and then whether it is a Single System, Development and Production System, or Three Systems in Group.

Enter your selection and click Continue. Depending on selection, the system will then ask which systems play which role: development, production, or quality assurance. It will then generate the transport routes according to user entries. If you are not using standard configuration but need to define complex transport systems, you can also use standard settings for initial transport routes and then define additional consolidations or delivery routes. The TMS includes two types of editors (you can configure editor settings in the Graphical Editor and using the Transport Routes Editor option from Settings in the main menu) for defining and configuring transport routes:

  • A hierarchical list editor, where systems and transport routes are displayed in a tree structure. To create transport routes in this editor, from the initial TMS screen select Overview | Transport Routes and then, while in change mode, select the Create button on the application toolbar.
  • A graphical editor, where systems and transport routes are displayed graphically and editing can be performed using the mouse. For accessing the graphical editor, from the hierarchical list editor screen, select Goto | Graphical Editor. Information on the display areas and on working with the graphical editor can be found in the online documentation. As introduced in the section on transport system concepts, transport routes can either be of the consolidation or delivery type. For a standard threesystem landscape (development, quality assurance, and production), the transport routes are as follows:
  • The consolidation route links the development system and the quality assurance system. This transport layer is named Z<SID>, where <SID> is the system ID of the development system.
  • A delivery route is generated for linking the quality assurance system and the production system.

When developments or changes are made in the development system that include objects whose package refers to the standard transport layer, these changes are recorded in change requests. These change requests will be transported first to the quality assurance system and then to the production system.The transport system also creates the consolidation route SAP that is used when changes are made to SAP objects. In these cases, the changes are recorded in repair tasks that can be transported the same way.

Notice that you will only be able to create delivery routes for existing consolidation routes.

Transport route configuration

Transport route configuration

You will notice in the title bar that the system includes a version number. When an active configuration is modified and saved, the system creates a new version. You can activate a stored version by choosing Configuration | Get Other Version from the transport domain controller on the Transport Route screen.

Distributing and Verifying TMS Configuration

Before distributing the TMS configuration to other systems in the group, you should first check the configuration. There are several checking options available that should behave without errors before the TMS can function properly. If any errors are found, review your configuration or network settings before proceeding. Within the Transport Routes Overview screen, select Configuration | Check | Request Consistency and then either Local or All Systems. Because all SAP systems in a transport domain communicate using RFC connections, you should also check these RFC connections in the TMS system overview. Select Overview | Systems, and then from the Systems screen, select SAP System | Check | Connection Test.

To check whether the transport control program tp and the TPPARAM file are correctly configured, select SAP System | Check | Transport Tool from the Systems Overview screen. Additionally, you should also verify the availability of the transport directories in all systems within the transport domain. Select SAP System | Check | Transport Directory from the Systems Overview screen. When the configuration of the transport domain controller is complete, the next step is to distribute the configuration to all other R/3 systems within the transport domain. To do this, select Configuration | Distribute and Activate from the Transport Routes Overview screen. You can also select Extras | Distribute and Activate Configuration from the Systems Overview screen.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd Protection Status