Anda di halaman 1dari 26

Change Request Management with Solution Manager 7.

2
TCS Smart Operations for SAP CoE, 2016

September, 2016
| Copyright 2015 Tata Consultancy Services Limited

Agenda

New Architecture and Infrastructure

ChaRM Administration Cockpit

Release and Requirement Management

Retrofit and Quality Gate Management

SAP SolMan 7.2 Upgrade path and Impact

Difference between SAP Solution Manager 7.1 and 7.2

New Architecture and Infrastructure

New Architecture in SAP Solution Manager 7.2

Infrastructure Change in SAP Solution Manager 7.2


Existing Infrastructure of Solution and Project is going to convert in Solution and Solution Branches
Logical Components are structured in Logical Component Groups
Different Projects are converted in branches of Solution.

SAP Solution Manager 7.2

Solution Branches and Logical Component Groups


Branched represent the version of Solution Documentation containing
processes, libraries and system.
Maintenance branch contain editable version of the productive
solution documentation
Production branch represents the productive version of the entire
solution documentation.

There is always one production and one


maintenance branch but based on customer
scenario multiple branches can be created.

Dual track landscape can be maintained under


single logical component group.
6

Administration Cockpit

Change Control Management Administration Cockpit

Central web based UI for ChaRM administration

Replacement of various outdated SAP GUI tcodes like


/tmwflow/reporting,/tmwflow/lockmon

Central Place for Import Scheduling, Transport analysis, Cross


System object lock, Critical Object

Change CTS switch for any landscape.

New web based Task list UI.

Enterprise search enabled.

Snapshot of Administration Cockpit

Search Scheduled
various
Landscape
Task
Transport
Critical
List
Solution
Imported
Operations
Objects
Overview
Analysis
related
Jobscontent

Release and Requirement


Management

Release Management
Challenges
No Release Schedule against each planned Change cycle
Maintain schedules in Excel or other formats
Efforts to maintain conflicts and dependency with different
releases
Solution
Maintain Minor and Major release.

Track dates against each release.


Avoid dependency and conflicts with other releases.

11

Change and Release Management Strategy

12

Release Management
Release & Deployment Management is essential to manage successful deployment of all related
changes into the productive environment.
Release Management defines dates and schedule for Releases.
Release content is determined by Projects, Requests for Changes, and related Change Documents.
The Release Cycle is a technical container and model for the release content.
Results in

Incident

Problem

Request for
Change

Handover to RfC in case of bug-fix

Business
Requirement

Relates to

IT
Requirement

Create(1:n)

Change
Document

Assign (n:1)

Release
IT
Project
Project Task

Process
Repository

Links to (1:1)

Release Management Strategy : Continues Deployment, Phase Driven Deployment, Release Management
13

Requirement Management

14

Retrofit and Quality Gate


Management

Backlog Transport Processing


After completion of Retrofit and Dual Track landscape setup, all the open and released TRs must be captured in CSOL table with the
help of Managed System setup under Change Control Management.
Retrofit data must be created for all released transports in production support track.

Create CSOL Entry

Create Retrofit Data

16

Standalone Retrofit and Quality Gate Management


How Does it Work
When Transport Request is released in maintenance development system, the BADI CTS_EXPORT_FEEDBACK triggers
the creation of Retrofit data in Solution Manager
When an object is saved in transport request in project landscape, the object has to be recorded in the cross system
object lock table.
How can it be configured
The retrofit parameter STANDALONE must be active.
The BADI CTS_EXPORT_FEEDBACK must be implemented.
The transport backlog must be executed as part of SOLMAN_SETUP wizard.
Retrofit can be started for all released transport request that belong to change.

17

Upgrade Path and Impact

SolMan 7.2 Upgrade Impacts on Existing SolMan Functionalities


Scenario

Impact

Details of Impact

Project Management

LOW

Project Management capabilities are similar between 7.1 and 7.2

IT Service Management

LOW

No disruption to 7.1 functionality, innovation can be adopted at own pace

Landscape Management

LOW

Simplification (Maintenance Planner can also be adopted without upgrade; more consistent handling of
landscape entities with removal of the product system)

Data Volume Management

LOW

No disruption to 7.1 functionality, innovation can be adopted at own pace

Application Operation

MEDIUM

No disruption to 7.1 functionality, significant renovation of user experience (UI5 instead of flash). No
architecture changes in Monitoring and Alerting infrastructure

Change Control Management

MEDIUM

Simplified landscape concept to be implemented (Logical component groups), included in content activation

