STMS

TMS(1)

Why Transport Management SystemWithin the R/3 System Landscape customizing & development changes performed in a development client , has to transfer 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 (ie inconsistent) then we may not be able to create transportable change request .

After SAP R/3 installation we have to configure TMS for the following reasons : To create transportable change request To import transport request To setup Global Transport System between R/3 systems To transport clients between R/3 systems

Why Transport Management SystemWithin the R/3 System Landscape customizing & development changes performed in a development client , has to transfer 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 (ie inconsistent) then we may not be able to create transportable change request .

After SAP R/3 installation we have to configure TMS for the following reasons : To create transportable change request To import transport request To setup Global Transport System between R/3 systems To transport clients between R/3 systems

TMS(2)

Why Transport Management System

The R/3 change management system, also known as the Change and Transport System (CTS), provides options for data transfer between and within R/3 Systems.

The tool can be used, to transport tuned and tested customizing settings between systems and clients.

Using transport requests and customizing settings, development work created in a separate development system (DEV) can be automatically recorded in change requests and then transported into a quality assurance client, and finally into a production client.

Once the change request has been released from the source system, it becomes a transport request.

Development / Correction Most changes are recorded to development/correction tasks which contain changes to objects that originated in the current R/3 system .Repair A repair is a change to an R/3 repository object that originated on an r/3 system other than the current R/3 system .The object be an sap delivered object or customer developed object.

Why Transport Management System

The R/3 change management system, also known as the Change and Transport System (CTS), provides options for data transfer between and within R/3 Systems.

The tool can be used, to transport tuned and tested customizing settings between systems and clients.

Using transport requests and customizing settings, development work created in a separate development system (DEV) can be automatically recorded in change requests and then transported into a quality assurance client, and finally into a production client.

Once the change request has been released from the source system, it becomes a transport request.

Development / Correction Most changes are recorded to development/correction tasks which contain changes to objects that originated in the current R/3 system .Repair A repair is a change to an R/3 repository object that originated on an r/3 system other than the current R/3 system .The object be an sap delivered object or customer developed object.

TMS(3)

To activate customizing changes permitted in a particular client ,and whether these Customizing changes are automatically recorded to a change request ,have to set ‘Changes and transports for client-specific objects’ using the transaction code SCC4

To activate customizing changes permitted in a particular client ,and whether these Customizing changes are automatically recorded to a change request ,have to set ‘Changes and transports for client-specific objects’ using the transaction code SCC4

TMS(4)

To permit or disallow create or changes to R/3 repository objects from any client ,have to set ‘Client independent object changes’ using the transaction code SCC4

To permit or disallow create or changes to R/3 repository objects from any client ,have to set ‘Client independent object changes’ using the transaction code SCC4

Change Request (1)

Types of CHANGE REQUEST

Customizing Change RequestUsed for record only client dependent changes using IMG .And after completion of customizing , the changes can be transport to other r/3 system . To manage the customizing change request we use transaction code SE10 .

Workbench Change Request Used for client independent (cross-client) customizing objects and all repository objects created or maintained through the ABAP workbench .To manage the workbench change request we use transaction code SE09 .

Transportable Change RequestThe change requests which are transported to other R/3 systems after release .

Local Change RequestA 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 Request . Local change request can be released but not transportable .

Types of CHANGE REQUEST

Customizing Change RequestUsed for record only client dependent changes using IMG .And after completion of customizing , the changes can be transport to other r/3 system . To manage the customizing change request we use transaction code SE10 .

Workbench Change Request Used for client independent (cross-client) customizing objects and all repository objects created or maintained through the ABAP workbench .To manage the workbench change request we use transaction code SE09 .

Transportable Change RequestThe change requests which are transported to other R/3 systems after release .

Local Change RequestA 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 Request . Local change request can be released but not transportable .

Change Request (2)

Example of a change request : SCMK900210

The ID number of a change request or tasks begins with the three character system-ID SCM . Followed by K9 . Then five digit number 00210 .

Next task will be SCMK900211 .

If project leader assign another user to the change request then another task will create with ID SCMK900215.

A change request is a collection of tasks .

Change Request (3)

To release the Change Request ,each separate task in the change request must be documented & released separately .using the button

To release the Change Request ,each separate task in the change request must be documented & released separately .using the button

Releasing the task SCMK900212

Releasing the task SCMK900212

Follow the messageFollow the message

Components of the R/3 CTS system:

The CTS system is actually made up of various components which allow for the movement of objects and help to maintain comparable and up-to-date changes from one system to the next. Here is a list of the components you may encounter while using the CTS to perform various tasks.

-Tasks, Change requests and Repairs - Correction system or Workbench Organizer - Transport System - Development class - Transport layer - System types in the CTS pipeline. - Repository objects - Customizing objects - Unix file systems in the transport process - Important SAP delivery class and table types and tables in the CTS process - Programs in the CTS process - Version Management - TP and R3trans program

The CTS system is actually made up of various components which allow for the movement of objects and help to maintain comparable and up-to-date changes from one system to the next. Here is a list of the components you may encounter while using the CTS to perform various tasks.

-Tasks, Change requests and Repairs - Correction system or Workbench Organizer - Transport System - Development class - Transport layer - System types in the CTS pipeline. - Repository objects - Customizing objects - Unix file systems in the transport process - Important SAP delivery class and table types and tables in the CTS process - Programs in the CTS process - Version Management - TP and R3trans program

