tadm12_2 en col99 fv part ltr

TADM12_2SAP NetWeaver AS

Implementation & OperationII

SAP NetWeaver

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 99Course Duration: 10 DaysMaterial Number: 50118034

An SAP course - use it to learn, reference it for work

Copyright

Copyright 2013 SAP AG or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Trademarks

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks ofAdobe Systems Incorporated in the United States and other countries.

Apple, App Store, FaceTime, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Citrix, ICA, Program Neighborhood, MetaFrame now XenApp, WinFrame, VideoFrame, andMultiWin are trademarks or registered trademarks of Citrix Systems Inc.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

Edgar Online is a registered trademark of EDGAR Online Inc., an R.R. Donnelley & Sons Company.

Facebook, the Facebook and F logo, FB, Face, Poke, Wall, and 32665 are trademarks of Facebook.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, GoogleMobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater,Google Voice, Google Mail, Gmail, YouTube, Dalvik, and Android are trademarks or registeredtrademarks of Google Inc.

HP is a registered trademark of the Hewlett-Packard Development Company L.P.

HTML, XML, XHTML, and W3C are trademarks, registered trademarks, or claimed as genericterms by the Massachusetts Institute of Technology (MIT), European Research Consortium forInformatics and Mathematics (ERCIM), or Keio University.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, Systemz, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, PowerSystems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter,System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks,OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarksor registered trademarks of IBM Corporation.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registeredtrademarks of Microsoft Corporation.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

IOS is a registered trademark of Cisco Systems Inc.

The Klout name and logos are trademarks of Klout Inc.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Mozilla and Firefox and their logos are registered trademarks of the Mozilla Foundation.

Novell and SUSE Linux Enterprise Server are registered trademarks of Novell Inc.

g201331611117

OpenText is a registered trademark of OpenText Corporation.

Oracle and Java are registered trademarks of Oracle and its affiliates.

QR Code is a registered trademark of Denso Wave Incorporated.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch,BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry AppWorld aretrademarks or registered trademarks of Research in Motion Limited.

SAVO is a registered trademark of The Savo Group Ltd.

The Skype name is a trademark of Skype or related entities.

Twitter and Tweet are trademarks or registered trademarks of Twitter.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

SAP, R/3, ABAP, BAPI, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjectsExplorer, StreamWork, SAP HANA, the Business Objects logo, BusinessObjects, Crystal Reports,Crystal Decisions, Web Intelligence, Xcelsius, Sybase, Adaptive Server, Adaptive Server Enterprise,iAnywhere, Sybase 365, SQL Anywhere, Crossgate, B2B 360 and B2B 360 Services, m@gicEDDY, Ariba, the Ariba logo, Quadrem, b-process, Ariba Discovery, SuccessFactors, Executionis the Difference, BizX Mobile Touchbase, It's time to love work again, SuccessFactors Jam andBadAss SaaS, and other SAP products and services mentioned herein as well as their respectivelogos are trademarks or registered trademarks of SAP AG in Germany or an SAP affiliate company.

All other product and service names mentioned are the trademarks of their respective companies.Data contained in this document serves informational purposes only. National product specificationsmay vary.

Disclaimer

These materials are subject to change without notice. These materials are provided by SAP AG andits affiliated companies (SAP Group) for informational purposes only, without representation orwarranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to thematerials. The only warranties for SAP Group products and services are those that are set forth inthe express warranty statements accompanying such products and services, if any. Nothing hereinshould be construed as constituting an additional warranty.

g201331611117

g201331611117

About This HandbookThis handbook is intended to complement the instructor-led presentation of thiscourse, and serve as a source of reference. It is not suitable for self-study.

Typographic ConventionsAmerican English is the standard used in this handbook. The followingtypographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as wellas menu names, paths, and options.

Also used for cross-references to other documentationboth internal and external.

Example text Emphasized words or phrases in body text, titles ofgraphics, and tables

EXAMPLE TEXT Names of elements in the system. These includereport names, program names, transaction codes, tablenames, and individual key words of a programminglanguage, when surrounded by body text, for exampleSELECT and INCLUDE.

Example text Screen output. This includes file and directory namesand their paths, messages, names of variables andparameters, and passages of the source text of aprogram.

Example text Exact user entry. These are words and characters thatyou enter in the system exactly as they appear in thedocumentation.

Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

2013/Q1 2013 SAP AG or an SAP affiliate company. All rights reserved. v

About This Handbook TADM12_2

Icons in Body TextThe following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructor'spresentation.

vi 2013 SAP AG or an SAP affiliate company.

All rights reserved. 2013/Q1

Contents

Course Overview .......................................................... ixCourse Goals .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixCourse Objectives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Unit 1: Introduction to SAP Software Logistics..................... 1

SAP System Landscape ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Client Concept.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13System and Client Change Options ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Unit 2: Setting Up an SAP System Landscape.................... 29

Setting Up the Transport Management System (TMS) ... . . . . . . . 30Extended Transport Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Unit 3: Creating and Exporting Transport Requests............. 77

Customizing and Customizing Projects .. . . . . . . . . . . . . . . . . . . . . . . . . . . 79Transport Requests for Customizing ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Customizing Procedure ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105Transport Requests for Development .. . . . . . . . . . . . . . . . . . . . . . . . . . . .122Customer Development .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140Modifying SAP Objects.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

Unit 4: Importing Transport Requests ............................. 179

The Transport Process ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181Imports Using TMS ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187QA Approval Procedure and Transport Proposals .. . . . . . . . . . . . .209Import Process ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225Monitoring Tools.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245Cleaning Up the Transport Directory .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .268

Unit 5: Enhanced Change and Transport System (CTS+) .....277

Configuration of Change and Transport System For TransportingNon-ABAP Objects.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278

Transport of non-ABAP Objects.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298

Unit 6: Client Tools ..................................................... 327

Client Copy and Client Transport Tools .. . . . . . . . . . . . . . . . . . . . . . . . . .328Client Compare and Maintenance Tools .. . . . . . . . . . . . . . . . . . . . . . . . .349

2013/Q1 2013 SAP AG or an SAP affiliate company. All rights reserved. vii

Contents TADM12_2

Unit 7: SAP Note Assistant, SAP Support Packages, SAPEnhancement Packages and SAP System Upgrades........... 365

SAP Note Assistant.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367SAP Support Packages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .389SAP Enhancement Packages and SAP System Upgrade ... . .410

Unit 8: Advanced User Administration Topics ................... 429

Introduction to CUA... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .431Setting Up a CUA ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .437User Administration with CUA... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .469Introduction to Directory Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .487Work with Identity Management .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .498Introduction to SAP Governance, Risk, and Compliance (GRC)

10.0 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .512

Glossary................................................................... 533

Index ....................................................................... 541

viii 2013 SAP AG or an SAP affiliate company.


Course OverviewThis course complements the course TADM10 for providing you with all thedatabase- and operating system-independent knowledge for being an SAPTechnology Consultant.

TADM12 is largely independent of the type of operating system and databasetechnology.

Like the other TADM courses, TADM12 comprises several individual courses (orparts thereof), which are arranged here in a way that will enable you to gain theknowledge you require as an SAP Technology Consultant as efficiently as possible.