Custom Code Management

MEDIUM

Complete redesign of technical infrastructure, migration wizard execution is required

Process Management

HIGH

Complete redesign of Solution Documentation, Content Activation required, additional innovation can be
adopted at own pace

Test Management

HIGH

Complete redesign of Solution Documentation and assigned test cases, Content Activation required, no
upgrade of existing Test Plans

Business Process Operation

HIGH

Complete redesign of Solution Documentation, Content Activation required, adoption of Monitoring and
Alerting infrastructure required
19

Upgrade Path
Content Activation has split in 2 Major Steps

Define Scope(Pre-Upgrade)
Select which Solar projects shall be considered for migration
Change Request Management Migration will consider only Projects with active Cycle and Task List

Content Activation(Post upgrade)


Adapt Number Ranges
Adapt IT Calendar Configuration
Check Readiness of ChaRM Content 1643013 - Dump SYNTAX_ERROR in SAPLCRM_CONDITION_COM_OW
Activate ChaRM Content

20

Automatic Content Activation and Manual Checklist


Change Request Management look for Change Control Landscape with corresponding landscape definitions for system landscape which
defined in solar project before.
If there are Change Control Landscapes, those will be reused else new Change Control Landscape will be created.
New Change Cycle for each SOLAR project which has active task list/ Change Cycles, It will be assigned to Change Control Scenarios and
Respective branches
Existing Tasks list will be reassigned to the newly created Change Cycles automatically.
All SMDV(Project Cycle) and SMMN(Maintenance Cycle with SAP Variant0) will be mapped to Phase Cycle(SMIM).
All SMMM(Maintenance Cycle with SAP Variant1) will be mapped to Continual Cycle(SMAI).
All Change cycles will be having same status as before.
After Completion of Change Cycle update, all open change transaction will be mapped from their solar projects to newly created
changes cycle automatically

Automatic Content Activation

CRM upgrade procedure need to be considered as new CRM Enhancement package is part of SAP Solution Manager 7.2 upgrade.
User Interface needs to be adjusted manually.
New fields has been introduced like change cycle which is replacement of Project and Solution field
BADI or Function and Methods which are dependent on Solar Project Environment needs to be manually checked and updated.
End User Education would be required for Change Manager, Administrator and Release Manager.

Checklist for Manual Steps after activation

21

Guidance for Configuration


All Change Control IMG activity now moved to SOLMAN_SETUP configuration wizard only.
New and revised Change Control Structure for Change Control Management, Quality Gate Management and Managed System setup
LMDB would be single source of truth for all landscape information and SMSY T-code will be no longer available with Solution Manager
7.2.
TMS related data can reset using Administration Cockpit
CTS data is directly synched from CTS domain controller to LMDB.

SAP Solution Manager 7.2 comes with SAP CRM 7.0 EHP3. Significantly lower impact than in 7.1 upgrade.
2331779 - How to Manage Change Requests and Change Documents which are not part of Migrated Projects in SAP Solution Manager
7.2

22

What will Change in ChaRM with SAP Solution Manager 7.2

23

Difference Between 7.1 and 7.2

Difference between SAP Solution Manager 7.1 and 7.2


Area

SAP Solution Manager 7.1

SAP Solution Manager 7.2

Cycle Type

Maintenance Cycle with SAP Variant0(SMMN)


Project Cycle(SMDV)
Maintenance Cycle with SAP Variant1(SMMM)

Continual Cycle(SMAI)
Phase Cycle(SMIM)
Release Cycle(SMRE)

ChaRM Reporting

/TMWFLOW/TRMO
/TMWFLOW/REPORTINGN
/TMWFLOW/PROJ
/TMWFLOW/LOCKMON
Not Available

Change Control Management Administration Cockpit

Requirement
Management

Business Requirement(SMBR) and IT Requirement(SMIR)

BW Based Reporting

Various distributed reporting

UI5 based reporting and improved infrastructure with administration


cockpit

Release Management

Not Available

Introduced with Major and Minor release concept

Retrofit

Retrofit can be performed with ChaRM

Standalone Retrofit, Backlog Transport processing and Retrofit with Quality


Gate Management

cCTS

Uneven landscape are not supported

Uneven landscape supported with cluster for UC

25

Thank You

Reach us at : EntSolSAPCoE SmartOps Grp

TCS Smart Operations for SAP CoE,


2016
| Copyright 2015 Tata Consultancy Services Limited

26

Anda mungkin juga menyukai