Overview of Task, Change Request and Repair:

TASK: Corrections and repairs are recorded in tasks and transported using the change requests. It can control changes to internal components of the system that includes data dictionary objects, ABAP/4 programs, screens, CUA definitions, and documentation. The task can register and can keep the documentation of all the changes to the system objects. Once the objects are locked the system prevents parallel changes to the system objects. For existing objects, the system ensures that only a single original copy of each object exists. The previous version of an object can be restored and two versions of the objects can be compared. The CTS system asks for a change request number (if the recording is on in that client) whenever a customizing change is done or a new object is created with a development class other than $TMP (local object development class). A task is automatically created under a change request. User has to release the task first to release the change request. The user can be able to create or modify the object only after he or she opened a task. Opening a task registers the change with the system. Once the user releases a task, the objects in task get transferred to the change request. After the unit testing in customizing master client is completed, a task is released to its change request. After a task is released, it can no longer be modified. If the user wants to modify the same objects, which were included in the released task, he has to create a new task..

TASK: Corrections and repairs are recorded in tasks and transported using the change requests. It can control changes to internal components of the system that includes data dictionary objects, ABAP/4 programs, screens, CUA definitions, and documentation. The task can register and can keep the documentation of all the changes to the system objects. Once the objects are locked the system prevents parallel changes to the system objects. For existing objects, the system ensures that only a single original copy of each object exists. The previous version of an object can be restored and two versions of the objects can be compared. The CTS system asks for a change request number (if the recording is on in that client) whenever a customizing change is done or a new object is created with a development class other than $TMP (local object development class). A task is automatically created under a change request. User has to release the task first to release the change request. The user can be able to create or modify the object only after he or she opened a task. Opening a task registers the change with the system. Once the user releases a task, the objects in task get transferred to the change request. After the unit testing in customizing master client is completed, a task is released to its change request. After a task is released, it can no longer be modified. If the user wants to modify the same objects, which were included in the released task, he has to create a new task..

The transport types

K type: The system owner does not get changed with K type transport. This kind of transport is only allowed to consolidation and production system. After the K type of transport is done no correction is allowed to those objects. Any changes to K type transport objects in consolidation system are called repair. The repairs can be done to those objects if the change option is selected in SE06 and change option is there in client level selection in T00 table. Generally K type transport is used for stage and production environment. C type: With the C type transport the ownership of that object is also transferred to the target. After the transport is done, the target system is the owner of the transported objects. The objects will be originals of the target system. These kind of transports are generally done in a four tier architecture, where a bundle of development objects can go from the sandbox environment to development environment or development environment to integration environment and vice versa. SAP recommends doing these transports when the objects should move to another system for further development work. T type: T type is called a transport of copy. The ownership of the object remains with the source; the target system just gets the copy of the objects. When a sap patch is applied to the development system and transported to other systems, those are perfect example of T type transports

K type: The system owner does not get changed with K type transport. This kind of transport is only allowed to consolidation and production system. After the K type of transport is done no correction is allowed to those objects. Any changes to K type transport objects in consolidation system are called repair. The repairs can be done to those objects if the change option is selected in SE06 and change option is there in client level selection in T00 table. Generally K type transport is used for stage and production environment. C type: With the C type transport the ownership of that object is also transferred to the target. After the transport is done, the target system is the owner of the transported objects. The objects will be originals of the target system. These kind of transports are generally done in a four tier architecture, where a bundle of development objects can go from the sandbox environment to development environment or development environment to integration environment and vice versa. SAP recommends doing these transports when the objects should move to another system for further development work. T type: T type is called a transport of copy. The ownership of the object remains with the source; the target system just gets the copy of the objects. When a sap patch is applied to the development system and transported to other systems, those are perfect example of T type transports

Exporting change request

This is the physical copying of the recorded objects from the database of the R/3 system to files at the operating system level .

This files are located in the transport directory .

Operating system level file K900210.scm created on directory /usr/sap/trans/cofiles

& the file R900210.scm created on directory /usr/sap/trans/data & the file

SCME900143.SCM created on directory /usr/sap/trans/log .

The file extension will be the source system sid name .

This is the physical copying of the recorded objects from the database of the R/3 system to files at the operating system level .

This files are located in the transport directory .

Operating system level file K900210.scm created on directory /usr/sap/trans/cofiles

& the file R900210.scm created on directory /usr/sap/trans/data & the file

SCME900143.SCM created on directory /usr/sap/trans/log .

The file extension will be the source system sid name .

Transport directory(1):

Transport directory is a file system located on OS level where the objects in change requests that were released and exported from that R/3 system are physically copied so that they can subsequently be imported to a target R/3 system.

/usr/sap/trans is the parent transport directory

Often in a system landscape there is only one common transport directory .

All R/3 systems that share the same transport directory make up a TRANSPORT GROUP.

If the transport directory is not shared with other systems ,it is called the Private transport directory .

Transport directory is a file system located on OS level where the objects in change requests that were released and exported from that R/3 system are physically copied so that they can subsequently be imported to a target R/3 system.

/usr/sap/trans is the parent transport directory

Often in a system landscape there is only one common transport directory .

