Friday, February 17, 2012

What are theTMS, Transport Domain Controller,Transport Domain &TMS Configuration procedure

                  It is required to be configured to export and import transport request among the systems in the landscape. This can be obtained with the help of R3trans.exe and tp.exe which are located in the kernel of central instance.
                  TMS should be configured as a part of post installation after CTS has initialized. Where in TMS configuration, we have to identify one of the systems as TDC in the landscape.
 Transport Domain Controller (TDC):
                  Which acts as a leader for all the systems part of transport domain. TDC configures its local transport directly, /usr/sap/trans, as common transport directory for all the systems in transport domain and TDC allows configuration and administrative settings to be performed  for other systems in the domain then changes distributed to all other systems.
 Transport Domain (TD):
                  Collection of all the systems connected together in TMS is called as Transport Domain. Usually development system configured as TDC instead of quality and production.

TMS Configuration:
 (1) Setting up of TDCUsually once Dev server installed we have to configure TMS after CTS initialization, which should be done by configuration of TDC. As QAS and PRD systems are not yet installed in the initial stage of implementation, generally, DEV gets configured as TDC.  
Logon to DEV with DDIC in client 000, execute STMS after initializing CTS. Once STMS executed for the first time system asks for the transport domain name setup and information of domain controller. Once required information is given save the configuration.
 Note:-To configure current system as TDC that local system information no need to be given, instead save the configuration.
                   Once TDC configured system performs below steps in back end.
  (I)   Configures TD and TDC.
 (ii)  Creates Domain. CFG and Transport Profile in bin directory, which is sub    directory of common transport directory.
 (iii)  Creates a user TMSADM with type communication.
(IV)    Creates required RFC communications using TMSADM user.
                  This file is a part of bin directory created after TMS configured which maintains TD information means all the systems information taken place in TD. Incase this file has been corrupted, has to be regenerated by TMS tool, but should not be edited manually.

Transport Profile:
                  It is a configuration file of transport domain resides in bin directory gets created by the system when TMS got configured. This transport profile TP_DOMAIN_SID.PFL, which contains all the system information includes SID, Common transport directory, DB type and DB information, etc… in terms of parameters and values.
                  As per the configuration settings maintained in transport profile we are required to use different unconditional modes upon the requirement when importing a TR in to a specific system.

(2) Virtual System Creation: As per the initial stage of the implementation project, only DEV system get installed which will be configured as TDC. When developer customizes object and includes them in a TR that request should be routed to its target system where it gets imported. But as the target quality system would not be installed already .We are required to create other quality and production system as virtual systems in TMS configuration with same SID will be used in future installation of these systems.
So that a transport request can be exported to its mentioned target which is quality automatically once it is released.

                  Later once other quality and production systems are physically installed we can convert them as physical systems in TMS by specifying same TDC as it was configured and approving them through TDC.

Go to STMSàSystem OverviewàSAP SystemàCreateàVirtual System
     Mention SID and Description and save and repeat the same for other virtual systems also.

(3) Create Transport Layer: Classification of all development objects as per its type which are standard and customized should be assigned with a transport layer which is standard and customized through which these objects gets exported/imported from integration to consolidation system.
                  A transport layer configuration is a logical assumption because all the dev objects should be assigned with the transport layer either standard or customized.

                  There is a standard layer “SAP” already exists in the system we need to create customized layer with Z<SID> format. Now two consolidation routes required to be created from integration to consolidation system with the assignment standard and customized layer. So that all standard objects will be moved through the standard layer, SAP, and customized objects moved through Z<SID> layer.

(4)Transport route Configuration: Logical route gets created between the systems taken place in transport domain through which we assume a TR can be export/import is called transport route.
                  We have two types of transport routs in TMS

                     -Consolidation route
                     -Delivery route

Consolidation Route: The route obtained between integrated system and consolidation system is known as consolidation route.

Delivery route:  The route obtained between consolidation system to recipient system is called as delivery route.