Week 1 of course TADM12 is based on content taken from the followingcourses:

1. ADM110

2. ADM100

3. ADM102 / ADM103

4. ADM800

In addition there is a part of the first week that is presented only in TADM12 (thispart is not presented in other ADM classes).

Week 2 of course TADM12 is based on content taken from the followingcourses:

1. ADM325

2. ADM102 / ADM103

3. ADM900 / GRC100

Target Audience

This course is intended for the following audiences:

SAP Technology Consultants (Associate Level)

Course Prerequisites

Required Knowledge

Content of the class TADM10

2013/Q1 2013 SAP AG or an SAP affiliate company. All rights reserved. ix

Course Overview TADM12_2

Course GoalsThis course will prepare you to:

Work as an Associate Consultant (Junior Consultant) within the SAPtechnology environment

Install, configure and maintain SAP systems based on SAP NetWeaver ASABAP

Install, configure and maintain SAP systems based on SAP NetWeaver ASJava

Course Objectives

After completing this course, you will be able to:

perform basic tasks within the technology environment of SAP systems

x 2013 SAP AG or an SAP affiliate company.


Unit 1Introduction to SAP Software

Logistics

Unit OverviewIn this unit, you will learn about SAP systems and instances, about the data typesin the database and the client concept. You will also learn about the purpose ofdifferent client roles and different SAP system types in an SAP system landscaperecommended by SAP. Additionally, you will learn about the system and clientchange options. Finally, you will identify the components of the Change andTransport System (CTS).

Unit ObjectivesAfter completing this unit, you will be able to:

Describe SAP systems

Identify the SAP system landscape recommended by SAP

Identify the types of data in an SAP system

Explain the client concept in an SAP system

Describe the system change options in an SAP system

Describe the client change options in an SAP system

Unit ContentsLesson: SAP System Landscape... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Lesson: Client Concept .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Lesson: System and Client Change Options... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2013/Q1 2013 SAP AG or an SAP affiliate company. All rights reserved. 1

Unit 1: Introduction to SAP Software Logistics TADM12_2

Lesson: SAP System Landscape

Lesson OverviewIn this lesson, you will learn about the SAP's product portfolio, SAP BusinessSuite, SAP NetWeaver, SAP systems and instances. You will also identify thecomponents of the SAP system landscape that SAP recommends.

Lesson ObjectivesAfter completing this lesson, you will be able to:



Business ExampleAn SAP system administrator needs to understand the roles of different SAPsystems in the SAP system landscape before deciding how to configure theTransport Management System.

SAP Buisness Suite, SAP ERP, SAP NetWeaver

Figure 1: SAP Business Suite

2 2013 SAP AG or an SAP affiliate company.


TADM12_2 Lesson: SAP System Landscape

As a first step, let's review the SAP product portfolio. SAP ERP is a SAPsolution. SAP offers other SAP solutions for the areas of Customer RelationshipManagement (SAP CRM), Supplier Relationship Management (SAP SRM),Product Lifecycle Management (SAP PLM), and Supply Chain Management (SAPSCM). All these solutions are part of the SAP Business Suite (formerly known asmySAP.com). As a result, a customer with a SAP Business Suite license has alsothe license for the solutions that can be seen as subsets of the SAP Business Suite.

Note: Instead of SAP solution sometimes the term SAP application isbeing used.

Inside the SAP solutionss, SAP offers the SAP components, like SAP ECC, SAPSCM server or others. From a technology point of view, these are the componentsthat a customer installs or upgrades.

Another important product to mention is SAP NetWeaver. It representsthe technology stack provided by SAP to support the SAP Business Suite.Furthermore, SAP NetWeaver and its integration capabilities also allow theintegration of non-SAP products. SAP NetWeaver is delivered with all of theSAP applications. As a result, customers can make use of the SAP NetWeavercomponents for a specific application. SAP NetWeaver is a set of differentcomponents like SAP NetWeaver AS, SAP NetWeaver BW, SAP NetWeaverPortal, SAP NetWeaver PI, SAP NetWeaver MDM and others. These technicalcomponents of SAP NetWeaver can be installed as needed to serve differentrequirements.

The SAP for Industry applications, which are also part of the SAP productportfolio, can be seen as extensions to the SAP Business Suite and its SAPapplications. SAP for Industry applications, which were historically add-onsto one single component called SAP R/3, now provide not just add-ons to SAPcomponents but also preconfigurations and best practices.



Figure 2: Example: Architecture of SAP ERP

As an example of an SAP solution, this figure gives a good overview of the SAPsolution SAP ERP.

Figure 3: Get the 'Numbers' straight: SAP R/3 / ECC Releases




This slide gets rid of the confusion concerning the different SAP R/3, SAP R/3Enterprise, SAP ECC, Extension Set and SAP ERP and SAP Basis, SAP Web AS,SAP NetWeaver AS and SAP NetWeaver releases.

Instead of delivering new full SAP ECC releases, SAP delivers SAP enhancementpackages for SAP ERP. For detailed information on SAP ERP enhancementpackages see SAP Service Marketplace, Quick Link /erp-ehp.

Note: In this course the term enhancement package is abbreviated withEHP.

Hint: There are also SAP enhancement packages for SAP CRM, SAPSCM, SAP SRM. For detailed information on these SAP enhancementpackages see SAP Service Marketplace, Quick Link /crm-ehp, SAPService Marketplace, Quick Link /scm-erp and SAP Service Marketplace,Quick Link /srm-ehp.

SAP Systems, Instances and Servers



Figure 4: Architecture of the SAP Solution Manager 7.1 (AS ABAP+Javawith two Instances)

Hint: The graphic shows the very seldom case of an AS ABAP+Javasystem (dual stack system). SAP recommends: you should not install anduse such an dual stack system - except for an SAP PI and an SAP SolutionManager (as shown in the grafic). Starting from PI 7.30 there is also thepossibility to install PI as AS Java only.

Hint: In some SAP NetWeaver AS Java releases, for example 7.10, 7.11,7.20, 7.30, 7.31 there is no Java dispatcher but instead a Java ICM. Thereis also an AS Java gateway in the AS Java central service instance.

In all AS ABAP releases starting from AS ABAP 7.0 there is thepossibility to install an AS ABAP system with an ABAP central serviceinstance. Starting from AS ABAP 7.31 this is the default with newinstallations.

The Internet Communication Manager (ICM) is the interface to the internet.It can deal with web requests as server and as client. It supports severalprotocols like HTTP, HTTPS and SMTP. The SAP NetWeaver AS can beused as a web server and as a web client.

The ABAP-Dispatcher dispatches requests to the Work Processes. If allwork processes are busy at the moment, the requests are queued in theDispatcher-Queue.

The ABAP Work Processes execute the ABAP coding.

The Message Server exchanges messages and can perform a load balancingin the SAP system.

On the Java-side of the SAP NetWeaver AS there are components like theJava-Dispatcher (or ICM instead in some releases), Server Processes, theSoftware Deployment Manager (SDM) and the Central Services (SCS).

The SAP Java Connector (JCo) provides communication between theABAP-Stack and the Java-Stack of the SAP NetWeaver AS, in bothdirections.