All R/3 systems that share the same transport directory make up a TRANSPORT GROUP.

If the transport directory is not shared with other systems ,it is called the Private transport directory .

DEVDEV QASQAS

Common transport directory

Common transport directory

Private transport directory

Private transport directory

PRDPRD

Transport Group 1Transport Group 1 Transport Group 2Transport Group 2


One or Many Transport Directory :

The network connection to an R/3 system is not fast enough .

There is no permanent network connection between the different R/3 systems of the system landscape .

There are security reasons that prevent direct access to an R/3 system (like PRD).

There are different hardware platforms that do not allow a common transport directory.

Common transport directory is standard practice .

When more than one transport directory ,then manual transfer the operating system level file from server to server.

Every computer of the transport group on which an R/3 instance is installed should have write access & read access to the transport directory.

One or Many Transport Directory :

The network connection to an R/3 system is not fast enough .

There is no permanent network connection between the different R/3 systems of the system landscape .

There are security reasons that prevent direct access to an R/3 system (like PRD).

There are different hardware platforms that do not allow a common transport directory.

Common transport directory is standard practice .

When more than one transport directory ,then manual transfer the operating system level file from server to server.



\usr\sap\trans\usr\sap\trans

binbin

datadata

cofilescofiles

bufferbuffer

loglogtmptmp actlogactlog

sapnamessapnames

olddataolddata

epseps


eps : This is download directory for SAP support packages from SAPNET .eps : This is download directory for SAP support packages from SAPNET .

bin : This directory contains TP_<domain>.PFL (e.g. TP_DOMAIN_SCM.PFL) file which is the mainly transport parameter file .

bin : This directory contains TP_<domain>.PFL (e.g. TP_DOMAIN_SCM.PFL) file which is the mainly transport parameter file .

data : This directory contains actual data file of the related change requests with the customizing & development changes . (e.g. R900210.scm ) .

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 ) .

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 .

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 ) .

log : This directory contains all types of log files about the export , import of change requests (e.g. SCME900143.SCM ) .

actlog : This directory stores the log of user actions in R/3 for all change requests & tasks like date/user of creation & release of CR (e.g. SCMZ900143.SCM ).This directory is accessed by CTO only.

actlog : This directory stores the log of user actions in R/3 for all change requests & tasks like date/user of creation & release of CR (e.g. SCMZ900143.SCM ).This directory is accessed by CTO only.

olddata : This directory is needed when we clean up the transport directory.Old exported data that is to be archived or deleted is stored in this directory .

olddata : This directory is needed when we clean up the transport directory.Old exported data that is to be archived or deleted is stored in this directory .


Technical info about transport directoryTechnical info about transport directory



Estimate 100 MB per R/3 instance that will be using the transport directory .Estimate 100 MB per R/3 instance that will be using the transport directory .

To share common transport directory ,all application & database servers must be in the same windows NT domain or if domain differs create NT trusted relationship between them.

To share common transport directory ,all application & database servers must be in the same windows NT domain or if domain differs create NT trusted relationship between them.

Set a global share sapmnt to point the directory \usr\sap files . Then \usr\sap\trans files can be access as \sapmnt\trans .

Set a global share sapmnt to point the directory \usr\sap files . Then \usr\sap\trans files can be access as \sapmnt\trans .

Set NT access type Full Control for Everyone on this transport directory .Set NT access type Full Control for Everyone on this transport directory .

Must define the transport host using the alias SAPTRANSHOST . For this have to make an entry on file c:\winnt\system32\drivers\etc\hosts

92.83.18.149 scma SAPTRANSHOST .

Must define the transport host using the alias SAPTRANSHOST . For this have to make an entry on file c:\winnt\system32\drivers\etc\hosts

92.83.18.149 scma SAPTRANSHOST .


Preparing Operating System Users:

If we want to install tp, the operating system users must fulfill the following:

Each user that wants to use the transport system requires read and write authorization in the transport directory.

If you call a transport program directly from the operating system level, only use the operating system user <SAPSID>ADM , SAPService<SAPSID>

Preparing Operating System Users:

If we want to install tp, the operating system users must fulfill the following:

Each user that wants to use the transport system requires read and write authorization in the transport directory.

If you call a transport program directly from the operating system level, only use the operating system user <SAPSID>ADM , SAPService<SAPSID>

Performing import

Imports are normally not performed by the developer who requested an export, but by the system administrator.For import the administrator must log onto the operating system of a host in the target

system as the user <sapsid>adm .

we can start a complete import with the following command:

cd \usr\sap\trans\bin

tp addtobuffer SCMK900211 PRD

tp import SCMK900211 PRD client100 --- Importing one change request

tp import all PRD client100 --- Importing all change requests

In the SAP System, there are 2 background events that are triggered by tp at

the beginning and/or end of an import with tp import all and with tp put:

SAP_IMPORT_START , SAP_IMPORT_STOP

Imports are normally not performed by the developer who requested an export, but by the system administrator.For import the administrator must log onto the operating system of a host in the target

system as the user <sapsid>adm .

we can start a complete import with the following command:

cd \usr\sap\trans\bin

tp addtobuffer SCMK900211 PRD

tp import SCMK900211 PRD client100 --- Importing one change request

tp import all PRD client100 --- Importing all change requests

In the SAP System, there are 2 background events that are triggered by tp at

