ChaRM Overview

SAP Solution Managers Change Request Management Functionality
Overview Creating Projects and Cycles Utilizing ChaRM Transaction Types Common Challenges and Solutions
Applying Advanced Topologies (Best Practices) Wrap-up
E2E Change Deployment Typical Questions
How to change ABAP & Java components synchronous ? Did we record automatically application changes ?
Did we import all changes successfully ?
Is there ONE place to manage the software logistics ?
How to manage heterogenous development environments ?
SAP AG 2007, 3
SAP E2E Standards for Solution Operation Cover All Operations Processes
Example: Process standards Change Request Management and Change Control Management
Champs
Request Business Change *
PMO
Application Mgmt
Technical Operations
Implement Change Monitor Change
Test Change
Deploy Change
Available Information:
White Papers Detailed technical description
Training Certifications
SAP AG 2007, 4
Sign-Off Change
* Business Changes = Request Adaptation or Request Project
Story Line: Change Request Management

Effective application management is key for companies to stay ahead of the competition SAPs scope of application management includes all types of application changes:
Business process changes, implementation and upgrade projects Periodic maintenance
Emergency corrections
Change Request Management strengthens the strategy of SAP Solution Manager as SAPs standard application management platform which:
Ensures reliability
Reduces total cost of ownership and increases total solution value Bridges the gap between business requirements and IT
administration
Helps meet audit/Sarbanes-Oxley (SOX) compliance requirements
SAP AG 2007, 5
The Three Tiers of Change Request Management

SAP Solution Manager
Change Admin
Management of all
Project Management
Project planning
Change Logistics
Customizing and
change requests
Change request
and budgeting
Project
development (Realization)
Test execution Seamless
categorization
Change
documentation
Customizing and
documentation
Approval
development (Specifications)
Test management
integration into TMS

Transport
workflow
Status reporting
scheduling
Transport
Complete change
tracking
history
SAP AG 2007, 6
Change Request Management Roles in a Nutshell
Requestor
creates an Service Message or a Change Request directly.
Service Desk handles the Service Message and creates a Change Request. Employee Change Manager Change Advisory Board Developer
categorizes, approves and monitors Change Requests.
is the Steering Committee in the Change Management process. implements a change and hands over to the Tester.
Tester
tests a change, sets status in the Change Document.
IT Operator
takes care of software logistics.
SAP AG 2007, 7
Overview Creating Projects and Cycles Utilizing ChaRM Transaction Types Common Challenges
Applying Advanced Topologies (Best Practices) Planned Outlook and Wrap-up
Release Management with Change Request Management

Release Management refers to packaging and coordinating changes into releases for deployment SAP Solution Manager projects can be extended by adding project cycles, which control project phases Project phases determine whether transport requests can be or cannot 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 phase-specific projects
SAP AG 2007, 9
Solution Manager Can Manage Parallel Implementation and Maintenance Projects

SAP Solution Manager Change Request Management
Development
Test
Production
Implementation Project Market Campaign Implementation Reorg Finance
Maintenance Project Finance and Customer Relation

Maintenance Cycles Urgent Corrections
SAP AG 2007, 10
General Project Administration
Transaction SOLAR_PROJECT_ADMIN
General project administration functions: Create projects Change projects Display projects Delete projects Transport projects Access project templates
SAP AG 2007, 11
SAP Solution Manager Projects and Project Cycles
cProject
SAP Solution Manager Project
Project Cycle
Development phase (without or with release) Test phase
Emergency correction phase
Go-live phase
SAP AG 2007, 12
Project Cycle
SAP AG 2007, 13
Using Cycle Task List General Functions

Task lists allow scheduling and monitoring batch processing:
Daily imports
Parallel imports into multiple systems (ECC, CRM, BW, )
Cycle Task List

General Tasks
Track1 of Project
Source Systems
. . .
Target Systems
Monitor task logs

Insert additional tasks Add notes and documents
. . .
Production Systems
. . .
Send mail Change layout

Print task list
Single Systems
. . .
Post-Processing Systems
Track2 of Project
General Final Tasks
SAP AG 2007, 14
Task Lists
Central navigation to and monitoring of the relevant systems and functionality
SAP AG 2007, 15
Change Request Management Cycle Management

Cycle Transaction
Change Manager
PRD
Controlled transports
Project Cycle QAS
Cycle Task List
DEV
SAP AG 2007, 16
Phase Shift in Change Request Management
SAP AG 2007, 17
Consistent Regular Corrections in a Project Cycle
Project buffer
Project buffer
DEV
QAS
PRD
Legend:
Regular Corrections Test Transports (Transport of Copies)
SAP AG 2007, 18
Release Management with Change Request Management

