What is a System LandscapeTMS(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 o !ects"using the transaction code SCC#TMS(4)

To permit or disallow create or changes to $%& repository o !ects from any client , have to set Client independent o !ect changes"using the transaction code SCC#Change

Request (1)

Types of C'()*+ $+,-+ST

Customizing Change $equest -sed for record only client dependent changes using ./* 0(nd after completion of customizing , the changes can e transport to other r%& system 0 To manage the customizing change request we use transaction code S+12 0 Wor3 ench Change $equest -sed for client independent 4cross-client5 customizing o !ects and all repository o !ects created or maintained through the (6(7 wor3 ench 0 To manage the wor3 ench change request we use transaction code S+28 0 Transporta le Change $equest The change requests which are transported to other $%& systems after release 0 Local Change $equest ( change to an $%& repository o !ect in a development system ut not transporta le to quality or production system will e recorded to a local change $equest 0 Local change request can e released ut not transporta le 0

Change Request (2)

+9ample of a change request : SC/;822<12 The ID number of a change request or tasks begins with the three character system-ID SC/. Followed by K9. Then five digit number 22<12. e!t task will be SC/;822<11 0 .f pro!ect leader assign another user to the change request then another tas3 will create with .= SC/;822<1>0 " change request is a collection of tasks .

Change Request (3)

To release the Change $equest ,each separate tas3 in the change request must e documented ? released separately 0using the utton $eleasing the tas3 SC/;822<1< @ollow the messageComponents 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 re!uests and "epairs -Correction system or #orkbench $rgani%er -Transport System -&evelopment class -Transport layer -System types in the CTS pipeline. -"epository objects -Customi%ing objects -'nix file systems in the transport process -(mportant S)* delivery class and table types and tables in the CTS process -*rograms in the CTS process -+ersion ,anagement -T* and "-trans programRFC

.) transport domain comprises all "/- Systems jointly administrated through the T,S .Transport paths are centrally configured from each "/- System to all other "/Systems .The domain controller defines the reference configuration .)ll other "/- Systems automatically receive copies of the reference configuration .#ithin a transport domain the T,S enables "0C communication between all "/- Systems for example to distribute configuration changes or perform imports. Centralized Configuration Data Domain Controller

Overview of Tas ! Change Re"uest and Repair: T)S12Corrections and repairs are recorded in tasks and transported using the change re!uests. (t can control changes to internal components of the system that includes data dictionary objects )3)*/4 programs screens C') definitions and documentation. The task can register and can keep the documentation of all the changes to the system objects. $nce the objects are locked the system prevents parallel changes to the system objects. 0or 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 re!uest number 5if the recording is on in that client6 whenever a customi%ing change is done or a new object is created with a development class other than 7T,* 5local object development class6. ) task is automatically created under a change re!uest. 'ser has to release the task first to release the change re!uest. The user can be able to create or modify the object only after he or she opened a task. $pening a task registers the change with the system. $nce the user releases a task the objects in task get transferred to the change re!uest. )fter the unit testing in customi%ing master client is completed a task is released to its change re!uest. )fter a task is released it can no longer be modified. (f the user wants to modify the same objects which were included in the released task he has to create a new task.. Exporting change request

This is the physical copying of the recorded o !ects from the data ase of the $%& system to files at the operating system level 0 This files are located in the transport directory0 Aperating system level file ;822<120scmcreated on directory %usr%sap%trans%cofiles ? the file $822<120scmcreated on directory %usr%sap%trans%data? the file SC/+8221#&0SC/created on directory%usr%sap%trans%log 0 The file e9tension will e the source system sid name 0

Transport directory(1):

Transport directory is a file system located on AS level where the o !ects in change requests that

were released and e9ported from that $%& system are physically copied so that they can su sequently e imported to a target $%& system0 %usr%sap%transis the parent transport directory Aften in a system landscape there is only one common transport directory0 (ll $%& systems that share the same transport directory ma3e up a T$()S7A$T *$A-70
.f the transport directory is not shared with other systems ,it is called the 7rivate transportdirectory 0

&8+9)SCommontransport directory*rivatetransport directory *"& Transport :roup ; Transport :roup <

Transport directory(2):
Ane or /any Transport =irectory : The networ3 connection to an $%& system is not fast enough 0 There is no permanent networ3 connection etween the different $%& systems of the system landscape 0 There are security reasons that prevent direct access to an $%& system 4li3e 7$=50 There are different hardware platforms that do not allow a common transport directory0 Common transport directory is standard practice 0 When more than one transport directory ,then manual transfer the operating system level file from server to server0 +very computer of the transport group on which an $%& instance is installed should have write access ? read access to the transport directory0