the beginning and/or end of an import with tp import all and with tp put:

SAP_IMPORT_START , SAP_IMPORT_STOP

The Route of a Request into the Target System

The transport of a request begins when the owner of the request releases itThe transport of a request begins when the owner of the request releases it

After released , it is unlocked and the data is exported to OS level After released , it is unlocked and the data is exported to OS level

tp registers that the request has to be imported into the target system. tp registers that the request has to be imported into the target system.

Perform import to the target system using the STMS which calls tpPerform import to the target system using the STMS which calls tp

1.1.

2.2.

3.3.

4.4.

The object will transferred to target system The object will transferred to target system 7.7.

Configure Transport Management System

Before starting work with the Transport Management System (TMS), We must configure it in all SAP Systems in system landscape.

In Configuring the transport domain we define which SAP systems in system landscape form a transport domain, and which SAP system is to be the transport domain controller.

In Configuring the transport routes the transport routes are used to define in which target system we want to consolidate change requests, and which SAP Systems are forwarded this information automatically.

In transport domain, the SAP System that is configured as the domain controller is of special significance. If this SAP System fails, we cannot make changes to the TMS configuration during this time. Therefore if transport domain contains more than three SAP Systems, SAP recommend configuring a backup domain controller.If domain controller fails, the backup controller can assume the function of the domain controller.

Before starting work with the Transport Management System (TMS), We must configure it in all SAP Systems in system landscape.

In Configuring the transport domain we define which SAP systems in system landscape form a transport domain, and which SAP system is to be the transport domain controller.

In Configuring the transport routes the transport routes are used to define in which target system we want to consolidate change requests, and which SAP Systems are forwarded this information automatically.

In transport domain, the SAP System that is configured as the domain controller is of special significance. If this SAP System fails, we cannot make changes to the TMS configuration during this time. Therefore if transport domain contains more than three SAP Systems, SAP recommend configuring a backup domain controller.If domain controller fails, the backup controller can assume the function of the domain controller.

Configuring the Transport Domain(1)

To configure and maintain the transport domain we need the authorization S_CTS_CONFIG contained in the profile S_A.SYSTEM.

First, we must decide which SAP System we want to configure as the transport domain controller

We can only carry out all the activities relevant to the entire transport domain, such as configuring transport routes or configuring RFC connections, in the domain controller.

The transport domain controller should normally be configured in a production system or quality assurance system.

To configure and maintain the transport domain we need the authorization S_CTS_CONFIG contained in the profile S_A.SYSTEM.

First, we must decide which SAP System we want to configure as the transport domain controller

We can only carry out all the activities relevant to the entire transport domain, such as configuring transport routes or configuring RFC connections, in the domain controller.

The transport domain controller should normally be configured in a production system or quality assurance system.

Configuring the Transport Domain(2)

1. Log on in client 000 in the SAP System that we want to configure as the transport domain controller.

2. Enter Transaction STMS. The dialog box TMS: Configure Transport Domain appears.

3. Enter the name and a short description of the transport domain.

4. Save your entries. The following actions are performed automatically in

SAP System: The user TMSADM is created. The RFC destinations required for the TMS are generated. The TMS configuration is stored in the transport directory. The transport profile for the transport control program tp is

generated. The SAP System is configured as a single system

1. Log on in client 000 in the SAP System that we want to configure as the transport domain controller.

2. Enter Transaction STMS. The dialog box TMS: Configure Transport Domain appears.

3. Enter the name and a short description of the transport domain.

4. Save your entries. The following actions are performed automatically in

SAP System: The user TMSADM is created. The RFC destinations required for the TMS are generated. The TMS configuration is stored in the transport directory. The transport profile for the transport control program tp is

generated. The SAP System is configured as a single system

Configuring Virtual SAP Systems

We may not want to install all the SAP Systems we have planned for system landscape at the same time. However, we can use TMS to configure SAP Systems as virtual systems in the transport domain so that we can model the transport routes of our whole system landscape.

To configure a virtual system:

1. Log on to the SAP system (In transport domain controller)2. Call Transaction STMS.3. Choose Overview Systems. The system overview appears.4. Choose SAP System Create Virtual system. The dialog box TMS: Configure Virtual System appears.5. Enter the name and a short description of the SAP System. The domain controller is proposed as the communications system. The communications system is required to act as a substitute for accessing the transport directory.6. Save entries and confirm that we want to distribute the configuration change to all real SAP Systems.

We may not want to install all the SAP Systems we have planned for system landscape at the same time. However, we can use TMS to configure SAP Systems as virtual systems in the transport domain so that we can model the transport routes of our whole system landscape.

To configure a virtual system:

1. Log on to the SAP system (In transport domain controller)2. Call Transaction STMS.3. Choose Overview Systems. The system overview appears.4. Choose SAP System Create Virtual system. The dialog box TMS: Configure Virtual System appears.5. Enter the name and a short description of the SAP System. The domain controller is proposed as the communications system. The communications system is required to act as a substitute for accessing the transport directory.6. Save entries and confirm that we want to distribute the configuration change to all real SAP Systems.

Configuring the Transport Control Program tp

The transport control program tp requires a transport profile that contains information about establishing the database connection for all SAP Systems in the transport domain. TMS generates and manages this transport profile as a part of the transport domain configuration.

