ADM325 Unit 2–Setting up an SAP System Landscape (ABAP) rodapé 2011

PROCEDURES : Summary of Online Documentation : http://help.sap.com

-> SAP NetWeaver -> SAP NetWeaver 7.0 (2004s) -> Enhancement Package1- SAP NetWeaver Library -> SAP
NetWeaver by Key Capability -> Solution Lifecycle Management by Key Capability -> Software Lifecycle Management
-> Software Logistics -> Change and Transport System -> Transport Management System -> Configuring TMS

Unit 2: Setting up an SAP System Landscape

1- Preparation: Delete TMS configuration

- DEV , Client 000, user like DDIC
- STMS -> Overview -> Transport routes -> Display/Change
- Click on each route and -> Delete -> Delete selected link
- Configuration -> Distribute and activate
- Environment -> System overview -> click on virtual systems and QAS -> SAP System -> Delete
- Box: Delete system. Delete system from transport domain? -> Yes
- Extras -> Delete TMS configuration -> message: Do you really want to delete TMS configuration for
DOMAIN_DEV ? -> Yes
 The RFC connections generated by TMS are deleted.
 User TMSADM is not deleted.
 Transport requests or transport objects are not deleted.
 The transport route configuration is deactivated, but not deleted. (After TMS is reconfigured, you can reactivate
and distribute the old transport route configuration.)
 The settings from the transport profile are deleted for systems deleted from the transport domain. After the
deletion in this system, you cannot release or import any transport requests in this system.
- Again, the same procedure for QAS
- On PcAnywhere, log on operating system and remove .CFG and .PFL files on usr/sap/trans/bin

2- Initializing the Transport Domain Controller (figure 20) :

- DEV , Client 000, user like DDIC
- STMS, box: Configure Transport Domain
- Description, domain name: DOMAIN_<SID> -> Save
- STMS, message: You are logged on to the domain controller
- SU01: display user TMSADM
- SM59 : display RFC destinations [email protected]_DEV
- AL11 : display usr/sap/trans/bin files .CFG and .PFL

3- Requesting inclusion from an SAP system within the same transport group (figure 21) :
- QAS, Client 000, user like DDIC
- STMS, box: Include System in Transport Domain
- Description -> Save
- Message : SAP system is waiting for inclusion in transport domain
- SU01: display user TMSADM
- SM59: display RFC destination [email protected]_DEV

4- Requesting inclusion from an SAP system in a different Transport Group (after figure 21) :
- QAS, Client 000, user like DDIC
- STMS, box: Configure Transport Domain
- -> Other configuration
- box: Include System in Transport Domain
- Description, target host, system number -> Save
- Message : SAP system is waiting for inclusion in transport domain
- SU01: display user TMSADM
- SM59: display RFC destination [email protected]_DEV
- Look at Status icons before and after the acceptance.

5- Acceptance of New Systems into the Transport Domain (after figure 21):
- DEV (domain controler) , user with profile S_A.SYSTEM
- STMS, message: You are logged on to the domain controler
- Overview -> Systems . See the status icon
- Mark QAS: SAP System -> Approve, box: Include system QAS in transport domain? -> Yes
- See status icon Active, message: System QAS was included in the domain
- ATTENTION maybe your system has a bug: System overview -> double click QAS ->Communication ->
Change -> Transport Group -> if blank, inform the same group from DEV (F4)
- The new configuration will be distributed to all systems in the domain
- AL11 : see TP_DOMAIN_DEV.PFL file in usr/sap/trans/bin

1
 - Verify configuration: in System Overview -> Goto -> Transport Groups

6- Creating a Virtual System (after figure 21):

- STMS -> Systems overview -> SAP system -> Create -> Virtual System
- Box: Configure Virtual System: SID, description, communication system
- Save
- Box: Distribute the TMS configuration, message: Should configuration change be distributed immediately? ->
Yes
- Or after: System overview -> Extras -> Distribute and activate configuration

7- Replacing a Virtual System with a Real System :

- STMS -> System Overview -> select the virtual system -> SAP system -> delete (the files in Transport
Directory are not removed)
- Extras -> Distribute and activate configuration
- Procedure 3 or 4- Requesting inclusion from an SAP system (with same SID as virtual)
- Procedure 5- Acceptance of New Systems into the Transport Domain

8- Defining a system as the Backup Domain Controller (figure 23) :

- Log on to Domain Controller -> STMS -> Overview -> Systems
- Choose a real system -> SAP system -> Change
- In tab Communication , field Backup = SID of backup domain controller
- Save and distribute the configuration

- To move the domain controller to the QAS System:

- Log on to QAS -> STMS -> Overview -> Systems
- Choose -> Extras -> Activate Backup Controller

9- Maintaining the Transport Profile (figure 24) :