Client requests to the SAP NetWeaver AS Java are handled by the Java Dispatcher.It chooses a free Server Process for serving the request and builds up a connectionbetween the client and the Server Process. The Java Dispatcher works accordingto a 'Round Robin' algorithm.

The Software Deployment Manager (SDM) is the standard tool with which J2EEcomponents are installed on the SAP NetWeaver AS Java.

The Central Services run on one server and forms an own Java instance. It consistof a Message Service and an Enqueue Service and are the basis for communicationand synchronisation for the Java Cluster.




Each instance of a SAP NetWeaver AS ABAP+Java contains the ABAPDispatcher with its Work Processes and the Java Dispatcher with its ServerProcesses. One of the instances is usually installed as an ABAP Central Instance,which means, that the Enqueue Work Process runs here. Alternatively the SAPsystem can be installed without a Central Instance, but with a stand alone EnqueueServer. The applications and data for ABAP and Java both have their owndatabase scheme in one common database.

In the newer releases the term Central Instance was renamed to PrimaryApplication Server and the term Dialog Instance was renamed to AdditionalApplication Server.

Users can log on and communicate with the SAP system either using the SAPGUI or a web client (browser):

Communication using the SAP GUI: users log on using the Message Server(for load balancing) or directly log on to a ABAP Dispatcher. The WorkProcesses execute the requests of the users.

Execution of web requests: web requests are handled by the InternetCommunication Manager (ICM). These HTTP(S) requests can be intendedfor the Internet Communication Framework (ICF), which means that theyare executed by an ABAP Work Process (for example Web Dynpro forABAP or BSP applications).

SAP System Landscape Recommended by SAPFrom now on we focus on the SAP NetWeaver AS ABAP.



Figure 5: Aims of the SAP System Landscape

To maintain data security, you should protect application data by using the clientconcept, which separates data according to clients, and the authorization concept,which separates data within one client according to the users.

In addition, you should strictly separate the environments for development, qualityassurance, and production.

The stability and performance of the production client should not be affected bydevelopment and test activities in the other clients.

Changes to Repository objects are client-independent, and immediately affect thebusiness functions and processes. Therefore, changes have to be tested beforebeing transported to the production system.

If you had only one SAP system, no further development would be possible afterproduction had started. Changes to repository objects could be made only whenproduction operations were stopped for development and testing.

A two system landscape is not optimal because development and quality assurancetesting both take place in the development system.




Figure 6: The SAP-Recommended SAP System Landscape

To ensure smooth production operation, an SAP system landscape should containthe three SAP systems, the standard clients, and any required additional clients.

A three system landscape is recommended and meets the needs of most customers.

Development takes place in the development system. Changed objects are thenreleased to the quality assurance system.

In the quality assurance system, you can test new developments without affectingthe production environment. A quality assurance system enables you to integratedevelopment efforts and to check the validity and consistency of transportedobjects before moving the objects into production.

All objects imported into the quality assurance system should also be delivered toone or more production systems.

The three system landscape is also a basis to apply SAP Support Packages orto perform a release upgrade.

SAP systems in the same SAP system landscape require unique SAP systemnames.



SAP provides the tools required for the creation, documentation, and distributionof changes within a SAP system landscape. To set up the SAP system landscapeso that it supports the management, verification, and testing of all changes:

A single client is recommended for all customizing work. Set client changeoptions appropriately before using your clients.

A single SAP system (the development system) is recommended for alldevelopment work. Set the system change options appropriately.

To create and assign appropriate user authorizations to developers andcustomizers, use the sample profiles included in the SAP system. Theseauthorizations control whether a user can create, modify, or release tasksand transport requests.

Record and document all changes to a client or SAP system.

Figure 7: Change and Transport System (CTS)




The Change and Transport System (CTS), comprising the following tools:

The Change and Transport Organizer (CTO) provides functions fororganizing software development projects. It is designed to support projectsof all sizes, whether they are carried out centrally or in a distributedenvironment.

The Transport Management System (TMS) organizes, monitors, andperforms transports for all SAP systems within a SAP system landscape.In addition, TMS is used to configure and manage the setting up of SAPsystems and transport routes within a SAP system landscape.

The transport tools are executables and programs that communicate with theSAP system, the database, and files generated during the transport process.



Lesson Summary

You should now be able to:





TADM12_2 Lesson: Client Concept

Lesson: Client Concept

Lesson OverviewIn this lesson, you will learn how to identify client roles in the SAP system. Inaddition, you will learn about the concepts of change management within an SAPsystem environment.




Business ExampleAs an SAP system administrator or project team leader, you must monitor softwareconfiguration and program code changes to protect your production system fromincorrect configuration settings or program bugs.

Data in an SAP SystemData in an SAP system can be divided into two categories: client-specific dataand cross-client data.

1. Client-specific data, application, customizing and user master data, whichaffects only one client.

2. Cross-client data, cross-client customizing data and all Repository objects,which affects the whole SAP system environment.



Figure 8: Data Types in an SAP System

The ABAP Dictionary is a data dictionary that is part of the ABAP Repository.

Clients in an SAP SystemA client is a self-contained unit in commercial, organizational, and technicalterms, with its own user master data and set of table key ranges.

Figure 9: Clients in SAP Systems




Data from different clients is kept separate at the kernel level. Open SQLstatements executed by an SAP application use the client number in thewhere-clause. Although a table may contain data from several different clients,the where-clause limits access to particular clients.

The following are client-specific data:

User master data, such as parameters, user groups

Customizing data, such as organizational units, assignments, and documenttypes

Application data, such as business transaction data, and material master data

The SAP client concept can integrate several companies or subsidiaries in a singleclient by using company codes and the SAP authorization concept.

Company codes define the smallest corporate organizational units for which acomplete self-contained set of accounts can be drawn up for external reporting.

The SAP authorization concept enables the parent company to access allsubsidiaries for report purposes, while subsidiary-specific data is protected againstaccess from other subsidiaries through company code definition.

Figure 10: Standard Client Roles

The standard client roles fulfill the optimal minimum requirements of your SAPsystem.



Client CUST, development and customizing, is the central customizing clientwhere complete adaptation of the SAP system to customer-specific needs takesplace. All changes performed in this client are recorded so they can be supplied tothe other clients using the Transport Management System (TMS).

Client QTST, quality assurance, is used to test and verify the new customizingsettings in the application.

Client PROD or production is the client for production activities, that is, whereyour company's business is carried out. Customizing changes imported into thisclient have to be first tested carefully in the QTST client in order to ensure thatproduction operation is free of disruption.

To realize the full benefit of a three-system landscape, every critical client shouldhave a separate SAP system.

Figure 11: Additional Client Roles

Additional clients within a SAP system landscape may include:

1. A sandbox client to experiment with transaction data and settings.

2. A test client to verify customizing changes against sample data in a morestable environment. This can be done by 'copying' customizing settings fromthe customizing client to the sandbox client. This is called a unit test.

3. An end-user training environment.

4. A client that satisfies customer-specific requirements.




Lesson Summary






Lesson: System and Client Change Options

Lesson OverviewIn this lesson, you will learn about the system and client change options of anSAP system.




Business ExampleAs a transport administrator, you need to set the correct system change options foreach SAP system and the correct client change options for all clients.

System Change Options

Figure 12: System Change Options



TADM12_2 Lesson: System and Client Change Options

