SAP TADM12-Part 2_EN_Col15_NW 7.40.pdf

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM12 SAP NetWeaver AS - Implementation & Operation II


P A R T IC IP A N T H A N D B O O K INSTRUCTOR-LED TRAINING Course Version: 15 Course Duration: 5 Day(s) Material Number: 50128491


0

Visit : www.erpexams.com


SAP Copyrights and Trademarks

© 2015 SAP SE. All rights reserved. No part of this publication may be reproduced or transm itted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. •

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

•

IBM, DB2, DB2 Universal Database, System i, System i5, System p. System p5, System x, System z, System zlO, System z9, zlO, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S /39 0 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, P0WER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

•

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

•

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

•

Oracle is a registered trademark of Oracle Corporation

•

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

•

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

•

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

•

Java is a registered trademark of Sun Microsystems, Inc.

•

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

•

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries.

•

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

•

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP 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 specifications may vary.




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






0



Typographic Conventions American English is the standard used in this handbook. The following typographic conventions are also used.

This information is displayed in the instructor’s presentation

Demonstration

Procedure

Warning or Caution

A

O

Hint

Related or Additional Information

Facilitated Discussion

User interface control

Example text

Window title

Example text


0




0



Contents ix

Course Overview

1

Unit 1:

2 10 14 25

Lesson: Describing the SAP System Landscape Lesson: Describing the Clients in an SAP System Lesson: Defining System and Client Change Options Unit 2:

26 45 52 65

Unit 3:

Lesson: Managing Transport Requests for Customizing Exercise 2: Create and Assign Transport Requests for Customizing Lesson: Describing the Customizing Process Flow Exercise 3: Perform Business Configuration with IMG Lesson: Describing Change Management for ABAP Development Exercise 4: Create a Package for a Customer Development Lesson: Developing Customer Programs

119 121

Exercise 5: Create a Customer Program Lesson: Modifying SAP Objects

136 143

173 184 189 199 205 215 225 235 244

Transport Request in SAP Customizing and ABAP Development

Lesson: Customizing SAP Systems

87 95 102 113

159 164

SAP System Landscape

Lesson: Setting Up the Transport Management System (TMS) Exercise 1: Verify the Transport Landscape Lesson: Creating Extended Transport Control

67 75 S3

157

Introduction to SAP Software Logistics

Exercise 6: Modify an SAP Program and an SAP Table Structure Unit 4:

Transport Request Import

Lesson: Describing the Transport Process Flow Lesson: Importing Transport Requests Using TMS Exercise 7: Perform Imports Using TMS Lesson: Defining the Quality Assurance (QA) Approval Procedure andTransport Proposals Exercise 8: Perform a QA Approval Exercise 9: Create and Manage a Transport Proposal Lesson: Maintaining the Import Process Exercise 10: Monitor the Import Process Lesson: Monitoring Transport Activity Exercise 11: Troubleshoot Import Problems Lesson: Cleaning Up the Transport Directory




Lesson: Configuring the Change and Transport System (CTS) for Transporting Non-ABAP Objects Lesson: Transporting Non-ABAP Objects

258 277 289 303

Exercise 12: Transport Non-ABAP Objects with Enhanced CTS Unit 6:

305 309 311 321 324

Lesson: Describing Client Copy and Client Transport Tools Lesson: Performing Client Copies Exercise 13: Perform a Local Client Copy Lesson: Managing a Client Transport Lesson: Deleting Client Copies Lesson: Monitoring Client Copies

326 330 335 343

Client Tools

Lesson: Performing Client Compare and Adjustment Exercise 14: Perform a Client Compare and Adjustment Unit 7:

SAP Software Maintenance

Lesson: Implementing SAP Notes

345 355 369 372 377 384

Exercise 15: Implement a Note with the Note Assistant Lesson: Describing SAP Support Packages Lesson: Managing SAP Support Packages

389

Exercise 16: Perform the Modification Adjustment Lesson: Managing SAP Support Packages with Software Update Manager(SUM) Lesson: Implementing SAP Enhancement Packages and SAP