Project cycle transaction
Project cycle task list
Physical (development) systems
Logical systems (clients) Transport Request

CTS project
IMG project
cProjects
CTS project
CTS project
...
SAP Solution Manager project IMG project
CTS project
Project created in cProjects
CTS project
CTS project
...
SAP AG 2007, 19
...
Advantages of Release Deliveries and Parallel Projects Advantages of Release Deliveries:

Common regression testing for several projects at once Changes in production only at certain points in times No crossreference dependencies with other projects
Higher stability in production
Advantages of Parallel Projects:

No wait times for release deliveries Individual project duration of each project is possible
Faster realization by individual timing of each project
SAP AG 2007, 20
Sample Change Transaction with Audit Trail in Change Request Management
John Doe
John Doe
SAP AG 2007, 22
Change Document Text, Audit Trail Part 1
SAP AG 2007, 23
SAP AG 2007, 24
SAP AG 2007, 25
Harmonizing Maintenance Activities

cProject SAP Solution Manager Project (Maintenance Project)
Maintenance Cycle
Development (without or with release)
Test
Emergency Correction
Harmonization
Harmonization
Go-Live
Harmonization
Regular Corrections
Test messages (during integration test)
Urgent Corrections (independent of Maintenance Cycle)
SAP AG 2007, 26

cProject
SAP Solution Manager Project (Maintenance Project)
Maintenance Cycle
Development (with or without release)
Harmonization
Test
Harmonization Harmonization
Go-Live
Regular Corrections
Urgent Corrections (independent of Maintenance Cycle)
SAP AG 2007, 27

cProject
Maintenance Cycle
Development (without or with release)
Test
Go-Live
Harmonization
Regular Corrections
Urgent Corrections (independent of MC)
SAP AG 2007, 28
Change Request Management Regular Correction

Feedback
Service Desk Employee
Service Message
Requester
Change Request
Developer
Change Manager
PRD
Tester
Change Document
Maintenance Cycle QAS
IT Operator
DEV
SAP AG 2007, 29
Consistent Regular Corrections in a Project Cycle
Import buffer
Import buffer
DEV
QAS
PRD
Legend:
Regular Corrections Test Transports (Transport of Copies)
SAP AG 2007, 30

cProject
Maintenance Cycle
Development (without or with release) Test
Go-Live
Regular Corrections
SAP AG 2007, 31
Change Request Management Urgent Correction

Feedback
Service Message
Requester
Change Request
Developer
Change Manager
PRD
Tester
Change Document
Task List
QAS
IT Operator
Maintenance Cycle
DEV
SAP AG 2007, 32
Consistency of Urgent Corrections and Maintenance Activities

Legend:
Urgent corrections are transported individually, and thus have no dependency on other corrections.
Maintenance Activities Urgent Correction Consolidated Transport
Transport buffer
Transport buffer
DEV
QAS
PRD
Urgent corrections are imported by the import subset transport method, 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.
SAP AG 2007, 33
Differences Between Urgent and Normal Corrections
SAP AG 2007, 34

cProject
Maintenance Cycle
Development (without or with release) Test
Go-Live
Harmonization
Regular Corrections
SAP AG 2007, 35
Change Request Management Test Message

Cycle Transaction
Developer
Change Manager
PRD
Tester
Test Message
Cycle Tasklist
QAS
Project Phases DEV
SAP AG 2007, 36
Harmonizing Project Activities

cProject
SAP Solution Manager Project (All Projects)
Project Cycle
Development without release
Development with release
Harmonization
Test
Go-Live
Harmonization
Harmonization
Normal Corrections
Administration Message
SAP AG 2007, 37
Change Request Management Administration Message

Feedback
Service Message
Requester
Change Request
Change Manager
PRD
Admin Message
Cycle Tasklist
QAS
IT Operator
Project Phases
DEV
SAP AG 2007, 38
Typical Questions to Be Answered by ChaRM Reporting

Which change requests are in process/completed? By status, type, next steps, maintenance window How long do change requests take to be completed? Per organization, user, type, step Which transports belong to which change request and vice versa? What is the current transport status (in which system)? How many incidents triggered a change request? Per organization, SAP component How many change requests were rejected? Per organization, user, type, by whom and why
How many corrections were withdrawn? Per organization, user, type, by whom and why
SAP AG 2007, 40
Change Request Management Reporting: Access I
Three points of access:

