Adeyinka Olurin - Goal 3 - Change Request Management

Adeyinka Olurin
SAP Digital Business Services.
August 15, 2016.
Change Request Management with SAP Solution
Manager 7.2 (SP02)
Internal

© 2016 SAP SE or an SAP affiliate company. All rights reserved. 2Internal
Disclaimer
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of
SAP. Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or
any other service or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this
presentation or any related document, or to develop or release any functionality mentioned therein.
This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms
directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice.
The information in this presentation is not a commitment, promise or legal obligation to deliver any material, code or
functionality. This presentation is provided without a warranty of any kind, either express or implied, including but not limited to,
the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This presentation is for
informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in
this presentation, except if such damages were caused by SAP’s intentional or gross negligence.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially
from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only
as of their dates, and they should not be relied upon in making purchasing decisions.

Agenda
Change Request Management
 Business Requirement
 Change Cycle Types
 Change Documents
 Transport Management
 Release Management
 Content activation steps in ChaRM context.
Live DEMO
• Creating:
• Solution, Branches, Change Cycles (Phase Cycle, Continual Cycle)
• Request for Change
• Change Documents (Normal Change, Urgent Change)
• Transport Management (Transport Request, Transport Organizer, Task List)
• Release Planning
• Reporting

SAP’s Change Control Management Portfolio
Change Request
Management
Quality Gate
Management
Change and Transport
system (SAP / Non SAP)
Central Transport
Management
Retrofit Transport
Analytics /
Change
Diagnostics
Release
Management

Lifecycle based on Branches
Basics
DevelopmentMaintenance
Production
A Branch represents a version of the
solution documentation containing processes,
libraries, and systems.
The Maintenance Branch represents
the editable version of the productive
solution documentation. It provides an
safe environment for performing
changes.
The Production Branch represents the
productive version of the entire solution
documentation.
Further Branches e.g. to
deliver the future solution
documentation.

Lifecycle based on Branches – 2
Multiple Branches
DevelopmentMaintenance
Production
There is always a Production and a
Maintenance Branch but customers can
define as many additional Branches as
required.
The Branch setup should be driven by the
customers System (Transport) Tracks and
the planned customer Releases.
Branch
Branch Branch Branch
Planned
Innovations

Understand the transformation from 7.1 to 7.2
Logical
Component Group
Project
Solution
Existing Infrastructure 7.1 New Infrastructure 7.2
Logical Component
Logical Component
Logical
Component
Logical
Component
Logical
Component
Logical
Component
CheckIn/Out
Branches
Example “ERP”:

BranchesSystem Landscape
Introducing the Solution Landscape and its Components
Logical Component Development
Development
Development
DG3-100 QG3-100
Production
Log Comp Group ERP
Logical Component Production
Maintenance Production
DG1-100 QG1-100 PG1-100
Planned
Innovations

Solution Landscape:
Single Production System
Logical Component Development
Logical Component Production
Maintenance
Production
Development
Production system track
DG1-100 QG1-100 PG1-100
Development system track
DG3-100 QG3-100
Branches
(Solution documentation versions)
Logical Component (Group)
Architecture
System Landscape
(Customer system tracks)
Logical Component
Group ERP
Planned
Innovations

Landscape Views
3 System Landscape 4 System Landscape
Multiple Landscape
Maintenance Landscape
Implementation Landscape

Enhanced Cycle Switch with Task List Re-Use
Logical
Component Group
Logical Component
Logical Component
Branches
Task List
“Phase Cycle” Phase Cycle #1
Phase Cycle #2
Cycle
Switch
Task Lists will be re-used if Cycles are closed
to minimize the time for re-assignment activities

Task List Re-Use for Release Management
Logical
Component Group
Logical Component
Logical Component
Branches
Task List
“Minor Release”
Task List
“Major Release”
Minor Release
Cycles
Major Release
Cycles
Task Lists will be re-used for the same Release Track to
allow central transport tracking and administration

Example: Change Cycle for ERP System only
Branches
Logical
Component
Groups
Logical
Component
Change Control
Landscape
Get Logical Components Get Logical Component Groups
Change Cycle
for ERPBranch: Maintenance
Contains logical Components of
Maintenance Landcape
Change Control Landscape: ERP
Contains logical Component Group
for ERP
Already defined
Already defined Already defined
Already defined
Planned
Innovations

New Fiori User Interface

Administration Cockpit
 Central UI for Administrators
 Replaces several outdated SAP GUI