The system change options define whether or not Repository objects andclient-independent customizing objects are globally modifiable. If they areglobally modifiable, you can specify whether or not each software component andnamespace can be modified.

To reach the system change option use transaction SE06 and choose SystemChange Option. A software component is a set of dedicated development classes.

For the software components, there are four different possible settings:

Modifiable

Restricted modifiability (can only create objects as non-originals)

Not modifiable; enhanceable only (changes not allowed; objects can beenhanced using the Enhancement Framework only)

Not modifiable; not enhanceable (changes and enhancements not allowed)

You can reserve namespaces for software developed by SAP customers andpartners. These namespaces are designed for large-scale customer enhancementsas well as add-ons developed by partners.

The syntax for objects from reserved namespaces is: //. For each SAP system, the customer can define whether or not the objectscontained in the namespaces and name ranges can be changed. To enable you tochange objects, the SAP system must not be globally locked to changes.



Client Change Options

Figure 13: Client Change Options

Client change options that are found in the clients master table T000, can bemaintained by using transaction SCC4.

The two settings that must be maintained to implement controls on where changesare made and enforce the changes being recorded to transport requests are:

Changes and transports for client-specific objects

Cross-client object changes

The following list gives a brief description of what each option allows:

Changes and transports for client-specific objects:

Changes without automatic recording

This flag means that changes in the Customizing settings of theclient are permitted. The changes are not automatically recorded ina transport request.

Customizing settings can be exported from the client by manualcreation of a transport request. A manual transport can be carried out inthe particular transaction (if possible) or manually.

This variant makes sense for pure test, training or demonstration clients.

Automatic recording of changes



as1admHighlight

as1admHighlight


This flag means that changes are permitted in the customizing settingsof the client and all the changes are automatically recorded in atransport request.

It is also possible to export independently of the automatic recordingfrom the client customizing settings by manual creation or recording ofa transport request.

In a productive client, settings that can be maintained as current settingsare excluded from automatic recording; current settings (e.g. exchangerates, posting periods) are maintained without recording the changes.

This variant can be used for customizing clients and productive clients.

No changes allowed

This flag means that changes in the customizing settings of the clientare not permitted.

However, customizing settings can be exported from the client bymanual creation of a transport request.

In a productive client, the customizing settings that can be maintainedas current settings are excluded from the client lock; this means thatcurrent settings (e.g. exchange rates, posting periods) can always bemaintained in the productive client.

This variant can be used for productive clients, demonstration clientsand training clients.

Changes w/o automatic recording, no transports allowed

This flag means that changes are permitted in the customizing settingsof the client. The changes are not automatically recorded in a transportrequest, however.

No manual transport of customizing settings from the client is possible.

This variant can be used for pure test clients.

Cross-client object changes

This feature controls in which clients you are allowed to maintain cross-clientobjects.

It makes sense to disallow cross-client maintenance if the objects to bemaintained in a client are exclusively application objects (all client-specific)or client-related customizing objects. In this case (for example in a testclient), you must be able to ensure that cross-client functionality cannotbe changed.



Cross-client functions include all cross-client customizing objects (e.g.factory calendar, definition of price list conditions, printer controls). But inparticular they also include all objects of the SAP Repository (programs,function modules, screens, dictionary etc.).

Changes to repository and cross-client customizing allowed

There are no restrictions on the maintenance of cross-client objectsfor the client when this setting is used. Both cross-client customizingobjects and objects of the SAP Repository can be maintained.

Use in customizing/development client only

No changes to cross-client customizing objects

Cross-client customizing objects cannot be maintained in the clientwith this setting.

Only use this if development client is separate from customizing client

No changes to repository objects

With this setting, objects of the SAP Repository cannot be maintainedin the client.

Only use this if customizing client is separate from development client.

No changes to repository and cross-client customizing objects

Combination of both restrictions: Neither cross-client customizingobjects nor objects of the SAP Repository can be maintained in theclient.

Use this in every client in the landscape except customizing/developmentclient(s)




Figure 14: Customizing Using Current Settings

In a customizing project and also during the maintenance of a SAP system all thecustomizing changes should be transported and tested in the quality assurancesystem. But certain kinds of customizing changes, so called data-only customizingchanges, need to be carried out in a production client without being saved astransport requests. Examples of such data include interest rates, health insurancepremiums, pension schemes, tax schemes, and currency exchange rates, whichmay require frequent adjustment in SAP systems.

Since these types of changes have a frequent change rate and they are not subject toextensive testing like other customizing changes, these changes are done directlyin the productive client in the productive system. To avoid having to use transportrequests for these changes, SAP has introduced the Current Settings function.

Current Settings may be used within a production client without impactingbusiness flow-related Customizing objects.

SAP-approved Current Settings for customizing objects are kept in the fieldCURSETTING in the table OBJH. SAP recommends that no customer changes bemade to the table.

When using Current Settings in a production environment:

Client role is set to: Production

Cross-client object changes are set to: No changes to Repository andcross-client Customizing objects

Changes and transports for client-specific objects are set to: No changesallowed.



Lesson Summary






TADM12_2 Unit Summary

Unit SummaryYou should now be able to:








Unit Summary TADM12_2



TADM12_2 Test Your Knowledge

Test Your Knowledge

1. List the functions of the Transport Management System (TMS).

2. List examples of client-specific data.

3. List categories in which data in an SAP system can be divided.

4. Define a client in an SAP system.

5. If the system change options are set to not modifiable and in the clientchange options allow the changing of repository objects, you can not changerepository objects from within this client.

Determine whether this statement is true or false.

True

False


as1admHighlight

Test Your Knowledge TADM12_2

Answers

1. List the functions of the Transport Management System (TMS).

Answer: The Transport Management System (TMS) organizes, monitors,and performs transports for all SAP systems within an SAP system landscape.

2. List examples of client-specific data.

Answer: Examples of client-specific data are:

User master data.

Client-specific customizing data such as organizational units,assignments, and document types.

Application data such as business transaction data and material masterdata.

3. List categories in which data in an SAP system can be divided.

Answer: Data in an SAP system can be divided into two categories:client-specific data and cross-client data. Client-specific data, such as usermaster and application data, affects only one client.

Cross-client data, such as cross-client customizing data and all Repositoryobjects, affects the whole SAP system environment.

4. Define a client in an SAP system.

Answer: A client in an SAP system is a self-contained unit in commercial,organizational, and technical terms. A client has its own user master dataand set of table key ranges.

5. If the system change options are set to not modifiable and in the clientchange options allow the changing of repository objects, you can not changerepository objects from within this client.

Answer: True

If the system change options are set to not modifiable and in the clientchange options allow the changing of repository objects, you can not changerepository objects from within this client.



as1admHighlight

as1admHighlight

as1admHighlight

Unit 2Setting Up an SAP System Landscape

Unit OverviewBefore the development or customizing can start, it is necessary to configure theTransport Management System (TMS).

This unit focusses on how to configure the TMS for an SAP system landscape. Inaddition, you will learn about the implementation of Extended Transport Controland the Quality Assurance (QA) approval controls.

Unit ObjectivesAfter completing this unit, you will be able to:

explain the steps for setting up the transport management system (TMS)

configure transport routes