396

System Upgrades Lesson: Reviewing Phases in the Technical Implementation of an SAPSystem Update/Upgrade Lesson: Activating Business Functions with SAP Switch Framework 5

401

407

408 427

Unit 8:

Advanced User Administration Topics

Lesson: Implement Central User Administration (CUA) Exercise 17: Distribute User Data with CUA




Course TARGET AUDIENCE This course is intended for the following audiences:

•

Program/Project Manager

•

System Administrator

•

Technology Consultant


0






UNIT 1

Introduction to SAP Software Logistics

Lesson 1 Describing the SAP System Landscape

2

Lesson 2 Describing the Clients in an SAP System

10

Lesson 3 Defining System and Client Change Options

14

UNIT OBJECTIVES

•

Describe SAP systems

•

Identify the Recommended SAP System Landscape

•

Summarize data types in an SAP system

•

Describe a client

•

Define system change options

•

Define client change options


0



Unit 1 Lesson 1 Describing the SAP System Landscape

LESSON OVERVIEW This lesson describes the recommended SAP system landscape. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


•


SAP Systems

SAP Business Suite, SAP ERP, SAP NetWeaver

SAP ERP is an application located in SAP Business Suite

SAP product, license model

SAP Business Suite SAP C R M ~ SAP ERP Analytics SAP SRM a « r a rc m

Solutions

Financials Human Resources

SAP SCM

Corporate Services

SAP CRM SAP SRM

SAP ERP SiIAP SCM siAP PLM

F g r J S ’.T

Installable unit, SAP system

Figure 1: SAP Business Suite

SAP Enterprise Resource Planning (ERP) is an SAP solution. SAP offers other SAP solutions for the areas of Customer Relationship Management (SAP CRM), Supplier Relationship Management (SAP SRM), Product Lifecycle Management (SAP PLM), and Supply Chain Management (SAP SCM). All these solutions are part of the SAP Business Suite (formerly known as mySAP.com). As a result, a customer with an SAP Business Suite license has the license for the solutions that can be seen as subsets of the SAP Business Suite.




Inside the SAP solutions, SAP offers the SAP components, like SAP ECC, SAP SCM server, or others. From a technology point of view, a customer installs or upgrades these components. SAP NetWeaver represents the technology stack provided by SAP to support the SAP Business Suite. Furthermore, SAP NetWeaver and its integration capabilities allow the integration of nonSAP products. SAP NetWeaver is delivered with all of the SAP applications. As a result, customers can use the SAP NetWeaver components for a specific application. SAP NetWeaver is a set of technical components like SAP NetWeaver AS, SAP BW, SAP Enterprise Portal, SAP Process Integration, SAP NetWeaver MDM, and others. These technical components of SAP NetWeaver can be installed to serve different requirements. The SAP for Industry applications, which are also part of the SAP product portfolio, can be seen as extensions to the SAP Business Suite and its SAP applications. SAP for Industry applications, which were historically add-ons to one single component called SAP R/3, now provide not just add-ons to SAP components but also preconfigurations and best practices. SAP Business Suite

SAP ERP SAP ECC SAP XSS

Figure 2: Architecture of SAP ERP

As an example of an SAP solution the figure Architecture of SAP ERP gives a good overview of the SAP solution SAP ERP.




SAP R/3 / ECC Part of SAP NetWeaver 7.4 7.0 EHP 3 7.0 EHP 2 7.0 EHP 1 7.0 7.0 7.0 7.0 (2004s) 2004 (’04)

7.3 EHP 1 7.3

Basis Functionality (SAP Basis/ SAP W ebAS/SAP NetWeaver AS) 7.4 7.03 7.02 7.01 7.00 7.00 7.00 7.00 6.40 6.30 6.20 4.6C ... 7.31 7.30 7.20 7.11 7.10

ess Business ionality (Core) Extension Set 6.07 (6.06) (6.05) (6.04) (6.03) (6.02) (6.01) 6.0 5.0 4.7 4.7 4.6C