transactions
 Some Highlights
 One-Stop Shop for Admins
 Transport Analysis Features
 New Tasklist UI (Web Based!)
 Central Place for Import
Scheduling
 Enterprise Search enabled
Planned
Innovations

Administrator‘s Cockpit unites all key information in a central place
Transport
Overview
Landscape
Overview
Fulltext
Search
Task ListTrackingCSOL Data

Simplified Cycle Types in SAP Solution Manager 7.2
Maintenance Cycle (SMMN)
Maintenance Cycle (SMMM)
Project Cycle (SMMM)

Simplified Cycle Types in SAP Solution Manager 7.2
Continual Deployment Phase Driven Deployment Release Management
• Development and Imports may
happen either individually or
bundled (on demand / daily /
weekly)
• Deploy changes into
production at anytime
However:
- No phases, no gates!
• All changes and transports of
a cycle will be imported
together (Import All)
• Mostly relevant for Project or
Wave based transport and
change management
• Based on Release Planning
according to ITIL definition
• Defined Relationships and
dependencies between each
Release
• Import job for the entire
Release content
• Additionally, no risk changes
can be imported bundled

Normal Change Urgent Change Admin Change General Change Defect Correction
Change Documents
 Daily maintenance
 Implementation
Projects
 Depending on project
release-cycle
 Integrated with SAP
Transport
Management
 Emergency Changes
 Optimized for fast
processing
 Independent from
project release cycle
 Integrated with SAP
Transport
Management
 Documentation only
 Administrative
activities
 Related to system
landscape of change
project
 Not integrated in
SAP Transport
Management
 Changes on IT
Assets
– Mobile Devices
– Printer
– …
 Not mandatory
related to any
change project
 Used during test-
phase of
implementation or
maintenance projects
 Document test
defects and their
correction
 Integrated in SAP
Transport
Management

Change Request Management – User Roles
… categorizes, approves and monitors change requests.
… 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.
… takes care of software logistics.
… creates a service message or a change request directly.
… handles the service message and creates a change request.
Requestor
Service Desk
Employee
Change
Manager
Developer
Tester
IT Operator
Change
Advisory
Board

Request for Change Workflow

Urgent Change Workflow

Normal Change Workflow

User Interface and Usability Improvement
“Status Overview” assignment block
 Visualize the status scheme of your transactions.
New Search Criteria
Additional search criteria
New search criteria are mostly available for:
 Change Documents
 Change Cycles
 Requests for Change
 Urgent Changes
 Normal Changes

Scope Assignment Block
Document description for each scope item
Change manager approves or denies request
Scope Definition
Request Approval

Transport Management in Change Request Management
Task List Cross-System Object Locks

New and Revised Import Scheduling
 Scheduling has been improved to
cope with special customer situations
that require high import frequency
 Import Scheduling is now possible
with any timeframe!
 Users can re-use existing timeframes
or define periods from scratch
Planned
Innovations

Release 1.1 Release 1.2 Release 2.0Release 1.0
Minor Release 1.2
Release Management – Major and Minor Releases
Major Release 2.0
Minor Release 1.1 Minor Rel. 2.1
Urgent Changes
for Release 1.1
Urgent Changes
for Release 1.2
Urgent Changes
for Release 2.0
This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind,
either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement
Urgent Changes
for Release 1.0
Go-Live
Go-Live
Go-Live

Release Planning
First level
Second level
 Third level

The 3-Step Approach for Release Management in Solution Manager
Release Track
Definition
Manage Release CycleRelease Planning
Durations & Go-Live Date
Assign Change Documents &
Manage Release DeploymentSystem Landscape

Better Support for „Warning Mode“ of Downgrade Protection
New usability features for „Warning
Mode“ introduced which allow easier
processing of conflicts
In case of conflicts in warning mode,
the user gets a popup which contain
information about the conflicts for
instant processing.
The customizing possibilities of DGP
have also been revised and enhanced
to provide better support for various
customer use-cases.

Important to Know & Your Next Steps
Upgrade details
Relevant for all customers:
 No CRM issues this time: SAP Solution Manager 7.2 does not
contain a new SAP CRM release. We only move to a new
enhancement package, the impact of the 7.2 upgrade is
significantly lower than in the 7.1 upgrade
 If you already adopted the Monitoring & Alerting infrastructure,
then you are fine. Note that business process monitoring
based on the Monitoring and Alerting Infrastructure (MAI)
is mandatory in 7.2
 The split of ABAP and JAVA stacks, and the upgrade to SAP
