Beruflich Dokumente
Kultur Dokumente
PUBLIC
Table of Contents
Preface ................................................................................................................................................ 5
How SAP can Support........................................................................................................................ 10
1. Discover ..................................................................................................................................... 14
Strategic Planning............................................................................................................... 15
Trial System Provisioning.................................................................................................... 27
2. Prepare Phase ........................................................................................................................... 30
Project Initiation .................................................................................................................. 32
Establish Project Governance ............................................................................................. 35
Plan Project ........................................................................................................................ 36
Project Kick-off and On-Boarding ........................................................................................ 38
Project Team Enablement ................................................................................................... 40
Project Standards & Infrastructure....................................................................................... 43
Prototyping ......................................................................................................................... 49
Transition Planning ............................................................................................................. 51
Transition Preparation......................................................................................................... 67
Custom Code Cleanup and Improve................................................................................ 69
Project Delivery Platform Setup ....................................................................................... 71
2.12. Execution, Monitoring, and Controlling of Results ............................................................ 74
2.13. Organizational Change Management Roadmap .............................................................. 75
2.14. Phase Closure and Sign-Off phase Deliverables ............................................................. 75
3. Explore Phase ............................................................................................................................ 77
Phase Initiation ................................................................................................................... 79
Execution, Monitoring, and Controlling Results.................................................................... 79
Planning ............................................................................................................................. 81
Learning Design.................................................................................................................. 82
Organizational Change Management (OCM) ....................................................................... 84
Prep Steps and Data Model Adjustment .............................................................................. 85
Data Volume Planning ........................................................................................................ 93
Data Volume Design ........................................................................................................... 95
Security Design................................................................................................................... 96
Analytics Design ............................................................................................................. 97
Custom Code Impact Analysis......................................................................................... 98
Test Planning ................................................................................................................ 100
Sandbox System Setup ................................................................................................. 103
Data Migration Design for Remote Conversion .............................................................. 104
DEV Setup .................................................................................................................... 107
Sizing............................................................................................................................ 109
Technical Architecture Definition ................................................................................... 111
IT Infrastructure Definition ............................................................................................. 114
Technical Design .......................................................................................................... 117
Operations Impact Evaluation ....................................................................................... 122
Release and Sprint Plan................................................................................................ 126
Change Impact Analysis................................................................................................ 129
Phase Closure and Sign-Off phase Deliverables ........................................................... 129
4. Realize Phase .......................................................................................................................... 132
Phase Initiation ................................................................................................................. 134
Plan Realize Phase........................................................................................................... 134
Sprint Initiation (Iterative) .................................................................................................. 135
Execution Plan for Realize Phase ..................................................................................... 135
Sprint Closing ................................................................................................................... 136
Learning Realization ......................................................................................................... 137
Configuration .................................................................................................................... 140
Data/Object Transformation for In-place Conversion ......................................................... 141
Cleanup/Archive ............................................................................................................... 147
Data Tiering .................................................................................................................. 147
Integration Validation .................................................................................................... 151
Analytics Configuration.................................................................................................. 155
Custom Code Management Execution .......................................................................... 159
Test Preparation ........................................................................................................... 160
Test Execution .............................................................................................................. 161
QAS Setup.................................................................................................................... 164
Object/Data Migration & Verification for Remote Conversion ......................................... 164
Cutover Preparation ...................................................................................................... 169
Sizing & Scalability Verification...................................................................................... 173
IT Infrastructure Setup and Test .................................................................................... 175
Operations Implementation ........................................................................................... 180
Execution, Monitoring and Controlling Results ............................................................... 188
OCM Alignment Activities .............................................................................................. 193
Phase Closure and Sign-Off phase Deliverables ........................................................... 193
5. Deploy Phase ........................................................................................................................... 196
Phase Initiation ................................................................................................................. 198
Learning Realization ......................................................................................................... 198
Integration Validation ........................................................................................................ 201
Dress Rehearsal ............................................................................................................... 202
IT Infrastructure Service Finalization ................................................................................. 202
Operations Readiness....................................................................................................... 204
Execution, Monitoring and Controlling Results................................................................... 205
Release Closing................................................................................................................ 206
Production Cutover ........................................................................................................... 207
Post Go-Live Enduser Training...................................................................................... 210
Production Support after Go-Live .................................................................................. 210
Hyper Care Support ...................................................................................................... 211
Handover to Support Organization ................................................................................ 214
Project Closure and Sign-Off Project Deliverables ......................................................... 216
QG5 – Transition to Support Organization ..................................................................... 218
6. Run Phase ............................................................................................................................... 220
Operate Solution ............................................................................................................... 221
Improve and Innovate Solution .......................................................................................... 224
Preface
The Transition Road map for SAP BW/4HANA supports customers and the project team with descriptions
of all phases and activities in the transition project, and accelerators providing links to guides and
documentation, and listing the SAP service offering to support the transition to SAP BW/4HANA. The
Transition Road map to SAP BW/4HANA describes the different paths the customer can take to transition
his SAP BW system to SAP BW/4HANA.
The Transition to SAP BW/4HANA road map follows the SAP Activate methodology framework, the same
way as the Transition to SAP S/4HANA road map. They both use the same phases, activities and tasks
wherever possible to help users work with the content without significant re-learning effort.
This road map describes SAP BW/4HANA implementations on-premise only. SAP offers dedicated road
maps for cloud implementation projects (see accelerator section at the end of this chapter).
The structure of this road map is release independent. Release specific information is given explicitly
where a certain activity or task is required for a dedicated release.
• Path 1: New implementation: For those who would like to implement a new SAP BW/4HANA
system by either migrating a legacy system or by running a net-new installation of SAP BW/4HANA.
• Path 2: System conversion: For those who want to run a conversion of an existing SAP Business
Warehouse system to SAP BW/4HANA. There are three types available for this scenario:
▪ In-Place Conversion
▪ Remote Conversion with parallel operations
▪ Shell Conversion
For the in-place conversion and the remote conversion, classic BW objects (e.g. InfoCubes,
classic DSO, BEx Report) need to be migrated to the related new HANA-optimized object type.
If your current SAP landscape has been highly maintained (SAP BW powered by SAP HANA and
mainly usage of new HANA-optimized BW object types), you most likely can convert to SAP
BW/4HANA in just a few steps.
For the shell conversion, neither master nor transaction data are transferred. Data models and flows
are transferred to target SAP BW/4HANA system using transports.
• Path 3: Landscape transformation: For those who would like to consolidate their existing data
warehouse landscape or carve out selected data models or flows into an existing SAP BW/4HANA
system. Landscape transformation including a selective data migration, which could be conducted
within a customer-specific project with SAP.
In the road map all three transition paths are covered, however the focus is on path 1 and the different
types of path 2. Path 3 is by far the most complicated one and can only partially be standardized.
The “Transition to SAP BW/4HANA” implementation road map is structured in project phases (x-axis) and
work streams (y-axis). Each box represents an activity which should be executed in the project as part of a
certain work stream, and within a certain project phase. The position of the activities in the roadmap
picture and in the roadmap description only give a rough indication of a timely order!
Figure Preface 2: Explanation of Road map structure
The “Transition to SAP BW/4HANA” road map is structured into the following work streams (groups of
semantically related activities):
• Project management – The project management team performs common project and quality
management tasks, including project planning. The Technical Quality Manager (TQM) from SAP is
part of this work stream and works closely together with the project manager (from your company,
or the implementation partner, or both). In addition this work stream includes organizational change
management (OCM), and the enablement of the project team.
• Application: Solution adoption – This work stream covers the creation of the training strategy
and the learning paths, and the enablement of the end users to be ready for optimal use of the new
SAP BW/4HANA solution.
• Application: Design and configuration – In this work stream the classic BW models are converted
to HANA-optimized data models and flows as prerequisite for BW/4HANA. If you do a new
implementation, you immediately start with new data models with HANA-optimized objects and then
load or migrate relevant data from the source systems.
• Custom code extensions – Your code may need adjusting to function properly with SAP
BW/4HANA. You first clean up unused custom code, then identify affected custom code, e.g. in
transformations or user exits, and finally plan and execute the necessary adjustments. You can also
leverage the full power of SAP HANA by an optimization of your ABAP custom code for SAP HANA
in parallel to SAP’s optimizations within SAP BW/4HANA by using new process types, such as HAP
(HANA Analysis Process) or HANA-optimized transformations.
• Application: Testing – This work stream covers test planning and execution (integration,
regression, user acceptance).
• Analytics: This work stream covers the Analytics Design which takes care for the detailed analytics
architecture, the detailed transition project plan, and creation of a blueprint.
• System and data migration – Here you plan the implementation of all SAP BW/4HANA systems
(sandbox systems, support non-production system such as maintenance development and test
system). Depending on the scenario, this may include migrating from SAP BW on any database to
BW edition for SAP HANA and then upgrading to SAP BW/4HANA.
• Technical architecture and infrastructure – SAP BW/4HANA has SAP HANA as the underlying
database. The introduction of SAP HANA (single or scale-out) into your data center must be properly
planned based on your business and IT requirements. You may also include connectivity to SAP
HANA Cloud Platform for integration or extension use cases.
• Transition to operations – IT operational procedures and tools need to be adjusted before going
live to help ensure safe operations. IT support experts need to be trained as well.
Time wise, the SAP BW/4HANA road map is structured into six project phases. The phase names are
according to SAP’s implementation methodology SAP Activate (see accelerators section):
The road map is first of all a structured documentation for customers. An “always up-to-date” version of
this road map is available to all customers in the SAP road map viewer in the Hana Cloud Platform HCP –
see accelerator section for a link. From the Solution Specific Roadmaps, select “SAP BW/4HANA”.
The “Transition to SAP BW/4HANA” implementation road map is a superset of activities covering all
implementation scenarios. Some activities and tasks have been grouped to make reading more
convenient. The road map contains many accelerators helping you to execute a certain activity or task.
Accelerators may link to resources which require either upfront registration (e.g. SAPs online learning
platform OpenSAP), or require a certain support status. For instance, the access to documents and
trainings in the SAP Enterprise Support Academy requires SAP Enterprise Support status.
Once you have opened the road map Content tab in the Road Map Viewer, you should filter for your
scenario to hide all activities and tasks which are not relevant to you. The following scenarios are
available:
• New Implementation
• In-Place Conversion
• Remote Conversion
• Shell Conversion
To select, open the Content page and scroll down to the More section, in the left structure pane and
select the scenario in scope.
SAP intends to update this road map once per quarterto provide the latest information and include new
features and functions.
To support customers executing the SAP BW/4HANA transition successfully, SAP has developed several
service offerings. The offerings are structured for:
SAP Value Assurance supports customers on their own or partner-led projects with dedicated planning,
design support, and functional and technical safeguarding services orchestrated by the technical quality
management (TQM) approach and embedded in the service center concept but does not provide any
implementation or delivery services.
Figure Preface 4: Service Plan SAP Value Assurance for the transition to SAP BW/4HANA in
Customer/partner-led project
In addition the SAP Advanced Deployment service offering also contains execution services for the
Realize phase of the project, and is delivered by SAP Professional Services in case of SAP prime
projects.
Figure Preface 5: Service Plan transition to SAP BW/4HANA in SAP prime project
All service components from SAP Value Assurance are available to Premium Engagement customers as
well. However, in particular SAP MaxAttention customers do have access to a broader set of offerings like
enterprise architecture planning. Where appropriate, those services are listed in this road map as well.
SAP Value Assurance has been structured into three service packages:
• Plan and Safeguard: This package is for customers who would like to properly plan the digital
transformation together with SAP, and who would like to get safeguarding support throughout the
implementation phase until Go-Live. The project execution is supported by SAP but executed by
the customer or the implementation partner or both. A TQM supports the customer project manager
throughout the project and builds a bridge to the mission control center MCC at SAP. The technical
and functional implementation is done by the customer or the implementation partner or both.
Identified product gaps can be validation, and the functional design evaluated by SAP.
SAP has added a Plan and prototype option to this package. The prototyping approach enables
you to evaluate the solution in a short time frame with your real business scenarios using your real
data, thereby enabling you to quickly validate the value addition, identify and mitigate risks, if any,
at an early stage and efficiently plan your IT investments.
• Business-ready: On top of ”Plan and Safeguard”, SAP actively supports customers in the design of
a a “close-to-standard” implementation. The implementation is done by the customer or the
implementation partner or both.
All SAP Value Assurance service packages can be tailored to your requirements. A description can be
found in the “accelerators” section.
The SAP Value Assurance service packages help you to quick-start your transformation with a defined set
of services, and are pre-calculated based on minimum scope, requirements and SAP involvement. Further
characteristics are:
• The scope can be easily extended as required
• Further optional services can be added for a higher hands-on involvement of SAP
• The technical quality manager will manage the extension together with you.
The following services have been designed to support customers in an SAP S/4HANA
implementation:
A service consists of one to many service components (SAP Value Assurance), or scope options (SAP
Professional Services). For simplicity reasons, this road map uses the term “service component” only. This
road map provides information about how a certain service component supports the implementation of an
activity or task. See the accelerator section for a description of services and service components. If you
are interested in SAP Value Assurance service packages, you can either contact your main SAP contact
person (TQM i or client partner). Alternatively, you can also ask for a tailored offer based on a scenario-
specific scope (see accelerator section for contact form details).
Individual support offerings from SAP Enterprise Support are also mentioned in the section “How SAP can
Support” throughout the road map.
Accelerators:
• SAP Activate
o General Information
o Overview Presentation
o Solution Brief
o Methodology
o FAQ
• Roadmaps
o Road Map Viewer in SAP Solution Manager
1. Discover
In the Discover Phase, customers become familiar with the benefits of SAP HANA and SAP BW/4HANA,
and the benefits it can bring to customers’ business.
• In a first step many customers want to (re)define their analytics strategy, which includes the User
Experience component (‘frontend analysis tools’) as well as the backend part e.g. with a data
warehouse. In this step customers want to evaluate the role of SAP BW/4HANA in a newly redefined
analytics landscape. Customers who have already participated In the SAP BW/4HANA Discovery
Workshop already have a functional and technical overview and may have defined their specific
approach. The Analytics Strategy Workshop works out potential customer-specific road map
options.
• In a second step a trial system could be provisioned to support the impact evaluation. For trial
systems there are 3 versions available in the SAP Cloud Appliance Library:
- SAP BW/4HANA 1.0
- SAP BW/4HANA SP03 including BW/4HANA Content SP01 XT
- SAP BW/4HANA 1.0 SP09 and BPC 11 SP05 including BW/4 Content SP06
To learn about the current SAP BW/4HANA release, it is recommended to look at the central release
information note of SAP BW/4HANA, and the release restriction note. Both are given for SAP BW/4HANA
1.0 in the accelerator section.
Regarding SAP BW/4HANA releases and the availability of landscape transformation tools supporting the
data transformation to SAP BW/4HANA you may check the product road map listed in the accelerator
section.
Accelerators
• Innovation Discovery Finder
• Platform and Technology of SAP Road Maps
• SAP BW/4HANA Overview and Roadmap
• SAP BW/4HANA Community
• SAP Online Help Portal for SAP BW/4HANA
• Cloud Appliance Library
• Release Information SAP BW/4HANA 1.0
• SAP Note 2347382: General Information SAP BW/4HANA
• SAP Note 2347384: Important Information SAP BW/4HANA
• SAP Note 2383530: Conversion from SAP BW to SAP BW/4HANA
• Discovery Workshop for SAP BW/4HANA
• Service Information – Service Components for Planning
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
Strategic Planning
Description
SAP BW/4HANA is a new product built to fully leverage the SAP HANA in-memory platform. It provides a
simple set of objects that is well suited for modelling an agile and flexible layered architecture of a modern
data warehouse. SAP BW/4HANA manages all sorts of data, whether from SAP applications or other
systems, structured or unstructured, and allows accessing of all models through an open SQL
interface. Now depending on the start position of the customer, if the customer is currently running SAP
BW on anyDB or already uses SAP BW powered by SAP HANA, the overall innovation strategy and road
map needs to be defined.
You may check the SAP Transformation Navigator starting from your current product map, and your
current and planned business capabilities, to determine a high-level future product map which lists the
strategic SAP go-to products and solutions including details on the transformation scenarios. The tool lists
the value drivers influenced by the SAP products which can help you with the business case. The results
are compiled in three documents with different focus on business, IT, and transformation.
Figure: Entry screen of the SAP Transformation Navigator
The SAP Transformation Navigator should be the first preparatory step for the creation of your digital
transformation road map.
• New options exist for analytics from OLTP embedded analytics up to SAP HANA Data Warehouse
and cloud based solutions like SAP Digital Boardroom.
• SAP HANA provides advanced platform capabilities for your core analytical processes: Real-time
reporting, Analytical / predictive processing, Big Data / IoT integration
• SAP portfolio has been streamlined and simplified:
o SAP BW/4HANA is the new flagship in the EDW space. SAP BW/4HANA has been rebuilt
to fully leverage the SAP HANA in-memory platform and be more open, simpler, faster and
equipped with new interfaces.
o SAP BusinessObjects BI has been simplified and products are merged and functionally
extended.
o SAP BusinessObjects Cloud offers an alternative UX/frontend solution for customers, which
fully want to leverage cloud capabilities.
• Path 1: New implementation: For those who would like to implement a new SAP BW/4HANA
system by either migrating a legacy system or by running a net-new installation of SAP BW/4HANA.
• Path 2: System conversion: For those who want to run a conversion of an existing SAP Business
Warehouse system to SAP BW/4HANA. There are three types available for this scenario:
▪ 2a: In-Place Conversion
▪ 2b: Remote Conversion with parallel operations
▪ 2c: Shell Conversion
• For the In-Place Conversion and the Remote Conversion, classic BW objects (e.g. InfoCubes,
classic DSO, BEx Report) need to be migrated to the related new HANA-optimized object type.
If your current SAP landscape has been highly maintained (SAP BW powered by SAP HANA and
mainly usage of new HANA-optimized BW object types), you most likely can convert to SAP
BW/4HANA in just a few steps.
• For the Shell Conversion, neither master nor transaction data are transferred. This allows for
optimized modeling and a re-design of the data models. Only selected data models and flows are
transferred to target SAP BW/4HANA system using transports.
• Path 3: Landscape transformation: For those who would like to consolidate their existing data
warehouse landscape or carve out selected data models or flows into an existing SAP BW/4HANA
system. Landscape transformation including a selective data migration, which could be conducted
within a customer-specific project with SAP.
Note: Since Q1 2019, SAP BW/4HANA 2.0 is available for new installation, but a direct conversion to
SAP BW/4HANA 2.0 is currently not supported and is planned for Q3 2019. After a conversion to SAP
BW/4HANA 1.0 has been completed, an upgrade to SAP BW/4HANA 2.0 is possible.
There are some challenges to be considered for creating a parallel productive SAP BW/4HANA
system:
Challenges
• SAP BW/4HANA system shall be used productively for system conversion (risk & runtime
mitigation)
• Both systems shall be operated in parallel temporarily, hence data supply must be synchronized
• Delta management in the source systems must be made aware of the new SAP BW/4HANA system
• Source systems must not have any downtime (data booking must not be interrupted)
Solution
Procedure
• Check the Conversion Readiness of the current SAP Business Warehouse
• Run an Analytics Strategy Workshop. This service component describes the main components
of the SAP Analytics strategy from UI as well as from data warehousing perspective, and works out
potential customer-specific road map options.
• Decide on the innovation strategy and a high-level analytics road map
• Define the strategic analytics road map and value case
•
Results
As a result, there should be
• A customer specific 3-5 year roadmap for analytics and/or data warehouse approach, which
has been commonly worked out and agreed in the workshop
• main change activities and sequences on the defined roadmap
• Key values from business as well as from IT perspective supporting this roadmap
• Demo scenarios for the one or other scenario in BW/4, SAP Lumira or other involved components.
The discovery workshop for SAP BW/4HANA helps customers identify crucial benefits and suggested
approaches for their road to SAP BW/4HANA in order to leverage latest functional and technical
innovations and move forward to the future-proof, scalable and high performance enterprise data
warehousing platform by SAP.
It helps to evaluate possible transition scenarios towards SAP BW/4HANA for increased predictability,
identify areas of added value due to functional and technical innovations and ensure security of
investment by planning the road to the future data warehousing platform.
During a preparation phase relevant customer information will be gathered. If applicable SAP will not only
analyze the information gathered from the customer but also the existing system itself by conducting
various checks inside the customer system. After all relevant information is gathered and the customer
requirements have been identified the workshop material will be adjusted according to the outcome of the
preparation phase.
The 2-day on-site workshop itself will cover all of the topics of relevance that have been identified. Areas
of interest might be following:
• SAP BW/4HANA Roadmap
• SAP BW/4HANA functional overview and technical innovations
• SAP BW/4HANA in combination with SAP S/4HANA
• Transition paths to SAP BW/4HANA and offered system conversion tools
• Prerequisites for SAP BW/4HANA and results of system analysis and pre-checks
• Business use cases and SAP BW/4HANA business content
• Analytics with SAP BW/4HANA using SAP BusinessObjects Cloud and SAP BusinessObjects
Design Studio
• Viable recommendation for the next steps on the road to SAP BW/4HANA
The Discovery Workshop for SAP BW/4HANA is not part of any SAP Value Assurance service
package, however it is not free of charge. Customers should contact the local SAP sales
representative for ordering details.
Accelerators
• Service Information – Service Components for Planning
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• Conversion Guide for SAP BW/4HANA 1.0
• SAP Note 2733740 - BW/4HANA – Information
• SAP Note 2347382 - BW/4HANA – Information
• SAP Note 2347384 - Important SAP Notes for SAPBW/4HANA
• SAP BW/4HANA Master Guide
• SAP BW/4 HANA Planning Product Availability Matrix (Planning PAM)
• SAP BW/4HANA End of Mainstream Maintenance Key Dates
• Discovery Workshop for SAP BW/4HANA
1.1.1.Check the Conversion Readiness of the current SAP Business Warehouse
Objective
There could be show stoppers (e.g. incompatible Add-On’s installed in the existing SAP BW system) or
requirements that may have impact on your conversion project. The objective of this task is to identify all
items that could have a major project impact as early as possible, to be able to adapt the overall project
plan accordingly.
Prerequisites
This task is in particular important for System Conversion and Landscape Transformation scenarios (in
case they start with a system conversion).
Procedure
Check the availability matrix of the conversion type for the respective SAP BW system releases:
SAP recommends to check the following areas, and to document the results:
Results
The results document of this task describes the implications of SAP BW/4HANA; which need to be
addressed either before starting the transition project, or as part of the transition project.
It is basically a filter on the “Simplification List for SAP BW/4HANA” based on usage of the individual
system. I.e. the SAP Readiness Check for SAP BW/4HANA performs a remote analysis of the settings,
configuration, and object compatibility and then lists all simplification items relevant for this system.
Once you have prepared the current SAP BW system, you can execute the SAP Readiness Check for
SAP BW/4HANA yourself, either via SAP Solution Manager (recommended) or in the current SAP BW
itself. When the data has been analyzed by SAP, you can access the results conveniently in a dashboard
running in a web browser. Based on the results you can initiate the recommended activities yourself, or
with the help of SAP.
The following picture shows the results dashboard of the SAP Readiness Check for SAP BW/4HANA, with
dedicated sections for custom code analysis, add-on compatibility, relevance of the simplification items
and so on.
From the results that are displayed on tiles in the dashboard you can navigate to the corresponding
detailed views.
In case you need further interpretation of the SAP Readiness Check results, SAP offers a “Readiness
Check Explained” service component, which explains the check results in general and puts them into
perspective with respect to conversion feasibility and complexity. See accelerator section “Service
Information – Service Components for Planning” for more details.
SAP BW/4HANA Simplification Items:
For a given customer, only a limited number of simplification items from this extensive list are applicable.
The list covers all system capabilities, to include industry solutions. In the detailed view, you see the
simplification items for your SAP BW 7.x system, ranked by assessed relevance. The detailed view also
includes a reference to each simplification item's group, application area, category, and SAP Note where
you can find additional information.
SAP BW objects are listed according to their compatibility with SAP BW/4HANA:
• Green Bar
The objects are compatible with SAP BW/4HANA and can be used without changes.
• Yellow Bar
The objects are not compatible with SAP BW/4HANA. They either have to be changed, replaced
or deleted. We have a tool available to automate this process (partially or fully). The to-do column
will give a bit of details about it.
• Red Bar
The objects are not compatible with SAP BW/4HANA. They either have to be changed, replaced
or deleted. However, there are no tools available and the re-design has to be done manually. In
most such cases, we offer an automated deletion for any objects the customer deems obsolete.
This check shows how many add-ons are installed in your system, and whether they are compatible with
SAP BW/4HANA. In the detail view, you find the names of the add-ons, the vendor (SAP, 3rd Party on
SAP pricelist, 3rd party unknown), and the compatibility status.
Please see the accelerator section for the landing page of the SAP Readiness Check, which contains all
important information on preparation, execution, and analysis.
Accelerators
• SAP Readiness Check – Landing Page
• SAP Readiness Check – Central JAM (SAP internal link)
• Service Information – Service Components for Planning the Digital Transformation
Procedure
To define the analytics road map, you will need to clarify questions like:
Results
As a result, there is a high-level multi-year road map which describes the main change activities and
sequences them on a high-level time line.
The Analytics Strategy Workshop is available as service component in the Value Assurance service
“Planning the Digital Transformation” and as a service component in new SAP MaxAttention service
“Architecture Transformation”.
Accelerators
• Service Information – Service Components for Planning the Digital Transformation
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• Service Information – Architecture Transformation
A holistic overview of the main topics has to be considered for the transition, including a high level
overview about the transition approaches, tools, sizing and technical dependencies.
Outcome of the workshop should be one or several roadmap options with brief description of the key mile
stones and high level time lines.
The workshop also gives an overview about possible conversion paths to SAP BW/4HANA, which is
usually part of the strategic Analytics road map discussion.
The delivery approach of the Analytics Strategy Workshop service component can be split in 4 major
steps:
Figure: Steps of the Analytics Strategy Workshop
Details on the Analytics Strategy Workshop service component can be found in the accelerators
section.
Accelerators
• Service Information – Service Components for Planning the Digital Transformation
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• Service Information – Architecture Transformation
1.1.4.Discover the Value of SAP Business Planning and Consolidation (BPC) version for SAP BW/4HANA
Description
The new release of SAP Business Planning and Consolidation (SAP BPC) is available since June 2017 –
SAP Business Planning and Consolidation 11.0, version for SAP BW/4HANA.
SAP BPC 11.0 is anew release of SAP BPC, optimized for SAP BW/4HANA. it is not a successor to BPC
10.1, version for SAP NetWeaver or BPC 10.1, version for the Microsoft platform.
Figure: Paths to SAP BPC 11.0 on SAP BW/4HANA
The 11.0 release offers Planning and Consolidation capabilities via the standard and embedded model.
Much of it is based on functionality from BPC NW.
Due to the fact that it’s BW/4HANA platform which leverages the SAP HANA database, BW-IP is no
longer supported, and the BPC Standard model requires the SAP HANA platform.
SAP took the opportunity of BPC 11 development to redesign and improve user experience believing that
better user experience makes user’s work more productive and life easier. SAP Fiori was chosen as our
design language for a harmonized SAP wide look and feel. We also made functional enhancements, such
as home page and search, for a better experience to all users.
SAP BPC 11.0 can be included in an in-place conversion or a remote conversion, following the
prerequisites listed in the figure below:
Figure: Available Conversion scenarios from SAP BPC standard to SAP BPC 11.0 version for SAP
BW/4HANA
Accelerators
• Service Information – Service Components for Planning the Digital Transformation
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• Service Information – Architecture Transformation
Prerequisites
The definition of the road map is based on:
Procedure
The following steps should be taken into account (recommended step sequence):
1. Develop the building blocks (such as functional, organizational or technical steps) required
to reach the defined target architecture
2. Perform a transformation maturity assessment to identify the ability of the customer to
execute the transformation e.g. related to organizational change, budget, technical
capabilities and project experiences
3. Determine the risks of transformation
4. Compose a consolidated road map of building blocks to implement the target solution
landscape
5. Agree on requirements & conditions for the business case calculation
6. Define KPIs, and link them to the identified value drivers
7. Determine the value driver
8. Determine the cost driver
Upload all documents to the SAP Solution Manager so information can be shared across the project team.
Results
There is a documented implementation road map and a value case available.
Accelerators
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• Service Information – Service Components for Planning the Digital Transformation
• Service Information – Architecture Transformation
Procedure
• Provide a Trial System
Results
As a result, project members have access to the trial system for demoing, value identification, and impact
evaluation.
Accelerators
• SAP Cloud Appliance versus Blu-Ray Installation
Prerequisites
User account at cloud provider required (e.g. Amazon Web Services (AWS)).
Procedure
You can access the cloud appliance via the SAP Cloud Appliance Library (SAP CAL, see link in the
accelerator section). It is a pay-per-use model hosted on Amazon Web Services (AWS). When using the
SAP CAL option, you can choose between a 30-day trial, or a longer-lasting engagement. With the trial,
only AWS hosting fees need to be paid by the customer.
Note: Check your cloud provider page for prices. You find the recommended VM sizes in the details
section of the selected image.
If you opt to go beyond the 30-day limit, an SAP CAL subscription license and a regular SAP license
for the product is required. Besides the SAP backend, you also receive access to a MS Windows
Terminal Server (WTS) with the pre-configured Fiori Launchpad URL, SAP GUI logon, and other useful
frontend software.
Figure 1.6: Relation of user, SAP Cloud Appliance Library and AWS Cloud
Figure 1.7: SAP BW/4HANA 1.0 with BPC 11in the Cloud Appliance Library
Results
Once the trial image has been started by the cloud provider (the instance is up and running within 15 - 60
minutes depending on the complexity of the solution), you have access to the trial system.
Accelerators
• SAP CAL
• SAP CAL at SAP SCN
• Getting Started Guide BW4HANA Trial
2. Prepare Phase
Once the business case has been approved, the project is initiated in the Prepare phase.
The formal setup of the project needs to be aligned with the customer project manager. In general, each
company or implementation partner has a methodology to plan and execute projects. SAP’s
implementation methodology is called “SAP Activate”. See Accelerator’s section for more details. Note
that currently the SAP Activate methodology is always described in the context of SAP S/4HANA, but a lot
of the SAP Activate content is generic and can help with the implementation of other SAP products, too.
Yet, some tasks are still relevant for SAP, like the availability of the SAP Solution Manager as the project
delivery platform, or a continuous project reporting (e.g. during Quality Gates) to the SAP Mission Control
Center. SAP experts can help quicker in case of problems.
If the customer wants to go for prototyping it takes place in the Prepare phase. Prototyping is an optional
small project on its own. It requires dedicated planning, execution and final evaluation.
The transition project itself is planned at a high-level in the Transition Planning activity in the Migration
Planning Workshop (conversion) or the Transition Planning Workshop (new implementation). Results
from the Discover phase – in particular the functional implementation road map - need to be considered as
well. The project plan will be further detailed out in the Explore phase. If not yet done in the Discover
phase, a readiness assessment is performed on the current SAP BW system to identify aspects that could
have a major impact on the system conversion project.
The planning workshops often reveal preparation activities (e.g. the database migration to SAP HANA),
which could be done before the Explore phase starts. Those larger preparation activities need to be
planned in detail in the Project Management work stream and will be executed in the Transition
Preparation activity. These can be complete pre-projects which have to be performed before the actual
transition project can go into the Explore phase.
• For conversion projects: The cleanup of custom code which is not in use, and which could be
decommissioned before the conversion starts.
• The installation and configuration of SAP Solution Manager
The Prepare phase ends with a first Quality Gate to ensure proper project preparation.
Accelerators
• SAP Activate
o General Information
o Solution Brief
o Methodology
o FAQ
Project Initiation
Description
An important part of the Prepare Phase of a project is the formal setup of the project. This needs to be
aligned between SAP and the customer.
• The customer has bought one of the four SAP Value Assurance service packages.
• The SAP Technical Quality Manager (TQM) and the access to SAP’s Mission Control Center
and Premium Mission Critical Support is part of each and every Value Assurance package..The
SAP TQM is your contact partner to discuss all topics related to your transition project. The TQM
makes sure that all issues are resolved and you receive the services and support activities at the
right point in time with the right skills from SAP.
• SAP TQM tasks and deliverables:
• Setup of the governance structure for your project
• Leadership for scope definition and execution of all tasks done by SAP
• Definition and review of quality gates
• SAP Mission Control Center:
• Access to the whole SAP back office organization including SAP Development
• Verification of engagement plans
• Access to premium mission critical support
• Support for gap clarifications
• There is a project manager from the customer and/or implementation partner, and the SAP
TQM who supports to run this project. The roles and responsibilities in the project, especially
those that are leading the project (customer or partner) are defined.
• The customer is managing the project by either using a 3rd party software (e.g. Microsoft MS
Project), or SAP IT Portfolio & Project Management. SAP provides project templates for
download as a starting point, which need to be adapted to the customer project specifics.
• The Quality Gates are managed in SAP Solution Manager by the SAP TQM. All important
documents and Quality Gate check lists are stored there. There are several applications in SAP
Solution Manager to service this aim:
• IT Portfolio & Project Management (ITPPM; formerly known as cProjects)
• Project road map (transaction RMMAIN)
• Project Management (transactions SOLAR*)
As of SAP Solution Manager 7.2 ITPPM should be used for managing Quality Gates.
• Documents that need to be shared across the project team (e.g. Risk-Response-Log), are
stored in SAP Solution Manager, e.g. by attaching them to the corresponding activity and/or
task in SAP ITPPM. Alternatively, in case of SAP Value Assurance, SAP JAM could be used for
sharing documents across the project teams.
• Quality Gate check lists can be sent to SAP for reporting and safeguarding reasons.
Project management in the context of an SAP implementation has been documented in detail in SAP
Activate road maps (e.g. “SAP Activate methodology for Business Suite and On-Premise – Agile”).
See accelerator section for a link.
All general project management activities, tasks, and accelerators can be taken from there, by filtering on
the Project Management work stream. This road map focuses on additional project tasks which are owned
by the SAP Technical Quality Manager (TQM).
Results
Once this activity has been completed, the transition project has been successfully initiated.
The service always includes the Focus TQM described above. In addition you may request additional
resources like the Project Manager / Project Lead, and Engagement Architect from SAP as part of this
service. See accelerator section for a service component description.
Accelerators
• Service Information - Value Assurance Foundation
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• SAP Digital Business Services (DBS) Delivery Infrastructure
• SAP Activate road map “SAP Activate methodology for Business Suite and On-Premise – Agile”
• SAP BW/4HANA_Project Plan Templates
• Classroom training: Implementation Projects with SAP Solution Manager
Procedure
Typically, during these calls the account team and project team review the following areas: project
background, business case, business drivers, customer goals, scope, RACI, success metrics for the
project, customer expectations, delivery model, Statement of Work, Order Form, assumptions
Procedure
• Review Order Form Assumptions
• Review Order Form Scope
• Review Order Form RACI
• Review Order Form Resources & Budget
• Review Order Form Customer Staffing
• Review Order Form Solution Scope
• Current Situation
• Proposed Resolution
• Solution Description
• Project Goal
• Project Objectives
• Business Case Summary
• Total Estimated Project Costs
• Key Dates
• Project Stakeholders
• Critical Success Factors
• Risk Assessment
Procedure
• Define Project Purpose or Project Justification and measurable Project Objectives
• High-Level Project Description and Boundaries
• Project Success and Approval Criteria
• Assumptions and Constraints
• High-Level Requirements
• High-Level Solution and Project Scope
• Summary Milestone Schedule
• Summary Budget
• Stakeholder Group and Key Names Stakeholders
• High-Level Risks
Accelerators
• Business Case Template (Customer)
• Project Charter Template (Customer)
• Scope Statement Template (Customer)
Procedures
• Establish Scope Baseline
• Establish Schedule Baseline
• Establish Cost Baseline
• Establish Quality Baseline
• Define Scope Management Plan
• Define Requirements Management Plan
• Define Schedule Management Plan
• Define Cost Management Plan
• Define Quality Management Plan
• Define Process Improvement Plan
• Define Human Resources Management Plan
• Define Communications Management Plan and Project Reporting Standards
• Define Risk Management Process
• Define Procurement Management Plan
• Define Stakeholder Management Plan
• Define Change Management Process
• Define Issue Management Process
• Define Project Constraints
• Define Project Standards
• Obtain Project Management Plan Sign-Off
Accelerators
• External Risk List Template (Customer)
• Focused Build for SAP Solution Manager (Customer)
• Project Management Plan Template (Customer)
• Resource Plan Template (Customer)
• Risk Identification Session Guide (Customer)
• Subsidiary Project Management Plans Guide (Customer)
Accelerators
• Agile Project Team Roles and Responsibilities (Customer)
Plan Project
Description
The purpose of this deliverable is to properly plan the project to guide both project execution and project
control.
Procedure
• Create Scope Statement
• Create WBS
• Create Project Schedule
• Create Budget
• Plan Quality
• Plan Communications
• Plan Risks
• Plan Procurement
• Plan Stakeholders Management
2.3.2.Create WBS
Objective
The purpose of this task is to create the work breakdown structure (WBS) for the project, which is a
deliverable-oriented, hierarchical decomposition of the work to be executed by the project team to
complete the project. It is the basis for the organization and coordination of the project. A WBS consists of
WBS elements that describe project tasks and subtasks to perform within a defined time period.
• Top-down view of how activities fit into the overall project structure
• Defines the total scope of the project (specified in the approved scope statement)
• Work packages at lowest level can be subdivided into activtities/tasks
Procedure
1. Define Activities
2. Sequence Activities
3. Estimate Activity Resources
4. Estimate Activity Durations
5. Develop Schedule
2.3.4.Create Budget
Objective
The purpose of this task is to create a project budget, that outlines all the costs associated with the
project, including labor, hardware, software, cloud provisioning, contracting fees, and facilities. The project
budget is a living document that the project manager maintains. At this stage the project manager sets the
budget baseline and will manage the budget according to the cost management plan that is developed as
part of the Project Management Plans task.
Procedure
• Estimate Costs
• Determine Budget
Accelerators
• Resource Plan Template (Customer)
2.3.5.Plan Quality
Objective
The purpose of this task is to identify the standards of the project and how the quality will be managed and
validated throughout the implementation of the project.
Accelerators
• QGateChecklist Concept SAP Activate
• QGateChecklist Template Introduction
• Quality Built In New QGateChecklist
2.3.6.Plan Communications
Objective
The purpose of this task is to plan the communication management and define the communication
requirements for the project.
Accelerators
• Communication Plan Overview Template (Customer)
2.3.7.Plan Risks
Objective
The purpose of this task is to plan and define the project risks.
Procedure
1. Identify Risks
2. Assess Risks: Estimating and Evaluating Risk
3. Create Risk Register ( refer to the "Risk Register Template" provided )
4. Define Risk Responses
Accelerators
• External Risk List Template (Customer)
• Risk Identification Session Guide (Customer)
2.3.8.Plan Procurement
Objective
The purpose of this task is to plan and prepare the guidelines for all the procurement activities on the
project. This includes materials, products or services identified for outside procurement.
Accelerators
• OCM Stakeholder Identification Guide (Customer)
• OCM Stakeholder Identification Template (Customer)
Tasks
• Prepare for Kick-off Meeting
• Conduct Kick-off Meeting
• Prepare Team Onboarding Document
• On-board Project Team
Accelerators
• Project Kick-off Template (Customer)
Accelerators
• Project Guideline Template (Customer)
The purpose of this activity is to prepare the on-boarding package for external consultants and new project
team members from SAP and partner companies coming to the project. The on-boarding package
contains the essential information that each new team member needs to understand, which is the purpose
of the project, goals, operating procedures, and other key information.
• Project objectives, scope, and goals including SAP solutions being implemented
• Project schedule including milestones
• Project governance including key project stakeholders
• Organizational chart for the project-showing both internal and external resources
• Overview of the existing SAP landscape
• Outline of regular project meetings
• Travel policies, dress code, project location, and other project guidelines as needed.
Project Team Enablement
Description
The purpose of this task is to develop a comprehensive training strategy that provides all team members
with a learning path for acquiring the skills and knowledge needed to complete the project successfully.
Procedure
• Provide key self-learning material to the project team
• Train the customer project team.
Results
As a result the project team has been trained successfully.
Prerequisites
The project has been initiated.
Procedure
Organize self-learning possibilities for ITprofessional to understand the new solution with digital learning
environments (e.g. Learning Hub). This may include:
Ensure that all team members can access the Best Practices documentation (see accelerator section)
at the SAP Support Portal. The SAP Support Portal can be access via the URL:
https://support.sap.com. First time users must register. The customer or installation number is
required and can be provided by the customer's IT Contact or SAP account team. The SAP Support
Portal allows access to various SAP content and resources used during and after an implementation
project.
Ensure that all project team members can access the SAP Learning Hub. The Learning Hub is central
location which allows access to different SAP Learning Rooms. SAP Learning Rooms are interactive
social learning environments. Available online 24/7, they facilitate informal learning and knowledge
sharing as well as expert-hosted live sessions, videos, quizzes, and postings on a wide range of SAP
topics. To access the learning hub, read the blog in the accelerator section.
Ensure the project team is properly trained on the usage of SAP Solution Manager. SAP Solution
Manager provides a central point of access for a variety of essential project support functions. The
reference materials provide more details about available Solution Manager trainings, Focused Build
for SAP Solution Manager, and a video describing how SAP Solution Manager is perfect for SAP
implementation. SAP provides customers with a SAP Solution Manager tool set that supports
customers in implementation of the project standards for the purposes of the project or operations. It
is highly recommended to use the SAP Solution Manager Focused Build service solution. Additional
details can be found in the accelerator section.
Results
Key learning resources are available to the project team for self-learning.
Accelerators
• Access to Best Practices
o SAP Best Practice Explorer
o How to Use SAP Activate Content in SAP Solution Manager 7.2
• Access to the SAP Learning Hub
o Create SAP Learning Hub Account, Join SAP Learning Rooms, and Troubleshoot
Issues (SAP Internal Link)
• Self-Enablement Materials
o Setup Access to SAP Learning Hub (SAP Internal Link)
• SAP Solution Manager Materials
o Classroom training: Implementation Projects with SAP Solution Manager
o Focused Build for SAP Solution Manager
o Best Practices Reference Guide
o SAP Solution Manager Landing Page in the SAP Support Portal
o SAP Value Assurance - Description of Services and Service Components
• Agile Implementation
o Agile Concept Presentation
o Agile Management Introduction
o Agile Project Team Roles and Responsibilities
•
Prerequisites
The project has been initiated, and the project team has been set up.
Procedure
The starting point for creating knowledge transfer in transformation projects is the identification of the
learning requirements and the analysis of the digital learning opportunities for the professional IT team
members within the customer organization.
Matching the project scopes and objectives with the given resources and their requirements will identify
the skill-gaps for the project team members at the very first beginning of the project.
Proceed as follows:
• Identify the processes in scope and analyze the required skills together with the project team
• Evaluate SAP individual standard training from SAP Education courses (Classroom and Web-based
Trainings)
• Develop enablement plan including training, mentoring, coaching for individual project team
members / project team groups
• Organize and run system application training with individual learning methods
Results
The customer project team is ready for application design and implementation.
Please note that the training of the project team is not included in SAP Value Assurance, but is handled
separately by SAP Education.
Accelerators
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• Service Information – Service Components for Planning the Digital Transformation
• SAP Build Design Support ENA Additional Accelerators (SAP internal link)
Project Standards & Infrastructure
Description
The purpose of this deliverable is to provide consistent means of executing and governing project work in
an efficient and effective manner. The key objective of Project Standards is to identify, define, approve,
and communicate standards related to project execution. Where and when applicable, the current
customer processes and procedures, related to the project standards should be taken into account when
defining the most suitable standards for the project. Project team needs to setup tools like SAP Solution
Manager to enable execution of specific project standards. The SAP Solution Manager application
management solution is included in customer’s SAP maintenance agreement, and provides all integrated
content, processes, tools, and methodologies you need to efficiently implement, operate, monitor, and
support all your SAP and non-SAP applications. SAP Solution Manager is also the hub for collaboration
within the SAP ecosystem, to ensure delivery of high-quality services and support for your mission-critical
business processes. This enables better operations and faster implementation at lower costs.
Procedure:
1. Install and Setup SAP Solution Manager
Project standards are elaborated throughout the Prepare phase (some may be fine-tuned in a later stage
of the project). During the Prepare phase the foundational project standards must be defined, approved,
and communicated to the project team. Communication of project standards should be included in project
on-boarding communications for project team members. Given the integrated nature of project standards,
changes must be managed in accordance with the integrated change control procedure.
The project team needs to establish, at minimum, the project standards for the following areas:
• Requirements Management
• Authorizations / Security
The purpose of this task is to determine the customers framework to centrally document and relate
business processes and technical information of SAP and non-SAP Solutions in Solution Manager,
ensuring transparency, efficient maintenance and collaboration.
The purpose of this task, also known as Innovation Management, is to determine the customers approach
for the identification, adaptation and implementation of new and enhanced business and technical
scenarios. It is part of the application lifecycle and designed to decouple technical installation from
business innovation using SAP Solution Manager to implement the innovation in the system landscape.
The purpose of this task is to determine the customers template management approach that allows
customers with multi-site SAP installations to efficiently manage their business processes across
geographical distances - from initial template definition to template implementation and template
optimization, for example as part of a global rollout.
The purpose of this task is to determine the customers approach for managing functional and performance
testing of SAP-centric business processes to ensure validated system behavior after software change
events.
The purpose of this task is to determine the customers approach of handling business and technology-
driven changes, using a standardized process leading to improved reliability of solution and minimized risk
through segregation of duties and transparency of changes.
The purpose of this task is to determine the customers approach of a centralized and common incident
and issue message processing for multiple organization levels. The process offers a communication
channel with all relevant stakeholders of an incident, including business user, customer-side SAP experts,
SAP Service & Support and Partner Support employees. The Application incident Management is
integrated in all ALM processes of SAP Solution Manager, in any SAP Business Suite solution and can be
connected to an Non-SAP Help Desk application
The purpose of this task is to determine the customers approach of monitoring, alerting, analyzing and
administrating of SAP solutions. It allows customers to reduce TCO by predefined content and centralized
tools for all aspects of operations in SAP Solution Manager, including End-to-End reporting functionality
either out-of-the-box or individually created by customers.
The purpose of this task is to determine the customers approach of Maintenance Management, how SAP
Notes are handled and how they are applied (upon request e.g. current incident in productive
environment, information from SAP about potential issue (Hot News, Security Notes).
The purpose of this task is to determine the customers approach for the identification, adaptation and
implementation of new and enhanced business and technical scenarios. It uses Solution Manager to
manage the upgrade project holistically and effectively end-to-end and allows SAP customers to better
understand and manage the major technical risks and challenges in an upgrade project, and to make the
upgrade project a "non-event for the business".
Accelerators
• Best practices for Implementing CTS+
2.6.3. Define and Set Up Agile Project Standards and ALM Tools
Objective
The purpose of this task is to define and set up SCRUM standards and tools, such as SCRUM board,
burn-down chart, product backlog template and retrospective template. Organization of daily stand-up
meetings, scrum-of-scrum-, release/sprint planning and retrospective meetings. At this time the project
also needs to prepare definition of Ready and definition of Done for each critical step in the iteration. At
minimum the team needs to prepare and agree on definition of Ready and Done for following:
• Ready for Build (e.g. backlog item has proper size, it is clearly defined and understood, test
procedure is defined, etc.)
• Ready for Demo (e.g. backlog item is fully developed and unit tested)
• Ready for Integration Test (e.g. backlog item integration test is defined (automated), test data is
ready)
• Ready for Release (e.g. backlog item user level documentation is complete, ALM Solution
Documentation is ready, Feature passed Integration Test)
Note that definition of Ready for one step in the implementation process == definition of done of the
previous step. Using clear definition of Ready and Done is critical for SCRUM based implementations.
Accelerators
• Agile Definition of Ready and Done (Customer)
• Agile Sprint Burndown and Task Board (Customer)
The objective of this task is to check availability of SAP Solution Manager environment for the project
team. This should be validated early in the project, if not before the project starts.
If there are no setup activity needed to be planned to install Solution Manager, ensure that the technical
team has completed the general Solution Manager set-up and then has covered the process specific
configuration in the following areas:
• Process Documentation
• ITSM
• Test Management
• Application Operations
Please ensure the following has been completed by the technical team:
• users created in the system (with appropriate access roles) and Business Partners created and
connected to users for all project team members
• users can all access SolMan and there is an appropriate schedule of project team training for
each project phase / key activity using SolMan.
• the procedure for requesting access to SolMan and other systems and tools is agreed, setup and
communicated.
• Has the required work space been arranged at all project sites?
• Are there sufficient conference rooms planned for the project team?
• Has multimedia equipment been planned for all conference rooms (e.g. video conferencing,
projectors, etc.)?
• Has physical access been granted for all project team members in different geographical
sites?
• Is there a working area assigned to the project members?
Customer Policies
Physical Security
Telephone/Voice Mail
• Is the required equipment (computer, laptops, mobile and etc.) available to all project team
members?
• Are office supplies available to the project member?
• Are the required software licenses purchased? (if needed)
Prototyping is an optional small project on its own. It requires dedicated planning, execution and final
evaluation, thus is always driven by business or IT requirements.
Procedure
Results
The result of a prototype usually has significant influence on the main project (e.g. Go / No-Go decision,
learnings on how to prepare the main project, or what functionality to set up).
SAP offers a Plan and Prototyping service, providing rapid, tangible proof to the customer by building
customer-specific proof-of-concepts and solution prototypes.
Accelerators
• After the initial planning has been finished a “Scoping Workshop for Prototyping” (service
component) defines the boundaries of the prototype.
• Parts from the “Platform Execution” service are used to technically set up the prototype
system.
• In the case of a system conversion, the “Custom Code Impact Analysis” service component
helps to analyze and offer transparency on the existing custom code situation, including a
customer’s own objects and modifications.
• The purpose of the service component “Mandatory Preparations for System Conversion” is
to support all activities required to meet the functional prerequisites of the prototype (system
conversion only).
• During the service component “Activate Solution”, SAP assists in the activation of
preconfigured content, best practices, and test-activated processes associated with the SAP
Activate innovation adoption framework in the prototyping system landscape for the defined
functional scope.
• The objective of the service component “Fit Gap and Delta Design” is to support customers in
designing, building, and evaluating customer-specific processes, applications, or functions in
the prototyping project.
• During the service component “Result Workshop for Prototyping”, SAP guides the customer
to leverage the learning and documentation from the prototyping project to realize the value
during project implementation for production use.
Further details on the delivery of the prototyping service and the involved services and service
components, see accelerator section.
SAP Enterprise Support customers can join the Expert Guided Implementation session “Set up
Prototype”. This 4-days session explains the main steps required to set up a prototype in the
CAL.
Accelerators
As already highlighted in the preface, there are three conversion paths/scenarios to SAP BW4HANA:
• Path 1: New implementation: For those who would like to implement a new SAP BW/4HANA
system by either migrating a legacy system or by running a net-new installation of SAP BW/4HANA.
• Path 2: System conversion: For those who want to run a conversion of an existing SAP Business
Warehouse system to SAP BW/4HANA. There are three types planned for this scenario:
o in-place system conversion (via SAP BW7.5 powered by SAP HANA)
o Remote conversion
o Shell conversion
• Path 3: Landscape transformation: For those who would like to consolidate their existing data
warehouse landscape or carve out selected data models or flows into an existing SAP BW/4HANA
system. Landscape transformation including a selective data migration, which could be conducted
within a customer-specific project with SAP.
In the Transition Planning activity the decision for one of the scenarios should already be clear.
Note: As Landscape Transformation tool support is not yet available, this roadmap documentation
focusses on the New Implementation and the system conversion scenarios.
The following figure shows the software units that are used for data warehousing:
• With SAP BW∕4HANA, SAP offers the SAP HANA database being the in-memory deployment option
for the data warehousing use case. In combination with SAP BW∕4HANA 1.0, it is necessary to use
SAP HANA SPS 12 or a higher revision.
• The Modeling Tools represent a modeling IDE (Integrated Development Environment) built on top
of the Eclipse platform, supporting SAP BW∕4HANA model with state-of-the-art modeling tools.
These tools include integration with SAP HANA modeling and the consumption of SAP HANA
elements in Open ODS Views or CompositeProviders with powerful UI (user interface) capabilities.
Results
The required implementation steps and preparatory steps should now be defined in an action plan.
In addition, SAP offers a lot of information on the different paths to SAP BW/4HANA in the SAP
BW/4HANA Community. In the SAP Community for SAP BW/4HANA consultants report on their
experiences made during the early adoption phase and give a step-by-step description of the
implementation / conversion process which may be very informative for consultants as well as customers.
For customers who have a productive SAP BW but want a fresh start, SAP is planning to offer an option to
transport certain objects from their existing SAP BW system to a newly installed SAP BW/4HANA system.
For a tool to check the transports, see SAP Note 2361350.
Accelerators
• SAP Product Availability Matrix
• Service Information – Service Components for Planning
• Service Component Delivery Suitcase - Migration Planning Workshop (SAP internal link)
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• Installation Guides on SAP Service Marketplace
• SAP BW/4HANA Community
• OPEN SAP Training Class - SAP BW/4HANA in a Nutshell
• The Road to SAP BW/4HANA (document)
• Technical Presentation on BW/4HANA
• SAP First Guidance – BW/4HANA complete functional scope (CFS)
• SAP Note 2347382 – SAP BW/4HANA information
• SAP Note 2361350 – B4H mode: transport check for RS_B4HANA_CHECK_ENABLE
Procedure
Same as for BW/4HANA – see task “Transition Planning – New Implementation”.
Results
The required implementation steps and preparatory steps should now be defined in an action plan.
In case of a new implementation without any predecessor tool, SAP can support with a Technical
Architecture and Infrastructure service.
Accelerators
All steps for the system conversion have to be planned in this activity, depending on the starting point of
the current BW system.
Existing BW-on-HANA customers (SAP BW, powered by SAP HANA) will first go through the prepare
steps like running the Maintenance planner, perform pre-checks and work trough the simplification list. In
the Realize phase they will first apply the SAP BW/4HANAStarter add-on, then use tools to transfer the
classical objects to the fully HANA-optimized object types. Afterwards, the system conversion is performed
to change the system to SAP BW/4HANA. These steps all need to be planned in detail during this
transition planning task.
Customers starting from BW on anyDB have to start with a database migration to SAP HANA. This is a
separate project which should run during the Transition Preparation activity.
Procedure
1. Check the conversion readiness of the current SAP BW system (system conversion scenarios only)
2. Define the scope and the objectives of the transition
3. Define the cutover approach (high-level)
4. Clarify the custom code adaption
5. Clarify operational readiness
6. Define the technical architecture (high level)
7. Define the data migration architecture (important for new implementation and landscape
transformation)
Results
As a result, a first version of an action plan has been documented which could serve as the basis for a
project plan. A high-level transition planning document should be stored in SAP Solution Manager.
For conversion projects, SAP offers the Migration Planning Workshop (MPW) for SAP BW/4HANA. The
MPW helps to define the scope and execution plan for the customer’s conversion project.
• decision or at least the decision support for the right transition approach to SAP BW/4HANA (in-
place or Remote conversion, system landscape transformation)
• Verification of the prerequisites for the chosen transition approach
• The onsite portion of the service includes knowledge transfer of key concepts and consideration,
as a means to ensure that the customer is making informed decisions.
• In case customer decides to perform an In-Place system conversion, check the Prerequisites
Checklist for the In-Place Conversion and identify the required preparation steps to get the system
and data conversion-ready
• The outcome of the workshop includes
o development of a system-level transition road map
o a customer tailored high-level milestone project plan
o the Prerequisites Checklist with the identified preparation steps (if applicable)
The MPW covers many of the tasks described before, and summarizes the results in a service report. This
consolidated view of critical project planning decisions is why SAP considers the Migration Planning
Workshop as a “mandatory service” for system conversion. Details on the MPW can be found in the
accelerator section.
• The business process streams are assessed in order to define the Best Practice scope, review
existing GAPs, collect information for data migration, quick-sizing and Interface-architecture.
• Create/review high-level architecture with Interfaces
• Create/review Quick-sizing
• Empower the customer for data migration respectively review existing data migration strategy
• (optional) Develop/review of high-level-scope statement and project schedule, project governance
and operational standards
• (optional) Provide substantial knowledge on SAP Activate Methodology, Data Migration Approach
and Strategy, SAP BW/4HANA Sizing
Note: The same sizing process used for SAP BW powered by SAP HANA applies to SAP BW/4HANA.
See SAP Note 2296290. For hardware sizing to run a BW/4HANA system, refer also to SAP Note
2363248 (see accelerator section).
If the customer has decided to perform an in-place system conversion, he may make use of the SAP Best
Practices for In-place system conversion to SAP BW/4HANA as a PS service for the Realize phase.
This PS service provides the customer with a proven project approach and configuration guides for the
conversion of an existing SAP BW to SAP BW/4HANA, without reimplementation and with minimal impact
on business operations. The tool-based conversion to SAP BW/4HANA includes step-by-step
documentation with project WBS structure, streamlined project methodology, and optimized project tools.
Best practices help to plan and convert the system, gaining all of the benefits of BW/4HANA.
Note that filling the Prerequisites Checklist in the MPW is mandatory as a preparation for the in-place
conversion.
Accelerators
• Service Information – Service Components for Planning the Digital Transformation
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• SAP Note 2383530 - Conversion to BW/4HANA - Step by Step description
• SAP Note 2189708 -SAP BW/4HANA Add-On Handling and Usage
• SAP Note 2296290 - New Sizing Report for SAP BW/4HANA
• SAP Note 2363248 – BW/4HANA Hardware Sizing
For a re-implementation of BPC 11.0 Standard model in BPC 11.0 Embedded Model, please refer to the
task New Implementation of BPC 11.0.
Procedure
The in-place conversion of BPC is supported by the Transfer Tool (version 1.5) for BPC Standard as well
as for BPC Embedded.
Note: The same sizing process used for SAP BPC powered by SAP HANA applies to BPC 11.0 and is
based on the sizing for BW/4HANA. See SAP Note 2296290. For hardware sizing to run a BW/4HANA
system, refer also to SAP Note 2363248 (see accelerator section).
Results
As a result, a first version of an action plan has been documented which could serve as the basis for a
project plan. A high-level transition planning document should be stored in SAP Solution Manager.
Accelerators
• Conversion Guide SAP BPC 11.0
• SAP Note 2383530 - Conversion from SAP BW to SAP BW/4HANA
• SAP Note 2531382 - BPC 11.0 version for SAP BW/4HANA - Installation and Conversion
Information
• SAP Note 2510414 - Conversion to SAP Business Planning and Consolidation 11.0, version for
SAP BW/4HANA Central Note
• Efficient and lean transfer from SAP BW 7.3 or higher on anyDB to SAP BW/4HANA
• Tailors the scope of the migration to focus on relevant objects instead of converting the entire
system
• Leaves outdated and unused objects behind in the current data warehouse
• One-step approach for conversion as no prerequisites such as DB migration to SAP HANA or SAP
BW upgrade on the productive system are required
• Risk mitigation due to a parallel system. A copy of the data still remains in the source system during
conversion, hence the retrieval of original data is possible in case or errors
• Uses BW4/HANA Conversion Cockpit as a single point of control, monitoring, and documentation
• Retains business continuity during conversion
Procedure
For customers planning a Remote Conversion it is beneficial, too, to attend a Migration Planning
Workshop (MPW) to develop a customer-specific high-level project plan. See the detailed description of
the MPW in the task “Transition Planning – In-Place Conversion”.
In case customer decides to perform Remote conversion, check the Prerequisites Checklist for the
Remote Conversion and identify the required preparation steps to get the system and data conversion-
ready.
Accelerators
• Technical Presentation on BW/4HANA
• Service Information – Service Components for Planning the Digital Transformation
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• Service Component Delivery Suitcase - Migration Planning Workshop for System Conversion (SAP
internal link)
• SAP Note 2383530 - Conversion to BW/4HANA - Step by Step description
• SAP Note 2296290 - New Sizing Report for SAP BW/4HANA
• SAP Note 2363248 – BW/4HANA Hardware Sizing
• SAP Note 2513088 – SAP BW/4HANA Conversion Cockpit – System Setup & Prerequisites
Procedure
The Conversion Cockpit can be used for a remote conversion of BPC Embedded. However, this
procedure is currently only released in pilot mode.
Note: Please create an incident using the SAP Support Portal, component “EPM-BPC-BW4” with text
‘BPC 11.0 Embedded Remote Conversion’ in subject. SAP will process the ticket and guide you through
the steps to enable remote conversion.
The prerequisite for a remote conversion with the ConversionCockpit is that the following objects are not
in use:
▪ All ‘Local Objects’ (objects created directly in a system which can’t be transported),
including local InfoProviders, local models, local dimensions and master data, local
hierarchy and local queries
The remote conversion for BPC Standard is covered by the BPC-own “Backup and Restore Tool”
(transaction UJBR). An alternative remote conversion scenario for BPC Standard is not planned.
The Remote conversion requires a Data Migration Assessment for Remote Conversion to SAP
BW/4HANA which has to take place in the Explore phase – see activity Data Migration Design.
Accelerators
• SAP Note 2531382 - BPC 11.0 version for SAP BW/4HANA - Installation and Conversion
Information
• SAP Note 2510414 - Conversion to SAP Business Planning and Consolidation 11.0, version for
SAP BW/4HANA Central Note
• SAP Note 2363248 – BW/4HANA Hardware Sizing (also relevant for BPC 11.0)
• Conversion Guide SAP BPC 11.0
• SAP Note 2602319 – Remote Conversion for BPC Embedded Model
2.8.7.Transition Planning – Shell Conversion
Objective
A Shell conversion works very similar to a Remote conversion, but it tailors the scope of the migration to
focus on relevant objects instead of converting the entire system. It leaves outdated and unused objects
behind in the current data warehouse and provides flexibility in selecting and transferring data flows.
Benefit
The Shell conversion allows for a re-design in the target system as the objects initially are not filled in the
target. For the scope selection the shell conversion is more flexible compared to the remote conversion
because dependencies through request/transaction ID do not need to be considered
Procedure
• New SAP BW/4HANA system is installed on additional hardware.
• Data models are transferred to target SAP BW/4HANA system using transports.
Neither master nor transaction data are transferred. Options at customer’s convenience:
For customers planning a Shell Conversion it is beneficial, too, to attend a Migration Planning
Workshop (MPW) to develop a customer-specific high-level project plan. See the detailed description of
the MPW in the task Transition Planning – In-Place Conversion.
• with multiple SAP BW, or SAP BW on SAP HANA systems, or hybrid cases, who want to perform
a consolidation into one global SAP BW/4HANA system or perform selective data migrations.
• who want to consolidate their landscape or carve out selected data models or flows into an
existing SAP BW/4HANA system
• who want to stay with their current data warehouse landscape and move gradually to SAP
BW/4HANA innovations
The starting point typically describes the SAP solution in focus, the transition target product and the
systems in scope (either to be converted, or to be replaced by a new installation). In addition, already
planned changes to the SAP solution and further boundary conditions have to be determined.
The objectives comprise the business and IT requirements related to the new functionality and technology,
e.g.
Process the subsequent tasks in the road map to enhance the scoping document with boundary
conditions and requirements from the business, as well as requirements and prerequisites from target
product perspective.
The transition project can be combined with already planned infrastructure changes, e.g. the replacement
of server hardware or the introduction of a virtualization solution for the application server layer. This can
help to reduce the overall effort for all change activities. Consequently, further limitations or opportunities
might exist, which need to be incorporated. These boundary conditions need to be known to the transition
project to integrate them in the planning and execution.
Document already planned software or hardware changes in the SAP solution landscape, which are to be
synchronized with the transition project. Examples are:
Document release plans or calendars of development projects in the target SAP solution.
Before planning more detailed transition steps, the current SAP solution needs to be described in detail,
so that the required target SAP solution architecture and related transition steps could be derived
(“Inventory”). So if for example the server hardware needs to be changed, the capabilities of the current
server hardware and the related technical architecture of the SAP systems need to be understood in detail
to design the future technical architecture and its mapping to the new hardware.
Additionally, components depending on the changed database or other changed components in the SAP
solution (e.g. the embedded Frontend Server for SAP Fiori) have to be detected to later verify how they
integrate with the future SAP solution.
Accelerators
• SAP Product Availability Matrix
• SAP BW/4HANA Discovery Workshop
SAP provides guidance on the target IT support process activities, tools and resources required for you to
safely and efficiently operate the new SAP solutions in its environment. SAP provides, for example, Best
Practices on daily DB administration procedures, troubleshooting procedures, monitoring tools, knowledge
content for the resources to be ramped up for the post go live operation…
Clarification on the steps required to ensure the IT Operational Readiness will be given later in the Explore
Phase (see activity Operations Impact Evaluation). As a result, a number of tasks will be defined and
included in the conversion plan.
Procedure
Customers who are new to SAP should look at SAP’s general recommendations to set up a Customer
Center of Expertise. At least a primary CCOE certification should be gained.
SAP has also published SAP Support Standards which should be implemented as part of the standard IT
support processes.
Accelerators
• Customer Center of Expertise
• Getting Started with Primary CCOE
• Primary CCOE Check List
• SAP Support Standards
For an in-place conversion, the original SAP BW system needs to have a minimum release level. The
following start releases are supported:
• SAP Business Warehouse 7.5 powered by SAP HANA (support package 5 or higher)
• An in-place conversion of SAP BW 7.51 or higher to SAP BW/4HANA 1.0 is not possible (since
SAP BW/4HANA 1.0 is based on SAP Basis 7.50)
For a remote conversion, the original SAP BW system needs to have a minimum release level. The
following start releases are supported:
• SAP Business Warehouse 7.3
• SAP Enhancement Package 1 for Business Warehouse 7.3
• SAP Business Warehouse 7.4
• SAP Business Warehouse 7.5
The remote conversion is independent of the database platform of your existing system (i.e. all supported
database platforms are allowed; see Product Availability Matrix). See the following table for minimum and
recommended support package level:
Figure 2.7: Release and Support Package Levels of the original SAP BW system
SAP BW/4HANA exclusively runs on SAP HANA. It can be deployed on SAP HANA release 1.0 or 2.0.
The minimum support package is given in the following table:
Procedure
If not done in the Discover phase (activity Strategic Planning):
Collect information for the following topics (as far as already available):
• Future and existing technical platform (hardware platform, virtualization solution, OS)
• General SAP application server architecture
• Availability SLAs for unplanned downtimes
• Data center strategy
• HA architecture and DR strategy and architecture
• Non-production and production landscape
• System to data center mapping
• Planned server hardware (application servers and SAP HANA) and storage hardware
• Integration with cloud services (e.g. with SAP HANA Cloud Platform for side-by-side
extensions of S/4HANA)
• Backup solution
Based on the results, create a first sketch of a technical deployment plan, by mapping the systems and
technical components to the hardware. The technical deployment plan documents which system runs on
which server. This deployment plan is the basis for ordering the hardware at your hardware provider. The
plan is constantly refined throughout the project.
Results
As a result of this task, a technical deployment plan exists.
How SAP Can Support
The Technical Architecture and Infrastructure service component supports customers in the technical
design of a scalable, flexible, and maintainable SAP solution that fits to their specific requirements. Ideally,
the information described in the procedure (above) should be provided by the customer beforehand.
This is especially relevant when customers plan to migrate/transition to SAP HANA and SAP BW/4HANA
which introduces often new IT infrastructure platforms to an existing SAP environment. In case of such a
transition, the new sizing report for SAP BW/4HANA can be used – SAP Note 2296290. Here is an
example output of the report:
In case of a new implementation a basic sizing will be done during the Technical Architecture and
Infrastructure service component with the SAP Quicksizer, see accelerator section:
Figure 2.10: SAP BW/4HANA view in the SAP Quicksizer
The Quicksizer results are rough estimations which should be verified with the hardware partner. An
advanced sizing is recommended during the Explore phase.
Accelerators
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• SAP Note 2021789 - SAP HANA Revision and Maintenance Strategy
• SAP Note 2363248 - BW/4HANA Hardware Sizing
• SAP Note 2296290 - New Sizing Report for SAP BW/4HANA
• SAP Quicksizer
Transition Preparation
Description
This activity covers all preparation work which happens before the project starts. Depending on the type of
conversion (in-place or remote) there might be larger ‘pre’-projects required, which must be identified and
scheduled right before the SAP BW/4HANA transition project starts.
However, significant preparation items should have been discussed in the appropriate planning workshops
in the Transition Planning activity upfront.
• Unicode Conversion
• Upgrade from an older SAP BW like SAP BW7.4 to SAP BW7.5
• Installation of the BW/4HANA Starter Add-on
Prerequisites
There is a high-level transition planning document stored in SAP Solution Manager. This preparation
activity is of particular relevance in case of a system conversion.
Procedure
• Properly analyze all preparation items which have been identified in the Transition Planning
activity.
• Plan in detail the execution of these items. This could result in own projects depending on the
scope of the item. It is in the responsibility of the Project Management work stream to take care
of proper project planning.
• Execute the item according to the plan.
Procedure
These preparation steps differ very much in time and effort. Most of them like the database migration and
the SAP BW upgrade, but also the Unicode conversion should be set up as separate projects.
In the Migration Planning Workshop a mandatory check has been performed to identify which
requirements are still open before the system conversion to SAP BW/4HANA can be performed. All these
identified steps should either be performed here or in the activity Prep Steps & Data Model Adjustment in
the Explore phase.
Results
The system is now on release SAP BW7.5 on SAP HANA. As a next step, the BW/4HANA Starter Add-on
will be installed.
Accelerators
• Conversion Guide for SAP BW/4HANA 1.0
Procedure
These preparation steps differ very much in time and effort. Most of them like the database migration and
the SAP BW upgrade, but also the Unicode conversion should be set up as separate projects.
In the Migration Planning Workshop a mandatory check has been performed to identify which
requirements are still open before the system conversion to SAP BW/4HANA can be performed. All these
identified steps should either be performed here or in the activity Prep Steps & Data Model Adjustment in
the Explore phase.
Results
The system is now ready for Remote Conversion with the sender, receiver and control systems set up.
How SAP Can Support
On help.cap.com SAP offers the SAP BW/4HANA Master Guide as well as the Conversion Guide for SAP
BW/4HANA 1.0 (pdf) with detailed information on required preparation steps for the conversion to SAP
BW/4HANA and all required SAP notes. SAP supports customers with separate projects to run a database
migration or a SAP BW upgrade. These should be planned as sub projects to the transition to SAP
BW/4HANA.
Accelerators
• Conversion Guide for SAP BW/4HANA 1.0
• SAP BW/4HANA Master Guide
• SAP Note 2383530: Conversion from SAP BW to SAP BW/4HANA
• ABAP Syntax corrections in case involved data structures or function modules have changed
or were removed (user exit for authorization check has been converted into a BadI)
• Syntax corrections to avoid data inconsistencies (e.g. missing ‘order by’ with HANA DB could
cause unexpected results when data is processed in internal tables)
• HANA-optimized programming to achieve quick wins from performance perspective and to fulfill
performance KPIs.
SAP Standard tools like ATC (ABAP Test Cockpit or formerly known as ABAP Code Inspector) are not
able to identify all custom code in BW systems as some custom code (e.g. in BW transformations) is
generated in the development package SAP and not in the customer name space.
Due to this reason there are additional tools required for analyzing all custom code in BW systems, which
are described in the SAP Note 2462639 - BW4SL – Interfaces and Customer-Specific ABAP
Development.
Procedure
• Run analysis tools to identify custom code which needs to be changed
• Identify transformation and other custom code which can be decommissioned before the SAP
BW/4HANA conversion takes place
Results
You have installed and run analysis tools for ABAP custom coding with the latest corrections.
In case more help is required to interpret the results of the analysis tools and get help in transforming the
ABAP code properly to achieve maximum benefit, SAP provides a service component, which is called
Custom Code Impact Analysis. For details see the activity Custom Code Impact Analysis in the Explore
phase.
Accelerators
• SAP Note 2462639 - BW4SL - Interfaces and Customer-Specific ABAP Development
• ABAP custom code adaption for SAP HANA – the efficient way
• Decommissioning with CCLM in Solution Manager SP12
• ABAP Test Cockpit
• Setup of the Usage & Procedure Logging
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
Procedure
Proceed as follows:
• Set up the Decommissioning Cockpit in SAP Solution Manager. Decommission unused
custom code as documented in the Accelerators section.
• Compare the list of used code (identified via UPL or business process documentation), with
the custom code inventory list. This helps you to identify code that is not in use.
Results
Unused custom code has been decommissioned.
Accelerators
• Decommissioning with CCLM in Solution Manager SP12
• Service Information – Service Components for Custom Code Management
Procedure
Proceed as follows:
Results
Existing custom code will be adjusted or improved and new ones will be created with the necessary quality
level.
Accelerators
• SAP Note 1847431 - SAP BW ABAP Routine Analyzer
Procedure
In the Prepare phase SAP Solution Manager is set up and configured.
Results
SAP Solution Manager has been set up for project work.
Procedure
• In case there is an SAP Solution Manager 7.2 available on premise, update to the latest
support pack.
• In case this release level is not available on premise, SAP offers SAP Solution Manager
also via Cloud Appliance Library (CAL), and use this SAP Solution Manager for project
support.
• The general sequence for the implementation of an SAP Solution Manager system is as
follows:
o You plan the implementation (such as scope, hardware and software requirements,
and release restrictions).
o You plan the system landscape for your use cases.
o You install the components of your SAP Solution Manager system.
o You configure your system.
o You set up the connection to the managed systems.
• Once SAP Solution Manager is set up, the following areas are key for project support:
o Solution Implementation – the identification, adaptation, and implementation of
new and enhanced business scenarios.
o Solution Documentation – centralized documentation repository ensuring the
relationship of business process definitions with technical configuration decisions.
o Change Control Management – synchronized deployment of application
configuration with integrated project control and quality management.
• SAP provides customers with a SAP Solution Manager toolset that supports customers in
implementation of the project standards for the purposes of the project or operations. It is
highly recommended to use the SAP Solution Manager Focused Build service solution.
Additional details can be found in the accelerator section. The SAP Solution Manager
Focused Build is available in SAP Solution Manager 7.1. However the training materials
refer to the functionality of 7.2.
Results
You have set up SAP Solution Manager, and configured for project support.
SAP can install SAP Solution Manager for you. The corresponding service offer is called “Implementation
of SAP Solution Manager for IT Operations”. Please ask your SAP contact (e.g. SAP Client Partner) for
more information. Alternatively consider using SAP Solution Manager from the Cloud Appliance Library
(CAL).
In addition, SAP supports this activity with the “SAP Solution Manager Starter Pack” service
component. The SAP Solution Manager Starter Pack is applicable when you need direct assistance with
the basic configuration and use of the SAP Solution Manager.
Accelerators
• Service Information - Value Assurance Foundation
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• SAP Digital Business Services (DBS) Delivery Infrastructure
• SAP CAL
• SAP CAL at SAP SCN
• Focused Build for SAP Solution Manager
• Implementation of SAP Solution Manager for IT Operations
2.12. Execution, Monitoring, and Controlling of Results
Description
The purpose of this deliverable is to execute the project management plan and control and monitor the
work defined in the project scope statement. Management plans developed during the project preparation
phase (see deliverable "Project Management Plan") guide the approach to management, execution, and
control of project activities. The project manager is responsible for ensuring that the management plans
are applied at the appropriate level of control.
Tasks
• Direct and Manage Project Execution
• Monitor and Control Project Activities
• Manage Issues, Risks and Changes
• Communicate Status and Progress to Project Stakeholders
Accelerators
• Project status report for SAP Activate / S/4HANA
Accelerators
• Backlog including Delta Requirements and Gaps.xlsx
Accelerators
• Backlog including Delta Requirements and Gaps.xlsx
Accelerators
• Change Request Log - template (Customer)
• Open Issues List Template.xls (Customer)
Tasks
• Prepare Organizational Change Management Roadmap
• Conduct OCM Workshop with Project Manager and all Project Workstreams Owners.
Accelerators
• Organizational Change Management Guide (Customer)
Accelerators
• OCM Roadmap Presentation Sample (Customer)
2.13.2. Conduct OCM Workshop with Project Manager and all Project Workstream Owners
Objective
The purpose of this workshop is to align with the entire project management team regarding OCM
activities to be conducted. The OCM roadmap, along with the stakeholder analysis on hand at this stage
should be shared. An initial communication strategy should be drafted as part of this workshop.
• Ensure that all required deliverables from this phase and the project are complete and accurate,
and close any outstanding issues
• Identify lessons learned during the phase to prepare for formal phase closure
• Capture customer feedback and potential Customer References
Tasks
• Conduct Knowledge Management Gate
• Conduct Project Quality Gate
• Conduct Project Management Review Service
• Obtain Customer Sign-Off for Phase Completion
2.14.1. Conduct Knowledge Management Gate
Objective
The purpose of this task is to collect knowledge assets and lessons learned at the end of each phase of
the project that can be reused later by other projects. Collecting documents, experiences, project
highlights and lessons learned throughout the duration of the project can help to facilitate the project by
providing quick access and insights into key deliverables from earlier stages of the project.
Accelerators
• Lessons Learned Guide (Customer)
• Lessons Learned Template (Customer)
The purpose of this task is to conduct regular quality checks at defined or critical stages of the project
lifecycle to assess the health of the project:
The deliverables assessed at each quality gate will be performed using the quality gate checklist /PtD
System with defined expectations to the maturity of particular project deliverables /aspects.
Note: New additional key deliverables need to be added in the quality gate checklist by the Project
Manager to the different project types.
Accelerators
• QGateChecklist Concept SAP Activate
• QGateChecklist Template Introduction
• Quality Built In New QGate Checklist
Accelerators
• Phase Sign-Off Template (Customer)
3. Explore Phase
Once the Prepare phase has been finalized considering a detailed planning for the functional and
technical work streams, the Explore phase will be kicked off.
In the Application: Solution Adoption work stream, the training strategy is developed for the end users.
In the Application: Design & Configuration work stream, the Data Model Adjustment takes place and
the data/object transformation process coming in the Realize Phase is prepared. Especially for New
Implementation scenarios customers should attend the BW/4HANA Enablement service to get familiar
with the BW/4HANA concept and functionality, but also for conversion scenarios to learn how to use the
conversion tools. In the Data Volume Planning and Data Volume Design activities a scoping for data
volume management (DVM) is defined and the strategy for DVM is developed which will be executed in
the Realize phase. Security Design should be done in this phase, too.
The conversion to SAP BW/4HANA may impact your custom code. In the Custom Code Extensions
work stream, you will need to identify and prioritize affected custom objects that are used productively,
and that have to be adjusted as part of the system conversion project.
Based on the anticipated application changes customers should also start creating a strategy for testing
and end user training (Application: Testing work stream).
Analytics: The Analytics work stream contains the Analytics Design, offering the Analytics Design
Workshop which helps to create a detailed road map and blueprint, and explains the new data models in
BW/4HANA to enable the customer to start with the data model adjustment.
In the System & Data Migration work stream, customers will need to further prepare the platform for
project delivery. This touches SAP Solution Manager, and additional components depending on the
implementation scenario. A sandbox can be created for technical and functional experience gathering. Of
course, it depends on the scenario how the sandbox is created. In case of a new implementation or a
landscape transformation, data load needs to be prepared and planned as well. At the end of the Explore
phase the DEV environment needs to be set up (again scenario specific).
The technical design document is created in the Technical Architecture & Infrastructure work stream.
Transition to Operations runs an Operations Impact Analysis, to identify IT Support operational areas
that require adjustment to safely and efficiently operate the new system as of Go-Live. The actions taken
here depend on the SAP operational experience of the customer.
Phase Initiation
Description
The purpose of the phase initiation deliverable is to formally recognize that a new project phase starts.
Tasks
• Review Deliverables of Explore Phase
Tasks
• Update Project Management Plan
• Direct and Manage Project Execution
• Conduct SCRUM Meetings
• Monitor and Control Project Activities
• Manage Issues, Risks and Changes
• Communicate Status and Progress to Project Stakeholders
3. Sprint Demo
the purpose of this meeting is to demonstrate the results of the sprint to customer and obtain acceptance
to release the features developed during the sprint. The meeting is attended by Product Owner team, End
users and SCRUM team. It is conducted at the end of sprint.
4. Sprint Retrospective
or process improvement meeting is conducted right after Sprint Demo meeting prior to closing the sprint.
The objective of this meeting is for the SCRUM team to conduct retrospective of the sprint, identify
potential improvements of the process, prioritize and select top improvements to implement in the next
sprint.
Accelerators
• Agile Scrum Meeting Guidelines (Customer)
Accelerators
• Change Request Log - template (Customer)
• Open Issues List Template.xls (Customer)
3.2.6.Communicate Status and Progress to Project Stakeholders
Objective
The purpose of this task is to ensure that each contract is closed by verifying that all work specified in the
contractual arrangement was completed, and that all defined deliverables were accepted.
Accelerators
• Project status report for SAP Activate / S/4HANA
Planning
Description
The detailed project planning started in the Prepare phase, and is continued across the Explore phase.
The aim is to constantly adapt and refine the initial plan from the Prepare phase. In particular, the
implications from the Fit / Gap workshops need to be included in the project plan.
Procedure
• Refine Project Planning
Procedure
• Project management in the context of an SAP implementation has been documented in detail in
SAP Activate road maps (e.g. “SAP Activate methodology for Business Suite and On-Premise –
Agile”). See accelerator section for a link. All general project management activities, tasks, and
accelerators can be taken from there, by filtering on the Project Management work stream (see
accelerator section).
Please make sure to include the results from the ”Application: Design & Configuration” work stream so far.
Accelerators
• Explore phase of SAP Activate road map “SAP Activate methodology for Business Suite and On-
Premise – Agile”
Learning Design
Description
In this activity, the training requirements for key user and end users are analyzed and documented. Based
on the analysis, a training plan will be designed, and executed in the following project phases.
The project team has been enabled already, and is not in scope of this activity.
Procedure
• Develop a Training Concept
Results
A training concept has been developed for key users and end users.
Procedure
To develop a training concept for key users and end users, proceed as follows:
• Evaluate the business processes (including user interfaces) in scope for implementation, and
analyze the required skills.
• Evaluate SAP individual standard training from SAP Education courses (Classroom and Web-based
Trainings)
• Develop and document a training concept including obligatory and recommended training per user
role, mentoring, coaching, and in alignment with the project plan
• Per future role, assign users to trainings.
SAP recommends to establish a network of well-trained key users as part of the transition project.
Results
A training concept has been developed and documented.
Enablement Concept
• The enablement concept analyzes the current end user situation and clearly defines the high-level
training strategy. It is important to first understand the customer digital learning context and to define
methods to identify and create the learning content. The concept defines the scope, objectives,
deliverables, schedule, and benefits of the Solution Adoption work stream. Moreover, it includes the
process of identifying, developing and maintaining the required skills and Performance Support
Materials.
• The Enablement Analysis service component clarifies if current training capabilities are sufficient
for an effective training delivery, and makes necessary investment decisions transparent as early
as possible.
• A key user network is an essential method of knowledge transfer in digital transformations. Building
and managing a key user network will help to enable end users. In addition, the network may take
part in other important activities such as testing, change request management, and first level
support.
• The Enablement Analysis service component helps to establish a well-performing key user network.
• The essential step for creating knowledge transfer in transformation projects is the identification of
the learning requirements and the analysis of the digital learning opportunities for key user & end
user. Matching the results of the change impact analysis with the training needs will identify skill-
gaps for specific groups.
• The LNA as part of the Enabling Analysis identifies learning needs for the two groups, and comes
up with the required enablement portfolio.
Please note that the training of the key users and end users is not included in SAP Value Assurance, but
is handled separately by SAP Education.
Accelerators
• Service Information – Service Components for Functional Design
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
Organizational Change Management (OCM)
Description
The planning and execution of Organizational Change Management in the context of an SAP
implementation has been described in detail already. Most current information on Organizational Change
Management can be found in the road map “SAP Activate methodology for Business Suite and On-
Premise – Agile”. See the accelerator section for a link. In the context of SAP Activate, Organizational
Change Management is part of the “Solution Adoption” work stream (the Road Map Viewer offers to filter
on work stream names).
Procedure
• Execute Change Impact Analysis
Accelerators
• SAP Activate road map “SAP Activate methodology for Business Suite and On-Premise – Agile”
3.5.1.Execute Change Impact Analysis
Objective
The objective of this task is to execute an organizational change impact analysis.
Procedure
Execute a Change Impact Analysis as documented in SAP Activate.
Follow the link in the accelerator section, and run the analysis as described in the road map “SAP Activate
methodology for Business Suite and On-Premise – Agile”.
Accelerators
• Change Impact Analysis in the SAP Activate road map “SAP Activate methodology for Business
Suite and On-Premise – Agile”
Figure 3.2: Preparation Steps for the in-place and remote conversion
Procedure
• Use the Maintenance Planner to prepare the installation of the SAP BW/4HANA Starter Add-on
• Run the “Pre-Checks” (program RS_B4HANA_CONVERSION_CONTROL and Simplification List
for SAP BW/4HANA)
• Install SAP Notes for the installation of SAP BW/4HANA Add-On (if required)
• Run the Custom Code Check (see Activity Custom Code Impact Analysis)
Make yourself familiar with the new data model and concept in SAP BW/4HANA and the conversion tools
offered by SAP. A good starting point is the SAP First Guidance – complete functional scope (CFS) for
SAP BW/4HANA (see accelerator section).
Accelerators
• Service Information – Service Components for Analytics Design
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• SAP First Guidance – complete functional scope (CFS) for SAP BW/4HANA
• SAP Note 2432247 – SAP Best Practices for in-place system conversion for SAP BW/4HANA
(attached: Configuration Guide – Getting Started with Implementing the SAP Best Practices for in-
place system conversion for SAP BW/4HANA V1.10)
• Enablement Service for SAP BW/4HANA
3.4.1 Use the Maintenance Planner to prepare the installation of the SAP BW/4HANA Starter Add-on
Objective
Before the migration to the SAP BW/4HANA can be performed, the required software components have to
be downloaded in the Maintenance Planner.
Prerequisites
The decision to run an in-place system conversion to SAP BW/4HANA has been taken.
Procedure
1. Log on to the Maintenance Planner and select your SAP Backend System
2. Check that your system data is replicated to the Maintenance Planner (this might take a
few minutes)
3. Continue with the Maintenance Task: Select “Plan a Conversion to SAP BW/4HANA” and
select the listed add-ons as displayed in the screenshot. Confirm the selection.
Figure 3.3: Maintenance Planner with selection “Plan a Conversion to SAP BW/4HANA”
4. Add software details of your system, select SAP HANA database and the components
below.
5. Download the Stack XML and push the files to your Download Basket.
Note: If the needed software component SAP_ABA 75A was not selected by the Maintenance Planner, you
can also download the necessary files manually and add the files to the import queue.
For a step-by-step guide with screenshots see the blog “On the Road to BW/4HANA – second stage
finalized” in the accelerator section.
Results
When all files are in the import queue, you can continue with the technical migration to SAP BW/4HANA in
the Realize phase.
Accelerators
• SAP Note 2383530 – Conversion to BW/4HANA – Step by Step
• Maintenance Planner Information (Blogs.sap.com)
• Maintenance Planner (Support Portal)
Procedure
• Before installing the SAP BW/4HANA Starter Add-On, it is recommended to run the program
RS_B4HANA_CONVERSION_CONTROL in transaction SA38. The program checks the readiness
of your system for a BW/4HANA conversion with extensive checks and provides guidance for the
conversion project.
• The pre-check report determines which objects are not supported by SAP BW/4HANA,
automatically converted, deleted, or need manual adjustment. The pre-check then provides links to
the documentation of the corresponding Simplification List.
Accelerators
• SAP Note 2383530 - Conversion to SAP BW/4HANA - Step by Step Description
Based on the “Simplification List for SAP BW/4HANA”, SAP will provide information about the SAP
BW/4HANA related simplifications for each application/functional area and type of data warehousing
object. The Simplification List is a collection of individual “Simplification Items” that focus on what needs to
be considered throughout an implementation or system conversion project from SAP BW 7.0 or higher to
SAP BW/4HANA 1.0.
The simplification list supports customers in converting their system from SAP BW to SAP BW/4HANA
and adapt data models to SAP HANA-optimized object types.
Procedure
Check all relevant simplification items and perform the steps indicated in the related SAP Notes.
Results
When all relevant simplification items are processed and the readiness check report results are analyzed
and processed, the system is close to be ready for conversion.
Accelerators
Procedure
• If the SAP BW system is not on SP06, implement the following notes:
SAP Note 2330548 – SAP BW 7.5, edition for SAP HANA: Prepare Check (DataStaging)
SAP Note 2361350 – B4H mode: transport check for RS_B4HANA_CHECK_ENABLE
SAP Note 2369561 – RSPM migration (IOBJ, DEST): Missing checks when switching to BW/4HANA
mode
SAP Note 2375192 – B4H Mode: Add-on Name Changed
SAP Note 2383743 – IOBJ_PROP: MOVE_CAST exception in cl_rsd_iobj_prop_cache=>get_cha
SAP Note 2384110 – BW4HANA: RS_B4HANA_CHECK_ENABLE – the last checks (no new
checks/features will be implemented in this report anymore)
SAP Note 2424016 – SAP HANA processing: BW 7.50 with SP04 – SP07: SAP HANA analysis processes
and SAP HANA transformations
SAP Note 2403821 – Problems when creating DTPs extracting from Composite Providers
SAP Note 2404122 – Check for BW Upgrade to BW4HANA
SAP Note 2430579 – Support Package 5 for SAP NetWeaver BW 7.50 -> incorrect data
Once you are installing the SAP BW/4HANA Starter Add-on, the system is in compatibility mode
where existing scenarios can continue running but changes of legacy objects (like Virtual
InfoProvider) are forbidden. To modify a legacy object, you should add its technical name to the
whitelist. Please note that the whitelist will be ignored in B4H mode. Before switching to B4H
mode, you need to remodel your scenarios manually according to the suggestions above.
Results
SAP offers SAP Notes which give guidance for the handling and usage of the SAP BW/4HANA Starter
Add-on (SAP Note 2189708) and for prerequisites and installation (SAP Note 2246699). Refer to the
Accelerators section for details.
Accelerators
• SAP Note 2330548 – SAP BW 7.5, edition for SAP HANA: Prepare Check (DataStaging)
• SAP Note 2361350 – B4H mode: transport check for RS_B4HANA_CHECK_ENABLE
• SAP Note 2369561 – RSPM migration (IOBJ, DEST): Missing checks when switching to
BW/4HANA mode
• SAP Note 2375192 – B4H Mode: Add-on Name Changed
• SAP Note 2383743 – IOBJ_PROP: MOVE_CAST exception in cl_rsd_iobj_prop_cache=>get_cha
• SAP Note 2384110 – BW4HANA: RS_B4HANA_CHECK_ENABLE – the last checks (no new
checks/features will be implemented in this report anymore)
• SAP Note 2424016 – SAP HANA processing: BW 7.50 with SP04 – SP07: SAP HANA analysis
processes and SAP HANA transformations
• SAP Note 2403821 – Problems when creating DTPs extracting from Composite Providers
• SAP Note 2404122 – Check for BW Upgrade to BW4HANA
• SAP Note 2430579 – Support Package 5 for SAP NetWeaver BW 7.50 -> incorrect data
• SAP Note 2189708 – SAP BW/4HANA Starter Add-On -Handling and Usage
• SAP Note 2246699 – SAP BW/4HANA Starter Add-On – Pre-Req/Installation/De-
Installation/Update
• SAP Note 2011192 – Uninstalling ABAP add-ons
• SAP Note 2378346 – Errors when preparing Add-On Installations / Upgrades in Add-On
Installation Tool (SAINT) Version 0063
3.4.5. Familiarize with the Data Model Adjustment for the In-Place System Conversion
Prerequisites
All preparation steps are defined and planned during the Migration Planning Workshop and the
Analytics Design Workshop.
Objective
In this task, the customer should make himself familiar with the conversion procedure from the classical
objects to the SAP HANA-optimized objects.
Procedure
• Perform all identified preparation steps
• Implement the required SAP Notes with the SAP Note Analyzer (refer to SAP Note 2383530 –
Conversion to SAP BW/4HANA – Step by Step Description)
• Familiarize with the object conversion process
After you have installed the SAP BW/4HANA Starter Add-on in the Realize phase, a number of preliminary
tasks have to be performed to prepare the switch to the so called ‘compatibility mode’ which then allows
only the usage of SAP HANA-optimized object types.
Existing classic objects types (like InfoCubes, classic DSOs) need to be transformed to a SAP HANA-
optimized object type (e.g. aDSO). In the Transfer Cockpit, which is delivered with the Starter Add-on -
transaction RSB4HTRF - you can transfer InfoCubes, DataStore objects (classic) and HybridProviders to
DataStore objects (advanced). InfoCubes with non-cumulative key figures are transferred to DataStore
objects (advanced) with non-cumulative key figures. MultiProviders and ad hoc CompositeProviders are
transferred to central CompositeProviders.
After the BW data model is cleaned up and all classic objects types have been converted or removed, the
compatibility mode can be switched on. From now on you can only use SAP HANA-optimized object
types.
The queries on HybridProviders and all other converted InfoProviders are transformed. If the InfoProvider
is created as a copy, the queries are also copied. If the names are identical, the queries remain
unchanged. Queries that use 0INFOPROV are adjusted. The objects are copied without data.
Figure 3.4: Classical objects and their HANA-optimized object types
SAP provides the Transfer Cockpit - transaction RSB4HTRF – to automate the transfer of the listed
objects.
Transferring Queries
• Queries are transferred to the new providers with their original name plus the prefix /B4H/. If naming
conflicts occur, a unique ending is added.
• Queries with the following properties are displayed in the definition but are not transferred:
o If variables are used on formulas or text variables
o If variables are used on InfoObjects that are not contained in the provider
BW Workspace objects
Results
You are familiar with the object conversion process.
Accelerators
Procedure
• Perform data volume planning
• Define data volume strategy
• Data volume reporting (will be done in the Realize phase to prepare the cleanup/archiving)
Results
Road map that defines the exact scope of the data volume management activities, like data deletion or
archiving, and implementation of data volume reporting.
Accelerators
• Service Information – Service Components for Safeguarding the Digital Transformation
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
Procedure
A detailed look at the system identifies the major pain points and gives an outlook on the most beneficial
measures to take (for example, deletion or data archiving) when implementing a data volume strategy. In
some cases, the implementation of an enhanced data volume reporting may be the most reasonable first
step to take in case the data on the system is still young and therefore the expected effect of a data
volume strategy may be small. One central tool supporting data volume reduction is the SAP DVM Work
center in SAP Solution Manager, including tools with a special focus on SAP HANA.
• Guided Self Service: You can generate a best practice document to determine data
that can be reduced most efficiently in an SAP system before the conversion. You
can use the same tool after the conversion to develop a blueprint for a DVM strategy.
• Reorganization and Compression: You can use this tool without a SAP HANA context
Results
A decision and road map on how to proceed with DVM upfront of a transition to SAP BW/4HANA.
Accelerators
• Service Information – Service Components for Functional Design
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
Data Volume Design
Description
Data volume design is the follow-up of data volume planning. It should support the implementation of a data
management and data archiving strategy or alternatively supports the assessment of existing strategies.
Requirements and Constraints
This activity is of general interest for all scenarios.
Based on the analysis results from the data volume planning, the blueprint of a data management and
archiving strategy is developed from a technical point of view and using general SAP best practices. In the
second phase, the data volume strategy is realized.
Procedure
• determine the type and amount of data that can be archived, as well as the corresponding archiving
objects
• reveal connections between tables and archiving objects
• provide information on which archiving objects should be used, in which order and frequency
• consider retention periods as well as the requirements of your business teams
• maintain the customizing for the archiving objects and the definition of archiving selection variants
• test archiving of some documents to demonstrate the retrieval of archived data
Results
There is a documented and implemented strategy on Data Volume Management.
• Data avoidance
• Data summarization
• Data deletion
• Data archiving
During the test archiving as preparation for Go-Live, the service also offers assistance, if help is required
on performing mass tests and performance tests.
Accelerators
• Service Information – Service Components for Safeguarding the Digital Transformation
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
Security Design
Description
SAP BW/4HANA uses the user administration and authentication mechanisms from the Application Server
for ABAP. The security recommendations and guidelines for user administration and authentication
described in the Security Guide for SAP NetWeaver Application Server for ABAP therefore also apply
to SAP BW/4HANA. In addition to these guidelines, SAP provides information about user administration
and authentication that specifically applies to SAP BW/4HANA.
The SAP BW/4HANA conversion project involves many areas of the SAP BW due to its technical
complexity. This results in a comparably large involvement of business users and IT users during the
project. IT users are responsible for all IT administration and remodeling task which will mainly arise
during the project and business users will be affected by necessary testing activities after changes
occurred. The use of the Transfer Cockpit in productive systems could require special alignment between
business users who are owners of business processes and their data and the IT users responsible for
transferring the data flow including the inherent data to new SAP BW/4HANA supported objects. During
the scope transfer of a dataflow/unsupported BW objects the data of the involved InfoProviders needs to
be accessed. For a period of time the authorizations to access the InfoProviders data must be assigned to
the executing user of the Transfer Cockpit.
Procedure
Supply the affected data owners with the authorization for the Transfer Cockpit and execute the tested
and prepared Transfer Cockpit scenario in the productive environment.
Procedure
After the SAP BW/4HANA Conversion authorization objects need to be adjusted, for more information
please check SAP Note 2468657 BW4SL Standard Authorizations which contains a list with SAP BW
authorization objects and their availability in SAP BW/4HANA.
Results
You are able to implement SAP BW analysis authorizations and SAP HANA analytics privileges.
Prerequisites
Ideally, an analytics strategy workshop has already been conducted to define the strategic SAP solution
components for analytics, resulting in a target analytics architecture. Alternatively, the customer has
already conducted similar activities to get familiar with strategic SAP analytics solution components
around SAP S/4HANA embedded analytics, enterprise data warehousing (SAP BW based or SAP HANA
based), and the BI strategy (SAP Analytics Cloud, SAP Digital Boardroom, and SAP BusinessObjects BI
platform), and defined a strategic analytics infrastructure.
Procedure
• The outcome of the Analytics Strategy Workshop and the Migration Planning Workshop should
be a high-level architecture for the target solution landscape and a filled checklist of the mandatory
preparation steps for the system conversion. Based on these outcomes, the detailed roadmap and
the detailed project plan should be created.
• Customer should be empowered to understand all aspects of the data model transformation to SAP
BW/4HANA
• Model a blueprint for the target architecture with integration of BW and HANA models
Results
The target architecture has been defined and a detailed project plan is available. The customer is
prepared to perform the preparation steps and start the actual configuration of the data models for the
system conversion (activity Prep Steps and Data Model Adjustment).
The Analytics Design Workshop ideally refers to the results of the Analytics Strategy Workshop and a
Migration Planning Workshop. A scoping process prior to the workshop helps to tailor the service to the
customer requirements.
Accelerators
• Service Information – Service Components for Analytics Design
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
A first analysis of the custom code situation should have been done in the Prepare phase already.
Procedure
1. Run a custom Code check an perform Adoption
Results
Custom code is checked and issues are solved.
SAP BW-specific customer enhancements (often called "customer exits", transaction CMOD) are not
available in SAP BW/4HANA. For several SAP BW releases, SAP has offered corresponding
enhancement spots. If customer enhancements are used in SAP BW, the code will have to be adjusted
and converted to enhancement spots in SAP BW/4HANA.
Procedure
Check SAP Note 2462639 BW4SL Interfaces and Customer-Specific ABAP Development and analyze
your custom coding with the according tools provided. Solve all issues identified by the analysis. The
Transfer Cockpit will later on again execute checks, offer support and prompt you to acknowledge that any
findings were adjusted accordingly.
Accelerators
• Service Information – Service Components for Custom Code Management
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• ABAP custom code adaptation for SAP HANA – The efficient way
• SAP Note 2462639 – BW4SL – Interface and Customer-Specific ABAP Development
• SAP Note 1909597 - SAP BW Migration Cockpit for SAP HANA
Test Planning
Description
To minimize the number of issues during or after Go-Live, it is critical to manage the quality of the solution.
As a part of any scheduled maintenance event, it is necessary to consider and plan the testing cycles
required to mitigate production support issues. At this phase of a system conversion project, it is
necessary to evaluate the existing test and quality management processes and procedures that could be
leveraged to support the project.
The following key elements of the test planning must be documented in the test strategy:
• Test Scope
• Types of Testing, e.g.
o Unit Testing
o Business Process (String) Testing
o Integration testing
o Data Conversion Testing
o User Acceptance Testing
• Testing Approach
o Description, how different test types relate to each other, e.g. successful unit test is a pre-
requisite for doing a string test or migration test results might lead into a pre-requisite for a user
acceptance testing
• Test Automation
• Testing Tools
o Which tools will be used to perform different tests (e.g. SAP Solution Manager)
• Defect Management
o Description of how defects will be documented (e.g. Test Workbench in SAP Solution Manager)
Procedure
1. Make yourself familiar with the tools in test management, and set up test management in SAP
Solution Manager
2. Test Scope Determination
3. Detailed Test Planning
Accelerators
• Service Information – Service Components for Functional Design
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• SAP Support Standard for Test Management
• SAP Solution Manager WIKI - Test Suite
• SAP Rapid Deployment for ALM Wave Test Management
3.12.1. Set Up Test Management in SAP Solution Manager
The goal of this task is to make you familiar with the test tools in SAP Solution Manager, and their setup.
Some EGI sessions that help you set up Test Management in SAP Solution Manager are listed in the
accelerator section.
Accelerators
• Test Management I: SAP Test Workbench
• Test Management II: Business Process Change Analyzer
Prerequisites
Test and quality management processes and procedures should already be in place.
Procedure
• Evaluate the existing process and procedures to determine the different testing cycles required to
support the project.
• Utilize the existing process and procedures to guide the decision making process on how to
determine the applicable test cases and test scripts. As a best practice to compile test cases and
test scripts, it is recommended to define business critical transactions/reports, evaluate most
frequently used transactions/reports, and analyze prior productions support issues.
• In particular for new implementation: Determine the overall test data approach by aligning with the
overall data migration approach. The test data approach will be documented as part of the testing
strategy.
• Document your findings in a test strategy document, and store it centrally in SAP Solution Manager
Results
As a result, a test strategy, and a defined set of test cycles, test cases, and test scripts in scope to support
the conversion project are created.
The focus is to determine which of the testing cycles (e.g. functional, scenario, integration, regression,
user acceptance, performance, and/or cutover) are required to fulfill the quality gate criteria of the Realize
phase. Furthermore the start date, duration, criteria, and resources for each of the required testing cycles
needs to be planned.
Procedure
• Evaluate and enable test management and test automation tools to support the testing cycles.
• Execute the tasks within this activity utilizing the SAP Application Lifecycle Management Best
Practices for Test Management. Tailor the templates for Test Strategy, and the high-level Functional
Test Plan to your needs.
• Create a detailed testing plan that is integrated with the project plan and aligned with the overall
SAP Software Change Management strategy. The plan should support the objective of mitigating
risk both to the end-state solution and the cutover process required to position the end-state.
Accelerators
• Test Strategy Template
• Functional Test Plan Template
• SAP Test Management Best Practice
Sandbox System Setup
Description
The purpose of this task is to set up the sandbox system either as a SAP Cloud Appliance installation or
on premise.
Procedure
Install a software appliance for project jump-starts.
The appliance can be consumed in two ways:
1. Hosted in the cloud: Customers can access the appliance via the SAP Cloud Appliance Library (SAP
CAL, https://cal.sap.com) in a pay-per-use model hosted on Amazon Web Services (AWS). When using
the SAP CAL option, the customer can choose between a 30-day trial and a longer-lasting engagement.
With the trial, only AWS hosting fees need to be paid by the customer. If the customer opts to go beyond
the 30-day limit, an SAP CAL subscription license and a regular SAP BW/4HANA license is required.
2. Installed on-premise: If customers/partners prefer an on-site installation on their own hardware, they
can order a Blu-Ray disc from SAP and unpack the appliance from the Blu-Ray. A regular SAP
BW/4HANA license is required. See also activity Provide a Trial System in the Discover phase, and the
task Define Cutover Approach in the Prepare phase.
Results
The sandbox system is set up.
Data Migration Design for Remote Conversion
Description
As a preparation of the Remote Conversion Execution Service it is mandatory to run a Data Migration
Assessment (Remote Conversion Assessment) in the Explore phase to set the scene for the data
transfer from the old BW system to the SAP BW/4HANA which will be installed as new implementation.
The findings of the assessment have to be taken into consideration to close the gaps before the data
migration into the new system can take place.
The Assessment is the starting point for planning and preparing the Remote Conversion. The graphic
displays the detailed steps from planning to go-live of a Remote Conversion.
Procedure
• Perform the Data Migration Assessment for the Remote conversion
• Perform the Preparation steps and prepare the data model adjustment for the Remote conversion
• In case of a remote conversion including SAP BPC, perform the migration of SAP BPC relevant
data
Key Objectives of the Service: Helping in the preparation of the remote conversion with Remote
Conversion Execution for SAP BW/4HANAService
• Check of the sender system and preparation activities (like Transfer Cockpit and software
installation)
• Identify and tailor the scope
• Feasibility check of the planned transition
• Creation of a WBS and define responsibilities
• Project Planning: Planning of the execution cycles and Go-live
• Creation of an effort estimation
• BW HANA Checklist
Implement (in development and transport up to production or a recent copy of production) SAP
Note 1729988 - SAP BW powered by SAP HANA and SAP BW/4HANA - Checklist Tool , execute
and provide the results of this Note
• Sizing Report
Implement (in development and transport up to production or a recent copy of production) the
latest version of
SAP Note 2296290 - New Sizing Report for BW/4HANA, execute and provide the results of this
note.
Accelerators
• Service Information – Service Components for Data Migration Design
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• SAP Note 2383530 - Conversion to SAP BW/4HANA - Step by Step Description
• SAP Note 1729988 - SAP BW powered by SAP HANA and SAP BW/4HANA - Checklist Tool
• SAP Note 1909597 - SAP BW Migration Cockpit for SAP HANA
• Remote Conversion Execution for SAP BW/4HANA
3.14.2. Perform the Preparation Steps and prepare the Data Model Adjustment for the Remote
Conversion
Objective
If the customer performs a remote conversion to SAP BW/4HANA, he may want to transport certain
configuration and data models from the existing landscape to SAP BW/4HANA. This is only supported for
the initial system setup, not for continuously updating the new landscape. The BW/4HANA Conversion
Cockpit enables the migration of objects and dataflows on SAP BW7.3 or higher and not 3.x.
Analyze in this step what the status of the objects in the existing landscape is and which steps have to be
performed to convert them to BW/4HANA compatible objects.
Procedure
• Make use of the outcome of the Data Migration Assessment and define the steps which have to
be taken to fulfill all requirements for the data transfer.
• Perform the required prep steps
• Execute tools from the Transfer Cockpit (BW/4 Migration Cockpit or the BW/4 Checklists described
in SAP Note 2383530 – Conversion to SAP BW/4HANA – Step by Step Description)
• Execute report RS_B4HANA_CONVERSION_CONTROL
• Check the Simplification List for SAP BW/4HANA (SAP Note 2421930)
•
The transfer of the objects is supported by the SAP Professional Service offering Remote System
Conversion to SAP BW/4HANA. For a detailed description refer to the activity Data Migration &
Verification in the Realize phase.
Accelerators
• 1909597 - SAP BW Migration Cockpit for SAP HANA
• SAP Note 2383530 - Conversion to SAP BW/4HANA - Step by Step Description
3.14.3. Perform the Migration of Data relevant for SAP BPC
Objective
If the customer performs a remote conversion to SAP BW/4HANA with SAP BPC 11.0, he may want to
transport certain configuration and data models from the existing landscape to SAP BW/4HANA.
Procedure
In case of a remote conversion of BPC Standard Model to BPC 11.0 powered by BW/4HANA, it is
necessary to use the backup & restore tool UJBR (see Conversion Guide SAP BPC 11.0).
In case of a remote conversion of BPC Embedded Model to BPC 11.0 powered by BW/4HANA, the
procedure is identical to the conversion of other BW objects.
See in task Perform the Preparation Steps and prepare the Data Model Adjustment for the Remote
Conversion, usage of the Transfer Cockpit.
Accelerators
DEV Setup
Description
Before configuration and development work starts in the Realize phase, the development system (DEV)
needs to be set up.
There is a technical design document stored in SAP Solution Manager which includes the technical
deployment plan, and the software components which need to be installed / updated.
Procedure
• DEV Setup or re-use of Sandbox environment
• Install the SAP BW/4HANA Basis Content Add-on and the SAP BW/4HANA Content Add-on
Results
The Dev system is installed and set up with the content add-ons.
Procedure
Proceed as follows:
• Decide if the sandbox environment should be re-used as the DEV environment. In this case no
additional system installation is required. When having used the virtual appliance as sandbox
environment, a client that is ”ready-to-activate” is already in place and can be used.
Please note: A sandbox which has been set up by using the SAP BluRays, and which is used as a
DEV system afterwards may have activated business functionality which is subject to additional
licensing.
• Execute the technical installation of the required SAP Products for DEV environment as
documented in the technical design document.
Results
Finally the DEV environment is ready for configuration.
• Installation of an SAP HANA System and SAP BW/4HANA system in the development environment
• Basic configuration of SAP HANA and SAP BW/4HANA development system
• Replication of global settings and exchange rates
• Implementation of ODP 2.0 if basis level component in ECC source system is appropriate
(SAP_BASIS >=730)
• Basic configuration in order to connect one SAP ECC source system
• Activate FI or CP: Activation of one content area from FI or CO from the business content.
• Activate SD/MM (no Cockpit): Activation of one content area from MM or SD from the business
content, if LO Cockpit is already configured in source system.
• Activate SD/MM and LO Cockpit: Activation of one content area from MM or SD from the business
content. LO Cockpit configuration for one area from MM or SD.
• ODP 1.0 Framework: Implementation of ODP 1.0 if SAP BASIS level in source system is <730.
The activation of the business content can be done in the activity “Configuration” in the Realize phase.
Accelerators
• SAP Note 2393067 – Installation Note
• SAP Note 2400585 – Collective Note & FAQ: SAP BW/4HANA Content (BW4CONT &
BW4CONTB)
• Implementation Service for SAP BW/4HANA
Sizing
Description
Run a capacity estimation on the required hardware for application server and databases (CPU, RAM,
storage, network).
Timing:
• Explore phase (non-production systems), realize phase (production and production-like systems)
There is an implementation plan available which provides first information about the target solution.
Procedure
• Perform / Check Sizing
Results
There is a documented estimate on the required hardware, which can be discussed with the hardware
vendor.
Procedure
• An initial sizing should have been provided either as part of the “Technical Architecture Workshop”,
or as part of the “Migration Planning Workshop” in the Prepare phase.
• In case initial sizing has not been done so far or needs to be updated, you should follow the sizing
procedures documented in the SAP note 1793345 “Sizing for SAP Suite on HANA” (see accelerator
section).
• For new implementation, initial sizing is performed in the Quicksizer tool in SAP Service
Marketplace (see “General Information on Sizing” in the accelerator section).
• Run this activity for all related infrastructure components (e.g. including Front End Server).
• In case of an in-place or remote conversion, the sizing report should be executed periodically in the
productive system throughout the project to check on the growth of the source system.
• For a Shell conversion it is mandatory to check the sizing report of the source system and manually
calculate the sizing considering the objects that will be transferred to the new system.
Results
A sizing has been performed and is documented.
How SAP Can Support
SAP can perform this task with the “Advanced Sizing” service component. The service component fits to
all three on-premise transition scenarios, and can be also extended to capacity management requirements
of very large systems including aspects like data avoidance strategies, data tiering, or landscape
scalability.
SAP Enterprise Support customers can also listen to the Meet the Expert recording “Guided Sizing for
SAP HANA”. This session gives an overview about the current knowledge on SAP HANA sizing and the
principles on how to size SAP HANA in a Greenfield and migration situation.
Accelerators
• Service Information – Service Components for Platform Design
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• General Information on Sizing
• Proactive Performance and Capacity Management - Best-Practice Document
• Sizing Approaches for SAP HANA (incl. SAP S/4HANA and Fiori) – Lessons Learned Document
• SAP ES - Guided Sizing for SAP HANA
3.16.2. Perform Sizing for SAP BPC 11.0
Objective
The objective of this task is to either perform a sizing, or in case a first estimate has been provided already
check the initial sizing.
Procedure
The sizing for BPC needs to be performed on top of the BW sizing. The approach is different depending
on the BPC Model and the conversion type.
For an initial sizing of BPC Standard Model, the paper-based sizing guide for BPC needs to be consulted.
An initial sizing for BPC Embedded model is performed with the help of the SAP Quicksizer for
BW/4HANA.
BPC sizing in case of system conversion is usually done with the help of the report
/SDF/HANA_BW_SIZING.
SAP can perform this task with the “Advanced Sizing” service component, which is part of the “Platform
Design” service.
Accelerators
• SAP Note 2296290 – New Sizing Report for SAP BW/4HANA
• Sizing guide for SAP BPC
• SAP Quicksizer
• SAP Note 2363248 - SAP BW/4HANA Hardware Sizing
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• Service Information – Service Components for Platform Design
There is an implementation plan available which provides first information about the target solution.
Procedure
• Discover Technical Boundary Conditions
• Create Technical Solution Map
Results
As a result, there is a documented technical solution map available in SAP Solution Manager.
Accelerators
• Service Information – Service Components for Platform Design
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
Procedure
The Technical Boundary Conditions in scope are:
All information needs to be stored in the Project Management space of SAP Solution Manager for central
access.
• Collect the amount, size and purpose of the planned non-production systems per SAP system. Align
the plan with the implemented software change management strategy.
• The information can be derived from the existing software change management model.
Alternatively, design a new software change management model according to SAP Best Practices.
• Timing: Explore phase or early Realize phase.
DC Strategy
Availability Requirements
Accelerators
• Best Practice Document - Change Management: Elements of a Software Change Management
Strategy
• White Paper - Storage Architecture in SAP HANA Tailored Datacenter Integration (TDI) Landscapes
• Best Practice - Enterprise Storage Architecture
• Check List - Configuration and Maintenance of the Storage Infrastructure
• Best Practice - Business Continuity Management for SAP Landscapes
• Maintenance Planner and Maintenance Optimizer
Prerequisites
The technical boundary conditions have been documented.
Procedure
Proceed as follows:
Results
There is a technical solution map of the target architecture available in SAP Solution Manager.
Accelerators
• Technical Solution Map Template
IT Infrastructure Definition
Description
Within the IT Infrastructure definition phase customers need to create a detailed technical platform design.
This includes the selection of hardware vendors for servers and storage, mapping of technical
components, network design and also the definition of cloud integration options.
Procedure
1. Decide on Integration with Cloud Applications
2. Hardware Selection and Utilization
3. Develop Virtualization Strategy
4. Design Network
5. Test Preparation
Results
As a result, there is a documented IT infrastructure definition available in SAP Solution Manager.
Accelerators
• Service Information – Service Components for Platform Design
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
3.18.1. Decide on Integration with Cloud Applications and SAP Analytics Cloud
Objective
The objective of this task is to decide on the integration with cloud applications and SAP Analytics Cloud.
SAP Analytics Cloud combines business intelligence, planning and predictive analytics into one cloud
solution that is entirely based on the SAP Cloud platform. The Software-as-a-Service (SaaS) solution
provides access to all the possible data so that the user can visualize, plan and predict using real-time
data. SAP Analytics Cloud is a foundation of a real-time steering in the digital age. It allows to integrate all
internal and external data sources in only one solution.
Figure 3.9: Data Connections Environment
Procedure
In case cloud applications are in scope as well for the implementation project, backend integration with
these have to be discussed. For instance, available bandwidth, peak times, availability requirements and
recovery procedures might be a limiting factor here.
Decide if SAP BW/4HANA should be connected to SAP Analytics Cloud via import data connection or live
data connection – refer to the guided playlist for SAP Analytics Cloud “Connections Overview” for details
(see accelerator section).
Results
As a result, a technical architecture for the integration of on-premise and cloud-solutions has to be
created.
Accelerators
• SAP Analytics Cloud (Public)
• SAP Analytics Cloud "Introduction to Connection" (Public)
Prerequisites
As a prerequisite, the sizing results including the software change management landscape has to be
mapped to possible hardware and/ or virtual container sizes.
Procedure
An assessment of different hardware vendors and products is recommended. For instance, different
server models might be extendable or not which could be an important factor depending on the capacity
growth requirements.
The hardware requirements have to be mapped to project phases afterwards and planned together with
the hardware vendor.
Results
As a result, there is a documented deployment plan which includes the definition of the hardware
Procedure
Especially for the SAP application layer, virtualization is an interesting option to enhance agility and
adaptability and to provide a “cloud-like” behavior. For instance, virtual instances of additional application
servers can be created on the fly to overcome temporary load peaks, system images can be moved to a
more powerful hardware dynamically and so on.
To fulfill this task, an overview about available virtualization products and the respective capabilities is
required. Boundary conditions, limitations, typical use cases and similar should be collected to check if
these are matching the requirements. In addition, tools like the SAP Landscape Virtualization
Management (LVM) should be evaluated. The picture below shows some examples of boundary
conditions for SAP application server.
Results
As a result, a general technical architecture of the new systems in virtualized environments has to be
created/ adapted. In addition, general technical configuration rules for the SAP S/4 HANA have to be
considered.
Sizing rules for LAN and WAN segments have to be applied. In case of limited bandwidth or high latency,
WAN acceleration solutions have to be considered.
Results
As a result there is a network design document stored in SAP Solution Manager.
Prerequisites
The target technical architecture has been designed and documented.
Procedure
Prepare test cases for:
Results
As a result, as test plan including a timeline and test case description has been created.
Technical Design
Description
This task is recommended for all implementation scenarios.
The technical architecture, and the IT infrastructure has been designed and documented.
Procedure
The technical design is documented in a technical solution design document. It is usually developed in a
series of workshops and post-processing work, and covers the following aspects:
• Technical components
• Scalability and load balancing concept
• Backup concept
• HA/DR concept
• Technical architecture for non-production systems
• Production system deployment plan
• Expert sizing & scalability verification
• Technical architecture for production systems
• Technical infrastructure
• Deployment patterns and deployment plans
• DC integration
• 3rd party integration
The aspects have dependencies to each other, and to the boundary conditions. Some of them need to be
considered iteratively.
The Technical Architecture Workshop (see activity Technical Architecture in the Discover phase) should
have touched many of the aspects from above).
The technical solution design is created in this activity, and continuously updated in later phases of the
project (e.g. Sizing Verification in the Realize phase).
Results
A technical solution design document is available in SAP Solution Manager for central access.
Procedure
Take the appropriate “Technical Solution Design Template” from the accelerator section, and tailor it to
your project requirements.
Technical components: Determination of required technical components for the SAP solution, and their
deployment options.
Procedure
• Based on the technical applications specified in the Technical Solution Map, document which
installable technical components are required.
• Distinguish non-production and production systems, as well as required and optional components.
• Timing: Explore phase (non-prod), Realize phase (prod).
Scalability and load balancing concept: Determine how applications in the SAP solution can grow from
workload & data footprint perspective.
Procedure
• Document how each technical component can scale (scale up and/or scale out via multiple
instances).
• Document data scalability solutions (for large systems).
• Document how to balance workload between multiple instances of the same technical component.
• Timing: Realize phase (since typically required for production).
Backup concept: Definition of the backup infrastructure and backup execution strategy for each
persistency type.
Procedure
HA/DR concept: Definition of the technical architecture for high availability (SPOF protection) and
disaster recovery (data protection, recovery procedures).
Procedure
• For each “availability class” in the SLA, determine the required technical architecture for each
technical component.
• Describe related IT infrastructure requirements.
• Describe assumptions & boundary conditions.
• Timing: Realize phase.
Technical architecture for non-production systems: Determination of technical deployment and setup
of non-production systems (DEV, QAS; Typically simpler architecture than PRD).
Procedure
Production system deployment plan: Determine the amount and, for global customers and complex
solutions, regional distribution of systems.
Procedure
• Number of production systems (SIDs): Is more than one production system required (per
component)?
• Options to co-deploy applications: Can/should certain applications be co-deployed on one platform?
• Timing: Realize phase.
Technical architecture for production systems: Determination of technical deployment and setup of
production and production-like systems.
Procedure
Technical infrastructure: Description of hardware requirements and the selected hardware to implement
them.
Procedure
• Determine the selected technical server platform (server hardware, OS & virtualization type).
• Determine the storage infrastructure and its scalability concept.
• Determine the (high-level) network architecture.
• Timing: Explore phase (non-prod), Realize phase (prod)
Procedure
DC integration: Specification of the integration of the SAP solution into data centers.
Procedure
3rd party integration: Specification of the technical integration of the SAP solution with non-SAP / legacy
systems.
Procedure
• Description of the high-level technical integration architecture between the SAP solution and non-
SAP / legacy systems or components.
• Description of non-functional requirements (performance, availability) of the technical interfaces.
• Timing: Realize phase
Results
As a result a technical solution design is documented and stored in SAP Solution Manager for central
access.
Accelerators
• Service Information – Service Components for Platform Design
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• Best Practices - SAP Productive System Strategy for Large Enterprises
• Best Practices - Technical Deployment Options for SAP Systems with SAP HANA
• Check List - High Availability and Disaster Recovery Implementation for SAP Systems
• Best Practices - SAP System Landscapes on Virtualization and Cloud Infrastructures
• Technical Solution Blueprint – Template for Small Customer
• Technical Solution Blueprint – Template for Large Customer
Operations Impact Evaluation
Description
With the introduction of a new product like SAP BW/4HANA, the current IT support framework will change.
The impact of the new product on the support framework may vary on the scenario. Example scenarios
include the following:
• On-premise solution
IT is responsible for the entire SAP BW/4HANA and needs to learn about the technical and
functional specifications of the solution.
• Hosted solution
IT is responsible for monitoring application performance, troubleshooting, and all application
support activities.
• Cloud-based solution
IT is responsible for security and user administration, software logistics, development, and testing
of solution changes. The IT team therefore requires the necessary knowledge and skills to
complete these tasks. If the solution is the first to be implemented in the cloud, the current support
operations need to be reviewed to include, for example, communication with the provider of the
cloud-based services.
• Third-party support
When application support is handled by a third party, knowledge about the solution must be
transferred from the project team to the third party. Business process owners, business
relationship managers, and service desk agents within customer’s organization still need to learn
about the solution, and they should also consider changes in the incident or change management
support processes.
• Greenfield customers
All the topics mentioned in this activity are relevant for “Greenfield” customers. The effort to
prepare for the support of SAP BW/4HANA will depend on many factors like the current support
model, the maturity of the organization, the future support strategy and deployment, like hosting
hardware, cloud deployment. SAP provides optional support to “Greenfield” customers to help
them with every aspect of the implementation of the future support framework. The extent of this
optional support varies according to the support framework currently in place for running and
operating the legacy systems that are replaced by SAP BW/4HANA.
The technical solution design document (see activity Technical Architecture Definition in the Explore
phase) provides a list of technical components that needs to be operated after the project go-live. Many
other tasks mentioned in this road map are an important source of information on how and what needs to
be supported by IT once the new solution is live. This includes the Technical Architecture, the Delta
Design and Configuration, Product Enhancements.
The goal of this activity is to review the list of potentially affected IT operational activities and to evaluate
the exact changes required in the current customer IT support framework based on the project scope.
Procedure
SAP provides information on the recommended IT Support framework to safely and efficiently operate
SAP BW/4HANA after Go-Live. This includes:
• Identifying the target IT support framework for the future customer operations where the support
processes, people and tools will ensure efficient operations of the migrated and converted solution.
• Recommending Best Practices for the support tools in the areas of monitoring, troubleshooting and
software logistics
• Defining the changes to the current support framework required to support the future solution, and
their respective severity/priority
• Adding Activities to the project plan to implement those changes
• Additional SAP IT operational support in the Realize Phase of the project to help ramp-up support
resources and improve their knowledge transfer, to prototype or implement required tools, and to
further adapt process and procedures.
• Executing technical checks for the support tools mentioned above and ensuring that the changes
to the support framework with high priorities have been implemented and tested.
See also task Clarify on Operational Readiness as part of activity Transition Planning (Prepare phase).
Results
At the end of this activity the impact of SAP BW/4HANA on the existing support organization has been
documented and stored in SAP Solution Manager.
• Clarifying the impact of the SAP BW/4HANA on IT Operations by reviewing the target support
framework for the operations of the new solution: this includes the target support processes, support
tools, and support teams.
• Identifying the required support skills/roles and knowledge on SAP BW/4HANA for the support
resources.
• Defining what needs to change in the current support framework and the corresponding list of
operations implementations activities which need to be included into the overall project plan to
ensure the operational readiness of the support organization. The customer will be responsible for
managing those activities using SAP's recommendations, Best Practices, knowledge maps and
knowledge transfer plans.
• The Operations Impact Evaluation will specify further the SAP detailed involvement required to
support the customer if they cannot implement themselves the recommendations defined during
this activity (for lack of resources or lack of knowledge).
•
• Figure 3.11: Example of an operations service plan created in an Operations Impact Evaluation
Workshop
The review of the recommended target support framework drives the definition of project activities that will
fill the gaps between the current IT support framework and the target support framework created by the
introduction of SAP BW/4HANA.
Accelerators
• Service Information – Service Components for the Transition to Operations
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• SAP HANA Technical Operations Manual
Procedure
During the Operations Impact Evaluation activity, the SAP BW/4HANA project scope is analyzed to
evaluate potential operational risks and areas in the support framework that need to be looked at and
modified/implemented prior to the go-live. The aim is to define the list of operational activities which:
• Need to be newly set up: support processes like incident management need to be able to handle
the new component.
• Are existing, but have to be modified: For example, daily backup routines need to be adjusted to
properly fit the new SAP BW/4HANA. Support tools like monitoring, troubleshooting or software
logistics tools need to be in place.
• Can be retired: For example, DB routines and scripts for AnyDB can be retired. AnyDB monitoring
set up should be retired as well.
All the relevant support areas need to be analyzed in a comprehensive manner that is analyzing all the
roles and skills required for the support of the SAP BW/4HANA, the processes/procedures, the operations
documentation and the enabling support tools.
SAP can support you in all these activities as part of the SAP BW/4HANA service packages where a
systematic approach to operational activities will ensure you analyze all the changes in IT operational
activities caused by the new solution.
Once the affected support areas are analyzed in a systematic way, a road map is defined that includes the
key activities for IT to fill the gaps and prepare the future IT support framework. The key activities required
are many and include:
• Defining the sourcing strategy for a new role: project resource moving to operations, ramp up of a
current resource to support the new solution, hiring or handover of activity to partner
• Setting up and configuring tools and where SAP will be engaged to support
• Documenting operating procedures by project resources or by operational resources
• Organizing for knowledge transfer to ensure the future operational resources have the required
knowledge and skills – this includes formal education of current operational resources, training,
hands on and shadowing on new solution. It includes as well training of all the IT support resources
involved in the support of the new solution like the service desk
• Operations cut-over activities (e.g. team access, roll over of open defects…)
• Retirement of some part of the current support framework
An SAP engagement model should be created as part of an SAP BW/4HANA service package for SAP to
support you in where your knowledge is minimum or where your resources are busy on operational topics.
The possible services include for example:
Results
There is a plan documented and stored in SAP Solution Manager how to adjust IT operations to be ready
to safely and efficiently operate SAP BW/4HANA as of Go-Live.
Tasks
• Update and Prioritize Backlog
Scale
The desirability of the feature to a broad base of users (business impact, acceptance);
Importance
The desirability of the requirement to a small number of important users or customers (influencing key
stakeholders, business value).
How to establish clear priorities: In agile projects the Process Owner must prioritize and force rank list of
all requirements in project backlog. No two items can end up being ‘equal’ on the list (e.g. have the same
priority and ranking). Main reason for this is to prevent that everything is rated as a “Must Have”. The
MSCW prioritization (Must-Have, Should-Have, Could-Have, Would-Have) is used for an initial grouping of
requirements. Secondary step is to rank items within the same priority group.
Accelerators
• Agile Definition of Ready and Done (Customer)
• Agile Release Planning (Customer)
• Backlog including Delta Requirements and Gaps.xlsx
• Backlog Template
• Estimates are done by the experts in the team who are implementing the functionality and have
experience from similar projects
• More expert opinions lead to better the estimation results
• Everybody on the team participates in the estimation process
• Verbal communication is preferred over detailed written specs
• It is possible to use Planning Poker especially for estimates where experts disagree widely (see
next slide)
• Clear the assumptions of estimates prior to estimating - e.g. what is the definition of done for sprint
and for the release
• Avoid anchoring, it invalidates estimates – e.g. “I would say this is easy so it should be X ideal
person days”
• Estimate in the same unit of measure for the entire project (e.g. Ideal Person Days / Story Points)
• If consensus cannot be reached defer the estimate of requirement to later time.
Accelerators
• Agile Sprint Burndown and Task Board (Customer)
• Backlog Template
The image below shows an example of the iterative agile approach to build functionality for one release.
Release represents functionality that is deployed to production system and rolled out to the end users.
Each release is built in sequence of time-boxed sprints in which the project team develops the highest
priority capabilities as determined by the business owners. One or multiple sprints may be needed to
finalize functionality for end-to-end scenario (or Epic as it is known in agile projects)
4. Sprint Demo
5. Sprint Retrospective
During the project the team will run two types of sprints:
1. Build sprints - the goal of these sprints is to build and unit test the new capabilities
2. Firm-up sprints - the goal of these sprints is to conduct testing of strings of process steps to
continuously ensure integration. During this sprint the team also develops solution documentation
Accelerators
• Agile Release Planning (Customer)
Tasks
• Validate Organizational Alignment Approach
• Establish Baseline of Current State
Accelerators
• OCM Change Impact Analysis Guide (Customer)
• Ensure that all required deliverables from this phase and the project are complete and accurate,
and close any outstanding issues
• Identify lessons learned during the phase to prepare for formal phase closure
• Capture customer feedback and potential Customer References
Tasks
• Conduct Knowledge Management Gate
• Conduct Project Quality Gate
• Execute Baseline Retrospective
• Conduct Project Management Review Service
• Conduct Design Review Service
• Manage Fulfilled Contracts
• Obtain Customer Sign-Off for Phase Completion
Accelerators
• Lessons Learned Guide (Customer)
• Lessons Learned Template (Customer)
• Conduct regular quality checks at defined or critical stages of the project lifecycle to assess the
health of the project.
• Ensure that all key deliverables and actions of the gate have been completed in compliance with
recommended practices and to the customer’s satisfaction.
• Enable project management to continuously communicate the process and build quality directly
into the project.
• Provide a tool to effectively manage project expectations and monitor customer satisfaction. The
deliverables assessed at each quality gate will be performed using the quality gate checklist with
defined expectations to the maturity of particular project deliverables.
Note:
New additional key deliverables need to be added in the quality gate checklist by the Project Manager
to the different project types.
Accelerators
• QGateChecklist Concept SAP Activate
• QGateChecklist Template Introduction
• Quality Built In New QGate Checklist
Accelerators
• Agile Sprint Retrospective Template (Customer)
3.23.4. Conduct Project Management Review Service
Objective
The purpose of this task is to execute a Project Management Review that provides a proactive quality
assurance review, with an impartial analysis of all aspects of the project - across all project management
disciplines, enabling early detection of project issues with actionable recommendations.
Accelerators
• Phase Sign-Off Template (Customer)
4. Realize Phase
Once Quality Gate 2 (i.e. Q2) – Explore-to-Realize has been passed successfully, the functional and
technical implementation takes place in the Realize phase.
In the Application: Solution Adoption work stream, the trainings for the end users start.
In the Application: Design & Configuration work stream the SAP BW/4HANA Implementation Service
or the data and object transformation takes place according to the applied scenario. SAP can safeguard
the activities via the Integration Validation offering, which covers key aspects like Exception Management,
Integration, and Performance and Scalability.
In the Custom Code Extensions work stream, impacted custom code is adjusted and tested as well.
Application changes are thoroughly tested in the Application: Testing work stream.
In the System & Data Migration work stream, the transition of the quality assurance system takes place
according to the detailed transition plan. Technical adjustments may be implemented as part of the
activity. Load and verification runs ensure business data can be migrated with acceptable time and quality.
At the end of the Realize phase, the preparation for cutover starts, which for instance includes the setup of
the new productive system in case of a new installation.
The technical infrastructure is set up in the Technical Architecture and Infrastructure work stream,
according to the technical design document. In parallel, the sizing of the productive instance is verified.
According to the Operations Impact Evaluation, the operations implementation (people, processes tools)
takes place in the Transition to Operations work stream.
Phase Initiation
Description
The purpose of this deliverable is to formally recognize that a new project phase starts.
Tasks
• Review Deliverables of Realize Phase
Tasks
• Plan Sprints and Solution Reviews
• Plan Testing
Accelerators
• Agile Definition of Ready and Done (Customer)
Tasks
1. Manage Sprints
4.4.1.Manage Sprints
Objective
The purpose of this task is to ensure consistent execution and monitoring of sprint activities.
Sprint Closing
Description
The purpose of this deliverable is to formally close the sprint by conducting the Sprint Review Meeting with
key users, product owner group and key stakeholders; formally sign-off the results and conduct sprint
retrospective.
Tasks
• Conduct Sprint Review Meeting
Accelerators
• Agile Sprint Burndown and Task Board (Customer)
Accelerators
• Agile Release Planning (Customer)
• Agile Sprint Retrospective Template (Customer)
Learning Realization
Description
In this activity the training material for end user will be created.
The following preconditions are required before end user training material creation can start:
• End user training material, a training environment, logistics, and infrastructure is available.
• Skilled instructors are available based on the framework defined in the training strategy document
from activity.
Procedure
• Train your Key User
• Create Training Material for End User
Results
At the end of this activity, the training for the end user is ready to be delivered (including systems, demo
data etc.).
Procedure
Train your key user as planned in the Explore phase. Training could happen e.g. via class room training,
or on the sandbox system.
Please note: Key users should be trained in such a way that they can support the creation of training
material for end users, or the test of newly implemented functionality.
Results
Key users are trained.
Accelerators
• SAP Education Consulting Services
Procedure
Based on the training concept the usage of a recording and authoring tool for creating the end user
training material needs to be discussed and decided. SAP recommends the SAP Enable Now (successor
of the SAP Workforce Performance Builder (WPB)) as the tool for creating the training material, supporting
translations, developing e-learning with or/and without audio voice description.
The SAP Enable Now can be used for SAP and Non-SAP applications and is therefore suitable for a
seamless recording and documentation process for the end user in one tool. The final documents can be
exported in standard formats as PDF, MS Word, and PowerPoint. Furthermore SAP Enable Now can also
support the test phase with documentation of test cases and results. You can find all important documents
on SAP Enable Now in the SAP Online Help Portal (e.g. “What’s New in SAP Enable Now”, “Master
Guide”, or “Creating Documents for HP Quality Center”) – see accelerator section.
SAP is following the approach to enable the customer key users to develop the end user training material
mainly themselves. SAP can coach the key users in developing the right structure and in reviewing the
documents. The goal is to transfer the knowledge as much as possible to the key users to enable them for
the end user training. As a prerequisite the key users should already be trained didactically, methodically,
and for using the tool appropriately during the Explore phase and the key user training work package.
The following list describes possible end user training documents required to be developed for every
training:
• Course Concept
For each training event (classroom training), a course concept is created together with the customer.
The course concept defines the required content to be communicated. The course concept is
converted it into an appropriate structure and recorded in a template for training delivery.
• Training Manual
The training manual contains instructions, notes, and references to important points during the
training. They explain the processes, and provide the trainer with the structure, times, and procedures
for the courses (up to max. one page per content day).
• Conceptual Design Slides
Conceptual design slides are created for the training events as a visual aid, and a guideline during
training. They provide not only a general overview of the course but also the main procedures as well
as role-specific and process-specific information. The slides have a modular structure and are
discussed during training (up to max. five concept slides per content day).
• Work Instructions for Transaction Steps
The work instructions contain not only step-by-step explanations for the relevant transactions, but also
screenshots from the customers SAP system as well as explanations of screens and input fields.
• Exercises, Including Data
Exercises are an integral part of each training measure. Active processing phases within a training
event help participants to understand and learn about sub-processes and functions relating to their
new system. The exercises are carried out in a customer SAP system during the training event to
ensure that the training includes a large proportion of practical applications. Up to four exercise
scenarios are generally needed for each training day. Training data needs to be available early, so
that the key user can already try out during training material creation.
• Simulations
Simulations help to visualize operating steps in the SAP system. They enable end users to practice in
an environment that is separate from a genuine SAP system and thus allow them to acquire the
necessary experience. Simulations can only be created once a suitable authoring tool is available
(e.g. SAP Enable Now).
• E-Learning
E-Learning helps to reduce the effort for classroom training. As a self-learning offering, e-learning is
also available after the project has ended. This enables new employees to become acquainted with
topics independently. Trained employees can "refer back to" various topics or "take a look at" the
system simulations as required. Creating customer-specific e-learning content requires a stable and
fully developed / customized SAP system.
SAP assumes that e-learning will merely comprise of less complex and overview content such as
process overview per stream, main functional features, highlighting key changes and benefits. SAP
develops e-learning content comprising approximately 56 hours of net learning time. Net learning time
describes the amount of time that an average learner requires to work through the program without
any interruptions.
• Web Based Training (WBT)
Web based training is a reasonable addition to e-learning and has the advantage that a course can be
attended location-independently by one or more persons. Communication with the trainer via phone or
chat is feasible, during which all open questions resulting from previous self-learning experience can be
answered by an expert.
If possible, the course material and the exercises and solutions could be derived from the corresponding
classroom training courses. If not, a course concept, training manual, conceptual design slides, work
instructions for transaction steps, and exercises (including data and simulations) should be developed
Based on the end user training the customer training system need to be set up by the customer key users.
SAP can support this activity. The technical set up is finalized by the IT team.
In addition to the development of the end-user training material and the training system set up, the
customer key users should have a final workshop with SAP experts to finally prepare the end user
trainings, and to define the tandem approach for the first end user trainings. The tandem approach means
that the customer key user will be accompanied during the first training sessions by an experienced SAP
trainer to get confidence and safety in performing the trainings.
SAP expects DEV and QAS (or a dedicated training system) to be completely available during training
development period. SAP recommends a systematic buildup of the training client in the QAS test system
during the Realize phase. The training client should be available when training material creation starts
(e.g. processes, master and booking data).
Results
The training is ready to be delivered to end user.
Accelerators
• SAP Education Consulting Services
Configuration
Description
After the setup of the Dev system, you need to run the post-installation steps and start with the
configuration of the system.
Procedure
• Run the post-installation steps as described in the Master Guide (see accelerator section).
• Activate the required business content.
Result
The basic configuration of the new SAP BW/4HANA system is done.
Accelerators
• SAP BW/4HANA Master Guide
• SAP BW/4HANA Content Add-on (online help)
Procedure
• Run tasklist SAP BW4_SETUP_SIMPLE in transaction STC01. The tasklist performs the basic
system setup tasks, like creating and configuring the SAP BW/4HANA background user, setting the
SAP BW/4HANA client and installing the essential technical content.
• Use the Implementation Guide (IMG) to add further settings
• Install the permanent SAP license.
• Install the SAP BW/4HANA Basis Content Add-on, if not yet done with the system setup. Refer to
SAP Note 2393067 – Installation Note
• Install the SAP BW/4HANA Content Add-on, if not yet done with the system setup
• Activate the content areas from the business content as required for your business.
• Configure the connection to your source systems. This may require the implementation of ODP 1.0
in case of source systems < 730 and the implementation of ODP 2.0 if the basis level component
SAP_BASIS is >= 730.
• Installation of an SAP HANA system and SAP BW/4HANA system in the development environment
• Basic configuration of SAP HANA and SAP BW/4HANA development system
• Replication of global settings and exchange rates
• Implementation of ODP 2.0 if basis level component in ECC source system is appropriate
(SAP_BASIS >=730)
• Basic configuration in order to connect one SAP ECC source system
• Activate FI or CP: Activation of one content area from FI or CO from the business content
• Activate SD/MM (no Cockpit): Activation of one content area from MM or SD from the business
content, if LO Cockpit is already configured in source system
• Activate SD/MM and LO Cockpit: Activation of one content area from MM or SD from the business
content. LO Cockpit configuration for one area from MM or SD.
• ODP 1.0 Framework: Implementation of ODP 1.0 if SAP BASIS level in source system is <730.
Accelerators
• SAP Note 2393067 – Installation Note
• SAP Note 2400585 – Collective Note & FAQ: SAP BW/4HANA Content (BW4CONT &
BW4CONTB)
• Implementation Service for SAP BW/4HANA
Procedure
• Install Starter Add-on
• Run the Conversion Control tool
• Use the Transfer Toolbox to replace unsupported Objects
• Perform Custom Code Adjustments
• Switch to Ready for Conversion mode
Result
The system is ready for the technical conversion.
4.8.1.Install the SAP BW/4HANA Starter Add-on
The Starter Add-on installation is the first step in the execution phase of the SAP BW/4HANA conversion
project. The Starter Add-on switches the system into Compatibility mode. This marks the begin of the
various manual and tool supported conversion activities required to reach B4H mode and consecutively
Ready for Conversion mode. Refer to SAP Note 2246699 - SAP BW/4HANA Starter Add-On - Pre-
Requisites/Installation/De-Installation/Update.
The installation procedure is comparable to the installation of a NetWeaver upgrade.
Prerequisite
The stack.xml is downloaded as described in task “Prepare the Installation of the SAP BW/4HANA Starter
Add-on” in the activity Prep Steps and Data Model Adjustment.
Procedure
The installation is executed with SUM of the SL toolset.
1. Start SUM via SAP Hostagent
2. Execute the installation with SUM
3. Authorization Assignment
You need authorization for authorization objects S_RS_B4H, S_TC, and S_RFC. You also
need authorization for advanced DataStore objects (S_RS_ADSO), CompositeProviders
(S_RS_HCPR), or any other object created or modified during the conversion.
Result
The SAP BW/4HANA Starter Add-on is installed.
• A coarse estimation of the In-Place System Conversion steps and durations can be seen in this
graphic:
Procedure
Immediately after installing the BW/4HANA Starter Add-on, the system is automatically set to compatibility
mode.
Use the Conversion Control Tool to run a simulation of the B4H mode. Analyze the readiness check report
results and solve all red and yellow check results either by
• Remodeling
• Replacing with new functionality (manual activities and with automated tool support)
• Deletion of unsupported/obsolete objects
After successfully solving all yellow and red checks execute the switch to B4H mode with the Conversion
Control Tool. The task list RS_COMPATIBILITY_TO_B4H is called during the switch operation to B4H
mode. Complete all task list steps which mainly consist of obsolete object deletion tasks.
Result
The final step of this task list performs the switch to the new B4H mode.
4.8.3. Use the Transfer Cockpit to convert data models and data flows to HANA-Optimized Objects
Objective
Object types that are not available in SAP BW/4HANA are replaced by other object types or
features. The following table lists the object types that are not available anymore and can be
converted using the Transfer Cockpit, together with their successors and the Simplification
Item (see the corresponding SAP Notes for details and limitations regarding each object
type):
Figure 4.5: Object Types and Simplification Items
Procedure
Start the SAP BW/4HANA Transfer Cockpit using transaction RSB4HTRF and proceed as described in
detail in the Conversion Guide for SAP BW/4HANA (see accelerators). The duration of the transfer
depends on the number of objects included in the scope and the data volume that must be transferred.
Results
All transferrable objects are converted to HANA-optimized objects.
Procedure
The Transfer Cockpit transfers the unsupported objects to new supported objects, copies the data to the
new objects and the old objects are deleted. The relevant objects are identified by the readiness check
report. The Transfer Cockpit activities are generally the most time-consuming activities in this project
phase. The activities must be performed in each system of the system landscape separately (In-place
conversion). Generally, the changes cannot be transported.
How SAP can Support
For a complete and up-to-date list of unsupported objects, processes and functionalities, together with
their successors/replacements and the relevant conversion method, refer to the latest version of the SAP
Simplification List for SAP BW/4HANA 1.0.
Procedure
Follow up on the results from the Custom Code Impact Analysis. Also refer to the activity “Custom Code
Management Execution”.
Procedure
Use the Conversion Control Tool to execute the switch operation to Ready for Conversion mode. The task
list RS_B4H_TO_READY4CONVERSION is called and all task list steps must be completed successfully.
The switch to Ready for Conversion mode is executed by the last task list step.
Result
The system is switched to the Ready for Conversion Mode.
Procedure
1. Open transaction SAINT in the SAP BW system.
2. Choose your created stack.xml file.
3. Additionally you have to select the SAP_ABA 75A component in the selection here as well.
For a step-by-step guide see the Conversion Guide in the accelerator section.
Results
The implementation is finished now. Run transaction SPAU to reset everything back to SAP standard.
Once the SAINT procedure is finished, you can continue in your new system with BW/4HANA specific
settings. Check the Document “SAP First Guidance – complete functional scope (CFS) for SAP
BW/4HANA” (see accelerator section).
Accelerators
• Conversion Guide for SAP BW/4HANA 1.0
• In-place system conversion for SAP BW/4HANA Service
• SAP First Guidance – complete functional scope (CFS) for SAP BW/4HANA
• SAP Note 69455 – Servicetools for Applications ST-A/PI
• SAP Note 1815374 – Clean up entries in tables after delete source system
• SAP Note 2069865 – ITAB_DUPLICATE_KEY dump in program SAPLRSAODS during various
staging processes
• SAP Note 2214733 – SAPI: Inconsistent IDoc segments/transfer structures in source system
• SAP Note 2400086 – Myself-System not allowed in strict mode
Cleanup/Archive
Description
In this activity the Data Volume Strategy that has been defined and (partly) implemented is further realized
(see description of activity Data Volume Design).
Data Tiering
Description
Data Tiering allows you to assign data to various storage areas and storage media. The critera for this
decision are data type, operational considerations, performance requirements, frequency of access, and
security requirements.
Customers often employ a multi-temperature or data tiering storage strategy, with data classified
depending on frequency of access and certain other criteria as either hot, warm or cold. Depending on this
classification, the data is kept in different storage areas or media.
In addition to frequently accessed active data, large SAP BW∕4HANA systems also contain a large volume
of data that is only accessed rarely. The data is either never or rarely needed in Data Warehouse
processes or for analysis. The main challenge of implementing a data tiering strategy is to seamlessly
integrate the warm and cold memory areas and to make these areas invisible to the outside, in order to
ensure that all required functions are applied to this data. SAP provided data tiering solutions for this,
helping to reduce TCO thanks to optimized SAP HANA main memory resource management.
The following solutions are available in SAP BW∕4HANA for data tiering available.
Data Tiering Optimization (DTO) is the strategic solution for data tiering in SAP BW∕4HANA. It offers the
following advantages:
• A single data tiering solution for hot data (hot store in SAP HANA), warm data (warm store in SAP
HANA) and cold data (cold store to SAP IQ, Hadoop, SAP Vora)
• Central definition of the data temperature based on partitions of the DataStore object (advanced)
• Moving data to the dedicated storage location as a simple and periodically performed housekeeping
activity (TCO reduction)
• Smooth co-existence of Data Tiering Optimization and the existing near-line storage approach, as
the same technical concepts are used for the storage areas for cold data, such as locking archived
data
Note: Near-line storage with SAP IQ and Hadoop, a solution for the cold store, is still supported in SAP
BW∕4HANA and provides:
• Continuity for data archiving scenarios that are already implemented with near-line storage with
SAP IQ or Hadoop before SAP BW∕4HANA Data Tiering Optimization is introduced
• Support for more complex data archiving scenarios that are not covered by SAP BW∕4HANA Data
Tiering Optimization
For new DataStore objects however, you should use Data Tiering Optimization wherever possible.
The following graphic shows a SAP Hana Scale-out landscape with extension node:
Tasks
• Configure SAP HANA Extension Node as a Warm Store
• Configure Hadoop or SAP Vora as Cold Store
Results
Data Tiering Optimization is prepared and the DataStore objects can be configured accordingly.
4.10.1. Configure SAP HANA Extension Node as a Warm Store
Objective
To implement a multi-temperature memory strategy in your SAP BW∕4HANA system, as of SAP HANA 1.0
SPS12 (DSP), you can use the extended node concept for warm data. The data (with no functional
restrictions) is saved in a dedicated SAP HANA scale-out node. This enables you to optimize usage of the
main memory in SAP HANA.
Based on typical data distribution in a SAP BW∕4HANA system, a single extension node is normally used.
Multiple extension nodes should only be used in exceptional circumstances. If you do use data tiering
optimization with multiple extension nodes, SAP HANA 2.0 is a prerequisite.
Procedure
• Configure SAP HANA for use with extention node (see SAP Note 2343647).
• Specify the data tiering properties (information about which temperatures or memory areas should
be supported by an object) in the modeling screen for the relevant DataStore objects. Use the
definition of an object temperature or partition temperature to specify which data is stored in which
memory area.
• Define a data tiering optimization job which regularly moves data to the extention nodes for the
corresponding configured DataStore objects.
Results
Performance and memory usage are increased as only hot data is stored on the standard node whereas
warm data is stored on the extension node.
Accelerators
• SAP Note 2343647: How to Configure SAP HANA for the BW extension node
• SAP Note 2317200: Data Lifecycle Management for BW on HANA and extension nodes
• Details on Data Lifecycle Management for BW on HANA (SCN blog)
• More details: HANA extension nodes for BW on HANA (SCN blog)
• FAQ: SAP BW/4HANA and SAP BW-On-HANA with SAP HANA Extension Nodes
• Data Tiering Optimization with SAP BW/4HANA
Procedure
• For Hadoop, all configuration steps are described in the online help “Configuring Hadoop as a cold
store/Neral-Line Storage Solution” (see accelerator section):
• Perform configuration steps for Hadoop
• Perform configuration steps on SAP HANA
• Perform configuration steps in SAP BW/4HANA
For SAP Vora, all configuration steps are described in the online help “SAP Vora as a Cold Store” (see
accelerator section):
Results
Either Hadoop or SAP Vora has been configured as cold store.
The BW near-line storage Empowering Service is a workshop that can be ordered as a follow-up to the
Data Volume Management service components. It includes a results presentation of the strategy service.
In addition, the workshop covers the following topics:
Accelerators
• SAP BW/4HANA Data Tiering Optimization
• SAP Empowering Service BW Near-line Storage (CRM 9500540)
• Help.sap.com: Configuring Hadoop as a Cold Store/Near-Line Storage Solution
• Help.sap.com: SAP Vora as a Cold Store
• SAP Note 2608405 – SAP Vora Cold Store: Information, Recommendations and Limitations
• SAP Note 1796393 – SAP BW near-line solution with SAP IQ
• SAP Note 2343647 – How-To: Configuring SAP HANA for the BW Extension Node
• SAP Note 2453736 - How-To: Configuring SAP HANA for SAP BW Extension Node in SAP HANA 2.0
• SAP Note 2415279 – How-To: Configuring SAP HANA for the SAP HANA Extension Node
• SAP Note 2165650 – FAQ: BW Near-Line Storage with HANA Smart Data Access
• SAP Note 2100962 – FAQ: BW Near-Line Storage with HANA Smart Data Access: Query Performance
• SAP Note 1999431 – SIQ: Setting up SSL for connections to IQ
• SAP Note 2133194 – Can SAP IQ run in a cloud environment?
• FAQ: SAP BW/4HANA and SAP BW-on-Hana with SAP HANA extension Nodes
• SAP Note 2486706 – FAQ: SAP BW/4HANA and SAP BW-on-HANA with Extension Nodes
• SAP Note 2643763 – FAQ: SAP HANA Extension Node for SAP HANA native applications
• SAP Note 2334091 – BW/4HANA: Table Placement and Landscape Redistribution
• SAP Note 2317200 – Data lifecycle management for BW on SAP HANA and extension nodes
Integration Validation
Description
When implementing and running Solution Landscapes that drive mission-critical business processes, the
integration of solutions can be complex and challenging. The implementation work is typically distributed
across many teams and in most cases many stakeholders, including custom-built and third-party software.
Integration Validation helps to introduce solutions into a production environment smoothly, while
maintaining ongoing operations with minimal disruption. This offering from SAP combines tried-and-tested
processes and tools, such as the SAP Solution Manager Application Management solution, with a clear
governance model and holistic, one-issue tracking methodology (“single source of the truth”).
The organizational framework for each Integration Validation project is provided by the Innovation Control
Center (ICC), which is formed from the Customer Center of Expertise (CCOE) location. It unites customer
experts, partners, and SAP staff as one team in one room and works in principle like a NASA control
room. Every mission-critical application and technology component is represented as well as every
implementation and operation services provider.
Besides others, IV addresses the following aspects:
• Data consistency:
All data integration is posted automatically, for example, from sales and distribution and materials
management to financials and controlling. In distributed solution landscapes, the consistency of the
data across software systems must be subject to checks and validations at any time. Data passed
via interfaces between software systems must be consistent. This requires transactional security of
the interface technology (end-to-end transactional consistency). All integration queues and
interfaces have to be monitored.
• Business process monitoring and exception management:
There must be 100% transparency of status and completion of business processes. The continuous
flow of documents throughout the business process must be monitored. This includes backlogs of
business processes and indicators for throughput, as well as alerts indicating business exceptions,
for example, out-of-stock situations. There must be 100% transparency of exceptions and backlogs.
• Performance and scalability:
Response time for defined critical transactions should be lower or equal to what was specified in
the business requirements. Batch runtime for defined critical batch jobs should be lower or equal to
what was specified in the business requirements. Batch processing for critical jobs that are part of
the core business process should fit in the given batch-processing window. Volume growth and
resource consumption must have a linear relationship. Adequate load balancing must be in place
to support throughput of performance-critical business processes.
Procedure
1. Identify the IV Scope
2. Initiate the Corresponding IV Support Activities
3. Initiate SAP Going-Live Check
Results
As the result of this activity, integration validation activities have been planned, documented and initiated.
They will continue across the Deploy phase.
Accelerators
• SAP Thought Leadership Paper - Integration Validation of Networked Solutions
• Documented Procedure for Integration Validation
• Presentation - Value Proposition for Integration Validation of Network Solution
4.11.1. Identify the IV Scope
Objective
The goal of this task is to identify the scope of Integration Validation in the context of the transition project.
Procedure
Validating the integration of a complex solution is a challenging and extensive task. To improve the
efficiency and effectiveness of the task, a collaborative approach should be employed. This makes
knowledge transfer an integral part of Integration Validation, enabling all parties involved – the customer,
the system integrator, and SAP experts – to work together to validate the solution.
The final cross-check is led by SAP, with support from the customer and system integrator. The check
results documented in SAP Solution Manager provide the basis for this cross-check. To determine jointly
the scope of Integration Validation and to develop a detailed plan of how to validate the solution, product
and operations standards, the following information is required:
• The critical core business processes, including all relevant interfaces and the underlying software
landscape
• Volumes of data to be processed for the critical business process, including peak volume
• Performance KPIs (transactional, batch, and batch window)
In close cooperation with the customer and partner, SAP drives the validation of the customer’s Solution
Landscape based on the scope defined. Throughout the process of validation, SAP provides knowledge
transfer on an on-going basis and supports the customer and partner as they validate all related core
business process steps and interfaces.
For complex scenarios, Integration Validation can be very detailed, and possibly structured as a project on
its own. The concept needs to be tailored to the project scope. See the road map “ESRV Integration
Validation (V2.2)” in transaction RMMAIN in SAP Solution Manager for details.
Results
The scope of Integration Validation in the context of the transition project has been documented and
stored in SAP Solution Manager.
Accelerators
• SAP Thought Leadership Paper - Integration Validation of Networked Solutions
• Documented Procedure for Integration Validation
• Presentation - Value Proposition for Integration Validation of Network Solution
• Innovation Control Center (White Paper)
Prerequisites
The scope of IV has been defined.
How SAP Can Support
IV is usually executed with SAP participating. The SAP TQM will initiate the right IV support activities from
SAP:
• Technical Feasibility Check service component (TFC): Assess the technical feasibility of the
transition project with focus on compatibility, business continuity, performance and consistency.
• Technical Integration Check service component (TIC): The TIC is an assessment service and aims
to verify that the built solution supports the integration test with focus on consistency, performance
and stability across systems. Interfaces integration, Data Volume and Business Process
Management are assessed.
• Integration Validation service component: This service component provides technical validation of
core business processes with respect to non-functional requirements, identification and addressing
of technical risks prior to Go-Live and during the production cutover including hyper-care phase. A
comprehensive status of technical Go-Live readiness for core business processes (Integration
Validation matrix) is part of the service component.
• Business Process Technical Validation service component: This service component ensures
technical readiness of the core business process for Go-Live. It addresses areas like data
consistency, exception management, performance and scalability, system integration, batch and
volume processing. In the focus is the technical validation of the core business processes and
preparation for the subsequent efficient operation of the software solution.
• Technical Performance Optimization service component: The technical performance optimization
service component improves your SAP solution by helping you to configure your SAP S/4HANA
system in an optimal way. The identification and elimination of costly performance bottlenecks
optimizes the response times and throughput of your SAP solution.
SAP Enterprise Support Customers can order the CQC for Technical Performance Optimization (TPO).
Accelerators
• Service Information – Service Components for Safeguarding the Digital Transformation
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• CQC for Technical Performance Optimization (TPO)
Prerequisites
The SAP GoingLive Check is recommended for all scenarios.
Procedure
There are three different SAP GoingLive Checks available:
All services are delivered remotely. An analysis session should be performed 6 weeks in front of the Go-
Live date, to have sufficient time to fix identified issues. The verification session runs some weeks after
Go-Live, to check the system in its productive use.
See accelerator section for detailed service information. Schedule the appropriate service for the SAP
system, and additionally for the SAP Gateway in case it runs as a separate instance.
Results
You have successfully requested the correct SAP GoingLive Check.
Accelerators
• SAP OS/DB Migration Check
• CQC OS/DB Migration Check
• SAP Going-Live Functional Upgrade Check
• CQC for Upgrade
• SAP Going-Live Check for Implementation
• CQC for Implementation
Analytics Configuration
Description
With live data connection to SAP BW/4HANA, SAP Analytics Cloud treats the integration with BEx queries
like an InfoProvider for data consumption purposes. Support on BEx query consumption is focused on:
• Customers are recommended to create specific queries for compatible usage in SAP Analytics
Cloud
• Only queries configured with “Allow External Access to this Query” flag enabled, can be consumed
by SAP Analytics Cloud
Note:
• SAP Analytics Cloud is leveraging selective BW query feature concepts relevant to data import:
• Once the data is imported into SAP Analytics Cloud, the calculation engine will be HANA. The BW
OLAP engine is no longer tied to the imported data set
• Imported data can be kept up to date via scheduled refresh
Full documentation on BEx query consumption support and product limitations are available on the Help
Portal: https://help.sap.com/cloud4analytics.
Procedure
• Understand the benefits and functionality of SAP Analytics Cloud
• Create Data Models in SAP Analytics Cloud
Accelerators
• SAP Analytics Cloud integration with SAP BW
• Online help https://help.sap.com/cloud4analytics
4.12.1. Understand the Benefits and Functionality of SAP Analytics Cloud
Objective
Understand the concept and how to work with SAP Analytics Cloud.
Procedure
Make yourself familiar with SAP Analytics Cloud with the help of the webinars and guided playlists on the
SAP Analytics Cloud homepage https://www.sapanalytics.cloud.
• Overview and Architecture of SAP Analytics Cloud and SAP Digital Boardroom
• Data Connectivity
• Data Load – Excel to SAP Analytics Cloud
• Modeling Management of SAP Analytics Cloud
• User Administration of SAP Analytics Cloud
• Visualization Creation and Atory Composition for SAP Digital Boardroom.
Accelerators
• Enablement Service for SAP Analytics Cloud and SAP Digital Boardroom (50124566)
Procedure
You can use the Guided Playlist “Introduction to Data Models” in the SAP Analytics Cloud Guided Playlists
(see accelerator section).
Note: Before designing your story, please check the help page “Supported Features and Known
Limitations to SAP BW Live Data Connections” (see accelerator section) to identify the limitations when
using e a BW Live Data Connection:
Results
You have learned the fundamentals of data models.
Accelerators
• SAP Analytics Cloud Guided Playlist “Introduction to Data Models”
• Supported Features and Known Limitations to SAP BW Live Data Connections
Procedure
SAP Note 2541557 will help you to have your Backend in sync.
Results
SAP B/4HANA and SAP Analytics Cloud are kept in sync.
Accelerators
• SAP Note 2541557 – Support further SAP Analytics Cloud BW Features
Procedure
The transition from SAP Business Explorer to SAP BusinessObjects requires a manual migration
(currently no tools will perform the conversion automatically). SAP customers may need to purchase new
licenses to be able to deploy SAP BusinessObjects tools (SAP BusinessObjects is not a successor of SAP
Business Explorer). The “SAP BEx Query Designer” has transitioned to the BW Modeling Tools Query
Designer.
The custom code work list of affected objects has been created (see activity Custom Code Impact
Analysis).
Procedure
1. Adjust Affected Custom Code
2. Test and Optimize Your Custom Code
Results
Custom code has been adjusted for SAP BW/4HANA.
Accelerators
• Service Information – Service Components for Custom Code Management
• ABAP custom code adaptation for SAP HANA – The efficient way
• SAP Note 1909597 - SAP BW Migration Cockpit for SAP HANA
4.13.1. Adjust Affected Custom Code
Objective
Adjust the custom code you have identified in the steps before and make it SAP BW/4HANA ready.
Accelerators
• Custom Code Management Tools Enablement
Test Preparation
Description
The purpose of this activity is to prepare all business-process-related tests according to customer-specific
configurations.
Procedure
• Prepare Tests
Accelerators
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
Procedure
Within each implemented solution scope, the following steps need to be executed:
The best-practice test scripts are part of the solution scope description, and can be found in SAP Service
Marketplace.
Accelerators
• SAP Best Practice Explorer
Test Execution
Description
In this activity, integration test, regression test and user acceptance test takes place.
The unit test has been done as part of the development process in the DEV system already.
Procedure
Prepare a test environment with the required test data as defined in the activity Test Planning.
Once the tests have been planned and test data is available on the test systems, testing can begin. The
typical basic process for the Realize phase is as follows:
• Software developers perform unit tests in the DEV systems. Depending on the type and scope of
the test cycle, various functional tests are performed.
• Manual testers are provided with the tester handout document and receive details regarding their
test package by e-mail.
• Automated tests are scheduled or started directly.
• Every test that is executed is logged and documented with test notes and a test status is set
manually or automatically.
• If the system responds in an unexpected way during manual testing, for example, if an error
message appears, the tester records the incident in the corresponding ITSM system, attaching
screenshots, log messages, and so on. Usually, this also has to be done manually even for
automated tests.
• The incident is sent to the persons responsible for the analysis and categorization of defects, who
then correct the defect in the development system.
• The correction is transported to the test system according to the existing arrangements and
timelines, where it is then retested.
Given the complexity and heterogeneity of modern software solutions, SAP recommends performing the
activity Integration Validation, especially for important business processes. This involves gathering and
subsequently evaluating a substantial amount of data from the software applications that are active while
a given business process is being executed. This type of validation also allows you to identify the hidden
warnings and error messages that frequently occur at the interfaces between applications.
Furthermore the operations team should monitor the testing system as if it were production in order to gain
early visibility and hands-on experience to possible production issues.
If large-scale changes are made or new software solutions are implemented, load tests should be
performed before these are used in production. These tests simulate a situation in which the expected
load (known number of users and background load in a load-peak situation) is simulated. While doing so,
system behavior in handling large data volumes can be inspected. Throughout the entire test cycle, test
coordinators monitor the test status and progress, as well as the processing status of incidents that have
been reported.
The quality of the test data and test scripts directly affect the stability of the productive system following
the Go-Live of the change event. Consider an array of representative variances when preparing for the
execution of the regression test cycle. It is important to execute realistic data sets that representative
production operations of critical business process.
4.15.1. Perform Integration / Regression / User Acceptance Test
Objective
The goal of this task is to perform integration test, regression test and user acceptance test.
Procedure
Integration Testing is performed to verify proper execution of the entire application including interfaces to
external applications. This ensures that the integrated components are functioning properly according to
the requirements and specifications. The objective is to perform the end-to-end process integration
between all SAP and non-SAP components of the Solution Landscape to validate that all application
systems are functioning properly. Integration testing in combination with Regression Testing ensures that
all business scenarios have been tested prior to the User Acceptance Testing.
Define and document integration test cases, end-to-end customer business process scenarios,
according to the test plan. Test plans and test case documentation is stored in Solution
Manager.
The purpose of this task is to document the integration test cases outlined in the integration
test plan. This activity contains also aligned setup of relevant test data that will be commonly
used.
Perform the Integration test according to previously defined plan. During test execution all
issues must be logged and documented in the system for traceability purpose.
Resolve any issues identified during the Integration Test. It is crucial that the issues are re-
tested by the users that reported them (or designated re-testers) and that they are confirmed.
The conversion to SAP BW/4HANA may impact productive business processes following even a
successful cutover. In order to mitigate the risks and issues to those business processes, it is necessary
to regression test them as a part of the project or Release.
• Prepare a detailed regression test plan with test cases and test scripts.
• Set up test management procedures to track the progress of the test execution. Set up defect
tracking to ensure all identified issues are addressed.
• Execute the regression test scripts based on the test plan and test cases. Document any
anomalies or defects.
• Monitor the test system as if it were production, as this will provide an indication of end-state
operations. For example, errors in the system log, which may not be noticed by testers, could
cause instability in the production system. Therefore it is important to leverage the regression
testing cycle to proactively address such issues.
• Resolve any defects, and retest to ensure all identified issues are closed.
Update the existing integration test cases, end-to-end customer business process scenarios,
based on the learnings from previous test phase. UA test plans and test case documentation is
stored in Solution Manager.
The purpose of this task is to document the UA test case outlined in the UA test plan. This
activity contains also aligned setup of relevant test data that will be commonly used.
Perform the test according to previously defined plan. During the test all issues must be logged
and documented in the system for traceability purpose.
Resolve any issues identified during testing. It is crucial that the issues are re-tested by the
users that reported them (or designated re-testers) and that they are confirmed.
There is a technical design document stored in SAP Solution Manager which includes the technical
deployment plan, and the software components which need to be installed / updated.
Procedure
• QAS Setup
Procedure
Proceed as follows:
• Execute the technical installation of the required SAP Products for QAS environment as
documented in the technical design document.
• Run the technical system setup.
• Transport development and configuration changes from DEV to QAS. Consider also potential
manual rework activities.
Results
Finally the QAS environment is ready for testing.
• BW objects and data flows are transferred to the new BW/4HANA system (Remote Conversion)
• Only selected data models are transferred without data (Shell Conversion).
In the case of Shell Conversion, historical data is ignored and the system starts fresh. However,
you have the option to load data from the old BW system or from source systems.
Tasks
• Perform Data Migration & Verification for the Remote Conversion
• Prepare the data transfer for the Remote Conversion using the BW/4HANA Conversion Cockpit
• Perform Data Model transfer for the Shell Conversion
4.17.1. Perform Data Migration & Verification for the Remote Conversion
The Remote Conversion includes the following aspects
• Transport of data flow related BW Objects from SAP BW to the new SAP BW/4HANA system
including the necessary update of object types (e.g. DSO to ADSO)
• Transfer of data for the selected data flows
• Change of logical system names to target ID, Request handling to TSN and if necessary SID-
Mapping of data
The Planning and preparation of the Remote Conversion has taken place in the Explore phase with the
Assessment followed by customer activities like system setup and software installation of the SAP
BW/4HANA system. In the Realize phase the first test cycle of the data migration can start.
After the transfer and conversion of the data flow related BW objects, the transfer of data for the selected
data flows take place.
Procedure
• Preparation of the data transfer using the BW/4HANA Conversion Cockpit and Task List
• Execution of test cycles
• Execution of Go-Live (see Deploy phase)
4.16.2. Prepare the data transfer for the Remote Conversion using the BW/4HANA Conversion Cockpit
and Task List
Prerequisite
The BW sender system and the BW/4HANA receiver systems are set up and the necessary pre-checks
are done.
Procedure
The Remote Conversion is performed using a toolset that consists of the BW/4HANA Conversion Cockpit
and the Task List application.
Figure 4.9: SAP BW/4HANA Conversion Cockpit
The BW/4HANA Conversion Cockpit offers status management and progress tracking to ensure a
comprehensive documentation of the executed activities. All activities are performed from within the
BW/4HANA Conversion Cockpit with a step-by-step guidance. In case of issues, the data transfer activity
picks up the process from the latest state – re-execution of already performed steps is not required.
Accelerators
• Conversion Guide for SAP BW/4HANA 1.0
• Remote Conversion Execution for SAP BW/4HANA
Procedure
Open the Transfer Cockpit and click “Execute Scope Transfer”. Select “Remote (Metadata only)”.
Choose that you want to create a new conversion run. The task list
“SAP_BW4_TRANSFER_REMOTE_SHELL” opens.
Select the step “Collect scope for transfer (Data Flow)”, here you define which objects should be
converted and execute the task list run.
Figure 4.11: Task List SAP_BW4_TRANSFER_REMOTE_SHELL
Note: To limit the scope to the least number of objects based on dependencies, you can select “Minimal
scope”. This options allows to separate the transfer of the reporting layer from the transfer of the staging
layer. This way you can, for example, convert a MultiProvider to a CompositeProvider without selecting
the Part Providers of the MultiProvider.
As a next step, define the object mapping between the old objects and HANA-optimized objects.
Proceed with the task list until the end of the Prepare phase.
Results
The selected Data Models and data flows are transferred from SAP BW to SAP BW/4HANA and
converted to HANA-optimized objects.
Accelerators
• Conversion Guide for SAP BW/4HANA 1.0
Cutover Preparation
Description
The purpose of this activity is to perform the final preparation steps for cutover. The cutover plan will be
tested in the Dress Rehearsal activity in the Deploy phase.
There is a technical design document stored in SAP Solution Manager which includes the technical
deployment plan, and the software components which need to be installed / updated.
Procedure
• Production System Setup
• Create Cutover Plan (New Implementation)
or
Prerequisites
This task is required for those scenarios which set up a new production system.
Prerequisite is that the productive hardware is already available and set up.
Procedure
• Execute the technical installation of the required SAP Products for PRD environment as
documented in the technical design document. See the installation guide how to install the
components.
• Run the technical system setup as documented in the administration guide.
• Transport development and configuration changes from the new QAS to PRD. Consider also the
manual rework activities as described in the administration guide.
Results
Finally the PRD environment is ready for final Go-Live simulations.
Procedure
• Execute Go Live Simulations 1 – n
The purpose of this task is to rehearse or simulate the cutover activities. During simulation, the main
objective is to validate and document the tasks, sequence, and duration of items on the cutover plan.
These simulations help determine data load efficiency, timing, and sequencing and foster an
understanding of requirements for the detailed cutover schedule.
The number of simulations varies from project to project, so do the objectives for each simulation.
Rehearsals are repeated until go-live risk is minimized. Load simulations give the project team a chance to
review the data for errors and data cleansing issues.
Results
After completing the simulations, the project team has very good understanding of the potential issues as
well as timing and sequence of the final production system data load. The project team is able to refine the
cutover schedule and make sure that it realistically reflects the time and effort required for all activities
during cutover.
Equally important is a contingency plan to handle issues that cannot be resolved within the planned
business downtime.
Procedure
The conversion of the production system requires a clearly defined cutover plan and will typically be
controlled by a cutover manager.
You can look up a sample cutover plan in the SAP Best Practices for system conversion for SAP
S/4HANA (accelerator section) for getting insight into the level of detail the cutover plan should have.
A cutover plan documents the end-to-end activities of the cutover; from the steps leading up to the event,
through to the end of the conversion. High-level tasks commonly found in cutover plans include:
Every task within the cutover plan should have an assigned owner, estimated duration, and identified
dependencies. Whenever possible, assign a name to the owner of the task, and not a team or group of
resources. The owner of each task should validate and approve the task to ensure they understand their
responsibilities. If there are any tasks required to specifically enable the conversion activities, the cutover
plan should include related tasks to reset the values to the intended productive state.
The cutover plan should also include a contingency plan to revert the changes in the event there is a No-
Go decision. If the contingency plan does not exist within the actual cutover plan, the cutover plan should
have reference to the location of the fallback plan.
Equally important, is a contingency plan in the event there is an unforeseen issue that is unable to be
resolved within the planned business downtime.
Accelerators
• Cutover Plan - Example
Sizing & Scalability Verification
Description
In this activity, the sizing estimation performed in the Explore phase (see activity Sizing in the Explore
phase) is further detailed out and verified afterwards. The initial assumptions made are now challenged
with KPIs from reality.
There is a documented sizing estimation from the Explore phase stored in SAP Solution Manager.
Procedure
• Optional: Perform Sizing Verification
• Optional: Perform Scalability Verification
Accelerators
• General Information on Sizing
• Proactive Performance and Capacity Management - Best-Practice Document
• Sizing Approaches for SAP HANA (incl. SAP S/4HANA and Fiori) – Lessons Learned Document
Prerequisites
There is a documented sizing estimation from the Explore phase stored in SAP Solution Manager.
Procedure
To validate the sizing projections, SAP proposes a two-fold approach:
The latter is based on technical resource consumption monitoring, the sizing report and application
workload analysis.
Results
The sizing estimation for the productive system has been validated.
Accelerators
• Service Information – Service Components for Platform Design
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
4.19.2. Optional: Perform Scalability Verification
Objective
To guarantee the success of the smooth processing of core business processes, these processes need to
be measured, tested and compared between the source and target systems. As a goal the converted SAP
system shall deliver the same or better performance indicators as compared to before the conversion.
Therefore the results have to be compared against the predefined performance baseline.
Prerequisites
There is a test system available which has comparable hardware than the future productive system.
Procedure
For the proper verification a test conversion will be performed on comparable hardware containing the
representative data volume. The different scenarios for single and mass load testing and verification are
set up and processed.
Results
The performance gain has been properly measured and documented in SAP Solution Manager.
Accelerators
• Planning High Volume Load Tests – A Methodology
IT Infrastructure Setup and Test
Description
In the Realize phase the technical infrastructure has to be installed and configured as required for the Go-
Live. Prior to the Go-Live, a technical verification is proposed to ensure that SAP Best Practices are
followed. The technical infrastructure follows the technical design document created in activity Technical
Design.
A technical design document has been created and stored in SAP Solution Manager.
Procedure
1. Set Up IT Infrastructure
2. Set Up Integration with SAP Analytics Cloud
3. Test IT Infrastructure
Results
The technical infrastructure has been properly tested.
• The setup of the server hardware, OS and (optional) virtualization platform: In the event SAP
HANA is delivered as an appliance, only sizing, floor space, power, cooling, and network need to
be considered. Keep additional setup activities for the SAP application server, or the storage layer
in case of TDI (Tailored Datacenter Integration) in mind.
• The setup of the storage solution: The physical setup of the storage infrastructure – storage
systems, storage network, connecting host systems to the storage network – requires
comprehensive knowledge of the selected components, and is usually done by system engineers
of the storage supplier.
• Integration of the new components into the existing IT environment (e.g. integration into the
existing backup or monitoring solution, network).
• Setup of High Availability, Disaster Recovery, and Backup.
Prerequisites
The IT infrastructure components are available and ready for setup.
Procedure
Proceed as follows:
• Install the IT infrastructure as designed in the technical design document, and dictated by the
conversion method and related conversion guides.
• Document or enhance the installation process in a cookbook for use with future builds.
The IT infrastructure is often set up by the hardware partner.
Results
The IT infrastructure is set up.
4.20.2. Set up Integration with SAP Analytics Cloud
Objective
Connect the SAP BW/4HANA to SAP Analytics Cloud.
There are two types of data connections possible: live data connections and import data connections.
Prerequisite
The decision to connect SAP BW/4HANA to SAP Analytics Cloud with a Live Data Connection or an
Import Data Connection has been taken.
Procedure
A live connection to the SAP BW/4HANA from SAP Analytics Cloud means that queried data from SAP
BW/4HANA always remains behind the corporate firewall and does not enter into the cloud. You can
follow the Guided Playlist to perform all required steps for setting up the Live Data Connection:
Figure 4.12: Guided Playlist for SAP BW Live Data Connection
With the Import Data Connection, data is queried from SAP BW/4HANA and is imported to SAP Analytics
Cloud.
You can follow the Guided Playlist to perform all required steps for setting up the import data connection.
Figure 4.13: Guided Playlist for SAP BW Import Data Connection
In detail, the following setup steps have to be performed, using the SAP Analytics Cloud Agent Simple
Deployment Kit (for more information, see „SAP Analytics Cloud Agent Simple Deployment Kit“ in the
accelerator section):
• Install the cloud connector. For more information, see „Installing the SAPCP Cloud Connector“.
• Install the SAP Analytics Cloud agent. For more information, see „Installing SAP Analytics Cloud
Agent“.
• Install the SAP Java Connector (must be installed using the instructions in the Post-Setup Guide
included in the kit - for more information, see „Installing the SAP Java Connector“).
• Configure the SAPCP cloud connector. For more information, see „Configuring the SAPCP Cloud
Connector“.
• Configure the SAP Analytics Cloud agent in SAP Analytics Cloud For more information, see
„Configuring SAP Analytics Cloud Agent“.
Accelerators
• SAP Analytics Cloud Guided Playlists
• SAP Analytics Cloud Agent Simple Deployment Kit
• Installing the SAPCP Cloud Connector
• Installing SAP Analytics Cloud Agent
• Installing the SAP Java Connector (JCo)
• Configuring the SAPCP Cloud Connector
• Configuring SAP Analytics Cloud Agent
• https://blogs.sap.com/2017/11/28/sap-analytics-cloud-live-data-connection-to-sap-bw4hana-using-
cors-and-sso/
• SAP Analytics Cloud: Live Data Connection to SAP BW/4HANA using CORS and SSO
Prerequisites
The IT infrastructure has been set up.
Procedure
Proceed as follows:
• Execute the infrastructure tests based on the test cases and test plan. This should include the
following scenarios:
o Performance
o Flexibility procedures (e.g. by moving system load to other hosts (e.g. by using
virtualization technics), adding instances, changing instances)
o High Availability
o Disaster Recovery
o Backup and Restore
o Infrastructure Security
• Document any anomalies or defects.
• Monitor the test system as if it were production, as this will provide an indication of end-state
operations. It is important to leverage this testing cycle to proactively address issues that could
arise in production.
• Measure the performance against the defined key performance indicators to ensure the
infrastructure operates within the boundary conditions of the business (see activity performance
verification).
• If already available, test the productive hardware as well at this point in time, in order to validate
the configuration. Otherwise, the productive hardware is tested in the Deploy phase.
• Resolve any defects, and retest to ensure all identified issues are closed.
Results
The IT infrastructure has been tested properly.
Operations Implementation
Description
Based on the outcome of the Operations Impact Evaluation in the Explore phase, support operations need
to be implemented or adjusted. This may affect the IT support staff (their roles and responsibilities;
knowledge transfer), support processes and procedures (including proper documentation), and the setup
and configuration of support tools.
The documented results of the Operations Impact Evaluation (Explore phase) are stored in SAP Solution
Manager.
Procedure
1. Collect detailed Operations Requirements
2. Roles and Responsibilities
3. Support Processes and Procedures
4. Operations Support Tools
5. Operations Documentation
6. Knowledge Transfer
Results
IT support operations has been prepared to operate SAP BW/4HANA as of Go-Live.
• SAP ESRV System Monitoring: System, Database and Host Monitoring – empowering and
knowledge transfer are the main goals of this service
• SAP ESRV Integration Management: Empowerment and knowledge transfer on interface and
connection monitoring are the main goals of this service
• SAP ESRV Root Cause Analysis and Exception Management: Empowerment and knowledge
transfer
• SAP ESRV Data Volume Management (see Activity Data Volume Planning)
• SAP ESRV Test Management: This service is used to implement the ALM process “Test
Management” on a pilot basis at a customer. The pilot implementation addresses the processes of
User Acceptance-, Functional-, integration-, and Regression Testing (including Test Scope
Identification and Test Automation)
• SAP ESRV Security Engagement: This service will help the customer on tuning their operations on
different aspects based on the needs of the customer, for example:
o Identify the key security topics of interest
o Complement the view by a high level 360 degree review on potentially relevant security
areas and by recent security news
o Define the focus spots to be addressed and set up a project plan
o Define Improvements of the customer’s security situation
• System Administration Workshop: update for SAP BW/4HANA will be available in Q2/2017
• SAP Solution Manager Starter Pack: Guidance for the customer on the initial configuration of SAP
Solution Manager
• SAP Empowering Services: Empowering IT resources to maintain, operate, administer an SAP
component
Accelerators
• Service Information – Service Components for the Transition to Operations
• SAP System Monitoring Service
• SAP Integration Monitoring Service
• SAP Root Cause Analysis and Exception Management Service
• SAP Data Volume Management Service
• SAP Change Control Management
• SAP Test Management
• SAP Security Management
• SAP System Administration Workshop
• SAP Solution Manager Starter Pack
• SAP Empowering Service BW
In other words, it works like the software change management process and a list of change requests to
the IT support framework has been defined. Those have severities and priorities based on the customer
management decisions.
This activity takes place during the Explore phase with the primary goal to raise the awareness of IT upper
management on how the current IT support framework will be impacted. New project activities will be
defined to fill the gaps and this will mean changes in the project plan, potentially additional cost and
resource conflicts that will have to be addressed. Analyzing the necessary changes to the IT support
framework later in the project will make it more and more difficult to manage these conflicts. Not planning
the future support framework will increase the risks of issues in operations after go-live and can be the
cause of poor customer satisfaction and increased project costs as often project resources end up with
extensions in their involvement to support the new solution. The downside of having the Operations
Impact Evaluation take place early in the project is that a lot of details are not yet known, and the specific
requirements for the changes to the support framework cannot be always gathered. This needs to happen
later in the project.
During the Operations Implementation, the project activities defined and prioritized during the Operations
Impact Evaluation need to be executed, in other words all the IT related change requests need to be
implemented. The first step will be to define the detailed information required for their implementation,
their detailed specifications like which interfaces need to be monitored, key objects to be monitored to
ensure data consistency or which access needs to be granted to the future support team members. For
this to happen a coordination task needs to take place where the detailed information is gathered from
other project activities.
Prerequisites
The Operations Impact Evaluation has taken place and the detailed activities necessary to ready the
future IT support framework for the operations have been added to the project plan.
Procedure
The detailed information required to prepare the future IT Support Framework is well known from other
project tracks, for example:
• The Business Process priorities are defined during the Application Design which includes the critical
processes, interfaces, and jobs. This will serve as a direct input to the monitoring setup with
information on the underlying systems and the solution components.
• The new/modified roles and authorization objects will be defined as well during Application Design
and during the Technical Architecture. This will bring input to finalizing the new Access Management
process with the differences in roles assignments, and this for business users as well as for the
support resources.
• The inventory of modifications to non-standard SAP code will be defined during Development. This
will be a critical input to Knowledge Transfer for the new technical support resources.
During the Operations Impact Evaluation, activities related to gathering detailed information will be defined
for each area of the support framework that needs to be modified. The way to gather the related
information will depend on the project structure and responsibilities.
Note: Defining a transition manager to manage all the Operations Implementation activities will make it
more efficient than having each activity responsible go to the project resource having the knowledge
required for his activity. The transition manager can regroup the detailed information required for the
different activities and gather the corresponding details from the best project resources at once.
When you implement SAP BW/4HANA, there are changes in the roles and responsibilities of some of
these resources. These changes will highly depend on your current solution (if you already have SAP
implemented), on your support strategy (if you engage a Service Provider to support your SAP
BW/4HANA solution), and on your deployment strategy (cloud vs on-premise).
Prerequisites
The documented results of the Operations Impact Evaluation (Explore phase) are stored in SAP Solution
Manager.
Procedure
The following IT support processes are potentially affected with the implementation of SAP BW/4HANA:
• Event Management:
o Analyze process change in event management caused by new/modified/retired
monitors
o Retire obsolete monitors, and monitor templates (in SAP Solution Manager)
o Retire obsolete manual monitoring procedures
• Incident Management:
o Update assignment groups, review incident triage
o Update support resources
o Update incident categorization
o Process flow and escalation management including partners and SAP
o Remove obsolete incident attributes
• Problem Management:
o Update problem management process to include new analysis tools
• Service Level Management:
o Update SLAs if required (due to changed business KPIs)
o Update SLA reporting
• Access Management:
o Access for new solution / tools granted to new support team members including
partner resources
o New/changed access management process for new/changed solution items (e.g.
SAP HANA database)
• Change Management:
o Update support resources including requesters and new approvers
o Update categorization, if required
o Process flow including partners and escalation management
o Include project defects in incident database
o Remove obsolete change attributes
o Evaluate current change process to include e.g. SAP HANA changes
• Test Management:
o Test library should include new test plans/scripts
• Job Management:
o Adapt job schedule caused by the new, modified and retired jobs (certain batch
jobs may no longer be required, as a result of some reports being able to execute
in dialog)
• Data Volume Management:
o Changed tools and activities due to new concepts in data volume management
(e.g. data aging)
o Adapt process in those areas where classic data archiving is no longer available
• System Recovery:
o Adapt system recovery process to reflect the changed HA/DR architecture
IT support processes need to be tested, and access to the new support tools need to be considered.
Training on the IT support process changes needs to be in place (or communication in case of small
changes).
SAP has a lot of experience and additional recommendations on IT support process design that are
required for the efficient support of the new SAP BW/4HANA. Please contact SAP for a tailored offering in
case you need support.
Please also remember the Primary CCOE Certification which need to be in place for Enterprise Support
customers.
Accelerators
• Customer Center of Expertise
• Getting Started with Primary CCOE
• Primary CCOE Check List
• SAP Support Standards
For “Greenfield” customers, the effort required to implement the tools will be much greater. This will
require additional effort for the support resources to learn how to use the tools, especially SAP Solution
Manager.
Prerequisites
The documented results of the Operations Impact Evaluation (Explore phase) are stored in SAP Solution
Manager.
Procedure
With the introduction of SAP BW/4HANA, it may be required to adjust existing IT operational support tools,
or to set up new tools (e.g. SAP HANA cockpit in case this is the first system on top of SAP HANA).
The following list gives you some common examples where adjustment activity may take place. The main
list should have been created in the Operations Impact Evaluation (see activity Operations Impact
Evaluation in the Explore phase for details). See the Accelerators section for more information on how to
execute the necessary adjustments. As part of the Premium Engagement packages, SAP has dedicated
offerings to support this task.
Plan to ramp down support tools (e.g. DB specific scripts your database administrators used in the past),
which are no longer required, and adjust IT support procedure descriptions accordingly.
Accelerators
• SAP Support Standards
• Applications Operations WIKI for SAP Solution Manager
• SAP HANA Administration Guide
• SAP HANA Technical Operations Manual
• Monitoring SAP Fiori Apps
• Troubleshooting SAP Fiori Apps
4.21.5. Operations Documentation
Objective
IT operations documentation should be stored centrally in an operations documentation repository, which
is then shared across all operational support teams.
Prerequisites
The documented results of the Operations Impact Evaluation (Explore phase) are stored in SAP Solution
Manager.
Procedure
Adapt all operational documentation that changes with SAP BW/4HANA. The content needs to be
provided by the project team, based on SAP standard documentation that is modified with respect to
customer solution specific information.
Store the updated operations handbook centrally, either in a company Content Management System, or in
SAP Solution Manager.
Based on activity Operations Impact Evaluation, and on activity Operations Support Tools, the operational
procedures are updated in the operations handbook.
The following areas are typically included in the operations handbook (besides others):
• System Description: Outlines new functions and capabilities, high level architecture, integration
details, number of users, expected volumes, use cases, priorities, etc.
• System Architecture: Architecture, sizing and technical setup information of Solution Manager and
other operations tools.
• Access, Roles and Profiles: Identifies user groups, roles and role approval list
• Restart and Recovery Procedures: Outlines how to restart or recover from process failures and
clearly describes error messages and conditions.
• Backup / Recovery: Documented process of the backup / recovery methodology; includes standard
and emergency backup scheduling and approval process.
• Batch Scheduling: Documents and presents the batch job schedule. Includes details on the jobs
(e.g. stop, restart, criticality, owner, failure procedure), and the batch scheduling tools (if applicable).
• Run Books: A collection of routinely executed procedures either performed through automated
means or manual execution by system administrators (example: system stop and start procedures).
• Storage Management: Provides technical information on the storage and when to add storage; may
also contain instructions on data volume management.
• Disaster Recovery: Documented process of the recovery steps in case of a disaster (and the
disaster declaration procedure itself).
• Maintenance Management Strategy: Documents the process to implement patches and upgrades
(in alignment with the change management strategy).
• Network Management: Maintenance instructions for the network, network settings and parameters.
If applicable, also contains vendor contact information.
• Non-Functional Requirements: The requirements that do not affect the solution but affect the
behavior of the system. It includes availability, maintainability, performance, scalability, security,
and system usability.
• Output Management: Defines the settings and management for all output mechanisms such as
printers, fax machines, emails, etc.
• OS & DB parameters: Defines the operating system and database parameters (and a procedure
description how change parameters according to the change management process).
• Vendor Information: Vendor contact information for operations support, and the minimum set of
information which needs to be provided.
• IT Calendar: Identifies agreed maintenance windows, backups and additional
technology/infrastructure activities in calendar format.
How SAP Can Support
SAP has a lot of experience in creating a tailored operations handbook. Please contact SAP for a tailored
offering in case you need support.
Accelerators
• SAP Support Standards
• SAP HANA Administration Guide
• SAP HANA Technical Operations Manual
• Monitoring SAP Fiori Apps
• Troubleshooting SAP Fiori Apps
• SAP Fiori Troubleshooting Guide
• SAP Fiori UI Development Toolkit
• Define a repetitive process that can be applied for each release and to new hires
• Reduce or mitigate risk through ownership and accountability
• Develop metrics to capture and assess performance for knowledge transfer capabilities
Prerequisites
The documented results of the Operations Impact Evaluation (Explore phase) are stored in SAP Solution
Manager.
Procedure
To define the Knowledge Transfer Approach for a new solution Go-Live, you will need to take many
aspects into account including:
• The alignment of the knowledge transfer with the overall system conversion project plan
• The project scope and initial definition of all the knowledge transfer areas to be planned: the
functional areas are to be defined, and all technical areas (especially the new ones like Fiori) as
well as new support tools
• The project methodology and documentation
• The future support organization
• The availability of the project support resources now and in future (workload and time)
• The hyper care phase exit criteria as per contract
• The sponsorship for the knowledge transfer activities, both for the project and the future IT support
operations team
The following criteria could be considered to decide when knowledge transfer to the IT support operations
team is complete:
• All high-priority failures resolved
• All high-priority gaps implemented
• All deferred requirements fully documented and specified
• All deferred requirements development planning completed
• All deferred requirements testing planned
• All deferred requirements release scheduling planned
• Master Data is operational and no critical issues exist
• Interfaces are running stable
• All business critical reports are available
• Knowledge transfer is documented
• Service Desk call level is manageable with the team in place, to conduct Level-1 support
immediately
The Project Management Plan developed during the Prepare phase for each of the PM knowledge areas
guides the team's approach to management, execution, monitoring, and control of project activities. This
methodology provides steps to be considered when each activity is engaged and supported by the team's
monitoring/controlling plans. The project manager is responsible for ensuring that the
monitoring/controlling plans developed in the planning phase are applied at the appropriate level of
control.
Tasks
• Direct and Manage Project Execution
• Update Project Management Documents
• Manage Project Issues, Risks, and Changes
• Communicate Project Status and Progress
• Plan and Execute Agile Sprints
• Perform Scrum-of-Scrums Meeting (Iterative)
In executing the project work, the project team will perform the following types of activities:
In monitoring/controlling work results, the project team performs the following types of activities:
Management plans developed during the Prepare phase guide the team's approach to management,
execution, and control of project activities. See “Prepare Project Management Plan” task in the
Prepare phase for details. The project manager is responsible for ensuring that the management
plans are applied at the appropriate level of control.
The project management documents are, together, a comprehensive body of project documents that
includes the project schedule, budget/cost information, monitoring/controlling plans for each of the nine
knowledge areas of the Project Management Body of Knowledge (PMBOK), and other information as
appropriate. The project management plan document developed for each of the knowledge areas provide
the foundation for the consistent application of project management practices.
• Project WBS
• Project schedule
• Project budget
• Business case
• Scope document
In on-premise projects, this environment is the SAP Solution Manager, and depending on the type and
status, it may be directly transferred over to SAP for resolution.
In cloud projects, teams are advised to use a dedicated issue tracking document based on the Open Issue
List Template in the SAP Activate methodology.
• During the issue creation, the person raising the issues assigns the priority and the responsible
person for resolution of the issue.
• The Project Manager follows up on issues on a regular basis in addition to the standard issue
management process defined for the project (part of the management plans)
• Critical issues will be reviewed as an input for each Quality Gate review meeting.
Open issues are reviewed and updated on a regular basis and communicated to the appropriate
stakeholder groups as part of the regular project reporting and communication.
From SAP's perspective, issue tracking allows for better visibility and transparency of open issues,
problems, action items, and associated action plans to the project management team.
A central issue tracking system (e.g. a support or an incident ticket system) allows stakeholders to
manage and maintain lists of issues that require action and resolution to ensure the success of the project.
• Team member status update produced typically weekly and shared with the team lead. It is
recommended that this report is kept very lightweight and provided to the team lead via e-mail or
in a team meeting.
• Team status reports on regular cadence, typically weekly. The team status reports are prepared
by the team leads and are delivered to the project manager as an input for the project status
report. The team status report may be reviewed in regular team review with the Project Manager
or provided in a predefined format.
• Project status report, using the project status report template. The project status report is
created weekly, based on the input from individual teams and additional information like issues
list, risk list, etc.
• Executive status report is typically prepared on monthly or quarterly cadence and is provided to
the project executive steering group. Generally, this report re-uses the key information from the
weekly project status report, expands on the value and benefits of the program, and includes
discussion of the decisions that are needed from the executive steering group.
Additionally, throughout the project, as more is known, the project communication matrix should be
reviewed and updated. The communication matrix documents the project team’s approach to
communication (including status reporting). It captures the analysis completed as part of communications
planning and serves as a tool to guide the project team throughout the project.
4.22.5. Plan and Execute Agile Sprints
Objective
The purpose of this task is for the project team to plan and execute agile sprints. The project team runs
the Realize phase in sequence of sprints in which the project team follows the process outlined below.
The goal of these sprints is to incrementally and iteratively build the solution capabilities captured in the
backlog, test them and review their completion with the customer process owners (product owner in agile
terminology).
At the beginning of the sprint the project team runs a planning meeting during which the team (jointly with
the process owner) select the highest priority items from the backlog and conducts detailed planning for
the execution activities in the sprint. Each backlog item is further decomposed to tasks that need to be
completed during the sprint. These tasks may be configuration, coding, unit testing, data preparation,
documentation and others. These tasks are then captured in the sprint backlog and estimated to validate
the original estimates for each backlog item. As a result of this planning the team has clarity on what
needs to be completed for each backlog item included in the sprint and has confidence that the team has
sufficient capacity to complete the work.
During the sprint the team members execute the tasks that have been planned and the team keeps track
of the progress on the team board. The team board contains swim lanes showing the status of each
backlog item and each task. Teams are encouraged to use boards on the wall and use the post-it notes to
keep visual track of their progress.
The team also regularly updates the burn-down chart that is used to track the progress of completing the
individual tasks and backlog items. The team reviews the progress on a daily basis in the daily stand-up
meeting.
Daily Stand-up Meeting
During the daily stand-up meeting the team members review the (a) progress they have made since last
meeting; (b) plans for activities and tasks until the next meeting; and (c) any issues of blockers that may
prevent them from completing the tasks they are working on. The daily stand-up meeting is not a project
status meeting, but rather a session designed to help the team communicate the progress with each other.
Sprint Demo
Towards the end of the sprint the team conducts the sprint demo meeting during which the team
demonstrates to the business owners (product owner in agile projects) the completed functionality. The
project team seeks acceptance of the completed features. During this meeting the business owner may
request additional items to be added to the backlog (or items to be removed from the backlog). It is
recommended that the team previews the functionality with process owners prior to this meeting. Many
projects had great experience with having the business process owners demo the completed functionality
to the rest of the business users and decisions makers (instead of the project team members).
Sprint Retrospective
SCRUM Master organizes and facilitates the retrospective meeting for the team. The meeting is typically
scheduled shortly after the sprint demo meeting. Purpose of the meeting is to continuously improve the
Scrum process using lessons learned from the sprint execution.
The team selects one or two improvement opportunities and puts it into the backlog for the next sprint.
This way the agile process gets improved in an incremental way and remains responsive to the changing
environment of the project.
Accelerators
• Agile Release Planning (Customer)
• Backlog Template
Accelerators
• Agile Scrum Meeting Guidelines (Customer)
OCM Alignment Activities
Description
The purpose of this deliverable is to identify and assess other OCM relevant areas.
Tasks
• OCM and Testing Alignment
• OCM and Data Migration Alignment
Procedure
• Perform Assessment of Testing Strategy and Execution
• Capture Feedback from Testing Team
Procedure
• Perform Assessment of Data Migration Strategy and Execution
• Capture Feedback of Data Migration Team
• Ensure that all required deliverables from this phase and the project are complete and accurate,
and close any outstanding issues
• Identify lessons learned during the phase to prepare for formal phase closure
• Capture customer feedback and potential Customer References
Tasks
• Conduct Knowledge Management Gate
• Conduct Project Quality Gate
• Conduct Project Management Review Service
• Conduct Design Review Service
• Manage Fulfilled Contracts
• Obtain Customer Sign-Off for Phase Completion
4.24.1. Conduct Knowledge Management Gate
Objective
The purpose of this task is to collect knowledge assets and lessons learned at the end of each phase of
the project that can be reused later by other projects. Collecting documents, experiences, project
highlights and lessons learned throughout the duration of the project can help to facilitate the project by
providing quick access and insights into key deliverables from earlier stages of the project.
Accelerators
• Lessons Learned Guide (Customer)
• Lessons Learned Template (Customer)
A Quality Gate is a checklist milestone at the end of a project phase. Prior to moving into the next phase
each project manager must demonstrate that they have complied with the mandatory deliverables
associated with a methodology while ensuring best practice standards have been applied to ensure
quality. In detail:
• To assure that all key deliverables and actions of the gate have been completed in compliance
with recommended practices and to the customer’s satisfaction
• To enable project management to continuously communicate the process and build quality directly
into the project
• To provide a tool to effectively manage project expectations and monitor customer satisfaction.
The deliverables assessed at each quality gate will be performed using the quality gate checklist
with defined expectations to the maturity of particular project deliverables.
Note: New additional key deliverables need to be added in the quality gate checklist by the Project
Manager to the different project types.
Accelerators
• QGateChecklist Concept SAP Activate
• QGateChecklist Template Introduction
• Quality Built In New QGate Checklist
• Ensure that all required deliverables from this phase and the project are complete and accurate,
and close any outstanding issues
• Identify lessons learned during the phase to prepare for formal project closure
Accelerators
• Phase Sign-Off Template (Customer)
5. Deploy Phase
Once quality gate Q3 – Realize-to-Deploy has been passed successfully, the final preparation for Go-Live
starts in the Deploy Phase.
End user trainings for the new solution are running in the Application: Solution Adoption work stream.
In the Application: Design & Configuration work stream, the implementation activities will come to an
end. Integration validation ensures the required performance.
Testing (in particular regression and user acceptance testing) is taken care of in the Application: Testing
work stream. All affected custom code should have been adapted and tested in the Realize phase
already. Overall there is nothing to do in the Custom Code Extensions work stream in the Deploy phase.
In System & Data Migration, the final rehearsal of the cut-over procedure will take place. Most
importantly, this work stream processes the implementation of the productive system which will be
finalized at the Go-Live weekend.
In the Technical Architecture and Infrastructure work stream, final IT service setup activities will take
place.
Transition to Operations ensures the IT operations team is ready to operate the new system
environment safely and securely. Of course the IT operations team will continue to gain real-life
operational experience in the hyper care phase after Go-Live.
Quality gate Q4 Deploy-to-Run will ensure that everything is ready for Go-Live. The final “Go” decision is
the start for the implementation of the productive system. The Deploy phase ends with the production
cutover at the Go-Live weekend.
Phase Initiation
Description
The purpose of the phase initiation deliverable is to formally recognize that a new project phase starts.
Tasks
• Allocate Resources and Update Project Schedule
• Perform Kick-off Meeting
Accelerators
• Project Setup Checklist Sample (Customer)
Accelerators
• Global Resource Management Portal page (SAP Employee)
Accelerators
• Project Kick-off Template (Customer)
Learning Realization
Description
This activity continues from the Realization phase. Based on the learning material which has been created
there, end user training takes place in this phase.
Procedure
1. Create Training Execution Plan
2. Execute End User Training
Results
The end users have been trained. They are enabled to use the new system.
Procedure
.
The training execution plan should include:
Prerequisites
A training execution plan has been created before.
Procedure
The training will be performed either by the customer key user in a tandem approach with SAP trainers, or
by SAP trainers only. Assumptions and/or pre-requisites for the trainings are described in the training
concept prior to the end user trainings. Examples are:
Results
As a result, end users are trained. SAP recommends issuing participation certifications, and collecting end
user feedback.
With event and invitation management, SAP can support this task as part of an individual education
consulting offer from SAP Education. Event and invitation management is the process of booking training
facilities /resources, managing courses in the learning management solution, and publishing learning
content in the digital environment. For instance, SAP can:
• Send invitations to trainers and end users including all necessary information
• Prepare facilities (virtual or onsite) for training delivery
• Allocate properly sized and equipped rooms for training (including network connection)
• Organize training material distribution.
Accelerators
• SAP Enable Now at SAP Online Help Portal
Integration Validation
Description
The Integration Validation activities initiated in the Realize phase, are continued and finalized in this
activity.
Procedure
Finalize the Integration Validation activities which have started in the Realize phase (see activity
Integration Validation).
Results
As the result of this activity, integration validation has been finished.
Prerequisites
Integration Validation has started in the Realize phase.
• Integration Validation service component: This service component provides technical validation of
core business processes with respect to non-functional requirements, identification and addressing
of technical risks prior to Go-Live and during the production cutover including hyper-care phase. A
comprehensive status of technical Go-Live readiness for core business processes (Integration
Validation matrix) is part of the service component.
• Business Process Technical Validation service component: This service component ensures
technical readiness of the core business process for Go-Live. It addresses areas like data
consistency, exception management, performance and scalability, system integration, batch and
volume processing. In the focus is the technical validation of the core business processes and
preparation for the subsequent efficient operation of the software solution.
• Technical Performance Optimization service component: The technical performance optimization
service component improves your SAP solution by helping you to configure your system in an
optimal way. The identification and elimination of costly performance bottlenecks optimizes the
response times and throughput of your SAP solution.
SAP Enterprise Support Customers can order the CQC for Technical Performance Optimization (TPO).
Accelerators
• Service Information – Service Components for Safeguarding the Digital Transformation
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• CQC for Technical Performance Optimization (TPO)
Dress Rehearsal
Description
In preparation for the Go-Live of the transition project, it is imperative to execute an end-to-end dress
rehearsal of the cutover procedures. The rehearsal should be executed about two to four weeks prior to
the Go-Live. All changes intended to be included in the cutover should be available for the dress
rehearsal. This includes any changes that result from the testing cycles, as even a single transport could
greatly impact the duration of the process.
From this point forward, changes to production should be restricted in order to mitigate risks to the cutover
procedures (system conversion only). If there is a need to make a change to production after this point, it
should be carefully evaluated and the impact should be fully understood. In some cases, there may be a
requirement to postpone the Go-Live and re-execute the dress rehearsal in order to accommodate
intrusive changes.
1. The detailed cutover plan with owners, dependencies and durations fully documented.
2. The involvement of all task owners.
3. A test environment representative of the source and target platforms for production.
4. The technical cookbook, which details all of the required technical migration steps.
Procedure
• Perform Cut-Over Rehearsal
Procedure
Execute the cutover plan in its entirety in a non-productive environment, which is representative of the
current state and end-state of production.
The dress rehearsal is intended to be used to confirm the ownership, sequence, and duration of the
cutover procedures. If significant changes to the process are required as a result of the dress rehearsal,
there may be a need to postpone the Go-Live.
It is also very critical to communicate the latest plan to related parties to ensure a smooth Production
Cutover for the last time.
Procedure
Proceed as follows:
• Complete the setup of the IT infrastructure hosting production (e.g. hardware setup, network
connections, etc…).
• Correct all critical open items which have been detected in the IT infrastructure test (see activity IT
Infrastructure Setup and Test in the Realize phase for details).
• Finalize IT infrastructure service definition and documentation as part of the IT service catalog
(properly explaining for instance what SLAs IT is offering to the Lines of Business for a particular IT
infrastructure service).
Results
As a result, the IT infrastructure is ready for hosting production.
Operations Readiness
Description
This activity checks the customer’s ability to operate SAP HANA and SAP BW/4HANA as of Go-Live.
Procedure
• Operational Readiness (System Conversion)
or
Procedure
Check if all operational aspects have been implemented as planned (see Operations Implementation
activity in the Realize phase). This covers:
Results
The IT support organization is ready to operate SAP BW/4HANA as of Go-Live.
Accelerators
• Service Information – Service Components for the Transition to Operations
Procedure
For customers who know how to operate SAP BW already: Check if all operational aspects have been
implemented as planned (see Operations Implementation activity in the Realize phase). This covers:
• Check if all operational aspects have been implemented as planned (see Operations
Implementation activity in the Realize phase).
• Check if all IT Support Processes have been implemented / adjusted with respect to SAP
BW/4HANA operations (see SAP Support Standards).
• Check if primary CCOE certification has been gained.
For new SAP customers, SAP offers additional expertise and help to check and ensure operational
readiness before Go-Live. See also the Organizational and Production Support Readiness Check as part
of OCM in this phase. Please contact SAP for a tailored offering in case you need support.
Accelerators
• Service Information – Service Components for the Transition to Operations
• Customer Center of Expertise
• Getting Started with Primary CCOE
• Primary CCOE Check List
• SAP Support Standards
Tasks
• Update Project Management Plan
• Direct and Manage Project Execution
• Monitor and Control Project Activities
• Manage Issues, Risks and Changes
• Communicate Status and Progress to Project Stakeholders
Accelerators
• Project status report for SAP Activate / S/4HANA
Accelerators
• Change Request Log - template (Customer)
• Open Issues List Template.xls (Customer)
Accelerators
• Project status report for SAP Activate / S/4HANA
Release Closing
Description
The purpose of this deliverable is to formally close the release and prepare for next release and/or sprint
planning meeting.
Tasks
• Prepare Product Backlog for Next Release/Sprint
• Conduct Release Retrospective
• Update the Release and Sprint Plan
Accelerators
• Agile Sprint Retrospective Template (Customer)
Accelerators
• Backlog including Delta Requirements and Gaps.xlsx
Production Cutover
Description
The purpose of this deliverable is to perform the cutover to the production software and go live.
This activity is mandatory for all scenarios. The steps being performed are of course scenario specific.
Procedure
• Convert Productive System (System Conversion)
or
or
Results
After completion of this activity, the productive SAP BW/4HANA system is available for the end users.
SAP Enterprise Support customers can request a Continuous Quality Check (CQC) for “Going-Live
Support”. Ask your SAP Enterprise Support Advisor for details.
Accelerators
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
• Service Information - Value Assurance Foundation
• CQC for Technical Performance Optimization (TPO)
Procedure
Proceed as follows:
1. Request Restore Point of Production System Prior to Final Cutover Activities
2. Execute the conversion of the production system following the tasks defined in the cutover plan.
3. Document the actual duration of each step to support future projects.
4. Capture any variances to the plan along with decision maker who approved the change.
5. The cutover manager(s) should proactively notify task owners of upcoming tasks, to ensure their
availability.
6. Regularly communicate status to stakeholders.
7. After conversion has finished (including mandatory post-processing activities), the system has to
be tested and validated
8. Obtain system sign-off
Results
The customer approval (sign-off) documents the agreement with the stakeholders that cutover tasks have
been executed, the go-live acceptance criteria have been met, and the cutover is finished. It indicates
formal approval to end the cutover activities. At this point, the solution is live in production.
Procedure
1. Execute the cutover following the tasks defined in the cutover plan. This includes the final
production data load.
2. Document the actual duration of each step to support future projects.
3. Capture any variances to the plan along with decision maker who approved the change.
4. The cutover manager(s) should proactively notify task owners of upcoming tasks, to ensure their
availability.
5. Regularly communicate status to stakeholders.
6. After the data is loaded, testing and data reconciliation must be completed.
7. Obtain system sign-off
Results
The customer approval (sign-off) documents the agreement with the stakeholders that cutover tasks have
been executed, the go-live acceptance criteria have been met, and the cutover is finished. It indicates
formal approval to end the cutover activities. At this point, the solution is live.
Post Go-Live Enduser Training
Description
The purpose of EU training is to ensure that end users have adopted the solution, knowledge resources
are maintained, and responses to the end-user acceptance survey are positive
Tasks
• Prepare End-User Training for Scope Option
• Deliver End-User Training for Scope Option
• Collect Training Evaluations Feedback
• Perform People Readindess Assessment
Tasks
• Finalize Solution Manager Update – Solution Documentation
• Obtain Solution Transition to Production Acceptance Protocol Sign-off
Workload analysis
With the analysis of the current hardware consumption, the load distribution across the different
applications and task types, as well as average response times you establish a kind of benchmark to
measure the success of the conversion. As response times are very sensitive KPIs it makes sense to
capture its data over a long period of time, ideally more than six months (this can be established by
collecting monitoring data long term in SAP Solution Manager).
The scalability analysis contains system health checks (DB buffer, wait time, etc.) as well as the
identification of statements that cause bottleneck situations.
Sizing verification
Customers should monitor the technical KPIs in terms of CPU and memory consumption to assess the
actual usage vs. the deployed hardware.
Precondition is that the Monitoring Infrastructure (SAP Solution Manager preferred) is already set up.
Procedure
• Monitor Resource Consumption
• Analyze Workload
• Check System Scalability
• Run Going-Live Service (Verification Session)
Accelerators
• Service Information – Service Components for Safeguarding the Digital Transformation
• SAP Value Assurance for SAP BW/4HANA – Service and Service Component Descriptions
Procedure
The following KPIs are to be measured:
1. Physical CPU consumption over time (SAP application and DB server): [average per month /
week / day]
2. Workload profile (SAP application and DB server): [peaks, averages, load balancing]
3. Consider seasonal fluctuations: [e.g. period end closing]
4. Memory consumption (SAP application and DB server): [buffer settings and usage]
Procedure
You measure the following KPIs
Procedure
Proceed as follows:
1. Sort the list of top consumers by the consumption of the resource that is the largest bottleneck.
2. Check, starting with the largest resource consumer:
o Whether it is possible to reduce the resource consumption by optimizing the database or
the coding that is responsible for the resource consumption.
o Whether it is possible to avoid the bottleneck by optimizing load balancing and scheduling
of services.
o Whether the business value obtained from the service justifies the resource consumption.
As a result, the load drivers on your system are thoroughly understood. The top resource consumers are
well optimized and their business relevance is known. Optimal support for the business can be provided,
even for changing business requirements. Knowing the load drivers for the top resource consumers allows
to predict the effect of changing business beforehand.
Four to six weeks after Go-Live the verification session of this service should take place. This session
analyzes the converted system, and provides corrective measures to avoid potential bottlenecks.
Procedure
Proceed as follows:
Accelerators
• SAP OS/DB Migration Check
• CQC OS/DB Migration Check
• SAP Going-Live Functional Upgrade Check
• CQC for Upgrade
• SAP Going-Live Check for Implementation
• CQC for Implementation
Handover to Support Organization
Description
Once the hyper care phase ends it is important to fully enable the regular support organization at
customer site to safely and securely operate the new SAP system. This includes (but is not limited to):
Procedure
1. Resolve and Close Open Issues
2. Handover Operations Responsibility
Evaluates process management knowledge transfer and IT support team capabilities for
future maintenance
The Handover to Support scope option builds on top of deliverables created in the functional design
and execution services.
Please ask your SAP contact (e.g. SAP Client Partner) for more information.
Accelerators
• Build Execution
Procedure
The purpose of this task is to achieve a closure of all open project issues. In case this is not possible
within acceptable time, prepare for an agreement with the IT operations team to take responsibility to
resolve and close the issue. Hand over the current analysis and correction state to the IT operations team.
Prerequisites
• System documentation is complete and available.
• Operations procedures are fully documented in the operations handbook.
• The IT support operations team is set up and trained to safely and securely operate and
troubleshoot the new SAP system.
• The top issues and priority incidents identified during hyper care, are either solved, or there is a
documented work around and move-forward plan available.
Procedure
Hand over operations responsibility to the IT support operations team.
Project Closure and Sign-Off Project Deliverables
Description
The purpose of the phase closure and sign-off deliverable is to:
• Ensure that all required deliverables from this phase and the project are complete and accurate,
and close any outstanding issues
• Identify lessons learned during the phase to prepare for formal phase closure
• Capture customer feedback and potential Customer References
Tasks
• Conduct Knowledge Management Gate
• Conduct Project Quality Gate
• Conduct Project Management Review Service
• Manage Fulfilled Contracts
• Resolve and Close Open Issues
• Finalize Project Closeout Report
• Obtain Sign-off for Project Closure and Results Acceptance
Accelerators
• Lessons Learned Guide (Customer)
• Lessons Learned Template (Customer)
• Conduct regular quality checks at defined or critical stages of the project lifecycle to assess the
health of the project.
• Ensure that all key deliverables and actions of the gate have been completed in compliance with
recommended practices and to the customer’s satisfaction.
• Enable project management to continuously communicate the process and build quality directly
into the project.
• Provide a tool to effectively manage project expectations and monitor customer satisfaction. The
deliverables assessed at each quality gate will be performed using the quality gate checklist with
defined expectations to the maturity of particular project deliverables.
• Note: New additional key deliverables need to be added in the quality gate checklist by the Project
Manager to the different project types.
Accelerators
• QGateChecklist Concept SAP Activate
• QGateChecklist Template Introduction
• Quality Built In New QGate Checklist
Accelerators
• Phase Sign-Off Template (Customer)
• Project Closeout Report Presentation Template (Customer)
QG5 – Transition to Support Organization
Description
When reaching quality gate 5, operations of the new SAP system has been matured, and the conversion
project comes to an end.
Requirements and Constraints
This quality gate runs together with the activity Project Closure and Sign-Off Project Deliverables.
Procedure
• Run Q-Gate Transition to Support Organization
Prerequisites
In order to support the appropriate Quality Gates for the engagement, the SAP TQM and Quality Manager
must have access to the Project Charter and any primary document giving an overview of the project
schedule and the major milestones defined by the customer’s Project Management Office.
Procedure
The quality gate includes the review of the project status, the confirmation of major deliverables being
completed, and the formal sign-off of the quality gates based on the defined completion criteria. The
process owner is the project manager. To get the most possible value out of the quality gate, it is
recommended to perform /execute the quality gate by a quality manager (from customer/ partner or SAP
side) who is independent of the project management constrains (time, cost and budget) but experience in
managing projects and generally experienced in the technical and operational background. In exceptional
case project participated key team members (customer project manager supported by the SAP TQM) may
take over the role of the quality manager.
How to proceed:
• Process begins with a preparation call to plan the deliverables to be checked during the quality
gate, and to identify participants at the assessment meeting (include the customer project manager,
SAP TQM (if SAP has delivered services within the project phase), program manager as applicable
and representation from others on invitation partner project manager, PMO and additional experts
to support specific technical or business aspects.
• At the beginning of the quality gate the customer project manager presents the overall project status.
• The assigned quality manager reviews the fulfillment of the requirements of the checklist items. He
verifies the quality of deliverables regarding completeness, accuracy (if applicable) and actuality to
reach defined and agreed customer expectations.
• The result of the quality gate is a signed quality check list which contain agreed action items for
follow-up.
When the Q-Gate is not passed the transition to new stage is on hold and action items have to be defined
for follow-up. Store the Q-Gate results in SAP Solution Manager if possible. Decide on sending the Q-
Gate results to SAP.
Results
The filled out Q-Gate check list shows the status of the project at the end of the Hyper Care phase.
The team has handed over all open tasks, issues to the operations team and, if in place the SAP
Engagement (MaxAttention).
Accelerators
• Q-Gate Check List Transition to Support Organization
6. Run Phase
The transition project has ended with the Deploy phase. In the Run phase the aim is to establish safe and
efficient operations of the newly created solution. This includes the operations platform, core IT support
processes, the setup / fine tune of new / additional operations tools, and the enablement of the operational
support team. Moreover, a continuous operations improvement should be established to improve IT
operations based on newly gained experience.
In addition, this is the right time to plan for further innovations which could be implemented according to
the overall implementation strategy, which has been created in the Discover phase of the project (or
separately, as part of a business transformation work stream). The implementation strategy can now be
reviewed and enriched based on system usage experience which has been gained in the first weeks after
Go-Live.
Procedure
IT is in charge to ensure business continuity on the one hand. On the other hand, IT needs to enable
business change at the required speed and with no disruption. IT support should not be organized in a
way to only “keep the lights on” – instead, safe and efficient IT support guarantees business continuity
AND continuous improvement. Both aspects are covered in this activity.
Note that this activity deals with the organization of IT support and improvement. Business improvement
will be covered in the activity Improve and Innovate Solution.
SAP has documented IT support standards which describe these support processes in the SAP
context. See accelerator section for details. In addition, in case of SAP Enterprise Support, your
COE needs to be “Primary Certified”.
• Configure efficient system management - SAP has developed a concept called “Run SAP like a
Factory”. Core elements are:
o Application Operations
o Business Process Operations
See SAP Support Portal (accelerator section) for getting an overview about all capabilities
including offline demos.
• Operations Control Center (OCC)
One approach to efficiently operate IT operations is to implement an OCC, which collects all
critical alerts centrally, and pro-actively reacts before issues turn into problems. The OCC is tightly
integrated with the Mission Control Center (MCC) at SAP.
Based on the alert information, the OCC can establish a continuous improvement process to
avoid critical alerts in future. This could feed into the next task Continuously Optimize IT
Operations.
How SAP Can Support
SAP has a large set of offerings to SAP Premium Support customers with respect to both configuration
and enablement of operations functionality in SAP Solution Manager. For example SAP can configure
Application Operations in your environment, and trains your IT support experts in daily using the tools. Ask
your TQM for more details.
In case you want SAP to execute IT operational tasks, then SAP Application Management Services can
help you. SAP Application Management Services act as your extended team, run your SAP solutions,
provide an end-to-end application management to you for all their specific SAP solutions.
SAP Applications Management offers services in 3 value generating layers. The first layer is the basis for
application support, monitoring and change management, which is provided through:
all under guaranteed SLA’s and with 24/7 support available in multiple languages. In effect of these,
customers will see an increased solution stability and reduced number of incidents. At the same time
customers do have permanent service available to address required changes and execution of service
requests.
In case customer wants to hand-over the complete system landscape operation to SAP, then SAP HANA
Enterprise Cloud would be the applicable offer. SAP HANA Enterprise Cloud is a fully scalable and
secure private cloud offering available only from SAP. It gives you the full power of SAP solutions in a
private, managed cloud environment that is supported by the most knowledgeable resources in the
industry – from infrastructure to applications.
Accelerators
• SAP HANA Enterprise Cloud
• SAP Application Management Services
• Operations Control Center (OCC)
• Customer Center of Expertise
• Getting Started with Primary CCOE
• Primary CCOE Check List
• SAP Support Standards
• SAP Support Processes supported by SAP Solution Manager (Information and Offline Demos)
6.1.2.Continuously Optimize IT Operations
Objective
The purpose of this task is to continuously improve IT operations (e.g. via automation, or switching from a
re-active to a pro-active operations approach).
Procedure
This task can only name some out of many improvement options:
• Advanced Customer Center of Expertise (aCCOE)
The regular assessment and review of IT operations efficiency is offered by SAP Application Management
Services to all customers. Moreover, SAP offers to run the Operations Control Center for you (Managed
OCC).
Accelerators
• SAP Application Management Services
• Advanced Customer Center of Expertise (aCCOE)
• Continuous Improvement and Innovation with a Customer Center of Expertise – White Paper
Improve and Innovate Solution
Description
The aim of this activity is to further improve and simplify your new solution to realize maximum benefit. On
the one hand, this requires the periodic update, by implementing feature and support packs, to bring the
latest innovations from SAP into your solution. On the other hand, a new planning cycle needs to be
initiated together with your peers from the business units, to identify innovations which are mostly
required.
Procedure
• Periodically update your SAP system
• Initiate a new innovation cycle
Procedure
Implement a maintenance management process for your SAP system, and implement feature and support
packs from SAP in a timely manner.
Please note: More details on SAP feature and support pack implementation will be added to the road map
in a future version.
Accelerators
• SAP Application Management Services
6.2.2.Initiate a new Innovation Cycle
Objective
The goal of this task is to close the loop, but initiating a new innovation cycle.
Procedure
Innovation is not a one-step-process, but a continuous journey. Your SAP system runs stable, and is
updated with latest innovations from SAP.
Now it is time to review the innovation and implementation strategy you have created at the beginning of
the project. Business requirements may have changed meanwhile, and your company may have gained
experience on what is possible with the new solutions from SAP.
Adjust your innovation strategy accordingly, and start the next round by entering the Design phase of the
next innovation project.
• SAP offers “Business Transformation Services”, to create and update your transformation and
innovation journey. They can help align your people, processes, and technology to your corporate
goals using industry-specific best practices and expertise. Take advantage of proven innovation
management methodology and services, quickly deploy the latest digital business technologies,
and keep your company on the very cutting edge. Core areas are business innovation, digital
transformation, and value optimization.
• Business Process Improvement is a methodology to identify weaknesses in existing business
processes in order to make them more efficient and effective. The methodology is supported by
Business Process Analytics, which is a problem oriented tool in SAP Solution Manager providing
fast root cause analysis capabilities. Moreover, Business Process Analytics monitors how the
current solution is being used.
• Business Improvement offering by SAP Application Management Services is a collaboration
between SAP and you. An SAP Solution Architect will work with you to define service plans,
execution timelines and effort estimations. This also includes regular proactive planning sessions
for improvement driven by business demand. Finally, SAP will be responsible of the execution of
the agreed business improvement, while working in conjunction with the Change/Release Manager
to inject new solutions or enhancements into your SAP solution.
See accelerator section for details on all items listed above. You can also contact your SAP lead (e.g.
Client Partner, TQM) for more information.
Accelerators
• Business Transformation Services
• Business Process Analytics
• Business Process Improvement
• SAP Application Management Services