explain the use of transport target groups and client-dependent transportroutes

list the necessary steps to perform transports between different transportgroups and transport domains

Unit ContentsLesson: Setting Up the Transport Management System (TMS) ... . . . . . . . . 30

Exercise 1: Setting Up the Transport Management System (TMS)(verification) .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Lesson: Extended Transport Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63


Unit 2: Setting Up an SAP System Landscape TADM12_2

Lesson: Setting Up the Transport Management System(TMS)

Lesson OverviewIn this lesson, you will learn how to set up the transport management system(TMS). At first some basic terms such as SAP system landscape, transport domainand transport group are introduced. Then you will learn how to set up a transportdomain and how to configure a transport domain controller. After that, transportroutes are defined. Finally the QA approval procedure will be introduced and theTMS setup will be checked.


explain the steps for setting up the transport management system (TMS)

configure transport routes

Business ExampleAn SAP system administrator needs to understand the roles of different SAPsystems and clients in the SAP system landscape before making decisions onhow to configure the Transport Management System (TMS). After you installthe first SAP system but before you perform customizing or development, youneed to configure the TMS so that it will record, track and control customizingand development changes for the subsequent transports to other SAP systemsin the SAP system landscape.



TADM12_2 Lesson: Setting Up the Transport Management System (TMS)

Overview and PrerequisitesThe following list gives an overview of what has to be considered before, duringand after installation of an SAP system.

Before SAP system and database installation:

Define the network structure for the SAP system landscape.

Install the hardware and the operating systems for the SAP systems.

During SAP system and database installation:

Create one common transport directory (in certain cases you want tohave more then one).

After SAP system and database installation:

If you have set up the SAP system using a database copy, initialize theChange and Transport Organizer (CTO) (transaction SE06).

In any case: set up the Transport Management System (TMS).

Hint: If you have set up the SAP system using a database copy, initializethe Change and Transport Organizer (CTO) using transaction SE06,choosing Database Copy or Database Migration and pressing the PerformPost-Installation Actions button.

In any case you have to configure the SAP system landscape using theTMS using transaction STMS. The process of setting up the SAP systemlandscape with transaction STMS will be described in detail in this lesson.

To set up your SAP system landscape, it is sufficient to start with an existingSAP system as a development system; the quality assurance and production SAPsystems are not required at this stage. All future SAP systems can be representedat this stage as virtual systems. You will also have to create a transport directoryat file system level for all SAP systems. This directory is required for the TMS.



Figure 15: Creating a Transport Directory

Depending on your existing SAP system landscape, the global transport directoryand all the necessary subdirectories are created automatically during theinstallation of the SAP system. See the installation guide for your SAP systemfor more details.

The SAP profile parameter DIR_TRANS has to point to the path of the transportdirectory. For Unix, the default path is /usr/sap/trans. For Windows, the defaultpath is \\\sapmnt\trans.




The subdirectories required in the common transport directory include (amongothers):

bin: configuration files for tp (TP_.PFL) and TMS(DOMAIN.CFG).

buffer: transport buffer for the each SAP system, indicating which transportrequests are to be imported.

data: data part of the exported transport requests.

cofiles: command or transport request information files that includeinformation on the transport type, object classes, required import steps, andpost-processing exit codes.

log: transport logs, trace files, and statistics.

tmp: temporary data and log files.

sapnames: information belonging to transport requests per SAP user.

EPS: download directory for SAP Support Packages.

Note: To enable transports in a heterogeneous operating systemenvironment, you must set up different transport directories. However, toenable transports in a heterogeneous operating system environment usinga single transport directory, refer to SAP Note 83327.

Transporting enables you to synchronize customizing and development in multipleSAP systems through the transfer of changes from the development system todownstream SAP systems. Transports along the transport routes must occur inonly one direction.


as1admHighlight


Figure 16: SAP System Landscape Logical and Physical Transport Sequence

As mentioned above, transporting requires a transport directory to enable SAPsystems in the SAP system landscape to store and access various data files,command files, and log files.

Physically, objects in a three-system landscape are transported in three steps:

1. All objects in a (transportable) transport request that are to be released areexported by being copied from the database of the source system tothe transport directory.

2. These objects are imported into the database of the quality assurance system.Here they are tested and validated.

3. After testing and verification, the objects can be imported into the databaseof the productive system.

Note: The terms export and import are meant as copy, not as move,of course. At the end, the objects exist four times: in the database of DEV,QAS and PRD and in the transport directory!

So actually the truck is a very bad visualization: because it does amove! A fax machine would be much better...




TMS: Concepts and TerminologyDepending on the size of an organization and the scope of its SAP implementation,there can be many different individuals responsible for carrying out customizingand development projects. Some will be involved in customizing specificapplication areas, others may be involved in development of new ABAP programs,others in the QA testing and acceptance of changes. There can be hundreds oreven thousands of changes that have to be transported through the SAP systems inthe landscape. The transport of these changes will be done using the functions ofthe TMS (TMS).

The concepts behind TMS are:

Centralized configuration of Change and Transport System (CTS) for allSAP systems

Centralized management of transport requests and especially the importprocess

Transport strategy based on predefined transport routes

The purpose of the TMS, accessed via transaction STMS, is to centrally controlthe propagation of changes through the SAP system landscape based on predefinedpaths. This is designed to ensure the consistency of the SAP repository andthe contents of the customizing tables in all SAP systems in the landscape. Allnecessary activities can be done from within the SAP system (using the SAPauthorization concept) and there is no need to execute scripts at operating systemlevel manually.

With TMS you are able to

Define an SAP system's role within an SAP system landscape or transportdomain

Configure the transport routes using either an editor or delivered standardconfiguration settings

Configure the transport tool program's (tp) parameter profile

Display the import queues of all SAP systems in the transport domain

Define quality assurance / acceptance procedures in the QA system

Schedule the import of transport requests in an import queue

Perform transports between SAP systems without a common transportdirectory

Handle transport proposals of developers

TMS thus enables SAP system administrators to centrally manage the transportconfiguration of multiple SAP systems by defining transport domains, assigningtransport domain controllers and defining transport routes.



Figure 17: What is an SAP System Landscape?

A transport domain consists of all SAP systems that you plan to managecentrally. Within the transport domain, all SAP systems must have uniqueSAP system IDs (SIDs) and only one of these SAP systems is identified as the(transport) domain controller.

The transport domain controller is the SAP system where all TMS configurationsettings are maintained. Any changes to the configuration settings are distributedto all SAP systems in the landscape. This ensures that the TMS configurationsettings are consistent throughout the domain. The transport domain controllerstores the reference configuration and all other SAP systems receive a copy of thereference configuration.

An SAP system landscape is a set of SAP systems that share customizing andrepository objects via transported transport requests. The typical landscapeis made up of, but not limited to, a development, a quality assurance, and aproduction system. In most cases, the SAP system landscape and the transportdomain are made up of the same SAP systems but it is not uncommon to havemultiple landscapes within one transport domain.




Examples of a single transport domain with multiple landscapes are:

A multi-national company may have separate landscapes for each subsidiary.DE1, QA1, and PR1 may be the landscape for the Asian implementation andDE2, QA2, and PR2 may be the landscape for the European implementation.Even though they are separate landscapes, both can still be controlledcentrally in one transport domain.

