Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Release
Management
Change Request
Management
Quality Gate
Management
Central Transport
Management
Retrofit Transport
Analytics /
Change and Transport Change
system (SAP / Non SAP) Diagnostics
Basics
The Production Branch represents the
productive version of the entire solution
Production documentation.
Maintenance Development
Multiple Branches
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
Maintenance Development Branch
customers System (Transport) Tracks and
the planned customer Releases.
Logical Component
Branches
Check In / Out
Project
Logical Logical
Component Component Logical
Component Group
Logical Component
Example ERP:
Solution
Logical Logical
Component Component
Production
Maintenance Production
Logical Component Production
Development
DG3-100 QG3-100
Complete Landscape
Definition
Solution (all LCGs incl. all LCs)
+ filter
Landscape
Logical
Component
Subset for
Variant Selection
(only particular LCs)
Branches
+ filter
Logical
Component Group
Stencil for
Deployment Control
& Release Tracks
Change Control (only particular LCGs)
Landscape
Innovation (Sandbox)
Landscape-Type Vector
SRM
Rollout / Local Systems
CRM
Development (n+1)
ERP
HANA
BW
Production / Maintenance
Logical Logical
Component Component
Groups
Administration Cockpit
Some Highlights
One-Stop Shop for Admins
Transport Analysis Features
New Tasklist UI (Web Based!)
Central Place for Import
Scheduling
Enterprise Search enabled
Uneven Landscapes
Uneven landscapes
EPD EPQ EPP
Non- Non- Non-
are fully supported in
ABAP ABAP ABAP 7.2
Empty imports are
BWD BWQ BWR BWP done in uneven
ABAP
clusters for UC
ABAP ABAP ABAP
transports
Landscape Flexibility
Project Flexibility
Project 1
Miscellaneous
Improved Cycle Switch Performance (when closing and re-creating a new Cycle)
Easy access to
predefined Drilldowns
Development and Imports may All changes and transports of a Based on Release Planning
happen either individually or cycle will be imported together according to ITIL definition
bundled (on demand / daily / (Import All) Defined Relationships and
weekly) Mostly relevant for Project or dependencies between each
However: Wave based transport and Release
- No phases, no gates! change management Import job for the entire Release
content
Additionally, no risk changes can
be imported bundled
Task List
Phase Cycle Phase Cycle #1
Logical Component
Cycle
Branches
Switch
Logical
Component Group
Logical Component
Phase Cycle #2
Task List
Minor Release
Logical Component Minor Release
Cycles
Branches
Logical
Component Group
Task List
Logical Component
Major Release
Major Release
Cycles
Transport
Request for
IT Requirement
Change
Process
Maintenance
Release Cycle
Process Step
Release Change
DEV
Changes
1
Maintenance
1
Logical Component
Group ERP
Production
Logical Component Production
Development
DG3-100 QG3-100
Upgrade details
2015 SAP AG or an SAP affiliate company. All rights reserved. This is the current state of planning and may be changed by SAP at any time. Public 46
Content Activation Overview: Recommended procedure
SAP recommends to prepare the Content Activation on your up-and-running SAP Solution Manager 7.1
system. This can be done at any point in time and does not affect your productive environment in any way.
After the preparation, the technical upgrade to release 7.2 is followed by post-processing Content Activation
activities in SAP Solution Manager 7.2.
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
Due to the fact that a new CRM Enhancement Package is part of the upcoming SAP Solution
Manager Release, typical CRM upgrade procedures need to be taken into account:
Create
Re- Re-
Match Change Update
Create Assign Cycle Assign
Landscape Control Referen- Done
Cycles Task Mapping Trans-
of Projects Land- ces (opt.)
Lists actions
scape
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.
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.
8. At this point, technically the content activation is already over. However, please be aware of
additional manual activities, which have to be checked.
Release
Management
Change Request
Management
Quality Gate
Management
Change
Control
Central Transport
Management
Transparency
2015 SAP AG or an SAP affiliate company. All rights reserved. Public 56
More information needed? @SAPITSM
Link: http://wiki.sdn.sap.com/wiki/display/SAPITSM