Must enter the necessary profile parameters for this SAP System in the transport profile TPPARAM using a text editor.

The transport control program tp requires a transport profile that contains information about establishing the database connection for all SAP Systems in the transport domain. TMS generates and manages this transport profile as a part of the transport domain configuration.

Must enter the necessary profile parameters for this SAP System in the transport profile TPPARAM using a text editor.

tp / r3trans /tpparam (1)

Transport Control Program tp

Transport control program tp is an utility to transports objects between the sap system & Upgrading the sap release. tp is called by the other programs

Change & Transport System (CTS) Transport Management System (TMS) Upgrade control program R3up (Upgrade control program)

R3trans Program

This sap program uses to transport data between the sap systems & the migration between the different sap release.Mainly R3trans is called by the programs tp & r3up

Transport profile (tpparam)

This is a global parameter file used by tp & administrated by SAP TMS .

For each transport group there are one transport profile .The transport profile contains the settings needed to configure the transport control program tp & transport program r3trans .

Transport profile file stores in the directory sapmnt/trans/bin directory with names TP_DOMAIN_SCM.PFL. .

The line in this file preceded by # is a comment line .

Transport Control Program tp

Transport control program tp is an utility to transports objects between the sap system & Upgrading the sap release. tp is called by the other programs

Change & Transport System (CTS) Transport Management System (TMS) Upgrade control program R3up (Upgrade control program)

R3trans Program

This sap program uses to transport data between the sap systems & the migration between the different sap release.Mainly R3trans is called by the programs tp & r3up

Transport profile (tpparam)

This is a global parameter file used by tp & administrated by SAP TMS .

For each transport group there are one transport profile .The transport profile contains the settings needed to configure the transport control program tp & transport program r3trans .

Transport profile file stores in the directory sapmnt/trans/bin directory with names TP_DOMAIN_SCM.PFL. .

The line in this file preceded by # is a comment line .

tp / r3trans /tpparam (2)

In time of setting up transport profile the file TPPARAM.TPL copy to subdirectory \usr\sap\trans\bin directory as a file name tpparam .

All SAP Systems should have unique names. Transport only possible between SAP systems that have different names.

If we have several SAP Systems with the same names, transporting is impossible because the target system of a transport is not unique.

Do not use any of the following names as the system name:

ADD, ALL, AND, ANY, ASC, COM, DBA, END, EPS, FOR, GID, INT, KEY, LOG, MON, NOT, OFF, RAW, ROW, SAP, SET, SGA, SH0, SID, UID, VAR

Transport profile parameters :

SID /DBHOST = scma (hostname of the database server )

SID /DBNAME = SCM (name of the database instance)

SID /DBTYPE = ora (database type)

SID /TP_VERSION = 266 (tp version )

TRANSDIR = \\scma\sapmnt\trans (path of the transport directory on network )

In time of setting up transport profile the file TPPARAM.TPL copy to subdirectory \usr\sap\trans\bin directory as a file name tpparam .

All SAP Systems should have unique names. Transport only possible between SAP systems that have different names.

If we have several SAP Systems with the same names, transporting is impossible because the target system of a transport is not unique.

Do not use any of the following names as the system name:

ADD, ALL, AND, ANY, ASC, COM, DBA, END, EPS, FOR, GID, INT, KEY, LOG, MON, NOT, OFF, RAW, ROW, SAP, SET, SGA, SH0, SID, UID, VAR

Transport profile parameters :

SID /DBHOST = scma (hostname of the database server )

SID /DBNAME = SCM (name of the database instance)

SID /DBTYPE = ora (database type)

SID /TP_VERSION = 266 (tp version )

TRANSDIR = \\scma\sapmnt\trans (path of the transport directory on network )

tp Commands(1) tp connect <sapsid>This informs connection with the SID system is successful or not .It logs on to database & then logs off (If successful then TMS will work) .tp addtobuffer <request> <sapsid>This adds the transport request to the buffer of the <SID>system. & places it as the last request to be imported.If it is already in the buffer ,modifies the order& places at last .tp showbuffer <sapsid>This displays the transportable change requests ready for import to the <sid>tp cleanbuffer <sapsid>This deletes successfully imported change requests from the list of requests that are marked for import into the SAP System <SAPSID>.tp count <sapsid>This displays the number of requests in the <sid> buffer waiting for importtp delfrombuffer <request> <sapsid>If the specified request is marked for import into the specified SAP System, this flag isdeleted from the import list.tp locksys <sapsid>The specified SAP System is locked to prevent users other than SAP* and DDIC fromlogging on. When a user other than SAP* or DDIC tries to log on to the system, themessage Logon not possible, put in progress appears.tp unlocksys <sapsid>The lock set by the command tp locksys <sapsid> is deleted.

tp connect <sapsid>This informs connection with the SID system is successful or not .It logs on to database & then logs off (If successful then TMS will work) .tp addtobuffer <request> <sapsid>This adds the transport request to the buffer of the <SID>system. & places it as the last request to be imported.If it is already in the buffer ,modifies the order& places at last .tp showbuffer <sapsid>This displays the transportable change requests ready for import to the <sid>tp cleanbuffer <sapsid>This deletes successfully imported change requests from the list of requests that are marked for import into the SAP System <SAPSID>.tp count <sapsid>This displays the number of requests in the <sid> buffer waiting for importtp delfrombuffer <request> <sapsid>If the specified request is marked for import into the specified SAP System, this flag isdeleted from the import list.tp locksys <sapsid>The specified SAP System is locked to prevent users other than SAP* and DDIC fromlogging on. When a user other than SAP* or DDIC tries to log on to the system, themessage Logon not possible, put in progress appears.tp unlocksys <sapsid>The lock set by the command tp locksys <sapsid> is deleted.