NetWeaver 7.40 are performed automatically in a standard
upgrade procedure
 Activation of Solution Documentation can be prepared well in
advance of the upgrade
Optional upgrade step:
• The migration to SAP HANA fully supports the one-step-
upgrade approach (i.e. the SAP standard for migrating to SAP
HANA)
The upgrade from SAP Solution Manager 7.1 to 7.2 is standard
Planned
Innovations
This is the current state of planning and may be changed by SAP at any time.

The Upgrade Road to Success – SAP Solution Manager general
For SAP Solution Manager customers we plan to offer
 quick identification of those parts of your solution documentation which matter to you
 decision support to plan and execute content activation
 best practices, services, and tools for the upgrade to SAP Solution Manager 7.2
Start preparing Select what’s right Know the impact
Your journey starts today!
Planned
Innovations
This is the current state of planning and may be changed by SAP at any time.

Going to SAP Solution Manager 7.2 – Required Post-Upgrade Work
Automatic Steps
 As part of the Content Activation data persistency is managed automatically
 New Change Cycles will automatically be created and replace existing (unfinished) Change
Cycles
 All references are automatically updated and refreshed
Manual Steps
 Update and Check of existing Custom Implementations: Interfaces to Solar-Environment
 Update of customer specific User Interface Configuration required; Replace former
Project/Solution fields with new delivered attributes, or copy the SAP standard User Interface
Configuration again to customer specific User Interface Configuration and adjust manually.
 End-User Education – mostly for Change Managers, Administrators and Release Managers

Solution Manager 7.2 Content Activation
Content Activation is split in two
major steps:
Step 1: Define Scope (pre-upgrade)
Step 2: Content Activation (post-upgrade)
In Step 1 customers select which SOLAR-
Projects shall be considered for the
migration
Change Request Management
migration can consider ONLY projects
with active Cycles and Task Lists

The ChaRM specific Content Activation
Guided Procedure for Change Request
Management contains 4 Basic Steps:
 Adapt Number Ranges
 Adapt IT Calendar Configuration
 Check Activation Readiness
 Start Content Activation Job
All steps will be executed
automatically!

Detailed Content Activation Steps in the context of ChaRM
Match
Landscape
of Projects
Create
Change
Control
Land-
scape
Create
Cycles
Re-
Assign
Task
Lists
Cycle
Mapping
Re-
Assign
Trans-
actions
Update
Referen-
ces (opt.)
Done

What happens during the automatic content activation?
1. As part of the content activation, Change Request Management will look for Change
Control Landscapes with corresponding landscape definitions to the system landscape
which was defined in the Solar-Project before.
2. If there are Change Control Landscapes, those will be re-used – otherwise new Change
Control Landscapes will be created.
3. The job will then create new Change Cycle documents for each selected Solar-Project
which has active task lists / Change Cycles. Those will be assigned to the Change Control
Scenarios and respective Branches.
4. The existing task lists will be re-assigned to the newly created Change Cycles
automatically.

What happens during the automatic content activation?
5. All SMDV and SMMN will be mapped to a “Phase Cycle”. All SMMM will be mapped to a
“Continual Cycle”. Each Change Cycle will then get the same status as before.
6. After the Cycles have been updated, all open change transactions (Request for Change +
Change Documents) will be re-assigned from their former Solar-Project assignment to the
newly created Change-Cycles automatically.
7. Optional, only in case applicable: Existing references to Processes, Steps or Scenarios in
Solutions or Projects will also be automatically updated to the new entity in the related
Branch.
8. At this point, technically the content activation is already over. However, please be aware of
additional manual activities, which have to be checked.

Live DEMO
• Creating:
• Solution, Branches, Change Cycles (Phase Cycle, Continual Cycle)
• Request for Change (Using Continual Cycle)
• Change Documents (Normal Change – with Major Release, Urgent Change)
• Transport Request and Task List
• Release Planning
• Reporting
Internal

Thank you
Contact information:
Adeyinka Olurin
SAP GSS
adeyinka.olurin@sap.com

Adeyinka Olurin - Goal 3 - Change Request Management

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (18)

En vedette

En vedette (7)

Similaire à Adeyinka Olurin - Goal 3 - Change Request Management

Similaire à Adeyinka Olurin - Goal 3 - Change Request Management (20)

Adeyinka Olurin - Goal 3 - Change Request Management