Tcode STMS -> Tools → Administration → Transports → Transport
Management System.
The Transport Management System (TMS) allows transports between different R/3 Systems to be administered centrally.
The TMS classifies R/3 Systems into transport groups and transport domains:
A transport group consists of all R/3 Systems that can access a common transport directory.
A transport domain consists of one or more transport groups.
To enable transports to be administered centrally, it must be possible to administer all systems in the transport domain from a designated R/3 System, called the transport domain controller.
For the administration of transports, the following information is stored centrally:
The systems participating in the transports
Their transport routes
This configuration data does not need to be set manually in every R/3 System. Instead, using RFC, the transport domain controller distributes the data to all participating R/3 Systems.
Transport Management System (TMS):
TMS: Administering R/3 Systems
To create a transport domain, call the TMS from Client 000. To automatically define the transport domain controller as as the current system choose Tools → Administration → Transports → TransportManagement System.
As soon as the domain has been created, additional systems can apply for acceptance by the domain. For security reasons, these systems are not accepted until they have been authorized by the transport domain controller.
The TMS System Overview displays the various system statuses:
Waiting for acceptance by the domain
Active
System locked for the TMS
System not accepted
System deleted
Technically, TMS can connect systems with different R/3 release statuses. However, SAP does not support any transports between such systems.
Because of its central importance, the transport domain controller should run on an R/3 System with a high availability.
Configuring Transport Routes
To configure the transport routes between systems in the domain, use the hierarchical list editor and graphical editor provided by the TMS. Define these settings in the transport domain controller.
The transport routes can be either consolidation or delivery routes.
For consolidation routes, a transport layer is used, for example to define a
route between the development and the quality assurance system.
Delivery routes connect systems, for example the quality assurance and the
production system. They do not use transport layers.
Create transport routes in the graphical editor using drag and drop.
After the transport routes have been configured in the transport domain
controller, they can be distributed across all systems in the domain.
These setting must be activated in all the systems in the domain. This can also be
done centrally by the transport domain controller.
To enable previous configurations to be reused, you can create versions in the TMS.
TMS : Setting up an R/3 Transport Landscape
1. Make the transport directory available.
2. Configure the transport domain controller and define the domain.
3. Configuration of the transport program (tp) is done automatically and
must not be done at OS level.
4. In the TMS:
- Include all remaining systems in the domain
- Define the transport routes
- Define QA approval procedure
5. Set the system change options according to the role of the R/3 System.
6. Create clients and set the client change options for the production system,
development system, and so on.
The steps for setting up a transport landscape are summarized below.
To set up an R/3 transport landscape:
Make a transport directory available to every R/3 System that will be ransporting.
The TMS allows a local transport directory for every R/3 System.
To configure the TMS, define the transport domain controller.
In the TMS:
- Include all remaining systems in the domain.
- Define the transport routes.
Set the system change options according to the role of the R/3 System.
Create clients in every R/3 System and set the client change options (production
system, development system, and so on).
R3trans Return Codes
R3trans sets a return code that shows whether or not the transport has succeeded. You can view details on transports in the log file. Here are the following return codes:
0 : No errors or problems have occurred.
4 : Warnings have occurred but they can be ignored.
8 : Transport could not be finished completely. Problems occurred with certain objects.
12 : Fatal errors have occurred, such as errors while reading or writing a file or unexpected errors within the database interface, in particular database problems.
16 : Situations have occurred that should not have.
Examples:
Constants in the program are too small
Not enough available memory
Internal R3trans error
Other return codes are not set by R3trans itself but point to errors, such as segmentation faults.
SAP R3trans Unconditional Modes
By using unconditional modes, you can override the rules of the transport system. The following modes are available:
Export:
· 1: Ignore incorrect status of a change request.
If you do not set this mode, only change requests with the status A (all locked), O (open) or R (released) are exported. If the export is successful, the change request is released by R3trans.
· 8: Allow direct selection of forbidden tables.
Some tables are part of complex objects and generally cannot be exported alone.
Import:
· 1: Ignore that this change request was already imported into this system and import everything again.
If you do not set this mode, only objects that have not already been imported successfully are imported again.
· 2: Overwrite originals
· 6: Overwrite repaired objects
· 8: Ignore the restriction resulting from table classifications and import all table entries into specified clients.
SAP Netweaver 2004s - Components of Monitoring - System Landscape Directory (SLD)
The SAP System Landscape Directory (SLD) is the central information provider in a system landscape. The SLD contains two types of information:
- Component information: all available SAP products and components and their versions. If appropriate, external products are also registered here.
- Landscape description: all installed systems in a system landscape.