tp Commands(2)

tp/ R3trans Return Codes

R3trans sets a return code that shows whether or not the transport has succeeded. 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.

tp/ R3trans Return Codes

R3trans sets a return code that shows whether or not the transport has succeeded. 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.

Maintaining and Monitoring the Transport Domain

Once we have configured the transport domain controller and included SAP Systems in the transport domain, there will be situations in which the configuration of the transport domain has to be adjusted. We must change the configuration, for example when:

An SAP System moves to another host

A virtual system is replaced with a real system

An SAP System is deleted from the transport domain

An SAP System is linked to another transport directory

The settings for the transport control program have to be changed

Once we have configured the transport domain controller and included SAP Systems in the transport domain, there will be situations in which the configuration of the transport domain has to be adjusted. We must change the configuration, for example when:

An SAP System moves to another host

A virtual system is replaced with a real system

An SAP System is deleted from the transport domain

An SAP System is linked to another transport directory

The settings for the transport control program have to be changed

Configuring the Backup Domain Controller

The SAP System that we want to use as the backup controller must have the same release version as the domain controller. Otherwise, configuration information may be lost when changing the transport domain controller.

To configure a backup domain controller:

1. Log on to the SAP System functioning as the transport domain controller.

2. Enter Transaction STMS.3. Choose Overview Systems. The system overview appears.4. Position the cursor on the domain controller.5. Choose SAP System Change. The brings you to the screen

Change TMS Configuration: System <SID>.6. In the field Backup, enter the SAP System you want to use as the

backup controller of your transport domain.7. Save your entries and distribute the configuration change.

The SAP System that we want to use as the backup controller must have the same release version as the domain controller. Otherwise, configuration information may be lost when changing the transport domain controller.

To configure a backup domain controller:

1. Log on to the SAP System functioning as the transport domain controller.

2. Enter Transaction STMS.3. Choose Overview Systems. The system overview appears.4. Position the cursor on the domain controller.5. Choose SAP System Change. The brings you to the screen

Change TMS Configuration: System <SID>.6. In the field Backup, enter the SAP System you want to use as the

backup controller of your transport domain.7. Save your entries and distribute the configuration change.

Activating the Backup Domain Controller

If domain controller failed and we have to make changes to the TMS configuration, we can activate the backup controller.

To activate the backup domain controller:1. Log on to the SAP System functioning as the backup domain controller.2. Enter Transaction STMS.3. Choose Overview Systems. The system overview appears.4. Choose Extras Activate backup controller.5. Confirm the prompt.

If domain controller failed and we have to make changes to the TMS configuration, we can activate the backup controller.

To activate the backup domain controller:1. Log on to the SAP System functioning as the backup domain controller.2. Enter Transaction STMS.3. Choose Overview Systems. The system overview appears.4. Choose Extras Activate backup controller.5. Confirm the prompt.

Configuring Transport Routes

Before configure the transport routes, the following prerequisites must be met:

The transport domain has been configuredAll SAP Systems involved were included in the transport domain.

The configuration of the transport routes is managed in the SAP System that serves as the transport domain controller and can be distributed to and activated in all other connected SAP Systems in the transport domain.

The transport route configuration consists of:System attributesConsolidation routesDelivery routes

SAP provides two editors for configuring transport routes:Graphical editorThe SAP Systems and their transport routes are displayed graphically.You can position and link the SAP Systems together by clicking and holding the mouse.Hierarchical list editorThe SAP Systems and their transport routes are displayed in a tree structure.

Before configure the transport routes, the following prerequisites must be met:

The transport domain has been configuredAll SAP Systems involved were included in the transport domain.

The configuration of the transport routes is managed in the SAP System that serves as the transport domain controller and can be distributed to and activated in all other connected SAP Systems in the transport domain.

The transport route configuration consists of:System attributesConsolidation routesDelivery routes

SAP provides two editors for configuring transport routes:Graphical editorThe SAP Systems and their transport routes are displayed graphically.You can position and link the SAP Systems together by clicking and holding the mouse.Hierarchical list editorThe SAP Systems and their transport routes are displayed in a tree structure.

Maintain Transport Management system(1)

We can maintain transport management system using STMSWe can maintain transport management system using STMS

We can add another system using this option

We can add another system using this option

Maintain Systems to a transport domain (1)

Choose SYSTEM or SHIFT F6 then we get the screen .Choose SYSTEM or SHIFT F6 then we get the screen .

The list of systems connected with the Transport Domain

The list of systems connected with the Transport Domain

We choose this option to create a virtual System

We choose this option to create a virtual System

Specify the virtual system name as DEV

Specify the virtual system name as DEV

Maintain Systems to a transport domain(2)

System DEV attached to the system listSystem DEV attached to the system list

Newly created system DEV attached already

Newly created system DEV attached already

Maintain Transport Route to a Transport Domain(1)