Transaction DSWP (solution-specific reporting) Transaction SOLAR_EVAL (cross-solution reporting) Transaction /TMWFLOW/REPORTING (cross-solution reporting)
SAP AG 2007, 41
Change Request Management Reporting: Access II
Transaction DSWP (solution-specific reporting)
Choose Execute.
SAP AG 2007, 42
Change Request Management Reporting: Access III
Transaction SOLAR_EVAL (cross-solution reporting)
Solution -> Change Management
SAP AG 2007, 43
Change Request Management Reporting: Access IV
Transaction /TMWFLOW/REPORTING (cross-solution reporting)
Final selection screen displayed from all three points of access
SAP AG 2007, 44
Change Request Management Reporting: Results Example Results of previous query Header, project, task list, and transport data about the selected transaction is displayed
SAP AG 2007, 45
Change Tracking in SAP Solution Manager
SAP AG 2007, 46
Transport Management Transition Approach 1

Cycle Transaction
PRD
Project Cycle QAS
Cycle Task List IT Operator
DEV
SAP AG 2007, 48
Transition Extension: Change Document

PRD Developer
Tester
Change Document
Task List
QAS
IT Operator
Project Cycle
DEV
SAP AG 2007, 49
Transition Extension: Approval Process

Requester
Change Request
Developer
Change Manager
PRD
Tester
Change Document
Task List
QAS
IT Operator
Project Cycle
DEV
SAP AG 2007, 50
Transition Extension: Service Desk

Feedback
Service Message
Requester
Change Request
Developer
Change Manager
PRD
Tester
Change Document
Task List
QAS
IT Operator
Project Cycle
DEV
SAP AG 2007, 51
SAPs End-to-End (E2E) Solution Operations
SAPs End-to-End Solution Operations supports SAP customers in managing and supporting their mission-critical operations
SAP E2E Solution Operations provides:
Know-how Methods Best practices
Tools
Training
SAP E2E Solution Operations is based on industry best practices and lessons learned
SAP AG 2007, 53
Tips for Those Getting Started with Solution Manger

Very detailed, well-prepared, free-of-charge documents (~80 documents and SAP Tutor lessons): These can be found at http://service.sap.com/rkt-solman (requires login credentials to the SAP Service Marketplace)
SAP AG 2007, 54
Your Turn!
Q&A
SAP AG 2007, 55

ChaRM Overview

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ChaRM Overview

Uploaded by

Copyright:

Available Formats

SAP Solution Managers Change Request Management Functionality

E2E Change Deployment Typical Questions

Is there ONE place to manage the software logistics ?

How to manage heterogenous development environments ?

Implement Change Monitor Change

* Business Changes = Request Adaptation or Request Project

Story Line: Change Request Management

The Three Tiers of Change Request Management

integration into TMS

Change Request Management Roles in a Nutshell

creates an Service Message or a Change Request directly.

categorizes, approves and monitors Change Requests.

tests a change, sets status in the Change Document.

takes care of software logistics.

Release Management with Change Request Management

Solution Manager Can Manage Parallel Implementation and Maintenance Projects

Implementation Project Market Campaign Implementation Reorg Finance

Maintenance Project Finance and Customer Relation

General Project Administration

SAP Solution Manager Projects and Project Cycles

SAP Solution Manager Project

Emergency correction phase

Using Cycle Task List General Functions

Cycle Task List

Monitor task logs

Send mail Change layout

General Final Tasks

Central navigation to and monitoring of the relevant systems and functionality

Change Request Management Cycle Management

Project Cycle QAS

Cycle Task List

Phase Shift in Change Request Management

Consistent Regular Corrections in a Project Cycle

Release Management with Change Request Management

Project cycle transaction

Project cycle task list

Physical (development) systems

Logical systems (clients) Transport Request

Project created in cProjects

Advantages of Release Deliveries and Parallel Projects Advantages of Release Deliveries:

Higher stability in production

Advantages of Parallel Projects:

Faster realization by individual timing of each project

Sample Change Transaction with Audit Trail in Change Request Management

Change Document Text, Audit Trail Part 1

Change Document Text, Audit Trail Part 2

Change Document Text, Audit Trail Part 3

Harmonizing Maintenance Activities

Test messages (during integration test)

Urgent Corrections (independent of Maintenance Cycle)

Harmonizing Maintenance Activities

Test messages (during integration test)

Urgent Corrections (independent of Maintenance Cycle)

Harmonizing Maintenance Activities

Test messages (during integration test)

Urgent Corrections (independent of MC)

Change Request Management Regular Correction

Service Desk Employee

Maintenance Cycle QAS

Consistent Regular Corrections in a Project Cycle

Harmonizing Maintenance Activities

Test messages (during integration test)

Urgent Corrections (independent of MC)