E2 E2 00 Change Cont rol M a nage me nt

E2 E2 0 0

Change Control Management

SAP Solution Manager

2008/Q4

© SAP 2009

̈ ̈ ̈

SAP Solution Manager Collection 84 Material number: 50095127

Copyright

Copyright 2009 SAP AG. All rights reserved. Neither this training manual nor any part thereof may be copied or reproduced in any form or by any means, or translated into another language, without the prior consent of SAP AG. The information contained in this document is subject to change and supplement without prior notice. All rights reserved.

© SAP 2008

̈ ̈

̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈

̈

Trademarks: Microsoft ®, Windows ®, NT ®, PowerPoint ®, WinWord ®, Excel ®, Project ®, SQL-Server ®, Multimedia Viewer ®, Video for Windows ®, Internet Explorer ®, NetShow ®, and HTML Help ® are registered trademarks of Microsoft Corporation. Lotus ScreenCam ® is a registered trademark of Lotus Development Corporation. Vivo ® and VivoActive ® are registered trademarks of RealNetworks, Inc. ARIS Toolset ® is a registered Trademark of IDS Prof. Scheer GmbH, Saarbrücken Adobe ® and Acrobat ® are registered trademarks of Adobe Systems Inc. TouchSend Index ® is a registered trademark of TouchSend Corporation. Visio ® is a registered trademark of Visio Corporation. IBM ®, OS/2 ®, DB2/6000 ® and AIX ® are a registered trademark of IBM Corporation. Indeo ® is a registered trademark of Intel Corporation. Netscape Navigator ®, and Netscape Communicator ® are registered trademarks of Netscape Communications, Inc. OSF/Motif ® is a registered trademark of Open Software Foundation. ORACLE ® is a registered trademark of ORACLE Corporation, California, USA. INFORMIX ®-OnLine for SAP is a registered trademark of Informix Software Incorporated. UNIX ® and X/Open ® are registered trademarks of SCO Santa Cruz Operation. ADABAS ® is a registered trademark of Software AG The following are trademarks or registered trademarks of SAP AG; ABAP/4, InterSAP, RIVA, R/2, R/3, R/3 Retail, SAP (Word), SAPaccess, SAPfile, SAPfind, SAPmail, SAPoffice, SAPscript, SAPtime, SAPtronic, SAP-EDI, SAP EarlyWatch, SAP ArchiveLink, SAP Business Workflow, and ALE/WEB. The SAP logo and all other SAP products, services, logos, or brand names included herein are also trademarks or registered trademarks of SAP AG. Other products, services, logos, or brand names included herein are trademarks or registered trademarks of their respective owners.

Disc la im e r
The current release of the SAP Solution Manager is: SAP Enhancement Package 1 for SAP Solution Manager 7.0. The following note only applies to SAP customers in Germany and Austria: The extent of the usage of the software package "SAP enhancement package 1 for SAP Solution Manager 7.0" depends on the type of maintenance contract you have signed:
> > > >

SAP Enterprise Support SAP Product Support for Large Enterprises SAP Premium Support SAP MaxAttention

You are authorized to use all functions in the software package, without any restrictions. If you have signed exclusively standard support contracts, you are allowed to install this software package, however, with a restricted functionality. You are not allowed to use the following Enterprise Edition functions:
> > >

Business Process Change Analyzer Quality Gate Management Custom Development Management Cockpit

© SAP 2009

Course Pre requisit e s

Required Knowledge
̈ ̈

Fundamentals of Software Change Management Basics of SAP Solution Manager

Recommended Knowledge
̈

End-to-End Solution Support (E2E040)

© SAP 2009

Course Goa ls

This course will prepare you to:
̈ ̈ ̈

Understand the value of E2E Change Control Management Describe the concept and methods of E2E Change Control Management Leverage the SAP Solution Manager as an application platform for E2E Change Control Management

© SAP 2009

T a rge t Audience

This course is intended for the following audiences:
̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈

Change Managers: Responsible for approval and change processes System Landscape Architects: Responsible for the design of the transport landscape topology System Administrators: Responsible for executing transports Development Managers: Responsible for performing development changes Test and QA Managers: Responsible for software quality and testing Persons responsible for a module / Application Manager: Responsible for approving and performing changes in an application module Support Manager and members of the Customer Competence Center (CCC) Partners and System Integrators for the Run phase

Duration: 5 day(s)
© SAP 2009

̈

User notes • These training materials are not a teach-yourself program. They complement the explanations provided by your course instructor. Space is provided on each page for you to note down additional information. • There may not be sufficient time during the course to complete all the exercises. The exercises provide additional examples that are covered during the course. You can also work through these examples in your own time to increase your understanding of the topics.

Course Cont e nt

Unit 1 Introduction to E2E Change Control Management Unit 2 Software Change Strategies Unit 3 Enhanced Change and Transport System Unit 4 Solution Documentation Unit 5 Quality Gate Management Unit 6 Change Request Management Unit 7 Maintenance Management Unit 8 Test Management Unit 9 Change Diagnostics

© SAP 2009

End-t o-End Change Cont rol M a na ge m ent Ce rt ific a t ion
Title: Application Management Expert ? Change Control Management Duration: 1 hour, at Friday 3:00 pm Number of Questions per Certification Topic:
2 3 6 3 6 6 6 3 5 (5%) (7,5%) (15%) (7,5%) (15%) (15%) (15%) (7,5%) (12,5%) Introduction Software Change Strategies Enhanced Change and Transport System Solution Documentation Quality Gate Management Change Request Management Maintenance Management Test Management Change Diagnostics

--------40

TOTAL

© SAP 2009

T ra ining La ndsca pe a nd Archit e c t ure

TT5 Host: <host>.wdf.sap.corp (monitored) SAP EP http://<host>:55000/irj Front End PC SAP GUI Browser Web AS Java SAP ECC Instance: 50; Client: 800 Web AS ABAP

RDBMS TT4 Host: <host>.wdf.sap.corp (monitoring) SAP SolManDiag http://<host>:50000/smd Web AS Java SAP SolMan Instance: 00; Client: 200 Web AS ABAP

RDBMS
© SAP 2009

̈

This diagram shows the system landscape which is available for the training

I nt roduc t ion t o E2 E Cha nge Cont rol M a nagem ent

Unit 1 Introduction to E2E Change Control Management Unit 2 Software Change Strategies Unit 3 Enhanced Change and Transport System Unit 4 Solution Documentation Unit 5 Quality Gate Management Unit 6 Change Request Management Unit 7 Maintenance Management Unit 8 Test Management Unit 9 Change Diagnostics

© SAP 2009

© SAP AG

E2E200

1-1

I nt roduc t ion t o E2 E Cha nge Cont rol M a nagem ent : U nit Obje c t ive s

After completing this unit, you will be able to:
̈ ̈ ̈

Explain the SAP standards and understand the benefits of SAP End-to-End Solution Operations Explain the scope of End-to-End Change Control Management Explain the role of SAP Solution Manager to manage changes in your solution landscape

© SAP 2009

© SAP AG

E2E200

1-2

I nt roduc t ion t o E2 E Cha nge Cont rol M a nagem ent : U nit Ove rvie w Dia gra m
Introduction to E2E Change Control Management Lesson 1: E2E Solution Operations Lesson 2: Scope of E2E Change Control Management

© SAP 2009

© SAP AG

E2E200

1-3

T he N a t ure of Busine ss I s Changing
Business networks lead to increasing innovation and integration speed

» I N CREASED SAP LAN DSCAPE I N T EGRAT I ON
Business Networks No. of users

̈

Every customer has m ission-critica l a pplica tions along with integration needs SAP landsc a pe s become more sophistic at ed the more c om pre he nsive & int egrat ed they are To run these landscapes a new set of ca pabilit ie s is re quire d

̈

Manguistics

R/3
Legacy System

̈

20 00

20 07

2 0 10

Optimized solution operations is the key success factor to manage speed of innovation and integration, risk and total cost of operations Enabled by SAP Solution Manager Enterprise Edition
© SAP 2009

© SAP AG

E2E200

1-4

T ypic a l I T Re quire m e nt s
V ALUE OF I T
Ac c e le ra t e d I nnova t ion & Prot e c t ion of I nve st m e nt ̈ Business speed requires fast deployment of new functionality ̈ IT innovation to provide flexibility and to enable differentiation ̈ Legal compliance and sustainability

M a nage Busine ss Cont inuit y ̈ Disruption free changes ̈ Providing scalability of business processes and systems to meet business requirements ̈ Ensuring performance, stability and availability Re duc e T ot a l Cost of Ope ra t ions ̈ Standardization of IT Operations

I m prove Busine ss Va lue ̈ Comply with business driven KPI’s and SLA’s ̈ Pro-active monitoring of end-toend business processes ̈ Continuous improvement to keep up with business requirements

̈ Reduce test and change effort despite high number of changes ̈ Tuning and management of performance, data growth and business process operations

SAP Enterprise Support is addressing all of these areas
© SAP 2009

© SAP AG

E2E200

1-5

H ow Ca n We I mple me nt End-t o-End M issionCrit ic a l I T Ope ra t ions?
The “Run SAP” Methodology
Tools Training & Certification Services SAP Standards for Solution Operations

End-to-End Root Cause Analysis End-to-End Change Control End-to-End Test Management End-to-End Business Process Integration and Automation End-to-End Enterprise SOA Readiness End-to-End Custom Code Management …
© SAP 2009

̈ ̈

SAP’s End-to-End Solution Operations addresses these challenges End-to-End Solution Operations is the basis for mission-critical IT operations

© SAP AG

E2E200

1-6

H ow Ca n We I mple me nt End-t o-End M issionCrit ic a l I T Ope ra t ions?
The “Run SAP” Methodology

Work Centers (Tools)

SAP Standards for Solution Operations

© SAP 2009

© SAP AG

E2E200

1-7

SAP St a nda rds for Solut ion Ope ra t ions Role s and Re sponsibilit ie s
BUSINESS Global Business Process Champion Regional Business Process Champion End User, Key User
Integrated Help Desk

Program Management Office (PMO)
Change Request Management

Application Management
Blue printing, testing, e-learning management, maintenance management, issue management, document management, application diagnostics

Custom Development

Business Process Operation IT Infrastructure

SAP Technical Operations

IT
Out tasking Outsourcing
SAP Standards available

© SAP 2009

̈

SAP Standards in Operations are a prerequisite for SAP mission-critical support and advanced support for continuous improvement

© SAP AG

E2E200

1-8

SAP St a nda rds for Solut ion Ope ra t ions De fine Ope ra tions Proce sse s
̈ ̈

Exception Handling Data Integrity

̈

Incident Management

̈ ̈ ̈ ̈

Change Request Management Testing Upgrade eSOA Readiness

̈ ̈ ̈ ̈

Root-Cause Analysis Change Control Management Minimum Documentation Remote Supportability

̈ ̈

System Administration System Monitoring

̈ ̈ ̈ ̈
© SAP 2009

Business Process and Interface Monitoring Data Volume Management Job Scheduling Management Transactional Consistency

̈ ̈

SAP Standards for Solution Operations define Operations Processes For more information on all SAP Solution Operation standards, see http://service.sap.com/supportstandards

© SAP AG

E2E200

1-9

E2 E Change Cont rol Ma na ge m ent Role s and Re sponsibilit ie s
Solution Design
Global / Regional Business Process Champion Solution Architecture

Solution Maintenance
SAP Maintenance Management

Solution Correction
End User / Key User Incident Management

Program Management Office Change Request Management

Application Management Test Management Workbench / Customizing Changes Custom Development Change Deployment Application Change Diagnostic System Change Diagnostic

Correction & Transport System SAP NetWeaver Team

DB / OS / HW Changes & Maintenance IT Infrastructure
© SAP 2009

̈

The program management office is the central group in the customer business unit that is responsible for the overall planning, implementation, and continuous improvement of the business processes in the solution landscape. All requests for changes, including Solution Design, Solution Maintenance, Solution Correction flow through this office and need to be integrated into a schedule of landscape changes. As such, change request management is a large part of the program management office’s activities. This office is responsible for managing everything from day-to-day changes and adaptations to all release planning and major infrastructure technology shifts. In addition, these activities must be aligned with all stakeholders. The key interface between business and IT is the application management organization. End users, key users and the program management office use the services of IT for a wide variety of tasks; from solution landscape planning to implementation, from business unit request handling to execution, from documentation standards, training and certification to management level reporting. Being such a central component, several of the introduced roles use the application management platform as their central working application. It is essential that changes to the solution landscape are managed carefully to ensure transparency. The Change Request Management standard ensures that standardized methods and procedures are used for the efficient and prompt handling of all changes. In addition to Change Request Management, the deployment and the analysis of changes need to be addressed to ensure that changes are executed without disrupting ongoing business. This is the focus of the Change Control Management standard. The standard covers two major areas of change control: Change Deployment and Change Diagnostics for Application and System Changes.

̈

̈

© SAP AG

E2E200

1-10

SAP St a nda rds for Solut ion Ope ra t ions Cove r a ll Support Proc e sse s
Example: Process Standard “Change Request Management”
Champs
Request Business Change * Implement Change Monitor Change Test Change Deploy Change Sign-off Change

PMO

Appl Mgmt

Tech Op

Available Information
̈ ̈ ̈ ̈

*Business Changes = Request Adaptation or Request Project

White Papers Detailed technical description Training Courses Certifications

© SAP 2009

© SAP AG

E2E200

1-11

SAP Solut ion M a na ge r Work Cent e rs
Work Centers … ̈ are role-based ̈ enable easy navigation for end users ̈ use a common interface for central administration of solutions ̈ support Service Level Management ̈ are based on SAP Solution Manager 7.0

http://<host>:<port>/sap/bc/ webdynpro/sap/ags_workcenter/

Available Work Centers (EhP1) myHome SAP Solution Manager Administration ̈ System Landscape Management ̈ Implementation/Upgrade ̈ Solution Documentation Assistant ̈ Test Management ̈ Change Management
̈ ̈
© SAP 2009

System Monitoring System Administration ̈ Business Process Operations ̈ Job Management ̈ Incident Management ̈ Root Cause Analysis ̈ SAP Engagement and Service Delivery
̈ ̈

© SAP AG

E2E200

1-12

SAP Solut ion M a na ger Applic a t ion Life cyc le M a na ge m e nt
Change Management

•Missing governance, project management and integration between requirements management and software logistics
Solution Updates

Transparency on Processes & Apps
partner applications, system landscape

• Identification of core business processes • Central documentation of processes, custom code,
Innovation Management
Design

•Missing guidance for upgrade projects •Handling of custom code during upgrade •Consistent SAP updates •Zero downtime during upgrades
Problem analysis in complex & diverse technology stacks

Requirements

Optimize
Applic a tion M a na ge me nt

•Root-cause analysis across technology
stack from front-end down to database / OS level

•Requirements management •Innovation discovery •Innovation w/o disruption •Project management
Integration Testing

Operate

Build & Test Deploy

Incident Management

•Missing support for mission critical processes •Exchange of required technical information •Involvement of partners in problem resolution
Monitoring & System Administration

•Test in heterogeneous environments •Change Impact Analysis •Test Data Management, Test Automation

Integration Validation

•Data inconsistencies in complex system landscapes •Performance bottlenecks
Software logistics

•Decentralized monitoring, alerting and service
level reporting •Central system administration & job scheduling •Data volume management
© SAP 2009

•Synchronized transport of ABAP, Java, .NET and C components •Complex and opaque transport situation

̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈

Challenge: Consider the feedback from customers concerning chronic problems in this slide. Development and Support of large and complex software applications can be a nightmare for companies of any size with budget overruns and delivery delays. Also, as potential outsourcing's risks grow ever greater, the need for control by in-depth monitoring of disruptions and deviations is critical. If corporate data, intellectual property, and business processes are to remain stable, transparency in real time, becomes a necessity. The stability of a company's outsourcing practice depend on it. Answer: Ensure that everything gets done. Efficient Application Lifecycle Management should utilize the capabilities of SAP Solution Manager.

© SAP AG

E2E200

1-13

I nt roduc t ion t o E2 E Cha nge Cont rol M a nagem ent : U nit Ove rvie w Dia gra m
Introduction to E2E Change Control Management Lesson 1: E2E Solution Operations Lesson 2: Scope of E2E Change Control Management

© SAP 2009

© SAP AG

E2E200

1-14

End-t o-End Change Cont rol M a na ge m ent a s Pa rt of t he Cha nge M anagem ent Proc e ss

End-t o-End Cha nge M a na ge m e nt Proc e ss Register and classify RFC Approve change Confirm and schedule change Build change Test change Implement change and review result

Change Manager

Change Manager

Change Manager

Developer

Tester

Change Manager

E2 E Cha nge Cont rol M a na ge m e nt
DEV DEV TST TST Production Production

© SAP 2008

̈ ̈

The end-to-end change management process starts with the requirement and ends with a postimplementation review of the change in production. End-to-End Change Control Management primarily focuses on the technical implementation of the change in an SAP landscape.

© SAP AG

E2E200

1-15

E2 E Change Cont rol Ma na ge m ent T ools
Controlling the changes during the entire application lifecycle becomes crucial for End-to-End Solution Operations

End-to-End Change Control Management
Build
Bring changes from system A to system B

Test
Impact Analysis and Test

Run
Reporting and History of changes is important

Enhanced Change and Transport System Quality Gate Management Change Request Management Maintenance Management
© SAP 2009

Business Process Change Analyzer Custom Development Management Cockpit Code Inspector Test Workbench and Automation

Solution Documentation Change Diagnostics

̈

Different tools are available to control changes in all phases of the application lifecycle.

© SAP AG

E2E200

1-16

Enha nc ed Cha nge and T ransport Syst e m I nt egra t e s a ll Work be nche s
ABAP Workbench SE80

CHANGE AND TRANSPORT SYSTEM
TPZ

Exchange Infrastructure Integration Builder
SCA

Development Landscape

Transport

Quality Landscape

Transport

Production Landscape

Developer Studio and NWDI
EPA

Development Landscape

Transport

Quality Landscape

Transport

Production Landscape

Enterprise Portal Content Administrator

Development Landscape

Transport

Quality Landscape

Transport

Production Landscape

… (open Interface for non-ABAP objects)

© SAP 2009

© SAP AG

E2E200

1-17

Qua lity Ga t e M a na ge m ent Provide s one I nte gra t ed Qua lit y Proc e ss
̈ ̈

100% transparency of changes A central transport mechanism and change control system to manage changes across technology stacks and application components A central test plan for core business processes A central quality manager validating test execution and test completeness Integration of every development workbench into the central transport and change control system

All operational units across all organizations integrated in one integrated and consistent quality process
Synchronization
NW Portal 7.0
Dev System

NW Portal 7.0
QAS System

NW Portal 7.0

FIX

Presentation layer

̈ ̈

CE 7.1
Dev system

CE 7.1
QAS system

CE 7.1
PRD system

FIX

ERP6.0
Dev system

ERP6.0
Dev system

ERP6.0

̈

FIX

PRD system

Development Landscape Transport Multiple Development Workbenches

Quality Landscape Transport

Production Landscape

Build to Test

Test to Deploy

© SAP 2009

̈

Controlling changes in all phases of the application lifecycle and across all technologies from a central entry point is the goal of End-to-End Change Control Management.

© SAP AG

E2E200

1-18

Change Reque st Ma na ge m ent Cont rols Single Change Reque st s
SAP Solution Manager
Service Desk Service Desk Employee

Service Message

Incident
ture Fea

Requester

New

Change Request Management

Developer
Do c of um Ac ent tiv ati iti on es

Change Request

Change Manager

PRD

Controlled transports

Tester

Change Transaction

Maintenance Cycle QAS

Controlled transports

IT Operator DEV

© SAP 2009

̈ ̈

Change Request Management ensures that all changes are approved and tested before they go to production. Furthermore a documentation of each change is provided automatically by the Change Request Management process.

© SAP AG

E2E200

1-19

Cust om Deve lopm e nt Ma na ge me nt Cock pit a nd Busine ss Proc e ss Cha nge Analyzer – I m pa c t
Custom Development Mgmt Cockpit Business Process Change Analyzer
Core Processes with TBOM Planned Changes
̈ ̈ Internet Sales: B2C ̈ ̈ Business-to-Consumer

SAP Objects Changed SAP Objects, e.g. Support Pack

Selected Business Scenarios

Business Processes

SAP Support Packs SAP Enhancement Packages Custom Code Customizing changes

BC

Register in Web Shop Select Product Update Shopping Basket

Custom Objects

Custom Objects using changed SAP Objects

Core Processes affected by the Change

Business to Consumer Select Product Update Shopping Basket

© SAP 2009

̈

The Custom Development Management Cockpit analyzes the changed SAP objects, for example, in an upgrade or support pack implementation. Then it determines which customer objects are using these changed objects. These are the objects which are potentially affected by the change. The Business Process Change Analyzer requires an object list (TBOM) for the critical core business processes. These lists are determined by an initial trace. They can be compared against the object lists of transport requests in order to find out which core business process is affected by this change.

̈

© SAP AG

E2E200

1-20

Cha nge Dia gnost ics Re ports on Curre nt Set t ings a nd Re c e nt Change s

Java Extractors Java System
E2E Change Diagnostics

OS/DB

ABAP System

ABAP Extractors
OS/DB

BI Reporting

Managed Systems

Data Collection

© SAP 2009

̈ ̈ ̈ ̈

End-to-End Change Diagnostics collects data in the managed systems (ABAP and JAVA) and stores it in the Config Stores of the SAP Solution Manager. During the upload of the data the system determines which configuration item was changed. Only the changes are stored in the database. All data is uploaded into BI InfoCubes which allows flexible reporting and navigation in the data. There are three different use cases for change diagnostics: • If an error occurs, you need to know what has been changed recently. • Statistical information on changes allow you to determine how stable the systems are and how well certain IT processes are executed. If certain thresholds are exceeded (such as for the number of hotfixes) you need to take corrective action. • For compliance reasons, all changes must be transparent and reproducible.

© SAP AG

E2E200

1-21

M a inte na nc e M anagem ent K e e ps t he Solut ion U p-t o-Da te
2007 2008 2009

Implementation Projects
Market Campaign Complaint Management Rollout Brazil

SAP Maintenance
SP Stack / EhP Hot News Top Notes Incident
© SAP 2009

One or two times per year …. …. Periodic review and corrections Urgent Corrections Notes/Patches

….

̈

Support Packages • Include bugfixes and legal changes

̈

Enhancement Packages • Include new functionality

̈

SAP HotNews • Contains solutions for customer problems with very high priority, such as systems standstills or data loss • Allows customers to filter and display SAP HotNews for their chosen components

̈

SAP TopNotes • Inform you about potential hot spots in your projects • Are Published on a monthly basis • Represent the ten most important SAP Notes for each component • Are Reviewed monthly by experts in the relevant departments and updated based on the current SAP Note customer usage rate

© SAP AG

E2E200

1-22

Soft w a re Change St ra t e gie s Se t the Right Priorit ie s
SAFETY
Separation maintenance and development (=more instances) Extensive testing Transport changes only bundled over longer intervals [“Business Release Strategy”]

Small number of instances; Little testing

Transport changes every day into production [“Single Transport Strategy”]

COST
Small number of releases; Focused testing
© SAP 2009

FLEXIBILITY
Testing or support costs due to daily transports

̈ ̈

The best transport strategy depends on the customer focus. This can be safety, flexibility, or cost. There is no single best practice that fits all criteria equally well. If one criterion is very important, then the other two cannot be achieved at the same time.

© SAP AG

E2E200

1-23

I nt roduc t ion t o E2 E Cha nge Cont rol M a nagem ent : U nit Sum m a ry

You should now be able to:
̈ ̈ ̈

Explain the SAP standards and understand the benefits of End-to-End Solution Operations Explain the scope of End-to-End Change Control Management Explain the role of SAP Solution Manager to manage changes in your solution landscape

© SAP 2009

© SAP AG

E2E200

1-24

Soft w a re Change St ra t e gie s

Unit 1 Introduction to E2E Change Control Management Unit 2 Software Change Strategies Unit 3 Enhanced Change and Transport System Unit 4 Solution Documentation Unit 5 Quality Gate Management Unit 6 Change Request Management Unit 7 Maintenance Management Unit 8 Test Management Unit 9 Change Diagnostics

© SAP 2009

© SAP AG

E2E200

2-1

Soft w a re Change St ra t e gie s: U nit Obje c t ive s

After completing this unit, you will be able to:
̈ ̈ ̈ ̈

Understand the limitations of a three-system-landscape Understand the benefits of bundling changes in maintenance cycles, projects and synchronized releases Understand the benefits of advanced landscape topologies Understand the challenges of software changes in an integrated solution landscape

© SAP 2009

© SAP AG

E2E200

2-2

Soft w a re Change St ra t e gie s: U nit Ove rvie w Dia gra m
Software Change Strategies Lesson 1: Challenges in a Three-System-Landscape Lesson 2: Release Management Lesson 3: Advanced System Landscapes Lesson 4: Transport Dependencies and Solution Transports Appendix: SAP Change and Transport System

© SAP 2009

© SAP AG

E2E200

2-3

Soft w a re Change St ra t e gie s: U nit Ove rvie w Dia gra m
Software Change Strategies Lesson 1: Challenges in a Three-System-Landscape Standard Transport Process Risk: Import Single Strategy Risk: Inconsistencies in the Transport Landscape Lesson 2: Release Management Lesson 3: Advanced System Landscapes Lesson 4: Transport Dependencies and Solution Transports Appendix: SAP Change and Transport System

© SAP 2009

© SAP AG

E2E200

2-4

T hre e -Syst e m -La ndsca pe

CR

CR

CR

DEV

QAS

PRD

Buffers 1
CR

2

3

CR

© SAP 2009

̈ ̈ ̈ ̈

A three-system-landscape consists of a development system DEV, a quality assurance system QAS and a productive system PRD. The development system DEV is needed to implement changes. The quality assurance system QAS is needed to perform functional tests and integration tests with production-like data. QAS is also needed to test the import of the change requests. Without a quality assurance system, the import of transports cannot be tested before it is executed in production.

© SAP AG

E2E200

2-5

St e p 1 : T he T ra nsport Reque st is re le a se d

Systems
CR CR CR

DEV

QAS

PRD

Buffers 1
CR CR

© SAP 2009

̈ ̈ ̈

Step 1: The transport request CR is released. Development objects which are locked, are released and the change request CR is written to the import queue of the quality assurance system. The import queue has two functions. The first one is that it contains all change requests that have been released, and the second is to remember the sequence, in which the change requests have been released.

© SAP AG

E2E200

2-6

St e p 2 : T he T ra nsport Reque st is im port e d int o QAS
Systems
CR CR CR

DEV

QAS

PRD

Buffers 2

CR

CR

© SAP 2009

̈ ̈ ̈ ̈ ̈

Step 2: The complete import queue for the quality assurance system QAS is imported. System QAS is used for first tests with production-like data and, therefore, the import of the complete transport buffer should be done in short time intervals, for example, every 15 minutes. This can be scheduled automatically. The change requests that are imported are also written to the import queue of the productive system PRD. This guarantees that the change requests and their import sequence to the quality assurance system QAS are remembered.

© SAP AG

E2E200

2-7

St e p 3 : T he T ra nsport s a re im port ed int o Produc t ion
Systems
CR CR CR

DEV

QAS

PRD

Buffers 3

CR

CR

© SAP 2009

̈ ̈

Step 3: The import buffer of the productive system is imported into production.

© SAP AG

E2E200

2-8

Soft w a re Change St ra t e gie s: U nit Ove rvie w Dia gra m
Software Change Strategies Lesson 1: Challenges in a Three-System-Landscape Standard Transport Process Risk: Import Single Strategy Risk: Inconsistencies in the Transport Landscape Lesson 2: Release Management Lesson 3: Advanced System Landscapes Lesson 4: Transport Dependencies and Solution Transports Appendix: SAP Change and Transport System

© SAP 2009

© SAP AG

E2E200

2-9

Single T ra nsport St ra te gy Proble m s and Risk s
Problems:
> Transport requests are imported in an individual sequence > Risk of forgotten transports > Risk of version downgrades by transport sequence violations

Recommendation:
> Use the Import Project ALL or Import ALL strategy

© SAP 2009

̈

There are several risks in a three-system-landscape: The following slides explain these risks in more detail

© SAP AG

E2E200

2-10

Risk : Forgot t en T ra nsport s

DEVK900001

DEVK900001

DEVK900002

DEV
DEVK900002

QAS
DEVK900002

PRD

1

PROG ZREPORT … CALL ZMODULE … •FUNC ZMODULE

2

PROG ZREPORT … CALL ZMODULE …

4

PROG ZREPORT … CALL ZMODULE …

3
© SAP 2009

Test of ZREPORT in QAS is o.k.

Generation of ZREPORT will lead to error

̈ ̈ ̈

Transport request DEVK900002 contains a report ZREPORT which calls the function module ZMODULE in request DEVK900001. In QAS DEVK900001 and DEVK900002 are tested together. The test is ok. But then only DEVK900002 is transported into PRD. The generation of ZREPORT fails, because DEVK900001 was forgotten and function module ZMODULE cannot be called.

© SAP AG

E2E200

2-11

Risk : Dow ngra ding Obje c t Ve rsions

DEVK900001

DEVK900001

DEVK900002

DEV
DEVK900002

QAS
DEVK900002

PRD
DEVK900001

1

PROG ZREPORT … CALL ZMODULE … •FUNC ZMODULE

5

PROG ZREPORT … CALL ZMODULE … •FUNC ZMODULE

2

PROG ZREPORT … CALL ZMODULE …

4

PROG ZREPORT … CALL ZMODULE …

3
© SAP 2009

Test of ZREPORT in QAS is o.k.

Old version of ZREPORT is active in PRD

̈ ̈ ̈ ̈

Transport request DEVK900002 contains a report ZREPORT which calls the function module ZMODULE, which is transported in request DEVK900001. In QAS DEVK900001 and DEVK900002 are tested together. The test is ok. However, only DEVK900002 is transported into PRD. It fails because DEVK900001 was forgotten. Now DEVK900001 is also imported into PRD. But the test in PRD fails again because now the old version of ZREPORT (version of DEVK900001) has overwritten the newer version (version of DEVK900002).

© SAP AG

E2E200

2-12

Soft w a re Change St ra t e gie s: U nit Ove rvie w Dia gra m
Software Change Strategies Lesson 1: Challenges in a Three-System-Landscape Standard Transport Process Risk: Import Single Strategy Risk: Inconsistencies in the Transport Landscape Lesson 2: Release Management Lesson 3: Advanced System Landscapes Lesson 4: Transport Dependencies and Solution Transports Appendix: SAP Change and Transport System

© SAP 2009

© SAP AG

E2E200

2-13

I nconsist enc ie s in t he T ransport La ndsca pe

Systems

DEV

QAS

PRD

Open developments

Transports in transition

Inconsistencies between DEV, QAS and PRD
̈ Open developments in DEV which have not yet been exported ̈ Transports in QAS which have not yet been imported to PRD

© SAP 2009

̈ ̈ ̈ ̈ ̈

The development system DEV contains all developments. The quality assurance system QAS contains transports, which have already been imported into PRD, but also transports which have not been imported yet into PRD. Therefore all three systems are on different software levels. These different software levels in a three-system-landscape cause risks. One big risk is, that programs, which have been tested successfully in QAS might fail in PRD. The main reasons, why these inconsistencies cannot be avoided in such a transport landscape will be explained in more detail on the following slides.

© SAP AG

E2E200

2-14

I nconsist enc ie s in t he T ransport La ndsca pe Re a sons and Possible Solut ions
Reasons:
̈ Transport sequence violations ̈ Transports which were not transported completely into all systems ̈ Transports stay in the import buffer of QAS or PRD too long ̈ Wrong initial system set up ̈ Several parallel projects with different project timelines ̈ Projects and maintenance in parallel

Solutions:
̈ Forward all transport requests that are released in the development system

quickly into the test and production system

© SAP 2009

̈

There are several risks in a three-system-landscape: The following slides explain these risks in more detail.

© SAP AG

E2E200

2-15

Risk : V e rsion I nc onsist e nc ie s during Bugfix ing
Systems

DEV
Obj1

QAS

PRD

Object 1 is different

1) Error in production å Object 1 must be maintained 2) Object 1 is already changed in DEV and cannot be maintained

© SAP 2009

̈

Objects which have been changed in a project that is currently in transition cannot be maintained anymore during bug-fixing.

© SAP AG

E2E200

2-16

V e rsion Com pa re for Fix e s be tw e en DEV a nd PRD
Systems

DEV

Obj1V2

QAS

PRD
Obj1V1

Object 1 is different

1) Comparing active DEV object version with active PRD object version 2) Intermediate switch DEV object version for fix

© SAP 2009

̈

You can compare the object versions in DEV and PRD before a maintenance task. If the versions are different, then you have to temporarily switch back an old object version from the version history in the development system. This object version is corrected and transported to production. In the next step the correction is done again with the latest object version. This procedure is not possible for BW objects, because they do not have a version history. The procedure to maintain two different versions of one object via versions, and to transport these versions through the system landscape is error-prone. Alternatively the developer can search for objects in transition with transaction SE03.

̈ ̈ ̈

© SAP AG

E2E200

2-17

Risk : De t e c t ion of Cross Re fe re nc e Errors during Bug-fix ing
Systems
Obj1 Obj2V2 Obj1 Obj2V2 Obj1 Obj2V1

DEV

QAS
Test in QAS is ok

PRD
Error in PRD

1) Error in production å Object 1 must be maintained 2) Object 1 uses Object 2. Object 2 was changed by the project 3) Test in QAS is ok 4) Error in PRD because Object 2 is still in the old version

© SAP 2009

̈ ̈

In this example Object 1 was not changed by the project. But Obj1 uses Obj2, and Obj2 was changed. At the beginning Obj1 does still work. Now Obj1 has to be corrected. The new version of Obj1 does still work with the new version of Obj2. However, the new version of Obj1 does not work with the old version of Obj2. This is only detected in PRD. For example Object1 could be a program, which uses a data type Obj2, which has been declared in the data dictionary. If the new data type has only been brought to QAS but not to PRD, the program will work in QAS but it will fail in PRD, because the data type is not there. Another example for Obj1 could be a program that reads data from a table (Obj2). At the beginning, the program reads data from the first 3 columns of the table. Then, an additional column is added to the table. If the program now also reads data from the new column, this only works with the new version of the table. It will fail in PRD.

̈

̈

© SAP AG

E2E200

2-18

Cross-Re fe re nc e Inconsist enc ie s and Pre Produc t ion

Obj1V2

Obj2V2

Obj1V2

Obj2V2

DEV

QAS

Obj1V2

PRE

Obj2V1

Obj1V1

Obj2V1

PRD

The Preproduction System (PRE) has the current software/configuration state of production The next urgent correction or project cycle can be isolated in PRE Cross Reference Errors can be detected before they go into Production

© SAP 2009

̈

The system landscape topology, which can be used to detect cross-reference inconsistencies is a Preproduction system. A fourth system called Preproduction is brought between the QAS and the PRD. If this Preproduction system has the current software / configuration state of production, a cross-reference error can already be detected during tests in Preproduction.

© SAP AG

E2E200

2-19

Soft w a re Change St ra t e gie s: U nit Ove rvie w Dia gra m
Software Change Strategies Lesson 1: Challenges in a Three-System-Landscape Lesson 2: Release Management Lesson 3: Advanced System Landscapes Lesson 4: Transport Dependencies and Solution Transports Appendix: SAP Change and Transport System

© SAP 2009

© SAP AG

E2E200

2-20

Re lea se M a na ge me nt

Background
̈ ̈

During the lifecycle, changes of different types, risk/impact and criticality will need to be developed, tested and imported into production For bundling of changes different possibilities and strategies exist – from a permanent flow of changes (at a given point in time, all changes are moved through the landscape and imported into production) to a strict release management (bundling of changes to larger packages – releases – that are transported and quality assured as one entity). A strict bundling of changes into different release categories enables an effective Quality Management process and reduces the frequency of importing changes to production. Recommended approach However in some cases bundling of changes into releases slows down the realization time of changes. This leads to the parallel project approach.

̈

̈

© SAP 2008

© SAP AG

E2E200

2-21

Soft w a re Change St ra t e gie s: U nit Ove rvie w Dia gra m
Software Change Strategies Lesson 1: Challenges in a Three-System-Landscape Lesson 2: Release Management Parallel Projects Synchronized Releases Lesson 3: Advanced System Landscapes Lesson 4: Transport Dependencies and Solution Transports Appendix: SAP Change and Transport System

© SAP 2009

© SAP AG

E2E200

2-22

Work ing w it h Pa ra lle l Proje c ts

Trade Promotion Management Rollout CIC 1.1 Implementation CIC 2.0

Go Live

01 / 2006

04 / 2006

07 / 2006

10 / 2006

01 / 2007

© SAP 2009

̈

Projects are defined by their release cycles. Any change, which is related to a project, moves synchronously from development through test to production or delivery.

© SAP AG

E2E200

2-23

Work ing w it h Pa ra lle l Proje c ts: Obje c t Conflic t s a nd Obje c t Depende nc ie s

Project 1 Project 1 Conflicts Project 2 Project 2
Dependencies

DEV

DEV

© SAP 2009

̈ ̈ ̈

There are two types of problems when working with parallel projects. Object Conflicts: This means that the same objects are contained in different projects. The project which is imported last, overwrites the objects of the other project. Therefore, the project which was imported first might not work anymore after the import of project 2. Object Dependencies: Objects in different projects use each other, for example, a program in project 1 calls an object included in project 2. If only one of the projects is imported into another system, it will fail. This problem is called cross-reference inconsistency.

̈ ̈

© SAP AG

E2E200

2-24

Re com me nda t ion for Pa ra lle l Proje c t s: Pre produc t ion Syst e m

DEV

QAS

PRE

PRD

The Pre-Production System (PRE) has the current software/configuration state of production plus the next coming project The next upcoming project cycle can be isolated in PRE Cross Reference Errors can be detected and solved before they go into Production

© SAP 2009

̈

The solution for cross-referencing inconsistencies is a Pre-Production system. If the Pre-Production system has the current software / configuration state of production, the error can already be detected and fixed in Pre-Production.

© SAP AG

E2E200

2-25

Pa ra lle l Proje c t s Be st Pra c t ic e Re com me nda t ions
Best practice recommendations for parallel projects
̈ ̈ ̈ ̈ ̈

An estimation of potential collisions (objects changed differently in several projects) should be performed before a project starts by the responsible development teams. If no collisions are expected, projects can be done in parallel. If collisions are expected, projects should be done in sequence or handled as one common project. If possible, several small projects should be bundled into one big project with a common GoLive date. Working with parallel projects requires a stringent governance and process control. Ideally a quality manager should be responsible for controlling the collisions and define possible workarounds. Tools should be available to mitigate the risk of undetected collisions. These tools can be:
̈ ̈ ̈

̈

Release transport requests late in order to keep the object lock Lock objects which are identified as potential collisions in a dummy transport Put objects which are identified as potential collisions to the critical objects list

̈ ̈

Swap out long running projects into separate environments. Clearly assign transport requests to their project, either by using CTS projects or by using a naming convention for the short text of the transport requests.

© SAP 2009

© SAP AG

E2E200

2-26

Pa ra lle l Proje c t s Bundle T ra nsport s in CT S Proje c t s
Create an IMG project and activate the CTS project functionality

© SAP 2009

̈ ̈ ̈ ̈

SAP offers the use PROJECTS, to group comprehensive customizing and development activites. With projects, you can define the customizing scope you want to cover. Please note that this is only important if you have several, simultaneous project activities. By activating a CTS project to work with your customizing project, you can link every change request to a CTS project. The CTS project attribute of the change request lets you control the import of these changes into several target systems.

© SAP AG

E2E200

2-27

CT S Proje c t s in t he I m port Que ue

Project Assignment

Predecessor information

̈ ̈

Transport requests can be bundled in CTS projects and imported together with the Import Project All method. For this you have to filter the import queue by the Project ID. Dependencies with other projects are automatically detected at the time when a transport request is exported. The column Predecessor indicates that a predecessor transport with an identical object exists in another CTS project. By clicking on the predecessor symbol you see the relevant transport and object information.

̈

© SAP 2009

̈ ̈

If the project intersection check is activated for a CTS project a sequence is proposed between the requests of different projects if they contain identical objects. The Chain-symbol indicates that there is a predecessor transport in another CTS project which contains the same object. If you doubleclick on it, you see the predecessor transport request and the object in conflict. You can decide to include the predecessor transport in the import of the CTS project. If the project intersection is activated, the export of a transport request might have a long runtime. Therefore CTS projects that are completely imported should be closed (e.g. in transaction SPRO_ADMIN). Then they are not included in the intersection check any longer.

̈

© SAP AG

E2E200

2-28

Soft w a re Change St ra t e gie s: U nit Ove rvie w Dia gra m
Software Change Strategies Lesson 1: Challenges in a Three-System-Landscape Lesson 2: Release Management Parallel Projects Synchronized Releases Lesson 3: Advanced System Landscapes Lesson 4: Transport Dependencies and Solution Transports Appendix: SAP Change and Transport System

© SAP 2009

© SAP AG

E2E200

2-29

Re lea se M a na ge me nt

Background
̈

A strict bundling of changes into releases enables an effective Quality Management process and reduces the frequency of importing changes to production. Recommended approach To leverage the benefits of Release Management, it is of key importance to define clear criteria for change categories that easily can be followed and monitored. The duration of the release cycles needs to be aligned with the business requirements for flexibility and speed.

̈ ̈

Change Categories guarantee the right testing approach for each change. They also allow maximum flexibility and speed for the realization of uncritical changes.

© SAP 2008

© SAP AG

E2E200

2-30

De c ision Crit e ria for Change Ca t egorie s

Urgent Corrections
̈ ̈ ̈

Critical Business Process does not work Resolution of priority 1 incidents See SAP Note 67739 for the definition of priorities

Low Impact Changes
̈ ̈

Non-invasive repetitive changes were the impact is well known. A positive list should be provided (shift plans, read only reports, SAP script forms, authorizations, currency exchange rates, …)

Bugfixes and Small Enhancements
̈ ̈ ̈

Corrections to existing functionality Resolution of incidents that come from the service desk procedure Small enhancement requests with limited effort (e.g. less than 5 days for development and testing)

New Demand
̈ ̈ ̈

Completely new functionality Enhancement requests with a major effort (e.g. more than 5 days) System outage required

© SAP 2009

̈

Note 67739 explains the priority for problem messages, that customers send to SAP. The criteria for the category “very high” can be taken as criteria for emergency changes.

© SAP AG

E2E200

2-31

Re lea se M a na ge me nt Be st Pra c t ic e Re com me nda t ion
Major Release Transport Cycle every: Change Categories Priorities Test focus Some 3 - 6 months Minor Release 1 - 4 weeks Bugfixes and small enhancements (+ ReImport of Emergency Changes) Normal Core processes and new features Non-critical configuration, medium or low priority incidents Low Impact Changes 1 – 3 days Low impact changes only (non invasive and impact well known) Normal Ideally, regressions for the related core processes by automated tests Pre-approved repetitive standard changes e.g. authorizations, currency exchange rates Urgent Corrections On Request only

All types of changes including invasive changes Normal Complete test scope

Emergency only

Emergency only Regressions for core processes by automated tests Any changes to solve high priority incidents

Examples

New (major) functions, Support / Enhancement Packages, Upgrades


Development phase Test and emergency correction phase Go-live phase Post Go-live support phase

Urgent Corrections Minor Release Major Release

© SAP 2008

© SAP AG

E2E200

2-32

Re lea se M a na ge me nt Eva lua t ion
Advantages of Bundling Changes to Releases
̈

Frequency of changes to production is dramatically reduced
̈ ̈

Endusers will not be confused by frequently changed functionality The rollout of new functionality can be done in a controlled way, including announcement, end user training, testing and documentation Enough time for testing invasive changes in Major Releases. Common regression and integration testing for several projects in one run – resulting in lower cost and reduced risk (dependencies are taken into account) Appropriate tests and infrastructure for testing Minor Releases Reduction of daily changes to the absolute emergencies No restriction to Non-invasive standard changes (can be imported as needed – without impacting stability/consistency of the landscape å maximum flexibility)

̈

For each type of change the right testing approach is taken
̈

̈ ̈ ̈ ̈ ̈ ̈

Risk of inconsistencies (“forgotten transports” or sequence violations) reduced Reduced administration efforts for transport management as all projects move from one phase to another at a single point in time Using change categories consequently still allows flexibility for urgent changes

© SAP 2008

© SAP AG

E2E200

2-33

Re lea se M a na ge me t M a inte na nc e Ca lenda r
Maintenance Calendar
̈

Especially for Major Releases it is required to set up and publish a fixed maintenance calendar for a complete year. This calendar also should include SAP maintenance activities (Support Packages and/or Enhancement Packages). The maintenance calendar needs to cover all relevant systems across the complete landscape. This will help to reduce integration tests for processes across system borders. A well defined maintenance calendar is an important condition for the approval process and for planning the changes. This calendar needs to include also the related test activities and code freeze periods. In order to measure and optimize downtimes caused by release imports, the pre-production system should be leveraged to verify import times.

̈ ̈ ̈

© SAP 2008

© SAP AG

E2E200

2-34

M a inte na nc e Planning Ca lenda r Ex a mple
Maintenance Calender for 2010
January
2 Mon [1] 3 Tue 4 Wed 5 Thu 6 Fri Epiphany (G) 7 Sat 8 Sun 9 Mon [2] 10 Tue 11 Wed 12 Thu 13 Fri 14 Sat 15 Sun 16 Mon [3] 17 Tue 18 Wed 19 Thu 20 Fri 21 Sat 22 Sun 23 Mon [4] 24 Tue 25 Wed 26 Thu 27 Fri 28 Sat DC Main (G) 29 Sun DC Main (G) 30 Mon [5] 31 Tue Maintenance Cycle Functional Release ERP BI CRM

February
1 Wed 2 Thu 3 Fri 4 Sat 5 Sun 6 Mon [6] 7 Tue 8 Wed 9 Thu 10 Fri 11 Sat 12 Sun 13 Mon [7] 14 Tue 15 Wed 16 Thu 17 Fri 18 Sat 19 Sun 20 Mon [8] 21 Tue 22 Wed 23 Thu 24 Fri 25 Sat 26 Sun 27 Mon [9] 28 Tue

ERP BI CRM

March
1 Wed 2 Thu 3 Fri 4 Sat 5 Sun 6 Mon [10] 7 Tue 8 Wed 9 Thu 10 Fri 11 Sat 12 Sun 13 Mon [11] 14 Tue 15 Wed 16 Thu 17 Fri 18 Sat 19 Sun 20 Mon [12] 21 Tue 22 Wed 23 Thu 24 Fri 25 Sat 26 Sun 27 Mon [13] 28 Tue 29 Wed 30 Thu 31 Fri

ERP BI CRM
ISP ICP IWP

April
1 Sat 2 Sun 3 Mon [14] 4 Tue 5 Wed 6 Thu 7 Fri 8 Sat 9 Sun 10 Mon [15] 11 Tue 12 Wed 13 Thu

ERPBI CRM

May
1 Mon [18] 2 Tue 3 Wed 4 Thu 5 Fri 6 Sat 7 Sun 8 Mon [19] 9 Tue 10 Wed 11 Thu 12 Fri 13 Sat 14 Sun 15 Mon [20] 16 Tue 17 Wed 18 Thu

ERPBI CRM

1 Sun New Year´s Day [1]

14 Fri Good Friiday (G) 15 Sat
ISP ICP IWP

16 Sun Easter Day 17 Mon Easter Monnday (G) [16] 18 Tue 19 Wed 20 Thu 21 Fri 22 Sat 23 Sun 24 Mon [17] 25 Tue 26 Wed 27 Thu 28 Fri 29 Sat 30 Sun

19 Fri 20 Sat DC Main (G) 21 Sun DC Main (G) 22 Mon [21] 23 Tue 24 Wed 25 Thu Ascension Day (G) 26 Fri 27 Sat 28 Sun 29 Mon [22] 30 Tue 31 Wed

© SAP 2009

̈ ̈ ̈ ̈ ̈ ̈

This example shows the maintenance calendar of a solution consisting of a BW, CRM and ERP system. Support Packages are imported from the end of January to beginning of February. Every second weekend, there are maintenance deliveries (Go-Lives of maintenance cycles). Sometimes, there are codefreezes due to quarter end activities. Projects can be incorparated into any maintenance cycle. This gives flexibility to the projects as there are many Go-Live windows. This calendar shows 2 Best Practices: • All systems in a solution should be delivered with projects or maintenance cycles at the same time. This is due to the dependencies of changes in different systems (see „transport dependencies“). • The system owners are also responsible for maintenance. First, the maintenance is planned. Then, the implementation projects consider the maintenance plan in their project schedule.

© SAP AG

E2E200

2-35

Soft w a re Change St ra t e gie s: U nit Ove rvie w Dia gra m
Software Change Strategies Lesson 1: Challenges in a Three-System Landscape Lesson 2: Release Management Lesson 3: Advanced System Landscapes Lesson 4: Transport Dependencies and Solution Transports Appendix: SAP Change and Transport System

© SAP 2009

© SAP AG

E2E200

2-36

Soft w a re Change St ra t e gie s: U nit Ove rvie w Dia gra m
Software Change Strategies Lesson 1: Challenges in a Three-System Landscape Lesson 2: Release Management Lesson 3: Advanced System Landscapes System and Client Roles Customer Requirements and Resulting Landscapes Lesson 4: Transport Dependencies and Solution Transports Appendix: SAP Change and Transport System

© SAP 2009

© SAP AG

E2E200

2-37

Syste m Role s a nd Clie nt s De ve lopme nt Syst e m 1 /2
Configuration Configuration Unit Test Unit Test Test Data Backup Test Data Backup

Syst e m Role
̈

The development system (DEV) is where all initial configuration and development occurs, and unit testing is performed.

Client s
Configuration ̈ Source of all development and customizing changes. ̈ Only this client is changeable, all other clients are locked. ̈ Does not contains transaction and master data. ̈ Should never be overwritten. ̈ Unit Test: ̈ This client should be used to test customizing changes before the transports are released. The customizing can be transferred into this client via transaction SCC1 ̈ Receives all transports from the configuration client immediately ̈ When the test data is destroyed or consumed by the testers, this client can be refreshed from the Test Data Backup client.
̈

© SAP 2009

© SAP AG

E2E200

2-38

Syste m Role s a nd Clie nt s De ve lopme nt Syst e m 2 /2
Configuration Configuration
̈

Test Data Backup
̈

Unit Test Unit Test Test Data Backup Test Data Backup
̈

This client is the source for refreshing the unit test client and the clients in the QA system. These clients need to be refreshed on demand, e.g. when new test data is required or when old test data has been consumed by the testers. Master data can be distributed via ALE into this client. Transactional data must be created manually. Alternatively it can be created via eCATT or TDMS. Receives all transports from the configuration client after they have been released.

̈

© SAP 2009

© SAP AG

E2E200

2-39

Syste m Role s a nd Clie nt s Qua lity Assura nce Syst e m
Integration Test Integration Test

Syst e m Role
̈

Data Conversion Data Conversion

The Quality Assurance system (QAS) is used as a testing environment. Here are integration testing and data conversion testing executed.

Clie nt s
̈

Integration Test
̈ ̈ ̈

The Scenario Test and the Integration Test are executed in this client. Receives all transports from the configuration client once approved. When the test data is destroyed this client can be refreshed from the Test Data Backup client. Trial data loads and data conversions for the next Release Receives all transports from the configuration client once approved. When the test data is destroyed this client can be refreshed from the Test Data Backup client. If the data conversion causes a high workload, it can be set up as a separate system in order to avoid a negative impact on the integration testing.

̈

Data Conversion
̈ ̈ ̈ ̈

© SAP 2009

© SAP AG

E2E200

2-40

Syste m Role s a nd Clie nt s Pre -Produc tion Syst e m 1 /2
Syst e m Role
Preproduction Preproduction
̈

Pre-Production system (PPD)
̈

The Pre-Production system is the environment for the Final Integration Test once the scope of the release has been fixed (Release Test), Regression Test, Technical System Test including Performance and Volume Test and User Acceptance Test. Furthermore production support changes are tested here (particularly while QA is being used for Integration Testing of a new development release). The Pre-Production environment is owned by the Production Support organization The Pre-Production system must not be “corrupted” with new Release functionality or new Maintenance Packages until the appropriate time (ideally as close to go-live as possible). All Pre-Production systems should be regularly refreshed from Production, if possible.

̈ ̈

̈

© SAP 2009

© SAP AG

E2E200

2-41

Syste m Role s a nd Clie nt s Pre -Produc tion Syst e m 2 /2
Syst e m Role (continued)
Preproduction Preproduction
̈

The overall setup of all Pre-Production systems should mimic Production as closely as possibly, including hardware-architecture, to ensure that the testing performed is valid. In detail this means:
̈ ̈ ̈ ̈

Same high-availability and fail-over solutions Same hardware architecture, processor types and storage subsystem Same disk size and data volume (due to system copy) The number of dialog instances can be reduced and possibly enhanced on demand by means of virtualization (only needed when a full and exact simulation of the productive workload is possible)

Clie nt s
̈

The Pre-Production system has only one client.

© SAP 2009

© SAP AG

E2E200

2-42

Syste m Role s a nd Clie nt s Produc t ion Syst e m (PRD)
Syst e m Role
Production Production
̈ ̈

Production (PRD) is where end users actually work It represents the live Solution.

Clie nt s
̈

Production (PRD) should contain only one productive client.

© SAP 2009

© SAP AG

E2E200

2-43

Re com me nded T ra nsport Rout e s Ex a mple : Single T ra ck 4 -Syst e m Landsca pe
2
Configuration Configuration

2

Integration Test Integration Test Preproduction Preproduction Data Conversion Data Conversion

1

SCC1

Production Production

Unit Test Unit Test Test Data Backup Test Data Backup

On demand: Client Copy

On demand: System Copy

Tim ing of Transport Act ivit ies
̈ ̈ ̈ ̈

The export of a transport request must be planned carefully, because it should not be deleted any more from the import queues once it has been released. Transport requests should be tested in the Unit Test client before they are released Once a transport request has been released it can be imported immediately into the clients of QA system and into the Unit Test client and Test Data Backup client. The import into preproduction should take place as late as possible. Only changes that are supposed to go to production with the next GoLive should be allowed to enter Pre-Production.

© SAP 2009

© SAP AG

E2E200

2-44

Syste m Role s a nd Clie nt s Sa ndbox Syst e m (SBX)
Syst em Role
Sandbox Sandbox
̈

Sandbox environments are made available for testing specific functionality and in particular system-wide or “non-removable” changes (e.g. Activating extension sets). Transports should not be allowed out of the Sandbox. It is a purely standalone landscape with no connections to other environments. However the sandbox should receive transports from DEV in order to stay up-to date. The Sandbox system is required to cater for initial testing of Support Packs or other solution components (e.g. Extension Sets), without impacting on the development environments.

̈

̈

© SAP 2009

© SAP AG

E2E200

2-45

Syste m Role s a nd Clie nt s T ra ining Syst e m (T RN )
Training Execution Training Execution

Syst e m Role
̈

Training Master Training Master

The Training environment is where learning and training course execution occurs. Some demonstration sessions for “future” Solutions may also be conducted within this system. A separate Training system is recommended to ensure that Training is able to be developed and conducted without impacting other phase activities like testing – or likewise being impacted by these activities.

̈ ̈

Client s
̈

Training Master
̈ ̈ ̈

Used to build all training courses and refresh Training Execution Client. Receives transports once approved from DEV. Exercises and demos are prepared here including sample data. Training takes place in this client Regularly refreshed from Training Master for training execution.

̈

Training Execution
̈ ̈

© SAP 2009

© SAP AG

E2E200

2-46

Soft w a re Change St ra t e gie s: U nit Ove rvie w Dia gra m
Software Change Strategies Lesson 1: Challenges in a Three-System Landscape Lesson 2: Release Management Lesson 3: Advanced System Landscapes System and Client Roles Customer Requirements and Resulting System Landscapes Lesson 4: Transport Dependencies and Solution Transports Appendix: SAP Change and Transport System

© SAP 2009

© SAP AG

E2E200

2-47

Sc ena rio 1 : M a int enance Sc ena rio

Sc e na rio De scription
The major development cycle and the rollout are complete. Ongoing changes are limited to Support Packs, operating system and database patches. SAP configuration changes are required to support minor business requirements. There is an occasional need to train new users in the use of the system.

Urgent Corrections

Maintenance Packages

© SAP 2009

̈

This scenario typically consists of a SAP R/3 system and maybe a SAP BI system on an old release serving one or several countries. The major development cycle and the rollout are complete. Ongoing changes are limited to Support Packs, operating and database patches. SAP configuration changes are required to support minor business requirements. In this case a three-system-landscape might be sufficient. The maintenance transports are bundled into packages, so that they can be tested alltogether. This scenario works well, if the number of urgent corrections is low. Non-urgent corrections should be released late, so that QAS stays close to PRD for the test of urgent corrections.

̈ ̈ ̈ ̈

© SAP AG

E2E200

2-48

Re c omm e nde d La ndsc a pe for M a int e na nce Sc e na rio

4 -Syst e m T ra nsport La ndsca pe

Supporting systems

Production Support

SBX SBX

S DEV DEV QAS QAS QAS QAS

S PPD PPD

M PRD PRD

L

De sc ription/Evalua tion
̈In DEV only urgent corrections, standard changes and smaller non-invasive functional enhancements are developed. ̈PPD is required e.g. for testing of Urgent Corrections during the time periods while the Minor Release is “blocking” QAS ̈If the number of changes is very small, a 3-system landscape might be sufficient ̈Any invasive changes – like Support Packages – are tested in SBX It is important to move the SP fast through the landscape in order to limit the time period of inconsistent releases in the landscape å Reduction of SP transition time by thorough testing in SBX, clear definition of test scope (reflecting the changes of the concrete SP), test automation, ensured availability of test resources ̈If the number of changes is very small, a 3-system landscape might be sufficient
© SAP 2008

Explanation of the required system sizes
̈ ̈ ̈

S: small data volume, no HA, small CPU, RAM M: full data volume, HA, reduced CPU, RAM L: full data volume, HA, full CPU, RAM

© SAP AG

E2E200

2-49

Sc ena rio 2 : I m ple m ent a t ion Sce na rio
Sc e na rio De scription
This scenario typically consists of several integrated SAP Business Suite systems which represent an integrated solution Three major activities need commence in parallel: ̈ Safe maintenance of the production environment – Implementation of SAP Support Packs, operating and database patches to keep the production instances current – Implementation of corrections to the customer-specific code ̈ On-boarding of new countries into the global or regional instances including user training and minor configuration changes to support local business requirements ̈ Development of a new integrated release to support new business requirements driving more significant configuration changes and limited customisation.


© SAP 2009

Emergency Corrections Maintenance Packages Project Releases (functionality)

© SAP AG

E2E200

2-50

Sc ena rio 2 : I m ple m ent a t ion a nd Count ry Rollout of a ne w SAP Busine ss Suit e Solut ion

GoLive Date

2010

2011

2012

Development Plan

Release 1

Release 2

Release 3

Rollout Plan

Region1 Region2 Region3

Release 1

Release 2 Release 2

Release 3 Release 3 Release 3

© SAP 2009

̈

This scenario typically consists of several SAP Business Suite products which are rolled out worldwide or in a major region. The instances are fully integrated. Three major activities need commence in parallel: • Implementation of Support Packs, operating and database patches to keep the production instances current • On-boarding of new countries into the new solution including user training and minor configuration changes to support local business requirements • Development of a new integrated release to support new business requirements driving more significant configuration changes and limited customisation.

̈ ̈ ̈

The solution is rolled out sequentially, region by region. After the go live of a release, this release has to be maintained, while a new release is developed. The rollout plan and the development plan have to be synchronized, because a region needs a certain release level in order to go live.

© SAP AG

E2E200

2-51

Rec omm ended La ndsca pe for I m plem ent at ion Scena rio

Ex t e nde d Phase d Tra nsport La ndsc a pe
Production Support

S MDV MDV
Retrofit

S MQA QAS MQA QAS MPP MPP

M PRD PRD

L

Cutover

Supporting systems

S SBX SBX TRN TRN PDV PDV
Project Development

S PQA PQA PPP PPP

M

Not permanently needed

De sc ript ion
̈ The main principle of this design is the decoupling of production support and project development. ̈ In the Production Support track all urgent corrections are created as well as Standard Changes and “Minor Releases” consisting of uncritical changes. ̈ In the Project Development track, the development of larger new functionality is done – Major Releases and SAP Support Packages å Only at well defined points in time, the new developments are taken over into the Production Support track. This is done via an explicit cut over after a sufficient testing period in the PPP system. The new release needs to be accepted by the business as well as by the owner of the Production Support track ̈ Changes done in the Production Support track are retrofitted into the project track (in a timely manner)
© SAP 2008

Explanation of the required system sizes S: small data volume, no High Availability (HA), small CPU, RAM ̈ M: full data volume, HA, reduced CPU, RAM ̈ L: full data volume, HA, full CPU, RAM
̈

Why is a single track landscape not sufficient? ̈ A single track landscape in principle does work. But it comes with the following limitations and risks: • Challenges and risks arise mainly from the fact that all types of changes need to be managed in a single development system and in a single transport track. (In a best practices environment, there are 5 types of changes – emergencies, minor releases, major releases, standard changes and SAP maintenance) • There are conflicts that will need to be managed explicitly by respective processes. These conflicts will lead to limitation in either the project development or the creation of corrections (one has to wait). • Limited flexibility for developing new functions • Limited test capabilities for testing new functions (time and environment) • Risk for urgent corrections (the release/development status of the MDV system is different to the status of the production system. Potentially, in MDV there are new developments active the objects that needs to be corrected has been changed by a new development project) - urgent corrections potentially take longer to be implemented - the test environment for urgent corrections potentially is “far from production” (only the preproduction system reflects the status of production)
© SAP AG E2E200 2-52

Pha sed T ra nsport Landsc ape De c iding Fa c tors
De ciding Fact ors for Choosing a Pha sed T ra nsport Landsc ape
̈ Major ̈ The

implementation projects (Major Releases) or upgrade projects are in the pipeline of the production environment has a very high priority.

overall change volume is high

̈ Safety/quality/availability ̈ At

the same time, a high number of functional developments is required to meet the business needs (flexibility and agility) majority of changes is performed in the implementation project. This means the number of project changes is significantly higher than the number of changes in the Production Support landscape. This has a major influence on the effectiveness and efficiency of the whole change management process å needs to be ensured by appropriate governance.

̈ The

© SAP 2008

© SAP AG

E2E200

2-53

Sc ena rio 3 : I ntegra t ed Busine ss Suite Landsc ape
Sc e na rio De scription
This scenario consists of a PI integration hub. New integration scenarios are developed and implemented on an ongoing basis; the overall rate of content change is high. This overlaps with the requirement to apply Support Packs, operating system and database patches to keep the instance current. Changes are affecting several systems and need to be synchronized (PI and connected business systems)

Emergency Corrections Minor Releases Major Releases (Patches)

© SAP 2009

© SAP AG

E2E200

2-54

Sc ena rio 3 : I ntegra t ed Busine ss Suite Landsc ape

SCM PI
CRM

CRM SRM

ERP
Necessary change in the system

For all change categories solution transports are needed to incorporate the dependencies between the transports.
CRDK901024 PIDK920095 ERDK933362

© SAP 2009

̈ ̈

Changes of an interface in one system often induce changes in PI and the corresponding system. All these changes have to be transported at the same time to the productive solution. In this example ERP sends data to CRM via PI.

© SAP AG

E2E200

2-55

Soft w a re Change St ra t e gie s: U nit Ove rvie w Dia gra m
Software Change Strategies Lesson 1: Challenges in a Three-System-Landscape Lesson 2: Release Management Lesson 3: Advanced System Landscapes Lesson 4: Transport Dependencies and Solution Transports Appendix: SAP Change and Transport System

© SAP 2009

© SAP AG

E2E200

2-56

Ex a mple for Solut ion T ra nsport s Port a l iV ie w use s BI We breport
SAP Porta l
iView with reference to BI Webreport

SAP BI
BI Webreport

SAP ERP
Data Element

EPDK901024
̈

BWDK910095
̈

ERDK923362
̈

iView

BI Webreport

Data Element

Example:
̈ ̈ ̈

An iView uses a BI Webreport. The Webreport is based on an additional data element in the ERP backend. All three changes must be transported at the same time into the test and production environments.

© SAP 2009

© SAP AG

E2E200

2-57

Ex a mple for Solut ion T ra nsport s Port a l iV ie w use s BI We breport
Development Quality Assurance Production

EPD BWD ERD
EPDK901024 BWDK910095 ERDK933362

EPQ BWQ ERQ

EPP BWP ERP

A collection of transports in different development systems, that must be moved synchronously through the whole systemlandscape, is called a solution transport. Two Solution Manager Tools support solution transports:
̈ ̈

Quality Gate Management Change Request Management

© SAP 2009

© SAP AG

E2E200

2-58

Sync hroniza tion of Proje c t s a c ross t he Landsc ape
Development Landscape
Development Environment Transport Landscape ERP Transport Landscape CRM Transport Landscape EP Transport Landscape BW Transport Landscape PI SE80 DS & DI SE80 DS & DI System

QA Landscape
System SAP ERP

Production Landscape
System SAP ERP

SAP ERP

SAP CRM

SAP CRM

SAP CRM

Portal Content Administrator DS & DI

Enterprise Portal

Enterprise Portal

Enterprise Portal

SE80

BW

BW

BW

SE 80 Integration Builder

Process Integration (XI)

Process Integration (XI)

Process Integration (XI)

Enhanced Change and Transport System CTS+
© SAP 2009

Change Request Management Quality Gate Management

SAP Solution Manager

̈

This slide shows a three-system-landscape, that contains the most popular products of SAP. It also shows one topic, which has not been discussed yet. Since SAP delivers products on an ABAP and a Java-Stack, it has to be also assured, that the deployment of Javabased Solutions is integrated in the transport mechanism. This topic is adressed via CTS+(Enhanced Change and Transport System).

© SAP AG

E2E200

2-59

Appe ndix : SAP Cha nge and T ransport Syst e m

Software Change Strategies Lesson 1: Challenges in a Three-System-Landscape Lesson 2: Release Management Lesson 3: Advanced System Landscapes Lesson 4: Transport Dependencies and Solution Transports Appendix: SAP Change and Transport System

© SAP 2009

© SAP AG

E2E200

2-60

SAP Change a nd T ra nsport Syst e m

Change and Transport System

Change and Transport Organizer (CTO)
Transactions: SE09/SE10/SE01

Transport Management System (TMS)
Transaction: STMS

Transport Tools (tp, R3trans, …)

© SAP 2009

̈

The change and transport system is divided roughly in three areas: • The change and transport organizer to manage transport requests, which consists of the transactions SE09, SE10 and SE01 • The transport management systen, which contains transaction STMS to manage the transport configuration • OS-level tools like tp or R3trans, which are used to execute transport steps

© SAP AG

E2E200

2-61

T ra nsport Orga nize r & T ra nsport Reque st s

SE80/SE37…. ABAP-Objects
Automatic Change Recording
Reports, Function Modules, Dictionary Objects, ….

SE09 Task Transport Request

All workbench tools are tightly integrated with the SE09 functions. All changes are automatically recorded within tasks. A transport request is the container for transporting.

© SAP 2009

© SAP AG

E2E200

2-62

Re lea se T ra nsport Reque st s

Task

Transport Request

Import Queue

Release

Release
EPDK9000H

DEV Export

Transport Directory
R3trans data file

Pointer

© SAP 2009

̈

After release the transport request is exported as data file to the transport directory (../trans/data) and the request is listed in the import queue

© SAP AG

E2E200

2-63

I m port T ra nsport Reque st t o T a rge t Syst e m

Import Queue
EPDK9000H

TP

Target System A Import

Transport Directory
R3trans data file

© SAP 2009

̈

During import tp triggers R3trans to import the data into the target system and executes all relevant transport steps to generate and activate the objects.

© SAP AG

E2E200

2-64

Fle x ible Configura t ion of T ra nsport Route s

Consolidation Routes

Delivery Routes

Training System

QA System

Production Systems
© SAP 2009

̈ ̈ ̈

Here you can see an example for a the transport routes of a complex customer system landscape. There are several production systems and a training system connected. The green lines are consolidation routes. They go out of the development system. Development classes and packages are assigned to consolidation routes. This determines where a certain repository object is transported to. The black lines are delivery routes from the QA system to the production and training systems. All customizing and workbench requests that are imported into the QA system are automatically forwarded into the import queues of the production and training systems. Transports of copies which are imported into the QA system do not follow the transport routes into the production and training systems.

̈

̈

© SAP AG

E2E200

2-65

M ulti De ve lope r Ca pa bilit y

© SAP 2009

̈

The process for work with change requests is as follows: • The Team leader –who has the responsibility für a specific implementation- creates a change request and adds the team members to it. • All team members receive automatically a task inside the change rquest. Customizing or change of Repository objects done by the team member is then entered in the corresponding task.

̈

There are two main types of change requests for recording changes: • WB change request: They are used to record changes of repository obejcts, like reports, includes, tables, screens, transactions, and so on. • They also used to record all cross-client customizing changes, for example: logical systems, printers, file name defintions • CUST change requests include all client-specific customizing changes, which are normally client-specific table entries

© SAP AG

E2E200

2-66

Fea t ure s of t he ABAP Change and T ra nsport Syste m
Development Workbench
̈ ̈ ̈ ̈ ̈

Automatic recording of all changes in transport requests Object locking Classification of development objects in packages Version history Customizing logging

Transport Organizer
̈ ̈ ̈ ̈

Transport of single objects (lowest granularity) Teamwork capabilities (one transport request with several tasks for different developers) No control of correct transport sequence No control of completeness of transport requests

© SAP 2009

© SAP AG

E2E200

2-67

T M S Qua lity Assura nc e Proce dure

© SAP 2009

̈ ̈

TMS Quality Assurance increases the quality and the availability of the production systems by letting you check requests in the QA system before they are delivered to subsequent systems. To use this feature, activate the QA approval procedure in your QA system. When activated, transport requests are only forwarded to the delivery systems if all the QA approval steps are processed for each request in the QA system and each request has been approved. (When you configure the QA system, you determine how many QA approval steps have to be processed for each request.) If a check for an approval step is not successful, the entire request cannot be approved. Rejected requests are not imported into the delivery systems of the QA system. If you reject requests, there is the risk that errors may occur when they are imported into the delivery systems. This is a result of the requests containing objects that are referenced from other requests. It is safer to correct an error using a subsequent transport.

̈ ̈

© SAP AG

E2E200

2-68

T ra nsport of Copie s

DEV

QAS

PRE

PRD

Legend: Original Transport Transport of Copies

© SAP 2009

̈ ̈

Transports of Copies are special transport requests. These kind of requests are used to transport objects to only one specified SAP System, without delivery to another SAP System. Advantages: • Repository objects are locked as long as possible in DEV • Number of Transports in Production is reduced • Transports of copies are periodically imported into QAS but do not follow the transport routes into PRE • Only the original transport request can reach PRE • PRE remains a clean environment • Transport of Copies are used in the Change Request Management to create test transports, which are only transported to the test system, but which are never transported to the production system.

© SAP AG

E2E200

2-69

Crit ic a l Obje c t s Che ck

DEV: 0 QAS: 7 PRD: 3

Request 1 DEVK900016 2 DEVK900018 3 DEVK900020 4 DEVK900023 5 DEVK900002 6 DEVK900033 7 DEVK900035

Object list Object list R3TR PROG ZABAP Object list R3TR PROG ZABAP R3TR TABU ZTABLE Object list R3TR PROG ZABAP R3TR TABU ZTABLE ............... PROG ZABAP Object R3TR list R3TR TABU ZTABLE ............... PROG ZABAP Object R3TR list R3TR TABU ZTABLE ............... PROG ZABAP Object R3TR list R3TR TABU ZTABLE ............... PROG ZABAP Object R3TR list R3TR TABU ZTABLE ............... PROG ZABAP R3TR R3TR TABU ZTABLE ............... R3TR TABU ZTABLE ............... ...............

Compare critical objects

R3TR

TABU

ZTABLE

Table of critical objects
© SAP 2009

̈

To check if the change requests in an import queue contain critical objects that should not be imported into the target system, go to the Import Overview 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 icon. The critical objects are highlighted in color. Before performing this check, you need to have maintained the critical transport objects in the SAP System whose import queue you want to check for critical objects. To display or maintain the critical transport objects defined for the relevant SAP System, call transaction STMS in the SAP System for which you want to display/maintain the critical objects. Choose Overview åImports åExtras Critical transport objects. Since the table of critical objects is a Customizing table, it should be maintained in the development system, and then transported to other SAP Systems from there. The TMS check for critical transport object is executed at the time of the import into production. The transport parameter CHK_CRIOBJ_AT_EXPORT allows a check for critical objects before release.

̈ ̈

̈ ̈ ̈

© SAP AG

E2E200

2-70

Ex a mple s for Crit ic a l T ra nsport Obje c ts

Uncritical Objects
̈ ̈ ̈

Forms, e.g. SAP Scripts Authorizations Simple Customizing (without generation of repository objects)

Critical Objects
̈ ̈ ̈

Customizing with generation of repository objects (e.g. LIS) Report sources Dictionary Objects

Very Critical Objects
̈ ̈ ̈

Frequently used Sources (e.g. User Exits) Dictionary Objects which must be converted (esp. Big tables like vbap, coep) Dictionary Objects which are frequently used by other objects (komk, komp, t001w)

Critical Objects from a Business Perspective
̈ ̈ ̈

SD condition tables Central user exits Complete development classes in business critical areas

© SAP 2009

̈

Critical Transport Objects have a long import runtime. During the time of the import, inconsistencies, dumps and, in rare cases, even logical errors (wrong results) can occur in the system. Therefore, critical transport objects should be known. Imports that contain critical transport objects should be imported during downtime or, at least, during times of low system usage. Business critical objects are central objects, which are used by many applications or very critical applications. If they are changed it might have severe side-effects in many areas. Therefore, an extended test is needed before these objects are imported into production.

̈

© SAP AG

E2E200

2-71

Soft w a re Change St ra t e gie s : U nit Sum m a ry

You should now be able to:
̈ ̈ ̈ ̈

Understand the limitations of the three-system-landscape Describe pros and cons of parallel projects, synchronized releases and maintenance cycles Understand the pros and cons of advanced system landscapes Understand, which tools can be used to manage transport dependencies

© SAP 2009

© SAP AG

E2E200

2-72

Exercises
Unit: Software Change Strategies

In this exercise, you can test your knowledge on system landscapes and transport strategies.

This exercise consists of questions and answers.

2-1-1 Which of the following are risks when using the Import Single strategy? More than one answer is correct. Decide whether each answer is true or false.

True

False Inconsistencies between workbench and customizing requests Cross-reference inconsistencies due to forgotten transports Object versions in DEV and PRD can be different due to long-running implementation projects Wrong transport sequence

© SAP AG

E2E200

2-73

2-1-2 What is recommended when several parallel implementation projects with different golive dates are running in one transport landscape? Please choose the correct answer.

Unit test client Separate development client for each project Preproduction system

2-1-3 Which of the following are advantages of a phased system landscape? More than one answer is correct. Decide whether each answer is true or false.

True

False Faster realization of business requirements Implementation projects and maintenance tasks can be separated. No code freeze required Clean environment for emergency corrections

© SAP AG

E2E200

2-74

Solutions
Unit: Software Change Strategies

2-1-1

Which of the following are risks when using the Import Single strategy? More than one answer is correct. Decide whether each answer is true or false.

True O

False X Inconsistencies between workbench and customizing requests Cross-reference inconsistencies due to forgotten transports Object versions in DEV and PRD can be different due to long-running implementation projects Wrong transport sequence

X

O

O

X

X

O

2-1-2

What is recommended when several parallel implementation projects with different go-live dates are running in one transport landscape? Please choose the correct answer.

O O X

Unit test client Separate development client for each project Preproduction system

© SAP AG

E2E200

2-75

2-1-3

Which of the following are advantages of a phased system landscape? More than one answer is correct. Decide whether each answer is true or false.

True O X

False X O Faster realization of business requirements Implementation projects and maintenance tasks can be separated No code freeze required Clean environment for emergency corrections

O X

X O

© SAP AG

E2E200

2-76

Enha nc ed Cha nge and T ransport Syst e m

Unit 1 Introduction to E2E Change Control Management Unit 2 Software Change Strategies Unit 3 Enhanced Change and Transport System Unit 4 Solution Documentation Unit 5 Quality Gate Management Unit 6 Change Request Management Unit 7 Maintenance Management Unit 8 Test Management Unit 9 Change Diagnostics

© SAP 2009

© SAP AG

E2E200

3-1

Enha nc ed Cha nge and T ransport Syst e m : U nit Obje c t ive s

After completing this unit, you will be able to:
̈ ̈

Explain how the Enhanced Change and Transport System (CTS+) works Understand the basic concepts of Enterprise Portal, SAP NetWeaver Development Infrastructure, and Process Integration and how they are supported by CTS+ Describe best practices for the setup and usage of CTS+ in different scenarios

̈

© SAP 2009

© SAP AG

E2E200

3-2

Enha nc ed Cha nge and T ransport Syst e m : U nit Ove rvie w Dia gra m
Enhanced Change and Transport System Lesson 1: CTS+ Overview Lesson 2: Working with CTS+ Lesson 3: Enterprise Portal and CTS + Lesson 4: SAP NetWeaver Development Infrastructure and CTS+ Lesson 5: Process Integration and CTS+ Appendix: CTS+ Transport Parameters

© SAP 2009

© SAP AG

E2E200

3-3

Sit ua tion Be fore Enhanced CT S – V a rious T ra nsport T ools Are U se d
Various Transport Tools Multiple Types of Backends

CTS

File System, CMS

File System

CMS

...

SAP NetWeaver SAP NetWeaver SAP NetWeaver AS ABAP AS ABAP AS ABAP

ESR/PI/XI XI/PI System XI/PI System System
on SAP NetWeaver (Dual Stack)

Portal System
on SAP NetWeaver AS Java

SAP NetWeaver SAP NetWeaver AS Java AS Java on SAP NetWeaver AS Java

NW DI

... ... ...

Multiple Development Workbenches

...

© SAP 2009

̈

SAP offers many tools and Workbenches to develop applications or create content for end users. There are also many different tools which are used for transporting the applications from a development system to a productive system through a system landscape. In some cases, the tool supports a transport, like CTS, for example, does it for the ABAP Workbench. In other cases, for example, in the Portal, both an import and an export mechanism is available; however, the system administrator has to take care that the files are available at the right locations when performing an import. There is a difference between Export / Import and Transport. Export / Import means that the changes made in an application or newly created content can be collected and then exported in a file format. This file needs to be stored somewhere. An administrator has to upload the file to the target system and start the import or deployment. Transport includes logistics for the exported files. The administrator has to start the import, but he does not have to watch for the location of the files. In addition, there is an option to track what has been imported, to monitor the results, and to get reports on import statuses. CTS does all this for ABAP-based programming and customizing.

̈

© SAP AG

E2E200

3-4

Enha nc ed CT S – One T ra nsport T ool for M ult iple Work benc he s
One central Transport Tool Multiple Types of Backends
SAP NetWeaver SAP NetWeaver SAP NetWeaver AS ABAP AS ABAP AS ABAP

Enhanced CTS

ESR/PI/XI XI/PI System XI/PI System System
on SAP NetWeaver (Dual Stack)

Portal System
on SAP NetWeaver AS Java

SAP NetWeaver SAP NetWeaver AS Java AS Java on SAP NetWeaver AS Java

NW DI

... ... ...

Multiple Development Workbenches

...

© SAP 2009

̈

Enhanced CTS offers the possibility to transport objects created in other languages than ABAP via the Change and Transport System of ABAP. The goal is to have one Transport Tool (CTS) which supports all workbenches and applications when it comes to transports. The tools for creating applications and creating content remain the same. Options to attach applications or content to a CTS Transport Request are integrated into the different workbenches. The level of integration is different for different workbenches. This is explained in detail on the following slides. Enhanced CTS aims for a unified single transport tool which simplifies the life of an Administrator who is responsible for performing imports. He has to access only one tool to start imports for very different backends. Deployment tools are called automatically. It is very easy to monitor what has already been imported and if the import went well. The queues and the history in CTS provide a good overview on what needs to be imported.

© SAP AG

E2E200

3-5

Enha nc ed Cha nge and T ransport Syst e m Be ne fits
Benefits of the Enhanced Change and Transport System
̈

It is recommended to use the Enhanced Change and Transport System (CTS+), which allows the use of one central ABAP-based CTS for all types of changes (including Java) with the following advantages:
̈ ̈ ̈

Non-ABAP applications inherit all properties of the ABAP Change and Transport System in terms of documentation, tracking, and troubleshooting features. Transport of ABAP and non-ABAP objects can be managed centrally. Transports for mixed objects (ABAP, JAVA, …) are possible to synchronize changes to business processes which run in ABAP and JAVA.

ABAP Workbench SE80 PI / XI Integration Builder Developer Studio and NWDI Enterprise Portal Content Administrator Others (via open Interface for nonABAP objects)

TPZ SCA EPA

Enhanced Change and Transport System (CTS+)

Development Landscape

Transport

Quality Landscape

Transport

Production Landscape

© SAP 2009

̈ ̈ ̈ ̈ ̈ ̈ ̈

Connect Java systems to standard CTS Non-ABAP applications inherit all properties of the ABAP Change and Transport System in terms of documentation, tracking, and troubleshooting features Central administration of all transports (ABAP, Java, EP objects, PI objects …) in one User Interface (UI) Simplified transport management to avoid inconsistent system states Combined transport requests for mixed sets of objects (ABAP, Java, EP objects, PI objects, …) Synchronized updates of mixed processes (ABAP/non-ABAP applications) No need to upgrade of Java landscapes

© SAP AG

E2E200

3-6

Cre a t ing T ransport Re que st s for N on-ABAP Syste m s

© SAP 2009

̈

Transport requests are created in the communication system with the SID of the non-ABAP development system as part of the request name, such as EPDK000129.

© SAP AG

E2E200

3-7

T ra nsport La ndsca pe

TMS in Communication System

Virtual EPD

Virtual EPQ

Virtual EPP

Java Runtime Systems

© SAP 2009

̈

A typical landscape consists of three systems for an application. One system where the developments are done, one test system, and one system used productively by end users. The setup may differ. For supporting transports, one additional system is needed where CTS can be used. Recommendations on which system is to be used for CTS will follow later on. The content is created or developed in the development system or the corresponding development workbench, respectively. Within the workbench, the developer should find a mechanism to export what he did. During the export, he or she might have an option to choose a transport request and attach the files directly from within the workbench. The availability of this option depends on the application. If it is not available, a manual attachment process is needed to post the new content to CTS. After that, a transport request can be released and the import can be started. This is done within CTS. For the file types supported by now (see previous slide), CTS calls the deployment tool (for example, SDM) of the application to deploy the new content to the next system in the route. After a successful import into the QA system of the application, CTS forwards the transport request to the queue of the next system – in this case, the productive system. After a successful test, the administrator in CTS can start the import for the productive system. Some systems require post-installation steps. If you transport epa files containing roles, for example, you have to assign the new roles that were imported to the users or groups who will use the new content. KM documents require a manual import into the target system. In case of PI you have to activate manually on the target system.

̈

© SAP AG

E2E200

3-8

Support e d Solut ions and De ployment Opt ions

Transport of:
̈

Java-based and JEE-based objects
̈ ̈ ̈ ̈

Software Component Archives (SCAs) Software Deployment Archives (SDAs) Enterprise Application Archives (EARs) DTR Activities in NWDS (DIPs) Enterprise Portal Archives (EPAs) Portal Archives (PARs) KM documents and configurations Integration Repository design objects, Integration Directory configuration objects, ABAP mappings

̈

Portal-based objects
̈ ̈ ̈

Deployment Options:
> SDM/DC > XI > SLD > File

̈

PI/XI-based objects
̈

̈ ̈ ̈

SLD Objects MDM (specific set of data model objects) Any Files (.doc, .xls, .xml, …)

© SAP 2009

̈

This slide lists the object types which can currently be transported via CTS+. Not all of these objects types were supported with the first release of CTS+ in NW7.0 SPS 12. A look into the release notes both of CTS+ and the application is always advised to find out about supported objects with the release that you currently have in place. In addition, the level of integration is not the same for all supported files. Some require manual work when attaching them to a transport request, for others, you need to something in the target application after the import. DIP stands for Development Infrastructure Packages. It is a new file format used when Activities are transported. Details will be provided later. With MDM 7.1 the following set of data model objects can be transported from a source system to a target repository: Tables & Fields, Relationships, Languages, Roles, URLs (Web Links), XML Schemas, Remote Systems, Ports, Validations and Calculations, Assignments, Workflows (new with MDM 7.1), Import Maps (new with MDM 7.1), Syndication Maps (new with MDM 7.1), Matching Rules including Matching Strategies (new with MDM 7.1)

̈ ̈

© SAP AG

E2E200

3-9

Loose Coupling and Close Coupling

Loose Coupling
1) Export Java Archive 2) Upload to Transport Req.

Close Coupling
Attach Java Archive to a Transport Req.

© SAP 2009

̈

Loose Coupling • No direct integration of CTS+ mechanisms into application • Additional tool needed to create transport requests, attach files, and release transport orders • Manual attachment of files to transport requests via file upload

̈

Close Coupling • CTS+ mechanisms are available trough additional buttons, links, and input fields within the existing export UIs • Automatic attachment of files to transport requests directly within the application (EP, PI, etc.) • Get default transport requests • Automatic creation of transport requests possible • Automatic release of transport request possible • Connection from application server to CTS server

© SAP AG

E2E200

3-10

Enha nc e me nt s of the CT S

Enhanced Change and Transport System
Transport Organizer Web UI

Change and Transport Organizer (CTO)
Transaction: SE09/SE10/SE01

Transport Management System (TMS)
Transaction: STMS

Transport Tools (tp, R3trans, …) Transport Tools – Java
CTS Deploy Web Service

© SAP 2009

̈

The boxes in light colors show the parts of CTS that were already in place and which are used for ABAP transports. The “Transport Organizer Web UI” and the “CTS Deploy Web Service” have been added for CTS+. The Transport Organizer Web UI is a Web Dynpro ABAP Application which has to be used by applications to manage transport request. It replaces the transaction SE09. SE 09 can only be used for non-ABAP transports in case of the Dual Stack system SAP NetWeaver Process Integration. The CTS Deploy Web Services is needed to be able to deploy via SDM, for example. CTS+ requires an AS Java for this Web Service and an AS ABAP for the rest of CTS.

̈

̈ ̈

© SAP AG

E2E200

3-11

CT S+ Com pone nt s

Communication System ABAP stack
Transport Organizer Web UI

Java stack

Deploy WS

Portal Target System Java stack
Export Client

Portal Target System Java stack

Portal Target System Java stack

Import Service

Import Service

© SAP 2009

̈ ̈

Communication System: The communication system is the system, where the TMS transport systems (ABAP and non-ABAP) with their transport layer and transport route are configured. Deploy Web Service: The Deploy Web Service Client is needed on the ABAP side to enable the transport control program tp on SAP NetWeaver AS ABAP to communicate with the CTS Deploy Web service on SAP NetWeaver AS Java. It consists of two configuration parts: http connection (SM59) and logical port (LPCONFIG). Transport Organizer Web UI (ABAP): Web UI implemented as Web Dynpro ABAP application with basic SE09 functions to create and maintain transport requests for non-ABAP systems and JAVA stacks of dual-stack systems, attach non-ABAP objects and release transport requests. Export Client: Tight integration of CTS+ in the application of the source system where non-ABAP objects are created (known as close coupling – available since SP Stack 14 for EP, NWDI, SLD, PI, KM); to enable this tight integration, an RFC destination to the TMS communication system needs to be configured in the Visual Administrator of the source system (except for NWDI use case – here, the NWDI server needs to be configured for tight integration, not the non-ABAP source system). The Export Client communicates with the enhanced Transport Organizer to fetch a transport request and to attach the non-ABAP objects directly with the application (for example, EP Content Studio – Export Wizard). Import Service: Import mechanism running on the target system (SDM, XI Import Tool, SLD Import, KM Import, etc.). During the import of non-ABAP objects, the transport control program tp calls the Deploy Web Service on the Java stack and the Deploy Web Service triggers the CTS+ Import Service on the target system (for example, SDM) to deploy the transported objects.

̈

̈

̈

© SAP AG

E2E200

3-12

Enha nc ed Cha nge and T ransport Syst e m : U nit Ove rvie w Dia gra m
Enhanced Change and Transport System Lesson 1: CTS+ Overview Lesson 2: Working with CTS+ Lesson 3: Enterprise Portal and CTS + Lesson 4: SAP NetWeaver Development Infrastructure and CTS+ Lesson 5: Process Integration and CTS+ Appendix: CTS+ Transport Parameters

© SAP 2009

© SAP AG

E2E200

3-13

Role s in CT S+

Administrator on CTS
̈ ̈ ̈

Working on transport system Creating systems Configuring transport routes Transport Admin on CTS
̈ ̈ ̈

Working on transport system Importing transport requests Monitoring transports

Administrator in Application
̈ ̈ ̈

Configuring application for CTS+ Providing tools to developer Monitoring application Developer / Content Creator in Application
̈ ̈ ̈

Working within Application Starting Exports Releasing Transport Requests

© SAP 2009

̈ ̈

In principle, four roles can be identified in the process of using CTS: An administrator in the CTS system has to do some initial configurations to make CTS+ work. After that, he or she needs to create systems which represent the application’s landscape in CTS and needs to connect these systems to transport routes. This administrator can fulfill his or her tasks in ABAP on the CTS system. A transport admin is responsible for monitoring the transport requests (taking a look into the queues) and starting imports. He or she can also perfom all tasks within the CTS system. An administrator for the application is responsible for the initial configuration of the application. The administrator makes the CTS system known to the application and provides the necessary tools to the developers working in the application. He or she has to monitor the application in general. The developer or content creator creates new stuff for the application – for example, new iViews and pages within the portal. The developer has to take care that all the objects needed for a new feature are part of a transport request. He or she releases the transport request as soon as all objects are attached to a transport request. These four roles are an example and show the different tasks within the different systems. They do not represent static roles. One user can fulfill tasks of several roles or several users might contribute to one role. In the portal use case, it might be helpful, for example, to have one developer who develops portal applications and someone else includes these applications into iViews and roles.

̈ ̈

̈

̈

© SAP AG

E2E200

3-14

Who Doe s Wha t H ow Oft e n?

CTS

Configure CTS Configure Routes

Import Requests Monitor Transports

Configure Application Application

Monitor Transports Release Requests Export Content Create Content

once
© SAP 2009

often

̈ Each role described on the previous slide has to work either within the application or within the CTS

̈ ̈ ̈

̈

̈

̈

system. Nevertheless, there are tasks that are closely related to the other system and tasks which can be fulfilled with very little knowledge about the other side. This slide tries to show the tasks a certain role has to fulfill and how often this needs to be done. An administrator on CTS has to do the initial configuration tasks. This is a one-time task and he or she does not need any knowledge about the applications for this. After that, the administrator has to configure transport routes. To be able to do so, he or she needs to know about the applications and about the systems used. This task occurs from time to time whenever new systems are set up or a transport route has to be changed. An administrator of the application has to do some settings to make CTS known by the application. This needs to be done only once per application. The administrator of the application needs to know details about the CTS system. A developer working on an application has to fulfill several tasks. Some of them are closely related to CTS+ and require some knowledge about transport requests. Others can be done without knowing anything about CTS. Most applications do not use any change recording as of today. Therefore content is created by the developers without contacting CTS. At the same time, this is the main task of a developer. After having created some content, the developer exports this content. When doing so, he or she needs to know about the transport requests to be used. The developer can use one transport request to collect several content objects. During the export process, the developer can select a transport request. After having exported all necessary objects, the developer has to release the transport request. This is done by using the Transport Organizer Web UI – a tool closely related to CTS+. After having released a transport request, the developer can and should monitor the transport. He or she can use the Transport Organizer Web UI for this as well. The developer can view the import log from within the Transport Organizer Web UI. If there was an error during the import, the developer has to work with the administrator if the error was caused by deployment issues and not by the content of the transport. A transport administrator of the CTS system has to start the imports from the queue of the respective system. Before doing so, the administrator needs to know a bit about the content of a transport request. If a certain request requires a restart, for example, this import should only be done if a downtime of the application is possible. Like the developer, the transport admininstrator has to monitor the imports.
E2E200 3-15

© SAP AG

Cre a t ing N on-ABAP Syst e m s

Source System
̈ Define

Target System
̈ Define

Communication System Transport Organizer

Communication System Deployment Service

̈ Activate

̈ Configure

© SAP 2009

̈

To create a transport route in CTS, a representation of the source and the target system has to be created in CTS. In transaction STSM (in the system overview), you can create a non-ABAP system. Then, a wizard to create the system is started. In the first step, you can decide whether you want to create a source or a target system (a system can in exceptional cases also have both roles). Depending on the role of the system, you have to define different parameters. For a source system, the Transport Organizer has to be activated, for a target system, you have to define the deployment mechanism. If one target system has several usage types installed, you can also activate several deployment methods. The next step of the wizard will ask you for the passwords for the different deploy tools that you have selected. The options that you selected in the wizard may be changed later. They are stored as properties of the system. This means that you have to open the configuration of the system and then you can change the properties manually. The wizard does not support this any more. These tasks have to be fulfilled by a CTS system administrator.

̈

© SAP AG

E2E200

3-16

Cre a t ing T ransport Rout e s

̈ Consolidation

route between Dev and QA ̈ Delivery route between QA and Prod (and any other system behind QA)

© SAP 2009

̈

After having created the non-ABAP systems, the administrator of the CTS system can arrange the systems within transport routes. When doing so, he ro she has to create a transport layer. There are two types of transport routes available: Consolidation and delivery. Consolidation is only used between development and QA systems. All following routes are normally defined as delivery. All transport requests are created in the development system and then imported in QA and the productive system consecutively.

© SAP AG

E2E200

3-17

T he T ra nsport Orga nize r We b U I

̈ Is

an ABAP Web Dynpro Application to be used to handle transport requests for non-ABAP objects / systems

̈ Has ̈ Is

linked to applications (PI, NWDI, DS, Portal, SLD …) features for managing transport requests

̈ Provides ̈ ̈ ̈ ̈ ̈ ̈

Create Set as default View attached objects Attach objects Release …

© SAP 2009

̈ ̈

From the STMS you can jump into the Transport Organizer Web UI. The Transport Organizer Web UI is an ABAP Web Dynpro Application which has been introduced with SAP NetWeaver SPS 12. In SPS 13, a new version was provided. The name of the ABAP Web Dynpro application is CTS_BROWSER (from SPS 13 onwards). It is used to handle transport requests for non-ABAP systems. If you know how to transport in ABAP: SE09 cannot be used for non-ABAP systems, the CTS_BROWSER must be used instead. The Transport Organizer Web UI provides the features a developer of the applications requires in order to be able to handle transport requests. The developer may, for instance, create transport requests, attach objects, and release the transport requests. In addition, he or she can view the status of released requests. The Transport Organizer Web UI can be called from the applications which provide an integration of CTS+ into their export tools. The developer can then change a transport request or create a new one without having to go to the CTS system. The Transport Organizer Web UI runs on the CTS system, but if Single Sign-On between the application and the CTS system is enabled, the developer’s experience is seamless. The Transport Organizer Web UI can be called with several URL parameters. This is why it might show different options when it is called from different places.

̈

̈

© SAP AG

E2E200

3-18

T ra nsport Orga nize r – M odifiable Reque st

Default request used for close coupling

Options to work with requests

List of requests for the user

Details about the selected request

Add tasks for different developers to a transport request

© SAP 2009

̈ ̈

If you are working on a modifiable request, you have several options what you can do within the transport organizer Web UI. One transport request is marked with a red arrow. This request is currently used as your default request. This means that this request will be displayed within applications which provide close coupling. On top of the list of requests, you can find several buttons to work with the requests: You can create or delete a request, you may choose a different request as the default one, you can attach objects or release the request. If you mark one request out of the list, you can find detailed information below the requests’ list in a second list. Here, you can see the properties and change the description on the Properties tab. On the Object List tab you can find out what has already been attached to a transport request. If you release a request, it is not modifiable any more. If you refresh the list, you will not see it any more in this list. You may choose Released from the Status box. Then, different options are available for a transport request. The next slide explains the details. A new tab will be provided for modifiable transport requests. The tab is named Team. You can add several users to a transport request. When adding a user to the team, the option Preselected Request for added user is set by default. The request becomes the preselected request for the new team member. You can change this option. And the new team member can do so as well when he or she opens the Transport Organizer Web UI by just marking another transport request and by clicking on Preselect Request. All team members can add objects to the same transport request. This helps making sure that all objects belonging to one new feature are part of the same transport request. Every team member can release the transport request. It is not necessary that each team member releases the transport request. The whole transport request is released after one team member did so.
E2E200 3-19

̈

̈

̈

̈

© SAP AG

At t a c h an Objec t Loose Coupling

Button Attach can be used to add Java archives manually (loose coupling)
© SAP 2009

̈

The button to attach an object manually to a transport request is now part of the Object List tab of the respective transport request. If an application provides loose coupling as integration level with CTS+, objects are attached to a transport request via the Transport Organizer Web UI. The developer uses the Attach button. A pop-up window comes up where the developer can then browse for a file and attach it to the transport request.

© SAP AG

E2E200

3-20

T ra nsport Orga nize r Re lea se d Reque st
List of released requests

Request is released Info about request’s status per system SID is a link to logs

Target Systems

© SAP 2009

̈ ̈

This slide shows the Transport Organizer Web UI and its options if the list of released requests is displayed. A lock is now shown in front of the number of the transport request. The transport request cannot be changed any more; it is not possible any more to attach objects or to set a standard request. The transport request cannot be deleted. The properties and the attributes of a transport request can still be displayed, but not changed any more. A new tab Logs is added. The first column shows the systems where the transport request will be imported. The third column shows the status of the transport request for the respective system. You can move your mouse over the symbol and a text appears that explains the status. Clicking on the SID of the system will lead you to the log. For the first system (the development system), the export log will be displayed; for the following systems, the import log will be shown. Using these logs will help the developer to find out what went wrong in case of an error. The administrator of the CTS system does not have to send logs around. Each developer can take a look on his or her own.

̈ ̈

© SAP AG

E2E200

3-21

N a viga t e T hrough the T ransport Log Files (J a va )

© SAP 2009

̈ ̈ ̈

The transport log files can be reached from the Import History or from the Transport Organizer. In the detailed log file for the Deployment step, you can see whether the deployment was successful. You can also see additional information, such as host and port of the SDM.

© SAP AG

E2E200

3-22

Syste m -Spe c ific Pe rm issions

Only Developers or Development Managers should be allowed to do exports

Only Administrators of the QA system should be allowed to start imports

Only very few Administrators who know e.g. about possible downtimes should be allowed to do imports for the productive system

© SAP 2009

̈ ̈

You can restrict the permissions that a certain user has for a specific system. One scenario might be that a developer only exports the objects that he or she created. The import is to be done by someone else. The developer needs to have export permissions for the development system, but he should not be able to start the import. Another option would be to restrict the import permissions per system. Several administrators could have the permission to start the import for the QA system but only a few should be able to import new stuff into the productive system. This might be helpful if imports require post-import steps that might include a system restart. Restarts have to be coordinated and agreed on within the company especially if productive systems are concerned.

̈

© SAP AG

E2E200

3-23

Syste m -Spe c ific Pe rm issions Configura t ion
New options to set authorizations for a role in PFCG:
̈

S_SYS_RWBO

If you would like to restrict the permissions for generating requests
̈

S_CTS_SADM

If you would like to restrict the permissions for importing

© SAP 2009

̈ ̈ ̈ ̈

The permissions for systems have to be set via a role in the transaction PFCG. This slide shows the authorization objects used. S_SYS_RWBO is used to restrict the permissions for creating transport requests. You have to enter the SIDs of the systems for which the user should be able to create transport requests. S_CTS_SADM is used to restrict the permissions for importing. If you need different settings for different users, you have to create different roles.

© SAP AG

E2E200

3-24

N e w Fe a t ure : Obje c t List Pla nne d for SAP N e t We a ve r EhP2
̈ ̈

Implemented for Enterprise Portal and Development Infrastructure Overview of objects contained in an EPA or SCA or DIP

© SAP 2009

© SAP AG

E2E200

3-25

Syste m De m o

Transport Organizer Web UI

© SAP 2009

© SAP AG

E2E200

3-26

I m port via SAP T ra nsport M a nage me nt Syst e m

© SAP 2009

̈ ̈

The import process is identical for ABAP and non-ABAP transport requests. In both cases, transaction STMS is used. In the screenshot above transaction STMS was included in the Portal as a transactional iView.

© SAP AG

E2E200

3-27

I m port H ist ory
N on-ABAP Syst em s I nhe rit a ll Propertie s of ABAP

© SAP 2008

̈ ̈ ̈ ̈

By using the ABAP Change and Transport System, Java applications inherit all properties of the ABAP CTS. The import history can be reached from transaction STMS: Overview åImports å <SID> å Goto åImport History Here, you can find the list of all transports which were imported into a system and the import timestamp. From the import history, you can navigate through the object list and to the transport log files

© SAP AG

E2E200

3-28

Enha nc ed Cha nge and T ransport Syst e m : U nit Ove rvie w Dia gra m
Enhanced Change and Transport System Lesson 1: CTS+ Overview Lesson 2: Working with CTS+ Lesson 3: Enterprise Portal and CTS + Lesson 4: SAP NetWeaver Development Infrastructure and CTS+ Lesson 5: Process Integration and CTS+ Appendix: CTS+ Transport Parameters

© SAP 2008

© SAP AG

E2E200

3-29

Ent e rprise Port a l Obje c t s

Corporate Branding Navigation (Roles)
My Sales Figures

Detailed Navigation

iView

© SAP 2009

̈ ̈

When you look at a portal screen, there are several elements or components which might require a transport: Corporate Branding: the branding of the portal consists of a theme, a framework page, a desktop, and rule collections. These objects have to be transported to provide the same look&feel in the target system. Navigation (Roles): Content in the portal is assigned to a user by the help of roles. The roles consist of iViews, pages, and worksets. Portal Content: The content displayed within an iView requires a transport as well. Depending on the type of content, different transport mechanisms have to be used. In some cases, it might be sufficient to transport only the role with all its dependent objects; in other cases, it additional transports might be required on the backend system landscape in use.

̈ ̈

© SAP AG

E2E200

3-30

Ent e rprise Port a l Obje c t s

Role
A role defines a person’s responsibilities and authorizations in the organization. Workset 1

Role
Workset 2 page 1
iView 1 iView 2

Worksets Pages

A workset is a cluster of related tasks.

page 1
iView 1 iView 2 iView 3

page 2

A page defines the arrangement of the included elements.

iViews
iViews are the smallest units of information. iViews provide access to applications, reports, services, and information needed to complete a task. page 2.1
iView 1 iView 2

page 2.2
iView 1 iView 2

© SAP 2008

̈

̈

̈ ̈ ̈ ̈ ̈ ̈

The business package is structured as follows: • For each role, one or more business packages are provided with the required content. • Each business package contains the content needed to complete the various tasks a person with that role typically has to complete. These collections of task-oriented content are called “worksets.” • Each workset consists of those iViews required to complete the tasks in that workset. iViews are the smallest content units. They contain the actual resources needed to complete the tasks that make up each workset. The following PCD objects may need to be maintained by means of SAP or other vendors‘ shipments, for example, a Business Package shipped with iViewStudio: • Folders (and their content) • iViews • Pages • Worksets • Roles The Enterprise Portal Import / Export iView is used to transport the PCD objects. Local changes to the current object version will be overwritten by the import of the associated EPA file. The file type for exports / imports of PCD objects is EPA (Enterprise Portal Archive). Any PCD object (including “folders“ and their content) can be exported from one Enterprise Portal System and imported into another one. The EPA file may also contain *.PAR files if the exported PCD objects were created based on their components. If PCD objects are delivered as part of Business Packages, updates can be imported from iViewStudio.
E2E200 3-31

© SAP AG

Wha t I s a n iV ie w ?

It is the basic unit of portal content – a small application that displays information.
̈ ̈ ̈ ̈

iView information can be in any format (texts, figures, graphs, reports, tables, charts, etc.) iViews can be interactive, allowing you to perform business functions iViews can display information from any data source iViews are based on portal components (for example, developed in the SAP NetWeaver Developer Studio)

© SAP 2009

© SAP AG

E2E200

3-32

Port a l Cont ent St udio

̈ Portal ̈ Used

tool to create iViews, pages, roles…

by Portal Content developers

© SAP 2009

̈

The Portal Content Studio is used to create iViews, pages, and roles, for example. A content developer can create the navigation structure here. Very different applications can be integrated in the portal by the help of iView templates, which are provided by SAP or were developed by a customer or partner. All content objects (like roles, worksets, iViews, and pages) are available in the Portal Catalog and are maintained in the Portal Content Studio. The Portal Catalog provides a central access point to all portal content objects stored in the PCD. It permits you to store, manage, and organize content in a structured hierarchy.

̈ ̈

© SAP AG

E2E200

3-33

Pa ck age Export Edit or

The Package Export Editor
̈ ̈

Is used to collect Portal Content in an epa file Is an export tool – it does not provide any transport logistics or transport routes

© SAP 2009

̈

The Package Export Editor is used to export portal content (including roles, iViews, pages, rule collections, etc). This tool is provided to portal administrators via the system administration role. After having chosen the objects that require an export, a transport package named <name><exporttime>.epa is created. If CTS+ is not configured, the epa file can now be downloaded to your client and is stored on the server. This epa file can be imported on the target system. There is a special tool for exporting portal themes, the Theme Transport in the system administration role. Themes cannot be part of an epa file. The theme export requires a download. The following slide explains what is different when using CTS+. More information about transporting portal content can be found at http://help.sap.com/saphelp_nw70/helpdata/en/c5/56599164d0c04cb566b a0e2d7ed55c/frameset.htm

̈ ̈ ̈

© SAP AG

E2E200

3-34

Close Coupling for T ra nsport ing Port a l Content

Link to Transport Organizer Web UI Transport Method Information about the Transport Request

Information for the CTS Administrator

© SAP 2009

̈ As of SAP NetWeaver SPS 13, the Package Export Editor supports CTS+. New fields have been introduced in

the Package Export Editor for NW 7.0 SPS 13 / 14. The screenshot is taken from SPS 14.
̈ If a CTS+ system is configured in the Visual Administrator, the user can choose whether he wants to use the

̈

̈ ̈

̈ ̈ ̈ ̈ ̈

‘classic’ way of exporting via the file system or the CTS+. Therefore, the drop-down listTransport Method has been introduced. The fields Transport Request, Owner, and Description are read from the CTS+ system. This is the request currently flagged with the red arrow in the Transport Organizer Web UI that we have seen before. In the CTS+ system, you can define a transport strategy for every non-ABAP system. This strategy determines the behavior of the CTS system whenever an application asks for a transport request: • Smart If there is no default request available for the user, the system creates a new one and flags it as the standard request. • Tagged This is configured as the default value in the system. You must have created a transport request already in Transport Organizer Web UI and flagged it as the standard request. If there is none, there is no transport request taken from the CTS+ system. The field File name can only be edited if File system is chosen as a transport method. If you used the file name for information purposes for the administrator, you would now be able to use the field Note instead. The field Note can be used to add some comments concerning the specific file. The input field is only available if CTS is chosen as transport method. The text that you enter here will be added to the transport request documentation in the CTS system. Portal themes can not be transported as part of an epa file. Currently, there is no option to transport portal themes via CTS+ except for file system transport. This option requires a manual import in the target system. Every other object of the PCC (Portal Content Catalogue) can be added to an epa file when collecting the objects. When importing an epa file via CTS+, the Overwrite mode is used. Be careful when transporting rule collections. They might contain users, groups, or roles that do not exist in the target system. Rules in the target system might be lost (remember the overwrite mode!) A more detailed description can be found on the SAP Help Portal at http://help.sap.com/saphelp_nw70/helpdata/en/62/117d0cb40145d6bfc655dac7de b9c1/frameset.htm. E2E200 3-35

© SAP AG

Syste m De m o

Portal Content Studio

© SAP 2009

© SAP AG

E2E200

3-36

Port a l Applic a t ion Obje c t s

Developer Studio Deployment (NWDI control recommended)

Portal Applications:
Java programs, such as Calculator ̈ WebDynpro Java
̈

SDM Service

SDM Service

SDM Service

EPD
Portal Content Studio

EPQ
Portal Content Studio Import

EPP
Portal Content Studio

Export File Share
© SAP 2009

Portal Content:
̈

iViews, Pages, Roles

© SAP AG

E2E200

3-37

CT S+ Se t up w it h Port a l Cont e nt St udio and N WDI
NWDI
(Java Development Environment) Developer Studio

Solution Manager Transport Controller ABAP stack
Transport Organizer Web UI

Repository (DTR)
Workspace

Build Server (CBS)
Buildspace

Java stack

Deploy WS
Change Management Server (CMS)

Portal Source System Java stack
Export Client

Portal Target System Java stack

Portal Target System Java stack

Import Service Import Service

Import Service

© SAP 2009

̈ ̈

Scenario with Portal Systems (Single Stack Java and NWDI) A typical scenario where use cases are combined is the transport of portal content (Portal iView, for example) together with their Java applications (Java Web Dynpro application, for example). Depending on the existing Portal and Java landscape, the transport scenario looks different. As the recommended development infrastructure for Java-based developments is the NWDI and NWDI is tightly integrated with CTS+ the combined use cases NWDI and SAP Portal are very common.

© SAP AG

E2E200

3-38

Be st Pra c t ic e Re com me nda t ion: I nc lude iV ie w s for T ra nsport M a na ge m ent in t he Port a l

© SAP 2009

̈

An optional configuration is to create an ABAP Web Dynpro iView which shows the Transport Organizer Web UI in the portal. This iView might be used by developers to take a look at the current status of their transports or to create new transport requests, for example.

© SAP AG

E2E200

3-39

Fea t ure s and Lim ita t ions of CT S+ in a Port a l Environm ent
What it does
̈ Transport Portal Content ̈ Epa files can be added to a transport request and

What it does not
̈ Provide Collision Management: ̈ Epa files are imported without any respect to

will be deployed via SDM.
̈ In addition, par, ear, sca, and sda files can be

creation date of the epa file.
̈ iViews, etc. are imported without any respect to

transported and deployed.
̈ Other file types can be transported. They will be

change date of already existing content.
̈ Automate Change Recording ̈ You still have to create epa files ̈ You have to create transport request and attach the

deployed to a specified folder on the file system of the target system. ̈ Provide Landscape Configuration
̈ The landscape is configured within the ABAP

stack as known for ABAP systems. It is now possible to configure non-ABAP systems and to create transport routes. ̈ Support ‘old’ releases:
̈ It is possible to use systems from SAP

epa files to this transport request. This is done via a Web Dynpro Application that can be integrated into the portal. (Close coupling available for SPS 13 to attach epa directly to Transport Requests within the Transport Package Editor.) ̈ Organize your transports
̈ No link between a transport request and a change

NetWeaver 04 SPS 09 (SDM available to deploy epas)
̈ No functionality within the portal required. (close

request

ChaRM

̈ No version management for single items ̈ No control mechanisms that all the content that is

coupling starting with SPS 13).
̈ Logging and tracing ̈ All the logging and tracing mechanisms known

needed for a certain change is included in a transport request

from ABAP can be used.

© SAP 2009

© SAP AG

E2E200

3-40

Ex e rc ise

Portal Content Studio

© SAP 2009

© SAP AG

E2E200

3-41

T ra ining La ndsca pe a nd Archit e c t ure

TT5 Host: <host>.wdf.sap.corp (monitored) SAP EP http://<host>:55000/irj Front End PC SAP GUI Browser Web AS Java SAP ECC Instance: 50; Client: 800 Web AS ABAP

RDBMS TT4 Host: <host>.wdf.sap.corp (monitoring) SAP SolManDiag http://<host>:50000/smd Web AS Java SAP SolMan Instance: 00; Client: 200 Web AS ABAP

RDBMS
© SAP 2009

̈

This figure shows the system landscape which is available for the training

© SAP AG

E2E200

3-42

Enha nc ed Cha nge and T ransport Syst e m : U nit Ove rvie w Dia gra m
Enhanced Change and Transport System Lesson 1: CTS+ Overview Lesson 2: Working with CTS+ Lesson 3: Enterprise Portal and CTS + Lesson 4: SAP NetWeaver Development Infrastructure and CTS+ Lesson 5: Process Integration and CTS+ Appendix: CTS+ Transport Parameters

© SAP 2009

© SAP AG

E2E200

3-43

J a va De ve lopme nt Wit hout N WDI

DEV

CONS

TEST

PROD

Deployment

Developer PC with SAP NetWeaver Developer Studio Local J2EE Engine
© SAP 2009

File Share

Sources Libraries

̈

SAP NetWeaver Developer Studio: SAP’s own development environment for developing multi-layer Java-based business applications. The new development environment is based on the open source product Eclipse. It fully supports SAP’s component model. Optionally, the developer has a local engine in which he can make a first test. Then he deploys it into the central systems DEV, CONS, TEST, PROD. The sources and libraries are stored on a file system. This setup bears some risks and limitations: • No central place for sources. Different developers might have local copies which are outdated. • No version management for sources. Old versions are not kept. • No conflict detection and resolution for sources. If two developers work on the same object, they will overwrite their changes. • No central build. Different developers could have local copies of the libraries which are outdated. • No automatic identification of dependent libraries. • No transport control. The developer is not forced to deploy to DEV, CONS, TEST, PROD in the correct order.

̈ ̈ ̈

© SAP AG

E2E200

3-44

J a va De ve lopme nt w it h N WDI

DEV

CONS

TEST

PROD

Developer PC with SAP NetWeaver Developer Studio Local J2EE Engine
© SAP 2009

CMS
Check in and out

DTR

CBS

Im po rt

Bu De ild pl an oy d

Import & Approval

& oy ly pl mb De se As

SLD

̈ ̈

The SAP NetWeaver Development Infrastructure is located on a separate server. It consists of the following components: DTR: Central store for all types of source files. The store is presented logically as a hierarchical files and folders structure. The contents are physically stored in a database and can be accessed using the open protocols WebDAV and DeltaV. CBS: Build Environment. The CBS stores all imported libraries (archives) to start development of new Software Components (SCs). It also builds and stores all newly created development components. CMS: Administration and quality management environment for (logical) development systems. It consists of the Landscape Configurator (responsible for the definition of development environments for specific SC releases (tracks with development configurations for development and consolidation)) and of the Transport Studio (which enables transport mechanisms for development components from Development å Consolidation å Assembly å Approval.) SLD: SAP J2EE application that contains all relevant information about software products and components (both ABAP and Java) that can be installed in a system landscape. It also contains a description of the current system landscape. The SLD also stores the development configurations. Note: SLD is not part of NWDI, but already part the of standard SAP Web AS Java installation. SLD is required by the NWDI. The arrows here indicate from where the import into the different systems are triggered. Note that the developer triggers the transfer of his or her local development into the central DEV system by using the SAP NetWeaver Developer Studio. SAP NetWeaver Developer Studio uses the CBS and CMS to start the deployment into the DEV system. The import into subsequent systems is triggered and controlled directly from CMS.
E2E200 3-45

̈

̈

̈

̈ ̈

© SAP AG

De sign T im e Re posit ory (DT R)

Check In/Check Out Model
̈ ̈ ̈

Files are checked out from DTR and modified “offline” Files are checked in again when change is complete When a file is checked out, it is locked for other users Old object versions are stored in the database of the DTR

Version History
̈

Conflict Resolution
̈ ̈ ̈

Conflict detection Support for conflict resolution The following SAP applications are shipped with sources and can be modified by the customer. For modification adjustments, the DTR is necessary:
̈ ̈ ̈

ERP 6.0 – SAP XSS (Self Services) ERP 6.0 – SAP Biller Direct CRM 5.0 – SAP E-Commerce

© SAP 2009

̈

The DTR provides central storage, versioning and management of java sources and other resources with an automated conflict detection and resolution. The Developer Studio enables comprehensive DTR support for all available project types (Web Dynpro, EJB,...). ̈ Distributed, concurrent development – the DTR addresses the needs of large scale development: • Some projects are so big that the development team is spread over different locations. The groups work in parallel. The same applies if you want to allow your customers to do modifications to your applications, which means modifications to the Java source code. • The versioning mechanism of the DTR that spans repositories means that you can safely propagate changes from one DTR repository to another. • The conflict detection allows you to detect whether two versions of one development object were created in parallel; it also prevents inconsistent states of versions • Conflicts that are reported by the DTR can of course be solved there: A conflict is always an uncertainty which of two versions of a certain file is to be active in the DTR; the content of the conflicting versions can be displayed and the user can decide how to solve the conflict ̈ Files and Folders: • Though the DTR stores all objects in a database, the content of this database is presented to the DTR client in a files and folders fashion. This meets the concepts of SAP’s Eclipse-based IDE – the SAP NetWeaver Developer Studio. • The storage of files is independent of the programming language so in principle all types of files can be stored and versioned, even if they are not part of the Java programming model. ̈ Check in/check out model: • To change a file in the DTR you must check it out: To change it, you will use a copy in your local file system. • Changed objects will be checked back in to the DTR server – all changes will be part of an activity then.

© SAP AG

E2E200

3-46

Component Build Se rvic e (CBS)

Central Build
̈ ̈ ̈

All libraries and executables are centrally stored in the CBS. Files are checked in again when the change is complete. When a file is checked out, it is locked for other users.

Identification of Dependencies
̈ ̈

“Used” development components are included into the build process. “Using” development components are rebuilt again, because they were changed indirectly. Dependencies are handled at Development Component level. This is the lowest granularity. Assignment of version numbers to archives. These version numbers are checked by the Software Deployment Manager. No transport sequence violations are possible.

Build Time Reduction
̈

Versioning
̈

© SAP 2009

© SAP AG

E2E200

3-47

Change M a nage me nt Se rvic e (CM S)

Definition of Fixed Transport Tracks
̈

The systems DEV, CONS, TEST, PROD must be delivered in this order. No exeptions are possible.

Approval Procedure
̈

An approval is needed that the test was successfully executed.

Support of Different Landscape Topologies
3-system landscape (without CONS) 4-system landscape (with CONS) ̈ Phased system landscape (for project and maintenance) with automatic retrofit
̈ ̈

© SAP 2009

© SAP AG

E2E200

3-48

Syste m La ndsca pe Dire c t ory (SLD)

For Java development, SLD provides the following services
̈ ̈ ̈

Definition of software components to be developed and their interdependencies Naming Service: Reserve name spaces for unique names of development components Storage of development configurations required for development

© SAP 2009

© SAP AG

E2E200

3-49

CM S T ra c k Configura t ion w it hout CT S+

CMS Track

Development Development Configuration Workspaces Workspaces

Consolidation Development Configuration Workspaces Workspaces

Test

Production

Buildspace

Buildspace

Central Development System

Consolidation System

Test System

Production System

Runtime Systems

DEV

CONS

TEST

PROD

© SAP 2009

̈

Here you can see the classic design of a track in NWDI with 4 runtime systems connected. This setup has some limitations: • No reuse of ABAP transport knowledge – need to learn new concept • Build transport routes with a limited number of systems in one track • System roles (DEV, CONS, TEST, PROD) are predefined • Development configurations and repair capabilities are predefined (DEV, CONS) • No multiple direct successor systems for each system possible in one track • Transport granularity after assembly is the complete Software Component (SCA) • No synchronized transports between different object types and other content

© SAP AG

E2E200

3-50

CM S T ra c k Configura t ion w it h CT S+

CMS Track

CTS+ Communication System

Development Development Configuration Workspaces Workspaces

Consolidation Development Configuration Workspaces Workspaces

DEV

TEST

PROD

Buildspace

Buildspace

Central Development System

SCA Consolidation System

Runtime Systems

DEV

CONS

TEST

PROD

© SAP 2009

̈ ̈ ̈

If you are using CTS+ with NWDI, then the transport archive is created with the assembly step. This archive is then attached to a transport request which was created in the ABAP stack. If the NWDI is configured for the close coupling scenario, this step is done automatically. The import into the QA and PROD system is then done synchronously in the ABAP and JAVA stack with the same transport request.

© SAP AG

E2E200

3-51

N WDI – CT S+ Applic a t ion I nt egra t ion (Close Coupling)

Link to Transport Organizer Web UI

Information about the Transport Request

Information for the CTS Administrator

© SAP 2009

̈

These screenshots show how the integration of CTS+ in CMS looks like. In the top right corner, the user can find a link to the Transport Organizer Web UI. He or she can use it, for example, to check the available transport requests, create a new one or check the import status of already released transport requests. When the user clicks on Assemble Component(s)… a new window opens up to set the Assembly Options. On this screen, the user can decide about the transport request to be used. A link to the Transport Organizer Web UI is provided as well. In addition, the user can add some documentation to the transport request via the input field Note. The same transport strategies as for the portal can be used (Smart or Tagged).

© SAP AG

E2E200

3-52

Advant age s of U sing CT S+

Enhanced CTS allows the user to
̈ ̈ ̈ ̈ ̈

Use the ABAP change and transport system (CTS) for all transports Build transport routes with an arbitrary number of systems Define arbitrary system roles Define multiple direct successor systems for each system Support synchronized transports between ABAP and Java or other content

DEV
automatic transport of objects lists

System QA

CONS

...

PRE System PROD
automatic transport of objects lists

PROD

PROD2

SANDBOX

© SAP 2009

̈

Here, the advantages are listed that the new DI CM Services solution provides with its integration in CTS+.

© SAP AG

E2E200

3-53

Addit iona l Opt ion w it h EhP1 : CM S Single T ra c k Configura t ion
CMS Track CTS+ Communication System

Development Development Configuration Workspaces Workspaces

DEV

TEST

PROD

Buildspace

Central Development System

SCA

Runtime Systems

DEV

TEST

PROD

© SAP 2009

̈ ̈ ̈ ̈

You now have the option to create single system tracks in NWDI. In case of single system tracks, the Consolidation tab is no longer available in CMS. You can change a normal track into a single system track, but there is no way back. This single system track offers the advantage that in case of dual stack systems the ABAP and the Java part of a transport can be imported via the same transport request. In case of separate systems for ABAP and Java, the import can be started from the same CTS system. The transport requests are then part of different queues, but only one tool needs to be used to start the import. The disadvantages that you have to configure two systems and that the transport of the Java part can only be on the granularity of SCA remain the same as before. You cannot perform a consolidation with a single system track since all activated changes are assembled. Everything that is activated in a single system track gets directly assembled, so remember to release your changes immediately after the activation.

̈ ̈ ̈

© SAP AG

E2E200

3-54

Enha nc ed Cha nge and T ransport Syst e m : U nit Ove rvie w Dia gra m
Enhanced Change and Transport System Lesson 1: CTS+ Overview Lesson 2: Working with CTS+ Lesson 3: Enterprise Portal and CTS + Lesson 4: SAP NetWeaver Development Infrastructure and CTS+ Lesson 5: Process Integration and CTS+ Appendix: CTS+ Transport Parameters

© SAP 2009

© SAP AG

E2E200

3-55

PI Com ponent s

Shared Collaboration Knowledge
Integration Builder

Execution of Collaborative Business Processes
Central Monitoring
SAP Systems

Integration Repository (IR)

Integration Directory (ID)

Integration Server (IS)

3rd Party Systems
3rd Party Middleware Component Marketplace/ Business Partner

System Landscape Directory (SLD)

© SAP 2009

̈ ̈

SAP PI consists of the following components: Design Time / Configuration Time • The Integration Builder: A client-server framework for accessing and editing two stores of Shared Collaboration Knowledge: – The Integration Repository: For the design and development of Interface, Process, and Mapping objects that are used to implement Integration Scenarios. – The Integration Directory: For configuring scenarios from the Integration Repository in the concrete customer landscape. – By separating design time activities from configuration time activities, SAP can ship content for the Integration Repository, which each customer can implement for their specific landscape in the Integration Directory. As far as possible, the goal is to reduce the problem of developing interfaces to the simpler task of configuring interfaces.

̈

Runtime • The Integration Server: The central processing engine of the PI. All messages, whether SAP or non-SAP, A2A or B2B, regardless of backend technology or vendor, are processed in a consistent way. • Central Monitoring: To give a comprehensive and focused view of all components and processes at runtime.

̈

SLD • The System Landscape Directory: A central repository of information about your system landscape and software components. This data is required during design time and runtime.

© SAP AG

E2E200

3-56

I nt egra t ion Re posit ory Ex port ing a Soft w a re Component V e rsion
2

Software Component Version

3 1

© SAP 2009

̈ ̈ ̈ ̈ ̈

Since the functionality is similar in both the Integration Repository (IR) and the Integration Directory, the screenshots in this unit show the IR use case only. Log on to the IR of your PI development system. Select the software component version that you would like to export and choose Export in the context menu. Select Transport Using CTS as the transport mode, enter a description and choose Continue. On the subsequent wizard screen you can select into the transport all or a restricted number of objects. Choose Continue. The system now displays a proposed transport request (either a newly created one or an existing standard request for your user).

© SAP AG

E2E200

3-57

I nt egra t ion Re posit ory Ex port ing a Cha nge List of a U se r
2

3 Changelist

1 4

© SAP 2009

̈ ̈

Log on to the Integration Repository of your PI development system. Select a transportable change list and in the context menu choose Release for CTS Transport. The transport wizard is started. You have the possibility to go with the preselected standard request or to open the Transport Organizer Web UI to create and define a new standard request to be used.

© SAP AG

E2E200

3-58

Soft w a re Logist ic s Fea t ure s of t he I nt egra t ion Builde r
Recording of Changes
A change list per user is recorded automatically. ̈ All objects in the changelists are locked.
̈

Granularity of Transports
Transports can be executed for change lists (all changed objects by a certain user) ̈ In addition, single objects, namespaces, or complete software components can be transported
̈

Versioning
̈ ̈

Changed objects are recorded in a versions database Each PI repository object has a version history. The latest version is automatically active. Therefore, no transport sequence violations are possible.

Supported Transport Mechanisms
Export/Import Procedure on file system (*.tpz files) ̈ Interface to Change Management Service of NWDI ̈ Interface to CTS+
̈

© SAP 2009

̈ ̈ ̈

The Integration Builder Server Framework provides software logistics features like Locking, Versioning, and Change List Management. It provides an Import/Export interface as well as an interface to CMS of the NWDI. Changes are saved in user-specific change lists. To make these changes visible for all users of a repository, the developer must activate the entire change list.

© SAP AG

E2E200

3-59

Spec ia l Aspec t s of t he Int e gra t ion Dire ct ory

Automatic source system mapping after the import
̈

Usage of transport targets in SLD

Non-transportable fields must be maintained manually in the target integration Directory
̈

For example, users and passwords

Integration Directory transports must be activated manually
̈

No automatic activation of the latest version

© SAP 2009

© SAP AG

E2E200

3-60

PI De pe nds on t he SLD

PI Uses the SLD in Several Ways
̈ ̈ ̈

Server for business system names (landscape description) Transport targets for directory content transports Management of software component versions and their dependencies (component information) During SLD downtime, operation of your PI system is jeopardized.

Ü

Ü Often

the SLD content is the prerequisite for the PI transportation. An error message will occur, if the imported Integration Repository or Integration Directory objects cannot find related entities from the SLD.

© SAP 2009

̈

There are two main areas of content in the SLD: the software catalog and the system catalog. „ The software catalog describes the installed products and their constituent components. The software catalog is delivered with content about all SAP products. Customers and partners can extend this catalog with information about software from other vendors. „ The system catalog describes the systems in the data center from two perspectives: a logical view (business systems) and a physical view (technical systems). In other words, the system catalog describes the concrete implementation of the customer landscape.

̈

Information from the software catalog is used in the IR to organize development efforts. Information from the system catalog is used in the ID to drive the specific configuration of Integration Scenarios.

© SAP AG

E2E200

3-61

Be st Pra c t ic e Sce na rio for Double St a c k Syste m s, suc h a s PI
XI/PI
Source System ABAP stack
Transport Organizer Web UI

XI/PI
Target System ABAP stack

XI/PI
Target System ABAP stack

Deploy WS Client
Transport Route Transport Route

Deploy WS Client

Java stack

Java stack
Deploy WS

Java stack
Deploy WS Import Service

Export Client Import Service

In double-stack systems the transport routes for the ABAP stack can be used by the Java stack as well. This allows you to have one transport requests that contains both ABAP and non-ABAP objects.

© SAP 2009

̈

The following section describes the configuration and setup of CTS+ for a dual-stack system landscape, where the development and target systems are dual-stack systems (for example, PI use case). The typical configuration for using CTS+ functionality for a dual-stack landscape is to set up/use the existing ABAP transport domain controller configuration. For using CTS+ functionality, the CTS+ components need to be configured in addition to the existing ABAP transport configuration. The main difference to a non-ABAP system landscape is that each target system triggers the imports using the tp program running on that target system (same behavior as in ABAP). Having a dualstack system landscape with a tp running on each system leads to the fact that the corresponding Deploy Web Service (DEPLOYPROXY) should run and should be configured for the Java stack part of that dual-stack system. Therefore the corresponding Deploy Web Service Client consisting of the HTTP Connection and the Logical Port needs to be configured on the ABAP stacks of all target systems.

̈

© SAP AG

E2E200

3-62

Enha nc ed Cha nge and T ransport Syst e m : U nit Ove rvie w Dia gra m
Enhanced Change and Transport System Lesson 1: CTS+ Overview Lesson 2: Working with CTS+ Lesson 3: Enterprise Portal and CTS + Lesson 4: NetWeaver Development Infrastructure and CTS+ Lesson 5: Process Integration and CTS+ Appendix: CTS+ Transport Parameters

© SAP 2009

© SAP AG

E2E200

3-63

T ra nsport Pa ra m e t e rs for CT S+

Source System Parameters:
̈ NON_ABAP_SYSTEM (SPS12)
̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈

Target System Parameters:
̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈

NON_ABAP_SYSTEM (SPS12) COMMUNICATION_SYSTEM (SPS12) CTS_SYSTEM_TYPE (SPS14) DEPLOY_DATA_SHARE (SPS12) DEPLOY_WEB_SERVICE (SPS12) DEPLOY_URL (SDM) (SPS12) DEPLOY_SLD_URL (SPS14) DEPLOY_XI_URL (SPS12) DEPLOY_OUTBOX (SPS12) CTS_SYSTEM_TYPE (EhP1)

COMMUNICATION_SYSTEM (SPS12) NON_ABAP_WBO_CLIENT (SPS12) NON_ABAP_WBO_INBOX (SPS12) WBO_GET_REQ_STRATEGY (SPS13) WBO_REL_REQ_STRATEGY (SPS13) WBO_FILE_TRANSFER (SPS14) WBO_USR_MAP_STRATEGY (SPS14) CTS_SYSTEM_MAPPING (SPS14) CTS_SYSTEM_TYPE (EhP1)

© SAP 2009

© SAP AG

E2E200

3-64

T ra nsport Pa ra m e t e rs for CT S+

NON_ABAP_SYSTEM:
̈

By setting non_abap_system=true for a certain system, it will be marked as a system where no ABAP content will be exported from or imported into, but only files. This corresponds to the new R3trans feature to include FILEs into transport requests.

COMMUNICATION_SYSTEM
̈

If the parameter non_abap_system=true is set for a certain system, you have to specify its communication system by setting the parameter COMMUNICATION_SYSTEM to the communication system's SID. The communication system must not be defined as a non-ABAP system. The communication system serves as a system where all transport meta data is stored and which may also serve as the transport domain server.

NON_ABAP_WBO_CLIENT
̈ ̈

Client of the CTS system Specify the client in which you want to use Transport Organizer for this non-ABAP system

NON_ABAP_WBO_INBOX
̈ ̈

Path to the directory where Transport Organizer searches for files. This parameter enables you to choose between a close or loose coupling of your SAP applications and CTS: Close coupling You need this parameter setting when you attach files to a transport request from a server share/mount. The default setting uses file streaming (see parameter WBO_FILE_TRANSFER). Loose coupling You need this parameter setting when you attach files to a transport request from a server and not from a desktop (client).

̈ ̈

© SAP 2009

© SAP AG

E2E200

3-65

T ra nsport Pa ra m e t e rs for CT S+

WBO_GET_REQ_STRATEGY
̈

Tagged
̈

Transport Organizer Web UI (or ChaRM) has to be used to create a request for a user and to mark them with a tag. If there is no tagged request found for a given user, the application reacts with an error. If there is no tagged request available for a user, the transport backend creates a valid request. The export wizards in the applications are never interrupted, because there is always a valid request.

̈

Smart
̈

WBO_REL_REQ_STRATEGY
̈

Manual
̈

Transport requests can only be released using the Transport Organizer Web UI or ChaRM. Transport requests are automatically released from the Transport API after the objects are attached to the request.

̈

Automatic
̈

WBO_FILE_TRANSFER
̈ ̈ ̈

File transfer method between applications (clients) and the CTS system (streaming or file share/mount) You need this parameter only if you choose a close coupling. Parameters: Stream (default) or Share

© SAP 2009

© SAP AG

E2E200

3-66

T ra nsport Pa ra m e t e rs for CT S+

WBO_USR_MAP_STRATEGY
̈ ̈

If you need to use user mapping because the user IDs in your Portal as and in your CTS system are not identical, have a look at note 1003764 and install the attached correction. Parameter: System Enter the system ID of your non-ABAP system if it is not the same as the name of the corresponding nonABAP system in TMS. If possible, always create your non-ABAP systems in TMS with the same system ID that you gave the nonABAP system during installation. Classification of the systems in transaction SMSY for SAP Solution Manager scenarios When you create a non-ABAP system, this parameter is generated with the value JAVA automatically. For non-SAP systems, change this parameter to OTHERS. The directory where the CTS Deploy Web service accesses the data saved by the transport program tp If the CTS Deploy Web service is not on the CTS server and is on another server instead, you have to change this parameter. The server on which the CTS Deploy Web service runs must be able to access the transport directory. Specify the directory used by the CTS Deploy Web service to access the ABAP transport directory.

CTS_SYSTEM_MAPPING
̈ ̈

CTS_SYSTEM_TYPE
̈ ̈

DEPLOY_DATA_SHARE
̈ ̈

DEPLOY_WEB_SERVICE
̈

Name of the Web service = CTSDEPLOY

© SAP 2009

© SAP AG

E2E200

3-67

Enha nc ed Cha nge and T ransport Syst e m : U nit Sum m a ry

You should now be able to:
̈ ̈

Explain how the Enhanced Change and Transport System (CTS+) works Understand the basic concepts of Enterprise Portal, SAP NetWeaver Development Infrastructure and Process Integration and how they are supported by CTS+ Know best practices for the setup and usage of CTS+ in different scenarios

̈

© SAP 2009

© SAP AG

E2E200

3-68

Exercices
Unit: Lesson: Enhanced Change and Transport System Portal Content Studio

At the conclusion of this exercise, you will be able to: • Create a Role and Assign a workset • Assign the Role to your Portal user

TT4 is the Communication System for the CTS+ The transport track JAD å JAQ å JAP consists of virtual Portal systems They all reference to the physical Portal system TT5.

3-1

Create a new role in the Enterprise Portal TT5. 3-1-1 3-1-2 3-1-3 Log on to the Enterprise Portal on system TT5 with your user E2ECC-## (Change “##” to your group number). In the Portal Content Catalog, navigate to the folder com.sap.OTO_Training Create a new role. Assign the following general properties to your role: Role Name: Role_User_## (Change “##” to your group number) Role ID: Role_User_## Role ID Prefix: com.sap Master Language: English Description: Role of group ## 3-1-4 Mark the role as an entry point.

3-2

Assign the role to your user. 3-2-1 3-2-2 3-2-3 In the Portal, navigate to User Administration search for your user. Identity Management and

Assign the role that you already created to your user. Refresh your browser and check if there is a new entry in the top level navigation.

© SAP AG

E2E200

3-69

3-3

Assign the workset Working Time to your role. 3-3-1 3-3-2 3-3-3 In the Portal Content Catalog, navigate to the folder com.sap.OTO_Training Open the role you created earlier. Assign the workset Working Time to the opened role as a Delta Link. The workset can be found in Portal Content å Content provided by SAP å End User Content å Employee Self Service å Worksets. Refresh your browser and check if there is a new workset under your role.

3-3-4

© SAP AG

E2E200

3-70

Exercices
Unit: Lesson: Enhanced Change and Transport System Transport Package Editor

At the conclusion of this exercise, you will be able to: • Create a transport package • Attach a transport package to a transport request using the close coupling scenario

3-4

Put your changes into a transport package and export the transport package to a transport request. 3-4-1 3-4-2 3-4-3 Log on to the Enterprise Portal on system TT5 with your user E2ECC-## (Change “##” to your group number). Go to the Transport Package Editor and navigate to the role that you have just created. Create a new Transport Package. Assign the following attributes to your Transport Package (Change “##” to your group number): Transport Package Name: Transport_Package_User_## Transport Package ID: Transport_Package _User_## Transport Package ID Prefix: com.sap Master Language: English Open the object for editing. 3-4-4 Assign your role to your transport package. Right-click on your role and select Add object to transport package. Click on Export. Which transport methods are possible? Answer: __________________________________________________ What is the ID of the transport request? Answer: _______________________________________________ What is the name of the new created file?

© SAP AG

E2E200

3-71

Exercices
Unit: Lesson: Enhanced Change and Transport System Transport Organizer Web UI

At the conclusion of this exercise, you will be able to: • Create and releases transport requests in the Transport Organizer Web UI • Check the object list and the logfiles of transport requests.

3-5

Release your transport request in the Transport Organizer Web UI. 3-5-1 Call the Transport Organizer Web UI by opening the Transport Management tab. 3-5-2 3-5-3 3-5-4 3-5-5 3-5-6 Find your transport request. Is it flagged as a standard request? Enter a description for your transport request. Check the object list of your transport request Release the transport request Check the transport request log file

3-6

Import the transport request into JAQ. 3-6-1 Preparation: Delete the assignment of your role to the workset Time Recording. The development system JAD and the quality assurance system JAQ point to the same physical Portal system. Therefore, you need to delete the assignment of the workset so that you can verify that the transport was successful. 3-6-2 3-6-3 3-6-4 Go to the import queue for system JAQ. The iView is part of the role Transport Management which is assigned to your Portal user. Mark your transport request and start the import (only your transport request, not the whole queue). Check the import log files in the Import Queue. Which transport steps were performed during the import? Answer: ___________________________________________________ What was the return code of the import? Answer: ___________________________________________________ Check if the workset is assigned to your role in the Portal.
E2E200 3-72

3-6-5
© SAP AG

Solutions
Unit: Lesson: Enhanced Change and Transport System Portal Content Studio

3-1

Create a new role in the Enterprise Portal TT5. 3-1-1 Log on to the Enterprise Portal on system TT5 with your user E2ECC-## (Change “##” to your group number). Use the URL http://<hostname>.wdf.sap.corp:55000/irj 3-1-2 In the Portal Content Catalog, navigate to the folder com.sap.OTO_Training In the tab Content Administration open the folder Portal Content. Go to Browse the Portal Catalog and open Portal Content.

3-1-3

Create a new role. Assign the following general properties to your role: Role Name: Role_User_## (Change “##” to your group number) Role ID: Role_User_## Role ID Prefix: com.sap Master Language: English Description: Role of group ## Right-click on com.sap.OTO_Training and choose NewåRole

© SAP AG

E2E200

3-73

Step 1: Fill in General Properties (see following screenshot):

Change the “##” to your group-number. Choose Next. Step 2: Check the summary.

Choose Finish. 3-1-4 Mark the role as an entry point. Select Open the object for editing and choose OK. Select Entry Point Yes and choose Save.

© SAP AG

E2E200

3-74

3-2

Assign the role to your user 3-2-1 In the Portal, navigate to User Administration / Identity Management and search for your User. In the tab User Administration, open the folder Identity Management. Enter your User-ID (E2ECC-##) and choose Go. 3-2-2 Assign the role that you already created to your User. Select the line of your User-ID and click-on the tab Assigned Roles in the Details section. Click the button Modify and enter the name of your role in the section Available Roles. In the search field, enter an asterisk ‘*’ at the beginning and at the end of the role name and click on Go.

Select the line of your Role and choose Add. Choose Save to finish. 3-2-3 Refresh your browser and check if there is a new entry in the top level navigation. Refresh your browser (F5) and you will see your role in the Top Level Navigation.

. 3-3 Assign the workset Working Time to your role. 3-3-1 In the Portal Content Catalog, navigate to the folder com.sap.OTO_Training On the tab Content Administration, open the folder Portal Content. Go to Browse the Portal Catalog and open Portal Content.

© SAP AG

E2E200

3-75

3-3-2

Open the role that you created earlier. Open the folder com.sap.OTO_Training and double-click the role you created before.

3-3-3

Assign the workset Working Time to the opened role as a Delta Link. The workset can be found in Portal Content å Content provided by SAP å End User Content å Employee Self Service å Worksets. Right-click the workset Working Time and choose Add Workset to role å Delta Link

© SAP AG

E2E200

3-76

Choose Close to finish. 3-3-4 Refresh your browser and check if there is a new workset under your role. Refresh your Browser (F5) and you will see the new workset under your role.

© SAP AG

E2E200

3-77

Solutions
Unit: Lesson: Enhanced Change and Transport System Transport Package Editor

3-4

Put your changes into a transport package and export the transport package to a transport request. 3-4-1 Log on to the Enterprise Portal on system TT5 with your user E2ECC-## (Change “##” to your group number). Use the URL http://<hostname>.wdf.sap.corp:55000/irj 3-4-2 Go to the Transport Package Editor and navigate to the role that you have just created. On the tab System Administration open the folder Transport Transport Packages Export. Go to Browse the Portal Catalog and open Portal Content. 3-4-3 Create a new Transport Package. Assign the following attributes to your Transport Package (Change “##” to your group number): Transport Package Name: Transport_Package_User_## Transport Package ID: Transport_Package _User_## Transport Package ID Prefix: com.sap Master Language: English Right-click com.sap.OTO_Training and choose NewåTransport Package Step 1: Fill in General Properties (see following screenshot):

Change the “##” to your group-number. Choose Next.

© SAP AG

E2E200

3-78

Step 3: Check the summary.

Choose Finish. Select Open the object for editing and choose OK. 3-4-4 Assign your role to your transport package. Right-click your role can choose Add object to transport package

Click-on Export and check the summary. Which transport methods are possible? Answer: CTS and File System What is the ID of the transport request? Answer: JADK9*****

© SAP AG

E2E200

3-79

Click-on Start Export. What is the name of the newly created EPA file? Answer: com.sap.Transport_Package_User_XX_********_******.epa

© SAP AG

E2E200

3-80

Solutions
Unit: Lesson: Enhanced Change and Transport System Transport Organizer Web UI

3-5

Release your transport request in the Transport Organizer Web UI. 3-5-1 Call the Transport Organizer Web UI by opening the Transport Management tab. In the tab Transport Management open the iView Transport Organizer. 3-5-2 Find your transport request. Is it flagged as a standard request? Search for the transport request that you created earlier.

3-5-3

Enter a description for your transport request. Mark the line of your transport request, go to the Properties tab and enter a description. Enter “Transport Request for Group ##”. Change “##” to your groupnumber. Choose Save.

3-5-4

Check the object list of your transport request. Go to the Object List tab and check if you can see the EPA file you exported before.

© SAP AG

E2E200

3-81

3-5-5

Release the transport request. Choose Release to release the transport request.

3-5-6

Check the transport request log file. In the Status field, select Released. Go to the Logs tab and double-click JAD. Scroll to the end of the window that opens and check the return code (should be “0”).

3-6

Import the transport request into JAQ. 3-6-1 Preparation: Delete the assignment of your role to the workset Time Recording. The development system JAD and the quality assurance system JAQ point to the same physical Portal system. Therefore, you need delete the assignment of the workset so that you can verify that the transport was successful.
E2E200 3-82

© SAP AG

In the tab Content Administration, open the folder Portal Content. Go to Browse the Portal Catalog and open Portal Content. Go to the folder com.sap.OTO_Training and double-click your role to open it. On the right side, the structure of the role is displayed.

Mark the workset Working Time and press the Delete button. 3-6-2 Go to the import queue for system JAQ. The iView is part of the role Transport Management, which is assigned to your Portal user. On the tab Transport Management, open the folder STMS Queue.

Double-click JAQ to open the import queue.

© SAP AG

E2E200

3-83

3-6-3

Mark your transport request and start the import (only your transport request, not the whole queue). Choose Menu å Request å Import. Check the Start Import window and choose Yes. Check the status of your transport request in the import queue. It should turn to yellow (“Request is ready for import again”)

3-6-4

Check the import log files in the Import Queue. Mark your transport request and choose Menu å Request å Display å Logs. Which transport steps were performed during the import? Answer: Selection for Import, Import, Deployment What was the return code of the import? The return codes for all import steps should be 0.

3-6-5

Check if the workset is assigned to your role in the Portal. Log on to the Portal again or refresh your browser (F5). You should now see again the new workset Working Time under your role.

© SAP AG

E2E200

3-84

Solut ion Docum ent a t ion

Unit 1 Introduction to E2E Change Control Management Unit 2 Software Change Strategies Unit 3 Enhanced Change and Transport System Unit 4 Solution Documentation Unit 5 Quality Gate Management Unit 6 Change Request Management Unit 7 Maintenance Management Unit 8 Test Management Unit 9 Change Diagnostics

© SAP 2009

© SAP AG

E2E200

4-1

End-t o-End Busine ss Proc e sse s Are a Cha llenge for Solut ion Ope ra t ion

Spread Sheet

EP 7.0 EP 6.0

Siebel CRM XI Manugistics Legacy System BW

Outlook External Web

People soft HR

Documentum

R/3

© SAP 2009

̈

In the last few years, the IT world of SAP customers has become much more complex. Instead of one single SAP R/3 system there are now extensive system landscapes distributed over the entire globe and involving different SAP solutions. Therefore, it has become much more complicated to keep track of the whole system landscape. If something goes wrong within the solution landscape, it is much more difficult to judge the relevance for other activities. It is, therefore, much more important to have an operational concept for the customer’s solution landscape.

© SAP AG

E2E200

4-2

Why Solut ion Docum ent a tion I s I m port a nt

Get a common understanding on business processes

Accelerate search for information

Training of new employees and rollouts of new functionality

Foundation for bug fixing and later process enhancements

Basis for End to End Solution Operations

© SAP 2009

© SAP AG

E2E200

4-3

SAP Solut ion M a na ge r Arc hit ec t ure

SAP Solut ion M a na ge r
Roadmap, Blueprint and Implementation Testing
ple Up m e gr nta ad ti e on

Change Diagnostics

Maintenance Optimizer

cts oje Pr

Application Management

on uti l So

ns tio era Op

Im

Service Desk

Optimization

Change Request Management

BPR

Implementation Content

Business Processes

Documentation Systems

SAP ERP
© SAP 2009

NW BI

NW XI

Other

̈ ̈

As the central instance, SAP Solution Manager provides a variety of centralized services for implementing and operating your SAP solutions. The advantages are the following: • One central point of access • End-to-end process control • Guaranteed consistency within your system landscape • Dependencies between different components are taken into account

̈

Business processes can be created manually or customers can use predefined processes from the Business Process Repository (BPR)

© SAP AG

E2E200

4-4

Solut ion Docum ent a t ion: U nit Ove rvie w Dia gra m
Solution Landscape Documentation Lesson 1: Solution Manager System Landscape (SMSY) Lesson 2: System Landscape Directory Lesson 3: Projects Lesson 4: Solutions Appendix: Solution Documentation Assistant

© SAP 2009

© SAP AG

E2E200

4-5

H ow t o Ca pt ure Syst e m Da t a ?

Automatic Retrieval from Existing Repositories
̈ ̈

System Landscape Directory (SLD) Transport Management System (TMS)

Manual Data Entry
̈ ̈

Add additional information Include non-SAP systems

SAP Solution Manager

SMSY

© SAP 2009

© SAP AG

E2E200

4-6

Solut ion M a nage r Da t a M ode l (T ra nsac t ion SM SY )
Product System / Product Version Main Instance Logical System Customer system landscapes
Logical component A

Product
Client 002 DEV system QA system PRD system … system

System

ABAP

Client 200 Client …

Logical component B
DEV system QA system PRD system … system

J2EE

TREX
Project 2 Project 1
Logical component A
DEV QA PRD

Solution 2 Solution 1
Logical component A
DEV QA PRD

Logical component B
DEV QA PRD

Logical component B
DEV QA PRD

© SAP 2009

̈ ̈

A logical component is an administration unit which uniquely assigns logical systems to system roles for a product throughout the system landscape and across projects. For example, we can have the logical component Z_ERP, defined for product SAP R/3, with product version 4.6C and main instance ‘R/3 Server’ containing the three systems R3D, R3Q, and R3P with the roles of ‘development’, ‘quality’, and ‘productive’ respectively. A product can have several main instances. For example, SAP CRM consists of CRM Server, TREX, CRM IPC, CRM Mobile Client. Process steps can only run on ‘Logical Components’. On the other hand, a business process step can be executed on ‘implementation-relevant’ main instances. Therefore, you can have one logical component for every implementation relevant main instance of a product. For definitions of Products, Product Versions, Systems, Logical Components, Main Instances see: Media Library Solution http://service.sap.com/supportstandards Documentation

̈

̈

© SAP AG

E2E200

4-7

T ra nsac t ion SM SY : Soft w a re and H a rdw a re I nve nt ory

SID, Product, Main Instance Installation Number Data Source and Reliabilty of data Message Server, System Nr., DB

Software Components, version information and SP Level

© SAP 2009

̈

Data retrieved for ABAP systems: • System name and number • Message server • Clients (information from client table T000) • Installed software components, releases, and patch levels • Instances of the system • Servers assigned to the instances • Server data • Databases of a system • Server of a database • License keys from system

© SAP AG

E2E200

4-8

Syste m De m o

SMSY

© SAP 2009

© SAP AG

E2E200

4-9

Ex e rc ise

SMSY

© SAP 2009

© SAP AG

E2E200

4-10

Solut ion Docum ent a t ion: U nit Ove rvie w Dia gra m
Solution Landscape Documentation Lesson 1: Solution Manager System Landscape (SMSY) Lesson 2: System Landscape Directory Lesson 3: Projects Lesson 4: Solutions Appendix: Solution Documentation Assistant

© SAP 2009

© SAP AG

E2E200

4-11

SAP Syst e m La ndsca pe Dire c t ory

Customer

Master Component Repository
Applications Scenarios Software Units
Usage Types Appl. Comp.

SLD
Landscape description CIM* Update Component information CIM*

Customer Landscape

3rd-Party / Customer Component Types

Landscape Patterns
Possible Combinations

Regular manual task å SAP Note 669669

© SAP 2009

̈

At the SAP site, a Master Component Repository mirrors the data from the SAP Product and Production Management System (PPMS). Therefore, the Master Component Repository contains up-to-date information about all available SAP products and their dependencies. The content of the Master Component Repository is published on the SAP Service Marketplace, so that customers can update their individual component information. The content updates are available as delta files (see note 669669 for details). Customers can add additional information about 3rd-party products in use and their own development activities to their individual component information in their System Landscape Directories. The landscape description contains information about all systems and installed products or components at the customer’s site. Applications and tools (installation, administration, etc.) use information from the System Landscape Directory as a central information provider. Based on proven industry standards of the Distributed Management Task Force (DMTF): • Common Information Model (CIM) • Web-Based Enterprise Management (WBEM)

̈

̈

̈ ̈ ̈

̈

You can access SLD by directing a browser to http://<server>:<port>/sld (where <server> is the SLD server and <port> is the J2EE HTTP port). You will be prompted for a user name and password.

© SAP AG

E2E200

4-12

I nform a t ion St ored in t he SLD

Name Reservation for Java Development

Component Information

Landscape Description
̈ ̈ ̈

Technical Landscape Landscapes Business Landscape

© SAP 2009

̈ ̈

SLD is part of the J2EE Engine and can be accessed at: http://<server_name>:<http_port>/sld It contains the following parts: • Landscape Description • Technical Landscape • Business Landscape – business systems are logical systems that act as senders or receivers within the SAP NetWeaver Exchange Infrastructure. A business system is always associated with a technical system.

̈ ̈

Component Information Name Reservation • Namespaces (done only by administrators) • Single names (done only by administrators – developers perform this task in the SAP NetWeaver Developer Studio)

© SAP AG

E2E200

4-13

SAP Solut ion M a na ge r a nd Syst e m Landsc a pe Dire c t ory

SAP Solution Manager

SAP ABAP System

SMSY

SAP Java System SAP SLD Server

SLD

If you use SLD as data repository for SAP Solution Manager, you get data about Java systems in addition to ABAP system data.
© SAP 2009

̈ ̈ ̈ ̈

SAP Solution Manager also provides a system data repository. Both system data repositories can be used independently of each other. A synchronization point exists. SMSY can read data from SLD. Use of these repositories depends upon current customer‘s landscape: • If there are only ABAP components in place, then SLD is optional. • If there are also Java components in place (SAP NetWeaver Enterprise Portal, SAP NetWeaver Exchange Infrastructure, etc.), then SLD is mandatory.

̈

Data retrieved from SLD in addition for Java systems • Instances of the system • Servers assigned to the instances • Server roles (types) • Installed software components, releases, and patch levels • TREX, 3rd party, etc.

© SAP AG

E2E200

4-14

H ow t o Sw it c h SAP Solut ion M a nage r t o SLD

To switch to SLD:
̈

Use transaction SMSY_SETUP in SAP Solution Manager:

̈

Perform several tasks in SLD Connection Setup (see SAP Solution Manager Implementation Guide):

© SAP 2009

̈

SLD Clients • Configure the SLD Data Supplier (in an ABAP system). Call transaction RZ70 and maintain the gateway server host and the name of the gateway service. • Configure the SLD Data Supplier (in a J2EE system). Start the J2EE Engine Visual Administrator and navigate to Administration Server Services SLD Data Supplier.

̈

SAP Solution Manager • Connect System Landscape Directory to Solution Manager (transaction SLDAPICUST). • Create a TCP/IP connection to the SLD (SM59). • For automatic data capturing, start the TX SMSY_SETUP and configure the sources System Landscape Directory with the time interval. • See IMG of Solution Manager for details: basic settings landscape connect SLD system landscape put systems in

̈ ̈

SLD Server: Activate the SLD Server. Call up the SLD initial page http://<host>:<port>/sld and choose Administration Server Settings. Enter a name for the Object Server. Import and select the

̈

Import the SAP Master Component information. Choose Administration file CR_content.zip.

© SAP AG

E2E200

4-15

̈

Specify Service for Communication (JCo RFC Provider). From the J2EE side , /usr/sap/JCXX/J2EE/admin/go or go.bat, Visual admin—Server å Services å Jco RFC Provider (fill with the information shown on the screen).

© SAP AG

E2E200

4-16

SLD Landsc ape Se t up Possible Sc ena rio
Key Message
̈

Two central SLDs, one for design time, one for runtime, local SLD on SAP Solution Manager Front Ends
SAP NetWeaver Developer Studio
SLD local

Management Systems
SAP Solution Manager

Automatic Forwarding
SLD (design-time)
of all technical landscape data

Selective Transport
of individual data

SLD (runtime, central receiver of client data)

NWDI

PI (non-prod.)

Other application systems (non-prod.)

PI (prod.)

Other application systems (prod.)

Non-Production Environment
© SAP 2009

Production Environment

̈ ̈ ̈ ̈ ̈ ̈

This slide shows the recommended SLD landscape with one central runtime SLD and one central design time SLD. In addition, the local SLD on the Solution Manager should be configured to store the technical system information for transaction SMSY. If no PI or other application is used which relies heavily on SLD information, the local SLD of the Solution Manager can be used as the central runtime SLD. All managed systems should be connected and send technical system data to the central SLD. The central SLD should auto-forward the technical system data to the design time SLD and the local SLD of the Solution Manager. As of NW 7.10 the fully automatic synchronization can be used also. Information that has been written to the design time SLD can then be transported to the central runtime SLD. This can be customer software components and name reservations for Java developments. A planning guide for the System Landscape Directory is available at: http://www.sdn.sap.com/irj/sdn/nw-sld

̈

© SAP AG

E2E200

4-17

Syste m De m o

System Landscape Directory

© SAP 2009

© SAP AG

E2E200

4-18

Solut ion Docum ent a t ion: U nit Ove rvie w Dia gra m
Solution Landscape Documentation Lesson 1: Solution Manager System Landscape (SMSY) Lesson 2: System Landscape Directory Lesson 3: Projects Lesson 4: Solutions Appendix: Solution Documentation Assistant

© SAP 2009

© SAP AG

E2E200

4-19

Solut ion M a nage r Proje c t s

Projects
̈ Projects focus on managing changes
̈

The project serves as container for project information:
̈ ̈ ̈ ̈ ̈

Project documentation System landscape Project standards Milestones … Implementation Testing Upgrade E-Learning Management Quality Gate Management Change Request Management Handover to Operation

̈ All implementation scenarios in SAP Solution Manager are based on projects:
̈ ̈ ̈ ̈ ̈ ̈

̈ Any project change is copied to the solution directory after being set active
̈
© SAP 2009

© SAP AG

E2E200

4-20

Sc ope of Proje c t s

Project Phases
Realization Final Preparation Go Live

Solution
Project Landscape

Gobal ERP Global CRM Global BW Development

Gobal ERP Global CRM Global BW Quality Assurance

Gobal ERP Global CRM Global BW Production

© SAP 2009

̈ ̈

In this example, the project works on the ERP and CRM system. The complete transport landscape is part of the project.

© SAP AG

E2E200

4-21

H ow t o Doc um ent Y our Solut ion in SAP Solut ion M a nage r?
1) Create a project 2) Model the business process 3) Assign documentation
̈ ̈ ̈ ̈ ̈ ̈

Definition of entry points Development object list Functional documentation / business background Performance and value KPIs Integration and volume test Application operations guide

4) Transfer information into solution

© SAP 2009

© SAP AG

E2E200

4-22

St e p 1 : Cre a t e a Proje c t (T ra nsac t ion SOLAR_PROJ ECT _ADM I N )
Content
̈ ̈ ̈ ̈ ̈

Project name System landscape Team member Project standards (key words) …

© SAP 2009

All existing projects are displayed in the project overview of Solution Manager. Additional functions are available to coordinate the project administration data of a project. ̈ Transaction SOLAR_PROJECT_ADMIN provides an overview of the active projects in the customer organization. Alternative: You can use Workcenter: Implementation/Upgrade Plan Create or Maintain Project You can enter the following data on the General Data tab: ̈ Person responsible - The responsible person must exist in the project administration of the SAP system. You can use the possible entries help to change the responsible person. ̈ Project language • When you choose a project language, all language-dependent information for this language (project documentation and status information) is made available to project members. This is independent of the logon language of the project member. • The project structure is created in the specified project language. • All content will be stored in the chosen project language. • Once the project language has been selected and saved, it can no longer be changed. ̈ Status - The default values for status are set on the Project Standards tab. ̈ Plan Data - This tab allows you to enter the dates for the planned project start and finish as well as the work required in man days (MD). ̈ Actual Data - This tab allows you to enter the dates of the actual project start and finish and the actual work carried out in man days (MD). • The planned data and the actual data represent the time plan for the entire project. Any date entered for individual process steps in the Business Blueprint or Realization phases must lie within the time frame set on the General Data tab.
̈

̈

© SAP AG

E2E200

4-23

Busine ss Proce sse s in SAP Solut ion M ana ge r

© SAP 2009

̈

The definition of the Business Blueprint allows you to document the business processes in your enterprise, which you wish to use in your SAP system. You create a project structure in which relevant business scenarios, business processes, and process steps are organized in a hierarchical structure. You can also create project documentation to assign to individual scenarios, processes, or process steps. To define how your business processes have to run in your SAP systems, you then assign transactions to each process step. The definition of the Business Blueprint provides you with a detailed description of your business processes and system requirements. You can also print out the Business Blueprint document. The project documentation and the project structure that you use during the Business Blueprint phase, can also be put to further use during configuration and test organization. • When you configure your business processes, the system displays the project structure you created for the Business Blueprint. You can use the Business Blueprint project structure as orientation point during configuration. • You can also display and edit the project documentation from the Business Blueprint phase during configuration. • The project structure from the Business Blueprint forms the basis for all test plans that you create during test organization. The transactions that you assign to process steps in the Business Blueprint are put in test plans during test plan generation. The transactions can be processed as function tests to test the transactions.

̈

© SAP AG

E2E200

4-24

St e p 2 : M ode l t he Busine ss Proc e ss (T ra nsac t ion SOLAR01 )
Reuse of existing content
̈ ̈

Business Process Repository Other project / solution

Create new content

© SAP 2009

© SAP AG

E2E200

4-25

St e p 3 : Assign Doc um ent a t ion (T ra nsac t ions SOLAR01 / SOLAR0 2 )
Procedure
̈ ̈ ̈ ̈

Select entry in hierarchy Select tab Insert document Change document

© SAP 2009

̈

For each element in the project hierarchy, there are multiple tabs for collecting documentation • Transactions • Development objects • Configuration • Project documentation • Administration (Status, plan/actual data, team member, keywords) • Test cases • Issues / messages • Training materials • End user roles

̈

SAP Solution Manager provides version control

© SAP AG

E2E200

4-26

Busine ss Proce ss Gra phic

Documentation linked to business process steps

© SAP 2009

̈ ̈

The Business Process Structure is the central documentation directory. It is available in a graphical view, which can be used to discuss the business processes.

© SAP AG

E2E200

4-27

Syste m De m o

Projects

© SAP 2009

© SAP AG

E2E200

4-28

Ex e rc ise

Projects and Business Processes

© SAP 2009

© SAP AG

E2E200

4-29

Solut ion Docum ent a t ion : U nit Ove rvie w Dia gra m
Solution Landscape Documentation Lesson 1: Solution Manager System Landscape (SMSY) Lesson 2: System Landscape Directory Lesson 3: Projects Lesson 4: Solutions Appendix: Solution Documentation Assistant

© SAP 2009

© SAP AG

E2E200

4-30

Solut ion Dire c tory in SAP Solut ion M a nage r

Solutions are groups of related systems
̈ ̈ ̈ ̈

Joint maintenance and administration Individual monitoring dashboards Provide restricted view of the systems …

Solution 2

Solution 3

Solution 1
© SAP 2009

̈ ̈

A solution describes a collection of information about systems, software components, and business processes (scenarios). Solutions are the basis for the operation scenarios • Solution Monitoring • Service Desk • Change Request Management • Collaboration

̈

Solutions provides handover information from the project phase to the operations phase • Any project change is copied to the solution directory after being set active

© SAP AG

E2E200

4-31

Crit e ria for T a iloring a Solut ion

̈ Business processes must run in one solution only (most important

criterion).
̈

All systems involved in a business process belong to the same solution. There is no strict limit, but the number of systems should be limited due to performance and usability aspects. The performance is driven by the number of monitoring alerts that need to be processed within a certain period. Are different organizations supporting different system groups? Is it necessary to restrict authorization to monitoring and functional data to certain system groups? Does a hosting provider support different companies?

̈ The number of systems in the solution should be limited.
̈ ̈

̈ Organizational units of a company or a corporate group
̈ ̈ ̈

̈ Normally, customers of small businesses and midsize companies

may use only one solution!

© SAP 2009

̈

From SAP’s point of view, the critical drivers for tailoring a solution are the size of the documented end-to-end business processes as well as the related number of systems involved, depending on use, for example, system monitoring. For complex organizations, we recommend that you define several solutions in accordance with the organizational tailoring and the selection requirements of the individual organizational units. In this way, large and complex customers and corporate groups can be displayed more clearly in special sections and administrated more effectively. However, it is essential that all of the business objects for a business process are located within one solution. The process must not be divided among several solutions or subprocesses.

̈

© SAP AG

E2E200

4-32

Solut ion Ove rvie w

Transaction SOLUTION_MANAGER is the central access point for all operation scenarios in the SAP Solution Manager
© SAP 2009

̈

The Solution Overview is the central point for maintaining business processes in SAP Solution Manager. Here, you can assign logical components to your solution landscape, create business processes, and copy business processes from implementation projects or other sources. You can also maintain your solution settings, such as the name of the solution. You can access the Solution Overview with the transactions DSWP or SOLUTION_MANAGER. Alternatively, you may access the Solution Overview via Workcenter: Solution Manager Solutions new Administration You can access the Solution Directory by using the transaction SOLMAN_DIRECTORY.

̈

̈

© SAP AG

E2E200

4-33

Busine ss Proce ss I nform a t ion in a Solut ion

Content
̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈

Process steps Transactions Development objects Configuration Documentation Test cases Graphic Training materials End user roles
Documentation linked to business process steps

© SAP 2009

̈ ̈ ̈ ̈

The data is displayed in a “swim-lane” graphic (as is also used in the project maintenance) indicating on which logical component the business process step is executed. Business processes are attached to either a project or a solution. Business Processes can be copied from a project to a solution when a project goes live. Set the status for the business process to “Production” if you want to monitor the business process. This is only possible if there is a production system assigned to the logical components that the business process is using.

© SAP AG

E2E200

4-34

T ra nsfe r Projec t t o Solut ion

Procedure
̈ ̈ ̈ ̈ ̈

Select Solution Go to the Structure tab Source: Project Use value help for Scenario Name Select project

© SAP 2009

̈

Business processes can be created manually, copied from the Business Process Repository, from other solutions or from projects.

© SAP AG

E2E200

4-35

Solut ion Docum ent a t ion Be st Pra c t ic e Re com me nda t ion
SAP Solution Manager enables the documentation of SAP solutions At least, the following information should be documented for core business processes:
̈ ̈ ̈ ̈ ̈

Involved systems Business process steps Used transactions/background jobs Interfaces Custom developments

Solution documentation is the foundation for proficient application management.
̈ ̈

Transparency enables efficient collaboration Solution documentation is the foundation of support processes (incident management, root cause analysis, maintenance, delivery of support services, integration validation, implementation/upgrade of SAP solutions, …)

Solution documentation enables customers to run application management processes efficiently and to use the complete benefits of SAP Enterprise Support
© SAP 2009

© SAP AG

E2E200

4-36

Syste m De m o

Solutions

© SAP 2009

© SAP AG

E2E200

4-37

Ex e rc ise

Solutions

© SAP 2009

© SAP AG

E2E200

4-38

Solut ion Docum ent a t ion: U nit Ove rvie w Dia gra m
Solution Landscape Documentation Lesson 1: Solution Manager System Landscape (SMSY) Lesson 2: System Landscape Directory Lesson 3: Projects Lesson 4: Solutions Appendix: Solution Documentation Assistant

© SAP 2009

© SAP AG

E2E200

4-39

Solut ion Docum ent a t ion Assist a nt Wha t doe s it do?

Wha t Doe s t he Solution Doc um e nt a tion Assit a nt Do?
̈

The solution documentation assistant reads the usage statistics in a productive system and maps them against the business process structure of a Solution Manager project. It is also possible to define SQL Check steps in order to analyze the database content. For all process steps that have transactions assigned the solution documentation assistant will automatically determine if the process step is used or not. The solution documentation assistant can thus automatically determine the used business processes in a productively used system.

̈ ̈

© SAP 2009

̈ ̈

The solution documentation assistant can be started via the workcenter. There is a separate workcenter for the solution documentation assistant. The solution documentation assistant provides an overview of the current status of your analysis projects and analyses. The overview also gives you quick access to your current analysis projects, analyses, and analysis results.

© SAP AG

E2E200

4-40

Solut ion Docum ent a t ion Assist a nt Ana lysis Proje c t – De fine the Chec k s

Business scenarios from projects are the input for a usage analysis

By default, all transactions which are assigned to process steps are checked for usage statistics (ST03). Additional checks can be defined, e.g. SQL statements which check for certain table entries.

© SAP 2009

̈

Analysis Project • Project created from an existing SAP Solution Manager project. Existing structures and objects are copied to the Analysis Project. Results are mapped to the structures in the Analysis Project, and can then be copied back to the underlying project to indicate what is in scope for the upgrade.

̈

Check Steps • The Analysis Result is based on check steps. You use Check Steps to determine what the Analysis should display. Check steps can be brought into the Analysis Project from the underlying Solution Manager project structure, or added from the Rule Database.

̈

Check Item • Organization object in the Analysis Project so you can group Check Steps. Check Items rate Analysis Structure nodes during analysis. The rating is based on the results of Check Steps assigned to the Check Items. You can assign any number of Check Steps to a Check Item. You can assign any number of Check Items to a structure node.

̈

Rule Database • Repository for Check Steps, can contain customer-specific transactions and report information from an analysis result. Check Steps detected during an analysis can be copied to the Rule Database for use in future analyses.

© SAP AG

E2E200

4-41

Solut ion Docum ent a t ion Assist a nt Ana lysis Re sults – Ex e cut e t he Chec k s

• Green: Active • Yellow: Probably Active • Red: Inactive
© SAP 2009

If the number of executions in the analysis period exceeds the threshold value, a transaction is marked as active. If it is an identifying check, then the corresponding business process step is marked as active.

̈

Analysis Results • Output of the Analysis, contains detailed consideration of analyzed objects such as transactions or reports. Results can also copied to the project or displayed in an HTML report.

© SAP AG

E2E200

4-42

Solut ion Docum ent a t ion Assist a nt U pda te t he Solut ion M a na ge r Proje c t

SAP Solution Manager Project is now updated, items not in scope have been deselected

© SAP 2009

̈ ̈

The results of the Solution Documentation Assistant can be transferred back to the source project. Steps which were identified as active by the Solution Documentation Assistant can be set to “In Scope”. Steps which were identified as not active can be set to “Out of Scope”. Steps with no results are not changed.

© SAP AG

E2E200

4-43

Solut ion Docum ent a t ion: U nit Sum m a ry

You should now be able to:
̈ ̈

Explain the architecture and use cases of the Solution Manager system landscape Keep the solution landscape documentation up to date by using automatic data collection procedures within SAP Solution Manager and System Landscape Directory Use Solution Manager projects to manage complex implementation projects Define and tailor solutions to manage productive systems Document business processes in the SAP Solution Manager

̈ ̈ ̈

© SAP 2009

© SAP AG

E2E200

4-44

Exercises
Unit: Lesson: Solution Documentation SMSY

At the conclusion of this exercise, you will be able to: • Find version information for a customer solution in SAP Solution Manager

TT4 is the Solution Manger system that contains all information about the system landscape. TT5 is a satellite system which is managed by TT4.

4-1

Check the support package level for the managed system TT5 4-1-1 What transaction is used to find the system landscape description in SAP Solution Manager? Answer: _____________________________________________________ 4-1-2 Call transaction SMSY and find information for the SAP ERP System TT5. What is the current Support Package Level for the software component SAP_APPL? Answer: ____________________________________________________ What is the data source of the version information? Answer: ____________________________________________________ When was the data last refreshed? Answer: ____________________________________________________ 4-1-3 Find version information for the Enterprise Portal on TT5 (SAP ERP TT5). What is the current Support Package Level for the software component SAPJEE? Answer: ____________________________________________________ What is the data source of the version information? Answer: ____________________________________________________ When was the data last refreshed? Answer: ____________________________________________________

© SAP AG

E2E200

4-45

Exercises
Unit: Lesson: Solution Landscape Documentation Projects

At the conclusion of this exercise, you will be able to: • Create a project in SAP Solution Manager • Maintain project data

This exercise has to be executed in the Solution Manager system TT4. The project consists of the SAP ECC system and an Enterprise Portal.

4-2 Create a project 4-2-1 4-2-2 What transaction in SAP Solution Manager do you use to create a project? Answer: ____________________________________________________ Create a new project with the name E2ECC_## of type Implementation project (## = your group number). Do not assign a solution. Enter a title for the project and select the project language English. On the tabstrip System Landscape -> Systems, enter the following logical components with the F4 Help: SAP ERP SAP ECC Server å logical component Z_ERP_CCM SAP NetWeaver Enterprise Portal å logical component Z_EP_CCM Create an IMG project for both logical components. When asked to create a transport request, immediately choose No, Later. Finally, both IMG projects should show a green light.

4-2-3

4-2-4

© SAP AG

E2E200

4-46

Exercises
Unit: Lesson: Solution Landscape Documentation Business Processes

At the conclusion of this exercise, you will be able to: • Transfer business processes from the business process repository • Assign documentation and test cases to the business process

This exercise has to be executed in the Solution Manager system TT4. The project consists of the SAP ECC system and an Enterprise Portal.

4-3

Create a business process from the business process repository in the new implementation project 4-3-1 Go to the business blueprint of the implementation project that you have created in the exercise before. In which transaction do you find the blueprint? Answer: ___________________________________________________ 4-3-2 Create a new business scenario HCM in the process structure (Do NOT select a scenario from the business process repository!) and save it. 4-3-3 Create a new business process. From the business process repository, select the Human Capital Management scenario and the process Managing Employee Time and Attendance. In the subsequent dialog box, deselect the proposed additional logical components. Save your selection. 4-3-4 The business process steps can now be maintained. Navigate to the structure of the process. After the first step, add an additional manual step (as an alternative to enter the working times in the ABAP backend system instead of the Portal). Enter the step name: Record working times in backend and assign the logical component for the ABAP backend system. Save your definition. Delete the last business process step Transfer analytics to SAP BW. 4-3-5 Navigate to the first step Record working times and absences and assign the URL for accessing the Enterprise Portal. What is the URL? Answer: ___________________________________________________ 4-3-6 Navigate to the newly created second step and assign the transaction CAT2. Test the transaction. In which system and client are you logged on? Answer: ____________________________________________________
E2E200 4-47

© SAP AG

4-3-7 4-3-8

Display the graphic and documentation for the process. Assign customizing activities to the newly created business process step. Which is the transaction for this? Answer: ____________________________________________________ Alternative: Go to the Work Center Implementation/Upgrade. From the Overview, choose the section Build and then click the link Goto Business Process Configuration. In this transaction, select the newly created step and assign a specific customizing activity from the F4 help in the tabstrip Configuration of type IMG Object. Choose the activity via the F4 help in the column Object and select the following IMG path in the Structure window: Cross Application Components Timesheet specific settings for CATS regular CATS regular Record Working Time -> define field selection. Choose Copy selected nodes and save your settings. What is the technical name of the IMG activity? Answer: ____________________________________________________ You can navigate into the customizing activity by double-clicking on the technical name. In which client on which system is the reference IMG started? Answer: ____________________________________________________

4-3-9

Assign an eCATT test case and a manually created test case to the newly created business process step. For the eCATT test case, use the F4 help (do NOT select a logical component) and search for the test case ZETIMERECORDING. For the manual test case, select type Test Document. In the dialog box, select Copy of Solution Manger Document. Select project E2ECC_DEMO and the test document ZDTIMERECORDING. In the column Test Object assign transaction CAT2.

© SAP AG

E2E200

4-48

Exercises
Unit: Lesson: Solution Landscape Documentation Solutions

At the conclusion of this exercise, you will be able to: • Create a Solution in SAP Solution Manager • Transfer a business process from a project to a Solution

This exercise has to be executed in the Solution Manager system TT4. The project consists of the SAP ECC system and an Enterprise Portal.

4-4

Create a solution and transfer the new business process to the solution 4-4-1 4-4-2 4-4-3 Name two transactions to call the operations part of SAP Solution Manager: Answer: ____________________________________________________ Create a new solution with the name E2ECC_## (## = your group number) Transfer the newly created business process into the solution. Check if the assigned logical components, the transaction, and the URL are included.

© SAP AG

E2E200

4-49

© SAP AG

E2E200

4-50

Solutions
Unit: Lesson: Solution Documentation Solution Manager System Landscape

4-1

Check the support package level for the managed system TT5 4-1-1 What transaction is used to find the system landscape description in SAP Solution Manager? The transaction name is SMSY 4-1-2 Call transaction SMSY and find information for the SAP ERP System TT5. What is the current Support Package Level for the software component SAP_APPL? In the tree structure on the left hand side of transaction SMSY, drill down into Landscape Components Systems SAP ERP TT5 SAP ECC Server. On the right hand side, choose the tab Software Components. Search for the software component SAP_APPL and check the SP Level. What is the data source of the version information? Choose the tab Header Data and check the value for Data Source. When was the data last refreshed? Check the value for Last Changed On/By. 4-1-3 Find version information for the Enterprise Portal on TT5 (SAP ERP å TT5). What is the current Support Package Level for the software component SAPJEE? In the tree structure on the left hand side of transaction SMSY, drill down into Landscape Components SAP ERP TT5 SAP NW – Enterprise Portal. On the right hand side, choose the tab Software Components. Search for the software component SAP-JEE and check the SP Level. What is the data source of the version information? Choose the tab Header Data and check the value for Data Source. When was the data last refreshed? Check the value for Last Changed On/By.

© SAP AG

E2E200

4-51

Solutions
Unit: Lesson: Solution Documentation Projects

4-2 Create a project 4-2-1 What transaction in SAP Solution Manager do you use to create a project? Answer: SOLAR_PROJECT_ADMIN Alternative: Select Work Center, then tabstrip Implementation / Upgrade. From Overview, choose the section Plan and then click the link Create or Maintain Project Create a new project with the name E2ECC_## of type Implementation project (## = your group number). Do not assign a solution. Enter a title for the project and select the project language English. In transaction SOLAR_PROJECT_ADMIN, create a new project. Enter the project name E2ECC_## and the project type Implementation project. Do not assign a solution. In the next screen, enter a title for the project and below the tabstrip General data select the project language English In the tabstrip System Landscape -> Systems enter the following logical components with the F4 Help: SAP ERP SAP ECC Server å logical component Z_ERP_CCM SAP NetWeaver Enterprise Portal å logical component Z_EP_CCM Alternatively to the menu path you can select in the tabstrip System Landscape -> Systems in the column Logical Component the F4-help button and enter in the next screen via the Search button the logical components Z_ERP_CCM and Z_EP_CCM. Finally save your selection and confirm the window Enhancements for documents. Create an IMG project for both logical components. When asked to create a transport request, immediately choose No, Later. Finally, both IMG projects should show a green light. Choose the tab IMG Projects. You should see a red light for your project. Mark your project and press button Create IMG Project ( ) . Choose No, Later on the dialog box that asks you to create a transport request immediately. Choose Yes when asked to give your IMG Project a new name. Name your IMG project E2ECC_##I (where ## is your group number). Choose No, Later on the dialog box that asks you to create a transport request immediately. Repeat the steps for the second logical component. Choose Back. Save the project.
© SAP AG E2E200 4-52

4-2-2

4-2-3

4-2-4

Solutions
Unit: Lesson: Solution Documentation Business Processes

4-3

Create a business process from the business process repository in the new implementation project 4-3-1 Go to the business blueprint of the implementation project that you have created in the exercise before. In which transaction do you find the blueprint? Answer: SOLAR01 Alternative: Select Work Center, then tabstrip Implementation / Upgrade. From the Overview, choose the section Plan and then click on the link Define Business Blueprint 4-3-2 Create a new business scenario HCM in the process structure (Do NOT select a scenario from the business process repository!) and save it. Navigate in the Business Blueprint Structure to Business Scenarios, select tabstrip Structure and enter HCM as the Scenario Name. Save your settings 4-3-3 Create a new business process. From the business process repository, select the Human Capital Management scenario and the process Managing Employee Time and Attendance. In the subsequent dialog box, deselect the proposed additional logical components. Save your selection. In the Business Blueprint Structure, navigate to Business Processes, and select tabstrip Structure. Use the F4 help in the column Process Name and enter in the next screen via the Search button the process Managing Employee Time and Attendance. Choose the entry below this process and choose Continue. Deselect the logical component selection in the next screen and save your settings. 4-3-4 The business process steps can now be maintained. Navigate to the structure of the process. After the first step, add an additional manual step (as an alternative to enter the working times in the ABAP backend system instead of the Portal). Enter the step name: Record working times in backend and assign the logical component for the ABAP backend system. Save your definition. Delete the last business process step Transfer analytics to SAP BW. In the Business Blueprint Structure, mark the newly created process Managing Employee Time and Attendance. Select the tabstrip Structure on the right and mark the second step Record and administrate time data. Select the icon Insert Line and enter Record working times in backend as the step name. Select logical component Z_ERP_CCM from the F4 help and save your settings. Now mark the last process step Transfer analytics to SAP BW and press the button Delete Row. Confirm the next dialog box and save your settings.
E2E200 4-53

© SAP AG

4-3-5

Navigate to the first step Record working times and absences and assign the URL for accessing the Enterprise Portal. What is the URL? Navigate to the first step in the business blueprint structure. Select tabstrip Transactions. Use type web address or file, type in the text Portal Access and the URL for the Portal access: http://<servername>:55000/irj/portal

4-3-6

Navigate to the newly created second step and assign the transaction CAT2 Test the transaction. In which system and client are you logged on? Navigate to the newly created step in the Business Blueprint Structure. Select tabstrip Transactions. Use type: Transaction, enter CAT2 in the field Object and save your settings. Select the Execute button of the new business process step in the Business Blueprint Structure. You are logged on to client 800 in the ECC system TT5.

4-3-7

Display the graphic and documentation for the process Navigate to the process in the Business Blueprint Structure. Then choose the tabstrip Graphic. The documentation can be found under the tabstrip General Documentation. The graphic should look like this:

4-3-8

Assign customizing activities to the newly created business process step. What is the transaction for this? Answer: SOLAR02 Alternative: Go to the Work Center Implementation/Upgrade. From the Overview, choose the section Build and then click the link Goto Business Process Configuration. In this transaction, select the newly created step and assign a specific customizing activity from the F4 help in the tabstrip Configuration of type IMG Object.

© SAP AG

E2E200

4-54

Choose the activity via the F4 help in the column Object and select the following IMG path in the Structure window: Cross Application Components Timesheet specific settings for CATS regular CATS regular Record Working Time -> define field selection. Choose Copy selected nodes and save your settings. What is the technical name of the IMG activity? Answer: The technical name is PCUI_ESS_CATS_004 The technical name can be found below the column Object of the related business step. You can navigate into the customizing activity by double-clicking on the technical name. In which client on which system is the reference IMG started? Answer: Client 801 in the ECC system TT5 4-3-9 Assign an eCATT test case and a manually created test case to the newly created business process step. For the eCATT test case, use the F4 help (do NOT select a logical component) and search for the test case ZETIMERECORDING. Solution: Navigate to your new step in the configuration structure on the left handside. Select tabstrip Test Cases. Below column Test Case Type, choose eCATT Test Configuration and do NOT select a logical component. Enter the name ZETIMERECORDING in column Test Case via the F4 help in the field Test Configuration in the next window and save the settings. For the manual test case, select type Test Document. In the dialog box, select Copy of Solution Manger Document. Select project E2ECC_DEMO and the test document ZDTIMERECORDING. In the column Test Object assign transaction CAT2. Solution: Choose Test document as the type. In the next popup select Copy of a Solution Manager Document. In the next popup select the project E2ECC_Demo and Execute. Then mark ZDTIMERECORDING and press Enter, Save and Close. In column Test Object assign transaction CAT2 by using the F4-help.

© SAP AG

E2E200

4-55

Solutions
Unit: Lesson: Solution Documentation Solutions

4-4

Create a solution and transfer the new business process to the solution. 4-4-1 4-4-2 Name two transactions to call the operations part of SAP Solution Manager: Answer: DSWP, SOLUTION_MANAGER Create a new solution with the name E2ECC_## (## = your group number) Execute transaction DSWP. In the Solution Overview, choose Create. Enter the name of your solution. Leave all other fields unchanged and choose Continue. 4-4-3 Transfer the newly created business process into the solution. Check if the assigned logical components, the transaction and URL are included. Navigate into Solution Landscape Maintenance of your new solution. Switch to change Mode . In the business process section, transfer the business process from your implementation project (make sure that the source is set to project!). 1. Press F4 in Scenario Name field 2. Drilldown to your project E2ECC-##, click Business Scenarios, then HCM, Copy and Continue 3. Save and Refresh. Confirm the assigned logical components.

Navigate to the first two process steps. Check under tabstrip Transactions if the URL and the transaction CAT2 have been assigned.

© SAP AG

E2E200

4-56

Qua lity Ga t e M a na ge m ent

Unit 1 Introduction to E2E Change Control Management Unit 2 Software Change Strategies Unit 3 Enhanced Change and Transport System Unit 4 Solution Documentation Unit 5 Quality Gate Management Unit 6 Change Request Management Unit 7 Maintenance Management Unit 8 Test Management Unit 9 Change Diagnostics

© SAP 2009

© SAP AG

E2E200

5-1

Qua lity Ga t e M a na ge m ent : U nit Obje c t ive s

After completing this unit, you will be able to:
̈ ̈ ̈ ̈ ̈

Explain the concept of solution transports and track synchronization Describe the project phases in quality gate management Describe the tasks of a quality manager in different phases of an implementation project Create and release transport requests centrally in SAP Solution Manager for ABAP and non-ABAP environments Set up and use quality gate management as a central transport management tool

© SAP 2009

© SAP AG

E2E200

5-2

Qua lity Ga t e M a na ge m ent : U nit Ove rvie w Dia gra m
Quality Gate Management Lesson 1: Overview Lesson 2: Project Phases and Quality Gates Lesson 3: Central Transport Management Lesson 4: Creating new Projects Lesson 5: Prerequisites and Setup

© SAP 2009

© SAP AG

E2E200

5-3

St a nda rd Applic at ion a nd Qua lit y M a nage m ent One int e gra t e d a nd Consist e nt Quality Proc ess
ALL OPERATIONAL UNITS ACROSS ALL ORGANIZATIONS INTEGRATED IN ONE INTEGRATED AND CONSISTENT QUALITY PROCESS
Synchronization
NW Portal 7.0
Dev System

NW Portal 7.0
QAS System

NW Portal 7.0

FIX

Presentation layer

CE 7.1
Dev system

CE 7.1
QAS system

CE 7.1
PRD system

FIX

ERP6.0
Dev system

ERP6.0
Dev system

ERP6.0

FIX

PRD system

Development Landscape Transport Multiple Development Workbenches

Quality Landscape Transport

Production Landscape

100% transparency of changes ̈ A central transport mechanism and change control system to manage changes across technology stacks and application components ̈ A central test plan for core business processes ̈ A central quality manager validating test execution and test completeness ̈ Integration of every development workbench into the central transport and change control system
̈

© SAP 2009

© SAP AG

E2E200

5-4

Qua lity Ga t e M a na ge m ent Role s and Re sponsibilit ie s
Development Lead IT Operator

… creates and releases changes and transports for the developers. … performs imports into the test and production systems.

Quality Manager Quality Advisory Board

… performs quality checks at certain project milestones.

… supervises the risks of an implementation project.

© SAP 2009

̈ ̈ ̈ ̈ ̈

Responsibilities: In principle, four roles can be identified in the process of using Quality Gate Management: A development lead is responsible for creating changes and transport requests, assigning them to the developers and releasing them, when the development is complete. An IT Operator is responsible for importing the transport requests into the test and production systems. He monitors the imports and fixes technical problems during the import process. The Quality Manager performs quality checks at certain project milestones. For example he checks if project documentation and testcases are available in a good quality. He also checks the result of automated quality checks like code inspection analyses or completeness of transports in the test system. The Quality Advisory Board is the steering committee for the implementation project. It supervises the risks of an implementation project

̈

© SAP AG

E2E200

5-5

I m port a nt Role : Qua lity M a na ge r

Responsibility:
The Quality Manager performs manual and automated quality checks at certain project milestones. For example, he or she checks if project documentation and test cases are available and in a good quality. He also supervises the result of automated quality checks like code inspection analyses, checks of critical transport objects, completeness and consistency of transport requests. The quality manager is responsible to define standards, procedures, and metrics to make sure that the development department or external implementation partners deliver a good code quality with regard to development standards, documentation, maintainability, supportability, performance, volume-readiness, etc. He or she reports to the quality advisory board and organizes quality review meetings at milestones of an implementation project.

© SAP 2009

© SAP AG

E2E200

5-6

I m port a nt Role : Qua lity Advisory Boa rd

Responsibility:
The quality advisory board is the steering committee for an implementation project. It supervises budget, timelines, and risks of an implementation project.

© SAP 2009

© SAP AG

E2E200

5-7

Work Cent e r Cha nge M anage m ent : Ove rvie w

© SAP 2009

̈ ̈

In the Overview you get a quick insight about the different projects and their status. You see all projects you are involved in, sorted by project phase. From here, you are able to jump directly into the Project view.

© SAP AG

E2E200

5-8

Work Cent e r Cha nge M anage m ent : Proje c ts å Gra phica l V ie w

̈

Project and Quality Gate Calendar

© SAP 2009

̈

The Graphical view of your project contains an overview of the deadlines, Q-Gates, and milestones in your project. You can prepare existing projects for quality gate management, or change them, and manage document templates for the project Q-Gates, with Maintain Project.

© SAP AG

E2E200

5-9

Work Cent e r Cha nge M anage m ent : Proje c ts å List V ie w

Central transport mechanism and change control Manage changes across the technology framework and application ̈ Every development workbench is integrated
̈ ̈
© SAP 2009

̈

You can display and edit your project in a list, in the List View. The following subscreens are available: • Project List • List of Changes for a Project • List of Transports for a Change

̈

The top list or table shows the projects which you have selected with the display filter at the top of the screen. The second table shows the changes made to the project selected in the first table. The third table contains the transport requests for the change selected in the second table. You can create new changes, release transport requests, or import from another system. A subscreen has several tabs in which you can perform other functions, such as check TMS configuration or go to the Q-Gate data.

̈

© SAP AG

E2E200

5-10

Work Cent e r Cha nge M anage m ent : Proje c ts å Proje c t Sta t us

© SAP 2009

̈ ̈

This is a graphical overview of your system landscape. The systems are separated by Q-Gates. You can go to the Q-Gate screens. The color of the Q-Gates indicates their status: • Grey: Q-Gate initial, not yet processed • Orange: Q-Gate in process • Green: Q-Gate passed

© SAP AG

E2E200

5-11

Work Cent e r Cha nge M anage m ent : Proje c ts å Risk s

© SAP 2009

̈ ̈

The Risks View shows the risks associated with transports in your project. The risks are collected automatically by the system. The quality manager can decide before each phase or phase completion whether all transports have run correctly into the next system or whether he or she must take measures to ensure that they do so. The view has two screen areas: • The top area contains the systems and the risk descriptions. • The bottom area contains the change requests for your project which are affected by these errors.

̈

̈

Risks can be, for example: • Transport error (return code • Missing transport requests • Transports that did not run synchronously 8)

̈

The quality manager can react to critical situations appropriately, and assesses the project risk.

© SAP AG

E2E200

5-12

Qua lity Ga t e M a na ge m ent : U nit Ove rvie w Dia gra m
Quality Gate Management Lesson 1: Overview Lesson 2: Project Phases and Quality Gates Lesson 3: Central Transport Management Lesson 4: Creating new Projects Lesson 5: Prerequisites and Setup

© SAP 2009

© SAP AG

E2E200

5-13

U sa ge of Proje c t s

Implementation Projects

Development

Test

Production

Implementation Project Market Campaign Complaint Management Rollout Brazil

Maintenance Project ERP … … Maintenance Cycles … Urgent Corrections

© SAP 2009

̈ ̈ ̈

Quality gate management bundles transport requests in projects. This has the following advantages: Comprehensive customizing and development activities are grouped together. Basis for release management

© SAP AG

E2E200

5-14

Solut ion M a nage r Proje c t Enhance d by the Proje c t Pha se s

Solution Manager Project
̈ ̈

Logical Components: DEV å QAS å PRD Project Documentation (Business Processes, Documentation, Testcases, …)

̈

NEW: Project Phases

Scope

Build

Test

Deploy

© SAP 2009

̈ ̈ ̈

SAP Solution Manager projects can be extended by adding project phases. Quality gate management projects have four phases: The Scope phase ensures that the tasks that are required for successful completion are performed in the project. You can verify the architecture and the technical prerequisites of the systems for your projects. The scope phase performs the following: • Document a functional or technical design • Document the requirements of departments • Evaluate technical realizability of the project

̈

̈

The scope phase begins at the Q-Gate "Project Start".

© SAP AG

E2E200

5-15

Proje c t Pha se s – Wha t H a ppens When?

Scope

Build

Test

Deploy

Create Changes Create Transports Release Changes Release Transports

Create Changes Create Transports Release Changes Release Transports Import Changes into test systems Import projects into test systems

Create Changes Create Transports Release Changes Release Transports Import Changes into test systems Import projects into test systems Import projects into production systems

© SAP 2009

̈

The Build phase is the actual development process. Transport requests are created and given development objects, in all systems in the project. The transports are imported into the subsequent systems together, to guarantee a correct function if the transport requests are functionally interdependent. The scope phase begins at the Q-Gate "Scope to Build". In the Test phase, projects, or changes to projects are imported and activated in the test systems. The previously defined test cases (for example, integration and user acceptance test) must be accepted by the test team. If there are errors in the test cases, you must make the corrections which are assigned to the development systems in new transport requests. The test phase begins at the "Build to Test" Q-Gate. Only the entire project, with all changes and corrections, can be imported into the Deploy phase. This ensures that all transport requests of a project are imported completely and in the correct sequence into the production systems. Project go live is the formal end, with the last Q-Gate. The deploy phase begins at the Q-Gate "Test to Deploy".

̈ ̈

̈ ̈

̈

© SAP AG

E2E200

5-16

T ra nsport Re st ric t ions via CT S Proje c t St a t us Sw it c he s
Quality Gate Management

Transport Landscape

Import into QAS possible

Import into PRD not possible

QAS

QAS

CTS Status Switch Import TR

PRD CTS Status Switch
Import TR

PRD

CTS Project Status Switches

© SAP 2009

̈ ̈ ̈

Imports into a system are only possible when the previous quality gate has been passed. Quality gate management uses the CTS project status switches to protect systems against imports. In this example, the quality gate “Build to Test” is passed. Therefore, imports into the QA system are possible. The quality gate “Test to Deploy” has not yet been passed. Therefore, imports into the PRD system are not possible.

© SAP AG

E2E200

5-17

T ype s of Projec t s U se d in Qua lit y Ga t e M a nagem ent
Physical (development) systems Logical systems (clients) Transport Request
CTS project

IMG project
SAP Solution Manager SAP Solution Manager project

CTS project CTS project

... IMG project
CTS project CTS project CTS project

...
© SAP 2009

...

̈ ̈

The Solution Manager project is represented as an IMG project in each satellite system and a CTS project in each satellite system client. Transport requests are only managed by the project. The project assignment of each transport request is mandatory.

© SAP AG

E2E200

5-18

Qua lity Ga t e s Be t w e e n t he Proje c t Pha se s

Scope

Build

Test

Deploy

Project Start

Scope to Build

Build to Test

Test to Deploy

Project Closure

© SAP 2009

̈ ̈

There is a quality gate between each phase that must be passed before the project can be switched into the next phase. In addition, there is a quality gate at the start and at the closure of the project. The names of the quality gates are: • Project Start • Scope to Build • Build to Test • Test to Deploy • Project Closure

© SAP AG

E2E200

5-19

Chec k list for Qua lit y Ga t e s Be st Pra c t ic e Re com me nda t ion
Scope
Q Gate
Requirements from business departments Functional and technical blueprint Functional and technical feasibility Scope to Build

Build
Extend Solution
̈SAP Updates ̈Custom Dev. ̈Partner solutions

Test
Q Gate Build to Test Execution of Functional and User Acceptance Tests Data Consistency Checks Performance Tests Incident & Problem Mgmt. and Root Cause Analysis Incident & Problem Mgmt. and Root Cause Analysis

Deploy
Q Gate Test to Deploy

Unit Tests Prepare Solution Operations
̈Solution Docu ̈Enablement of

Standards for Solution Operations Prepare Tests
̈Test Scope

Transports in Cycles

Final Transport

Identification

̈Test Requirements ̈Test System Setup ̈Test Planning

Handover to Production

Collaboration and Project Controlling
© SAP 2009

̈ ̈

The figure above shows SAP’s best practice recommendations on which information is to be available at the end of each project phase. In the quality gate it should be checked if all required information is available. Only in this case, the project can move forward into the next phase.

© SAP AG

E2E200

5-20

Qua lity Ga t e Proc e ss
Qua lit y Ga t e Ope n Qua lit y Ga t e Pa sse d

Build

Quality Gate

Test

Quality Gate Document Tester Quality Manager
̈ Document

Developer

Quality Steering Board

Operator

the Confirm / reject Quality Manager recommendation

results
̈ Upload

documentation
̈ Q-Gate

rating

̈ Quality

Gate Maintenance with SoD (Segregation of Duties)

SAP Solution Manager Project using Quality Gate Management
© SAP 2009

̈

The rating of the quality gates follows the four-eye principle. The quality gate must be rated as “Passed” or “Partially Passed” by the quality manager and by a member of the quality advisory board.

© SAP AG

E2E200

5-21

Ra t ing of Qua lit y Ga t e s

© SAP 2009

̈ ̈ ̈ ̈ ̈

You can edit data for the q-gate in the graphical, list, or project status view. In the graphical view, select a Q-Gate to open it. In the list view, put the cursor on a project and choose Open Q-Gate. In the list view, you can only open the currently active Q-Gate. In the project status view, putting the cursor on a Q-Gate activates the Q-Gate pushbutton. All views show information about the Q-Gate. Some fields are ready for input. You can upload, download or delete documents in the system, or enter issues, at the bottom of the screen.

© SAP AG

E2E200

5-22

Syste m De m o

Rating of Quality Gates

© SAP 2009

© SAP AG

E2E200

5-23

Qua lity Ga t e M a na ge m ent : U nit Ove rvie w Dia gra m
Quality Gate Management Lesson 1: Overview Lesson 2: Project Phases and Quality Gates Lesson 3: Central Transport Management Lesson 4: Creating new Projects Lesson 5: Prerequisites and Setup

© SAP 2009

© SAP AG

E2E200

5-24

Sync hroniza tion of Proje c t s Ac ross t he Landsc ape
Development Landscape
Development Environment Transport Landscape ERP Transport Landscape CRM Transport Landscape EP Transport Landscape BW Transport Landscape PI SE80 DS & DI SE80 DS & DI System

QA Landscape
System SAP ERP

Production Landscape
System SAP ERP

SAP ERP

SAP CRM

SAP CRM

SAP CRM

Portal Content Administrator DS & DI

Enterprise Portal

Enterprise Portal

Enterprise Portal

SE80

BW

BW

BW

SE 80 Integration Builder

Process Integration (XI)

Process Integration (XI)

Process Integration (XI)

Enhanced Change and Transport System CTS+
© SAP 2009

Quality Gate Management

SAP Solution Manager

̈

In this example, the Solution Manager project comprises several SAP systems. The systems have dependent transports. All transports for the whole solution are bundled under the umbrella of the Solution Manager project. When the project goes live, all transport requests that belong to the same Solution Manager project are imported at the same time. So all dependencies are considered automatically.

© SAP AG

E2E200

5-25

Solut ion T ra nsport s a nd T ra ck Synchroniza t ion
SAP Solution Manager Change Control
SAP Solution Manager Project
CT S Proje c t Change 1
Transport Request Transport Request

SAP Enterprise Portal

SAP ECC

CT S Proje c t

1 2
Transport Request Transport Request

Change 2

3 4

Change 3

Transport Request

5
Transport Request

6

© SAP 2009

© SAP AG

E2E200

5-26

Ex a mple : Port a l iV ie w U se s BI We bre port

SAP Portal
iView with reference to BI Webreport

SAP BI
BI Webreport

SAP ERP
Data Element

EPDK901024
̈

BWDK910095
̈

ERDK923362
̈

iView

BI Webreport

Data Element

Example:
̈ ̈ ̈

An iView uses a BI Web report. The Webreport is based on an additional data element in the ERP backend. All three changes must be transported at the same time into the test and production environments.

© SAP 2009

© SAP AG

E2E200

5-27

Qua lity Ga t e M a na ge m ent Role s and Proce ss Flow
Transport Manager
̈ ̈ ̈

Creating Changes Creating Transport Requests Notify Developers Developers / Content Creators in Application
̈ ̈ ̈

Working within Application Recording Objects in Transport Requests Releasing Tasks

Transport Manager
̈ ̈

Releasing Transport Requests Releasing Changes

Quality Manager / Quality Advisory Board
̈ ̈

Controlling QA activities Rating of Quality Gates

© SAP 2009

̈ ̈ ̈

In principle, three roles can be identified in the process of using quality gate management: A transport manager is responsible for creating changes and transport requests and starting imports. The developer or content creator creates new stuff for the application – for example, new iViews and pages within the portal. He or she has to take care that all the objects needed for a new feature are part of a transport request. The quality manager and the quality advisory board have to make sure that certain quality criteria are met at the end of a project phase. If these criteria are met, the quality gate can be set to “Passed”.

̈

© SAP AG

E2E200

5-28

Syste m De m o

Central Transport Management

© SAP 2009

© SAP AG

E2E200

5-29

Qua lity Ga t e M a na ge m ent Full I nt egra t ion of CT S+
CTS+ enables quality gate management to support the whole business process platform.

One central Transport Tool Multiple Types of Backends
SAP NetWeaver SAP NetWeaver SAP NetWeaver AS ABAP AS ABAP AS ABAP

Enhanced CTS

ESR/PI/XI XI/PI System XI/PI System System
on SAP NetWeaver (Dual Stack)

Portal System
on SAP NetWeaver AS Java

SAP NetWeaver SAP NetWeaver AS Java AS Java on SAP NetWeaver AS Java

NW DI

... ... ...

Multiple Development Workbenches

...

© SAP 2009

̈

Enhanced CTS allows you to transport objects created in other languages than ABAP by using the Change and Transport System of ABAP. The goal is to have one Transport Tool (CTS) which supports all workbenches and applications when it comes to transports. The tools for creating applications and creating content remain the same. Options to attach applications or content to a CTS transport request are integrated into the different workbenches. The level of integration is different for different workbenches. This is explained in detail on the following slides. Enhanced CTS aims for a unified single transport tool which simplifies the live of an administrator who is responsible for performing imports. He or she has to access only one tool to start imports for very different backends. Deployment tools are called automatically. It is very easy to monitor what has already been imported and whether the import went well. The queues in CTS provide a good overview on what needs to be imported.

© SAP AG

E2E200

5-30

Proc e ss Flow for N on-ABAP Environm ent s 1 /2

Quality Gate Management

Transport Manager

Transport Organizer Web UI

Developer

Quality Gate Management

Transport Manager

Create Change

Preselect standard transport request that belongs to the change request

Release transport request

Quality Gate Management

Transport Manager

Non-ABAP development environment

Developer

Quality Gate Management

Transport Manager

Create Transport Request

Perform development change

Import transport request into the Quality Assurance System

Non-ABAP development environment

Developer

Attach change to transport request

© SAP 2009

̈ ̈

For non-ABAP environments there is an additional step “Preselect transport request“ that must be done by the developer. In non-ABAP environments the transport request must be selected in a separate step, before objects can be attached to it. This is different from ABAP environments, where the system asks you if several transport requests are available. All other steps of the quality gate management process are identical for ABAP and non-ABAP environments.

̈

© SAP AG

E2E200

5-31

Proc e ss Flow for N on-ABAP Environm ent s 2 /2
Create transport request in quality gate management Preselect transport request in the Transport Organizer Web UI

2

1
Attach non-ABAP object to transport request in the non-ABAP development environment

Release transport request in quality gate management

3 4
© SAP 2009

5

̈ ̈ ̈ ̈ ̈

1. Quality gate management: create workbench request 2. Non-ABAP development envrionment: Perform the change and go to the export wizard. From there you can jump into the Transport Organizer Web UI 3. Transport Organizer Web UI: Preselect the request that belongs to your change document as standard request 4. Non-ABAP development environment: In the export wizard, attach the archive with the change to the preselected request 5. Quality gate management: release transport request

© SAP AG

E2E200

5-32

Qua lity Ga t e M a na ge m ent : U nit Ove rvie w Dia gra m
Quality Gate Management Lesson 1: Overview Lesson 2: Project Phases and Quality Gates Lesson 3: Central Transport Management Lesson 4: Creating new Projects Lesson 5: Prerequisites and Setup

© SAP 2009

© SAP AG

E2E200

5-33

Cre a t e N e w Proje c t

Project Administration – SAP Solution Manager
Check: Logical component assigned to SAP Solution Manager project Assign all your systems to system roles

© SAP 2009

© SAP AG

E2E200

5-34

Ac t iva te I M G Proje c t

Project Administration – SAP Solution Manager
Check: IMG project assigned to SAP Solution Manager project If status red: Create IMG project using the button below

© SAP 2009

© SAP AG

E2E200

5-35

M a inta in Proje c t

Change Management Workcenter SAP Solution Manager
Choose Projects on the left Choose your Solution Manager project and maintain it The guided procedure will be opened

© SAP 2009

̈

Choose Maintain Project in the graphical or list view. You go to a window in which you perform the steps required to set up a project in the quality gate management.

© SAP AG

E2E200

5-36

De fine Q-Ga t e s a nd M ile st one s

Change Management Workcenter SAP Solution Manager
Guided Procedure Step 1:
̈ ̈

Define quality manager and quality advisory board member Define milestones, planned start and additional Q-Gates

© SAP 2009

̈

Specify the Q-Gate and milestone data. Proceed as follows: • Enter the name of the quality manager and the person responsible from the quality advisory board, at the top. • To specify your own milestones as Q-Gates, choose Add Milestone, enter a name for the milestone, and set the flag in the Q-Gate column. • Enter the planned deadlines for all Q-Gates and milestones.

̈ ̈

You can upload template documents for Q-Gates. Select the row of the Q-Gate and choose Upload Template. The system administrator uploads the template documents into the system. These are templates for the project team members who can edit them by downloading them into the Open Q-Gate window, and then upload them again.

© SAP AG

E2E200

5-37

Chec k T ransport La ndsca pe

Change Management Workcenter SAP Solution Manager
Guided Procedure Step 2:
̈

Check the logical component. If the TMS check is red, check the logical component and the CTS transport routes. See also Application Log (SLG1).

© SAP 2009

̈ ̈

Display system transport landscape check: The logical components that you use in your project are at the top. If you select a row, the system shows the system information (system/client/system role) of the logical component, at the bottom of the screen. Only logical components which have been assigned to the project in the project administration (transaction SOLAR_PROJECT_ADMIN) are shown. The TMS Check column indicates whether a logical component for the TMS has been configured correctly. Green = correct, red = incorrect. Select the logical components that you wish to use in the quality gate management, in the Use in Project column.

̈ ̈ ̈

© SAP AG

E2E200

5-38

Assign Q-Ga t e s t o Syst e m Role s

Change Management Workcenter SAP Solution Manager
Guided Procedure Step 3:
̈

Assign Q-Gates to system roles

© SAP 2009

̈ ̈ ̈

Assign or change system roles for Q-Gates. The phase is shown in the third column. You specify which Q-Gate is to be passed for which system. The project phases are shown, depending on the assignment to the Q-Gates, in the Phase column. You can only assign each Q-Gate once.

© SAP AG

E2E200

5-39

Chec k Configura t ion

Change Management Workcenter SAP Solution Manager
Guided Procedure Step 4:
̈ ̈

Check configuration and confirm data Ready to use quality gate management

© SAP 2009

̈

Finally, your project can be used in quality gate management.

© SAP AG

E2E200

5-40

Fle x ible Se t up of Adva nc ed T ra nsport Landsc ape s
Logical Components:
̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈

EB1:100 å QG1:100 å PB1:100 EB1:100 å QG1:200 EB1:100 å QG1:300 EB1:100 å QG1:400 EB1:100 å QG1:500 EB1:100 å QG1:600 EB1:100 å QG1:700 EB1:100 å QG1:800 EB1:100 å QG1:900

© SAP 2009

̈ ̈ ̈ ̈

Quality gates can flexibly be assigned to systems and project phases. If a quality gate is assigned to a system this means that imports into that system are possible after the quality gate has been passed. If a quality gate is assigned to a project phase this means that this project phase starts at the latest when the quality gate has been passed. Additional quality gates can be defined. However, the project phases are fixed.

© SAP AG

E2E200

5-41

Syste m De m o

Create a New Project

© SAP 2009

© SAP AG

E2E200

5-42

Qua lity Ga t e M a na ge m ent : U nit Ove rvie w Dia gra m
Quality Gate Management Lesson 1: Overview Lesson 2: Project Phases and Quality Gates Lesson 3: Central Transport Management Lesson 4: Creating new Projects Lesson 5: Prerequisites and Setup

© SAP 2009

© SAP AG

E2E200

5-43

Re quire d CT S Se t t ings

Check or create transport routes between DEV å QAS å PRD If necessary, create a domain link between the SAP Solution Manager domain and the target system domain. Required Transport Parameters
̈ ̈ ̈ ̈ ̈

CTC = 1 (for ABAP and Double Stack Systems only) Import_Single_Only=1 Import_Single_Strategy=1 No_Import_All=1 Worklow_Strategy=0

© SAP 2009

̈

For more information, refer to the online documentation at http://help.sap.com å SAP NetWeaver 7.1 (or below) å SAP NetWeaver Library å SAP NetWeaver Key Capability å Software Lifecycle Management å Software Logistics å Change and Transport System

© SAP AG

E2E200

5-44

Re quire d CT S Se t t ings for N on-ABAP Syst e m s

Required Transport Parameters for for the Transport Organizer
̈ ̈

WBO_GET_REQ_Strategy: TAGGED (only for exclusive Q-Gate Management usage) WBO_REL_REQ_Strategy: MANUAL

Required Transport Parameters for JAVA standalone systems
̈ ̈

CTC = 0 CTS_SYSTEM_TYPE = JAVA

© SAP 2009

̈

For more information, refer to the online documentation at http://help.sap.com/ å SAP NetWeaver 7.1 (or below) å SAP NetWeaver Library å SAP NetWeaver Key Capability å Software Lifecycle Management å Software Logistics å Change and Transport System

© SAP AG

E2E200

5-45

Pa ra m e te r CT S_SY ST EM _T Y PE for Single J AVA St a c k s

1

Set transport parameter CTS_SYSTEM_TYPE = JAVA

2

After a landscape fetch the communication system will appear in SMSY.

3
© SAP 2009

An IMG project can be created for the JAVA system in the communication system.

̈ ̈ ̈

For single Java stacks the transport parameter CTS_SYSTEM_TYPE = JAVA must be set. After a landscape fetch, the CTS+ communication system will appear in SMSY. In transaction SOLAR_PROJECT_ADMIN an IMG project can now be created for the Non-ABAP system in the CTS+ communication system.

© SAP AG

E2E200

5-46

Role s and Aut horiza t ions

User Roles
̈ ̈ ̈ ̈

Quality Gate Superuser (Role 1) Quality Manager (Role 2) User for Quality Gate Mgmt. Transport Activities (Role 3) Quality Advisory Board Member (Role 4)

Required authorizations
̈ ̈ ̈ ̈

Role 1: SAP_SM_QGM_ALL Role 2: SAP_SM_QGM_STATUS_QM Role 3: SAP_SM_QGM_TRANSPORT Role 4: SAP_SM_QGM_STATUS_QAB

© SAP 2009

© SAP AG

E2E200

5-47

U se rs in Sa te llit e Syst e m s: Clie nt -Spe c ific T ra nsport Authoriza t ion Chec k s
Quality gate management uses the import functions of the Transport Management System (TMS). The TMS remote infrastructure is based on RFC connections that point solely to the 000 client of a target system. Operators and administrators who are responsible for the import must have users:
̈ ̈

In the client into which changes are imported In the 000 client of these systems

Task Create Request Release Request Import Request

Target Client SOLTMW<SID><CLI> (backgrounduser) SOLTMW<SID><CLI> (backgrounduser) Trusted RFC (User needs Import Authorization)

Client 000

Trusted RFC (User needs Import Authorization)

© SAP 2009

̈ SOLTMW<SID><CLI> (backgrounduser)

© SAP AG

E2E200

5-48

Solut ion M a nage r Syst e m Landsc ape (SM SY )

System Landscape – SAP Solution Manager
̈ ̈

Check or create Server, Database, Systems (T-Code SMSY) Check or create RFC Destinations (RFC Read Access, Trusted System RFC)

© SAP 2009

© SAP AG

E2E200

5-49

Logic a l Com pone nt s

System Landscape – SAP Solution Manager
Check or create logical component
̈ ̈

Managed systems assigned to system roles (managed systems) Note: Logical component and CTS transport routes must be identical.

© SAP 2009

© SAP AG

E2E200

5-50

Ex e rc ise

Quality Gate Management

© SAP 2009

© SAP AG

E2E200

5-51

Qua lity Ga t e M a na ge m ent : U nit Sum m a ry

You should now be able to:
̈ ̈ ̈ ̈ ̈

Explain the concept of solution transports and track synchronization Describe the project phases in quality gate management Describe the tasks of a quality manager in different phases of an implementation project Create and release transport requests centrally in SAP Solution Manager for ABAP and non-ABAP environments Set up and use quality gate management as a central transport management tool

© SAP 2009

© SAP AG

E2E200

5-52

Exercises
Unit: Lesson: Quality Gate Management Creating New Projects

At the conclusion of this exercise, you will be able to: • Activate quality gate management for a new SAP Solution Manager implementation project

You want to customize transaction CAT2 in the back end and create an iView for time recording in the portal. Both transport requests must be transported synchronously.

5-1

Activate quality gate management for your implementation project, E2ECC_##. 5-1-1 Log on to SAP Solution Manager with your user, E2ECC-## (change ## to your group number). Navigate to the Change Management work center and choose the Projects tab. In the List view of the details area, select the project that you created. Make sure to choose your Solution Manager project and not your IMG project!. Set up quality gate management for your project by pressing the Maintain Project button. The Define Q-Gates and Milestones dialog box appears. Enter the Quality Manager and the member of the Quality Advisory Board. Choose your user for the Quality Manager and your neighbor’s user for the member of the Quality Advisory Board. Alternatively, you can enter the instructor’s user, E2ECC-00. Enter the planned start date for each project phase. When you have entered all dates, choose the Next button. 5-1-4 In the Check Transport Landscape screen, you see the logical components of your project. Make sure that only the logical components Z_EP_CCM and Z_ERP_CCM are included in quality gate management. If other logical components occur, deselect them. Choose the Next button.

5-1-2 5-1-3

© SAP AG

E2E200

5-53

5-1-5

Assign each Q-Gate to the system role and phase that should be used when the Q-Gate is passed. Make the following assignments. Q-Gate Start of Project Scope to Build Build to Test Test to Deploy System Role Evaluation System Development System Quality Assurance System Production System Retrofit System Choose the Next button and then choose Save &Exit. Remark: You can only activate Quality Gate Management successfully, if you have completed the exercise on Solution Documentation at least to exercise number 4-2-4 (creation of IMG projects). Phase Scope Build Test Deploy Deploy

© SAP AG

E2E200

5-54

Exercises
Unit: Lesson: Quality Gate Management Project Phases and Quality Gates

At the conclusion of this exercise, you will be able to: • Rate quality gates • Upload documents into the quality gates

TT4 is the Solution Manger system that contains all information about the system landscape. Z_ERP_CCM and Z_EP_CCM are logical components that describe transport landscapes for an SAP ECC system and a portal.

5-2

Rate the Start of Project and Scope to Build quality gates. 5-2-1 5-2-2 5-2-3 5-2-4 Open the Start of Project quality gate and set Status set by: Quality Manager to Passed. Your neighbor acts as a member of the Quality Advisory Board. Ask him or her to set the Status set by: Quality Advisory Board to Passed. What is the current phase of your project? Repeat the steps that were described for the Start of Project quality gate for the next quality gate, Scope to Build. Note: Alternatively, you can navigate to the Scope to Build quality gate from the Project Status tab. Select the first quality gate and choose Open Q-Gate. 5-2-5 Go to the Project Status tab and check your project.

© SAP AG

E2E200

5-55

Exercises
Unit: Lesson: Quality Gate Management Central Transport Management

At the conclusion of this exercise, you will be able to: • Create and release changes in quality gate management • Create and release transport requests in quality gate management • Trigger imports in quality gate management

TT4 is the Solution Manger system that contains all information about the system landscape. Z_ERP_CCM and Z_EP_CCM are logical components that describe transport landscapes for an SAP ECC system and a portal.

5-3

Create a change with a transport request in the ERP back end and a related transport request in the portal. 5-3-1 In the List view, create a change. Enter the description “Solution Transport Portal-ERP.” Write down the number of the change. Change number: ______________________________________________ 5-3-2 Within your change, create a transport request of type Customizing for the ERP back end. Enter the short text “Solution Transport Portal-ERP / Time Rec.” Write down the transport request. ERP transport request: ________________________________________ 5-3-3 Within your change, create a transport request of type Workbench for the portal. Enter the short text “Solution Transport Portal-ERP / Time Rec.” Write down the transport request. Portal transport request: _______________________________________

5-4

Perform a customizing change for transaction CAT2 in the ERP back end. 5-4-1 Navigate to the customizing activity that you assigned to your implementation project for the step Record working times in backend. In SAP Solution Manager, call transaction SOLAR02 and select your implementation project. Navigate to the business process step Record working times in backend and select the Configuration tab. Double-click on the IMG object PCUI_ESS_CATS_004.

© SAP AG

E2E200

5-56

Which system is assigned to the customizing activity? Answer: __________________________________________________ What is the transaction code of the customizing activity? Answer: __________________________________________________ 5-4-2 Start the customizing activity Define Field Selection. In the customizing transaction, select Data entry section and choose Influencing.

5-4-3

In the next screen, select entry Z_E2E_## (## = your group number) and press Enter. Customize the visible fields for data entry in transaction CAT2. Add the additional fields Accounting Indicator, Activity Number, and Activity Type (change the first three entry from Hide to Input).

Save the changes in your customizing request. 5-4-4 Go to transaction SE09 and release the task of your customizing request in the development client, TT5-801. In transaction SE09, select all modifiable customizing requests for your user. If there are several, look at the short text to find the one that you created. Navigate to the transport request and put the cursor on the task below the transport request. Choose the Release button to release the task. Note: You are not authorized to release the transport request itself from transaction SE09. This must be done in the Quality Gate application.

© SAP AG

E2E200

5-57

5-5 Perform a portal change. Create a role, workset, and iView for the Time Recording activity. 5-5-1 5-5-2 Log on to the portal and navigate to the Transport Organizer Web UI. Preselect the transport request that you created for the portal. Go to the Transport Package Editor and select the transport package that you created before in the CTS+ exercise. The name should be: Transport_Package_User_##. (## is your group number). Export the transport package to the transport request that you have created in the Quality Gate Management. Which export method is preselected? ______________________________ Which transport request is preselected? ____________________________ Remark: The transport request contains the Time Recording workset. This was created in a previous exercise; therefore, it is already available. Optionally, you can repeat the preparation steps of exercise 3-6-1 to delete the object again. It will re-appear when the transport request is imported. 5-6 Release the transport requests in quality gate management. 5-6-1 5-6-2 5-7 Release the portal transport request that belongs to your change. Release the ERP transport request that belongs to your change.

5-5-3

Rate the Build to Test quality gate. 5-7-1 5-7-2 Open the Build to Test quality gate and set the Status set by: Quality Manager to Passed. Your neighbor acts as a member of the Quality Advisory Board. Ask him or her to set the Status set by: Quality Advisory Board to Passed.

5-8

Import the transport requests into the test systems. 5-8-1 Import the transport request for the portal into the test portal. 5-8-2 Log on to the portal and check the fields of the Time Recording application. Which fields are available? Answer: _____________________________________________________ 5-8-3 In quality gate management, go to the Risks tab and check the status of your change. Which risk is displayed? Answer: _____________________________________________________ 5-8-4 Import the transport request for the ERP back end. 5-8-5 In the portal, check again the fields in the Time Recording application. Logon again to the portal or press the Refresh button of your browser. Which fields are available after the import of the ERP transport? Answer: _____________________________________________________

5-8-6
© SAP AG E2E200 5-58

Solutions
Unit: Lesson: Quality Gate Management Creating New Projects

5-1

Activate quality gate management for your implementation project, E2ECC_##. 5-1-1 Log on to SAP Solution Manager with your user, E2ECC-## (change ## to your group number). Navigate to the Change Management work center and choose the Projects tab. In the User menu, select WDY_APPLICATION Work Center.

Then select the Change Management work center and the Projects tab.

5-1-2 In the List View of the details area, select the project that you created. Make sure to choose your Solution Manager project and not your IMG project!

© SAP AG

E2E200

5-59

5-1-3

Set up quality gate management for your project by pressing the Maintain Project button. The Define Q-Gates and Milestones dialog box appears. Enter the Quality Manager and the member of the Quality Advisory Board. Choose your user for the Quality Manager and your neighbor’s user for the member of the Quality Advisory Board. Alternatively, you can enter the instructor’s user, E2ECC-00. Enter the planned start date for each project phase. When you have entered all dates, choose the Next button. After you have finished, your input the screen should look like this:

5-1-4

In the Check Transport Landscape screen, you see the logical components of your project. Make sure that only the logical components Z_EP_CCM and Z_ERP_CCM are included in quality gate management. If other logical components occur, deselect them. Choose the Next button. Assign each Q-Gate to the system role and phase that should be used after the Q-Gate is passed. Make the following assignments. Q-Gate Start of Project Scope to Build Build to Test Test to Deploy System Role Evaluation System Development System Quality Assurance System Production System Retrofit System Phase Scope Build Test Deploy Deploy
5-60

5-1-5

© SAP AG

E2E200

Choose the Next button and then choose Save &Exit. You should now see the following screen. The transport routes indicate that the TMS and the logical components are consistent.

Choose Save & Exit. Quality gate management is now activated for your implementation project. Remark: You can only activate Quality Gate Management successfully, if you have completed the exercise on Solution Documentation at least to exercise number 4-2-4 (creation of IMG projects).

© SAP AG

E2E200

5-61

Solutions
Unit: Lesson: Quality Gate Management Project Phases and Quality Gates

5-2

Rate the quality gates Start of Project and Scope to Build. 5-2-1 Open the Start of Project quality gate and set Status set by: Quality Manager to Passed. In the list view, choose the Open Q-Gate button and set the Status set by: Quality Manager to Passed. 5-2-2 Your neighbor acts as a member of the Quality Advisory Board. Ask him or her to set the Status set by: Quality Advisory Board to Passed. In the List view, choose Open Q-Gate and set the Status set by: Quality Advisory Board to Passed. Confirm the dialog box. 5-2-3 What is the current phase of your project? In the List view, choose the Refresh button in the project grid and check the entry in the Current Phase column. Your project should now be in the Scope phase. 5-2-4 Repeat the steps that were described for the Start of Project quality gate for the next quality gate, Scope to Build. Note: Alternatively you can navigate to the Scope to Build quality gate from the Project Status tab. Select the first quality gate and choose Open Q-Gate. 5-2-5 Go to the Project Status tab and check your project. The project should look like this

© SAP AG

E2E200

5-62

Solutions
Unit: Lesson: Quality Gate Management Central Transport Management

5-3 Create a change with a transport request in the ERP back end and a related transport request in the portal. 5-3-1 In the List view, create a change. Enter the description “Solution Transport Portal-ERP”. Write down the number of the change. Change Number: ________________________________________ Go to the List View. In the Changes tab, choose Create Change and enter the description.

5-3-2

Within your change, create a transport request of type Customizing for the ERP back end. Enter the short text “Solution Transport Portal-ERP / Time Rec.” Write down the transport request. In the Transport Requests for Change tab, choose Create Transport Request. Select a customizing request for system TT5801. Enter the short text.

5-3-3

Within your change, create a transport request of type Workbench for the portal. Enter the short text “Solution Transport Portal-ERP / Time Rec.” Write down the transport request. In the Transport Requests for Change tab, choose Create Transport Request. Select a workbench request for system JAD. Enter the short text.

5-4

Perform a customizing change for transaction CAT2 in the ERP back end. 5-4-1 Navigate to the customizing activity that you assigned to your implementation project for the step Record working times in backend. In SAP Solution Manager, call transaction SOLAR02 and select your implementation project. Navigate to the business process step Record working times in backend and select the Configuration tab. Double-click on the IMG object PCUI_ESS_CATS_004. Which system is assigned to the customizing activity? Answer: The system is TT5-801 What is the transaction code of the customizing activity? Answer: The transaction code is CAC2.

© SAP AG

E2E200

5-63

5-4-2

Start the customizing activity Define Field Selection. In the customizing transaction, select Data entry section and choose Influencing.

5-4-4

In the next screen, select entry Z_E2E_## (## = your group number) and press Enter. Customize the visible fields for data entry in transaction CAT2. Add the additional fields Accounting Indicator, Activity Number, and Activity Type (change the first three entry from Hide to Input).

Save the changes in your customizing request. 5-4-4 Go to transaction SE09 and release the task of your customizing request in the development client, TT5-801. In transaction SE09, select all modifiable customizing requests for your user. If there are several, look at the short text to find the one that you created. Navigate to the transport request and put the cursor on the task below the transport request. Choose the Release button to release the task. Note: You are not authorized to release the transport request itself from transaction SE09. This must be done in the Quality Gate application.

5-5 Perform a portal change. Create a role, workset, and iView for the Time Recording activity. 5-5-1 Log on to the portal and navigate to the Transport Organizer Web UI. Preselect the transport request that you created for the portal. Log on to the portal via the link http://<hostname>.wdf.sap.corp:55000/irj/portal with your user, E2ECC<##>. Select the Transport Management tab and the Transport Organizer page. Preselect the transport request you have created in the Quality Gate Management.
© SAP AG E2E200 5-64

5-5-2

Go to the Transport Package Editor and select the transport package that you created before in the CTS+ exercise. The name should be: Transport_Package_User_## (## is your group number). In the System Administration tab, choose Transport å Transport Packages å Export. Go to Browse the Portal Catalog and open Portal Content.

Select your transport package Transport_Package_User_##.

© SAP AG

E2E200

5-65

5-5-3

Export the transport package to the transport request that you created in the Quality Gate Management. Double-click on your transport package to open it.

Which export method is preselected? Answer: The export method CTS is preselected. Which transport request is preselected? Answer: The transport request that you created should be preselected. Choose Start Export. If the export was successful, you will receive status information that the selected transport package was added to the related transport request. Note: The transport request contains the Time Recording workset. This was created in a previous exercise; therefore, it is already available. Optionally, you can repeat the steps of exercise 3-6-1 to delete the object again. It will reappear when the transport request is imported again.

© SAP AG

E2E200

5-66

5-6

Release the transport requests in quality gate management. 5-6-1 Release the portal transport request that belongs to your change. In the work center, select your project and your change. Then select the portal transport request and choose Release Transport Requests.

5-6-2

Release the ERP transport request that belongs to your change. Select the related ERP transport request and choose Release Transport Requests.

5-7

Rate the Build to Test quality gate. 5-7-1 Open the Build to Test quality gate and set the Status set by: Quality Manager to Passed. In the Project Status view, select the Build to Test Q-Gate and choose Open Q-Gate. Set the Status set by: Quality Manager to Passed. 5-7-2 Your neighbor acts as a member of the Quality Advisory Board. Ask him or her to set the Status set by: Quality Advisory Board to Passed. In the Project Status view, select the Build to Test Q-Gate and choose Open Q-Gate. Set the Status set by: Quality Advisory Board to Passed. Confirm the dialog box. In the Project Status tab, your project should now look like this:

© SAP AG

E2E200

5-67

5-8

Import the transport requests into the test systems. 5-8-1 Import the transport request for the portal into the test portal. In the List View of your Quality Gate Management project, mark your change in the Changes tab. Then click on the button Start Import. On the next popup, select the CTS project TT4_P000## and mark the transport request for the portal. Click on OK to import the transport request immediately into the portal system JAQ. 5-8-2 Log on to the portal and check the fields of the Time Recording application. Which fields are available? Log on to the portal. Navigate to your newly created role, Role_User_##, and then to the Working Time workset. Select the Record Working Time iView and check the fields.

The fields Att./abs. type and Total should be available. 5-8-3 In quality gate management, go to the Risks tab and check the status of your change. Which risk is displayed? Answer: The risk is Missing Synchronization.

© SAP AG

E2E200

5-68

5-8-4

Import the transport request for the ERP back end. In the List View of your Quality Gate Management project, mark your change in the Changes tab. Then click on the button Start Import. On the next popup, select the CTS project TT5_P000## and mark the transport request for the ERP backend. Click on OK to import the transport request immediately into the client TT5-802.

5-8-5

In the portal, check again the fields in the Time Recording application. Logon again to the portal or press the Refresh button of your browser. Which fields are available after the import of the ERP transport? Navigate to your newly created role, Role_User_##, and then to the Working Time workset. Choose the Record Working Time iView and check the fields. Compare the fields before and after you import the transport request in the ERP system.

You should now see the additional input fields Activity Number, Activity Type and Accounting Indicator, that you have customized before in transaction CAC2.

© SAP AG

E2E200

5-69

© SAP AG

E2E200

5-70

Change Reque st Ma na ge m ent

Unit 1 Introduction to E2E Change Control Management Unit 2 Software Change Strategies Unit 3 Enhanced Change and Transport System Unit 4 Solution Documentation Unit 5 Quality Gate Management Unit 6 Change Request Management Unit 7 Maintenance Management Unit 8 Test Management Unit 9 Change Diagnostics

© SAP 2009

© SAP AG

E2E200

6-1

Change Reque st M a na ge m ent : U nit Obje c t ive s

At the end of this unit, you will be able to:
̈ ̈ ̈ ̈

Define the Change Request Management business process Explain how to use the SAP Solution Manager system for the Change Request Management scenario Describe the various elements of Change Request Management as part of SAP Solution Manager Describe SAP’s best practices in transport management which are implemented in the SAP Solution Manager

© SAP 2009

© SAP AG

E2E200

6-2

Change Reque st Ma na ge m ent : U nit Ove rvie w Dia gra m
Change Request Management Lesson 1: Change Request Management Overview Lesson 2: Project and Release Management Lesson 3: Change Requests Lesson 4: Maintenance Activities Lesson 5: Integration of Non-ABAP Systems Lesson 6: Tools Lesson 7: Best Practices

© SAP 2009

© SAP AG

E2E200

6-3

St ory Line : Change Reque st M a nage m ent

Change Request Management supports the complete end-to-end change process, from the requirements to the productive implementation. It provides a workflow for the organizational change processes and is fully integrated into the Change and Transport System. Using Change Request Management, you may expect the following:
̈ ̈ ̈ ̈

Each change has to be approved before development starts. No untested changes go into production. Each change is completely documented. Changes are bundled in maintenance cycles and releases, based on SAP’s best practices.

© SAP 2009

© SAP AG

E2E200

6-4

I T I L Change M a na ge m ent Proc e ss

Create RfC
Rejected: New RfC

Configuration Management processes the data and controls the status of the CIs

Accept: Filter RfC Classify: Category and Priority Urgent?
no yes

Plan: Impact und Resources Coordinate Develop Test Implement Control
yes no Correct

Evaluate and close
© SAP 2009

̈

What is ITIL®? • Acronym for the "IT Infrastructure Library" guidelines developed for the British government • De-facto global standard in the area of service management • Contains comprehensive, publicly accessible documentation on the planning, provision and support of IT services • Provides the basis for improving the use and effect of an operationally deployed IT infrastructure • Describes the architecture for establishing and operating IT service management • The ITIL books are best practice guidelines for service management, with the guidelines describing what rather than how. Service management is tailored to the size, the internal culture and, above all, the requirements of the company. The impartial view of the external consultant may help to break away from the rigid structures.

© SAP AG

E2E200

Fallback

Urgent Correction

6-5

T hre e Area s of Change Reque st M a na gem e nt

SAP Solution Manager
Change Admin
̈

Project Management
̈

Change Admin
̈

Management of all change requests Change request categorization Change documentation Approval workflow

Project administration Project documentation Customizing & development (specifications) Test management

Customizing & development (realization) Workbench Organizer Transport Management Transport scheduling Transport tracking

̈

̈

̈

̈

̈

̈

̈ ̈ ̈

̈

̈

Status reporting Complete change history
̈

© SAP 2009

© SAP AG

E2E200

6-6

Change Reque st Ma na ge m ent Role s and Re sponsibilit ie s
Requestor

… creates a service message or a change request directly. … handles the service message and creates a change request. … categorizes, approves, and monitors change requests.

Service Desk Employee Change Manager Change Advisory Board Developer

… is the steering committee in the change management process.

… implements a change and hands over to the tester. … tests a change, sets status in the change document.

Tester

IT Operator
© SAP 2009

… takes care of software logistics.

̈

Responsibilities: • Requestor: To describe the change required in detail. To identify the priority of the request and describe why the capability is needed, and to identify the impact if the desired capability is not provided. • Service Desk Employee: To act as the central point of contact between the User and IT Service Management. To handle Incidents and requests, and provide an interface for other activities, such as Change, Problem, Configuration, Release, Service Level, and IT Service Continuity Management. • Change Manager: - To ensure that standardized methods and procedures are used for efficient and prompt handling of all changes, in order to minimize the impact of any related incidents on service. - To accept or reject change requests. - To monitor the Change Management process. - To release changes for production. • Developer: To implement and document a change in the development system, to provide adequate test cases or update existing ones. • Tester: To follow instructions in the relevant test cases and make sure that the change has been promoted correctly into the consolidation environment. If a change causes incidents in the consolidation environment, it is the tester’s duty to set the change back into development. • IT Operator: To provide support if the Change Management process is impeded in any way. To import the change into the production environment.

© SAP AG

E2E200

6-7

I m port a nt Role : Cha nge Ma na ge r

Responsibility:
To ensure that standardized methods and procedures are used for efficient and prompt handling of all changes, in order to minimize the impact of any related incidents upon service. To accept, or reject change requests. To monitor the Change Management process. To release changes for production.

© SAP 2009

© SAP AG

E2E200

6-8

I m port a nt Role : Cha nge Advisory Boa rd

Responsibility:
The Change Advisory Board (CAB) considers change requests, and in the light of the business need makes recommendations as to whether they should be accepted and implemented or rejected. Recommendations are based upon the impact on existing services, the cost of change, and other relevant factors. The CAB members are chosen to ensure all changes can be adequately assessed from both the business and technical viewpoint. The CAB members are likely to include: Change manager, chairing the process Relevant IT staff ̈ Suppliers, maintainers, and developers ̈ Customers and users ̈ Office services and other non-IT supporting services ̈ Experts/technical consultants
̈ ̈

© SAP 2009

© SAP AG

E2E200

6-9

Foc us of Change Re que st M a na ge m ent and Qua lity Ga t e M a na ge m ent
Change Request Management
Process control - Detailed documentation for single changes of objects and processors Quality assurance, workflow and risk analysis for single changes (segregation of duties) Enhanced Change and Transport System (CTS+) fully integrated

Quality Gate Management
Activity / Event driven Documentation on project level and technical tracking of changes Quality assurance, workflow and risk analysis for projects (Segregation of duties)

Focus

Level of control

Transport Management

Enhanced Change and Transport System (CTS+) fully integrated

Impact on customer organization

Complete process control

Complete gate control

Affected roles

Requestor, change manager, developer, tester, system administrator

Quality manager, system administrator

© SAP 2009

© SAP AG

E2E200

6-10

Change Reque st Ma na ge m ent : U nit Ove rvie w Dia gra m
Change Request Management Lesson 1: Change Request Management Overview Lesson 2: Project and Release Management Lesson 3: Change Requests Lesson 4: Maintenance Activities Lesson 5: Integration of Non-ABAP Systems Lesson 6: Tools Lesson 7: Best Practices

© SAP 2009

© SAP AG

E2E200

6-11

U sa ge of Proje c t s

Implementation Projects

Development

Test

Production

Implementation Project Market Campaign Complaint Management Rollout Brazil

Maintenance Project ERP … Maintenance Cycles … Urgent Corrections

© SAP 2009

̈

Advantages: • Comprehensive customizing and development activities are grouped together. • Basis for release management

© SAP AG

E2E200

6-12

Solut ion M a nage r Proje c t I s Enha nc ed by t he Proje c t Cyc le

Solution Manager Project
̈ ̈

Logical Components: DEV å QAS å PRD Project Documentation (Business Processes, Documentation, Testcases, …)

̈

NEW: Project Cycle

Development without release

Development with release

Test

Preparation for Go-Live

Go-Live

© SAP 2009

̈ ̈ ̈ ̈

SAP Solution Manager projects can be extended by adding project cycles that control project phases. Project phases determine whether or not transport requests can be created, released, or imported. Project phases are visible in the blueprint and configuration transactions. cProjects can be used to extend project management capabilities and to manage multiple phasespecific projects.

© SAP AG

E2E200

6-13

Proje c t Pha se s ? Wha t H appe ns Whe n?

Development without release

Development with release

Test

Preparation for Go-Live

Go-Live

Transport requests and transport tasks can be created. Exports are not permitted (except in the case of urgent corrections). Export of urgent corrections are permitted in every phase except for the Go-Live phase. When using the new regular correction (SDMJ), this phase is not recommended because transport of copies can not be exported.
© SAP 2009

Transport requests can be released from within a regular correction. For regular corrections, the administrator has to use the task list to import all released corrections into the test systems or he has to schedule regular import batch jobs in the satellite systems.

Release of regular corrections is not possible anymore (code freeze) Errors can be fixed with test messages Urgent corrections can be used as in the previous phases Unfinished developments will not be included in the actual test and golive, they can be included in the next test phase.

If changes still have to be made after the test phase has been completed, transport requests and tasks can be created and released as part of the Preparation for Go-Live phase, but only by using the task list of the Schedule Manager.

Importing the entire project buffer into the production system. No type of correction can be released during this phase.

̈ ̈ ̈

Each project cycle is controlled by its phases. Project phases are static and linked to each cycle. Each project cycle phase offers certain functions which differ according to the project type. Project cycles control the following things: • Whether or not transports are created, exported, or imported • Incorporate all logical systems that belong to a project • Project cycles an be closed after the go-live phase, or reset to the “In Development” phase

© SAP AG

E2E200

6-14

T ype s of Projec t s U se d in Change Request M a nagem ent
SAP Solution Manager Physical (development) systems Logical systems (clients) Transport Request
CTS project

Project cycle transaction

Project cycle task list

IMG project
cProjects

CTS project CTS project

...
SAP Solution Manager project

Project created in cProjects

IMG project

CTS project CTS project CTS project

...
© SAP 2009

...

̈ ̈

The Solution Manager project is represented as an IMG project in each satellite system and a CTS project in each satellite system client. For each Solution Manager project, a project cycle is generated, which is represented by a task list for managing the technical administration, and a cycle transaction for managing the organizational administration of the project cycle. Transport requests are only managed by the project cycle. The project assignment of each transport request is mandatory. The Solution Manager project can be extended by cProjects to manage project phases and project tasks. cProjects allow the management of interproject dependencies.

̈ ̈

© SAP AG

E2E200

6-15

Re pre sent a t ive s of t he Projec t Cyc le

SAP Solution Manager

Change Request Management

Cycle Transaction

Change Manager

PRD

Controlled transports

Project Cycle QAS

Cycle Task List

Controlled transports

DEV

© SAP 2009

̈ ̈

The project cycle is an abstraction layer, representing the fixed phase structure of a cycle that cannot be changed. The cycle task list represents the system landscape tracks and the tasks to be used by an IT administrator for managing project-related IT activities, especially imports. Custom task list templates with additional tasks can be created by customers. The cycle transaction represents the service request for managing the phase changes. Documentation, additional status, notification, electronic signatures, etc. can be managed from within the cycle transaction. Phase shifts should be done from within the cycle transaction but not from within the cycle task list, since additional activities and status can only be managed from within the service request. The project cycle has two representatives which can be seen in the system: The cycle transaction and the cycle task list.

̈

̈

© SAP AG

E2E200

6-16

Cyc le T ra nsa c t ion

© SAP 2009

̈ ̈

The maintenance cycle has its own cycle transaction. In the cycle transaction you can switch the project phase. In the task list of the cycle transaction you can start the import of the project buffer. This triggers an Import Project All.

© SAP AG

E2E200

6-17

Proje c t Cyc le

̈ ̈ ̈

SAP Solution Manager projects define the project landscapes. Project landscapes contain one or more logical components. Logical components incorporate logical systems that have the following system role types:
̈ ̈ ̈ ̈ ̈

Source system (development systems and starting systems) Target system (any system between the development and production systems) Production system (production systems and ending systems) Single system (evaluation systems without connection to a transport route) Post-processing system (retrofit systems)

̈ ̈

Only one active cycle can exist simultaneously for each project IMG and CTS projects collect changes:
̈ ̈

An IMG project represents an SAP Solution Manager project in one development system. A CTS Project represents an IMG project in one client.

© SAP 2009

̈ ̈

When a project cycle is being generated, all logical components and the transport routes of all systems are taken into account. Tracks are generated for each development system that matches to a system of role type ”Source System” in the logical component and as a source of a consolidation route in TMS. Each track is represented by one CTS project. Projects of type maintenance are represented by transaction type SDMN. Projects of type implementation, upgrade, and template are represented by transaction type SDDV.

̈ ̈

© SAP AG

E2E200

6-18

Syste m De m o

Create a Maintenance Project

© SAP 2009

© SAP AG

E2E200

6-19

Change Reque st Ma na ge m ent : U nit Ove rvie w Dia gra m
Change Request Management Lesson 1: Change Request Management Overview Lesson 2: Project and Release Management Lesson 3: Change Requests Lesson 4: Maintenance Activities Lesson 5: Integration of Non-ABAP Systems Lesson 6: Tools Lesson 7: Best Practices

© SAP 2009

© SAP AG

E2E200

6-20

Wha t Ha ppens Wit hout Change Reque st M a nagem ent ?
Hi Judy, can you change the sales report for me?

Flexibility

Yes, I can change it immediately and transport it to production. I have some additional requirements. Can you do this, too?

Why do I always get different sales figures?

Stability

Who allowed to change the sales report? This is against legal compliance rules ! Where is the documentation of the change?

© SAP 2009

̈ ̈

If no Change Request Management tool is in place, changes are often performed in an informal way, for example, the business requestor calls the developer. This procedure is very fast and efficient, however, causes a lot of follow-up problems: • Changes are not coordinated inside the business department, so not all requirements are considered. • Other users are not informed about the changes and might be surprised (missing transparency). • It is not guaranteed that all changes will be tested. There might be unwanted side effects (missing testing). • Changes are not approved by the responsible business process owner (missing governance). • The change is not documented. After some time nobody knows what was changed and why it was changed (missing documentation).

© SAP AG

E2E200

6-21

Approva l Proc e ss: Crea t e and Ac ce pt RfC

Create RfC
Rejected: New RfC

Accept: Filter RfC

Classify: Category and Priority

Urgent?
no

yes

Plan: Impact und Resources

© SAP 2009

̈

Create RfC: • Provide a tool so that no change requests are lost

̈

Accept: Filter RfC • Assign RfC to a business process • Is the requestor authorized? • Is it an RfC or an incident?

̈ ̈

Assign a responsible change manager Check if there are similar requests • Bundle and consolidate them

̈ ̈

Check if there are ongoing changes in this area Tools: • Change Request Reporting

© SAP AG

E2E200

Urgent Correction

6-22

Approva l Proc e ss: Cla ssify a nd Pla n RfC

Create RfC
Rejected: New RfC

Accept: Filter RfC

Classify: Category and Priority

Urgent?
no

yes

Plan: Impact und Resources

© SAP 2009

̈ ̈

Classify: Category and Priority: Priority: • Impact to the business process ($) • Due date (for example, month end closing)

̈

Category: • Depends on the priority • Which cycles exist - Urgent correction - Normal correction - Project request • Identify the components and business processes which are involved

̈

Plan: Impact and Resources • Complexity of change • Business areas affected • Critical objects check • Regression test required

© SAP AG

E2E200

Urgent Correction

6-23

Cre a t ing a nd Approving a Cha nge Re quest in SAP Solut ion M a na ge r
SAP Solution Manager
Service Desk
Feedback

Service Desk Employee

Service Message

Requester

Change Request Management

Change Request

Change Manager

Change Transaction

© SAP 2009

̈

A change request can be created out of a service desk message (incident) or directly as a request for change.

© SAP AG

E2E200

6-24

Change Reque st Form in SAP Solut ion Ma na ge r

© SAP 2009

̈ ̈

The entry in the IBase field is used to identify the production system that the change is required for. The entry in the Subject field is used to identify the project type and the change process type. Change types: • Urgent correction (only for maintenance projects) • Normal correction (for any project type) • Administration activity (for any project type)

̈

Project types: • Implementation • Maintenance

̈ ̈ ̈ ̈

Customizable fields: Category, Priority, Reference, Date, Products Extended general Customizing (project): Event-driven notifications, feedback, cost management, extended custom fields, and custom tabs Extended change request-specific Customizing (project): Text profiles, activity profiles, status schema, transaction types An approved change request results in the creation of a change transaction.

© SAP AG

E2E200

6-25

Assign Proce ss St ruc t ure Ele m ent s a nd Docume nt s t o Cha nge Re que st s

Assign Process Documents

Assign Process Structure Elements

© SAP 2009

̈

In change requests, you can assign structure elements documents from projects or solutions. This is useful as it allows the user to quickly find the objects in a change procedure that are affected by changes. You can navigate from the structure elements assigned in the change procedure to the assigned projects and solutions. In the change request navigate to the tab Transaction Data and then Content.

̈

© SAP AG

E2E200

6-26

Assign Ex ist ing T e st Docume nt s t o Cha nge Re que st s

© SAP 2009

̈ ̈ ̈

Existing test case descriptions from projects and solutions can be assigned to change requests. For this, the test cases must be available as Test Documents in the process structure. In the attributes of the test document you can generate a document URL. In the change request, you can add this URL link in the Documents tab.

© SAP AG

E2E200

6-27

Syste m De m o

Create a Change Request

© SAP 2009

© SAP AG

E2E200

6-28

Ex e rc ise

Create a Change Request

© SAP 2009

© SAP AG

E2E200

6-29

Change Ma nage me nt Work ce nt e r: Ove rvie w
Fast entry screen to get an overview of all change requests and change documents with business partner role and document status.

© SAP 2009

̈ ̈ ̈ ̈ ̈ ̈

The overview provides a summary of important objects is provided in Change Management, sorted by the business partner status and function: Change requests assigned to your business partner Change documents assigned to your business partner, sorted by change procedure type, for example, urgent correction Product maintenance procedures you have created or changed, or to which your business partner is assigned Click a hyperlink to go to a view of a filtered list. For example, as requester of your approved change requests, you go to the Change Requests view with a list of your approved change requests.

© SAP AG

E2E200

6-30

Change Ma nage me nt Work ce nt e r: Change Reque st s t a b
Choose business partner role Select request status Set a filter for searching requests

Create a new change request

- Description of request - All status changes and text changes are logged with user and timestamp

© SAP 2009

̈ ̈ ̈ ̈ ̈

In the Change Requests tab a list of change requests is provided which you can, for example, filter by status. To display and edit a change request, click in the list on the ID or change request description. You can also create new change requests. When you select a change request from the list, the system displays the details of this change request below the list, for example, the long text. The long text contains a complete history of all activities of the change request (who performed which activity at what time) You can perform the following functions from any view in the work center: • New Change Request • New Maintenance Transaction

© SAP AG

E2E200

6-31

Change Ma nage me nt Work ce nt e r: Change Docum ent s t a b
Choose business partner role Select request status Set a filter for searching requests

Choose transaction of type

- Description of change document - All status changes and text changes are logged with user and timestamp Create a new change request

© SAP 2009

̈ ̈ ̈

In the Change Documents tab a list of change documents is provided which you can, for example, filter by status. To display and edit a change document, click in the list on the ID or change document description. When you select a change document from the list, the system displays the details of this change document below the list, for example, the long text.

© SAP AG

E2E200

6-32

Change Reque st Ma na ge m ent : U nit Ove rvie w Dia gra m
Change Request Management Lesson 1: Change Request Management Overview Lesson 2: Project and Release Management Lesson 3: Change Requests Lesson 4: Maintenance Activities Lesson 5: Integration of Non-ABAP Systems Lesson 6: Tools Lesson 7: Best Practices

© SAP 2009

© SAP AG

E2E200

6-33

I m ple me nta t ion Proje c t s

SAP Solution Manager Project (Implementation Project)

Development without release

Development with release

Test

Preparation for Go-Live

Go-Live

Project Cycle

Normal corrections Test messages
(during integration test)

© SAP 2009

̈ ̈

For Implementation, Upgrade and Template Projects, Normal Corrections can only be approved during the project phase development w/o release and development w/ release. For these project types no urgent corrections are possible. This is not necessary, because the new functionality is not yet life in production.

© SAP AG

E2E200

6-34

Ma inte na nc e Projec t s

SAP Solution Manager Project (Maintenance Project)

Development without release

Development with release

Test

Preparation for Go-Live

Go-Live

Maintenance Cycle

Normal corrections Test messages
(during integration test)

Urgent corrections

© SAP 2009

̈ ̈

The maintenance project is a prerequisite for production support. It is the central unit for all information, such as logical component and system landscape, and the high level project plan. It closes the gap between planning and software logistics: • SAP Solution Manager project • IMG project • CTS project

̈

A maintenance cycle belongs to just one maintenance project.

© SAP AG

E2E200

6-35

M a inte na nc e Projec t : De finit ion

̈ ̈ ̈ ̈

The maintenance project is prerequisite for production support. A maintenance project manages maintenance cycles as long as defined by the project lifecycle. The maintenance cycle distributes consistently any maintenance or urgent correction change to any system of the project landscape. One maintenance project can have multiple maintenance systems assigned to it, including the corresponding transport routes (one logical system for Workbench requests and one logical system for Customizing requests, for example). A maintenance cycle belongs to exactly one maintenance project.

© SAP 2009

© SAP AG

E2E200

6-36

Ma inte na nc e Cyc le : De finit ion

A maintenance cycle is the period of time in which you
̈ ̈ ̈

Make changes in maintenance systems Include these changes in new transport requests Import these requests into follow-on systems for testing

At the end of a maintenance cycle, all transport requests are imported into the production system at the same time. Subsequently, the maintenance cycle can be closed manually and a new one can be created, if necessary (but only in compliance with the rules of the change requests that belong to the maintenance cycle).

© SAP 2009

© SAP AG

E2E200

6-37

Pha se s of a M a int enance Cyc le : Wha t Can Be Done in Which Pha se ?

Development without release

Development with release

Test

Preparation for Go-Live

Go-Live

Transport requests and transport tasks can be created. Exports are not permitted (except in the case of urgent corrections). Export of urgent corrections are permitted in every phase except for the Go-Live phase. When using the new regular correction (SDMJ), this phase is not recommended because transport of copies can not be exported.
© SAP 2009

Transport requests can be released from within a regular correction. For regular corrections, the administrator has to use the task list to import all released corrections into the test systems or he has to schedule regular import batch jobs in the satellite systems.

Release of regular corrections is not possible anymore (code freeze) Errors can be fixed with test messages Urgent corrections can be used as in the previous phases Unfinished developments will not be included in the actual test and golive, they can be included in the next test phase.

If changes still have to be made after the test phase has been completed, transport requests and tasks can be created and released as part of the Preparation for Go-Live phase, but only by using the task list of the Schedule Manager.

Importing the entire project buffer into the production system. No type of correction can be released during this phase.

© SAP AG

E2E200

6-38

Pha se s of a M a int enance Cyc le (1 of 2)

Created
̈

Initial status of a maintenance cycle

In Development without Release
̈

Corrections can be developed, and transport requests and transport tasks can be created. Exports, however, are not permitted (except in the case of urgent corrections). Export of urgent corrections are permitted in every phase except for the Go-Live phase. When using the new regular correction (SDMJ), this phase is not recommended because transport of copies cannot be exported.

In Development with Release
̈

Transport requests can be released from within a regular correction. For regular corrections, the administrator has to use the task list to import all released corrections into the test systems or he has to schedule regular import batch jobs in the satellite systems.

Test
̈

The test phase is necessary for integration testing. No regular corrections can be released any more, so a code-freeze can be guaranteed. To fix errors which occurred during the integration test, test messages have to be used. Urgent corrections can be used as in the previous phase. Unfinished developments will not be included in the actual test and go-live, they can be included in the next test phase.

© SAP 2009

© SAP AG

E2E200

6-39

Pha se s of a M a int enance Cyc le (2 of 2)

Emergency Correction (Preparation for Go-Live)
̈

If changes still have to be made after the test phase has been completed, transport requests and tasks can be created and released as part of the Preparation for Go-Live phase, but only by using the task list of the Schedule Manager.

Go-Live
̈

Importing the entire project buffer into the production system. No type of correction can be released during this phase.

To Be Closed
̈

If there are no open transport requests, the maintenance cycle can be closed by setting the status to To be closed. Subsequently, a new maintenance cycle can be created.

Completed
̈

Maintenance cycle is closed. No further changes in this maintenance cycle are possible.

When completing the maintenance cycle all open requests and transactions will be decoupled from the task list. When generating a new task list for the same project, all open requests and transactions will be linked to this new task list and can be processed further.

© SAP 2009

© SAP AG

E2E200

6-40

T e chnica l Re a liza t ion of T ra nsport Re st ric t ions via CT S Proje c t St a t us Sw it c he s
Change Manager

Project Cycle
Control settings

DEV

DEV
Create TR Release TR

CTS Status Switch

QAS

QAS
Import TR

CTS Status Switch

PRD PRDStatus Switch CTS
Import TR

Transport Landscape

© SAP 2009

̈ ̈ ̈ ̈

Change Request Management uses the CTS project status switches in order to lock exorts and imports in the connected system. The task list tasks will open and close the status switch inherently when performing create, release, or import transports. Project assignment should be set to mandatory since only project import is being supported next to import subset for urgent corrections. In the Workbench Organizer only “release task” can be performed.

© SAP AG

E2E200

6-41

U rge nt Correc t ion

SAP Solution Manager Project (Maintenance Project)

Development without release

Development with release

Test

Preparation for Go-Live

Go-Live

Maintenance Cycle

Normal corrections Test messages
(during integration test)

Urgent corrections

© SAP 2009

̈ ̈ ̈ ̈

Urgent corrections are fast changes that have to be imported into the production environment as quickly as possible. An urgent correction can be described as the smallest subproject of a broader maintenance project cycle. Urgent corrections can be performed during the maintenance project phases ”Development w/o release” up to ”Emergency Correction”. Urgent corrections can be approved and developed but not exported during Go-Live Phase.

© SAP AG

E2E200

6-42

Change Reque st Ma na ge m ent ? U rge nt Corre c t ion
SAP Solution Manager
Service Desk
Feedback

Service Desk Employee

Service Message

Requester

Change Request Management

Developer

Change Request

Change Manager

PRD

Controlled transports

Tester

Change Transaction

Task List

QAS

Controlled transports

IT Operator

Maintenance Cycle DEV

© SAP 2009

̈ ̈ ̈ ̈

An urgent correction is represented by a singular task list that is created when an urgent correction is being generated during approval time. An urgent correction task list is closed when the urgent correction is closed. An urgent correction can be described as the smallest subproject of a broader maintenance project cycle. Technically, an urgent correction is managed by “import subset” and is automatically merged into the current open maintenance cycle.

© SAP AG

E2E200

6-43

Syste m De m o

Urgent Correction

© SAP 2009

© SAP AG

E2E200

6-44

N orm a l Corre c t ion

SAP Solution Manager Project (Maintenance Project)

Development without release

Development with release

Test

Preparation for Go-Live

Go-Live

Maintenance Cycle

Normal corrections Test messages
(during integration test)

Urgent corrections

© SAP 2009

̈ ̈ ̈ ̈

The “Normal Correction” relates to the life cycle of the project. As of SAP Solution Manager 4.0 SP6 the transaction type for the normal correction will be SDMJ. It is an optimization of the normal correction (SDMI), which is already available. Each project can have as many normal corrections as required. A Normal Correction phase depends on the phase of the project cycle phase. • For Maintenance Projects normal corrections can be approved during the phases “Development w/o release” up to “Go-Live”. • From the Test phase up to Go-Live, no export of transports is possible.

̈

Normal corrections allow development up to unit testing: • Transport requests can be created. • Transport tasks can be created. • Test transports can be created. • Test transports can be exported. • Development can be closed. • Unit test can be performed. • Unit test can be confirmed.

© SAP AG

E2E200

6-45

N orm a l Corre c t ion

̈ ̈ ̈

The normal correction relates to the life cycle of the project. Each project can have as many normal corrections as required. A normal correction can be shared by multiple developers, and multiple transport requests and transport tasks can be created. A normal correction phase depends on the phase of the project cycle. Normal corrections can only be distributed using the import project method. > Transport requests/tasks can be created and exported from within the service request. > Project exports and imports can be managed by the maintenance task list.

̈ ̈

© SAP 2009

© SAP AG

E2E200

6-46

Change Reque st Ma na ge m ent N orm a l Corre c t ion
SAP Solution Manager
Service Desk
Feedback

Service Desk Employee

Service Message

Requester

Change Request Management

Developer

Change Request

Change Manager

PRD

Controlled transports

Tester

Change Transaction

Maintenance Cycle QAS

Controlled transports

IT Operator DEV

© SAP 2009

̈ ̈ ̈

A normal correction is generated as a follow-up transaction by the approval activity. Normal corrections are directly linked to a project cycle transaction and project cycle task list. From within a normal correction, the creation of a transport request and transport task and the release of related transports are controlled by the change request or normal correction. Imports are done by means of import projects from within the cycle task list. A normal correction can be shared by multiple developers, and multiple transport requests and transport tasks can be created

̈

© SAP AG

E2E200

6-47

N orm a l Corre c t ions U se T e st T ra nsport s

Legend: Normal Correction

Test transport

Test Transport (Transport of Copies)

Transport buffer

Transport buffer

DEV

QAS

PRD

Original Workbench or Customizing transport

Test transport and original transport reach QAS

Only original transport follows the transport routes to PRD

© SAP 2009

̈ ̈ ̈

Normal corrections are exported as test transports, which are performed as transports of copies. Up to status consolidated, only test exports are possible: The system generates and exports transports of copies from the workbench or customizing requests of the activity. When the status is transferred to consolidated, all transport requests will be exported and put in the import queue of the quality system. • No new transport requests can be created for the normal correction.

̈

Normal corrections are imported by using the “import project” method from within the cycle task list. • All exported transport requests are imported using the “import project” method. • Transport requests can be imported once into each project system that has the role type target or production. • During the in Development status only test transports can be performed. • Test transports are exported and transported as transports of copies into the consolidation buffer.

̈

Benefits of using test transports are: • Workbench objects in transition stay locked in the development system. • The number of erroneous customizing and workbench requests is reduced. This reduces the import time in production.

© SAP AG

E2E200

6-48

Consist enc y of U rgent Correc tions and M a inte na nc e Ac t ivit ie s
Legend:

Urgent correction

Normal Correction Urgent Correction Consolidated Transport

Transport buffer

Transport buffer

DEV

QAS

PRD

Regular correction

Test of Regular Correction running

Import in correct order to ensure consolidated system state

© SAP 2009

̈ ̈ ̈ ̈

Urgent corrections are transported individually and thus have no time dependency with respect to other corrections. Urgent corrections are imported by the transport method import subset and stay in the transport buffer after import. Urgent corrections are propagated into other systems at the end of phases in the maintenance cycle together with the normal corrections by the transport method import project all. For normal corrections, the import into the follow-on systems occurs in the historical sequence.

© SAP AG

E2E200

6-49

Diffe rence s Be t w ee n N orma l a nd U rge nt Corre c t ions
Normal Correction
Transport requests have to be created manually using actions of the change transaction. Test transports are used during the phase “Development with Release”. Transports are exported and imported in concordance with the phases of the maintenance cycle. A violation against the separation of functions is only a warning. No individual task list but the task list of the maintenance cycle is used.
© SAP 2009

Urgent Correction
Transport requests are generated automatically Test transport functionality is not available. Transports can be propagated directly into the follow-on systems but remain in the transport buffer. Developer and tester must be different persons. An individual task list is used.

© SAP AG

E2E200

6-50

Syste m De m o

Normal Correction

© SAP 2009

© SAP AG

E2E200

6-51

Ex e rc ise

Normal Correction

© SAP 2009

© SAP AG

E2E200

6-52

N orm a l Corre c t ion in Pha se “De ve lopment w it hout Re lea se “
Phase In Development without Release SDMJ-Status Created User Action Set to In Development Technical Action

In Development

Create Transport Request

Transport Requests are created

In Development

System Logon / Perform Fix / Release Task

© SAP 2009

̈ ̈

This table explains the different statuses of a normal correction and how they are related to the phases of the project. In each status certain user actions are possible that cause technical actions in the systems.

© SAP AG

E2E200

6-53

N orm a l Corre c t ion in Pha se “De ve lopment w it h Re le a se “
Phase In Development with Release SDMJ-Status In Development User Action Create Transport of Copies Technical Action

In Development

Set to To be Tested

Transport of Copies is created and exported Import Project into Test Systems (in the tasklist of the maintenance cycle)

To be tested

To be tested To be tested

System Logon / Perform Unit-Test Set Correction to Consolidated Original Transport Request is exported

Consolidated

© SAP 2009

© SAP AG

E2E200

6-54

N orm a l Corre c t ion in Pha se “Te st “

Phase Test (No Export possible)

Status Consolidated

User Action

Technical Action Import Project into Test Systems • consolidated + transport of copies • in the task list of the maintenance cycle

System Logon / Perform Integration Test

© SAP 2009

̈

When the project cycle is switched to the phase Test no exports are possible.

© SAP AG

E2E200

6-55

N orm a l Corre c t ion in Pha se “GoLive “

Phase

Status

User Action

Technical Action

GoLive

Consolidated

Import Project into Production Systems (only consolidated change requests are in the import buffer) Set Correction to Productive

Productive

© SAP 2009

̈ ̈ ̈

Only in the GoLive phase imports into production are possible. Only workbench and customizing requests are in the import queue of the productive system. Test transports did not follow the transport routes into the import queue of production.

© SAP AG

E2E200

6-56

T e st M e ssa ge s

SAP Solution Manager Project (Maintenance Project)

Development without release

Development with release

Test

Preparation for Go-Live

Go-Live

Maintenance Cycle

Normal corrections Test messages
(during integration test)

Urgent corrections

© SAP 2009

̈ ̈ ̈

Transport requests cannot be exported during the test phase. No exports are possible in maintenance projects. Furthermore, no new change requests can be created in implementation projects. A test message allows a tester to contact a developer, and to create and export a transport request within the test phase of a project cycle. Phase “Test“ for a maintenance cycle: • Test messages can be created. • New normal corrections can be created but not exported any more. • Urgent corrections can still be created and also propagated up to going live.

̈

Test messages must be released and closed before the status Emergency Correction is set.

© SAP AG

E2E200

6-57

Change Reque st Ma na ge m ent T e st M e ssa ge
SAP Solution Manager

Change Request Management

Developer

Cycle Transaction

Change Manager

PRD

Controlled transports

Tester

Test Message

Task List

QAS

Controlled transports

Project Phases DEV

© SAP 2009

̈

A test message is supposed to be created by a tester, but only in the test phase of a certain project: • Log on to development system. • Create transport request. • Create transport task. • Release transport request.

̈ ̈ ̈

Test messages can be created by using transaction CRMD_ORDER or transaction TEST_CREATE. The test phase represents the integration test phase within a project cycle. Therefore, corrections are not directly linked to a change request but to the complete project cycle. The change manager, quality assurance manager or project manager has the ability to create test messages for a certain project when he or she switches a phase to TEST. Test messages do not require an approval. The import of corrections into test systems must be performed by the IT operator by means of periodically running import jobs.

̈

© SAP AG

E2E200

6-58

T e st M e ssa ge : Sum ma ry

̈ Test

messages can only be used in the Test phase. ̈ Test messages do not require an approval.
̈ Test

messages allow the insertion of any system of the system landscape as a reference, supposedly a test system. ̈ Test messages must be released before the status preparation for go-live is set. ̈ Test messages allow the user to create and release transport requests.

© SAP 2009

© SAP AG

E2E200

6-59

Adm inist ra t ion M e ssage s

SAP Solution Manager Project (Maintenance Project)

Development without release

Development with release

Test

Preparation for Go-Live

Go-Live

Maintenance Cycle

Administration messages
(during all project phases)

© SAP 2009

̈ ̈ ̈

Administration messages can be created during all operational phases of a project and allow the logon to any project landscape system. Administration messages are intended to manage changes that do not require to create a transport request, for example, database or parameter changes. Nnon-SAP systems can also be handled with Administration messages.

© SAP AG

E2E200

6-60

Change Reque st Ma na ge m ent Adm inist ra t ion M e ssage
SAP Solution Manager
Service Desk
Feedback

Service Desk Employee

Service Message

Requester

Change Request Management

Change Request

Change Manager

PRD

Controlled transports

Admin. Message

Cycle Tasklist

QAS

Controlled transports

IT Operator

Project Phases DEV

© SAP 2009

̈ ̈ ̈

Administration messages must be approved by a change request, unlike test messages that are open to be performed whenever a project cycle phase is being switched to test. The administration message is linked to the cycle task list and custom tasks can be added to the cycle task list template. Administration messages allow administration activities in the systems of a project landscape. • Logon to target systems • Documentation of administration changes

̈

Additional tasks can be included in the cycle task list and in the activities of the administration message.

© SAP AG

E2E200

6-61

Adm inist ra t ion M e ssage s: Sum ma ry

̈ Administration

messages allow the user to perform any action including actions where no transport request is needed (including logon that can be performed within one particular system): server switching, browser update, etc. ̈ An administration message can be created during all phases of a project and allows logon to any system that is part of the project.
̈ Access

to the task list is provided.

© SAP 2009

© SAP AG

E2E200

6-62

Comple t ing Projec t Cyc le s

̈ It

is possible to complete a project cycle and its task list, although it still has changeable change transactions and transport requests assigned to it. ̈ The system saves the change transactions and transport requests while the cycle is completed, and provides them automatically with the next cycle when it is created. All change transactions can be used within the new cycle.
̈ When

you start the completion process for the cycle (that is switch the cycle phase from being completed to completed), you will see an overview of all checks which will be performed for completing the cycle, and information about the importance of the checks. Some checks may be ignored, some must not be ignored (marked with ).

© SAP 2009

© SAP AG

E2E200

6-63

Comple t ing Projec t Cyc le s ? N e w Assignm e nt s

When you create a new cycle in the SAP Solution Manager, the saved business transactions and transport requests are assigned to the new cycle. You see messages about the new assignments in the application log.
̈

Go to transaction SOLAR_PROJECT_ADMIN and select Appl. Log on the tab strips System Landscape Change Requests

© SAP 2009

© SAP AG

E2E200

6-64

Change Reque st Ma na ge m ent : U nit Ove rvie w Dia gra m
Change Request Management Lesson 1: Change Request Management Overview Lesson 2: Project and Release Management Lesson 3: Change Requests Lesson 4: Maintenance Activities Lesson 5: Integration of Non-ABAP Systems Lesson 6: Tools Lesson 7: Best Practices

© SAP 2009

© SAP AG

E2E200

6-65

Change Reque st M a na ge m ent CT S+ I s Fully I nt e gra t ed

CTS+ enables Change Request Management to support the whole Business Process Platform.

One central Transport Tool Multiple Types of Backends
SAP NetWeaver SAP NetWeaver SAP NetWeaver AS ABAP AS ABAP AS ABAP

Enhanced CTS

ESR/PI/XI XI/PI System XI/PI System System
on SAP NetWeaver (Dual Stack)

Portal System
on SAP NetWeaver AS Java

SAP NetWeaver SAP NetWeaver AS Java AS Java on SAP NetWeaver AS Java

NW DI

... ... ...

Multiple Development Workbenches

...

© SAP 2009

̈

Enhanced CTS offers the possibility to transport objects created in other languages than ABAP through the Change and Transport System of ABAP. The goal is to have one Transport Tool (CTS) which supports all workbenches and applications with respect to transports. The tools for creating applications and creating content remain the same. Options to attach applications or content to a CTS Transport Request are integrated into the different workbenches. The level of integration is different for different workbenches. This is explained in detail on the following slides. Enhanced CTS aims for a unified single transport tool which simplifies the live of an administrator who is responsible for performing imports. He or she has to access only one tool to start imports for very different backends. Deployment tools are called automatically. It is very easy to monitor what has already been imported and if the import went well. The queues in CTS provide a good overview on what needs to be imported.

© SAP AG

E2E200

6-66

Re quire d CT S Se t t ings for N on-ABAP Syst e m s

Required transport parameters for the Transport Organizer
̈ ̈

WBO_GET_REQ_Strategy: TAGGED (only for exclusive ChaRM usage) WBO_REL_REQ_Strategy: MANUAL

Required Transport Parameters single JAVA stacks
̈ ̈

CTC = 0 CTS_SYSTEM_TYPE = JAVA

© SAP 2009

̈

Online documentation available at • http://help.sap.com/ - SAP NetWeaver 7.1 (or below) å SAP NetWeaver Library å SAP NetWeaver Key Capability å Software Lifecycle Management å Software Logistics å Change and Transport System

© SAP AG

E2E200

6-67

Pa ra m e te r CT S_SY ST EM _T Y PE for Single J AVA St a c k s

1) Set transport parameter CTS_SYSTEM_TYPE = JAVA 2) After a landscape fetch the communication system will appear in SMSY

3) An IMG project can be created for the JAVA system in the communication system
© SAP 2009

© SAP AG

E2E200

6-68

Proc e ss Flow for N on-ABAP Environm ent s 1 /2

Change Request Management

Change Manager

Transport Organizer Web UI

Developer

Change Request Management

Developer

Approve Change Request and create Urgent Correction

Preselect standard transport request that belongs to the change request

Release transport request

Change Request Management

Developer

Non-ABAP development environment

Developer

Change Request Management

Developer

Set UC to “In development” å A workbench request is created

Perform development change

Pass correction to test å The workbench request is imported in QA

Non-ABAP development environment

Developer

Change Request Management

Tester

Attach change to transport request

Test correction

© SAP 2009

̈ ̈

For non-ABAP environments there is an additional step “Preselect transport request“ that must be done by the developer. In non-ABAP environments the transport request must be selected in a separate step before objects can be attached to it. This is different from ABAP environments, where the system asks you if there are several transport requests available. The system logon does not work for all development environments. Therefore, the developer must log on manually to the development environment in some cases. All other steps of the Change Request Management process are identical for ABAP and non-ABAP environments.

̈ ̈

© SAP AG

E2E200

6-69

Proc e ss Flow for N on-ABAP Environm ent s 2 /2

Create Transport Request in Change Request Management

Preselect transport request in the Transport Organizer Web UI

1

2

Attach Non-ABAP object to Transport Request in the Non-ABAP development environment

Release Transport Request in Change Request Management

5 3 4
© SAP 2009

̈ ̈ ̈ ̈ ̈

1. Change Request Management: Create workbench request 2. Non-ABAP development envrionment: Perform the change and go to the export wizard. From there you can jump into the Transport Organizer Web UI 3. Transport Organizer Web UI: Preselect the request that belongs to your change document as standard request 4. Non-ABAP development environment: In the export wizard, attach the archive with the change to the preselected request 5. Change Request Management: Release transport request

© SAP AG

E2E200

6-70

Syste m De m o

ChaRM with CTS+

© SAP 2009

© SAP AG

E2E200

6-71

Change Reque st Ma na ge m ent : U nit Ove rvie w Dia gra m
Change Request Management Lesson 1: Change Request Management Overview Lesson 2: Project and Release Management Lesson 3: Change Requests Lesson 4: Maintenance Activities Lesson 5: Integration of Non-ABAP Systems Lesson 6: Tools Lesson 7: Best Practices

© SAP 2009

© SAP AG

E2E200

6-72

Change Reque st Ma na ge m ent : U nit Ove rvie w Dia gra m
Change Request Management Lesson 6: Tools Change Request Management Reporting Change Tracking Tasklist Cross System Object Lock Critical Object Approval Process Retrofit

© SAP 2009

© SAP AG

E2E200

6-73

Change Ma nage me nt Reporting Re quire m ent s

Development

Quality

Productive

Poll via RFC

Poll via RFC

SAP Solution Manager

Poll via RFC

Change Request Management configured Data Collector job is scheduled
© SAP 2009

̈ ̈ ̈

Change Management Reporting in SAP Solution Manager requires that the monitored systems are included in projects for which Change Request Management is activated. Data from satellite systems is collected every hour (default setting) and after each import that is scheduled by means of the task list. Information on transported objects can be collected on demand. Object reporting increases the data volume in the SAP Solution Manager if large system landscapes are managed.

© SAP AG

E2E200

6-74

T ypic a l Que stions t o Be Answ e red by Cha nge Re que st M a nage me nt Report ing
Operational Questions for the Project Manager
̈

Which transport requests were imported into which systems?
̈

No manual tracking necessary For example, at the development close Transparency of the scope of a release

̈

Which change requests are in process or completed ...?
̈

̈

Which change requests are part of a customer development cycle?
̈

Reporting on Key Performance Indicators for Future Process Improvements
̈

How many urgent and normal corrections were created?
̈

Which percentage of changes was urgent? Per organization, user, type, step Per organization, user, type, by whom and why

̈

How long do change requests take to be completed?
̈

̈

How many change requests were rejected or withdrawn?
̈

© SAP 2009

© SAP AG

E2E200

6-75

Change Reque st Ma na ge m ent Report ing Ac ce ss via Work ce nte r

Reporting tool for Change Request Management

© SAP 2009

̈

Cross-solution reporting with report variants is provided to analyze change requests and change documents. You can either upload the documents manually to Solution Reporting or schedule it as a background job. For more information, see Report: Change Management. Alternatively, access is possible by using transaction SOLAR_EVAL: Analysis å Solution å Change Management

̈

© SAP AG

E2E200

6-76

Change Reque st Ma na ge m ent Report ing St a t us of Da t a

© SAP 2009

̈

The Status of Data field displays the date and time when the last data collector run took place. If, for any reason, the data collector could not collect data about a particular system (system downtime, for example), this system is displayed in the Differing Systems field. This field only appears if there are any inconsistencies. By clicking the icon next to the field, you can perform an online update of the system data (may take some time). The Differing Systems field then disappears.

© SAP AG

E2E200

6-77

Change Reque st Ma na ge m ent Report ing: Addit iona l I nform a t ion
Many more combinations of selection criteria are possible. You can narrow down a query by returning to the selection screen and entering more information. If the result list does not provide enough detail, you can always return to the selection screen to select a different view (Result List group box Display field) The Header view displays the least amount of detail; the Header, Project, Task List, and Transports view, for example, displays more details.

© SAP 2009

© SAP AG

E2E200

6-78

Ex e rc ise

Change Management Reporting

© SAP 2009

© SAP AG

E2E200

6-79

Syste m De m o

Change Management Reporting

© SAP 2009

© SAP AG

E2E200

6-80

Change Reque st Ma na ge m ent : U nit Ove rvie w Dia gra m
Change Request Management Lesson 6: Tools Change Request Management Reporting Change Tracking Tasklist Cross System Object Lock Critical Object Approval Process Retrofit

© SAP 2009

© SAP AG

E2E200

6-81

Change Ma nage r: Change T ra ck ing

© SAP 2009

̈

The change tracking function of Change Request Management allows you to track everything relating to changes within the context of a Solution Manager project or an IMG project. It is possible to track all transport requests from the system where they are created, to the systems into which they are imported. Within the project context, all transport requests that belong to a particular project can be tracked across all the systems in the project landscape. Project analysis: Track all changes for one Solution Manager project or for one IMG project System analysis: Compare change requests within systems, differences in the number of change requests, and differences in the sequence in which requests are exported and imported Request analysis: Track change requests, starting with the system where the request was created, to all systems into which the transport is imported Start analysis: Transaction /TMWFLOW/TRMO å Choose Tracking

̈ ̈ ̈ ̈

© SAP AG

E2E200

6-82

Change Reque st Ma na ge m ent : U nit Ove rvie w Dia gra m
Change Request Management Lesson 6: Tools Change Request Management Reporting Change Tracking Tasklist Cross System Object Lock Critical Object Approval Process Retrofit

© SAP 2009

© SAP AG

E2E200

6-83

T a sk List

© SAP 2009

̈ ̈ ̈

The task list is the interface to the Change and Transport System in the satellite systems. You can create, release, and import transport requests from there. The task list is normally used in the background by the CRM transactions. Only the import of a project by the project manager is done directly in the task list. Task lists are based on project landscape role types: • Source system • Target system • Production system • Single system • Post-processing system

̈ ̈ ̈ ̈

When a project landscape changes, the systems have to be deleted or inserted correctly by an administrator. Phases can be shifted from within the cycle task list (as well as the cycle transaction). Cycle task lists can be activated, locked, and completed. Tree structures can be locked against usage from normal corrections, test messages, and administration messages.

© SAP AG

E2E200

6-84

T a sk List De t a ils

© SAP 2009

̈

Monitor tasks with detailed log information

© SAP AG

E2E200

6-85

Change Reque st Ma na ge m ent : U nit Ove rvie w Dia gra m
Change Request Management Lesson 6: Tools Change Request Management Reporting Change Tracking Tasklist Cross System Object Lock Critical Object Approval Process Retrofit

© SAP 2009

© SAP AG

E2E200

6-86

Dow ngra de Risk w it h U rge nt Corre c t ions

Project Buffer

Project Buffer

DEV

1 2

QAS

2

PRD

Legend:

Urgent Corrections

© SAP 2009

̈

The locking of objects within an urgent correction prohibits an urgent correction bypassing another with the same object, but a newer object version.

© SAP AG

E2E200

6-87

Dow ngra de Risk w it h Pa ra lle l Proje c t s

Project Buffer

Project Buffer

DEV

QAS

PRD

Legend:

Project1 Project2

© SAP 2009

̈ ̈

Normal corrections or project transports that share the same production system, but have different life cycles and can include different versions of the same objects. Depending on the life cycle of parallel projects and on object conflicts, objects might be downgraded.

© SAP AG

E2E200

6-88

Cross-Syst e m Lock

Workbench and Customizing Objects are locked

SAP Solution Manager Cross-System Object Lock Projects

NC(O1) – P2 – SYS1 failed UC(O2) – P1 – SYS1 failed NC(O3) – P2 – SYS1 failed UC(O2) – P2 – SYS2 failed

NC(O1) – P1 NC(O1) - P2 UC(O2) – P1 UC(O2) – P1 NC(O3) – P2

Test System

Production System

NC(O3) – P2 UC(O2) – P2

© SAP 2009

̈ ̈ ̈

The cross-system lock can be activated by the report /TMWFLOW/CONFIG_SERVICES. You can see the active locks in transaction /TMWFLOW/LOCKMON. There, you can also delete locks if needed. There are four main different locking modes that can be configured (with SP8 for Solution Manager 4.0 some new scenarios available). • Cross-project and client-specific - Urgent corrections cannot interfere – Error - All other changes are recognized – Warning • Cross-project and cross-client - Urgent corrections cannot interfere, but only regarding cross-client Customizing, ABAP, and DDIC – Error - All other changes are recognized – Warning • Project-specific and client-specific - Urgent corrections cannot interfere – only for Customizing but not ABAP and DDIC data – Error - All other corrections regarding Customizing between projects are recognized, ABAP and DDIC changes are only recognized within a project – Warning • Project-specific and cross-client - Urgent corrections cannot interfere regarding cross-client Customizing, ABAP and DDIC within a project context – Error - Other changes are recognized – Warning

© SAP AG

E2E200

6-89

Syste m De m o

Cross-System Object Lock

© SAP 2009

© SAP AG

E2E200

6-90

Change Reque st Ma na ge m ent : U nit Ove rvie w Dia gra m
Change Request Management Lesson 6: Tools Change Request Management Reporting Change Tracking Tasklist Cross System Object Lock Critical Object Approval Process Retrofit

© SAP 2009

© SAP AG

E2E200

6-91

Crit ic a l Obje c t Approva l Proc e ss

Critical objects are approved at the time of export.
̈

Critical objects are defined as:
̈ ̈ ̈

Modifications Workbench objects in transport piece list format Customizing objects in transport piece list format

Critical object check is activated for each logical system:
̈ ̈ ̈ ̈

R3TR objects LIMU objects Logical objects for Customizing views Table entries for Customizing tables

Modification approval is activated once in SAP Solution Manager:
̈

Activate for each logical system

© SAP 2009

̈ ̈

For general information about Critical Objects, refer to unit “Transport Strategies” in Lesson 2. The benefits of this procedure compared to the TMS check for critical transport objects are the following: • Customizing entries can also be marked as critical. • The check is performed at the time of the export from the development system. This gives the organization many options on how to deal with that critical object. If a critical object is only detected at the time of the import, it is often difficult to postpone a scheduled Go-Live.

© SAP AG

E2E200

6-92

Crit ic a l Obje c t De finit ion and Approva l

/TMWFLOW/CMSCONF

Only users with the role Change Manager can approve critical objects
© SAP 2009

̈ ̈ ̈ ̈

For the definition of critical objects use the transaction /TMWFLOW/CMSCONF; select the critical object tab page The check can be activated on a system level and a client-specific level. When a critical object is contained in a transport of the change transaction, no export is possible unless the change manager approves the critical object. In the Schedule Manager application log, you see the following information: Transport object checks are activated. Request <request number> contains critical objects!

̈

Only users with the role “change manager” can approve critical objects.

© SAP AG

E2E200

6-93

Syste m De m o

Critical Object Approval

© SAP 2009

© SAP AG

E2E200

6-94

Change Reque st Ma na ge m ent : U nit Ove rvie w Dia gra m
Change Request Management Lesson 6: Tools Change Request Management Reporting Change Tracking Tasklist Cross System Object Lock Critical Object Approval Process Retrofit

© SAP 2009

© SAP AG

E2E200

6-95

Re t rofit Proc e ss: Support for a Pha sed Syst e m Landsc ape
Project Landscape

DEV
Retrofit

TST

Maintenance Landscape

CON

QAS

PRD

© SAP 2009

̈ ̈ ̈

In a phased system landscape all bugfixes in the maintenance landscape must be manually performed again in the project landscape. This process is called dual maintenance or “Retrofit”. Change Request Management provides an automatic procedure for the retrofit process. A retrofit system must be avialable in the SAP Solution Manager maintenance project (role type: post processing system). It should be a development system of another project, for example, an implementation project. The task list of the maintenance project will have two new tasks: • General Tasks å Assign post-processing system to development system • Track Section å Post processing systems å Retrofit Systems å Start Retrofit

̈

© SAP AG

E2E200

6-96

Re t rofit Proc e ss in SAP Solut ion M anager

© SAP 2009

̈ ̈

There will be a new activity “Start Retrofit” in the Action Profile. This new activity is available when a normal correction reaches the status Consolidated or an urgent correction reaches the state Authorized for Production

© SAP AG

E2E200

6-97

Se le c t T ra nsport Re que st for Re t rofit

© SAP 2009

̈ ̈

For the execution of the retrofit, a transport request must already exist in the retrofit system (retrofit request). The retrofit process is based on the following tools: • Correction Workbench (SCWB) for Workbench Objects • Customizing Synchronization (Customizing Scout) for Customizing Objects

© SAP AG

E2E200

6-98

Som e Objec t s Are not Support e d by Re t rofit

© SAP 2009

̈ ̈ ̈ ̈

Some objects are not supported by the retrofit process, since the tools retrofit uses (SCWB and BCSet) cannot retrofit these objects. The column Critical Retrofit indicates that a transport request contains some of these objects. If you click on the traffic light which corresponds to the transport request, you will get an application log of the objects that are not supported by retrofit. In this case, you must perform the retrofit manually. Use the button Retrofit Manual in order to indicate that the transport request was retrofitted manually.

© SAP AG

E2E200

6-99

Re t rofit M e t hods a nd Support ed Obje c t s

SAP Correction Workbench
̈ ̈ ̈

Single lines of coding can be transferred between systems by building a context block, a delete block and an insert block. The delta information is transferred into the target system and can be activated there. The delta is shown in a splitscreen editor. All coding objects are supported by this method, that is all objects which are also supported by the SAP Note Assistant.

BC Set Activation
̈ ̈

Customizing settings are packed into a BC Set. The BC Set is transferred into the target system and activated there. Most Customizing tables are supported by BC Sets. You can find all supported Customizing tables in transaction SOBJ.

Manual Retrofit
̈ ̈ ̈

All other objects must be retrofitted manually. The column Critical Retrofit indicates if a transport request contains such objects. The status of these transport requests must be set to Manually Retrofitted.

© SAP 2008

© SAP AG

E2E200

6-100

Syste m De m o

Retrofit

© SAP 2008

© SAP AG

E2E200

6-101

Change Reque st Ma na ge m ent : U nit Ove rvie w Dia gra m
Change Request Management Lesson 1: Change Request Management Overview Lesson 2: Project and Release Management Lesson 3: Change Requests Lesson 4: Maintenance Activities Lesson 5: Integration of Non-ABAP Systems Lesson 6: Tools Lesson 7: Best Practices

© SAP 2008

© SAP AG

E2E200

6-102

Be st Pra c t ic e s

Change Request Management workflows are based on best practices of how to manage short-term changes, maintenance projects, and new implementations.
̈ ̈ ̈ ̈

Urgent corrections for immediate change Normal corrections for mid-term and long-term changes Maintenance projects for housekeeping activities Implementation projects for new implementations

© SAP 2008

© SAP AG

E2E200

6-103

Change Reque st Ma na ge m ent : U nit Ove rvie w Dia gra m
Change Request Management Lesson 7: Best Practices Review Best Practice for Transport Management Use Case: Implementation Complexity

© SAP 2008

© SAP AG

E2E200

6-104

Be st Pra c t ic e : U sa ge of Projec t s

Implementation Projects

Development

Test

Production

Implementation Project Market Campaign Complaint Management Rollout Brazil

Maintenance Project ERP … Maintenance Cycles … Urgent Corrections

© SAP 2008

̈

Advantages: • Comprehensive customizing and development activities are grouped together. • Basis for Release Management

© SAP AG

E2E200

6-105

Be st Pra c t ic e : Pha se Sw it c hing

SAP Solution Manager Project (Maintenance Project)

Development without release

Development with release

Test

Preparation for Go-Live

Go-Live

Maintenance Cycle

Normal corrections Test messages
(during integration test)

Urgent corrections

© SAP 2008

̈

Advantages: • All projects can choose one of the selected Go-Live dates. • All projects that Go-Live together will also go into the test phase together. • Higher stability in production • Changes in production only at certain points

© SAP AG

E2E200

6-106

Be st Pra c t ic e : U rge nt Corre c t ions a re Pre lim ina ry T ra nsport s
Legend:

Urgent correction

Maintenance Activities Urgent Correction Consolidated Transport

Transport buffer

Transport buffer

DEV

QAS

PRD

Regular correction

Test of Regular correction running

Import in correct order to ensure consolidated system state

© SAP 2008

̈

Advantage: • Consolidated transports guarantee consistent project import/deployment.

© SAP AG

E2E200

6-107

Be st Pra c t ise : Four-Syst e m Landsc ape

DEV

QAS

PRE

PRD

© SAP 2008

̈

Best Practice: • Cross-system lock • Critical object approval process

̈

Additional recommendations: • Allocation of systems to phases - Development phase: DEV and QAS (using test transport for unit tests) - Test phase: PRE - Go-Live: PRD • Synchronize Go-Live with set-up of Release Management process: - All projects which are part of the next Go-Live enter the preproduction system together. - All other projects have to stay in the development or unit test environment.

© SAP AG

E2E200

6-108

Be st Pra c t ic e : U sa ge of T e st T ra nsport s

DEV

QAS

PRD

PRD

Legend: Normal Corrections Test Transports (Transport of Copies)

© SAP 2008

̈

Advantages: • Repository objects are locked as long as possible in DEV. • Number of transports in production is reduced. • Transports of copies are periodically imported into QAS but do not follow the transport routes into PRE. • Only the original transport request can reach PRE. • PRE remains a clean environment.

© SAP AG

E2E200

6-109

Be st Pra c t ic e : Aut om a t ed Double M a int enance w it h Re t rofit
Project Landscape

DEV
Retrofit

TST

Maintenance Landscape

CON

QAS

PRD

© SAP 2008

̈

Advantages: • Tool based • Minimized risk through integration in the maintenance project • Logging of the changes • No effort for “double maintenance” • No “forgotten” retrofit

© SAP AG

E2E200

6-110

Be st Pra c t ic e : Cross-Syst e m Obje c t Lock

SAP Solution Manager Cross-System Object Lock Projects

Development System 1 Client1 … Test System Development System 2 Client1 … Production System

© SAP 2008

̈

Advantages: • Identify changes on the same objects in different projects • Minimize risk of downgrades through different go-live dates of changes from different projects

© SAP AG

E2E200

6-111

Be st Pra c t ic e s: Crit ic a l Obje c t Approva l

© SAP 2008

̈

Advantage: • Identify changes to critical objects (prerequisite: knowledge of these objects)

© SAP AG

E2E200

6-112

Change Reque st Ma na ge m ent : U nit Ove rvie w Dia gra m
Change Request Management Lesson 7: Best Practices Review Best Practice for Transport Management Use Case: Implementation Complexity

© SAP 2008

© SAP AG

E2E200

6-113

T ra nsport M a nage me nt Approa ch
SAP Solution Manager

Cycle Transaction Change Request Management Project Cycle PRD

Controlled transports

Task List

QAS

Controlled transports

IT Operator DEV

© SAP 2008

̈

This scenario has the lowest complexity: • Use of the task list instead of TMS to import transports • Use of the task list instead of Workbench Organizer to create transport requests

̈

Advantages: • Projects and phase switching make release management possible • Improved tracking of transports with the change manager

© SAP AG

E2E200

6-114

Ex t e nsion: Change T ra nsa c t ion
SAP Solution Manager

Change Request Management

Developer

PRD

Controlled transports

Tester

Change Transaction

Task List

QAS

Controlled transports

IT Operator

Project Cycle DEV

© SAP 2008

̈ ̈

This scenario is the entry in the CRM-based transaction. In addition to the task list functionality, you may use change documents to manage: • Only urgent corrections • Urgent and normal corrections

̈

Advantages: • Comprehensible documentation of implemented changes and their ramifications • Tracking and audit ability • Consistent handling of urgent corrections

© SAP AG

E2E200

6-115

Ex t e nsion: Approva l Proce ss
SAP Solution Manager

Requester

Change Request Management

Developer

Change Request

Change Manager

PRD

Controlled transports

Tester

Change Transaction

Task List

QAS

Controlled transports

IT Operator

Project Cycle DEV

© SAP 2008

̈ ̈

This is the complete Change Request Management Scenario. Advantages: • All best practices available • Comprehensible documentation of planned and implemented changes and their ramifications • Improved efficiency of Change Management projects • Minimized business disruptions • Tracking and audit ability

© SAP AG

E2E200

6-116

Ex t e nsion: Se rvic e De sk
SAP Solution Manager
Service Desk
Feedback

Service Desk Employee

Service Message

Requester

Change Request Management

Developer

Change Request

Change Manager

PRD

Controlled transports

Tester

Change Transaction

Task List

QAS

Controlled transports

IT Operator

Project Cycle DEV

© SAP 2008

̈

This extension bridges the gap between the incident or problem management process and the change or release management process.

© SAP AG

E2E200

6-117

Change Reque st Ma na ge m ent : U nit Sum m a ry

You should now be able to:
̈ ̈ ̈ ̈

Define the Change Request Management business process Explain how to use the SAP Solution Manager system for the Change Request Management scenario Describe the various elements of Change Request Management as part of SAP Solution Manager Describe SAP’s best practices in transport management which are implemented in the SAP Solution Manager

© SAP 2009

© SAP AG

E2E200

6-118

Exercises
Unit: Lesson: Change Request Management Change Requests

At the conclusion of this exercise, you will be able to: • Create and approve change requests • Provide documentation in a change request

TT4 is the SAP Solution Manger system which contains all information about the system landscape. TT5 is a satellite system which is managed by TT4.

6-1

Create a change document. Describe your requirements. In this part you are acting as a requester. 6-1-1 6-1-2 6-1-3 Log on to the SAP Solution Manager system. Enter the transaction code SOLMAN_WORKCENTER in the command field and choose Enter. In the work center select the Change Management tab and choose Change Requests. In the Common Tasks menu on the left hand side, choose New Change Request. You are on the order processing screen now. Please maintain all information for your change request. Maintain the Short Description and Partner functions. Enter your user as Requestor and Change Manager. Enter the business partner 32 as the Soldto-Party. Enter the production system that you want to make the change for. Select IBase 1 and the component 34 “Simulation of PRD (803)”. Maintain a description of the change in the text box. Save the change document and go back. If information is missing, maintain the missing data and save the change document again. Write down the number of the change request. Change request number: __________________________________

6-1-4

6-1-5

6-1-6 6-1-7

© SAP AG

E2E200

6-119

6-2

Find the change document and approve it. In this part you are acting as a Change Manager. 6-2-1 6-2-2 Log on to the system and navigate to the Change Management work center. At the work center you can find the new change document. In the Change Requests tab, you can find the change request with a filter on the change request number. Open the document by clicking on the document ID. Go into change mode. Classify the change document as a Normal Correction and save. Approve the change request and save. When a dialog box appears that asks you for a Task List/Maintenance Cycle, please choose the maintenance cycle that was created by your instructor. Note: In general, operational activities like triggering the creation of a change document are always linked to a certain status of the current document. This ensures consistency between the administrative view and the technical execution. 6-2-7 Write down the change document number. You can find it when you choose Document Flow .

6-2-3 6-2-4 6-2-5 6-2-6

Change document number: __________________________________

© SAP AG

E2E200

6-120

Exercises
Unit: Lesson: Change Request Management Maintenance Activities

At the conclusion of this exercise, you will be able to: • Process the developer’s tasks with the help of a normal correction • Pass the normal correction to the tester

TT4 is the Solution Manger system that contains all information about the system landscape. TT5 is a satellite system that is managed by TT4.

6-3

Find the change document. Take the Change Document in development. In this part you are acting as a developer. 6-3-1 Log on to the SAP Solution Manager system and open the Change Management work center. Find the change document (normal correction) via selection. On the table on the right-hand side, you should find the change document that you created in the last exercise. If there are many documents listed, you can set a filter to search the document ID. Click on the document ID to navigate to the change document. 6-3-3 6-3-4 Go into change mode. Verify that the IBase component equals the IBase component of the production system (34 “Simulation of PRD (803)”) and change it manually if necessary. Note: The IBase component is used to calculate the maintenance system. Therefore, it is crucial that you use the correct IBase component here. 6-3-5 Set the change document to In Development and save the document.

6-3-2

© SAP AG

E2E200

6-121

6-3-6

Create a transport request and save the document. Choose the development/maintenance system by double-clicking on it. In the dialog box, check if your user is the owner of the transport request and assigned to the tasks. For this exercise, you need a customizing transport request. You can de-select the workbench request.

6-3-7 6-3-8 6-3-9

Log on to the development system. Maintain the Table/View T009T in transaction SM30. Search for your entry and change the description.

6-3-10 Save your entry. When prompted for a transport document, choose your own customizing task by choosing the Own Documents button. Your customizing transport contains the number of your change document in its description. Write down the transport request number. Transport request number: ____________________________________ 6-3-11 After saving your entry, go to transaction SE09 in the development system. Choose the customizing task that refers to your change document number and release it. Note: Do not release the transport request; this will be done by SAP Solution Manager in the background. Furthermore, you are not allowed to release the transport document because the CTS status switches do not authorize you to do so. 6-3-12 Navigate back to the change document. 6-3-13 Complete the development and save. The status is set to To be tested. 6-3-14 Leave the document and the monitor list.

© SAP AG

E2E200

6-122

Exercises
Unit: Lesson: Change Request Management Reporting

At the conclusion of this exercise, you will be able to: • Use Change Management reporting to find change requests, transport requests, and transported customizing objects

TT4 is the Solution Manger system that contains all information about the system landscape. TT5 is a satellite system that is managed by TT4.

6-4

Search for a certain Change Request. 6-4-1 Log on to the SAP Solution Manager system, call transaction SOLMAN_WORKCENTER, and choose the Change Management tab. On the left-hand side, open the Reports menu. On the right-hand side, choose the Report link. In the Result List screen area, choose Header, Project, Task List, and Transports via the F4 help button. Open the Transaction Data screen area. In the Document Number field, fill in the number of your change document, which you wrote down in the Change Requests exercise. Execute your selection. Check your results and find the transport request. Write down the transport request number:

6-4-2

6-4-3 6-4-4

6-4-5 6-4-6

© SAP AG

E2E200

6-123

6-5

Search for a change request that contains a certain transport request and display the transported objects. 6-5-1 Log on to the SAP Solution Manager system, call transaction SOLMAN_WORKCENTER, and choose the Change Management tab. On the left-hand side, open the Reports menu. On the right-hand side, choose the Report link. In the Result List screen area choose Header, Project, Task List, Transports, and Objects via the F4 help button. Open the Transport Request screen area. In the Document/Task field, fill in the number of the transport request you wrote down in the step before. Execute your selection. Check your results and find the object. Write down the name of the object. The name of the object is case-sensitive

6-5-2

6-5-3 6-5-4

6-5-5 6-5-6

6-6

Search for a change request that contains a certain object. 6-6-1 6-6-2 Navigate to Change Management reporting. In the Result List screen area, choose Header, Project, Task List, Transports, and Objects via the F4 help button. Open the Transport Objects screen. In the Table Name field, enter T009T. In the Table Keys field, fill in your object from the exercise before. The key fields are case-sensitive. Execute your selection. Check your results.

6-6-3 6-6-4

6-6-5 6-6-6

© SAP AG

E2E200

6-124

Solutions
Unit: Lesson: Change Request Management Change Requests

6-1 Create a change document. Describe your requirements. In this part you are acting as a requester. 6-1-1 Log on to the SAP Solution Manager system. Enter the transaction code SOLMAN_WORKCENTER in the command field and choose Enter. 6-1-2 In the work center select the Change Management tab and choose Change Requests.

6-1-3

In the Common Tasks menu on the left hand side, choose New Change Request. You are on the order processing screen now. Please maintain all information for your change request. Maintain the Short Description and Partner functions. Write a short description for the change and search for your user (F4 help) in the partner functions Requestor and Change Manager. Enter the business partner 32 as the Sold-to-Party. Search for the production system that you want to make the change for. Press the F4 Help for the Component field. In the dialog box, enter installed base 1 and confirm. Select component 34 TT5 Simulation of PRD (803). Maintain a description of the change in the text box. Go to the text maintenance box and select text type Description of change. Save the change document and go back. If information is missing, maintain the missing data and save the change document again
E2E200 6-125

6-1-4

6-1-5

6-1-6

6-1-7
© SAP AG

6-2

Find the change document. Take the change document into process. In this part you are acting as a change manager. 6-2-1 Log on to the system. Call transaction SOLMAN_WORKCENTER. Select Change Documents and choose Show as change manager. 6-2-2 In the work center, you can find the new change document. In the Change Requests tab, you can find the change request with a filter on the change request number.

6-2-3 6-2-4 6-2-5

Open the document by clicking on the document ID. Go into change mode by choosing .

Classify the change document as a Normal Correction. Open the F4 help on the Subject field. Choose Normal Correction (Maintenance). Save your settings. Approve the change request and save. Choose the Actions button and then choose Authorize Change Document.

6-2-6

Choose Save. The change document for the normal correction is generated. When a dialog box appears that asks you for a Task List/Maintenance Cycle, please choose the maintenance cycle that was created by the instructor. Remark: In general, operational activities like triggering the creation of a change document are always linked to a certain status of the current document. This ensures consistency between the administrative view and the technical execution. 6-2-7 Write down the change document number. Choose Document Flow to access the number.

Leave the change document via the Back arrow (F3) and return to the work center. The document status is now Authorized.

© SAP AG

E2E200

6-126

Solutions
Unit: Lesson: Change Request Management Maintenance Activities

6-3

Find the change document. Take the change document in development. In this part you are acting as a developer. 6-3-1 Log on to the SAP Solution Manager system and open the work center with transaction SOLMAN_WORKCENTER. Select the Change Management tab. Find the change document (normal correction) via selection. Choose Change Documents on the right-hand side. If your user is already involved in urgent and normal corrections, you must select Normal Correction in the Change Documents menu.

6-3-2

On the table on the right-hand side, you should find the change document that you created in the last exercise. If there are many documents listed, you can set a filter to search the document ID.

Click on the document ID to navigate to the change document (Fast Entry view). 6-3-3 Go into change mode.

© SAP AG

E2E200

6-127

6-3-4

Verify that the IBase component equals the IBase component of the production system (34 Simulation of PRD (803)) and change it manually if necessary. Note: The IBase component is used to calculate the correct maintenance system. Therefore, it is crucial that you use the correct IBase component here.

6-3-5

Choose Actions, choose Set to ‘In Development’, and save the document. Choose Actions and choose Create Transport Request. Save the document. Choose the development/maintenance system by double-clicking.

6-3-6

Check in the dialog box if your user is the owner of the transport request and assigned to the tasks. For this exercise, you need a customizing transport request. You can de-select the workbench request.

Create the transport request. 6-3-7 Choose Actions and choose System Logon to log on to the development system via a trusted RFC connection. Call transaction SM30. In the Table/View field, enter T009T. Choose .

6-3-8

© SAP AG

E2E200

6-128

6-3-9

Search for your user’s entry and change the description.

6-3-10 Save your entry. When prompted for a transport document, choose your own customizing task via the Own Documents button. Your customizing transport contains the number of your change document in its description. Write down the transport request number. Transport request number:____________________________________ 6-3-11 After saving your entry, go to transaction SE09 in the development system. Choose . Navigate to your transport request and select . the task below the transport request. Release the task by choosing

Note: Do not release the transport request, as this will be done by SAP Solution Manager in the background. Furthermore, you are not allowed to release the transport document because the CTS status switches do not authorize you to do so. 6-3-12 To navigate back to the change document, choose Back (F3) twice, and then choose Exit (Log off). You are now back in the change document. 6-3-13 Choose Actions and then choose Complete Development. Choose Save. The status is set to To be tested. 6-3-14 Leave the document and the monitor list.

© SAP AG

E2E200

6-129

Solutions
Unit: Lesson:
6-4

Change Request Management Reporting

Search for a certain Change Request. 6-4-1 Log on to the SAP Solution Manager system, call transaction SOLMAN_WORKCENTER, and choose the Change Management tab. On the left-hand side, open the Reports menu.

On the right-hand side, choose the Report link.

6-4-2

In the Result List screen area, choose Header, Project, Task List, and Transports via the F4 help button. Open the Transaction Data screen area by choosing .

6-4-3 6-4-4

In the Document Number field, fill in the number of your change document, which you wrote down in the Change Requests exercise. Execute your selection Choose or press F8. Check your results and find the transport request. Write down the transport request:

6-4-5

6-4-6

© SAP AG

E2E200

6-130

6-5

Search for a change request that contains a certain transport request and display the transported objects.. 6-5-1 Log on to the SAP Solution Manager system and call transaction SOLMAN_WORKCENTER. Choose the Change Management tab. On the left-hand side, open the Reports menu.

On the right-hand side, choose the Report link.

6-5-2

In the Result List screen area, choose Header, Project, Task List, Transports, and Objects via the F4 help button.

6-5-3 6-5-4

Open the Transport Request screen area by choosing

.

In the Document/Task field, enter the number of the transport request you wrote down in the step before. Execute your selection. Choose or press F8. Check your results and find the object. Write down the object. The object name is case-sensitive.

6-5-5

6-5-6

© SAP AG

E2E200

6-131

6-6

Search for a change request that contains a certain object. 6-6-1 Navigate to Change Management reporting. In the Change Management work center, choose the Change Management tab. On the left-hand side, open the Reports menu.

On the right-hand side, choose Report.

6-6-2

In the Result List screen area, choose Header, Project, Task List, Transports, and Objects via the F4 help button.

6-6-3 6-6-4

Open the Transport Objects screen area by choosing

.

In the Table Name field, enter T009T. In the Table Keys field, enter your object from the exercise before. The table key is case-sensitive. Execute your selection. Choose or press F8. Check your results.

6-6-5 6-6-6

© SAP AG

E2E200

6-132

M a inte na nc e M anagem ent

Unit 1 Introduction to E2E Change Control Management Unit 2 Transport Strategies Unit 3 Enhanced Change and Transport System Unit 4 Solution Documentation Unit 5 Quality Gate Management Unit 6 Change Request Management Unit 7 Maintenance Management Unit 8 Test Management Unit 9 Change Diagnostics

© SAP 2009

© SAP AG

E2E200

7-1

M a inte na nc e M anagem ent : U nit Obje c t ive s

At the end of this unit, you will be able to:
̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈

Understand the SAP Maintenance Strategy Describe all types of support items delivered by SAP Explain the support package stack strategy Describe the enhancement package concept Explain the role of SAP Solution Manager in the maintenance process Know the software lifecycle management tools to implement patches and find information on current patch levels Perform an upgrade or change impact analysis with the custom development management cockpit Execute side effect reporting for a Support Package queue Find and implement HotNews as urgent correction Know SAP’s best practice recommendations for maintenance management

© SAP 2009

© SAP AG

E2E200

7-2

M a inte na nc e M anagem ent : U nit Ove rvie w Dia gra m
Maintenance Management Lesson 1: SAP Maintenance Strategy Lesson 2: Types of Maintenance Lesson 3: SAP Enhancement Packages Lesson 4: Maintenance Optimizer Lesson 5: Software Lifecycle Management Tools Lesson 6: Maintenance Certificate Lesson 7: Upgrade / Change Impact Analysis Lesson 8: Best Practice Recommendations

© SAP 2009

© SAP AG

E2E200

7-3

M a inte na nc e M anagem ent : U nit Ove rvie w Dia gra m
Maintenance Management Lesson 1: SAP Maintenance Strategy SAP Release and Maintenance Strategy Support Package Stacks

© SAP 2009

© SAP AG

E2E200

7-4

SAP Re le a se a nd M a int enance St ra t e gy Ex a mple SAP ERP

SAP ERP 6.0**

Mainstream Maintenance

Ext. Maint. (+ 2%)*

Cust.-Spec. Maint.

mySAP ERP 2004

Mainstream Maintenance

Ext. Maint. (+ 2%)*

Ext. Maintenance (+ 4%)*

Customer-Specific Maintenance

New 7-2 maintenance strategy for SAP ERP 6.0:
̈

Mainstream maintenance extension from March 2013 to December 2015 Extended maintenance offered for two years to December 2017

SAP R/3 Enterprise 47x110, 47x200

Mainstream Maint. Mainstream Maint.

Ext. Maint. (+ 2%)*

Ext. Maintenance (+ 4%)*

Customer-Specific Maintenance Customer-Specific Maintenance

̈

Extended maintenance (no add. fee, included in SAP Enterprise Support contract)

SAP R/3 4.6C

Ext. Maint. (+ 2%)*

Ext. Maintenance (+ 4%)*

Customer-Specific Maintenance Customer-Specific Maintenance

Extended maintenance (no add. fee, included in SAP Enterprise Support contract)

SAP R/3 3.1I – 4.6B

Ext. M. (+ 4%)*

Customer-Specific Maintenance

As of January 01, 2009, extended maintenance for SAP R/3 4.6C and SAP R/3 Enterprise is included in SAP Enterprise Support and extended by one year Dec Dec 2016 2017 Mar

Dec

Dec Mar

Dec

Dec

Mar

Jun

Mar

Mar

2006

2007

2008

2009

2010

2011

2012

2013

2014

2015

* Overall payment is SAP support fee plus additional fee of 2% or 4% of the maintenance base per year. ** SAP ERP 6.0 is the application release formerly known as mySAP ERP 2005.
© SAP 2009

This strategy is also valid for all industry-specific add-on applications and SAP enhancement packages for SAP ERP based on the releases above.

̈

5-1-2 maintenance strategy: • The 5-1-2 maintenance strategy introduced in 2004 is a set of rules (for details, refer to http://service.sap.com/maintenance å Maintenance strategy). It is valid for application releases of release type “standard” that are based on SAP NetWeaver 2004 or higher. Older releases do not follow the 5-1-2 rules. • Under this strategy, for core application releases (SAP ERP, SAP CRM, SAP SRM, SAP SCM, SAP PLM), SAP offers 5 years of mainstream maintenance; 1 year of extended maintenance at an additional 2% fee; and another 2 years of extended maintenance at an additional 4% fee per year. Thereafter, the releases will enter customer-specific maintenance. ̈ 7-2 maintenance strategy • The 7-2 maintenance strategy introduced in 2008 is a set of rules (for details, refer to http://service.sap.com/maintenance å Maintenance strategy). It is valid for application releases of release type “standard” starting with the core application releases shipped with SAP Business Suite in November 2008, and for SAP ERP 6.0 and SAP NetWeaver 7.0. • Under this strategy, for core application releases (SAP ERP, SAP CRM, SAP SRM, SAP SCM, SAP PLM), SAP offers 7 years of mainstream maintenance and 2 years of extended maintenance at an additional 2% fee per year. Thereafter, the releases will enter customer-specific maintenance. ̈ In both cases, the following rules apply: • Maintenance for an SAP NetWeaver main release is synchronized with the maintenance of the core application releases that build upon it. • Maintenance for add-on application releases is synchronized with the maintenance of the underlying application releases. If there are several releases of an add-on for the same underlying release, only the latest add-on release will be supported to the end of mainstream maintenance and during extended maintenance for the underlying release. • Exceptions to the maintenance strategy rules: Applications such as SAP Business One, or composite applications, as well as some other applications, may have a shorter mainstream maintenance duration, and extended maintenance is not offered. Special rules apply to content shipments.
© SAP AG E2E200 7-5

SAP Busine ss Suit e 7 Sync hronisa t ion of Enhance m ent Pa ck age s
2006 EhP1 ERP 6.0 CRM 7.0 PLM 7.0 SCM 7.0 SRM 7.0 (Selected) enhancements* across the Suite End-to-end network collaboration Value chain responsiveness Logistics for global networks … Business Suite release strategy Synchronized Suite release Adaptive supply chain & manfing Virtual workforce management Service chain for asset-intensive industries ... Holistic performance and risk management Next generation online communities for business partners Flexible organization management … 2007 EhP2 EhP3 2008 EhP4 2009 EhP x … 2010

* Topics subject to change
© SAP 2009

Enhancement Packages across the Suite

̈

Business Suite: The key goal is minimized downtime for maintenance (including support and enhancement packages). The introduction of enhancement packages serves the goal to keep support packages free from any functional additions and changes and to allow the incremental activation of business functions – both should help to reduce testing efforts. Also the technical processes are optimized towards less downtime. Additional hardware resources may be needed to leverage these investments, but dynamic capacity allocation should make this feasible. More information about the SAP Business Suite 7 can be found at: http://service.sap.com/solutions and http://service.sap.com/businesssuite.

̈

© SAP AG

E2E200

7-6

Produc t Ava ila bilit y M a t rix

See next screen

© SAP 2009

̈

The technical and release planning information on SAP product versions are directly displayed in the Product Availability Matrix on SAP Service Marketplace at http://service.sap.com/pam. The Product Availability Matrix also offers quick links and additional information area for release planning information on SAP components for quick reference.

̈

© SAP AG

E2E200

7-7

Produc t Ava ila bilit y M a t rix H ow t o use ?

Navigation tree

Quick Search

Short documentation

general availability date / end of maintenance date

© SAP 2009

̈

The Product Availability Matrix bundles technical and release planning information on SAP components for quick reference. You will find information on the availability of SAP component releases (product versions), maintenance end dates, and upgrade paths, as well as technical release information (DB platforms, JSE platforms, operating systems, languages, countries, etc.). An SAP component release is structured into instances. An instance is a bundle of technically dependent software component versions to be installed on one single logical system. The technical release information is displayed per instance. Example: The product version SAP NetWeaver 7.0 is structured into the instances Application Server ABAP, Application Server Java, Enterprise Portal, Frontend, etc. The Application Server ABAP itself consists mainly of the software component versions SAP BW 7.00, SAP ABA 7.00, SAP BASIS 7.00 and SAP kernel 7.00 32-BIT (or a newer downward compatible one). Choose one of the other tab strips to find additional technical release information. You will see a second row with one or more tab strips, depending on the complexity of the SAP component. These tab strips name the system instances within the SAP component for which a given type of release information is relevant. As each system instance carries several sets of release information, you may see the same system instance under operating systems as well as under web browsers, for example. Note that a type of release information entitled xyz platform always refers to a combined release information of xyz and an operating system. For example, a database platform is a combination of database version and operating system version, and a web browser platform is a combination of a web browser version and an operating system version.

̈

© SAP AG

E2E200

7-8

Syste m De m o

Product Availibility Matrix

© SAP 2009

© SAP AG

E2E200

7-9

M a inte na nc e M anagem ent : U nit Ove rvie w Dia gra m
Maintenance Management Lesson 1: SAP Maintenance Strategy SAP Release and Maintenance Strategy Support Package Stacks

© SAP 2009

© SAP AG

E2E200

7-10

M a inte na nc e M anagem ent Be ne fits of Support Pa c ka ge s
General recommendation
̈

Besides single corrections through SAP notes that usually are applied in a reactive mode, it is recommended to set up a proactive maintenance concept for the SAP systems. The import of SAP Support Packages should be scheduled on a regular basis as part of the Maintenance Calendar. Regular import of SAP Support Packages offers advantages like:
̈ ̈ ̈ ̈

Proactive solutions of known problems Basis for a fast reaction on problems: Avoid the need to implement many single notes or even Support Packages in order to be able to implement a single note to solve a problem Troubleshooting is easier on a current Support Package level Besides proactively avoiding potential issues, a regular import of Support Packages also helps to ensure agility for implementing new functions (on urgent business requirements) – these functions might have dependencies to new EhPs and/or SPs. Prerequisite for the implementation of Enhancement Packages

© SAP 2009

© SAP AG

E2E200

7-11

M a inte na nc e M anagem ent SAP Support Pa c ka ge St a ck s
Recommendation: Implement SP Stacks (instead of single SPs).
̈

Appl. ABA Basis Kernel

SAP Support Package Stacks (SP Stacks) ? SAP released sets of Support Packages per product. Shipment dates available at http://service.sap.com/sp-stacks Support Packages & patches of SP Stacks must be used in the given combination, other combinations only apply for exceptional cases Higher quality and ensured compatibility of included Support Packages Simplified download of included Support Packages from a one page summary

Appl. ABA Basis Kernel

̈

̈ ̈

Appl. ABA Basis Kernel

Q1

Q2

Q3

Q4

t

© SAP 2008

̈

Support Package Stacks: • Contain the optimal combination of Support Package and patch statuses for the individual components at the given time • Reduce the complexity of Support Package application • Increase quality and transparency

̈ ̈ ̈

SP Stacks are already tested at SAP SP Stacks are well known at SAP å SAP recommendation: Apply a Support Package Stack as a whole to update an SAP system

© SAP AG

E2E200

7-12

Support Pa ck age St a ck Schedule

© SAP 2009

̈ ̈ ̈

On the Service Marketplace, there is a support package stack calendar which shows the planned availablity of the support package stacks for the different products. You can use this calendar to schedule your maintenance projects. Products which are new or still in the ramp-up phase have a high support package stack frequency (such as monthly). Older and stable releases only deliver Support Package Stacks twice a year.

© SAP AG

E2E200

7-13

Syste m De m o

Support Package Stacks

© SAP 2009

© SAP AG

E2E200

7-14

M a inte na nc e M anagem ent : U nit Ove rvie w Dia gra m
Maintenance Management Lesson 1: SAP Maintenance Strategy Lesson 2: Types of Maintenance Lesson 3: SAP Enhancement Packages Lesson 4: Maintenance Optimizer Lesson 5: Software Lifecycle Management Tools Lesson 6: Maintenance Certificate Lesson 7: Upgrade / Change Impact Analysis Lesson 8: Best Practice Recommendations

© SAP 2009

© SAP AG

E2E200

7-15

M a inte na nc e M anagem ent : U nit Ove rvie w Dia gra m
Maintenance Management Lesson 1: SAP Maintenance Strategy Lesson 2: Types of Maintenance ABAP Corrections Java Corrections

© SAP 2009

© SAP AG

E2E200

7-16

T ype s of Corre c t ions

Corrections / Changes
New Functionality
̈

ABAP
Enhancement Packages

Java

Standard correction process Emergency correction process

̈ ̈ ̈

Support Package Stack SAP Kernel Patch ABAP Support Package
̈ ̈

Java Support Package Java Support Package Patch Java Single Patch (Fix)

̈

SAP Note Correction (ABAP)

̈

© SAP 2009

̈

Standard correction process: • Support Package Stack: • Description: The Support Package Stack is a list of ABAP and Java Support Packages for all software components (SC) included in SAP NetWeaver. It is used to bring each Software Component of SAP NetWeaver to a defined SP level. • ABAP Support Package: • Description: ABAP Support Packages contain quality improvements for the SAP system, or make necessary adjustments due to legal changes, for example. The objects affected are replaced in your system.

• Java Support Package: • Description: Java Support Packages are used to ship correction levels of software components. They correspond to the ABAP Support Packages. ̈ Emergency correction process: • • • • SAP Note Correction (ABAP): Description: SAP Note Corrections contain single ABAP corrections. Java Support Package Patch: Description: A Java Support Package patch contains corrections for the Java Software Components. Java Support Package patches are normally created and released on demand. They correspond to a SAP Note that describes the same correction. • Java Single Patch: • Description: A full version of a single Development Component. Java single patches correspond to a SAP Note that describes the corresponding prerequisites and dependencies.
E2E200 7-17

© SAP AG

Component M ode l and M a inte na nc e (ABAP)

Products

P1

P2

Release Support Package

Software Components

S1

S2

(in ABAP, not the complete SC is shipped - only the changed objects)

Packages
D4

D6

D8

D11

D5

D7

D9

D10

Objects

O1

O2

O3

Notes

© SAP 2009

̈

The SAP component model for ABAP objects is shown above: „ Products are updated by installations and upgrades. „ Software components are updated by Support Packages and add-ons. „ Single objects can be updated by SAP Notes.

© SAP AG

E2E200

7-18

SAP N ot e in t he Se rvic e M a rke t pla ce

© SAP 2009

̈

SAP Notes: • Describe how to remove known errors in the SAP system. They include a description of the following: - The symptoms of the error - The root cause of the error - The release and Support Package status for which they are valid • They contain (depending on the type of error): - Workarounds - Descriptions of how to correct the source code (correction instructions) - Links to Support Packages that correct the problem • Correction instructions change single lines of coding • SAP Notes with correction instructions are implemented with the Note Assistant in the development system, and then forwarded by transports to production.

© SAP AG

E2E200

7-19

Corre c t ion I nst ruc t ion: Changing a Func t ion M odule
Old version
FUNCTION test_package_attributes. *"---------------------------------------------------------------------*"*“Local Interface: *" IMPORTING *" VALUE(IV_PATCH) LIKE PAT03-PATCH *" EXPORTING *" VALUE(ES_PAT03) LIKE PAT03 STRUCTURE PAT03 *" TABLES *" T_PAT07 STRUCTURE PAT07 *" EXCEPTIONS *" NOTHING_FOUND *"---------------------------------------------------------------------SELECT * FROM pat03 INTO es_pat03 WHERE patch = iv_patch. ENDSELECT. IF sy-subrc <> 0. RAISE nothing_found. ENDIF. SELECT * FROM pat07 INTO TABLE t_pat07 WHERE patch = iv_patch. ENDFUNCTION.

New version
FUNCTION test_package_attributes. *"---------------------------------------------------------------------*"*“Local Interface: *" IMPORTING *" VALUE(IV_PATCH) LIKE PAT03-PATCH *" EXPORTING *" VALUE(ES_PAT03) LIKE PAT03 STRUCTURE PAT03 *" TABLES *" T_PAT07 STRUCTURE PAT07 *" T_PAT08 STRUCTURE PAT08 *" EXCEPTIONS *" NOTHING_FOUND *"---------------------------------------------------------------------SELECT * FROM pat03 WHERE patch = iv_patch. ENDSELECT. IF sy-subrc <> 0. RAISE nothing_found. ENDIF. MOVE-CORRESPONDING pat03 TO es_pat03. SELECT * FROM pat07 INTO TABLE t_pat07 WHERE patch = iv_patch. SELECT * FROM pat08 INTO TABLE t_pat08 WHERE patch = iv_patch. CALL SCREEN 0100 STARTING AT 14 2. ENDFUNCTION.

© SAP 2009

̈ ̈

Objects that can be changed with the Note Assistant: New Objects can be created • CLAS: Global ABAP Classes (ABAP-OO) • INTF: Interfaces (ABAP-OO) • REPS: ABAP programs and includes • FUNC: Function modules with interface and all attributes • DYNP: Screens with all attributes • TYPD: Type Pools • WAPP: Business Server Pages • SMIM: MIME objects (only with small data volume) • IAMU, IARP, IASP, IATU: Internet transaction server • ENH*: Enhancement objects

̈

Objects which are not supported: • Creating an entire function group • BSP applications • Deleting an object • Changes to tabular content (R3TR TABU) • Language dependent texts • DDIC objects

© SAP AG

E2E200

7-20

N ot e Brow se r

> The

Note Browser gives you a list of all SAP Notes notes according to implementation status SNOTE å GOTO å SAP Note Browser

> Select

> Transaction

© SAP 2009

̈ ̈ ̈

The Note Browser gives you a list of all SAP Notes which are imported into an ABAP system. Select all notes with the implementation status Completely implemented. Transaction SNOTE å GOTO å SAP Note Browser

© SAP AG

E2E200

7-21

ABAP Support Pa c ka ge s

http://service.sap.com/swdc
© SAP 2009

̈

ABAP Support Packages: • All note corrections within a certain time period are bundled into a support package. • A support package contains full objects, not just single lines of coding. • Support packages are delivered for each software component. • Support packages are incremental. That means that all support packages of a software component must be implemented. • Support Packages contain all objects that were changed in a certain time period.

© SAP AG

E2E200

7-22

V e rsion Informa t ion of ABAP Syst e m s Syste m å St a t us

© SAP 2009

̈

The version information of ABAP-based systems can be accedd through the menu bar: System å Status å (Button) “Component information“

© SAP AG

E2E200

7-23

M a inte na nc e M anagem ent : U nit Ove rvie w Dia gra m
Maintenance Management Lesson 1: SAP Maintenance Strategy Lesson 2: Types of Maintenance ABAP Corrections Java Corrections

© SAP 2009

© SAP AG

E2E200

7-24

Component M ode l and M a inte na nc e (J AV A)

Products

P1

P2

Release Support Package

Software Components

S1

S2

(in JAVA, the complete SC is Shipped. Packages are cumulative)

Packages
D4

D6

D8

D11

(Fix)
D5 D7 D9 D10

Objects

O1

O2

O3

© SAP 2009

̈

Software maintenance is organized into three tiers: • Products are installed or undergo an upgrade to a new release. A release is a full delivery of software components that provide new functions (and possibly user interfaces) or improvements. Installation and upgrade are not performed with CMS resources. • A Support Package (SP) is (unlike ABAP) a full delivery of one (or more) software component(s) and contains a number of fixes. The usual file format of an SP is the SCA format. Support Packages are implemented using the Java Support Package Manager Tool (JSPM). JSPM distinguishes between systems that are under NWDI control and systems that are not under NWDI control. Java-based Support Packages are cumulative. Update from a lower SP Stack to a higher SP Stack only requires the import of the appropriate target SP Stack. • Fixes are full deliveries of a development component that allow a quick error correction, before the complete SP is available. The usual file format is the SDA format. - Hint: SAP usually does not yet deliver fixes. The smallest unit of delivery of SAP software is a Support Package. • Development Objects (DOs): - Stored as versioned files in the source repository (DTR) - Example: Web Dynpro view, table definition, Java source file

© SAP AG

E2E200

7-25

J a va Support Pa ck age s

Java Support Packages:
̈ ̈ ̈ ̈

Support packages are delivered for software components. They are shipped as software component archives (SCA). Software component archives contain several software development archives. Support packages are delivered at regular intervals as part of a Support Package Stack according to a schedule. Java Support Packages are cumulative. That means each Support Package contains all objects in a software component.
software component archives (SCA) SP20 SDA 1 SP18 SDA 2 SP20 SDA 3 SP16 SDA 4 SP17 SDA 5 SP20

© SAP 2009

© SAP AG

E2E200

7-26

J a va Fix e s

̈ ̈ ̈ ̈ ̈

The smallest unit that can be delivered is the software development component, which is shipped in a software development archive (SDA). A fix corrects a single error. SDA file fixes are used for preliminary correction in urgent cases. Published on demand as attachment in SAP Notes or customer messages Only apply fixes with guidance from SAP’s support. Apply the next higher Support Package Stack instead.

software component archives (SCA) SP20 SDA 1 SP18 SDA 2 SP20 SDA 3 SP16 SDA 4 SP17 SDA 5 SP20

SDA 5 Fix

Fix

© SAP 2009

̈ ̈ ̈ ̈

Java Objects are grouped in development components. Development components are grouped in software components. The smallest unit that can be delivered is a complete development component (fixes). Fixes should only be applied in emergency situations and with guidance from SAP Support.

© SAP AG

E2E200

7-27

J a va Pa t c he s

Java Patches (as of NetWeaver 2004s):
̈ ̈ ̈

Like a regular Support Package, a patch contains a full software component and is delivered as software component archive (SCA). A patch contains the latest regular Support Package plus all fixes that were published since the release of the latest Support Package. It is published on demand.

Software component archive, SP20, Patch 1 SDA 1 SP18 SDA 2 SP20 SDA 3 SP16 SDA 4 SP17 SDA 5 Fix

Patch / Patched SP

© SAP 2009

© SAP AG

E2E200

7-28

J a va Pa t c he s a re de sc ribe d in SAP N ot es

SAP Notes describe single bugs which are fixed in patches.

© SAP 2009

̈

This note describes a problem which is solved by support packages or patches.

© SAP AG

E2E200

7-29

SAP Se rvic e M a rk e t pla ce

Java Patches and Support Packages are published on the SAP Service Marketplace, quick link /swdc

© SAP 2009

̈ ̈ ̈

Java Support Packages and Patches are delivered as full Software Component Archives. Support Packages have patch level 0. Patches have a higher patch level. Patches are always created for the highest Support Package Level. They are also created for lower Support Package Levels, if required. If you click on “Info“ of a patch, you see a list of notes that describe the individual corrections, which are solved with the patch. For Support Packages, there is a summary note which describes all corrections in the Support Package.

© SAP AG

E2E200

7-30

V e rsion Informa t ion of J a va Syst e m s Component I nfo
http://<hostname>:<port>/sap/monitoring/ComponentInfo

Release 7.00 SP Level 10 Patch 1

© SAP 2009

̈ ̈

The version information of a JAVA-based system can be seen in the Component Information http://<hostname>:<port>/sap/monitoring/ComponentInfo. For each software component, the version string shows release, Support Package, and patch level.

© SAP AG

E2E200

7-31

Solut ion M a nage r Workc ent e r ? Ge t t ing t he Curre nt Support Pa c ka ge Le ve l
SOLMAN_WORKCENTER å System Landscape Management å System Management

ABAP components Java components

© SAP 2009

̈

Go to transaction SOLMAN_WORKCENTER å System Landscape Management å System Management to display the current Support Package Level of the software components.

© SAP AG

E2E200

7-32

T ype s of Cont ent Correc t ions in SAP Web AS

SAP Web AS ABAP SMSY
Release

SAP Web AS JAVA SMSY
Release

Support Package Stack

Support Package Stack

Support Packages

Support Packages

SAP Notes

Patches

SNOTE
SAP Hotfix

Software Deployment Manager/ JSPM

© SAP 2009

̈ ̈ ̈

To find out the current Support Package Level of all software components running on the Java system see: http://<host>:<http_port>/sap/monitoring/SystemInfo å Software Components å all components Or with transaction SOLMAN_WORKCENTER å System Landscape Management å System Management.

© SAP AG

E2E200

7-33

Ex e rc ise

Support Package Stacks / Find Version Information

© SAP 2009

© SAP AG

E2E200

7-34

M a inte na nc e M anagem ent : U nit Ove rvie w Dia gra m
Maintenance Management Lesson 1: SAP Maintenance Strategy Lesson 2: Types of Maintenance Lesson 3: SAP Enhancement Packages Lesson 4: Maintenance Optimizer Lesson 5: Software Lifecycle Management Tools Lesson 6: Maintenance Certificate Lesson 7: Upgrade / Change Impact Analysis Lesson 8: Best Practice Recommendations

© SAP 2009

© SAP AG

E2E200

7-35

Diffe rent Proc e sse s for M a int enance a nd N e w Func t iona lit y
Bug Fixes
̈ ̈

Support existing processes Proactive solution of known bugs
̈

SAP Support Packages
Implemented on a regular basis ̈ No changes to existing processes ̈ No user acceptance test ̈ Limited testing

Legal Changes
̈ ̈

Support existing processes Proactive solution of known bugs

SAP Enhancement Packages New Functionality
̈ ̈

New functionality New business processes

Implemented on demand Innovation ̈ No user acceptance test ̈ Limited testing
̈ ̈

© SAP 2009

̈

Customers have the need to stabilize their core systems and yet to still deliver ongoing innovation. With the SAP enhancement package concept SAP tackles this challenge. SAP enhancement packages represent a new software delivery strategy that allows you to get innovations on top of SAP ERP 6.0 without the need for fully upgrading your current release. With SAP enhancement packages, the methodology for implementing new functionality has significantly changed. You can now install new functionality, without any change for end users right at the outset. Therefore, the SAP enhancement packages installation should be performed in a normal maintenance window as part of your existing regular Support Package Update with only minor additional effort. Afterwards, you can activate new functionality when you want to, and you know exactly which functional changes will occur and what you have to test after the activation of the new functionality. SAP’s aim is to provide new functionality for well-defined user groups without side effects for the rest. Support Packages contain only corrections and legal changes; in case you only want to maintain your current state, SAP assures that your system will stay stable and compliant.

̈

̈

̈

© SAP AG

E2E200

7-36

I nst a lla t ion of N e w Func t iona lit y Se pa rate d from Ac t iva t ion
Selective Installation Optional
Each SAP enhancement package contains new versions of existing software components. ̈ You only update software components which are related to the functionality you wish to use. ̈ After installation:
̈
̈ ̈

Enhancement Packages

̈

No UI or process change until a business function is activated (ABAP) However, SAP enhancement packages require a defined ERP Support Package Stack One common regression test for both, SP and enhancement package

Selective Activation
New functionality must be explicitly switched on to become active in the system (with EHP4: ~300 Business Functions). ̈ If activated:
̈
̈

Support Packages

̈

Changes are predictable, only well described changes in the activated areas. Testing is simplified with templates, provided for every business function

Mandatory Mandatory
© SAP 2009

̈

SAP enhancement packages allow you to update a subset of the software components that are part of your SAP ERP 6.0 implementation. For example, you are now able to update parts of your SAP ECC Server. The selection of software components is driven by the functional enhancements that you plan to implement. In the figure, you can see how new HCM functionality is installed by updating only EA-HR (version 602) on the SAP ECC Server. The maintenance optimizer automatically identifies the relevant installation packages (potentially also including Support Packages) according to the current system status and the chosen Technical Usage(s). As the whole procedure is highly automated, the maintenance optimizer also provides a configuration file for the installation tools. As SAP leverages the Enhancement and Switch Framework to deliver new functionality, the installation of an SAP enhancement package has no impact on existing business processes or user interfaces, as long as no business function has been activated. However, SAP enhancement packages require a defined SAP ERP Support Package Stack, including a certain level of SAP ERP and SAP NetWeaver Support Packages. Furthermore, you potentially need to perform a modification adjustment (SPDD/SPAU). If you have modifications to the SAP code in your system and you separate the installation of the Support Package Stack and the installation of the SAP enhancement package into two steps, you need to perform the modification adjustment twice (and in part for the same objects), since SAP enhancement packages also contain corrections from the equivalent Support Package Stacks.

̈

© SAP AG

E2E200

7-37

I nst a ll SAP Enhance m ent Pa ck age s Combined w it h t he Support Pa c k Stac k

Maintenance Cycle Implementing Support Package Stacks:
Modification Adjustment & Regression Test

Install SPS

Go-Live

Implementing EHPs:
Understand Concept Discover New Functions Modification Adjustment & Regression Test Activate & Configure Acceptance Test

Install EHP

Go-Live

Possible to combine it in one step

Innovation Cycle

© SAP 2009

The SAP enhancement package is designed to decouple technical installation from business innovation. You can install SAP Enhancement Packages combined with Support Pack Stack as a maintenance activity with only minor additional effort. ̈ The Enhancement Package Lifecycle includes 5 steps: • Step 1: Discover - Receive an overview of available enhancements - Understand their potential business benefits - Identify enhancements relevant for you • Step 2: Evaluate & Decide - Evaluate relevant enhancements - Understand their particular benefit for you - Assess effort and impact of their implementation • Step 3: Prepare & Install - Download, load, and install the relevant components - Test SPAU and Regression for the upgraded components • Step 4: Activate & Configure - Check dependencies - Activate business functions - Configure new capabilities • Step 5: Test & Go-Live - Use templates for acceptance testing - Complete relevant end user training - Go-Live
© SAP AG E2E200 7-38

̈

Ex a mple : Sit ua t ion a fte r Applying EH P 3 Component s (ABAP)
SAP ECC Server

ABAP EhP3 IS-UT 600 FI-CAX 600 IS-PS-CA 600 INSURAN CE 600

ECC-IS Layer

IS-CWM 600

IS-OIL 600

ECC-DIMP 603

IS-H 600

EA-RETAIL 600 EA-GLTRADE 600

EA-DFPS 603

SAP ECC Core Layer

LSOFE 600 (Front End)

EA-FINSERV 600

EA-PS 603

IS-M 600

FI-CA 600

ERECRUIT 600

EA-IPPE 400

EA-HR 603

EA-APPL 600 603

SEM-BW 600

SAP_HR 600

SAP_APPL 600 603

FINBASIS 600

SAP_AP 700 ST-PI 2005_1_700 NetWeaver SAP BW 700 PI_BASIS 2005_1_700 SAP_ABA 700 SAP_BASIS 700 SAP KERNEL 700
© SAP 2009

̈

A selective exchange of one component is possible: With SAP EHPs you can selectively update software components. Note that matching combinations of software components as well as PI/EP/BI content and Java software components are grouped by technical usages. As the number of software components is limited, for example, a separate installation of logistics and financials (both are located in the core software component SAP/EA_APPL) is not possible. Strict separation of technical installation and the implementation of the new functionality: Explicit activation separately for each business function (with EHP3 we have approximately 150 business functions). However, only backend functionality (ABAP) is switchable.

̈

© SAP AG

E2E200

7-39

I nst a lla t ion Proce dure : Broa d or Se lec t ive
Broad Installation Selective Installation
Evaluate & Decide Prepare & Install

1. Choose business functions, for example: ‘Retail Buying’ and ‘Retail Planning’
SAP Notes

1+2. Choose relevant Technical Usage(s) with potential business value for your company.

2. Map business function(s) to Technical Usage(s)

EHP3: 1083576, EHP4: 1165438

Now defined: technical usage(s)

Queue of installable packages + stack xml

3. Select technical usage(s) using maintenance optimizer. Automated calculation and download of required installation files (see below) 4. Install these installation packages using SAINT or EHP Installer (mandatory as of EHP4) 5. Modification Adjustment

6. Regression Test
© SAP 2009

Two alternative installation approaches (for SAP ECC Server): 1) Broad Installation • Customer’s IT strategy for EHP installations: 1. Proactively add full scope of new functions to be in best shape to activate further business functions as soon as these are requested by the business. 2. Use synergy effects with your maintenance cycles to avoid a separate regression test. • Proceeding for SAP ECC: Installation approach - Look at the technical usages offered. 2. Exclude the ones that you do not use on this system. 3. For the remaining technical usages check if the enhancements inside potentially add value for you. 4. If yes, install these technical usages. • Advantages: Minimize initial effort for analyzing new functions. Be in best shape for new implementations. • Main Disadvantage: All Installed EHP components have to be updated with every future SAP enhancement package installation. Potentially additional adjustment effort and downtime must be considered. 2) Selective Installation • Customer’s IT strategy for EHP installations: - Change (install) only what is needed for activating a business function that the business decided to use. - Use synergy effects with your maintenance cycles to avoid a separate regression test. - Proceeding: Install exactly those technical usages that are needed to activate the business functions that are in scope for your project. - Advantages: 1. Minimize risk for this implementation project. 2. Less potential adjustment efforts as less software components are touched. 3. This is the recommended approach by SAP as it minimizes the implementation effort. ̈ Installed EHP components have to be updated with every future SAP enhancement package installation. Customers who have activated an industry business function set have to include the corresponding industry software component version into the EHP installation.
© SAP AG E2E200 7-40

̈

Busine ss Func t ions and Te chnica l U sa ge s

Business Function
‘cluster of functions that can be switched-on’
RE_GEN_CI_1 (Real Estate)

Technical Usage
Mapping via maintenance optimizer ‘installable unit: valid subset of software components required for a business function’ Mapping via SNote

Instances & Software Components
SAP ECC Server
EA_APPL 603 SAP_APPL 603

Central Applications

SAP ECC Server
EA_HR 603

HCM_ASR_CI_1 (HCM, Admin. Services 01)

HCM – Administrative Services

SAP NetWeaver Portal
Business Package

Mapping between business functions and technical usages: See description in SAP Note 1083576 (EHP3) and 1165438 (EHP4). ̈ This mapping of software components to technical usages is automatically done by the maintenance optimizer.
̈

© SAP 2009

̈

Once you have the names of the required business functions, you have to find out the software components you need. In addition to ABAP software components, you might need to update Java components, portal content, or XI content as well. To help you ensure consistency, we have bundled ABAP components, Java components, portal content, and XI content as "Technical Usages.“ A Technical Usage bundles a number of business functions and instances and components that are needed to make a particular business function work. It synchronizes the changes over the different stacks and components. For example, some changes in an ECC core component may need additional Portal and XI content. New business functions are mapped to technical usages by a note or documentation A technical usage contains all components that have to be installed in the instances so that you can use a business function. This TU (at the top) needs only new portal content and EA HR_602. There are other technical usages needing Java components, XI, or BI content. As the number of software components are limited, for example, a separate installation of logistics and financials (both are located in the core software component SAP/EA_APPL) is not possible. The mapping is done with the help of a SAP Note. You will find all specific information in the SAP enhancement package master guide. Please remember: SAP enhancement packages are a delta shipment for SAP ERP 6.0, so please check if additional technical components (such as Trex) are required. You find more information about this in the release notes, documentation, and the Master Guide.

̈

̈

© SAP AG

E2E200

7-41

Equiva lent Support Pa ck age Le ve l

Equivalent Support Packages are time-synchronized SPs for different versions of one software component
Example: 600 SPS13 602 SPS3 603 SPS2

SAP ERP 6.0 EhP 3 (SWC Version 603)

SPS 1

SPS 2

SPS 3

SAP ERP 6.0 EhP 2 (SWC Version 602)

SPS 1

SPS 2

SPS 3

SPS 4

Different SoftwareComponentVersions for ERP 6.0 + enhancement packages

Equivalent (same correction level), time-synchronized Support-Packages

SAP ERP 6.0 (SWC Version 600)

SPS 9

SPS 10

SPS 11

SPS 12

SPS 13 SPS 14

Today SWC=Software Component Version
© SAP 2009

time

̈ ̈

SAP enhancement packages also contain a certain level of corrections and therefore require an equivalent Support Package Level for the software components which remain on version 600. Therefore, EHPs should always be installed together with the required Support Package Stack. As a consequence, customers have to adjust possible modifications and test the application, however, this was the same with the pure Support Package Stack installation. Efforts should be expected to be comparable or slightly higher. Equivalent Support Packages (see also SAP Note 1064635): • Are time-synchronized SPs for different versions of one software component (SWC) • Contain identical corrections for capabilities that both versions have in common • Differ only with respect to corrections for new capabilities (which are only provided by the higher software component version)

̈

̈

Support Package Stacks for SAP ERP include Support Packages for SAP NetWeaver

© SAP AG

E2E200

7-42

Enha nc e me nt Pac ka ge s for SAP ERP a nd SAP N e t We a ve r
SAP Enhancement Packages for

Installation Procedure

Selective Activation

SAP ERP

̈ Requires maintenance optimizer ̈ Uses Enhancement Package Installer

̈ New functions are switched on selectively (ABAP switch framework) ̈ SAP provides an impact analyzer tool and test case templates

SAP NetWeaver

̈ maintenance optimizer is ̈ NW EHP adds new optional functionality at installation time, but ̈ Uses Enhancement does not replace Package Installer existing functionality

© SAP 2009

̈

SAP enhancement packages for SAP ERP and SAP NetWeaver: The installation procedure is in both cases efficient and fast. The installation is performed with the EHP installer (from EHP 3 on) based on proven SAP software lifecycle management tools. In both cases, there is no UI or process change for end users after installation of an enhancement package and by that the impact of installation is limited. Also, new functions are switched on selectively. Remember that EHP 4 components for SAP ECC Server 6.0 always require SAP enhancement package 1 for SAP NetWeaver 7.0. • SAP NetWeaver systems with usage types, for example AS ABAP, AS Java, EP, PI, DI, …: - Only systems that benefit from an EHP are touched. - EHPs for SAP NetWeaver are downward compatible: - In a landscape you can update each selection of systems. However, all usage types of a single system need to be on the same EHP state. • SAP NetWeaver as basis of SAP products, for example SAP ERP: - SAP NetWeaver cannot be updated independently from products on top of it. For example, SAP ERP 6.01 may not use SAP NetWeaver 7.0 EHP1, but ERP 6.04 must use it. - EHPs for SAP NetWeaver need not be applied separately but are part of the product’s EHP.

̈

̈

© SAP AG

E2E200

7-43

SAP Enhance me nt Pa cka ge ? I nform a t ion Ce nte r
SAP Service Market Place ~erp-ehp is the single point of access to all levels of details around SAP Enhancement Packages.

The Concept
Strategy and Enhancement Package Lifecycle

̈ Purpose of the SAP ERP

enhancement package strategy
̈ Concept and methodology of
SAP Enhancement Package for SAP ERP 6.0

enhancement packages
̈ What you need to know before ̈ How to implement them ̈ What to test at what point in time

Short overview

Detailed overview

Detailed presentation

Detailed online info

Functional Overview
Financials Human Capital Mgmt. Procurement and Logistics Execution Product Development and Manufacturing Sales and Service Corporate Services Cross ERP

̈ Which enhancements are included

in each enhancement package?
̈ Which areas of the solution were

touched by new developments?

Level 1 => ‘Short overview presentation’:

Level 2 => ‘Detailed overview presentation’:

Level 3 => ‘Detailed presentation’:

Level 4 => ‘Online information’: Assess each business function, using all related information. This is presented in a table-like list with links to documentation, test cases, release notes, detail presentations, etc.

Get an idea of each business function Understand each business function with Understand each feature of (short description and target group) features included, benefits, target users a business function and their and technical name. (~ 1 slide per feature) (~ 1 slide per business function)
© SAP 2009

̈

The central starting to point to get information about SAP enhancement packages is the SAP Enhancement Package Information Center. You can access it on the SAP Service Marketplace using the quick link /ERP-EHP. There, you will find the EHP FAQ document, for example, the EHP Must Know Guide and you will get direct access to the EHP forum and the Wiki pages. The Enhancement Package Information Center is the single point of access to all information related to a business function for the business expert. Here, you can find presentations, documentation, release notes, test catalogs and Learning Maps. The business function documentation allows the user to get to know the capabilities behind a business function and how to use them; learn about options the business function provides; and notes which software components are needed. Note that each business function has a technical name. This identifier is important to determine which parts of the system need to be updated. Get information on which business function (this is the switchable unit which is well described from a functional perspective) should be used.

̈ ̈

̈

© SAP AG

E2E200

7-44

Syste m De m o

SAP Enhancement Package Info Center

© SAP 2009

© SAP AG

E2E200

7-45

M a inte na nc e Opt im ize r Guide d Dow nload Proc edure for EhPs

̈

Technical usage: predefined, installable subsets of an SAP enhancement package for SAP ERP SAP Note 1083576 (EHP3) maps identified business functions to a technical usage You enter the technical usage in the maintenance optimizer and it automatically calculates the relevant download files Prerequisites: Solution Manager 7.0 SP15 or higher, configuration steps done, Data maintenance with SAP Solution Manager (SMSY)

̈

̈

̈

* This is an example of installed software components in SAP ECC. For Java components and BI-, PI- and Portal content, a different installation procedure would be used.
© SAP 2009

̈

If you use the maintenance optimizer – as strongly recommended and already required for downloading Support Packages in general – you only need the name of the technical usage to install all needed software components. Based on that information, the maintenance optimizer calculates the needed software components and Support Packages automatically. Create a new maintenance transaction for updating your system with SAP enhancement packages for SAP ERP 6.0. A guided procedure leads you through the preparation process for updating your systems. Select all systems that are affected by the application of the SAP enhancement package. In the next step of the guided procedure, you select the technical usages you want to apply to your systems. The maintenance optimizer automatically calculates all needed Support Packages and new software component versions needed for installing the previously selected Technical Usages. As a result, the maintenance optimizer creates the Stack XML file that can be read by the installation tools to create a valid import queue. You can find further information about the maintenance optimizer at service.sap.com/solman-mopz, detailed documentation at help.sap.com å SAP Solution Manager å (select your preferred language) in the "Change Management" section. Please remember: The software components of SAP enhancement packages for SAP ERP 6.0 contain new developments (as we partially replace existing software components). Therefore, if you take a look at your system after applying the SAP enhancement package software components, you will find software components in version 600 (for example, with Support Package level 10) as well as software components in version 602 (for example, SAP enhancement package 2 with Support Package level 0 which contains equivalent corrections to SP level 10 of the same component in version 600).

̈

̈

© SAP AG

E2E200

7-46

Ac t iva te & Configure (T ransac t ion SFW5): Be fore & Aft e r t he Ac t iva t ion

Activities before the Activation …
̈ View the list of business functions now selectable ̈ Access documentation, release notes, test

Activation …
̈ Mark the chosen business function ̈ Activate all marked business functions (automatic

catalog and possible dependencies from here ̈ Install the relevant documentation, refer to SAP note 1066110
̈ Lock system for end-users.

alert in case that set of business functions is invalid)
̈ Import business function configuration of chosen

business function(s)
̈ Unlock system for end-users.

Benefits
̈ Transparency of all system and User Interface changes

Benefits
̈ New coding active only where activated ̈ Faster implementation because only activated parts

that will take place after activation
̈ Stability for all other parts of the solution
© SAP 2009

are configured

The switch transaction shows all the business functions that can now be activated after the installation of the 3 new software components. The customer is currently only interested in the BF “Retail Buying”. For each BF, this transaction provides direct links to documentation, release info, etc. ̈ Result: The coding of the 3 software components has been completely updated. ̈ Before an activation of the business functions, the system does not yet change its behavior. After the installation, the customer executes the SPAU transaction to check and manage his affected modifications. • Activities (BEFORE) - View the list of business functions available with the latest system setup - Access documentation, release notes, test catalog, and possible dependencies - Install the relevant documentation, refer to SAP Note 1066110 • Benefits: - Transparency of all system and UI changes that will take place • Activities (AFTER) - Activate the chosen business functions - Configure the chosen business functions • Benefits: - New coding becomes effective only where activated - Faster implementation because only activated parts are configured - No change in system behavior before the activation (ECC) - Stability for all other parts of the solution
© SAP AG E2E200 7-47

̈

Ex e rc ise

Enhancement Packages

© SAP 2009

© SAP AG

E2E200

7-48

M a inte na nc e M anagem ent : U nit Ove rvie w Dia gra m
Maintenance Management Lesson 1: SAP Maintenance Strategy Lesson 2: Types of Maintenance Lesson 3: SAP Enhancement Packages Lesson 4: Maintenance Optimizer Lesson 5: Software Lifecycle Management Tools Lesson 6: Maintenance Certificate Lesson 7: Upgrade / Change Impact Analysis Lesson 8: Best Practice Recommendations

© SAP 2009

© SAP AG

E2E200

7-49

M a inte na nc e Opt im ize r ? Be t t e r H a ndling of Cust ome r Support Proc e sse s
Planning of maintenance
Stack configuration file for update ̈ Download of Support Packages and stacks ̈ Download of enhancement packages
̈

Display current level and recommended level

maintenance optimizer governs the whole maintenance process using the Software Lifecycle Manager (SLM) service

Approve and download

Track centrally and provide transparency

Import

Test

Release to production
© SAP 2009

̈

The maintenance optimizer (MOPZ) simplifies the process of identifying and downloading applicable support items for all of your systems by providing you with an organized, easy-to follow, guided procedure. The maintenance optimizer provides overall governance of maintenance activities. It detects relevant software component Support Packages and patches and provides an overall structure for planning and managing the maintenance process by guiding the user through the required steps in the correct sequence. Automated steps make the maintenance process simpler and more comfortable. As of April 2007, support items for SAP Busness Suite 2005 and higher are only available through MOPZ. The MOPZ can use the Software Lifecycle Manager (SLM) service of SAP NetWeaver Application Server (AS) Java to automatically download identified support items (SP15 and higher) and will automate the deployment of support items (beginning with SP18). SLM ist integrated with the System Landscape Directory (SLD) and with SAP Solution Manager – it stores and retrieves system landscape information in the SLD and supports the planning process in SAP Solution Manager. With SP15 of SAP Solution Manager, MOPZ detects which support items are required, calls SLM through a Web service, and transfers the detected items via XML to SLM. The SLM retrieves the necessary URL from the SAP Service Marketplace and sends a request to the Software Logistic Controller (SLC) of SAP NetWeaver AS to download the support items from the SAP Service Martetplace to a central download directory. Any previously downloaded files are not downloaded again.

̈

̈

̈

© SAP AG

E2E200

7-50

M a inte na nc e Opt im ize r T e chnica l Proc e ss De sc ript ion

NW BI

1

Check Versions
ntio er lu So anag M

2

Select Files

NW BI

ice rv et Se ark M lace P

6
SAP ERP

Maintain Status 3a Confirm Files
(only possible in Solution Manager)

Download Basket (part of SMP)

5 Implement Support Packages
(as of SPS 19 via SLM)

3b
Server

Or: Download Files via SLM

© SAP 2009

̈ ̈ ̈

This picture provides an overview of the maintenance optimizer procedure. The administrator checks the Support Package Levels in the SAP Solution Manager and starts a new maintenance process from there. After selecting a system, the SAP Solution Manager provides a link to the SAP Service Marketplace where the latest support packages can be selected and added to the download basket or the MOPZ carries out automatically the delta calculation for the Support Package Levels. In the next step, there is another link from the SAP Solution Manager into the SAP Service Marketplace. Now, the administrator has to confirm the patch files in the download basket. The patch files can now be downloaded via Software Lifecycle Manager to a central file share. From there, it can be implemented in the managed systems. Finally, the status of the maintenance activity is maintained in the SAP Solution Manager. All activities except for the EHP implementation (from EHP4 on) of the support packages can be done in the SAP Solution Manager. Single track system update is possible from SP18. Note that track update of the whole system landscape is in piloting phase.

̈ ̈ ̈ ̈ ̈

© SAP AG

E2E200

7-51

M a inte na nc e Opt im ize r Pre re quisit e s

̈ Maintenance

Optimizer configured according to the SAP Solution Manager configuration guide
̈ ̈ ̈

Solution defined S-user assigned for SAP Support Portal Functionality RFC User for Communication with SAP Service and Support maintained Authorizations provided to end users Activated Maintenance Optimizer BC Sets

̈ ̈

̈ SAP

Download Manager installed

© SAP 2009

̈

Prerequisites • You have configured the maintenance optimizer using the SAP Solution Manager configuration guide: - Solution defined. - S-users for SAP Support Portal Functionality assigned (user IDs for the SAP Service Marketplace to user IDs for the SAP Solution Manager). - RFC users for communicating with SAP Service and support systems maintained (RFC connection SAP-OSS created and RFC user assigned). - The end users that are to be able to use the maintenance optimizer must have the required authorizations. - The relevant BC Sets have to be activated.

̈ ̈ ̈

All these settings are included in the “Wizard-based Initial Configuration of Basic Settings” or can be performed manually in the ‘Standard Configuration of Basic Settings’ of the IMG. You have installed the SAP Download Manager locally (available in the SAP Software Distribution Center in the SAP Support Portal) Further information: • SAP Note 1024932 “maintenance optimizer: Collective Note” • SAP Support Portal http://service.sap.com/solman-mopz • You have configured the maintenance optimizer in SAP Solution Manager as described on SAP Help Portal at http://help.sap.com å SAP Solutions å SAP Solution Manager å SAP Solution Manager <Release> <Language> å Change Management å maintenance optimizer Planning and Monitoring Product Maintenance

© SAP AG

E2E200

7-52

SAP Support Port a l Conta c t Pe rson Assignme nt

Your S-user is the user ID assigned to you by SAP that you use to log on to the SAP Support Portal. Your system administrator must have performed the following SAP Implementation Guide (IMG) activities:
̈ Maintain User for Communication with SAP Service and

Support
̈ Assign S-user for SAP Support Portal functionality or with

the transaction AISUSER

© SAP 2009

̈

Your S-user must be assigned to the same customer or corporate number as the S-user which your administrator entered in the SAP-OSS RFC destination. If this is not the case, the maintenance optimizer will not be able to read your download basket. Always log on to the SAP Support Portal with the same S-user which is assigned to your Solution Manager user. If you do not do this, the maintenance optimizer will not be able to confirm and approve any files you place in that S-user’s download basket.

̈

© SAP AG

E2E200

7-53

Opt iona l Enha nce m ent Soft w a re Life c yc le M a na ge r
Software Lifecycle Manager
̈ ̈

Optional enhancement to the maintenance optimizer Provides an automated download of all suppport items into a central download directory Optionally, the SLM can start and control the deployment of Support Packages into the managed systems. However, enhancement packages must be installed with the Enhancement Package Installer.

̈

̈

© SAP 2009

̈

The central systems are the SAP Solution Manager system and the system with component Software Lifecycle Manager (SLM) and System Landscape Directory (SLD) content. On the one hand, SAP recommends to install SLM and SLD on the Solution Manager system; in this case, there is only one central system for configuration. On the other hand, if you already have a system with SLD, you will need to configure these 2 central systems to make use of the already configured SLD. In addition, a SAP Solution Manager system can connect to more than one SLM component. The managed systems are systems to be maintained by the maintenance optimizer (MOPZ). The SAP Solution Manager system and the system with SLM themselves are also managed systems when they are updating their own components. Except for MOPZ and SLM, relevant tools in central systems and managed systems need to be set up and configured. In the SAP Solution Manager central system, MOPZ resides here; in the SLM central system, the component SLM, SLD content, and the Software Logistic Controller (SLC) need to be installed. In managed systems, the following tools and service need to be ready: SLC, Support Package Manager (SPAM), Java Support Package Manager (JSPM), SAPControl Web service.

̈

̈ ̈

© SAP AG

E2E200

7-54

Soft w a re Life c yc le M a na ge r Pre re quisit e s

̈ Software

Lifecycle Manager configuration
RFC connection setup Logical port setup Download Directory Assistant setup Software Lifecycle Manager setup

̈ ̈ ̈ ̈

© SAP 2009

̈

If you wish to download product maintenance files automatically, you must have successfully completed the following activities for configuring the Software Lifecycle Manager in SAP Solution Manager Customizing: Setting up the RFC connection and logical port: SAP recommends you set up an HTTPS connection. For more information, see the Security Guide on SAP Service Marketplace at http://service.sap.com/instguides å SAP Components å SAP Solution Manager å Release 7.0 å Security Guide SAP Solution Manager 7.0. Setting up the Download Directory Assistant Setting up the Software Lifecycle Manager • Benefits SLM (from SP18 on): - Possibility to use the same download transaction also for implementation (If customers use 701 systems). That means that after downloading the archives, they will be deployed to the system in the next step. Another advantage is that already downloaded archives will not be downloaded again, since the files have a common location. - In the version 702, an automated handling of Kernel and IGS components will be added, not only for Java and ABAP as in 701. - At last, Solution Manager will be the frontend for all operations, and customers will not see any of the logistic tools on any of the sytems in the landscape.

̈

̈ ̈

̈

Further information, access the SAP Support Portal at http://service.sap.com/solutionmanager å Media Library å Technical Papers å How to Configure maintenance optimizer (SPS18) to Use SLM

© SAP AG

E2E200

7-55

M a inte na nc e Opt im ize r Guide d Proc edure

Initialization

Select Files

Download Files

Perform Implementation

End Maintenance

1

2

3

4

5

1. Plan the maintenance (or EhP installation)
̈ ̈

To start planning, create a new Maintenance Transaction. Choose product version, system, and logical component to be updated with an EHP. Choose Find files for the stack version. Choose the files for your OS/DB combination and continue. Check the files for the stack and continue to confirm the selection with Select Download Type. To display it, choose Confirm files in Download Basket. Check the list of flies and choose Confirm Download. Choose to Download Files from the Download Basket. You see the download; to start step 4, choose Continue. The stack configuration file (XML format is displayed). The download and Stack Configuration File have been prepared. The process in the maintenance optimizer ends.

2. Select Files (prepare the download stack)
̈ ̈ ̈

3. Download Files (prepare the download stack)
̈ ̈ ̈ ̈ ̈ ̈ ̈
© SAP 2009

4. Perform Implementation (prepare the download stack)

5. End Maintenance

̈ ̈

You can either start the download procedure for your active solutions in transaction DSWP or call transaction solman_workcenter. The stack definition XML file is generated by the maintenance optimizer and saved to the EPS inbox directory of SAP Solution Manager. For more information about the stack definition XML file, see SAP Note 884537.

© SAP AG

E2E200

7-56

M a inte na nc e Opt im ize r ? Reporting

1. Start transaction /n/tmwflow/maintenance 3.Choose Execute

2.Choose parameters

4.Results

© SAP 2009

̈ ̈

Transaction /TMWFLOW/MAINTENANCE: Product maintenance reporting gives you an overview of all product maintenance procedures in your SAP Solution Manager system. You can simultaneously view procedures which belong to several different solutions and you can also view closed or withdrawn procedures. You can use the reporting function to: • Create an overview of product maintenance procedures which match specific criteria such as status or priority. • Navigate to the corresponding step of an open product maintenance procedure in the maintenance optimizer. • Create an overview of product maintenance procedures and save the overview to a local file for further processing.

̈

© SAP AG

E2E200

7-57

Syste m De m o + Ex e rc ise

Maintenance Optimizer

© SAP 2009

© SAP AG

E2E200

7-58

Appe ndix

Maintenance Optimizer Step by Step

© SAP 2009

© SAP AG

E2E200

7-59

Cre a t e a N e w M a int ena nc e T ra nsa c t ion

SOLMAN_ WORKCE NTE R

1. Start transaction SOLMAN_WORKCENTER 2. Go to Change Management

3. Create New Maintenance Transaction

© SAP 2009

̈ ̈ ̈

The maintenance optimizer is started from transaction SOLMAN_WORKCENTER. Choose Change Management å maintenance optimizer Create a new maintenance transaction.

© SAP AG

E2E200

7-60

St e p 1 : Pla n M a int enance

3. You can add business partners and documents

1. Choose Solution and/or Product Version

2. Select a system

© SAP 2009

̈ ̈

1. Start Maintenance Planning: Specify the necessary information for product maintenance. Mandatory fields are indicated with a red asterisk. • Short Text: Enter a descriptive text. By default, the text “New maintenance optimizer procedure” appears. • Solution: Select a solution (not a MUST anymore). • Product version: You can choose one of the product versions from the current solution. The maintenance optimizer determines the selection of product versions based on the systems assigned to your solution. • System: Once you choose a product version, the maintenance optimizer displays the systems assigned to that product version. Select the system(s) for which you want to perform product maintenance.

̈

Choose Continue.

© SAP AG

E2E200

7-61

St e p 2 : Se le c t File s

Option 1: Calculate download files automatically

Option 2: Select files manually

© SAP 2009

̈

2. Select Files • You can let the maintenance optimizer calculate the required download files in order to update to a new Support Package Stack or you can choose to download individual files manually.

© SAP AG

E2E200

7-62

St e p 2 : Se le c t File s

Maintenance

Enhancement Packages

© SAP 2009

© SAP AG

E2E200

7-63

St e p 2 : Se le c t Dow nload M e t hod

Download files with SLM or with Download Basket

© SAP 2009

̈

You may use the Software Lifecycle Manager to download the files to a central directory or you can download the files from the download basket, for example, by using the Download Manager.

© SAP AG

E2E200

7-64

St e p 3 : Confirm File s

1. Go to Download Basket 2. Confirm files in Download Basket

© SAP 2009

̈

3. Download Files • Before you can download the files, you must first confirm your selection in the maintenance optimizer. To do this, choose Confirm Selection in the maintenance optimizer. • In the following screen, select the files and choose Confirm Download. • By confirming your selection, the files are assigned to the maintenance procedure and released for download. • In the following screen, select the files and choose Confirm Download. • By confirming your selection, the files are assigned to the maintenance procedure and released for download. • Now, you can download the files using the SAP Download Manager. For more information about using the SAP Download Manager, see the documentation on SAP Service Marketplace.

© SAP AG

E2E200

7-65

St e p 4 : Pe rform I mple m ent a t ion

1. Set status of implementation to Completed

© SAP 2009

̈

4. Perform Implementation • After downloading the files, perform the required maintenance in your systems. • If you assigned systems at the beginning of the procedure, the maintenance optimizer lists these systems for you. You can enter the start date and end date for the implementation and indicate the status of the procedure. • The maintenance optimizer displays an overview of the files that you selected in the previous step. For each Support Package, you can view the documentation of the corrections and their side effects by clicking the corresponding link. • Once you have performed the required maintenance in all selected systems, you can complete the maintenance procedure. To complete the procedure, you must first set the implementation status for each system assigned to the procedure to Complete. • Choose Continue.

© SAP AG

E2E200

7-66

St e p 4 : Pe rform I mple m ent a t ion

© SAP 2009

̈ ̈

The SAP Download Manager is a PC tool which is installed on the administartor‘s PC. The patches are downloaded to the PC where the SAP Download Manager was called and can then be implemented in the system, for example with transaction JSPM.

© SAP AG

E2E200

7-67

St e p 5 : End M a int enanc e

Complete maintenance transaction

© SAP 2009

̈

5. End Maintenance • If you have successfully finished the maintenance of your systems, complete the procedure for product maintenance. Once you set the status to Complete, the procedure can no longer be changed.

© SAP AG

E2E200

7-68

M a inte na nc e M anagem ent : U nit Ove rvie w Dia gra m
Maintenance Management Lesson 1: SAP Maintenance Strategy Lesson 2: Types of Maintenance Lesson 3: SAP Enhancement Packages Lesson 4: Maintenance Optimizer Lesson 5: Software Lifecycle Management Tools Lesson 6: Maintenance Certificate Lesson 7: Upgrade / Change Impact Analysis Lesson 8: Best Practice Recommendations

© SAP 2009

© SAP AG

E2E200

7-69

Soft w a re Life c yc le T oolse t

Software Lifecycle tools

Install

Upgrade

Maintenance

SAPup SAPinst

SAPJup

JSPM SPAM

SID JAVA SID SID SID SID SAPehpi AddOns SAINT

ABAP SID

Landscape

© SAP 2009

̈

̈

̈

̈

̈

̈

̈

SAP provides you with tools and processes to manage your system landscape throughout the entire life cycle. Besides initial implementation of an application, the tools support continuous application and system optimization that result from business or organizational changes, as well as the implementation of additional functions. Software logistics aims to simplify and automate life-cycle management while reducing administration effort. SAPinst: SAP provides a powerful state-of-the-art set of tools that offers an integrated framework for the whole planning and installation process. SAPinst is the standard SAP installation tool, covering a broad range of platforms and products and both the ABAP and Java technology. Whether you install an SAP NetWeaver system, an SAP ERP system or a standalone engine – such as SAP liveCache – you can handle all these installations easily through the uniform look and feel of the SAP installation tool. SAPup/SAPJup: These are the standard SAP upgrade tools for ABAP and Java for the execution of the main upgrade activities.The tools share a similar architecture in that they both consist of an upgrade program (SAPUp or SAPJup) and a control program (Upgrade GUI or SDT GUI). SAP delivers changes to ABAP components in the form of ABAP Support Packages. These are imported using the Support Package Manager. Add-ons (such as industry solutions, plug-ins, and partner projects) are installed with the Add-On Installation Tool using the same technology. With the help of optimized maintenance tools, you can enhance and update SAP systems fast and with great flexibility. In SAP NetWeaver 2004s, the Java Support Package Manager (JSPM) has been introduced, in order to simplify the Support Package management process for Java applications at customer site. The JSPM must be called at the operating system level. SAP Enhancement Package Installer (SAPehpi): Use SAPehpi to install SAP enhancement package 1 for SAP NetWeaver 7.0 or SAP enhancement package 4 for SAP ERP 6.0 and higher. Install SAP EHPs in one process with the SP stack. You can find more information at http://www.sdn.sap.com/irj/sdn/softwarelogistics regarding software lifecycle tools.
E2E200 7-70

© SAP AG

SAP Support Pa c ka ge M a nage r (SPAM ) I nst a ll ABAP Support Pa ck age s
Activities:
All Support Packages can be installed in one queue. Modification adjustment transports can be included if necessary.

Benefit:
Dependencies between Support Packages are checked.

Preparation:
Update SPAM to the latest version before starting the Support Package implementation (read SAP Note 822379)

© SAP 2009

̈

ABAP Support Packages contain corrections and adjustments for the ABAP-based Software Components of the SAP system. In contrast to Java Support Packages, ABAP Support Packages are non-cumulative. Therefore, ABAP Support Packages must be installed in the correct sequence, one after the other. You cannot skip any intermediate Support Packages. ABAP Support Packages are delivered as SAR files. They are installed using the Support Package Manager (SPAM). Before you start using the Support Package Manager, see SAP Note 822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP. We recommend that you always use the latest version of the Support Package Manager. You can download it from SAP Service Marketplace at http://service.sap.com/swdc --> Download Support Packages and Patches å Entry by Application Group å Additional Components å SAP SPAM/SAINT UPDATE. For more information about SPAM and SAINT, see the online documentation on SAP Help Portal at http://help.sap.com/nw70 å SAP NetWeaver 7.0 including Enhancement Package 1 å SAP NetWeaver7.0 Library (including Enhancement Package 1) <Language> å SAP NetWeaver Library å Administrator’s Guide å Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS ABAP (Application Server for ABAP) å Software Logistics å Software Maintenance.

̈ ̈

̈

© SAP AG

E2E200

7-71

SAP Addon Inst a lla t ion T ool (SAI N T ) I nst a ll Add-Ons and EH Ps for ABAP
Activities
Install the loaded upgrade packages that you find in the inbox of the transaction SAINT (SAINT update level: 24) Loading Enhancement Package stack definition from Solution Manager maintenance optimizer using Stack Configuration button All software components can be installed in one step. SPAU comparison for upgraded software components (if system contains modifications) Usual support stack regression test

Benefits
Stability of large system parts Reduced effort for SPAU comparison and regression test
© SAP 2009

̈

The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on components. You can use the Add-On Installation Tool to import add-on components with their prerequisite ABAP Support Packages. If a particular Support Package Stack requires the installation or upgrade of some add-on components, you must use the ABAP Add-on Installation Tool (transaction SAINT) instead of the Support Package Manager. In this case, SAINT is able to import both the add-on components and the related Support Packages of ordinary SAP components in a single import queue. For more information about SPAM and SAINT, see the online documentation on SAP Help Portal at http://help.sap.com/nw70 -> SAP NetWeaver 7.0 including Enhancement Package 1 SAP NetWeaver 7.0 Library (including Enhancement Package 1) <Language> -> SAP NetWeaver Library -> Administrator’s Guide Technical Operations Manual for SAP NetWeaver -> Administration of SAP NetWeaver Systems -> AS ABAP (Application Server for ABAP) -> Software Logistics -> Software Maintenance

̈

© SAP AG

E2E200

7-72

J a va Support Pa ck age M anage r (J SPM ) I nst a ll J AV A component s
Activities
̈ ̈

Using Java Support Package Manager (JSPM) Enhancement Package Stack definition:
̈

Extension of SP Stack definition

̈ ̈ ̈

JSPM of SPS12 and lower: manual selection of packages to be installed JSPM of SPS13 and higher: Enabled for extended stack definition Packages selected and installed as a bundle

Preparation
̈ ̈

Packages residing in the inbox For SPS13 and higher: System Stack definition file for EhP

© SAP 2009

̈

In SAP NetWeaver 2004s, the Java Support Package Manager (JSPM) has been introduced, in order to simplify the Support Package management process for Java applications at customer site. The JSPM must be called at the operating system level. In the directory \usr\sap\<SID>\<Instance>\j2ee\JSPM\ call the script go.bat. The JSPM works similarly to transaction SPAM and has similar features. • JSPM is a patch tool – it updates components on the same release • JSPM deals with only one SID • JSPM deals with Java Stack engine only

̈

Useful Links: • Starting point: http://service.sap.com/jspm å JSPM Media Library å JSPM User Guide • SAP Note 891983 - JSPM: Central note

̈

When applying a Support Package Stack to a dual-stack system (ABAP+Java), the Java Support Package Manager (JSPM) will necessarily restart the system several times to make the changes effective. The ABAP part will only be restarted when JSPM is updating the SAP kernel and IGS.

© SAP AG

E2E200

7-73

M a inte na nc e Opt im ize r & Life c yc le M gmt T ools – H ow Do T he y Work Toge t he r?

Solution Manager
̈ ̈ ̈

Maintenance Optimizer (MOPZ) SLD (required if Java systems in the landscape) Business Blueprint & system landscape data maintained (SOLAR01 & SMSY) Stack.XML ABAP MOPZ Java SLD
Manually passed to the tools, tools called by admin

Managed Systems
ABAP EHPI Java EHPI

Generated via maintenance optimizer

OS-Tools + Kernel ABAP SAINT
OS-Tools + Kernel

Java JSPM
OS-Tools + Kernel

OS-Tools + Kernel

© SAP 2009

̈

This figure illustrates the use of the downloaded stack XML file to feed the actual installation tools. The SAP Solution Manager receives a customer-specific stack XML which contains the information about the queue of selected support and enhancement packages. The stack definition XML file is generated by the maintenance optimizer and saved to the EPS inbox directory of SAP Solution Manager. For more information about the stack definition XML file, see SAP Note 884537. The installation tools now use this information to bring the specific system to a well-defined and consistent system state.

̈

̈

© SAP AG

E2E200

7-74

SAP Enhance me nt Pa cka ge I nst a lle r Proc e ss Flow
install

SMP <SID>
… … input input

install

- Landscape data - System States
SAP Solution Manager 7.0 / System Landscape Directory result

EHP 1
output … …

SCF
input

SAP NetWeaver 7.0 EHP1

SPS X
3) Chosen enhancement package and required Support Package Stack calculated by the maintenance optimizer

Download

SAP EHPI
install

ABAP stack Java stack

1) SAP NetWeaver target system to install enhancement package 1 with SAP NetWeaver usage types

2) SAP Solutions Manager and SAP NW System Landscape Directory: Guided procedures for stack definition & download based on system information

4) Stack Configuration File and download from SAP Service Marketplace

5) SAP Enhancement Package Installer controlling tools for the ABAP and Java stack respectively in a guided procedure

1. Define systems to be updated 2. Start gathering of required downloads in the SAP Solution Manger based on SLD information in a guided procedure 3. The system generates a stack configuration file automatically with EHP and required SPS 4. The stack configuration file and download basket in SAP Service Marketplace are created … 5. … and consumed by the SAP Enhancement Package Installer in a second a guided procedure – downloaded objects are installed to all stacks on the system synchronously
© SAP 2009

̈

To find out the latest things about SAPehpi and its download path in the SAP Service Marketplace see Note 1245473 “Additional Information - SAP Enhancement Package Installer”.

© SAP AG

E2E200

7-75

Enha nc e me nt Pac ka ge I nst a lle r U pt im e a nd Dow nt im e Pha se s

Initialization Extraction

Configuration

Checks

Preprocessing

Downtime

Postprocessing Finalization

1
Shadow Syst. Operat.

2
Create Shadow Repository

3
Create Shadow Instance

4
Modification Adjustment Import EHP & SP stack

5
Remove Shadow System Activation Distribution Table operat.

6

7

8

Check System

Point of noreturn
Process can be reset without artefacts until here

SAPehpi uptime op.

Uptime

SAPehpi uptime processing
Syst. Switch (AS ABAP)

Test & Validation
Deployment (AS Java)

Backup

Downtime

SAPehpi downtime

Backup

uptime
© SAP 2009

downtime

uptime

̈

The SAP Enhancement Package Installer uses a system cloning and switch procedure. This procedure installs a copy of the system, the shadow system, in parallel to the original system. The shadow system is used to update the affected software components and to install the additional components, while the original system is still in production operation.

© SAP AG

E2E200

7-76

Enha nc e me nt Pac ka ge I nst a lle r U se r I nt e rfac e

© SAP 2009

̈ ̈ ̈

Enhancement Package Installer is mandatory as of EHP4 for ERP 6.0. SAP EHPs are installed in one process with the SP stack. All installation steps run as a guided procedure: • Preparing the download stack • Applying the download stack • All prerequisites are checked

̈

Downtime is minimized through • Use of shadow tables • Synchronization of ABAP and Java stacks • Measurably better than with SPAM/SAINT/JSPM (used for the identical scenario)

© SAP AG

E2E200

7-77

M a inte na nc e M anagem ent : U nit Ove rvie w Dia gra m
Maintenance Management Lesson 1: SAP Maintenance Strategy Lesson 2: Types of Maintenance Lesson 3: SAP Enhancement Packages Lesson 4: Maintenance Optimizer Lesson 5: Software Lifecycle Management Tools Lesson 6: Maintenance Certificate Lesson 7: Upgrade / Change Impact Analysis Lesson 8: Best Practice Recommendations

© SAP 2009

© SAP AG

E2E200

7-78

M a inte na nc e Ce rt ific a t e : I nt roduc t ion
The Maintenance Certificate ensures that only customers with a valid maintenance contract can apply Support Packages. It prevents unauthorized use. Coverage:
̈

All SAP products based on SAP NetWeaver 7.0 and beyond (including SAP Business Suite 2005)

Deployment of Maintenance Certificates:
̈ ̈

Automatically to all systems by SAP Solution Manager Manual fallback scenario (self-service) will be offered in SAP Support Portal

Validity:
̈

A maintenance certificate has a validity of 3 months

Procedure:
̈ ̈ ̈

Maintenance certificate is stored in license store of SAP system (Transaction: SLICENSE) SAP import tools (e.g. SPAM, SAINT, JSPM) check for valid maintenance certificate Import is stopped if no maintenance certificate is available

© SAP 2008

̈ ̈

More information are available in the SAP Support Portal under the quicklink /maintenancecertificate. The maintenance certificate enables software logistics tools to identify your system and the exact scope of your corresponding SAP maintenance agreement. It ensures that no unwanted Support Packages are applied and prevents unauthorized use.

© SAP AG

E2E200

7-79

M a inte na nc e Ce rt ific a t e File

----- Begin SAP License ----SAPSYSTEM=TT5 HARDWARE-KEY=Q0045252782 INSTNO=0120003411 BEGIN=20090316 EXPIRATION=20090617 LKEY=MIIBOwYJKoZIhvcNAQcCoIIBLDCCASgCAQExCzAJBgUrDgMCGgUAMAsGC SqGSIb3DQEHATGCAQcwggEDAgEBMFgwUjELMAkGA1UEBhMCREUxHDAaBgNV BAoTE215U0FQLmNvbSBXb3JrcGxhY2UxJTAjBgNVBAMTHG15U0FQLmNvbSB Xb3JrcGxhY2UgQ0EgKGRzYSkCAgGhMAkGBSsOAwIaBQCgXTAYBgkqhkiG9w 0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wOTAzMTcyMDE0N TBaMCMGCSqGSIb3DQEJBDEWBBRV+8ZR8LppuuNRsBxcsXsiMAojhjAJBgcq hkjOOAQDBC8wLQIUdaiB+Q4CRXOHAoZXCKdMbsdgZtkCFQCgoZdZRiueMm9 IYbjdHTTEYbuNRw== SWPRODUCTNAME=Maintenance_MSS SWPRODUCTLIMIT=2147483647 SYSTEM-NR=000000000310651354 SWPRODUCTNAME = Maintenance_<Database> indicates a Maintenance Certificate
© SAP 2009

̈

To display this file, go to workcenter Change Management å License Management. Filter for the system you want to check. Chhose Download Licenses to display the content of the maintenance certificate file. Run report RAGS_MK_DISPLAY_FILE with transaction SE38 on SAP Solution Manager to display the XML file.

̈

© SAP AG

E2E200

7-80

Dist ribut ion of M a int enance Ce rt ific a te Aut oma t ed or M a nua l
Distribution through SAP Solution Manager (recommended) Manual distribution

Master Data
Data Exchange Regular Automatic Update of Maintenance Certificate

Customer
---- Inst 00001234 ---- Inst 00001245 ---- Inst 00001256

Data Exchange via SAP Service Marketplace

SELF-SERVICE: Request Certificate

SAP Solution Manager distributes Maintenance Certificate to system

SAP Service & Support Infrastructure
Maintenance Certificate is installed manually on every system SAINT SPAM JSPM

SAINT SPAM JSPM

Customer System Landscape
© SAP 2009

Customer System Landscape

̈ ̈

The most important prerequisite is that the system data is maintained correctly and that it is up to date. Current system data is required to generate valid maintenance certificates for systems. Important SAP Notes: • SV-SMG-LIC • SV-SMG-LIC • SV-SMG-LIC • SV-SMG-LIC • SV-SMG-LIC • SV-SMG-LIC • SV-SMG-SDD • SV-SMG-SVC 1236587 1240265 1251060 1264784 1266139 1280664 1293657 1229904 JSPM - no valid maintenance certificate found SPAM/SAINT: No valid maintenance certificate found Error in requirement process of maintenance certificate Job log correction for request for maintenance certificates Incomplete SMSY systems do not receive maint. certificate Distribution of maintenance certificates:Troubleshooting Error in distribution of Maintenance Certificates in SDCCN Maintenance certificate distribution for service provider

̈

The application log (TA SLG1) does not deliver any error for the object = SOLAR, subobject = AGS_MAINT_KEY

© SAP AG

E2E200

7-81

Aut oma t ic Dist ribut ion of M a int enance Ce rt ific a t e
Customer
SAP Solution Manager
SolMan requests 1 Maintenance Certificates

Global Support Backbone
Maintenance Certificates are generated

2
Managed system

3 4

SolMan receives Maintenance Certificates

System receives Maintenance Certificate

1 SAP Solution Manager requests maintenance certificates for all connected systems. 2 Maintenance Certificates are generated in Global Support Backbone. 3 SAP Solution Manager receives maintenance certificates upon next connection. 4 Managed system pulls maintenance certificate from SAP Solution Manager. End-to-end process may take up to 48 hours (as SAP Solution Manager connects to Global Support Backbone once a day.)
© SAP 2009

̈

Process overview: • The SAP Solution Manager passes the system numbers of the managed systems for which automatic license data distribution is active, to the SAP Global Support Backbone. • The SAP global support backbone checks each system for a valid maintenance contract. • If there is no valid maintenance contract, the process in the SAP global support backbone ends, and customer SAP Solution Manager is informed. • If there is a valid maintenance contract, the SAP global support backbone checks for a maintenance certificate, and returns it to the SAP Solution Manager. • If there is no maintenance certificate, the SAP global support backbone generates one for this system. The next time it runs (in 24 hours), SAP Solution Manager can get this maintenance certificate in the SAP global support backbone. • The maintenance certificates are passed to the SAP Solution Manager, where they are saved and made available. • The task Maintenance Package runs daily in the managed systems, in the Service Data Control Center (transaction SDCCN). It gets the maintenance certificate from the SAP Solution Manager by RFC. • If a maintenance certificate has been fetched, it is saved locally in the SAP license management (transaction SLICENSE). • If the installation tools SPAM or SAINT import SAP Support Packages or SAP Support Package Stacks, the system is checked for a valid maintenance certificate.

© SAP AG

E2E200

7-82

SAP Solut ion M a na ge r Lic ense M anage me nt
Manage automatic distribution of Maintenance Certificate and licenses per system. Download received Maintenance Certificate and Licenses in bulk Filter

Status in the managed system (TA SLICENSE)

job REFRESH_ADMIN_DATA_FROM_SUPPORT – download the maintenance certificate from SAP backbone

© SAP 2009

̈ ̈

For more information, see http://help.sap.com å SAP Solution Manager å Change Request Management and Change Control å License Management. The following prerequisites are fulfilled in the managed system in order to display the licenses and maintenance certificates of the managed system in the license management: • The software component ST-PI has at least the SAP support package: - SAP Basis 700: ST-PI 2008_1_700 Support Package 06 - SAP Basis 710: ST-PI 2008_1_710 Support Package 04 • The following prerequisites are fulfilled in the SAP Solution Manager system, to be able to display the licenses and maintenance certificates of the managed system in the license management: Automatic Data Capture for System Landscape is set up (background job LANDSCAPE FETCH).

© SAP AG

E2E200

7-83

M a inte na nc e M anagem ent : U nit Ove rvie w Dia gra m
Maintenance Management Lesson 1: SAP Maintenance Strategy Lesson 2: Types of Maintenance Lesson 3: SAP Enhancement Packages Lesson 4: Maintenance Optimizer Lesson 5: Software Lifecycle Management Tools Lesson 6: Maintenance Certificate Lesson 7: Upgrade / Change Impact Analysis Lesson 8: Best Practice Recommendations

© SAP 2009

© SAP AG

E2E200

7-84

U pgrade /Cha nge I mpac t Ana lysis is Pa rt of t he Cust om De ve lopm ent M a na ge m ent Coc kpit

Custom Development Management cockpit is a tool that helps to analyze the use of customer developments as well as to optimize their upgrades. Key capabilities:
̈

Clearing Analysis: Analysis the use of custom developments in a SAP system combined with an identification of potentially unused objects

̈

Upgrade/Change Impact Analysis Identification of potential impacts an upgrade can have on customer individual developments

Consider im ple m e nt ing a solution t hat helps you t o c re at e lea n a nd c onsist e nt de velopm e nt a nd t e st e nvironm e nt s ba se d on re al busine ss dat a
© SAP 2009

̈ ̈

CDMC consists of two parts, the clearing analysis (CA) and the Upgrade/Change Impact Analysis (UCIA). With the clearing analysis, you can identify and analyze obsolete customer-specific workbench objects. The results of a clearing analysis are an ideal starting point for the clearing process for custom development. With the Upgrade/Change Impact Analysis, you can find out about the technical impact of an SAP Upgrade or Support Package on your custom developments and estimate the amount of work required for adapting them.

̈

© SAP AG

E2E200

7-85

U pgrade /Cha nge I mpac t Ana lysis T he Cha lle nge

Which custom objects need to be adjusted?

Which transactions should be included in the test plan?

What effort is required for the adjustment of the custom code?

Which transactions are not affected by the upgrade?

© SAP 2009

© SAP AG

E2E200

7-86

U pgrade /Cha nge I mpac t Ana lysis T he Princ iple

Customer objects/piecelist using changed SAP objects

SAP objects used by customer objects/piecelist

SAP objects changed (for example, by Support Packages)

© SAP 2009

© SAP AG

E2E200

7-87

Cust om De ve lopm ent M a na ge m ent Coc kpit H ow t o Ac c e ss?
1. Via Workcenter Implementation /Upgrade 2. Via SAP GUI

© SAP 2009

̈

The custom development management cockpit is available as of the SAP Solution Manager 7.0 EhP1 and can be accessed in two ways: • Through the Solution Manager work center • Via SAP GUI

© SAP AG

E2E200

7-88

U pgrade /Cha nge I mpac t Ana lysis Globa l Se t t ings
̈ ̈

Maintain average adjustment times for every customer object type Adjustment times appear on the result list for every customer object and will be the basis for a first effort estimation for adjusting the custom objects in the course of an upgrade

© SAP 2009

̈

In the „global settings“ phase, the preparations for an Upgrade/Change Impact Analysis project is limited to the maintenance of average adjustment times per object type. These times reflect the average duration that is necessary to adjust a custom development in the course of an upgrade. This information will be the basis for a first effort estimation to adjust the custom objects in the course of an upgrade to ensure a better planning security and helping to keep the upgrade costs within the given budget.

© SAP AG

E2E200

7-89

Proje c t Ove rvie w Sc re e n

̈ ̈

Activities are clustered into phases For every activity in the process tree: Documentation Executable function

̈

Status information provided in the project overview screen: Running Completed, o. k. Warning Terminated

© SAP 2009

̈ ̈ ̈

The Project Overview screen is your central “cockpit“ for all activities in an Upgrade/Change Impact Analysis (UCIA) project. The project tree (as shown on the slide) contains all activities for a UCIA project. Each activity has an executable function, which you start by choosing the Execute symbol next to the relevant activity. You also get the admin information that you require to monitor the progress of each activity and of the project as a whole, for example the activity status and the runtime. An activity log with more detailed status information is available for each activity that has been executed. In addition, the Project Overview screen contains general information about your project and the participating systems, so that you have it at hand at any time during your project.

̈

© SAP AG

E2E200

7-90

U pgrade /Cha nge I mpac t Ana lysis Proje c t Syste m La ndsca pe
CDMC Analysis Systems CDMC Control System
Central solution manager system (recommended)

QAS
1
Rel. 4.7

CDMC Reference System/ Knowledge Base
Testsystem Rel. ECC 6.0 or a knowledge base content

QAS2
Rel. 4.6c

or
QAS
3
Rel. 4.7

Knowledge Base Content

QAS4
Rel. ERP2004

© SAP 2009

̈

The first thing you do in preparation to an Upgrade/Change Impact Analysis project is to define the system landscape in which you want the project to take place. There are three system roles you need to
consider: system roles are triggered from here via RFC connections. CDMC projects and their process trees are created and accessed in the control center. The results of the analyses are transferred from all other systems to this system so that you can view and maintain them here. Usually this system role is taken over by the central solution manager system as it provides integration aspects into other solution manager applications which is the launch of CDMC within the workcenter implementation/upgrade and the upgrade roadmap. In the analysis systems, all project-related analyses (including selection of relevant objects) are executed, and the results are stored in a CDMC database table. This is to avoid putting too much load on the production system. The role analysis system is usually taken over by the QAS system and should contain a consistent set of custom development objects used for the subsequent analysis activities. If this is not the case, a system reconciliation needs to be performed by activity “check TADIR inconsistencies” between the analysis and statistic system. A typical analysis system would be a QAS system. The reference system is a system in which the upgrade or other planned change has already been carried out, so that the SAP objects exist there in the version from after the change. During the impact analysis, this version is compared against the version from before the change that is stored in the analysis system. The test system for the upgrade might well be used as the reference system. The main goal of having a Knowledge Base for the CDMC Upgrade/Change Impact analysis is to provide features to customers that help them to get an estimation about workload of harmonization activity even before doing a test Upgrade. Customers can use the knowledge base to get an idea about workload of harmonization, calculate the budget for their upgrade project, and make a 'Yes' or 'No' decision, and then if required, they can go for a test upgrade. Therefore, the major task is to provide an alternative approach for identifying the details of changed SAP Objects in case the customer does not have a test upgraded system or a reference system. SAP recommends a three-system landscape consisting of control system, analysis system and reference system. However, it is also possible to combine the analysis and control system in one system ID. Typically, these roles would be taken over by the QAS system. This approach has the effect of loosing the integration

̈ In the control system, the control center for all CDMC projects is located. All activities in systems with other

̈

̈

̈

̈

aspects of CDMC into the central solution manager system, for example, the launch of CDMC via the workcenter implementation/upgrade and via the upgrade roadmap. The reference system in this case would run on a separate system ID.
© SAP AG E2E200 7-91

U pgrade /Cha nge I mpac t Ana lysis Pha se s of a Proje c t
Key activities

̈

Project settings ̈ Define project landscape
̈ ̈ ̈

Maintain copied program list Display SAP Notes Maintain adjustment times

̈

Analysis
̈ ̈ ̈ ̈ ̈

Find used SAP objects Find changed SAP objects Perform remote comparison Customer Batch Input Analysis Analysse External Subroutine Calls

̈

Display
̈

Display and evaluate results

© SAP 2009

̈ ̈

An Upgrade/Change Impact Analysis project consists of four phases: Project settings, collect, analysis, and display. The project settings phase includes three activities: Defining the system landscape for the project (as described above), displaying the relevant SAP Notes and to maintain the adjustment times. The background for the activity of displaying the relevant SAP Notes is as follows: In the general settings for your CDMC installation, you defined SAP notes that are likely to be relevant for your projects. (This is described in more detail in the overview tutorial for CDMC.) When you execute the function for activity Display SAP Notes now, you get this list of Notes and can check out the ones that are likely to contain useful information for the project at hand. In the activity „maintain adjustment times“ you define the average adjustment times per object type for your custom developments.

© SAP AG

E2E200

7-92

U pgrade /Cha nge I mpac t Ana lysis Pha se s of a Proje c t
Key activities
̈

Project settings
̈ ̈ ̈ ̈

Define project landscape Maintain copied program list Display SAP Notes Maintain adjustment times

Analysis Activities

̈

Analysis
̈ ̈ ̈ ̈ ̈

Find used SAP objects Find changed SAP objects Perform remote comparison Customer Batch Input Analysis Analysse External Subroutine Calls

Log Information

̈

Display
̈

Display and evaluate results

© SAP 2009

̈

The “analysis“ phase consists of the activities: • Find used SAP objects • Find changed SAP objects • Perform remote comparison • Customer batch input analysis • Analyse external subroutine calls

̈

We will have a more closer look on the functioning on each single activity on the subsequent slides.

© SAP AG

E2E200

7-93

Ana lysis Pha se of a U CI A Projec t Ac t ivit y 1 /3
Project Settings Analysis Display Results

Step 1: Find the SAP objects that are used by (referred to) custom objects or piecelist

Custom Objects

SAP objects
SAP objects used by custom objects

or Piecelist
e.g. transactions and reports used

© SAP 2009

̈

In the first analysis activity, a list of all the SAP objects that are being used in your custom developments is prepared. You can choose if you want the list to cover all objects in the customer namespace or only objects from the specified development classes (packages).

© SAP AG

E2E200

7-94

Ana lysis Pha se of a U CI A Projec t Ac t ivit y 2 /3
Project Settings Analysis Display Results

Step 2: Find used SAP objects that change during the upgrade

SAP objects used by custom objects/ piecelist

Used and changed

SAP objects changed during upgrade

© SAP 2009

̈

In the next activity, you find the intersection of the SAP objects used in the customer-specific objects and the SAP objects changed during the upgrade (or other change). When using a reference system, the program for this activity runs in the reference system. If you want to check the implications of a transport for a support package or correction, you can specify this transport in the dialog box that is displayed when you execute the function. When using the knowledge base, a check is carried out to verify if the knowledge base content for the specified Knowledge base name is available in the control system.

̈

© SAP AG

E2E200

7-95

Ana lysis Pha se of a U CI A Projec t Ac t ivit y 3 /3
Project Settings Analysis Display Results

Objects covered:
̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈

Domains Data elements Search helps Lock objects Views Tables Function modules Programs …

Step 3: Compare version from A system with version from R system

Determine impact of changes

SAP objects Used used by and custom objects/ changed piecelist

SAP objects changed during upgrade

© SAP 2009

̈

In the last activity of this phase, you compare the found objects in the reference system/knowledge base against their counterparts in the analysis system. The program that runs in this activity does the comparison and evaluates the results. For each custom object, the program notes if it is affected by the planned upgrade or change or not. In addition, the program uses the results of the comparison and the adjustment times you specified earlier to calculate the estimated effort required to adjust these objects. Note that this activity, like all the others, is triggered from the control system and obtains the required information from the analysis system and the reference system through the RFC connections. In case the knowledge base is used, no RFC connections are necessary to the reference system as the knowledge base data is stored in the control system.

̈

© SAP AG

E2E200

7-96

U pgrade /Cha nge I mpac t Ana lysis Pha se s of a Proje c t
Key activities

̈

Project settings
̈ ̈ ̈ ̈

Define project landscape Maintain copied program list Display SAP Notes Maintain adjustment times

̈

Analysis
̈ ̈ ̈ ̈ ̈

Find used SAP objects Find changed SAP objects Perform remote comparison Customer batch input analysis Analyse External Subroutine Calls

̈

Display
̈

Display and evaluate results

© SAP 2009

̈ ̈

When the comparison is finished, you can look at the analysis results and decide how to proceed with the listed objects. We will explain how to work with the result list in the next lesson.

© SAP AG

E2E200

7-97

Syste m De m o

Upgrade/Change Impact Analysis

© SAP 2009

© SAP AG

E2E200

7-98

Work ing w it h t he Re sult List Assign Proce ssor

© SAP 2009

̈

When the comparison is finished, you can look at the analysis results and decide how to proceed with the listed objects. The example given on the slide has been simplified to show you the basic structure of the list. In the real CDMC environment, you have various options for viewing and filtering the data. For example, you can choose between a compressed view and a detailed view. The process for obtaining and further analyzing the objects in question according to the use case at a glance look as follows: • Select the objects in question you would like to analyze • Determine the estimated effort connected to the affected objects • Assign a processor to the objects • Send notification to the processors • Analysis of the impact the SAP object has on the customer object by using the following features - Remote Comparison of referenced SAP objects - Retrieval of further object details • Set the status of each object on To be analysed.

̈

© SAP AG

E2E200

7-99

Work ing w it h t he Re sult List Se t St a t us

© SAP 2009

̈

You can also set the status for each object you analyzed and assign a “processor”, that is, a person who should analyze the given object in more detail and decide how to handle it. You can download the results in a piece list and send them to the assigned processors.

© SAP AG

E2E200

7-100

Work ing w it h t he Re sult List Displa y T e chnica l Se ve rit y

© SAP 2009

̈

The meaning of the traffic lights in the Impact column is as follows: • A green traffic light means that no adaptation of the object is required in connection with the planned upgrade or change. • A yellow traffic light means that adaptation of the object is probably required. • A red traffic light means that the object must be adapted to ensure its correct functioning after the upgrade (or other change).

̈

Note that the traffic lights in column Impact of the compressed view represent a summary evaluation for each custom object. This evaluation is based on a detailed analysis of each SAP object used by the given custom object. The detailed view shows the results of the analysis and provides more information about the rating criteria. To give you just one example: If the data type for a data element changes during the upgrade, the data element gets a red light in the detailed analysis, and all custom object that refer to this data element also get a red light in the summary impact evaluation.

© SAP AG

E2E200

7-101

T e c hnic a l Seve rit ies Cha nges w ith Crit ic a l I m pa ct (Re d T ra ffic Light )
OBJ_ TYPE OBJ_ TYPE FORM FORM FORM FUNC FUNC FUNC SHLP TABL TTYP TTYP TTYP VIEW VIEW
© SAP 2009

DESCRIPTION The object does not exist in one of the systems

DESCRIPTION Interface Parameter(s) in Anal. Sys not found in Ref. Sys Attributes of the interface parameter(s) have changed Form Routine does not exist in the Upgraded System Interface Parameter(s) in Anal. Sys not found in Ref. Sys Attributes of the interface parameter(s) have changed Function module flagged as obsolete Number of fields has changed Primary Key changed Attributes of reference object have changed Key components of table type object have changed Row type has changed Number of fields has changed Number of databases changed

CLAS CLAS CLAS CLAS DOMA DTEL DYNP DYNP DYNP ENQU

Attributes have changed Method has changed Parameters of Method have changed Method Properties changed Data type has changed Data type has changed Screen Field discontinued in the Upgraded System Discontinued Screen in the Upgraded System Screen Field Format has changed in the Upgraded system Lock parameters have changed

© SAP AG

E2E200

7-102

Work ing w it h t he Re sult List Re mot e Compa re

© SAP 2009

© SAP AG

E2E200

7-103

Syste m De m o + Ex e rc ise

Working with the Result List

© SAP 2009

© SAP AG

E2E200

7-104

Appe ndix : I m port a nt SAP N ot e s for t he Cust om De ve lopm ent M a na ge m ent Coc kpit

SAP Note Number
1243233

Title
Information about Custom Development Management cockpit Installation of Custom Development Management cockpit

Description
Collective note for Custom Development Managment Cockpit CDMC Information about how to install the Custom Development Management cockpit

1244713 .

© SAP 2009

© SAP AG

E2E200

7-105

M a inte na nc e M anagem ent : U nit Ove rvie w Dia gra m
Maintenance Management Lesson 1: SAP Maintenance Strategy Lesson 2: Types of Maintenance Lesson 3: SAP Enhancement Packages Lesson 4: Maintenance Optimizer Lesson 5: Software Lifecycle Management Tools Lesson 6: Maintenance Certificate Lesson 7: Upgrade / Change Impact Analysis Lesson 8: Best Practice Recommendations Side-Effect Reporting Support Package Content Analysis HotNews Inbox Customer Specific Aspects
© SAP 2009

© SAP AG

E2E200

7-106

Side Effec t s of Single N ot e s

© SAP 2009

̈

In some cases, SAP Notes and Support Packages are dependent on each other. Resolving a particular issue with one SAP Note may cause new issues to arise in other areas or situations. To resolve these new issues, SAP publishes new SAP Notes that are related to the original SAP Note. Before implementing an SAP Note, you should check if it has any side effects. On SAP Service Marketplace at http://service.sap.com/notes you can view any known side effects on the Side Effects tab of a single SAP Note. The upper table on this tab displays other SAP Notes that can be corrected using this SAP Note, whereas the lower table shows other SAP Notes that correct the side effects of this SAP Note.

̈

© SAP AG

E2E200

7-107

Side -Effec t s Re port ing: Ca lcula t ion for Support Pa c kage Queue s
Side-Effect Report

SPy

Note
----------------------

Version
SuppPackage -------------

Version

Note
Side-effect --------

776552

SPx

Note
73510 276432 23443 234234 655465 464564 456466 33535 223424 23223

Version
SuppPackage 0012 0010 0001 0003 0005 0008 0001 0001 0002 0004

Version

Note
Side-effect 376552

-----

743543
--------

...

0003 0004

343543

0002 321254, ...

Example

Queue Calculation:
> Side > Side

Effects that are solved within the same SP queue will be filtered automatically î Individual calculation

Effects that are solved within an SP queue of another software component are not yet filtered automatically only in the SAP Solution Manager.

© SAP 2009

̈ ̈ ̈ ̈

SAP Support Packages are collections of SAP Notes that provide software corrections. Since SAP Notes in subsequent Support Packages solve most of the side effects caused by a Support Package, these notes must be excluded from the list of side effects. Only side effect notes which are not contained in the import queue need to be imported separately after a Support Package import. Open topics of Side Effect reporting, see SAP Note 684859.

© SAP AG

E2E200

7-108

Side -Effec t Report ing ove r t he Whole St ac k in t he SAP Solut ion M anage r

Request side effects for ABAP Support Package Stack from the Service market

© SAP 2009

̈

The files selected for implementation and product maintenance are listed in a table which also contains details and information about side effects of the corrections for each Support Package as well as for the whole stack. You can order the side effect from the Service Market for the single ABAP Support packages or for the whole Support package stack. A link will be provided to you were you can select the side effects you want to download.

© SAP AG

E2E200

7-109

Side Effec t s Re port ing T ool in t he SAP Se rvic e M a rk e t place

© SAP 2009

̈

To allow easier detection of these interdependencies, a reporting tool is available on the SAP Service Marketplace. When importing a Support Package or SAP Note, you can check for known side effects and find relevant SAP Notes to treat these. Using the tool, you can proactively prevent problems that may occur as a result of applying Support Packages or SAP Notes, not only accelerating and improving the quality of issue resolution, but also reducing maintenance effort and costs.

© SAP AG

E2E200

7-110

N um be r of K now n Side Effec t s ove r t he T im e

Number of Known Side Effects

Development Close

Internal Tests

Release of SP Stack

Customer Projects

Most bugs are fixed

Internal Messages

Customer Messages

Side effect Notes
© SAP 2009

Side effect Notes

̈ ̈

The number of known side effects of a Support Package rises continuously after the time of the development close. Most side effects are known at the time a support package is released. However, if you execute the side effect report several times, you might see more known side effects if you execute the reporting at a later point in time.

© SAP AG

E2E200

7-111

M a inte na nc e M anagem ent : U nit Ove rvie w Dia gra m
Maintenance Management Lesson 1: SAP Maintenance Strategy Lesson 2: Types of Maintenance Lesson 3: SAP Enhancement Packages Lesson 4: Maintenance Optimizer Lesson 5: Software Lifecycle Management Tools Lesson 6: Maintenance Certificate Lesson 7: Upgrade / Change Impact Analysis Lesson 8: Best Practice Recommendations Side-Effect Reporting Support Package Content Analysis HotNews Inbox Customer Specific Aspects
© SAP 2009

© SAP AG

E2E200

7-112

Ge t List of N ot e s from SAP Se rvic e M a rk e t place
http://service.sap.com/swdc Click title to get the list of notes

© SAP 2009

̈ ̈ ̈

SAP Support Packages are collections of SAP Notes. You can see the available Support Packages in the Software Download Center of the SAP Service Marketplace. If you click on the title of a Support Package, you get a list of SAP Notes which are contained in it.

© SAP AG

E2E200

7-113

List of N ot e s in a Support Pa c ka ge

© SAP 2009

̈

Expand the list and download it.

© SAP AG

E2E200

7-114

N um be r of N ot e s pe r Applic a t ion Subc omponent
̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈

FI-AP-AP FI-GL-GL XX-CSC-IN AP-MD-BP MM-PUR-GF XX-CSC-BR LE-SHP-DL CO-PC-ACT FI-AA-AA

Accounts Payable General Ledger Country Spec. India Business Partner Purchasing Country Spec. Brazil Delivery Processing Actual Costing Asset Accounting

602 544 436 405 377 319 304 287 284 280

Identify relevant components with most changes

FS-BP Fin.Serv. – Bus.Part.

© SAP 2009

̈ ̈

Now the number of notes is displayed per application subcomponent. This view makes it clear in which areas most changes took place. The customer can now select components which are relevant for him. He can also see if there are components which have no changes at all.

© SAP AG

E2E200

7-115

Ana lyze Short t e x t for N ot e s of Re le vant Component s

Delivery Processing is a critical application for this customer. Therefore, he checked the short texts of all notes in this component. Critical notes will be checked in more detail. In addition, all notes with priority 1 should be checked. These are the Top Issues which were solved with the Support Package Stack.

© SAP 2009

̈ ̈

For the relevant components, you can now quickly review the short text of the notes and decide if the individual note is relevant. The relevant notes must then be read in detail.

© SAP AG

E2E200

7-116

M a inte na nc e M anagem ent : U nit Ove rvie w Dia gra m
Maintenance Management Lesson 1: SAP Maintenance Strategy Lesson 2: Types of Maintenance Lesson 3: SAP Enhancement Packages Lesson 4: Maintenance Optimizer Lesson 5: Software Lifecycle Management Tools Lesson 6: Maintenance Certificate Lesson 7: Upgrade / Change Impact Analysis Lesson 8: Best Practice Recommendations Side-Effect Reporting Support Package Content Analysis HotNews Inbox Customer Specific Aspects
© SAP 2009

© SAP AG

E2E200

7-117

U se SAP’s T hre e I mport a nt N ot e Se rvice Offe rings
1. SAP HotNews
̈ ̈

Contain solutions for customer problems with very high priority, such as systems standstills or data loss Allow customers to filter and display SAP HotNews for their chosen components

2. SAP TopNotes
̈ ̈ ̈ ̈

Inform you about potential hot spots in your projects Published on a monthly basis Represent the ten most important SAP Notes for each component Reviewed monthly by experts in the relevant departments and updated based on the current SAP Note customer usage rate

3. SAP FAQNotes
̈ ̈

Present the most frequently asked questions for particular topics with brief and 'to-the-point' answers Ideal place to start looking for a quick and easy answer before embarking on a full-blown search

© SAP 2009

̈

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. SAP TopNotes are the most important notes of a component or a subcomponent reported on successfully closed customer support messages. The selection of the 10 most successful notes is done regularly, on a monthly basis, in a semi-automatic process. The process is described in note 568167.

̈

© SAP AG

E2E200

7-118

Be st Pra c t ic e for H ot N e w s a nd T opN ot es

Set up regular procedures to check for new HotNews
̈ ̈

HotNews å Weekly cycle TopNotes å Monthly cycle

Solution Manager
̈ ̈ ̈ ̈

Define a responsible person to check for new HotNews and create Change Requests (for example, Change Control Engineer) Change requests are forwarded to the person responsible for the module Choose components where a customer opened OSS calls in last 3 – 6 months Get SAP Service Marketplace Newsletter weekly

© SAP 2009

© SAP AG

E2E200

7-119

Work cent e r – H ot N e w s I nbox

Select a Solution, then you can find all SAP HotNews belong the Solution

SAP HotNews:
Contains solutions for customer problems with very high priority, such as systems standstills or data loss Allows customers to filter and display SAP HotNews for their chosen components.

© SAP 2009

̈

You can access the existing HotNews directly in an active solution.

© SAP AG

E2E200

7-120

Syste m De m o

HotNews Inbox

© SAP 2009

© SAP AG

E2E200

7-121

M a inte na nc e M anagem ent : U nit Ove rvie w Dia gra m
Maintenance Management Lesson 1: SAP Maintenance Strategy Lesson 2: Types of Maintenance Lesson 3: SAP Enhancement Packages Lesson 4: Maintenance Optimizer Lesson 5: Software Lifecycle Management Tools Lesson 6: Maintenance Certificate Lesson 7: Upgrade / Change Impact Analysis Lesson 8: Best Practice Recommendations Side-Effect Reporting Support Package Content Analysis HotNews Inbox Customer-Specific Aspects
© SAP 2009

© SAP AG

E2E200

7-122

M a inte na nc e M anagem ent Be st Pra c t ic e Re com me nda t ions
When to implement Support Packages?
å SAP recommends to follow the Support Package Stack schedule
̈

At least every second SP stack should be implemented.

Aspects influencing timing of the import:
̈ ̈ ̈

Schedules of custom development releases Support Package Stack schedule Seasonal aspects like holiday periods

How to implement Support Packages?
A central question is whether the SP Stack import should be bundled with a major custom development release or treated as a “standalone” process. There are several competing factors determining this decision:
̈ ̈ ̈

Time required to propagate the Support Packages through the landscape should be as short as possible due to the impact on production support Requirement to deliver the upgrade to production by certain date due to possible legal requirements Effort required to perform system build (sandbox) and test activities should be minimized

© SAP 2009

© SAP AG

E2E200

7-123

M a inte na nc e M anagem ent Be st Pra c t ic e Re com me nda t ions
How to handle Support Package Stacks across the Solution Landscape? Should SPs be imported into all systems of the solution at the same time?
̈ ̈

Advantage: Interfaces have to be tested only once. Challenge: High effort for testing at one point in time (resource constraints)

Aspects to be considered
̈

The dependency network in the solution landscape is large (many different components playing a role in E2E business processes) Very difficult to determine subsets for testing Some of the new components have a higher frequency of changes (because of either not sufficient maturity or business requirements for new functions) Some of the components require legal changes

̈ ̈

An overall maintenance schedule needs to be defined reflecting the landscape as well as the specific requirements. This schedule can change over time (decision fixed only for the next year).

© SAP 2009

© SAP AG

E2E200

7-124

M a inte na nc e M anagem ent Sum m a ry of Re com me nda t ions
̈

Perform Side Effect Reporting å Eliminate problems because of dependencies to other Notes and avoid already known bugs in SPs and Notes Identify the potential impact of a given SP on custom developments Identify affected business process and custom objects by analyzing the SAP Notes within a SP
̈ ̈

̈ ̈

Input for defining the test focus for these SPs Input for planning for adjustment of custom objects

̈ ̈ ̈

Besides a pure manual analysis you can leverage the tool SAP Business Process Change Analyzer as part of SAP Solution Manager to automate this process. Use SP stacks instead of single SPs - stacks consist of special bundles of SPs that are tested in this combination internally thus ensuring higher quality. See also the following slide. Leverage the maintenance optimizer to download SPs and obtain transparency of downloaded and implemented SPs
̈ ̈

This functionality will be extended with the upcoming Solution Manager SPs For the download of SAP Enhancement Packages the maintenance optimizer is mandatory to calculate dependencies between the different software components. Participate from the experiences SAP and other customers have made î Implement these very high priority Notes proactively

̈

Proactively check SAP HotNews – leverage the SAP Solution Manager HotNews Inbox
̈

© SAP 2009

© SAP AG

E2E200

7-125

M a inte na nc e M anagem ent : U nit Sum m a ry

You should now be able to:
̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈

Understand the SAP Maintenance Strategy Describe all types of support items delivered by SAP Explain the Support Package Stack strategy Describe the enhancement package concept Explain the role of SAP Solution Manager in the maintenance process Know the software lifecycle management tools to implement patches and find information on current patch levels Perform an upgrade or change impact analysis with the custom development management cockpit Execute side effect reporting for a Support Package queue Find and implement HotNews as urgent correction Know SAP’s best practice recommendations for maintenance management

© SAP 2009

© SAP AG

E2E200

7-126

Exercises
Unit: Lesson: Maintenance Management Support Package Stacks

At the conclusion of this exercise, you will be able to: • Find information on available Support Package Stacks in the SAP Service Marketplace

You need to log on to the SAP Service Marketplace with your own Suser.

7-1

Find the latest available Support Package Stack. 7-1-1 Log on to the SAP Service Marketplace with your S-user. Where can you find information on the available Support Package Stacks? Check the latest Support Package Stack for SAP ERP 6.0. What is the name of this stack?

7-1-2

© SAP AG

E2E200

7-127

Exercises
Unit: Lesson: Maintenance Management Version Information

At the conclusion of this exercise, you will be able to: • Find information on installed software versions in SAP Solution Manager

TT4 is the SAP Solution Manger system that contains all information about the managed systems. TT5 is a satellite system that is managed by TT4.

7-2

Detection of version information 7-2-1 Log on to SAP Solution Manager system TT4 and check the support package level for the ERP system TT5. Where can you find this information? What is the release and Support Package level for the ABAP software component SAP_APPL of the ECC server? What is the release and Support Package level for the Java software component SAP_ESS?

7-2-2

7-2-3

© SAP AG

E2E200

7-128

Exercises
Unit: Lesson: Maintenance Management Enhancement Packages

At the conclusion of this exercise, you will be able to: • Find information on new functionality in Enhancement Packages • Find information on the required technical usages • Learn important aspects for the planning of an Enhancement Package project You need to log on to the SAP Service Marketplace with your own S-user.

7-3

Find information about new functionality within Enhancement Packages 7-3-1 Check for new functionality in Retail in the SAP Enhancement Packages Information Center: http://service.sap.com/erp-ehp. Look at the details of the business function Retail, Method of Accounting (ISR_RETAIL_RMA). Which information is available? As of which Enhancement Package is this business function available? Answer: _____________________________________________________ Note: Another way to find information about new functionality is the Solution Browser tool. This can be found at http://solutionbrowser.erp.sap.fmpmedia.com/. 7-3-3 Which technical usage must be implemented as a prerequisite for your selected business function? Note: The mapping between business functions, technical usages, and software components for EHP3 is described in SAP Note 1083576. The relevant pages are attached at the end of the exercise description. Answer: ___________________________________________________

7-3-2

© SAP AG

E2E200

7-129

Exercises
Unit: Lesson: Maintenance Management Maintenance Optimizer

At the conclusion of this exercise, you will be able to: • Create a new maintenance activity in the maintenance optimizer • Find existing maintenance optimizer activities •

TT4 is the SAP Solution Manger system that contains all information about the managed systems. TT5 is a satellite system that is managed by TT4.

7-4

SAP maintenance optimizer 7-4-1 Create a new maintenance activity for the Enhancement Package installation with the maintenance optimizer. Enter or select the following data: Short text: ERP EhP Installation ## (## is your user number) Solution: E2ECC_## Product version: SAP ERP 6.0 Logical component: Z_ERP_CCM 7-4-2 On the next screen select Enhancement Package Installation. Save your input and exit the transaction by pressing the Cancel button. Check all completed maintenance activities for the E2ECC Demo Solution in the reporting transaction of the maintenance optimizer. What is the transaction name? Answer: _____________________________________________________ Which support packages were downloaded in these maintenance activities? Answer: _____________________________________________________

7-4-3

© SAP AG

E2E200

7-130

Exercises
Unit: Lesson: Maintenance Management Upgrade/Change Impact Analysis

At the conclusion of this exercise, you will be able to: • Perform an upgrade/change impact analysis with the Custom Development Management Cockpit • Find customer objects that must be reviewed after the implementation of an SAP software package • TT4 is the Solution Manger system that contains all information about the managed systems. TT5 is a satellite system that is managed by TT4.

7-5

Custom Development Management Cockpit – upgrade/change impact analysis 7-5-1 Start the Custom Development Management Cockpit and create a new upgrade/change impact analysis project. Enter the project name 001## (where ## is your group number) and a short description. Navigate into your newly created project and read the description of the first activity: Define Project Landscape. Execute the activity and enter the following systems: • • • 7-5-3 Control Center: NONE (= local system TT4)

7-5-2

Analysis System: SM_TT5CLNT800_TRUSTED Reference System: NONE (= local system TT4)

Maintain the adjustment times. Make the following entries:

© SAP AG

E2E200

7-131

7-5-4

Perform the first analysis activity: Find Used SAP Objects. Again, first read the description and then execute the activity. Restrict the object selection to the development class ZCDMC. The analysis takes about five minutes. Choose Refresh to see if the analysis is already completed.

7-5-5 Perform the second analysis activity: Find Changed SAP Objects. Again, first read the description and then execute the activity. Compare all used SAP objects. 7-5-6 Perform the third analysis activity: Perform Remote Comparison. Again, first read the description and then execute the activity. 7-5-7 Display the results for development class ZCDMC. What is the total effort for the adjustment time? Answer: ______________________________________________________ What is the reason for the yellow traffic light of the customer object DTEL ZCHARG? Answer: ______________________________________________________ In the detailed view, perform a remote comparison for the used object DOMA CHARG. Enter the local system (NONE) as source system and the RFC connection SM_TT5CLNT800_TRUSTED as the destination system and as RFC connection. What was changed in the object DOMA CHARG? Answer: ______________________________________________________ What is the reason for the red traffic light of the customer object TABL ZTEST_DUMP1_SA? Answer: ______________________________________________________

© SAP AG

E2E200

7-132

SAP Note 1083576: EhP3_BF_TU_Mapping_v6.pdf

© SAP AG

E2E200

7-133

© SAP AG

E2E200

7-134

Solutions
Unit: Lesson: Maintenance Management Support Package Stacks

7-1

Find the latest available Support Package Stack. 7-1-1 Log on to the SAP Service Marketplace with your S-user. Where can you find information on the available Support Package Stacks? The URL is http://service.sap.com/sp-stacks. 7-1-2 Check the latest Support Package Stack for SAP ERP 6.0. What is the name of this stack? In the SAP Business Suite SP Stacks area, choose SAP ERP 6.0 (SAP ERP 2005). In the next window, the latest target stack is pre-selected in the Target Stack field. Write down the name of the target stack.

© SAP AG

E2E200

7-135

Solutions
Unit: Lesson: Maintenance Management Version Information

7-2

Detection of version information 7-2-1 Log on to SAP Solution Manager system TT4 and check the support package level for the ERP system TT5. Where can you find this information? Go to the Solution Manager work center by choosing System Landscape Management System Management. Select system TT5 from the list.

7-2-2

What is the release and Support Package level for the ABAP software component SAP_APPL of the ECC server? The release is 600 and the Support Package level can be found in the Software Components list on the bottom of the screen.

7-2-3

What is the release and support package level for the Java software component SAP_ESS? The release is 600 and the support package level can be found in the Software Components list.

© SAP AG

E2E200

7-136

Solutions
Unit: Lesson: Maintenance Management Enhancement Packages

7-3 Find information about Enhancement Packages. 7-3-1 Check for new functionality in Retail in the SAP Enhancement Packages Information Center: http://service.sap.com/erp-ehp. Go to http://service.sap.com/erp-ehp. Choose Industries Retail

7-3-2

Look at the details of the business function Retail, Method of Accounting (ISR_RETAIL_RMA). Which information is available? As of which Enhancement Package is this business function available? Answer: ISR_RETAIL_RMA is available as of Enhancement Package 3. Note: Another way to find information about new functionality is the Solution Browser tool. This can be found at http://solutionbrowser.erp.sap.fmpmedia.com/

7-3-3

Which technical usage must be implemented as a prerequisite for your selected business function? Note: The mapping between business functions, technical usages, and software components for EHP3 is described in SAP Note 1083576. The relevant pages are attached at the end of the exercise description. Answer: The business function ISR_RETAIL_RMA requires the technical usage Retail. Note: “Broad” or “selective” installation could be chosen. You should choose the selective approach because you want to install exactly those technical usages that are needed to activate the new business functions that are in scope for your project.

© SAP AG

E2E200

7-137

Solutions
Unit: Lesson: Maintenance Management Maintenance Optimizer

7-4 SAP Maintenance Optimizer 7-4-1 Create a new maintenance activity for the Enhancement Package installation with the maintenance optimizer. Go to the Solution Manager work center, choose Change Management Maintenance Optimizer, and select New Maintenance Transaction. Enter or select the following data: Short text: ERP EhP Installation ## (## is your user number) Solution: E2ECC_## Product version: SAP ERP 6.0 Logical component: Z_ERP_CCM Choose Continue. 7-4-2 On the next screen select Enhancement Package Installation. Save your input and exit the transaction by pressing the Cancel button. Check all completed maintenance activities for the E2ECC Demo Solution in the reporting transaction of the maintenance optimizer. What is the transaction name? The transaction name is /TMWFLOW/MAINTENANCE. Select the Completed checkbox and choose the solution E2ECC Demo Solution. Press Execute. Which support packages were downloaded in these maintenance activities? In the list of the completed maintenance activities, double-click on one activity. On the next screen, click on step number 4 of the maintenance activity Perform Implementation. The downloaded support packages are in the Recorded and confirmed download files block. Expand this block and check the corresponding packages.

7-4-2

© SAP AG

E2E200

7-138

Solutions
Unit: Lesson: Maintenance Management Upgrade/Change Impact Analysis

7-5 Custom Development Management Cockpit – upgrade/change impact analysis 7-5-1 Start the Custom Development Management Cockpit and create a new upgrade/change impact analysis project. Enter the project name 001## (where ## is your group number) and a short description. Start the Custom Development Management Cockpit with transaction CNV_CDMC. Right-click on the Upgrade / Change Impact Analysis folder and choose Create Project. Enter the project name 001## (where ## is your group number) and a short description. 7-5-2 Navigate into your newly created project and read the description of the first activity Define Project Landscape. Execute the activity and enter the following systems: • • • Control Center: NONE (= local system TT4) Analysis System: SM_TT5CLNT800_TRUSTED Reference System: NONE (= local system TT4)

7-5-3

Maintain the adjustment times. Make the following entries:

© SAP AG

E2E200

7-139

7-5-4 Perform the first analysis activity: Find Used SAP Objects. Again, first read the description and then execute the activity. Restrict the object selection to the development class ZCDMC. The analysis takes about five minutes. Choose Refresh to see if the analysis is already completed. Execute the first analysis step Find Used SAP Objects.

In the next screen, select Restricted Object Selection and enter the development class ZCDMC. 7-5-5 Perform the second analysis activity: Find Changed SAP Objects. Again, first read the description and then execute the activity. Compare all used SAP objects. Execute the second analysis step Find Changed SAP Objects.

In the next screen, choose Compare all used SAP objects. 7-5-6 Perform the third analysis activity: Perform Remote Comparison. Again, first read the description and then execute the activity. Execute the third analysis step Perform Remote Comparison.

7-5-7 Display the results for the development class ZCDMC. Choose Display Results and select the development class ZCDMC in the dialog box. What is the total effort for the adjustment time? In the Result screen, select the Adjustment Time column and chose Total . You see the total effort for the adjustment time in the last line of the Result screen. What is the reason for the yellow traffic light of the customer object DTEL ZCHARG?

© SAP AG

E2E200

7-140

Click on the button with the question mark in the Reason column. The data element DTEL ZCHARG uses the domain DOMA CHARG, which was changed. The reason is Fixed values / value table has changed. In the detailed view, perform a remote comparison for the used object DOMA CHARG. Enter the local system (NONE) as source system and the RFC connection SM_TT5CLNT800_TRUSTED as the destination system and as RFC connection. What was changed in the object DOMA CHARG? Toggle to the detailed view by choosing Detailed View in the

. In toolbar. Select object DTEL ZCHARG and choose the reference system TT4, value table MCH1 was removed from the domain. What is the reason for the red traffic light of the customer object TABL ZTEST_DUMP1_SA? Scroll down to the line for the object TABL ZTEST_DUMP1_SA and click on the question mark in the Reason column. The reason for the red traffic light is The Object does not exist in one of the systems. This means the table TABL ZTEST_DUMP1_SA uses the data element DTEL NAME. This is not available in the reference system TT4.

© SAP AG

E2E200

7-141

© SAP AG

E2E200

7-142

T e st M a nage me nt

Unit 1 Introduction to E2E Change Control Management Unit 2 Software Change Strategies Unit 3 Enhanced Change and Transport System Unit 4 Solution Documentation Unit 5 Quality Gate Management Unit 6 Change Request Management Unit 7 Maintenance Management Unit 8 Test Management Unit 9 Change Diagnostics

© SAP 2009

© SAP AG

E2E200

8-1

T e st M a nage me nt : U nit Obje c t ive s

At the end of this unit, you will be able to:
̈ ̈ ̈ ̈

Explain different types of tests and test strategies Understand SAP’s methodology for testing and how it is implemented in SAP Solution Manager Determine the change impact with the Business Process Change Analyzer Use the Test Management Workcenter

© SAP 2009

© SAP AG

E2E200

8-2

T e st M a nage me nt : U nit Ove rvie w Dia gra m
Test Management Lesson 1: Test Methodology Lesson 2: SAP E2E Integration Testing Lesson 3: Business Process Change Analyzer Lesson 4: Test Workbench

© SAP 2009

© SAP AG

E2E200

8-3

T e st St a ge s T ypic a l T e st St a ge s in SAP Proje c t s

Go-Live and Support / Operations

Test Stage User Acceptance Test

Final Preparation

Technical System Test Regression Test

Realization

Integration Test Scenario Test Unit Test

© SAP 2008

© SAP AG

E2E200

8-4

T e st St a ge s De sc ript ion
̈ Unit
̈ ̈

1 /2

Test

A functional test for individual transactions or function modules. It focuses primarily on internal functions rather than integration and interfaces. Interaction with other activities is not tested, with the exception of interfaces within the tested unit.

̈ Scenario
̈ ̈

Test

Test of multiple related transactions, such as a series of transactions within a business area. Test focus is on the interaction between individual transactions and their interfaces.

̈ Integration
̈ ̈ ̈

Test

Integration tests cover complete end-to-end business processes including process variants. Integration tests also include the integration of SAP solutions with non-SAP applications and system interfaces. Customer business processes are mapped in the form of end-to-end scenarios; systems are tested in accordance with cross-module and cross-system scenarios.

© SAP 2008

© SAP AG

E2E200

8-5

T e st St a ge s De sc ript ion
̈ Regression
̈

2 /2

Test

Regression tests ensure that solution functionality and business processes have not suffered adverse effects after a system change.

̈ Technical
̈

System Tests (primarily performance tests)

Technical system tests evaluate the entire system, not only focusing on business processes but also on infrastructure such as database, application servers, front ends, networks, printers, etc. Performance tests are one of the most important technical system tests. They test the runtime behavior (for example, to evaluate answer times, SLAs) of a solution and its infrastructure by simulating system load.

̈

̈ User
̈

Acceptance Test

Final acceptance from project stakeholders/end users for an implementation/project.

© SAP 2008

© SAP AG

E2E200

8-6

T e st Da t a Provisioning Ove rvie w
̈

Test data is vital for the quality of tests. In SAP environments, test data is oftentimes copied or migrated from the production system(s) to the test system. This approach ensures high data quality and enables testers to work in a familiar environment. Within test case descriptions, it has to be ensured that testers know which test data to choose for the execution of the test case that leads to the documented expected result. This can be achieved by either delivering specific test data or a generic description on how to create or access test data. In test automation, the availability of a sufficient amount of test data has to be ensured. Alternatively, test data can also be generated by automation scripts. ???

Input (Test Data)

̈

Check

Output (Test Result)

̈

© SAP 2008

̈ ̈

Test cases should be reviewed if they contain descriptions on how to access or generate test data necessary to execute the described test. Ensure that automated test cases either have sufficient test data available or generate their test data in a prerequisite step.

© SAP AG

E2E200

8-7

T e st Ca se De sc ript ions Wha t Should Be I nc lude d in a Te st Ca se?
Test case descriptions should be based on a unified document template which contain at least the following information:
̈ ̈ ̈ ̈ ̈

Test case title Short description of test case Preparation / prerequisite steps to conduct the test Execution / test steps Expected result

The quality and detail level of test cases should be defined in the test concept. A workflow should be in place to keep the test cases up-to-date when the business processes change.

© SAP 2009

̈

The quality and detail level of test cases should be defined in the test concept. As a general rule, it has to be ensured that the detail level of the test case descriptions is sufficient for every target group, for example, for local testers within a template approach, for test automation by automation experts or for the outsourcing of tests. Additionally, test case descriptions may also contain fields for the tester documentation (actual result). Uploading a test case with documentation by a tester should be supported by the testing tool. Adaptations to business processes result in changed test case descriptions. A workflow should be put in place to ensure that test cases are up-to-date.

̈ ̈

© SAP AG

E2E200

8-8

T e st Sc ope I de nt ifica t ion Wha t Should Be t e st e d?
What should be tested?
̈

The scope of a test and the execution priority of test cases is primarily determined by using a risk-based approach, for example, by evaluating business processes regarding their criticality or usage frequency. The usage frequency of transactions and reports can be determined by the ST03 workload analysis. Manual impact estimation by the developer and business process owner Automated impact analysis with the Business Process Change Analyzer and the custom develepment management cockpit Test cases that showed problems in previous test runs

̈ ̈ ̈ ̈

© SAP 2009

̈

SAP provides different tools for an automated impact analysis: Business Process Change Analyzer and custom development management cockpit.

© SAP AG

E2E200

8-9

Re gre ssion T e st ing a nd T e st Aut oma tion Be st Pra c t ic e Re com me nda t ions
Regression Testing
̈ ̈ ̈

The most critical business processes need to be repeatedly tested after each change (for instance, transports, service pack implementation, process changes). Typically, a regression test set consists of a selection of integration test cases. It is recommended to use a risk-based test case selection for regression testing in combination with a technical change analysis (by using Business Process Change Analyzer).

Test Automation
̈

Automated testing can siginificantly reduce cost and time effort. However, the initial planning of the automation approach as well as the qualification of the internal testing team can be time-consuming. Resources freed by test automation can be used to extend the scope of a regression test. The key criteria to determine an automated test case are business criticality as well as the number of times the test case will be executed in the future.

̈ ̈

© SAP 2009

© SAP AG

E2E200

8-10

T e st M a nage me nt : U nit Ove rvie w Dia gra m
Test Management Lesson 1: Test Methodology Lesson 2: SAP E2E Integration Testing Lesson 3: Business Process Change Analyzer Lesson 4: Test Workbench

© SAP 2009

© SAP AG

E2E200

8-11

M a na ging Cha nges is Crit ic a l for Business Agility M e t hodology, T est Proc ess, a nd T e st Ca pa bilit ies
Methodology
̈

E2E Solution Operations methodology for the ongoing management of end-to-end solutions Run SAP methodology to implement end-to-end solution operations including SAP standards, best practices, roadmap, training, certification, services, and tools for E2E solution operations

̈

New SAP Solution SAP Solution Update

Test Process
Business Blueprint Test Planning Change Impact Analysis Test Execution Apply Changes to Production

̈ ̈ ̈

From change events and change impact analysis … to test planning and test execution … to deployment of changes in production system

Test Capabilities
̈

SAP Solution Manager
̈

SAP Solution Manager acts as central point of access to SAP and 3rd Party test capabilities … as well as additional capabilities like E2E integration validation

© SAP 2009

© SAP AG

E2E200

8-12

E2 E I nt e grat ion T e sting of SAP Solut ions T e st Proc e ss Em bedde d in t he ASAP M e t hodology
Planning
New SAP Solution
̈

Blueprint
Business Blueprint
̈ ̈

Realization

Final Preparation

GoLive

Implementation of new SAP Solution

Business Blueprint Design Solution Configuration

Test Planning System Setup

Test Execution

Deploy Changes to Production

SAP Solution Update

Change Impact Analysis

̈

SAP Support Packages SAP Legal Change Packages SAP Enhancement Packages Customizing changes Custom Code Interface changes

̈

Business Blueprint Update Identification of Business Processes affected by SAP Solution Updates Recommendation of business processes for regression tests

̈

Development of Test Cases Test Plan setup Compilation of Test Packages Assigment of Testers Setup of Test System Creation of Test Data

̈ ̈ ̈

Manual tests Automated tests Integration Validation Incident Management Performance tests Test status and progress reporting Test sign-off

̈

̈

̈

̈ ̈

̈ ̈ ̈ ̈

̈ ̈ ̈ ̈

Deployment of changes through transports from Test to Production system SAP Support packages, Legal Change Packages, Enhancement Packages

̈

̈

̈

̈

̈

Note: Test Project Preparation as first step including: test strategy review, definition of test objectives, test tools, test budget, timeline, roles & responsibilities
© SAP 2009

© SAP AG

E2E200

8-13

E2 E I ntegra t ion T e st ing of SAP Solut ions Opt ions for SAP Cust ome rs
Type of Change Test Scope Identification

New SAP Solution

Business Blueprint Test Planning System Setup Change Impact Analysis
Test Scope Identification Test Planning Manual Tests Automated Tests

Test Execution Manual and automated tests

Apply Changes to Production

SAP Solution Update

Option 1

UI based Tests
HP: QTP CPWR:TestPartner

SAP Solution Manager

Business Blueprint
SAP Solution Manager

SAP Solution Manager

SAP Solution Manager

Test Workbench SAP TDMS

Test W orkbench

SAP Solution Manager

eCATT

Backend Tests eCATT: Application Logic Tests

Business Process Change Analyzer*

Option 2
SAP Solution Manager

Adapter HP Quality Center SAP TDMS HP Quality Center

SAP TAO HP QTP

Business Blueprint
SAP Solution Manager

Business Process Change Analyzer*

* Availability with SAP Solution Manager 7.0 EhP1
© SAP 2009

̈

From the many tools available for testing SAP-centric business processes, two options have emerged. In option 1, almost all the test tools are provided by SAP Solution Manager, while option 2 relies on a combination of SAP Solution Manager, SAP Quality Center by HP, SAP TDMS, and SAP TAO. Both of these options support the entire testing process, from the Business Blueprint and change analyses to test requirements, planning and execution, problem handling, quality gate management, and transporting changes to the production system. In both options, SAP Solution Manager plays a pivotal role in bringing together technical and business aspects. Both options feature comprehensive test management functions and thereby offer optimum support for coordinating and executing tests. Companies should choose between the two options on the basis of their particular situation and implement the selected one with all the tools it contains to achieve the greatest levels of efficiency and transparency in their test management activities.

̈

̈

© SAP AG

E2E200

8-14

SAP Solut ion M a na ge r Ada pt e r for SAP Qua lit y Ce nte r by H P
SAP Solut ion M a na ge r Ada pt e r for SAP Qua lit y Ce nt e r by H P int e gra t e s a pplic a t ion life c yc le m a na ge m e nt c a pa bilit ie s of SAP Solut ion M a na ge r w it h t e st pla nning a nd t e st e x e c ut ion c a pa bilit ie s of SAP Qualit y Ce nt er by H P

Ada pt e r
SAP Solution Manager SAP Quality Center by HP

Outbound ̈ Business Blueprint ̈ Bus. Requirements Inbound Test Results ̈ Defects
̈

© SAP 2008

© SAP AG

E2E200

8-15

SAP T e st Ac c e le ra t ion a nd Opt im iza t ion (T AO)
SAP TAO Frontend SAP Quality Center by HP

4 Upload to Quality Center

1 2 3

User selects Business Processes Automatic inspection of SAP Transactions Automatic generation of Test Components 5 User composes Test Case 6 Test Case execution

Customer SAP Test Systems ERP ERP R/3 R/3 CRM CRM
Inspect

SAP Business Process

SAP TAO Agent

© SAP 2009

̈ ̈ ̈ ̈

There is an SAP TAO agent on the frontend that automatically inspects a SAP GUI-based user interface for test components (buttons, input fields, menus, etc.) The test components are stored in the SAP TAO frontend and can be uploaded into SAP Quality Center by HP. The test components can be put together to quick test professional test scripts by drag and drop. This eliminates the need to record the test scripts manually. The big advantage of SAP TAO, however, is the rescanning capability. This feature allows you to rescan all user interfaces following a system change and find the changed test components. The changed test components and the dependent test scripts can then be updated automatically.

© SAP AG

E2E200

8-16

SAP T e st Da t a M igra t ion Se rve r (T DM S)
Motivation
̈ ̈ ̈

Pain point: Test system setup with a copy of the entire SAP production system not suitable Goal 1: Fast creation of lean test system with production like environment, but reduced volume Goal 2: Transfer of specific test data, such as posted documents and master data

SAP TDMS

Available Scenarios
̈ ̈

Shell Creation – Repository and client-independent data only TDMS Classic: ̇ Master and configuration data only ̇ Master and configuration data plus time slice of transactional data

̈ ̈

̇ Master and configuration data plus time slice of transactional data for specific company code(s) Business Process Library – Predefined business objects, process data, or test cases Specific data by means of custom-specific transfer scenarios (TDMS Workbench)

© SAP 2009

With SAP TDMS you can:
̈ ̈ ̈ ̈ ̈ ̈ ̈

Reduce data volume in test systems Simulate production environment by using real business data Preserve consistent business processes within the target system Reduce post-processing work by keeping administrative data (objects) in the target system unchanged (interfaces, users, authorizations, etc.) Perform selective refresh of individual clients in target system (esp. in multi-client systems) Scramble sensitive data according to your needs TDMS also copies Customizing data. This means all transports that have already been imported into the target system but are missing in the source system must be re-imported.

© SAP AG

E2E200

8-17

T e st M a nage me nt Work ce nt e r: Role -Spec ific Ent ry Point for a ll T e st-Re la t e d Ac t ivit ie s

Test Coordinator

Quality Expert

Tester

VP of QA
Status Reporting

© SAP 2009

̈ ̈

This workcenter is the central access to all functions for preparing, creating, managing, and evaluating test plans. In addition, you can prepare projects and solutions for using the Business Process Change Analyzer in this workcenter, perform change influence analyses, and generate tailored test plans from the results.

© SAP AG

E2E200

8-18

T e st M a nage me nt : U nit Ove rvie w Dia gra m
Test Management Lesson 1: Test Methodology Lesson 2: SAP E2E Integration Testing Lesson 3: Business Process Change Analyzer Lesson 4: Test Workbench

© SAP 2009

© SAP AG

E2E200

8-19

Busine ss Proce ss Cha nge Ana lyze r – Wha t I s It?
SAP Solution Updates Occur Frequently
̈ ̈

SAP triggered: Support Packages, enhancement packages Customer triggered: Customizing changes, custom code development

Customer Pain Point
̈

Which business processes are affected by planned change?

Approach
SAP Solution Update

Change Impact Analysis
̈

Test Planning
̈

Test Execution
̈

Identification of business processes affected by change Risk-based Test Recommendation

Test Case review and creation of missing test cases Test Plan generation

Regression Tests
̈ ̈

Manual Tests Automated Tests

̈

̈

© SAP 2009

̈

When a change is done in an existing SAP solution, this raises the question of whether important applications or critical business processes are affected. No matter if SAP source code is adjusted due to SAP maintenance packages or customer enhancements, or if the configuration or interfaces have been changed – the question must always be addressed which areas of the solution are affected by the change. SAP Solution Manager 7.0 enterprise edition EhP1 (SP18) offers a new analysis function: The Business Process Change Analyzer (BPCA). The purpose of this function is to precisely analyze the SAP objects that are used when business processes are executed. In the event of an intentional change, the very detailed information delivered is compared with the Technical Bill of Material (T-BOM) to identify the affected business processes and areas. This allows the customer to make the intended change at the planned time or a later point if there is not enough time to run a satisfactory regression test on all affected areas.

̈

© SAP AG

E2E200

8-20

Busine ss Proc e ss Cha nge Analyzer Pre paration – Ana lysis – T est Re com m enda tion
Preparation
Order to Cash Sales Order Delivery Goods Issue Billing
Execution of mission-critical Trace Result: business processes by Business Technical Bill of Material (T-BOM) User ̈ Code: Function modules, …
̈ UI: Dynpro 1000, … ̈ Tables: Customizing, Master

Data

Change Impact Analysis
“Which critical Business Processes will be affected by planned changes?”

Planned Change
̈ SAP Support Packs ̈ SAP EhPs ̈ Custom Code ̈ Customizing changes

Business Process Change Analyzer
Order to Cash Sales Order å code change Delivery Goods Issue å UI change Billing Procure to Pay Create PO å customizing change

Risk-based Test Scope
“Can I get a recommendation for regression tests?”

Business Process Change Analyzer
̈ Identification of business processes impacted

by software changes
̈ Support decision making whether planned

change is to be executed
̈ Automatic test plan generation for SAP Test

Workbench
© SAP 2009

̈

To ensure as much accuracy as possible, the analysis is not performed statically on the source code but rather dynamically at run time to record all the SAP objects used in the busi-ness process variant. To this end, the customer executes the critical business processes in an appropriate system again. As the processes are being executed, the BPCA records all of the SAP objects (module pools, function modules, configuration and master data tables, interfaces, and so on) that are used and generates a technical bill of materials (TBOM) that is assigned to the business process using the Business Blueprint. If SAP support packages, SAP enhancement packages, custom developments, or configuration adjustments are to be implemented later on, the business processes affected can be identified with the BPCA. These analyses can be saved with a timestamp and contain very detailed information that can be used for subsequent test applications. It is advisable to assign all relevant test cases to the business processes using the Business Blueprint. It is then possible to automatically generate a test plan containing all affected processes on the basis of the BPCA – Test Workbench integration.

̈

̈

© SAP AG

E2E200

8-21

Busine ss Proce ss Cha nge Ana lyze r St e p 1 : Pre pa ra t ion
Business Blueprint Alternatives to provide Business Blueprint
1) Business Blueprint already available within SAP Solution Manager “project“ or “solution“ 2) Activiation of SAP Business Content: Business Process Repository (BPR) 3) Manual setup for mission-critical processes 4) Semi-automatic setup via SAP Solution Manager – Solution Documentation Assistant

Technical Bill of Material (T-BOM)
SAP ERP, …

1

2

Business User activity:
1) Execution of mission-critical business processes
̈

Background: SAP Solution Manager BPCA creates trace (T-BOM) of all used SAP objects

2) T-BOM auto assignment to Business Process
̈ ̈ ̈
© SAP 2009

Code: Module pools, function modules, … User interfaces: Dynpro,… Tables: Customizing, Master Data, …

̈

A TBOM (Technical Bill of Materials) contains all the objects involved in a transaction. The Business Process Change Analyzer uses TBOMs to determine whether a transaction is affected by a change or not. In order to be able to run the Business Process Change Analyzer usefully, you therefore have to create a TBOM for each transaction that you use in your scenarios, processes, and process steps.

© SAP AG

E2E200

8-22

Re cording of t he T e chnic a l Bill of M a t e ria l (T ra nsac t ion SOLAR01 )

© SAP 2009

̈ ̈

The TBOM is an attribute of a transaction in the Business Process Hierarchy (SOLAR01). The generation of dynamic TBOMs is not available in managed systems with kernel 620/640 but it is available in systems with kernel 46C and above 640. The generation of static TBOMs is available for all managed systems with ST-PI 2008_01. TBOM contents can be generated dynamically or statically. A TBOM can also contain a mixture of both content types. Dynamic: • In the dynamic generation of a TBOM, the corresponding transaction is called using the corresponding RFC user in the managed system. All objects involved in the transaction are entered in the background and copied to the TBOM once the transaction is complete. • The generation of the dynamic TBOM only covers operations in the managed system that are processed within a context there. Branches to other systems (for example, by RFC) are not recorded. This also applies to branched GUI procedures, which occur, for example, if a Web Dynpro is called within an SAP transaction. The operations within the Web Dynpro application are not recorded.

̈ ̈

̈

Static: • In the static generation of a TBOM, the transaction is not called. The system uses an environment analysis to determine the objects involved in the transaction. Dynamic calls or generated objects are not found and therefore do not enter the TBOM either.

© SAP AG

E2E200

8-23

Re sult from Busine ss Proce ss e xe cution: T e chnica l Bill of M a t e ria l (T -BOM )
PgID R3TR LIMU R3TR R3TR Obj PROG DYNP TABU TABU Obj Name SAPMV45A SAPMV45A TVAK T685 TABC TABC G (Cust) C (Cust) Cl Type Cl.Value Soft.Component SAP_APPL SAP_APPL SAP_APPL SAP_APPL Comment Modulpool of T-Code VA01(*) UIs / Dynpros for Modulpool Customizing: Document Type Customizing: Conditions: Access Sequence

(*) Modulpool for Transaction VA01: SAPMV45A

© SAP 2009

̈

A TBOM contains a list of all objects that are involved in a certain transaction. These objects are, for example, elements of the user interface, module pools, function modules or tables.

© SAP AG

E2E200

8-24

Syste m De m o

Create Technical Bill of Material

© SAP 2009

© SAP AG

E2E200

8-25

Busine ss Proce ss Cha nge Ana lyze r St e p 2 : Ana lysis

“Which critical Business Processes will be affected by the planned changes?”

Planned software changes
̈ SAP Support Packages ̈ SAP Enhancement Packages ̈ SAP Legal Change Packages ̈ Custom Code ̈ Customizing changes

?

Business Process Change Analyzer
Business Processes with T-BOM
Order to Cash Sales Order å code change Delivery Goods Issue å UI change Billing Procure to Pay Create PO å customizing change

Identification of business processes affected by software changes

Customer Benefit: Increased insight into effects of software change events
© SAP 2009

̈

Changes to the system, for example, Support Packages, customer developments or add-on installations can affect different business processes. The Business Process Change Analyzer compares the objects included in a transport to the objects contained in the TBOMs of the target system. Since every TBOM is clearly assigned to a certain transaction in a certain scenario, business process, or process step, you can determine precisely which parts of a Business Process Hierarchy are affected by the change.

© SAP AG

E2E200

8-26

Busine ss Proce ss Cha nge Ana lyze r – Ana lysis

Compare objects of transport CTEK000559 against TBOMs in Solution Manager Project

© SAP 2009

̈

You can use this analysis to check whether a process structure is affected by specific changes. You can precisely specify both the relevant parts of the process structure and the relevant changes.

© SAP AG

E2E200

8-27

Busine ss Proce ss Cha nge Ana lyze r Ana lysis Re sult

Result of the analysis run

Project affected by change

BPCA identified Transaction “Sales Order“ as affected

© SAP 2009

̈

The result of the analysis is a list of the affected nodes in the process structure.

© SAP AG

E2E200

8-28

Busine ss Proce ss Cha nge Ana lyze r De t a ile d Ana lysis Re sult

Result Interpretation
Customer plans to transport a customizing change from Dev systemå Test system å PRD system BPCA identifies business process “Create Sales Order“ as impacted by this change event

Details: The Transport Request includes customizing changes to tables T685 (Access sequence for conditions) and TVAK which controls the document type of T-Code VA01

© SAP 2009

̈

The list shows the technical objects which both in the object list of the transport request and also on the Technical Bill of Material of a transaction which was analyzed.

© SAP AG

E2E200

8-29

Syste m De m o

Change Impact Analysis

© SAP 2009

© SAP AG

E2E200

8-30

T e st M a nage me nt : U nit Ove rvie w Dia gra m

Test Management Lesson 1: Test Methodology Lesson 2: SAP E2E Integration Testing Lesson 3: Business Process Change Analyzer Lesson 4: Test Workbench

© SAP 2009

© SAP AG

E2E200

8-31

Busine ss Proce ss Cha nge Ana lyze r – St e p 3 : T e st Re com m enda t ion

“Can I get a recommendation for regression tests?”

Risk-based Test Scope Recommendation
BPCA Analysis: affected Business Processes Test Workbench Semi-automatic Test Plan generation via BPCA

Business Blueprint with assigned test cases

Customer Benefit: Semi-automatic Regression Test Plan generation for affected processes
© SAP 2009

̈

You can use the test cases contained in the Business Process Hierarchy to create test plans that are tailored to the relevant changes. You can check scheduled changes as well as changes that have already been made.

© SAP AG

E2E200

8-32

Risk -ba sed T e st Rec omm enda t ion – Aut oma t ic a lly Cre a te T e st Pla n

Direct link from BPCA result analysis …

… to semi-automatic generation of test plan for SAP Solution Manager Test Workbench

© SAP 2009

̈ ̈

From the result of the Business Process Change Analyzer run you can automatically create a test plan. This test plan will contain all test cases of the affected business process steps.

© SAP AG

E2E200

8-33

T e st Work be nc h – Ove rvie w

Test analysis

Test package

Business Process with assigned test cases

Test plan

Test package Test package Test package Test package Test package

Testers

Collection of test cases
Project/business related e.g. Implementation CRM 4.0 Interaction center

Selection of test cases
Aim and time related e.g. for applying a specific Support Package

Assignment of test packages to testers
operation queue of a single tester

Test Execution

© SAP 2009

̈

Test catalog, Project or Solution Directory structure: • Repository for the collection of test cases

̈

Test plans: • View on one test catalog • Contains all test cases for one test cycle

̈

Test package: • Person and time-oriented view on a test plan • Contains all test cases one tester has to work with

̈

Test case: • Business process step / process chain • Manual test case description or eCATT script

© SAP AG

E2E200

8-34

T e st Pla n M a nagem ent
̇ Intuitive navigation to access Test Plan and Test Packages and related features ̇ Standard Queries All Test Plans / My Test Plans to list all or only own Test Plans ̇ Users can create their own queries based on various selection criteria

© SAP 2009

* SAP Solution Manager 7.0 EhP1 available with SAP Enterprise Support

© SAP AG

E2E200

8-35

De finit ion of T e st Se quence s

1 . Ac c e ss Te st Se que nc e s via Te st M a na ge m ent Work Ce nte r

2 . H e re you ca n a ssign e a ch Te st Ca se to individua l Te ste rs a nd de fine orde r of e xe c ution

Test Cases selected for a Test Package

̈ ̈

Assigned Tester: System User or Business Partner

Sequence and order of Test cases within Sequence

© SAP 2009

̈

A workflow can be activated that informs tester 2 when test case 1 was executed.

© SAP AG

E2E200

8-36

Syste m De m o

Test Workbench

© SAP 2009

© SAP AG

E2E200

8-37

Ex e rc ise

Test Management

© SAP 2009

© SAP AG

E2E200

8-38

T e st M a nage me nt : U nit Sum m a ry

You should now be able to:
̈ ̈ ̈ ̈

Explain different types of tests and test strategies Understand SAP’s methodology for testing and how it is implemented in SAP Solution Manager Determine the change impact with the Business Process Change Analyzer Use the Test Management Workcenter

© SAP 2009

© SAP AG

E2E200

8-39

© SAP AG

E2E200

8-40

Exercises
Unit: Lesson: Test Management Business Process Change Analyzer

At the conclusion of this exercise, you will be able to: • Record a technical bill of material for transaction CAT2 • Perform an impact analysis with the Business Process Change Analyzer • Create a test plan out of the results of the Business Process Change Analyzer

TT4 is the SAP Solution Manger system that contains all information about the managed systems. TT5 is a satellite system that is managed by TT4.

8-1

Record a technical bill of material (TBOM) for transaction CAT2. 8-1-1 Log on to SAP Solution Manager with your user, E2ECC-## (change ## to your group number). Navigate to the Test Management work center and choose Test Preparation. In the Test Preparation view, select the Solution Manager project (not the IMG project) that you created in the exercise for Solution Documentation. Navigate to the Business Blueprint. Which transaction is it? Answer: _____________________________________________________ 8-1-3 In your project, select the business process step Record working times in backend, which you added in the exercise for Solution Documentation, and select the attributes of the related transaction. In the attributes of transaction CAT2, chose the TBOM tab. Start to create a technical bill of material for this transaction. Choose Create Option Dynamic. This means that a trace is executed to record all objects that are used in this transaction. To which system, client, and transaction are you logged on? Answer: _____________________________________________________

8-1-2

8-1-4

© SAP AG

E2E200

8-41

8-1-5

Enter some working time in transaction CAT2 and finalize the creation of the TBOM. Make the following entries in transaction CAT2.

Do not change the default values for Data Entry Profile and Personnel Number.

Enter some working time entries and save it. After that, a TBOM with name and date will be created. 8-1-6 8-2 Display the object list of the newly created TBOM.

Perform an impact analysis run with the Business Process Change Analyzer. 8-2-1 Enter all relevant data in the Business Process Change Analyzer. Choose the project you created in the exercise for Solution Documentation and the transport request you created in the exercise for Quality Gate Management. Start the change/impact analysis and list the results. Which objects are affected? List all objects that are in the transport request and also in the TBOM.
E2E200 8-42

8-2-2 8-2-3

© SAP AG

8-3

Create a test plan based on the results of the Business Process Change Analyzer. 8-3-1 Create a test plan. In the next screen, enter following values.

8-3-2

Generate the test plan with the preselected test cases. Which test cases are selected? Answer: _____________________________________________________ In the Transport dialog box, save the test plan as local object.

© SAP AG

E2E200

8-43

© SAP AG

E2E200

8-44

Solutions
Unit: Lesson: Test Management Business Process Change Analyzer

8-1

Record a technical bill of material (TBOM) for transaction CAT2. 8-1-1 Log on to SAP Solution Manager with your user, E2ECC-## (change ## to your group number). Navigate to the Test Management work center and choose Test Preparation. In the User menu, select WDY_APPLICATION -Work Center.

Then select the Test Management work center and the Test Preparation tab.

8-1-2

In the Test Preparation view, select the Solution Manager project (not the IMG project) that you created in the exercise for Solution Documentation. Navigate to the Business Blueprint. Which transaction is it?

© SAP AG

E2E200

8-45

You can navigate to the Business Blueprint by choosing Goto å Business Blueprint. You should then reach transaction SOLAR01. 8-1-3 In your project, select the business process step Record working times in backend, which you added in the exercise for Solution Documentation, and select the attributes of the related transaction.

8-1-4

In the attributes of transaction CAT2, chose the TBOM tab. Start to create a technical bill of material for this transaction. Choose Create Option Dynamic. This means that a trace is executed to record all objects that are used in this transaction. To which system, client, and transaction are you logged on?

You are logged on in system TT5, client 801, and transaction CAT2.

© SAP AG

E2E200

8-46

8-1-5

Enter some working time in transaction CAT2 and finalize the creation of the TBOM. Make the following entries in transaction CAT2 .

Do not change the default values for Data Entry Profile and Personnel Number.

Enter some working time entries and save it. After that a TBOM with name and date will be created.

© SAP AG

E2E200

8-47

8-1-6

Display the object list of the new created TBOM.

In the following screen, you will see all objects that are used in transaction CAT2.

© SAP AG

E2E200

8-48

8-2

Perform an impact analysis run with the Business Process Change Analyzer. 8-2-1 Navigate to the Test Management work center and select the BP Change Analyzer menu. Enter all relevant data in the Business Process Change Analyzer, and choose the project you created in the exercise for Solution Documentation and the transport request you created in the exercise for Quality Gate Management. In the following screen you will find the necessary entries.

8-2-2

Start the change/impact analysis and list the results. Select the Run field and, in the next screen, choose Start Immediately.

After a few seconds, choose Refresh.

If the run was successful, the status is set to Finished.

© SAP AG

E2E200

8-49

Select your project and choose Display Details.

8-2-3

Which objects are affected? List all objects that are in the transport request and also in the TBOM. Choose Display Intersection to display the list of objects.

You will get following detailed view.

© SAP AG

E2E200

8-50

8-3

Create a test plan based on the results of the Business Process Change Analyzer. 8-3-1 Create a test plan. Choose Create Test Plan.

In the next screen, enter following values.

8-3-2 Generate the test plan with the preselected test cases. Which test cases are affected? After confirming the Create Test Plan screen, you will see the Test Plan: Project: E2ECC_<XX> - Create screen. Drill down in the test plan hierarchy until you see the test cases. The following test cases are preselected: - The automatic test case ZETIMERECORDING - The manual test case ZDTIMERECORDING Select all test cases and choose Generate Test Plan.

In the Transport dialog box, save the test plan as local object. If successful, you will receive a success message.
© SAP AG E2E200 8-51

© SAP AG

E2E200

8-52

Change Diagnost ic s

Unit 1 Introduction to E2E Change Control Management Unit 2 Transport Strategies Unit 3 Enhanced Change and Transport System Unit 4 Solution Documentation Unit 5 Quality Gate Management Unit 6 Change Request Management Unit 7 Maintenance Management Unit 8 Test Management Unit 9 Change Diagnostics

© SAP 2009

© SAP AG

E2E200

9-1

Change Diagnost ic s: U nit Obje c t ive s

After completing this unit, you will be able to:
̈ ̈ ̈ ̈ ̈ ̈

Understand the concepts and architecture of E2E Change Diagnostics Know which configuration items are collected Find current configuration information with the Change Reporting tool Find recent changes in the solution landscape with the E2E Change Analysis tool Compare multiple systems with the Configuration Validation tool Configure and run non-standard configuration validation reports

© SAP 2009

© SAP AG

E2E200

9-2

Change Diagnost ic s: Mot iva t ion Why is Cha nge Diagnost ic s I m port a nt ?
Controlling the changes during the entire application lifecycle becomes crucial in End-to-End Solution Operations.

End-to-End Change Control Management
Build/Deploy
Bring changes from system A to system B

Test
Impact Analysis and Test

Run
Reporting and History of changes is important

Control changes for all technology platforms Control the quality of implementation projects Document the full change request management process Keep solution up-to-date
© SAP 2009

Estimate the impact of a planned change Perform automated quality checks Perform tests with lowest cost and risk

Provide information for Root Cause Analysis Collect metrics to evaluate and improve IT processes Meet regulatory requirements

̈

Why Change Diagnostics? • Understand the big picture before starting a deeper root cause analysis - Check system landscape: The satellite systems, their main functions and how they connect with each other - Check software components and their versions • Symptoms: - The system behaves differently after a certain date or some changes - One landscape works differently from the other one. For example, QAS is working fine, but PRD has issues.

© SAP AG

E2E200

9-3

T ypic a l Que stions

Which database parameters were changed by the 24/7 support team last night?

How many transports did we import last month?

How many urgent corrections did we import last month? What was last month content of the j2ee/cluster/ instance.properties file?

How many objects did we change last month?

Is there one place where all changes in the system are listed?

What are the configuration differences between server0 and server1?

How many stabilization transports did we have after the last GoLive?

© SAP 2009

̈

End-to-End Change Analysis and Reporting is an important part of End-to-End Change Control Management. If an unknown problem comes up, End-to-End Change Analysis answers the question “What was changed in the system?”

© SAP AG

E2E200

9-4

E2 E Change Diagnost ic s: Be ne fit s

Change Diagnostics supports customers in identifying, controlling, maintaining, and verifying the versions of configurations (such as OS/DB, SAP NetWeaver, Application, Customer Coding)

Benefits of E2E Change Diagnostics
> Central > BI

entry point for analyzing changes in a solution hints for root cause analysis with data and trends

methods to drill down from overviews to detailed lists of changes

> Providing > Providing > Enabling

accurate information on configuration parameters and their history (e.g. database parameters, ABAP parameters, JAVA parameters) the organization to standardize the solution configuration security by controlling the versions of configurations in use

> Improving

© SAP 2009

© SAP AG

E2E200

9-5

Change Diagnost ic s: U nit Ove rvie w Dia gra m
Change Diagnostics Lesson 1: Configuration Items Lesson 2: Data Collection Process Lesson 3: Change Reporting Lesson 4: E2E Change Analysis Lesson 5: Configuration Validation

© SAP 2009

© SAP AG

E2E200

9-6

Config St ore Definit ions Ove rvie w
Software Stores Config Stores

̈ Support Package Stack ̈ Software Component Versions

̈ SAP Product-specific settings ̈ PI/XI-specific configuration ̈ BI-specific configuration ̈ BIA-specific configuration

Application

̈ Implemented SAP Notes ̈ Imported ABAP Transports

̈ Web AS ABAP kernel release

̈ ABAP instance parameters ̈ Java VM parameters for J2EE

Basis

̈ Java VM version ̈ Web AS Java Release

̈ Database Release

̈ Database parameters

Database

̈ Operation System Release

̈ Operating system environment settings

Operating System

̈ Standard Users

Security
© SAP 2009

̈ Gateway Secinfo ̈ Gateway Reginfo

̈

The configuration items of existing systems are stored regularly in corresponding ConfigStores. There are different types of ConfigStores depending on the type of data stored in it. The most important types are xml, txt, ini, properties (two-column based container: parameter, value), table (more than two column based container: key1, key2, value1, value2 …) and event (as table but event-based). See also Note 1230404 “E2E CA Store Content List”

̈

© SAP AG

E2E200

9-7

Config St ore Definit ions De t a ils

http://<hostname>:8000/sap/bc/webdynpro/sap/e2e_ca_store_list

More than 2000 Config Store Definitions Type of Data Source Config Store Store Group Store Hierarchy Store Type Store Category

© SAP 2009

̈

To get a complete list of all the defined ConfigStores, the application “e2e_ca_store_list“ can be used. To start the application, use the URL: http://<server>:<port>/sap/bc/webdynpro/sap/e2e_ca_store_list Stores are defined in the Change Reporting Template Management: WebDynpro appliation diagtpl_upload_app Store Name: Name of the Config Store. The name can also contain wildcards. Then we talk about Config Store Definitions. Store Group: Superset of Config Stores Name: Indicates to which entity in the product hierarchy the config store belongs Store Type: Property, Table, Event, XML, Text Store Category: Software Store or Config Store

̈ ̈ ̈ ̈ ̈ ̈

© SAP AG

E2E200

9-8

Config St ore Definit ions Ex a mple s
ABAP Software Store Name
ABAP_COMP_SPLEVEL ABAP_COMP_RELEASE ABAP_PACKAGES ABAP_TRANSPORTS ABAP_NOTES ABAP_SWITCH_FRAMEWORK

J2EE Dispatcher Configuration Database Store Type
TABLE PROPERTY PROPERTY EVENT TABLE TABLE

Store Name element-info.properties *.properties hosts.txt *.xml

Store Type PROPERTY PROPERTY TEXT XML

© SAP 2009

̈ ̈

* File name patterns are used for the file system extraction to extract several files with one store definition. Store names with wildcards are store definitions that define several config stores.

© SAP AG

E2E200

9-9

St ore T ype s Diffe rent St ruc t ure
Store Type XML Layout

Text

Table / Ini / Property Event

© SAP 2009

̈

The configuration items of existing systems are stored regularly in corresponding ConfigStores. There are different types of ConfigStores depending on the type of data stored in it. The most important types are xml, txt, ini, properties (two column based container: parameter, value), table (more than two column based container: key1, key2, value1, value2 …) and event (as table but event-based). Store content is displayed differently according to its type.

̈

© SAP AG

E2E200

9-10

Da t a Colle c t ion M e t hod Snapshot or T im e st a mp
Store Type Store Type
XML, TEXT, TABLE, INI XML, TEXT, TABLE, INI PROPERTY, such as PROPERTY, such as ̈ OS, DB, ABAP parameters ̈ OS, DB, ABAP parameters ̈ Software version Information ̈ Software version Information

Data Collection Method Data Collection Method
Snapshot Method Snapshot Method ̈ Daily snapshot is transferred ̈ Daily snapshot is transferred to E2E Change Analysis to E2E Change Analysis ̈ Changed values are calculated ̈ Changed values are calculated and saved and saved Timestamp Method Timestamp Method ̈ Number of events since last ̈ Number of events since last data collection run is data collection run is transferred to E2E Change transferred to E2E Change Analysis Analysis

Detail Viewer Detail Viewer
Details available Details available ̈ Number of changes is ̈ Number of changes is displayed in the overview displayed in the overview ̈ Full configuration set can ̈ Full configuration set can be displayed for each day be displayed for each day Details available Details available ̈ Number of events is ̈ Number of events is displayed in the overview displayed in the overview ̈ Detail information can be ̈ Detail information can be accessed by drilldown accessed by drilldown

EVENT EVENT ̈ ABAP Transports ̈ ABAP Transports ̈ Non-ABAP Transports ̈ Non-ABAP Transports

© SAP 2009

̈

In E2E Change Analysis, we differentiate between two types of data: • Technical configuration, such as OS, DB, and ABAP parameters. These parameters are not recorded by the Change and Transport System. A full snapshot of each configuration set is extracted on each day. • Changes that are recorded in transport requests or Support Packages and patches, are already documented in the managed systems. For these types of changes, only the number of events since the last data collection run is transferred to E2E Change Analysis. Details are located in the managed systems.

© SAP AG

E2E200

9-11

Change Diagnost ic s: U nit Ove rvie w Dia gra m
Change Diagnostics Lesson 1: Configuration Items Lesson 2: Data Collection Process Lesson 3: Change Reporting Lesson 4: E2E Change Analysis Lesson 5: Configuration Validation

© SAP 2009

© SAP AG

E2E200

9-12

Change Diagnost ic s Arc hit e c ture
E2E Change Analysis
InfoCube: 0SMD_CA02 E2E Change Analysis BI Reporting

Extractor Franework (EFWK) Once a day

Change Reporting

Drilldown navigation

Configuration and Change DB
JAVA based Installations Diagnostics Agent EWK Once a day

ABAP based Installations Solution Tool Plugins

© SAP 2009

̈

The CCDB config stores are daily updated by extractors scheduled within the EFWK. The data are collected in Java-based systems using Diagnostics Agents and in ABAP-based systems by means of the Solution Tool Plugin Extractors. InfoCube 0SMD_CA02 (E2E Change Analysis II) is updated daily with changes provided by the CCDB. In the E2E Change Analysis BI reporting tool it is possible to navigate from the aggregated level of data (number of changes per day) to the detailed configuration data using the Change Reporting Viewer. The Change Reporting Viewer can also be accessed directly from the RCA workcenter Analysis. System

̈

̈

© SAP AG

E2E200

9-13

Da t a Load Proce ss Ove rvie w
Managed Systems Solution Manager (ABAP) Business Intelligence Solution Manager Diagnostics

Cube

E2E WA Web Templates BEx Queries

Extractor
Cube

E2E EA

Extractor

Extractor Framework

Cube

E2E CA

Agent
Virtual Cube

Agent

Configuration Validation

Solution Manager (CCDB) Manage & Control Data Collection Store, Aggregate & Render Data

Change Reporting

Data Flow

Collect Data

Display Data in E2E Applications

© SAP 2009

̈ ̈ ̈

The configuration data is collected from different sources of differing system types. In the above figure these are displayed as “Managed Systems“ on the left side. The data is collected on a Product Instance Perspective, which means that an access is provided to data specific to the component in question, for example, CRM or XI, ABAP or Java-based systems. The technical infrastructure to collect the data into the Solution Manager Diagnostics and into the BI is the Extractor Framework (EFWK). The Extractor Framework guarantees that the strong emphasis on the Product Instance Perspective is available for the E2E applications displaying the data by enriching the data with additional information. The extracted configuration data is stored in the Configuration and Change Database (CCDB). The Configuration Validation and the Change Reporting use the data of the CCDB. However, for the E2E Change Analysis the CCDB data is aggregated and saved in an InfoProvider of Business Intelligence (BI) which allows using BI reporting capabilities by E2E Diagnostics applications. The Configuration Validation reads the CCDB data by means of a Virtual InfoProvider to provide BI reporting capabilities. The validated data is not stored in BI. The further information on E2E Diagnostics can be found at http://service.sap.com/diagnostics.

̈

̈

© SAP AG

E2E200

9-14

Ex t ra c t or Fra me w ork Adm inistra t ion U se r I nt e rfac e

Extractor Status
© SAP 2009

Last successful Extractor run

̈ ̈ ̈

The Extractor Framework can be monitored in the workcenter Root Cause Analysis. Then click on Extractor FWK Administration. You see the status of all Extractors for a given system. In the Log view you see the time of the last extractor run and if it was successful.

© SAP AG

E2E200

9-15

Change Diagnost ic s Se t up Pre re quisit e s
̈

SAP Solution Manager with SPS18 is in place (to have the latest features)
̈ ̈

BI Content 704, Level 1 Solution Manager EHP 1 Managed Systems connected with E2E Diagnostics Diagnostics Agents and Solution Tool Plug-ins installed Extractor Framework configured

̈

E2E Diagnostics is configured
̈ ̈ ̈ ̈

D Sta ia n gn d os ard ti c E Se 2E tu p

Configuration Data are available in the Configuration and Change Database ( CCDB )

̈

Role for Change Management Workcenter is assigned to the end-user profile

Detailed Info on Installation
̈

http://service.sap.com/diagnostics
̈ ̈ ̈ ̈

Root Cause Analysis Installation and Upgrade Guide SAP Solution Manager Starter Pack Frequently Asked Questions Media Library

© SAP 2009

© SAP AG

E2E200

9-16

Change Diagnost ic s: U nit Ove rvie w Dia gra m
Change Diagnostics Lesson 1: Configuration Items Lesson 2: Data Collection Process Lesson 3: Change Reporting Lesson 4: E2E Change Analysis Lesson 5: Configuration Validation

© SAP 2009

© SAP AG

E2E200

9-17

H ow t o Ac c e ss Change Report ing 1 /2

1. Access the Root Cause Analysis Workcenter

2. Choose System Analysis

© SAP 2009

© SAP AG

E2E200

9-18

H ow t o Ac c e ss Change Report ing 2 /2

3. Select the Query which includes your system (or define a new query)

4. Select the system for your analysis

5. Click the Change Reporting button

© SAP 2009

© SAP AG

E2E200

9-19

Change Report ing: Applica t ion Ove rvie w
Change Reporting

Data Viewer

Comparison Tool

© SAP 2009

̈ ̈

The Change Reporting application has two main functions: a Data Viewer and a Comparison Tool. They are located in two different tab strips to easily switch from one to another. First let us focus on the Data Viewer

© SAP AG

E2E200

9-20

Change Report ing: Da t a V ie w e r – La yout
Filtering and Searching Timestamp selection Store List (of selected StoreGroup)

Navigation tree (till StoreGroup level)
© SAP 2009

Store Content (of selected Store )

̈ ̈ ̈ ̈

The Data Viewer provides a snapshot of the Store content at a given timestamp of the selected Technical System. It also offers capabilities for Searching and Filtering Store content. The left panel is a Navigation panel with Timestamp selection, a tree to navigate through the satellite landscape, and the Filtering/Searching tool. The right panel provides the detail views (Store list and Store content). The timestamp selection defines at which date you want to view your data. It will then display in the Navigation tree and in the Store list only entities that have been created before that date.

© SAP AG

E2E200

9-21

Change Report ing: Da t a V ie w e r – N a viga t ion T re e
The navigation tree displays the Landscape and Store content at the previously selected timestamp and enables the user to select the StoreGroup to be inspected.
Collapse all Landscape entities

Store entities

Nested Store entities information
Group Source :

Store Hierarchy :
Technical System Main Instance Host Installed Technical System Instance Server/Dispatcher Node

ABAP File System SapOsCol Windows Registry Engine Database JMX SLD CTC

© SAP 2009

̈ ̈ ̈ ̈ ̈ ̈ ̈ ̈

The navigation tree displays the landscape and store content "at" the previously selected timestamp of the satellite system. The user can now select the StoreGroup to inspect. StoreGroups have the yellow folder icon, with its source underneath (ABAP, OS, FileSystem…). They can be attached to any landscape level. The other levels are related to the satellite system landscape entities. The upper one is always the technical system. Moving the mouse over the icons will display tooltips showing more information on the entity (rntity level, PPMS ID, instance type, instance source…). JMX… Java Management Extensions SLD… System Landscape Directory CTC… Client Transport Control

© SAP AG

E2E200

9-22

Change Report ing: Da t a V ie w e r – St ore List
The contained Stores of the selected StoreGroup (at the given timestamp) are displayed. Store Alias:Subalias
Store Path + Name (usefull for Filtering)

Store type legend :
XML Text Table (n keys and m values) Ini (table with 2 keys and 1 value) Property (table with 1 key and 1 value) Event (timestamp, n keys and m values)
© SAP 2009

Store state legend :
XML format Text files ABAP tables .ini files .property files ABAP Transport Requests Complete with most recent data Complete with outdated data Errorneous : - Corrupted
Outdated Erroneous - Max length reached - Not authorized - Extractor not found - Extractor error - Extractor not registered

̈ ̈

Store state log reports only changes of the store state, and is strictly independent from changes in the store content. "Outdated" state indicates that the store has not been "seen" since more than two days, and thus the latest known state is displayed "grayed". This could happen if the underlying extractor is not running or failing, or if the store has been removed from the templates or from the file system.

© SAP AG

E2E200

9-23

Change Report ing: Da t a V ie w e r – St ore List
2 functionalities are available in the StoreList :

Store state history

© SAP 2009

̈

A click on the History icon in the Store List displays detailed information about store state changes.

© SAP AG

E2E200

9-24

Change Report ing: Da t a V ie w e r – St ore List
2 functionalities are available in the StoreList :

Store details

© SAP 2009

̈

The More Details button will display a table popin with some more technical information as well as a jump-in link to the RCA FileSystemBrowser application for Stores belonging to StoreGroups of type "FileSystem".

© SAP AG

E2E200

9-25

Change Report ing: Da t a V ie w e r – St ore Cont ent
You can display the element history (if any) by clicking the icon. As “History“everything is considered that is not part of the Initial data upload, i.e. : modification add deletion
Displays only elements having Historical values vs
deactivated for XML stores

Set line selection to the next element that has historical data

Historical values

© SAP 2009

̈

No History icon means the element has been created at store creation.

© SAP AG

E2E200

9-26

Change Report ing: Da t a V ie w e r – St ore Cont ent
Deleted elements are by default not displayed in the snapshot view of the store content. It is however possible to display them:

Set line selection to the next deleted element

© SAP 2009

̈

Red background indicates that these elements have been deleted.

© SAP AG

E2E200

9-27

Change Report ing: Da t a V ie w e r – Filt e ring & Se a rc hing
Search & Filter trays are by default collapsed and can be expanded at any time.

A green light indicates if filter or search criteria have been applied.

Independent “Reset“ and “Apply“ for both features. Any search criteria is then applied relatively to the eventual filters already applied.

© SAP 2009

̈

The important feature is the independent "Reset" and "Apply" for both searching and filtering. In other words, you can first apply filter criteria, and the eventual search will be performed against the already filtered data. Resetting the filters will automatically deactivate the search. However, resetting the search will keep the filters active.

̈

© SAP AG

E2E200

9-28

Change Report ing: Da t a V ie w e r – Se a rc hing

Store(s) containing the found element(s)

Set line selection to the next found element

The lens and bold-characters indicate the StoreGroup(s) where the element(s) has been found
© SAP 2009

Found element(s)

̈ ̈ ̈

The usage of “*” as wildcard is possible. You can use filtering and searching in conjunction. A green background indicates the found elements.

© SAP AG

E2E200

9-29

Syste m De m o + Ex e rc ise

Change Reporting

© SAP 2009

© SAP AG

E2E200

9-30

Change Report ing: Applica t ion Ove rvie w
Change Reporting

Data Viewer

Comparison Tool

© SAP 2009

̈

It is often useful to know what has changed in a system between two timestamps, or what differs between two given systems from a configuration point of view. The embedded comparison tool of Change Reporting will enable the user to answer those questions.

© SAP AG

E2E200

9-31

Compa rison T ool La yout
<Reference> Selection <Custom> Selection

Compare options

Compare results & filters
© SAP 2009

̈ ̈ ̈ ̈ ̈

The upper panels are for system selection and compare options. The lowest part of the application displays the results of the comparison. When triggering a comparison, we need a reference system. It is always the system selected at application startup and is not selectable. We can only choose the timestamp of the reference system. The timestamp selection dropdown aggregates hourly the number of changes. Indeed, it displays the number of changes ( = number of elements ADDED + DELETED + CHANGED) in the time range. It may happen that the number of changes is 0. This is the case when an empty store is uploaded in the CCDB. The custom selection is filtering all existing systems to display only those having the same type as the reference. In this case, only ABAP systems can be selected as we choose the ABAP stack of B70 as reference satellite. Timestamp selection is also available and has the same features as in the reference selection.

̈

© SAP AG

E2E200

9-32

Compa rison T ool Landsc ape Se lec t ion
Landscape selection has an automatic helper mechanism from left to right to find the corresponding entity to compare. Manual selection in the custom tree is still possible in case the relevant entity is not found or on user needs.

The “Compare“ button is enabled/disabled according to the selected entities using the following rule : Only entities of the same type can be compared, otherwise a warning is displayed :
Please select 2 identical types of elements to compare

© SAP 2009

̈

Once the reference and custom systems have been selected, both navigation trees are automatically updated to also reflect the selected timestamps. The user can now select entities he or she would like to compare. Once the user has selected two "comparable" entities (that is entities having the same type), the Compare button is enabled.

̈

© SAP AG

E2E200

9-33

Compa rison T ool Compa re Opt ions

Comparison type: “Fast“ vs. “Deep“
The compare algorithm stops drilling down when it detects identical entities and does not store them in the compare result. With the “Fast” flavor: å Only changes can be displayed å Significantly faster when comparing XML The compare algorithm compares all entities and store them in the compare result.
© SAP 2009

Multi-compare checkbox: When activated, the Custom tree is “multi-selection enabled“

Multi-selection is enabled as follows: - for ABAP System: Multi Instances - for JAVA System: Multi-Server Nodes

̈ ̈

The "Fast vs. Deep" comparison type option defines the algorithm that will be applied. When "Fast" is selected, the algorithm stops drilling down when it detects identical entities, and does not store those identical entities in the compare results. It is then called "Fast" as it is skipping any identical entities. It is particularly the case for deep xml stores. When "Deep" is selected, the compare algorithm compares all entities and stores them in the compare result (even if they are equal). Multi-Compare • By default, it is a one-to-one comparison between the selected reference and the custom entities. It is, however, possible for some elements type to compare one reference entity to multiple custom entities. • If you check the Enable multi-compare checkbox, the Custom navigation tree will be updated and will include a multi-selection capability.

̈ ̈

© SAP AG

E2E200

9-34

Compa rison T ool Compa re Re sult s Sum m a ry

Click to see Result details

“Reference“ selection entity “Custom“ selection entity(ies) with the Compare Status :
Compare Algorithm did not detect changes Changes have been detected

© SAP 2009

̈ ̈

Compare results are dispatched in two sections: a result summary and a result details section. Here, you see the result summary. The first line is always the reference entity that has been selected.

© SAP AG

E2E200

9-35

Compa rison T ool De t a ile d Compa re Re sult s
Root compared entities

Each level has a Compare Status
Identical Not in “reference“ Not in “custom“ Modified Modified in children Compare not allowed / not relevant
© SAP 2009

Possibility to drill-down to the store content and see the changes (Reference value / Custom value)

̈

For non-table stores (Text and XML), you have a direct view of the compared values and differences. For table stores, the details are displayed in a popin when pressing the icon in the Details column.

© SAP AG

E2E200

9-36

Compa rison T ool Compa re Re sult s Filt e rs

“Show only Identicals

© SAP 2009

̈

Depending on the selected comparison type ("Fast" or "Deep"), the filter dropdown is enabled or not. Indeed, the "Fast“ algorithm does not store elements flagged as "equal", so the Filter dropdown is disabled and limited to "Show only differences" By setting the comparison type to “Deep” you are allowed to choose different filter options. With filter setting “Show ALL” also the equal elements are displayed. With filter setting “Show only Identicals” just the identical elements are displayed.

̈ ̈

© SAP AG

E2E200

9-37

Syste m De m o

Comparison Tool

© SAP 2009

© SAP AG

E2E200

9-38

Change Diagnost ic s: U nit Ove rvie w Dia gra m

Change Diagnostics Lesson 1: Configuration Items Lesson 2: Data Collection Process Lesson 3: Change Reporting Lesson 4: E2E Change Analysis Lesson 5: Configuration Validation

© SAP 2009

© SAP AG

E2E200

9-39

H ow t o Ac c e ss E2 E Change Ana lysis 1 /2

1. Access the Root Cause Analysis Workcenter

2. Choose End-To-End-Analysis

© SAP 2009

© SAP AG

E2E200

9-40

H ow t o a c ce ss E2 E Change Ana lysis 2 /2

3. Select the Query which includes your system (or define a new query)

4. Select the system for your analysis

5. Click ‘Change Analysis’ Button

© SAP 2009

̈

The End-to-End Analysis starts with the selection of one or several systems that should be analyzed.

© SAP AG

E2E200

9-41

E2 E Change Ana lysis Ove rvie w

© SAP 2009

̈

The Change Analysis opens an Overview Tab Strip, and an additional tab strip for each product instance of the selected systems and for the hosts will be created. The tab strips description is composed of the system ID and the product instance. The Overview - Summary allows you to identify in a chart or table view the product instance that had the most or the most recent changes and should be analyzed first.

̈

© SAP AG

E2E200

9-42

E2 E Change Ana lysis H ist ory of Cha nge s for t he la st 2 yea rs

© SAP 2009

̈ ̈

The tab History of Changes for the last two years reads the data of the current quarter and the 8 quarters before and displays the number of changes for each quarter. As changes cannot be determined for the time prior to the setup of the E2E Change Analysis, the overview report History of Changes for the last 2 years may not necessarily show the changes of the last two years. The displayed timeframe is restricted by the setup of E2E Change Analysis. The report will probably take some time to display the result, because it reads data of several quarters.

© SAP AG

E2E200

9-43

E2 E Change Ana lysis La st Cha nge Da t e

© SAP 2009

̈ ̈ ̈

Below the diagram for the history of the last 2 years you find the table with the Last Change Date. The Last Change Date table lists the date of the most recent change per change group and type. Expanding the hierarchy node will display the change type.

© SAP AG

E2E200

9-44

E2 E Change Ana lysis ECC Se rve r (Sum ma ry)

© SAP 2009

̈

Depending on the type of the product instance, a Summary is displayed. For most types of product instances, additional buttons for details or grouped changes are offered. The example shows an ECC Server summary. The Product Instance - Summary allows you to identify (in a chart or table view) the grouped changes that are the best candidate for a further look on details. In the Product instance of type ABAP the details are grouped by Software Maintenance, Parameter, Transport Requests, SAP Notes and Miscellaneous.

̈ ̈

© SAP AG

E2E200

9-45

E2 E Change Ana lysis ECC Se rve r (T ra nsport Re que st s)

© SAP 2009

̈ ̈ ̈

The slide shows an example of the ECC-specific change group “Transport Requests“. It displays the number of transports per day for the choosen timeframe. Additional statistical information about applying of transport requests is available under Chart: Transports per Hour‚ and Chart: Transports per Day. Cells with a green background color allow calling the Change Reporting Viewer to display the changed content of the ConfigStore.

© SAP AG

E2E200

9-46

T ra nsport St a t ist ic s pe r Da y, pe r Work da y, pe r H our

© SAP 2009

© SAP AG

E2E200

9-47

E2 E Change Ana lysis Ent e rprise Port a l (Sum ma ry)

© SAP 2009

̈

For product instance Enterprise Portal, the changes are grouped by Summary, Dispatcher Configuration, Server Configuration, Node Type Independent Configuration and Software Maintenance as shown in the screenshot.

© SAP AG

E2E200

9-48

E2 E Change Ana lysis Ent e rprise Port al
(for Ex a m ple, Dispat c her Configurat ion)

Change Reporting Viewer will display the changes of the chosen config store in the timeframe, for instance 01/01/2009 to 20/03/2009
© SAP 2009

Change Reporting Viewer will display the changes of the config store onthe date, for instance 19/03/2009 (header of the column)

̈

A green background color is used for cells which have enough detailed information to offer a jump to the Change Reporting Viewer to show the content of a ConfigStore. Depending on the cells‘ information different time selections will be applied.

© SAP AG

E2E200

9-49

E2 E Change Ana lysis H ost

© SAP 2009

̈

For the selected system(s) data of all hosts is displayed on the Hosts tabstrip. In this example, only one host was affected by changes of the environment variables stored in the ConfigStore ENVIRONMENT_VAR_TT5ADM. The details are shown in the Change Reporting Viewer, which is started by a mouse click on a cell with a green background.

̈

© SAP AG

E2E200

9-50

Change Diagnost ic s

Unit 1 Introduction to E2E Change Control Management Unit 2 Transport Strategies Unit 3 Enhanced Change and Transport System Unit 4 Solution Documentation Unit 5 Quality Gate Management Unit 6 Change Request Management Unit 7 Maintenance Management Unit 8 Test Management Unit 9 Change Diagnostics

© SAP 2009

© SAP AG

E2E200

9-51

Change Diagnost ic s: U nit Obje c t ive s

After completing this unit, you will be able to:
̈ ̈ ̈ ̈ ̈ ̈

Understand the concepts and architecture of E2E Change Diagnostics Know which configuration items are collected Find current configuration information with the Change Reporting tool Find recent changes in the solution landscape with the E2E Change Analysis tool Compare multiple systems with the Configuration Validation tool Configure and run non-standard configuration validation reports

© SAP 2009

© SAP AG

E2E200

9-52

Change Diagnost ic s: Mot iva t ion Why is Cha nge Diagnost ic s I m port a nt ?
Controlling the changes during the entire application lifecycle becomes crucial in End-to-End Solution Operations.

End-to-End Change Control Management
Build/Deploy
Bring changes from system A to system B

Test
Impact Analysis and Test

Run
Reporting and History of changes is important

Control changes for all technology platforms Control the quality of implementation projects Document the full change request management process Keep solution up-to-date
© SAP 2009

Estimate the impact of a planned change Perform automated quality checks Perform tests with lowest cost and risk

Provide information for Root Cause Analysis Collect metrics to evaluate and improve IT processes Meet regulatory requirements

̈

Why Change Diagnostics? • Understand the big picture before starting a deeper root cause analysis - Check system landscape: The satellite systems, their main functions and how they connect with each other - Check software components and their versions • Symptoms: - The system behaves differently after a certain date or some changes - One landscape works differently from the other one. For example, QAS is working fine, but PRD has issues.

© SAP AG

E2E200

9-53

T ypic a l Que stions

Which database parameters were changed by the 24/7 support team last night?

How many transports did we import last month?

How many urgent corrections did we import last month? What was last month content of the j2ee/cluster/ instance.properties file?

How many objects did we change last month?

Is there one place where all changes in the system are listed?

What are the configuration differences between server0 and server1?

How many stabilization transports did we have after the last GoLive?

© SAP 2009

̈

End-to-End Change Analysis and Reporting is an important part of End-to-End Change Control Management. If an unknown problem comes up, End-to-End Change Analysis answers the question “What was changed in the system?”

© SAP AG

E2E200

9-54

E2 E Change Diagnost ic s: Be ne fit s

Change Diagnostics supports customers in identifying, controlling, maintaining, and verifying the versions of configurations (such as OS/DB, SAP NetWeaver, Application, Customer Coding)

Benefits of E2E Change Diagnostics
> Central > BI

entry point for analyzing changes in a solution hints for root cause analysis with data and trends

methods to drill down from overviews to detailed lists of changes

> Providing > Providing > Enabling

accurate information on configuration parameters and their history (e.g. database parameters, ABAP parameters, JAVA parameters) the organization to standardize the solution configuration security by controlling the versions of configurations in use

> Improving

© SAP 2009

© SAP AG

E2E200

9-55

Change Diagnost ic s: U nit Ove rvie w Dia gra m
Change Diagnostics Lesson 1: Configuration Items Lesson 2: Data Collection Process Lesson 3: Change Reporting Lesson 4: E2E Change Analysis Lesson 5: Configuration Validation

© SAP 2009

© SAP AG

E2E200

9-56

Config St ore Definit ions Ove rvie w
Software Stores Config Stores

̈ Support Package Stack ̈ Software Component Versions

̈ SAP Product-specific settings ̈ PI/XI-specific configuration ̈ BI-specific configuration ̈ BIA-specific configuration

Application

̈ Implemented SAP Notes ̈ Imported ABAP Transports

̈ Web AS ABAP kernel release

̈ ABAP instance parameters ̈ Java VM parameters for J2EE

Basis

̈ Java VM version ̈ Web AS Java Release

̈ Database Release

̈ Database parameters

Database

̈ Operation System Release

̈ Operating system environment settings

Operating System

̈ Standard Users

Security
© SAP 2009

̈ Gateway Secinfo ̈ Gateway Reginfo

̈

The configuration items of existing systems are stored regularly in corresponding ConfigStores. There are different types of ConfigStores depending on the type of data stored in it. The most important types are xml, txt, ini, properties (two-column based container: parameter, value), table (more than two column based container: key1, key2, value1, value2 …) and event (as table but event-based). See also Note 1230404 “E2E CA Store Content List”

̈

© SAP AG

E2E200

9-57

Config St ore Definit ions De t a ils

http://<hostname>:8000/sap/bc/webdynpro/sap/e2e_ca_store_list

More than 2000 Config Store Definitions Type of Data Source Config Store Store Group Store Hierarchy Store Type Store Category

© SAP 2009

̈

To get a complete list of all the defined ConfigStores, the application “e2e_ca_store_list“ can be used. To start the application, use the URL: http://<server>:<port>/sap/bc/webdynpro/sap/e2e_ca_store_list Stores are defined in the Change Reporting Template Management: WebDynpro appliation diagtpl_upload_app Store Name: Name of the Config Store. The name can also contain wildcards. Then we talk about Config Store Definitions. Store Group: Superset of Config Stores Name: Indicates to which entity in the product hierarchy the config store belongs Store Type: Property, Table, Event, XML, Text Store Category: Software Store or Config Store

̈ ̈ ̈ ̈ ̈ ̈

© SAP AG

E2E200

9-58

Syste m De m o + Ex e rc ise

E2E Change Analysis

© SAP 2009

© SAP AG

E2E200

9-59

Change Diagnost ic s: U nit Ove rvie w Dia gra m
Change Diagnostics Lesson 1: Configuration Items Lesson 2: Data Collection Process Lesson 3: Change Reporting Lesson 4: E2E Change Analysis Lesson 5: Configuration Validation

© SAP 2009

© SAP AG

E2E200

9-60

Configura t ion V a lida t ion Cha llenge s
Are the OS, DB, software and kernel on the certain / latest level? … on all systems? … Please show me? Have we applied SAP Note xxxxx on all systems? … Please report implementation status for all systems? Have we imported Transport Request xxxx (with important performance changes) on all systems? … could I have a list of the systems where it is still missing?

Are all our CRM systems compliant with the new Configuration Baseline ?.. not compliant.. which systems?..why exactly?

Are security settings applied? …on all systems? … could you please confirm and report?

Challenges ̈ A large number of systems … Complex SAP Landscape … ̈ … Need to compare current configuration status against a defined target or standard configuration baselines ̈ … with minimum efforts and ASAP
© SAP 2009

© SAP AG

E2E200

9-61

Configura t ion V a lida t ion – Goa l

The Configuration Validation application is used to compare and validate current values of configuration items of many systems against a defined target system.

© SAP 2009

̈ ̈

The main goal of the Configuration Validation application is to compare and validate current values of configuration items of many systems against a defined target or standard configuration. The validation results are displayed in the browser using Business Intelligence (BI) reporting capabilities. This allows you to perform an interactive cross-system configuration audit and configuration reporting for a large number of compared systems.

© SAP AG

E2E200

9-62

Possible Re fe rence Syst e m s Configura t ion Ba se line s
Compared Systems Reference Systems
1
Existing System (CCDB)

Reference Is a Current System
̈ ̈ ̈

Data stored in the configuration and change database (CCDB) Latest available snapshot used for comparison No changes of configuration items allowed

compare

̈ copy ̈ filter ̈ maintain

Reference Is a Target System compare 2
̈ ̈

Content of current configuration is copied to a separate database table Copied configuration items can be edited to match a specific audit task The reference system should contain a restricted number of configuration items

Existing Systems (CCDB)
© SAP 2009

Target System (DB Table)

̈

© SAP AG

E2E200

9-63

Configura t ion V a lida t ion Arc hit e c ture Ove rvie w
Solution Manager Configuration Validation
Virtual InfoProvider 0SMD_VCA1 Interactive BI-based Reporting - Cross systems / landscape-oriented - Flexible BI user interaction - Customer configuration baselines

Configuration Validation Reporting
Customer-Defined System Configurations / Baselines - Configuration items are edited manually DB Table

Function Module

Target System Maintanence
Manual Maintenance of Copied Configuration Data - Independent from CCDB - Flexible maintenance options

Copy

Existing System Configurations - No changes on Configuration Items allowed

Configuration and Change Database ( CCDB )

Change Reporting

JAVA-Based Installations
Diagnostics Agents
© SAP 2009

ABAP-Based Installations
Extractor Framework (EFWK) Once a day

Solution Tool Plugins

Configuration and Change Reporting - SID-oriented (no crosssystem reporting possible) - No maintenance options for creating configuration baselines (all changes are reported)

̈ ̈ ̈

Validation of the configuration items is based on the data stored in the configuration and change database (CCDB), which is a part of the E2E Diagnostics Infrastructure. The figure describes the architecture and data flow of the configuration validation and the functions of the components belonging to it. As first step, the single configuration items of existing systems are collected and stored by the Extractor Framework (EFWK) in the ConfigStores of the configuration and change database (CCDB). To make this configuration data available for BI reporting, the data from CCDB is read and evaluated by the function module RS_BW_BTC_SMD_CA2_COMPLIANCE1 and passed to the Virtual InfoProvider 0SMD_VCA1 and queries defined on it. The data is not stored in the Virtual InfoProvider 0SMD_VCA1; the validation reports use the appropriate BI structures and reporting features to display the results in the browser.

̈

© SAP AG

E2E200

9-64

H ow t o Ac c e ss Configura t ion V a lida t ion

1. Via direct URL

2. Via SAP GUI

© SAP 2009

̈

Configuration validation is available as of the SAP Solution Manager 7.0 EhP1 and can be accessed in two ways: • Via Solution Manager Work center • Via SAP GUI

̈

The first option accesses the Configuration Validation tool from the Change Management work center of the SAP Solution Manager. To do so, start the Solution Manager work center in the browser by entering http://<hostname>:<port>/sap/bc/webdynpro/sap/ags_workcenter/ and navigate to the Change Management tab. On the left side, you see the Related Links section. In this section, you will find the links Maintenance and Reporting to start applications for target system maintenance and configuration validation reporting. Another way to access configuration validation is using SAP GUI. In the SAP Easy Access menu navigate to Change Management and then open the Configuration Validation section. There are two links below Configuration Validation: Maintenance and Reporting. The link Maintenance starts the Target System Maintenance tool. The link Reporting starts the Configuration Validation Reporting tool. The application configuration validation starts in a separate browser window.

̈

© SAP AG

E2E200

9-65

Configura t ion V a lida t ion T ools Ove rvie w
Target System Maintenance Configuration Validation Reporting

Create and maintain target systems (configuration baselines) ̈ Create templates for target systems ̈ Create comparison lists
̈
© SAP 2009

Select reference system and comparison lists ̈ Execute configuration validation reports
̈

̈ ̈

Target System Maintenance is aimed at creating and maintaining target system configurations, create templates for target system configurations, and create comparison lists. Configuration Validation Reporting is aimed to execute validation reports for selected systems.

© SAP AG

E2E200

9-66

Edit T a rge t Syst e m

Customer-defined target systems

Configuration Stores

Configuration item

© SAP 2009

© SAP AG

E2E200

9-67

Re port ing – Ove rvie w

Select the reference systems

Select the systems to be compared via comparison list

Select the configuration validation report

Execute report
© SAP 2009

© SAP AG

E2E200

9-68

V a lida t ion Report – Ex a mple

Overview Dashboard - Red rating is given if at least one system is not compliant - Green rating is given when all the systems are compliant

Detailed Dashboards - Each area in scope has its own tab - No rating is done

Systems in scope - Reference System - Compared Systems

Navigation Block to Restrict Displayed Items: - As all Items are read, other items can be shown by filtering or deleting the selection - Display of compliant Items also possible (reference values)

Statistics (Number of Compliant and NonCompliant Items) - e.g. to answer the question: “Which systems are not compliant?”
© SAP 2009

Overview of Non-Compliant Items - e.g. to answer the question “Why is a system not compliant?”

© SAP AG

E2E200

9-69

Syste m De m o

Configuration Validation

© SAP 2009

© SAP AG

E2E200

9-70

Configura t ion V a lida t ion In De t a il Cre a t e T a rge t Syst e m
Create Target System
(1) Select Source System (2) Choose necessary Config Stores (3) Create new Target System (3a) Alternatively create new Target System from Template (4) Select Target System (5) Delete unnecessary parameters (if necessary) (6) Modify parameter values (if necessary)

Edit Target System

Create Comparison List

Execute Report

BI User Interaction

Target System as reference

(7) Create new comparison list

(9) Choose Reference System (10) Choose System to be compared (use comparison lists) (11) Choose Configuration Validation Report (12) Execute Report

(13) Personalize data (if applicable)

Existing System as reference

(8) Insert Systems to be compared

(14) Save Bookmark (if applicable) (15) Use export/printing services (if applicable) (16) Use Information Broadcasting (if applicable)

© SAP 2009

̈ ̈

The figure gives an an overview of the configuration validation procedure. In the first step, the target or baseline configuration is defined. It could either be based on a current configuration of an existing system or on a template. If an existing system is supposed to be used as reference system in the reporting, step 1 can be skipped. After the creation of the target system, the selection of the configuration items and their values can be adjusted in accordance with the requirements. At this step, you may define the systems that are to be compared with the reference system. During this step, it is possible to create a comparison list. This step and the use of the comparison list avoids that the user has to select the same comparison systems every time a report is executed.

̈ ̈

© SAP AG

E2E200

9-71

T a rge t Syst e m – V a ria nt s for Crea t ion

̈

Not all configuration items (CIs) relevant for configuration validation (for example, IP address, host names, DIR paths, etc.) When creating the target system, consider this:
̈ ̈

Which Config. Stores relevant and need to be copied? Which parameters and Configuration Items (CIs) relevant? Variant 1 (Create from selected Stores) CCDB Variant 2 (Create from template) CCDB
(1) Select Template (2) Relevant Config Stores selected and stored automatically (4) Relevant Configuration Items (CIs) are restricted automatically

Template contains list of - relevant Config Stores - relevant CIs

(1) Manually select relevant Config Stores

(2) Store selected Config Stores

(3) Manually restrict relevant Configuration Items (CIs)

Target System
© SAP 2009

Target System

̈ ̈

There are two variants to create a target system: Variant 1: Creation from manually selected ConfigStores. This option should be used to create a target system in case configuration items which have to be validated are not contained in the predefined validation templates. Variant 2: Creation in accordance to predefined templates. ConfigStores and configuration items are defined here based on the delivered templates that correspond to one of the predefined validation areas. Those are security validation, software validation, database validation, BI validation. A new target system is created for both of the variants as displayed in the figure.

̈

̈

© SAP AG

E2E200

9-72

Cre a t e T a rge t Syst e m V a ria nt 1 : Cre a te from Se lec t ed St ore s 1/2
1. Start target system maintenance application -Via direct URL: http://<host>:<port>//sap/bc/webdynpro/sap/diagcpl_virt_sys - From Solution Manager Work Center “Change Management”

2. Choose option: “Create Target System” 3. Find source system -Choose “Display all” or SID 4. Use filter to restrict by -Product -SID -Install. Nr 5. Select source system In the right side corresponding Config Stores would be displayed

6. Select required Stores 7. Click the button: “Create from selected Stores”

Variant 1 (Creat e from selecte d Stores ) CCDB

Variant 2 (Creat e from Tem plate) CCD B
(1) Sel ect T empl ate

(1) M an uall y sel ect rel eva nt Con fig Stores

(2) S to re sel ecte d Conf ig S tor es

(2) Rel eva nt Co nfig Sto res sel ecte d and st ore d a utoma tical ly

(3) M an uall y re strict r elev ant Config urati on Ite ms (CI s)

(4) Rel eva nt Co nfigu ratio n Ite ms (CIs ) are r estrict ed a ut omati cally

Target System

Target System

© SAP 2009

̈

The configuration items stored in the CCDB provide information about the technical configuration and the applied software versions of existing systems. This also includes system-specific configuration items like host name, IP address, and so on. However, no other system corresponds with all configuration items to another system. In addition, only some specific configuration items but not the complete system configuration might be relevant for validation. Thus, in many cases, instead of performing a validation against an existing system configuration, a validation against a defined target configuration is required, for example, to validate settings according to corporate security baselines or performance settings across a large number of systems. These target configurations are created based on existing system configurations, and stored in the Solution Manager as "Target Systems". After the required ConfigStores are selected, click the button Create from selected Stores at the bottom of the screen.

̈

̈

© SAP AG

E2E200

9-73

Cre a t e T a rge t Syst e m V a ria nt 1 : Cre a te from Se lec t ed St ore s 2/2
8. Provide in the Popup Window further info for Target System - System ID (up to 8 characters) - Long description (up to 60 characters) 9. Click button: “Save”

10. Check results Make sure that all the Config. Stores are saved in database successfully

11. Close the Popup window

Result
̈

Complete content of the selected stores would be stored in Database

Variant 1 (Creat e from selecte d Stores ) CCDB

Variant 2 (Creat e from Tem plate) CCD B
(1) Sel ect T empl ate

(1) M an uall y sel ect rel eva nt Con fig Stores

(2) S to re sel ecte d Conf ig S tor es

(2) Rel eva nt Co nfig Sto res sel ecte d and st ore d a utoma tical ly

(3) M an uall y re strict r elev ant Config urati on Ite ms (CI s)

(4) Rel eva nt Co nfigu ratio n Ite ms (CIs ) are r estrict ed a ut omati cally

Target System

Target System

© SAP 2009

̈ ̈

In the popup window the name for target system and a description must be provided. The name could be maximum 8 characters long and must not start with 0 which is reserved for SAP objects. After the system ID and the description are provided, the Save button will finally store the content of the selected ConfigStores. Feedback regarding the results of the creation of the selected ConfigStores is provided.

© SAP AG

E2E200

9-74

Cre a t e T a rge t Syst e m V a ria nt 2 : Cre a te from T e mpla t e 1/2
1. Start target system maintenance application -Via direct URL: http://<host>:<port>//sap/bc/webdynpro/sap/diagcpl_virt_sys - From Solution Manager Work Center “Change Management”

2. Choose option: “Create Target System” 3. Find source system -Choose “Display all” or SID 4. Use filter to restrict by -Product -SID -Install. Nr 5. Select source system In the right side corresponding Config Stores would be displayed 6. Click the button: “Create from Template”
Variant 1 (Creat e from selecte d Stores ) CCDB Variant 2 (Creat e from Tem plate) CCD B
(1) Sel ect T empl ate

(1) M an uall y sel ect rel eva nt Con fig Stores

(2) S to re sel ecte d Conf ig S tor es

(2) Rel eva nt Co nfig Sto res sel ecte d and st ore d a utoma tical ly

(3) M an uall y re strict r elev ant Config urati on Ite ms (CI s)

(4) Rel eva nt Co nfigu ratio n Ite ms (CIs ) are r estrict ed a ut omati cally

Target System

Target System

© SAP 2009

© SAP AG

E2E200

9-75

Cre a t e T a rge t Syst e m V a ria nt 2 : Cre a te from T e mpla t e 2/2
7. Provide in the popup window further info for target system -System ID (up to 8 characters) - Long description (up to 60 characters)

8. Select template Template provides information on which Config Stores would be used to create a Target System and which Configuration Items (e.g. parameters) would need to be saved.

Option to keep all Configuration Items: If this option is selected then complete content of Config Stores would be copied.

Result
̈

9. Click button: “Create”

From the source system content of only those stores would be copied that are known in the Template Configuration items from these Stores would be restricted in accordance with the template

̈

Variant 1 (Creat e from selecte d Stores ) CCDB

Variant 2 (Creat e from Tem plate) CCD B
(1) Sel ect T empl ate

(1) M an uall y sel ect rel eva nt Con fig Stores

(2) S to re sel ecte d Conf ig S tor es

(2) Rel eva nt Co nfig Sto res sel ecte d and st ore d a utoma tical ly

10. Check results Make sure that all the Config. Stores are saved in Database successfully
© SAP 2009

(3) M an uall y re strict r elev ant Config urati on Ite ms (CI s)

(4) Rel eva nt Co nfigu ratio n Ite ms (CIs ) are r estrict ed a ut omati cally

Target System

Target System

̈

Provide Target System Name and Description: In the popup window the name for target system and a description must be provided. The name could be maximum 8 characters long and must not start with 0 which is reserved for SAP objects. Select Template: After the target system ID and the description are provided, the required template from the template list is selected. The templates for the different validation areas, such as validation of BI, database, software, or security are available. In this example, a target system for software configuration validation is to be created. To do this, the template “0SW” can be used. This template contains preselected configuration items for the areas: ABAP and Java Software Level, ABAP Kernel Level, OS Level, SAP Notes, Transport Requests, ABAP Profile parameters and for ABAP Memory configuration. Click the Create button: At this step, the ConfigStores matching the template will be copied from the selected source system. The configuration items within these stores will be filtered in accordance with the configuration items defined in the ConfigStores of the template. To store all the configuration items from the source ConfigStore without filtering, the option Keep all parameters from source system has to be selected at the bottom of the screen. In that case, the template determines only the ConfigStores. Check the saving results. After a target system is created from a template, a feedback is provided. The newly created target systems might be found and maintained under the link Edit Target System, which is described in the chapter “Editing Target System”.

̈

̈

̈

© SAP AG

E2E200

9-76

Syste m De m o

Create Target System

© SAP 2009

© SAP AG

E2E200

9-77

Configura t ion V a lida t ion in De ta il Edit T a rge t Syst e m
Create Target System
(1) Select Source System (2) Choose necessary Config Stores (3) Create new Target System (3a) Alternatively create new Target System from Template (4) Select Target System (5) Delete unnecessary parameters (if necessary) (6) Modify parameter values (if necessary)

Edit Target System

Create Comparison List

Execute Report

BI User Interaction

Target System as reference

(7) Create new comparison list

(9) Choose Reference System (10) Choose System to be compared (use comparison lists) (11) Choose Configuration Validation Report (12) Execute Report

(13) Personalize data (if applicable)

Existing System as reference

(8) Insert Systems to be compared

(14) Save Bookmark (if applicable) (15) Use export/printing services (if applicable) (16) Use Information Broadcasting (if applicable)

© SAP 2009

̈

After a target system is created, it is often necessary to adjust it to the customer requirements. For example, to perform a validation of security standards, the existing ABAP instance parameters need to be restricted to only those that are relevant for security validation.

© SAP AG

E2E200

9-78

Edit T a rge t Syst e m
1. Start target system maintenance application -Via direct URL: http://<host>:<port>//sap/bc/webdynpro/sap/diagcpl_virt_sys - From Solution Manager Work Center “Change Management”

2. Choose option: “Edit Target System” 3. Find target system Choose “Display all” or search by SID 4. Select target system In the right side corresponding Config Stores would be displayed 5. Select Store to be edited Content of Config Store in source system Not editable (Info only)

6. Edit content of Config Store in target system

© SAP 2009

̈ ̈ ̈

Start the tool Target System Maintenance: Start the Target System Maintenance tool as is described in chapter “Start Target System Maintenance“ . Choose Edit Target System: After the tool has been started, click the link Create Target System on the left side to start the application for the target system creation. Find target system: All existing target systems can be displayed by clicking the link Display all in the section Edit Target System. Alternatively, filtering is possible by entering the required system ID into the corresponding input field. Table Select Target Systems displays the system ID, product name, and description of the target systems Select Target System: Select a target system for editing by clicking on the system name. As soon as a target system is selected all ConfigStores included into this system will be displayed at the right side in the table ConfigStores of Target System. The title of this table displays the currently selected target system. Select Store to be edited: Clicking on the ConfigStore name will allow editing the content of ConfigStore. At the bottom of the screen, two tabs are displayed. In the Tab Edit Store Content at the left side a list of configuration items from the selected ConfigStore is displayed. These entries can be modified. Here, you can change values, insert new entries, or delete old entries. In the table on the right side, the configuration items from the corresponding source system are displayed. In this table, the current values of the configuration items are displayed. This view allows comparing the modifications done in the target store with the real configuration item values stored in the source system.

̈

̈

© SAP AG

E2E200

9-79

Edit T a rge t Syst e m M a inte na nc e Func tions
Select / Deselect all Invert selection Remove Filter Delete selection Add entry Display Options Filter options Wild cards could be used (e.g. *, !, <!, +)

Select Configuration Item At the right side corresponding Configuration Item from the Source System would be highlighted (if exists)

Edit value Any value could be inserted

Delete single Configuration Item Any value could be inserted

Detailed Info on Config Store - Source System - Changed On - Changed by -…

Save current content

© SAP 2009

̈ ̈

This figure provides an overview of the maintenance options available for editing target systems. With these options it is possible to select, delete, and insert entries. In the example, the entries that are not relevant for configuration validation will be be deleted and only the necessary configuration items will be left.

© SAP AG

E2E200

9-80

Edit T a rge t Syst e m Displa y Opt ions

Display Matching Entries On the right side (Source) entries in Source matching to Target System entries are displayed.

Select options for source system

Display Extra Entries On the right side (Source) entries in Source missing in Target System are displayed. - You can add entries to the target system at any time.
Add entries from source to target
© SAP 2009

̈ ̈

Display matching entries: By default, on the right (source system) only the entries matching the selected Target ConfigStore are displayed. Display extra entries: To display all parameters existing in the source systems and missing in the target system, click the button in the menu bar: This view can be used if some other configuration items need to be added from the source system later. To add the configuration items, select the necessary configurations items and click the button. The parameters will be added to the target system and removed from the table of source system configuration items.

© SAP AG

E2E200

9-81

Edit T a rge t Syst e m Add/Rem ove St ore s
Add / Remove Stores from Target System

Add Stores from Source to Target System Remove Stores from Target System

Save Target System as Template

© SAP 2009

̈ ̈

To add additional ConfigStores from the corresponding source system, use the link Add/Remove Stores. Display the ConfigStores from the source system: In the popup window on the right side, the ConfigStores of the target system are displayed. On the left side, the available ConfigStores of the source system are displayed. The displayed source system was used to create the target system. From the left table, additional stores can be added to the target system. Filter the necessary ConfigStores: To find the required ConfigStores, filter options might be used. In the example below, additional ConfigStores are added to the target system. Those are ABAP_COMP_SPLEVEL, ABAP_NOTES and ABAP_PACKAGES. To do this, first all the existing ConfigStores are filtered to only those that have an “ABAP” string in their name. Select the required ConfigStores. Add the required ConfigStores to the target system: After the necessary ConfigStores are selected, the Add button adds the selected ConfigStores to the target system. At this step, the content of the selected ConfigStores will be copied to the target system.

̈

̈ ̈

© SAP AG

E2E200

9-82

Displa y T e m pla te

1. Choose option: “Display Template” 2. Find template Template starting with 0 in the name are delivered by SAP and cannot be changed 3. Select template In the right side corresponding Config Stores would be displayed 5. Select source system To display content of corresponding store Display content of template Condig Store -In the template no values are stored but only names of parameters or configuration items - Values are taken from Source by creation of Target System - Not editable (display only)
© SAP 2009

Source Systems that have Config Store with this name

4. Select Store to be displayed

Content of Config Store in Source System Not editable (display only)

̈ A template contains information about ConfigStores and configuration items and is used to filter the

configuration items when a target system is created.
̈ In the diagram the steps to display content of templates are provided: ̈ Choose option “Display Template”: Templates can be displayed in the Target System Maintenance

application by using the link Display Templates.
̈ Find Template: All available templates can be displayed by clicking on the link Display all in the section

Display Templates. Alternatively, filtering is possible by entering the required template ID into the corresponding input field. The table Templates displays the system ID, product name, and description of displayed templates. A template that starts with "0" is delivered by SAP and cannot be modified. These templates are used to create target systems for predefined validation areas such as validation of BI, database, or software configuration.
̈ Select Template: Select a template for display by clicking the system name. As soon as a template is selected,

all the ConfigStores included into this template will be displayed at the right side in the table "ConfigStores of Target System" The title of this table displays the currently selected template
̈ Select Store to be displayed: To display the content of a ConfigStore from a templates click on the

ConfigStore name. In the example below the content of ConfigStore SAP_KERNEL of the template CRM_TPL is displayed. In the bottom part of the screen the content of template ConfigStore is displayed. As can be seen in the figure above, the values of configuration item are not part of the template.
̈ Select Source System: In the middle of the screen, a list of the ConfigStores from source systems is displayed

which have the same name.

© SAP AG

E2E200

9-83

Syste m De m o

Edit Target System

© SAP 2009

© SAP AG

E2E200

9-84

Configura t ion V a lida t ion in De ta il Cre a t e Com pa rison List s
Create Target System
(1) Select Source System (2) Choose necessary Config Stores (3) Create new Target System (3a) Alternatively create new Target System from Template (4) Select Target System (5) Delete unnecessary parameters (if necessary) (6) Modify parameter values (if necessary)

Edit Target System

Create Comparison List

Execute Report

BI User Interaction

Target System as reference

(7) Create new comparison list

(9) Choose Reference System (10) Choose System to be compared (use comparison lists) (11) Choose Configuration Validation Report (12) Execute Report

(13) Personalize data (if applicable)

Existing System as reference

(8) Insert Systems to be compared

(14) Save Bookmark (if applicable) (15) Use export/printing services (if applicable) (16) Use Information Broadcasting (if applicable)

© SAP 2009

̈

After the reference configuration is prepared, it is possible to define systems for comparison. These might be, for example, “all ABAP production systems” or “all SAP BI systems” or “all systems relevant for critical Business Process”. It is not necessary to have these lists defined, since the restriction on the systems can also be done in the variable screen of the validation report. However, it is more convenient to create a comparison list while having in mind to use them regularly. In order to avoid selecting single systems one by one each time, a validation report is executed it is possible to create a list of these systems only once and use it for configuration validation reporting. A list of systems to be compared is named “Comparison List". This chapter describes how to create and maintain such a list.

̈

© SAP AG

E2E200

9-85

Cre a t e Com pa rison List s
2. Choose option: “Create New”

1. Choose option: “Maintain Comparison Lists”

3. Provide Name and Description 4. Display Systems available for Configuration Validation 5. Use filter options to restrict displayed Systems

6. Select Systems to be added to the Comparison List 7. Create Comparison List

© SAP 2009

̈ ̈ ̈ ̈

This figure describes the steps required to create a new comparison list. Choose Maintain Comparison Lists: The link Maintain Comparison Lists starts the application. Create New: The link Create new opens a new popup window to select systems and create a new comparison list. Provide Name and Description: In the popup window the name for comparison list and a description must be provided. In this example, a list including all systems having ABAP-based components will be created. Let us name it "ALL_ABAP“. Display systems available for Configuration Validation: After the list name and the description are provided, the systems can be added to the list. The link Display all shows all available systems. In the table, all systems relevant for configuration validation are displayed. For systems with a double stack, separate entries for ABAP- and Java-based components are displayed. Filter Option: The filter option at the top of the table can be used to filter systems by system ID, type, installation number, or product name. In the example, all systems that have ABAP-based components have to be filtered. To do so, the dropdown list in column Type is used for filtering. Select Systems to be added: After ABAP-based systems are filtered, the required entries are selected. You may select all entries or one after the other. Create “Comparison List”: Adding the selected systems to the Comparison List

̈

̈

̈ ̈

© SAP AG

E2E200

9-86

Compa rison List s – M a int e na nc e Opt ions

1. Choose option: “Maintain Comparison Lists”

3. Display Systems available for Configuration Validation 4. Use Filter to restrict displayed systems

2. Select Comparison List In the bottom side corresponding Systems would be displayed

5. Add selected Systems to Comparison List

4a. Selected Systems to be added to the Comparison List
© SAP 2009

̈

Display systems from the comparison list: Clicking on the link in the column Name displays the systems belonging to this list. On the left side, the systems belonging to the comparison list are displayed. Remove systems from the comparison list: The icon in the column Delete removes systems from the list. Add systems to the comparison list: On the right-hand side of the screen, the list of the source systems that do not belong to the selected comparison list are shown. These systems can be added to the comparison list at any time. To add the systems to the comparison list, select the required systems and click the Add button.

̈ ̈

© SAP AG

E2E200

9-87

Syste m De m o

Create Comparison List

© SAP 2009

© SAP AG

E2E200

9-88

Configura t ion V a lida t ion in De ta il Ex ec ut e Re port
Create Target System
(1) Select Source System (2) Choose necessary Config Stores (3) Create new Target System (3a) Alternatively create new Target System from Template (4) Select Target System (5) Delete unnecessary parameters (if necessary) (6) Modify parameter values (if necessary)

Edit Target System

Create Comparison List

Execute Report

BI User Interaction

Target System as reference

(7) Create new comparison list

(9) Choose Reference System (10) Choose System to be compared (use comparison lists) (11) Choose Configuration Validation Report (12) Execute Report

(13) Personalize data (if applicable)

Existing System as reference

(8) Insert Systems to be compared

(14) Save Bookmark (if applicable) (15) Use export/printing services (if applicable) (16) Use Information Broadcasting (if applicable)

© SAP 2009

̈

After defining a target system and a comparison list, everything is ready to execute configuration validation reports in accordance with the validation area.

© SAP AG

E2E200

9-89

Re port ing – T e chnic a l Bac kground

Existing System (CCDB)

Provides validation results for BI Reporting - Configuration Validation results are stored in format appropriate to BI Query execution - Data are not persisted but available for the time of reporting only

Function Module

Virtual InfoProvider
0SMD_VCA1

Target System (DB Table)

Performs Configuration Validation - Read configuration data of existing and Target Systems - Perform validation - Fill Virtual Info Provider with validation results

Execution of predefined Reports - Selection of Reference and Compared Systems - Reports for most common areas - Generic report for customer defined configuration baselines - Accessible from a central entry point - Pre-calculation via BI possible to minimize query response times BI User Interaction - Execution in a browser - High-level dashboards - Drill-down to detailed dashboards

© SAP 2009

̈ ̈

SAP delivers a number of predefined validation reports for different validation areas such as security configuration validation or software level validation. The validation reports are BI WebTemplates with queries or views based on the Virtual InfoProvider 0SMD_VCA1 as data provider. BI WebTemplates allow the use of standard BI reporting capabilities such as user interaction, broadcasting, and publishing.

© SAP AG

E2E200

9-90

Re port ing – Func t ions Ove rvie w

2. Select Reference Systems (optional) - Existing systems with real configuration data - Target System (customer defined) Target System (customer defined) <SID> VIRTUAL Existing System <SID> <Install. Number>

1. Start Configuration Validation Reporting
-Via direct URL: http://<host>:<port>//sap/bc/webdynpro/sap/config_compliance_report - From Solution Manager Work Center “Change Management”

Maintain Comparison Lists (optional) - Create new - Display systems from list

4. Select Configuration Validation Report Could be edited Predefined Reports for validation of - Software Configuration - Security Configuration - Database Configuration - BI Configuration Generic Reports for validation based on - Customer defined ConfigStores and Configuration Items / Parameters
© SAP 2009

3. Select Comparison List (optional)

5. Execute Report - Check / adjust selected reference and compared systems - Suppress variable pop-up for direct report execution

̈ ̈ ̈

Start the tool Configuration Validation Reporting: The Configuration Validation Reporting tool is started by clicking the Reporting link from the SAP Solution Manager Work Centers. Select Configuration Validation Report: As the Configuration Validation Reporting tool is started at the top of the screen, the predefined reports are displayed. Execute Configuration Validation Report: The link Start configuration validation reporting at the bottom part of the screen executes the selected validation report.

© SAP AG

E2E200

9-91

Re port ing Pre defined Report s w ith We b T e m pla t e s
Software Configuration Validation - ABAP and Java Software Level - ABAP Kernel Level - OS Level - SAP Notes - Transport Requests - Profile parameters (ABAP Memory) Security Configuration Validation - ABAP Software Level - ABAP Kernel Level - SAP Notes - IGS Level - GW secinfo settings (*) - GW reginfo settings (*) - Standards Users (*) - Profile parameters (ABAP security) BI Configuration Validation - BI parameter configuration: (ROIDOCPRMS, RSADMINS, RSADMINA, RSADMIN, RSFRONTENDINIT) Reference Configuration Validation - Choose reference system (target or current one) - Validation would be done on basis of ConfigStores and configuration items available in the reference system.

Database Configuration Validation Database Level and parameters for - Oracle - MS SQL - DB2 UNIX and Windows - MaxDB Custom Configuration Validation - Choose ConfigStore (s) using the query variables pop-up - Choose Configuration Items (s) using the query variables pop-up

(*) The Configuration Compliance Comparison is not done versus the items of the reference system, but in accordance with defined rules. See SAP Note 1234799 for more information. The reference system can have non-compliant items as well.
© SAP 2009

̈

To minimize efforts required for the implementation of configuration validation, a number of predefined validation reports are delivered for different validation areas. Those are: software validation, security validation, database validation, SAP BI validation, and customer-defined validation.

© SAP AG

E2E200

9-92

Re port ing – Report Ex ec ution
1. Select Configuration Validation Report 2. Execute Configuration Validation Report (Variant 1). Directly execute validation report - if option Suppress query variables pop-up is selected

(Variant 2) Check / adjust selected Systems and Configuration Items If query variables pop-up” is not suppressed
© SAP 2009

̈ ̈

If you do not select the Suppress query variable pop-up, a window will appear in which you can check or adjust the reporting parameters. The option Suppress query variable popup can be selected to avoid displaying the variable screen and to directly execute a validation report. Of course, a reference system (section “Choose a Reference System“) needs to be selected before.

© SAP AG

E2E200

9-93

Syste m De m o

Execute Report

© SAP 2009

© SAP AG

E2E200

9-94

Configura t ion V a lida t ion in De ta il BI U se r I nt e ra c t ion
Create Target System
(1) Select Source System (2) Choose necessary Config Stores (3) Create new Target System (3a) Alternatively create new Target System from Template (4) Select Target System (5) Delete unnecessary parameters (if necessary) (6) Modify parameter values (if necessary)

Edit Target System

Create Comparison List

Execute Report

BI User Interaction

Target System as reference

(7) Create new comparison list

(9) Choose Reference System (10) Choose System to be compared (use comparison lists) (11) Choose Configuration Validation Report (12) Execute Report

(13) Personalize data (if applicable)

Existing System as reference

(8) Insert Systems to be compared

(14) Save Bookmark (if applicable) (15) Use export/printing services (if applicable) (16) Use Information Broadcasting (if applicable)

© SAP 2009

̈ ̈

If necessary, the output of the BI report can be adapted or saved offline. In this chapter, it will be shown how to use some important standard BI User Interaction functionalities.

© SAP AG

E2E200

9-95

BI U se r I nt e ra c t ion Ove rvie w a nd De ta ile d Da shboa rds
Overview Dashboard - Red rating is given if at least one system is not compliant - Green rating is given when all the systems are compliant Detailed Dashboards - Each area in scope has its own tab - No rating is done

Systems in scope - Reference System - Compared Systems

Navigation Block to restrict displayed Items: - As all Items are read, other items can be shown by filtering or deleting the selection - Display of compliant Items also possible (reference values)

Statistics (number of compliant and Non compliant Items) e.g. to answer question: “Which Systems are not compliant?”
© SAP 2009

Overview of non-compliant Items - e.g. to answer question “Why System is not compliant?”

̈ ̈

After the report is executed, the validation results are displayed. In this diagram, an output of the validation report is shown. The information is separated into different tabs corresponding to the validated areas. The first tab is an overview screen that comprises the results for all validated areas. The further tabs contain detailed information on the corresponding area. At the top of the screen, the system ID of the reference system and the list of the comparison systems and their installation numbers are displayed. In the middle of the screen, an overview of all areas covered by the report is displayed. In this example, the following areas have been covered: ABAP Software Level, ABAP Kernel Level, Profile Parameters, Gateway Secinfo, SAP Notes, IGS Level, Standard Users, and Gateway Reginfo. For each validation category, the number of compliant and non-compliant systems is displayed. In case there is at least one system that is not compliant with the reference system, the validation category is highlighted in red. Only if all the systems are compliant, the validation category is marked green. Validation for Standard Users, Gateway Security, and Gateway Reginfo is not done versus the configuration items of the reference system but in accordance with the rules that are listed in the SAP Note 1234799. The content of the ConfigStore of the reference system is not taken into account here.

̈ ̈ ̈ ̈

̈

© SAP AG

E2E200

9-96

BI U se r I nt e ra c t ion – Filt e r Opt ions

1. Filter single System

1. Right mouse click on System Name

2. Choose Keep Filter Value”

3. Values displayed only for C60

2. Display reference values
1. Navigation Block - Remove option for Compliance filter

2. Values displayed both for noncompliant as well as for compliant systems - You can compare values from reference and compared systems

© SAP 2009

̈

Filter single system: If a lot of the systems or configuration items are used for comparison, then the list of validated items displayed is very long. In this case, it is useful to filter values only for one system and hide all the other values. In the example, the configuration items for system C60 are filtered. This is possible by clicking with the right mouse button on the system name C60 and choosing the option Keep Filter Value from the drop-down list. Then the values for the selected system are filtered while all the other values are hidden. Now the table Not compliant items includes only values for the C60 system. Display reference values: In the middle part, a Navigation Block is provided aimed to restrict the displayed data. By default, only the non-compliant configuration items are displayed. The filter option in the navigation block can be removed to display also the compliant values, such as the values from the reference system. The filter may be removed by clicking the waste container icon in the filter column of characteristic Compliance.

̈

© SAP AG

E2E200

9-97

BI U se r I nt e ra c t ion – M a int e nence Opt ions

3. Display validity date of displayed configuration data

1. Navigation Block - Display “ConfigStore Valid To”

2. Validity Date is displayed - Timestamp of last successful ConfigStore update

4. Export to Excel (BI standard functionality)
1. Navigate to Enhanced Menu Right mouse click on the list 2. Export to CSV or Excel format

© SAP 2009

̈

Display validity date of displayed configuration data: In order to check when the configuration items have been updated, click the icon for the section: ConfigStore Valid To. The column ConfigStore Valid To is added to the table Not compliant Items. Export to Excel: Navigate to the enhanced menu of the context menu. To do this, click in any place of the table with the right mouse button and choose Enhanced Menu. Choose Export as CSV File or MS Excel 2000 File from the drop-down list.

̈

© SAP AG

E2E200

9-98

BI U se r I nt e ra c t ion Re fe re nc e Va lida t ion Report
Target System ConfigStores - Only these ConfigStores would be taken for validation in the compared Systems - Only Configuration Items from these ConfigStores would be validated

Compliance 1 – Configuration Item is compliant 0 – Configuration Item is not compliant

Validation Results - Hierarchical view of Compared Systems - Display of ConfigStores and Configuration Items matching Target System definition
© SAP 2009

̈

These reports (CUSTOM and REFERENCE VALIDATION) are not restricted to ConfigStores. For the REFERENCE VALIDATION all ConfigStores and Configuration Items of the reference system are taken for the validation. The CUSTOM VALIDATION additionally offers to restrict on 'Config Store', 'Configuration Items', 'Item Value' and a time interval for 'Transport Requests in Date Range': Both validations display a top-down view starting with the system level and the information whether all items of the reference system in case of the REFERENCE VALIDATION or the selected items in case of the CUSTOM VALIDATION are found as compliant in the comparison system. The REFERENCE VALIDATION is restricted on items whose compliance is “Yes” or “No”. It is expected that a target system with a restricted number of items per ConfigStore is used. Thus, the comparison systems will have more items in their ConfigStores. These are found and valuated with compliance 'Additional in Comparison System'. Because of the mentioned restriction on compliance “Yes” or “No”, these items are not taken into account as long the restriction is not removed. The CUSTOM VALIDATION on the other hand does not have this restriction in default.

̈ ̈

̈

© SAP AG

E2E200

9-99

Syste m De m o

BI User Interaction

© SAP 2009

© SAP AG

E2E200

9-100

Ex e rc ise

Configuration Validation

© SAP 2009

© SAP AG

E2E200

9-101

Change Diagnost ic s: U nit Sum m a ry

You should now be able to:
̈ ̈ ̈ ̈ ̈ ̈

Understand the concepts and architecture of E2E Change Diagnostics Know which configuration items are collected Find current configuration information with the Change Reporting tool Find recent changes in the solution landscape with the E2E Change Analysis tool Compare multiple systems with the Configuration Validation tool Configure and run non-standard Configuration Validation reports

© SAP 2009

© SAP AG

E2E200

9-102

Exercises
Unit: Lesson: Change Diagnostics Change Reporting

At the conclusion of this exercise, you will be able to: • Find information for a customer solution in Solution Manager diagnostics • Use the Change Reporting tool in the Solution Manager diagnostics to find the change history of single parameter and to compare the parameter settings in a clustered environment

TT4 is the SAP Solution Manger system that contains all information about the managed systems. TT5 is a satellite system that is managed by TT4.

9-1

Use the Change Reporting tool to answer the following questions. 9-1-1 Start the Change Reporting tool and find information for the Change Reporting TT5 ABAP instance. What is the current Support Package level for the software component SAP_APPL? Answer:_______________________________________________________ Who is the vendor and what is the version of the ABAP database? Answer:_______________________________________________________ What is the value for the max server memory (MB) parameter for the ABAP database? Answer:_______________________________________________________ What is the value for the kernel patch level? Answer:_______________________________________________________ 9-1-2 Find information for the TT5 JAVA instance. What is the current release and Support Package level for the software component SAP J2EE Engine? Answer: _______________________________________________________

© SAP AG

E2E200

9-103

What is the current release and Support Package level for the software component SAP ESS? Answer: ________________________________________________________ How many MB of physical RAM does the hardware have? Answer: ________________________________________________________ 9-2 The values for Java VM parameters –XX:PermSize and –XX:MaxPermSize specify the amount of memory that is reserved for objects (for example, classes) that the J2EE application needs to be stored permanently in the RAM. It is therefore an important parameter which could have a significant impact on performance. Use the Change Reporting tool to find out if this parameter was changed on system TT4. 9-2-1 How many server nodes does the TT4 Java instance ahve? Answer:________________________________________________________ 9-2-2 Check the Cluster Node Information store group on server node 0. What is the current value for parameter –XX:MaxPermSize on this node? Answer:_______________________________________________________ 9-2-3 What was the previous value for this parameter? Answer: _______________________________________________________ 9-2-4 When was this parameter changed? Answer: _______________________________________________________ 9-2-5 What is the current value for this parameter on server node 1? Answer:________________________________________________________ 9-2-6 Compare the oldest available configuration snapshot of the Solution Manager (TT4) Java Stack with the most current configuration snapshot of the Solution Manager (TT4) Java Stack. What are the differences in the Cluster Node Information store group of server node 0? Answer:_______________________________________________________

© SAP AG

E2E200

9-104

Exercises
Unit: Lesson: Change Diagnostics E2E Change Analysis

At the conclusion of this exercise, you will be able to: • Find information for a customer solution in SAP Solution Manager Diagnostics • Use the E2E Change Analysis tool to discover all changes of the last week in the ABAP and JAVA stack of the SAP ERP system TT5. • Find detailed information for each change. 9-3 Analyze the changes in the SAP ERP system TT5 in the current week. 9-3-1 9-3-2 9-3-3 Navigate to E2E Change Analysis. What is the path? What is the number of changes for each main instance in this week? Look at the main instance TT5 – SAP ECC Server. For which change groups have changes been recorded? Look at the main instance TT5 – SAP NW – Enterprise Portal. For which change groups have changes been recorded? Which J2EE transport requests were imported into the TT5 – SAP NW – Enterprise Portal (check the Node Type Independent Configuration tab)?

9-3-4

9-3-5

© SAP AG

E2E200

9-105

Exercises
Unit: Lesson: Change Diagnostics Configuration Validation

At the conclusion of this exercise, you will be able to: • Maintain a target system with reference configuration values; these values can be compared against existing systems in order to see if the defined configuration items are identical in all compared systems • Maintain a comparison list with systems that will be compared with the reference system • Execute a Configuration Validation report 9-4 Execute the predefined Configuration Validation report for Software Validation. 9-4-1 9-4-2 9-4-3 Start the Configuration Validation Reporting application. Execute the first report: 0TPL_0SMD_COMPL_SW_START for SOFTWARE VALIDATION. Enter the reference system TT4 0120003411 and the comparison system TT5 0120003411 and execute the comparison. Which store groups are compliant? Answer: ____________________________________________________ 9-4-4 Look in the details for the ABAP Parameters. How many parameters were compared? Answer: ____________________________________________________ 9-4-5 9-5 Display the compliant values in the result table.

Create a new target system. This will be used as a reference system for comparisons with physical systems. 9-5-1 9-5-2 Start the Configuration Validation Maintenance application. Create a new target system. Choose the following stores from the source system TT4: • • • • ABAP_COMP_SPLEVEL ABAP_INSTANCE_PAHI ABAP_NOTES MSSQL_LEVEL

Choose Create from selected Stores. Enter the ID S## (where ## is your group number) for your target system.
© SAP AG E2E200 9-106

9-6

Edit the target system. Only certain parameters of the selected config stores will be used for the comparison. 9-6-1 By default, all items of the selected config stores are included in your new target system. However, you only want to compare a limited set of parameters, which are listed below. Delete all other parameters. ABAP_COMP_SPLEVEL • ST-PI abap/heap_area_dia abap/heap_area_nondia abap/heap_area_total 0001286192 0001286678 SQLVERSION ABAP_INSTANCE_PAHI • • •

ABAP_NOTES • •

MSSQL_LEVEL • 9-7 Create a new comparison list that includes the systems TT4 and TT5. These systems will later be compared with the reference system. 9-7-1 9-8 Create a new comparison list that comprises the systems TT4 and TT5. Name it SOL## (where ## is your group number). Execute the Configuration Validation report. Compare the values that are defined in your target system with the values of the systems TT4 and TT5 of your comparison list. Are the systems compliant?

Execute the Configuration Validation report. 9-8-1

9-9

The BI User Interaction allows you to display the result in different views based on BI query navigation options. 9-9-1 The result table on the right-hand side shows the comparison systems TT4 and TT5, including the compared config stores, the config store items, and the item values. Include the reference system in this table, too. Display only the values for the system TT5 in the result table. Remove the values of the configuration items from the result table.

9-9-2 9-9-3

© SAP AG

E2E200

9-107

© SAP AG

E2E200

9-108

Solutions
Unit: Lesson: E2E Change Diagnostics Change Reporting

9-1

Use the Change Reporting tool to answer the following questions 9-1-1 Start the Change Reporting tool and find information for the TT5 ABAP instance. Log on to SAP Solution Manager and open the Root Cause Analysis work center. Choose System Analysis and select the TT5 system. Choose Change Reporting and select the Change Reporting TT5-ABAP tab. If you did everything right, you should see a screen similar to this one.

What is the current Support Package level for the software component SAP_APPL? Choose ABAP-Software. Then open the store with the alias ABAPSOFTWARE: SUPPORT-PACKAGE-LEVEL. Who is the vendor and what version does the ABAP database have? Choose ABAP-DATABASE. Then open the store with the name MSSQL_LEVEL. What is the value for the max server memory (MB) parameter for the ABAP database? Enter the search text in the Search field and navigate to the section ABAPDATABASE MSSQL_PARAMETER. The parameter will be highlighted in the Store Content area.

© SAP AG

E2E200

9-109

What is the value for the kernel patch level? Choose Instance å SAP_KERNEL. You will find the kernel patch level in the Store Content area. 9-1-2 Find information for the TT5 JAVA instance What is the current release and Support Package level for the software component SAP J2EE Engine? Select the Change Reporting TT5 JAVA tab. Select the store group J2EESOFTWARE and select the store with the name J2EE_COMP_SPLEVEL. In the Store Content area, search for the software component SAP J2EE ENGINE.

What is the current release and Support Package Level for the software component SAP ESS? In the Store Content area, search for the software component SAP ESS.
© SAP AG E2E200 9-110

How many MB of physical RAM does the hardware have? Choose the HARDWARE store group and select the store with the name saposcol. In the Store Content area, search for the property PhysicalRAMInMB. 9-2 The values for Java VM parameters –XX:PermSize and –XX:MaxPermSize specify the amount of memory that is reserved for objects (for example, classes) that the J2EE application needs to be stored permanently in the RAM. It is therefore an important parameter which could have a significant impact on performance. Use the Change Reporting tool to find out if this parameter was changed on system TT4. 9-2-1 How many server nodes does the TT4 Java instance have? In the RCA work center, choose System Analysis and select the TT4 system. Choose Change Reporting and then choose the Change Reporting TT4-JAVA tab. Choose TT4-Java Solution Manager JAVA Stack tt4tdc00 Installed on path G:\usr\sap\TT4 Instance DVEBMGS00. Answer: The TT4 Java instance has two server nodes. 9-2-2 Check the Cluster Node Information store group on server node 0. What is the current value for parameter –XX:MaxPermSize on this node? Answer: The parameter –XX:MaxPermSize has the value 512 MB. 9-2-3 What was the previous value for this parameter? Click the icon in the History column at the end of the row to see the change history.

Answer: The previous value for the parameter was 400 MB.

© SAP AG

E2E200

9-111

9-2-4

When was this parameter changed? Answer: The change date was March 31, 2009.

9-2-5

What is the current value for this parameter on server node 1? Choose the Cluster Node Information store group of server 1 and open the store in the Store List section. The requested parameter can be found in the store content below the VmParameters section.

Answer: The current value for the parameter –XX:MaxPermSize on server node 1 is 400 MB. 9-2-6 Compare the oldest available configuration snapshot of the Solution Manager (TT4) Java Stack with the most current configuration snapshot of the Solution Manager (TT4) Java Stack. What are the differences in the store group Cluster Node Information of server node 0? Choose the Compare tab and select the oldest available timestamp in the Reference section. Check that the timestamp in the Custom section is showing the most current value. Select Solution Manager JAVA Stack as the reference system and make sure that the same entry is selected as Custom System. Scroll down and choose Compare.

© SAP AG

E2E200

9-112

The comparison result will be displayed in the lower section of the screen. Select the row with status Different to see the result details.

© SAP AG

E2E200

9-113

Navigate to section server 0 and open the store below the Cluster Node Information store group. The table displays for each of the sections, including the Reference Value and the Custom Value. The differences are marked with a red icon.

© SAP AG

E2E200

9-114

Solutions
Unit: Lesson: Change Diagnostics E2E Change Analysis

9-3

Analyze the changes in the SAP ERP system TT5 in the current week. 9-3-1 Navigate to E2E Change Analysis. What is the path? Go to the Root Cause Analysis work center and choose End-to-End Analysis. Then select system TT5 and choose Change Analysis.

9-3-2

What is the number of changes for each main instance in this week? The time frame This week should be pre-selected. Select the Overview and Summary tabs to see all changes for this week. Expand the Table view below the diagram. A table appears that shows the number of changes for each main instance per day. Summarize the number of changes for each main instance.

© SAP AG

E2E200

9-115

9-3-3

Look at the main instance TT5 – SAP ECC Server. For which change groups have changes been recorded? Select the tab for component TT5-SAP ECC Server and choose Summary. Open the table below the diagram. A table is displayed that contains a list of all change groups. The change groups are Software Maintenance, Parameter, Transport Requests, SAP Notes, and Miscellaneous. If changes occurred for the different change groups, you can see the number of changes per day in the table.

9-3-4

Look at the main instance TT5 – SAP NW – Enterprise Portal. For which change groups have changes been recorded? Click on the tab for component TT5 – SAP NW – Enterprise Portal and choose Summary. Open the table below the diagram. A table is displayed that contains a list of all change groups. The change groups are Dispatcher, Server, Node Type Independent, and Miscellaneous. If changes occurred for the different change groups, you can see the number of changes per day in the table.

9-3-5

Which J2EE transport requests were imported into the TT5 – SAP NW – Enterprise Portal (check the Node Type Independent Configuration tab). Under TT5 – SAP NW – Enterprise Portal, choose Node Type Independent Configuration. Expand the J2EE-TRANSPORTS tree. You now see the number of J2EE transports. In the green line, click on the number. You will then see the detailed list of transport requests.

© SAP AG

E2E200

9-116

Solutions
Unit: Lesson: Change Diagnostics Configuration Validation

9-4

Execute the predefined Configuration Validation report for software validation. 9-4-1 Start the Configuration Validation Reporting application. Go to the Change Management work center and choose Configuration Validation Reporting. You should see a list of six predefined Configuration Validation reports. 9-4-2 Execute the first report: 0TPL_0SMD_COMPL_SW_START for SOFTWARE VALIDATION.

9-4-3

Enter the reference system TT4 0120003411 and the comparison system TT5 0120003411. Execute the comparison. Which store groups are compliant? Enter the systems and choose Execute. You will then see the result screen in a BW Web template. The store groups Operating System and Parameters are compliant.

9-4-4

Look in the details for the ABAP Parameters. How many parameters were compared? Select the ABAP Parameters tab. The Compliant Nr. of values is six. That means six parameters were compared and are equal in TT4 and TT5.

9-4-5

Display the compliant values in the result table. In the Navigation Block, click on the filter icon for the characteristic Compliance. Select the Filter values Yes and No.

9-5

Create a new target system. This will be used as a reference system for comparisons with physical systems. 9-5-1 Start the Configuration Validation Maintenance application. Go to the Change Management work center and choose Configuration Validation Maintenance. You should see the following menu:

© SAP AG

E2E200

9-117

9-5-2

Create a new target system. Choose the following stores from the source system TT4: • • • • ABAP_COMP_SPLEVEL ABAP_INSTANCE_PAHI ABAP_NOTES MSSQL_LEVEL

Choose Create from selected Stores. Enter the ID S## (where ## is your group number) for your target system. Choose Create Target System. In the Source System list, select source system TT4. If it does not appear automatically, choose Display all first. In the Select Config Stores area, select the four stores mentioned above. Choose Create from selected Stores. In the dialog box, enter the ID and a short description for your target system. Choose Save and Close. 9-6 Edit the target system. Only certain parameters of the selected config stores will be used for the comparison. 9-6-1 By default, all items of the selected config stores are included in your new target system. However, you only want to compare a limited set of parameters, which are listed below. Delete all other parameters. ABAP_COMP_SPLEVEL • ST-PI abap/heap_area_dia abap/heap_area_nondia abap/heap_area_total 0001286192 0001286678 SQLVERSION ABAP_INSTANCE_PAHI • • •

ABAP_NOTES • •

MSSQL_LEVEL • In the Target System Maintenance, choose Edit Target System.

© SAP AG

E2E200

9-118

In the Select Target Systems list, select the target system that you just created. If it does not appear on the list, choose Display all first. In the area Config Stores of Target System area, select the config store with the store name ABAP_COMP_SPLEVEL. The store content is now displayed in the lower area of the screen. Select the software component ST-PI, which will be included in the target system. To delete all other software components, you must now invert your selection by choosing , and then delete all selected lines by choosing Delete . Save your settings. In the Config Stores of Target System area, select the next config store with the store name ABAP_INSTANCE_PAHI and delete all parameters except for the three parameters mentioned above. Note: To find the required parameters more quickly, you can choose Filter . Use the wildcard * option in the filter criteria. Repeat the steps for the config stores ABAP_NOTES and MSSQL_LEVEL. 9-7 Create a new comparison list that includes the systems TT4 and TT5. These systems will later be compared with the reference system. 9-7-1 Create a new comparison list that comprises the systems TT4 and TT5. Name it SOL## (where ## is your group number). In the Target System Maintenance, choose Maintain Comparison Lists. Choose Create new. In the dialog box, enter the name of your comparison list and a short description. In the Select Source Systems area, select the systems TT4 and TT5 (both ABAP and Java stack). Choose Create and Close. 9-8 Execute the Configuration Validation report. 9-8-1 Execute the Configuration Validation report. Compare the values that are defined in your target system with the values of the systems TT4 and TT5 of your comparison list. Are the systems compliant? Go to the Change Management work center and choose Configuration Validation Reporting. In the next screen, expand the Reference system and comparison systems tray. Select your target system and your comparison list. In the lower part of the screen, choose a Configuration Validation report. Select the report 0TPL_0SMD_COMPL_REF_CONFSTORES. This report allows you to compare all parameters of a reference system.

© SAP AG

E2E200

9-119

Choose Start configuration validation reporting. On the next screen, you can control your settings. Choose Execute. On the next screen, the result is displayed. Both systems should be compliant. That is, they should have the same values as the reference system.

© SAP AG

E2E200

9-120

9-9

The BI User Interaction allows you to display the result in different views based on BI query navigation options. 9-9-1 The result table on the right-hand side shows the comparison systems TT4 and TT5, including the compared config stores, the config store items, and the item values. Include the reference system in this table, too. In the Navigation Block, click on the filter next to Compliance System and select the system roles Reference system and Comparison system. 9-9-2 Display only the values for system TT5 in the result table. In the result table, right-click on system TT5. In the context menu, choose Keep Filter Value. 9-9-3 Remove the values of the configuration items from the result table. In the result table, right-click on a configuration item value. In the context menu, choose Remove Drilldown.

© SAP AG

E2E200

9-121

© SAP AG

E2E200

9-122

Appendix
Unit: Example Certification Questions

In this exercise, you can test your knowledge on E2E Change Control Management. It contains one question for each unit. The questions are similar to the questions in the certification exam.

This exercise consists of questions and answers.

10-1

Introduction: What is the central group in the customer business unit that is responsible for the overall planning and implementation of changes in the solution landscape? Please choose the correct answer. Application Management. Global / Regional Business Process Champion Program Management Office

10-2

Software Change Strategies: What is an advantage of a pre-production system? Please choose the correct answer. Faster realization of business requirements. Isolated testing of the set of transports which will be imported into production next. Reduced effort for the development department.

© SAP AG

E2E200

10-1

10-3

CTS+: Which tasks can only be performed in the Transport Organizer Web UI but not in the ABAP Transport Organizer? More than one answer is correct. Decide whether each answer is true or false.

True

False Upload Non-ABAP archives into a transport request (e.g. in double stack systems) Create transport requests for a Non-ABAP system with a separate SID. Release transport requests that contain Non-ABAP archives (e.g. in double stack systems) Preselect a transport request as standard request.

10-4

Solution Documentation: Where can you find information about systems and software versions? Please choose the correct answer. Transaction SOLAR_PROJECT_ADMIN Transaction SMSY Transaction STMS

10-5

Quality Gate Management: Quality Gate Management groups transport requests into changes. Which transport requests can be grouped together in one change? Please choose the correct answer. Only transport requests from one development system. In double stack systems only transport requests from one stack. Transport requests from multiple development systems. Only transport requests from one development system. But in double stack systems transport requests for the ABAP and JAVA stack can be included.

© SAP AG

E2E200

10-2

10-6

Change Request Management: The critical object approval process is different in the change request management procedure compared to the transport management system (TMS) procedure. Which of the following statements are correct for the change request management procedure? More than one answer is correct. Decide whether each answer is true or false. True False Each project can have a different list of critical objects. The check is performed at the time of the import in the systems. The check is performed at the time of the export from the development system. Critical object check can be activated for Customizing table entries.

10-7

Maintenance Management: Which components should be updated during a Support Package Stack implementation? More than one answer is correct. Decide whether each answer is true or false. True False SAP Kernel SAP GUI In double stack installations: ABAP and JAVA stacks should be patched together If newer support packages or patches exist for single software components, they should be imported proactively after the SPS import

© SAP AG

E2E200

10-3

10-8

Test Management: When should a performance test be performed? Please choose the correct answer. In parallel to the functional tests. When the functional tests have been completed successfully Before the functional tests

10-9

Change Diagnostics: Where can the Configuration Validation application be started? Please choose the correct answer. Root Cause Analysis Workcenter Change Management Workcenter Transaction SOLMAN_CV

© SAP AG

E2E200

10-4

Solutions
Unit: Example Certification Questions

10-1

Introduction: What is the central group in the customer business unit that is responsible for the overall planning and implementation of changes in the solution landscape? Please choose the correct answer. O O X Application Management. Global / Regional Business Process Champion Program Management Office

10-2

Software Change Strategies: What is an advantage of a pre-production system? Please choose the correct answer. O X Faster realization of business requirements. Isolated testing of the set of transports which will be imported into production next. Reduced effort for the development department.

O

© SAP AG

E2E200

10-5

10-3

CTS+: Which tasks can only be performed in the Transport Organizer Web UI but not in the ABAP Transport Organizer? More than one answer is correct. Decide whether each answer is true or false. True O False X Upload Non-ABAP archives into a transport request (e.g. in double stack systems) Create transport requests for a Non-ABAP system with a separate SID. Release transport requests that contain Non-ABAP archives (e.g. in double stack systems) Preselect a transport request as standard request.

X

O

O

X

X

O

10-4

Solution Documentation: Where can you find information about systems and software versions? Please choose the correct answer. O X O Transaction SOLAR_PROJECT_ADMIN Transaction SMSY Transaction STMS

10-5

Quality Gate Management: Quality Gate Management groups transport requests into changes. Which transport requests can be grouped together in one change? Please choose the correct answer. O Only transport requests from one development system. In double stack systems only transport requests from one stack. Transport requests from multiple development systems. Only transport requests from one development system. But in double stack systems transport requests for the ABAP and JAVA stack can be included.

X O

© SAP AG

E2E200

10-6

10-6

Change Request Management: The critical object approval process is different in the change request management procedure compared to the transport management system (TMS) procedure. Which of the following statements are correct for the change request management procedure? More than one answer is correct. Decide whether each answer is true or false. True O False X Each project can have a different list of critical objects. The check is performed at the time of the import in the systems. The check is performed at the time of the export from the development system. Critical object check can be activated for Customizing table entries.

O

X

X

O

X

O

10-7

Maintenance Management: Which components should be updated during a Support Package Stack implementation? More than one answer is correct. Decide whether each answer is true or false. True X O X False O X O SAP Kernel SAP GUI In double stack installations: ABAP and JAVA stacks should be patched together If newer support packages or patches exist for single software components, they should be imported proactively after the SPS import

O

X

© SAP AG

E2E200

10-7

10-8

Test Management: When should a performance test be performed? Please choose the correct answer. O X O In parallel to the functional tests. When the functional tests have been completed successfully Before the functional tests

10-9

Change Diagnostics: Where can the Configuration Validation application be started? Please choose the correct answer. O X O Root Cause Analysis Workcenter Change Management Workcenter Transaction SOLMAN_CV

© SAP AG

E2E200

10-8

Sign up to vote on this title
UsefulNot useful