We can maintain transport management system using STMSWe can maintain transport management system using STMS

We can add another Transport Route using this option

We can add another Transport Route using this option


We can maintain(add/change) Transport Layer from this screenWe can maintain(add/change) Transport Layer from this screen

Choose display/Change to edit/change the transport routes

Choose display/Change to edit/change the transport routes

Choose to create new Transport Layer

Choose to create new Transport Layer

Give name ZDEV of the new Transport Layer

Give name ZDEV of the new Transport Layer


Then the newly created transport layer added to the systemThen the newly created transport layer added to the system

Transport layer ZDEV added to the system

Transport layer ZDEV added to the system

Used this option to create a new transport route

Used this option to create a new transport route

Specify the systems & transport layers

Specify the systems & transport layers


Transport route ZDEV added for the system DEV

Transport route ZDEV added for the system DEV


Graphical Presentation of the Transport DomainGraphical Presentation of the Transport Domain

IMPORTANT TRANSACTION CODES FOR TMS:

STMS Initial screen of the Transport Management System

STMS_QUEUES Displays the import queue

STMS_IMPORT Import queue of the current SAP System

STMS_PATH TMS transport routes

STMS_DOM TMS system overview

SE01 Transport Organizer (Extended)

SE09 ,SE10 Transport Organizer

Create Change Request(1)

We can create Change Request of a role using PFCG to transporting one role to another server .

We can create Change Request of a role using PFCG to transporting one role to another server .

Double click to make change request

Double click to make change request

Click hereClick here

Create Change Request(2)

We can create a new Change Request or assign to old Change Request .

We can create a new Change Request or assign to old Change Request .

Create a request click here.

Create a request click here.

Enter DESCRIPTION & target SERVER

Enter DESCRIPTION & target SERVER

New Change request will be generated

New Change request will be generated

Check Change Request(1)

Now we can check the change request using the TC SE01Now we can check the change request using the TC SE01

Click hereClick here

This message confirms the creation of change request

This message confirms the creation of change request


Now we can check the change request using the TC SE01Enter the change request SCMK900314

Now we can check the change request using the TC SE01Enter the change request SCMK900314

After entering the change request ,use Display Button

After entering the change request ,use Display Button

Enter the change request

Enter the change request


We get the details of the change requestWe get the details of the change request

Type of the Change request

Type of the Change request

Customizing task corresponding to the CR

Customizing task corresponding to the CR

ADD a new TASK to a Change Request(1)

To create new task for another user to a change request press F7To create new task for another user to a change request press F7

Press F7 to add new task for a new user

Press F7 to add new task for a new user

Enter user name to attach a new task

Enter user name to attach a new task


New task created with the name of user , TEST-USER1New task created with the name of user , TEST-USER1

New task created on a same change requestWith name SCMK900327



Now Login as a TEST-USER1 Now Login as a TEST-USER1



ADD a new object to a change Request(1)Now Login as a TEST-USER1 Now assign one role-object Z_PFCG to the previously created task SCMK900327 which belongs to the task SCMK900314

Now Login as a TEST-USER1 Now assign one role-object Z_PFCG to the previously created task SCMK900327 which belongs to the task SCMK900314

Now transport the roleNow transport the role

Now attach the change request SCMK900314

Now attach the change request SCMK900314

ADD a new object to a Change Request(2)

We get the message of confirmation

We get the message of confirmation

ADD a new object to a Change Request (3)

Now Login as a SAPBASIS .Use transaction code SE01, we get the following screen .

Now Login as a SAPBASIS .Use transaction code SE01, we get the following screen .

We select the change request SCMK900314

We select the change request SCMK900314

Now use the button DisplayNow use the button Display


Now we get the following screen . Now we get the following screen .

The role object Z_PFCG already attached with the task SCMK900327

The role object Z_PFCG already attached with the task SCMK900327


Now we add another object Z_NEW_AG_SPRO to a task SCMK900327 using the user TEST-USER1 .Login as a TEST-USER1

Now we add another object Z_NEW_AG_SPRO to a task SCMK900327 using the user TEST-USER1 .Login as a TEST-USER1

Now we attach the role object Z_NEW_AG_SPRO to the C.R. SCMK900327

Now we attach the role object Z_NEW_AG_SPRO to the C.R. SCMK900327


Login as a SAPBASISUse the TC SE01 to find the details .

Login as a SAPBASISUse the TC SE01 to find the details .

Two objects attached with the task SCMK900327

Two objects attached with the task SCMK900327

Change the owner of the task in a Change Request (1)

We can change the owner of the change request .We can change the owner of the change request .

By this option we can change the owner of the task

By this option we can change the owner of the task

Change the owner of the task in a Change Request (2)

Then the owner of the task have been changed to SAPBASIS Then the owner of the task have been changed to SAPBASIS

Owner of the task have been changed to SAPBASIS

Owner of the task have been changed to SAPBASIS

Release a Change Request (1)

We have to release the change request after completion the work We have to release the change request after completion the work

To release the task usethis button or F9

To release the task usethis button or F9


Then the owner of the task have been changed to SAPBASIS Then the owner of the task have been changed to SAPBASIS

•SCMK900327 Task released & get the message like this.

•SCMK900327 Task released & get the message like this.

But SCMK900315 not released