- Log on to Domain Controller -> STMS -> Overview -> Systems
- Choose the system (double click) -> tab Transport Tool (only parameter values that override the default values)
- Goto -> tp Parameters (all current parameter value settings)
- Display/change in tab Transport Tool
- Ex: insert row, new parameter NO_IMPORT_ALL value 1 -> save -> distribute

10- Configure Transport Route for a Standard Three-system Landscape (figure 26)
- Log on to Domain Controller -> STMS -> Overview -> Transport Routes
- Display/Change
- Configuration -> Standard configuration -> Three systems in a group
- Enter the SIDs , DEV, QAS, PRD -> Save
- Description -> transfer -> Distribute
- See : consolidation route for transport layers Z<SID> and SAP, delivery route

11- Adding a new system to the landscape (Transport Routes) (figure 27)
- Ex: TRN is a new virtual system
- Log on to Domain Controller -> STMS -> Overview -> Transport Routes
- Display/Change
- Edit -> Transport Layer -> Create : ZTRN
- Click on the new system in the node area
- Move your cursor to the Display Area and click once again
- Edit -> Transport route -> Add transport route
- Draw a line from DEV to TRN (example). Select Consolidation, ZTRN -> Transfer
- Edit -> Transport route -> Add transport route
- Draw a line from QAS to TRN (example). Select Delivery -> Transfer
- Save -> Transfer -> Distribute or not the configuration
- See this graphical editor.
- Settings -> Transport route editor -> Choose Hierarchical
- Back, enter again on transport routes. See hierarchical editor.
- Extras -> user settings -> Choose Graphical . Back, enter again on transport routes.

12- Activating the QA Approval Process (figure 29) :

- STMS -> Transport routes -> Display/Change
- Double click system QAS or Select QAS and Edit -> System -> Change
- Tab System Attributes, mark “Delivery after confirmation”
- Click on Procedure -> box Change TMS Approval Procedure. Options to activate: Approved by request owner,
department and system administrator (based on authorizations)
- Transfer, save, distribute and activate

13- Verifying the TMS setup (after figure 29):

- STMS -> Systems overview -> select a system or the whole column:
2
 - SAP System -> Check -> Connection test
- SAP System -> Check -> Transport directory
- SAP System -> Check -> Transport tool

14- Creating Transport Target Groups (figure 31) :

- Make sure transport parameter CTC = 1 in all systems
- Log on to Domain Controller -> STMS -> Overview -> Transport Routes
- Display/Change
- Click on each route from DEV to QAS and -> Delete
- Edit -> Transport target group -> Create
- Name /GRCONS/ and description: Consolidação(grupo)
- Click on Client Assignment
- List of target <SID> and client number (ex: QAS 100, DEV 200)
- Transfer
- Click on Trans.group in Node area -> click on Display area
- Edit -> Transport route -> Add transport route
- Draw a line from Source system DEV to trans.group
- Consolidation: ZDEV and SAP
- Save -> Distribute and activate
- All the transport routes are assigned client specific or not. You cannot have a combination of both.

Unit 3: Creating and Exporting Transport Requests

15- Creating a new change request (figure 52) :
- SE09 or SE10 -> Create
- Type of request: customizing or workbench
- Description
- Project id
- More user Ids
- Save

16- Activating the CTS functionality of a Project (figures 55) :

- SPRO_ADMIN -> Create a project or change an existing project
- If new, write a description and save
- Tab Transport Request -> select Activate CTS functionality
- Continue or enter
- Demo tabs: Scope, Project views,

17- Assigning change requests to a Project (figure 56) :

- SPRO_ADMIN -> change or new project -> tab Transport request, after activating CTS
- Choose Assigned CTS Request
- Choose Create Request and create a new, or choose the Add own request
- If in SE10 , creating a new Change Request, enter the Project Id
- If in SE10, select a Modifiable change request , change mode, tab Properties -> enter the Project ID -> Save

18- Copy based on a Transport Request (figure 60) :

- Log on TEST client (Ex: 200)
- SCC1 -> source client = CUST client (ex:100)
- Enter the task ID , or Request ID (if need all tasks, mark Including Request Subtasks)
- Schedule as background job or Start immediately

19- Releasing a change request Task (figure 61) :

- SE09 or SE10 -> Display-> expand the tree structure
- Cursor on the task -> Release icon

20- Releasing a Change Request (figure 61) :

- SE09 or SE10 -> Display-> expand the tree structure
- All tasks must have previously been released
- Cursor on the change request -> Release icon

21- Configuring a Transport Strategy (figure 97) :

- Prerequisite: you have configured TMS with transport routes between the systems
- STMS -> Transport routes -> Display/Change
- Select QAS system , Edit -> System -> Change
- Tab System Attributes, choose your transport strategy: Queue-controlled transports (mass or single) or
Workflow-controlled transports.
- You must set all systems in a system group either to Queue OR Workflow controlled transports. You can set
mass or single transports for individual systems.
- Transfer , Configuration -> Distribute and activate Martha Soares – maio/2011