6.07 (6.06) (6.05) (6.04) (6.03) (6.02) (6.01) 6.00 5.00 2.00 1.10

Part of SAP ERP 6.0 EHP 7 6.0 EHP 6 6.0 EHP 5 6.0 EHP 4 6.0 EHP 3 6.0 EHP 2 6.0 EHP 1 6.0 (2005) 2004 (2003) (2003)

Basis Functionality not used for SAP R/3 / ECC

6 .1 0

4.6D

Figure 3: SAP R/3 / ECC Releases

The figure SAP R/3 / ECC Releases removes the confusion concerning the different SAP R/3, SAP R/3 Enterprise, 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 enhancement packages for SAP ERP. For detailed information on SAP ERP Enhancement Packages (EHP) see SAP Service Marketplace, Quick Link /erp-ehp. The systems for this course are based on SAP NetWeaver Version 7.4 (SAP_BASIS 740) SP04 and include SAP ERP 6.0 EHP7. More information on current supported releases can be found in the Product Availability Matrix located on Service Marketplace at www.service.sap.com/PAM.

Hint: There are also SAP enhancement packages for SAP CRM, SAP SCM, SAP SRM. For detailed information on these SAP enhancement packages see the following quick links in SAP Service Marketplace: /crm-ehp, /scm-erp, and /srm-ehp.

SAP Architecture and Terminology This section covers the infrastructure of the SAP systems used in the landscape. The figure Architecture of SAP Solution Manager represents 7.3 and higher.




SAP NetW eaver A p p licatio n Server ABAP System

SAP N etW eaver A p p licatio n Server Java System

cs

PAS

ES

ICM

r SP

MS

GW

I • • ■

Java

SP

SAP N etW eaver A p p licatio n Server ABAP+Java System CS

ES

MS

GW

ABAP

Java

Figure 4: Architecture of SAP Solution Manager

Hint: Avoid installing and using dual stack systems, except for SAP Process Integration and SAP Solution Manager as shown in the Architecture of the SAP Solution Manager figure. Starting from SAP Process Integration 7.30, you can install Process Integration as AS Java only. Some things to note about the architecture of the SAP systems: •

The Internet Communication Manager (ICM) is the interface to the Internet. It facilitates Web requests as a server and as a client. It supports several protocols like HTTP, HTTPS, and SMTP. The SAP NetWeaver AS can be used as a web server and as a web client.

•

The ABAP-Dispatcher dispatches requests to the Work Processes. If all work processes are busy at the moment, the requests are placed in the Dispatcher-Queue.

•

The ABAP Work Processes execute the ABAP coding.

•

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

•

The Java-side of the SAP NetWeaver AS contains components like the Java-Dispatcher (or ICM instead in some releases), Server Processes, the Software Deployment Manager (SDM), and the Central Services (SCS).

•

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




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 connection between the client and the server process. The Java Dispatcher works according to a round-robin algorithm. The Software Deployment Manager (SDM) is the standard tool with which J2EE components are installed on the SAP NetWeaver AS Java. The Central Services run on one server and form its own Java instance. It consists of a Message Service and an Enqueue Service, which are the basis for communication and synchronization for the Java Cluster. Each instance of an SAP NetWeaver AS ABAP+Java contains the ABAP Dispatcher with its Work Processes and the Java Dispatcher with its Server Processes. One of the instances is installed as an ABAP Primary Application Server, which means that the Enqueue Work Process runs here. Alternatively, the SAP system can be installed without a central instance, but with a stand-alone Enqueue Server. The applications and data for ABAP and Java both have their own database schema in one common database. In the newer releases, the term Central Instance was renamed to Primary Application Server and the term Dialog Instance was renamed to Additional Application Server. A user can log on and communicate with the SAP system either using the SAP GUI or a web client (browser) in one of the following ways: •

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

•

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

Recommended System Landscape From this point on, this course focuses on SAP NetWeaver as AS ABAP. SAP System Landscape