An SAP customer may have multiple landscapes for different kinds of SAPsystems. DCC, QCC, and PCC may be the landscape for the SAP ECCsystems, while DBW, QBW, and PBW may be the landscape for the SAPBW systems. Again, separate landscapes are controlled centrally using onetransport domain.

A transport domain contains at least one transport group. Very simply, atransport group consists of one or more SAP systems that share a commontransport directory. The following figure shows the relation between a transportdomain and a transport group.

Figure 18: Transport Domain and Transport Group

TMS supports several transport directories within a single transport domain. Thismight be the case e.g. for the multi-national company mentioned above where eachsubsidiary may have its own (local) transport directory. Or think about a transport



domain containing a landscape that has a DEV system with its own transportdirectory and QAS and PRD system sharing a common transport directory, forsecurity reasons. In this case, the domain would consist of two transport groups.

Note: The terms transport domain, domain controller, and transport groupconcern only the SAP systems in the environment. They do not includethe transport relationship between the SAP systems, which is defined bythe transport routes.

Establishing a Transport DomainTo set up the transport domain, first determine which SAP systems should beincluded in the transport domain. The transport domain should contain all SAPsystems in all the SAP system landscapes that will be centrally administeredusing TMS.

Note: Not all SAP systems need to be installed and present when thedomain is first configured but planning what the landscape will look likeis necessary. These future SAP systems can be represented by so calledvirtual systems.

Overview

The configuration of TMS can be broken down into three individual steps.

1. Configuring the transport domain defines which SAP systems will beincluded in the domain.

2. Configuring the transport routes defines the SAP system and client roleswithin the landscape(s).

3. Optional: Configuring the QA procedure defines who is responsible forapproving the acceptance of changes and the promotion of those changes tothe delivery system(s).

The following figure shows the three steps. Note that the first two steps aremandatory for setting up an SAP system landscape whereas the last step (QAprocedure configuration) is optional.




Figure 19: Setting Up the Transport Management System

Initializing the transport domain controller

The first SAP system you configure is automatically selected as the transportdomain controller but you may later switch the role of the domain controller to adifferent SAP system.

Figure 20: Establishing a Transport Domain



Since certain configuration tasks that are relevant to the entire transport domain(e.g. creating transport routes) can only be carried out on the transport domaincontroller, SAP recommends that the SAP system chosen to be the domaincontroller has the following attributes:

High availability

High security precautions

Highest level of maintenance

Therefore, a production system might be the ideal choice to be transport domaincontroller. Since the development system is usually installed before the qualityassurance and production systems, the common practice is configuring thedevelopment system as the transport domain controller and then later movingthe assignment of the transport domain controller to the production system.Another scenario might be to use an SAP system that you use already for centralmonitoring and/or central user administration as transport domain controller.

Note: The system load on the SAP system caused by work on thetransport domain controller is very low.

When using TMS for the first time after SAP system installation, you areautomatically prompted to initialize the TMS. You must initialize the TMSwhile logged on to client 000. For configuring TMS you need the authorizationS_CTS_ADMIN.

Transaction STMS in client 000 will:

Assign the SAP system as the transport domain controller

Create transport domain name DOMAIN_

Create transport group GROUP_

Create system user TMSADM in client 000

Create RFC destinations

Set up file DOMAIN.CFG and TP_.PFL in directorybin of the transport directory




When you initialize the TMS, the following actions will automatically be carriedout by the SAP system:

A transport group is created with the name GROUP_.

In client 000, the system user TMSADM is created.

The RFC destinations required for the TMS are generated.

The TMS configuration file DOMAIN.CFG is stored in the transportsubdirectory bin. This file contains the transport domain name anddescription as well as the transport domain controller's host name, instancenumber, SID, and transport group.

The transport profile for the transport control program tp is generatedand stored in the transport subdirectory bin under the name TP_.PFL. The parameters in this profile are maintained using thetransaction STMS.

Note: The name of the transport domain may not contain blanks and maynot be changed afterwards without reconfiguring the domain controller.By default, a transport domain will have the name DOMAIN_,where is the SAP system ID of the domain controller.

Adding additional SAP systems to a transport domain

To add new SAP systems to an existing transport domain, you must performconfiguration activities on both the new SAP system and the transport domaincontroller.

Figure 21: Adding Additional SAP Systems to a Transport Domain



Each additional SAP system must apply for inclusion to the transport domaincontroller. Since configuration of the TMS can only be done on the transportdomain controller, the transport domain controller then must confirm inclusionfor each SAP system. The initial screen of transaction STMS indicates if an SAPsystem is waiting for inclusion in the transport domain.

The description of the transport domain is stored in the file DOMAIN.CFG inthe bin subdirectory of the common transport directory. All other SAP systemsconnected to this transport directory read the file DOMAIN.CFG during STMSinitialization to identify the domain controller and transport group address. Ifyour SAP systems do not have a common transport directory, you can manuallyconfigure TMS with the address of the domain controller. In this case chooseOther configuration Include system in domain when entering transaction STMSfor the first time. In the next popup, enter the target host and the instance numberof the transport domain controller. In any case, when an SAP system has beenconfigured for the TMS and approved in the domain, you will find a newly createduser TMSADM and generated RFC destinations required for the TMS.

Hint: When configuring the TMS on an SAP system, you can specify theapplication server (i.e. the instance) to be used for all TMS functions.Choose the instance with the highest availability. This is generally theinstance that provides the enqueue service, the primary application server(formerly known as central instance).

Caution: In order to exchange data and objects between the SAP systemsof an SAP system landscape all SAP systems should have the same release,SAP Support Package level and correction level. For more information ontransporting between different releases, see SAP Note 1090842.

Figure 22: Centralized Configuration Data




The SAP systems within a transport domain communicate with each other usingRemote Function Calls (RFCs). RFC communication requires user IDs to accesstarget SAP systems. When SAP systems are added to a transport domain, thenecessary RFC destinations and user IDs are automatically configured by the TMStool. The transport domain configuration settings are distributed throughout thetransport domain using RFC communication.

Changes to the transport domain configuration are made in the transport domaincontroller, and then distributed to all SAP systems in the transport domain. Eachtime you make a change to the transport domain controller, a dialog box isdisplayed asking whether to distribute the change. You can distribute severalchanges in one distribution process.

When SAP systems are initially added to the TMS configuration, thecommunication user TMSADM is configured with limited authorizations. Thisuser is utilized when distributing and activating the TMS configurations.

There are two types of RFC destinations created by the TMS:

TMSADM@.

TMSSUP@..

The user TMSADM is inserted as system user into the TMSADM@. destination but there is no RFC user inserted into theTMSSUP@. destination. Therefore, if you try to execute afunction that goes beyond the limited authorizations of the TMSADM user, forexample, scheduling an import, TMS uses the TMSSUP destination. As a result,the SAP system prompts you for a user name and password on the target SAPsystem that does have the necessary authorizations.

Virtual SAP Systems

Extending a transport domain is not restricted to physically installed SAP systems.Virtual SAP systems are often included as place holders for planned SAP systemsand are replaced by the planned SAP system after it is physically installed. Inaddition, you can extend the transport domain to include external SAP systems,for example, an SAP system from a different transport domain.

