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
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
Course TARGET AUDIENCE This course is intended for the following audiences:
•
Program/Project Manager
•
System Administrator
•
Technology Consultant
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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:
•
Describe SAP systems
•
Identify the Recommended SAP System Landscape
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.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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)
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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:
•
Describe SAP systems
•
Identify the Recommended SAP System Landscape
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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:
•
Summarize data types in an SAP system
•
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 )£ ) z> 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
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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:
•
Summarize data types in an SAP system
•
Describe a client
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At :
[email protected]
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]
Visit : www.erpexams.com
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: /
/. For each SAP system, the customer can define whether or not the objects contained in the namespaces and name ranges can be changed. To enable you to change objects, the SAP system must not be globally locked to changes.
Client Change Options Client change options that are found in the clients master table T000 can be maintained by using transaction SCC4. Maintain the two settings to implement controls where changes are made and enforce the changes being recorded to transport requests are as follows: •
Changes and transports for client-specific objects
•
Cross-client object changes
Table 1: Change and Transports for Client-Specific Objects The following cross-specific object change and transport options are available: Radio Button
Attributes
Changes without automatic recording
•
Changes in the Customizing setting are per mitted.
•
Changes are not automatically recorded in a transport request.
•
Customizing settings can be exported from the client by manual creation of a transport request.
•
A manual transport can be carried out in the particular transaction (if possible) or man ually.
•
This variant makes sense for pure test, training, or demonstration clients.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Radio Button Automatic recording of changes
No changes allowed
Attributes •
Changes are permitted in the customizing settings of the client.
•
All the changes are automatically recorded in a transport request.
•
It is also possible to export independently of the automatic recording from the client cus tomizing settings by manual creation or re cording of a transport request.
•
In a productive client, settings that can be maintained as current settings are excluded from automatic recording; current settings (for example, exchange rates and posting periods) are maintained without recording the changes.
•
This variant can be used for customizing cli ents and productive clients.
•
Changes in the customizing settings of the client are not permitted.
•
Customizing settings can be exported from the client by manual creation of a transport request.
•
In a production client, the customizing set tings that can be maintained as current set tings are excluded from the client lock. This option means that current settings (for ex ample, exchange rates and posting periods) can always be maintained in the production client.
•
This variant can be used for production cli ents, demonstration clients, and training cli ents.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Radio Button
Attributes
Changes without automatic recording, no transports allowed
•
Changes are permitted in the customizing settings of the client.
•
The changes are not automatically recorded in a transport request.
•
No manual transport of customizing set tings from the client is possible.
•
This variant can be used for pure test cli ents.
Cross-client object changes control which clients you are allowed to maintain objects. If the maintained objects in a client are exclusively application objects (all client-specific) or clientrelated customizing objects, it makes sense to disallow cross-client maintenance. In this case (for example in a test client), ensure that cross-client functionality cannot be changed. Cross-client functions include all cross-client customizing objects (for example, factory calendar, definition of price list conditions, and printer controls). They also include all objects of the SAP Repository (programs, function modules, screens, dictionary, and so on). Table 2: Cross-Client Changes The following cross-client object change options are available: Field Value
Attributes
Changes to repository and cross-client cus tomizing allowed
•
There are no restrictions on the mainte nance of cross-client objects for the client when this setting is used.
•
Both cross-client customizing objects and objects of the SAP Repository can be main tained.
•
Use in customizing/development client on ly.
•
Cross-client customizing objects cannot be maintained in the client with this setting.
•
Only use this option if development client is separate from customizing client.
•
With this setting, objects of the SAP Reposi tory cannot be maintained in the client.
•
Only use this option if customizing client is separate from development client.
No changes to cross-client customizing ob jects
No changes to repository objects
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Field Value
Attributes
No changes to repository and cross-client cus tomizing objects
•
Combination of both restrictions: Neither cross-client customizing objects nor ob jects of the SAP Repository can be main tained in the client.
•
Use this option in every client in the land scape except for customizing/development clients.
Current Settings in Client Change Options Production Client
Table T000, transaction SCC4 •
Changes and transports for clientspecific objects: No changes allowed
•
Cross-client object changes: No changes to Repository and cross-client Customizing objects
•
Client role: Production
II
Table OBJH
Figure 13: Customizing Using Current Settings
In a customizing project and also during the maintenance of an SAP system, all the customizing changes are transported and tested in the quality assurance system. However, certain kinds of customizing changes, data-only customizing changes, are carried out in a production client without being saved as transport requests. Examples of such data include interest rates, health insurance premiums, pension schemes, tax schemes, and currency exchange rates, which may require frequent adjustment in SAP systems. Since these types of changes are performed frequently, they are not subject to extensive testing like other customizing changes. These changes are done directly in the productive client in the productive system. To avoid having to use transport requests for these changes, SAP has introduced the Current Settings function. Current Settings may be used within a production client without impacting business flow-related Customizing objects. SAP-approved Current Settings for customizing objects are kept in the CURSETTING field in the table o b j h . Do not make customer changes to the table. When using Current Settings in a production environment, bear the following in mind: •
Client role is set to Production
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
Cross-client object changes are set to No changes to Repository and cross-client Customizing objects
•
Changes and transports for client-specific objects are set to No changes allowed
LESSON SUMMARY You should now be able to:
•
Define system change options
•
Define client change options
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Learning Assessment
1. Which two areas make up the CTS? Choose the correct answers. | A TMS B CTO | C ABAP D SDM 2. Identify the various data area or systems in an SAP system landscape. Explain the need for a separate data area.
3. Explain the difference between client-specific and cross-client data types in an SAP system.
4. Identify the minimum requirement types of clients in an SAP landscape. Choose the correct answers. | A TRNG B PROD | C OUST D QTST
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected] 21
© Copyright. All rights reserved.
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
5. The system change options define whether objects can be changed in an SAP system. If the system is set up to be globally modifiable, what are the possible settings for software components ? Choose the correct answers. | A Changeable B Modifiable C Not Modifiable; Enhanceable only D Not Modifiable; Not Enhanceable E Restricted Modifiability 6. What are the two types of client change options? Give examples.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Learning Assessment - Answers
1. Which two areas make up the CTS? Choose the correct answers. [x ] A TMS \x \ B CTO | C ABAP D SDM
2. Identify the various data area or systems in an SAP system landscape. Explain the need for a separate data area. To ensure a smooth production operation, an SAP system landscape has three SAP systems, which include the standard clients, and any required additional clients. Use a three-system landscape, which meets the needs of most customers. Typical systems include development, production, and quality assurance. 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. 3. Explain the difference between client-specific and cross-client data types in an SAP system. Client-specific data, application, customizing, and user master data affect only one client. Cross-client data, cross-client customizing data, and all repository objects affect the whole SAP system environment._______________________________________________________
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
4. Identify the minimum requirement types of clients in an SAP landscape. Choose the correct answers. | A TRNG \x \ B PROD \x \ C OUST [x ] D QTST
5. The system change options define whether objects can be changed in an SAP system. If the system is set up to be globally modifiable, what are the possible settings for software components ? Choose the correct answers. | A Changeable [x ] B Modifiable |~xj C Not Modifiable; Enhanceable only |~xj D Not Modifiable; Not Enhanceable |~xj E Restricted Modifiability
6. What are the two types of client change options? Give examples. There are client-specific settings and cross-client settings. An example of a client-specific setting is Automatic Recording of Changes and an example of a cross-client setting is No Changes to Cross-Client Customizing Objects.______________________________________
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Lesson 1 Setting Up the Transport Management System (TMS) Exercise 1: Verify the Transport Landscape
26 45
Lesson 2 Creating Extended Transport Control
52
UNIT OBJECTIVES
•
Identify the basic configuration steps of the Transport Management System (TMS)
•
Set up a transport domain
•
Configure transport routes
•
Configure QA approval
•
Configure the extended transport control
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected] 25
© Copyright. All rights reserved.
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Setting Up the Transport Management System (TMS)
LESSON OVERVIEW
This lesson describes the basic steps involved in setting up the Transport Management System. It also covers setting up a transport domain and configuring transport routes, QA approval, and extended transport control. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Identify the basic configuration steps of the Transport Management System (TMS)
•
Set up a transport domain
•
Configure transport routes
•
Configure QA approval
Prerequisites of TMS The following list gives an overview of what to consider before, during, and after installation of an SAP system. Prerequisites for SAP system and Database Installation
Before SAP system and database installation, do the following: •
Define the network structure for the SAP system landscape
•
Install the hardware and the operating systems for the SAP systems
SAP System and Database Installation Step
During SAP system and database installation, do the following: •
Create one common transport directory (in certain cases you may want to have more than one)
SAP System and Database Steps After Installation
After SAP system and database installation, do the following: •
If you have set up the SAP system using a database copy, initialize the Change and Transport Organizer (CTO) (transaction SE06).
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
Set up the Transport Management System (TMS).
Hint: If you have set up the SAP system using a database copy, initialize the Change and Transport Organizer (CTO) using transaction S E 0 6 , choosing Database Copy or Database Migration and choosing the Perform Post-Installation Actions button. In any case, configure the SAP system landscape using the TMS and transaction s t m s . The process of setting up the SAP system landscape with transaction s t m s is described in detail in theTransport Directory Structure section. To set up your SAP system landscape, it is sufficient to start with an existing SAP system as a development system. The quality assurance and production SAP systems are not required at this stage. All future SAP systems are considered virtual systems. You also have to create a transport directory at the file system level for all SAP systems. This directory is required for the TMS. Transport Directory Structure
Transport Directory
Figure 14: Creating a Transport Directory
Depending on your existing SAP system landscape, the global transport directory and all the necessary subdirectories are created automatically during the installation of the SAP system. See the installation guide for your SAP system for more details. The SAP profile parameter DIR_TRANS points to the path of the transport directory. For Unix, the default path is /usr/sap/trans. For Microsoft Windows, the default path is \\ \sapmnt\trans. Some of the subdirectories required in the common transport directory include the following: •
bin: configuration files for tp (TP_.PFL) and TMS (DOMAIN.CFG)
•
buffer: transport buffer for each SAP system, indicating which transport requests are to be imported
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
data: data part of the exported transport requests
•
cofiles: command or transport request information files that include information on the transport type, object classes, required import steps, and post-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 system environment, set up different transport directories. You can enable transports in a heterogeneous operating system environment using a single transport directory. For more information, see SAP Note 83327. Transporting enables you to synchronize customizing and development in multiple SAP systems through the transfer of changes from the development system to downstream SAP systems. Transports along the transport routes must occur in only one direction. T ra n sp o rt Sequence Logical transport sequence
Export (copy)
Import (copy)
|
Import (copy)
^
Transport Directory Physical transport sequence Figure 15: SAP System Landscape Transport Sequence
As mentioned previously, transporting requires a transport directory to enable SAP systems 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 the following three steps: 1. All objects in a (transportable) transport request that are to be released are exported by being copied from the database of the source system to the transport directory.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
2. These objects are imported into the database of the quality assurance system. In QA, they are tested and validated. 3. After testing and verification, you import objects into the database of the production 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 databases of DEV, QAS, and PRD, and in the transport directory.
TMS Terminology Depending on the size of an organization and the scope of its SAP implementation, there can be many different individuals responsible for carrying out customizing and development projects. Some customize specific application areas, others develop new ABAP programs, others do QA testing and acceptance of changes. There can be hundreds or even thousands of changes transported through the SAP systems in the landscape. The transport of these changes uses the functions of the Transport Management System (TMS). The concepts behind TMS are the following: •
Centralized configuration of Change and Transport System (CTS) for all SAP systems
•
Centralized management of transport requests and especially the import process
•
Transport strategy based on predefined transport routes
The purpose of the TMS, accessed through transaction s t m s , is to control centrally the propagation of changes through the SAP system landscape based on predefined paths. TMS is designed to ensure the consistency of the SAP repository and the contents of the customizing tables in all SAP systems in the landscape. All necessary activities can be done from within the SAP system (using the SAP authorization concept) and there is no need to execute scripts at the operating system level manually. Use TMS to do the following: •
Define an SAP system's role within an SAP system landscape or transport domain
•
Configure the transport routes using either an editor or delivered standard configuration 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 / quality acceptance procedures in the QA system
•
Schedule the import of transport requests in an import queue
•
Perform transports between SAP systems without a common transport directory
•
Process transport proposals of developers
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
TMS enables SAP system administrators to centrally manage the transport configuration of multiple SAP systems by defining transport domains, assigning transport domain controllers, and defining transport routes. Transport Domain: all systems controlled centrally
System landscape for the Asian implementation
System landscape for the European implementation
Figure 16: The SAP System Landscape
A transport domain consists of all SAP systems that you plan to manage centrally. Within the transport domain, all SAP systems must have unique SAP 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 configuration settings are maintained. Any changes to the configuration settings are distributed to all SAP systems in the landscape. This setting ensures that the TMS configuration settings are consistent throughout the domain. The transport domain controller stores the reference configuration and all other SAP systems receive a copy of the reference configuration. An SAP system landscape is a set of SAP systems that share customizing and repository objects through transported transport requests. The typical landscape includes, but is not limited to, a development, a quality assurance, and a production system. In most cases, the SAP system landscape and the transport domain are made up of the same SAP systems but it is common to have multiple landscapes within one transport domain. Examples of a single transport domain with multiple landscapes are the following: •
A multinational company may have separate landscapes for each subsidiary. DEI, QA1, and PR1 may be the landscape for the Asian implementation and DE2, QA2, and PR2 may be the landscape for the European implementation. Even though they are separate landscapes, both can still be controlled centrally in one transport domain.
•
An SAP customer may have multiple landscapes for different kinds of SAP systems. DCC, QCC, and PCC may be the landscape for the SAP ECC systems, while DBW, QBW, and PBW may be the landscape for other SAP BW systems. Again, separate landscapes are controlled centrally using one transport domain.
A transport domain contains at least one transport group. A transport group consists of one or more SAP systems that share a common transport directory. The figure Transport Domain and Transport Group shows the relationship between a transport domain and a transport group.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Transport Domain 1 Transport Group
Transport Directory
= Transport Domain Controller Figure 17: Transport Domain and Transport Group
TMS supports several transport directories within a single transport domain. This situation might be the case, for example, for the multinational company mentioned previously where each subsidiary may have its own (local) transport directory. Or a transport domain containing a landscape that has a DEV system with its own transport directory and QAS and PRD system sharing a common transport directory, for security reasons. In this case, the domain would consist of two transport groups.
Note: The terms transport domain, domain controller, and transport group concern only the SAP systems in the environment. They do not include the transport relationship between the SAP systems, which is defined by the transport routes.
Initialization of TMS To set up the transport domain, first determine which SAP systems should be included in it. The transport domain should contain all SAP systems in all the SAP system landscapes that are centrally administered using TMS.
Note: Not all SAP systems must be installed and present when the domain is first configured, however planning the landscape is necessary. These future SAP systems can be represented by virtual systems.
Overview
The configuration of TMS can be broken down into the following steps. 1. Configuring the transport domain defines which SAP systems are included in the domain.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
2. Configuring the transport routes defines the SAP system and client roles within the landscapes. 3. (Optional) Configuring the QA procedure defines who is responsible for approving the acceptance of changes and the promotion of those changes to the delivery systems. The Setting Up the Transport Management System figure shows the three steps. Note that the first two steps are required for setting up an SAP system landscape whereas the last step (QA procedure configuration) is optional.
Initializing the Transport Domain Controller
The first SAP system you configure is automatically selected as the transport domain controller but you may later switch the role of the domain controller to a different SAP system. Transport Domain Transport Domain Transport Group
DEV or PRD Transport Domain Controller
Transport Directory
Figure 19: Establishing a Transport Domain
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Certain configuration tasks that are relevant to the entire transport domain (such as, creating transport routes) can only be carried out on the transport domain controller. The SAP system used as the domain controller should have the following attributes: •
High availability
•
High security precautions
•
Highest level of maintenance
Therefore, a production system might be the ideal choice to be a transport domain controller. The development system is installed before the quality assurance and production systems. The common practice is configuring the development system as the transport domain controller and then later moving the assignment of the transport domain controller to the production system. Another scenario might be to use an SAP system that you use already for central monitoring and/or central user administration as transport domain controller.
Note: The system load on the SAP system caused by work on the transport domain controller is very low.
When using TMS for the first time after SAP system installation, you are automatically prompted to initialize the TMS. Initialize the TMS while logged on to client 000. For configuring TMS, you need a user with the authorization S_CTS_ADMIN. Transaction STMS in client 0 0 0 Functions
•
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 directory bin of the transport directory
When you initialize the TMS, the SAP system performs automatically the following actions: •
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 transport subdirectory bin. This file contains the transport domain name and description as well as the transport domain controller's host name, instance number, SID, and transport group.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
The transport profile for the transport control program tp is generated and stored in the transport subdirectory bin under the name TP_.PFL. The parameters in this profile are maintained using the transaction s t m s .
Note: The name of the transport domain may not contain blanks and may not be changed afterwards without reconfiguring the domain controller. By default, a transport domain has the name DOMAIN_, where is the SAP system ID of the domain controller.
Additional SAP Systems in a Transport Domain To add new SAP systems to an existing transport domain, perform configuration activities on both the new SAP system and the transport domain controller. Transport Domain Transport Domain Transport Group
Approve
DEV O f PRD Create Transport Domain Controller
Real system
Apply
Virtual system
Transport D irectory
Figure 20: Adding Additional SAP Systems to a Transport Domain
Each additional SAP system must apply for inclusion to the transport domain controller. Since configuration of the TMS can only be done on the transport domain controller, the transport domain controller then must confirm inclusion for each SAP system. The initial screen of transaction STMS shows if an SAP system is waiting for inclusion in the transport domain status. The description of the transport domain is stored in the file DOMAIN.CFG in the bin subdirectory of the common transport directory. All other SAP systems connected to this transport directory read the file DOMAIN.CFG during STMS initialization to identify the domain controller and transport group address. If your SAP systems do not have a common transport directory, you can manually configure TMS with the address of the domain controller. When entering transaction STMS for the first time, choose the Other Configuration button and then from the TMS Configuration dialog box, choose Include System in Domain. In the next dialog box, enter the target host and the instance number of the transport domain controller. In any case, when an SAP system has been configured for the TMS and approved in the domain, you see a newly created user TMSADM and generated RFC destinations required for the TMS.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Hint: When configuring the TMS on an SAP system, you can specify the application server (such as, the instance) to be used for all TMS functions. Choose the instance with the highest availability. This instance provides the enqueue service, the primary application server (formerly known as the central instance).
A
Caution: To exchange data and objects between the SAP systems of an SAP system landscape all SAP systems use the same release, SAP Support Package level and correction level. For more information about transporting between different releases, see SAP Note 1090842.
Transport Domain DOMAIN_PRD Transport Domain Controller
PRD [email protected] _PRD Accesses automatically (uses preset user/password), for uncritical actions
[email protected] _PRD Accesses manually (needs user/password), for critical actions Figure 21: Centralized Configuration Data
The SAP systems within a transport domain communicate with each other using a Remote Function Call (RFC). RFC communication requires user IDs to access target SAP systems. When SAP systems are added to a transport domain, the necessary RFC destinations and user IDs are automatically configured by the TMS tool. The transport domain configuration settings are distributed throughout the transport domain using RFC communication. Changes to the transport domain configuration are made in the transport domain controller, and then distributed to all SAP systems in the transport domain. Each time you change the transport domain controller, a dialog box displays asking whether you can distribute the change. You can distribute several changes in one distribution process. When SAP systems are initially added to the TMS configuration, the communication user TMSADM is configured with limited authorizations. This user is utilized when distributing and activating the TMS configurations. The two types of RFC destinations created by the TMS are as follows: •
TMSADM@.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
TMSSUP@.
The user TMSADM is inserted as system user into the TMSADM@. destination but without the RFC user inserted into the TMSSUP@. destination. Therefore, if you try to execute a function that goes beyond the limited authorizations of the TMSADM user (for example, 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 SAP system with the necessary authorizations. Virtual SAP Systems Extending a transport domain is not restricted to physically installed SAP systems. Virtual SAP systems are included as placeholders for planned SAP systems and are replaced by the planned SAP system after it is physically installed. In addition, 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 the planned SAP system landscape and ensure that the import queues of subsequent SAP systems are already created and maintained for later use. In the early stages of a new SAP implementation, customers frequently install only the physical development system and store the development and customizing work in the transport directory and import queues of the respective planned SAP systems. Backup Domain Controller If the SAP system acting as the transport domain controller fails, no changes can be made to the TMS configuration. Configure a backup domain controller that can take over the function of the domain controller when required. It may also be necessary to move the transport domain controller to another SAP system. Thus, activate the backup domain controller. Then, the backup domain controller becomes the domain controller, and the domain controller becomes the backup domain controller.
Transport Domain Transport Group
Transport Domain Controller Backup Transport Domain Controller
Transport D irectory
Figure 22: Transport Domain Management Using a Backup Domain Controller
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Hint: The SAP system you select as a backup domain controller must be an existing SAP system: it must not be a virtual or external SAP system. To check the current status of the transport domain configuration for each SAP system in the transport domain, access the TMS overview. From the TMS initial screen, choose Overview —> Systems. In this overview, you can also see whether the configuration is up-to-date, and if any errors occurred when distributing the configuration. Transport Control Program Parameters The transport control program tp requires a transport profile that contains information about establishing the database connection for all SAP systems in the transport domain and other technical information for performing the transport process. TMS generates and manages this transport profile as a part of the transport domain configuration. Do not adjust the transport profile using a text editor at the operating system level. Management
Communication
Transport Tool
w \&\&:mm &■,CaturnValue Global Parameters 0 □ □ □ □ □ □ □ □ □ □ □ □
TRANSDIR Isl CTC DBHOST 23NAME DBTYPE IMPORT_SINGL_ 0 IMPORT_SINGL_ 0 NBUFFORM NO_IMPORT_ALL 0 REPEATONERROR STOPONERROR TP_VERSION WORKFLOW_STR_ 0
\\twdf0000\sapmnt\trans 1 twdfOOOO DCC ada 0 0 1 0 9 9 266 0
Figure 23: Configuring the Transport Control Program tp
To display the tp parameters of an SAP system, enter transaction s t m s . Choose Overview —> Systems. Mark one SAP system and choose SAP System —> Display. Choose the Transport Tool tab. From the menu, choose Goto —> tp parameters. This choice displays the parameters in TP_.PFL and the default value of all parameters used by the programs tp and R3trans. A default value will be used when a parameter is not specified. Global parameters override defaults. Local parameters override global parameters. For example, you can specify a global parameter value for all but one SAP system if a local parameter applies to that SAP system. You can switch between the views Display All Parameters and Display Substituted Parameters Only (content of TP_.PFL). You can toggle by using the Display Less and Display More buttons. Up to SAP R/3 4.6c there was a configuration file tpparem. After performing an upgrade from SAP R/3 4.6c to SAP ECC 6.06, you might want to transfer your settings from the old to the new
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
configuration file. You can make this selection using the parameter overview by choosing Extras —> Copy Configuration from TPPARAM. Note: Although, it was previously correct to maintain the tpparam with a text editor, this choice is not correct anymore for the TP_.PFL.
Transport Routes Transport routes indicate the role of each SAP system and the flow of transport requests. The transport routes define your SAP system landscape. Overview of Transport Routes
Initializing the TMS and setting up the transport domain define the SAP systems in the environment only in terms of the transport domain, the domain controller, and the transport group. Define the transport relationship between these SAP systems. Although the TMS has been initialized, you cannot perform transports until the transport routes have been configured and distributed. Steps After Establishing a Transport Domain
After establishing a transport domain, establish the following: 1. Model transport routes from the transport domain controller using a default standard configuration (such as one-system landscape, two-system landscape, and three-system landscape configurations) or the graphical editor for nonstandard configurations. 2. Distribute and activate the new configuration data for all SAP systems within the transport domain. To reduce the effort of specifying individual transport routes, you can use standard configurations. Transport routes for the standard configurations are generated automatically. 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 all SAP systems involved are replaced by the standard settings, but the existing packages, transport layers, or objects created in the SAP system are not removed. For complex SAP system landscapes, define additional consolidation and delivery routes after setting up the transport route configuration based on one of the standard configurations. After you define a transport route, activate and distribute it to all SAP systems in the transport domain. Version management of the stored configurations is available. If you modify and save an active configuration, the version counter is increased. To activate a stored version, from transaction STMS choose Overview —► Transport Routes —► Configuration —> Get Other version. This screen For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
displays a list of all versions of the transport route configuration. Select the version you want from the list. To activate an older version, use the distribute and activate procedure. To ensure consistency, configure transport routes only on the domain controller. To help define a transport route, the TMS provides a graphical editor and a hierarchical list editor, which can be used interchangeably, as well as standard configurations for a one-system landscape, twosystem landscape, and three-system landscape configurations. Transport Layers and Transport Routes
As previously stated, transport routes define the flow of the transport requests from one SAP system to the next. Refer to these routes as either consolidation or delivery routes. |T?DCC(l)/000 Create Transport Route (• Consolidation
Consokdation DC?
Integration system r
O Delivery
Transport layer
ZDCCjb
Consokdation system
QCC
Dekvery Source system
DC?
Dekvery system
Iqcc I
Consolidation for export/import (named)
Figure 24: Transport Routes
Consolidation Route A consolidation route is an export / import route. Typically, the consolidation route proceeds from the development system (where the transport request is exported from) to the quality assurance system (where the transport requested is imported into) in a standard three-system landscape. Consolidation routes have names to be addressed. Delivery Route A delivery route is another import route. In a standard three-system landscape, the delivery route is specified between the quality assurance system and the production system because there is no additional export from the quality assurance system but another import in the production system. Delivery routes have no names. All repository objects are grouped into logical units called packages (formerly, development classes). The definition of each package contains an assignment to a transport layer. The transport layer is the name of a consolidation route. Objects, through the assignment to the package, inherit this transport layer assignment. All SAP-delivered objects are assigned according to their packages to the transport route SAP. Customizing objects (and others) are not grouped into packages. They follow the 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:
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
Integration system - the SAP system where changes originate and are assigned to transport requests. The SAP system where customer changes are integrated with the SAP 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. Transport Lay
ZDCC ECC Development| enti
DCC ZDCC
J
*
Transport Lay
SAP
ECC Productive S
ECC QA System |
QCC
Delivery
I
„
PCC __________ £
Delivery route Consolidation routes Standard transport layer Figure 25: SAP Landscape with a Standard Configuration of Three Systems
The graphical editor delivers a visual drag and drop interface, where the SAP systems in the transport domain can be positioned and linked using the mouse. The graphical editor is the default editor in the transaction s t m s . Use the following navigation in the graphical display pictured in the figure SAP Landscape with a Standard Configuration of Three Systems. To insert new SAP systems into the configuration, use drag and drop. To define transport routes, insert arrows and choose the type of transport route. Distribute and activate the new configuration. Configure more transport layers and transport routes if you have a more complex landscape and reroute certain objects away from the standard transport routes. For example, if you configure the system differently for training purposes, certain programs exist for it, but these programs do not belong in 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. To create transport routes, use the mouse to drag the appropriate SAP systems from the node area, and drop them in the display area. To create a transport route between these SAP systems, from the Display Transport Routes screen, choose the Add Transport Route button. The mouse pointer becomes a stylus. Using the stylus, draw a line connecting the two SAP systems where you want a transport route. In the Create Transport Route dialog box, enter the required information for either the consolidation or delivery route. For a consolidation route you assign a transport layer. You can create the transport layer on this screen.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Distribution and Activation of Transport Routes
Changes in the transport route configuration are not valid until they are distributed and activated. To distribute and activate the changes from the TMS editor of the transport domain controller, choose Configuration —> Distribute and Activate. For the activation, the RFC connections, which are created during the setup of the transport domain are used. To avoid any possible inconsistencies, especially any released transport requests waiting in any import queues, TMS performs a number of consistency checks on the version of the transport routes being activated. For example, it checks whether the settings of the transport control program tp are consistent with the transport route configuration. The activation also triggers checks to verify that new transport routes do not affect existing transport requests. If any problems exist, the configuration is not activated and you receive an error message indicating the nature of the error. Note: Once you have configured the transport routes correctly, you only need to make changes if your SAP system landscape changes, for example, by the addition of a new SAP system. Now include SAP system PC2 parallel to PCC, as shown in the figure SAP Landscape with Complex Configuration. •
Use the mouse to drag system PC2 from the node area and drop it into the display area.
•
To create a transport route between these systems, choose Add Transport Route on the Display Transport Routes screen. Draw a line connecting QCC and PC2. In the Create Transport Route dialog box, choose Delivery as the route.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Hint: You should have configured PC2 as an external system. You can demonstrate transporting with different transport groups later. Details are discussed in the lesson Extended Transport Control. Repeat the same step for system TRN. Ask the students how they would include the TRN system (that is intended for end-user training) in the SAP system landscape. Tell them that in our scenario the TRN system should look very similar to the PCC system but should receive some other development objects (such as a program to create training data). Point out that this goal can be achieved by creating a delivery route from QCC to TRN and a consolidation route from DCC to TRN. Confirm the Create Transport Layer dialog box when creating the consolidation route, with the proposed transport transport layer name ZTRN and description Bypass to ZTRN.
Approval Procedures When a transport request is released and exported from the development system (DEV), the import buffer of the consolidation system (QAS) is populated. The import buffer is a list of transport requests waiting for import. Once the transport request is imported into the consolidation system, the import buffer for all delivery systems (PRD) is populated.
&
* Export
Import
Transport Directory
A
Export
Import
a . Import
Transport Directory Figure 27: QA Approval Procedure
With the QA approval procedure, the buffer of the delivery systems is populated but the entries are marked as inactive. In other words, the transport requests cannot be imported until the responsible person marks 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 production systems by letting you check transport requests in the QA system before they are delivered to subsequent SAP systems. The SAP system for which the QA approval procedure is activated is called the QA system. When the QA approval procedure is activated, a transport request will only be imported into the delivery system or systems if all the QA approval steps are processed in the QA system For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
and the request has been approved. When you configure the QA system, you determine how many QA approval steps have to be processed for each transport request.
Figure 28: Configuring the QA Approval Procedure
The figureConfiguring the QA Approval Procedure shows you how to activate the QA approval process from the graphical editor and how to define the approval steps. Verification of the Transport Landscape Perform Tests on TMS
Once you have configured the TMS, you can perform the following tests to verify that there are no technical problems with the TMS configuration: RFC connection test Transport directory check Transport control program (tp) check Since the transport domain controller communicates with the other SAP systems in the domain using RFCs, check the RFC connections between the SAP systems in the domain. To check this step, from the Systems screen of the s t m s , select an SAP system from the list and choose SAP system —► Check —*■ Connection Test. This step verifies communications in both directions, to and from the domain controller. Since exports physically write files to the file system level and imports read and update these files, verify that the transport directory is available and has the appropriate file system level permissions. To check this step, from the Systems screen of the s t m s , choose SAP system —*• Check —> Transport Directory. This action creates, reads, and deletes a file to each of the transport directory subdirectories and returns a report on the success or failure of all subdirectories. If you receive any errors, make the appropriate corrections at the file system level. Since exports and imports are physically executed by the operating system level program tp, verify that the tp program and its parameter configuration are consistent. To check this step, For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
from the Systems screen of the s t m s , choose SAP system —> Check —> Transport Tool. This step executes tests verifying the tp interface, the transport profile, the RFC destinations, and connection to the databases and returns a report of the results.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 2 Exercise 1 Verify the Transport Landscape
Business Example
As an SAP administrator, you want to change the configuration of your transport domain. Before doing this exercise, verify the existing configuration. Verify the Transport Domain
Review the transport domain configuration. 1. To determine the transport domain name, logon with the following details: Data
Data Value
User ID
Course ID-##
Client
100
Development System
DCC
2. Determine which SAP systems are in the domain. 3. Determine which SAP system is the transport domain controller and whether or not a backup domain controller is configured. Determine also whether any virtual systems are configured. 4. Determine whether or not all systems belong to the same transport group. Review Transport Routes
Review 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 SAP system landscape? 3. List the SAP systems or systems that are considered consolidation systems. 4. Which SAP systems or systems are considered delivery systems? Verify QA Approval Procedure
Verify the configuration of the QA approval procedure. 1. Is the QA approval procedure selected? Which SAP system is configured as the QA system? 2. Who is responsible for approving transport requests? Verify TMS Configuration
Verify the technical configuration of the TMS.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
1. The domain controller uses RFCs to communicate with the SAP systems in the domain. Verify the RFC communications between QCC and the domain controller. 2. ‘Exports' physically writes files to the file system level directories and ‘Imports' reads and updates these files. Verify that the directory is available to the DCC, QCC, and PCC systems and that the appropriate file system level permissions are set. 3. The operating system level program tp executes the exports and imports. Verify that the tp program and its parameter configuration are consistent and that tp can access the DCC, QCC, and PCC databases.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 2 Solution 1 Verify the Transport Landscape
Business Example
As an SAP administrator, you want to change the configuration of your transport domain. Before doing this exercise, verify the existing configuration. Verify the Transport Domain
Review the transport domain configuration. 1. To determine the transport domain name, logon with the following details: Data
Data Value
User ID
Course ID-##
Client
100
Development System
DCC
a) In the Command field at the top left of the screen, enter s t m s . The name of the transport domain and the SAP system where you signed on displays. In this case, d o m a i n _ e c c and d c c . 2. Determine which SAP systems are in the domain. a) Enter s t m s in the Command field at the top left of the screen. b) From the Transport Management screen, choose Overview —> Systems. The SAP systems d c c ,QCC, p c c ,PC2 , and t r n display. 3. Determine which SAP system is the transport domain controller and whether or not a backup domain controller is configured. Determine also whether any virtual systems are configured. a) Enter s t m s in the Command field at the top left of the screen. b) From the Transport Management screen, choose Overview —> Systems. c) Examine the icon in the column displaying the system type (Column heading Typ or TMS System Type). This icon shows the system status. d) To compare icon status, either highlight the Typ icons or select the Legend icon. Either the development system DCC or the production system PCC is the transport domain controller. The quality assurance system QCC is the backup domain controller. The SAP system PC2 is an external system. The SAP system TRN is a virtual system. 4. Determine whether or not all systems belong to the same transport group.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
a) From the System Overview screen of transaction Groups.
stm s,
choose Goto —> Transport
This view displays a hierarchical list of the TMS configuration sorted by the SID within the group that is within the domain. There is only one domain. For example, d o m a i n _ e c c . There are two transport groups, g r o u p _ d c c and e x t g r p _ d c c . Review Transport Routes
Review transport domain and transport routes. 1. View the current transport domain and its transport routes. a) Enter s t m s in the Command field at the top left of the screen. b) From the Transport Management System screen, choose Overview —► Transport Routes to show the Display Transport Routes screen. If the display is too small, you can use the Zoom In icon. 2. What transport layers and transport routes have been defined for this SAP system landscape? a) On the graphical editor, the lines connecting the SAP systems represent the transport routes. The lines represent the following: •
The standard transport layer, ZDCC, exists as a consolidation route from DCC to QCC for the transport of customer objects. You know that ZDCC is the standard transport layer because it displays in the DCC system box.
•
The transport layer, SAP, exists as a consolidation route from DCC to QCC for the transport of SAP-delivered objects.
•
The transport layer, ZTRN, exists as a consolidation route from DCC to TRN for the transport of special customer objects that should not follow the standard transport layer.
.
There are delivery routes from QCC to PCC, from QCC to PC2 and from QCC to TRN
3. List the SAP systems or systems that are considered consolidation systems. a) QCC and TRN are consolidation systems, because they are target systems of a consolidation route. 4. Which SAP systems or systems are considered delivery systems? a) PCC, PC2, and TRN are delivery systems, because they are the target system of a delivery route. Verify QA Approval Procedure
Verify the configuration of the QA approval procedure. 1. Is the QA approval procedure selected? Which SAP system is configured as the QA system? a) Enter s t m s in the Command field at the top left of the screen for the QCC system. b) From the Transport Management System screen, choose Overview —► Transport Routes. Notice the Stamp of Approval icon in the lower left corner of the QCC system in the flowchart. This icon defines the QA approval procedure as selected and QCC as the QA system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
2. Who is responsible for approving transport requests? a) On the Display Transport Routes screen, double-click the q c c system. Notice that the Delivery after confirmation checkbox displays as selected. b) To Display the TMS Approval Procedure screen with the configured approval steps, choose Procedure. Notice that the system displays the approval steps To be approved by request owner and To be approved by department as selected.
>
Note: To be approved by system administration, you need the authorization value TADMforthe authorization object s _ C T S _ a d m i (CTS_ADMFCTfield).This authorization value is in the object s _ C T S _ a d m i n by default.
Verify TMS Configuration
Verify the technical configuration of the TMS. 1. The domain controller uses RFCs to communicate with the SAP systems in the domain. Verify the RFC communications between QCC and the domain controller. a) Enter s t m s in the Command field at the top left of the screen. b) From the Transport Management System screen, choose Overview —> Systems. c) Highlight the q c c system and choose SAP System —> Check —► Connection Test. If the systems can communicate using RFCs, you receive the message Connection to System QCC (host ) OK. If you highlighted the whole column System or System Name in the System Overview screen that indicates that the system would perform the test on every real SAP system of the transport domain. 2. ‘Exports' physically writes files to the file system level directories and ‘Imports' reads and updates these files. Verify that the directory is available to the DCC, QCC, and PCC systems and that the appropriate file system level permissions are set. a) Enter s t m s in the Command field at the top left of the screen. b) From the Transport Management System screen, choose Overview —> Systems. c) Highlight the DCC system and choose SAP System —> Check —> Transport Directory. The system attempts to write a file to each subdirectory of the transport directory, reads the file, and then deletes it. The returned screen displays the results of this test. A green check mark indicates that the test executed successfully. You can expand the display list to see the individual tests. d) Repeat the test for the QCC and the PCC system. If you highlighted the whole column System or System Name in the System Overview screen that indicates that the system would perform the test on every real SAP system of the transport domain.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
3. The operating system level program tp executes the exports and imports. Verify that the tp program and its parameter configuration are consistent and that tp can access the DCC, QCC, and PCC databases. a) Enter s t m s in the Command field at the top left of the screen. b) From the Transport Management System screen, choose Overview —► Systems. c) Highlight the DCC system and choose SAP System —> Check —► Transport tool. The system runs some consistency and connection tests on the transport program tp. The returned screen displays the results of this test. A green check mark indicates that the test executed successfully. Expand the display list to see the individual tests. d) Repeat the test for the QCC and PCC system. If you highlighted the whole column System or System Name in the System Overview screen that indicates that the system would perform the test on every real SAP system of the transport domain.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
LESSON SUMMARY
You should now be able to: •
Identify the basic configuration steps of the Transport Management System (TMS)
•
Set up a transport domain
•
Configure transport routes
•
Configure QA approval
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 2 Lesson 2 Creating Extended Transport Control
LESSON OVERVIEW
This lesson describes various facets of extended transport control and their configuration. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Configure the extended transport control
Transport Target Groups Using SAP standard transport control it is not possible to transport a transport request from one development system into multiple QA systems in an easy way. The reason is that it is not possible to create two transport routes with the same transport layer from one SAP system. Since every repository object is assigned (through a package) to a certain transport layer, it follows that a transport request can only have one target system. Transport Target Groups
The solution for the problem stated previously is to create a transport target group, which may lead to one or to one or more SAP systems.
To create a transport target group, use transaction s t m s and choose Overview —> Transport Routes and from there choose (using the change mode) Edit —► Transport Target Group —*■ Create.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Note: The name of the transport target group must start and end with a / symbol. When a transport request, which has a transport target group as target, is released, it will fill the import queues of all SAP systems in this transport target group. In the figure Transport Target Groups, all released transport requests that contain objects pointing to the transport layer ZDEV are ready for import into both the QAS system and the QA2 system. Client-Specific Transport Control Because some SAP system landscapes contain multiple clients in the development and quality assurance systems, it is a challenge for the TMS administrator to maintain consistent (clientspecific) customizing across the landscape. Different SAP systems and different clients within an SAP system may need to receive changes at different times, depending on quality assurance approval and acceptance procedures. Communication errors between customizing project leaders and TMS administrators can inadvertently cause inconsistencies in the configuration settings of certain clients. Because most customizing is client-specific, during the scheduling of an import process, the import scheduler prompts the TMS administrator for a target client. The administrator would need to schedule manually the imports for the different clients. This situation occurs based on instructions from customizing project leaders; you record which transport requests have been imported into which clients. Extended Transport Control Features
TMS offers the Extended Transport Control — also known as Client-specific Transport Control (CTC) — whereby the administrator can automate the process by: •
Client-specific transport target groups
•
Client-specific consolidation routes
•
Client-specific delivery routes
Client-specific transport targets The transport targets of consolidation and delivery routes do not just specify an SAP system, they also specify a client. Client-specific transport targets are entered in the form: . (for example, qas .100). Transport target groups combine several client-specific transport targets under a symbolic name. You can specify transport target groups when you define consolidation and delivery routes. To differentiate them from traditional transport targets, start and end the names with the / symbol (for example, / europe O I/). Note: In the context of client-independent transport routes, transport target groups were already discussed. The concept of transport target groups and client dependent transport routes can easily be combined. Client-specific consolidation routes For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
For each transport layer, the consolidation routes determine where changes made in the SAP system are transported to after the transport request has been released. If you have activated extended transport control, then the transport target can be a specific client in a target system or a transport target group. If you do not activate extended transport control, the transport administrator has to specify the correct target client at the time of import. Client-specific delivery routes Delivery routes determine whether transport requests are to be flagged for import into subsequent SAP systems/clients, after they have been imported into an SAP system. If you have activated extended transport control, then you can set the delivery routes as client-specific. This step makes it possible to supply several clients in one SAP system in sequence. You can also specify a target group as the target of a delivery route.
Figure 30: Extended Transport Control Using Client Dependent Transport Routes Training Landscape
In the Extended Transport Control using Client Dependent Transport Route figure, objects pointing to the transport layer ZDCC will be imported (through transport target group / D C C / ) into QCC client 100 and DCC client 200. For example, client 200 in DCC could be a client for functional tests. After QA approval in the QCC system (client 100), the objects are forwarded to PCC client 100, PC2 client 100, TRN client 100, and QCC client 200. Extended transport control makes daily transport tasks easier and increases security. Extended transport control also reduces the need for communication between project leaders and SAP system administrators, because the transport routes can now be configured completely. No additional details about the target client are given at the time of import. To take advantage of this function, in the transport program profile, explicitly set the (tp) parameter CTC (client-specific transport control) to TRUE (value of 1). The default value is FALSE (value of 0), which deactivates the extended transport control. This step is also done automatically, when choosing a client-specific transport target group.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
A
Caution: After activating the CTC, you can use the normal system-to-system transport or client-specific transport routes, but not a mixture of both types of connections in the same SAP system landscape. When using client-specific transport routes, specify the clients when defining the source target systems.
The standard transport layer (Z) determines the default transport target of the transport requests. When you use Extended Transport Control, you can set a different standard transport layer for individual clients from that set in the SAP system. You can forward customizing requests from different clients into different transport targets. The client-specific standard transport layer is also the default transport layer for new packages that have been created in a client. If you accept this default, then the cross-client objects that have been created in cross-client customizing are transported along the same route as the corresponding client-specific customizing.
»
Note: This scenario contradicts SAP's recommendation that all customizing/development changes originate in one single client. Client-specific transport layers are only used in circumstances, for example, as shown in the figure Extended Transport Control using Client Dependent Transport Routes.
Transport between Transport Groups and Transport Domains If you configure different transport groups in your SAP system landscape, there will be the need to perform transports between them. If there is more than one transport domain in your company, there might be the need to perform a transport from one transport domain to another domain. Transports between different Transport Groups
All the SAP systems in a transport domain share the same common transport directory. There are situations, in which separate transport directories are set up for different parts of the same domain. Multiple common transport directories are used in the following situations: •
An SAP system is connected to the domain through a slow or expensive network connection.
•
Strict security measures prevent allowing direct file system access from other SAP systems.
•
Dissimilar hardware platforms prevent the use of a common transport directory.
Within a transport domain, SAP systems that share a common transport directory form a transport group. The TMS supports transports between transport groups. The Transport Between Transport Groups figure outlines the procedure about transporting transport requests between different transport groups. (1) DEV. Transport Organizer: Export of transport request (2) QAS Import Queue: Extras —► Other Requests —*• Find in Other Groups (3) QAS Import Queue: Import of transport request
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Transport route
A
Transport Directory
Transport group A
Transport Directory
No c o p y o f log file s!
Transport group B
Figure 31: Transport between Transport Groups
After a transport request has been released from DEV, the request is marked for import into the target system. Be aware that this release happens in the transport directory of the DEV system (step 1). If the source and target systems are in different transport groups. To adjust the import queue of the target system from the Import Queue screen in the target system group, choose Extras —► Other requests —► Find in Other Groups (this step corresponds to step 2 in the figure Transport Between Transport Groups). TMS searches for requests for the selected SAP system in the import buffers (on operating system level) of all transport groups in the transport domain, and transfers the data files and cofiles belonging to the requests. Before the transfer of the data file, the transport request is marked in the import queue with a lightning icon that disappears after adjusting the import queue of the target system.
Note: There are limitations in regard to transporting between different transport groups. The transport logs displayed are specific to the transport group of the SAP system you are using, that is, they are not copied to the other transport directory. Transports displayed in the Change and Transport Organizers are also specific to the transport group of the SAP system you are using.
Transport between Different Transport Domains If you have configured multiple transport domains and want to make transports between SAP systems in different domains, you can use domain links. You can link: Domains (needs a permanent network connection) External systems For a domain link there must be a permanent network connection between the SAP systems in the two domains, similar to the connection between SAP systems within the same transport domain. Linking two transport domains with a domain link involves two steps. First, one transport domain controller has to request a link between the two transport domains. Then the transport domain
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
controller of the other transport domain has to confirm the link between the two transport domains. To request a transport domain link, enter transaction s t m s and choose Overview —*• Systems. In the SAP system overview, choose SAP System —► Create —► Domain Link. Enter the SAP system name, host name, and instance number of the transport domain controller you want to link to, and then confirm your entries. The SAP system generates the required RFC destinations automatically and sends the address data of the local transport domain controller to the transport domain controller of the other transport domain. To confirm a link between two transport domains, enter transaction s t m s and choose Overview —► Systems. In the System Overview, position the cursor on the transport domain controller where you requested the domain link and choose SAP System —► Approve. Confirm the prompt and distribute the configuration. Tasks Performed After Establishing a Domain Link
Make transports between SAP systems in different transport domains in the same way that you make transports between SAP systems in different transport groups; RFC is used to transfer transport files between the transport directories involved. Display transport logs of SAP systems in the other domain.
Note: Transport domains are independent administrative units. Change (such as transport route changes) only in the transport domain controller of the transport domain. Transport routes are not distributed between transport domains. You can, however, configure a route between SAP systems in different domains, but must configure it twice, once in each transport domain. The transport domains that are linked by a domain link must have different names. If you cannot operate a permanent RFC connection between SAP systems in the two transport domains, you can use external systems to make transports between the two domains. External systems are like virtual systems. However, for this type of SAP system, a separate transport directory is also defined. This directory can either be located on a disk partition that can be accessed by an SAP system in the other domain, or it is on a replaceable data medium, for example a DVD, memory stick or portable hard disk. The idea behind external systems is to reduce the problem of transporting between different transport domains to the problem of transporting between different transport groups in the same transport domain.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
D O M A IN A
D O M A IN B
External system
trans 1
Transport between transport groups
External system
trans ext
Transport between transport groups
trans 2
Figure 32: Transport between Transport Domains Using External SAP Systems
In the figure Transport Between Transport Domains Using External SAP Systems, you want to transport between the SAP systems DEI in DOMAIN_A and DE2 in D0MAINJ3. In transport domain DOMAIN_A, you create an external system called DE2 (pointing to the transport directory trans_ext). In transport domain DOMAIN_B, you create an external system called DEI (pointing to the transport directory trans_ext as well). In addition in both transport domains define a transport route between these two SAP systems. Configure the host of the SAP system DEI so that they can access the directory trans_ext. In the same way, the SAP system DE2 in the domain DOMAIN_B must be able to access the directory trans_ext. After you export a transport request from DEI to trans_l, you perform a transport between transport groups in DOMAIN_A. As a result, data files, cofiles, and the buffer entries for DE2 exist in trans_ext. Next, perform a transport between transport groups in DOMAIN_B so that all necessary data is sent to the transport directory trans_2. Then you can perform the import into DE2. To configure an external system, log on to the SAP system that is the transport domain controller and enter transaction s t m s . In the SAP system overview that appears choose SAP System —*• Create —> External System. Enter the path and a short description of the transport directory. Enter the transport directory path for the specific platform and relative to the communications system. The transport domain controller is proposed as the communications system. Save your entries and confirm the distribution prompt. Related Information: Transport Control There is additional information concerning the setup of the TMS in the online documentation for SAP NetWeaver 7.31. Choose Application Help —> Function-Oriented View —>Solution Life Cycle Management —> Software Logistics —> Change and Transport System —> Transport Management System (BC-CTS-TMS).. The following SAP Notes may be helpful: •
SAP Note 556734: FAQ Transport: Set up and further information
•
SAP Note 28781: Central transport directory NT/UNIX
•
SAP Note 83327: Setting up transport system in heterogeneous system group
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
LESSON SUMMARY You should now be able to:
•
Configure the extended transport control
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 2
Learning Assessment
1. Which statements are correct? Choose the correct answers. | A A transport domain can only consist of SAP systems sharing the same transport directory. B A transport group consists of SAP systems sharing the same transport directory. | C An SAP system landscape always consists of SAP systems sharing the same transport directory. D TMS supports one transport directory within a single transport domain. E A transport domain contains at least one transport group. 2. Which statements concerning transport routes are correct? Choose the correct answers. | A SAP distinguishes between consolidation routes and delivery routes. B SAP distinguishes between export routes and import routes. | C If you want to export transport requests from an SAP system, there must be at least one consolidation route starting from this SAP system. D If you want to export transport requests from an SAP system, there must be at least one export route starting from this SAP system. E If you want to export transport requests from an SAP system, there must be at least one delivery route starting from this SAP system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
3. Which of the following transport routes are available in TMS? Choose the correct answers. | A Consolidation route B Export route C Import route D Delivery route E Standard route. 4. Which of the following QA approval steps are available in TMS? Choose the correct answers. | A To be approved by department B To be approved by request owner C To be approved by system administration D To be approved by solution manager E To be approved by TMSADM 5. Which of the following extended transport control scenarios can be set up in TMS? Choose the correct answers. | A Client-specific consolidation routes B Client-specific delivery routes C Client-specific target domains D Client-specific target groups E Client-specific domain link
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 2
Learning Assessment - Answers
1. Which statements are correct? Choose the correct answers. | A A transport domain can only consist of SAP systems sharing the same transport directory. [x j
B A transport group consists of SAP systems sharing the same transport directory. | C An SAP system landscape always consists of SAP systems sharing the same transport directory. D TMS supports one transport directory within a single transport domain.
[~xj E A transport domain contains at least one transport group.
2. Which statements concerning transport routes are correct? Choose the correct answers. [x ] A SAP distinguishes between consolidation routes and delivery routes. B SAP distinguishes between export routes and import routes. [x ] C If you want to export transport requests from an SAP system, there must be at least one consolidation route starting from this SAP system. D If you want to export transport requests from an SAP system, there must be at least one export route starting from this SAP system. E If you want to export transport requests from an SAP system, there must be at least one delivery route starting from this SAP system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
3. Which of the following transport routes are available in TMS? Choose the correct answers. |~xj A Consolidation route B Export route C Import route |~xj D Delivery route E Standard route.
4. Which of the following QA approval steps are available in TMS? Choose the correct answers. |~xj A To be approved by department |~xj B To be approved by request owner |~xj C To be approved by system administration D To be approved by solution manager E To be approved by TMSADM
5. Which of the following extended transport control scenarios can be set up in TMS? Choose the correct answers. |~xj A Client-specific consolidation routes |~xj B Client-specific delivery routes C Client-specific target domains |~xj D Client-specific target groups E Client-specific domain link
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
UNIT 3
Transport Request in SAP Customizing and ABAP Development
Lesson 1 Customizing SAP Systems
67
Lesson 2 Managing Transport Requests for Customizing Exercise 2: Create and Assign Transport Requests for Customizing
75 83
Lesson 3 Describing the Customizing Process Flow Exercise 3: Perform Business Configuration with IMG
87 95
Lesson 4 Describing Change Management for ABAP Development Exercise 4: Create a Package for a Customer Development
102 113
Lesson 5 Developing Customer Programs
119
Exercise 5: Create a Customer Program
121
Lesson 6 Modifying SAP Objects
136
Exercise 6: Modify an SAP Program and an SAP Table Structure
143
UNIT OBJECTIVES
•
Explain customizing from a business and technical perspective
•
Display IMG projects
•
List tools for managing transport requests
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
Create transport requests with tasks
•
Perform customizing procedures
•
Distinguish cross-client from client-specific customizations
•
Plan change management for customizing
•
Plan change management for ABAP development
•
Distinguish between customizing and development
•
Create a customer program
•
Perform modifications on repository objects
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 3 Lesson 1 Customizing SAP Systems
LESSON OVERVIEW
This lesson explains the advantages of SAP system customization and describes some of the ways in which it can be achieved. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Explain customizing from a business and technical perspective
•
Display IMG projects
Customizing from a Business and Technical Perspective Definition of Customizing Sales and Distribution
Materials Management
Production Planning
Figure 33: Definition of Customizing
Customizing adapts the SAP software to meet a company’s individual business requirements by setting up the business transactions the company requires in the SAP system. To illustrate the kinds of business transactions, an enterprise may need to customize in an SAP system consider the example of an international company that sells video equipment wholesale. To enable customers at a particular outlet to place a wholesale order for video equipment, the company must customize the SAP system to recognize the company’s structure. This business transaction could encompass the following list.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Examples of Customizing in SAP Systems
•
Defining a sales organization
•
Defining distribution channels
•
Assigning distribution channels to the sales organization
•
Defining pricing conditions and tax determination rules
•
Assigning general ledger accounts
In this example, the definition of a sales organization and the distribution channels are done. This customizing is an example for the definition of the individual organizational structure of a company. This kind of customizing is typically stored in client-specific customizing tables. This customizing is also known as a client-specific customizing. Client-specific customizing affects only one particular client. Another type of customizing is customizing that adjusts the execution of programs such as the pricing conditions or the tax determination rules. This customizing is mostly also client-specific, but some customizing activities insert entries in client-independent tables or generate some repository objects (tables or programs). This customizing is known as cross-client customizing. Cross-client customizing affects all clients in the SAP system. Customizing from a Technical Perspective
The figure Customizing from a Technical Perspective shows the technical representation of customizing in the SAP system. Table T005 MANDT LAND1
100 100
View V T005 MANDT
AT AU
100 100
Table T005X
LAND1 AT AU
MANDT LAND 100 100
AT AU
Country A3 Ganaiai data AJtarn.count'y uv
Table T005T MANDT
SPRAS
LAND1
LANDX
100 100 100 100
D D E E
AT AU AT AU
Osterreich Australien Austria Australia
name Matonatty HatonaKy (Long) varycta country koy
PropoitMc EU Country Tina K j c r o t nama Procadura CacCJi Goods Ind. Addiasc fonrac
tool AuKrata Auctrata AuRraUn [AadMfan ATS
'm m l IAXAC
foc»1
^ | Lanouaga Kav Hard currency
EN CngMi
ISO coda s o coda 3
AC »r«
Pint Country Mi
Figure 34: Customizing from a Technical Perspective
Customizing activities typically create or change entries in multiple client-specific tables. This step is frequently done through table views. A table view is a virtual table, which presents data that is physically stored in one or multiple tables. You can compare a table view with a view that is used in an SQL database. The different customizing tables of a table view can be related to each other by foreign keys. The table entries created with the help of table views are identified by the key fields of the respective table. For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
In the figure Customizing from a Technical Perspective the table view for maintenance Global Parameters of Countries is shown. The country parameters are maintained with the help of view V_T005. All the different attributes for a country, such as, name, nationality, ISO code, date format, and decimal notation are maintained. These parameters are stored physically in different tables. For example, general country values in table T005, the country names in different languages in table T005T and the decimal point and date format in table T005X. The customizer does not need to care about the technical storage of the customizing, the customizer only has to maintain the information in the table view. The table maintenance can be accessed directly with the IMG or even with a generic table maintenance transaction as transaction SM30.
IMG Projects Perform customizing using the SAP Implementation Guide (SAP IMG). SAP systems provide a huge variety of different business processes that can be adapted to the individual needs of a customer by customizing. An SAP ECC system contains several 10.000s of customizing tables. The customer is guided through this customizing with the help of the IMG. An SAP system is delivered with a complete IMG for all processes available in the SAP system. This IMG is known as the SAP Reference Implementation Guide). The IMG can be accessed through transaction s p r o . S-luclure v S f f CuMomuira impiomonealton Ouie-cL i Actoete Uuslness f unctions sap ru«r»VA*v«r iX General Scltmo s [~ i SetCouril'ies Of Oeltre C o u r*** m mvSAP Srstern* LJ- (*/ SpaiDi Countries in mySAP Systems (C PM. S“ M. SCM. ("V Set Country Specdc Cleeks FX (£► Insert Htgiunt 1). (jp Dafli * County Codes (£> country Codes Tctophore Dcdrvc Evccpsonc [ i CuunlrvCodes - ledM. Urine Lweplxins LX Dartre Mnnila Talapnnne PrnpectlAA t> l_ i BetGeoccdmo b Currencies Ft. (Ja Cher.ktlreMnf MMAAiimmarl 1Jt <$► Maintain CMenoar (Ja WAintem Cslenoer tor Japan t> L i lime Zones !• [_i Field Olsplas Cnsractsnslks L i CiA Bettmo Vanantc tor Help
Adddonar lr»orma#on Cross-Cliert
CliArd-Sper «f Client.Spec Pc Client Spec tic Clierd-Bpet Ic Client-Spec *c Client 8pot Ac Client-SperAc Cllem-Spetdr.
Clierd-ftper.de Crose-CIlert Cross-CIlert
Cross Cllert
I---------------------- 1--------- --------------- 1------------------------ 1 Activities Access Customizing transactions
IMG Description
Project Management
• Concepts • Recommendations • Requirements • Activities
■ Status • Scheduling • Resources • MS Project for enhanced planning functionality
Project Documentation * Structured by note • types • MS Word • as a text editor ■ SAP Office folders
Figure 35: Using the IMG for Customizing
The IMG provides a hierarchical list with all possible customizing activities in that SAP system. This customizing is grouped by modules and ordered in the sequence in which the individual activity has to be performed. The IMG does not only show and group all customizing activities. The IMG also provides documentation on each customizing activity. This documentation explains the customizing activity that can be executed in this IMG node. Each customizing activity is classified into different areas. For example, if you are interested in which customizing activity is cross-client, you can use the SAP menu: enter transaction s p r o and then choose Additional Information —> Technical Data —> Client-Dependence. There is also a classification on language dependency and on transport type that can be displayed.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Apart from these tools for accessing customizing activities, displaying customizing documentation, and displaying customizing classification the IMG also provides tools for project management and project documentation. These tools support the project administration and project control out of the IMG. The SAP Reference IMG is split up into different areas. SAP Reference IMG
FI
SD Project IMGs
CO
MM
PP
HR
PS
...
MM PS
Project View
CO
CO
FI
FI
Project 002 Project 001
Project 002 View (required activities)
Figure 36: Customizing Projects from the IMG of SAP ECC
If a customer is setting up a new project for adoption of the SAP system, only some areas are in the scope of this adoption project. The customer can use a project IMG. A project IMG is the Implementation Guide for a specific customizing project. It contains all the customizing activities, which have to be performed in that project. You can determine the project scope of a project IMG by countries, components, or customizing activities. A project IMG is based on the SAP reference IMG, which can, for example, be reduced to the project scope by selecting countries and components. When defining a customizing project, customers select the functions they require in the different SAP areas and components. These functions are used to generate the project IMG. All relevant customizing transactions, project-specific or cross-project documentation, and projectmanagement information are then located in the subsets of the SAP reference IMG, known as project IMGs. Do all customizing activities directly within the project IMG. The project IMGs can be changed at any time through regeneration. The respective previous IMG is then overwritten. However, status information and project documentation is not lost. Within a project IMG it is possible to generate project views that restrict the extent of customizing, for example, to different levels of necessary activities. So it is possible to show within an IMG project view only the activities that are classified as mandatory and in a second IMG project view the activities that are classified as optional. The project IMGs are cross-client, that means the project IMG is visible in all clients. To access the IMG project definition, use the transaction code
s p r o _ a d m in
.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Project m anagem ent:
Project ABC
C reate custom izing projects and project views Define project scope and duration Assign team m em bers to the project Define project language and type o f docum entation Define and m aintain options
Project work: • Perform custom izing activities • Docum entation
Figure 37: Projects in Customizing
Depending on the scope of a customizing project, many different customizing activities are required. These customizing activities are done by different project members that are working on the implementation of a specific area. To make sure that everyone is working efficiently together, customizing projects need a clear organizational structure and responsibilities. The customizing and transport tools support the task sharing between the project leader and the project members. The customizing process is based on clearly-defined user roles. Each role has its specific areas of responsibility. The tools structure and organize the implementation activities. Tasks of the Project Leader
The project leader is responsible for defining and managing the project. The project leader's responsibilities include IMG projects used in the following ways: Create the customizing IMG projects and the project views Define the project scope and duration of the IMG project Assign team members to the IMG project (allow who is permitted to do changes) Define the IMG project language and type of project documentation Define and maintain IMG project options Customizing Team Members Project Work
Because you can see with the use of IMG projects, many of the general project administration tasks can be done inside the SAP system. The customizing team members do their project work in the following ways:
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
Perform customizing activities within the project IMG
•
Create documentation inside the project IMG
Any number of project team members can be assigned to each project. The project leader makes this assignment. The assigned project team members and new project team member assignments can be managed in transaction s p r o _ a d m i n . SAP Solution Manager in Implementation In this lesson so far, the IMG offers many tools and documentation that can be used for supporting the implementation process. However, if you set up and plan an implementation project, you have to manage all the different project phases, which appear in the following list. Different Phases of an Implementation Project
•
Project preparation
•
Business blueprint
•
Realization
•
Final preparation
•
Go live
•
Support For the coverage of these project phases, SAP offers the AcceleratedSAP / Value SAP method. The process of customizing the SAP system can be controlled and accelerated using the AcceleratedSAP / Value SAP method. Value SAP represents a framework of tools, content, and methodology to support the entire live cycle of a solution. Since SAP Solution Manager 2.2 these Value SAP tools are transitioning to the SAP Solution Manager. The SAP Solution Manger is the portal for implementation, operation, and continuous business improvement for SAP applications. The AcceleratedSAP / Value SAP CDs that were provided in the past with those methodologies and tools are now replaced and extended with the implementation content inside the SAP Solution Manager. It is now possible to run project with the tools inside the SAP Solution Manager (see SAP Note 576877). So, the SAP Solution Manager is now the platform for the entire project team.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
SAP Solution Manager in Implementation Project phase
Project preparation
(A
Business blueprint
Project definition
Define business blueprint
Define SAP system landscape
Set up of development landscape
ra -*-»
u
Customizing synchronization Configuration
1
o
Final preparation
Realization
Go live & support
End user training and documentation
Developments
Data transfer
Authorization
o
Testing
Cross functions
Project administration Issue tracking / monitoring / reporting Roadmaps
Figure 38: SAP Solution Manager Implementation Area
Features of the SAP Solution Manager in Implementation
•
Project Administration/Project Definition supports you initially in setting up your project during project preparation and enables you to carry out major administrative tasks such as the definition of project standards during the entire project.
•
In the SAP Solution Manager, you can centrally define and manage your SAP system landscape centrally, relevant for your implementation or template projects. Doing this step allows interaction with a related SAP system landscape; for example, during configuration and testing.
•
The definition and documentation of your project scope in business blueprint is accelerated through the Business Process Repository providing latest available implementation content. The purpose of the business blueprint is to document in detail the scope of business scenarios, business processes, and process steps of your implementation project from a business and technical perspective.
•
During configuration, configure the business requirements specified in the business blueprint phase in the related SAP system landscape. The SAP Solution Manager as central platform for your project team provides the access to the related project implementation guides and integrated use of other customizing technologies such as Business Configuration Sets (BC Sets) and customizing distribution.
•
The customizing distribution used with the SAP Solution Manager helps to control customizing changes centrally across the related SAP system landscape of your implementation project.
•
Testing functions support test coordinators to create test cases and test plans centrally reflecting sequence and integration tests. Testers can centrally execute their test packages, also leveraging existing test technologies for automated testing such as eCATT.•
•
The latest available roadmaps representing the standard SAP implementation methodologies are provided through the SAP Solution Manager. With the SAP Solution Manager, you can
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
track status, issues and/or upload your project-specific accelerators along the work packages and tasks of your implementation project. Implementation projects in an SAP system landscape today affect more than one SAP system (such as, SAP CRM server and SAP ECC). During that kind of project, customizing in more than one SAP system is required. The SAP Solution Manager in Implementation supports project maintenance and administration in an SAP system landscape. Implementation projects that affect a special SAP system landscape can be defined centrally for this SAP system landscape and then the project IMGs in the different SAP systems are generated. The SAP Solution Manager for Implementation provides the tools for supporting customizing projects in an SAP system landscape of multiple SAP systems. For instance, the SAP Solution Manager change manager can be used. Tools Supported by the Change Manager in SAP Solution Manager
Tools of the change manager in SAP Solution Manager support the following: •
Implementation projects
•
On demand development
•
Maintenance tasks
•
Hot-fix tasks
This list includes the transport tracking and approval tasks that are necessary in a productive system landscape with ongoing implementation project and maintenance tasks. LESSON SUMMARY
You should now be able to: •
Explain customizing from a business and technical perspective
•
Display IMG projects
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 3 Lesson 2 Managing Transport Requests for Customizing
LESSON OVERVIEW
This lesson explains how to manage transport requests for customizing. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
List tools for managing transport requests
•
Create transport requests with tasks
Tools for Managing Transport Requests
The Implementation Guide is the main customizing tool. It represents the central entry point for all project members for carrying out the customizing activities. Customizing takes place from the created IMG project, which contains all the customizing activities for a specific project scope in a hierarchical list. If the customizing is changed, record these changes. The Transport Organizer (transaction SE09 / S E 1 0 ) records the customizing changes in transport requests. For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
It is an information source in the Transport Organizer that records all changes and modifications made to Repository objects and customizing settings during a development project. If the customizing is finished, the transport request can be released to the transport system for transferring the changes to other SAP systems in the SAP system landscape. The function for recording the changes made during customizing, is integrated in the customizing and table maintenance transactions. The Transport Organizer is called from within these customizing transactions for recording the changes into transport requests. The Transport Organizer is fully integrated in the Transport Management System (TMS). &
R equest/T^sk
E dit
&
g o to -
S e ttin gs <1
Environm ent
System
5 -1
O
y e lp C
l f i C
I
( U
G
H
O
H
Transport Organizer
□ User
r CATON
C
R eq u est T y p e
Global In fo rm a tio n y
T ran sp o rt Proposals
^ ^ v C u s t o m e n g Request?"*,.
SD
W o rk b e n c h Requests,^*' □
cco 020
T ransport or copies Relocations
6
^
Transports
1
^
R epars
R e q u e st S ta tu s (y Modifiable
C
(a
-
Released
D splay
Figure 40: Transport Organizer Used for Customizing
The Transport Organizer is used to create, manage, release, and analyze transport requests that record customizing or Repository changes. To access the Transport Organizer, you can use the transaction code S E 0 9 . Information Provided by the Transport Organizer
Transport requests for customizing Transport requests for repository objects Global transport information All customizing requests that belong to a specific user are displayed according to a set of standard selection criteria in the Transport Organizer. The selection options include user, transport request type, transport request status, and date. An example of this selection criteria is shown in the figure Transport Organizer Used for Customizing. In the Transport Organizer the screen area Global Information is displayed. With the help of this area you can obtain a graphical cross-system overview on all transport requests. Within this area you can track if a transport was imported, for example, in the consolidation system. T ra n sp o rt Requests and Tasks Customizing mainly consists of client-specific table entries that are saved to transport requests of type customizing. A transport request belongs only to one user. It is possible that other users are also storing their objects in the same transport request. The owner of a transport request is For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
able to administer and release the request. For example, the owner can assign other users to the transport requests, release the transport request, and so on.
The Transport Organizer allows you to work with a team on a development or customizing project, and allows the changes made to the SAP system to be recorded. A transport request is used for transferring objects together into another SAP system. You can compare a transport request with a folder, which contains different documents (the customizing objects) and subfolders (the tasks). A transport request initially contains one task per member assigned to the transport request. Tasks are smaller units that are used by team members or customizers for recording the objects they want to transport. The changes a project member has done are stored in the tasks that the project member owns. A customizing object can be listed in several tasks belonging to the same transport request. Likewise, a team member can own several tasks belonging to a transport request. The recorded objects are only transported in the context of the entire transport request. This function is used to manage and control the distribution of changes within an SAP system landscape.
Recommendations to Manage Transport Requests
Use the following recommendations to manage your transport requests: The project manager or responsible person creates a transport request. The project members are assigned to the transport request by creating a task inside the transport request for each project member. The project members record their objects to their tasks.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Advantages in the Management of Transport Requests
The use of the transport functions leads to the following advantages for the management of transport requests: You as the project manager have control of all changes that are recorded in the transport request that you create.
m
•
Objects in tasks cannot be transported individually. They are only transported with the whole transport request.
•
With the release of the transport request the project leader is able to control when the objects are to be transferred to the other SAP systems in the SAP system landscape.
Hint: Create as few transport requests as possible by grouping the developers and customizers. Try to avoid creating a new transport request for each little change. It is much easier to handle transport requests when there are fewer of them.
T ra n sp o rt Request M anagem ent in IMG P rojects In this lesson you have seen so far how customizing changes are recorded to tasks and transport requests and how this step is done technically. You now have an idea of which organizational procedures during the creation and recording of transport request can help you obtain an overview of when the changes are transported. Now you see which functions the IMG projects provide for the assignment of transport requests to an IMG project.
Im p le m e n ta tio n P ro je c t A B C P ro je c t a ttrib u te s j— ►Activation of CTS
Project owner
C u s to m iz in g a c tiv itie s |— ►Transport request A I— ►Transport request B
D e v e lo p m e n t a c tiv itie s |— ►Transport request C I— ►Transport irequest D
Figure 42: Managing Transports in Projects
As of SAP R/3 4.6A, Project IMGs, project IMGs may be linked to the Change and Transport System (CTS). The transport requests created and assigned by the project leader contain smaller units called tasks that have been allocated to the project team members. In these tasks, the
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
changes made by the team members are recorded. A team member can also own several tasks belonging to a transport request. With the CTS functionality in the IMG projects it is now possible to link the transport projects to the project IMG in which the changes are done. This situation is possible by activating the project function inside the IMG project. The activation can be done inside the IMG project administration. If you want to use the CTS functionality in the IMG projects you have to activate the functionality in the IMG project first. IMG projects are cross-client. As a result, the CTS function may be separately enabled in different clients for the same IMG project. The figure Activation of CTS Project Functionality shows how to activate an IMG project. This activation can be done by changing the IMG project in the transaction s p r o _ a d m i n .
CTS Tasks that Affect the SAP System
When you activate the CTS project functions for an IMG project, you change the way the SAP system reacts as follows: •
You can assign transport requests to the project.
•
You can see this assignment in the request overview.
•
When you save the customizing changes in the Project IMG, the Transport Organizer proposes to make only those change requests that you have previously assigned to the project.
The assignment of transport requests to an IMG project can be done in two different ways. The first way is to assign the transport requests from the project administration (transaction S p r o _ a d m i n ). See the figure Assignment of Transports to CTS Projects . The second way is to assign a transport request to an IMG project and use the Transport Organizerto put the IMG project into the properties of the transport request. To use the second method enter transaction S E 0 9 , double-click the modifiable transport request and then choose Properties.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
C h a n g e : P r o je c t P R O JEC T_10: C o u n try S e ttin g s
®A*9Qn User...
project_io"
0As«gn Al Protect Tejm Mcrrtoers
Type
Customer^ Project
Country Settings
Pro). Teim Merrbef
Status vats
Keywords
Docurentaton Types
Transp. Racjjests
Cross-fief.
' __ 5
Current clent [^Protect Status Swftdv Setect Systems E )
fflfflK T
in
C
m
m
Otsctoy overview of project status swfiches
r
x
s e t t n a
Al ccnfgued transport targets System rfCC
“1
0®
Figure 44: Assignment of Transports to CTS Projects
In the import overview of the TMS, sort requests according to their assignment to projects, and import them. For more information on CTS project functions, refer to the online help documentation under h t t p : / / h e l p . sap. com /saphelp_nw73ehpl. In this URL, follow this menu path: Application Help —*• Function-Oriented View —> Solution Life Cycle Management —► Software Logistics —> Change and Transport System —>Transport Organizer —> Working with Projects. It is possible to transport projects separately as a unit containing several transport requests. Customizing projects should not overlap. However, during the release of transport requests, the system automatically checks whether the request's object list overlaps with the object lists of released requests from other projects that have already been released. Transporting Customizing Changes
Customizing transport requests usually contain changes to customizing. At the time the change is made in the SAP system, the keys that are identifying the table entry are stored in the transport For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
request's task. At the time when the transport request is exported, this transport request will extract the relevant table entries from the database of the SAP system and copies them to the transport directory. The content of the transport request always represents the customizing entries at the time when the transport request was released. Due to the dynamic access to table entries during customizing, both client-specific and cross client customizing are not protected from being overwritten. Table entries are locked while the customizing transaction is being used (by the enqueue work process), but they are unlocked as soon as the changes are completed and saved to a transport request. For additional information, see SAP Note 1916. Customizing changes can be logged. This is very often used for documentation such as who has changed a value of a customizing table. Transport requests only record the table keys at the time when a customizing entry is changed. From a customizing request, you can only obtain information on who has made the changes but no information about the state before and after the change. This information can be stored by activating the logging of customizing tables. To activate the logging of changes to customizing tables, use IMG logging through transaction code SCU3. Prerequisite for IMG Logging is the following: •
In Technical settings in ABAP Dictionary maintenance (transaction S E ll), the function log data changes have been selected for the respective customizing table or view.
•
The profile parameter rec/client is set for the appropriate clients.
Generally, all objects are transported to the target system in the state in which they exist in the source system. Objects transported from the source system overwrite objects in the target system that have the same names. Objects are deleted in the target system if they do not exist in the source system. For production systems, there are also some legal requirements in some countries that make it necessary to activate customizing table logging. Some legal requirements for activating the table logging can be found in SAP Note 112388. If not otherwise specified in the TMS configuration, the customizing settings are transported using the standard transport layer.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Create and Assign Transport Requests for Customizing
Business Example
Organize customizing within projects. For each group, PROJECT_## is already defined. However, to use the Change and Transport System (CTS), the project leader must first activate the CTS functions within the project. Check Project Scope
Review the scope of your project. 1. Log on with the following details. Check the scope of your project. Data
Data Value
System
DCC
Client
100
Project
P r o je c t ## (Replace # # with your group number)
Activate CTS for the Project and Assign Customizing Requests
Activate the CTS function for your project and create customizing requests. 1. In the Change: Project screen from the previous exercise, activate the CTS functions for your project. 2. Assign three customizing transport requests to your project. CTS Project Status Switch
As a final task, maintain the project status switches. 1. Verify that the project status switches for your project are correctly maintained so that the project can be transported into the QCC system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Create and Assign Transport Requests for Customizing
Business Example
Organize customizing within projects. For each group, PROJECT_## is already defined. However, to use the Change and Transport System (CTS), the project leader must first activate the CTS functions within the project. Check Project Scope
Review the scope of your project. 1. Log on with the following details. Check the scope of your project. Data
Data Value
System
DCC
Client
100
Project
Project ## (Replace # # with your group number)
a) Enter s p r o _ a d m i n in the Command field to review the definition of your PROJECT_##. b) Highlight your project.
p r o j e c t _##
and choose Project —*■ Display, or just double-click your
c) On the Change: Project screen, you can check the scope of the project by choosing Project IMG. Activate CTS for the Project and Assign Customizing Requests
Activate the CTS function for your project and create customizing requests. 1. In the Change: Project screen from the previous exercise, activate the CTS functions for your project. a) Choose Pencil for Display <-> Change to enter your project in change mode. b) Select the Transp. Requests tab. c) Choose Activate CTS functionality. d) In the Confirmation dialog box, acknowledge the CTS activation. e) In the Change: Project screen, choose Assigned CTS requests to assign customizing transport requests.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
2. Assign three customizing transport requests to your project. a) On the Request: Project screen, choose Create Request. b) In the Selection dialog box, choose Customizing request. c) On the Customizing Request screen, enter a short description to create a customizing request. Notice that the CTS project is already entered. d) Enter all project members that use this transport request. e) Save and repeat for each project while verifying that it contains a new transport request with a task for each transport request member. Notice that the SAP system generates a transport request name and a task name in the format of K9<5-digit number>. f) Repeat this procedure and create three customizing requests in total for your project. CTS Project Status Switch
As a final task, maintain the project status switches. 1. Verify that the project status switches for your project are correctly maintained so that the project can be transported into the QCC system. a) In the Change: Project screen, from the Transp. Requests tab, choose CTS project status switch for all configured transport targets. b) Choose Enter. c) Verify your project so that transport requests can be created and released as follows: Data
Data Value
SAP system
DCC
Client
100
d) Verify your project so that transport requests can be imported as follows: Data
Data Value
SAP System
qcc
Client
100
and
pcc
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
LESSON SUMMARY
You should now be able to: •
List tools for managing transport requests
•
Create transport requests with tasks
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Describing the Customizing Process Flow
LESSON OVERVIEW This lesson describes how to perform customizing procedures, distinguish different types of customizing, and plan for furture customizing. LESSON OBJECTIVES After completing this lesson, you will be able to:
•
Perform customizing procedures
•
Distinguish cross-client from client-specific customizations
•
Plan change management for customizing
Process Flow in Customizing In an SAP implementation where customizing and development changes are integral to the SAP system being available, execute projects in a structured environment using defined procedures to minimize the threat of downtime caused by program or business configuration errors. The goal of your project organization is to divide the large number of activities among the project team so the team members do not interfere with each other's work. Make sure that work logically belongs together, but is being performed by different team members. This process is carried out by dividing the tasks in a customizing project among three roles, each of which is responsible for performing certain tasks. Project Manager The project manager creates the transport requests and assigns the appropriate members to them. When a member is assigned to a transport request, the SAP system creates a task; the settings for each member are recorded in his or her task. For the transport to other SAP systems, the project manager can release the created transport requests. Customizer/Developer Customizers perform their customizing using the IMG and the developers perform their development mainly using the ABAP Workbench tools. They assign their work to their individual tasks in the transport requests assigned to them. For client-specific data, the customizers can copy their settings to the TEST client to test them. Both customizers and developers are authorized to release their own tasks in a transport request but are not allowed to release the transport request. TMS Administrator The TMS administrator uses the TMS to transport released transport requests to subsequent SAP systems in the SAP system landscape using the predefined paths.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Application consultants and employees in the department handle the roles of project manager and the customizers and developers. The project manager decides which customizing settings to perform and how to divide them among the project team members, who execute the customizing transactions. The TMS administrator is responsible for the transport between the SAP systems along the transport path after the transport requests are released to the TMS.
DEV Create transport requests and assign members
Perform customizing transactions from within the IMG Assign customizing settings to transport requests
Import transport requests into the target systems
Unit-test the contents of the task (client-specific customizing) Document and release the task containing customizing changes
Release/export transport requests
Transport directory
Authorizations exist to define a user's role
Complete change documentation Customizer
Project leader
Administrator
Figure 46: Customizing Procedure
The Transport Organizer and the Transport Management System are designed for supporting this task split. The sequence of the different customizing steps is shown in the figure Customizing Procedure. Customizing Steps
During normal customizing work, the sequence of the steps is as follows: 1. The project leader first assigns a transport request to a project and assigns the subsidiary tasks to the members involved. These members perform customizing changes that are recorded in the transport request. 2. After customizing work is completed, the members must release their tasks so that the transport request can then be released from the source system for export to the file system. 3. The transport request can now be imported into the subsequent SAP systems. Experience has shown that by utilizing these three clearly defined roles and instituting strict guidelines for the procedures and documentation of customizing, the overall customizing process is easier to manage and the chance of errors in production is greatly reduced.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Note: The authorization (security) administrator enforces these roles by assigning the appropriate authorizations to each user ID. For example, the customizer must be able to execute the assigned customizing transactions and be able to release his or her own tasks, but not be able to create or release transport requests. SAP delivers standard roles for the team leaders, team members, and TMS administrators. For additional details about authorization and role management, refer to SAP course ADM940.
Recording of Customizing Changes Project IMG
I*® B» ta®t a® »® ft®
Customizing transactions
... I .. I , . W CMitv-SMuk (J««W
Customizing settings in tables
h iK R ig o H
M t t CouiTi Ccoat C9«WTfC0«*t-TWiMnt C**»*Et Couny Con: T«m Dclro E»: iin M htIM M T *
A u to m a tic r e c o rd in g o f c h a n g e s
Client change option (SCC4) J
C h a n g e s w ith o u t a u to m a tic re c o rd in g
Transport request Figure 47: Recording of Customizing Changes
A customizing transaction is a transaction for setting customizing table entries. To use a customizing transaction, you do not have to know about the technical aspects of where and how a business object is maintained, or which transactions are used to access and change certain fields in specific tables. After the customizing settings have been changed using a customizing transaction, they need to be saved. Please note the following: •
When a client is configured to automatically record changes, the settings are automatically saved to a transport request managed by the Transport Organizer.
•
If the client is not configured for automatic recording of changes, the settings are saved but not recorded in a transport request. However, the changes can be included in a transport request manually. You can manually include the changes from the specific customizing transaction or from within the Transport Organizer.
All customizing transactions in the IMG also allow entries to be manually saved to a transport request.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Note: Some transactions are classified as manual transport. Changes done in these transactions must be manually added to a transport request for transport to their target system. In addition, some customizing transactions have transport steps that differ from those items indicated in the figure Recording of Customizing Changes. To view transport dependencies for items within the IMG, do the following: 1. Enter
spro
in the Command field in the top left of the screen.
2. Choose Additional Information —» Technical Data —> Transport Type. We recommend that all customizing changes originate in one client only and all changes be saved to transport requests. This control is established by the SAP system administrator and Client Change Options. Testing of Customizing
Testing of changes in the development system is very important. Only tested and error-free transport requests are released in the development system. The advantage of this method is that the amount of transport requests (only a few correction transports) and error corrections between the DEV and the QAS system are dramatically reduced, while the most errors are detected early before releasing a request and not later during testing in the QAS system. Before releasing a customizing transport request, perform a unit test to do the following: •
Test the functionality of the customizing within the transport request.
•
Verify that the content of the transport request is complete.
Maintaining a separate client for testing allows the following: •
True unit testing
•
Maintenance of test data without the risk of creating customizing-dependent data
Transaction SCC1 copies changes from one client to another based on the following: •
A task
•
A transport request
•
A transport request and its tasks
All customizing must be tested before production it two ways: unit testing and SAP system testing. Perform the unit testing first. Unit testing is the testing of individual customizing settings. SAP system testing is the testing of all customizing settings together. Unit testing is performed by the customizer and completed before the release of the transport requests. Unit testing typically requires application data. Because many customers find it advantageous to keep their customizing client free of application data, another client is created with the necessary application data for unit testing.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
The procedure for the unit test is the following. Before releasing a transport request, copy the recorded changes to a separate client for unit testing. To copy the contents of a transport request or one of the constituent tasks to another client within the same SAP system, use transaction S C C l.
After unit testing the tasks, the transport request can be released. Unit testing alone, however, is not sufficient for transporting customizing changes to production. After unit testing, the change needs to be tested with all other customizing settings in SAP system testing. This is done to ensure that all SAP system settings function properly together. In the SAP landscape, all customizing occurs on the OUST client but no application data exists in the OUST client. Unit testing occurs in the TEST client where application data does exist. A designated person is responsible for copying his work to the TEST client and must use the SCCl client. To do this step, the customizer must also have a user ID on the TEST client and use this procedure as shown in the figure Testing Customizing Transport Requests.
Figure 48: Testing Customizing Transport Requests
Note: When copying the contents of a task to the unit test client, do not release the task right away. Not releasing the task allows any errors identified during the unit test process to be corrected and assigned to the same task. Once a task is released, no further changes can be recorded to it. To copy the contents of a transport request from one client to another client, use Transaction SCCl. Log on to the target client, that is, the unit test client. Enter the source client and the transport request to be copied.
Note: If a transport request contains cross-client objects, these objects are not copied.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Releasing Customizing Transport Requests &
HeaJert/Tfjfc
goto
a
9 R Kt
jiUrjn
■]« h
ana o o co
he
®sc
Transport Organize: Requests
Cl
i
fr
U J- t$-
e ku Involving Cact CAIOO Olo.-’ .ln Cacao)
Transport Directory Transport files
Figure 49: Releasing Customizing Transport Requests*•
Promoting changes recorded in a transport request begins with releasing the relevant tasks. Releasing a task indicates that the owner of the task has completed customizing or development work that the unit testing is successful, and that the appropriate documentation is complete. Observe the following about the task: •
The task contains a recorded object.
•
The task has been documented.
•
The task is owned by the person releasing it or the person releasing it has the appropriate SAP system authorizations.
To release a task, execute the following procedure: 1. To enter the Transport Organizer, execute transaction SE09. 2. Choose Display. The request overview displays. The request overview displays. 3. To view all tasks in the specified transport request, expand the tree structure. 4. Position the cursor on the task you wish to release, and choose the Release icon. By releasing a transport request, you indicate that it has sufficient documentation, the changes recorded in it have been tested, and the changes are ready to be transported using the TMS transport routes. During the export process triggered by the release, the objects recorded in the transport request are copied from the SAP database to operating system level files in the transport directory. In addition, a record of the transport request is automatically added to the appropriate import queues of the SAP systems defined in the TMS. Hint: Only transport requests, which are transportable are exported when released.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Releasing and exporting a single transport request generates export logs and import logs when importing it into subsequent SAP systems. Testing in the quality assurance system and QA approval signoff are necessary before importing into the production system. To support the validation process and limit the technical and administrative overhead, we recommend to transport changes that belong to the same project together in a limited number of transport requests. This step is ideally done by assignment of tasks within the transport requests by the project leader or the person responsible for the transport.
Hint: To keep control, you must assign transport requests to a project. Doing so makes it easier to import and approve the project. Sometimes you want to merge transport requests. You can combine multiple transport requests into one single transport request. Merging requests can be done explicitly in the Transport Organizer by choosing Utilities —► Reorganize —> Merge Requests. Cross-Client Customizing In an SAP implementation different types of objects are involved in customizing or development change. Examples of objects used are as follows: •
Client-specific customizing Client-specific customizing typically involves customizing tables where the Client field is on the first position in the table key. For example, the customizing table T005 is used in the country customizing. The entries in that table only affect the client that is specified in the key field of the entry.
•
Cross-client customizing Cross-client customizing typically involves customizing tables without a client field in the key. An example of a cross-client customizing table is the table 7000 in which all clients that exist in an SAP system are stored.
•
Repository objects A repository object can be table definitions in the ABAP dictionary or programs and function modules.
To determine the client dependency of IMG transactions in a project IMG, from the IMG menu, choose View —► Additional Information —> Technical Data —> Client Dependence. Cross-client customizing affects one of the following: •
Cross-client customizing objects, which are repository objects generated by customizing demands. To ensure proper transport, assign these repository objects to a customer package. Examples of these objects are search helps, condition tables, and hierarchies.•
•
Global customizing settings are the standard SAP system settings and configurations in various tables whose key value does not contain a client number. Examples of these settings are calendars, printer settings, communication settings, and schedules.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
While client-specific customizing changes are recorded to customizing transport requests, you must save cross-client changes to workbench transport requests. Therefore, changes to cross client customizing objects, global settings, and repository objects require a workbench transport request. Comparison of Customizing Requests and Workbench Requests
Transport Organizer [&DEV(1)/100 Create Request
Figure 50: Customizing and Workbench Requests
To summarize, the following are the different types of transport requests with special properties: Customizing The first type is the transport request is a customizing transport request. A customizing transport request is used for copying and transporting settings from client-specific tables. Cross client customizing or workbench objects cannot be recorded into this kind of transport request. Workbench Another type of transport request is a workbench transport request. A workbench transport request is a transport request for transferring and transporting repository objects and changed SAP system settings from cross-client tables. By separating different activities into different types of transport requests a project leader or a person responsible for the transport can control who is allowed to transfer cross-client changes by assigning tasks inside the workbench requests.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 3 Exercise 3 Perform Business Configuration with IMG
Business Example
Regardless of the application area, the customizing procedures to record, copy, and test changes are the same. Part of the implementation project involves setting up country definitions. Perform Customizing Country Settings
Execute the required customizing transaction and save your work to a transport request assigned to your project. Use the customizing activity in the SAP system to accomplish this task. 1. Access your project and log on with the following details. Perform the necessary customizing activities to customize your project. Data
Data Value
User ID
CourseiD-## ( # # is your user number)
Client
100
Development System
DCC
Perform a Unit Test
Before transporting your customizing request to the quality assurance system, perform a unit test. 1. Log on with the details listed and copy your customizing settings. Data
Data Value
(Test) Client
200
Development System
DCC
Release the Task
View the content of the transport request and release the task that contains the customizing performed in the previous exercise tasks. 1. From the transport organizer using client 100, review the content of the task of your customizing transport request and release the task. Release the Transport Request
Release and export the transport request 1. Release and export the entire transport request to the transport system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 3 Solution 3 Perform Business Configuration with IMG
Business Example
Regardless of the application area, the customizing procedures to record, copy, and test changes are the same. Part of the implementation project involves setting up country definitions. Perform Customizing Country Settings
Execute the required customizing transaction and save your work to a transport request assigned to your project. Use the customizing activity in the SAP system to accomplish this task. 1. Access your project and log on with the following details. Perform the necessary customizing activities to customize your project. Data
Data Value
User ID
CourseiD-## ( # # is your user number)
Client
100
Development System
DCC
a) Enter s p r o _ a d m i n in the Command field to display the Customizing: Project Administration screen. b) Double-click your project and choose (Display) Project IMG. c) From the Change: Project —> View screen, choose SAP Customizing Implementation Guide —> SAP NetWeaver —> General Settings —> Set Countries —> Specify Countries in mySAP Systems. d) Verify that you are using the same customizing settings in the Confirmation dialog box. e) Add your customizing entry. In the Change View Global Parameters of Countries screen, choose New Entries. f) In the New Entry screen enter the following data: Field
Field Value
Country
U (1st character of country where you are taking the course, such as United States), 01 (Group 1)
Name (of country)
For example, United States
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Field
Field Value
Date format
any format, such as MM/DD/YYYY
g) To display the Prompt for Customizing request dialog box, choose Save. h) Select one of the customizing requests assigned to your project in the Request field and choose Continue. Perform a Unit Test
Before transporting your customizing request to the quality assurance system, perform a unit test. 1. Log on with the details listed and copy your customizing settings. Data
Data Value
(Test) Client
200
Development System
DCC
a) To copy your customizing settings, enter s c c i (Copy by Transport Requests) in the Command field. b) Choose Source Client 100. c) Enter the transport request that you established in the Perform Customizing Country Settings task. d) To activate your tasks and release them to the transport request, check the Including Request Subtasks checkbox. e) Choose Start Immediately. f) After the system finishes copying, perform a unit test by verifying your country settings. Do this step with your project IMG. Use transaction s p r o _ a d m i n and follow the steps in the Perform Customizing Country Settings task. Release the Task
View the content of the transport request and release the task that contains the customizing performed in the previous exercise tasks. 1. From the transport organizer using client 100, review the content of the task of your customizing transport request and release the task. a) Enter SEO 9 . in the Command field. b) In the initial screen of the Transport Organizer, select both request types, Customizing Requests and Workbench Requests. c) Choose Display. The system displays the transport requests according to your selection.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
d) Expand your customizing transport request to display all tasks associated with the request. e) Expand your task. The system displays a folder with all tasks associated with the request. f) Continue to drill down in the folders until you see the view and the tables with your customizing data. g) Expand the first table. You see the primary key (of the customizing data), the client, and the country. The data behind this key will be transported to the subsequent SAP systems in the landscape. h) Release the task in the customizing request to the transport request by selecting the task and the Release Directly icon. A check mark now displays behind the task, indicating that the task has been released. Release the Transport Request
Release and export the transport request 1. Release and export the entire transport request to the transport system. a) From the Transport Organizer: Requests screen, select the transport request and choose Release Directly. The display shows that the system releases the transport request to the transport system. b) Review the logs generated for the export.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Change M anagem ent Planning Now you know the different customizing tools and the technical settings that are required for the usage of these tools. To summarize, we will now discuss what is important for planning the customizing change management. From a process point of view, it is essential to establish policies on how customizing and development will be carried out and by whom. Planning Customizing Change Management involves customizing policies, restricting access to transport request management tasks, and establishing project teams. Customizing Policies
Defining customizing policies includes the following: •
Define policies for creating the project IMGs and views within a project, the use of project statuses, and documentation.
•
Establish a single client for all customizing.
Transport Management Restrictions
Restricting access to transport request management tasks includes the following: •
Determine change management roles.
•
Assign appropriate user authorizations.
Project Teams
Establishing project teams includes the following: •
Establish project team leaders to define projects and to assign tasks within transport requests to team members.
•
Provide training on the user of change request management tools to all project teams.
Customizing is the standard way of adapting the functions of the delivered SAP components to the requirements of a company. Project control tools allow easy documentation and monitoring of each phase of the SAP implementation and customizing. Customizing is required for implementations of SAP systems. Because customizing is a highly integrated process, both between functional modules and within the modules themselves, perform all customizing activities in a single client, specifically known as the development client. Restrict development tasks to this client, thus ensuring that there is a single environment for all implementation efforts. The project leader is responsible for creating transport requests for all project team members at the start of a development or customizing project. After project team members complete their work, they save their changes in the tasks that comprise the transport request, and document the changes in the task. When all project team members have released their tasks, the project leader releases the transport request for transport to other SAP systems within the SAP system landscape.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
The project managers or team leaders are responsible for creating the appropriate project IMGs for the specific business areas and assigning responsible parties to execute specific customizing transactions. The project management function enables you to assign tasks in the Transport Organizer. The project leader should activate the CTS functions of the project, create transport requests for recording and transporting the customizing settings, and add users to the transport requests. The project managers or team leaders are also responsible for training the team members on the CTO tools and processes, as well as establishing and enforcing documentation and unit testing standards. We recommend that transport requests should contain testable units of work, it is best to have a minimum number of transport requests with many tasks. This method reduces the number of transport requests moving through the transport system and makes it easier to troubleshoot problems when they arise.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
LESSON SUMMARY
You should now be able to: •
Perform customizing procedures
•
Distinguish cross-client from client-specific customizations
•
Plan change management for customizing
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 3 Lesson 4 Describing Change Management for ABAP Development
LESSON OVERVIEW
This lesson covers change management for ABAP development, including repository objects and packages. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Plan change management for ABAP development
•
Distinguish between customizing and development
Change M anagem ent fo r ABAP D evelopm ent Planning Change Management for ABAP Development
Before starting the development in an SAP system, plan how the change management for development is done. Table 3: Procedures for Different Areas of Change Management The areas described in the change management procedure for development include the following:_______________________________________________________________ Areas
Action
Restrict Repository Object Changes
•
Create a single SAP system for all develop ments. Note that there is typically one SAP system for one SAP system landscape.
•
Ensure that there are proper system and cli ent change options.
•
Assign the appropriate user authorizations.
•
Use packages to group repository objects.
•
Establish standards for development and documentation for repository objects.
•
Maintain versions for repository objects.
Define Development Standards
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Action
Areas Establish Project Teams
Use Projects to Group Transport Requests
•
Provide all project teams with training for transport request management tools.
•
Assign team leaders to projects.
•
Assign tasks within transport requests to team members.
•
Use the project assignment to import and approve whole projects, not single transport requests. Importing and approving com plete projects reduces the potential for er rors.
The tools that the SAP systems provide for change management are based on creating, documenting, and distributing transport requests. The customer must set up the infrastructure and procedures for management, verification, and testing of these development changes.
•
Create request
I I I Development Project leader
Create object
ZDz z
Y
Assignment to package
Developer
Developer
Assignment to request
Release task
Release Request Development Project leader
Transport Directory
Export
Figure 51: The Development, Release and Transport of Repository Objects*•
Recommendations for development change management include the following: •
Perform development efforts in a single environment only: the development system where you set the system change options.
•
Use packages to group functionally-related repository objects. The transport layer assigned when creating a package enables the same predefined transport route to be used for all objects in the package.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
When releasing a transport request, document the purpose and the status of the changes.
•
To maintain security, use authorizations to control which users can create, modify, or release transport requests. SAP delivers sample authorization profiles that provide the SAP system access required for various levels of responsibility in change management.
Most customers have to define development rules, customizing rules, and transport rules. These rules describe how and where changes are made, how and where these changes are tested, how the quality assurance is done, and how and who creates, releases, and imports transport requests in the SAP system landscape. C usto m izing C onstraste d w ith D evelopm ent SAP provides various implementation tools for customizing and development. Customizing
For customizing, use the following: •
The Implementation Guide (IMG) is the main customizing tool. Once you decide which business functions you require, the IMG automatically generates a hierarchical list of steps or customizing transactions for customizing.
•
The Transport Organizer (transaction SEO 9 ) records customizing changes in transport requests, which can be released to the transport system for export to other SAP systems in the SAP system landscape.
Development
For development, use the following: •
The ABAP Development Workbench provides access to development tools, which cover the entire software development cycle. You can use these tools for customer-specific development and for SAP enhancements of business.
•
The Transport Organizer (transaction SEO 9) also records ABAP Development Workbench changes in transport requests, which can then be released to the transport system for export to other SAP systems in the SAP system landscape.
•
The Transport Organizer is completely integrated with the Transport Management System (TMS).
The Transport Organizer records the customizing changes and ABAP Development Workbench changes in two types of transport requests. Client-specific objects are saved to customizing transport requests. Cross-client objects are saved to Workbench transport requests. The differences between these tools are described in the following lists. Customizing Tools
Customizing tools support the following: •
Change documentation
•
Support teamwork
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
Maintain connection to TMS
•
Maintain connection to client administration (client-specific customizing)
•
Log table change history (logging)
Workbench Tools
Workbench tools support the following: •
Change documentation
•
Support teamwork
•
Maintain connection to TMS
•
Require SSCR (for repository objects)
•
Use packages (for repository objects)
•
Use object locking (for repository objects)
•
Support version management (for repository objects)*•
Figure 52: Extended View of the Transport Organizer
Transport Organizer
The Transport Organizer can be used for customizing and workbench transport requests. It does the following: •
Creates, displays, manages, releases, and analyzes transport requests
•
Displays global transport information
•
Provides access to special tools
To access the Transport Organizer, use transaction
SE09
or
SEOl
for extended functionality.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
All workbench transport requests are displayed according to the selection criteria. Selection options include user (owner), transport request type, transport request status, and date. The screen area Global Information, provides a quick graphical overview of the status of transported transport requests and repairs.
Table 4: SSCR Registration Concepts The details about how SSCR registration concepts are created in the following table: Register developers to use ABAP Workbench
Register SAP objects to be modified
•
Developers must register with S
•
•
Each developer is assigned an ac^cos key
•
An access key can be used for all users with the same name in all clients in the SAP sys tem landscape
Modified SAP objects must be registered with SSCR
•
Each object is assigned an access key
•
An access key for each object is valid only for the current SAP release level
Any user in an SAP system who wishes to use the ABAP Workbench to create, modify, or delete repository objects, including customer objects, must be registered using the SAP SSCR process. Such users are referred to as development users or developers. Registration can be done at SAP Service Marketplace http://service.sap.com/sscr. As a result of the registration process, each developer is assigned an access key. The access key is entered and saved on the developer’s SAP system in the table DEVACCESS. The access key is associated with the developer's logon ID and the SAP system's license number. The developer is prompted for the access key during the initial attempt to create or change a repository object. You register developers and all SAP Repository objects (not customer objects) that are to be modified. When registering an object, you supply the object program ID, object type, object name, the SAP system's license number, and the release of your SAP system. After registering an SAP object in an SAP system and applying the access key, the key is stored in the database table ADIRACCESS. This step will ensure that further changes to the object do not require another key. Registered object keys become invalid after a release upgrade. SSCR provides development reliability, rapid error correction, and high system availability. This step can be done by limiting the access to the development and object keys. Most customers are doing the registration of objects and developers centrally.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
R epository O bjects and A ttrib u te s
Centralized Customer name ranges separate customer objects from SAP objects
SAP standard software
Decentralized
VTRESN Customers can assign a name range to a package
and SAP partners Customer development Complementary software
/xxxx/o b ject nam e Namespace prefixes uniquely identify objects created by SAP partners
Figure 53: SAP Repository Object Attributes
To prevent conflicts with object names when creating repository objects, developers must follow naming conventions. Extended name lengths allow you to use descriptive names. Object names should clearly describe the function of the repository object. Name ranges differentiate between SAP Repository objects and customer repository objects. Customer repository object names must begin with a Y orZ.
Hint: There are also other naming conventions. For example, customer fields in an SAP table definition must begin with ZZ, not with Z. Or, if the object name is a number, the customer name range begins with 9. For an overview of all of the current naming conventions for repository objects, see SAP Note 16466. Using customer name ranges correctly prevents object name conflicts between customer objects and SAP objects. If a customer has a more complex SAP system landscape with different SAP system strands and more than one development system, he or she requires additional naming conventions to prevent object name conflicts. Customer name ranges can be reserved using the view V_TRESN, which enables developers to assign a specific name range to a package. For example, you are developing in the SAP system DEI for a project within the package ZPROJECT1. You have chosen the naming convention ZPROJ1 for this project and maintained it in all your development systems. A developer in the SAP system DE2, working on another project within another package, now tries to create a program with the name ZPROJ1PROGRAM. The developer is told that this name is reserved for the package ZPROJECT1. The developer is prevented from assigning the object to another package. The developer has to choose a different name to assign the object to his package. This step avoids naming conflicts right from the start when objects are created.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Reserving namespaces is the only way to prevent naming conflicts that occur with objects created in complementary software from SAP partners. SAP partners and customer companies can apply to SAP for a namespace prefix through SAP Service Marketplace. For more information concerning namespaces and reservation use SAP Note 84282. SAP Repository objects are listed in the object directory. The object directory is a catalog of all repository objects in the SAP system, including all standard repository objects that are delivered with the SAP system, and all repository objects created by the customer using the ABAP Workbench. [&■ DEV(1)/100 Display Object Directory Entry Object
Jt3TR^PR0G ZREPORTINGOl
Attributes Package
ZPAKl
Person Responsible
CATON
Original System
DEV
Original language
EN Engteh
Created On
14.09.2011
/& Lock Overview
0
Figure 54: Correctly Naming SAP Repository Object Attributes
Object Directory
The object directory lists the following: •
All SAP standard repository objects
•
All customer-developed repository objects
Attributes for Repository Objects
The attributes for repository objects include the following: •
Package
•
Person responsible
•
Original system
•
Original language
Attributes for each repository object are assigned by the SAP system. The object directory is stored in table TADIR. This table is central to your SAP system's consistency. To change entries in TADIR, use only the standard functions SAP provides. With the appropriate authorization, you can modify the package and person responsible for the object. To modify object directory entries from the Workbench Organizer, call transaction SE09 and choose Goto —► Transport Organizer Tools. Alternatively, use transaction SE03. For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Some repository objects may be generated automatically by the SAP system as a result of customizing activities. In the object directory, these SAP system-created objects are identified as “generated” . For each entry in the object directory, the primary key is comprised of the following fields: program identification (PGMID), object type, and object name. The program identification is R3TR. Examples of object types are PROG (ABAP program), DEVC (package), TABL (table definition). Packages for Repository Objects Repository objects are organized by packages. All repository objects are assigned to a package, which is formerly known as development class. Packages
Provide a logical grouping of objects for coordination of development efforts Define a repository object's transport layer Can control naming objects Examples of package definitions are shown in the figure Packages and Transport Layers. Repository Objects Assigned to Transport Layers
•
A package is assigned to a transport layer.
•
If the transport layer is a valid consolidation route, the objects of that package are transported to the consolidation system.•
•
SAP objects modified in the customer integration system follow the SAP consolidation route.
( 7
pA k T
)
ZD C C Transport layer
Package
DCC
QCC SAP
Integration
ZDCC
Consolidation ZD C C
TRN ZT R N
Consolidation
Consolidation routes Figure 55: Packages and Transport Layers
When a transport layer is assigned to a package, all objects belonging to that package have the same predefined consolidation route, pointing from development to quality assurance system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
In the figure Packages and Transport Layers, both the SAP transport layer and the standard transport layer ZDCC follow the same consolidation route from DCC to QCC, that is, from the development system to the quality assurance system. All repository objects assigned to a package whose transport layer is ZDCC are transportable. In the figure, ZDCC or ZTRN would be the transport layer that is assigned to package ZPAK1, for example. In this example, the transport layer ZTRN follows a consolidation route from DCC to TRN, from the development system to the training system. All repository objects assigned to a package whose transport layer is ZTRN are transportable. SAP objects belong to the preinstalled SAP transport layer. In the figure Packages and Transport Layers, SAP objects that are modified in DCC follow the transport layer SAP and are transported to QCC. There is only one SAP transport layer in an SAP system landscape. In this example, you can transport only repository objects whose package has the transport layer SAP, ZDCC, or ZTRN using the Transport Organizer. If an object is assigned to a transport layer that is either blank or for which there is no transport route, you cannot transport the object using the Transport Organizer. Packages are objects of the ABAP Workbench and can be created by the Repository Browser (transaction S E 8 0 ). When creating a package, the standard transport layer is assigned by default to the package. Users may also choose an alternative transport layer. The transport layer will be used by the TMS tools to determine the consolidation route for the objects inside the package. Customer Created Packages
Customer created packages may begin with the following letters: •
A package beginning with a Y or Z indicates that the package is for customer objects that are to be transported.
•
A package beginning with a $ indicates a package for temporary objects that are not to be transported and do not require a transport layer.
•
A package beginning with TEST indicates a package for local objects, which are linked to the Transport Organizer that provides version management and object locking, but no transporting
The package class $TMP is used when a Repository object is saved as a local object and is not recorded to a transport request. You can use view V_TRESN to specify which packages can be assigned for a name range. For example, program names starting with the string ZABC are prevented from being assigned to a package other than the one defined for this name range in V_TRESN. The view V_TDEVC holds all packages in the SAP system, including all SAP packages.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Package Usage
Package Definition
0----------
ZPACKAGE1
Interfaces
package interfaces
Properties of Package Transport Layer ZDEV Software Component BC Use access Package interfaces
Figure 56: Package Usage for Development
The concept of packages has been extended since SAP Web AS 6.10. Existing development classes are simply containers for development objects with a transport layer that determines how the objects will be transported. Packages extend the concept of development classes with the addition of new attributes: nesting, interfaces, visibility, and use accesses, as follows: 1. Nesting of packages, defining the package hierarchy Nesting allows you to split the larger units of the SAP system into a hierarchical structure. The combination of interfaces and use accesses allows developers to hide package elements and protect them from unauthorized use. 2. Definition of package interface Packages use interfaces and visibility to make their services known to other packages. All the visible elements in a package can potentially be used by other packages, invisible elements cannot. This step allows the package to encapsulate its contents and protect its elements from being used by unspecified external packages. 3. Definition of use access Use access is the right of one package to use the visible elements in the interface of a second package (but not the other way round). The package concept offers the option of splitting and encapsulating the SAP system into technical units (the packages), reducing high levels of dependency and thus decoupling the SAP system on a large and small scale.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Create a Package for a Customer Development
Business Example
Before starting any development efforts, the project team leader must create at least one transport request for the project. Team members are assigned to tasks in the transport request where their efforts are then recorded. Project team members have been assigned a role in the project to create a development object and save it to the transport request. Repository objects are grouped by packages. To group your own development, create one or more packages and assign your Repository objects to them. Create Workbench Requests
Create five workbench transport requests for development efforts within your project. 1. Create a workbench transport request and assign it to your project. Log on as the project leader who has the authority to create transport requests with the following details and repeat this step five times to create five workbench transport requests: Data
Data Value
System
DCC
Client
100
Project Leader/User ID
## (where # # is your user num ber)
Short Description
Describe the transport request
Project
PROJECT_## (where # # is your user num ber)
2. (Optional) Create the workbench transport request from within your project. 3. Determine how many tasks are associated with your workbench transport request and add additional users. 4. What type of transport request did you create? What is the difference between a local transport request and a workbench transport request? Did you create all the transport requests? Create Package and Release Transport Request
Create a package for your customer developments, assign it to one of your transport requests and export this transport request. 1. Create a package, z p a c k a g e _## (replace # # with your user number), using the Object Navigator. Use the following details in the Create Package screen:
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Field
Value
Short Description
package description
Software Component
Home
Standard Transport Layer
ZDCC
Package Type
Development Package
2. Assign the package to one of your transport requests. 3. Check your transport requests in the Transport Organizer.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Create a Package for a Customer Development
Business Example
Before starting any development efforts, the project team leader must create at least one transport request for the project. Team members are assigned to tasks in the transport request where their efforts are then recorded. Project team members have been assigned a role in the project to create a development object and save it to the transport request. Repository objects are grouped by packages. To group your own development, create one or more packages and assign your Repository objects to them. Create Workbench Requests
Create five workbench transport requests for development efforts within your project. 1. Create a workbench transport request and assign it to your project. Log on as the project leader who has the authority to create transport requests with the following details and repeat this step five times to create five workbench transport requests: Data
Data Value
System
DCC
Client
100
Project Leader/User ID
## (where # # is your user num ber)
Short Description
Describe the transport request
Project
PROJECT_## (where # # is your user num ber)
a) Enter SEO 9 in the Command field in the top left of the screen. b) From the Transport Organizer screen, choose Request/Task —*• Create. The Create Request dialog box appears. c) Select Workbench request and choose Copy (Enter). d) On the Create Request screen, enter the details for the transport request provided in step 1. e) Choose the Save (Enter) button. 2. (Optional) Create the workbench transport request from within your project, a) Enter s p r o _ a d m i n in the Command field in the top left of the screen.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
b) Select your project. c) Add a workbench request by choosing Transport Project. The system assigns your project, when creating the transport request from within the project. 3. Determine how many tasks are associated with your workbench transport request and add additional users. a) The number of tasks assigned to the transport request equals the number of users assigned. b) Enter SE09 in the Command field in the top left of the screen and choose the Display button. c) In the Transport Organizer: Requests screen, choose the Display Requests button. d) To select the transport request, go to the Display Request screen. e) Choose Request/Task —► Request —> Add User. The Add User dialog box displays. f) Enter additional team members and choose Copy (Enter). 4. What type of transport request did you create? What is the difference between a local transport request and a workbench transport request? Did you create all the transport requests? a) The newly created request is a workbench transport request. Repeat steps 1 through 4 to create five workbench transport requests. b) Workbench transport requests can transport to target systems. Local transport requests do not. They are local to the SAP system. Create Package and Release Transport Request Create a package for your customer developments, assign it to one of your transport requests and export this transport request. 1. Create a package, z p a c k a g e _## (replace # # with your user number), using the Object Navigator. Use the following details in the Create Package screen: Field
Value
Short Description
package description
Software Component
Home
Standard Transport Layer
ZDCC
Package Type
Development Package
a) Enter SE80 in the Command field in the top left of the screen. b) In the Object Navigator screen, choose the Repository Browser button and choose Package from the unlabeled Description field.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
c) In the next field, enter the name group number.)
z p a c k a g e _##
for your package. (Replace # # with your
d) Choose Enter to create a package. e) In the Create Pack. (Package) dialog box, indicate Yes to create your package. f) In the Create Package screen, assign the necessary details to the package. g) To create your package and display the Prompt for transport Workbench request dialog box, choose the Continue button. h) Continue with the next question. 2. Assign the package to one of your transport requests. a) To assign your newly created repository object (your package) to a workbench request, go to the Prompt for transportable Workbench request dialog box and choose the Own Requests button. b) In the Prompt for transportable Workbench request screen, double-click a transport request that you created for your project. c) On the Prompt for transportable Workbench request dialog box, choose the Continue button to confirm the selection. 3. Check your transport requests in the Transport Organizer. a) Enter SE09 in the Command field in the top left of the screen to access the Transport Organizer screen to check the assignment. b) Choose the Display button to display all transport requests that you created but have not yet released. There is a task described as Development/Correction under the transport request, where you assigned the newly created package. You can choose the Display Requests button to filter completed requests or display all requests. There are workbench requests and they appear by default. c) Select the transport request and release it. As you release the transport request, the system exports the transport request with your package. d) Verify that the export terminated without errors.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
LESSON SUMMARY
You should now be able to: •
Plan change management for ABAP development
•
Distinguish between customizing and development
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Developing Customer Programs
LESSON OVERVIEW
This lesson explains various aspects of customer program creation and management. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Create a customer program
Object Locking
In the figure SAP Repository Object Locking, note that objects may be changed by developers assigned to the workbench request. Only developers assigned to the workbench request may change repository objects locked by that workbench request. Locking Mechanisms
There are two locking mechanisms when repository objects are being modified that appear in the following list: •
The editor program, which works with the enqueue work process to ensure that only one user at a time can modify an object in the SAP system.•
•
The workbench transport request, which ensures that the developer modifying the object is assigned to a valid task within the workbench transport request.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
When a repository object is assigned to a task within a workbench transport request that object can only be modified by the developers associated with that transport request. This step prevents users outside the development team from changing any of the objects in the transport request before the development project is completed and the associated transport requests are released. An object list is associated with each task. Each user working on an object has a corresponding entry in the object list of their task. The object list records which users have actually edited the object. Objects may be manually entered in the object list of a task or transport request. In the Transport Organizer (transaction S E 0 9 ) choose Display. You can manually add objects, for example, by double-clicking the transport request and adding the desired objects. Or you can use the function Request/Task —*■ Object List —*• Include Objects. If objects are entered manually, then they are not automatically locked. To lock the object manually, in the Transport Organizer initial screen (transaction S E 0 9 ), choose Display —*• Request/Task —► Object List —> Lock Objects. Transport Request Release
In the figure Releasing Transport Requests note that releasing a task requires content to be in that task. Releasing a transport request requires a release of all tasks in the transport request and documentation of all tasks when that procedure is enforced. After the development tasks are completed, a transport request is released so that the content can be transported to another SAP system. Releasing a task or transport request requires the user to have the necessary authorization. A released task can no longer be changed, but additional tasks can be created to change the objects in the released task, as long as the transport request is not released. A released task cannot be deleted. However, if the task is empty, it is deleted when the transport request is released. Releasing a transportable transport request records a version of all the objects included in the transport request (that are included in the version management), and then exports the objects. For example, it copies the objects from the database to a file in the transport directory. Objects are unlocked during the release. Releasing a local transport request records a version of the objects in the transport request (that are included in the version management), but does not export them to file system level.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
Create a Customer Program
Business Example
During the implementation process, you may be required to create repository objects. Create an ABAP Program
Create a new customer program. 1. Log on to the SAP system and create the ABAP program. Use the following details: Data
Data Value
SAP system
DCC
Client
100
ABAP program
zpgm
## (Replace # # with your user num
ber.)
Note: If the team member is not registered in the SAP system as a developer, the SAP system prompts you for the developer's access key. For the purpose of this course, you do not need to provide the key.
2. Enter a title for the attribute and identify the type as executable program. 3. Since this step creates a repository object, the SAP system displays the Create Object Directory Entry screen. Assign your new ABAP program to the package you created for your project. 4. The Prompt for transportable Workbench request dialog box appears. Select one of the transport requests that you created for your project. 5. From the ABAP Editor: Change Report screen, on a new line below the report name, enter the following command: Write / 'Hi! I am a test program! Make sure that you surround the text with single quotes and end the command with a period. Release the Workbench Task and the Transport Request
Release the workbench task and the transport request. 1. Verify that the task containing your ABAP program has been released. 2. As the project leader, you release and export the transport request.
0
Change the ABAP Program and Release the New Request
Change the last program again and export the corresponding transport request. 1. Change the ABAP program, ZPGM_##, by adding a new line to the program. Add the following command:Write / 'The end.'. 2. As the developer, you release the task. As the project leader, you release the transport request. Assign Local Object to a Package for Transport
Create a local object and later reassign it to a package for transporting. 1. Create an ABAP program called ZCREATEDLOCAL_##. (Replace # # with your group number.) Enter a short title for your program. Choose Executable program for type, and Test Program for status. 2. Save this new program as a local object. 3. On a new line of the ABAP Editor, enter the command: Write 'I was born as a local object...'. 4. Is there a transport request associated with this program? Why or why not? 5. Is there a package associated with this program? 6. Is this object transportable? Why? Which change is necessary to make this local object a transportable object? Reassign your program to the package, from the previous exercise. What happens? 7. Assign the former local program to one of the transport requests of your project. Release the transport request. Restoring Repository Objects
Use this exercise to restore a repository object from a previous version. 1. How many versions of your ABAP program, ZPGM_##, exist? Compare the first version with the latest version of your program. What does the comparison indicate? 2. Retrieve the first saved version of your program, restoring your program back to its former status. Why does the SAP system ask for a transport request? 3. As the developer, you release the task. As the project leader, you release the transport request. Analyze the Attributes of Repository Objects
Analyze the attributes of repository objects using the Transport Organizer tools. 1. Search for transport requests and tasks using the relevant tools in the Transport Organizer. Locate all transport request and tasks containing your ZPGM_## program. 2. Display all of the attributes associated with the objects in the transport request.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Create a Customer Program
Business Example
During the implementation process, you may be required to create repository objects. Create an ABAP Program
Create a new customer program. 1. Log on to the SAP system and create the ABAP program. Use the following details: Data
Data Value
SAP system
DCC
Client
100
ABAP program
zpgm
## (Replace # # with your user num
ber.)
a) Enter S E 38 in the Command field in the top left of the screen. b) In the ABAP Editor: Initial Screen, enter
z p g m _##
in the Program field.
c) Choose Create. The ABAP: Program Attributes dialog box displays.
Note: If the team member is not registered in the SAP system as a developer, the SAP system prompts you for the developer's access key. For the purpose of this course, you do not need to provide the key.
2. Enter a title for the attribute and identify the type as executable program. a) In the ABAP: Program Attributes dialog box, enter a title in the Title field. b) Choose Executable program in the Type field. c) Choose Save. The Create Object Directory Entry dialog box appears. 3. Since this step creates a repository object, the SAP system displays the Create Object Directory Entry screen. Assign your new ABAP program to the package you created for your project.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
a) On the Create Object Directory Entry dialog box, enter the package assigned to your project in the Package field. Use the Search function, if you need to. b) Choose Save. The Prompt for transportable Workbench request dialog box appears. Hint: If the system assigns a package with an invalid transport layer to an object, the system cannot transport the object to the target system.
c) Choose Enter (Continue). The program goes to the ABAP Editor: Change Report screen where you can view/change the attributes. 4. The Prompt for transportable Workbench request dialog box appears. Select one of the transport requests that you created for your project. a) In the Prompt for transportable Workbench request dialog box, enter a Workbench transport request. Use the help from the Request field. b) Choose Continue (Enter). The ABAP Editor: Change Report screen displays. 5. From the ABAP Editor: Change Report screen, on a new line below the report name, enter the following command: Write / 'Hi! I am a test program! Make sure that you surround the text with single quotes and end the command with a period. a) When entering the command, make sure that you end the command with a period, otherwise a syntax error will result. Enter Write / 'Hi! i am a test program!'. b) To check your program for errors, choose Program —> Check —► Syntax. c) If there are no syntax errors in the program, activate the program by choosing Program —► Activate. d) If a dialog box displays, choose Continue (Enter). e) Choose Back to return to the ABAP Editor: Initial Screen. f) On the ABAP Editor: Initial Screen, choose Execute to run your program. Release the Workbench Task and the Transport Request
Release the workbench task and the transport request. 1. Verify that the task containing your ABAP program has been released. a) Enter SEO 9 in the Command field in the top left of the screen to access the Transport Organizer screen. This screen displays the transport requests and tasks assigned to your user, ##. b) Choose Display and select your transport request.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
c) On the Transport Organizer: Requests screen, choose Request/Task —> Release to release a task. When a task is released, a check mark appears to the right of the task. 2. As the project leader, you release and export the transport request. a) Enter SEO 9 in the Command field in the top left to access the Transport Organizer screen. b) Choose Display and select your transport request. c) On the Transport Organizer: Requests screen, choose Request/Task —► Release —> Directly. You cannot release the transport request unless the tasks have been released or the tasks are empty. The SAP system deletes empty tasks when you release a transport request. Change the ABAP Program and Release the New Request
Change the last program again and export the corresponding transport request. 1. Change the ABAP program, ZPGM_##, by adding a new line to the program. Add the following command: W rite / 'The e n d .'. a) Enter S E 38 in the Command field in the top left of the screen to edit a program. b) Enter
z p g m _##
in the Program field.
c) Choose Change. d) Add the following command: W rite /
'The e n d .'.
e) Choose Save and then choose Activate. f) When prompted, choose a transport request for the changes you just made. 2. As the developer, you release the task. As the project leader, you release the transport request. a) Enter S E 0 9 in the Command field in the top left of the screen. b) Choose Display. c) On the Transport Organizer: Requests screen, select the task of the transport request to be released. d) Choose Request/Task —» Release —*■ Directly. e) On the Transport Organizer: Requests screen, select the transport request. f) Choose Request/Task —» Release —*■ Directly. Assign Local Object to a Package for Transport
Create a local object and later reassign it to a package for transporting. 1. Create an ABAP program called ZCREATEDLOCAL_##. (Replace # # with your group number.) Enter a short title for your program. Choose Executable program for type, and Test Program for status. a) Enter S E 38 in the Command field to access the ABAP Editor.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
b) Enter the name of the program you wish to create,
z c r e a t e d l o c a l _##.
c) Choose Create. d) In the ABAP: Program Attributes Change dialog box, enter the following details: Field
Field Value
Title
Enter a description
Type
Executable Program
Status
Test Program
e) Choose Save. 2. Save this new program as a local object. a) When the Create Object Directory Entry dialog box displays, choose Local Object. 3. On a new line of the ABAP Editor, enter the command: Write 'I was born as a local object...'. a) On the ABAP Editor: Change Report screen, enter the command, Write ' I was born as a local object...'. b) Choose Save. c) Choose Program —*• Check —> Syntax to check this program for syntax errors. d) Choose Activate. 4. Is there a transport request associated with this program? Why or why not? a) Enter SEO 9 in the Command field in the top left of the screen to display the Transport Organizer screen. b) Choose Display to see your requests. There is no transport request associated with this program. Local objects are not linked to the Transport Organizer. 5. Is there a package associated with this program? a) Enter SE38 in the Command field in the top left of the screen to search the object directory for the object. b) In the ABAP Editor: Initial Screen, enter the name of the program from step 1 in the Program field. c) Choose Goto —> Object Directory Entry to display the Display Object Directory Entry screen. The package for this object is $t m p .All repository objects, including local objects, appear in the Object Directory (table t a d i r ).
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Hint: You can also find out the attributes in the object catalog by choosing the Workbench Organizer Tools, transaction SE03.
6. Is this object transportable? Why? Which change is necessary to make this local object a transportable object? Reassign your program to the package, from the previous exercise. What happens? a) No, the object is not transportable. The package is $t m p ,which does not have a valid transport layer. Local objects are not linked to the Transport Organizer. Reassign the object to a package that contains a valid transport layer. b) Enter SE38 in the Command field in the top left of the screen to access the ABAP Editor screen. c) In the Program field, enter your program,
z c r e a t e d l o c a l _##.
d) Choose Goto —*• Object Directory Entry. e) In the Display Object Directory Entry dialog box, enter Change.
z p a c k a g e _##
and choose Display/
f) In the Change Object Directory Entry dialog box, choose Save. The Prompt for transportable Workbench request dialog box displays because the object is now assigned to a package with a transport layer. The system links the package to the Transport Organizer. 7. Assign the former local program to one of the transport requests of your project. Release the transport request. a) In the Prompt for transportable Workbench request dialog box, select one of your unused transport requests. The transport request must a Workbench type. b) Enter SEO 9 in the Command field in the top left of the screen to go to the Transport Organizer screen where you can verify that the transport request is transportable. c) In the Transport Organizer screen, select Display. d) Select the task and choose Request/Task —► Release —> Directly. e) Select the transport request and choose Release/Task —> Release —> Directly. Restoring Repository Objects
Use this exercise to restore a repository object from a previous version. 1. How many versions of your ABAP program, ZPGM_##, exist? Compare the first version with the latest version of your program. What does the comparison indicate? a) Enter SE38 in the Command field at the top left of the screen to go to the ABAP Editor:lnitial Screen.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
b) Enter
z p g m _##
in the Program field.
c) To view all saved versions of the program, choose Utilities —> Versions —*■ Version Management. d) In the Versions of Object <> of Type Report Source Code screen, compare two versions by selecting the two versions that you wish to compare, then choosing Versions —► Compare. e) In the Compare Programs: All screen, verify two versions of your program. The system created the first version of the program when it released the first transport request. The system created the second version of the program when it released the second transport request. This comparison adds a new command line to the program. 2. Retrieve the first saved version of your program, restoring your program back to its former status. Why does the SAP system ask for a transport request? a) In the Versions of Object <> of Type Report Source Code screen, mark the first version in the list to retrieve the first version of your program. b) Choose Retrieve. c) In the Restore Version XYZ of Program ABC dialog box, choose Continue (Enter). The warning represents a change in the program and to be recorded assign it to a transport request. d) In the Versions of Object <> of Type Report Source Code screen, choose Save and then choose Activate to activate the program. 3. As the developer, you release the task. As the project leader, you release the transport request. a) EntersE09 in the Command field in the top left of the screen. b) Choose Display to display the tasks and transport requests. c) In the Transport Organizer: Requests screen, select the task. d) Choose Request/Task —*■ Release —► Directly to release the task of the transport request. e) In the Transport Organizer: Requests screen, select the transport request. f) Choose Request/Task —>■ Release —► Directly. Analyze the Attributes of Repository Objects
Analyze the attributes of repository objects using the Transport Organizer tools. 1. Search for transport requests and tasks using the relevant tools in the Transport Organizer. Locate all transport request and tasks containing your ZPGM_#ff program. a) Enter SE03 in the Command field at the top left of the screen to go to the Transport Organizer Tools screen. b) Double-click Search for Objects in Requests/Tasks. The Search for Objects in Requests/Tasks screen displays
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
c) Mark the Object Selection checkbox next to R3TR PROG, and enter the name of the program. d) Check the Released checkbox at the bottom of the screen to display all released transport requests containing this ABAP program. e) Choose Execute.
Note: Check Also Search for Subobjects to find transport requests containing entries of the program, for example, l i m u r e p s .
2. Display all of the attributes associated with the objects in the transport request. a) Enter S E 03 in the Command field in the top left of the screen to display the Transport Organizer Tools screen. b) Double-click Analyze Objects in Requests/Tasks. c) In the Analyze Objects in Requests/Tasks screen, enter the transport request number in the Request/Task field. d) Choose Execute. A list of all objects contained in the transport request displays. e) In the Analyze Objects in Requests/Tasks screen you can display the attributes associated with an object by selecting one of the objects and choosing (Display) Object Directory. The system stores the attributes in the object directory (table TADIR).
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Version Management of ABAP Programs _
□r
Versions
&
Edit
g o to
Ji
System
Help
□
asasa a t i c a he
V e r s io n s o f O b j e c t Z R E P O R T I N G O 1 o f T y p e R e p o r t S o u r c e C o d e □ □
Retrieve
Request te x t o n /o ff
REMOTE comparison
Versions: Report Source Code ZREPORTIHGOl
Version Cat Fla SAF Rel. Arch Request
Project
Date
lime
Author
Version(s) in the development database: Hnodil '/lectio
702 702
DEVK9002S5 DEVK900255
14.09.2011 10:30:30 CATO!! 14.09.2011 10:35:44 CATON
Development DB Active and modified versions
Version(s) in the version database: n 00005 O 00004 □ 00003 □ 00002
□ OOOOI
D 0
702 702 702 702 702
DCVK900255 14.09.2011 16:36:39 DCVK900255 14.09.2011 16:36:36 DEVK900252 DEV_P00002 14.09.2011 16:3S:S4 DEVK9002S0 DEV_P00002 14.09.2011 16:35:08 DEVK900244 DEV P00002 14.09.2011 16:33:49
CATON CATON CATON CATON CATON
Version DB Versions saved by version management
Figure 59: Version Management
As illustrated in the figure Version Management, versions of SAP Repository objects can be displayed, compared, or restored. When a Workbench transport request is released, a new version of each repository object in the transport request is written to the version database, which thus contains a complete change history of all repository objects. In addition to the versions created automatically by the release of transport requests, users can also create temporary versions at any time. To do this step, in the maintenance transaction for the repository object, for example transaction S E 3 8 , choose Utilities(M) -> Versions -> Version Management -> Generate version. Locations To Access Version Management
You can access version management Utilities(M) -> Versions -> Version Management from the locations in the following list: •
Object Navigator / Repository Browser (transaction
•
Transport Organizer (transaction
•
SE 80)
SE0 9)
Display and maintenance transactions for all repository objects (transactions
SE38, S E i i,
or
SE 37)
In the Version Overview, the active and modified versions are displayed in the development database, and versions saved as a result of released transport requests are displayed in the version database. The version database resides in the development system. Versions cannot easily be transported between SAP systems. If the development system is removed from the SAP system landscape, all versions in the version database are lost.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
T ra n sp o rt O rganizer S e ttin g s fo r ABAP D evelopm ent C e'
Io o l
&
E d it
G o to
S ystem
Ti
Help
<1 H
©
©
«
Transport Organizer Tools C D
- ^ 8 T ra n spo rt Organizer Tools - e a O b je cts n R equests " Cr ) Search fo r O b je cts n R equests/Tasks * Analyze O b jects n R equests/Tasks * 'of Include O b je cts in a Tra n spo rt R equest ► CJ O b jects ► CD O b je c t D irectory ~ R equests/Tasks • (a ) Fmd R equests • M erge O b je c t Lists * d f* U nlock O b je cts (E x p e rt T o o l) * Cancel R elocation T ransport ~ <28 A dm nrstratio n • ("3 S e t S ystem Change O ption • # Dtspby/Change Namespaces • ^ Dtsplay/Change Naming C onventions • C 3 Global Customizing (T ra n s p o rt O rganizer) • Disptay/Change R equest A ttn b u te s
Figure 60: Transport Organizer Tools
The Transport Organizer tools support the work of the Change and Transport System. Use Transport Organizer tools to access objects, objects in transport requests, object directories, transport requests or tasks, and administration topics. These tools can be reached either by the corresponding button in the Transport Organizer (transaction S E 0 9 ) or by starting transaction S E 0 3 directly. You can find documentation of the functions by using the Documentation button, shown in the figure Transport Organizer Tools. Documentation of the tools can also be found in their context menus. Transport Organizer Settings
Transport Organizer settings provide customers with several options that can be used for the following tasks: 1. Displaying transport errors at logon 2. Applying object checks to objects contained in transport requests before the transport request is exported to a file in the transport directory To cause transport errors to be displayed to transport request owners when they log on, select the setting display transport errors at logon. Object checks identify and display errors found in workbench transport requests. Errors, such as program syntax errors, are identified and displayed when a transport request is released, but not yet exported. More detailed information about the error can be found by simply double-clicking the error on the displayed report.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
G lo b a l C u sto m izin g (T ra n s p o rt O rg a n ize r)
Q l^log Transport Error Display when Loggrg On J3lobafy Activated
C Globaty Deactivated O Set by User Check Objects when Request Released
O Globaty Activated O Globaty Deactivated (?) Set by User
Check Existence of Task Documentation when Task Released
O’ Globaty Activated O Globaty Deactivated ® Set by User
Figure 61: Transport Organizer Settings
Display of Transport Errors
To activate or deactivate the display of transport errors at logon and object checks, do the following: •
Globally, enter transaction Choose Globally activated.
•
Fora specific user, enter transaction SEO 3 Administration —*• Global Customizing (Transport Organizer). Choose the option Set by User.
•
For a logged-on user, enter transaction SEO 9 Display —► Utilities(M) —>Settings. Change to the Transport Organizer tab. Choose the option Display transport errors at logon and Check objects when request is released can be set by the user that is logged on.
SEO3
Administration —*• Global Customizing Transport Organizer.
You can use the Transport Organizer tools for many different tasks concerning objects in tasks and requests. These tools also allow access to several administrative transactions, which can also be accessed in other ways. E xport Logs After releasing a transportable transport request, review the transport logs to ensure that the export was successful.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
& Iranspoft
Edit
goto
© £
Utities
^ < 1 0
Enyronment
©©©
System qsqss
_
Help
atica
he
□
®s
O v e r v ie w o f A H T ra n s p o rt L o g s f o r D E V K 9 0 0 2 4 4
S
Q <&•
a©
Overview for DEVK900244 DEVK900244 Q
DEV
Development System
-----^ Qr -----r A 200 ^ 100 Cfi Import
—a (jAs br
Development pert 2
Checks at Operating System Level Pre-Export Methods Selection for Import Export steps not specific to transport request
14.09.2011 14.09.2011 14.09.2011 14.09.2011
16:33:49 16:33:52 16:33:59 16:33:59
(0) (0) (0) (0)
Successfully Successfully Successfully Successfully
Completed Completed Conpleted Conpleted
Quality Assurance System
S Selection for Import Inport steps not specific to transport request
14.09.2011 16:33:59
(0) Successfully Conpleted
Return code (0) means “everything is OK” Figure 62: Transport Logs
To access the transport logs from the initial screen of the Transport Organizer enter transaction code S E 0 9 , choose Display button, and choose Goto —*• Transport Logs. Meaning of Return Codes
In the transport logs, the following return codes indicate the success or failure of the export: •
0 - The export was successful.
•
4 - A warning was issued but all objects were transported successfully.
•
8 - An error in an object occurred. Whether the objects are transported successfully depends on tp parameter settings.
•
12 or higher - A critical error occurred. This error is generally not caused by the objects in the transport request.
O verview o f A u th o riz a tio n s fo r Change M anagem ent The authorization object S_CTS_ADMI only has one field, CTS_ADMFCT, whose values describe the various administration activities that can be checked using the authorization object. The table. Field CTS_ADMFCT, provides a summary of the administration functions that are currently defined.
Note: Do not use the authorization IMPT any more. Instead, grant one of the specific authorizations IMPA, IMPS, TADD, TDEL, TQAS, or TADM.
Table 5: Field CTS_ADMFCT Field Value
Function
TABL
Configures transport routes
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Field Value
Function
1NIT
Initializes transport organizer
SYSC
System change option
PROJ
Creates/changes projects
IMPA
Imports all transport requests
IMPS
Imports individual transport requests
INBX
Edits worklists in TMS workflow
TADD
Forwards transport requests to an import queue
TDEL
Deletes transport requests from an import queue
TQAS
Activates or deletes requests in an import queue
TADM
Executes tp commands
QTEA
Approves transports into the production syste.
EPS1
Generates EPS objects
EPS2
Changes EPS objects
WHIT
Only if the CTS plug-in is installed in the sys tem
Different tools exist for managing customizing and workbench transport requests in a controlled way. How these tools are used and the responsibility for changing customizing and repositories in an SAP system are normally defined in the customizing and development roles for that SAP system. But in actuality most of these roles are only observed if they are dispensed in user authorizations and authorization roles. Authorizations for Change Management
In most cases, the authorizations occur as shown in the Authorizations for Change Management figure and the tasks are broken down as follows: Super user (that is, SAP system administrator) - has all authorizations related to transport requests and tasks. •
Project leader - can create and manage transport requests and tasks.
•
Developer - can only use existing transport requests.
•
End user - Only has display authorization.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
LESSON SUMMARY
You should now be able to: •
Create a customer program
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 3 Lesson 6 Modifying SAP Objects
LESSON OVERVIEW
This lesson explains how to modify various SAP objects, including repository objects, programs, and tables. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Perform modifications on repository objects
Repository Object Changes Repository objects are only changed in the SAP system where the SAP system identifies them as original objects. An object is the original in only one SAP system, the SAP system where it was created. All other SAP systems may only contain copies of the object. This step ensures that changes are only made to repository objects in the development system. When a repository object is transported to a downstream SAP system, it exists there as a copy. Changes to copies, which are referred to as repairs, are made only in exceptional cases. In all customer SAP systems, including the customer's development system, SAP-delivered repository objects are copies. The original of those objects exists at SAP in the development system. Repairs to SAP objects are referred to as modifications. The system change options selected when setting up the Transport Organizer (transaction S E 0 6 ) identify which repository objects can be modified in the SAP system. Only in the development system, the system change option is set to permit changes to customer-developed objects and, if necessary, SAP objects.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Pgm. RSPFPAR
Pgm.RSPFPAR
Copy
Copy
Copy
Pgm. RSPFPAR
Repair
Repair
Repair
Modification
Modification
Modification
Pgm. ZREPORT01
Pgm. ZREPORT01
Pgm. ZREPORT01
O riginal
Copy
Copy
Correct./Develop.
Repair
Repair
Figure 63: Originals and Copies of Repository Objects
When changing an object that is not an original, the SAP system prompts the user to specify the object for a repair. For the object specified, a repair indicator is set to prevent the object from being overwritten by imports into the SAP system. Therefore, the object is locked exclusively for the task of type repair. When the corresponding transport request is released, the repair indicator is deleted automatically. Classification of Tasks and Transport Requests A distinction is made between two types of development tasks: development/correction (considered one task), or repair. Development/correction is a change in the original system, and repair is a change in an SAP system other than the original system. Objects saved as local objects cannot be transported. The only way to transport such an object is to assign it to another package, one that has an existing transport layer assigned. The package of the repository object determines whether the transport request type is transportable or local. If the assigned package has a valid transport layer, a transportable request is used. Otherwise, a local transport request is used.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unclassified Unclassified
Local Development/ correction
_ Repair
Transportable Development/ correction
Repair
Figure 64: Classifying Tasks and Transport Requests
As shown in the figure Classifying Tasks and Transport Requests, there are three types of transport requests: unclassified, local, and transportable. Characteristics of Transport Requests
Observe the following characteristics of transport requests: Transport requests or tasks of type Unclassified have empty object lists. Changes to original objects are saved to tasks of type Development/correction. Changes to copies are saved to tasks of type Repair. The package of a repository object determines when a transport request of Transportable or Local is required.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Process Flow for Changing Repository Objects
Create new object (development)
Change own object (correction)
Change SAP object (repair) Enter SSCR key
Figure 65: Changing Customer and SAP Objects
Before starting a modification, determine if it is really necessary to modify the standard programs or if the enhancement can also be done with SAP extension techniques, such as Business Add-ins (BAdls, appends, user-exits, and enhancements). Please remember that you may have to adjust the modification if SAP delivers this object in a newer version. For example, if the object were delivered in a Support Package, SAP enhancement package, or SAP system upgrade, you might need to adjust the modification. That situation can cause additional effort for the maintenance of the modification. Before changing any repository object (customer and SAP objects), register as a developer in SAP Software Change Registration (SSCR). In case you want to perform a modification (such as, SAP standard object), register each SAP object you intend to change. Registering the object gives you an access key, which you apply to the object. When performing a modification, the Transport Organizer prompts you for a transport request in the same way that it does when you change customer-owned objects. Since the object is owned by SAP, the change is saved as a repair task. All SAP objects have SAP-defined packages. Assign all new customer repository objects to a customer-created package. Packages are used to group objects in the project, and transport them along the same transport route. After the repair task or transportable task is complete, the developer releases the task and the lock on the object is transferred to the transport request. At the end of the project, the transport request is released. The system releases all locks and records a version of the changed objects, both SAP and customer objects, in the version database. Modification Assistant
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
&
Brogram
Edt
goto
Utibes(tj)
Enyronment
System
B E T
defe
- o a e
e
A B A P E d ito r : M o d i f y R e p o r t A D M 3 2 5 X 0 1
=i>
ti Rj '(D
A filH D
c/lnsert
c/Reptoce EfOeiete q&Undo
Figure 66: Modification Assistant
To support the different levels of modification, SAP provides tools such as the IMG, Business Add-Ins, transaction c m o d , and the ABAP development environment. The Modification Assistant helps you modify SAP standard delivered objects and simplify the modification adjustment. When you change SAP objects in an ABAP Workbench editor, you branch into a special modification mode. Originals are initially protected in this mode and are only changed when you click the corresponding buttons. The Modification Assistant logs all modifications that are made to the object. The log is easy to read and dramatically reduces the amount of effort needed for a modification adjustment. In addition, the Modification Assistant works with the most commonly used ABAP development tools such as ABAP Editor, Screen Painter, Menu Painter, and text element maintenance. The Modification Assistant is not used for changes made to objects such as global interfaces, and classes and their components. These objects are adjusted during modification adjustment manually. A list of all modified objects in the SAP system can be shown with the Modification Browser (transaction S E 9 5 ).
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Figure 67: Modification Adjustment
If a new version of an SAP object is imported into the customer SAP system, as part of an SAP Support Package, SAP enhancement package, or an SAP system upgrade, the repaired SAP objects are required to be adjusted. Modifications are considered repairs. Modifications may involve making the same customer changes to the new SAP object. Before applying a Support Package, applying an SAP enhancement package, or performing an SAP system upgrade, confirm, and release all open repairs. This check is performed by the upgrade check routines of the Support Package/SAP enhancement package/SAP system upgrade tool. To adjust the ABAP dictionary repository objects, use transaction repository objects, use transaction s p a u .
spdd.
To
adjust all other
Adoption of modifications is neither automatic, nor trivial. Customers must decide which development efforts and modifications they wish to retain, being mindful that the new SAP functions may possibly make retaining the modification unnecessary. Adjusting modified objects is simplified by the Modification Assistant.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 3 Exercise 6 Modify an SAP Program and an SAP Table Structure
Business Example
During the implementation process, you may be required to change standard SAP repository objects to fulfill the requirements of your business. The Modification Assistant is a tool delivered with the SAP system to aid you with modification adjustments, as well as helping you with future modification adjustments. Modify an SAP Repository Object
1. Log on to the SAP system and enter the following details. Determine which package the object belongs to and which SAP system is the original. Data
Data Values
SAP system
DCC
Client
100
ABAP Program
ADM325X## (Replace # # with your user num ber)
2. Modify the source code of ADM325X##. Because this object is owned by SAP, you are required to enter a registration key for the object. However, you are not prompted to enter a registration key for this exercise. 3. Use the Replace function of the Modification Assistant to modify line 38 of the source code as follows: [original] ORDER BY STRKORR TRKORR [modification] ORDER BY STRKORR AS4USER TRKORR 4. Save and activate the amended program to one of your transport requests. Verify the type of change that was created. 5. Execute program ADM325X## and view the Repair Flag checkbox. 6. Release only your task. Modify an ABAP Dictionary Object
Add a new field to an ABAP dictionary object. 1. Add an additional required field to the table ADM325X## (replace # # with group number), review the structure of this table using the ABAP Dictionary.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
2. Add the z z b i r t h p l a c e field to table ADM325X##. Assign a data element, and choose Enter.
g b o r t
, to
the field
3. Activate and save the changes to table ADM325X## to a new task within the same transport request used in the previous step of this exercise. The SAP system automatically prompts you for the new task. 4. Add entries to the table ADM325X##. 5. Release your task. 6. Release the transport request.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 3 Solution 6 Modify an SAP Program and an SAP Table Structure
Business Example
During the implementation process, you may be required to change standard SAP repository objects to fulfill the requirements of your business. The Modification Assistant is a tool delivered with the SAP system to aid you with modification adjustments, as well as helping you with future modification adjustments. Modify an SAP Repository Object
1. Log on to the SAP system and enter the following details. Determine which package the object belongs to and which SAP system is the original. Data
Data Values
SAP system
DCC
Client
100
ABAP Program
ADM325X## (Replace # # with your user num
ber)
a) Enter SE38 in the Command field in the top left of the screen to access the ABAP Editor screen. b) In the Program field, enter ADM325X##, the name of the SAP program.
c) Choose Goto —> Object Directory Entry. The package for this object is ADM325. The Display Object Directory Entry screen contains the object (ADM325X##) and the original system. 2. Modify the source code of ADM325X##. Because this object is owned by SAP, you are required to enter a registration key for the object. However, you are not prompted to enter a registration key for this exercise. a) In the ABAP Editor (transaction SE38), enter ADM325X## in the Program field, select the Source Code radio button, and choose Change. b) Read the Modification Assistant dialog box information. c) Choose Continue.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
The ABAP Editor: Modify Report screen displays where you can change items in the next step. 3. Use the Replace function of the Modification Assistant to modify line 38 of the source code as follows: [original] ORDER BY STRKORR TRKORR [modification] ORDER BY STRKORR AS4USER TRKORR a) Use the ABAP Editor: Modify Report screen that displayed after Modification Assistant dialog box to change this source code. 4. Save and activate the amended program to one of your transport requests. Verify the type of change that was created. a) Choose Save, then choose Activate. b) Because the original system for this program is SAP, this type of change is termed a repair so that the Modification Assistant can control the changes performed to the object. 5. Execute program ADM325X## and view the Repair Flag checkbox. a) Enter S E 38 in the Command field in the top left of the screen. b) Enter ADM325X## in the Program field. c) Choose Goto —> Object Directory Entry. The Display Object Directory Entry screen displays. d) To view all attributes including the Repair Flag checkbox, choose Object Attributes. 6. Release only your task. a) Enter SEO 9 in the Command field in the top left of the screen. b) Enter ADM325X## in the User field and choose Transport to display the transport requests and tasks assigned to the user. c) Select your task number and choose Release Directly, but do not release the request yet. Modify an ABAP Dictionary Object Add a new field to an ABAP dictionary object. 1. Add an additional required field to the table ADM325X## (replace # # with group number), review the structure of this table using the ABAP Dictionary. a) Enter S E 1 1 , in the Command field to display the ABAP Dictionary: Initial Screen and show the structure of table ADM325X##. b) Enter ADM325X## in the Database table field. c) Choose Change. d) In the Customer Modification: Different Original and Logon Languages dialog box, choose Maint. in logon lang. to maintain the logon language. The program goes to the Dictionary: Change Table screen where you can work with the fields.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
2. Add the z z b i r t h p l a c e field to table ADM325X##. Assign a data element, and choose Enter.
g b o r t ,to
the field
a) In the Dictionary: Change Table screen, enter a short description in the Short Description field and add a new field by placing your cursor on a blank line and entering z z b i r t h p l a c e in the Field field. b) In the Data element field, enter g b o r t .
c) Choose Enter. 3. Activate and save the changes to table ADM325X## to a new task within the same transport request used in the previous step of this exercise. The SAP system automatically prompts you for the new task. a) On the Dictionary: Change Table screen, activate the table by choosing Table —*■ Activate. b) On the Prompt for local Workbench request dialog box, enter the same transport request that you used for the SAP program ADM325X## and confirm the new task prompt.
Once activated, an Active status displays for the table on the Dictionary.Change Table screen. 4. Add entries to the table ADM325X##. a) On the Dictionary: Change Table screen, add additional table entries by choosing Utilities —*• Table Contents —> Create Entries. b) In the Table Insert screen, add your table entries.
c) Choose Save to save your entries. 5. Release your task. a) To release your task, go to the Transport Organizer (transaction SE09). b) Choose Display to display the transport requests and tasks assigned to your user ADM325X##.
c) On the Transport Organizer: Requests screen, select your tasks and choose Release Directly. 6. Release the transport request. a) On the Transport Organizer: Requests screen, select your transport request. b) Choose Release Directly.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
LESSON SUMMARY
You should now be able to: •
Perform modifications on repository objects
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 3
Learning Assessment
1. Customizing activities typically create or change entries in multiple client-specific tables. Which of the following enable this to take place? Choose the correct answers. | A Table Views B Table Labels | C Transaction STMS D Transaction SM30 2. Identify which statements are correct. Choose the correct answers. | A The project IMGs are cross-client. B The project IMG cannot be changed at any time. C All customizing activities are done directly within the project IMG. D A project IMG is the Implementation Guide for a specific customizing project. 3. Which of the following information can be found in the Transport Organizer? Choose the correct answers. | A Transport requests for customizing B Transport requests for repository objects C Global transport information and status D IMG project scope E Transport domain activities
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
4. A project team member can own several tasks belonging to the same transport request. Determine whether this statement is true or false. | True False 5. What are the three basic roles found in a typical customizing project? Choose the correct answers. | A Project manager B Customizer/Developer C Operating system manager D TMS administrator E Transport configurator 6. Which of the following transport requests can be found in the Transport Organizer? Choose the correct answers. | A Workbench request B Client Change request C Change Log request D Customizing request E Repository Change request 7. If the client is not configured for automatic recording of changes, the settings are saved but not recorded in a transport request. Determine whether this statement is true or false. | True False
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
8. What recommendations does change management for development include? Choose the correct answers. | A Restrict repository object changes B Define development standards | C Define customizing transport requests D Use projects to group transport requests E Establish project teams 9. Which of the following are attributes for repository objects? Choose the correct answers. | A Program identification B Package | C Original system D Person responsible E Original language 10. Which of the following statements about SSCR registration are true? Choose the correct answers. | A A user who uses the ABAP workbench to create, modify, or delete repository objects must register with SSCR. B All users must register with SSCR. C All SAP repository objects (not customer objects) that will be modified must register with SSCR. D Only SAP repository objects that will be enhanced must register with SSCR. E Only customer objects are required to be registered with SSCR.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
11. What are the different types of transport request classifications? Choose the correct answers. | A Object B Package C Unclassified D Local E Transportable
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 3
Learning Assessment - Answers
1. Customizing activities typically create or change entries in multiple client-specific tables. Which of the following enable this to take place? Choose the correct answers. [x ] A Table Views B Table Labels | C Transaction STMS |~x] D Transaction SM30
2. Identify which statements are correct. Choose the correct answers. [x ] A The project IMGs are cross-client. B The project IMG cannot be changed at any time. [~xj C All customizing activities are done directly within the project IMG. [x ] D A project IMG is the Implementation Guide for a specific customizing project.
3. Which of the following information can be found in the Transport Organizer? Choose the correct answers. |~X~| A Transport requests for customizing [~xj B Transport requests for repository objects [x ] C Global transport information and status D IMG project scope E Transport domain activities
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
4. A project team member can own several tasks belonging to the same transport request. Determine whether this statement is true or false. [x ] True False
5. What are the three basic roles found in a typical customizing project? Choose the correct answers. |~xj A Project manager |~xj B Customizer/Developer C Operating system manager |~xj D TMS administrator E Transport configurator
6. Which of the following transport requests can be found in the Transport Organizer? Choose the correct answers. |~xj A Workbench request B Client Change request C Change Log request |~xj D Customizing request E Repository Change request
7. If the client is not configured for automatic recording of changes, the settings are saved but not recorded in a transport request. Determine whether this statement is true or false. [x ] True False
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
8. What recommendations does change management for development include? Choose the correct answers. |~X~| A Restrict repository object changes [x ] B Define development standards | C Define customizing transport requests [~xj D Use projects to group transport requests |~X~| E Establish project teams
9. Which of the following are attributes for repository objects? Choose the correct answers. | A Program identification |~x] B Package [x ] C Original system [x ] D Person responsible [x ] E Original language
10. Which of the following statements about SSCR registration are true? Choose the correct answers. [x ] A A user who uses the ABAP workbench to create, modify, or delete repository objects must register with SSCR. B All users must register with SSCR. |~X~| C All SAP repository objects (not customer objects) that will be modified must register with SSCR. D Only SAP repository objects that will be enhanced must register with SSCR. E Only customer objects are required to be registered with SSCR.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
11. What are the different types of transport request classifications? Choose the correct answers. | A Object B Package
|~xj C Unclassified \x \ D Local |~X~| E Transportable
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Lesson 1 Describing the Transport Process Flow
159
Lesson 2 Importing Transport Requests Using TMS Exercise 7: Perform Imports Using TMS
164 173
Lesson 3 Defining the Quality Assurance (QA) Approval Procedure andTransport Proposals Exercise 8: Perform a QA Approval Exercise 9: Create and Manage a Transport Proposal
184 189 199
Lesson 4 Maintaining the Import Process Exercise 10: Monitor the Import Process
205 215
Lesson 5 Monitoring Transport Activity Exercise 11: Troubleshoot Import Problems
225 235
Lesson 6 Cleaning Up the Transport Directory
244
UNIT OBJECTIVES
•
Describe the steps in the transport process
•
Perform an import using TMS
•
Identify transport request import options
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
Identify transport strategies
•
Manage the transport and relocation of copies
•
Perform the QA approval procedure
•
Execute the transport workflow
•
Monitor the import process
•
Control transports between SAP systems for upgrading SAP releases
•
Describe the monitoring tools in TMS
•
Check for critical objects
•
Manage code freeze
•
Display the transport directory and log files
•
Troubleshoot transport errors
•
Manage the transport directory
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 4 Lesson 1 Describing the Transport Process Flow
LESSON OVERVIEW
This lesson provides an overview of the transport process.
LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Describe the steps in the transport process
Overview of the Transport Process
Previously, transports were performed at the operating system level. With the introduction of the Transport Management System (TMS), transports are performed from within the SAP system. In the TMS, transport requests are transported along predefined transport routes. You can define multiple consolidation and delivery routes. The import procedure can be performed by any authorized user from within the SAP system. Nearly all functions in transaction s t m s are executed by tp commands at the operating system level, which someone with technical knowledge can also perform manually. Transport requests to be imported are displayed in the import queue of the target system in the SAP system. Using TMS, you can import a complete import queue, that is, all transport requests can be imported that were exported from the development system. This step ensures that no import errors occur due to missing objects and that newer versions of an object are not overwritten by older versions. For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Development
Quality Assurance
Virtual Delivery
Production
1 0 0 CUST
100 TST
100
100 PRD
Project ABC TR1 TR2
o
Cl
x
LU
■co CO
buffer
data
DCC TR1 -j-p2
QCC
VDE
PCC
> TR1 TR2
- ► cofiles ^R1 TR2 Figure 69: Export of a Project from DEV
The first step in the transport process is to release a transport request and export all the associated objects from the database of the development system (DEV) to files in the common transport directory at file system level. For each transport request released, the data is exported to a data file in the subdirectory data and a control file is written to the subdirectory cofiles. During the export, the entries required for the subsequent import are created in the import buffers of the target systems, and a test import can be performed. In the directory buffer at file system level is an import buffer file for each SAP system in the transport domain. The file is named after the corresponding SAP system ID and contains control information regarding the transport requests to be imported and the order of import. Several transport control commands can be used to manage the import buffer files at the operating system level. The control information in the import buffer files is read and represented in import queues accessed from within the SAP system. An import queue shows all transport requests that are listed in the corresponding buffer.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Development
Quality Assurance
Project ABC 100 OUST
100 TST
Virtual Delivery
Production
1 0 0
100 PRD
VDE
PCC
TR1 TR2
QCC^)~
DCC c;-----
/usr/sap/trans
buffer
data
DCC
QCC
VDE
PCC
TR1 TR2 Upon successful import into QCC the system creates an entry in the VDE buffer. These entries are “inactive” until the QA Approval procedure is completed.
cofiles TR1 TR2
Figure 70: Import of a Project into QAS
Using TMS from within the SAP system, the second step in the transport process is to import all transport requests listed in the import queue of the Quality Assurance System (QAS). TMS performs the import by starting the transport control program tp at the operating system level. After the successful import into the quality assurance system, the transport requests are placed in the import buffer and import queue of the Production system (PRD) and any other delivery system.
Note: If the Quality Assurance (QA) procedure is activated, the entries are placed in the import queue of PRD so they cannot be imported without approval.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Development
Quality Assurance
Virtual Delivery
Production
Project ABC TR1 TR2
buffer
DCC
PCC
TR1 TR2
TR1 TR2
data
VDE
QCC
/After testing and validation in the QAS system the transports are approved for import. Approval updates the status of the buffer entries for VDE to “active”. All approved transport requests are then transferred to the PRD buffer using Report RSTMS DIST APPROVED REQUESTS.
cofiles TR2
Figure 71: QA Approval
After import to the quality assurance system, QAS, test the objects for possible errors. Correct errors in the development system, DEV, and the import the changes again into QAS. During import into QAS, the additional transport request is added to the buffer of the production system, PRD.
Development
Quality Assurance
Virtual Delivery
Production
100CUST
100TST
100
100 PRD
DCC
QCC
VDE
Project ABC TR1 TR2
1 /usr/sap/trans buffer
data
DCC TR1 TR2
QCC
VDE
TR1 TR2
TR1 TR2
cofiles TR1 TR2 Figure 72: Import into PRD
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
After all the transport requests that were imported into QAS have been thoroughly tested and verified, you approve the transport requests.
Note: If the Quality Assurance (QA) procedure is activated, the status of the entries in the import queue of PRD changes from inactive to active, and the transport requests are ready for import into the PRD.
O
Hint: Always approve and import complete projects. By doing these steps you minimize the risk of forgetting single transport requests and you keep the correct sequence of the transport requests.
Always use TMS to import all transport requests. To ensure that there is no negative effect on production activities in PRD, ensure that errors and their corrections are imported in the correct order. LESSON SUMMARY You should now be able to:
•
Describe the steps in the transport process
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 4 Lesson 2 Importing Transport Requests Using TMS
LESSON OVERVIEW This lesson describes how to import transport requests using TMS. LESSON OBJECTIVES After completing this lesson, you will be able to:
•
Perform an import using TMS
•
Identify transport request import options
•
Identify transport strategies
•
Manage the transport and relocation of copies
Im p o rt Queue and Im p o rt B u ffe r Imports Using TMS
The most important tool used to perform imports using TMS are the import queues that reflect the SAP system-specific import buffers at file system level. The import queues display the requests that are to be imported, in the correct order. The import queues of all SAP systems are displayed in each SAP system of the transport domain. You can perform imports to all the SAP systems from any SAP system in the domain.
Note: When importing a transport request into a different SAP system than the one you are logged on to, provide a user ID and password for the SAP system in which you import. To access the TMS import overview, use transaction s t m s and choose Overview —> Imports. The import overview shows the current status of the import queue of each SAP system of the transport domain. If you navigate in an import queue of one SAP system, you can see all future imported transport requests.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
With the extended transport control, you can have multiple target clients for one target system. You can choose to see one row for each target client or only one row per transport request. To improve performance, data is read from the transport directory only the first time you start TMS. After that the information shown is buffered in the database. The time stamp in the import overview indicates how recent the data is. The internal buffers of TMS become invalid at midnight. To refresh the data, choose Edit —► Refresh. It may be more convenient to have the refresh performed periodically in the background. For this method, choose STMS —► Overview —» Imports —> Extras —► Update All Import Queues. We recommend running this refresh hourly using r s t m s c o l . Import Queues and Import Buffers
r Import queue
1 DEVK900827 2 DEVK900833 3 DEVK900835 4 DEVK900837 End of import queue 5 DEVK900839 6 DEVK900841 7 DEVK900843
^
End mark
SAP system
r
File system
Import buffer
Transport Directory
^
MDEVK900827 DEVK900833 DEVK900835 DEVK900837 Stopmark DEVK900839 DEVK900841 DEVK900843
V. L
____
Stopmark
A
Figure 74: Import Queues and Import Buffers
The terms import buffer and import queues are related. The import queue in the SAP system represents the import buffer located in the transport directory. The import queue highlights the requests that will be imported during the next complete import (import all). Since there are end For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
marks, there may be more requests in the import buffer than those requests highlighted in the import queue. The end mark and stopmark are the corresponding markers in the import queues and buffers respectively. These markers indicate that only the requests before the mark will be imported by an import all. Regardless of how the end mark or stopmark is created, the mark is set in both the import buffer and the import queue. An end mark is indicated in an import queue through the statement End of import queue. In an import buffer, the term stopmark is visible. There can only be one end mark or stopmark in each import queue or import buffer. To set an end mark/stopmark by closing an import queue, in the import queue choose Queue —*• Close. This step is analogous to the operating system command tp setstopmark. The status bar shows the action performed. You can remove an end mark/stopmark by opening an import queue manually, typically not required, in the import queue screen choose Queue —> Open. Opening an import queue is analogous to the operating system command t p d e l s t o p m a r k . Using TMS, you can move end marks to any position in the import queue in front of a transport request (Queue —► Move End Mark). This step is analogous to the operating system command
tp
MVSTOPMARK.
[& Queue
Edit
goto
Bequest
&
Extras
Environment
6 0 1
System
Q N H
C
C
Help
f l C
l M
9 1
Im p o r t Q u e u e : S y s te m Q A S
<&> ID 3 % B £3
SS
® H 0
Requests for QAS: S
Number
Request
QM
Clt
RC
OMC
Owner
Project
Short Text
Figure 75: Import Queue
Import Queue Tasks Use the import queue to do the following: View the status of transport requests Access object lists, documentation, and transport logs Close and open the queue, and move the end mark Import all transport requests, complete projects, preliminary requests, and selected requests according to filter settings Add, delete, and forward requests To keep target SAP systems consistent, you need deadlines to coordinate the release of transport requests by developers. To prevent transport requests released after the deadline from being imported, the import queue can be closed. These transport requests are positioned after an
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
end mark in the queue for the next import. Only the requests before the end mark are imported in the next import. In exceptional cases, you can forward a transport request to another SAP system before being imported into the defined target system. For example, before being imported into the quality assurance system, you might need to rush a request to a training system. To import to a target system outside the predefined transport routes, in the Import Queue screen, choose Request —► Forward —► System. You can also delete transport requests from or add them to an import queue. Object dependencies may cause inconsistencies in the target system after the next import. For example, if you delete a request containing a new data element, all other requests containing tables that depend on that data element will fail. To avoid these inconsistencies, you are strongly advised not to delete individual transport requests. Make your corrections in the development system and release a new transport request.
O
Hint: Always import all transport requests into the production system, even when they contain errors. Be sure to include their corrections.
Transport Request Options
Request 1 DEVK900827 2 DEVK900833 3 DEVK900835 4 DEVK900837 5 DEVK900839 6 DEVK900841 7 DEVK900843
Project DEV_P00001 DEVP00002 DEV_P00002 DEVP00002 DEV_P00002 DEV_P00001 DEV P00002
Date
Import all requests
Execution | Options
Figure 76: Import all Transport Requests
To import all transport requests in the queue (performing what is known as an import all), choose the Import All Requests button. The Start Import dialog box appears. If you have configured the extended transport control, the target client is fixed. Otherwise, you can either choose a target client or keep the default target client. The default is the source client. (For this reason, name all major clients in all SAP systems alike.)
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Note: If you start the import from another SAP system in the transport domain, a logon window from the target system is displayed. In the Start Import dialog box, there are several options to control the import in the following list: •
In the Date tab, you can schedule the import.
•
In the Execution tab, you can select whether TMS starts tp synchronously or asynchronously. Selecting asynchronously means tp works in the background so that your user session is not blocked for the duration of the import.
•
In the Options tab, you can select expert options, the unconditional modes. The options and their defaults vary according to the selected import method and the configured transport strategy.
The Import Overview screen indicates whether the import is running. After the import, the end mark is removed and the queue is opened again automatically. After transport requests have been imported successfully, they are automatically added to the import queue of further target systems. When using the QA approval procedure function, all requests in the import queue of the subsequent SAP systems are set to inactive. The configured transport route specifies, which transport requests are automatically forwarded to which target systems. If an import containing one or more inactive requests is started, the TMS will not perform the import.
Note: If all requests for import have been checked for applicable approval steps (approved or rejected), you can then import all the transport requests into the delivery systems. If all the requests for one project have been approved, regardless if they are unprocessed or rejected in the work list, you can import them into the delivery system. If you perform an import through an import all, objects are imported in the correct sequence as they are listed in the import buffer file on file system. If transport requests near the start of the list and those transport requests near the end of the list affect the same objects, the final versions of the objects after import will represent the latest changes. As a result, the incorrect objects do not affect your production environment. They are not imported at all. You can deactivate the ability to perform a complete import (import all) for each SAP system using the TMS parameter n o _ i m p o r t _ a l l .
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Request 1 DEVK900827 2 DEVK900833 3 DEVK900835 4 DEVK900837 5 DEVK900839 6 DEVK900841 7 DEVK900843
Project DEV P00001 DEV P00002 DEV P00002 DEV P00002 DEV P00002 DEV P00001 DEV P00002 " Filter project D E V P 00001
Ir
Request 1 DEVK900827 6 DEVK900841
Import all requests of one project
Project DEV P00001 DEV_P00001
Figure 77: Import Complete Project
Before performing the import, we recommend setting the end mark to close the import queue. This step avoids unintentionally importing other transport requests that may appear in the import queue. You can set a filter on the import queue to limit the displayed transport requests to transport requests with specific properties so that you can see only those transport requests that belong to a specific project. To set a filter, place the cursor in a row of the import queue and choose the Filters button. To prevent transport requests being imported from unapproved projects, use the filter to import only the transport requests belonging to approved projects. Since SAP Web AS ABAP 6.40, it has been possible to use one tp process to import the requests of multiple projects into multiple target clients. Request 1 DEVK900827 2 DEVK900833 3 DEVK900835 4 DEVK900837 5 DEVK900839 6 DEVK900841 7 DEVK900843
Project DEV_P00001 DEV_P00002 DEV_P00002 D EVP00002 D EVP00002 DEV_P00001 DEV P00002
Select requests
* Request 1 DEVK900827 2 DEVK900833 3 DEVK900835 4 DEVK900837 5 DEVK900839 6 DEVK900841 7 DEVK900843
Project D E V P 00001 DEV P00002 DEV P00002 DEV P00002 DEV P00002 DEV P00001 DEV P00002
Import selected requests
Figure 78: Import Single Transport Requests (Preliminary Import)
In contrast to standard imports, preliminary imports are imports of single transport requests. We strongly recommend only using project-wide or full imports because of object dependencies and For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
the risk of inconsistencies when importing individual requests. For example, an ABAP report in one request can be successfully imported, but the table that it refers to can be in another request that has not yet been imported. Until the table is imported, executing the report generates short dumps. Use preliminary imports only in exceptional cases. To minimize the risks associated with preliminary imports, the request remains in the import queue after the import and is reimported the next time the entire import queue or the corresponding project is imported. This step guarantees the correct import sequences. The import sequence is defined by the Leave Transport request in queue for later import option, which is automatically marked depending on the transport strategy. If requests in the import queue depend on transport requests in other projects, TMS verifies this condition by default. The import is only possible when the predecessor's relationships will not be damaged. To change this default setting, choose Request —► Import and select Continue import. For example, it may be necessary to specify additional options when performing a preliminary import in the following situations: •
Ignore that the transport request has already been imported
•
Overwrite originals
•
Overwrite objects in unconfirmed repairs
•
Ignore invalid transport type
Importing and Marking Objects for Import The objects from the transport requests marked for import will be imported as follows: •
All objects of all selected transport requests are merged together.
•
First of all the objects are sorted according their level (such as, table definitions before programs).
•
In the case of an object in more than one transport request, only the version in the last transport request is imported (according to the sequence in the import queue).
Hint: If the transport strategy is set to mass transport, this sequence is used for import all, import project, and import single. Otherwise, this sequence is only used for import all and import project.
Import Scheduling
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Depending on whether you choose import by project, individual import, import all, or special transport workflow, and especially on the SAP release and SAP support package level, the available options may vary. Remember to check your logs after the import. When starting an import, you can select the following options in the Date tab: Immediate Selecting this option immediately starts the import. At Start Time Selecting this option starts the import at the specified time. The import is scheduled as a background job in the target system. If you also enter a date and time in the No Start After field, the import is started in the time frame between the times entered in Planned Start and No Start After fields. If there is no background process available during this time, an import does not occur. If you want the import to be performed regularly, enter a time in the Period field. After Event Selecting this option starts the import only after a specified event is triggered. If you select Execute Import Periodically, the import is started each time the specified event is triggered. Otherwise, the import is started only the first time the event occurs.
Note: The Period field does not exist for individual transports and the special transport workflow. From the import queue of each SAP system, you can monitor and maintain all planned imports by choosing Goto —*■ Job Monitor.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Development system
Quality assurance system
DEV
QAS
CUST
i t
Production system PRD ★
QTST
i t
i TEST
PROD
1 [TRNG
Transport points
Figure 80: Timing T ransports
Circumstances that Determine Timing of Transport
The timing of a transport is determined by the following: •
Role of client
•
Synchronization needs
•
Testing and verification
•
Code freezing requirements
Requirements for Importing into PRD
The system you work on may determine what you can do. While importing into QAS requires no ongoing testing related to the affected business processes, importing into PRD requires the following: No users working with the affected business processes No batch jobs running related to the affected business processes No RFC communication related to the affected business processes After export, a request is not automatically imported, but must be manually imported. When planning imports, include enough time to accommodate post-import tasks such as the quality assurance testing. We recommend planning imports at regular intervals, such as monthly, weekly, or daily, using Import All into the target system. Frequent importing is not recommended. Consider the following actions when you plan your imports: •
Releases of transport requests
•
Copy into a client in the same SAP system using transaction s c c i (unit testing)
•
Imports into clients in downstream SAP systems
Consider the timing of transports based on the following factors: •
Clients and their roles in your SAP system landscape
•
Synchronization requirements, that is, when changes are required in different SAP systems, prior backups•
•
Code freezing requirement
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 4 Exercise 7 Perform Imports Using TMS
Business Example
The project team leader has confirmed and released all required transport requests from the development system. The transport administrator can now import the transport requests into the target systems. The transport administrator follows the guidelines established for the transport strategy and the transport schedule. This way the transport administrator can ensure that the program distributes changes consistently to all systems in the landscape. Review Import Queues
Review import queues for all systems.
Hint: Before proceeding, release all transport requests from system DCC, client 100, if not previously done.
1. Determine whether any requests are waiting to be imported. 2. Are there any requests to be imported into the production system (PCC)?
3. Review the current status of the import queues of all SAP systems. Determine whether the import queue of QCC is open or closed. Import Queue for a System
Review the import queue of the quality assurance system (QCC). 1. Display the requests that are to be imported into the quality assurance system (QCC). Which SAP users released the requests? 2. Display the objects in the transport requests owned by your user account. Import Transport Requests into a System
Import all transport requests of a project into the quality assurance system (QCC). 1. Display more information about the transport requests now waiting in the import queue for QCC. Use the column output in the Import Queue: System QCC screen. Log on with the following details:
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Data
Data Value
System
QCC
Client
100
Column Output T
Type of transport request (IV - Customizing and K - Workbench Requests)
Column Output UMO
Unconditional modes (preliminary imports*)
Hint: All preliminary imports have the unconditional mode / after import. This mode indicates that the request can be reimported into the target system without manually setting any special options.
2. Set a filter so that the import queue displays only the transport requests belonging to your project. Import all your transport requests into the quality assurance system by performing a project import of your project.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 4 Solution 7 Perform Imports Using TMS
Business Example
The project team leader has confirmed and released all required transport requests from the development system. The transport administrator can now import the transport requests into the target systems. The transport administrator follows the guidelines established for the transport strategy and the transport schedule. This way the transport administrator can ensure that the program distributes changes consistently to all systems in the landscape. Review Import Queues
Review import queues for all systems.
Hint: Before proceeding, release all transport requests from system DCC, client 100, if not previously done.
1. Determine whether any requests are waiting to be imported. a) Enter s t m s in the Command field in the top left of the screen. b) To see the import overview of all SAP systems in the transport domain, go to the Transport Management System screen andchoose Overview —► Imports. c) To see the latest status, go to the Import Overview screen and choose Refresh. d) To see how many requests are ready to be imported into a specific SAP system, go to the Import Overview screen and view the Requests column. At this point, there are requests ready for import into the quality assurance system (QCC). Note: The number of requests ready for import to a particular SAP system may differ from the actual number of requests in the import queue. This number can be different, for example, if there are nonstandard transport requests in the queue or if there are additional requests after an end mark.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected] © Copyright. All rights reserved.
0
175
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
2. Are there any requests to be imported into the production system (PCC)? The only requests for import into the production system (PCC) are those requests that the system has successfully imported into the quality assurance system (QCC) and that have been approved for import into PCC due to the activation of QA Approval Process.__________ 3. Review the current status of the import queues of all SAP systems. Determine whether the import queue of QCC is open or closed. a) To verify the current state of each system's import queue, go to the Import Overview screen and select the Status column. b) Choose Extras —► Legend to see the Legend: Import overview screen that explains the meaning of the icons associated with SAP systems. The legend shows whether the system is open or closed. Import Queue for a System
Review the import queue of the quality assurance system (QCC). 1. Display the requests that are to be imported into the quality assurance system (QCC). Which SAP users released the requests? a) Enter s t m s in the Command field in the top left of the screen. b) From the Transport Management System screen, choose Overview —> Imports to see the import overview of all SAP systems in the transport domain. c) In the Import Overview screen, double-click q c c import queue in the Queue field.
d) To verify the latest status, go to the Import Queue: System screen and choose Refresh. The screen lists all requests to be imported into the QCC. The Owner field gives information about the user who released the specific request. 2. Display the objects in the transport requests owned by your user account. a) In the Import Queue: System screen, view the list of requests owned by your user account in the Owner field. b) Double-click the request number, or select the request and choose Request —> Display —► Object List. c) To see all objects when you click the folders, go to the Display Object List screen and expand the view of the object list. Import Transport Requests into a System
Import all transport requests of a project into the quality assurance system (QCC). 1. Display more information about the transport requests now waiting in the import queue for QCC. Use the column output in the Import Queue: System QCC screen. Log on with the following details: Data
Data Value
System
QCC
Client
100
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Data
Data Value
Column Output T
Type of transport request (IV - Customizing and K - Workbench Requests)
Column Output UMO
Unconditional modes (preliminary imports*)
Hint: All preliminary imports have the unconditional mode / after import. This mode indicates that the request can be reimported into the target system without manually setting any special options. a) Enter s t m s in the Command field in the top left of the screen. b) Navigate to the Import Queue screen. c) From the Import Queue: System QCC screen, choose Edit —► Display More. d) For system QCC, verify the contents of column T and UMO. 2. Set a filter so that the import queue displays only the transport requests belonging to your project. Import all your transport requests into the quality assurance system by performing a project import of your project. a) From within the QCC system, enter STMS in the Command field. b) To verify the import overview of all SAP systems in the transport domain, go to the Transport Management System screen, choose Overview —*• Imports. c) Double-click the SAP system qcc. All requests that are waiting to be imported into QCC appear. d) Mark the Project column and choose Edit —» Filters. e) In the Set Filter dialog box, enter the project name in the Request field and choose Copy (Enter). f) In the Import Queue screen, perform a project import and choose Queue —► Start Import. g) On the Options tab in the Import Transport Request window select the Leave Transport Request In Queue for Later Import and Ignore Invalid Component Versions checkboxes. h) In the subsequent dialog boxes, choose Continue and Yes.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
T ra n s p o rt S tra te g ie s Transport Strategy Types
There are three different transport strategies available, which include the following: •
Queue-controlled mass transports (default)
•
Queue-controlled single transports
•
Workflow-controlled transports
Hint: The transport strategy defaults to queue-controlled mass transports.
Mass transports provide a good solution when there are many transport requests to administer and you want to automate the process. The continuous use of mass transports is the most secure way of keeping your SAP systems synchronized and consistent. Before you import mass imports into your production systems, check all requests in the quality assurance system and confirm their transport into other SAP systems. Use the TMS quality assurance procedure when doing this step. Define mass imports as the import method for the relevant SAP systems. To do this step, choose the transport strategy queue-controlled mass imports. The administrator can schedule the imports periodically in TMS, or start each import manually. Import single transport requests (single imports) before others in the queue for special cases. Transport requests that are imported in advance by the TMS are imported again in the regular import. You can use the transport workflow to import single imports in advance. If you want to maintain a production system with a small amount of specific transports, it is best to import single requests rather than using importing all changes waiting for import. Use single transports if you have fewer changes to transport and your organization prevents you from having a fixed transport schedule. This method entails extra work for the administrators compared to periodic imports. Developers must pay extra attention to the consistency of their transport requests. If a few developers are working on a project, or if the developers work closely with the administrator, they make their own single transports. You want to make specific single transports into your SAP systems, but would rather have this step done by the SAP system administrator, we recommend that you use the transport workflow. This method automatically triggers a workflow when you release a transport request. The workflow ensures close communication between development and administration. As a prerequisite, configure the transport workflow for your SAP system. Maintain Transport Strategy
If you want to work with queue-controlled, single transports or workflow-controlled transports instead, change the configuration as described in this section.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Maintain Transport Strategy Procedure
1. Enter transaction
STMS
in the Command field.
2. Choose Overview —► Transport Routes. The Display Transport Routes screen appears and shows the existing transport routes in the transport domain. 3. Switch to the change mode by choosing Configuration —► Display <-> Change. 4. Position the cursor on the SAP system for which you want to choose a transport strategy. 5. To display the Change System Attributes dialog box, choose Edit —► System —► Change. 6. Select the System Attributes tab and select your transport strategy.
Note: Within a transport group, set all SAP systems either to Queue-controlled transports or Workflow-controlled transports.
7. Choose Transfer. 8. Choose Configuration —> Distribute and Activate Settings in TMS and Transport Strategy
Features of the transport strategy can include the following: Queue-controlled mass transports By default, the import option, Leave transport request in queue for later import, is activated when performing import single.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Hint: The import option, Leave transport request in queue for later import, causes transport requests that have been imported as single transport requests to be imported in the correct order in the next import of all transport requests. This option is useful if you have to make preliminary imports for individual transport requests. This option prevents older objects from being imported at the next regular import of all the transport requests. Queue-controlled single transports •
By default, the import option, Leave transport request in queue for later import, is deactivated.
Hint: If you supply an SAP system only with single transport requests, this option is not useful since the transport requests remain in the queue after the import and have to be manually deleted from the import queue.
•
The button changes according to the requirements of the single import strategy (for example, it contains a select function).
•
In the Import All Requests function is only available if you have selected one or more projects using the filter function. This selection prevents importing all the transport requests in the queue accidentally.
Workflow-controlled transports •
Transport proposals are created automatically when transport requests are exported.
•
The import options correspond to those options for single transport requests.
•
Imports become linked to the processing of transport proposals in the TMS worklist.
•
A warning appears in the import queue when you try and make transport requests without using the transport workflow.
The following parameters for the transport control program and the Change and Transport System (CTS) are set according to the chosen transport strategy: Table 6: tp parameters for transport strategies Parameter
Value for Queue-Control led Mass Trans ports
Value for QueueControlled Single Transports
Value for Work flow-Controlled Transports
IMPORT_SINGLE_ONLY
0
1
1
NO_IMPORT_ALL
0
1
1
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
IMPORT_SINGLE_STRATEGY
0
1
0
WORKFLOW_STRATEGY
0
0
1
REPEATONERROR
9
8
8
STOPONERROR
9
9
9
The tp parameter STOPONERROR specifies at which return code the import stops. REPEATONERROR specifies the return code after which the import is not classified as successful and is repeated. For example, with Single Transports, return code 8 is classified as a nonsuccessful import and is repeated. With Mass Transports, return code 8 would be a successful import.
Hint: Do not manually change the parameters that are relevant to the transport strategy. TMS generates these parameters each time the transport route configuration is changed.
T ra n s p o rt o f C o pies and R elo catio n D E V (1 )/1 0 0 Create Request O Customizing request
O W orkbench
request
Transport to any SAP system, without following transport routes
^ T r a n s p o r t o f copies
- i
Relocation o f objects w /o package change Relocation o f objects w ith package change Relocation o f Com plete Package
Permanent future development of all objects of package in different development system
~— r—— —— Temporary development of objects in different development system
Permanent future development of objects in different development system
Figure 82: Transport of Copies and Relocation
Select Transport of copies to transport objects to another SAP system of your choice. Use this function if the target system is not a consolidation system from the current SAP system. The objects are transported in the version they have in the current SAP system. The original location of the objects is not changed. The transport request will not be added to the import queue of a subsequent SAP system. Select Relocations of objects w /o package change when development work on objects is to take place in another SAP system temporarily. Special developments may be carried out in a separate SAP system. For example, this process occurs without interfering with the development process. This request type allows you to move the original location of objects to the target system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Select Relocations of objects with package change when the development system of individual objects changes permanently. This request type allows you to change the original location of objects to the target system and change the package of the objects at the same time. Due to the automatic package change, the objects have the desired transport attributes immediately after being imported into the target system of the request. Select Relocations of Complete Package when the development system of a complete package is to be changed on a permanent basis.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
LESSON SUMMARY You should now be able to: •
Perform an import using TMS
•
Identify transport request import options
•
Identify transport strategies
•
Manage the transport and relocation of copies
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 4 Lesson 3 Defining the Quality Assurance (QA) Approval Procedure andTransport Proposals
LESSON OVERVIEW This lesson describes the Quality Assurance (QA) approval procedure and transport proposals. It also covers transport workflows.
LESSON OBJECTIVES After completing this lesson, you will be able to: •
Perform the QA approval procedure
•
Execute the transport workflow
QA Approval Procedure Configuration The TMS quality assurance (QA) approval step increases the quality and the availability of the production systems by letting you check transport requests in the quality assurance system before delivering them to subsequent SAP systems. When you activate the QA approval procedure, transport requests are only forwarded to the delivery systems if all the QA approval steps are processed for the request in the QA system and the request has been approved. (When you configure the QA system, you determine how many QA approval steps have to be processed for each request.) All checks for an approval step must be successful or the entire request cannot be approved. You can only import completely approved requests into the delivery systems. Rejected requests are not imported into the delivery systems of the QA system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Before you can process transport requests you should configure the QA approval step. Ensure that the SAP system landscape and/or transport domain is set up so that there is at least one development, one quality assurance, and one production system. Attributes of a QA System
The SAP system to be configured as the QA system must have the following attributes: •
It must be the target of at least one consolidation route (starting from a development system).
•
It must deliver to at least one additional SAP system.
In the SAP system attributes for the chosen SAP system, the option delivery after confirmation must be set. In the approval procedure, you can define which users must provide approval so that the transport can be imported into the delivery system. After configuration, the QA worklist is automatically set up. All the requests imported into the QA system are included in the QA worklist. Process Flow in QA Approval To display the QA worklist, use transaction s t m s and choose Overview — > Imports —>Goto —► QA worklist. The date/time at the upper-right side of the screen indicates when the QA worklist was last updated: the upper-left side indicates how many requests remain to be processed. The list displays the transport requests corresponding to the selected approval steps. By default, the transport requests corresponding to all approval steps are shown in transaction s t m s . T o select the approval step whose corresponding transport requests you wish to see, choose Worklist —>Select Approval Step. By double-clicking various items in the table listing the transport requests, you obtain further information on those items.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Development
Quality Assurance
Virtual Delivery
Production
Project ABC TR1 TR2
buffer
data
DCC
TR1 TR2
QCC
VDE
PCC
TR1 TR2 /After testing and validation in the QAS system the transports are approved for import. Approval updates the status of the buffer entries for VDE to “active”. All approved transport requests are then transferred to the PRD buffer using Report RSTMS DIST APPROVED REQUESTS.
cofiles TR2
Figure 84: QA Landscape Graphic Import Process QA Approval
Hint: From a security point of view, do not allow users, except the administrator, to enter transaction s t m s . Check out the subordinate transactions of s t m s by searching for entries in table TSTC (through transaction S E 1 6 ) beginning with STMS*
Hint: In the QA approval process, approve complete projects, not just single transport requests. Test the requests in a QA worklist before importing them in the delivery systems. The QA status Rejected means that one or more approval steps of a request were rejected by the responsible person. A request is approved only if all the approval steps have the status Approved. QA Worklist
In the QA worklist, you can see the following: QA status (St) Overall status (GS) Number of steps (Nr) Requests can be imported into the delivery systems only when all the requests ready for import have received approval according to the various approval steps. If all the requests for one project
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
have been approved, they can be imported into the delivery system if other projects still have unprocessed or rejected requests in the worklist. Requests with the QA status Rejected as well as unprocessed requests in the worklist are not imported into the delivery systems. The approval or rejection of a single step can be changed, as long as not all approval steps were performed. As soon as all defined approval steps are performed, you can no longer change the decision. We recommend not rejecting requests containing errors, but correcting the error using subsequent transport requests and approving the affected transport requests as an entire package. &
Wofkist
Edit
fio to
e ri
Refluest
Extras
System
Help
^T
©cos 10
Q A W o r k lis t: S y s te m Q A S U )
&
9
^
^ ? s a v e
^
®
H B
D -
^
r
l
D
S
^
t
Q
'
H
8 &
E l
@
§?Entries for QAS 1
14.09.2011 17:24:2S
)Z( Approval step Overall view (no step selected)
Humber 1 2 3 4 S € 7
Request
Mdt
Owner
DCVK900244 DEVK900250 DCVK900252 DEVK900242 DEVK900236 DCVK900261 3CVK900257
100 100 100 100 100 100 100
CATOH CATOH CATOH CATOH CATOH ADK32S-00 ADH325-00
Project
V
Development Development Development Development Customizing Development Development
part part part part part part part
2 4 S 1 1 10 6
Type
W ho approved quality assurance testing fo r this transport request?
ca §
& &
Description Distribution required New In Process Request rejected Request approved
Figure 85: QA History
Approval Statuses
The meaning of the different approval statuses is the following: •
Distribution required: The QA status for this request could not be distributed. After correcting errors, repeat the distribution.
•
New: The request is new in the worklist.
•
In processing: There are still some approval steps for this request that have to be processed.
•
Request rejected: The request was rejected for an individual step or for all steps (depending on the view displayed in the QA worklist).•
•
Request approved: The request was approved for an individual step or for all steps (depending on the view displayed in the QA worklist).
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
From the QA worklist screen, you can access the QA history by choosing Goto —>QA History. The QA history shows all the requests for a specific period that are no longer displayed in the QA worklist. Requests are no longer displayed in the QA worklist when they have been approved or deleted. The default period for the QA history is 30 days but this time period can be changed. To determine who was responsible for approving a transport request, choose Request —>Display —>QA status.
Note: The QA history is stored in the database of the QA system (the QAS system). If you perform a database or SAP system copy from PRD to QAS, the history is lost. To prevent the QA history from being deleted in this way, see SAP Note 397138.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 4 Exercise 8 Perform a QA Approval
Business Example
Import transport requests into the production system that you have previously tested in the quality assurance system. For the SAP system administrator, you cannot tell if the transport request objects were tested, therefore the quality assurance procedure allows you to ensure that objects are tested before we import while identifying the responsible person. The special transport workflow can be integrated into the transport management system. Use the transport workflow in situations where it may be necessary to transport an urgent correction directly into the production system bypassing the configured transport route. Or, use it for importing transport requests into the quality assurance system even though the schedule does not include regular imports. Perform Quality Assurance Testing
Perform quality assurance testing after doing successful imports into the quality assurance system. 1. After a successful import of transport requests, the functionality of the SAP system must be extensively tested. How is this test performed?
2. Verify that the customizing entries that you transported exist in the quality assurance client. Log on with the following details: Data
Data Value
System
QCC
Client
100
Transaction
SPRO.ADMIN
3. Verify that the development objects you transported exist in the quality assurance system. Log on with the following details: Data
Data Value
System
QCC
Client
100
ABAP Program
ZPGM_## (Replace # # with your user num ber.)
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Data
Data Value
Package
ZPACKAGE_## (Replace # # with your user number.)
Transaction
SE38
Perform the QA Approval Procedure
Perform the QA approval procedure that permits the import of transport requests into the production system (PCC). 1. Once you import transport requests into the QCC system with client 100, the system places the requests into the import queue of the subsequent SAP system. Display the status of your transport requests in the import queue of the subsequent SAP system. Is an import of this transport request into the subsequent SAP system now possible? One subsequent SAP system is the production system p c c ,client 100. 2. Perform the quality assurance approval procedure. Look at the QA worklist of the quality assurance system. Use the filter to display only the transport requests for your project. Log on with the following details: Data
Data Value
System
QCC
Client
100
Transaction
STMS
3. Select the approval step. 4. Display the import queue of the subsequent system. 5. Are your approved requests ready for import into our Production system PCC?
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 4 Solution 8 Perform a QA Approval
Business Example
Import transport requests into the production system that you have previously tested in the quality assurance system. For the SAP system administrator, you cannot tell if the transport request objects were tested, therefore the quality assurance procedure allows you to ensure that objects are tested before we import while identifying the responsible person. The special transport workflow can be integrated into the transport management system. Use the transport workflow in situations where it may be necessary to transport an urgent correction directly into the production system bypassing the configured transport route. Or, use it for importing transport requests into the quality assurance system even though the schedule does not include regular imports. Perform Quality Assurance Testing
Perform quality assurance testing after doing successful imports into the quality assurance system. 1. After a successful import of transport requests, the functionality of the SAP system must be extensively tested. How is this test performed? The QA system must use the following guidelines: You need a dedicated quality assurance system with a well-defined set of test data, for example, a copy of the production system. Ensure existing functions work even after the import of new changes and additional functions. You use test scripts automated with a tool such as eCATT to test business functions. You compare the results of the test scripts with desired results. You note all inconsistencies and forward them back to the customizers and developers for correction in the development system.______________________________________________________________________ 2. Verify that the customizing entries that you transported exist in the quality assurance client. Log on with the following details: Data
Data Value
System
QCC
Client
100
Transaction
SPRO.ADMIN
a) To substantiate customizing, use the SAP Reference IMG transaction s p r o _ a d m i n to verify that some of your customizing objects exist in the client 100 in q c c .Customizing refers to your country settings from the Customizing exercise.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
The existence of changes is not enough verification. You also have to test the flow of processes and whether the data works in a real-life scenario. 3. Verify that the development objects you transported exist in the quality assurance system. Log on with the following details: Data
Data Value
System
QCC
Client
100
ABAP Program
ZPGM_## (Replace # # with your user num ber.)
Package
ZPACKAGE_## (Replace # # with your user number.)
Transaction
SE38
a) Enter S E 38 in the Command field on the top left of the screen. b) To verify if the program exists, enter z p g m _## in the Program field, choose the Attributes radio button and then select Display. c) On the ABAP Editor: Initial Screen, choose Execute to verify if the program works. Perform the QA Approval Procedure Perform the QA approval procedure that permits the import of transport requests into the production system (PCC).
1. Once you import transport requests into the QCC system with client 100, the system places the requests into the import queue of the subsequent SAP system. Display the status of your transport requests in the import queue of the subsequent SAP system. Is an import of this transport request into the subsequent SAP system now possible? One subsequent SAP system is the production system p c c ,client 100. a) Enter s t m s in the Command field in the top left of the screen. b) In the Transport Management System screen, choose Overview —> Imports to see the Import Overview screen of all SAP systems in the transport domain. c) Double-click the subsequent SAP system. The Import Queues: System screen appears. d) In the ST (Status) field, verify that the transport requests imported into the QCC system with client 100 have the status Request must still be approved. These requests cannot be imported into the subsequent system until they are confirmed through the QA approval procedure. If the QA approval procedure is not defined, the transport requests that are imported into the quality assurance system may be directly imported to any delivery system of this quality assurance system. 2. Perform the quality assurance approval procedure. Look at the QA worklist of the quality assurance system. Use the filter to display only the transport requests for your project. Log on with the following details:
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Data
Data Value
System
QCC
Client
100
Transaction
STMS
a) Enter s t m s in the Command field in the top left of the screen. b) To see the import overview of all SAP systems in the transport domain, go to the Transport Management System screen and choose Overview —► Imports. c) Highlight the quality assurance system qcc and choose Goto —► QA Worklist. d) In the QA Worklist: System screen, choose Refresh to refresh the QA worklist. The transport requests appear on the QA Worklist screen. 3. Select the approval step. a) To select the corresponding approval step, go to the QA Worklist screen and choose Worklist—► Select Approval Step. b) Choose To be approved by request owner or To be approved by department based on your role in the project. c) Select the Project column and choose Edit —> Filter. d) In the Set Filter dialog box, enter your project name in the Project field and choose Copy to confirm. e) In the QA Worklist screen, mark your transport requests after testing for your specified project by choosing Request —» Approve. f) Enter a reason and confirm that this decision cannot be changed in the Confirmation dialog box. 4. Display the import queue of the subsequent system. a) While in transaction
stm s,
return to the Import Overview screen (Overview —> Imports).
b) Select subsequent systems. The Import Overview screen appears with the import queue and status displayed. Note: The status of your transport requests has changed.
c) In the ST (Status) column, you see that the transport requests approved in the QCC system have the status Request waiting to be imported in system VDE.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
5. Are your approved requests ready for import into our Production system PCC? No. Approved requests will be forwarded to down stream system queues only after the program RSTMS_DIST_APPROVED_REQUESTS has been executed on the Quality Assurance System (QCC). This program may be executed directly or scheduled as a background job and set to run periodically. Please inform your instructor when you have approved your requests. The instructor will execute program RSTMS_DIST_APPROVED_REQUESTS for the class as a group._______________________________________________________________________
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
T ra n sp o rt W orkflo w
\
Important!
A O.K.
fc = _ / Transport Directory Buffers:
DEV QAS
|T R 1
PRD
I
Data/Cofile TR1
Figure 86: Special Transport Workflow
Use the special transport workflow if transport corrections are needed urgently, or if transport requests are required that do not follow the defined transport routes. Before you can use the special transport workflow, configure one SAP system as the Workflow Engine. SAP System Criteria
This SAP system must have the following criteria listed in order of importance: High availability Low to medium SAP system load These prerequisites are met by the Quality Assurance System (QAS), for example. All the tasks performed in the special transport workflow are processed centrally on the Workflow Engine and the results communicated to the affected SAP systems.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
DEV
■
Configuration
fd c
Onto
F«tr>t
Sy
tf a a s
PRD
Help
r h © at © o m e
0
C h a n g a 7M S C o n f i g u r a t i o n : D o m a i n D O M A IfV *2?
■
Workflow Engine
RFC
©
QAS
0
0
*
3
ECC
^
id
U om w i S h o rt D is c re tio n M jn jg a m a n t
i x a u iN t c v T ran sp o rt d om ain ECC W orkflow E n g r a
♦
QA A pproval P ro c e d u re
L ocation <5> Local O o m a n O O th e r D o m a n
♦ _♦
RFC A d d ia u S y s te m c ie n r T a rg e t H ost S y s te m No. U ser
♦ DCC ECC D e v e lo p m e n t S y s te m 1 0 0 D ev e lo p m e n t twdfOOOO
+
s
TWMM_MT
Figure 87: Configuring the Special Transport Workflow
Steps for Special Transport Workflow Configuration
To configure the special transport workflow, do the following: 1. Log on to client 000 in the transport domain controller. 2. Enter transaction
stm s.
3. Choose Overview —*• Systems. 4. Choose Goto —*• Transport Domain. 5. Choose the Workflow Engine tab. 6. Switch to Change mode by choosing the Display <-> Change button. 7. Enter the values for the SAP system, the client, and the target host for your Workflow Engine. 8. Choose Save. 9. Respond affirmatively to the Distribute the Configuration Change dialog box. 10. In the subsequent screen, log on to the SAP system configured as the Workflow Engine. The SAP system automatically does the following: •
Creates the user TMSADM_WF
•
Generates the RFC destinations required for the Workflow Engine
•
Sends the address data of the Workflow Engine to all SAP systems in the transport domain
•
Performs the workflow-related customizing on the Workflow Engine
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
T ra n s p o rt Proposal
Create transport proposal
Transport Organizer Global In fo rm a tio n
mmm Information on transport proposals
T ra n s p o rt Proposals
0
In b o x £>
O u tb o x
Figure 88: Creating Transport Proposals
To use the special transport workflow, create a transport proposal. To create a transport proposal, go to the Transport Organizer (Transaction SE09) and select released requests. Choose Display. Position the cursor on a request that you want to transport and choose Utilities (M) —> Create Transport Proposal. The Create Transport Proposal dialog box appears. Enter a short description, the target system, and other transport requests, if needed. The target systems apply to all transport requests that you enter. Any transport requests that you place in the transport proposal must have been previously released. If a transport proposal is created, the SAP system gives this transport proposal a proposal number, and then places it in the specific TMS work list for the transport administrator. If the transport administrator rejects your transport proposal, it reappears in your transport proposal inbox. You can cancel the transport proposal, or revise it and send it back to the transport administrator. After the transport administrator has approved your transport proposal, the import of the corresponding transport requests is started and the transport proposal reappears in your transport proposal inbox. Check that the transport requests are being imported correctly into the target systems, and confirm the transport proposal.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Import into target system
Figure 89: Transport Proposal Worklist
Procedure to Approve or Reject a Transport Proposal
To approve or reject a transport proposal, do the following: 1. Enter transaction
STM S.
2. To display the TMS worklist, choose Overview —> Worklist. 3. Double-click the transport proposal you want to process. 4. Verify the correctness of the transport requests, the list of target systems, and the import times and import options for the transport proposal. 5. Display the transport requests by choosing Display and selecting the button for transport logs 6. To change the transport requests, transport targets, import times, or import options, switch to Change mode You can create a message for a developer by choosing the Manage Attachments button. To process the transport proposal, choose the respective button to approve or reject the transport proposal. If you approved the transport proposal, the import into the specified SAP systems is automatically started. The transport proposal is placed in the developer's transport proposal inbox and the developer confirms it. If the transport proposal was rejected, it is placed in the developer's transport proposal inbox for modification.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 4 Exercise 9 Create and Manage a Transport Proposal
Business Example
Create transport proposals for an important transport request as part of your transport management. Import transport requests into the production system that you have previously tested in the quality assurance system. Create Transport Proposal
Create a transport proposal for an important transport request. 1. As a developer, change your program ZPGM_## (where # # is your user number) and then assign the program to a new transport request and release. Create a transport proposal for this transport request and send it to client 100 in the target system QCC. Log on with the following details: Data
Data Value
System
DCC
Transaction
S E 38
Target System
QCC
Client
100
In the Create Transport Proposals screen, enter the following details: Field
Field Value
Short Text
Description of transport proposal
Requests for Import
New transport request created for this exer cise
Tgt Systems (Target Systems)
QCC
Target Clnt (Target Client)
100
Time
Date and Time of import to take place (op tional-otherwise it occurs when the system accepts your transport proposal)
Options
Use the default or choose additional import options (unconditional modes)
2. As a transport administrator, check all transport proposals in the TMS Worklist. Mark your transport proposal and reject it. Log on with the following details:
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Data
Data Value
System
DCC
Client
100
Transaction
STMS
3. As a developer, monitor the status of your transport proposal from the Transport Organizer. Find the rejected transport proposal and accept the rejection of the transport proposal.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 4 Solution 9 Create and Manage a Transport Proposal
Business Example
Create transport proposals for an important transport request as part of your transport management. Import transport requests into the production system that you have previously tested in the quality assurance system. Create Transport Proposal
Create a transport proposal for an important transport request. 1. As a developer, change your program ZPGM_## (where # # is your user number) and then assign the program to a new transport request and release. Create a transport proposal for this transport request and send it to client 100 in the target system QCC. Log on with the following details: Data
Data Value
System
DCC
Transaction
S E 38
Target System
QCC
Client
100
In the Create Transport Proposals screen, enter the following details: Field
Field Value
Short Text
Description of transport proposal
Requests for Import
New transport request created for this exer cise
Tgt Systems (Target Systems)
QCC
Target Clnt (Target Client)
100
Time
Date and Time of import to take place (op tional-otherwise it occurs when the system accepts your transport proposal)
Options
Use the default or choose additional import options (unconditional modes)
a) Enter SE38 in the Command field on top left of the screen.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
b) In the ABAP Editor: Initial Screen, enter z p g m _## in the Program field.
c) Choose Save and then Activate. d) To assign the program to a new transport request, enter SE09 in the Command field. Release this request in the Transport Organizer screen. e) Choose the Transport Proposals tab on the right side of the screen. f) Choose Create Proposal. g) In the Create Transport Proposal screen, enter the details provided in step 1. You can add additional attachments with the Create Attachments button. h) To send your transport proposal, choose the Create and Send Proposal button. 2. As a transport administrator, check all transport proposals in the TMS Worklist. Mark your transport proposal and reject it. Log on with the following details: Data
Data Value
System
DCC
Client
100
Transaction
STMS
a) Enter s t m s in the Command field in the top left of the screen. b) In the Transport Management System screen, choose Overview —► Worklist to display the TMS worklist screen. If the workflow server is not the same system, the system performs a log on to the workflow server. c) To display the transport proposals, go to the TMS Worklist screen and choose Select Transport Proposal. d) In the Find Transport Proposals screen, select your transport proposal and choose the Execute button. e) Go back to the TMS Worklist screen and select your transport proposal entry. f) To reject the request, go to the Accept Transport Proposal screen and choose Reject. 3. As a developer, monitor the status of your transport proposal from the Transport Organizer. Find the rejected transport proposal and accept the rejection of the transport proposal. a) Enter SEO 9 in the Command field in the top left of the screen. b) To display the status of your transport proposals, go to the Transport Organizer screen on the Transport Proposals tab, choose Inbox. You see that your transport proposal is In process. c) Double-click your transport proposal.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
d) In the Approve Transport Proposal screen, you can choose either Withdraw, or Save and Send Back for your transport proposal.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
LESSON SUMMARY
You should now be able to: •
Perform the QA approval procedure
•
Execute the transport workflow
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 4 Lesson 4 Maintaining the Import Process
LESSON OVERVIEW
This lesson describes the import process and the tools that are used during it, as well as the means by which the process is monitored. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Monitor the import process
•
Control transports between SAP systems for upgrading SAP releases
tp Processing Sequence Steps in the Import Process
When importing several transport requests simultaneously, the following can occur: •
tp collectively processes each import step for all requests before proceeding with the next import step.
•
tp does not process all import steps for only a single request before proceeding to the next request.
Sequence of steps
TASK DEVK900827 DEVK900833 DEVK900835 DEVK900837 DEVK900839 DEVK900841 DEVK900843 DEVK900845
DDIC | ACTIV 4
4
3
3
1
1
MAIN I I 1 23 1 1 21 2 1 1
I I I I I I I I
■■■
I
| I I I I I I I I
...
| VERS F I XPRA | GENERA | UMODE I I I I I I I I
5 23 1 4 21 2 1 2
I I I I I I I I
| 2 | I | I I I |
1 23 1 1 21 1 1
I I I I I I I I
Figure 90: tp Processing Sequence
tp processes import steps collectively for all requests in the import queue. The required steps for each request are listed in the import buffer file. The contents of the buffer file are organized as a table where each column represents an import step. The numbers in the columns indicate when the import step is necessary or when the number of objects in the request require that specific step.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
In the figure tp Processing Sequence, the first import step DDIC displays the transport requests where it is required (DEVK900827, DEVK900837, and DEVK900845). The second import step ACTIV displays for the same transport requests The third import step Main I displays all transport requests, and so on. The tp import all command does not process all steps for one request before moving on to the steps for the next request. For example, if you detect an error in an object that has already been released, you correct the object and release it again. Import all then imports the whole buffer in the correct sequence and the faulty object is overwritten. Since the generation step is the last step and is performed only once for all objects in the requests, the faulty object does not affect your production system. Only the correct version of the report is activated and generated. Process Flow During Import Table 7: Steps and Tasks that Occur during the Import Process The following summary describes the steps that occur during import: Steps
Import Process Major Steps
1
Import of dictionary objects
2
Treatment of dictionary ob jects
3
Import of all other objects
4
Treatment of other objects
Tasks •
ABAP Dictionary import
•
ABAP Dictionary activation
•
Distribution
•
Structure conversion
•
Move nametabs
•
Main import
•
Activation of the enqueue definitions
•
Enqueue conversion
•
Versioning
•
Execution of user-defined activities (XPRAs)
•
Generation of ABAP pro grams and screens
To perform detailed steps for import, note the following: DDIC I: ABAP Dictionary import •
In an import with R3trans, all ABAP Dictionary structural data is imported inactively, thus enabling you to import into an active SAP system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
Log file: H9.
•
Transport tool: R3trans
ACTIV: ABAP Dictionary activation •
Runtime descriptions (nametabs) are written inactively. This setting is the beginning of the downtime.
•
Log file: A9.
•
Transport tool: RDDMASGL
ACTIV: ABAP Dictionary distribution •
After activation and running logical checks for the new dictionary structures, the distribution program decides what actions are required to bring the new objects into the running SAP system.
•
Log file: S9.
•
Transport tool: RDDGENBB
ACTIV: Structure conversion •
If necessary, changes are made to the table structures.
•
Log file: N9.
•
Transport tool: RDDGENBB
ACTIV: Move nametabs •
The new ABAP runtime objects are put into the active runtime environment, database structures are adjusted if necessary.
•
Log file: 69.
•
Transport tool: pgmvntab
MAIN I: Main import •
All data is imported.
•
Log file: l9.
•
Transport tool: R3trans
MCACT: Activation and conversion of enqueue objects •
Enqueue objects such as search helps that were not previously activated are activated in this separate step after the main import. They are used immediately in the running SAP system.
•
Log file: M9.
•
Transport tool: RDDGENBB
ADO I: Application-defined objects import
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
Import of application-defined objects (ADOs): These objects include forms, styles, and printer definitions.
•
Log file: D9.
•
Transport tool: RDDIC1L
VERSF: Versioning •
Versions of repository objects are only created if transport parameter vers_at_import is active. However, the import process does modify the object's version counter, which is incremented for all repository objects during import.
•
Log file: V9.
•
Transport tool: RDDVERSL
XPRA: Execution of user-defined activities •
XPRAs are objects that can be used to start programs in the target system. The XPRA object has the same name as the program.
•
Log file: R9.
•
Transport tool: RDDEXECL
GENERA: Generation of ABAP programs and screens •
During this step, you can resume normal business activities in the SAP system.
•
Log file: G9.
•
Transport tool: RDDIC03L
Tools Used During Import DEV
QAS Export
Import
SAP system Operating system
QAS
DEV
/ I connect, update,
X
connect read
Transport directory
delete and insert
Figure 91: Introducing tp and R3trans
R3trans is a transport tool at the operating system level used to transport data between SAP systems. R3trans is called by other programs such as tp, the upgrade control program. For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
For transports between SAP systems to access the database, tp indirectly calls R3trans by causing UNIX to issue a fork, Windows to issue a CreateProcess, and AS/400 to issue a spawn. During export, R3trans stores the object data extracted from the database in data files in the transport subdirectory data. The format of these data files, R3trans format, is independent of the platform. During import, R3trans reuses these data files. Direct use of R3trans is not supported but may be required in certain cases. In case of transports, R3trans should always be used through tp. Import steps differ for the different object types. Further activities may be required in addition to R3trans activities, tp ensures that all export and import steps, including R3trans activities, are completed successfully. For upward compatibility, R3trans writes data using a standard transport format. Thus you can export data with an old R3trans version and import data with a new version of R3trans. You can also transport between different databases or operating systems.
Note: Although exports and imports are independent of the R3trans version, the database platform, or the operating system, SAP does not support using tp or R3trans for transports between different SAP system releases.
E *c0-•f)) (>/> Q_ < (/>
0 >
o O
Im p o r t d is p a tc h e r
DDIC activation
RDDIMPDP
R3trans
Conversion
tp
Generation
Buffer
V)
Figure 92: Import Process: tp and the Import Buffer
The first step of an import process is the tp call, triggered by starting an import through TMS or by a tp import command at operating system level. During the whole import process, tp reads the buffer file that includes all the necessary steps for the specific request. If you trigger a tp import all, tp has to ensure that at the beginning of the import process all transport requests stored in the buffer are imported. This step is done by executing command tp setstopmark each time a tp import all process is started. After the steps of the import process are completed, the command tp delstopmark is performed automatically, and a tp cleanbuffer deletes the transport requests from the import buffer. After all involved tools have finished their work, tp exits to the operating system level and writes a return code to the appropriate log file for the activity. For example, tp import and tp setstopmark commands are recorded in the ULOG file.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Note: The command tp import is reentrant. If an error occurs during import, after you eliminate the error condition and restart tp, tp finds the correct point to restart. By default, tp aborts if one import phase receives a return code larger than 8. The transport profile parameter stoponerror defines what return code value should cause tp to abort. Steps Q o
and Q Im p o rt
DDIC activation
Conversion
Generation
< co
Figure 93: Import Process: R3trans
tp reads the buffer file that includes all the necessary steps for the specific request and calls R3trans at the operating system level. For each import step, tp passes information from the buffer file to R3trans. R3trans reads the corresponding data files in the transport subdirectory data and connects directly to the database to perform inserts or updates to the included objects. After R3trans finishes performing inserts or updates, it passes an exit code to tp. For each transport action, R3trans writes a log file in transport subdirectory tmp. After R3trans completes its work, tp moves these log files to the transport subdirectory log. During the import process, R3trans is executed by the import steps of the ABAP Dictionary import (for the import of ABAP Dictionary definitions), and main import (for the import of table contents).
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Steps E 0) (/) > » CO Q.
and I Im p o r t d is p a tc h e r
RDDIMPDP
< )
DDIC activation
Conversion
TRBAT
ra
Generation
TRJOB
■Q
* n-> Q o > oJ — (/) O
Triggers
Inserts entries
R3trans
Figure 94: Import Process: tp / SAP System Communication (1)
In addition to the steps performed by R3trans, tp triggers the import dispatcher. The import dispatcher is a background job with the name RDDIMPDP in the SAP system, which performs steps in the import process. tp and RDDIMPDP communicate through table TRBAT. For every transport request, tp writes an entry in table TRBAT. The import function currently being performed for the request is represented by a character. In the example following, there are three transport requests waiting for DDIC activation in the table TRBAT. Request
Function
Return Code
Timestamp
DEVK904711
J
9999
00000001
DEVK904712
J
9999
00000002
DEVK904713
J
9999
00000003
HEADER
J
B
20083001143701
tp inserts a header entry to tell RDDIMPDP to start processing. Some activities that are independent of transport requests, such as distribution and structure conversion, only have a header entry in table TRBAT. Return code 9999 indicates that the step is waiting to be performed. For the header entry, tp inserts a B (for begin) as the return code. To trigger the transport daemon RDDIMPDP in the SAP System, tp uses the operating system level tool sapevt.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
and I
Steps E
o % >> > Q_ < >
Im p o r t d is p a tc h e r
starts relevant RDD*-jobs
----- I----DDIC activation
RDDIMPDP
Conversion Generation
i___
Checks and writes table
0 ) (rA e nre
Writes status
Inserts jo b i number
re
Q
Buffer
in O
../log - Log file(s)
J
Figure 95: Import Process: tp / SAP System Communication (2)
When RDDIMPDP is started, it checks the table TRBAT to identify when there is an action to be performed for the transport requests such as mass activation, distribution, or table conversion. It sets the header entry to R (for run), and starts the appropriate RDD* program as a background task, reschedules itself, and exits. The activated program (in this example, the mass activator) sets the status of the first entry in TRBAT to active (return code 8888): Request Function Return Code Timestamp Request
Function
Return Code
Timestamp
DEVK904711
J
8888
00000001
DEVK904712
J
9999
00000002
DEVK904713
J
9999
00000003
HEADER
J
R
20083001143903
Each of the required background tasks receives a job number generated by background processing. This job number and the step ID are inserted into table TRJOB by the RDD* jobs.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
E
a -t— CO ) a. c
Import dispatcher
restarts relevant RDD *-jobs
R D D IM P D P
a >) -G
TO
« Q
Writes logs
Q ) > Q >
Buffer
_l
CO
o
Moves logs
Figure 96: Import Process: tp / SAP System Communication (3)
The background tasks write their return codes in table TRBAT and delete the corresponding entry in table TRJOB. Return codes of 12 or less indicate that the step is finished. In TRBAT, the TIMESTAMP column contains the finishing time. When all the necessary actions are performed for all transport requests, the header entry is set to F (for finished) by the RDD* jobs. Request
Function
Return Code
Timestamp
DEVK904711
J
4
00000001
DEVK904712
J
0
00000002
DEVK904713
J
0
00000003
HEADER
J
F
20083001144512
All the background jobs log the performed steps either in the database or in transport subdirectory tmp. tp monitors the entries in theTRBAT and TRJOB tables. When the header entry in theTRBAT table is set to F and the TRJOB table is empty, tp copies the logs of the completed steps from directory tmp to log and deletes the corresponding entries in the TRBAT table. If problems are detected by tp when monitoring the TRBAT and theTRJOB tables, tp retriggers RDDIMPDP through sapevt. RDDIMPDP automatically recognizes if a previous step is still active or was aborted by checking the TRJOB and TRBAT tables. If a step was aborted, RDDIMPDP restarts this step. tp uses the TRBAT and TRJOB tables to communicate with the various ABAP programs. These ABAP programs run as background processes, there must be at least two background work processes running in the SAP system. tp and the background jobs needed for transports communicate using the TRBAT table, which contains temporary data, tp inserts information into TRBAT specifying the steps to be performed for a specific request, tp then triggers RDDIMPDP to read TRBAT and executes the required programs as background jobs whose names start with RDD. For example, RDDMASGL is for mass activation, RDDGENDB for conversion, and RDDVERSL for versioning. Each RDD* job receives a job number that is recorded in table TRJOB. The jobs report their current status back to TRJOB. For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
When imports are performed, tp triggers the import dispatcher RDDIMPDP5 by sending the event SAP_TRIGGER_RDDIMPDP with the help of the tool sapevt. In client 000 and each client that is to receive imports, user DDIC must schedule the job RDDIMDP with event-based scheduling.
Hint: RDDIMPDP can be scheduled by running the ABAP program RDDNEWPP.
RDDIMPDP is automatically scheduled after a client copy. To verify that the required import dispatchers are scheduled, check the job overview using transaction SM 37. The correct name of the import dispatcher for each client is RDDIMPDP_CLIENT_<###>, where # # # represents the client's name. The corresponding event is SAP_TRIGGER_RDDIMPDP_CLIENT.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 4 Exercise 10 Monitor the Import Process
Business Example
To enable the post import activities with the import dispatcher, schedule RDDIMPDP correctly in the SAP system. Monitor the import dispatcher RDDIMPDP. Monitor Import Dispatcher
Monitor the import dispatcher RDDIMPDP. 1. Verify the scheduling of the import dispatcher RDDIMPDP in SAP systems QCC and PCC. Log on and view the scheduling of RDDIMPDP with the following details: Data
Data Value
System QCC
Client 100
System PCC
Client 100
Transaction
SM37
2. If the job RDDIMPDP and the client-specific job RDDIMPDP_CLIENT_## (where # # is your user name) are not scheduled, how would you schedule them?
Monitor Import All
Perform this exercise with the instructor's assistance to monitor the import all feature. 1. After the instructor starts a long-running import of some transport requests into SAP system, PCC and client 100, monitor the progress of the import from the SAP system, PCC. Start the different tools in parallel. 2. In the first session, run the TMS import monitor. 3. In the second session, check the subdirectory tmp under DIR_TRANS. 4. In the third session, check all the RDD* jobs. 5. In the fourth session, check the table of contents of TRBAT. 6. In the fifth session, check the table of contents of TRJOB. 7. In the sixth session, look for tp and R3trans under Top 40 CPU processes.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
8. What can you find out from these sessions?
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 4 Solution 10 Monitor the Import Process
Business Example
To enable the post import activities with the import dispatcher, schedule RDDIMPDP correctly in the SAP system. Monitor the import dispatcher RDDIMPDP. Monitor Import Dispatcher
Monitor the import dispatcher RDDIMPDP. 1. Verify the scheduling of the import dispatcher RDDIMPDP in SAP systems QCC and PCC. Log on and view the scheduling of RDDIMPDP with the following details: Data
Data Value
System QCC
Client 100
System PCC
Client 100
Transaction
SM37
a) Enter SM37 in the Command field in the top left of the screen. b) In the Simple Job Selection screen, enter r d d i m p d p * in the Job name field and the character * in the Username field. c) Deselect Finished in the Job status checkbox. d) Enter the character * in the or after event field. e) Choose Execute. f) In the Job Overview screen a list of all scheduled RDDIMPDP jobs is displayed: RDDIMPDP_CLIENT_001, RDDIMPDP_CLIENT_100, and SO On.
r d d im pd p ,
g) To obtain more details about the job, double-click a job, or select a specific job and choose Job —> Job details to go to the Display Job screen. In the Display Job screen, notice that after raising event s a p _ t r i g g e r _ r d d i m p d p job r d d i m p d p is started. After raising event s a p _ t r i g g e r _ r d d i m p d p _ c l i e n t all clientspecific RDDIMPDP jobs ( r d d i m p d p _ c l i e n t _ # # # ) are started. The Job frequency is Event periodic.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
2. If the job RDDIMPDP and the client-specific job RDDIMPDP_CLIENT_## (where # # is your user name) are not scheduled, how would you schedule them? To schedule the job RDDIMPDP, log on to client 000 and run the program RDDNEWPP. To schedule the client-specific job RDDIMPDP_CLIENT_###, log on to the appropriate client ## and run the program RDDNEWPP. The step in the job is scheduled under user DDIC, independent of the user with which you logged on.___________________________________ Monitor Import All
Perform this exercise with the instructor's assistance to monitor the import all feature. 1. After the instructor starts a long-running import of some transport requests into SAP system, PCC and client 100, monitor the progress of the import from the SAP system, PCC. Start the different tools in parallel. a) Log on to the SAP system with the details provided in step 1 and open six sessions. b) Run the following transactions (step 2 through step 7). 2. In the first session, run the TMS import monitor. a) Enter s tm s in the Command field in the top left of the screen. b) Enter PCC in the System field and choose Import Overview .
c) On the Import Overview screen, choose Goto —► Import Monitor. The TMS Import Monitor shows the current import process. Hint: Use Refresh to follow the progress of the import process.
3. In the second session, check the subdirectory tmp under DIR_TRANS. a) Enter a l i i in the Command field in the top left of the screen. a) Choose DIR_TRANS —> tmp. 4. In the third session, check all the RDD* jobs. a) Enter SM37 in the Command field in the top left of the screen. b) Enter r d d * in the Job Name field and enter * in the User name field c) Deselect Finished. d) Choose Execute. 5. In the fourth session, check the table of contents of TRBAT. a) Enter SE16 in the Command field at the top left of the screen. b) Enter t r b a t in the Table Name field. c) Choose Table Contents.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
d) Choose Execute. 6. In the fifth session, check the table of contents of TRJOB. a) Enter
sei
6 in the Command field at the top left of the screen.
b) Enter t r j o b in the Table Name field.
c) Choose Table Contents. d) Choose Execute. 7. In the sixth session, look for tp and R3trans under Top 40 CPU processes. a) Enter s t o 6 in the Command field at the top left of the screen. b) Choose the Top 40 CPU processes snapshot. c) Find tp and R3trans. 8. What can you find out from these sessions? In the Import Monitor, you see the return code and during the import, you see log files in the temp directory. These entries are in tables TRBAT and TRJOB. In transaction SM37, jobs are visible, such as RDDMASGL, RDDMNTAB, and RDDVERSL. In transaction ST06, you can see tp and possilbly R3trans.________________________________________________________
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Overview of tp Commands The transport control program tp is used for controlling transports between SAP systems and for performing release upgrades. The tp program tracks transports by controlling exports and imports of objects between SAP systems. The program also ensures that the steps in exporting and importing objects are performed in the correct order and that imports into a target system are done in the same order as the exports from the source systems. tp is an operating system level program, which uses special programs, such as C programs, operating system commands, and ABAP programs in the SAP system. tp performs exports and imports separately. In the export phase, the objects to be transported are extracted from the database of the source system and stored in files in the transport directory. In the import phase, the objects are added to the database of the target system. An export always takes place immediately after the transport request has been released so that the objects are freed for further modification, tp uses the program R3trans at operating system level to establish a connection to the database and to perform the necessary steps in the database. There is no automatic mechanism that imports a request into a target system immediately after export. Although most transport activities can be performed using TMS, you may find the need to use tp commands for exceptional cases. Since import buffers and import queues are identical, the use of tp and TMS produces consistent results. Usage: tp [argument(s)] [option(s)], where may be one of:
-------------------- +----------------------- +-------Exporting EXPORT R3E SDE TST Importing
i Buffer Actions I EXPWBO I VERSE I i I
i I I i I
ADDTOBUFFER SETSYNCMARK SETSTOPMARK MARK CLEANBUFFER
I I I i I
I Disk Space DELFROMBUFFERI CLEAROLD DELSYNCMARK I CHECK DELSTOPMARK I TESTOLD UNMARK I I
+-------------------------------------- +■
I Special Functions
I Information -tPUT i I LOCKSYS I UNLOCKSYS I SHOWBUFFER IMPORT i I LOCK EU I UNLOCK EU I COUNT CMD I R3I I WRITELOG I GETPROTS I SHOWPARAMS I I SAPSTART I SAPSTOP I GO R3H I I GETTBATGENT I GETTRBATENT I CONNECT ACT I MVKERNEL I GETDDXTTENT I GETDDXTFENT I CHECKIMPDP SXPRA I SDI I GETOPENCORR I CREATECOFILE I SHOWINFO GENTB I GENT1 I PREPAREBUFFERI CREATEINFO I GETOBJLIST GENT 2 I EXTRDOCU I GEN I CONTP i EXPCHK DIST I XPA I SHOWSEMAPHOREI SHOWSEMACLIENI GETCONVENT MVNTABS I VERSI I SETSEMAPHORE I DELSEMACLIENTI EXPLAINRC IMPSYNC I DELIVER I DELSEMAPHORE I GETTPSTATENT I DEPLOY I IMPORT PREVIEWI CHECKIN I CHECKINMOVE I CHECKOUT CHECKDEPLOY I I I I For more details call tp with the desired command (and no other parameters)
Figure 97: Overview of tp Commands (tp help)
Use of tp Commands
tp commands are executed in the transport subdirectory bin by user adm. tp commands are called using syntax tp [argument(s)] [option(s)]. Note the following about tp commands: To display general information on the syntax of all tp calls, use tp help. To display a description of the syntax and function of a specific command, use tp without any options.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
To display a count of all transport requests registered for import into a specific SAP system, use tp count .
•
To test whether a connection to an SAP system's database was successful, use tp connect .
•
To display how the import dispatcher RDDIMPDP is scheduled for a specific SAP System, use tp checkimpdp .
•
To display all current settings of the parameter file, use tp showparams .
•
To display status information on the serialization of a specific SAP system, use tp status .
Syntax of tp Import Commands
c
Import with tp
Release and export from Transport Organizer
Transport directory tp import all QAS client=100 pf =TP_.PFL
DEVK900827 DEVK900833 DEVK900835 DEVK900837
tp import DEVK900835 QAS client=100 uO nf=TP PFL
Figure 98: tp Import Command Line Option
Imports performed using tp at the operating system level are restricted to exceptional cases, for example, when the TMS is not available. There are two commands to start an import using tp at the operating system level: •
tp import all client= pf=TP_.PFL Analogous to the default import of TMS, this command imports all waiting transport requests in the correct export sequence. Analogous to the TMS preliminary import, this command enables you to give individual transport requests priority.
•
tp import tra n s p o rt request> client= uO pf=TP_.PFL
Importing individual requests is not recommended as the correct order of requests is not necessarily maintained and thus newer versions of objects may be overwritten by older versions through the regular import of all waiting requests. To ensure that the objects imported through an individual transport are not overwritten by an older version, only use unconditional mode 0, that is, the option uO, when starting individual imports. Using this mode is analogous to the TMS preliminary import and causes the transport request to remain in the list of requests to be For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
imported. When the regular transport takes place, the request will automatically be imported again in the export sequence. Individual imports only are performed in exceptional cases. Processing imports out of order can result in severe inconsistencies in the target system. These inconsistencies are hard to diagnose. If you do not want to import single requests as preliminary import (this method is not recommended), you would use tp import tra n s p o rt request> client= pf=TP_.PFL, without the option uO.
Hint: Specify the full qualified path to the tp parameter file TP_.PFL by using the parameter pf=TP_.PFL. The content of import buffer files in the transport subdirectory buffer is organized as a table. Each line contains information on a specific transport request. One column includes the unconditional mode that is linked to the transport request. Other columns specify import actions. tp offers several commands for accessing buffers: •
tp showbuffer This command displays buffer entries.
•
tp addtobuffer tra n s p o rt request> This command registers the request as the last request to be imported.
•
tp delfrombuffer tra n s p o rt request> ctarget SID> This command deletes a single request from the buffer.
•
tp cleanbuffer This command removes successfully imported transport requests from the buffer. This function is included in the command tp import all . This action can be started in transaction STMS by choosing Overview —► Imports —*■ Import Queue —> Display —► Extras —*• Delete Imported Requests.
•
tp setstopmark This command places a stopmark at the end of a buffer so that subsequent tp import commands only process the requests that are located before the stopmark.
•
tp mvstopmark This command moves the stopmark in front of the transport request in the buffer.
•
tp delstopmark This command deletes the stopmark from a buffer.
The tp unconditional import modes are as follows: Table 8: Unconditional Modes 0
Overtaker
Import from the buffer without deleting and set unconditional mode 1 in the buffer to trigger another import.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
1
During export
Ignore incorrect status of a transport request.
During import
Ignore that this transport request was already imported into this system and import everything again.
2
During import
Overwrite originals.
6
During import
Overwrite repaired objects.
8
During export
Allow direct selection of forbidden tables. Some tables are part of com plex objects and cannot be exported alone.
During import
Ignore the restriction resulting from table classifications and import all ta ble entries into specified clients.
Hint: The unconditional modes may vary in dependence of the SAP and tp release.
Unconditional modes are among the options that can be assigned to tp commands. They are used to cause specific rules of the Change and Transport System (CTS) to be ignored. Each unconditional mode is represented by a digit. To use an unconditional mode, add an u to the tp command line and add the required digit. For example, if you want to import request DEVK900132 into the quality assurance system and overwrite originals, enter the following command: t p i m p o r t d e v k 9 0 0 1 3 2 qas U2. Use unconditional modes carefully. It is preferable to transport according to the rules of the Change and Transport System (CTS). Some unconditional modes can be used directly in TMS.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
LESSON SUMMARY
You should now be able to: •
Monitor the import process
•
Control transports between SAP systems for upgrading SAP releases
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 4 Lesson 5 Monitoring Transport Activity
LESSON OVERVIEW
This lesson shows how to monitor transport activity through TMS monitoring tools, checking for critical objects, code freezing and testing. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Describe the monitoring tools in TMS
•
Check for critical objects
•
Manage code freeze
•
Display the transport directory and log files
•
Troubleshoot transport errors
TMS Monitoring Tools TMS provides various tools with which you can monitor transport activities in your transport domain. Types of Monitoring Tools
•
Import monitor
•
Import history
•
tp system log
•
Import queue consistency check
•
Transport control program check
•
Transport directory check
•
RFC connection test
In transaction STMS, choose Overview —> Imports: •
Import monitor - To display tp status information from table TPSTAT, choose Goto —► Import Monitor.
•
Import history - To display the import history, choose Goto —*• Import History.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Note: The import history is collected from the log file ALOG and is kept in tables TPALOG and TPALOGHDR. For details, see SAP Note 375230: TMS: incomplete import history.
•
tp system log - To display all tp calls and errors for the current SAP system in the file SLOG, choose Goto —► tp System Log. To display the file ALOG containing the return codes of all individual transport steps for the current transport group, choose from the tp system log view Goto —*• Transport Steps.
•
Import queue consistency check - To check if the data files and cofiles of transport requests in an import queue exist in buffers of the transport directory and can be read, choose Queue —► Check —> Consistency.
In transaction stms , choose Overview —> Systems and mark one or more SAP systems: •
Transport control program check - To check the transport control program tp for all or just one specific SAP system within the domain, choose SAP System —> Check —► Transport Tool.
•
Transport directory check - To verify the availability of the transport directories of all SAP systems within the domain, choose SAP System —> Check —> Transport Directory.
•
RFC connection test - To check RFC connections in both directions, choose SAP System —> Check —> Connection test.
Critical Objects Before import manually
Request
1 DEVK900827
J m p o tt Q u e u e : S y s te m Q A S
a! a v
a
®
£4
ID
2 3 4 5 6 7
id
DEVK900833 DEVK900835 DEVK900837 DEVK900839 DEVK900841 DEVK900843
J Compare for critical objects
R3TR TABU R3TR XPRA
TABLE1 ZPGM1
Table of critical objects Figure 99: Checking for Critical Objects Before Import
Options to Check Critical Objects
Use one of the following options to check for critical objects: •
Before the import of a transport request into the target system
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Perform this option manually to list transport requests that contain critical objects. •
During the export of a transport request Perform this option automatically, if tp parameter CHK_CRIOBJ_AT_EXPORT is set to W (warning) or E (error).
To check if the transport requests in an import queue contain critical objects that may not be imported into the target system, go to the Import Overview {STM S —» Overview —► Imports) and choose Queue —► Check —> Critical Objects. The object lists of the requests are checked to see if they contain critical transport objects. The results are displayed in a hierarchical list. Requests containing critical objects are marked with the appropriate label. The critical objects are highlighted in color. Before performing this check, maintain the list of objects that are classified as critical by logging on to the domain controller. The information about critical objects is distributed to the whole domain when you save. To display or maintain the critical transport objects defined for the transport domain, enter transaction s t m s . Choose Overview —> Imports —> Extras —> Critical Transport Objects.
Note: You can also check requests for critical objects in the QA worklist. This step supports the decisions you make about approving or rejecting requests. If you want to check the whole QA worklist for critical objects, choose Worklist —*■ Check —> Critical Objects. Choose Confirm in the dialog box. An overview of the requests with critical objects appears. If you only want to check certain requests for critical objects, filter them in the display. Choose Worklist —» Check —► Critical objects. Choose Confirm the dialog box. An overview of the requests with critical objects appears. Only objects of the form object type R3TR are checked as transport objects. Transport objects that start with LIMU are subobjects of a repository object with an object directory entry. To check these objects, you must find out the object directory entry and enter it in the table of critical objects.
©
Hint: An example of interesting objects classified as critical are R3TR XPRA (XPRAs) or R3TR TABL (table definitions) or R3TR TABU (table content)
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Code Freezing and T e sting
V
■ T ra n s p o rt ^ ^ ^ ^ ^ T e s t i n g ^
r f
lstop
:
log
check
EE
Error fixing 2EVK900827
More development for project A
Sign-off
^nd.-
M ^ e n h c a h o ,
Import all requests into production using TMS
DEVK900849
mmn D E V K 900855
PRD import queue
Figure 100: Code Freeze and Testing*•
To ensure a stable test and development environment, use a developer deadline to freeze work on objects in the development system until the completion of the quality assurance verification. Object Development and Testing Procedure
Use the following procedure during object development and testing: 1. Release the transport request containing the developed objects. 2. Freeze development of the objects in the development system. 3. Import the objects and verify the changes in the quality assurance environment. 4. Sign off the changes. 5. If necessary, allow further development on the objects in the development system. An administrator can force code freezing for an SAP system landscape with the following tools: •
stop exports by creating a file in the transport directory: /usr/sap/trans/bin/T_OFF. The first line of the file T_OFF. will be displayed, whenever you start an export from the Transport Organizer.
•
stop imports by creating a file in the transport directory: /u s r/s a p /tra n s /tm p / NOIMPORT. The content of the file NOIMPORT. is not evaluated.
If an object has gone through the error fixing cycle, it is included in at least two different transport requests within the import queue of the production system. If you import the complete import queue, using Import all into the production system after sign-off, the pre-corrected object has no impact on your production environment.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Change management includes creating, releasing, distributing, and verifying transport requests for all SAP systems in the SAP system landscape. Ensure that your distribution procedures are supported by the TMS setup. Determine release, import, and verification requirements for all transport points in your SAP system landscape. For each transport point, define the following: •
When transports will take place?
•
Who is responsible for a transport request during its various transport phases?
•
How will transports be verified before being distributed or redistributed?
•
What happens if a transport is successful, but testing proves that the contents are incorrect?
•
Are sign-offs required for transporting?
Assign persons to be responsible for all transport steps. Use authorizations to restrict access to transport request management tasks and to the operating system level. SAP provides techniques for the distribution and management of changes using import buffers. These buffers indicate the changes to be transported to the target system and the transport order. You must establish and control the buffers and the distribution or redistribution process. To verify all imports, review transport logs, establish testing standards and quality assurance procedures, and define sign-off procedures. We recommend transporting a whole change project when all objects are in an acceptable state rather than each single object as soon it is ready. T ra n sp o rt D ire cto ry and Log Files Since the transport control program tp runs on many different operating systems, restrictive naming conventions are required. Transport requests are always represented in the following format K9<5 digits or characters>, where source SID is the SAP system in which the transport request is created and K9 indicates a customer request. The five digits form a serial number, which can be expanded using characters.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
The transport directory contains subdirectories, such as bin, data, cofiles, buffer, log, tmp, actlog, sapnames, and EPS. For more detail, see the following: bin This subdirectory contains the configuration files for the transport domain, data This subdirectory contains files named R9<5 digits >. containing the exported objects. cofiles This subdirectory contains command files named K9<5 digits>.. They contain, for example, import steps to be performed. buffer This subdirectory contains an import buffer for each SAP system named after the SID. When a transport request is released, the import buffer of the target systems is updated. log This subdirectory contains all log files, such as ULOGs, ALOGs, and SLOGs named 9<5 digits>. for each executed step, and log files named . for steps that are collectively executed, for example, step N (structure conversion) and step P (move nametabs). tmp This subdirectory contains log files before written to log. actlog This subdirectory contains files named Z<6 digits> recording each action on a request or task, for example, creation, release, or change of ownership. sapnames This subdirectory contains files named after the user's logon name. A file is created for each SAP system user who performs transport actions and updated when the user releases a request. EPS This subdirectory, Electronic Parcel Service (EPS), contains the directory in, to which SAP support packages are copied and applies them to the Support Package Manager (transaction s p a m ).
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Transport Tool Log Files
tmp
log
o o o o o o o o o o o
ULOG |o | SLOG 1° O ALOG O O O o
Import process
Figure 102: Monitoring and Analysis: Transport Tool Log Files
The various transport tools write a log for each transport action to the transport subdirectory tmp. After completion of this step, tp moves these logs from tmp to log. The log files are named <6 digits>., where the action is represented by a single character and the 6 digits are taken from the corresponding transport request. Each log file can be seen in the SAP system. You can choose different detail levels in the log file. The level for the transport protocol display in the SAP system. The possible levels are as follows: •
Performed actions and return code
•
Additional error messages
•
End user logs
•
Details for developer and the hotline
tp
Transport subdirectory log
Figure 103: Monitoring and Analysis: tp Log Files
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
For long-running imports, it may be helpful to monitor the log files written at the operating system level. All logs in the transport environment are stored in the transport subdirectory log. These logs include logs created by tp (ULOG, SLOG, and ALOG), and logs created by the various transport tools. The current ULOG file records all tp commands that are free of syntax errors and are named using the naming convention ULOG_. Each line in the ULOG file represents a tp command. The SLOG file is used to monitor the transport activities of a specific SAP system. It contains a general overview of performed imports indicating the return code and thus the success of each import. The name of the SLOG file can be set as tp parameter using the global parameter SYSLOG. The default setting is SLOG.. The ALOG file records the return code for all transport steps handled in the common transport directory. The name of the ALOG file can be set as tp parameter using the global parameter ALLLOG. The default value is ALOG.
Transport Tool Return Codes Table 9: Transport Tool Return Codes The following table summarizes the meanings of transport tool return codes: Transport Tool Return Code
Description
0
Successful transport
4
Warning
8
Error in object
16
Transport error
Table 10: tp Return Codes The following table summarizes the meanings of tp return codes: tp Return Code in File System
Description in Database
0-16
Transport tool return code
17-99
Combination of transport tool and tp return code of warning
100-199
tp return code of warning
200 and greater
tp error
Further Explanation of tp Return Codes
tp receives return codes from all the transport tools involved in an import process, tp ’s own return code following exit is interpreted as follows:
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0 to 16 indicate the maximum value of all return codes from transport tools. 17 to 99 are values that are calculated from the return codes of the transport tools and a tp warning, for example, the buffer of the target system does not have a write permission. 100 to 199 indicates warnings. Warnings mean that something went wrong and tp could not perform all the tasks. 100 to 149 are normal tp warnings. For example, RDDIMPDP cannot be triggered by sapevt. Return codes of 150 to 199 are rare and indicate incorrect operation by a user. For example, a return code of 152 is received if tp tries to import a request that is not included in the buffer. •
200 or more indicates tp errors. For example, when a file could not be accessed as required by the import process, the return code is 212.
The accompanying text is more significant than the value of a return code. To display the text of a specific tp return code, use the tp command tp explain rc . Transport Error Troubleshooting
Alert Monitor
System Log (SLOG)
• View all tp return codes
View tp connection errors Locate permission problems
Action Log (ALOG)
Locate what transport request or generic phase produced a warning or error
See RFC failures
Review individual log files at the operating system level.
Figure 104: Troubleshooting View 1
The first step in troubleshooting transport errors is to use the alert monitor, which records all TMS transport actions. The alert monitor is available in transaction s t m s by choosing Monitor —> Alert Viewer. The information displays the date and time, the user name, the TMS status message, and the target SAP system. To display the full text of an error message, double-click the error message. More detailed information can be seen in the SLOG file, which is used to monitor the transport activities of SAP systems and determine the success of import requests. If import failures are recorded in the SLOG file, drill down to the ALOG file and locate the import step that produced the return code listed in SLOG. Use ALOG file to identify the detailed log file, which is written for each step of a transport request. These log files can be accessed from the SAP system using the Transport Organizer, transaction S E 0 9 . To locate the log file for the request that produced an error use ALOG file.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
All log files that are not dependent on specific requests, such as the log files for structure conversion and nametab moving (mvntab), cannot be displayed in the SAP system. These files can be accessed at the operating system level in the transport directory. SE16 -ch ecktables V 000047
TRJOB
DEVK900003 N 0000 ...' DEVK900008 N 8888 ...
TRBAT
SM37 check protocols of RDD* jobs 12.10.1211:06 12.10.1211:07 12.10.1211:07 12.10.1211:08
516 560 007 518
Job overview
Job started Step 001 started Fatal error Job aborted
SAP system Operating system Transport directory tp R3trans sapevt File system
Figure 105: Troubleshooting View 2
Additionally, check whether the import dispatcher RDDIMPDP is scheduled correctly and is event-triggered. Use the job overview SM37 to monitor the related background jobs (RDD*). Enter RDD* in the Job name field and an asterisk * in the or after event field. Problems might result from wrong versions of tp or R3trans, tp not running, as in UNIX "ps -ef | grep tp ” , permission or share problems with the common transport directory, or no free disk space. When analyzing a problem, compare the logs and buffer entries with the entries in tables TRBAT and TRJOB, that is, transaction S E 1 6 . If required, insert the transport request or header in TRBAT and restart RDDIMPDP. If a communication problem between tp and the SAP system is indicated, try to start sapevt at the operating system level and trigger RDDIMPDP.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 4 Exercise 11 Troubleshoot Import Problems
Business Example
When transports cannot be finished successfully, it is essential to analyze the transport errors and solve the problem. Review Transport Logs
Review export and import logs in the transport directory. 1. If you want to see the transport logs generated by a transport request during export and import within your SAP system, to which SAP system (DCC, QCC, and so on) do you log on?
2. View the files in the transport directory related to one of your released and exported transport requests. Use transaction a l i i to view the files at the operating system level. 3. View the files in the transport directory related to one of your imported transport requests. Use transaction a l i i to view files at the operating system level. Fixing Import Errors and Working with the Import Queue
There are several tools to monitor the import process. 1. While the instructor imports the transport requests into the quality assurance system, monitor the import. Log on with the following details: Data
Data Value
System
QCC
Client
100
2. Monitor the import process by using the import monitor. 3. Monitor the import process by checking the tp System Log. 4. Monitor the import process by checking the transport steps in the tp System Log. 5. The import monitor reports a return code 0008. What import phase or transport request produced the import error? 6. Locate the log files for the transport request that produced the import error.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Hint: As long as the transport request is still in the import queue, you can directly reach the detailed log files by double-clicking the symbol for the return code of the transport request. Return codes only display in the extended view (Edit —► Display More). If you do not see them in the import queue, you can find them in import history (Goto —> Import history).
7. How would you correct the import error?
Working with Import Errors and ALOG
Additional errors appear in reports, as well as their resolutions. 1. While the instructor imports the transport requests into the quality assurance system, monitor the import process. 2. The import monitor reports a return of 0008. What import phase and/or transport request produced this import error? 3. How can you locate the log files for the transport requests that produce import errors? What types of errors occur? 4. What causes this error? How do you avoid it? 5. How can you correct this error?
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 4 Solution 11 Troubleshoot Import Problems
Business Example
When transports cannot be finished successfully, it is essential to analyze the transport errors and solve the problem. Review Transport Logs
Review export and import logs in the transport directory. 1. If you want to see the transport logs generated by a transport request during export and import within your SAP system, to which SAP system (DCC, QCC, and so on) do you log on? The DCC and QCC system share the same transport directory and thus are in the same transport group. Therefore, it does not matter from which SAP system where you view the transport directory. If your transport domain contains multiple transport groups, log on to an SAP system that accesses the transport directory where the log files reside. In this case, SAP system PC2 has its own transport directory.________________________________________ 2. View the files in the transport directory related to one of your released and exported transport requests. Use transaction a l i l to view the files at the operating system level. a) Enter a
l i
l
in the Command field to display the SAP Directories screen.
b) Select the directory parameter d i r _ t r a n s . The following files are created or modified in the transport directory during the export process for transport requests. The solutions use the transport request named DCCK902012, for example. Substitute your transport request number for DCCK902012. .
In the SAP Directories screen, the cofiles subdirectory contains important control information on how to import and process transport requests. You can find the command file K902012.DCC in the cofiles subdirectory.
.
In the SAP Directories screen, the data subdirectory contains data file R902012.DCC. This file stores all the data that was extracted from the development system based on the objects recorded in the transport request.
Note: The data files are in character format so the content is viewable. Otherwise, the data files would not be viewable.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected] 237
© Copyright. All rights reserved.
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
.
In the SAP Directories screen, the buffer subdirectory contains control information that describes which transports you import, into which systems, and the order of imports. Each buffer file name appears with the of the corresponding SAP system. You can see an entry in the buffer file of QCC. If you are using transport target groups to import into multiple clients, there may be multiple entries, one for each client in the target group. Note that comment lines begin with a # mark and are for informational purposes only.
.
In the SAP Directories screen, the log subdirectory contains transport logs, trace files, and statistics. The fourth letter in the log filename specifies the step that was performed. The at the end of each filename specifies the SAP system responsible for the actions. The system wrote the following example log files during the export process of request DCCK902012: D C C E K 9 0 2 0 1 2 . DCC (export log) and D C C P K 9 0 2 0 1 2 . q c c (test import log).
Note: The tp parameter, TESTIMPORT, controls whether the system automatically executes a test import during the export phase. If you deactivate this test import, the test import log does not exist
.
In the SAP Directories screen, the sapnames subdirectory contains information for each SAP user who released a request. Select a file of your user.
3. View the files in the transport directory related to one of your imported transport requests. Use transaction a l i l to view files at the operating system level. a) Enter a
l i
l in the Command field to display the SAP Directories screen.
b) Choose the directory parameter d i r _ t r a n s . The system creates or modifies the following files in the transport directory during the import process for transport requests. The solutions use the transport request named DCCK902012, for example. Substitute your transport request number. c) In the SAP Directories screen, choose subdirectory buffer, which contains each buffer file named with the corresponding . If you choose QCC, you can see request DCCK902012, if the system imports the transport request using the preliminary import functionality. d) After import into QCC, an entry for the request appears in the buffer of PCC. The log subdirectory contains log files written during both the export and import process. Examples of log files that the system may write during the import process of request DCCK902012 include: .
DCCH902012.QCC - dictionary import log file
.
DCCA902012.QCC - dictionary activation log file DCCI902012.QCC - main import log file
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
.
DCCM902012.QCC - enqueue log file
.
DCCV902012.QCC - versioning log file
.
DCCR902012.QCC - user-defined activities
•
DCCG902012.QCC - generation log file
Note: Each transport request requires different import phases. Log files appear only for the phases required by that transport request. Some import phases are generic and do not create individual log files for each transport request.
Fixing Import Errors and Working with the Import Queue
There are several tools to monitor the import process. 1. While the instructor imports the transport requests into the quality assurance system, monitor the import. Log on with the following details: Data
Data Value
System
QCC
Client
100
a) Enter s t m s in the Command field on the top left of the screen. b) Choose Overview —> Imports. c) Choose QCC by double-clicking it. d) Choose Edit —> Display More. On the Import Queue screen, you can now see the return code of the transport requests. e) To see detailed log files for the transport request, double-click the return code to display the Overview of Transport Logs screen. 2. Monitor the import process by using the import monitor. a) Enter s t m s in the Command field on the top left of the screen. b) Choose Overview —> Imports. c) Choose QCC by double-clicking it. d) Choose Goto —► Import Monitor. The Import Monitor screen shows the current import process. e) To follow the progress of the import, choose Refresh. 3. Monitor the import process by checking the tp System Log. a) Enter s t m s in the Command field on the top left of the screen.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
b) Choose Overview —> Imports. c) Choose q c c by double-clicking it. d) Choose Goto —> tp System Log. e) Scroll to the bottom of the SLOG listing to view imports. f) To follow the progress of the import, choose Refresh. 4. Monitor the import process by checking the transport steps in the tp System Log. a) From the tp System Log - System QCC screen, choose Goto —> Transport Steps. b) To view imports, go to the Transport Step Monitor screen and scroll to the bottom of the ALOG listing. c) To follow the progress of the import, choose Refresh. 5. The import monitor reports a return code 0008. What import phase or transport request produced the import error? a) To check for obvious setup errors, enter s t m s in the Command field. b) From the Transport Management System screen, choose Monitor —> TMS Alerts —► CCMS Alert Monitor. Find the QCC branch of the tree. No configuration errors are recorded. c) From the Transport Management System screen, determine the success of imports, by choosing Overview —► Imports. d) Select q c c and choose Goto —► tp System Log. You see as the last entry, imp all (import all) stopped with a return code 0008. e) At the tp System Log screen, choose Goto —> Transport Steps to access the action log file, ALOG. f) To locate the transport request or the generic phase that produced error 0008, go to the bottom of the entries and check the return codes of all individual transport steps. You can now detect the request that caused problems, displaying a return code of 0008 (error) for step G (generation). 6. Locate the log files for the transport request that produced the import error, a) On the tp System Log screen, view the ALOG and double-click the error.
Hint: As long as the transport request is still in the import queue, you can directly reach the detailed log files by double-clicking the symbol for the return code of the transport request. Return codes only display in the extended view (Edit —> Display More). If you do not see them in the import queue, you can find them in import history (Goto —► Import history).
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
7. How would you correct the import error? Correct the syntax error in the development system where the system imported the transport request. Always make corrections in the development system. Use the program check to ensure that the program is correct. Release and export the new request. Import the request with the corrected object into the target system._____________________________________ Working with Import Errors and ALOG
Additional errors appear in reports, as well as their resolutions. 1. While the instructor imports the transport requests into the quality assurance system, monitor the import process. a) Refer to steps 1-4 in the Fixing Import Errors and Working with the Import Queue exercise fora solution. 2. The import monitor reports a return of 0008. What import phase and/or transport request produced this import error? a) A transport request returned 0008 during the activation phase A. 3. How can you locate the log files for the transport requests that produce import errors? What types of errors occur? a) View the ALOG or the return code in the import queue and double-click the error. b) Expand the log file completely. The red lines indicate the source of the problem. During the ABAP Dictionary activation step of the import process, the SAP system detected that the field’s data element of a table from the transport request is not active or does not exist. The SAP system's underlying domain is either not active in the ABAP Dictionary in QCC, or it does not exist. Therefore, the system did not generate the runtime object (nametab) of the table and the system did not activate the table. 4. What causes this error? How do you avoid it? a) The system transports related objects such as the data element and the table in two different transport requests. b) This step occurs when the system does not import the data element in the same import step as the table that refers to it. c) These problems can occur if imports of single transport requests are triggered and the correct sequence is not considered. d) To prevent such problems, developers should transport all related objects in the same transport requests to ensure proper activation. 5. How can you correct this error? a) Import the transport request that contains the missing data element. b) If there are several, related transport requests, import them together in one step into the subsequent SAP systems.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
O
Hint: Developers must transport related objects together. The recommendation is to use projects here.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
LESSON SUMMARY
You should now be able to: •
Describe the monitoring tools in TMS
•
Check for critical objects
•
Manage code freeze
•
Display the transport directory and log files
•
Troubleshoot transport errors
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 4 Lesson 6 Cleaning Up the Transport Directory
LESSON OVERVIEW
This lesson explains how to clean up and manage the transport directory. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Manage the transport directory
Transport Directory Clean Up Data files, cofiles, and different log files are written to the transport directory. These files are not deleted, overwritten, or reorganized automatically so the transport administrator has to take care of them. To clean up the transport directory, use the commands tp check all and tp clearold all. In the course of time, many files accumulate in the transport directories. These files contain important information, but they also require disk space and become obsolete over time.
The command t p c h e c k a l l searches for transport requests that are not marked for import into any SAP system, as revealed by the buffer entries. The transport requests are listed in file ALL_old.lis, which is located in transport subdirectory tmp. The command t p c l e a r o l d a l l uses the result list of the command t p c h e c k a l l , to find files that are not needed anymore for import and that have exceeded a maximum age. To specify the maximum age, use the transport profile parameters DATALIFETIME, OLDDATALIFETIME, COFILELIFETIME, and LOGLIFETIME. Data files in the transport subdirectory data that are older For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
than the parameter DATALIFETIME are moved to the transport subdirectory olddata. Files in the subdirectories log and cofiles are immediately deleted when they exceed the age specified by LOGLIFETIME or COFILELIFETIME. Files in olddata are deleted if they are older than OLDDATALIFETIME.
O
Hint: Before cleaning up the transport directory, we recommend making a copy of the transport directory and saving it for audit purposes.
Hint: With the command t p t e s t o l d a l l , it is possible to create a list of files, which will be deleted by the command t p c l e a r o l d a l l . The result is located in subdirectory tmp.
Note: The files in the EPS subdirectory of the transport directory are not affected by the clean-up. The transport administrator has to deal with them manually.
Related Information: Transport Requests There is additional information concerning importing transport requests in the online documentation for SAP NetWeaver 7.31. Choose Application Help —*• Function-Oriented View —> Solution Life Cycle Management —*■ Software Logistics —> Change and Transport System —> Transport Tools. The following SAP Notes may be helpful: •
See SAP Note 41732: Deletion of data in transport directory
•
See SAP Note 83327: Setting up transport system in heterogeneous system group
LESSON SUMMARY
You should now be able to: •
Manage the transport directory
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 4
Learning Assessment
1. When a transport request is released, which of the following subdirectories does the system update at the file system level? Choose the correct answers. | A Buffer B Queue | C Cofiles D Control_files E Data 2. Which of the following statements about importing into a production system are true? Choose the correct answers. I A Production system should be shut down. B No users should be working with the affected business processes. | C No batch jobs running related to the affected business processes. D No RFC communication related to the affected business processes. E Change the role of production client to allow modifications. 3. Which of the following import options are supported in TMS? Choose the correct answers. | A Select requests according to filter settings B Complete projects | C Preliminary requests D All transport requests in the QA worklist E All transport requests in the import queue
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
4. Which of the following tp parameters are set to a value of T when the queue-controlled single transport strategy is chosen? Choose the correct answers. | A IMPORT_SINGLE_ONLY B NO_IMPORT_ALL | C IMPORT_SINGLE_STRATEGY D WORKFLOW_STRATEGY E IMPORT_ALL_STRATEGY 5. Which of the following is true about transport of copies? Choose the correct answers. | A Objects can be transported to any SAP system without following the transport routes. B The original location of the objects is not changed. C The transport request will not be added to the import queue of a subsequent SAP system. D The original location of objects can be changed to another system, and the package of the object can also be changed at the same time. E All objects of a package can be relocated to a different development system. 6. If the approval status is Distribution Required, the QA status for this request can be distributed. Determine whether this statement is true or false. | True False 7. After the transport administrator has approved your transport proposal, the import of the corresponding transport requests is not started and the transport proposal reappears in your transport proposal inbox. Determine whether this statement is true or false. | True False
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
8. During import, tp triggers the import dispatcher called RDDNEWPP to perform the steps in the import process. Determine whether this statement is true or false. | True False 9. tp commands are executed in the transport subdirectory bin by user adm. tp commands are called using syntax tp [argument (s) ] [option (s)]. Determine whether this statement is true or false. | True False 10. Which of the following tools can be used to monitor the import activities in TMS? Choose the correct answers. I A Import monitor B SLOG | C Table TRSTAT D ALOG E TLOG 11. When the tp parameter CHK_CRIOBJ_AT_IMPORT is set to W (warning) or E (error) then transport request is checked automatically before importing into the target system. Determine whether this statement is true or false. | True False
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
12. What is the sequence of steps performed during object development and testing? Arrange these steps into the correct sequence. 1 Release the transport request containing the developed objects. Freeze development of the objects in the development system. Import the objects and verify the changes in the quality assurance environment. J Sign off the changes. Allow further development on the objects in the development system. 13. The transport directory contains which of the following subdirectories? Choose the correct answers. | A bin B EPS C meta D cofiles E buffer 14. A tp return code between 100 and 199 is a tp warning, meaning that something went wrong and tp could not perform all the tasks. Determine whether this statement is true or false. | True False 15. Data files in the transport subdirectory data that are older than the parameter DATALIFETIME are moved to the transport subdirectory olddata. Determine whether this statement is true or false. | True False
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 4
Learning Assessment - Answers
1. When a transport request is released, which of the following subdirectories does the system update at the file system level? Choose the correct answers. [x ] A Buffer B Queue \x \ C Cofiles D Control_files \x \ E Data
2. Which of the following statements about importing into a production system are true? Choose the correct answers. I A Production system should be shut down.
[~xj B No users should be working with the affected business processes. [x ] C No batch jobs running related to the affected business processes. [x ] D No RFC communication related to the affected business processes. E Change the role of production client to allow modifications.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
3. Which of the following import options are supported in TMS? Choose the correct answers. |~xj A Select requests according to filter settings |~xj B Complete projects |~xj C Preliminary requests D All transport requests in the QA worklist |~X~| E All transport requests in the import queue
4. Which of the following tp parameters are set to a value of T when the queue-controlled single transport strategy is chosen? Choose the correct answers. [x ] A IMPORT_SINGLE_ONLY \x \ B NO_IMPORT_ALL \x \ C IMPORT_SINGLE_STRATEGY D WORKFLOW_STRATEGY E IMPORT_ALL_STRATEGY
5. Which of the following is true about transport of copies? Choose the correct answers. |~xj A Objects can be transported to any SAP system without following the transport routes. |~xj B The original location of the objects is not changed. |~xj C The transport request will not be added to the import queue of a subsequent SAP system. D The original location of objects can be changed to another system, and the package of the object can also be changed at the same time. E All objects of a package can be relocated to a different development system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
6. If the approval status is Distribution Required, the QA status for this request can be distributed. Determine whether this statement is true or false. | True \x \ False
7. After the transport administrator has approved your transport proposal, the import of the corresponding transport requests is not started and the transport proposal reappears in your transport proposal inbox. Determine whether this statement is true or false. | True \x \ False
8. During import, tp triggers the import dispatcher called RDDNEWPP to perform the steps in the import process. Determine whether this statement is true or false. | True \x \ False
9. tp commands are executed in the transport subdirectory bin by user adm. tp commands are called using syntax tp [argument (s) ] [option (s)]. Determine whether this statement is true or false. [x ] True False
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
10. Which of the following tools can be used to monitor the import activities in TMS? Choose the correct answers.
|~xj
A Import monitor
\x \ B SLOG | C Table TRSTAT \x \ D ALOG E TLOG
11. When the tp parameter CHK_CRIOBJ_AT_IMPORT is set to W (warning) or E (error) then transport request is checked automatically before importing into the target system. Determine whether this statement is true or false. | True \x \ False
12. What is the sequence of steps performed during object development and testing? Arrange these steps into the correct sequence. |~l] Release the transport request containing the developed objects. [ 2] Freeze development of the objects in the development system. [ 3] Import the objects and verify the changes in the quality assurance environment. [ 4 ] Sign off the changes. [ 5 ] Allow further development on the objects in the development system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
13. The transport directory contains which of the following subdirectories? Choose the correct answers. [x ] A bin \x \ B EPS | C meta |~x] D cofiles |~X~| E buffer
14. A tp return code between 100 and 199 is a tp warning, meaning that something went wrong and tp could not perform all the tasks. Determine whether this statement is true or false. [x ] True False
15. Data files in the transport subdirectory data that are older than the parameter DATALIFETIME are moved to the transport subdirectory olddata. Determine whether this statement is true or false. [x ] True False
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
UNIT 5
Enhanced Change and Transport System (Enhanced CTS)
Lesson 1 Configuring the Change and Transport System (CTS) for Transporting Non-ABAP Objects
258
Lesson 2 Transporting Non-ABAP Objects
277
Exercise 12: Transport Non-ABAP Objects with Enhanced CTS
289
UNIT OBJECTIVES •
Configure the CTS for transporting non-ABAP objects
•
Use enhanced CTS to transport non-ABAP objects
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 5 Lesson 1 Configuring the Change and Transport System (CTS) for Transporting Non-ABAP Objects
LESSON OVERVIEW This lesson describes how to configure the Change and Transport System (CTS) for transporting non-ABAP objects. LESSON OBJECTIVES After completing this lesson, you will be able to: •
Configure the CTS for transporting non-ABAP objects
HANA Application Lifecycle Management Depending on your implementation scenario, developers will create various HANA objects products, delivery units, packages, analytic and attribute views, etc. These objects normally are created in the HANA development system, and then transported into the other HANA systems in a managed way. Traditionally, customers had the choice of performing HANA transports manually through the export/im port functionality in HDB Studio or using integration with enhanced SAP Change and Transport System. HANA 1.0 SPS6 included a new alternative called HANA Application Lifecycle Management (ALM). The ALM is an XS application that is automatically installed as part of the HDB Server. The keys tasks that HANA ALM can perform are as follows: •
Designate source and target systems for transports
•
Assign the appropriate delivery units to the transport route
•
Execute a transport
•
Execute exports and imports (uploads and downloads)
•
Monitor the transport processes
SAP Change and Transport System (CTS) is the feature used to transport ABAP objects between systems in a landscape. SAP CTS was enhanced to cater non-ABAP objects - this enhanced version is known as Enhanced CTS. Since SAP HANA, SP5 Enhanced CTS has been enabled to transport SAP HANA objects as well.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Figure 107: Typical Enhanced CTS Deployment
The steps are explained as follows: 1. The user sets up a HANA delivery unit with the required HANA packages in HDB Studio. 2. The user triggers an export of the delivery unit in HDB Studio, and selects the option to connect to the CTS Organizer. This includes the exported objects in an ABAP transport. 3. he user connects to the CTS System and uses the STMS functionality to transport the HANA objects to subsequent systems in the HANA landscape. 4. Enhanced CTS calls the deployment service of the target HANA system which will import the HANA objects contained in the ABAP transport to the HANA system. The question is which of these tools — HANA ALM or HANA Enhanced CTS — best fits your use case. Both tools overlap in functionality, and choice really depends on your SAP Landscape. We will approach this question by a series of qualifying statements, and then for each we recommend which tool is most appropriate. When using this you must take into account your landscape as well as any other important factors that are part of your scenario. Qualifying Statement
HANA ALM
Enhanced CTS
Your SAP environment is made up of many SAP sys tems and you have an estab lished change process around ABAP transports.
X
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Qualifying Statement
HANA ALM
Enhanced CTS X
Your SAP environment already includes Enhanced CTS for transporting non-ABAP relat ed objects e.g. Portal, PI or SLD. Your HANA content is expect ed to be managed by a sepa rate dedicated group of people who have no responsibility or knowledge of your other SAP systems.
X
Your landscape does not con tain other SAP systems (ABAP or Java).
X
Your SAP landscape contains many ABAP systems but you do not have any Java systems for implementation of En hanced CTS.
X
Your SAP changes are man aged via SAP Solution Manag er Change Request Manage ment (ChaRM).
X
Overview of Transporting Non-ABAP Objects In an SAP system, you can develop in ABAP, in the J2EE / JEE standard, or in SAP-specific nonABAP technology, such as Web Dynpro Java, or SAP Enterprise Portal applications. You choose from these options based on the business applications, the available technologies, or technical advantages. So, you will find many or even all of these objects in an SAP landscape. When you use SAP Enterprise Portal, for example, to provide users with role-based access to a new functionality in your SAP ECC server backend SAP system, you need to synchronize the update of both the SAP Enterprise Portal and the SAP ECC server runtime. This step might even involve other SAP systems, for example, SAP Process Integration. When you use SAP NetWeaver Development Infrastructure (SAP NWDI for short) with its transport capabilities it simplifies the process. However, the easiest way is to manage such transports centrally in one SAP system. Tools for ABAP and Java Transports
So there are tools for ABAP and Java transports available (up to SAP SupportPackage stack 12 for SAP NetWeaver 7.0) and please note the following:• •
There is no automatic synchronization for mixed applications (such as SAP NetWeaver Process Integration) so you must use different tools to transport separate parts of the same application.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
There is no central control of SAP Enterprise Portal transports. (In addition, only rudimentary export/import tools are available. These tools are neither integrated into SAP NWDI nor into CTS.)
•
There is no central control of all transports into production SAP systems. — srl Multiple Development Workbenches
Sfc '
l
fill
S A P N.-tW*av*r'
Different Transport Tools
SAP CTS
SAP NWDI
AS ABAP
AS Java
□
S T Multiple Types of Backends
AS ABAP
AS ABAP+Java
AS Java
AS Java
Figure 108: Classic Transport Scenario: Different Tools for ABAP and Java Transports
With the enhancements of the SAP Change and Transport System (referred to as CTS+ or enhanced CTS), available with SP Stack releases of SAP NetWeaver 7.0, the CTS has been enhanced to handle the transport of non-ABAP objects.
One Central Transport Tool
Multiple Types of Backends
■
Enhanced CTS
AS ABAP
AS ABAP+Java
AS Java
AS Java
Enhanced CTS offers the transport of objects created in other environments than ABAP via the ABAP Change and Transport System (CTS) Figure 109: Using the Enhanced CTS
Therefore, an administrator of the AS ABAP system can now manage transports for the NonABAP parts of your SAP system landscape. By combining and synchronizing transports in a comprehensive approach, the enhanced Change and Transport System solves the transport issues.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
SAP System Landscape with Enhanced CTS The figure An SAP System Landscape Example with the Enhanced CTS shows an example of an SAP system landscape used with the enhanced Change and Transport System. In this figure, the Transport Domain Controller (TDC) is located on an SAP Solution Manager system which is an ABAP + Java-based SAP system. In addition, the CTS Deploy Web Service is configured in this system. Transport Domain Controller (TDC)
System landscape as defined on the TDC system (Transaction STMS) SAP ECC Consolidation Route
QCC
Delivery Route
SAP PI PIQ SAP Portal QEP
Figure 110: An SAP System Landscape Example with the Enhanced CTS
Hint: A different option than the one illustrated is to use an AS ABAP-based SAP system as a TDC system, and connect this SAP system to a different AS Java (different SID), where the CTS Deploy Web Service is configured. Within transaction s t m s on the TDC system, define both ABAP and non-ABAP systems (SAP systems) and configure Java Stacks for existing AS ABAP-based SAP systems. The SAP system landscape shown here contains a three-system landscape for SAP ECC systems. In addition, it contains a three-system landscape of SAP Enterprise Portal systems (usage type EP) and a three-system landscape for SAP Process Integration systems (usage type PI). Previously, SAP application products were shipped together with product-release-specific software logistics tools (SL tools). To be able to make the newest SL tools available for SAP application product releases, an independent delivery channel Software Logistics Toolset (SL Toolset) has been established. With the help of the CTS plug-in (software component CTS_PLUG), which is part of the SL Toolset, SAP continuously improves the capabilities of the Change and Transport System independently of SAP NetWeaver, SAP Solution Manager, or Support Packages. The CTS plug-in offers capabilities to define SAP and non-SAP application types and import actions to connect them with CTS using SAP Solution Manager. It also allows you to use your own deployment methods to import SAP and non-SAP applications into your target systems from CTS.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
SAP System Requirements
To use the enhancements of the change and transport system, both the CTS system and the runtime SAP systems must fulfill certain requirements.
Note: The term CTS system refers to SAP systems based on AS ABAP + Java, which the CTS Deploy Web Service is configured and will be used. This note refers to an SAP Solution Manager system or an SAP Process Integration system. The following list contains the SAP system requirements, which must be fulfilled for the Transport Domain Controller (TDC) system / the CTS systems. Requirements for TDC and CTS - AS ABAP Part
•
Establish the latest tp / R3trans version
•
At least AS ABAP 7.00 with SP Stack 12 (SP Stack 14 recommended)
•
Configure the connection to CTS Deploy Web Service
•
Configure the TDC System as Transport Domain Controller in transaction STMS
•
Define, if applicable, non-ABAP SAP systems and transport routes between these SAP systems
Requirements for TDC and CTS - AS Java Part
•
Configure and make the CTS Deploy Web Service operational
•
At least AS Java 7.00 with same SP Stack as AS ABAP part
If the TDC system is an AS ABAP + Java —based SAP system, you must fulfill all requirements on this SAP system. If the TDC system is an AS ABAP-based SAP system only, you must fulfill the AS Java part on a connected AS Java system (SAP system with a different SID).
Hint: As of enhancement package 1 for SAP NetWeaver 7.0, CTS Deploy Web Service is included in a software component that belongs to the AS Java. For SAP systems, based on SAP NetWeaver 7.0 (without any enhancement package installed), the CTS Deploy Web Service was shipped with the software component DI_CMS. However, you must deploy this software component on the AS Java part of every CTS system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Note: Using the CTS Deploy Web Service in another SAP system, as well as general information concerning enhanced CTS, is available in SAP Note 1003674, Enhancement for Non-ABAP SAP systems in CTS. It is also available on the SAP community network quick link /it-management/alm/sof tware-logistics (http://sen.sap.com/community/it-management/alm/softwarelogistics). From the second URL, you may follow the link to the key topic Change and Transport System (http://scn.sap.com/docs/DOC-7643).
Runtime SAP Systems
In addition to the CTS systems, the runtime SAP systems (that means the SAP systems that are included in the STMS SAP system landscapes) must fulfill certain requirements. SAP systems based on AS ABAP •
No specific release is required (CTS compatibility is sufficient)
SAP systems with usage type EP •
Minimum release SAP NetWeaver 2004 SP Stack 09
•
Configuration / Transport Scenario depends on Release / SP Stack (simplified with SAP NetWeaver 7.0 SP Stack 14)
SAP systems with Usage Type PI •
Minimum release SAP NetWeaver 2004 SP Stack 13
•
Configuration / Transport Scenario depends on Release / SP Stack (simplified with SAP NetWeaver 7.0 SP stack 14)
SAP systems with Usage Type Dl (NWDI systems) •
No specific release required
•
Simplified with SAP NetWeaver 7.0 SP Stack 14
Configuration of SAP Systems for Transporting Non-ABAP Objects Table 11: Main Steps for the Configuration of the CTS The following table summarizes the main configuration steps that are necessary on the Transport Domain Controller (TDC) system and the other CTS systems. Steps
Description
1
Export part: Activate ABAP Web Dynpro for Transport Or ganizer. Performed this step on the TDC System and on ev ery CTS development system (DEV stage).
Transaction •
SICF
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Steps
Description
2
Import part: Configuration of CTS Deploy Web Service. Per formed this step on the TDC System and on every CTS tar get system (QAS, PRD stage)
3
Transaction
System Landscape part: Acti vate Transport Domain Con troller and configure system landscape.
•
SM59
•
LPCONFIG
•
STMS
The CTS Deploy Web Service runs on the AS Java part of the CTS system. Configure it on the AS ABAP part of the CTS system because the AS ABAP part requires knowing how to connect to the CTS Deploy Web Service.
Hint: Configure the CTS Deploy Web Service on every SAP system on which the tp program triggers the deployment (for example, SDM deployment). For target systems based on AS Java (only) this step will be the communication system as defined in transaction s t m s . Typically, this communication system will be the transport domain controller system. For target systems based on AS ABAP + Java 7.00 SP Stack 12 or higher (for example, an SAP Process Integration system), tp can be called on the SAP system itself. These three main steps will be discussed in more detail in the following subsections. Training System Landscape in ADM325
SAP system landscape for transport domain DOMAIN_PSM
Consolidation
Delivery
Route
Route
*
SAP system landscape for transport domain DOMAIN_ECC DCC
Consolidation
QCC
Route
Delivery Route
PCC TDC
Figure 111: Course Training System Landscape
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Table 12: Systems in ADM325 Training System Landscape The figure Course Training System Landscape displays an illustration of the following systems: System ID
Export Configuration
Import Configuration
Remarks
PSM
X
X
Communication sys tem for DEP, QEP, and PEP
DCC, QCC, PCC
Systems based on AS ABAP only
DEP, QEP, PEP
Systems based on AS Java only
In this scenario, there is an SAP three-system landscape DEV, QAS, and PRD of SAP systems in the transport domain DOMAIN_PCC. This system landscape is not considered in this lesson because the runtime systems are not based on AS Java. There is a three-system SAP NetWeaver Enterprise landscape DEP, QEP, and PEP in the transport domain DOMAIN_PSM with runtime systems based on AS Java. These three SAP systems will have the transport domain controller system PSM as a communication system (in transaction s t m s , System Overview screen). In this case, configure the import part on the PSM system, as well because PSM plays the role of the communication system for the QEP and PEP system. The import into QEP, for example, will use tp and the CTS Deploy Web Service on the PSM system. Configure the export part on the PSM system, as well. This SAP system acts as communication system. It communicates for the DEP system so that transport requests for DEP (transport requests named DEPK9) will be created with the help of the Transport Organizer Web Ul that is located on the PSM system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Export Configuration: Activation of the Transport Organizer Web Service
Maintain service
Figure 112: Export Part Activation of the Service for the Transport Organizer Web Ul
As of SP Stack 13 of SAP NetWeaver 7.0, SAP provides a Web Dynpro application (CTS_BROWSER) that helps you to create transport orders and attach objects. Before you can use the Transport Organizer Web Ul, activate the CTS_BROWSER service in transaction s i c f on the CTS system (AS ABAP part).
Hint: With the SC CTS_PLUG 200, SAP ships an enhanced version of the Transport Organizer Web Ul (ABAP Web Dynpro application CTS_ORGANIZER). Activate this service in transaction s t m s in order to use it. For more information about this software component, see the online documentation at http://help.sap.com/ nwcts.
Import Configuration: Configuration of CTS Deploy Web Service As of enhancement package 1 for SAP NetWeaver 7.0, CTS Deploy Web Service is part of the SAP NetWeaver Application Server for Java. The figure Configuration of CTS Deploy Web Service shows the necessary steps to configure the CTS Deploy Web Service on the CTS system. The CTS Deploy Web Service connects the ABAP transport tools to the deployment tools in nonABAP applications.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Figure 113: Import Part: Configuration of CTS Deploy Web Service
The first step as displayed in the Configuration of CTS Deploy Web Service figure is to check the CTS Deploy Web Service on the AS Java part of the CTS system. To do this operation, open a browser, enter the URL for the AS Java start page on the CTS system and navigate to the Web Services Navigator. Verify that the Web Service DeployProxy is available in the list of the available Web Services on that server. The next step is to configure a logical port for the CTS Deplay Web Service. As of enhancement package 1 for SAP NetWeaver 7.0, SAP ships the logical port CTSDEPLOY for the proxy class CO_TFLDEPLOY_PROXY_VI_DOCUMENT in client 000 with the standard installation. This logical port refers to the RFC destination CTSDEPLOY. You therefore only need to check in transaction LPCONFIG (in client 000) that this logical port exists.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Note: When your TDC system or CTS system is based on SAP NetWeaver 7.0 (without any enhancement package), you need to create the logical port manually). For this step proceed as follows: 1. As logical ports are customizing objects, enable customizing changes for client 000. This step can be done in transaction SCC4. Make sure that Changes and Transports for Client-Specific Objects are allowed in this client. 2. After verifying that changes to customizing objects are allowed in client 000, create a logical port for the CTS Deploy Web Service. Do this step in transaction l p c o n f i g (client 000 in the AS ABAP part of the CTS system). In transaction l p c o n f i g , select the Proxy Class CO_TFLDEPLOY_PROXY_VI_DOCUMENTfrom the list (F4). Enter the Logical Port c t s d e p l o y ,select the Default Port checkbox and choose Create. On the next screen, enter a description for that logical port. On the Call Parameters tab, choose the HTTP Destination c t s d e p l o y and the Path Suffix /DeployProxy/default?style=document. Save and activate your changes. Record your changes within a new transport request. 3. After this step, reset the client change options of client 000 in transaction No Changes Allowed.
SCC4
to
Finally, create a new HTTP connection with the name c t s d e p l o y as RFC destination of connection type G in transaction SM 59. The name of this RFC destination will be needed for the logical port of the CTS Deploy Web Service. On the Technical Settings tab, enter the host name and the port of the AS Java part of the CTS system. On the tab Logon & Security, choose Basic Authentication as logon procedure (you may need to confirm a dialog box). As logon user, select the user ID of the AS Java part on which the CTS Deploy Web Service is used. This user must have the authorization to use the CTS Deploy Web Service. Large objects can cause timeouts in deployments. Therefore, you may need to set a timeout parameter for the Internet Communication Manager (ICM) on the CTS system (AS ABAP part), and on target systems based on AS ABAP + Java: to be longer than the longest expected deployment time. This step can be done in the definition of the RFC destination (transaction SM 59, tab Special Options) as well.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Transport Domain Controller and System Landscape Setup Configuration
STM S Icr-
Mo fMm iMwwnart 3*How M ot) 6 T r a n s p o r t M a n a g e m e n t S y s te m a
i w
*
A .? l
U
i i i » ________________ # * i _
liW M D m r
9 r* * " " o ro
OM*W«.OTO Trmoort iW
i OTO
© Figure 114: Activate Transport Domain Controller
Before you can work with the Transport Management System (TMS), configure it in your SAP system landscape. The TMS configuration includes the configuration of the transport domain. In this step, you define which SAP systems in your SAP system landscape form a transport domain, and which SAP system is to be the transport domain controller. Choose a CTS system to be the transport domain controller.
Note: The procedure to activate the TMS is the same as for normal ABAP transports, therefore in this step there is no specific configuration required for the enhanced functionality of CTS.
Table 13: Sequence of the Roadmap - Configuration of the SAP System Landscape This table shows the steps required to configure the SAP system landscape on the transport domain controller system. Steps
Description
3.1
Define non-ABAP systems/ Java stack configurations, and enter user and password for the deployment into this sys tem for the STMS System Overview.
3.2
Check and maintain tp param eters for non-ABAP systems for the STMS System Over view.
Transaction STMS (System Overview)
STMS (System Overview)
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Steps
Description
3.3
Define transport layers and transport routes for STMS Transport Routes.
Transaction STMS (Transport Routes)
Note: The configuration steps differ in detail with respect to both the SP stack level and the usage type (PI versus EP versus Dl) of the SAP systems in question.
Depending on the usage type of the runtime system, create the following Non-ABAP systems or perform Java Stack Configurations in transaction s t m s (System Overview area) on the transport domain controller system: •
Transport between SAP systems based on AS ABAP + Java (usage type PI, for example): If the CTS system is based on SAP NetWeaver 7.0 SP Stack 14 or higher, you need to create a Java Stack Configuration for the existing SAP system in transaction s t m s . Include the SAP Process Integration development system, the SAP Process Integration quality assurance system, and the SAP Process Integration production system to the transport domain as you do it for ABAPbased SAP systems. So, you need three SAP systems in transaction s t m s (in addition to the CTS system if the CTS system is different from one of the SAP Process Integration systems in question).
•
For transports between SAP systems based on AS ABAP (only), you do not need any nonABAP Systems in transaction s t m s .•
•
For transports between SAP systems based on AS Java only (usage type EP for example), define three non-ABAP Systems in transaction s t m s representing your Java development system, the Java quality assurance system, and the Java production system. With the CTS system, you use four SAP systems in transaction s t m s .
Note: For any non-ABAP System, choose the Transport Domain Controller system (TDC system) to be the Communication System when this SAP system fulfills the requirements listed in the SAP System Requirements section.
Table 14: tp Parameters Maintained with ABAP SAP Systems The following table shows the necessary tp parameters that need to be maintained on the transport domain controller system for the non-ABAP SAP systems in question:
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
Systems Source System •
Development system - AS Java part
•
Transport domain controller
Target System •
Quality assurance system
•
Production system - AS Java part
tp Parameters NON_ABAP_WBO_CLIENT NON_ABAP_SYSTEM* WB0_G ET_R EQ_ST RATEGY WBO_REL_REQ_STRATEGY NON_ABAP_WBO_INBOX•** WBO_FILE_TRANSFER DEPLOY_DATA_SHARE DEPLOY_WEB_SERVICE DEPLOYJJRL (or DEPLOY_XI_URL or DEPLOY_SLD_URL) NON_ABAP_SYSTEM*
* needed only for systems without AS ABAP ** needed only in case of loose coupling
The necessary tp parameters differ between the source system on the one hand and the target systems on the other hand. To check or maintain these parameters, use transaction s t m s o f the Transport Domain Controller system (System Overview area, double-click the SAP system in question and then select the Transport Tool tab). The available parameters are as follows: •
NON_ABAP_WBO_CLIENT specifies the client (on the CTS system or on the development system when it contains an AS ABAP stack) where transport requests can be created and released. This parameter is required to enable the Transport Organizer Web Ul and to restrict this Web Ul for non-ABAP SAP systems to one client.
•
The parameter WBO_GET_REQ_STRATEGY (SMART, TAGGED or CREATE) defines the automatic creation of transport requests during the export process. The parameter WBO_REL_REQ_STRATEGY (AUTO or MANUAL) defines the automatic release of transport requests.
•
The parameter NON_ABAP_WBO_INBOX points to the directory in which the transport organizer looks for files that are candidates to be transported. This parameter is used for loose coupling only (file transfer using a mount directory or a share directory).
•
If your SAP application is closely integrated with CTS (this step can be the case for SAP Enterprise Portal, SAP Process Integration, SAP NWDI, or SLD systems), you can attach objects directly from the application by default. The data is then transferred to the CTS server using SAP Java Connector (JCo). In this case the parameter WBO_FILE_TRANSFER is set to Stream (this value is the default value). If you need to transfer files using a share or a Network File System however, set the parameter WBO_FILE_TRANSFER to Share.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
The parameter DEPLOY_DATA_SHARE points to the directory where tp stores the data and the CTS Deploy Web Service takes it for deployment to the runtime SAP systems. For SAP systems based on AS ABAP (or AS ABAP + Java) the value of parameter DEPLOY_DATA_SHARE should point to the data directory beneath DIR_TRANS on the SAP system in question. This parameter will be generated automatically but you may need to adapt the value of this parameter manually.
Note: Instead of the parameter DEPLOY_DATA_SHARE, you can also use the parameter CTS_FILE_PROVIDER_URI. With this parameter, define an SAP Java Connector connection (JCo connection) for transferring data to the target system (instead of using a directory on operating system level). This parameter is only evaluated if the parameter DEPLOY_DATA_SHARE is not set.
•
The value of parameter DEPLOY_WEB_SERVICE must be the name for the logical port in transaction l p c o n f i g before (for example c t s d e p l o y ).This parameter is generated automatically.
•
If you want to trigger the deployment in the target systems, specify the tp parameter DEPLOYJJRL. This parameter is generated automatically and should point to the URL of the deploy tool (for example, SDM or deploy controller) in the target system.
The import of Java applications into subsequent SAP systems will be performed by the ABAP transport control program called tp. tp calls the CTS Deploy Web Service according to the tp parameters. The CTS Deploy Web Service in turn calls the deploy tool (for example the Software Deployment Manager (SDM) or the Deploy Controller (DC)). Specify a user with appropriate permissions to perform the import. This user must be specified on the transport domain controller system of the transport domain to which the SAP system belongs. In the System Overview area of transaction s t m s the transport domain controller, double-click the SAP system in question and select the Transport Tool tab. •
If your SAP system is an SAP Process Integration system, choose Goto —► XI User/ Password and enter the credentials of the user who will start the deployment. This user must exist on the selected SAP Process Integration system and the PFCG role SAP_XI_CMS_SERV_USER must be assigned to this user.
•
If your SAP system is based on an AS Java only (for example an SAP Enterprise Portal system), the deployment will be performed by the SDM or by the deploy controller. Therefore, choose Goto —>SDM/DC User/Password and enter the appropriate credentials for the Javabased SAP system in question. Either the SDM password or a user in the Java-based SAP system in question who is allowed to trigger the deployment.•
•
For the System Landscape Directory (SLD), the deployment procedure is different. Specify a different user on the SLD application.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Note: Perform this step for every SAP system in which you want to import non-ABAP objects. When you activate the Deployment Service for target systems (during the creation of a non-ABAP system or a Java Stack Configuration in transaction STM S) these credentials are maintained/stored automatically. Next, define transport layers and transport routes (consolidation routes and delivery routes) between the non-ABAP SAP systems in question. The transport layers and the transport routes that are required depend on the usage of different types of the SAP systems and on the SP stack level of the CTS system. The definition of transport layers and transport routes is done on the Transport Domain Controller system (TDC system) in transaction STMS ( Transport Routes button). Check TMS Settings
Once you have configured the TMS, there are some tests that you can perform to verify that there are no technical problems with the TMS configuration. For example, verify that the tp program and its parameter configuration are consistent. To do this step, from the Systems screen of the STMS, follow SAP System —> Check —► Transport Tool. This step executes tests that verify the tp interface, the transport profile, the RFC destinations, connection to the databases, and returns a report of the results. Configuration of SAP Systems In addition to the configuration of the Transport Domain Controller, you may need to configure your runtime SAP systems (that means the SAP systems used between the export and import). The necessary steps for the configuration of runtime SAP systems differ with respect to the usage type of these SAP systems. For target systems based on AS ABAP only, no specific preparation steps are required for the use of enhanced CTS. You simply configure your SAP systems for the use with CTS as usual. In addition, no specific release of the SAP systems based on AS ABAP only is required. The CTS compatibility is sufficient in this case. If you want to transport SAP Enterprise Portal content with the help of the enhanced CTS, configure the SAP Enterprise Portal systems accordingly. The main steps to be performed on all source systems are: 1. Maintain the Destinations service. 2. Use Single Sign-on (assertion tickets): if not available, maintain logon data. The RFC Destination is sap.com/com.sap.tc.di.CTSserver.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Analysis O verfle w * A d m stia b o n
De*4oy and Change C onfiguration
1
ttsto ry
D e s tin a tio n s
Destinations
»
D e s tin a tio n s
• Overflew • Aoo ca to n Modules
B>:«
m ms
D e ta ile d N a v ig a tio n
D e ta ils
• Appfcstton Rescu ces S a v e lfc a r w il • Visual Hosts
•LogtfOops
Destination
• System Properties Destination None
sap confcomsaptc olCTSserver
• Log Configuration Desfination Type: • SPNEGO Configuration VMwd C on nection S e flm g t
• Trusted Systems
Load Bslancrg.
TYes
System
*CT$
System fim oer
S y s te m L a n d s c a p e S e le c tio n
C cnti^r ed User
(SNo
• O rrent Jser (Assertion Tctet)
System*
C O rre rt User (Logon Ticket)
!□
System 0
Gateway Host Gateway Serflce
( Active
• inactive
R e p o rt o ry C onnection
11
A iite r tc M
Destination
B n y iy
»
[ihsOestinMion _
Pool S e ttin gs Connection Mode
SNCLtraryPath
Pool See M KdaunW W Tme
tQjOOO
SAP Router Sung Q RFC Trace
Figure 115: Configuration of SAP Enterprise Portal Source Systems as Runtime Systems
Applications or services can establish connections to other services. When using such connections, specify the remote service's address and the user authentication information to use for the connection. Many applications use the Destination service for this purpose. You can manually create HTTP destinations and RFC destinations using the Destination service in SAP NetWeaver Administrator (see the figure Configuration of SAP Enterprise Portal Source Systems as Runtime Systems) or in the Visual Administrator tool. Before you can attach objects to transport requests directly in the application, use RFC to connect your SAP application system to the CTS system. An SAP application system might be the SAP NetWeaver development infrastructure or SAP Enterprise Portal. The CTS system is more specifically the SAP system that acts as Communication System for your SAP Enterprise Portal system. This step enables your application to communicate with the transport system. To create this RFC connection open SAP NetWeaver Administrator of your SAP application system and choose (System Management —► ) Configuration —► Destinations. Create a destination of Type RFC (for the development system as Hosting system) called (exactly) sap.com/com .sap.t c . .CTSserver by choosing New. d
i
Maintain Destination Service to the CTS Systems
•
In the Connection and Transport Security Settings area, enter the connection data of your CTS system.
•
In the Logon Data area, select the Current User (Assetion Ticket) option as authentication for the connection to your CTS system. We recommend that you use Single Sign-On (SSO). If you cannot use SSO, select the Configured User option and enter your preferred language, a client, and an appropriate username and password. Enter the client from the tp parameter NON_ABAP_WBO_CLIENT on the CTS system. Use the value help under Repository Connection.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
In the Logon Data area, select the Current User (Assetion Ticket) option as authentication for the connection to your CTS system. We recommend that you use Single Sign-On (SSO). If you cannot use SSO, select the Configured User option and enter your preferred language, a client, and an appropriate username and password. Enter the client from the tp parameter NON_ABAP_WBO_CLIENT on the CTS system. Use the value help under Repository Connection.
•
In the Specific Settings area use, the default values for the Pool Settings. Finally choose Finish to save the destination.
Note: In SAP Process Integration runtime at SAP systems, create the Service user n w d i _ c t s a d m i n and to assign the role SAP_XI_CMS_SERV_USER to that user. The user that you have created will be used in the TDC system in the TMS System Overview. On the Transport Tool tab for the SAP system you selected, choose Goto —► XI User/Password from the menu and enter the credentials that you have maintained in the SAP Process Integration system.
LESSON SUMMARY
You should now be able to: •
Configure the CTS for transporting non-ABAP objects
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
Unit 5 Lesson 2 Transporting Non-ABAP Objects
LESSON OVERVIEW
This lesson explains how to use enhanced CTS to transport non-ABAP objects. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Use enhanced CTS to transport non-ABAP objects
Non-ABAP Objects Transport Process Flow After completing all necessary configuration steps, you are able to transport non-ABAP objects into subsequent target systems. The configuration steps include configuring for the transport domain controller system, that is, SAP systems on which the CTS deploy web service is configured (also known as CTS system) and the SAP systems that are included in the transport landscape. The following roadmap contains the main steps to transport non-ABAP content with the help of the enhanced Change and Transport System (CTS). As a prerequisite, all necessary configuration steps both on the TDC system and the target systems must have been performed. Table 15: Roadmap Transporting for Non-ABAP Content A summary of the steps for transporting non-ABAP content appears in the following table:
0
Step
Description
Transaction
Person
1
Create transport re quest (Workbench re quest)
SE09 orWebUI
Developer
2
Attach non-ABAP ob jects to transport re quest
SE09 orWebUI
Developer
3
Release transport re quest
SE09 orWebUI
Developer
4
Import transport re quest into subsequent SAP systems
STMS_QUEUES
Administrator
Step
Description
Transaction
Person
5
Test and activate con tent in target system in SAP PI directory content transports
Integration Builder or Integration Directory
Administrator
To transport non-ABAP content, in step 1 create a transport request (for SAP systems based on AS ABAP + Java use a workbench request). This step can be performed on the source system with transaction S E 09 (for development systems based on AS ABAP + Java). It can also be performed or on the communication system with the help of the Transport Organizer Web Ul (for development systems based on AS Java only).
Hint: Depending on the tp parameter WBO_GET_REQ_STRATEGY, you can configure the Transport Management System in such a way that a transport request will be created automatically. In step 2, attach non-ABAP objects (for example, SCAs, EARs, SDAs, EPAs, TPZs) to this transport request. This step can also be done either directly in transaction s e o 9 of the source system (based on AS ABAP+ Java 7.0 or higher) or with the help of the Transport Organizer Web Ul in the communication system. The Transport Organizer Web Ul applies in a development system based on AS Java only. In step 3, release the transport request. Again this step can be done either directly in transaction s e o 9 of the source system or with the help of the Transport Organizer Web Ul in the communication system.
Hint: Depending on the tp parameter WBO_REL_REQ_STRATEGY, you can configure the Transport Management System in such a way that a transport request will be released automatically. After the export has finished successfully, perform step 4 and import the transport request to a subsequent SAP system (for example, the quality assurance SAP Enterprise Portal system). The import can be introduced with transaction s t m s _QUEUES on either the target system (if it is based on AS ABAP + Java) or on the TDC system.
Hint: Transaction s t m s _QUEUES offers a subset of the s t m s functions. In the case of Integration Builder Content transports (TPZ files) and depending on the release and SP stack level, it might be necessary to activate the changes manually in the Integration Directory of the target system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Note: The transactions or Web Uls for the steps listed on the roadmap mentioned previously depend on the SP Stack level of the communication system.
Creation of Workbench Requests for Non-ABAP Objects Before you can perform the integrated transport scenarios, you create a workbench request transport request. This transport request can be created manually several ways. It can be created on the development (source) system in transaction S E 0 9 (Transport Organizer). It can be created in the Transport Organizer Web Ul, which is based on CTS_BROWSER, which is a Web Dynpro Application that runs on the AS ABAP part of the communication system. Or the transport request can be created automatically by the application by setting the tp parameter WBO_GET_REQ_STRATEGY to smart or create for the source system.
Figure 116: Creation of Workbench Requests
Note: The CTS_BROWSER Web Dynpro for the Transport Organizer Web Ul is available as of SAP NetWeaver 7.0 SP Stack 13 (for the communication system). It can be accessed directly from the entry screen of transaction STMS using the Transport Organizer Web Ul button.
©
Hint: When you create a transport request with transaction S E 0 9 , which transports nonABAP transport objects only, you may delete the tasks that are not needed for nonABAP transports. That is, only the transport request is needed for the transaction.
The transport request that you create with the help of this web Ul on the communication system will be named K9. This means that the number is a running number and is the name of the development system according to your transport landscape. For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
There are two options to attach non-ABAP transport objects (EAR or SCA files) to existing workbench requests. More detail about these options follows: •
Option 1- Transport Organizer. If you use transaction SEO 9 on the development (source) system, store the file in question on this host. Select the new transport request and choose the Include Objects button and choose Non-ABAP Object. Then, specify the directory and file name, which you want to deploy through CTS to the runtime SAP systems configured in the transport system landscape. Specify the type of application and deployment. The outcome is a non-ABAP object displayed in the Object List of the transport request.
•
Option 2 - Transport Organizer Web Ul. There are two ways you can do this process. First method,. You can start a browser and enter the following URL: http:/^Communication System-Host>:/sap/bc/webdynpro/sap/cts_browser?saplanguage=< language key>&SYSID=&APPLiCATiON=OTHERS. Alternative method. You can enter transaction STMS and select the Transport Organizer Web Ul button to attach non-ABAP objects. Either way, you can create a new transport request or select an existing transport request to attach files from your file system. Enter the client for which you want to perform the transport, your user ID in the communication system, and password.
Note: For certain transport scenarios, it might be necessary to mark this transport request as a Preselected Request.
O
Hint: With software component CTS_PLUG 200, which is part of SL Toolset, SAP ships an enhanced version of the Transport Organizer Web Ul. The related (ICF-) service CTS_ORGANIZER can be requested using the URL: http://:/sap/bc/webdynpro/sap/cts_organizer?saplanguage=&SYSID=&APPLICATION=OTHERS
There are several types of objects that can be attached to a transport request. You can browse your file system and choose the file that you want to attach to the transport request. When you have found the required file, choose the Attach button (you may need to switch into change mode for this step).
O
Hint: In SAP Enterprise Portal transports for the development portal system as of SP stack 14 for SAP NetWeaver 7.0, it is also possible to attach SAP Enterprise Portal files (for example EPA files). You can attach them directly from the Package Explorer to a transport request without browsing the file system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Transport Requests Containing Non-ABAP Objects After assigning non-ABAP objects to a transport request, you can release this transport request. The release of a transport request starts the export of the files to file system level (transport directory). After releasing the transport request, this transport request is ready for import into a subsequent SAP system (according to the definition of the transport landscape in transaction STMS on the transport domain controller system).
The release of the transport request K9 can either be done manually in transaction SE09 on the development system (in case of a development system based on AS ABAP + Java 7.0 SP Stack 12 or higher) or using the Transport Organizer Web Ul. This step is shown in the Releasing Transport Requests figure. Or it can be done automatically (by setting the tp parameter WBO_REL_REQ_STRATEGY for the source system to a u t o ). The import of transport requests into subsequent SAP systems is done in transaction STMS_QUEUES (a subset of transaction STMS) on the transport domain controller (TDC) system.
Figure 118: Importing Transport Requests
In transaction s t m s _QUEUES, double-click the consolidation system where you want to import the transport request (previously assigned as Target (System) in the workbench request). Select the transport request in question and choose the Import Request button. After the import has finished, check the deployment log.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
During the import, the transport control program tp triggers the import dispatcher RDDIMPDP that in turn triggers the job RDDEPLOY on the CTS system. This job opens a connection to the CTS DeployProxy. Keep this connection open during the complete deployment process. The CTS DeployProxy finally calls the import tool on the AS Java side (for example, Deploy Controller). As a result, the transport request is now listed in the import queue of the follow-up SAP system (according to the definition of the transport landscape in transaction s t m s , Transport Routes area).
Hint: If your import queue is not automatically refreshed, choose the Refresh button.
O
Note: For assigning SAP system-specific rights for non-ABAP SAP systems for predefined roles as templates, note the following: •
You may use the predefined role SAP_CTS_PLUS_ORG_TEMPLATE as a template to create a new role restricting permissions to create transport requests to certain SAP systems. It contains the authorization object S_SYS_RWBO (SAP systemspecific authorization Object for WBO proxy functions).
•
You may use the predefined role SAP_CTS_PLUS_TRANSPRT_TEMPLATE as a template to create a new role restricting permissions to import transport requests into certain systems. It contains the authorization object S_CTS_SADM (SAP system-specific administration (transport)).
Examples of Transports from Other SAP Systems The usage type Development Infrastructure (Dl) is also referred to as SAP NetWeaver Development Infrastructure (NWDI). It provides an infrastructure for developing Java based applications on the SAP NetWeaver platform and is responsible for versioning, build, and life cycle management of these applications. SAP NWDI takes care of all parts of the development process in a project-specific way. Note the following components of this process: •
Central source file management in the Design Time Repository (DTR) - a file storage in a database with check-out or check-in mechanisms that allows a versioning of source files.
•
Central build and archive management in the Component Build Service (CBS) - gives developers access to the latest archive versions in a central database storage and a central build triggered by the developer.•
•
Central landscape and transport management in the Change Management Services (CM Services) and the enhanced Change and Transport System - provides the central administration of the Java development landscape. The functions of the CM Services are closely interlinked with the DTR, the CBS, and the System Landscape Directory (SLD), which contains a description of your SAP system landscape.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
All the development processes in SAP NWDI are based on SAP's component model, which enhances the public and private concept of Java by metadata regarding the use of objects without implying any changes directly to the development objects. Therefore, a Java interface remains an interface and a public class remains a public class. By clearly defining visibility of objects and dependencies between objects, the component model helps you structure applications into reusable components. The figure Overview of SAP NetWeaver Development Infrastructure and Integration into the Enhanced CTS shows the integration of SAP NetWeaver Development Infrastructure with the enhanced Change and Transport System. Central Infrastructure
Local installation on Developer's PC
Runtime Systems
CTS System
AS Java
Change and Transport Syste
SAP NetWeaver
/
:
SAP NWDI System
m £ 0) s 8 £ E a>) (0 £ . O c
Component Build Service (CBS) Design Time Repository (DTR)
Component model
—
Java Runtime Environment 1Q. OE for O 2 E SAP Systems (DEV, QAS etc.)
CD
C
SLD Local build tool
Optional: local AS Java
Name Server System Landscape Directory (SLD)
Figure 119: Overview of SAP NetWeaver Development Infrastructure and Integration into the Enhanced CTS
One important feature of SAP NWDI is the ability to develop and build software, which belongs to different releases and SAP support package stacks. To do this step, you require only a single SAP NWDI system since the Component Build Service (CBS) creates the software in accordance with the release and SAP support package stack. SAP NetWeaver Developer Studio is SAP's own environment for developing multilevel Java-based applications. The development environment is based on the open source product Eclipse, whose open plug-in architecture provides a suitable platform that can be enhanced with special functions. On the side of the central infrastructure, there are the services shown in the Overview of SAP NetWeaver Development Infrastructure and Integration into the Enhanced CTS figure. They are the Design Time Repository, Component Build Service, and the name server as part of the System Landscape Directory. Developers use SAP NetWeaver Developer Studio to initiate the transfer of local development work to the central development system. SAP NetWeaver Developer Studio uses CBS and CM Services to start the deployment into the central development system. The import into all the following SAP systems is controlled exclusively through the Change and Transport System (CTS), and it is the administrator who starts the imports through transaction STMS.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Figure 120: Releasing Transport Requests in SAP NetWeaver Developer Studio
Before you can transport objects from SAP NWDI, there must exist a transport request type of Workbench request. This transport request can be created in the following two different ways: •
You can create a transport request in transaction SEO 9 on the AS ABAP part of the development system. In this case the transport request is called K9 where denotes the SID of the development system. This step can be used for SAP systems based on AS ABAP + Java.
•
As of SAP NetWeaver 7.0 SP Stack 14, a transport request can be generated and released automatically from SAP NetWeaver Developer Studio. Then they are handed over to CTS. This step can also be used for SAP systems based on AS Java only. As a prerequisite, set the following tp parameters for the source system on the transport domain controller system (transaction STMS): -
WBO_GET_REQ_STRA TEGY = smart or create
-
WBO_REL_REQ_STRA TEGY = AUTO
These two parameters allow the automatic creation and automatic release of a transport request.
Hint: As of enhancement package 2 for SAP NetWeaver 7.0, the value create for the tp parameter WBO_GET_REQ_STRATEGY has been introduced. When you choose this value, you receive a new transport request without verifying that a preselected request already exists. You can also select it as the default request. This step can be used in combination with WBO_REL_ REQ_STRATEGY set to auto .If auto is selected, developers don't need additional information about transports. In this case, a transport request is created automatically when exporting and is released afterwards.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
After releasing the transport request, this transport request appears in the import queue of the subsequent SAP system. It can be imported to the subsequent SAP system with transaction STMS for ABAP transport requests. To configure the SAP NWDI system for integration with the CTS system, do the following: 1. Maintain connection data to the communication system and the SID of the corresponding Java development system in the SAP NetWeaver Administrator (Configuration area). 2. For Destination Type, enter RFC. 3. For Destination Name, enter sap.com/com.sap.tc.di.CTSserver. 4. For the Connection and Transport Security Settings, enter the communication system of the Java development system in the TMS system landscape. 5. For Logon Data, enter Current User (Assertion Ticket) for authentication to the connection to your CTS system.
6. Additionally for the Logon field, we recommend using Single Sign-On. Otherwise, choose Technical User, your preferred language, a client, user, and password. Note, when you enter the client, use tp parameter NON_ABAP_WBO_CLIENT on the CTS system. 7. Keep default settings listed for Repository Connection and Pool Settings (Specific Settings). 8. Save your work.
Hint: This procedure also applies for the configuration of SAP Enterprise Portal systems for the use with the enhanced capabilities of CTS.
Usage Type EP for Transport for SAP Systems
As of some SP Stack for SAP NetWeaver 7.0 (for the SAP system based on usage type EP) a close coupling between the communication system and the SAP Enterprise Portal system is available. Close coupling means that a transport request can be created directly from the Package Export Editor (to enter this tool, switch to area System Administration —► Transport —*• Transport Packages —► Export). In addition objects (for example, EPA files that contain iViews) can be attached directly to this transport request within the Package Export Editor. For SAP Enterprise Portal systems that are based on SAP Web AS 6.40 or SAP NetWeaver 7.0 with SP Stack 12 or lower, you can only configure a loose coupling between the SAP Enterprise Portal system and the TDC system. Loose coupling means that transport requests must be created manually. In addition, non-ABAP objects must be exported to the file system level first before they can be attached to the transport request. For close coupling, the following (optional) tp parameters can be set for the source system on the transport domain controller (transaction s t m s ).The following two parameters allow the automatic creation and automatic release of a transport request:• •
WBO_GET_REQ_STRA TEGY = smart or create
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
WBO_REL_REQ_STRATEGY = AUTO
Consider the following close coupling scenario: With close coupling, it is possible to create and release transport requests automatically and directly from the Package Export Editor in the development SAP Enterprise Portal system. In this scenario, create an object that can be transported within the SAP Enterprise Portal system (transport package). Then you include your changes to the SAP Enterprise Portal objects in question in this transport package. In this case, select the Transport Method “CTS” . If you press Start Export the objects that are included in the transport package will be attached to a transport request. This transport request either must exist as Preselected Request (tp parameter WBO_GET_REQ_STRATEGY set to tagged )or is created automatically (tp parameter WBO_GET_REQ_STRATEGY set to smart or
CREATE). The release of this transport request can then be done either manually using the Transport Organizer Web Ul (tp parameter WBO_REL_REQ_STRATEGY set to manual )or automatically (tp parameter WBO_REL_REQ_STRATEGY set to auto ).
To import the transport request into a subsequent SAP system, you can use transaction STMS_QUEUES on the TDC system. Usage Type PI for Transport for SAP Systems
Since SAP Process Integration system contains both an AS ABAP and an AS Java part. You can use transaction SEO 9 (of the AS ABAP part) to create and release transport requests and use transaction STMS to import the transport requests into subsequent SAP systems. SAP Process Integration (PI) systems can play the role of the CTS system to transport non-ABAP as well (as they are based on AS ABAP + Java). As of SP Stack 13 of SAP NetWeaver 7.0 for the CTS system it is possible to include TPZ files directly from the SAP Process Integration application itself. In this case you do not need to include the non-ABAP object manually in transaction SEO 9. For a prerequisite, set the following tp parameters on the Transport Domain
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
Controller (in the System Overview section) for the SAP Process Integration development system (double-click the SAP system in question and switch to the Transport Tool tab): •
WBO_GET_REQ_STRA TEGY = smart or create
•
WBO_REL_REQ_STRA TEGY = AUTO
After the import into a subsequent SAP system, you can check the status of your SAP Process Integration transports in the receiver SAP system by using the Integration Builder for the Integration Repository or the Integration Directory. For this step, choose Tools —>Find Transports, define your search criteria, and choose Search. To access the details of the transport (Attributes and Transported Objects tab pages), double-click the transport line.
Hint: You may need to activate the changes manually in the Integration Directory of the subsequent SAP systems.
Note: You will find the objects for the service user that you have created in the SAP Process Integration system before (for example, user NWDI_CTSADM). Assign this user to the SAP_XI_CMS_SERV_USERS role.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 5 Exercise 12 Transport Non-ABAP Objects with Enhanced CTS
Business Example
Your company uses the Change and Transport System (CTS) to perform transports in transport landscapes based on SAP systems with AS ABAP. In addition, your company is performing some SAP NetWeaver Portal development. As a member of the transport administration team, you want to know how to transport changes for SAP systems based on AS Java with the help of the CTS. For these exercises, use the following details: Data
Data Value
System
The SAP Solution Manager system p s m and the Enterprise Portal Java runtime systems dep ,
QEP, PEP Client
Client 100 in the SAP Solution Manager sys tem, no client for SAP NetWeaver Portal sys tems dep , QEP, PEP
User ID
-##, this user should exist in all necessary systems (where # # is your user number)
Password
As specified by the instructor in the eCATT
Check tp Parameter Check the tp settings concerning the creation and the release of transport requests for the development portal.
1. Log on to system psm ,which is the CTS system for your SAP NetWeaver Portal transport landscape. Check your settings for the following tp parameters: w b o _ G E T _ r e q _ s t r a t e g y and (if maintained) w b o _ r e l _ r e q _ s t r a t e g y of your development portal system DEP. Log on with the following details: Data
Data Value
User ID
-## (Replace # # with your group number.)
CTS System
PSM
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Create and Release a Transport Request On the SAP Solution Manager system (CTS system), create a transport request for the portal development system. Assign your user to this transport request. Specify the transport request to be the preselected request. Attach a non-ABAP object to this transport request and release the transport request.
1. Log on to the CTS system used in your training class for your SAP NetWeaver Portal transport landscape. Start the Transport Organizer Web Ul for the portal development system. Use the credentials, which are provided by your instructor. 2. Create a transport request for the portal development system. Make sure that this transport request is the preselected request for your user. On the Create a transport request dialog box, enter the following details: Field
Field Value
Short Description
Enter a meaningful description
Owner
-##, is the Owner of this trans port request
Project
Transport Request Group ##, where # # rep resents your group number
Preselected Request checkbox
Selected
3. Attach a non-ABAP object to this transport request. Your instructor will provide you with nonABAP object details. Then, release the transport request. Field
Field Value
Location of files
Select the Server radio button
File
Browse the value help to attach the nonABAP object, which your instructor has specified to this transport request
Application
J2EE
You have created a transport request, attached a non-ABAP object to it, and released this transport request. Import Transport Requests into the Quality Assurance System Import the transport request assigned to you into the quality assurance portal for your SAP NetWeaver Portal system landscape and check the import logs after successful execution. 1. Check that the transport request that you created in the previous task, which now appears in the import queue of the quality assurance portal. 2. Start the import of your transport request into the quality assurance portal. 3. After the import executes successfully, check the import log for verification of import into the quality assurance portal.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Test the Transport Request in the Quality Assurance System (Optional) Test your application in the quality assurance portal system.
1. Open a browser and access the application, which you have transported into the quality assurance portal. Substitute your information for the first three details: Data
Data Value
##
Replace with your group number
twdfxxxx
Use host name from transaction CTS system
$$
Use instance number from transaction on the CTS system
URL
h t t p : / / t w d f x x x x . w d f . s a p . c o r p :5 $
stm s
on the
stm s
$ 0 0 /w e b d y n p r o / d is p a tc h e r /c o m p a n y . c o m /m a th ~ c a lc ~ g r o u p # # ~ w d / C a lc A p p # # ? S A P te s t!d = 0
Import the Transport Request into the Production System (Optional) Import the transport request assigned to you into the production portal for your SAP NetWeaver Portal system landscape and check the import logs after successful execution.
1. Check that the system added your transport request to the import queue of the production portal system. 2. Start the import of your transport request into the production portal. 3. After the import executes successfully, check the import log for the import into the production system. You have successfully imported a transport request into the quality assurance system of your SAP NetWeaver Portal transport landscape where you may have tested it. In addition, you may have imported the transport request into the production system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
Unit 5 Solution 12 Transport Non-ABAP Objects with Enhanced CTS
Business Example
Your company uses the Change and Transport System (CTS) to perform transports in transport landscapes based on SAP systems with AS ABAP. In addition, your company is performing some SAP NetWeaver Portal development. As a member of the transport administration team, you want to know how to transport changes for SAP systems based on AS Java with the help of the CTS. For these exercises, use the following details: Data
Data Value
System
The SAP Solution Manager system p s m and the Enterprise Portal Java runtime systems dep ,
QEP, PEP Client
Client 100 in the SAP Solution Manager sys tem, no client for SAP NetWeaver Portal sys tems dep , QEP, PEP
User ID
-##, this user should exist in all necessary systems (where # # is your user number)
Password
As specified by the instructor in the eCATT
Check tp Parameter Check the tp settings concerning the creation and the release of transport requests for the development portal.
1. Log on to system psm ,which is the CTS system for your SAP NetWeaver Portal transport landscape. Check your settings for the following tp parameters: w b o _ G E T _ r e q _ s t r a t e g y and (if maintained) w b o _ r e l _ r e q _ s t r a t e g y of your development portal system DEP. Log on with the following details: Data
Data Value
User ID
-## (Replace # # with your group number.)
CTS System
PSM
a) Enter
stm s
in the Command field in the top left of the screen.
b) In the Transport Management System screen, choose Overview —*• Systems. c) Double-click the development portal system system ID: dep . d) Choose the Transport Tool tab. e) The tp parameter w b o _ G E T _ r e q _ s t r a t e g y specifies when the system creates a transport request for non-ABAP objects:
. If the value for this parameter is smart ,the system creates a transport request (if not already available) and identifies it as the preselected request.
. If the value for this parameter is tagged,create a transport request manually in the Transport Organizer Web Ul and identify it as a preselected request. f) The tp parameter w b o _ r e l _ r e q _ s t r a t e g y specifies when the system releases a transport request for non-ABAP objects:
. If the value for this parameter is auto ,the system releases a transport request automatically as soon as the system or user adds an object to the request in an SAP NetWeaver Portal system or an SAP NetWeaver PI system. .
If the value for this parameter is manual ,release the transport request manually. If the system does not maintain the parameter w b o _ r e l _ r e q _ s t r a t e g y in this list, the default value MANUAL applies.
Create and Release a Transport Request On the SAP Solution Manager system (CTS system), create a transport request for the portal development system. Assign your user to this transport request. Specify the transport request to be the preselected request. Attach a non-ABAP object to this transport request and release the transport request.
1. Log on to the CTS system used in your training class for your SAP NetWeaver Portal transport landscape. Start the Transport Organizer Web Ul for the portal development system. Use the credentials, which are provided by your instructor. a) Log on to the CTS system used in your training class for your SAP NetWeaver Portal transport landscape. b) Enter s t m s in the Command field in the top left of the screen. c) In the Transport Management System screen, choose Transport Organizer Web Ul.. d) In the System dialog box, enter the portal development system in the System field. For example, choose system dep from the Help or choose F4. e) Choose Continue. f) Enter your credentials for the CTS system, if asked. 2. Create a transport request for the portal development system. Make sure that this transport request is the preselected request for your user. On the Create a transport request dialog box, enter the following details:
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Field
Field Value
Short Description
Enter a meaningful description
Owner
-##, is the Owner of this trans port request
Project
Transport Request Group ##, where # # rep resents your group number
Preselected Request checkbox
Selected
a) On the Transport Organizer Web Ul screen, choose Create Request. b) On the Create a transport request dialog box, enter the details provided in step 2. c) Choose Create to create a new transport request. 3. Attach a non-ABAP object to this transport request. Your instructor will provide you with nonABAP object details. Then, release the transport request. Field
Field Value
Location of files
Select the Server radio button
File
Browse the value help to attach the nonABAP object, which your instructor has specified to this transport request
Application
J2EE
a) On the Transport Organizer Web Ul screen, choose the Object List tab. b) Choose Attach (you may need to switch to the change mode for this step). c) On the Attach file object to request screen, enter the details provided in step 3. d) Choose OK. e) In the Transport Organizer Web Ul screen, choose Release to release the transport request. f) In the Confirmation dialog box, choose OK to confirm your release. g) Close the browser window of the Transport Organizer Web Ul. You have created a transport request, attached a non-ABAP object to it, and released this transport request. Import Transport Requests into the Quality Assurance System Import the transport request assigned to you into the quality assurance portal for your SAP NetWeaver Portal system landscape and check the import logs after successful execution. 1. Check that the transport request that you created in the previous task, which now appears in the import queue of the quality assurance portal.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
a) Log on to the CTS system. b) Enter
stm s
in the Command field in the top left of the screen.
c) Choose Overview —> Imports. d) On the Import Overview screen, double-click the line for the quality assurance portal. For example, q e p . e) If you cannot find your transport request, choose Refresh. 2. Start the import of your transport request into the quality assurance portal. a) On the Import Queue window, select the line with your transport request and choose Import Request. b) On the Import Transport Request screen, choose the Options tab. c) Deselect the Leave Transport Request in Queue for Later Import option. d) Choose Continue. e) In the Start Import dialog box respond Yes to start the import. It may take some time. 3. After the import executes successfully, check the import log for verification of import into the quality assurance portal. a) After a successful import in the Import Queue screen, choose Goto —*■ Import History. b) Select the line with your transport request. c) Choose Logs. d) On the Overview of Transport Logs window, choose Log for the deployment step. e) Expand the deployment log by choosing Expand. f) Choose Back until the Import Overview screen displays. Test the Transport Request in the Quality Assurance System (Optional) Test your application in the quality assurance portal system.
1. Open a browser and access the application, which you have transported into the quality assurance portal. Substitute your information for the first three details: Data
Data Value
##
Replace with your group number
twdfxxxx
Use host name from transaction CTS system
$$
Use instance number from transaction on the CTS system
stm s
on the
stm s
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Data
Data Value
URL
http://twdfxxxx.wdf.sap.corp:5$ $00/webdynpro/dispatcher/compa ny .com/math~calc~group##~wd/ CalcApp##?SAPtest!d=0
a) Open a browser and enter the following URL provided in step 1: http: // twdfxxxx.wdf.sap.corp:5$$00/webdynpro/dispatcher/company.com/ math~calc~group##~wd/CalcApp##?SAPtestId=0. b) Substitute your information for the details provided in step 1.
Note: You will only see an error if the application does not import successfully.
Import the Transport Request into the Production System (Optional)
Import the transport request assigned to you into the production portal for your SAP NetWeaver Portal system landscape and check the import logs after successful execution. 1. Check that the system added your transport request to the import queue of the production portal system. a) Log on to the CTS. b) Enter s t m s in the Command field in the top left of the screen. c) In the Transport Management System screen, choose Overview —> Imports. d) In the Import Overview screen, double-click the production portal system. e) If you cannot find your transport request here, choose Refresh. 2. Start the import of your transport request into the production portal. a) In the Import Queue window, select your transport request. b) Choose Import Request. c) In the Import Transport Request dialog box, choose the Options tab. d) Deselect the Leave Transport Request in Queue for Later Import option. e) Choose Continue. f) In the Confirmation dialog box select Yes to start the import. It may take some time. 3. After the import executes successfully, check the import log for the import into the production system. a) After a successful import, choose Goto —*• Import History.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
b) Select the line with your transport request. c) Choose Logs. d) On the resulting window, choose Log for the deployment step. e) Expand the deployment log by choosing Expand. f) Choose Back until the Import Overview screen displays. You have successfully imported a transport request into the quality assurance system of your SAP NetWeaver Portal transport landscape where you may have tested it. In addition, you may have imported the transport request into the production system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Related In fo rm a tio n : T ra n s p o rt o f Non-ABAP O bjects There is additional information for the transport of non-ABAP-objects with the help of the Change and Transport Systems in the online documentation of SAP NetWeaver 7.31. Choose Application Help —> Function-Oriented View —> Solution Life Cycle Management —> Software Logistics —> Change and Transport System —*• Change and Transport System - Overview (BC-CTS) —> Transporting Non-ABAP Objects in Change and Transport System. The following SAP Note may be helpful: SAP Note 1003674 - Enhancement for non-ABAP systems in CTS is a composite note that provides additional information about the enhanced CTS. Articles in SAP Community Network (SCN) appear regarding the enhanced functionality of the CTS. These are available on SAP Community Network, Quick Link /it-m anagem ent/alm / software-logistics (htto://scn.saD.com/communitv/it-manasement/alm/software-losistics). From this URL, you may follow the link to the Key Topic Change and Transport System {h ttp :// sen. sap. com/docs/DOC-7643).
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
LESSON SUMMARY You should now be able to: •
Use enhanced CTS to transport non-ABAP objects
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 5
Learning Assessment
1. Assume that you want to transport non-ABAP objects with the help of the ABAP Change and Transport System. Which statements are correct? Choose the correct answers. | A Create the RFC destination CTSDEPLOY from the ABAP part of the CTS system to the CTS Deploy Web Service. B Activate the Transport Domain Controller using the CTS Deploy Web Service. | C Define the non-ABAP SAP systems in transaction STMS and maintain the tp parameters for these SAP systems correctly. D Define transport routes between the non-ABAP SAP systems. E The CTS Deploy Web Service must be configured on every non-ABAP SAP system that is defined in transaction s t m s . 2. Which statements concerning the transport of the non-ABAP objects in ABAP Change and Transport System (CTS) are correct? Choose the correct answers. | A Use customizing requests to transport non-ABAP objects. B Use workbench requests to transport non-ABAP objects. | C Transport requests for non-ABAP objects can be created using the CTS_BROWSER Web Dynpro application (Transport Organizer Web Ul). D Transport Requests for non-ABAP objects can be created using transaction SE09 on the AS ABAP part of an SAP system based on AS ABAP + Java.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Learning Assessment - Answers
1. Assume that you want to transport non-ABAP objects with the help of the ABAP Change and Transport System. Which statements are correct? Choose the correct answers. |~xj A Create the RFC destination CTSDEPLOY from the ABAP part of the CTS system to the CTS Deploy Web Service. B Activate the Transport Domain Controller using the CTS Deploy Web Service. |~xj C Define the non-ABAP SAP systems in transaction parameters for these SAP systems correctly.
STMS
and maintain the tp
|~xj D Define transport routes between the non-ABAP SAP systems. E The CTS Deploy Web Service must be configured on every non-ABAP SAP system that is defined in transaction s t m s .
2. Which statements concerning the transport of the non-ABAP objects in ABAP Change and Transport System (CTS) are correct? Choose the correct answers. | A Use customizing requests to transport non-ABAP objects. |~xj B Use workbench requests to transport non-ABAP objects. [x ] C Transport requests for non-ABAP objects can be created using the CTS_BROWSER Web Dynpro application (Transport Organizer Web Ul). [x ] D Transport Requests for non-ABAP objects can be created using transaction SE09 on the AS ABAP part of an SAP system based on AS ABAP + Java.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
UNIT 6
Client Tools
Lesson 1
Describing Client Copy and Client Transport Tools
305
Lesson 2
Performing Client Copies Exercise 13: Perform a LocalClient Copy
309 311
Lesson 3
Managing a Client Transport
321
Lesson 4
Deleting Client Copies
324
Lesson 5
Monitoring Client Copies
326
Lesson 6
Performing Client Compare and Adjustment Exercise 14: Perform a Client Compare and Adjustment
330 335
UNIT OBJECTIVES •
Summarize client copy and client transport tools
•
Perform a local client copy
•
Perform a remote client copy
•
Perform a client transport
•
Delete a client
•
Analyze client copy activities
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
Perform a client compare
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Describing Client Copy and Client Transport Tools
LESSON OVERVIEW
This lesson describes the client copy and client transport tools and explains how to perform client copy testing. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Summarize client copy and client transport tools
Client Tools and Transport Tools Client copy and transport tools are available.
Client Application data
Client dependent customizing Figure 122: Client Data Overview
Characteristics of Client Copy and Client Transport Tools
Observe the following about client copy and client transport tools: Client copy and client transport tools are designed to replace the client data of one client with data from another client. Client copy and client transport tools are not designed to combine the data of different clients. Classifications of Client Data
Client data can be any of the following: For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Client-specific customizing data User master data Application data as defined by the data table's delivery class
O
Hint: Application data can only be copied with the corresponding customizing data.
Profiles define the tables to be copied through the delivery class of the table. Special data such as user master data can be selected by specifying criteria. These table delivery classes are explained in more detail later. Local client copy
Application data Client dependent customizing
-2
Applicat ion data
Client dependent 3 E customizing
Cross client customizing
R e m o te clien t
ra
E
3
™
-
co p y
ra
T3
■
(o p tio n a l)
Repository Source system
Application data Client dependent customizing
2 fk. Q) 3
E
Cross client customizing Repository
Client transport (Export)
Target system
Transport directory
(Import with TMS) Figure 123: Client Copy and Client Transport
Components of Client Copy
The client copy tools can copy the following components or data of the source client into the target client: User master data - User master data is only deleted in the target system when a profile with user master data is copied. Authorization profiles and roles belong to customizing and are therefore always copied with the customizing. Copying users without authorization profiles is problematic. The copy profile SAP_USER contains authorization profiles and roles. Customizing - All profiles except SAPJJSER contain customizing. Customizing data is typically in tables with delivery classes C,G,Et and S Cross-client customizing - Choose a profile with this data type when you want to create a test system analogous to the production system, without SAP system copy, for example. Master or transaction (application) data - Select this option when you want to set up a test system from the production client, for example.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Note: Application data depends on customizing data, so they can coexist. Therefore, application data is always deleted from the target client. However, an exception is made for copies with SAPJJSER. Note that application data is typically in tables with delivery class A. If you have maintained a logical system in both source and target clients, and assigned the logical system to the client, then the system automatically does the following. It assigns the logical system names in the target client application data and automatically converts the names after copying the application data (such as, with copy profile SAP_ALL). This information can be applied in transaction BD54. Transport Request Customization Transport requests for customizing are typically created in the development system. They are then released and imported into the quality assurance system. It can be a good idea to perform some pretesting in a separate client of the development system. Do this step before releasing the transport request. Before releasing a customizing transport request, perform a unit test to do the following: •
Test the functionality of the transport request.
•
Verify that the content of the transport request is complete.
Maintaining a separate client for testing allows the following: •
True unit testing
•
Maintenance of test data without the risk of creating customizing-dependent data
Transaction s c c i copies changes from one client to another based on the following: •
A task
•
A transport request
•
A transport request and its tasks
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Transaction S C C 1: Copy based on a transport request
Released or not released
For client specific data only
Cross client customizing Repository
| Figure 124: Testing Customizing Transport Requests
To copy the contents of a transport request from one client to another client, use transaction S C C l from the target client. Enter the source client and the transport request, from which you copy the objects. Only objects of one transport request may be copied at a time. Since copying objects of each transport request individually may be time consuming, use the Include Objects option in transaction S E 0 9 to bundle several transport requests into one transport request. The resulting objects of this larger transport request can then be copied to the target client and, as a result, save time.
Note: Of course, if the transport request contains cross-client objects, these objects are not copied.
LESSON SUMMARY You should now be able to: •
Summarize client copy and client transport tools
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Performing Client Copies
LESSON OVERVIEW
This lesson explains how to perform a local client copy and a remote client copy, and describes client copy profiles. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Perform a local client copy
•
Perform a remote client copy
Local Client Copy A local client copy replicates information between clients within the same SAP system. & ClientCopy Edit Soto Profie System Help
©jj
^41 e@« a
Client Copy ■ Copy a Client ’£jcSchedule as Background Job
iQ Start Immedately
Target d e n t
110 Test Client
Applicat ion data
fitlCC 1 0
*8
Selected Profie
SAP_ALL
Descrpton
A l dent-Specfic Data w /o Change Documents
Source dent
100 Develop, t Cust.
Source dent User Hesters
100 Develop, c Cust.
Client dependent customizing
to
>0 E
c> i s
> (0
3 *D
Target Client Applicat ion data
0
Client dependent customizing
O T e st Run
(A CO E <5
JS
« to 3 -o
Source Client
In the target client perform a L o c a l C lie n t C o p y
Application data
2 |
Client dependent customizing
3
Q) > RJ *0
SAP Client 000 Figure 125: Local Client Copy
Initiate both local and remote client copy from the target client using the following steps: 1. To create an entry for the target client in the client maintenance table, choose transaction SCC4.
2. Log on to the target client as s a p * with the initial password p a s s .
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Note: The user name SAP* with the password pass is only active if the profile parameter login/no_automatic_user_sapstar does not have the value 1
3. Perform the client copy using transaction
sccl.
4. Select the data to be copied with a profile. 5. Assign the source client for customizing data, application data, and user master records. 6. Begin the client copy. Since copying is a lengthy process, use background processing.
A
Caution: To ensure data consistency, you may not log on to the target client during a client copy. We recommend that you do not work in the source client during a client copy.
Note: We deliver the software with standard client 000. You may not work in client 000. But you may use client 001 as your production, if it exists. Client 001 is a copy of client 000. However, if no client 001 exists, we recommend that you begin SAP system implementation by creating a new client as a copy of client 000. You can improve the performance of the client copy, for example, by excluding tables or packages, with Edit —>Expert Settings. You can exclude tables from the client copy since they are not relevant for the target client, in the Tables tab. For further information about excluding tables from the client copy, choose the Help button in the expert settings. For more information about expert settings in the client copy, see SAP Note 446485.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Perform a Local Client Copy
Business Example
You need several clients during an SAP ECC application implementation. As a system administrator, you manage all the clients across your SAP system landscape by creating and setting up the clients. Create a Client
To start, create a new client. 1. Log on with the following details and create a new client with the details in the second table: Data
Data Value
System
DCC
Client
100
In the New Entries: Details of Added Entries screen, enter the following details: Field
Field Value
Client
2## and client description (where # # is your user number).
City
City where users are located
Client role
Test
Create a Local Client Copy
Log on to the DCC system to your new client and start a local client copy with profile the background.
sap
user
in
1. Log on to system DCC. Data
Data Value
System
DCC
Client
2##
User (Selected Profile)
SAP*
Password
pass
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
3
Note: To avoid having two client copies running at the same time in the SAP system, do this exercise in a distributed way based on direction from your instructor.
2. Call transaction SCCL, select the profile SAPJJSER and select client 100. 3. Schedule your local client copy as a background job. 4. Use transaction SCC3 to monitor the progress of your client copy. Note how many tables are copied. Review the logs generated by the process to determine if there were any errors in the copy process.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 6 Solution 13 Perform a Local Client Copy
Business Example
You need several clients during an SAP ECC application implementation. As a system administrator, you manage all the clients across your SAP system landscape by creating and setting up the clients. Create a Client
To start, create a new client. 1. Log on with the following details and create a new client with the details in the second table: Data
Data Value
System
DCC
Client
100
In the New Entries: Details of Added Entries screen, enter the following details: Field
Field Value
Client
2## and client description (where # # is your user number).
City
City where users are located
Client role
Test
a) Enter /NSCC4 in the Command field at the top left of the screen. b) In the Display View Clients: Overview screen, go to change mode by choosing Table View —> Display —> Change. c) In the Confirmation dialog box, choose Continue to indicate that the table is cross-client. d) Choose New Entries to create a new client. e) On the New Entries: Details of Added Entries screen, enter the details listed in the table above. f) Choose Table View —► Save. Create a Local Client Copy
Log on to the DCC system to your new client and start a local client copy with profile the background.
sap
user
in
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
1. Log on to system DCC. Data
Data Value
System
DCC
Client
2##
User (Selected Profile)
SAP*
Password
pass
Note: To avoid having two client copies running at the same time in the SAP system, do this exercise in a distributed way based on direction from your instructor. a) Log on to DCC using the details provided in the table above. 2. Call transaction SCCL, select the profile SAPJJSER and select client 100. a) Enter s c c l in the Command field in the top left of the screen. b) For the Selected Profile field, choose
sap_ u s e r .
c) For the Source Client field, select client 100. 3. Schedule your local client copy as a background job. a) Choose Schedule as Background Job. b) On the Schedule Client Copy in Background screen, choose Schedule Job. c) On the Start Time screen, enter the start time given by your instructor in the Scheduled start Time field and choose Save. d) In the Verification window, verify your field selections for Target Client (2##), Profile name (SAPJJSER), and Source (Client 100), then choose Continue. e) In the Information dialog box, choose Continue to confirm. Once you schedule the background job, you can monitor the process using SCC3. 4. Use transaction SCC3 to monitor the progress of your client copy. Note how many tables are copied. Review the logs generated by the process to determine if there were any errors in the copy process. a) Execute transaction /NSCC3. If you do not see your Client Copy and its status in the displayed table, choose All Clients. b) To view the current status of your job, choose Refresh. c) For further information double click on the line item for your Client Copy to access the Client Copy Log Analysis. Note the number of tables copied in the process. It should be 1
0
2
.
d) Choose Log File to review the log for your Client Copy.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Remote Client Copy
A remote client copy allows you to copy data between clients in different SAP systems. You can use a remote client copy to copy client-specific and cross-client customizing data between SAP systems, for example. A remote client copy proceeds in the same way as a local copy, but sends the data through a Remote Function Call (RFC) connection to the target client. Limitations of Remote Client Copy
A remote client copy is easy to use and does not require file system space. The limitations of a remote client copy are as follows: A remote client copy does not create a file at file system level, so there is no hard copy of the client to be copied. Therefore, the same, identical client copy cannot be duplicated at a later time. Cross-client customizing objects can be copied during a remote client copy, depending on the client copy profile. Identical structure. To be able to copy all data during the client copy, the structures of all copied tables in both SAP systems must be identical. During remote client copy, an automatic repository consistency check is performed. If inconsistencies are detected, the client copy is terminated and an error message is displayed. You can also perform the consistency check by choosing the RFC System Comparison button. If you experience problems copying from another SAP system, see SAP Note 557132. For more information about remote client copies, see also SAP Note 47502.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
QAS, SM59 Request for copying
QAS, RZ12
DEV
RFC group for parallel processing (define which instances and how many work processes should be used for copying)
ion data Client dependent customizing
«
to
Copy
3 "O
QAS
Applicati on data Client dependent customizing
Cross client customizing
Cross client customizing
Repository
Repository
0 ) u> (A 2
3 E
| Figure 127: Client Copy Using Parallel Processing
The client copy function can be used with multiple parallel processes, which speeds up the copying process. Consider other factors that optimize a client copy include the network performance and the database performance. The client copy processes are generated at runtime. They are parallel RFC processes, managed by server groups. Specify the maximum number of processes you want to use in the client copy program. Parallel processing can only be used when performing a local or remote client copy, it cannot be used for client transports. To specify the maximum number of client copy processes, use transaction s c c l for a local copy or transaction SCC9 for a remote copy and then Goto —>Parallel Processes. To define a RFC server group, use transaction SM59, RFC —>RFC Groups. For RFC server groups, the limitations on the SAP system parameters are explained in SAP Note 99284. During the execution of a client copy using parallel processing, each parallel process checks the other to see if it is still running. If a process has failed, it will be restarted automatically.
Hint: In an existing client, application data, client-specific customizing, cross-client customizing, and the repository rely on each other. The structures of all copied tables in both the source and target system must be identical. During remote client copy, an automatic repository consistency check is performed.
Client Copy Profiles SAP delivers all necessary profiles to be used by a client copy or a client transport. Roles (the former activity groups) are also copied with the user master records using the SAPJJSER profile. The table selected in the figure SAP Standard Client Copy Profiles depends on the type of client copy. This selection is for a remote client copy.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
For all typical client copy scenarios, SAP provides profiles affecting various kinds of data in the SAP system and using various copy functions (as shown in the figure SAP Standard Client Copy Profiles). Depending on the copy option you have selected, the client copy tool determines the purpose of the table in the SAP system when the table is copied. For example, if you selected the Customizing profile and the table belongs to Customizing, then the table is copied to the target client. If the table contains application data, however, the table contents are deleted, not copied. To determine the purpose of a table, the client copy tool uses the delivery class assigned. The client copy tool assumes that all tables belong to customizing except those tables that have classes L, A, and W.
7 Entries found Figure 129: Table Delivery Classes
Affects of Delivery Classes
Delivery classes affect the following: For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
Client copy within an SAP system (client-specific tables only)
•
Client copy between different SAP systems
•
Transports between SAP systems
•
Transports from SAP systems to customer's SAP systems
To understand the effect of table delivery classes during upgrading, transport, or client copy, especially when there are development projects that create new tables, see the SAP Online Documentation and SAP Note 2857. Table delivery classes are assigned to tables as follows: •
Tables containing application data use delivery class A.
•
Tables containing customizing data use different delivery classes, depending on how SAP changes the customizing settings in them.
•
Delivery class C may not contain new entries from SAP.
•
Delivery class G may be changed by SAP.
•
Delivery classes S, E, and W are for tables containing control and SAP system data, such as tables TADIR, VARI, TSTC, and CCCEXIT. W tables are SAP system tables that are filled internally. Their contents are purely technical. W tables are not taken into account by the client copy tool.
•
Delivery class L is for tables for temporary data such as spool data and background processing data, for example, tables TSP* and TBT*. These tables should be empty in the new SAP system and are deleted in the target client.
Use background processing for client copies because, depending on the profile used during a client copy, the client copy may take several hours. The time required for a client copy is much less due to parallel processing. To ensure data consistency in the target client, users, except for SAP* and DDIC, cannot log on to the target client during copying. Similarly, no one should work in the source client during the client copy. When you start a client copy, take into account runtime restrictions and database space. Storage requirements can only be estimated, because space available, is not taken into account. A client without application data needs approximately 500 MB in the database. In most databases, space made free by deleting data is only available after a reorganization. The maximum online runtime (parameter rdisp/max_wprun_time) must be longer than the time required to copy the largest table. A value of at least 2000 sec is recommended. To test whether there is sufficient database space, perform a test client copy, either as a simulation or as a considerably faster resource check. The resulting display shows the database memory requirements (for Oracle, Informix, Max DB, and DB2/6000). See information about how to copy large production clients in SAP Note 48690.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
O
Hint: To estimate the size of a client you can also run program RSTABLESIZE. There, you can distinguish between application and customizing data.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
LESSON SUMMARY You should now be able to: •
Perform a local client copy
•
Perform a remote client copy
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Managing a Client Transport
LESSON OVERVIEW This lesson describes how to perform and manage a client transport. LESSON OBJECTIVES After completing this lesson, you will be able to:
•
Perform a client transport
C lie n t T ra n sp o rt Export processing transaction SCC8 (in background) ISAPscriptl Application data Client dependent . .V customizing
Data files
Command files
RX RT RO
KX KT KO
data
cofiles
~ | <5 2 « ra 3 -a
Cross client customizing Repository
Import Queue: Target System
Source system/client
| Number
i 1 iI 2 !i _ 3
1
Request
Short text
KO Cross-client tables KT KX
Client-specific tables SAPscript texts
1
Figure 130: Client Transport Export Process
A client transport differs from a client copy in that it does not use RFC. Like a client copy, however, a client transport is used to copy data between different clients. A client transport can be used to replace a local or remote client copy. A client transport consists of two steps. First, a client export extracts client data from the source client to files at the operating system level. Then, the data is imported from the operating system files into the target client. Perform a Client Export
To perform a client export, use the following steps: 1. Log on to the source client.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
2. Enter transaction SCC8 (client export). 3. Select the data to be copied using a profile. 4. Indicate the target system to which the client will be copied. Define the target system in TMS as part of the transport domain. 5. Begin the client export. Since copying is a lengthy process, use scheduled background processing. The client export performed in the source system exports the client data asynchronously by requesting the transport program tp at the operating system level. Files Generated by the Export Process
This export process generates up to three data files at the operating system level as expressed by the following files: •
RO< number > contains cross-client data
•
RT< number > contains client-specific data
•
RX< number > contains SAPscript texts
O
Hint: The data export is asynchronous and still runs when transaction SCC8 has already finished. Do not run any other client copy tool before the data export is finished. You can check the status of the export with transaction S E O l. Display the logs for the request KT.
Note: During the client export, no information is available in transaction SCC3 because the export is done with R3trans. The system will say aborted in transaction SCC3 when the client export is running.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
o
Import processing transaction STMS
©
Post-import processing transaction SCC7
Target system/client Figure 131: Client Transport Import Process*•
Depending on the type of data selected through the client transport profile, the client copy command files added to the buffer of the target system are as follows: •
KO - cross-client data
•
KT - client-specific data
•
KX - SAPscript texts
The client export transport requests are not imported when an ‘Import all’ takes place. You can import these requests into the target client using TMS. Choose one of the transport requests of the client transport in the Transport Management System (TMS). The other transport requests from this client transport are then automatically added in the correct order. After the import process has completed, post-import activities are required for object generation steps. After completing the import, log on to the target client. Choose transaction SCC7. To display client transport logs, use the Transport Organizer (transaction S E 0 9 ). During a client transport, a repository consistency check can be performed by choosing the RFC system check button in transaction SCC8. If inconsistencies are detected, a list of the ABAP Dictionary table definitions missing in the target system is generated. This check will help you recognize in advance formal problems that may occur during the import of the source data.
LESSON SUMMARY
You should now be able to: •
Perform a client transport
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Deleting Client Copies
LESSON OVERVIEW
This lesson describes client deletion. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Delete a client
C lie n t D eletion Deleting a client transaction SCC5 &
£Wnt Copy
E dt
© J
go to
System
HiHp
-]
SHK
CO’
D e le te C lie n t D elete r Background
3
Client 110
Client 100
S ta rt Im m e d a te V
Application data Client dependent . . . customizing
"*S
2 |
^ ^ ^ A p p lic a t^ /(A
re
E o> ™ Clien^Jrfpendeht s 2 ^ re cn to customizing ~ 3 -0
O e U te r te n t d e n t t o b« de leted
□
110
■/ D elete e n try fro m TOOO
Cross client customizing
T e st run
& D€V (1) 110
wtwtfl903
WS
Repository
Figure 132: Client Delete
Client Delete Procedure
To delete a client from within an SAP system, do the following: 1. Log on to the client to be deleted. 2. Enter transaction
S C C 5.
3. Start the deletion of the client using background processing. When you delete a client entry from table TOOO with client maintenance, transaction SCC4, you can no longer log on to the client or update it using transport requests. This step, however, does not eliminate the data that belongs to the client. The client-specific data that remains in your SAP system occupies space in the database. Therefore, to eliminate an SAP client entirely, that is, to delete both the client and the client-specific data, use the client delete function, transaction SCC5 Deleting a client entry with client maintenance using transaction SCC4 temporarily allows you to lock the client. This deletion procedure preserves the data for the client, but prevents users from logging on to the client or accessing the data belonging to the client. To restore the client and
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
allow logon, re-create the client entry using client maintenance. The amount of time required for the deletion of a client can be reduced by performing the deletion using parallel processes.
Note: In most databases, free space is only available after a reorganization.
LESSON SUMMARY
You should now be able to: •
Delete a client
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Monitoring Client Copies
LESSON OVERVIEW
This lesson describes how to monitor and troubleshoot client copies, and explains how to analyze client copy logs. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Analyze client copy activities
Client Copy Monitoring and Troubleshooting
Application data
£ |
Client dependent . . V customizing
2
Transport directory logs
<5 ™ « ra -c
_____ I___
Target client
Client copy log analysis Target 100
Applica tion data Client dependent customizing
Runs 5
Last date Status 111111 ok
a> 2 3
T3
Source client Figure 133: Client Copy Logs and Control Information
Monitor Client Copies
To monitor client copies, perform the following: 1. Select a target client. 2. Select run. 3. Monitor copy process. 4. Show control information. 5. Show full table details.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
To display all log files fora completed local or remote client copy, choose transaction SCC3. Select the relevant target client and the relevant copying process. These copy logs provide the following information: •
Table statistics
•
Control information
•
Additional information about each table copied, including the link to the appropriate IMG component
Double-click the highlighted entries for more information. You see a selection list where you can obtain information about the copied tables (that is, the runtime and number of entries copied) and the exit programs from other application components used. If you had tables with copy problems in a local or remote client copy, you can recopy them with the Recopy Errors function. You can display the original log in the file system by choosing File Log. You can also display the export and import logs of the main transport request. To display client transport logs, use the Transport Organizer (transaction S E 0 1 ). Technically speaking, copy log information is located in the view V_CCCFLOW. For example, the view contains the runtime and processing status of a local client copy, the number of previously copied tables, and the name of the table being currently copied. All log files are physically stored in the transport log directory at the operating system level. Log files are named CC., where is the serial client copy number, and is the source system ID. If copying is unexpectedly terminated, the SAP system uses the name of the table being currently copied to restart the copy process.
&
Lq q s
Edit
Goto
& 4--r
L*st
Settngs
S y s te m
--- Jt < ia e © ® a sa ki e o ”
C lie n t C o p y / T r a n s p o r t L o g A n a ly s is til
A l T ra n s p o rt R e q u e s ts
E x p o rts
Client Copy Logs Selection: Compi. Copies T a rg e t d . N u m b er 100 1
L a st R u n D a te L a s t R u n S ta tu s T e x t 0 9 .0 5 .2 0 1 1 S u c c e s s f u l C o m p le te d
110
1
1 4 .0 9 .2 0 1 1
P ro c e s s n g ...
200
1
1 0 .0 8 .2 0 1 1
S u c c e s s f u l C o m p le te d
Figure 134: Client Copy Monitoring and Troubleshooting
Checks for Monitoring and Troubleshooting Remember the following about monitoring and troubleshooting: •
Verify that database resources are sufficient.
•
Monitor a client copy with transaction SCC3.
•
Restart a terminated run, if necessary.
When performing client copy error analysis check the copy log and the SAP system log, which tells you whether database problems are responsible for the client copy error. Correct any database problems before restarting the client copy. For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
When a client copy run terminates abnormally, the restart option is proposed by default. This restart continues the run from the point at which it was terminated. If the original run was recent, as indicated by the status line, choose Restart. Alternatively, to start the run from the beginning, choose Restart —*• New start. If a copy terminates for technical reasons, for example, due to a database shutdown, you can restart the process from the point of termination. If a client copy or client import postprocessing did not finish, the SAP system automatically proposes the restart mode when you enter the transaction. The same parameter settings are used automatically.
Note: When the last step is restarted you cannot continue to copy an incompletely copied table. The table is reinitialized and recopied.
Note: When the restart fails the log displays possible reasons for the error. Before you try to restart the program again, eliminate the error. To avoid the problem of insufficient free space in the database, perform a simulation test run or a resource check. A simulation test run estimates the space required by reading all records to be copied without updating them in the database. A resource check estimates the space required by counting the records to be copied. Client copies ignore tables in the local development class $TMP. If you want to copy these tables, modify the development class in the object directory. When you discover a write error in the target client it is due to insufficient space in the database or simultaneous processing in the target client typically. Check the SAP system log to determine the name of the tablespace. Extend the tablespace and repeat the copy. You do not have to delete it first. Do not work in either the source or target client during the copy. For more information about error analysis with the client copy tool, see SAP Note 22514 and SAP Note 69444. SAP system log messages like Syn. MC maintenance deactivated fully, Buffer TABL/TABLP reset, or Table logging do not indicate an error. These messages document special functions that are used to improve performance and guarantee consistency. If a termination in an exit program (the termination is explained in an ABAP runtime error) occurs, run the log display RSCCPROT to determine the name of the last exit program that caused the termination. This error does not mean that the client copy program crashed. It is an application error. When you discover an unexplained cancellation or error verify it in the following transactions: •
Copy log (transaction SCC3)
•
SAP system log (transaction SM21)
•
Dump analysis (transaction ST22)
•
Job overview (transaction SM37)
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
Possibly spool (transaction S P O l)
LESSON SUMMARY
You should now be able to: •
Analyze client copy activities
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 6 Lesson 6 Performing Client Compare and Adjustment
LESSON OVERVIEW
This lesson explains how to perform a client compare and client adjustment, and describes client maintenance settings. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Perform a client compare
C lie n t C o m p a re
When several SAP systems and clients are being implemented, it may be necessary to compare and adjust customizing settings between different SAP systems and clients. The compare function enables you to compare and adjust the contents of a table or view in two different clients, using RFC connections. Compare Remote client
Applica tion data
Local client
O ((/Z> C
Applica tion data
£ &_ CD
Client dependent customizing
tf> 3
Remote client
co "O
Applica tion data
(0 ■O
Compare (A
(0 Client dependent ustomizing
Client dependent Icustomizing
£
s_ a > (A
Z>
Cross client customizing
Repository
Cross client customizing
Compare
Local SAP system
Repository
Remote SAP system
Figure 135: Client Compare
To use the compare function, from the SAP systems initial screen, choose transaction scuo. Client Compare Function
Use client compare to do the following: Compare a client with a reference client, such as a customer-owned client or the SAP client 000. This step is especially useful after an upgrade or language import, since only client 000 is provided with data from tables belonging to table delivery class C. For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
Compare clients during a rollout scenario. For example, use compare when subsidiaries wish to adjust their customizing with respect to the reference customizing of a master client.
•
Compare cross-client customizing before combining different clients into one SAP system in a roll-in scenario. For example, use compare when subsidiaries wish to receive customizing changes from the reference client, master client of their parent organization.
List of Items Appearing in Transaction SCUO
Transaction SCUO lists the following: •
Objects
•
Differences
•
Table entries
To select the objects to be compared in a client compare, use a project-oriented approach with the IMG to define the objects. Or, select from application components' customizing object lists and transport requests. You can also select the objects manually. To start a client compare, use transaction SCUO in background processing. From the initial screen, select the component and choose Create. In the dialog boxes that appear, make the appropriate entries. Transaction SCUO can be restricted, for example, by client-specific data. Transaction scuo first displays an overview of the tables belonging to views for the selected IMG, application component, or request. Next, the comparison is performed. The SAP system creates a list of differences and indicates whether these differences are encountered in the table structure or in the table content.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
To display the differing table entries, select an object. This step enables you to perform a detailed comparison. The comparison client is typically an external environment, so you must access it through a Remote Function Call (RFC). For information on how to use an RFC, in the selection dialog box for the RFC destination, choose Info. For additional help for client compare, see SAP Note 91096. &
Comparison ©
gdt
goto
T T
*■ ]
Ut*ties(M) <1
0
©
System 0
©
Help Q
B Q
S 8
4
3
C
4
3
S
®
®
Customizing Cross-System Viewer: Change mode
*17 □□Compareon
o'a Applicator! component
Selection type: Manually Logon system: DCV/200/702 Stat. Object Subobject Subobject
acc
V T005 BAS
°a IMG
Envronment
0
Statistics
&
7
■
Filter: active Comparison run: 0000000003 <-> Comparison s y s t e m : DEV/100/702 - Last action: 14.09.2011 Description
V Global Parameters of Countries (Hew Diaensio
Cotcp Entries Entries Entries LooonSvs Only in Changed LoaonSvs Total
ft
241
0
0
Entries Component Only in CompSys. 1
BC-SKV-ADR
Figure 137: Client Compare: Difference List
The results of each comparison run are an overview of existing differences between the logon client and the comparison client. This overview serves as a starting point for subsequent processing of differences. The comparison runs are stored in a work list or difference list. Client Maintenance Tools For each compared object in a comparison run, the objects compared are listed along with a description. The most important information is the status indicators. The Comparison status is set automatically and indicates the existence and details of any differences. The Process status allows you to distinguish between the objects that have already been processed, that is, have been made identical in both clients, and those objects that have not. This kind of processing is also referred to as adjusting the respective object. The processing status is indicated by a traffic light where the different colors indicate the following. Red indicates not processed. Yellow indicates that the objects in both clients are in the process of being made identical. Green indicates the completion of this adjustment process. An explanation of the possible statuses under comparison status and process status can be obtained by choosing the Legend button. For a detailed analysis of a comparison run, choose Comparison.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
&
Comparison
Edit
fioto
Settrgs
•
&
UttdesOJ!1
e e e
Q
System
B
deb
O
O
T
KHS8
O v e rv ie w : C o m p a ris o n
M
44 4
► ►► M
&
^
statstics
view: V T 0 0 5 J B A S - Logon Syatea: DCV/200/702
Lst Settng E3 <-> Coaperlaon Syacem: DCV/100/702
Long naae
□
in W □ p
P«n«M
- Dece: 14.09.2011
Nationality
Nationality (Long)
Oman Fanar.a
Paradise Paradise Island Peru Peru Frenc.Polynesia French Polynesia Pap. New Guinea Papua New Guinea
Peruvian Peruvian French French Pap.New Guinean Papua Hew Guinean
Figure 138: Adjusting Customizing Objects with Transaction SCUO
Transaction SCUO Adjustments
Adjustment of individual objects with transaction SCUO do the following: •
Generate detailed information in worklist.
•
Display a comparison status for each record in worklist.
•
Describe comparison status through Legend button.
You can adjust one object at a time. The objects that can be adjusted are some of the tables and views maintained using transaction SM 30. You can also use the IMG. Other objects can only be compared. To perform an adjustment, from the Comparison screen, choose Edit —>Interact Copy. The Overview Adjustment screen displays. It shows the details about the differences between the two clients, record by record. To the left of each record in this adjustment worklist is the comparison status, which indicates whether each respective entry in the record exists in the comparison client and the logon client. An explanation for the possible statuses appears under the comparison status and process status can be obtained by choosing the Legend button.
Hint: Be careful when adjusting customizing as they might be dependent on other customizing activities. You can easily create inconsistencies when copying customizing from the source client when the dependencies are ignored in the target client.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
C lie n t M a in te n a n c e S e ttin g s
Cs’’ Xable View
&
Edit
f io to
r~
S election < 3 0
Change View N e w E n trie s
©
Utilities ©
©
s
m
e
i
q
~
q
C lients : D etails
[Q
G i &$> [ 3
El
53
C ro s s -O e n t O b je c t C h a n g e s C h a n g e s A lo w e d t o R e p o s ito ry a n d C ro s s -C lie n t C u s to m iz in g
P r o te c tio n : C he n t C o p ie r a n d C o m p a ris o n T o o l P ro te c tio n P ro te c tio n P ro te c tio n P ro te c tio n
le v e l le v e l le v e l le v e l
0: 0: 1: 2:
No No No No
re s tr ic tio n re s tr ic tio n o v e r w r it n g o v e r w r it n g , n o e x te r n a l avarfabrifty
(3
« ►
:::
—
i
« ►
Figure 139: Client Maintenance Settings
Values for Client Copy and Comparison Tool Protection Field
•
Set client option to Protection level 2: No overwriting, no external availability
•
Default value for this field is Protection level 0: No restriction
The Client Maintenance Settings figure illustrates the transaction SCC4 can be used to set up the client protection level. Navigate to Protection: Client Copy and Comparison Tool Protection field. Note that the default value for this field is Protection level 0: No restriction. This field can be set to prevent a client from being overwritten by the client copy or client compare and client adjustment. It can also be set to ensure that sensitive data is not viewable from another client during a client compare. Select a protection level from among one of the following: Protection level 1: No overwriting This protection level ensures that the client cannot be overwritten by the client copy program. Use this setting when customizing is being performed in this client, or when the client contains critical settings or data that cannot be overwritten. Protection level 2: No overwriting and no external availability This protection level also protects the client against overwriting and against read access from another client during a client copy or customizing comparison. Use this setting when the client contains sensitive data. All production clients use this setting. To set the Protection regarding client copy/comparison option, you require full authorization for the Workbench Organizer (authorization S_CTS_ADMIN).
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 6 Exercise 14 Perform a Client Compare and Adjustment
Business Example
In a multiclient SAP system landscape it can be necessary to compare and maintain customizing settings across clients.
Note: Client 2## was created by copying the profile SAP_USER from client 100, so client 2## contains no additional customizing country definition.
Client Comparison
As part of your customizing settings, compare country texts across clients. The T005T table contains country texts and the corresponding maintenance view is V_T005 (Define Countries) or V_T005_BAS (Specify Countries). 1. Compare customizing between the two clients. Compare the customizing in regard to view V_T005 or view V_T005_BAS and use the RFC connection provided by your instructor. Log on with the following details: Data
Data Value
System
DCC
Client
2## (where # # is your user number)
Transaction
SCUO
Client Adjustment
The following exercise adjusts country texts across clients. 1. The customizing of country definition does not exist in the new client 2##. Replicate your country definition to client 2## through the client adjustment. Log on with the following details: Data
Data Value
System
DCC
Client
2## (Replace # # with your user assigned number)
Transaction
SCUO
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Perform a Client Compare and Adjustment
Business Example In a multiclient SAP system landscape it can be necessary to compare and maintain customizing settings across clients.
Note: Client 2## was created by copying the profile SAP_USER from client 100, so client 2## contains no additional customizing country definition.
Client Comparison As part of your customizing settings, compare country texts across clients. The T005T table contains country texts and the corresponding maintenance view is V_T005 (Define Countries) or V_T005_BAS (Specify Countries). 1. Compare customizing between the two clients. Compare the customizing in regard to view V_T005 or view V_T005_BAS and use the RFC connection provided by your instructor. Log on with the following details: Data
Data Value
System
DCC
Client
2##
Transaction
SCUO
(where # # is your user number)
a) Enter scuo in the Command field on the top left of the screen. b) Select the Manual selection radio button and choose Create. c) In the Selection by: Manual Input screen, enter v _ t 0 0 5 _ b a s in the Object name field and choose v (View) in the Typ (Type) field. d) Choose Execute at the bottom. e) On the Selection by: Manual Input screen, enter a description in the Description field and the RFC connection given by your instructor in the R/3 Connection field. f) In the R/3 Connection field, choose 100 or the RFC destination provided by your instructor.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
g) Choose Total comparison. h) On the Customizing Cross-System Viewer screen, select the checkbox to the left of V_T005 or V_T005_BAS. i) Choose Comparison and then choose No in the Restrict selection set dialog box. j) In the Overview: Comparison screen, view the result of the following comparison by looking at the data. Since the compared client 100 contains plenty of country customizing and your client 2## does not contain any country customizing, the comparison shows a large difference. Client Adjustment
The following exercise adjusts country texts across clients. 1. The customizing of country definition does not exist in the new client 2##. Replicate your country definition to client 2# # through the client adjustment. Log on with the following details: Data
Data Value
System
DCC
Client
2## (Replace # # with your user assigned number)
Transaction
SCUO
a) At the Customizing Cross-System Viewer screen, as described in the Client Comparison exercise, you see either V_T005 or V_T005_BAS listed. Select the entry. b) Choose Edit —> Interact. Copy. c) In the Restrict Selection set dialog box, choose No. d) In the Overview: Adjustment screen, mark only the entry you created from the previous exercise and choose Adjust. e) In the Detail View: Adjust screen, choose All (Copy All Entries) . f) Exit the Detail View Adjust screen and return to the previous screen by choosing Back. g) Choose Save to save your adjustment. h) In the Confirmation dialog box, choose Yes. i) Create a customizing request and a transport request, if appropriate. j) Check the result by performing a new client comparison (previous exercise). The country settings you adjusted are identical in both clients, 100 and 2##.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
LESSON SUMMARY You should now be able to: •
Perform a client compare
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 6
Learning Assessment
1. Which of the following statements about client data are true? Choose the correct answers. | A Client data consists of user master data. B Client data consists of client-dependent customizing data. | C Client data consists of application data. D Client data consists of repository objects. 2. To initiate local client copy, log on to the target client using user DDIC and run transaction SCCL. Determine whether this statement is true or false. | True False 3. A remote client copy sends the data through a remote function call (RFC) connection to the target client. Determine whether this statement is true or false. | True False 4. A client transport uses RFC. Determine whether this statement is true or false. | True False
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
5. When you delete a client using transaction SCC4, client data is still preserved but you can no longer log on to the client or access the data belonging to the client. Determine whether this statement is true or false. | True False 6. What kind of information is provided in the SCC3 copy log for a completed local or remote client copy ? Choose the correct answers. | A Table statistics B Space information C Information about each table copied D Control information like status, user and start date & time E Application errors, if any exist 7. In a client comparison run, the process status allows you to distinguish between the objects that have already been processed and the objects that have not. This status is indicated by the color of the traffic light in transaction SCUO in the SAP system. For example, a yellow light indicates that the objects in both clients are in the process of being made identical and green indicates the completion of the adjustment process. Determine whether this statement is true or false. | True False
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 6
Learning Assessment - Answers
1. Which of the following statements about client data are true? Choose the correct answers. [x ] A Client data consists of user master data. [x ] B Client data consists of client-dependent customizing data.
[~xj
C Client data consists of application data. D Client data consists of repository objects.
2. To initiate local client copy, log on to the target client using user DDIC and run transaction SCCL. Determine whether this statement is true or false. | True \x \ False
3. A remote client copy sends the data through a remote function call (RFC) connection to the target client. Determine whether this statement is true or false. [x ] True False
4. A client transport uses RFC. Determine whether this statement is true or false. | True \x \ False
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
5. When you delete a client using transaction SCC4, client data is still preserved but you can no longer log on to the client or access the data belonging to the client. Determine whether this statement is true or false. 0
True False
6. What kind of information is provided in the SCC3 copy log for a completed local or remote client copy ? Choose the correct answers. |~xj A Table statistics B Space information |~xj C Information about each table copied |~xj D Control information like status, user and start date & time E Application errors, if any exist
7. In a client comparison run, the process status allows you to distinguish between the objects that have already been processed and the objects that have not. This status is indicated by the color of the traffic light in transaction SCUO in the SAP system. For example, a yellow light indicates that the objects in both clients are in the process of being made identical and green indicates the completion of the adjustment process. Determine whether this statement is true or false. 0
True False
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Lesson 1 Implementing SAP Notes
345
Exercise 15: Implement a Note with the Note Assistant
355
Lesson 2 Describing SAP Support Packages
359
Lesson 3 Managing SAP Support Packages Exercise 16: Perform the Modification Adjustment
372 377
Lesson 4 Managing SAP Support Packages with Software Update Manager(SUM)
384
Lesson 5 Implementing SAP Enhancement Packages and SAP System Upgrades
389
Lesson 6 Reviewing Phases in the Technical Implementation of an SAPSystem Update/Upgrade
395
Lesson 7 Activating Business Functions with SAP Switch Framework 5
401
UNIT OBJECTIVES
•
Apply SAP Notes
•
Define Support Packages
•
Apply SPAM/SAINT Update
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
Apply Support Packages
•
Apply Support Packages with SUM
•
Plan for new, updated, and upgraded functionality in SAP systems
•
Describe the technical phases of an SAP system update/upgrade
•
Activate business functions using the SAP Switch Framework
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 7 Lesson 1 Implementing SAP Notes
LESSON OVERVIEW
This lesson describes how to apply SAP Notes and implement SAP Note Assistant. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Apply SAP Notes
SAP Notes SAP Notes are used for different reasons. SAP Notes can provide general information, recommendations from SAP or tips and hints. They can also describe a problem and contain solutions to known problems in standard functions of SAP software. When discussing SAP Notes in this concept, we refer only to those SAP Notes that contain a change of a repository object. Not all repository objects can be handled with the Note Assistant; for example, dictionary objects are not supported. SAP Notes describe how to change a repository object in the SAP system by providing the correct source code. SAP Support Package Stack: Group of SAP Support Packages
Example: SAP ECC
SAP Support Package: Group of objects
SAP ECC
A d d -O PF
Cl-
EE
EE
SAP APPL
EE
It
’
IE
IE
'• 'S A P HR
SAP_ABA SAP BASIS
SAP Note: changes single object
EE
Enterprise Extension (“deltas to 4.6C“) Add-On Add-On, can be modifying
IE
Industry Extension (former Add-On, former Industry Solution)
Figure 140: Support Package and SAP Note
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Hint: Regularly check for security related SAP Notes for your SAP system with the RSECNOTE program.
Contents of SAP Notes
•
Symptoms of the problem
•
Cause of the problem
•
Description about correcting the source code
•
SAP version number that applies to the SAP Note
•
Support Package status that applies to the SAP Note
•
Links to Support Packages that correct the problem
Carefully read any SAP Note before you implement it. An SAP Note can contain prerequisites, interactions, and references to post processing activities, such as changing a table structure that you must consider first when you implement it. While implementing an SAP Note, you can remove the problem it refers to. Problems Implementing SAP Notes Manually
•
Costs
•
Quality Assurance
Manually implementing an SAP Note can lead to high costs involving resources and time. If an SAP Note is implemented incorrectly, the quality of the SAP system suffers. Before modifications based on the content of an SAP Note, verify that the SAP Note is applicable to your SAP release and that the symptoms in the SAP Note are the same as the symptoms apparent in your SAP system. In the case of uncertainty, contact SAP. Perform all modifications of SAP objects in the development system, test in the quality assurance system, and distribute to production system only after thorough testing and verification. Since modifications lead to the need for a modification adjustment during a later SAP system upgrade or when applying Support Packages, document your changes to speed up the modification adjustment process. When documenting, include the SAP Note number and SAP system release dependencies. Set attributes for transport requests to help you identify them. For example, after setting appropriate attributes, you can identify which transport request in the import queue contains a manual advance correction according to an SAP Note. Automatic implementation of SAP Notes contributes to enhanced quality because it reduces errors due to manual implementation. Automatic implementation is discussed in the next section. Tasks of Note Assistant
•
Automatically implement SAP Notes that address repository object source code corrections.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
Handle dependencies from other SAP Notes, Support Packages, and modifications.
•
Displas all SAP Notes implemented in the SAP system.
•
Handle updates included in Support Packages, enhancement packages, and system upgrades.
•
Correct a single problem. SAP Notes is not a replacement for Support Packages.
The Note Assistant includes the following functions: •
Reporting - Display an overview of all existing SAP Notes, their processing statuses, and all implemented source code corrections.
•
Workflow functions - Assign SAP Notes to users who specify a processing status for the SAP Notes. The SAP system informs you when an SAP Note has an inconsistent status.
•
Logging - Review processing steps in the system log.
•
Corrections - Implement automatically the source code corrections (correction instructions) contained in SAP Notes into your SAP system.
•
Integration - When you apply a new support package or upgrade your SAP system, the system automatically recognizes which SAP Notes have already been completed by an imported Support Package or SAP system upgrade and which correction instructions must still be implemented.
Apply SAP Notes with the Note Assistant in the following two ways: 1. If a connection to the SAP Service Marketplace is configured in the SAP system, you can directly download the SAP Notes to your SAP system. 2. You can also separately download the SAP Notes from SAP Service Marketplace (for example, with the download manager) to your PC and then upload them to the SAP system. The upload then takes place from within the Note Assistant. Transaction ANST The Automated Note Search Tool (transaction a n s t ) assists SAP NetWeaver administrators in searching for and implementing correction notes from SAP. These correction notes, when implemented, can solve or alleviate specific problems in standard SAP code. When an issue is reproduced on a customer's system, the ANST displays a list of application components that are involved in the issue. Based on the issue that is reproduced, the ANST looks up correction notes from SAP (belonging to a specific release and to certain application components) and displays them. You can implement any of these notes in your system just by double-clicking one of them in the Download Note column. This triggers a pop-up that requests you to confirm the implementation action. Once you confirm the download, the tool automatically calls the note assistant (transaction s n o t e ) and downloads the note making it ready for implementation. If irrelevant application components are selected, a note search can display many irrelevant notes. This makes it difficult to identify the relevant correction notes that could solve the problem. To optimize search results: For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
You can view the objects that were found in the trace for each subcomponent and look for correction notes for each object.
•
You can view or edit the object by double-clicking it.
Of course, problems can result from errors in customer code as well as errors in standard SAP code. Errors in customer code can result from BAdl implementations, user exists, field exits, or modified standard SAP code. You can use the ANST tool to identify these too. To do so, choose Customer Code. A list of objects from the customer code will be displayed. Double-click the row corresponding to the object to view or edit it. Once an issue is reproduced in the ANST, a trace of the process is created. This trace can be reused at any point in time to search for correction notes. To do this, choose Open Trace. A list of traces that were created and their descriptions are displayed. If no correction notes are available for a specific problem, the issue could have been due to changes in the standard SAP code. The ANST allows you to view the list of customizing tables. To view them, choose Customizing Table. The customizing tables that are involved in the process are displayed as a tree list, grouped by application component. To optimize the performance of the note search, you can customize some of the search parameters, as follows: •
You can select the objects to be included in the search results. To do so: 1. Choose Object Customizing 2. Lists of dictionary objects are displayed. Now, choose the objects that need to be included and then choose Save.
•
You can search for notes based on the date that the note was released. To do so: 1. Choose Settings. 2. Indicate the initial date from which the tool should search the available notes. Notes released with a date older than the one specified in this field are not included.
Note Assistant B -
S A P N o te
:o
E n v ir o n m e n t
- ] <3 H
©
U t ih t ie s ( M )
© © ©
Q S 0S8
©04353
Note Assistant: Worklist for User CA TON
(&■t*S>*6
£b
£J(D SP
a u %
SAP Notes ^-- GD H m i
o 0000427325 o 00004274^ 3. o o n o o437-?/k 2. E ^0427325001^^ ■o -o 0 4 2 7 3 2 5 0 0 3 1-o 0 4 2 7 3 2 5 0 0 4 1. o 0 4 2 7 3 2 5 0 0 5 Is o 0 4 2 7 3 2 5 0 0 6 1. ■o 0 4 2 7 3 2 5 0 0 7 1, ■o 0 4 2 7 3 2 S 0 0 8 1. •o 0 4 2 7 3 2 5 0 0 9 1. o 0 4 2 7 3 2 5 0 1 0 1. -o 0 4 2 7 3 2 5 0 1 1 1-
Demonstration Demonstration Demonstration Demonstration Demonstration Demonstration Demonstration Demonstration Demonstration Demonstration Demonstration Demonstration Demonstration Demonstration
note note note note note note note note note note note note note note
fo r fo r fo r fo r fo r fo r fo r fo r fo r fo r fo r fo r fo r fo r
NA NA NA NA NA NA NA NA NA NA NA NA NA NA
training training training training training training training training training training training training training training
Figure 141: Worklist For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
The Note Assistant is started with transaction s n o t e . The worklist is your personal view on the SAP Notes (unlike the Note Browser that displays all SAP Notes that are available in the SAP system). All users see inconsistent and new SAP Notes in their worklists. Only you see the SAP Notes under the category In Processing. They are the ones that you process. From your worklist, you can perform all actions such as upload, implement, and display SAP Notes.
S ’
SAP Not**
&
Ed*
fio to
T|
- ]
Settings
System € > ( d ©
O H
Q s a s a
mm
®
Note Assistant: Note Browser
d^Ai
i ,
i i
. | |
Note 427325 427423 427706 518092 573875 593352 657928 777918 943779 985720 1011229 1083851 1239229 1263455 1273605 1301132 1307663 1308982 1309506 1327372 1328700 1339623
Q
(D
&
& 9
7
Oft D
Short tex t 1. Demonstration not* for NA trading 3. Demonstration note for NA training 2. Demonstration note for NA traring Error betw een RS_FUNCTIONMODULE_INSERT and transport RS_FUNCTIONMODULE_INSERT with non-exstent FUGR SPAU/comparison: customer modules ncorrect ri SAP group Error n th e RS_FUNCTIONMODULE_INSERT functaon module SM36 creates ^consistent jobs Note Assetant: Important notes Incorrect message if 99 modules exist ri a function group CCMS: Performance of table CSMCONTX ST-PI: Corrections for E2E Diagnostics RZ20: Incorrect startup methods repeatedly restarted SM66 - Report name or database table name is truncated Sales Planning and Netweaver 701 ATRA: End-to-end support CCMS: Too many deletions n table CSMCONTX SU1M| RSUSR100N Status history, technical view SH0W_)08STATE does not show aljo b statuses SPAM/SAINT with paraBel R3trans Subdrectories for ADS spool requests WebReportmg: Exception in module WWW_GET_SCRIPT_AND_HTML ST02: Stte of dsp-r-work executables dsplayed as zero
Appl. Component BCUPGNA BCUPGNA BCUPGNA BC-OWB-TOO-FUB BC-OWB-TOO-fUB BC-DWB-TOO-FUB BC-OWB-TOO-FUB BC-CCM-8TC BC-OWB-TOO-FUB BC-CCM-MON SV-SMG-SER BC-CCM-MON BC-CCM-MON-TUN CRM-ANA-PS BC-ABA-LA BC-CCM-MON BC-SEC-USR-1S BC-CCM-BTC BC-UPG-OCS-SPA BC-CCM-PRN BC Cl WEBR BC-CCM-MON-TUN
Proc. Status new new new Not Relevant Not Relevant Not Relevant Not Relevant In Process In Process Not Relevant In Process In Process Fmshed Not Relevant Not Relevant Not Relevant Not Relevant Not Relevant In Process In Process In Process Not Relevant In Process
Implementation * Cannot be mpler Cannot be mpler Cannot be mpler Cannot be mpler Cannot be mpler Cannot be mpler Cannot be mpler Completely mplei Cannot be mpler Cannot be mpler Completely mplei Completely mplei Cannot be mpler Cannot be mpler Cannot be mpler Cannot be mpler Cannot be mpler Cannot be mpler Completely mplei Obsolete Completely mplei Cannot be mpler Cannot be mpler 4 ►
-
^ ^
Figure 142: Note Browser
The Note Browser gives an overview of all SAP Notes available in the SAP system. To reduce the number of SAP Notes that are displayed in the results list, you can specify various criteria in the selection screen (processing status, application component, implementation status). From the Note Browser, you can also implement or display SAP Notes. Note Assistant provides additional functions described in the following lists. Viewing information From your worklist, you can view the following information: •
SAP Notes that are assigned to you as a user
•
All SAP Notes that are inconsistent, even if they are assigned to another user
•
New SAP Notes that have not yet been processed
Finding SAP Notes You can use the note browser to find any SAP Note that is available in the SAP system. Choose Display Note to read through the SAP Note. Upload SAP Notes Download an SAP Note from the SAP Service Marketplace to your front end. Then choose Upload in transaction s n o t e to load the SAP Note into the Note Assistant. Checking SAP Notes
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Choose Check Note to check the implementation status. Specifying processing status You can specify the processing status by choosing Set Processing Status. You can implement the correction instructions that are contained in the SAP Note and then later remove them. In the log, you can display the processing steps and add your own comments to it. You select an SAP Note and choose the Corrected Objects button to go to the Modification Browser where you can see all the objects that an SAP Note has corrected. After importing a Support Package, you can use the Modification Assistant to perform follow-up activities. If you want to correct an error using an SAP Note, you must already know the number of the SAP Note that corrects the error. You can download the SAP Note from http: //service.sap.com/notes with the download manager. The download manager and its requirements are available in the SAP Service Marketplace.
Figure 143: Download from SAP Service Marketplace
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
&
S A P Note
Edit ^ S o t c T ^ Environment
&
»"
h
utilities(M)
© 0 ©
asaffl
a o a a
Note Assistant: W ork/ist fo r User CA TON
cs> c^S) ■og; <^2>
S U fD
^
^
SI
1 1 'A
SAP Notes '-- New
o o o Ltl o o o o o o o o o o
0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 4 4 4 4 4 4 4 4 4 4 4
0 0 0 2 2 2 2 2 2 2 2 2 2 2
0 0 0 7 7 7 7 7 7 7 7 7 7 7
4 4 4 3 3 3 3 3 3 3 3 3 3 3
2 2 2 2 2 2 2 2 2 2 2 2 2 2
7 7 7 5 S 5 5 5 5 5 5 5 5 5
3 4 7 0 0 0 0 0 0 0 0 0 0 0
25 23 06 01 02 03 04 05 06 07 08 09 10 11
1 . 3. 2. 1 . 1 .
1.
1 .
1. 1. 1. 1.
1. 1. 1.
Demonscracion Demonstration Demonstration Demonstration Demonstration Demonstration Demonstration Demonstration Demonstration Demonstration Demonstration Demonstration Demonstration Demonstration
note note note note note note note note note note note note note note
for for for for for for for for for for for for for for
N N N N N N N N N N N N N N
A A A A A A A A A A A A A A
t t t t t t t t t t t t t t
r r r r r r r r r r r r r r
a a a a a a a a a a a a a a
i i i i i i i i i i i i i i
n n n n n n n n n n n n n n
i i i i i i i i i i i i i i
ng ng ng ng ng ng ng ng ng ng ng ng ng ng
► Figure 144: Upload SAP Notes
To upload the SAP Notes, choose Goto —>Upload SAP Note
[&DEV(1)/100 Information
a
SAP Note 0427325001 can be implemented
n j
Figure 145: Check SAP Note
Check the implementation status of an SAP Note with Check SAP Note. For more comprehensive information, click the yellow question mark in the information window. &DEV(1)/100 Set Processing Status SAP Note 0427325001
QNew r
jSiln Processing
n
Proc. by:
CATON
O Compltd C)Not Relevant
Figure 146: Set Processing Status
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Set Processing Status
In the Set Processing Status dialog box, classify an SAP Note or set the processing status. Use the following processing statuses: •
If you want your colleague to process the SAP Note, enter your colleague's user name and set the SAP Note to In Processing. It will appear in his or her worklist.
•
If the SAP Note does not correspond to your situation, you can set it to Not Relevant.
•
After implementing an SAP Note, you can set the status to Compltd.
&
SAP Note
Edit
© T Lr
Goto
Environment
-- <3 0
Utities(M)
Qsasa © t T e o
N ote A ssistan t: W orklist for User CA TON
^
C(D [£ 2
a
[FI ^0427325001~^ Demonstration note for NA training
i
i
►
►
Figure 147: Implement SAP Note
Information about Implementing SAP Note
To implement the SAP Note, select the respective SAP Note and choose Implement SAP Note. Review the following information: •
Confirm that you have carefully read the SAP Note because it may contain prerequisites or postprocessing activities that are described only in the long description.
•
You are prompted to include your changes in a transport request.
•
Traffic light indicates whether the changes can be copied, that is, whether the correction instructions can be implemented. Double-clicking the message gives you more information.
•
Always perform a syntax check before you confirm the changes.
•
A log file is automatically created for each SAP Note that records all the steps that are performed in the Note Assistant. For example, you can enter a comment to leave a message for another processor.•
•
You cannot change the information that is entered in the log file.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
In certain situations, you want to deimplement an SAP Note that you have implemented. You can do this by choosing Reset SAP Note Implementation. When you do this step, the changes that have been introduced with the implementation of the SAP Note are reset and the SAP Note is reset to the status that it had before its implementation. [&■ DEV(1)/100 SAP Note queue to be imported Note Short text Component 427325001 "’ l . Demonstration note for NA training BC-UPG-NA " 427706001
4
►
2. Demonstration note for NA training BC-UPG-NA
Proc. Status Implementation Sta In Process Can be implementec In Process
Can be implementec
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ £ _______________________________________
4
Single
►
\$ r IB X
Figure 149: Handling SAP Notes with Preconditions
Sometimes corrections rely on other correction instructions. When preconditions exist, they are described in the SAP Note. The Note Assistant requires you to follow the exact information in the SAP Note, and you need to implement first all the other required SAP Notes. Download the required SAP Notes and upload them in the Note Assistant, before implementing them.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
The Note Assistant will implement as many SAP Notes as possible in one step. The Note Assistant is closely related to the Modification Assistant. From within the Note Assistant you can directly switch to the Modification Browser (transaction S E 9 5 ). The Modification Browser displays an overview of all objects that are changed with this SAP Note.
&
Program
© i L
£dit
g oto
System
Help
CCOJ3 HE
-■’ <1 a e © e □ J
Program SCWN REGISTER NOTES
Note Assistant: Register SAP Notes
0
Figure 150: Registering Manually Implemented SAP Notes
If you have implemented corrections from SAP Notes manually before using the Note Assistant, you must make these SAP Notes known to the Note Assistant. Otherwise, the Note Assistant does not know that this correction has already been implemented in your SAP system and implements it again and this step will lead to inconsistencies. Registration offers the following benefits: •
All the SAP Notes that have been implemented in your SAP system are displayed in the Note Browser.
•
If a manually implemented SAP Note is a prerequisite for an SAP Note that you want to implement using the Note Assistant, the Note Assistant recognizes that the prerequisite SAP Note has already been implemented and does not prompt you to implement it again.
•
For future Support Packages or upgrades, the manually implemented SAP Notes are displayed during the modification adjustment in the category SAP Note corrections. The SAP system determines whether these SAP Notes have to be implemented again or reset to their original status.
To register the SAP Notes, the SAP system loads the SAP Note and checks whether it is valid for your release and Support Package level. If you encounter problems with the Note Assistant, do the following: •
If implementation fails, create a problem message in SAP Service Marketplace and assign it to the component of the SAP Note (for example, FI-AR-CR).•
•
If you experience other problems with the Note Assistant, create a problem message and assign it to the component BC-UPG-NA.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 7 Exercise 15 Implement a Note with the Note Assistant
Business Example
SAP Notes can fix single problems in an SAP system by containing corrected coding. The administrator or developer uses the SAP Note to automatically implement these SAP Notes into an SAP system, and the administrator monitors the implemented SAP Notes. Apply Note Assistant
Apply an SAP Note with the Note Assistant. 1. The SAP program s a p b c 426_## (where # # is your user number) normally displays flights with their seats, but the program is not working properly. In step 2, apply the SAP note to a program, but first check the program and its result with transaction SE38 in this step. Log on with the following details: Data
Data Values
System
DCC
Client
100
Transaction
SE38
2. Read the description of the SAP Note and check if the SAP Note contains any manual activities. Use transaction s n o t e and SAP Note 4273250## to complete this task. 3. Use transaction s n o t e to check whether SAP Note 4273250## for the program s a p b c 4 26_# # can be implemented. 4. Implement and verify the implementation of SAP Note 4273250## for the program SAPBC 42 6_# #. Remove a Note
Use the Note Assistant to remove a Note. 1. After establishing a completed status, it is more difficult to locate the note for deimplementation. Use the Note Browser to locate the Note.
Note: When you set the status to completed, you no longer see the SAP Note in transaction SNOTE. It would be easier to see if you had not set the status.
Alternate Scenarios with the Note Assistant with Two Notes
Use the Note Assistant to implement two dependent SAP Notes. For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
1. Verify that you can implement SAP Note 4277060##. 2. If the note is implementable, then you actually need to implement SAP Note 4277060##. 3. Release the transport request.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 7 Solution 15 Implement a Note with the Note Assistant
Business Example
SAP Notes can fix single problems in an SAP system by containing corrected coding. The administrator or developer uses the SAP Note to automatically implement these SAP Notes into an SAP system, and the administrator monitors the implemented SAP Notes. Apply Note Assistant Apply an SAP Note with the Note Assistant.
1. The SAP program s a p b c 426_## (where # # is your user number) normally displays flights with their seats, but the program is not working properly. In step 2, apply the SAP note to a program, but first check the program and its result with transaction SE38 in this step. Log on with the following details: Data
Data Values
System
DCC
Client
100
Transaction
SE38
a) Enter S E 38 in the Command field in the top left of the screen. b) In the ABAP Editor: Initial Screen, enter
s a p b c 426_##
in the Program field and choose
Execute. c) In the Model Solution: Note and Modification Assistant Workshop screen, enter a valid airline carrier such as l h in the Airline field. You can use Help (F4) to select it. d) Start the selection by choosing Execute. On the Flights screen, note that the result looks poor. 2. Read the description of the SAP Note and check if the SAP Note contains any manual activities. Use transaction s n o t e and SAP Note 4273250## to complete this task. a) Enter s n o t e in the Command field to display the SAP Note text of your SAP Note 4273250##. Click the folder icon to expand. b) Double-click SAP Note 4273250## to read it. c) If the SAP GUI Security dialog box appears, change the setting to allow the transaction and choose OK to confirm.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
The program goes to the Note Assistant: Note Display screen where you can view the SAP Note.
Note: Ignore any warnings concerning ADS. We do not use it in this course.
d) On the Note Assistant: Note Display screen, choose Set Processing Status to change the processing status of the SAP Note to In Processing. e) On the Set Processing Status SAP Note dialog box, choose the In Processing radio button and choose Continue. f) If the SAP GUI Security dialog box appears, change the setting to allow the transaction and choose OK to confirm. 3. Use transaction s n o t e to check whether SAP Note 4273250## for the program sa p b c 426_## can be implemented. a) Enter
snote
in the Command field and choose Enter.
b) Download the required note(s) from SAP by choosing GOTO —*• Download SAP Note. c) Choose SAP Notes —*• New, expand the folder and select SAP Note 4273250##. d) With the note selected check whether it can be implemented in the system by choosing SAP Note —► Check SAP Note. A message is displayed indicating whether or not the note can be implemented in the system. 4. Implement and verify the implementation of SAP Note 4273250## for the program SAPBC 4 2 6 _ # #. a) On the Note Assistant: Worklist screen, choose Check Implementation Status of a Note. Ignore messages about having problems with SAPNet. b) In the Information dialog box, choose Continue to acknowledge the namespace message. c) In the Prompt for local Workbench request dialog box, enter a new transport request in the Request field and the SAP Note # in the Short Description field. d) In the Information dialog box, confirm changes by choosing Continue. e) In the Confirmation dialog box, confirm inactive objects by choosing Continue. f) On the Note Assistant: Note Display screen, choose Set Processing Status and set the processing status for your SAP Note to Compltd (Completed). g) Enter
S E 38
in the Command field in the top left of the screen.
h) Enter sapbc 426_## in the Program field and choose Execute. i) In the Model Solution: Note and Modification Assistant Workshop screen, enter a valid airline carrier such as l h in the Airline field and choose Execute. Notice that the last column Seats max remains empty. The seats do not display.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
Remove a Note
Use the Note Assistant to remove a Note. 1. After establishing a completed status, it is more difficult to locate the note for deimplementation. Use the Note Browser to locate the Note. Note: When you set the status to completed, you no longer see the SAP Note in transaction SNOTE. It would be easier to see if you had not set the status. a) Enter s n o t e in the Command field on the top left of the screen. b) In the Note Assistant: Worklist screen, choose Goto —» SAP Note Browser. c) In the Note Assistant: Note Browser screen, choose SAP Notes with Finished in the Processing Status field. d) Choose Execute. e) In the Note Assistant: Note Browser window, choose Reset SAP Note Implementation. f) Highlight the correct SAP Note for removal. g) In the Information dialog box, confirm your selection. Watch the processing status. Choose Processing Statusto set the status to In Processing before removing the note. Otherwise, it will be set automatically. h) Enter s n o t e in the Command field in the top left of the screen to check that the program runs again in its original state. Alternate Scenarios with the Note Assistant with Two Notes
Use the Note Assistant to implement two dependent SAP Notes. 1.
Verify that you can implement SAP Note
4277060##.
a) Log on with the following details: Data
Data Value
System
DCC
Client
100
Transaction
SNOTE
b) On the Note Assistant: Worklist screen, display the SAP Note clicking it.
4277060##
by double
c) If the SAP GUI Security dialog box appears, change the setting to allow the transaction and choose OK to confirm. d) On the Note Assistant: Note Display screen, read the SAP Note text.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
e) Change the processing status of the SAP Note to in Processing by choosing Set Processing Status and then choosing Continue. f) If the SAP GUI Security dialog box appears, allow the security setting and choose OK. Notice in the Note Assistant: Note Display screen, the SAP Note appears with in Processing in the Processing Status field. g) Choose Check SAP Note to verify that you can implement the SAP Note. View the Implementation Status field to see the Can be implemented status. 2. If the note is implementable, then you actually need to implement SAP Note 4277060##. a) Enter s n o t e in the Command field in the top left of the screen and select a note. b) On the Note Assistant: Note Display, choose Implement SAP Note. Ignore messages about having problems with SAPNet. The system displays the SAP Note queue. c) The system identifies the dependency to the SAP Note 3273250## and it is in an In Processing status. d) Choose Install. e) In the subsequent dialog boxes, choose Yes, Continue, and Continue. f) Set the Processing Status for the two SAP Notes to Compltd (Completed). g) Enter S E 38 in the Command field in the top left of the screen. h) In the ABAP Editor: Initial Screen, enter s a p b c 4 2 6 _ # # in the Program Name field and choose Execute. i) In the Model Solution: Note and Modification Assistant Workshop screen, enter a valid airline carrier ID such as l h in the Airline field and choose Execute. Notice that the last column Seats max. is now showing some values. Now the program works correctly. 3. Release the transport request. a) Release the task and transport request corresponding to the SAP Note implementation using transaction SE09.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
System Recommendations Software security remains a critical topic of interest to all companies and to the information technology industry. The security of a specific system thereby also significantly depends on the secure installation and operation of this system. SAP gained a lot of experience from its support for and engagement with numerous customers. It uses the resulting best practices not only for further improvements and enhancements of its support offering but also makes them available as recommendations, services and tools directly to its customers. Using the new application System Recommendations within the SAP Solution Manager you can track down critical Security Notes which are required for your systems. You could use Configuration Validation to analyze the security configuration for system landscape. To keep your SAP systems up-to-date and secured you have to apply various types of notes and patches. System Recommendations shows all relevant notes and patches for the selected systems in the SAP Solution Manger and helps you to keep all of your systems up-to-date. The key features of System Recommendations are as follows: •
Provides a detailed recommendation of SAP Notes that should be implemented, based on the actual sales of the system and already implemented Notes
•
The recommendations comprise the following notes categories: -
Security notes
-
Performance-related notes
-
HotNews
-
Legal change notes
-
Correction notes/patch notes
•
Powerful calculation method for notes provides a comprehensive recommendation for the selected system
•
Increase system security by applying up-to-date security-related notes exactly tailored for the respective system•
•
Integration into Change Request Management to directly create Requests for Change for the selected notes
•
Easy-to-use filter settings allow exact selection of system or solution
System Recommendations is a new functionality in SAP Solution Manager, focusing on SAP Notes. It provides a tailored recommendation of SAP notes which should be applied to a selected managed system, and this recommendation is calculated based on the actual “ SAP notes status” of this system. Questions like “ Is a specific SAP note already implemented in the system?" or “Which version do the implemented SAP notes have? Are there newer versions available?” are taken into account when calculating the recommendation for a system. System Recommendations collects needed information from the managed systems via a background job that should be scheduled on a regular basis (a direct refresh of the already calculated information for a specific system can also be started directly). The calculation itself is done in SAP’s Global Support Backbone, which means that there is no load being generated on the SAP Solution Manager system or on the managed system. For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Recommendations are divided into the following note categories: •
Security-relevant notes
•
Performance notes
•
HotNews
•
Legal change notes
•
Correction notes (for ABAP and Java)
After the recommendation has been calculated, the user can set various statuses for the recommended notes, like "to be implemented” , “ not relevant" or “ postponed” . This, in combination with a filter displaying only notes with a certain status, helps to keep an overview of all the recommendations and helps keeping track of tasks which are assigned to those recommendations. The process flow is as follows: 1. Select the system to check and update. 2. Retrieve system information (SP level, patch level, notes, etc). 3. Connect to SAP Global Support Backbone. 4. Calculate delta information (latest relevant notes, etc). 5. Send information back to the customer's SAP Solution Manager system. 6. Show relevant notes via System Recommendations of Configuration Validation.
9 \ j C ustom er
Retrieve system information (SP level, patch level, n o te s ,...)
□
□
Send information back to the customer’s SAP Solution Manager system
O
Calculate delta information (latest relevant notes, etc...)
Show relevant notes of the system (s) via System Recommendations or Configuration Validation
Figure 151: System Recommendations Process Flow
The following steps are necessary to run System Recommendations: For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
The SAP-OSS RFC connection needs to be set up correctly.
•
All managed systems have to be connected to SAP Solution Manager and documented in transaction SMSY, and they have to be assigned to a product system and to a solution.
•
Authorization object: SM_FUNCS (Control access and visibility of tabs in System Recommendations).
To collect this data automatically for the use within System Recommendations you should set up a batch job in the Settings area of System Recommendations. System Recommendations is part of the Change Management Work Center in SAP Solution Manager. More information is available within the following blog: http://www.sdn.sap.com /irj/scn/ weblogs?blog=/pub/wlg/24227 or in the online Help: http://help.sap.com/ saphelp_sm70ehpl_sp26/helpdata/ en/83/68fad4952d42al92469fa02586aeff/frameset.htm. Monthly on 2nd Tuesday
The week after the Patch Day
Within one month
During next maintenance cycle
Configuration Validation checks in Solution Manager
Security Patch Day of SAP
Apply Security Notes
Check System Recommendations in Solution Manager Check Early Watch Alert RSECNOTE
Perform individual regression test
Scheduled Implementation!
Apply Kernel Patches, Java Patches and ABAP Support Packages
4Apply additional manual configuration of Security Notes if necessary Complete Test
Figure 152: SAP Solution Manager Security Services
The Security Patch Day of SAP takes place on every second Tuesday per month. Please note the following: •
At the end of that day you can inspect the updated list of Security Notes on the page / securitynotes in the Service Marketplace. Here you see the complete list of all Security Notes.
•
Use the application System Recommendations to check which of the Security Notes are relevant for the various systems of your system landscape. (Usually you have scheduled the check as a background job: you might, for example, check the results every Wednesday.) You can create change requests directly from that tool.•
•
The EarlyWatch Alert report and the corresponding tool RSECNOTE show strong recommendations from Active Global Support concerning HotNews and other important
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
notes which are relevant for a given system. Usually you create and check these reports at the beginning of the next week. •
You will run a Risk Assessment concerning the criticality of the Security Note as well as concerning the risk of applying a change which might touch productively used business processes. As a result you decide which Security Notes should be applied as part of a monthly patch cycle and which will be part of the next maintenance cycle.
•
Using the application Configuration Validation you can create a report which checks which systems comply with your security policy. Therefore you add all notes which should be installed into the target system definition of the Configuration Validation.
•
Within the current month you apply the selected Security Notes and you run regression tests (if necessary) to ensure productively used business processes are working properly.
•
As part of the next maintenance cycle you will update the Kernel, apply Java Patches and ABAP Support Packages. As part of this update you will get the corrections of the Security Notes, too. However, some of the Security Notes describe configuration changes which you can apply now as well. While working on the update it might be the case that you will get new Security Notes from newer Patch Days. You should include these if possible. Finally you run a complete test of your business processes.
Hot News SAP HotNews are priority 1 (very high priority) SAP customer notes. These notes tell you how to resolve or avoid problems that can cause the SAP system to shut down or lose data. If you are affected by these problems, you must ensure that you are aware of these notes. It is recommended that you set up regular procedures to check for new HotNews. Define a responsible person to check for new HotNews and creation of requests for change. Requests for change are forwarded to the person responsible for the process. SAP Patch Day
SAP releases security patches every second Tuesday
System Recom m endations
System Recommendations identifies the relevant patches for the selected system(s)
The selected relevant notes or patches (Java) are applied to the SAP system
Configuration Validation
Provides a report focusing on the implementation status of the applied security notes
Security validation is done in Configuration Validation
Figure 153: System Recommendations Supporting Security
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
As the engineer is focusing on security-relevant SAP notes, he now finds all relevant notes on the tab Security Relevant Notes. To get more information on the recommended SAP notes, he can drill down further into each one of them, read the description of the note (by clicking on the notes title) and select a status - new, to be implemented, postponed, not relevant - for every note.
System Recommendation can also be used for Java systems. The procedure is exactly the same as described above; the only difference is that the Java patch notes will only show up on the tab Correction Notes. Choose Add to download basket to add the Java patches containing the selected notes directly to the download basket in SAP Service Marketplace. An integration into Maintenance Optimizer to approve the download basket is also available. Integration For Customers using the Change Request Management functionality in SAP Solution Manager, System Recommendations provides integration into the Change Request Management to trigger a Request for Change for the SAP notes selected for implementation. Integration into Maintenance Optimizer is provided to directly download the Java Patches containing relevant Java Patch notes. Integration into SAP Service Marketplace is available to directly add selected Java Patches to the users download basket. Additionally, integration into Configuration Validation (starting with SP03) exist to enable the compare of systems in your landscape. You could, for example, validate the notes with thestatus "To be implemented” in all systems of your solution.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
| SAP Note contains automatic correction instruction | SAP N o te co nta ins manual correction instruction |
SAP Note is aKernel Note
Figure 155: Coming Next in System Recommendations
To give improved support fortesting, the object list will be provided (planned for ST SP05). Thus the BPCA analysis could be started and used for testing integration. In case Change Request Management is not used an integration to transaction SNOTE in the development is provided. The SAP Note that is to be implemented will be sent to SNOTE and can be implemented there. Additional info regarding the correction instruction will be listed to provide a better overview about the impact and effort that has to be expected when implementing the SAP Note. The flat list view is also available and provides improved searching possibilities. SAP Notes Application Process Flow
SAP SMP
Search SAP Note in SAP Service Marketplace
User
Q
Load SAP Note
Q
Check SAP Note Apply SAP Note
SNOTE
SAP Note Assistant
First test + export
Import + quality assurance
Import
Transport directory Figure 156: Distribution of Corrections
Application of SAP Notes To apply the SAP Notes steps in your SAP system landscape, do the following:
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
1. Implement the SAP Notes with the SAP Note Assistant in the development system (DEV). 2. Transport the SAP Notes from the development system to the quality assurance system (QAS). Do this step with the transport request that contains the corrected objects. Do not implement the SAP Note with the Note Assistant in QAS. 3. Test these corrections. 4. Import the SAP Notes into the production system (PRD). Use the transport request that contains the corrected objects. Do not implement the SAP Note with the SAP Note Assistant in PRD.
A
Caution: Do not transport the implemented SAP Notes in the quality assurance system (QAS) before applying the same Support Packages in QAS, because you need to perform the same implementation sequence as in DEV. It is important that all SAP systems in an SAP system landscape use the same Support Package level.
For releases before SAP Web AS 6.10, the SAP Note Assistant is delivered as an add-on.You can download the add-on SAP Notes from the SAP Service Marketplace. Please read the related SAP Notes before you install the Note Assistant. Changes to SAP repository objects that are introduced using the Note Assistant do not require an SSCR key.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
LESSON SUMMARY You should now be able to: •
Apply SAP Notes
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 7 Lesson 2 Describing SAP Support Packages
LESSON OVERVIEW
This lesson describes the nature and usage of SAP support packages. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Define Support Packages
Support Packages An SAP system consists of different software components. All of these components are regularly updated using Support Packages. Installing upgrades mean that problems are solved, legal changes are shipped, security issues are solved, and new functions are provided. Apply support packages regularly to keep the system up-to-date. Example: SAP ECC
SAP Support Package Stack: Group of SAP Support Packages
Add-On
SAP Support Package: Group of objects
FE Add-On
EE
EE
T
EE
EE
IE
SAP APPL
IE
SAP HR
SAP ABA
SAP Note: changes single object
SAP BASIS
Figure 157: Support Package and Support Package Stack
Additional Components in SAP ECC
•
Enterprise extension (EE) - these are deltas to 4.6C
•
Industry extension (El) - formerly add-on and formerly industry solution
•
Add-on
What is a Support Package?
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
A Support Package is a group of corrected or new SAP objects. Support Packages are required to correct problems in various components. The upgrade is executed by replacing erroneous objects with corrected versions of these objects.
•
A Support Package stack is a combination of Support Packages that we recommend.
•
Each software component has a separate sequence of Support Packages.
Support Package Requests
SAP Support Package Stack
Figure 158: Requesting Support Packages*•
Requesting Support Packages: •
Requesting Support Packages and Support Packages stacks for SAP NetWeaver 7.0 and higher based SAP systems requires the SAP Solution Manager maintenance optimizer.
•
Requesting Support Packages and Support Packages stacks for SAP NetWeaver 7.0 and higher based SAP systems requires a maintenance certificate. Create the certificate manually every three months through SAP Service Marketplace or automatically with SAP Solution Manager.
Before you can apply Support Packages, first download them from the SAP Service Marketplace. Apply the whole Support Package stacks rather than other combinations of Support Packages. To request SAP Support Packages, access the maintenance optimizer (as part of SAP Solution Manager) for approving the download. The maintenance optimizer helps you to calculate the correct queue of Support Packages for your individual SAP system. You also need a valid maintenance certificate to apply Support Packages.
Note: Older releases of SAP systems may not require a maintenance certificate. We recommend that you create the maintenance certificates automatically with SAP Solution Manager. This action causes much less effort than creating them manually, especially if maintenance certificates for several SAP systems are needed. A maintenance certificate can also be created manually using the SAP Service Marketplace. This action can be initiated in the section where the customer declares the company's SAP systems.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Hint: A maintenance certificate is valid for three months only.
LESSON SUMMARY You should now be able to: •
Define Support Packages
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 7 Lesson 3 Managing SAP Support Packages
LESSON OVERVIEW
This lesson describes how to manage SAP support packages. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Apply SPAM/SAINT Update
•
Apply Support Packages
S P A M /S A IN T Update MOpz: request Service Marketplace: download Copy to SAP host Unpack SPAM/SAINT update SPAM: ‘load packages’ SPAM: apply update
Q
DEV
--------- ►
DEV
©
QAS
--------- ►
©
PRD PRD
QAS
Update the Support Package Manager (SPAM) Figure 159: Support Package Manager - SPAM/SAINT Update
The Support Package Manager (transaction
spam)
is the tool for applying Support Packages.
Before using the Support Package Manager, patch the tool with a SPAM/SAINT update. This patch enhances the functions of s p a m and s a i n t , for example, when dealing with new attributes from new Support Packages. Transaction s a i n t allows you to install and upgrade add-ons.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Note: Please note that SPAM/SAINT updates come in German and English only. If you work in another language, new or updated user interface elements and texts might not be properly displayed. This is why we recommend logging on in German or English if you want to use the Support Package Manager.
SAP Notes Application Process Flow
MOpz: request Service Marketplace: download Copy to SAP host Unpack SAP Support Packages SPAM: ‘load packages’ SPAM: settings SPAM: define queue SPAM: start conditions SPAM: apply queue SPDDISPAU: possibly modification adjustment
SPAM: check protocols
O DEV - ►
O
QAS - ► 0
PRD
SPAM: confirm queue
Figure 160: Applying Support Packages*•
The Support Package Manager ensures that only Support Packages that match your SAP system are displayed in the queue, for example, Support Packages from the same release or an add-on that has been installed will appear in the queue. Alternatively, you can compile a shared queue for all software components in the SAP system, by choosing All Components. The queue contains the Support Packages available for the selected components in your SAP system and any required Conflict Resolution Transports (CRTs) and associated add-on Support Packages. If Support Packages in the queue have a relationship to Support Packages for another software component (other predecessor relationship, required CRT), the queue is extended with other Support Packages until all predecessor relationships are fulfilled. The following rules apply when you create a queue: •
Support Packages for a selected component are placed in the queue according to their sequence.
•
When Support Packages in the queue are related to Support Packages for another software component (predecessor relationship, CRT required), the extra Support Packages are added to the queue until all predecessor relationships are included.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
If the SAP system calculates a consistent queue, display it and check it by choosing the Calculated Queue tab Note the following about testing: •
To set a test scenario or standard scenario, choose Extras —> Settings.
•
Use the test scenario to check whether a modification adjustment is necessary, or whether there are any conflicts or problems (such as unreleased repairs), before you actually import the Support Package. Use this scenario to estimate and possibly minimize the effort required to import the Support Packages. This scenario does not import any data or objects into your SAP system. If errors occur, you can continue the import without removing the errors. Select the test scenario explicitly. Note that the queue is empty after you run the test scenario and you define it again. At that point, select the standard scenario explicitly.
•
The standard scenario imports all Support Packages in the queue completely. If errors occur, you can only continue and complete the import after you have removed the errors. If you selected the standard scenario, you can choose between the standard import mode and the downtime-minimized import mode to reduce downtime.
Im p o rt Process Productive Downtime
0 -C
O Preparation
$ > in o SL, 1 cCo.9 _Q £o o° Q O O o . sg-o o Q Cfl Q
c d) S 2,1 | -=
Import 1
£
Q- (TJ O
o Post activities
Import 2
without 'downtime minimized' ) O 0) 0
o
o
OI o Q G 9- coQ CL l,£ Q CO
Preparation
t ° o f
0 > o X 1
Import 1
in E E con
^
>
O
CD
■c —
It
rr o ^ i X 0
Import 2
o CO O) co 0 O 0
CO
O Q.O Post activities
with 'downtime minimized' * Even much shorter downtime possible, when using SUM
Figure 161: Inactive Import
Note: During the time between the modules Preparation and Import 2 (or rather, until the modification adjustment), no transports other than the modification adjustment transport can take place. No manual changes can be made to repository objects (ABAP programs, dictionary objects) during this time. Keep the time period between Import 1 and Import 2 as short as possible. Due to the size and scope of current Support Packages, importing Support Packages requires longer SAP system downtime. The SAP system is not stopped and restarted during the import process. However, it should not be used productively during this time. This restriction is a For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
disadvantage for many production systems. To reduce the downtime during the import of Support Packages, an import procedure has been developed that allows you to import a large proportion of the objects to be imported during production operation. These objects are mainly programs. The downtime can be significantly reduced when a Support Package contains a high proportion of programs (up to 80%). With the inactive import, the objects are imported into the database in an inactive state and are therefore, invisible to the SAP system. You can at that point continue to use the SAP system productively.
Hint: When importing Support Packages, the Support Package Manager checks, if there are still any transport requests in the import queue for the old Support Package level. When the Support Package Manager produces a warning, you can ignore the warning and import the Support Packages.
Hint: It is possible to import Support Packages with the Software Update Manager (SUM). Importing Support Packages with SUM is by far more difficult and complex for the SAP system administrator, but this method leads to shorter downtime.
Hint: For some SAP systems, for example, SAP CRM, an advanced version of s p a m is used. In transaction s p a m , choose Environment —*■ Support Package Manager for EBP/CRM. SUM for EBP/CRM is interactive and helps the administrator to control the downtime.
Modification Adjustments
SAP ECC
Add-On
Modification adjustment necessary
EE
EE
EE
IE
IE
SAP HR x
Modification
SAP_ABA
SAP Support Package
SPDD for dictionary Repository objects SPAU for other Repository objects
SAP BASIS DEV
QAS
PRD
Manually
Manually or bind
Manually or bind
Manually
(j^ ^ V la n u a lly , x transport or *2^ % bind 4 *
^
<9^ > ^ ’Manually, A transport or \ bind 4
Figure 162: SPAM: Performing the Modification Adjustment
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Procedures to Perform Modification Adjustment in SUM
The procedures to perform modification adjustment in SUM are the following: 1. Wait for the Support Package Manager to stop to allow the modification adjustment. 2. For developers who will perform the modification adjustment, create a transport request in the Transport Organizer and request tasks inside it for these developers. 3. Require developers to perform the modification adjustment for their objects in the development client, not client 000. 4. After the adjustments are complete the developers must release the tasks and inform you, as the administrator. 5. (Optional) Once the transaction has been started, you access it again by entering the Support Package Manager (transaction s p a m ) and choose Support Package —► Import Queue. The SAP system prompts you again to perform the modification adjustment. Since it has already been completed, ignore the message and choose Continue. The Support Package Manager completes the processing and displays the status.
The selection, Import logs of the queue, displays logs for steps of the Support Package Manager that use the transport control program tp. After the queue has been successfully imported, always check these logs. To jump to the log display, choose Goto —>Log —>Queue in the initial screen of the Support Package Manager, transaction s p a m . Confirm the successful import of the queue into your SAP system. This step ensures that you can import other Support Packages in the future. Without this confirmation, it is not possible to import additional Support Packages. If you have not yet confirmed successfully imported Support Packages, you are prompted to confirm these packages during the upgrade of the SAP system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 7 Exercise 16 Perform the Modification Adjustment
Business Example
As the SAP system administrator for your company, you correct errors, introduce a collection new features, and implement Support Packages on a regular basis.
Note: In this exercise, the instructor enters transaction s p d d to display the dictionary objects to be adjusted and you adjust your own objects.You identify the basic configuration of the Transport Management System (TMS) and set up a transport domain. The instructor also enters transaction s p a u to display the non-dictionary objects to be adjusted and you adjust your own objects. You adjust all the modified programs from ADM325-XX. When you apply a Support Package, the SAP system checks for modification adjustments for other repository objects such as those from SPAU. In transaction SPAU, you adjust the modification to return to the SAP standard objects
Adjust Dictionary Repository Objects Using Transaction SPDD
Apply a Support Package. 1. To perform this modification adjustment on the dictionary objects, the instructor enters transaction s p d d to display the objects to be adjusted and you adjust your own objects. Log on with the following details (Replace # # with your user number.): Data
Data Values
System
DCC
Client
100
User
ADM325-##
Transaction
SPDD
Table
ADM325X##
Package
ZPACKAGE_# #
2. Choose the object to display for modification. To choose a modified dictionary object to display, start with the ending screen in the previous step adjustment on the dictionary object. The instructor will provide you with a new task for you to assign to your object. The system does not update the status to Yes until you confirm step 2 g.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Adjust Non-Dictionary Repository Objects
Adjust the non-dictionary repository objects using transaction SPAU. 1. To perform the modification adjustment on non-dictionary objects, log on with the following details: Data
Data Value
System
DCC
Client
100
User
ADM325-##
Transaction
SPAU
2. Choose the object to display for modification. To choose the non-dictionary object, start with the ending screen in the previous step, adjustment on the non-dictionary object. 3. Watch as the instructor returns to the Support Package Manager (transaction continues the application of the Support Package.
spam)
and
After adjusting all modifications that are necessary, and after successfully applying the Support Package queue, the instructor checks the logs in transaction s p a m . Afterwards, the instructor confirms the Support Packages using transaction s p a m .
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 7 Solution 16 Perform the Modification Adjustment
Business Example
As the SAP system administrator for your company, you correct errors, introduce a collection new features, and implement Support Packages on a regular basis.
Note: In this exercise, the instructor enters transaction s p d d to display the dictionary objects to be adjusted and you adjust your own objects.You identify the basic configuration of the Transport Management System (TMS) and set up a transport domain. The instructor also enters transaction s p a u to display the non-dictionary objects to be adjusted and you adjust your own objects. You adjust all the modified programs from ADM325-XX. When you apply a Support Package, the SAP system checks for modification adjustments for other repository objects such as those from SPAU. In transaction SPAU, you adjust the modification to return to the SAP standard objects
Adjust Dictionary Repository Objects Using Transaction SPDD
Apply a Support Package. 1. To perform this modification adjustment on the dictionary objects, the instructor enters transaction s p d d to display the objects to be adjusted and you adjust your own objects. Log on with the following details (Replace # # with your user number.): Data
Data Values
System
DCC
Client
100
User
ADM325-##
Transaction
SPDD
Table
ADM325X##
Package
ZPACKAGE_# #
a) Log on to DCC system with client 000. b) Enter s p d d in the Command field at the top left of the screen.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
c) In the Modification Adjustment Dictionary: Object Selection screen in the Selections area, in the Last changed by field, enter your user ID and choose the Execute button. d) To display objects in the Modification Adjustment Dictionary screen, choose Expand Subtree. e) To obtain the status of the object, choose Color Legend. 2. Choose the object to display for modification. To choose a modified dictionary object to display, start with the ending screen in the previous step adjustment on the dictionary object. The instructor will provide you with a new task for you to assign to your object. a) In the Modification Adjustment Dictionary screen, select the yellow traffic light icon of the object ADM325X##. An adjustment proposal appears. b) To accept the name of the Append Structure on the Create Append Structure dialog box, choose Continue. c) In the Create Object Directory Entry screen, in the Package field, enter z p a c k a g e _ # # and choose Save. d) Assign the modification to the transport request created by the instructor for adjustment.
spdd
We recommend that you keep the columns delivered by SAP and move your customer fields into a new append structure. e) To return to the Adjustment for Table screen, choose Back. f) In the Create Append Structure dialog box, verify the name, choose Yes, and choose Continue.
Note: The append structure is not a modification, but rather an enhancement. After the adjustment, your customer fields are in the append structure so the table can be reset.
g) After adjusting the object, the SAP system automatically assigns the status Object has been adjusted when you confirm the Information dialog box. h) Assign your object to a new task provided by the instructor for the transport request for SPDD adjustment. i) To release your tasks, use transaction SE09.
Do not release the transport request.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Note: The object ADM325X## now contains your previous modification (the ZZBIRTHPLACE field) in an append structure and the new field TELNO that came with the Support Package from SAP. Perform the modification adjustment now.
The system does not update the status to Yes until you confirm step 2 g. Adjust Non-Dictionary Repository Objects
Adjust the non-dictionary repository objects using transaction SPAU. 1. To perform the modification adjustment on non-dictionary objects, log on with the following details: Data
Data Value
System
DCC
Client
100
User
ADM325-##
Transaction
SPAU
a) Log on the DCC system and client 100. b) Enter s p a u in the Command field in the top left of the screen. c) In the Modification Adjustment screen, in the Selections area, in the Last changed by field, enter your user ID in and choose Execute. d) In the Modification Adjustment: Object Selection window, expand the Modification folder and select the With Modification Assistant checkbox. e) To obtain an explanation of the status on the object, choose Legend. 2. Choose the object to display for modification. To choose the non-dictionary object, start with the ending screen in the previous step, adjustment on the non-dictionary object. a) To return to the delivered version of columns in the Modification Adjustment: Object Selection window, position your cursor on the object and choose Modification —> Reset to Original. b) In the Reset object dialog box, choose Yes. c) Assign the modification adjustment to the transport request created by the instructor for the s p a u adjustment. d) Release your task by entering transaction S E 0 9 . Do not release the transport request. 3. Watch as the instructor returns to the Support Package Manager (transaction continues the application of the Support Package.
spam)
and
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
a) The instructor continues with transaction
spam
and the students watch the instructor.
After adjusting all modifications that are necessary, and after successfully applying the Support Package queue, the instructor checks the logs in transaction s p a m . Afterwards, the instructor confirms the Support Packages using transaction s p a m .
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
LESSON SUMMARY
You should now be able to: •
Apply SPAM/SAINT Update
•
Apply Support Packages
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 7 Lesson 4 Managing SAP Support Packages with Software Update Manager(SUM)
LESSON OVERVIEW
This lesson explains how to manage SAP support packages with Software Update Manager (SUM). LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Apply Support Packages with SUM
SAP Support Packages and TMS A transport request that was released from an SAP system with a certain version can only be imported into an SAP system with the same version number. This situation is obvious when transporting objects from the SAP standard, for example, modifications and customizing. Consider this restriction when transporting customer developments because these developments can be related to SAP standard objects. Not only the version (for example ECC 6.04 as compared with ECC 6.06) has to be considered, but also the level of the corresponding software components and the Support Package level. So, for example, do not import a transport request exported from an ECC 6.06 with SAP_APPL Support Package 9 into an ECC 6.06 with SAP_APPL Support Package 8.
Hint: Export release numbers should be equal to import release numbers. So transport requests usually rely on a certain version of the corresponding software components and their Support Package level. Do not import them into an SAP system with a different level, than the one they were exported from. You do not only consider the version, but also the level of the corresponding software components and the SAP Support Package level. Therefore, coordinate the application of SAP Support Packages and the importing of transport requests.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Calendar of DEV Sat/Sun
Thursday December 1 DVDK9G0G01 DVDK900002 DVDK900003 DVDK900004 DVOK9G0GG5
Apply SAP Support Package 1
Import transport requests
DVDK90G006 DVDK90G007
B
DVDK90000A DVDK90GG0B DVOK9G0OGC DVDK9GG0GD DVDK9Q00GE
Apply SAP Support Package 1
Import transport requests
Figure 163: Synchronization between Support Packages and TMS View 1
TMS verifies that a transport request fits the software component and the Support Package level of the target SAP system. The result of this verification is seen in the import queue in the CV column. This is the result of a comparison of the software component vector of the transport request with the software components of the target system. If the check is negative, the Status column displays Request does not match component version.
©
Hint: A transport request that does not fit the target system can still be imported by choosing the Ignore Invalid Component Version import option.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
STMS
I m p o r t Q u e u e : S y s te m Q A S
^(dzj^Qt© 6 » s* ms a y h Requests for QAS: 1
Humber 1 2 3
30.09.2011 09:45:03
Request
T
CM
Clt
RC
:
DCVX9002S4 DCVK900250 DCVX93003!
K K
100 100 100
100 100 100
o o o
k k k
H
0MC
Owner
Project
Short Text
DAT CM CATCH CATCH
DEV P00002 DCV_P00002
Development part C after
—7
\— le/ cv V ' O l >•\» /o
t r a n s p o r t r e q u e s ts in TM S w h ic h s h o u ld b e im p o r te d b e f o r ^ ^
Phase CHECK_REQOIR£MENTS: Explanation of Errors the import queue of the Transport Management System (transaction STMS) contains transport requests that are to be ixported before the current Support Package queue. These transport requests are listed below. Juap to the inport queue of the Transport Management System and import the transport requests for the isport. Then proceed with implementing the Support Package queue.
Phase CHECK_REQOIREKEHTS: Transport requests to be imported before Request
Descnptic
DEVK900244 DEVK9002S0 DEVK900252 DCVK900242 CEVK900236 DEVK900241 DEVTC900259 0CVK9002S7 DEVK900267 DEVK900269
Development pert Development pert Development pert Development pert Customizing pert Development pert Development pert Development pert Date Element Data Element 2
2 4 5 1 1 10 9 8
SPAM
Figure 164: Synchronization between Support Packages and TMS View 2
Hint: Perform a version check only when the tp parameter SP_TRANS_SYNC is set to ON for the SAP system receiving the import. A corresponding check is also performed when importing Support Packages. When there are still some transport requests in the import queue for the old Support Package level, the Support Package manager displays a warning. However, you can ignore the warning and import the Support Packages. SAP Support Packages with SUM It is also possible to apply Support Packages with SUM (Software Update Manager). SUM is the tool used for an SAP system update/upgrade. But it can also be used to apply Support Packages. SUM is somewhat more complicated to use, compared with the Support Package Manager, transaction s p a m , but it generates a much shorter downtime then SPAM.
Hint: In case downtime is a big issue and you have to apply many Support Packages, consider using SUM instead of SPAM.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
o Q a.
< a. w
to
Post activities
Downtime
Productive S U M 'sin g le m o d e ’ o O Q. to Productive
■
3 < £ <0 Downtime
Post activities
S U M ‘a d v a n c e d m o d e ’
Figure 165: Applying Support Packages with SUM
The SUM advanced mode uses a shadow system in which activities take place during the preparation phase, shifted from downtime.
O
Hint: For more details about SUM, see the next lesson dealing with SAP system update/ upgrade. Both, SPAM and SUM can be used for now and in the future. Both tools have scenarios in which they are the preferred choice.
Note: Both tools, SPAM and SUM, can be used to apply Support Packages. In most cases you would choose the SPAM, but you should choose SUM for applying a huge amount of Support Packages in downtime critical SAP systems.
SPAM C o ntraste d w ith SUM Table 16: Advantages of SPAM/SAINT and SUM The following list compares SPAM/SAINT with SUM:
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
SPAM/SAINT
SUM
•
Performs with easy handling
•
Performs with short downtime
•
Uses test mode (which shows modification preview)
•
Uses reset option that shows point of no return
•
Checks for SAP Notes (more precise)
•
•
Does not require SAP Solution Manager for Maintenance Optimizer (MOpz)
Checks available disk free space and database free space
•
Uses stack.xml for valid setup
•
Runs separately (outside SAP system)
•
Can restart SAP system and can switch the kernel
•
Works with third party add-ons unknown to Maintenance Optimizer (MOpz)
LESSON SUMMARY You should now be able to:
•
Apply Support Packages with SUM
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 7 Lesson 5 Implementing SAP Enhancement Packages and SAP System Upgrades
LESSON OVERVIEW This lesson explains how to plan for new, updated and upgraded functionality in SAP systems through a functionality implementation, a technical implementation overview, and an update/ upgrade to tools. LESSON OBJECTIVES After completing this lesson, you will be able to:
•
Plan for new, updated, and upgraded functionality in SAP systems
New F u n ctio n a lity Im p le m e n ta tio n
Hint: In the following text, the term update will be used instead of SAP enhancement package installation. An update and an upgrade are the same thing except they are based on different releases of the ECC system where they originate. If a release is ECC 6.0 and above, the procedure is called an update. If the start release is below ECC 6.0, the procedure is called an upgrade.
To start, recognize the need for an update/upgrade. Recognizing the need to update/upgrade can come from update/upgrade recognition trippers that are both operational and strategic. For example, on the operational side you may realize that you have a serious technical SAP system limitation within your current environment. At some point in time an SAP release reaches its end of maintenance. This means that SAP no longer delivers Support Packages that adapt your processes for legal requirements and correct errors. Refer to the Product Availability Matrix (PAM) in the SAP Service Marketplace for more details about release numbers and maintenance. New releases can contain many new functions that your company requires. New features that you might be interested in using can be added on the basis side (new administration tools) or on the application side (new and enhanced business functionality). The following factors are also important when deciding whether to update/upgrade: •
Costs - What will the update/upgrade cost me in total?
•
Payback/ROI - Will the update/upgrade have financial advantages for me?
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
Benefit - What advantages will the update/upgrade have?
•
Risks - Are there risks involved in the update/upgrade?
Change and improvements are integral parts of today's business environment. SAP supports and embraces the process of continuous change in the following ways: •
New SAP functions become available
•
Market technology changes
•
New business requirements are defined
Focus on the typical problem areas such as solution gaps. Assume you documented your initial implementation, one of the easiest things to evaluate during update planning is when any of the original gaps can be replaced by standard functions in the target release. Review each component of new release functions. Determine how these enhancements can add value to your company's operations. SAP system landscape 1 2
Upgrade project system
6
7
8
3 4
5
9 10 11 12
13 14 15 16 17 20 21 22 23 27 28 29 30
4 >
Temporary landscape Double mainten ; nee
Production landscape
DEV
Transfer
6.06
changes
e Figure 166: Updating or Upgrading a Three-System Landscape
Tasks in the PREPARE Phase
During an update/upgrade, the PREPARE phase performs the following verifications: Operating system update check Hardware check Database upgrade check Check for modifications Important Follow-Up Tasks in the Update/Upgrade Project
When performing an upgrade, do the following tasks on or after the upgrade: Perform a technical upgrade Adjust modifications
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
Backup system
•
Perform delta customizing
•
Set up new authorizations
•
Perform delta development
•
Perform quality assurance
•
Perform user acceptance tests
When planning the scope of an SAP system update or upgrade consider the following topics: •
Release Customizing
•
Modification adjustment and migration of modifications into SAP standard
•
Adaptation and testing of customer enhancements
•
Adaptation and testing of interfaces
•
End user training
•
Validation and testing of new releases
The biggest part of the upgrade project represents the adaptation of the current business processes to the new features of the new SAP system. There are not only changes to the customizing and the repository. There are also changes for the end users and how they will work with the new applications. When the development system has been update/upgraded to the new release it can still be necessary to develop bug fixes for the production system, which is still working with the start release. In addition to considering update/upgrade topics, there are additional technical update/upgrade process related issues provided in the following list: •
Hardware requirements on new release - server, front-end, and network
•
Sizing forecast and SAP system configuration for new release
•
Planning of OS, DB, and SAP system update/upgrade
•
Testing and validating of backup strategy for update/upgrade and on the new release
•
Performing technical update/upgrade on the whole SAP system landscape (transport landscape)
•
Post-update/upgrade activities including performance monitoring
Since the requirements of the new release are changing, you need a sizing forecast, which requires changes to the configuration. Finally, the whole environment is considered, for example, the server hardware, the client hardware, the network, the operating system, and the database. Test other software on the computer, especially when upgrading the operating system. For example, test the backup software. As a result of the new requirements, performance monitoring is more important after the update/upgrade. When deciding which SAP update/upgrade release you want to select, consider the following:
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
SAP's release strategy
•
IT costs for update/upgrade and maintenance
•
Cost for adapting business processes
•
Business requirements as compared with SAP functions
•
Costs versus Payback/Return On Investment
Note: When considering an update/upgrade of an AS ABAP- based SAP system, many aspects stated here depend on the activation of business functions. See the following information for details. An SAP system update/upgrade is more than just a technical update/upgrade. The update/ upgrade of an SAP system landscape should be executed as a project. A significant amount of planning and many steps are required to perform a release change for the SAP system landscape. Customer upgrade projects can last several months, update/upgrade projects last about half that time. Put thought into the following: •
Budgeting and resource planning
•
Revisions to the project in relation to other implementation/roll out activities
•
Availability of resources
•
End of maintenance for current release
Technical Im p le m e n ta tio n O verview
O
Hint: It is critical to read the SAP Notes concerning the update/upgrade before installing the update. If you do not do this step, your project is a serious risk for failure.
Tasks of Technical Update/Upgrades
Strategy and schedule - When planning the update/upgrade, anticipate decisions concerning the update/upgrade strategy. Plan an exact update/upgrade schedule before you start the project. Preparation - Meet certain requirements (software, hardware, operating system, and database) before you can update/upgrade the SAP system. Careful preparation of the update/upgrade is the best guarantee that it will run without errors. Start at the appropriate time - After you have performed the preparations, you can start the project. The prepare phase of the update/upgrade - The prepare phase of the update/upgrade automatically checks if your SAP system is properly configured for performing the update/
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
upgrade. However, perform many tests and actions manually before starting the update/ upgrade. During an update/upgrade, the prepare phase performs the following verifications: Operating system update check, hardware check, database upgrade check, check for modifications, inconsistencies check, and so on. •
Actual update/upgrade - Perform the update or upgrade.
•
Follow-up activities - Include all actions necessary for completing the update/upgrade. We recommend completing the actions in the order given in the update/upgrade guidelines.
Table 17: Technical Overview of the Update/Upgrade Steps
Where Information
Technical Steps
Step 1
SAP Solution Manager:
Provide in the Solution Manag er the technical usages and corresponding Support Pack ages, and other components, for example, SAP Enhance ment Package 6.
Selects target release
Step 2
SAP Notes - Pre-update/ upgrade steps:
See Update/Upgrade Guide: See SAP Note 1000009
Update/Upgrade Guide Pre-update/upgrade steps ASU Toolbox - Pre-update/ upgrade steps Step 3
Step 4
Step 5
SUM - Preparation steps SUM - Resolve negative checks SUM - Update/Upgrade De pending on the situation, SAPup sometimes is used instead of SUM. SAP Notes - Post update/ upgrade steps Update/Upgrade Guide Post update/upgrade steps ASU Toolbox - Post up date/upgrade steps
Roadmap steps 1- 5.4
Roadmap steps 5.5 - 5.8
See Update/Upgrade Guide: See SAP Note 1000009
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Note: In certain cases the tool SAPup is used instead of SUM.
Update/U pgrade Tools 5 .1 In it ia l iz a t io n
5 J E x t r a c t io n
5 .3
5 .4
C o n f ig u r a t io n
C hecks
5 .5 P r e p r o c e s s in g
5 .6 E x e c u t io n
5 .7
5 5
P o s t p r o c e s s in g F in a liz a tio n
Front end
Figure 167: Tools for the Update/Upgrade *•
Update/U pgrade Tools
SUM - Main update/upgrade tool that helps prepare the update/upgrade by checking for problems and configuring the software components for the update/upgrade and performs the actual update/upgrade. In certain cases, SAPup is used instead of SUM. SUM or SAPup simplifies the operations for the update/upgrade by providing a multifunctional user interface. Both SUM and SAPup have a front-end monitor for the update/upgrade that shows the progress of the current roadmap step. Several tools help perform the update/upgrade. They are part of the following technical update/ upgrade process: •
The main update/upgrade tool for an SAP enhancement package installation is the SUM (Software Update Manager). In certain cases, the tool SAPup is used instead.
•
The PREPARE part of SUM has to run before installing the SAP system update/upgrade. Repeat this step repeatedly, until it is error-free. The error messages are written to the log file checks.log. Checks are performed on the source release. For example, if the source release of the SAP system, the database, and the operating system are sufficient for this update/upgrade. That is, if there is enough space in the database available and if no modified SAP objects are unreleased transport requests, then these processes can be run.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
SAP enhancement package, Support Packages, and add-ons are collected for binding to the update/upgrade process. This step is important. If you, for example, do not bind enough Support Packages to the update/upgrade, this action will result in a loss of data during the SAP system update. If you do not maintain your add-ons, the whole SAP system can become unstable and inconsistent. Furthermore, tools are imported in the source SAP system that are needed for the SAP system update. •
Transaction i c n v (incremental table conversion) - This transaction is one of the tools imported by the PREPARE part of SUM. With each new release, the structure of the tables in the database changes. Depending on the changes in the table structure, a table conversion may be necessary. These table conversions occur during the update downtime (such as, phase PARCONVJJPG). By using i c n v ,you can convert many of these data records before downtime, during the production usage of the SAP system.
•
With the SUM front end, the update process runs independently from a dedicated front end server. You can control and monitor the progress of the update from a number of different places. SUM provides optimal support for a remote update. It provides an alert mechanism that lets you start an external program (for example, sending an SMS to your mobile) when it breaks down.
•
The SUM monitor lets you monitor the update/upgrade.
•
Transaction SGEN - With the new release, 100% of all ABAP programs of the new software components are exchanged. They are delivered in their source code, but not with their load. Delivery without their load is not possible because the load depends on the local environment (operating system and hardware). When you call a program the first time, its load is automatically generated when it does not already exist. This step may, however, reduce production system performance for some time after the update/upgrade. To avoid this problem, you can use transaction s g e n to generate the loads.
Hint: If there is time left in your downtime window, generate the loads directly after the update/upgrade.
LESSON SUMMARY
You should now be able to:• •
Plan for new, updated, and upgraded functionality in SAP systems
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 7 Lesson 6 Reviewing Phases in the Technical Implementation of an SAPSystem Update/ Upgrade
LESSON OVERVIEW
This lesson describes the phases in the technical implementation of an SAP system update or upgrade. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Describe the technical phases of an SAP system update/upgrade
Phases in the Technical Implementation
Old Release
Preparation Steps
Upgrade Steps
Imports
P ost-activation
•
•
• • • ■ • ■ • • •
• •
•
Transaction
• •
Manual actions PRD: delta transports*
Apply SAP Notes*
. ■ •
EUJMPORT (upgrade only) RUNRSDBSCPY (update only) RUN_RDDIT006 DIFF
Transaction SPDD* ACT UPG PARDIST_SHD Transaction ICNV* SHAXWJMPORT MODPROF TRANS EU SWITCH PARCONV_UPG PMVNTABJJPG
TABIM XPRAS
SPAU'
* Manual Figure 168: Phases of an SAP System Update/Upgrade
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Phases of an SAP System Update or Upgrade
•
EUJMPORT - Import of the new repository (as a shadow repository) from the upgrade DVDs (only for upgrade)
•
RSDBSCPY - Import of the new repository (as a shadow repository) as copy of the old repository (only for update)
•
RUN_RDDIT006 - Calculates the delta between a standard repository and the special repository of the SAP system to be updated/upgraded
•
DIFF - Coping of all modifications, own development, bounded Support Packages, and add-ons to the shadow repository
•
ACT_UPG - Activation of table definitions in the shadow repository
•
PARDIST_SHD - Parallel distribution of table definitions in the shadow repository
•
SHADOWJMPORT - Import of new tables that do not harm the production running SAP system
•
MODPROF_TRANS - Beginning of downtime
•
EU_SWITCH - Switching to the new repository (the shadow repository) and switching to the new kernel
•
PARCONVJJPG - Parallel conversion of table structure
•
PMVNTABJJPG - Parallel move nametab of table structure
•
TABIM - Import of new data (standard customizing, language dependent text elements, and so on)
•
XPRAS - Restructuring of business data
The start of the update/upgrade process involves the transfer of new data to the SAP system. Repository objects of the are imported into the SAP system, and the customer objects are For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
compared. All repository objects that have been modified by customers are compared to the new SAP standard during this update/upgrade process. To avoid loss of data and table fields that customers may have created, merge conflicting structures before the mass activation of dictionary objects in the update/upgrade process. If objects require adjustment, use the transactions s p d d and s p a u / s p a u _ e n h . All modifications made by customers are then merged with the new SAP object versions to retain data. Otherwise, the new SAP version will be activated and data may be lost. The SAP system is available during the activation phase. The activation takes place via the shadow instance through the shadow system in the shadow repository. When the update /upgrade completes successfully the SAP system will be running at the new release level. Customer-developed objects and modifications have been preserved.
Hint: The two transport requests from s p d d and s p a u (one from s p d d and one from S p a u ) can be included (not imported) into the update/upgrade of the subsequent SAP system in the same SAP system landscape. By doing this step, the modification adjustment is performed automatically in this subsequent SAP system. You only have to adjust those objects manually that were modified in the subsequent SAP system, but not in the SAP system you performed s p d d and s p a u . The ABAP Dictionary objects (tables, data elements, domains, and so on) are adjusted during production operation, before the activation of the ABAP Dictionary. The adjusted objects are collected in a transport request. You do not release this transport request. Instead, mark it for export in transaction s p d d . Towards the end of the update/upgrade, SUM exports this transport request into the transport directory, and then registers it for transport in the file \bin\umodauto.1st. Non-Dictionary repository objects (reports, screens, and so on) are adjusted towards the end of the update during downtime. At this stage, the import of SAP objects has already been completed. However, the previous, modified version is still available in the version database. As with ABAP Dictionary objects, all adjustments are released to a transport request that is flagged and then exported and registered by SUM.
Hint: Do not attempt to import adjustment transport requests into the SAP system manually during s p d d . This step can lead to a loss of data. Do not activate any objects during transaction the modification adjustment.
spdd.
Activation is carried out automatically after
After you have completed the update/upgrade phases, you have a maximum of 14 days to execute transaction s p a u without a key check (SAP Software Change Registration, SSCR) for the objects that you changed. For more information, see the upgrade manual and online application help for
spdd/ spau
.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
SAP Enhancement Packages Performing an SAP system update and is almost indentical to performing an SAP system upgrade. But there are some differences in handling the update project. Most new business functions are delivered inactively when performing an update or upgrade. This results in a major difference when performing an update. When performing an update most business functions are not changed compared to the old release. However, when performing an upgrade they are different compared to the old release even if they are not activated.
Hint: The major difference between an update and an upgrade is the delta between the old and the new releases.
Example: SAP Enhancement Package 6 for SAP ERP6.0
SAP_ABA SAP_BASIS SAP_APPL SAP_HR EA-APPL EA-HR IS-UT 606, IS-OIL Portal Content XSS
SAP ECC 6.0
SAP ERP
731 731 606 604 606 606 606 J 161 633
SAP ECC SAP ERP 1 SAP Portal SAP ERP SAP XSS
SAP ECC 6.06 EHP 6
Figure 170: SAP Enhancement Packages
SAP Enhancement Packages figure Note the following about the figure SAP Enhancement Packages: •
Because industry solutions ISJJT and IS_01L are not used, and XSS and SAP portal system do not exist in this SAP ERP landscape, these components are not imported.
•
Only a new business function in SAP_HR is required and activated. The functions SAP_ABA and SAP_BASIS are imported and active regardless.
An SAP system upgrade exchanges all software components of the old release with software components of the new release. An SAP system upgrade changes 100% of the repository. An SAP enhancement package only contains some new software components. When performing an update, the SAP system administrator and the business departments decide, which software components delivered by the SAP enhancement package must be applied. These packages being applied are all existing software components used in this SAP system.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
The mere application of an SAP enhancement package’s software components does not change functionality within an SAP ECC 6.0 system. The new functionality is hidden behind switches. The switch framework has an advantage over an SAP system upgrade — test and reimplementation efforts are required only when activating the business functions that must be used.
Hint: SAP enhancement packages are not SAP enhancement packages only (for example SAP ECC 6.0). They are enhancement packages for SAP ERP 6.0. This means that they contain components of several different ERP systems, such as an ERP ECC system, an ERP Portal system, an ERP BW system, an ERP XSS system, and so on.
SAP enhancement packages are available for the SAP solutions SAP ERP, SAP CRM, SAP SCM, and SAP SRM.
Hint: For detailed information look at http://service,sap.com/erp-ehp or crmehp or scm-erp or srm-ehp.
A
Caution: The SAP enhancement packages for SAP NetWeaver are not switchable. Applying an SAP enhancement package for an SAP NetWeaver system has the same result as upgrading the SAP system. The same applies for all AS Java-based SAP systems.
LESSON SUMMARY
You should now be able to: •
Describe the technical phases of an SAP system update/upgrade
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 7 Lesson 7 Activating Business Functions with SAP Switch Framework 5
LESSON OVERVIEW
This lesson provides an overview of SAP Switch Framework 5. LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Activate business functions using the SAP Switch Framework
SAP Switch Framework 5 The Switch Framework is a technical framework residing in the ABAP stack of SAP NetWeaver 7.0. It controls which development objects are active in a system. Each ABAP package can be assigned to switch. The switch settings determine whether a development object that belongs to a switched package is active. Elements of a standard development object may be switched as well. If a package is not assigned to a particular switch, it is considered a standard ERP package. The main purpose of the Switch Framework is to simplify an ABAP-based system landscape by adopting one or more industry solutions in a standard system. The Switch Framework allows you to externally control the visibility of repository objects or their components by means of switches. By using the Switch Framework, all industry solutions and a restricted list of repository objects are delivered in an inactive state in the system. With minor exceptions, you no longer need to install an industry solution - you can activate it when required. - S w itc h fr a m e w o rk : D is p la y B u s in e s s F u n c tio n S ta tu s
DCC
{ l Chet*Charges
fi?C'i:pl:iA:t«afi:
.2 SMik i F tr-urw i B'tw;oi
r#:
Bjrau Furdisn Jr
Des * • • • • • • • • • •
rnTri*'f>?r_r-'Trr«sc.«3 A :fClMMW4 AftUFAWJION <3 EACP A eacfp 4 EAFIN A EAFRC 0 FATS A EACH.T A (AM* A EAlCM
• 4 iecvu*«c
• • • • • • • • •
4 g 4 4 4 4 4
lBEVUAE_BT.Ecr g IPROffNC.DOCe.CC g iWOfMtC.lHXM.FIJLMS g flPRC*F't .DOC0.VYORD2CO7
Dot
a o
D !Aw fcr«l(F l.(i(S ta .iilr fin rtiW tfanuoi f0>C Regiiatory Rtponng
•A-tws®
■ <5 EAPLM • A EARS • >5 FARFT ■ 4 EA8CW • 4 CATRV ■ 4 J-A • LjtMlkW*'M»J»J«M«:iSI_»Ut4C'IO*4B • g IECV*A6'_0UERV • 4 IECV.94AP* • 4 iSCVNAtt 1 • g lE c v iM w c .s c e w e .
MCt
Aitou'fl-g iwi«!Nniim C(rUat Vlawar Eaw X tri I Ct r i e d m i n *pciic I CO'DBl VUMDI Mitfl I JCEMf.. I Ar.ti«rgtaF>«rOuumLI>I.C'~pti>« R*tU' I f .mlttna npro'Mmtts in MMto' Eu anc I C>Tp*r>t**Lni» AitrwngiFUrrenrle) I Artfiatig ftn Cup:l $to» 0 » M n I DataDdurga EnaAiawprrtotD30 0:
i I | ( I i
9 9 9 9 9 9 9 9 9 9 9 9 9 9 9
Re)»
R«l»
AppKMcn Cscrponent
T u t.
AtbraMdon
911 2014 1904 27
a
9
SAP
SI-PI EAAPPL EAD£P3 EAF N EAFIN FAFNSFRV EA TRADE EAFtORKK EAV>PL
I 2014 1904 27 1.2014 19 04 27 1 70141904 27 911 2014 19 04 27 014 1904 27 1911.2014 19 04 27 014 1904 27 911 2014 19 04 27 0141904 27 I 7014 1 14 27
BARREL EAA»PL EAPS F*.RFTAI EA4PPL CAH9CKX EAFN
SfaP_BE_F«
CAAYl
CAE®T-8CV CAE^T-BCV CAFPT-UCV CAE°T0CV MAfVR-CM
EAAPPL
MMPLfJEW
EAAPPL EAAPPL EAAPPL EAAPPL EAFiNSCRv 8AP.BE.F*C SAP.Bk.F"® SAP.BE.F^C
PM-VWX-MO LE-D3D LE-D3D LE-D3D LEDED FS-R9D CA0TFC06 CAOIMX7S CA0TF-C06
S'P.BE.F'C SAP BF Fft: HAP.BE_F«C
l*«Wl
0 SPWS * 1*0771 tie
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
To make the switch framework handling easier and to better group the individual switch settings, SAP has introduced business function sets and business functions. A business function set corresponds to an industry solution. Each business function set is a group of business functions, and each business function group consists of a set of switch settings. By means of business functions, several industry solutions (represented by different business function sets) may share a common set of business functions with identical switch settings. The Switch Framework is integrated in the ABAP Workbench and works closely together with the Enhancement Framework. The fact that the enhancement implementations of the Enhancement Framework can be switched is an important aspect of the Switch Framework. Therefore, the Enhancement Framework and the Switch Framework are closely coordinated and complement one another in their functions. This is evident when getting new functionality through the implementation of an Enhancement Package. The Switch Framework controls which enhancement implementations are to be performed. Directly after the import the system behaviour has not changed, because the imported sources that realize the new functionality are still not compiled and must be first switched on. You can thus choose only the parts you are interested in. With the use of the Enhancement and Switch Frameworks, you can change SAP standard objects with the flexibility allowed by modifications, but without modifying these objects. The Switch Framework enables you to enhance or change a component and retain the original component as well as the enhancements/changes in the same system. You can then decide whether to work only with the original component, or with the original component and one of the then activated enhancement components. With enhancements you avoid most of the work that modifications cause in the software lifecycle. Enhancements are never overwritten in an upgrade, because they are objects in your namespace, while modifications are part of the object they modify. So with enhancements, you have most of the advantages of modifications, while enjoying a freedom from most of the work that modifications require in an upgrade. With the Switch Framework you can use switches to control which Repository objects are active at runtime. Deactivated Repository objects are not compiled and at runtime. The benefits of this approach are: creation of enhancements avoids modifications and helps to save cost and effort: enhancements are very flexible and can be switched via the Switch Framework; customer individual development of switches possible. LESSON SUMMARY You should now be able to: •
Activate business functions using the SAP Switch Framework
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 7
Learning Assessment
1. The Note Assistant can be used for changing programs and DDIC objects. Determine whether this statement is true or false. | True False 2. We recommend to create the maintenance certificates automatically with SAP Solution Manager. Determine whether this statement is true or false. | True False 3. Before using the Support Package Manager, you should patch the tool by applying a SPAM/ SAINT update. Determine whether this statement is true or false. | True False 4. Support Packages of one component can be imported in any order. Determine whether this statement is true or false. | True False
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
5. If you have to apply many Support Packages when downtime is a major issue, use SPAM instead of SUM. Determine whether this statement is true or false. | True False 6. Which of the following tools can be used to perform an update or upgrade in the SAP environment? Choose the correct answers. | A PREPARE B SUM | C SAPup D Transaction STMS E SAPinst 7. Activate objects during SPDD, activation is not carried out automatically after the modification adjustment. Determine whether this statement is true or false. | True False
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 7
Learning Assessment - Answers
1. The Note Assistant can be used for changing programs and DDIC objects. Determine whether this statement is true or false. | True \x \ False
2. We recommend to create the maintenance certificates automatically with SAP Solution Manager. Determine whether this statement is true or false. [x ] True False
3. Before using the Support Package Manager, you should patch the tool by applying a SPAM/ SAINT update. Determine whether this statement is true or false. [x ] True False
4. Support Packages of one component can be imported in any order. Determine whether this statement is true or false. | True \x \ False
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
5. If you have to apply many Support Packages when downtime is a major issue, use SPAM instead of SUM. Determine whether this statement is true or false. | True \x \ False
6. Which of the following tools can be used to perform an update or upgrade in the SAP environment? Choose the correct answers. | A PREPARE \x \ B SUM \x \ C SAPup D Transaction STMS E SAPinst
7. Activate objects during SPDD, activation is not carried out automatically after the modification adjustment. Determine whether this statement is true or false. | True \x \ False
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
UNIT 8
Advanced User AcIministi'ation Topics
Lesson 1 Implement Central User Administration (CUA)
408 427
Exercise 17: Distribute User Data with CUA
UNIT OBJECTIVES
•
Explain Central User Administration (CUA)
•
Set up Central User Administration (CUA)
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected] 407
© Copyright. All rights reserved.
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 8 Lesson 1 Implement Central User Administration (CUA)
LESSON OVERVIEW
This lesson introduces the principles of Central User Administration (CUA) and provides decision making aids. The lesson also covers the required steps to set up CUA. Business Example
In your landscape of SAP systems, the same users exist in a number of systems and clients. You want to reduce the costs of maintaining users in the different SAP systems. In addition, you want the user administration of the SAP systems in your company to be organized more efficiently and clearly. To do this, you need to implement CUA. For this reason, you require the following knowledge: •
An understanding of the fundamentals of CUA
•
An understanding of the usefulness of CUA for your company
•
An understanding of how to set up CUA
•
An understanding of how to distribute user data with CUA
LESSON OBJECTIVES
After completing this lesson, you will be able to: •
Explain Central User Administration (CUA)
•
Set up Central User Administration (CUA)
Fundamentals of CUA User information is stored in a client-specific manner in SAP systems. This means that every client in a system has its own, independent group of permitted users. If you have a complex system landscape in your company, you might have more than one of the three standard system types (Development (DEV), Quality Assurance (QAS), and Production (PRD)). Hint: For example, there are three SAP production systems: an SAP Supply Chain Management (SAP SCM) application for production planning, an SAP ERP Central Component (SAP ECC) as an ERP production system, and an SAP Customer Relationship Management (SAP CRM) system. These systems are regarded as PRD systems. The users are maintained in the respective system and client. If, for example, a developer retires from your company, you must ensure that the relevant user record is removed from all affected For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
clients. You must ensure that the relevant user is locked. If you do not know exactly in which areas your colleague worked as a developer, you need to log on to every single client that he or she may have used, and manually search for and remove the user (colleague). In complex landscapes, this task becomes confusing. This may lead to potential security gaps in your user administration and can result in significant costs for consistent user maintenance.
Note: Users that are no longer to be used for logging on to the SAP system should be locked and not deleted.
Classic User Administration
SAP ECC
SAP ECC
SAP ECC
Client 100 Client 200
Client 100 Client 200
Client 100
QAS
PRD
SAP SCM Client 500 Client 550
DEV
The users are administered individually in each client Figure 172: Classic User Administration
The figure shows the structure of user administration in a classic scenario with multiple SAP systems. As you can see from the figure, the number of interesting clients (that is, clients other than 000, 001, and 066) to be administrated is 17, even in this simple example. The clients shown are used for different purposes. For example, client 200 is not required in the production system of the SAP ECC system, because it is a test client. Central User Administration (CUA) The aim of CUA is to reduce the cost of user administration and to make user administration more secure by centralizing the work. CUA envisions only a single client for maintaining user data. Therefore, to administer user data using CUA, you need to determine where you will be maintaining your users in your system landscape. To determine user data using CUA, the following points need to be defined:
Which user master records exist in which clients?
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
Which roles and profiles are assigned to these master records?
•
What are the initial passwords?
•
Is the user locked or not?
Prerequisites for Efficient CUA Implementation The prerequisites for the efficient implementation of CUA are as follows:
•
There are a large number of identical users in multiple clients.
•
There is a complex system landscape with a large number of clients to be managed.
•
You want to reduce the cost of complex, distributed user administration by implementing CUA.
These prerequisites should exist in your system landscape before the implementation of CUA, otherwise, the work reduction due to the implementation of CUA will not be optimal. However, these prerequisites are not entirely self-explanatory. For example, if you have a standard threesystem landscape in which each user primarily works in one client, and the user groups in the different clients are entirely different, the cost saving due to the implementation of CUA is not particularly large. The situation is similar if you use identical users in multiple clients, but your system landscape contains only a few clients or the number of administered users is not high.
Hint: CUA can also simplify user administration in small system landscapes. This is because the user master records are then only administered in one client of your system landscape, which is clearly laid out. This increases the security of the systems that you administer.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
User Administration Using CUA AS ABAP
AS ABAP
Central System Client 050
Central System Client 050
Figure 173: User Administration Using CUA - An Example
The figure shows all the work you can perform related to user master records from one central client when you implement CUA. In this example, two CUA landscapes are used to administer users in production and test systems, and the development systems are not managed as part of CUA. CUA resides in a dedicated system. Using CUA, you can distribute the following information from the central system to the child systems by using the ALE technology. The information is about which users exist in which system, in which client, with which roles, and profile assignments. You can also distribute the initial password. You can also distribute the initial password.
O
Hint: ALE is a powerful tool. Only a small portion of its many possibilities can be explained in the context of CUA.
Notes on Implementing CUA The following list contains im portant notes for implementing CUA:
CUA can be implemented using a system running at least SAP Basis 4.6C and above. Your system should be as up to date as possible, with the latest Support Packages and kernel patches.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
•
CUA can be used cross-release, although a linked system must have at least SAP Basis 4.5B (and should also have as current a Support Package status as possible).
•
CUA can also be used, for example, for user administration in SAP NetWeaver Business Warehouse (SAP NetWeaver BW), SAP CRM, and SAP Suppliers Relationship Management (SAP SRM) systems. However, you must refer to SAP Notes about this topic before implementing CUA.
In an ALE integrated system, SAP and non-SAP systems may need to communicate with each other. The systems linked to each other are called logical systems. The logical systems in the context of CUA are actually the clients where users need to be maintained. A single SAP system can house multiple logical systems in terms of ALE (and CUA). Data exchange in an ALEintegrated system is performed by exchanging intermediate documents (IDocs) by Remote Function Call (RFC).
A
Caution: Ensure that if CUA is in use and role definitions are transported (by means of transport requests from one system to another), the user assignments to the roles should not be transported. If CUA is in use and role definitions, including user assignments, are transported at the same time, discrepancies may arise in the user assignment to roles. You can avoid these problems as described in SAP Note 571276: PFCG: Transporting roles using transaction SM30 by setting the entry USER_REL_IMPORT in table PRGN_CUST to NO in all the child systems in CUA.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
CUA - Step by Step
Name the logical system s then assign the log. system s to clients
C reate the n ecessary technical users of type "system " w ith appropriate au thorizations
C reate RFC connections
Transactions BD54 and SCC4 in all systems Transactions SU01 and PFCG Transaction SM59
1 Configure and activate CUA (distribution model and partner profiles are generated im plicitly)
Set the p aram eters fo r field d istribution
C onfigure IDoc Processing
Transaction SCUA Implicit: transaction BD64, WE20
Transaction SCUM (See the notes in the handbook)
Synchronize the com pany addresses then tra n s fer users to CUA
Transaction SCUG
Check d istribu tion logs
Transaction SCUL
Figure 174: Roadmap for Setting Up CUA
The figure shows the steps to set up CUA.
Note: The term "technical users, refers to technical users in terms of user classification for system measurement. In this case, the class of technical users represents users for whom no license fees are charged. The technical users that are used for CUA are of the type System (created in transaction suOl), although the documentation and SAP Notes sometimes refer to users of the type Communication. However, this recommendation is out of date because users of the type Communication, unlike users of the type System, are subject to password change rules.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
Specify and Assign Logical Systems
Caution: In this section, only the terms “central system" and “child system" are used. These terms refer specifically to clients (logical systems). Therefore, if your company runs the central CUA and child CUA on the same SAP system (in different clients), the terms “central system" and “child system” refer to different clients in the same SAP system.
You can specify and assign the logical systems as follows:
1. Log on to your central system with an administration user ID. 2. In the Implementation Guide (transaction s a l e ), choose Basic Settings —> Logical Systems — y Define Logical System or run transaction B D 5 4. Alternatively, you can maintain table view V_TBDLS using transaction SM 30. 3. Choose Edit —> New Entries. 4. In the Log.System column, create a new logical name in uppercase letters so that you can easily identify systems by their names later. The naming convention for the logical system names is < S i d > c l n t # # # . where you replace with the relevant system ID and # # # with the relevant client number, for example, d e v c l n t i o o . Enter the name of the logical system, such as central system or child system. 5. Save your entries. These entries are then included in a transport request. 6. Create the logical system name of the central system and relevant child name in all the child systems. For this step, you have the following options: •
Send the transport request generated in step 5 (which contains the names of all logical systems) to all other systems in CUA.
.
Perform steps 1 to 4 in all the child systems of CUA. Create the logical system name of the central system and relevant child system in each case.
Hint: The data for the logical systems is created cross-client. If there are multiple logical systems of CUA in one SAP system, you need to perform steps 1 to 5 (or import the transport request) only once.
You can also use transaction s a l e to assign the logical systems. To do so, choose Basic Settings —> Logical Systems —> Assign Logical System to Client or run transaction SCC4 directly. Alternatively, you can edit table T000 using transaction SM 30. After you switch to the change mode, you can assign an appropriate entry to the field Logical system in the detail view of the client attributes. When doing so, use the input help (F4 help) to avoid input errors. Select the appropriate entry, such as DEVCLNTIOO, if you want to assign this
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
logical system to client 100 in the DEV system. Make this assignment of logical systems for all the clients involved in CUA (in all of the involved systems). Technical Users and RFC Connections
RFC connections are used to exchange data by ALE in the context of CUA. RFC connections are used to distribute user data from the central system to child systems, to send changes to this data in the child systems, and to send status reports back to the central system. In the context of CUA, the central system is treated like another child system in some respects. In the simplest case of CUA (two logical systems linked to each other, one central system and one child system, within the same SAP system), two RFC connections are required. If the central system and child system are in different SAP systems, three RFC connections are required. The RFC connections required are as follows:
•
RFC connections from the central system to itself (loopback)
•
RFC connections from the central system to the child systems
•
RFC connections from the child systems to the central system
RFC Connections from the Central System to Itself (Loopback)
A separate, additional RFC connection is required to connect the central system to itself. Special users are used for these RFC connections. These technical users are of the type System and their authorizations are clearly delimited using predefined roles.
Note: For more information about CUA minimum authorizations for communication users, see SAP Note 492589. The composite role SAP_BC_USR_CUA groups together the various roles for service users of CUA. The composite role is used only for documentation purposes. The single roles that it contains are assigned directly to the service users.
RFC Connections from the Central System to the Child Systems
RFC connections are required from the central system to all the child systems. These RFC connections use the users in the child systems. The naming convention recommended for these users is c u a _ < s i d > _ # # # . where is replaced with the system ID of the child system and # # # with the number of the client being addressed in the child system. This user also requires authorizations that are contained in the roles SAP_BC_USR_CUA_SETUP_CLIENT and SAP_BC_USR_CUA_CLIENT. However, you should not assign the delivered SAP roles to the technical users, but rather copies of these roles for which you have created authorization profiles with role maintenance (transaction p f c g ). For simplicity, name the copies of the SAP roles by adding Z_ to the start of the name, that is, Z_SAP_BC_USR_CUA_SETUP_CLIENT and Z_SAP_BC_USR_CUA_CLIENT.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Hint: Note that the technical user in the child system requires the role Z_SAP_BC_USR_CUA_SETUP_CLIENT only while you are setting up CUA. You can then remove this role from the technical user.
Hint: To increase the security and performance of your system, you can use the role Z_SAP_BC_USR_CUA_CLIENT in a shared way. This role contains the authorizations required to receive the IDocs of CUA and update them. However, the subrole Z_SAP_BC_USR_CUA_CLIENT_RFC (create this in the same way as the roles described earlier) contains only authorization to receive the IDocs. Furthermore, the role Z_SAP_BC_USR_CUA_CLIENT_BATCH contains the update authorization for the inbound IDocs. Assign the first role Z_SAP_BC_USR_CUA_CLIENT to the technical user. However, you assign the role Z_SAP_BC_USR_CUA_CLIENT_BATCH to a system user to allow the user to change user master records. This user is used (in the child systems) to schedule a periodic background job that implements the CUA changes in the child systems (periodically).
RFC Connections from the Child Systems to the Central System
RFC connections are also required from the child systems to the central system. Every child system must be able to open an RFC connection to the central system.
Hint: Because RFC connections can be used cross-client (all clients of a system can use a shared RFC connection), you need to create only one RFC connection to the central system if there are multiple child systems in one SAP system. The connection from the child system to the central system uses a technical user of the type System that must be known in the central system. This user should have the ID c u a _ < s i d >. In this case, stands for the system ID of the child system that communicates with the central system using this user. This user requires authorizations for the roles Z_SAP_BC_USR_CUA_SETUP_CENTRAL, Z_SAP_BC_USR_CUA_CENTRAL, and Z_SAP_BC_USR_CUA_CENTRAL_BDIST. Create the roles by copying the template roles (the template names have the same names as the specified roles, but without Z_ at the start of the name) and generating the profiles for them using transaction p f c g . The first role listed, Z_SAP_BC_USR_CUA_SETUP_CENTRAL, is required only while setting up CUA.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
A A
Caution: The role Z_SAP_BC_USR_CUA_CENTRAL_BDIST is required by the user in the RFC connection if the attributes in transaction s c u m are set to Redistribution.
Caution: In addition to the RFC connections from the child systems to the central system, you also require an RFC connection from the central system to itself (loopback). This connection also uses the user with ID c u a _ < s i d >, where is the ID of the central system. The required authorizations are contained in the roles Z_SAP_BC_USR_CUA_SETUP_CENTRAL, Z_SAP_BC_USR_CUA_CENTRAL, and Z_SAP_BC_USR_CUA_CENTRAL_BDIST.
Required RFC Connections and Technical Users for CUA
CUA Central System: SAP System CXY Cross-client RFC destinations for RFC connections to child systems and loopback: CXYCLNT100, DXYCLNT200
Logical system CXYCLNT100, CUA central system
System users: CUA_CXY with the password A and the roles Z_SAP_BC_USR_CUA_SETUP_CENTRAL:
Z_SAP_BC_USR_CUA_CENTRAL and Z_SAP_BC_USR_CUA_CENTRAL_BDIST CUA_DXY with password B and the same roles
RFC destination DXYCLNT200 User CUA_DXY_200. password C
RFC destination CXYCLNT100 User CUA_CXY, password A
RFC destination CXYCLNT100 User CUA_DXY, password B
CUA Child System: SAP System DXY Cross-client RFC destination for connecting to the central system: CXYCLNT100
Logical system DXYCLNT200, CUA child system
System users: CUA_DXY_200 with password C and the roles Z_SAP_BC_US R_C UA_SET U P_C LI ENT and
Z_SAP_BC_US R_CUA_CL IENT
The two roles printed in bold: Z_SAP_BC_USR_CUA_SETUP_CENTRAL and Z_SAP_BC_USR_CUA_SETUP_CLIENT
are required only to set up the CUA
Figure 175: Required RFC Connections and Technical Users for CUA
The figure shows the required RFC connections and technical users as well as the roles they require in a very simple CUA scenario.
Hint: For background information about the required authorizations and roles delivered by SAP in the CUA environment, see SAP Note 492589 - CUA: Minimum authorizations for communication users..
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
After you create the users (as shown in the figure) with the appropriate role assignments in all of the clients involved, you need to define only the RFC connections in transaction SM59. You can do so by performing the following steps:
1. In transaction s a l e in the central system, choose Communication —> Create RFC Connections (transaction SM59). 2. Choose the Create pushbutton. 3. Enter the following data in the respective fields: Field Name RFC Destination
Value For example, QASCLNT200 or (this entry must be in upper case letters)
d e v c l n t 200
Connection Type
3
Description
Connection to child system
A
Caution: The RFC destination name must be identical to the logical system that you want to address with the RFC connection. The RFC connection must be specified in uppercase letters.
4. Press the Return key. On the Technical Settings tab page, make the following settings: .
If you want to restrict the function of CUA to a particular server group, you can specify the logon group after selecting the Load Balance: Yes radio button and choosing the Return pushbutton.
•
If you do not want to use load distribution, specify the name of the host on which the central instance of your target system is running as Target Host and specify the instance number of the central instance.
5. On the Logon & Security tab page, specify the client of the required logical system and the technical user c u a _< s i d >_### (for example, c u a _ q a s _200 or c u a _ d e v _200) and password (in your training course, this password is specified by the instructor before the start of the course). 6. Save this connection. 7. Choose Utilities —*■ Test —*• Connection Test (CTRL + F3) and Utilities —► Test —> Authorization Test (CTRL + F4) to test the connection using the functions. To set up the required RFC connection from the child system to the central system, log on to the child system and perform steps 1 to 7 again. Use the user c u a _< s i d >, where is the system ID of your child system. You should also set up the RFC connection from the central system to itself.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Note: You can also use trusted RFC connections for the CUA communication. This increases the security of your CUA communication further. For information about configuring CUA using trusted RFC connections, see the online documentation.
CUA Activation
After you successfully activate CUA, you will no longer be able to create users in the linked child systems using transaction suoi. Before you activate CUA, it is still possible to create new users using transaction suoi in a child system. The activation of CUA has been significantly simplified and a number of necessary configuration steps are performed automatically by the system. To perform the CUA activation, follow the steps below:
1. Log on to the central system. 2. Access the Implementation Guide (transaction s a l e ),choose Modelling and Implementing Business Processes —> Configure Predefined ALE Business Processes —*• Cross-Application Business Processes —> Central User Administration —> Select Model View for Central Administration (transaction s c u a ). 3. Enter the name of your distribution model, such as CUA. 4. Choose Create. 5. Enter the names of all the child systems to be connected in the Recipient column. 6. Save your entries. 7. The result screen Display logs appears. If you expand the nodes for the individual systems, you see the following message for each system: ALE distribution model was saved Central User Administration activated Text comparison was started
Note: If problem messages are displayed here, follow the procedure in SAP Note 333441 CUA: Tips for problem analysis.
CUA Configuration When CUA is activated, the system carries out the following configuration steps automatically:
1. The corresponding ALE model is created or adjusted to match the new CUA model if changes have been made.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
2. Partner profiles are created in the system. 3. Text comparison with the child systems is carried out for roles (and profiles). The ALE distribution model defines which applications communicate with each other in the distributed systems and which data types are distributed. You require a separate ALE distribution model for CUA. In the central system, you define the structure of your CUA in the model view, which you then distribute to the child systems. In the ALE distribution model to be defined for CUA, the following types of data are distributed:
•
User master data (including assigned roles and profiles)
•
Company addresses
In the distribution model, two methods are required to distribute user data and company addresses. To implement these methods, the distribution model uses the Clone method from the Business Application Programming Interfaces (BAPIs) of the USER and User Company Business Objects. You can view the partner model in transaction BD64. Partner profiles define the conditions for electronic data exchange through the IDoc interface. If a partner profile does not exist, you cannot communicate with the partner through the IDoc interface. You can display these partner profiles in transaction WE20. The check tables and texts for roles, profiles, and license data in the individual child systems are saved temporarily in the central system. This means that they can be displayed quickly. If they have been changed, you have to run the text comparison. If you run the text comparison in the central system, you can select the child systems from which the data is to be read. If you run the text comparison in a child system, the current data is sent to the CUA central system.
Hint: The functions of transaction s c u a have been improved through Support Packages. For more information, see SAP Note 952349.
A
Caution: Even if users can no longer be created in the child systems, CUA is fully operational only after the steps have been carried out.
Parameters for Field Distribution
For each field of transaction suOl, you can use transaction which the field content can be administered.
scum
to determine the system in
The parameters to maintain for field distribution are as follows:
•
Global
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
You can maintain only data in the central system. The data is then automatically distributed to the child systems. The values for the corresponding fields cannot be changed there; the values can only be displayed. •
Local You can maintain only data in the child system. Changes are not distributed to other systems.
•
Proposal You have maintained a default value in the central system that is automatically distributed to the child systems when you create a user. After distribution, the data is maintained only locally and is no longer distributed if you change it in the central or child system.
•
Redistribution (Redist) You can maintain the data both centrally and locally. Every time the data is changed, the change is distributed back to the central system and is then forwarded from there to the other child systems.
•
Everywhere (Evrywhr) You can find this option only on the Lock tab page and for initial passwords (the Logon Data tab page). You can maintain initial passwords and lock data both centrally and locally. However, only the changes made to the data in the central system are distributed to the other systems. Local changes in child systems are not distributed.
A
Caution: If you subsequently change the distribution from Local or Proposal to Global or Redistribution, inconsistent data can be created. The only exception is that you can reset the indicators on the Lock tab page any time without danger. Ensure that you take into account SAP Note 611972 - SCUM: Change to field distribution parameters.
Hint: The settings of the distribution parameters are automatically forwarded to the child systems.
Recommendations for Transaction SCUM The following table lists the recommendations for the configuration of the parameter distribution for a number of fields:
Field
Setting
Print parameters (under Defaults)
Proposal
Parameters
Proposal
User group (under Logon Data)
Proposal
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Field
Setting
Fields for data that the users maintain them selves
Redistribution or Local
The recommendation for a Global setting applies to all the fields that are not listed (with the exception of locks).
A
Caution: For information about lock management for your users (for example, due to too many failed logon attempts), see the online documentation.
Configuration of IDoc Processing
Changes to company addresses and users that affect a child system are transferred to the child system(s) as an IDoc using the RFC connection. To optimize the ALE distribution of CUA, you can execute (separately) the outbound processing and inbound processing of the IDoc in the background.
Note: You can find more information about this in the online documentation under the Activated Background Processing keyword.
IDoc Inbound Processing in the Child System
In standard systems, the activation of CUA (using transaction s c u a )generates partner profiles in the child systems that allow immediate (synchronous) processing (online).
Note: To check partner profiles, run transaction WE20 in the child system. Navigate to the partner profile by choosing Partner Profiles —> Partner Type LS —> . On the first tab page, double-click inbound parameters for message types CCLONE and USERCLONE. Take note of the Processing by Function Module setting on the Inbound Options tab page. In standard systems, the receipt of the IDoc is separated from the IDoc processing (see SAP Note 555229). The dialog work process reserved for the RFC communication does not process the transferred IDocs itself. If an IDoc cannot be processed immediately because no dialog work processes are available, the system schedules a background job (with the step RBDAPP01) for this IDoc with an immediate start. The user that is used for the RFC communication requires additional authorizations for this scenario (see SAP Note 492589).
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Note: Scheduling of the background job is controlled by the entries in the table TEDEF. In the standard systems, this table (for the current clients) contains an entry with values EVENTT = t r f c - i d o c and ROUTID = b a t c h j o b . If you change the table entry to EVENTT = t r f c - i d o c and ROUTID = s y n c h r o n , the system updates all IDocs from the dialog work process that are currently used for the RFC communication. Across all applications, the table TEDEF controls the processing of all IDocs that are sent to the current clients. You can use the report RSESYNMESTYP to convert IDoc processing to synchronous processing, depending on the sent message type, IDoc type, or extension. The message types CCLONE and USERCLONE are relevant to CUA.
Note: The report RSESYNMESTYP sets the field ACTFLAG in the table EDIMSG for the selected objects.
Synchronization of the Company Addresses
As company address data has already been maintained in all systems of the future CUA, you must first ensure that at least the central system contains all valid company addresses. Then, distribute this complete company address set to all the child systems so that a consistent status exists for the company addresses in the entire CUA. You can use transaction s u c o m p to administrate company address data. You can use transaction SCUG in the central system to perform the synchronization activities between the central system and child systems. This synchronization is done by selecting your child system on the initial screen of transaction SCUG and then choosing Synchronize Company Addresses in the Central System. For more information, see the online documentation.
Note: For more information about this, see the online documentation. Alternatively, you can compare company addresses using transaction scuc. You cannot transfer user data in this transaction.
Synchronization of User Groups
To be able to transfer users from a child system to the central system or distribute them from the central system to a child system, the user group to which the user is assigned must exist in all the systems in which the user exists. Transfer of Users to Central Administration
After you synchronize the company addresses, you can transfer the users from the newly connected child systems to central administration. You can do so using transaction SCUG in the For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
central system. On the initial screen of transaction choose Copy Users to the Central System.
s c u g ,select
your child system and then
The user transfer options are as follows:
•
New users These users are not yet contained in CUA. By choosing Transfer users, you can transfer the selected users to the central system. All user parameters (such as address, logon data, and so on), profiles, and roles are transferred. The user is maintained centrally in the future.
•
Identical users There are users with identical user IDs (the user ID or ID is the string that you enter in the User field on the SAP Logon screen). For example, these could be user IDs with identical first and last names. You can transfer the roles and profile data of this user to the central system. The user is then distributed as it exists in the central system. Local data is overwritten. In such cases, it is assumed that, for example, the ID MOOREJ that exists in multiple logical systems, with the last name Moore and the first name Jane, always belongs to the same person. In large companies, this assumption is not always correct. For this reason, you should use unique character strings, such as the personnel number as the user ID.
•
Different users These user IDs exist both in the central and child systems, but the user has a different first and/or last name. If, in an individual case, these IDs actually refer to the same user, you can transfer the roles and profile data pertaining to the user to the central system. The user is then distributed as it exists in the central system. If the IDs do not refer to the same user, use CUA to create a new user ID in the child system for one of the users and delete the old ID in the child system. Alternatively, you can assign a new ID to the user in the child system (if different employees have an identical ID in different clients). For this purpose, you can start transaction suOl in the child system and choose Users —> Rename. If the user transfer is restarted, the user is listed as a New User rather than a Different User.
•
Already central user These users already exist in CUA and are only administered centrally.
O
Hint: A function is available for copying users. You can access this function using pushbuttons in transaction s c u g if the Already central user tab page is selected. Using these pushbuttons, you can transfer role assignments, profile assignments, and the license classification of users from the child systems, particularly in cases in which (despite CUA being in use) the corresponding administration was carried out until now in the child systems (in line with the settings in transaction SCUM).
Note: For more information, see SAP Note 704412 - CUA support for license data maintenance.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Hint: Until the user transfer is completed, the child systems affected still contain (unexpected) processing options for users who have not been transferred, such as the delete function for users in transaction suOl.
Distribution Status Check
You use the log display (transaction s c u l ) primarily to check the status of IDoc distribution when changing company addresses or users. If you change a company address in the central system of CUA, this is replicated and a CCLONE IDoc is sent to each child system of CUA. If you change a user in the CUA central system, the user data is also distributed to the child systems assigned to this user. At most, three USERCLONExx IDocs are sent for each user: user attributes (USER), profile assignment (PROFILE), and role assignment (ACTGRP). You can then see in the results list of the log display whether the user or company address was replicated successfully to the child systems.
Hint: It may not be possible to completely process IDocs with user changes in the child system (status Unconfirmed in transaction s c u l ) because not enough dialog work processes are available (in the child system or contacted instance). In this case, you can start post-processing of the IDocs in the child system using transaction BD87 or opt for inbound processing of the IDocs in background processing. For more information about IDocs, see SAP Note 399271 - CUA: Tips for optimizing ALE distribution performance.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 8 Exercise 17 Distribute User Data with CUA
Business Example
You need to maintain user profiles in the database and provide authorization to users from a central system. You need to use CUA. Task 1 Create a new role in the child system. 1. In your CUA child system, copy SAP role template SAP_BC_ENDUSER to Z_SAP_BC_ENDUSER. Also create an authorization profile for the new role. 2. Within your CUA child system, trigger a text comparison. You continue to work in your CUA child system. Make sure you are on the start screen of transaction p f c g .
Task 2 Create a new user for the child system using CUA. 1. In your CUA central system, create a new user, c h i l d # # . Make sure that this user gets the Z_SAP_BC_ENDUSER role in your CUA child system (but no master record in the central system). Also, maintain additional data, such as the telephone number, fax number, and so on. 2. In your CUA central system, check the distribution log for your new user, c h i l d # # . You continue to work in your CUA central system. Make sure you are on the start screen of transaction suOl and user ID c h i l d # # is selected for the User field. 3. In your CUA child system, check the user master record of your new user,
c h il d
# #.
4. Log on to your CUA child system as user c h i l d # # and maintain your own (user) data. 5. Log on to your CUA central system as user c h i l d # # and maintain your own (user) data. 6. In your CUA central system, use transaction s u i m to check which roles are assigned to the user you just created in all the systems connected to CUA.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 8 Solution 17 Distribute User Data with CUA
Business Example
You need to maintain user profiles in the database and provide authorization to users from a central system. You need to use CUA. Task 1 Create a new role in the child system. 1. In your CUA child system, copy SAP role template SAP_BC_ENDUSER to Z_SAP_BC_ENDUSER. Also create an authorization profile for the new role. a) Log on to your CUA child system as administration user ID c h i l d _ o f _ < s i d >. b) Run transaction PFCG.
c) On the Role Maintenance screen, choose Views and then choose Single Roles. d) Choose the SAP_BC_ENDUSER single role. e) Choose Copy. f) Enter Z_SAP_BC_ENDUSER, in the to role field. g) Choose the Copy all pushbutton. h) Open the new role, Z_SAP_BC_ENDUSER, in Change mode. i) Open the Authorizations tab page and then choose the Change Authorization Data pushbutton. j) Choose the yellow traffic light at the top and confirm the popup regarding full (*) authorizations that will be assigned to the Z_SAP_BC_ENDUSER role. k) Choose the Generate pushbutton and confirm the proposed profile name and text. Go back to the previous screen. l)
Note: You cannot assign users on the User tab page.
2. Within your CUA child system, trigger a text comparison. You continue to work in your CUA child system. Make sure you are on the start screen of transaction p f c g . a) Choose Environment —► Text Comparison for CUA Central System.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Hint: This will trigger the text comparison for the name and description of all roles and manual profiles.
Task 2 Create a new user for the child system using CUA. 1. In your CUA central system, create a new user, c h il d ##. Make sure that this user gets the Z_SAP_BC_ENDUSER role in your CUA child system (but no master record in the central system). Also, maintain additional data, such as the telephone number, fax number, and so on. a) Log on to your CUA central system as administration user ID -##. b) Run transaction suOl. c) On the User Maintenance: Initial Screen, enter c h il d ## in the User field and then choose the Create pushbutton. d) On the Address tab page, enter some data (in particular, for the Last Name field). e) On the Logon data tab page, enter any password in the Initial password field. Enter the same password in the Repeat password field. f) On the Parameters tab page, provide some Parameter ID (for example, b u k =
4 2 ).
g) On the Roles tab page, use the F4 help for a blank line to select the (logical) system of your CUA child system. In the same line, use the F4 help to select your new role, Z_SAP_BC_ENDUSER (for this, you may need to search for roles Z_SAP*). h) Press ENTER. You will see a notification that a new (logical) system is assigned to this user. You can verify this by opening the Systems tab page. i) Save the new user record. 2. In your CUA central system, check the distribution log for your new user, c h il d ##. You continue to work in your CUA central system. Make sure you are on the start screen of transaction suOl and user ID c h il d ## is selected for the User field. a) Choose Environment —» Distribution log. b) Keep all the default values, but select Successful on the Users tab page. c) Choose Execute pushbutton. Green indicators imply successful distribution. 3. In your CUA child system, check the user master record of your new user, c h il d ##. a) Log on to your CUA child system as administration user ID c h il d _ of_< s id >. b) Run transaction suOl. c) Enter c h il d ## in the User field and then choose the Display pushbutton.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
d) Note the data on all the tab pages. Note the Last Changed On field. Note the changeability when you enter the change mode: Only some fields that are ready for input (these should be the fields that you did not set to Global in transaction scum for maintaining field distribution parameters). e) Close the user master record. 4. Log on to your CUA child system as user c h il d ## and maintain your own (user) data. a) Log on to your CUA child system as new user c h i l d ##. You have to enter the initial password and a new password (twice). b) To maintain your own user data, you may do the following: .
On the SAP Easy Access screen, choose Menu —> User Menu —*■ Basis Functions —► Maintain Own User Data (Address, Default Values, Parameters).
.
Choose System —► User Profile —> Own Data.
. Run transaction SU3.
c) Note the restricted changeability of the fields. Change some data. d) Save your data. 5. Log on to your CUA central system as user c h i l d # # and maintain your own (user) data. a) Log on to your CUA central system as new user c h i l d ##. You will see a status message that you cannot log on to the CUA central system because of a missing CUA system assignment. 6. In your CUA central system, use transaction s u i m to check which roles are assigned to the user you just created in all the systems connected to CUA. a) Log on to your CUA central system as administration user ID -##. b) Run transaction s u i m (User Information System).
c) On the User Information System screen, choose User Information System —► User —► Cross-System Information (Central User Administration) -> Users by Roles. d) Run the Users by Roles report. e) On the Report Cross-System Information/Role screen, enter c h i l d # # in the User Name field. f) Choose the Execute pushbutton.
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
LESSON SUMMARY You should now be able to: •
Explain Central User Administration (CUA)
•
Set up Central User Administration (CUA)
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Unit 8
Learning Assessment
1. Identify the key benefits of using Central User Administration (CUA). Choose the correct answers. | A You can maintain roles in one place. B You can reduce the cost of user administration. | C You can create user data from multiple places. D You can provide secure user administration by centralizing the work. 2. For which of the following purposes are Remote Function Call (RFC) connections used in the CUA scenario? Choose the correct answers. | A To distribute user data from the central system to child systems B To distribute user data from one child system to another | C To send changes to the data in the central system to the child systems D To send status reports back to the central system
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
0
Visit : www.erpexams.com
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Learning Assessment - Answers
1. Identify the key benefits of using Central User Administration (CUA). Choose the correct answers. | A You can maintain roles in one place.
|~xj B You can reduce the cost of user administration. C You can create user data from multiple places. |~xj D You can provide secure user administration by centralizing the work.
2. For which of the following purposes are Remote Function Call (RFC) connections used in the CUA scenario? Choose the correct answers. |~xj A To distribute user data from the central system to child systems B To distribute user data from one child system to another |~xj C To send changes to the data in the central system to the child systems |~xj D To send status reports back to the central system
For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]
Visit : www.erpexams.com