But SCMK900315 not released


We get the message in time of release the change request SCMK900314We get the message in time of release the change request SCMK900314

Export is going onExport is going on


We get the message in time of release the change request SCMK900314We get the message in time of release the change request SCMK900314

After releasing two tasks the change request can be release.

After releasing two tasks the change request can be release.

Performing Transports

After you release a change request using the Transport Organizer, the objects in the request are exported from the database and stored in the transport directory. At the same time, the change request is marked for import into the target system by being placed in the import queue of the target system. After the export log has been checked, the developer's or project manager's work is initially finished.The subsequent import into the target system is generally performed by the transport administrator. The import overview (STMS →Overview →Imports) provides you with the following information on all SAP Systems in the transport domain:Number of requests ready for importStatus of the import queueFor performance reasons, the data required for this is only read from thetransport directory the first time the TMS is called. After that, information buffered in the database is always shown. The time stamp in the import overview indicates how current the displayed information is. To refresh the buffered information,choose Edit →Refresh.If an SAP System is locked for TMS, this system is not displayed in the import overview.

After you release a change request using the Transport Organizer, the objects in the request are exported from the database and stored in the transport directory. At the same time, the change request is marked for import into the target system by being placed in the import queue of the target system. After the export log has been checked, the developer's or project manager's work is initially finished.The subsequent import into the target system is generally performed by the transport administrator. The import overview (STMS →Overview →Imports) provides you with the following information on all SAP Systems in the transport domain:Number of requests ready for importStatus of the import queueFor performance reasons, the data required for this is only read from thetransport directory the first time the TMS is called. After that, information buffered in the database is always shown. The time stamp in the import overview indicates how current the displayed information is. To refresh the buffered information,choose Edit →Refresh.If an SAP System is locked for TMS, this system is not displayed in the import overview.

Starting an Import: Options

All the options for starting an import in TMS are listed here. The options you have depend on which import type you have chosen (project or individual import, import all requests, transport workflow).

Select all requests for later importThe requests remain in the import queue after the import and can be imported, for example, into another client. This is only useful if you have not switched on extended transport control, but you want to provide several clients with requests.

Leave transport request in queue for later importThis causes these requests to be imported again in the correct order with the next import of all the requests. This option is useful if you have to make preliminary imports for individual requests. This prevents older objects from being imported at the next regular import of all the requests The option Leave transport request in queue for later import is activated as a default only for Customizing requests and transportable change requests.

Import transport requests againThe transport control program also imports the transport request if it already has been completely imported.

All the options for starting an import in TMS are listed here. The options you have depend on which import type you have chosen (project or individual import, import all requests, transport workflow).

Select all requests for later importThe requests remain in the import queue after the import and can be imported, for example, into another client. This is only useful if you have not switched on extended transport control, but you want to provide several clients with requests.

Leave transport request in queue for later importThis causes these requests to be imported again in the correct order with the next import of all the requests. This option is useful if you have to make preliminary imports for individual requests. This prevents older objects from being imported at the next regular import of all the requests The option Leave transport request in queue for later import is activated as a default only for Customizing requests and transportable change requests.

Import transport requests againThe transport control program also imports the transport request if it already has been completely imported.

Starting an Import: Options

Overwrite originalsThe transport control program also imports objects if the objects are the originals in the target system. The object directory entry determines the SAP System where the original version of an object is located.

- Overwrite objects in unconfirmed repairsThe transport control program also imports objects if they were repaired in the target system and the repair is not yet confirmed.

Ignore unpermitted transport typeThe transport control program imports the transport request if this transport type was excluded by particular settings in the transport profile.

Ignore predecessor relationsYou can choose this option if you want to import all the requests for one or several projects, but additional requests from other projects exist for which there are dependencies. This option is switched off by default, which means the predecessor's relationships are checked before the import. The import only occurs if the predecessor's relationships will not be damaged.overview.

Overwrite originalsThe transport control program also imports objects if the objects are the originals in the target system. The object directory entry determines the SAP System where the original version of an object is located.

- Overwrite objects in unconfirmed repairsThe transport control program also imports objects if they were repaired in the target system and the repair is not yet confirmed.

Ignore unpermitted transport typeThe transport control program imports the transport request if this transport type was excluded by particular settings in the transport profile.

Ignore predecessor relationsYou can choose this option if you want to import all the requests for one or several projects, but additional requests from other projects exist for which there are dependencies. This option is switched off by default, which means the predecessor's relationships are checked before the import. The import only occurs if the predecessor's relationships will not be damaged.overview.

Troubleshooting

You can use the following tools for making checks and diagnoses in the Transport Management System:

-- CCMS Alert MonitorAlert Viewer Import History-- SAP Online Help Export History TMS Job Monitor Check RFC Connections Check the Transport Directory Check the Transport Control Program Check the Import Queue for Consistency Display the tp System Log Delete Requests from the QA Worklist Activate Inactive Requests

You can use the following tools for making checks and diagnoses in the Transport Management System:

-- CCMS Alert MonitorAlert Viewer Import History-- SAP Online Help Export History TMS Job Monitor Check RFC Connections Check the Transport Directory Check the Transport Control Program Check the Import Queue for Consistency Display the tp System Log Delete Requests from the QA Worklist Activate Inactive Requests

STMS

Documents

Transcript of STMS