Transport or Target group: In case more than one system configured at consolidation level or recipient level, more than one consolidation route or delivery route can not be created by assigning single transport layer. In this situation, grouping all consolidation systems with naming format /Name/ is called as target group. Now consolidation routes are targeting to this group, from the group to all the consolidation systems route obtained automatically.

                  So that a TR which has released an integrated system will be exported to all the systems in the group then can be imported into all.

Go to STMSàTransport routsàGraphical Editoràchange
                                 Drag and drop all the system boxes into the below area which are required to be configured with the routes.

Go to EditàTransport LayeràCreate
                           Create a customized layer with Z<SID> format.

Go to EditàTransport routeàCreate
Drag the route to consolidation system
                  Select Consolidation route give standard transport layer nameàcontinue….
Perform the above for delivery route also then àSave

                  So above configuration can be saved then distributed to all the systems in network.
                   As per the above configuration TMS setup will allow developers to customize R/3 objects and create a TR with the target of quality system. Once the TR is released will be exported to target system (QAS).As QAS and PRD being as virtual systems a TR could not be imported in to those databases. After quality and production servers are installed as a part of TMS configuration we need to give the information of TDC which is DEV system in QAS and Production systems.

                  Then Log on to TDC go to STMSàSystems Overviewàselect virtual systems(QAS,PRD)àgo to SAP systemàApprove.

                  Distribute and activate the configuration to all the systems in landscape. So three systems in the landscape created in TDC will be copied to other system (QAS, PRD).Then TR import is possible in QAS and PRD systems.

Transport Tools:
                  There are two executable programs, R3trans and tp, residing at Kernel level runs for a TR to be exported and imported.
This tool R3trans does the complete transport work for tp which can be used for transporting data between different sap systems, even when they don’t belong to the same group. R3trans normally is not used directly but called from the transport control program, tp. It is the basic tool for the transporting the request. Where in R3trans.exe which obtains connection to the database TP controls the transports and generates the R3trans control files in tmp directory, but does no database-connect itself. All the "real work" is done from r3trans.
So that R3trans reads the control file of TR and update the entries in to TRBAT and TRJOB tables. Then related programs, RDD*, started using background wp reads these table according to that imports the data form data file in to database of target system.
Common Transport directory:
                  Usr/sap/trans of TDC residing at OS level of central instance, is called as common transport directory for all the systems taken place in the TD.
Once a TR gets released accordingly there are two files get created in data and cofile folders of common transport directory and that TR number gets entered in to the target system buffer folder.

/Data: All transport requests data file gets stored in this, which are in the format of
/Cofile:  All transport requests control file gets stored in this, which are in the format of

/bin: where Domain.cfg and transport profile which is tp_Domain_<Sid>.Pfl gets stored

/Log: Where all the TR logs get stored which are two types

-Slog: Which called as status log maintains steps were performed by TR.

-Alog: This is nothing but Action log maintains log information of every step like execution of reports, generation….etc in detail with the information of object list of TR.

Note: As per return codes
                        RC 0à successfully completed
                        RC 4à ended with warnings,
                        RC 8à Ended with errors (should be reported to ABAPers)
                        RC 12 & aboveàended with errors (taken care by Basis admin).

/Buffer: Which maintains all the transport request information have to be added in to import queue of other systems connected in transport domain. Unless a TR added in to buffer which can not be imported in to target system..

/Sap Names: Maintains all the user ids of users who creates a TR and its list in that system

/Tmp: Called as temporary directory or temporary folder where support pack released logs get created.

(5)Importing Transport request: As per two types of TR, generally which are local and remote, scc1 is to import the TR between different clients of same database where it was created.
                  Remote TR consists two steps to move from one to another system, which are export and Import.

Export: Once a TR released as per the target mentioned to TR automatically gets added in to that target system import queue, If transport routes have been configured which is called as Export.

Import: Log on to the target system import clientàgo to STMSàImport Overviewàdouble click on SIDàselect TR added into Transport Queueàselect TRàand click small truck button.




You said that development system configured as TDC, i think sap recommended production server as Transport Domain controller


Hi Ramesh,
we will configure Domain controller always Development system. some times we will make Quality system but Production system will not preferred & also one more thing in my case we are using solution manager as DC


Can you explain reasons why we configure development and quality as DC and why not Production can you explain me please


Post a Comment