By creating virtual SAP systems, you can model the transport routes of theplanned SAP system landscape and ensure that the import queues of subsequentSAP systems will already be created and maintained for later use. In thebeginning stages of a new SAP implementation, customers frequently have onlythe development system physically installed and store the development andcustomizing work in the transport directory and import queues of the respectiveplanned SAP systems.



Backup Domain Controller

If the SAP system acting as the transport domain controller fails, no changescan be made to the TMS configuration. SAP therefore recommends that youconfigure a backup domain controller that can take over the function of the domaincontroller when required.

It may also be necessary to move the transport domain controller to another SAPsystem. In such a case, you must activate the backup domain controller. Then, thebackup domain controller becomes the domain controller and vice versa.

Figure 23: Transport Domain Management using a Backup DomainController

Hint: The SAP system you select as a backup domain controller must bean existing SAP system; it cannot be a virtual or external SAP system.

To check the current status of the transport domain configuration for each SAPsystem in the transport domain, access the TMS overview. From the TMS initialscreen, choose Overview Systems. In this overview, you can also see whetherthe configuration is up to date, and whether any errors occurred when distributingthe configuration.




Configuring tp

The transport control program tp requires a transport profile that containsinformation about establishing the database connection for all SAP systems in thetransport domain and other technical information for performing the transportprocess. TMS generates and manages this transport profile as a part of thetransport domain configuration. Do not adjust the transport profile using a texteditor at operating system level.

Figure 24: Configuring the Transport Control Program tp

To display the tp parameters of an SAP system, call transaction STMS. ChooseOverview Systems. Mark one SAP system and choose SAP System Display.Choose the tab Transport Tool. From the menu, choose Goto tp parameters.This displays the parameters in TP_.PFL and the default valueof all parameters used by the programs tp and R3trans. If a parameter is notspecified, a default value will be used. Global parameters override defaults. Localparameters override global parameters. For example, you can specify a globalparameter value for all but one SAP system if a local parameter applies to thatSAP system.



You can switch between the views Display All Parameters and Display SubstitutedParameters Only (content of TP_.PFL). You can switch by usingthe Display Less and Display More button.

Note: In releases up to SAP R/3 4.6C there was the configuration filetpparam. This is not used anymore. Although it was more or less ok, tomaintain the tpparam with an text editor, this is not ok anymore for theTP_.PFL

After performing an upgrade from SAP R/3 4.6C to SAP ECC 6.06, forexample, you might want to transfer your settings from the old to the newconfiguration file. You can do this in the parameter overview by choosingExtras -> Copy Configuration from TPPARAM.

Configuring Transport RoutesTransport routes indicate the role of each SAP system and the flow of transportrequests. The transport routes are what actually defines your SAP systemlandscape.

Overview

Initializing the TMS and setting up the transport domain define the SAP systemsin the environment only in terms of the transport domain, the domain controller,and the transport group. Next, you must define the transport relationship betweenthese SAP systems. Although the TMS has been initialized, you cannot performtransports until the transport routes have been configured and distributed.

After establishing a transport domain, you need to:

1. Model transport routes from the transport domain controller, using:

Default standard configurations (one-, two-, and three-systemlandscapes)

Graphical editor for non-standard configurations

2. Distribute and activate the new configuration data for all SAP systems withinthe transport domain

To reduce the effort of specifying individual transport routes, you can use standardconfigurations. Transport routes for the standard configurations are generatedautomatically.

You can choose from the following standard configurations:

Single system

Development and production system

Three SAP systems in Group




If you use the standard configuration function, the current configurations for allSAP systems involved are replaced by the standard settings. Existing packages,transport layers, or objects created in the SAP system are not deleted. For complexSAP system landscapes, define additional consolidation and delivery routes aftersetting up the transport route configuration on the basis of one of the standardconfigurations.

After you define a transport route, you must activate and distribute it to all SAPsystems in the transport domain.

There is a version management of the stored configurations. If you modify andsave an active configuration, the version counter is increased. To activate a storedversion, from the start screen of transaction STMS choose Overview TransportRoutes Configuration Get Other version. This displays a list of all versionsof the transport route configuration. Select the version you want from the list. Toactivate an older version, use the distribute and activate procedure.

To ensure consistency, transport routes can be configured only on the domaincontroller. To help define a transport route, the TMS provides a graphical editorand a hierarchical list editor, which can be used interchangeably, as well asstandard configurations for a one-, two-, and three-system landscape.

Transport Layers and Transport Routes

As previously stated, transport routes define the flow of the transport requestsfrom one SAP system to the next. These routes are called either consolidationor delivery routes.



Figure 25: Transport Routes

A consolidation route is an export / import route. Typically, the consolidationroute proceeds from the development system (where the transport request isexported from) to the quality assurance system (where the transport requested isimported into) in a standard three-system landscape. Consolidation routes havenames in order to be addressed.

A delivery route is an another import route. In a standard three-systemlandscape, the delivery route is specified between the quality assurance systemand the production system because there is no additional export from the qualityassurance system but another import in the production system. Delivery routeshave no names.

All repository objects are grouped into logical units called packages (formerly:development classes). The definition of each package contains an assignment to atransport layer. The transport layer is the name of a consolidation route. Objects,via the assignment to the package, inherit this transport layer assignment.

All SAP delivered objects are assigned according to their packages to the transportroute SAP.

Customizing objects (and others) are not grouped into packages. They followthe standard transport route. This standard transport route is named Z by default.

In the context of transport routes, an SAP system may play the following roles:




Integration system

The SAP system where changes originate and are assigned to transportrequests. The SAP system where customer changes are integrated with theSAP standard, customer developments and modifications take place.

Consolidation system

The target SAP system of a consolidation route.

Delivery system

The target SAP system of a delivery route.

Figure 26: Three SAP System Landscape Using a Standard Configuration

You need to configure more transport layers and transport routes if you have amore complex landscape and you need to reroute certain objects away from thestandard transport routes. For example, if a separate training system exists andthere are certain programs that are to run there but you do not want those programsgetting into the quality assurance or production system.

If the standard configurations delivered by SAP do not meet your landscape needs,TMS has editors available to allow you to maintain the landscape.

The graphical editor delivers a visual drag and drop interface, where the SAPsystems in the transport domain can be positioned and linked using the mouse.This is the default editor in the transaction STMS. It is shown in the followingfigure.



To create transport routes, use the mouse to drag the appropriate SAP systemsfrom the node area, and drop them in the display area. To create a transportroute between these SAP systems, from the screen Display Transport Routes,choose the Add Transport Route button. The mouse pointer becomes a stylus.Using the stylus, draw a line connecting the two SAP systems between whicha transport route is desired. In the Create Transport Route popup, enter therequired information for either the consolidation or delivery route. In case ofa consolidation route you need to assign a transport layer. You can create thetransport layer right here. Save your changes. The following figure shows a morecomplex landscape.

Figure 27: More Complex SAP System Landscape

Distribution and Activation of Transport Routes

Changes in the transport route configuration are not valid until distributed andactivated. To distribute and activate the changes from the TMS editor of thetransport domain controller, choose the Distribute and Activate icon and activateor follow Configuration Distribute and Activate. For activation the RFCconnections are used, that are created during the setup of the transport domain.