Protect application data using client roles and authorization concepts. Perform development, quality assurance, and production activities in separate environments to ensure consistency of repository objects, and a secure and stable production environment.




To maintain data security, protect application data by using the client concept, which separates data according to clients, and the authorization concept, which separates data within one client according to the users. In addition, strictly separate the environments for development, quality assurance, and production. The stability and performance of the production client cannot be affected by development and test activities in the other clients. Changes to repository objects are cross client, and they immediately affect the business functions and processes. Therefore, you are required to test changes before they can be transported to the production system. If you have only one SAP system, no further development is possible after production started. Change repository objects only when you have stopped production operations for development and testing. A two-system landscape is not optimal because development and quality assurance testing both take place in the development system. DEV

TEST

*#

PROD

151 151 15

1 system landscape

no stable business processes DEV

TEST

Chances endanger P ro d u c tiv e o p e r a tio n PROD

2 system landscape no stable test environment DEV

3 system landscape

stable business processes

TEST

Cross-client cust. Repository DEV DEV

PROD

TEST

4 system landscape 1 Cross-client cust.

I

Reoositor V____ 1 DEV

Reposito PRD

QAS

Cross-client cust. Repositorv____ QAS

PRE-PROD

PROD

Qross-client cust. PRE-PRD

PRD

Figure 6: SAP Recommended Landscape




To ensure a smooth production operation, an SAP system landscape has three SAP systems, which include the standard clients, and any required additional clients. A three-system landscape can often meet the needs of most customers. Typical systems include development, production, and quality assurance. Development takes place in the development system. Changed objects are then released to the quality assurance system. In the quality assurance system, you test new developments without affecting the production environment. A quality assurance system enables you to integrate development efforts and to check the validity and consistency of transported objects before moving the objects into production. All objects imported into the quality assurance system is delivered to one or more production systems. The three-system landscape is also a basis to apply SAP Support Packages or to perform a release upgrade. SAP systems in the same SAP system landscape require unique SAP system names. SAP provides the tools required for the creation, documentation, and distribution of changes within an SAP system landscape. To set up the SAP system landscape so that it supports the management, verification, and testing of all changes do the following: •

Use a single client for all customizing work. Set client change options appropriately before using your clients.

•

Use a single SAP system (the development system) for all development work. Set the system change options appropriately.

•

Use sample profiles included in the SAP system to create and assign appropriate user authorizations to developers and customizers. These authorizations control whether a user can create, modify, or release tasks and transport requests.

•

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

Figure 7: Change and Transport System (CTS)




Tools of the Change and Transport System (CTS)

•

The Change and Transport Organizer (CTO) provides functions for organizing software development projects. It is designed to support projects of all sizes, whether they are carried out centrally or in a distributed environment.

•

The Transport Management System (TMS) organizes, monitors, and performs transports for all SAP systems within an SAP system landscape. In addition, use TMS to configure and manage the setting up of SAP systems and transport routes within an SAP system landscape.

•

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

LESSON SUMMARY You should now be able to:

•


•





Unit 1 Lesson 2 Describing the Clients in an SAP System

LESSON OVERVIEW This lesson describes the data types, the client, and client roles in an SAP system. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


•

Describe a client

Data Types in an SAP System Data Types in an SAP System

Data types can be separated into the following categories: •

Client-specific data, application, customizing, and user master data, which affect only one client

•

Cross-client data, cross-client customizing data, and all repository objects, which affect the whole SAP system environment Client 100

Client 200

Application data

Application data

(orders, invoices, and so on)

Client-Specific Customizing (company codes, plants, storage locations, and so on)

(orders, invoices, and so on)

