2
TCS Smart Operations for SAP CoE, 2016
September, 2016
| Copyright 2015 Tata Consultancy Services Limited
Agenda
Administration Cockpit
Search Scheduled
various
Landscape
Task
Transport
Critical
List
Solution
Imported
Operations
Objects
Overview
Analysis
related
Jobscontent
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.
11
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
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
16
17
Impact
Details of Impact
Project Management
LOW
IT Service Management
LOW
Landscape Management
LOW
Simplification (Maintenance Planner can also be adopted without upgrade; more consistent handling of
landscape entities with removal of the product system)
LOW
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
MEDIUM
Simplified landscape concept to be implemented (Logical component groups), included in content activation
MEDIUM
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
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
20
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.
21
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
23
Cycle Type
Continual Cycle(SMAI)
Phase Cycle(SMIM)
Release Cycle(SMRE)
ChaRM Reporting
/TMWFLOW/TRMO
/TMWFLOW/REPORTINGN
/TMWFLOW/PROJ
/TMWFLOW/LOCKMON
Not Available
Requirement
Management
BW Based Reporting
Release Management
Not Available
Retrofit
cCTS
25
Thank You
26