To avoid any possible inconsistencies, especially if there are any released transportrequests waiting in any import queues, TMS performs a number of consistencychecks on the version of the transport routes being activated, for example,whether the settings of the transport control program tp are consistent with thetransport route configuration. The activation also triggers checks to verify that




new transport routes do not affect existing transport requests. If any problemsexist, the configuration will not be activated and you will receive an error messageindicating the nature of the error.

Note: Once you have configured the transport routes correctly, the onlyreason that changes would need to be made would relate to a change inyour SAP system landscape, for example, adding a new SAP system tothe landscape.

Configuring QA Approval ProcedureWhen a transport request is released and exported from the development system(DEV), the consolidation system's (QAS) import buffer is populated. The importbuffer is a list of transport requests waiting for import. Once the transport requestis imported into the consolidation system, the import buffer for all deliverysystems (PRD) is populated.

Figure 28: QA Approval Procedure

With the QA approval procedure , the buffer of the delivery systems is populatedbut the entries are flagged as inactive. In other words, the transport requests cannotbe imported until the responsible person(s) flags the transport request as approved,which results in activating the entries in the delivery systems' buffers.

TMS Quality Assurance increases the quality and the availability of the productionsystems by letting you check transport requests in the QA system before they aredelivered to subsequent SAP systems. The SAP system for which the QA approval



procedure is activated is called the QA system. When the QA approval procedureis activated, a transport request will only be imported into the delivery system(s)if all the QA approval steps are processed in the QA system and the request hasbeen approved. When you configure the QA system, you determine how manyQA approval steps have to be processed for each transport request.

Figure 29: Configuring the QA Approval Procedure

The figure above shows you how to activate the QA approval process from thegraphical editor and how to define the approval steps.

Verifying the TMS SetupOnce you have configured the TMS, there are some tests that you can perform toverify that there are no technical problems with the TMS configuration:

RFC connection test

Transport directory check

Transport control program (tp) check

Because the transport domain controller communicates with the other SAPsystems in the domain using RFCs, you should check the RFC connectionsbetween the SAP systems in the domain. To do this, from the Systems screen ofthe STMS, select an SAP system from the list and choose SAP system Check Connection Test. This verifies communications in both directions to and fromthe domain controller.




Since exports physically write files to the file system level and imports read andupdate these files, you should verify that the transport directory is available and hasthe appropriate file system level permissions. To do this, from the Systems screenof the STMS, choose SAP system Check Transport Directory. This actioncreates, reads, and deletes a file to each of the transport directory subdirectories andreturns a report on the success or failure of all subdirectories. If you receive anyerrors, the appropriate corrections would need to be made at the file system level.

Because exports and imports are physically executed by the operating system levelprogram tp, you should verify that the tp program and its parameter configurationare consistent. To do this, from the Systems screen of the STMS, follow SAPsystem Check Transport Tool. This executes tests verifying the tp interface,the transport profile, the RFC destinations, and connection to the databases andreturns a report of the results.



Exercise 1: Setting Up the TransportManagement System (TMS) (verification)

Exercise ObjectivesAfter completing this exercise, you will be able to:

Review the transport domain configuration

Review transport routes

Verify the technical setup of the Transport Management System (TMS)

Business ExampleAs an SAP administrator you want to change the configuration of your transportdomain. Before doing this, it is necessary to verify the existing configuration.

Task 1: Transport DomainReview the transport domain configuration.

1. Determine the name of the transport domain that includes the developmentsystem DCC.

Note: Log on with your user -## in client 100 ofdevelopment system DCC.

2. Which SAP systems are included in the domain?

3. Which SAP system is the transport domain controller? Is there a backupdomain controller configured? Are there any virtual systems configured?

4. Do all systems belong to the same transport group?

Task 2: Transport RoutesReview transport domain and transport routes.

1. View the current transport domain and its transport routes.

2. What transport layers and transport routes have been defined for this SAPsystem landscape? List the SAP system(s) that are considered consolidationsystem(s)? Which SAP system(s) are considered delivery system(s)?

Task 3: QA Approval ProcedureVerify the configuration of the QA approval procedure.

1. Is the QA approval procedure activated? Which SAP system is configured asthe QA system? Who is responsible for approving transport requests?

Continued on next page



Result

The approval steps To be approved by request owner and To be approvedby department are activated.

Note: To be identified as system administration, you need theauthorization for the value TADM for the authorization objectS_CTS_ADMI (CTS_ADMFCT field). By default, this is containedin the authorization S_CTS_ADMIN.

Task 4: Checking TMS configurationVerify the technical configuration of the TMS.

1. The domain controller uses RFCs to communicate with the SAP systems inthe domain. Verify the RFC communications between QCC and the domaincontroller.

2. Exports physically write files to the file system level directories and importsread and update these files. Verify that the directory is available to the DCC,QCC and PCC system and that the appropriate file system level permissionsare set.

3. Exports and imports are physically executed by the operating system levelprogram tp. Verify that the tp program and its parameter configuration isconsistent and that it can access the DCC, QCC and PCC databases.




Solution 1: Setting Up the TransportManagement System (TMS) (verification)

Task 1: Transport DomainReview the transport domain configuration.

1. Determine the name of the transport domain that includes the developmentsystem DCC.

Note: Log on with your user -## in client 100 ofdevelopment system DCC.

a) Execute transaction STMS.

This screen displays:

The name of the SAP system you are logged on to, in this caseDCC

The name of the transport domain: for example: DOMAIN_ECC

2. Which SAP systems are included in the domain?

a) In transaction STMS choose Overview System.

The SAP systems DCC, QCC, PCC, PC2 and TRN are displayed.

3. Which SAP system is the transport domain controller? Is there a backupdomain controller configured? Are there any virtual systems configured?

a) Examine the column displaying the system type (Column heading Typor TMS System Type).

b) Either highlight the icons or select the Legend icon and compare theicon status.

Either the development system DCC or the productive system PCCis defined as the transport domain controller. The quality assurancesystem QCC is defined as the backup domain controller. The SAPsystem PC2 is defined as an external system, the SAP system TRN isdefined as a virtual system.




4. Do all systems belong to the same transport group?

a) From the System Overview screen of transaction STMS, choose Goto Transport Groups.

This displays a hierarchical list of the TMS configuration sorted by theSID within the group within the domain. There is only one domain, forexample DOMAIN_ECC.

There are two transport groups, GROUP_DCC and EXTGRP_DCC.

Task 2: Transport RoutesReview transport domain and transport routes.

1. View the current transport domain and its transport routes.

a) Execute transaction STMS.

b) Choose Overview Transport Routes.

Hint: If the display is too small, choose the Zoom In icon.





2. What transport layers and transport routes have been defined for this SAPsystem landscape? List the SAP system(s) that are considered consolidationsystem(s)? Which SAP system(s) are considered delivery system(s)?

a) On the graphical display, the lines connecting the SAP systemsrepresent the transport routes.

The standard transport layer ZDCC exists as a consolidation routefrom DCC to QCC for the transport of customer objects.

Hint: You know ZDCC is the standard transport layerbecause it displays in the DCC system box.

The transport layer SAP exists as a consolidation rout

tadm12_2 en col99 fv part ltr

Documents