o (/> s => CTOO £ OJ t / j

Client-Specific Customizing (company codes, plants, storage locations, and so on)

/> "(D O O) w Q 0 )£ to TO E a> ^3

Cross-Client Customizing Repository Objects (such as table structures, programs , transactions, functidn modules) In-house developments in the Technology FI CO HR PP SD | customer namfspace

Packages Figure 8: Data Types in an SAP System




Clients and Client Roles A client is a unit of the SAP system that is technically, organizationally, and functionally selfcontained. A client has its own set of user master data, application data, and customizing data based on the table key ranges. Technical implementation of clients occurs when all users exist in one specific client within an SAP system. It has application data (master and transaction data) that belongs to one specific client.

Client 100 Application Data

(U re Q (A

re

Client-Dependent Customizing

a> (A 3

Figure 9: Clients in SAP Systems*•

Data from different clients is kept separate logically at the database. Open SQL statements executed by an SAP application use the client number in the where-clause to retrieve the client data. Although a table may contain data from several different clients, the where-clause limits access to specific clients. Client-Specific Data

•

User master data such as parameters, user groups

•

Customizing data such as organizational units, assignments, and document types

•

Application data such as business transaction data and material master data

The SAP client concept can integrate several companies or subsidiaries in a single client by using company codes and the SAP authorization concept. Company codes define the smallest corporate organizational units for which a complete self-contained set of accounts can be drawn up for external reporting. The SAP authorization concept enables the parent company to access all subsidiaries for reporting purposes, while subsidiary-specific data is protected against access from other subsidiaries through a company code definition.




Development and Customizing

For configuring client settings and creating new functionality

Quality assurance

For testing functionality and verifying configuration

CUST

QTST

Production

For production activities and business data

PROD Figure 10: Standard Client Roles

Standard Client Roles

Use the Developing and Customizing (CUST) client to configure client settings and create new functionality. CUST is the central customizing client where complete adaptation of the SAP system to customer-specific needs takes place. All changes performed in this client are recorded so they can be supplied to the other clients using the Transport Management System (TMS). Use the Quality Assurance (QTST) client for testing functionality and verifying configurations, such as new customizing settings in the application. Use Production (PROD) client for production activities and business data. The PROD client is where your company's business is carried out. Customizing changes imported into this client have to be first tested carefully in the QTST client to ensure that production operation is free of disruption. To realize the full benefit of a three-system landscape, every critical client requires a separate SAP system.




Sandbox

For experimenting with customizing transactions and settings

Test

For testing configuration settings using data in a more stable environment (unit test)

SAND

TEST

For end-user training

TRNG Figure 11: Additional Client Roles*•

Additional Client Roles

•

Use a Sandbox (SAND) client for experimenting with customizing transaction and settings.

•

Use a Test (TEST) client for testing configuration settings using data in a more stable environment. Customizing settings can be copied from the customizing client to the test client when performing the unit test.

•

Use a Training (TRNG) client for end user training.

•

Use any additional client to satisfy a customer-specific requirement.

LESSON SUMMARY You should now be able to:

•


•

Describe a client




Unit 1 Lesson 3 Defining System and Client Change Options

LESSON OVERVIEW This lesson defines system and client change options in an SAP system. LESSON OBJECTIVES After completing this lesson, you will be able to:

•

Define system change options

•

Define client change options

System Change Options As a transport administrator, set the correct system change options for each SAP system. S y s t e m C h a n g e O p tio n

^

S B

D e nt Settng

Global Settng

_________ X Modifiable

»

Figure 12: System Change Options

The system change options define whether or not repository objects and cross-client customizing objects are globally modifiable. If they are globally modifiable, you can specify whether each software component and namespace can be modified in transaction S E 0 6 , Goto —► System Change Option. Software Component Settings

A software component is a set of dedicated development classes. For the software components, there are four possible settings, as follows: For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]



• Modifiable • Restricted Modifiability (can only create objects as non-originals) • Not Modifiable; Enhanceabie Only (changes not allowed; objects can be enhanced using the Enhancement Framework only) • Not Modifiable; Not Enhanceabie (changes and enhancements not allowed)

You can reserve namespaces for software developed by SAP customers and partners. These namespaces are designed for large-scale customer enhancements, as well as add-ons developed by partners. The syntax for objects from reserved namespaces is: //

SAP TADM12-Part 2_EN_Col15_NW 7.40.pdf

Recommend Documents