Project-Plan en 19Q3-Activity and Task-Level

Sequence
1
1.1
1.1.1
1.1.2
1.1.3
1.1.4
1.2
1.2.1
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.3
1.3.1
2
2.1
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.2
2.2.1
2.3
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.3.10
2.3.11
2.3.12
2.3.13
2.3.14
2.4
2.4.1
2.4.2
2.4.3
2.4.4
2.4.5
2.4.6
2.5
2.5.1
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.6
2.6.1
2.6.2
2.6.3
2.7
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.7.7
2.7.8
2.7.9
2.8
2.8.1
2.8.2
2.8.3
2.8.4
2.9
2.9.1
2.9.2
2.9.3
2.9.4
2.9.5
2.9.6
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.11
2.11.1
2.11.2
2.12
2.12.1
2.12.2
2.12.3
2.12.4
3.1
3.1.1
3.1.2
3.1.3
3.2
3.2.1
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.4
3.5
3.5.1
3.5.2
3.6
3.6.1
3.7
3.7.1
3.8
3.8.1
3.9
3.9.1
3.10
3.10.1
3.11
3.11.1
3.12
3.12.1
3.13
3.13.1
3.13.2
3.14
3.14.1
3.15
3.15.1
3.16
3.16.1
3.16.2
3.16.3
3.16.4
3.17
3.17.1
3.17.2
3.17.3
3.17.4
3.17.5
3.17.6
3.17.7
3.17.8
3.17.9
3.18
3.18.1
3.18.2
3.19
3.19.1
3.19.2
3.20
3.20.1
3.21
3.21.1
3.21.2
3.21.3
3.22
3.22.1
3.22.2
3.22.3
3.23
3.23.1
3.23.2
3.24
3.24.1
3.25
3.25.1
3.25.2
3.25.3
3.25.4
3.25.5
3.25.6
3.25.7
3.26
3.26.1
3.27
3.27.1
3.28
3.28.1
3.28.2
3.28.3
3.28.4
3.28.5
3.28.6
3.29
3.29.1
3.29.2
3.29.3
3.29.4
3.30
3.30.1
3.30.2
3.31
3.31.1
3.31.2
3.31.3
3.31.4
3.31.5
3.31.6
4.1
4.1.1
4.1.2
4.1.3
4.2
4.2.1
4.2.2
4.3
4.3.1
4.3.2
4.4
4.4.1
4.5
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.6
4.7
4.7.1
4.8
4.8.1
4.9
4.9.1
4.10
4.10.1
4.11
4.11.1
4.12
4.12.1
4.13
4.13.1
4.14
4.15
4.15.1
4.15.2
4.15.3
4.15.4
4.16
4.16.1
4.16.2
4.16.3
4.17
4.17.1
4.18
4.18.1
4.18.2
4.18.3
4.19
4.19.1
4.19.2
4.19.3
4.20
4.20.1
4.20.2
4.20.3
4.20.4
4.20.5
4.21
4.21.1
4.22
4.22.1
4.22.2
4.23
4.23.1
4.23.2
4.24
4.24.1
4.25
4.25.1
4.26
4.26.1
4.26.2
4.27
4.27.1
4.27.2
4.28
4.28.1
4.28.2
4.29
4.29.1
4.29.2
4.29.3
4.29.4
4.29.5
4.29.6
4.30
4.30.1
4.30.2
4.30.3
4.30.4
4.31
4.31.1
4.31.2
4.31.3
4.31.4
4.31.5
4.31.6
4.32
4.32.1
4.32.2
4.33
4.33.1
4.33.2
4.33.3
4.33.4
4.33.5
4.33.6
5.1
5.1.1
5.1.2
5.2
5.2.1
5.2.2
5.3
5.3.1
5.4
5.4.1
5.4.2
5.5
5.5.1
5.5.2
5.6
5.6.1
5.6.2
5.6.3
5.6.4
5.6.5
5.6.6
5.7
5.7.1
5.7.2
5.7.3
5.8
5.8.1
5.8.2
5.8.3
5.9
5.9.1
5.9.2
5.9.3
5.9.4
5.9.5
5.10
5.10.1
5.10.2
5.10.3
5.10.4
5.11
5.11.1
5.11.2
5.12
5.12.1
5.12.2
5.12.3
5.12.4
5.12.5
5.12.6
6
6.1
6.1.1
6.1.2
6.2
6.2.1
6.2.2
Title
S/4HANA Sample Project
Discover
Strategic Planning
Create an Innovation Strategy and a High-Level Road Map
Accelerate Your Innovations with the Help of the SAP Leonardo Innovation Services (Optional Task)
Create a 360-Degree View on Security
Define the Analytics Architecture
Application Value and Scoping
Discover the Value of SAP S/4HANA for Your Company
Identify the impact of SAP S/4HANA on existing business processes
Check the Conversion Readiness of SAP ERP
Perform a Business Scenario and Solution Mapping
Define the Implementation Strategy
Create a Strategic Road Map and Value Case
Trial System Provisioning
Provide a Trial System
Prepare
Project Team Enablement
Conduct Agile Training for the Project Team
Conduct SAP Solution Manager Training

Perform Mobilization Training for the Project Team
Conduct Project Team Enablement prior to Fit-Gap Analysis
Conduct Key User Training

Prototype
Run Prototyping
Transition Planning
Check the Conversion Readiness of SAP ERP
SAP S/4HANA Transition Project: Scope Definition and Objectives
Define Cutover Approach
Clarify Custom Code Adaption
Clarify Operational Readiness
Define Technical Architecture
Define the Data Migration Architecture (New Implementation and Selective Data Transition)
Perform Data Volume Planning
Define the UX / UI strategy
Prepare Interface Register
Run a Legacy Impact Analysis on Interface Inventory and Data Integration
Run a first Assessment on Output Management
Run a first Assessment on Training Requirements
Optional: Run a Technical Security Self Check
Transition Preparation
Execute on Follow-Ups from Transition Planning
Clean up of Archive Data
Cleanup Unused Code (Optional Task)
Improve Custom Code Quality Measures (Optional Task)
Prepare SAP Solution Manager for Project Support
Import the Best Practices content to SAP Solution Manager
Project Initiation
Conduct Handover Meeting(s) from Opportunity Phase

Review Order Form with Customer
Identify Stakeholders, Stakeholders' Requirements and Expectations and Project/Deliverable Acceptance Criteria
Set Stakeholder Expectations for Agile Project
Create Project Charter

Create Project Management Plan
Establish Project Governance
Define Roles and Responsibilities
Define Project Organization

Review Project Management Plan
Plan Project
Create Scope Statement
Create WBS
Create Project Schedule

Create Budget
Plan Quality
Plan Communications
Plan Risks
Plan Procurement
Plan Stakeholders Management
Project Kick-Off and On-Boarding

Prepare for Kick-off Meeting
Conduct Kick-off Meeting
Prepare Team On-boarding Document
On-board Project Team

Project Standards, Infrastructure, and Solution
Define Project Standards

Determine Operational Standards
Define and Set Up Agile Project Standards and ALM Tools
Check Availability of SAP Solution Manager
Set up Project Team Logistics and Infrastructure
Setup and Test Remote Support

Execution, Monitoring, and Controlling of Results
Direct and Manage Project Execution
Monitor and Control Project Activities
Manage Issues, Risks and Changes
Communicate Status and Progress to Project Stakeholders
Organizational Change Management Roadmap
Prepare Organizational Change Management Roadmap

Conduct OCM Workshop with Project Manager and all Project Workstream Owners
Phase Closure and Sign-Off Phase Deliverables
Conduct Knowledge Management Gate
Conduct Project Quality Gate
Conduct Project Management Review Service

Obtain Customer Sign-Off for Phase Completion
Explore
Phase Initiation
Review Deliverables of Explore Phase
Review Acceptance Criteria
Review RACI Chart for Explore Phase
Learning Design
Develop a Training Concept
Activate Solution
Finalize Mandatory System Preparation Activities (System Conversion only)
Reconfirmation of Scope for Activation (New Implementation only)

Activation of Best Practices and Test-Activated Processes (New Implementation only)
Set up Integration with other Test Systems
Fit-Gap / Delta Design: Introduction
Fit-Gap / Delta Design: Finalize System Setup

Prepare Sample Data
Enhance system setup with additional configuration

Fit-Gap / Delta Design: Fit/Gap Analysis - Solution Validation
Run Fit Gap Workshops
Fit-Gap / Delta Design: Gap Identification

GAP Documentation / Specification
Fit-Gap / Delta Design: Delta Scope Prioritization

Prioritize Delta Scope
GAP Validation
Validate Gaps
Fit-Gap / Delta Design: Delta Design
Finalize Delta Design
Design Review
Perform Design Review
Fit-Gap / Delta Design: Verify and Accept
Perform Validation and Approval Sessions

UX Activation and Design
UX Activation
UX Design
Security Design
Define Security Infrastructure
Fit-Gap / Delta Design- Central Finance Design

Run Central Finance Design
Data Volume Design
Get Transparency on the HANA DVM Quick Wins
Optional: Set Up a DVM Strategy for Business Documents
Get Transparency on Open Business Documents
Adapt your DVM Strategy
Data Migration Design
Prepare and Conduct Data Migration Assessment
Data Audit
Prepare and Present Data Migration Scope and Requirements Document

Data Migration Approach and Strategy Document
Test Data Management

Define Specifications for Data Migration
Run a Landscape Transformation Assessment (Selective Data Transition only)
Set up Landscape Transformation Software (Selective Data Transition only)

Set up Data Migration Services (New Installation scenario only)
Custom Code Impact
Empowering on Custom Code Management Tools
Create a Custom Code Work List
Integration Design
Define Interface Architecture
Prepare Integration Design
Analytics Design
Design the Analytics Architecture
Test Planning
Make yourself Familiar with the Tools in Test Management, and Set Up Test Management in SAP Solution Manager
Test Scope Determination
Detailed Test Planning
Sandbox Setup / Conversion

Set Up SANDBOX (System Conversion scenario only)
Downtime Optimization Preparation (System Conversion scenario only)
Set Up SANDBOX (New Installation scenario only)
DEV Setup /Conversion
DEV Setup (New Implementation)
DEV Setup (System Conversion)
Sizing
Perform / Check Sizing
Technical Architecture and Infrastructure Definition
Discover Technical Boundary Conditions
Create Technical Solution Map
Decide on Integration with Cloud Applications

Hardware Selection and Utilization
Develop Virtualization Strategy

Design Network
Test Preparation
Technical Design
Create a Technical Solution Design Document
Operations Impact Evaluation
Operations Impact Evaluation
Execution / Monitoring / Controlling Results
Update Project Management Plan

Conduct SCRUM Meetings

Release and Sprint Plan
Update and Prioritize Backlog

Estimate Backlog Items Effort
Conduct Release and Sprint Planning Meeting
Validate Release and Sprint Plan Against SoW

Change Impact Analysis
Validate Organizational Alignment Approach
Establish Baseline of Current State
Phase Closure and Sign-Off phase Deliverables

Execute Baseline Retrospective
Manage Fulfilled Contracts

Realize
Phase Initiation
Review Deliverables of Realize Phase

Review Acceptance Criteria
Review RACI Chart for Realize Phase
Plan Realize Phase
Plan Sprints and Solution Reviews
Plan Testing
Learning Realization
Train your Key User
Create Training Material for End User
Sprint Initiation (Iterative)

Conduct Sprint Planning Meeting (Iterative)
Execution Plan for Realize Phase
Manage Sprints
Manage Unit/String Tests
Manage Integration Test
Manage Security Test
Manage User Acceptance Test

Configuration: Introduction
Configuration: Handover
Run Handover Session
Configuration: Main Configuration

Perform Main Configuration
Configuration: Unit Test

Run Unit Test
Configuration: String Test

Run String Test
Configuration: Solution Walk-Through
Run Solution Walk-Through

Configuration: Bug Fixing
Resolve Identified Issues
Configuration: Documentation
Document Configured Settings

Configuration- Central Finance Implementation
Product Enhancements
Adjust Affected Existing Custom Code
Development of WRICEF objects
Enhancement and development of user interface (e.g. FIORI)
Custom Development
Sprint Closing
Conduct Sprint Review Meeting
Signoff Sprint Results

Conduct Sprint Retrospective
Security Implementation
Implement Security
Data Volume Management Configuration
Cleanup or Archive Data

Configure Data Archiving and Data Aging (Design Time)
Test execution of Data Archiving and Data Aging (Runtime)

Integration Validation
Identify the IV Scope
Initiate the Corresponding IV Support Activities
Initiate SAP Going-Live Check
Data Migration and Verification
Legacy Data Migration (New Implementation)
Perform Load and Verification Runs (System Conversion)
Perform Client Transfer (LT Scenario- Client Transfer)
Perform System Merge (LT scenario- System Merge)
Perform Company Code Transfer (LT Scenario- Company Code Transfer)
Custom Code Quality

Establish / Adjust Custom Code Quality
Integration Implementation
Implement Integration Design
Validate Integration Implementation

Analytics Configuration
Configure Analytics and Digital Boardroom

Knowledge Transfer
Test Preparation
Prepare Tests
Test Execution
Perform Integration / Regression / User Acceptance Test
QAS Setup/ Conversion
QAS Setup (New Implementation)
QAS Setup (System Conversion)
Sizing and Scalability Verification

Optional: Perform Sizing Verification
Optional: Perform Scalability Verification

IT Infrastructure Setup
Set Up IT Infrastructure
Test IT Infrastructure
Operations Implementation
Collect detailed Operations Requirements
Roles and Responsibilities

Support Processes and Procedures
Operations Support Tools
Operations Documentation
Knowledge Transfer
Cutover Preparation
Production System Setup

Create Cutover Plan (New Implementation)
Create Cutover Plan (System Conversion)
Create Cutover Plan (Landscape Transformation)
Execution, Monitoring and Controlling Results

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)
OCM Alignment Activities

OCM and Testing alignment
OCM and Data Migration alignment
Phase Closure and Sign-Off Phase Deliverables

Execute Baseline Retrospective
Manage Fulfilled Contracts

Deploy
Phase Initiation
Allocate Resources and Update Project Schedule

Perform Kick-off Meeting
Learning Realization
Create Training Execution Plan

Execute End User Training
Integration Validation
Finalize Integration Validation
Operations Readiness
Operational Readiness (System Conversion)
Operational Readiness (New Implementation)
Dress Rehearsal
Finalize IT Infrastructure Services
Perform Cut-Over Rehearsal

Execution, Monitoring and Controlling Results
Update Project Management Plan

Release Closing
Prepare Product Backlog for Next Release/Sprint

Conduct Release Retrospective
Update the Release and Sprint Plan
Production Cutover
Convert Productive System (System Conversion)
Production Cutover (New Implementation)
Production Cutover (Selective Data Transition)
Hyper Care Support
Monitor Resource Consumption

Analyze Workload
Check System Scalability

Follow-up on GoingLive Check (Verification Session)
Delete Obsolete Data with the "Obsolete Data Handling Tool"

Post Go-Live End User Training
Prepare End-User Training for Scope Option
Deliver End-User Training for Scope Option
Collect Training Evaluations Feedback
Perform People Readiness Assessment
Handover to Support Organization

Resolve and Close Open Issues
Handover Operations Responsibility
Project Closure and Sign-Off Project Deliverables

Manage fulfilled Contracts
Resolve and close open Issues
Finalize Project Closeout Report
Obtain Sign-off for Project Closure and Results Acceptance

Run
Operate Solution
Safely and Efficiently Operate the new Solution
Continuously Optimize IT Operations
Improve and Innovate Solution

Periodically Update your SAP System
Initiate a new Innovation Cycle
Description
_x000D_
In the Discover phase, customers become familiar with the benefits of SAP
HANA and SAP S/4HANA, and the benefits it can bring to customers’
business. _x000D_
As depicted in the figure, the phase is structured as follows:_x000D_
_x000D_
Figure: Activities in the Discover phase In the first step customers should
create an overall company strategy on their digital transformation. This
includes SAP S/4HANA as the digital core, but looks at it from a broader
perspective. Key topics like Internet of Things, Big Data / Smart Data,
Omnichannel, or Business Networks can be included into the strategy as
well. In the next step customers should become familiar with the value
of SAP S/4HANA in general (e.g. the new and simplified functionality in SAP
S/4HANA, the new User Interface based on FIORI, agile customer innovations
using SAP Cloud Platform etc.). A trial system in the cloud could support this.
In the third step, a decision on the implementation scenario, and a
comprehensive implementation strategy for SAP S/4HANA should be
created. In the case of system conversion, the conversion readiness of the
existing SAP ERP system should be checked as well. A Learning Needs
Analysis for the project team should be performed as well._x000D_
The outcome of these steps can be leveraged within a company to build a
business case for an SAP S/4HANA implementation project._x000D_
To prepare this phase, customers should take use of the valuable information
sources on SAP S/4HANA listed in the accelerators section: There is a vibrant
community on SAP S/4HANA at the SAP Community Network. Customers
who are interested in SAP Fiori should visit the SAP User Experience (Fiori)
Community. The Innovation Discovery Finder is a tool that helps customers
to identify new and improved functionality for SAP S/4HANA based on
selection criteria such as Industry, or Solution Area. There is also good
information available in the print media, for instance “Migrating to SAP
S/4HANA” by Frank Densborn. Customers and partners, who want to build
de-coupled extensions for SAP S/4HANA using the SAP Cloud Platform can
find very helpful information at the SAP Blog “Extensibility of SAP S/4HANA”
(accelerator section)._x000D_
Regarding SAP S/4HANA releases:_x000D_
SAP plans to ship a new release of SAP S/4HANA on-premise once per year.
In between, innovations are shipped via feature packs. Information (like the
“Simplification List” explained later in the road map) is often release or
_x000D_
Over the last 10 years, SAP has helped customers begin their own digital
transformations with SAP HANA software and an extensive portfolio of cloud
applications for the enterprise. Now the &bdquo;Intelligent Enterprise“
combines new technologies and allows for automating repetitive manual
tasks and processes which earlier consumed valuable employee time. Hence,
the customer workforce can focus on higher-value activities such as
customer success, strategic planning, and innovation._x000D_
SAP’s Intelligent Enterprise features 3 key components across Applications
(Intelligent Suite), Platform (Digital Platform) and Intelligent
Technologies:_x000D_
_x000D_
Figure: The Intelligent Enterprise Suite_x000D_
The Intelligent Suite build on the ingredients of the digital core_x000D_
The Intelligent Suite delivers a suite experience while retaining the
modularity and flexibility of independent solutions. Scenarios are business-
driven, integrated, intelligent, and extensible. SAP enforces reusable business
services and integration through data sharing via the SAP Cloud
Platform._x000D_
Intelligent Technologies_x000D_
SAP Leonardo enables customers to leverage their data to detect patterns,
predict outcomes, and suggest actions with the help of advanced
technologies such as artificial intelligence, machine learning, advanced
analytics and the Internet of Things (IoT)._x000D_
The Digital Platform_x000D_
With SAP Cloud Platform and the HANA Data Management Suite, SAP can
facilitate the collection, connection, and orchestration of data as well as the
integration and extension of processes within the Intelligent Suite._x000D_
Find more details in the whitepaper “SAP Intelligent Enterprise” (see
accelerator section)._x000D_
Innovations and intelligence in SAP S/4HANA 1809 are explained in the Blog
&bdquo;Product Management Release blog SAP S/4HANA 1809“,
mentioning new capabilities in Procurement, Sales Distribution,
Manufacturing and Finance (see accelerator section)._x000D_
The aim of the task “Strategic Planning” is to define a comprehensive
innovation strategy and road map for all three key components mentioned
above. Once the innovation strategy has been defined a target enterprise
architecture for processes, data, application and integration needs to be
_x000D_
The objective of this task is to create a company specific innovation strategy,
and to derive a high-level multi-year road map from there._x000D_
Procedure _x000D_
To come to an innovation strategy, SAP Best Practice is to start with an
identification of strategic business and IT objectives, including current pain
areas. Those objectives need to be clustered to “benefit areas”. For each
benefit area, enablers (like SAP S/4HANA, but also other solution or platform
components) need to be identified, prioritized, and benchmarked with
respect to the industry reference architecture._x000D_
The target enterprise architecture (business / application, and IT) can be
derived in the next step. You will need to clarify questions such as: How
many SAP S/4HANA systems are ideal for the to-be business scenarios? Is
Co-Deployment preferred, or should I deploy standalone? What about IT-
Security Requirements?_x000D_
The strategic road map finally documents the main transition steps from as-
is to the to-be architecture, by clarifying: System Conversion, or New
Implementation? One-step conversion, or transformation via multiple steps?
Sequence of co-deployment?_x000D_
The following figure gives an example of a high-level implementation road
map. The illustrative figure is structured into three phases (2018, 2020, and
beyond), and shows individual projects structured per business area (e.g.
Financials)._x000D_
_x000D_
Figure: Example of a multi-year road map (high-level)_x000D_
_x000D_
Results_x000D_
As a result, there is a high-level multi-year road map which describes the
main change activities (including business driver), and sequences them on a
time line._x000D_
How SAP Can Support_x000D_
SAP supports the initial creation of a digital transformation road map with a
set of newly created or enhanced tools: _x000D_
The SAP Innovation and Optimization Pathfinder is a free of charge tool from
SAP, which-; based on your current system usage statistics - answers
questions like: "Of all the innovations from SAP -; SAP Fiori apps, SAP
Business Suite enhancements, SAP S/4HANA scenarios or Cloud extensions -;
which ones are the most relevant for your business?" _x000D_
_x000D_
Most likely your innovation strategy that was created before has identified
the need to further evaluate the value of advanced digital technology (e.g.
the use of IoT (Internet of Things) in your industry area). This task describes
how the “SAP Leonardo Innovation Services” can help you speeding up your
innovation._x000D_
Requirements and Constraints_x000D_
This task is optional. However, an SAP S/4HANA implementation project is an
ideal point in time to think about innovation in a broader context. You can do
this fast, with the help of the “SAP Leonardo Innovation Services”._x000D_
To come to a tailored innovation strategy, SAP MaxAttention customers can
consume innovation services. The offering is structured into three areas:
Innovation Advisory and Engineering:focuses on a single, guided innovation
cycle based on a defined business challenge, technology inspiration, or
industry case with the business value clearly defined for open innovation,
extensibility, and any other type of innovation use-case. Innovation
Portfolio Management and Empowerment: provides supports and advises
the customer as they expand their innovation maturity. It supports the
customer in establishing their own innovation management capabilities,
including growing their innovation use-case portfolio and establishing
innovation governance. Innovation Factory Advisory & Support: coaches
the customer in establishing and growing a sustainable innovation
framework that supports and drives business and technical transformation
through innovation and supports in further developing innovation
maturity._x000D_
See accelerator section for more details._x000D_
The new SAP Leonardo Innovation Services from SAP Professional Services
combines the tools, technology, and expertise of value to Business and IT, to
kick-start your innovation journey._x000D_
There are currently three editions: _x000D_
SAP Leonardo Innovation Services, express edition_x000D_
SAP delivers thoughtfully packaged innovative capabilities and services -; by
industry -; to engage with new customers in the context of their business.
_x000D_
SAP Leonardo Innovation Services, open innovation edition _x000D_
Starting from the individual customer challenge SAP provides an innovation
sprint from ideation to proof-of-concept based on the specific challenge
_x000D_
The goal of this task is to make you familiar with all SAP Security & GRC
relevant topics, and to collect security relevant information, which serves as
a foundation for a scoping on security._x000D_
Procedure_x000D_
Please listen to the recording which is linked from the accelerator section,
and get informed about security topics. After watching the recording take
the opportunity to fill out the questionnaire concerning your current security
situation, to identify the gaps you may have and to prioritize your next steps
on the way to a secured SAP landscape._x000D_
The “How-To” document (accelerator) explains the procedure in more
detail._x000D_
Results_x000D_
Once completed you will have a good general overview of the relevant SAP
Security & GRC topics, and a recognition of your own security
situation._x000D_
The questionnaire should be filled out after listening to the recording. It is
required to determine where your security issues are, and how SAP can
assist you most efficiently. The answers can be used to bring in additional
SAP Value Assurance services, or services from SAP Professional Services
during project implementation. This brings you together with SAP to build a
secure and compliant SAP S/4HANA landscape that best meets your needs
and requirements._x000D_
In May 2016, the European Union (EU) adopted a newly harmonized data
protection law called the General Data Protection Regulation (GDPR). The
transition period ends on May 25, 2018, from this day on GDPR is a directly
applicable law in all member states within the EU and the European
Economic Area (EEA). All organizations that offer goods or services to, or
monitor the behavior of EU data subjects and those that process or hold the
personal data of EU residents are impacted._x000D_
The EU-GDPR has different aspects for a legal basis as the consent, legal
obligation, protect of vital interests, contract, legitimate interest and the
public interest._x000D_
There are also different rights that the data subject gets through the EU-
GDPR: The right of information access, information to be provided,
restriction of processing, notification, correction, portability, erasure and
automated decision._x000D_
_x000D_
The purpose of this task is to evaluate the impact of SAP S/4HANA on the
company’s analytics architecture. The aim is to create a specific roadmap for
analytics protecting past investments and innovating via new platform
capabilities._x000D_
This activity is optional. However, SAP recommends taking the opportunity
to adjust your company’s analytics strategy by considering the analytics
capabilities of SAP S/4HANA._x000D_
Procedure _x000D_
The introduction of SAP S/4HANA into your solution landscape is an ideal
opportunity to review and potentially adjust your company’s analytics
architecture. There are many reasons why: SAP S/4HANA and SAP
BW/4HANA bring new analytics capabilities. The business data structure
significantly changes with SAP S/4HANA. There are many new analytic
products from SAP which perfectly integrate with SAP S/4HANA._x000D_
To review and potentially adjust the analytics architecture you should look
from a holistic perspective taking SAP and non-SAP components into
account. The strategy should consider: Product options like:
Embedded Analytics Stand-alone SAP BW and SAP BW/4HANA
SAP Digital Boardroom Front-end options like: SAP
BusinessObjects BI Suite SAP Analytics Cloud Data model
and access method changes like: CDS (Core Data Services)
Embedded Analytics Options with respect to data
persistence_x000D_
The accelerator section lists many information sources for both the tools and
strategy, to make you familiar with the options that you have. The analytics
road maps for “Solutions” and “Products” are located in the general SAP
Road Maps space at sap.com, under “Platform & Technology”._x000D_
The ideal analytics strategy should be based on a customer specific set of
decision criteria like: Functional analytics requirements, e.g. for
Operational Reporting and real-time Reporting Handling of historical data
Maintenance Schedule Data responsibility and ownership
Complexity and number of data sources_x000D_
With SAP S/4HANA system as the source, there are two source types for data
provisioning. Read the SAP Blog “Data Provisioning Supportability of SAP
S/4HANA On-Premise Edition 1709” from the SAP Regional Implementation
_x000D_
Once the general innovation strategy and high-level road map has been
defined, you will need to become familiar with SAP S/4HANA and as such,
the value it brings for your company’s business._x000D_
Furthermore, the impact on existing business processes needs to be
analyzed in more details. This may influence the implementation strategy for
SAP S/4HANA._x000D_
Finally, a customer specific application scoping should be created. This
includes a decision on the implementation scenario, and the mandatory and
optional / desired adoptions._x000D_
This activity is recommended for all scenarios. There is an innovation
strategy and a high-level road map available, which lists the implementation
of SAP S/4HANA as an upcoming major change event._x000D_
Access to an SAP S/4HANA trial system (one activity later in this phase) may
be beneficial._x000D_
Procedure Discover and document the value of SAP S/4HANA for your
company. Identify the impact of an SAP S/4HANA implementation on
your existing business processes. Analyze the relevance for Fiori apps
based on the usage of the existing system (for System Conversion scenario
only) Validate the conversion readiness of your existing SAP ERP system
(for System Conversion scenario only) Perform a business scenario and
solution mapping Define the implementation strategy by considering the
target architecture Create a strategic road map based on the target
architecture and implementation strategy_x000D_
Results_x000D_
As a result, there will be a plan on what to implement when in SAP
S/4HANA; and why. This information serves as the key input into the
customer business case._x000D_
Furthermore, a first impact analysis may have identified show stoppers or
road blocks, which could affect the implementation strategy, and which need
to be addressed in additional planning and preparation activities.
_x000D_
The objective of this task is to become familiar with SAP S/4HANA, and to
discover the value SAP S/4HANA may bring to your company._x000D_
Procedure _x000D_
To become familiar with SAP S/4HANA proceed as follows (all links can be
found in the accelerator section): Start with a study of the information
resources in the public web. See accelerator section for details. A good
information source is the central landing page of the SAP Online Help portal
which contains for instance: Aa “Feature Scope Description”
which shows all features provided with a certain release of SAP S/4HANA.
A “What’s New?” document focusing on new features coming with
this release. Alternatively, use the “What’s New Viewer” as an interactive
tool. The “Simplification List” focusing on what needs to be
considered in case of a migration project from SAP ERP. All relevant
guides like the “Installation Guide” for new implementation, or the
“Conversion Guide” for system conversion. A list of training offerings
on SAP S/4HANA. The Business Scenario Recommendations Report
lists SAP S/4HANA innovations that might help based on current usage
patterns of the business users. It’s tailored to your specific system and free of
charge. You can browse through the results report by Line of Business and
review individual business scenario details that include: business context,
value, business drivers, SAP S/4HANA and Fiori innovation, improved
transactions, and more. Explore SAP S/4HANA yourself by using a trial
system in the public cloud (see activity Trial System Provisioning later in this
phase). Regarding planning and consolidation, look up the SAP Blog
“Planning and Consolidation Options in S/4HANA” from the SAP RIG team.
A transition to SAP S/4HANA is a perfect opportunity to check if home
grown applications can be replaced by new functionality coming with SAP
S/4HANA, to move closer to the SAP standard (and to avoid maintenance
efforts in the future). This initiative is often called “Back to Standard”.
Explore options for efficient custom code management and agile customer
innovations using the extensibility capabilites of SAP S/4HANA and SAP
Cloud Platform. Examples are SAP Fiori and Mobile scenarios in the SAP
Cloud Platform decoupling custom user interface development from a stable
SAP S/4HANA core, or consuming innovations without upgrades (e.g. LoB
Finance innovations delivered via SAP Cloud Platform applications). You will
find helpful information and further links in the SAP blog “Extensibility of
S/4HANA -; Helpful Links” (accelerator section)._x000D_
_x000D_
The implementation of SAP S/4HANA may have a significant impact on
existing business processes. This is obvious for new implementation
scenarios, and depends on the application design. However especially for
system conversion scenarios, the functional impact needs to be analyzed,
because SAP has simplified functionality, and partly removed redundant
functionality in SAP S/4HANA (“Principle of One”). To properly plan the
implementation strategy, at least the major impact items should be known
as early as possible._x000D_
Prerequisites_x000D_
This task is particularly important for System Conversion scenarios._x000D_
Procedure _x000D_
Proceed as follows: Study the Simplification Item Catalog. In this catalog
SAP describes in detail on a functional level what happens in SAP S/4HANA
to individual transactions and solution capabilities. In some cases, SAP has
merged certain functionality with other elements or reflected it within a new
solution / architecture compared to the SAP Business Suite products.
Alternatively, study the “Simplification List for SAP S/4HANA” PDF document
for offline use which you can find in the SAP Online Help Portal (section
Conversion & Upgrade Assets). Compare these items with the functionality
which is in use today. Study the alternatives and recommendations, given by
SAP as part of the list. The Simplification Item Catalog also lists replaced
transactions in SAP S/4HANA. Check about usage today (e.g. by comparing
with usage statistics in transaction ST03). Analyze the relevance for Fiori apps
based on the usage of the existing system (for System Conversion scenario
only) Document your findings._x000D_
Please note: There is strong tool support for identifying impacted custom
objects and transitioning them to SAP S/4HANA. While the vast majority of
custom objects will easily be transferred to SAP S/4HANA, you may also
consider candidates for re-engineering using advanced SAP HANA
capabilities and even a de-coupling of custom objects (e.g., UI’s) using Web
IDE and SAP Cloud Platform. Details will be given in the Explore and Realize
phase of the roadmap. Support can be provided by the dedicated SAP IBSO
team._x000D_
Results_x000D_
There is a document available which documents the major impact items for
SAP S/4HANA._x000D_
_x000D_
There could be show stoppers (e.g. incompatible Add-On’s installed in the
existing SAP ERP system) or requirements (e.g. version dependency issues
with SAP NetWeaver hub system) that could have an 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, so as to be able to
adapt the overall project plan accordingly._x000D_
This task is particularly important for system conversion and selective data
transition (in case they start with a system conversion) scenarios._x000D_
Procedure _x000D_
SAP recommends checking the following areas, and to document the results:
Is today’s functional scope in SAP ERP supported in SAP S/4HANA (e.g.
Industry Solutions, Enterprise Extensions, 3rd party add-ons, etc…)?
Are there incompatible add-ons from 3rd party software vendors? In
this case please contact the software vendor early asking for advice.
Potentially there is a newer add-on version which is compatible with SAP
S/4HANA.
For SAP Standard add-ons, or add-ons delivered by SAP IBSO, please see
SAP note 2214409 - SAP S/4HANA: Compatible Add-ons. Is there
functionality used today that will need to be replaced with the conversion to
SAP S/4HANA (e.g. Cash Management)? You will need to compare the
functionality in use in the current SAP ERP with the Simplification List from
SAP: Are all technical system requirements fulfilled (e.g. software
levels, single stack system, Unicode, etc…)? Otherwise they will need
to be planned as part of the conversion. Are all dependent SAP
NetWeaver hub systems on the required release? How many custom
objects are impacted by the DB migration to SAP HANA? How many custom
objects are impacted by the simplification of the financial data model? How
many custom objects are impacted by the change in SAP software?
Which business critical reports and transactions are in use today, which will
be replaced / removed in SAP S/4HANA? Which configuration needs to
be adjusted? What is the estimated SAP S/4HANA system size? Are
there options to reduce the size before the conversion? _x000D_
Results_x000D_
The results document of this task describes the implications of SAP
S/4HANA; which need to be addressed either before starting the transition
project, or as part of the transition project._x000D_
_x000D_
Business Scenario & Solution Mapping establishes the business process
scope and relevant adjustments for the S/4HANA system conversion, with a
focus on S/4HANA._x000D_
The business areas in scope for mapping has been identified already. This
could have been done by gathering input from the Lines of Businesses, or by
requesting a Business Scenario Recommendation (BSR) report. The BSR is
part of the Discovery Workshop for SAP S/4HANA, or can be ordered
separately (see accelerator section)_x000D_
Procedure _x000D_
Proceed as follows: Set up a workshop together with process experts
from the Lines of Businesses Analyze each business priority in scope for
innovation. Run a business scenario fit analysis, by clarifying: Is
this innovation item relevant for me? Information source can be for instance
the Best Practice information which has been uploaded into SAP Solution
Manager, the simplification list, and the Business Scenario Recommendation
report (BSR). Quantify and describe the value in case of relevance.
Upload all documents to the SAP Solution Manager so information
can be shared across the project team._x000D_
Results_x000D_
As a result, you have a documented list of innovation items, which are in
scope for implementation. This information is also a valuable input for the
business case._x000D_
The Value and Implementation Strategy service component provides a
comprehensive SAP S/4HANA migration analysis down to proposed
implementation strategy and supporting value case as depicted in the figure
below. Starting from business priorities, it identifies key innovations and
mandatory changes applicable to the specific customer situation, along with
the impact on the overall target architecture, thereby highlighting the
customer specific value chain built on SAP S/4HANA._x000D_
_x000D_
_x000D_
Figure: Structure of the “Value and Implementation Strategy” service
component_x000D_
The following inputs are used SAP S/4 HANA Discovery Workshop
(optional); SAP Readiness Check for SAP S/4HANA results SAP Fiori
_x000D_
The objective of this task is to define an implementation strategy, based on
the “to-be state” of the business architecture._x000D_
There is a draft version of the “to-be” state of the business architecture
available already._x000D_
Procedure _x000D_
There are often multiple “Business Application to-be states’” possible and
different paths on how to get there. Functional capabilities, landscape
aspects, and technology capabilities need to be taken into consideration, and
there might be dependencies between these three aspects._x000D_
The definition of the implementation strategy should cover aspects like:
What are the implications of the SAP S/4HANA to the current landscape?
What is my productive system strategy? Scenario Decision: new
implementation versus system conversion or selective data transition.
Should I re-shape the existing landscape when introducing SAP S/4HANA?
Deployment Option: Cloud versus On-Premise Is it a “Big Bang”, or a
multi-year transition? What are intermediate architectures? Is SAP
S/4HANA a good opportunity to go “Back to SAP Standard”? How can I
use “Best Practice” content from SAP Activate? What are dependencies,
and what is the ideal sequence in the context of the overall release plan?
What is the strategy for custom development of SAP Fiori UI’s (e.g., using
Web IDE on SAP Cloud Platform) and other custom objects? What is the
security strategy? (e.g. authorization; authentication; technical security;
Governance Risk and Compliance; User management) What about Data
Privacy?_x000D_
Those questions can be addressed jointly with SAP, by using a structured
Best Practice approach: Limit the options according to boundary
conditions Define the right set of decision criteria, and rank the options
according to these criteria The strategy in general should be driven by
business needs. The more business critical a system is, the more serious it
is to consider the IT constraints._x000D_
Document the results. Upload all documents to the SAP Solution Manager so
information can be shared across the project team._x000D_
Results_x000D_
There is a document available which documents and explains the customer
specific implementation strategy._x000D_
_x000D_
The objective of this task is to derive the road map for implementing SAP S/4
HANA considering the findings from previous tasks.Prerequisites_x000D_
The definition of the road map is based on:Key findings from previous tasks
Identified architecture impact Consideration of parallel initiatives and
projectsProcedure _x000D_
In case this task is executed as part of the Value and Implementation
Strategy service component, the recommended step sequence is as
follows.Develop the building blocks (such as functional, organizational or
technical steps) required to reach the defined target architecturePerform 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 experiencesDetermine the risks of
transformationAgree on business transformation initiatives, and map the
value contribution to the segmented areas Compose a consolidated road
map of building blocks to implement the target solution landscapeAgree on
requirements & conditions for the business case calculationDefine KPIs, and
link them to the identified value driversDetermine the value driver
Determine the cost driver_x000D_
The value case is based on identified business benefits leveraging SAP
S/4HANA. _x000D_
Upload all documents to the SAP Solution Manager so information can be
shared across the project team.Results_x000D_
There is a documented implementation road map available.How SAP Can
Support_x000D_
See information on the Value and Implementation Strategy service
component from the tasks before.
_x000D_
To support the value identification, and the impact evaluation in the Discover
phase, it could be beneficial to have access to a trial system. At this point in
time in the project, there is no hardware available to run a new SAP system
on-premise, therefore installing a pre-configured appliance (“Blu-Ray, see
activity Define Cutover Approach in the Prepare phase) is not possible. A
cloud trial system is the preferred option in most cases._x000D_
User account at cloud provide required (e.g. Amazon Web Services
(AWS)._x000D_
Procedure_x000D_
Provide a Trial System_x000D_
Results_x000D_
As a result, project members have access to the trial system for demoing,
value identification, and impact evaluation._x000D_
SAP provides the cloud image of a pre-configured SAP system, which runs at
the cloud provider. See the landing page for a Quick Start and Demo
Guide._x000D_
_x000D_
Request an SAP Trial system in the cloud, and provide it to your project
team._x000D_
User account at cloud provide required (e.g. Amazon Web Services
(AWS))._x000D_
Procedure_x000D_
You can access the SAP cloud appliance via the SAP Cloud Appliance Library
(SAP CAL, https://cal.sap.com). It is a pay-per-use model hosted on Amazon
Web Services (AWS), MS Azure or Google Cloud Platform. When using the
SAP CAL option, you can choose between a 30-day trial, or a longer-lasting
engagement. With the trial, only cloud provider hosting fees need to be paid
by the customer. This is in the range of a few US$ per uptime hour plus a
small storage fee. If you opt to go beyond the 30-day limit, an SAP CAL
subscription license and a regular SAP license is required. Besides the SAP
backend, you also receive access to a MS Windows Terminal Server (WTS)
with the pre-configured Fiori Launchpad URL (if appropriate), SAP GUI logon,
and other useful frontend software. Go to the SAP Trial landing page at
SAP.COMInform yourself about the Cloud Appliance Library, and the different
options you have Click “Start your trial now” Accept terms and conditions
Select the right trial image (e.g. “SAP S/4HANA, on-premise edition
1809 Fully Activated”) Click “Try now” Accept terms and conditions
Maintain cloud provider account information Click “Create
Instance”_x000D_
_x000D_
Results_x000D_
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._x000D_
SAP provides the cloud image of a pre-configured SAP system, which runs at
the cloud provider._x000D_
_x000D_
_x000D_
Once the business case has been approved, the project is initiated in the
Prepare Phase as depicted in the figure below._x000D_
_x000D_
Figure: Activities in the Prepare phase_x000D_
There are customers running a prototype project in front of the real
transition project. The aim is often to check technical and functional
feasibility. Prototypes are small projects by its own, and usually last between
three and six months._x000D_
The formal setup of the project starts afterwards and 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._x000D_
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 more quickly in case of problems._x000D_
Project team enablement also starts now._x000D_
If not already done in the Discover Phase, an SAP S/4HANA readiness
assessment is performed on the SAP ERP system to identify aspects that
could have a major impact on the system conversion project (see task “Check
the Conversion Readiness of SAP ERP” for details)._x000D_
The project itself is planned at a high-level in a “Migration Planning
Workshop” for the conversion case, or in a “Transition Planning for 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._x000D_
The planning workshops often reveal preparation activity (e.g. the
“Customer Vender Integration” in the case of a system conversion), which
have to be done before the Explore phase starts. Those larger transition
preparation activities need to be planned in detail in the Project
Management work stream._x000D_
Some activities could start early: For conversion projects: The
cleanup of custom code which is not in use, and which could be
decommissioned before the conversion starts. Cleanup and archive
of business data, to reduce the size of your productive system. This will
reduce hardware requirements of your new SAP HANA database and reduce
_x000D_
The purpose of this deliverable is to ensure that the project team is informed
about the way of working during the Explore phase including usage of
Solution Manager for Solution Documentation._x000D_
Organize self-learning possibilities for IT professionals to understand the new
solution with digital learning environments (e.g. Learning Hub). This may
include: Grant project team member access to the SAP Support
Portal_x000D_
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 accessed 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 project team member
access to the SAP Learning Hub_x000D_
Ensure that all project team members can access the SAP Learning Hub. The
Learning Hub is a 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. Review training material on SAP
Solution Manager_x000D_
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 an
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. Review
training material on SAP Activate_x000D_
SAP Enterprise Support Customers can find information and sessions on SAP
Activate and SAP Solution Manager in the “Prepare” learning
journey._x000D_
_x000D_
The purpose of this task is to educate project team on Agile implementation
approach, principles and techniques.
_x000D_
The purpose of this task is to help the team understand the concept of SAP
Solution Manager with the focus on supporting implementation (and
upgrade) projects based on SAP Best Practices._x000D_
SAP Training platform provides Virtual Live Classroom "Implementation
Projects with SAP Solution Manager". The goal of the training is to: Explore
tools, services, and methods in detail to successfully and efficiently
implement complete software solutions Learn how to create a structured,
comprehensive and standardized project during the entire lifecycle of the
implementation and the solution
_x000D_
The purpose of this task is to educate the project team on Agile
implementation approach, principles and techniques. The training will focus
on Agile Project Delivery to enable the project manager and team leads to
effectively embed and execute Agile Project Delivery approach via SAP
Activate Implementation Methodology._x000D_
Project Management will provide additional project learning enablement
and approach where appropriate.
_x000D_
The purpose of this task is to clarify deliverables and expectations,
methodology, and tools. Typically, two to three days should be reserved for
this enablement. Once the team members or at minimum the team leads
are identified, they will be brought on board with this enablement session
before the phase kickoff meeting._x000D_
The enablement deliverable: Sets project team expectations and delta
design deliverables Provides guidance for delta design workshops and
relevant enabling toolsIntroduces quality assurance and its acceptance
criteria Prepares for essential skills, such as workshop facilitation,
requirements gathering, and process modeling Fosters teamwork within
project teams
_x000D_
The purpose of this task is to train the key users for the solution in scope
(pre-defined content).
_x000D_
To properly plan and prepare for the transition, it is key to understand the
value of the innovations delivered by the new system for customer business
solutions. Prototyping enables the customer to evaluate the value addition
with real business scenarios using real data._x000D_
Prototyping is an optional small project on its own. It requires dedicated
planning, execution and final evaluation; thus it is always driven by business
or IT requirements._x000D_
Procedure_x000D_
The main steps of a prototyping project are as follows (see figure below):
Run a scoping workshop for prototyping Set up the prototyping system
(either new installation, or system conversion) Conduct a data migration
(in case of a new implementation) Activate the solution in scope Run Fit-
Gap workshops, and finalize the setup of the prototype Validate the
prototype Run a final results workshop_x000D_
_x000D_
Figure: Structure of the “Plan & Prototype” approach_x000D_
Results_x000D_
The result of a prototype usually has a 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).
_x000D_
The goal of this task is to run a prototype._x000D_
Procedure _x000D_
The prototyping project is usually run in the discovery, prepare, and explore
phases of the overall implementation road map. In the discovery phase, the
customer and SAP agree on the detailed prototyping scope. In the prepare
phase, the project responsibilities and schedule are finalized, and the team
conducts the necessary steps to set up and prepare the prototyping system
landscape. In the explore phase, the agreed scope of the prototyping project
is implemented and validated._x000D_
SAP’ “SAP Value Assurance plan and safeguard” service package provides the
“Plan & Prototype (PLPT)” option. 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. The “Plan & Prototype” option can be used for
both system conversion and new implementation projects. The included
components are as follows:The “SAP Readiness Check” summarizes the most
important aspects of the conversion project in an easily consumable way.
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” professional 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 service component “UX Activation and
Design” supports the PLPT project in terms of activation of Fioris that have
been defined in the scope for the project. 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
_x000D_
The planning of the transition project helps to properly define the scope and
execution plan for the upcoming SAP S/4HANA transition project. The result
is a first version of an action plan, which can serve as the basis for a project
plan. The project plan will be constantly refined throughout the project
(during the Prepare and the Explore phase) as part of the project
management work stream._x000D_
Proper transition planning is required for all scenarios. However, the
conversion readiness only needs to be checked in case of a system
conversion or selective data transition._x000D_
Procedure Check the conversion readiness of the current SAP ERP (system
conversion scenarios only) Define the scope and the objectives of the
transition Define the cutover approach (high-level) Clarify the adaption
of existing custom code, and the development of new custom code (if
required) Clarify operational readiness Define the technical
architecture (if not already done in the Discover phase) Define the data
migration architecture (important for new implementation and selective data
transition) Plan your data volume management Define the UX / UI
strategy Prepare interface register Run a legacy impact analysis on
interface inventory and data integration Run a first assessment on Output
Management Run a first assessment on training requirements Optional:
Run a Technical Security Self Check_x000D_
Results_x000D_
As a result, a first version of an action plan has been documented which
could serve as the basis for a project plan._x000D_
The conversion readiness can be checked with the SAP Readiness Check for
SAP S/4HANA. See activity Implementation Strategy task Check the
Conversion Readiness of SAP ERP for details._x000D_
For conversion projects, SAP offers the Migration Planning Workshop (MPW).
The MPW helps to define the scope and execution plan for the customer’s
conversion project to SAP S/4HANA._x000D_
_x000D_
Figure: Structure of the “Migration Planning Workshop” (MPW)_x000D_
Main objectives / deliverables of the workshop are (see figure above): The
MPW helps customers who may be considering or planning the transition to
S/4HANA, Suite on HANA, and/or BW on HANA. The service provides a
_x000D_
In case the conversion readiness has not been checked already in the
Discover phase of the project (see activity Application Value and Scoping,
task Check Conversion Readiness of Sap ERP):
There could be show stoppers (e.g. incompatible Add-On’s installed in the
existing SAP ERP system) or requirements (e.g. version dependency issues
with SAP NetWeaver hub system) that could 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, so as to be able to adapt the
overall project plan accordingly._x000D_
This task is in particularly important for system conversion and selective data
transition (in case they start with a system conversion) scenarios._x000D_
Procedure _x000D_
SAP recommends checking the following areas, and to document the results:
Is today’s functional scope in SAP ERP supported in SAP S/4HANA (e.g.
Industry Solutions, Enterprise Extensions, 3rd party add-ons, etc…)?
Are there incompatible add-ons from 3rd party software vendors? In
this case please contact the software vendor early and ask for advice.
Potentially there is a newer add-on version which is compatible to SAP
S/4HANA.
For SAP Standard add-ons, or add-ons delivered by SAP IBSO, please see
SAP note 2214409 - SAP S/4HANA: Compatible Add-ons. Is there
functionality used today that will need to be replaced with the conversion to
SAP S/4HANA (e.g. Cash Management)? You will need to compare the
functionality in use in the current SAP ERP with the Simplification List from
SAP: Are all technical system requirements fulfilled (e.g. software
levels, single stack system, Unicode, etc…)? Otherwise they will need
to be planned as part of the conversion. Are all dependent SAP
NetWeaver hub systems on the required release? How many custom
objects are impacted by the DB migration to SAP HANA? How many custom
objects are impacted by the simplification of the financial data model? How
many custom objects are impacted by the change in SAP software?
Which business critical reports and transactions are in use today, which will
be replaced / removed in SAP S/4HANA? Which configuration needs to
be adjusted? What is the estimated SAP S/4HANA system size? Are
there options to reduce the size before the conversion? _x000D_
To do so, SAP recommends to: Study the Simplification Item Catalog.
_x000D_
To define and document the objectives of the transition project, you should
create a scope document. The scope documentation serves as a general
guideline for the transition project. It must describe the starting point of the
project as well as the project objectives. This information is necessary to
develop the target solution landscape, define the transition approach and to
finally verify the success of the overall project._x000D_
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 must be determined._x000D_
The objectives comprise the business and IT requirements related to the
new functionality and technology available with SAP S/4HANA, e.g.
Provision of new functionality in Finance and Logistics Reduction of costs or
complexity Performance improvements for specific business functions
Improvement of User Experience Landscape adaptations to comply with
changing market and business requirements_x000D_
Ideally, the objectives are defined in a way that they can serve as success
criteria for the transition project. Further success criteria can be derived
from boundary conditions, e.g. business downtime requirements for the
transition project._x000D_
There is an implementation strategy and road map already available as input
for the scope document._x000D_
Procedure _x000D_
Document the scope of the SAP S/4HANA transition project. Clarify and
describe the following general aspects: Expectations from the business
Expectations from IT Conversion target product including anticipated
functional quick wins SAP solution in scope for the conversion Related SAP
systems (name, SAP products, release, database size, and business
criticality)_x000D_
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 the target product
perspective._x000D_
The SAP S/4HANA 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
_x000D_
A good starting point to become familiar with system cutover is the
“Administration Guide for the Implementation of SAP S/4HANA” which
covers both the new installation of a system, and the system conversion. As
always administration, implementation and conversion guides are release
and feature pack specific. You can find all guides for all releases and feature
packs in the SAP Online help portal for SAP S/4HANA._x000D_
The cutover approach for system conversion and new implementation
differs. _x000D_
System conversion: _x000D_
Please note: The picture below presents the transition paths ´to the
SAP S/4HANA family. _x000D_
This road map documents the system conversion to the newest release of
SAP S/4HANA. _x000D_
_x000D_
Figure: Transition path to SAP S/4HANA _x000D_
System conversion to older releases are documented in former road map
versions which are available as PDF documents on request. Please also note
that this road map does not cover upgrade procedures (e.g. the upgrade
from SAP S/4HANA 1511 to SAP S/4HANA 1809). See SAP note 2426277
“Add. info. on converting to SAP S/4HANA using SUM 2.0 SP00” for details.
_x000D_
Please check the landing page of the SL Toolset (accelerator section) to find
the latest appropriate SUM version, and the respective SAP Note for more
information. _x000D_
A cutover planning starts from a system-level transition road map which
documents the conversion sequence, and the creation of temporary systems
to keep up a production support track. _x000D_
The following figure shows an example of such a transition road map in six
cycles. _x000D_
_x000D_
Figure: System-level transition road map for system conversion (Example)
1) References the creation of the sandbox from a copy from
production. 2) References the conversion of the development system
D01 while keeping DT1 as a temporary production support system. 3)
References the conversion of the quality assurance system Q01 while
keeping QT1 as a temporary production support system. 4)
References cutover preparation and dress rehearsal runs. 5)
_x000D_
Custom code may need to be adapted to work properly with SAP HANA and
SAP S/4HANA. This is important: In case of a system conversion: Details
on the identification of affected code will be given later in the Explore Phase
(activity “Custom Code Impact ”) or see accelerator section. In case of a
new implementation, and the old system is an SAP system where custom
code should be transferred over. The new implementation of an SAP
S/4HANA system is an opportunity to re-evaluate custom coding and SAP
modifications, that were required in the past, but that can be
decommissioned now, and replaced by new SAP standard solution._x000D_
This task is relevant in the case of a system conversion. It can be relevant for
new implementation scenarios, where custom code should be taken over
from an old SAP ERP system._x000D_
Procedure _x000D_
For system conversion: _x000D_
The 4-step sequence to adapt custom code with respect to a system
conversion to SAP S/4HANA is shown in the next figure. _x000D_
_x000D_
_x000D_
Figure: Preparatory and adjustment steps for custom code in the context of a
system conversion_x000D_
Either executed continuously, or in front of an SAP S/4HANA conversion
project: Step 1: Get transparency on your custom code situation -; The SAP
Readiness Check for SAP S/4HANA should have performed an early effort
estimation on custom code adjustment, which is sufficient for the high-level
conversion plan at this point in time.Step 2: Remove waste (custom code
that is no longer used) -; This is covered by task Clean up unused code from
activity Transition preparation._x000D_
As part of the SAP S/4HANA conversion project: Step 3: Identify the impact
of the DB migration to SAP HANA, and the conversion to SAP S/4HANA, and
create an adaption plan - This is covered by activity Custom Code Impact.
Step 4: Adapt your code by either going back to the SAP Standard, or by
adjusting the custom coding -; This activity happens later in the Realize
phase._x000D_
For new implementation: In case custom code should be transferred from
an old SAP ERP system, check if the custom code can be replaced by SAP
standard code instead._x000D_
_x000D_
With the introduction of a new solution like SAP S/4HANA, your current IT
support framework will change. For this, many aspects need to be
considered._x000D_
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…_x000D_
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, several tasks will be defined and included in the
conversion plan._x000D_
Procedure_x000D_
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._x000D_
SAP has also published SAP Support Standards which should be
implemented as part of the standard IT support processes._x000D_
See accelerator section for guidance._x000D_
See Primary CCOE Certification program in the accelerators section.
_x000D_
With the introduction of the first productive SAP component running on SAP
HANA, the IT architecture will change (e.g. new HW, new OS, new HA/DR
setup options…)._x000D_
There is an implementation road map (high level) available describing the
“to-be” business architecture of SAP S/4HANA._x000D_
Invite your hardware provider to join this task._x000D_
Procedure_x000D_
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 Cloud Platform for side-by-side extensions of S/4HANA)
Backup solution_x000D_
Clarify and document the following topics: What is the “to-be” SAP
Landscape? What is the anticipated SAP architecture (main technical
components)? What is the sizing relevant information (SAPS, memory,
disk space) of all SAP components? What technical options are in scope
(e.g. Tailored Data Center Integration (TDI))? What frontend components
are required for FIORI?What is the required HA / DR strategy, based on
availability requirements, business downtime SLAs and the existing data
center strategy? What is the ideal backup strategy? What is the strategy
for the non-production landscape based on change management
requirements?_x000D_
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._x000D_
Please note: Customers who do not have any experience with SAP, or with
SAP HANA should study the existing material on SAP HANA and SAP
S/4HANA before starting this task, because the definition of the technical
architecture requires sound knowledge on many technical aspects. A good
_x000D_
The purpose of this task is to prepare a high-level assessment of the source
systems and necessary data objects as well as for methods to extract /
transform / load the source data from legacy systems and or SAP
systems._x000D_
This activity is required for new implementation and selective data transition
scenarios in case of complex data operations which require a guidance for
data objects and data migration technologies._x000D_
Procedure _x000D_
The procedure differs depending on the implementation scenario._x000D_
Look up the SAP Blog “Migrating data to your (new) SAP S/4HANA” to learn
about the ways in which your business data can be migrated to your newly
deployed SAP S/4HANA system (on-premise or cloud)._x000D_
A first definition of the data migration architecture is discussed in the service
component Transition Planning for New Implementation. See also activity
Transition Planning for details._x000D_
The data migration architecture is further detailed out in the Explore phase
of the project (see activity Data Migration Design)._x000D_
SAP also offers a dedicated service component called “Data Migration
Architecture”, to identify the required data migration scenarios. The Data
Migration Architecture assessment for technical selective data transitions is
conducted on a high-level basis to identify the most suitable data migration
execution services, such as client transfer, consolidation of SAP ERP systems
to one target system for SAP S/4HANA, company code transfer, or data
migrations based on preconfigured objects. SAP experts lead you through
discussions to specify on a high level your requirements for the selection of
data, and tailor the scope of a subsequent Data Migration
Assessment._x000D_
SAP Enterprise Support customers can find information and services on data
migration in the context of SAP S/4HANA in the “Become competent”
section of the “Explore” learning journey.
_x000D_
Data Volume Management should be considered prior to a system
conversion to reduce the amount of data to be converted (this has
implications on duration / downtime of the cutover) as well as to reduce the
amount of data in memory (has implications of hardware costs). It is also
recommended in an up and running SAP HANA environment to develop a
common DVM Strategy including several systems, common retention
management and storage requirements. Data Volume Planning is the first
step in the Data Volume Management lifecycle._x000D_
Analyze the current database and determine how much data can be archived
or deleted upfront of an SAP S/4HANA implementation._x000D_
Data Volume Management Planning should be considered specifically in the
following cases: Sizing results indicate the need for an SAP HANA server
larger than the expected DVM Alerts from the SAP Early Watch Alert
report indicate a need for DVM Data archiving is already actively used. This
indicates the need to adjust the archiving strategy according to the new data
models and technology (i.e. data aging) The system is older than 5 years
and no significant data archiving has been scheduled and there is a high
probability that data is on the system that is no longer relevant for daily
business processes. Customer requires a roadmap to support their SAP
HANA conversion proactively._x000D_
In those cases, SAP recommends to further analyze, if there should be
additional DVM activities included in the SAP S/4HANA implementation
project._x000D_
Precondition is a first estimate on the expected database size of SAP HANA
(see task Define Technical Architecture under this activity)._x000D_
Procedure _x000D_
Use common analysis tools like DVM Work Center in SAP Solution Manager,
transactions DB02, TAANA, and SE12. However, in case you have not
archived before, it could be challenging to identify the key archiving objects
and their saving potential._x000D_
Results_x000D_
A decision for future DVM activities as part of this project and road map on
how to proceed with DVM (e.g. with clean-up or archiving) prior to a
transition to SAP S/4HANA._x000D_
SAP can perform this task with the “Data Volume Planning” service
_x000D_
With SAP S/4HANA comes a new user interface concept named “SAP Fiori”.
The purpose of this task is to create or update your UX / UI strategy to
incorporate the SAP Fiori concept._x000D_
You already have knowledge of your business users UX / UI requirements.
Ideally there is also an understanding of future business processes (including
UX / UI requirements) planned with SAP S/4HANA._x000D_
Procedure Clarify on the SAP Fiori concept in general, if not already done.
This includes the technical architecture, data provisioning, role model,or SAP
Fiori Apps Library. Collect UX / UI requirements from your business. This is
not limited to current requirements on SAP GUI or SAP Business Client. For
instance, think about mobile scenarios planned with SAP S/4HANA in future.
Design a strategy with SAP Fiori, based on collected requirements. The
strategy also describes the future SAP Fiori Front End Service
architecture._x000D_
As an input into your UX / UI strategy, you can order a free of charge “SAP
Fiori Apps Recommendation Report” early in the project. The report
provides recommendations based on your current system usage. See SAP
blog “SAP Fiori Apps Recommendation Report -; Easy discovery of relevant
SAP Fiori Apps” for ordering details. In addition, you may get additional
inspiration by looking up the the SAP Fiori lighthouse scenarios. You will find
them on the entry page of SAP Fiori Apps reference library._x000D_
Results_x000D_
You have created / updated a UX / UI strategy in the context of the SAP
S/4HANA implementation._x000D_
Regarding SAP Fiori, all customers should look at the SAP WIKI linked from
the accelerator section. Please also read the SAP Blog - Fiori for S/4HANA -;
Top 10 Myths & Misconceptions to Avoid._x000D_
SAP offers the “UX & UI Architecture” service component to support you
creating an UX Strategy for your company. It further clarifies the transition to
Fiori together with our experts for clear and optimal project and architecture
planning._x000D_
SAP Enterprise Support customers can find a lot of information and services
on UX strategy and SAP Fiori in the context of SAP S/4HANA in the “Become
competent” section of the “Prepare” and “Explore” learning journeys.
_x000D_
The purpose of the interface register task is to preliminarily identify the
external systems, applications, and business objects or transactions that
must be integrated with the SAP S/4HANA system to realize the objectives of
the project._x000D_
The interface register contains all interfaces and therefore allows to scope
and plan the implementation project. The customer must have a clear vision
of the to-be system & solution architecture with interfaces._x000D_
Procedure_x000D_
All interfaces are documented within a central document (called “interface
register”). By specifying the interfaces in predefined attributes a clear
grouping into technology and interface types is possible, which allows to
integrate the corresponding requirements into the project scoping and
planning structures._x000D_
Once an interface scope has been agreed, the interface register is updated
using a change control process. The interface register template is initially
pre-populated by the customer with legacy interfaces, that are in scope for
re-implementation against the new SAP S/4HANA system. New to-be
implemented interfaces are included into the interface register._x000D_
In case SAP Solution Manager 7.2 is available, it is recommended to
document interfaces directly there as part of the overall solution
documentation. Concentrating interface and business process information
centrally in SAP Solution Manager has a couple of advantages: Increased
visibility and avoidance of duplicate maintenance of interface data in
different tools. The effect of planned downtimes in your solution
landscape can be judged more easily, especially in case the interfaces are
assigned to business processes. In case a system has stopped unexpectedly,
or a particular interface has become stuck due to technical errors, you can
identify the affected business processes directly in SAP Solution Manager.
Finally, there is an integration with the interface & connection
monitoring application. Interface attribute data maintained in interface
documentation can be used to configure interface channels for monitoring &
alerting._x000D_
See accelerator section for a setup and end user guide on interface
documentation in SAP Solution Manager._x000D_
Results_x000D_
Populated interface register_x000D_
_x000D_
The objective of this task is to assess the impact on interfaces when moving
over from SAP ECC to SAP S/4HANA via system conversion or new
implementation. In both cases, interfaces can be affected by technology
changes (i.e. field changes)._x000D_
General remarks: In a hybrid cloud and on-premise landscape, different
integration capabilities are key. Those integration capabilities may change
over time, or be developed further. Integration capabilities from a current
to a successor product are generally preserved (e.g. when moving from SAP
ERP to SAP S/4HANA). SAP Cloud Platform Integration offers rich “Integration
as a Service” capabilities. SAP Cloud Platform delivers preconfigured
integration models for SAPs most important cloud solutions. Integration
capabilities are typically preserved when moving to a recommended
successor product._x000D_
To make the SAP S/4HANA adoption easy for all existing SAP customers, SAP
has kept most of the official interfaces to and from SAP ERP stable when
simplifying the applications in SAP S/4HANA. This is not necessarily the case
for non-official interfaces (e.g. usage of ODBC on DB level)._x000D_
An initial interface register must be already available._x000D_
Procedure As a first step you should analyze your existing interfaces, and
categorize them according to complexity, technology and custom
development. Potentially some interfaces can be retired as well.As a second
step check the compatibility with SAP S/4HANA and other new SAP products
(on-premise or cloud-based solutions) that you would like to introduce. For
cloud integration “SAP Cloud Platform Integration” offers a rich
preconfigured integration and API discovery. See “API Discovery” in the
accelerator section for details. Further information and links can be found
on the landing page of SAPs Technical Integration and Orchestration Group.
The functional work stream needs to check on interfaces that are in
scope (interface register) for technology changes. Document necessary
interface adjustments in the backlog as gap._x000D_
Results_x000D_
The transition impact on interfaces has been made transparent. Necessary
changes are specified and added to the project backlog as gap._x000D_
The “Integration Assessment (INAS)” service component explains the
interface register concept in SAP Solution Manager 7.2 to customers. It
_x000D_
SAP S/4HANA introduces a new style of output management (OM)._x000D_
The output management for SAP S/4HANA comprises all functionalities and
processes that are related to the output of documents. This includes the
integration of output management functions into the business applications,
the reuse component output control, as well as the SAP NetWeaver
technologies and the technical infrastructure._x000D_
The new output management is going to be the successor of all other output
management frameworks (SD Output Control, FI Correspondence, FI-CA
Print Workbench, CRM Post-Processing). However, all other frameworks are
still available and can be used. It is not mandatory to use the new output
management._x000D_
Business applications that have already adopted the new output
management use it by default. Nonetheless, customers can always revert to
the other supported framework. How this reversion is realized depends on
the business application (for example via SAP Note or by implementation of
an enhancement point). It is also possible to re-enable the new output
management again at a later point in time._x000D_
Hence, the new output management for SAP S/4HANA coexists with other
frameworks. Customers can decide on business application level which
framework supports their output scenarios best._x000D_
The objective of this task is to determine and to document the impact of the
new output management on your existing output management
configuration._x000D_
This task is of particular interest for system conversion scenarios, and for
selective data transitions which start with a system conversion._x000D_
New implementations will always start with the new output
management._x000D_
Procedure_x000D_
In the SAP ECC Business Suite, different output frameworks are used in
different applications (SD Output Control, FI Correspondence, FI-CA Print
Workbench, CRM Post-Processing Framework)._x000D_
Considering the conversion of an existing system to SAP S/4HANA, it
becomes evident that there cannot be one generic approach to cover the
conversion of all other OM frameworks._x000D_
Looking further into the most prominent existing OM framework SD Output
control (NAST), it becomes clear that: 100% feature parity is not a given
_x000D_
The objective of this task is to identify the enablement scope for end user
training._x000D_
Procedure_x000D_
Run a first assessment on the training requirements which arises from the
SAP transition project: Gather information about the SAP transition project,
and identify affected organizational units Conduct interviews regarding
training strategy elements Identify training relevant user groups (Project
Team, Key User, End User) Evaluate the high-level enablement scope for End
User Training_x000D_
SAP offers the “Initial Enablement Assessment”. It is part of the “Enablement
Charter” service component._x000D_
The Initial Enablement Assessment is the analysis of learning and
enablement related aspects of Digital Learning in general and with respect to
your actual situation. The assessment helps to get an understanding of the
general learning management situation, your enablement capabilities to
support the digital transformation process and the alignment with the
project scope and timeline. Based on the results of the assessment, specific
training management activities will be identified and recommendations will
be provided to enable a successful enablement delivery. It is particularly
relevant at the beginning of a project._x000D_
See accelerator section for details.
_x000D_
With the conversion to SAP S/4HANA, new technical and functional security
requirements may come up. The technical security requirements are related
to new components that are part of SAP S/4HANA (e.g. new security
settings, and security role changes related to SAP HANA, or related to HANA
Live). The Accelerators section contains links to detailed Security Guides. The
SAP ERP Central Component Security Guide for instance covers both
technical and functional security aspects._x000D_
However, this activity focuses on basic technical security checks that
customers can execute themselves. The recommendations arising from
these self-checks can then be implemented in the Realize Phase as part of
the conversion project._x000D_
This task is of particular interest for system conversion. However, customers
who would like to replace an existing SAP ERP with a new implementation of
SAP S/4HANA should be aware of significant security changes (technical and
functional)._x000D_
Procedure_x000D_
To get a status on the technical security in your SAP system, proceed as
follows: Have a look at the Security chapter of the Early Watch Alert (EWA)
report of your SAP ERP system and analyze the root cause of the findings.
See also SAP Note 863362 for a complete list of security checks as part of
EWA. Run a Security Optimization Service SOS. Enterprise Support
customers can order an EGI which runs them through the SOS Self Service.
See SAP Enterprise Support Academy for details. With Configuration
Validation, you can benchmark system configuration settings against SAP
Best Practice settings. Configuration Validation can also be used to check
your security settings (in front of a system conversion, and later on
continuously to support IT security in your support environment).
Configuration Validation, in general, can be easily set up by joining an EGI.
Security relevant checks as part of Configuration can be found in the SAP
WIKI on Technical Operations (see Accelerators section for details). Fill out
an SAP Security Baseline Template: _x000D_
The SAP Security Baseline Template document provided by SAP on how an
organization-specific SAP Security Baseline could be structured. It is pre-filled
with selected baseline-relevant requirements and corresponding concrete
values as recommended by SAP. In a first step, you should focus on chapter 2
- Regulations of the document. The latest version of the SAP Security
_x000D_
This activity covers all preparation work which happens before the project
starts. The intention to exclude the preparation work in an extra activity is
also to keep the business downtime small during cut-over weekend.
However, each significant preparation item should have been discussed
upfront in the appropriate planning workshops in the Transition Planning
activity._x000D_
The list below shows typical areas which need preparation because of
common functionality changes with SAP S/4HANA, and recommended
readings. Each item is documented by one or multiple simplification
items._x000D_
For system conversion:The migration of customers and vendors to Business
Partner (“Customer/Vendor Integration”) See the SAP Blog
“Business Partner -; Customer-Vendor Integration S/4HANA” from the
Regional Implementation Group (RIG) on this topic Look at the SAP
S/4HANA Cookbook on Customer / Vendor Integration
Replacement of Foreign Trade by SAP Global Trade Services (GTS)
See SAP Note 2223144 - S/4 HANA - Foreign Trade in SD/MM
New Asset Accounting See also the SAP Blog “S/4 HANA- New
Asset Accounting -; Considering Key Aspects” from the Regional
Implementation Group (RIG) on this topic See “Converting
Accounting Components to SAP S/4HANA”, which is attached to SAP
Note2332030 - Conversion of accounting to SAP S/4HANA General
Ledger -; Data conversion Replacement of Rebate Management by
Settlement Management See SAP note 2226380 - S/4 HANA:
Deprecation of SD Rebate Processing The introduction of new
Cash Management and Credit Management with SAP S/4HANA
Cash Management: See SAP Note 2270400 - S4TWL - Cash Management -
General Credit Management: See SAP Note 2270544 - S4TWL - Credit
Management The replacement of Revenue Recognition by RAR in
SAP S/4HANA See SAP Note 2225170 - S/4 HANA SD-Revenue
Recognition Material number field extension The impact of
SAP S/4HANA on BW extractors Data consistency analysis of transactional
data and totals. This is of particular interest in the finance area and should
be addressed at the latest in the first sandbox conversion. The cleanup of
custom code Analysis and close of open business to make those documents
available for archiving. This activity can be time consuming because you will
need to identify open business documents first, before clarifying the root
_x000D_
The goal of this task is to plan and execute all preparation activities which
should happen before the transition project starts._x000D_
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._x000D_
_x000D_
Procedure Properly analyze all preparation items which have been
identified in the Transition Planning This could be for instance the
Customer/Vendor Integration (CVI), or the use of SAP GTS instead of Foreign
Trade. 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._x000D_
SAP provides additional information for typical preparation activities in case
of a system conversion, for instance: The TOP Simplification List Items
including further explanation A Best Practice Guide on the Business
Partner Approach (Customer Vendor Integration) -; see attachments of SAP
Note 2265093 SAP expert blogs from the Regional Implementation Group
(RIG)_x000D_
SAP also offers the “Mandatory Preparation for System Conversion” service
component to support necessary preparation work (like Customer Vendor
Integration) in system conversion projects, which needs to be executed as
part of the sandbox system setup
_x000D_
In this task you clean up or archive data in the productive SAP system (before
it gets converted). See the accelerator section for a procedure
description._x000D_
This task is of particular interest in case of a system conversion
scenario._x000D_
There is a documented strategy on DVM, which defines the residence time
definition of business data._x000D_
Data volume planning (as part of Transition Planning activity) has indicated
the need for data cleanup and archiving._x000D_
Procedure _x000D_
Based on the residence time definition (i.e. when the business data can
either be deleted from the database or moved to an archive file) and the
corresponding customizing settings, the deletion and archive jobs must be
scheduled partly massively parallel to achieve that the data is really removed
from the database before the conversion starts. This job scheduling can only
be partly automated and requires manual interaction and monitoring by a
basis administrator._x000D_
Please note that due to necessary alignment between business and IT, data
cleanup can be a time-consuming process. You can already start this activity
already early on in the project, by focusing on basis tables which are owned
by the IT team._x000D_
Proceed as follows: Archive business data as defined in the DVM strategy.
Set up the write and delete jobs as described in the DVM Best Practice Guide
(accelerator section). Run housekeeping jobs e.g. on the SAP Spool
environment as described in the DVM Best Practice Guide (accelerator
section)._x000D_
Results_x000D_
The SAP system has been cleaned from data which can be either removed or
archived. The used space in the database has been reduced._x000D_
SAP can support this task with the "Cleanup / Archive" scope option, which
is part of the "Build Execution" service. Please see “SAP Advanced
Deployment” link below and ask your SAP contact
_x000D_
The objective of this task is to decommission custom code which is not in
use upfront of a system conversion. Although this task is optional, it is highly
recommended to avoid adjustment efforts for coding which is not
required._x000D_
Procedure_x000D_
Proceed as follows: Set up the Decommissioning Cockpit in SAP Solution
Manager. Decommission unused custom code as documented in the
accelerator 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._x000D_
Results_x000D_
Unused custom code has been decommissioned from the SAP system and
does not need to be adjusted in future._x000D_
The “Custom Code Migration Guide for SAP S/4HANA 1809” provides
instructions on how to adapt custom code in the context of a system
conversion to SAP S/4HANA (see accelerator section)._x000D_
In addition, SAP has published excellent blogs on custom code management
in the context of a system conversion: To learn about the challenge, start
with the SAP Blog “SAP S/4HANA System Conversion -; Challenge for your
custom code”. To understand the necessary adaption process for your
custom code, look at: The SAP Blog “SAP S/4HANA System
Conversion -; Custom code adaptation process” The SAP Blog “ABAP
custom code adaptation for SAP HANA -; The efficient way” What
you can (or better: should) do well upfront of a planned system conversion is
documented in the SAP Blog “What can you do today to prepare your
custom code for SAP S/4HANA”. This blog addresses both the cleanup as well
as the improvement of custom code quality. Finally, there is a blog series
describing all relevant expert tools required for analysis. The first issue is the
SAP Blog “Remote Code Analysis in ATC -; One central check system for
multiple systems on various releases”._x000D_
You will find all links in the accelerator section._x000D_
In a first step and if not already done, SAP can help you setting up the
required tools for custom code management and making you familiar with
these. This service component is called “Custom Code Management Tools
Enablement”:_x000D_
The Custom Code Management Tools Enablement service component is to
_x000D_
The objective of this task is to improve the software quality of your custom
code upfront of a system conversion. It also seeks for quality improvement
within the development process in general (thus relevant for all
scenarios)._x000D_
Please note: This task does not directly address the code adjustment
necessary due to the upcoming system conversion to SAP S/4HANA. Those
will be in later project phases._x000D_
Procedure_x000D_
Proceed as follows: Set up an efficient custom code quality management
process and project Implement the corresponding Software Quality check
tools, like SAP ABAP Test cockpit or SAP Code Inspector Incorporate them
in the development process Identify opportunities for side-by-side
extensions with SAP Cloud Platform, e.g., using Web IDE for Fiori UI’s.
Test your newly implemented quality measures by running a code quality
improvement project._x000D_
Results_x000D_
Quality measures for high code quality have been established, and tested in
a code quality improvement project. From now on custom code will be will
be created with the necessary quality level._x000D_
In a first step and if not already done, SAP can help you setting up the
required tools for custom code management and making you familiar with
these. This service component is called “Custom Code Management Tools
Enablement”:_x000D_
The Custom Code Management Tools Enablement service component is to
perform the CCM tools initialization and configuration in the customer’s SAP
environment and to facilitate the knowledge transfer about the tools
operation to the customer’s organization. Per default the project scope
includes the implementation of Custom Code Lifecycle Management and
activation of Usage and Procedure Logging tool. Depending on the
customer’s requirements, the project scope can be extended to facilitate the
configuration of other tools as well, e.g. ABAP Test Cockpit, Clone Finder or
Decommissioning Cockpit. The empowering part of the project includes the
knowledge transfer about the tools which are included in the scope._x000D_
In a next step, SAP can review your strategy on custom code quality, and help
you with a code quality improvement project. This service component is
called Custom Code Quality Improvement”:_x000D_
_x000D_
There should be at least an SAP Solution Manager 7.2 already set up and
configured on-premise. See Accelerator’s section for more details how to set
up SAP Solution Manager._x000D_
SAP Solution Manager is required for all scenarios. SAP Solution Manager
does both support project execution (e.g. scoping business processes
together with SAP Activate), as well as support operations of the new SAP
S/4HANA system after Go-Live (e.g. via system monitoring and root cause
analysis). This road map considers SAP Solution Manager 7.2 as available. In
case this release level is not available on-premise, SAP offers SAP Solution
Manager also via Cloud Appliance Library (CAL)._x000D_
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 also offers SAP Solution Manager via SAP Cloud
Appliance Library (SAP 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: You plan the implementation (such
as scope, hardware and software requirements, and release restrictions).
You plan the system landscape for your use cases. You install the
components of your SAP Solution Manager system. You configure
your system. You set up the connection to the managed systems.
Once SAP Solution Manager is set up, the following areas are key
for project support: Solution Implementation -; the
identification, adaptation, and implementation of new and enhanced
business scenarios. Solution Documentation -; centralized
documentation repository ensuring the relationship of business process
definitions with technical configuration decisions. Change Control
Management -; synchronized deployment of application configuration with
integrated project control and quality management. SAP provides
customers with an 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 for new implementation scenarios to
use the SAP Solution Manager Focused Build solution. Additional details can
be found in the accelerator section. It also contains a link to an overview
presentation which documents how Focused Build and SAP Activate nicely fit
together._x000D_
Results_x000D_
_x000D_
The purpose of this task is to import the SAP Activate Best Practices content
into SAP Solution Manager._x000D_
SAP Solution Manager 7.2 is available for project support._x000D_
Procedure_x000D_
The following screen shot shows a Best Practices business process diagram in
SAP Solution Manager._x000D_
_x000D_
Figure: Process diagram in SAP Solution Manager 7.2_x000D_
Follow the detailed instructions given in chapter “Identify, select and load
SAP Best Practices content into SAP Solution Manager 7.2” in the Best
Practice Reference Guide, to import SAP Activate Best Practice content into
SAP Solution Manager 7.2._x000D_
After import, the Best Practice process diagrams including documentation
and test scripts are available in SAP Solution Manager and can be used and
tailored in the sub sequent Fit / Gap workshops with the business process
champions._x000D_
Results_x000D_
The newest Best Practices content is available in SAP Solution Manager for
the project team._x000D_
See service component “Agile Methodology and Tool Coach”, which consists
of a single point of contact, who is responsible for all activities around the
implementation and operation of focused build. The focused build coach is
your contact to discuss all topics related to implementation methodology. He
or she makes sure all issues are resolved and that you receive the included
configuration services and trainings at the right point in time with the right
skills from SAP.
_x000D_
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._x000D_
The assumptions with respect to Project Management are as follows: 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*) _x000D_
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
_x000D_ for reporting and safeguarding reasons._x000D_
The purpose of this task is to efficiently transition the project from the
opportunity team to the delivery team. During this task the project manager
schedules and conducts internal meetings to transfer key information from
the opportunity phase into the project._x000D_
Procedure_x000D_
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.
_x000D_
The purpose of this task is to clarify any questions in regarding to the Signed
SAP Contract (SOW), Order Form, confirm scope, RACI and resolve any
issues. This includes review of the delivery model._x000D_
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
_x000D_
The stakeholder identification process is a critical process of initiating the
project and aligning the project objectives with the expectations and
requirements of the stakeholders. It is critical for the success of the project
to identify, and involve stakeholders and keep them engaged throughout the
project.
_x000D_
The purpose of this task is to build agile awareness of key stakeholders,
secure commitment to adopt standard SAP functionality where possible. It is
recommended to conduct informal and formal meetings to set the
expectations and confirm the project approach with key project
stakeholders.
_x000D_
The Project Charter formally documents the business needs and benefits of
the project to confirm alignment with customer key stakeholders. It
authorizes the project and is based on the Order Form(s) and Business Case.
This document outlines the purpose, high level approach and key
characteristics that define the project. The key benefit of creating the Project
Charter is a well-defined project start and boundaries, and a direct way for
senior management to accept and commit to the project._x000D_
Project Charter Contents 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_x000D_
Procedure Define Project Purpose or Project Justification and measurable
Project ObjectivesHigh-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
_x000D_
The Project Management Plan is the document that describes how the
project will be executed, monitored and controlled. It integrates and
consolidates all subsidiary plans and baselines from the planning
process._x000D_
Procedures Establish Scope Baseline Establish Schedule Baseline
Establish Cost BaselineEstablish 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
_x000D_
Project Governance is an oversight function that is critical to the success of
the project. It provides the project manager(s) with a framework for
consistently managing and controlling the project which includes tools for
decision making, role definition, responsibilities, accountability and the
alignment of stakeholders around the purpose of the project.
_x000D_
The purpose of this task is to determine the structure and composition of
the team and to ensure that roles and responsibilities are clearly defined.
The assignment of people to roles should also take into account their
qualifications and availability for the entire whole project time
frame._x000D_
The following roles are important for your SAP S/4HANA project: Project
manager Solution architect Organizational change manager Test manager
Business process owners / experts UX lead Integration lead Technical
lead / Basis expert Development resources Solution experts /
Consultants for Finance, Supply Chain plus the application areas you are
going to implement / change Enablement / Training expert_x000D_
See also SAP Blog - Essential Roles for S/4HANA Fiori Projects.
_x000D_
The purpose of this task is to define the organizational structure of the
project team.
_x000D_
The purpose of this deliverable is to review the project management plan
and the subsidiary plans on the basis of the project scope defined in the
project charter.
_x000D_
The purpose of this deliverable is to properly plan the project to guide both
project execution and project control.
_x000D_
The purpose of this task is to prepare the scope document with the pre-
defined content according to the Statement of Work (SOW) and solution
documentation.The project scope statement evolves through the initiation
and planning of the project and clearly and explicitly defines the deliverables
of the proposed project. This information and supporting documents align
key stakeholders around what the project is going to deliver.
_x000D_
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 to complete the project by the project team. 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 activities / tasks
_x000D_
The purpose of this task is to create a project schedule. The detailed project
schedule defines the work to be performed, the resources and associated
time commitments required for the project, and the individual phases of the
project. The work breakdown structure (WBS) serves as the foundation for
the project schedule and deliverables to be produced as part of the
project._x000D_
Procedures: Define Activities Sequence Activities Estimate Activity
Resources Estimate Activity Durations Develop Schedule
_x000D_
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._x000D_
Procedures: Estimate costs Determine Budget
_x000D_
The purpose of this task is to identify the standards of the project and how
the quality will be managed and valided throughout the implementiation of
the project.
_x000D_
The purpose of this task is plan the commincation Management plan and
define the communication requirements for the project.
_x000D_
The purpose of this task is to plan and define the project risks. _x000D_
Procedures: Identify Risks Assess Risks : Estimating and Evaluating Risk
Create Risk Register ( refer to the "Risk Register Template" provided )Define
Risk Responses
_x000D_
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.
_x000D_
The purpose of this task is to plan the appropriate management strategies to
identify and engage stakeholders.
_x000D_
The purpose of this deliverable is to kick-off the project and ensure that all
required information is shared with the project team resources, key
stakeholders, and anybody involved in the project. The goal of the kickoff
meeting is to ensure that everybody involved in the project understands the
goals and objectives of the project, as well as the schedule that the project
team will follow, which is one of the key ingredients for a successful project
execution._x000D_
_x000D_
The purpose of this task is to prepare the kick-off meeting which will help
ensure the involvement of the team and other key resources and their
commitment to the project schedule.
_x000D_
The purpose of this task is to schedule and prepare the project kick-off
meeting. The kick-off meeting includes discussion of project objectives,
organizational structure, roles and responsibilities, project governance,
schedule, scope, communication standards, change request process, and
decision-making process. The kick-off meeting is attended by the project
team, key stakeholders, project sponsor and company executives. Some
resources may attend the kick-off meeting remotely. In such cases it is
important to ensure good audio and video infrastructure so the remote
participants can take full part in the kickoff meeting session. Use the
attached accelerator as a template to prepare kick-off meeting materials
specific to your project
_x000D_
The purpose of this activity is to prepare the onboarding package for
external consultants from SAP and partner companies.
_x000D_
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._x000D_
The on-boarding package typically contains the following 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.
_x000D_
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._x000D_
_x000D_
The purpose of this task is to identify, define, approve, and communicate
standards related to project execution. Project standards provide a
consistent means of executing and governing project work in an efficient and
effective manner._x000D_
Project standards are elaborated throughout the Prepare phase (some may
be fine-tuned in a later stage of the project)._x000D_
Procedure: Establish, at minimum, the project standards for the following
areas: Requirements Management Business Process
Modeling Solution Configuration and Documentation Custom
Code / Development Authorizations / Security Test Planning and
Execution Change and Release Management Post-
implementation Support and Operations. Define, approve, and
communicate foundational project standards to the project team. Include
project communication standards in project on-boarding for project team
members. Manage changes in accordance with the integrated change
control procedure.
_x000D_
The purpose of the Operational Standards task 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 that
are related to the project standards should be taken into account when
defining the most suitable standards for the project._x000D_
Determine Solution Documentation Procedure_x000D_
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._x000D_
Determine Solution Implementation Procedure_x000D_
v_x000D_
Determine Template Management Procedure_x000D_
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._x000D_
Determine Test Management Procedure_x000D_
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._x000D_
Determine Change Control Management Procedure_x000D_
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 the solution and minimized risk through
segregation of duties and transparency of changes._x000D_
Determine Application Incident Management Procedure_x000D_
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
_x000D_
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 the following: Ready for
Build (e.g. backlog item has a 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)_x000D_
Note that definition of Ready for one step in the implementation process ==
definition of Done from the previous step. Using clear definition of Ready
and Done is critical for SCRUM based implementations.
_x000D_
SAP Solution Manager supports heterogeneous system environments. Its
functions cover all aspects of implementation, deployment, operation, and
continuous improvement of solutions. As a centralized, robust solution, SAP
Solution Manager combines tools, content, and direct access to SAP, to
increase the reliability of solutions and lower total cost of ownership. SAP
Solution Manager is the pivotal hub for collaboration in the ecosystem, as it
empowers communication between all the stakeholders in a solution,
including project teams, SAP partners, consulting and SAP Active Global
Support. SAP recommends customers to utilize the pre-configured
environment for SAP Solution Manager Focused Build that will provide
ready-to-run SAP Solution Manager environment. Alternatively, the customer
may decide to install and setup the SAP Solution Manager following the
installation guide, that provides step-by-step process for installation and
setup of SAP Solution Manager. The general sequence for the
implementation of an SAP Solution Manager system is as follows: You plan
the implementation (such as scope, hardware and software requirements,
release restrictions). You plan the system landscape for your use cases. You
install the components of your SAP Solution Manager system. You configure
your system. You set up the connection to the managed systems._x000D_
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 Project
Management and Requirements_x000D_
and activities scheduled to include the set up of: Test Management Change
Control Management Application Operations_x000D_
Please ensure the following has been completed by the technical team:
customer specific access roles have been created access roles created to
provide digital signature approvals to documents 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 SAP
Solution Manager and there is an appropriate schedule of project team
training for each project phase / key activity using SAP Solution Manager.
the procedure for requesting access to SAP Solution Manager and other
_x000D_
The objective of this task is to setup a physical project team environment
and ensure that the project team members have appropriate level of access
to the customer facility, project room and the project systems. This activity
also involves the setup of project team work stations/computers and/or
mobile devices (as necessary for the project support). The project manager
together with the technical team works on setup of the following (the
questions in each area are geared to help provide guidance):_x000D_
Project Equipment Is there a requirement for hardware (e.g.
servers,laptops, etc.)? Are there any additional software licenses required?
Are the software licenses purchased? Was the software installed for
the project team members? Is there an area planned for the project
equipment? Is there project equipment located in different geographical
sites? Is there any computer lab required for the project?_x000D_
Physical Project Environment 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?_x000D_
IT Infrastructure and Access Is the LAN access available to the Project
Team? Has the LAN access been tested? Do the Project Team Members
have the necessary printer drivers installed? Has IT access been granted for
the following: E-mail servers Internet access, Intranet
access Team collaboration space like SAP Jam MS-Office
Project team specific applications like modeling tool, test management
tools, etc. _x000D_
Customer Policies Is there a specific project policy applicable
(communication, confidentiality, back-up, etc.)? Has the project policy
been communicated?_x000D_
Physical Security Has all necessary access been granted in different project
sites? Have all sites policies been communicated (e.g.security, safety,
emergency exits, etc.)?_x000D_
Telephone/Voice Mail Is there a telephone number issued to project team
members? Has the Project Team Member been told how to set-up the
voice mail? Is there a central phone book for the project team members?
_x000D_
Project
_x000D_Team Member Equipment Is the required equipment (computer,
SAP customers are advised to set up remote access to SAP Support to ensure
timely response to incidents and support tickets. Set up remote access so
that support can quickly diagnose and solve incidents you report, without
needing to be at your desk or on the phone. This is especially helpful when
dealing with different time zones. In addition to solving your incidents faster,
setting up a remote connection between your company and SAP will also
allow you to receive services, such as Early Watch, and Continuous Quality
Checks, that you may be entitled to through the Support Programs your
company has purchased. Follow the guidance on SAP Support Portal linked
from the accelerators page to setup the remote access.
_x000D_
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._x000D_
Tasks Direct and Manage Project Execution Monitor and Control
Project Activities Manage Issues, Risks and Changes Communicate Status
and Progress to Project Stakeholders
_x000D_
The purpose of this activity is to ensure that the project is executed
according to what was agreed to in the project charter, scope statement and
project management plan.
_x000D_
The purpose of this activity is to ensure that resources are assigned to all
scheduled project activities (and tasks) and that work is progressing, and
deliverables are produced as expected.
_x000D_
The purpose of this activity is to capture and manage project issues, risks
and changes related to changes of project scope, timelines, costs etc.
_x000D_
The purpose of this activity to make sure that project stakeholders are aware
of the status and progress of the project including potential disturbances
due to existing risks and issues.
_x000D_
The purpose of this deliverable is to present an overview of all planned
change management activities. It guarantees that all activities are related to
each other as well as to the overall project plan and ensures the
"checkability" of OCM activities.Tasks Prepare Organizational Change
Management Roadmap Conduct OCM Workshop with project manager
and all Project Workstreams Owners.
_x000D_
The purpose of this activity is to collect all required input for the OCM
roadmap and document it in a format suitable for communication and
inclusion into the project management plan.
_x000D_
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.
_x000D_
The purpose of the phase closure and sign-off deliverable is to: _x000D_
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
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.
_x000D_
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._x000D_
Procedure: Review the QGate Checklist Concept SAP Activate accelerator
to ensure an understanding on what should be covered during the Quality
Gate. Areas covered should include: Specifically checking
deliverables been completed with recommended practices Assuring
project planning Validating open risks and issues, and measuring
customer satisfaction Conduct the Quality Gate utilizing the
Quality Gate Scorecard Template accelerator._x000D_
_x000D_
Procedure Note(s): New additional key deliverables need to be added in
the quality gate checklist by the project manager to the different project
types.
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.
_x000D_
The purpose of this task is to ensure that all required deliverables from this
phase and the project are complete and accurate, and close any outstanding
issues. The project manager should identify lessons learned during the phase
to prepare for formal project closure and capture customer feedback and
potential customer references._x000D_
Procedure: Identify and list all key deliverables from phase delivery.
Confirm status of completion and any outstanding actions. Provide signoff
document to signatory. Obtain phase signoff and agreement for any
possible outstanding actions._x000D_
When sign-off is obtained, the project can proceed to the next phase. Use
the Phase Signoff Template accelerator for this task.
_x000D_
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. The activities of the Explore phase are displayed in the following
figure._x000D_
_x000D_
_x000D_
Figure: Activities in the Explore phase_x000D_
In the Solution Adoption work stream, the training strategy for the end users
is developed according to the functional design._x000D_
In the Application design and configuration work stream, the results from
the SAP S/4HANA Value & Implementation Strategy will feed into the fit /
gap analysis and delta design workshops (per business priority in scope). Gap
validation and a final design review support this activity which is usually
executed in an agile manner. Additional SAP S/4HANA applications, like the
setup of Central Finance in a selective data transition, or the setup of an SAP
Digital Boardroom, are planned in this phase as well. In this step, the
detailed security status overview is to be planned. The SAP S/4HANA specific
security strategy and high-level road map is to be defined._x000D_
In the Data Management work stream, data load from source systems needs
to be prepared and planned (new implementation and selective data
transition only). Data volume management is either created or updated
according to new options and requirements coming with SAP
S/4HANA._x000D_
The conversion to SAP S/4HANA may impact your custom code. A first list of
impacted custom objects has been identified in the SAP Readiness Check for
SAP S/4HANA. In the Extensibility work stream, you will need to identify and
prioritize affected custom objects that are used productively, and that must
be adjusted as part of the system conversion project._x000D_
In the Integration work stream, integration design work starts in proper
alignment with the to-be application design, to properly integrate the SAP
S/4HANA system in the solution landscape. First basic integration setup
activities are performed for the sandbox (if required) and for the
development system._x000D_
Based on the anticipated application changes customers should also start
creating a strategy for testing and end user training (Testing work
stream)._x000D_
The technical design document is created in the Technical Architecture &
_x000D_
The purpose of the phase initiation deliverable is to formally recognize that a
new project phase starts.
_x000D_
The purpose of this task is to review all Deliverables of the Explore Phase
with the Customer.
_x000D_
The purpose of this task is to review the acceptance criteria with the
Customer.
_x000D_
The purpose of this task is to review the RACI Chart for the Explore Phase
with the Customer.
_x000D_
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._x000D_
This activity is required for all activities. It is based on an initial assessment
processed in the Prepare phase of the project (see activityTransition
Planning)._x000D_
The project team has been enabled already, and is not in scope of this
activity._x000D_
Procedure Develop a Training Concept_x000D_
Results_x000D_
A training concept has been developed for key users and end users.
_x000D_
The objective of this task is to develop a training concept for key users and
end users based on planned applications, existing skills levels, knowledge
gaps, and locations of training requirements._x000D_
Procedure_x000D_
A first assessment on training requirements has been performed in the
Prepare phase of the project (see activity Transition Planning, task Run a first
Assessment on Training Requirements for details). This task should further
refine this assessment and develop a training concept for key users and end
users on top._x000D_
Proceed as follows: Further re-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._x000D_
Please keep in mind: Skill levels, knowledge gaps, and training
requirements could depend on the location of end users. Special care
needs to be taken for key users: Key users are often involved in
various implementation activities throughout the project (e.g. testing the
newly implemented functionality). Therefore, they need to be trained early.
Key users could potentially support and run in end-user trainings.
After Go-Live, key users play an important role in customer’s
incident management process. In case of issues or questions, end users can
contact their local key users first, before filing an incident. _x000D_
SAP recommends establishing a network of well-trained key users as part of
the transition project._x000D_
Results_x000D_
A training concept has been developed and documented._x000D_
SAP can support this task with the “Enablement Analysis” service
component as part of the “Build Design” service. The service component can
address three aspects: Enablement Concept_x000D_
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,
_x000D_
The purpose of this activity is to ensure that a functional system is available
to be used for demonstration and visualization purposes during fit gap
sessions. This is an essential part of the overall implementation strategy as
this is the foundation to start with a pre-configured solution already during
the explore phase._x000D_
The scope for the activation should be reconfirmed, based on the results out
of the discovery and preparation phase._x000D_
For new implementations, the activation of the best-practice content, or the
implementation of an SAP Model Company (see task Define Cutover
Approach in the Prepare phase) will be provided. For system conversions,
the provisioning of the sandbox system is in scope. This is the baseline for
exploring the solution functionality that has been included in scope and for
confirming that the business needs are addressed. Activated content will be
presented during fit-gap sessions per solution capability in order to
determine relevant deltas so that the solution matches the business
needs._x000D_
This activity is required for all scenarios._x000D_
Precondition is that the technical SANDBOX system has been set up already
but without further configuration -; see activity Sandbox System Setup /
Conversion in this phase._x000D_
If not already done in the Project Delivery Platform Setup activity (Explore
phase), SAP recommends to install or update SAP Solution Manager to the
latest version. This includes: The technical installation of SAP Solution
Manager on one client The implementation of the technical baseline of SAP
Solution Manager to use basic functions: Connection of SAP Solution
Manager using the Managed Systems Configuration Wizard to the three-
system landscape Connection of the three-system landscape to the
Monitoring and Alerting Infrastructure (MAI)_x000D_
Setup of basic functions like Early watch Alert, Diagnostics and the
collaboration platform with SAP._x000D_
Procedure _x000D_
The procedure differs depending on your scenario: In case of a system
conversion, mandatory system preparation needs to be finalized. In case
of a new implementation, the activation scope should be reconfirmed.
Content activation should happen accordingly. Either way, make sure that
SAP Fiori is properly configured in the sandbox. For all scenarios you may
_x000D_
In case of a system conversion it might be required to run post-conversion
activities e.g. in the finance area._x000D_
Procedure_x000D_
Run post-conversion activities according to the Conversion guide, depending
on the functional area in scope. Typical post-conversion activities are posting
activities in MM or customizing and data migration activities in FI-AA.
Properly document your activities in the conversion cookbook (see activity
Sandbox System Setup / Conversion in this project phase)._x000D_
A relevance analysis for Fiori apps based on the usage of the existing system
allows a first UI scoping. Using a list of transaction codes uploaded to the
SAP Fiori apps reference library, the “Relevance and Readiness Analysis”
(open the SAP Fiori App Reference Library and click on “Learn more” on the
left side of the screen; see accelerator section) provides a list of SAP Fiori
apps that fit the business processes in scope._x000D_
The Fiori apps must be installed separately. The whole installation process
can be simplified by using the SAP Maintenance Planner. More details are
given in the activity UX Activation and Design._x000D_
All app-specific prerequisites need to be available according to the
information in the Fiori App Reference Library before carrying out the
following; Creating Fiori Users Connecting SAP Gateway to SAP S/4
HANA SystemConfiguring SAP Web Dispatcher (Fact sheets only) Setting
up the Fiori Launchpad and Launchpad Designer Generic Configuration for
Fact Sheet Generic Configuration for Analytical App Review basic security
set-up and configuration._x000D_
Note that some of the configuration differs between an embedded
landscape (backend and frontend in the same machine) and a Central Hub
set-up (having frontend and backend separated). SAP recommends a Central
Hub deployment._x000D_
In case the sandbox has been derived from the production system it is also
recommended to run the data consistency check reports listed in the
Conversion guide, to identify data inconsistencies which need to be tackled
in production.Please also see the lessons-learned document on finance in
the accelerator section for more details_x000D_
SAP supports this activity with the “Mandatory Preparation for System
Conversion” service component-; see the description of services and service
components
_x000D_ in the accelerator section._x000D_
In this task the business process scope of the sandbox system is reconfirmed,
to avoid a mismatch in process configuration._x000D_
Procedure_x000D_
Based on the results of the discovery and preparation phase, the best
practices scope must be confirmed, as this will be the baseline for the
relevant content structure of the project and the activation of the respective
best practices. In case of best practices content from SAP Activate, please
look up the individual scope items in the SAP Best Practices Explorer.
Alternatively, study the best practices content of SAP Activate in SAP Solution
Manager 7.2 after successful import. In case you take use of an SAP
Model Company, see the detailed process description which is part of the
package.
_x000D_
The objective of this task is to activate / validate the Best Practices
configuration._x000D_
Procedure_x000D_
The general activation procedures have been already described in the
activity Sandbox System Setup / Conversion in this phase. In case of using
an SAP S/4HANA fully-activated software appliance (either in cloud, or on-
premise), the sandbox is already preconfigured. The appliance comes with
four clients: 100: Trial & exploration client (merged-000-client) 200: Best
Practices ready-to-activate client (white list) 300: Best Practices fully-
activated reference client (white list)400 Best Practices fully activated
reference client (merged-000-client **) Either you can use one of the fully
activated clients 300 or 400 -; in this case there is no additional activation
required -; or you start from client 200, and selectively activate the best
practice content depending on your functional scope, by using the Solution
Builder. In case you have installed a fresh SAP S/4HANA system, you will
need to import the newest best practice content (if not already done as part
of the activity Sandbox System Setup / Conversion), and select and activate
the content based on your functional scope, by using the Solution Builder.
See the Administration Guide for details. Please note, that in this case, the
Fiori apps have to be installed separately. The whole installation process can
be simplified using the SAP Maintenance Planner. The Maintenance Planner
helps to plan the installation and to easily generate and download a
consolidated “stack.xml”. In case you are using an SAP Model Company,
the technical activation of the SAP Model Company is explained in a
handover workshop which is part of the SAP Model Company package. The
procedures differ per SAP Model Company. Please look at the info sheets you
will find for all Model Companies on the landing page at SAP.com
(accelerator section)._x000D_
In case SAP Activate can be used, SAP supports this activity with the
“Activate Solution” service component._x000D_
In case of an SAP Model Company, content activation and hand-over is part
of the SAP Model Company package. SAP Value Assurance and SAP Model
Company nicely fit to each other. The service component “Activate SAP
Model Company” is a placeholder which links to the individual SAP Model
Company. See accelerator section for details.
_x000D_
To be able to design cross-system business processes later in fit / gap
workshops it might be required to integrate your newly created sandbox
with other test systems (SAP / Non-SAP)._x000D_
In case your sandbox has been created from a copy of production, it is
important to adjust integration settings, to not integrate with other
productive systems._x000D_
This task is recommended for all scenarios._x000D_
In order to be able to conduct the setup properly, the integration was scoped
(i.e. in form of a system & solution architecture with interfaces, and a
mapping of functional requirements onto SAP solutions) and planned within
the Prepare phase of the transition project._x000D_
The corresponding bordering test systems are available._x000D_
Procedure_x000D_
The following picture displays the integration in general for cloud and on-
premise, between applications, business partners, real world objects, and
end users._x000D_
[image3.4.10]_x000D_
Figure: Integration of SAP S/4HANA with other components of the solution
landscape_x000D_
This task focuses on the standard integration (blue arrows) of SAP S/4HANA
on-premise with other test systems / components._x000D_
Implement the integration with the bordering test systems as described in
the accelerators: Setup B2B Integration Setup A2A Integration (On-Premise
& Cloud) Setup Solution Manager Integration Setup Output Management
Setup User Interface (UI) Integration Setup Internet of Things (IoT)
Integration_x000D_
Results_x000D_
Your sandbox is properly integrated with test bordering systems, and ready
to support fit / gap._x000D_
To assess the existing integration setup, The “Integration Assessment (INA)”
service component explains the central interface register concept in SAP
Solution Manager 7.2 to customers. It supports the setup process and helps
analyzing the conversion impact on interfaces with the help of the interface
register._x000D_
Regarding B2B integration, SAP recommends to use the “B2B Integration
_x000D_
The purpose of Fit-Gap / Delta Design is to validate the predefined scenarios
and enhancements in scope for implementation (based on the sandbox; see
activity Activate Solution), and identify potential gaps between the delivered
product and customer’s requirements._x000D_
Three significant steps will be the baseline for the deliverablesout of the
activity Fit-Gap / Delta Design: Fit Gap Analysis / Solution ValidationGAP
Validation Delta Design / Solution Design_x000D_
The following figure shows the Fip-Gap activities for a new implementation.
For conversion scenarios, the sequence of steps is the same -; however, the
ain of certain steps differ. For instance, step #6 -; Delta Design -; also
documents the configuration “must-do’s” which need to be performed due
to the business processes which are already in use in the source system.
_x000D_
_x000D_
Figure: Individual activities of Fit Gap / Delta Design_x000D_
Key objective of this phase is to gather all relevant information to be
sufficiently prepared to move ahead with configuration afterwards._x000D_
Procedure_x000D_
Fit-Gap / Delta Design is a “summary node” in the road map figure. It splits
into the following activities according to the sequence given in the figure
above: Fit-Gap / Delta Design - Finalize System Setup Fit-Gap / Delta Design
- Fit/Gap Analysis -; Solution Validation Fit-Gap / Delta Design - Gap
Identification Fit-Gap / Delta Design - Delta Scope Prioritization GAP
Validation Fit-Gap / Delta Design - Delta Design Design Review Fit-
Gap / Delta Design - Verify and Accept_x000D_
Steps 1-3 as lined out above include Fiori as an integrated part of the
workshops taking place. Starting with the prioritization (step 4) it becomes a
separate activity with dedicated UX/UI focus. For more details also see
activity UX Activation and Design._x000D_
The workshops are conducted, depending on the customer’s selected
application scope. The recommendation is to structure the solution
validation workshops along the Line of Business areas and End-to End
Solutions. The Line of Business (LoB) areas are structured into: Asset
Management Commerce Finance Human Resources Manufacturing
Marketing
_x000D_ R&D / Engineering Sales Services Sourcing and
The purpose of this activitiy is to finalize the system setup in the SANDBOX
environment.The project team together with key business users will
determine which user stories will be implemented in the sandbox and which
ones will be visualized. The result of this activity is a working system with
functionality that will be used for the following Fit-Gap workshops.
This activity is called “Baseline Build” in the SAP Activate
methodology._x000D_
_x000D_
Procedure Prepare sample data Enhance system setup with additional
configuration_x000D_
_x000D_
Based on the installed sandbox or the activated best practices the focus of
this task is to setup project specific sample data, which will be used during
the Fit GAP Workshops to present project specific data for each relevant line
of business (e.g. Material Master Data, Business Partner Master Data,
etc.)._x000D_
Please note: The accelerator section of the SAP Best Practices Explorer
contains many accelerators like: A list of SAP S/4HANA standard reports
Organizational data overview List of master data objects, e.g. for CO and FI
Account Determination A list of roles delivered with SAP S/4HANA
SAP Best Practice content library The Prerequisites Matrix_x000D_
You need to register to get access to these accelerators (S-User required).
See the accelerator section for a direct link to the SAP S/4HANA Best
Practices within the SAP Best Practices Explorer. You will need to scroll down
within the tool to the accelerator section. Please note that the accelerators
are independent of the chosen localization.
_x000D_
Especially in a new implementation scenario, some process areas might not
fully fit to the expected business scope. Examples for that might be a specific
localization. One of the key aspects of a successful explore phase is to have a
pre-defined and system-based solution available, and to always start the fit
gap workshops with a system based initial setup._x000D_
For those areas, where no Best Practice content is available, relevant
customizing must be enhanced and extended (e.g. by using transaction
SPRO). Input for this task is the detailed scoping document where the
elements need to be marked, which are not covered by Best-Practices. It also
requires clear guidance from scoping and planning, where the level of detail
needs to be pre-configured for the respective areas._x000D_
Procedure_x000D_
For new implementation projects follow the procedures described in the
Administration Guide (accelerator section)._x000D_
For conversion projects you will need to follow the preparation and post-
installation activities documented for instance in the conversion guide.
_x000D_
The aim of this activity is to present and discuss SAP Best Practices processes
and design elements, and to identify gaps which arise from business
requirements. Fit Gap Analysis / Solution Validation is executed via on-site
workshops involving the project team from the respective business
areas._x000D_
Procedure_x000D_
During each solution validation workshop, the target solution will be
presented toward the dedicated key users. For a newly implemented
scenario the following approach could be followed during a solution
validation workshop: Presentation of the process flow diagram out of the
Best Practice Presentation of relevant transactions for each process step
Presentation of the UIs along the process_x000D_
Solution validation workshops for one topic could run in different cycles
(sprints) to detail the solution systematically. The focus is to get key decisions
clarified first (like organizational units or master data concepts) and become
more detailed with each cycle (sprint)._x000D_
The result of the fit-gap analysis will be an initial gap list with an indication
for a potential solution._x000D_
Within each area (e.g. solution capability or Best Practice scope item), the
following requirements need to be initially documented within the delta
backlog: Defined organizational units Defined Master Data Objects,
including e.g. chart of account Defined configuration values based on
business drivers Technical deltas leading into reports, interface, conversion,
enhancements, forms, and workflow (RICEFW) objects Deltas leading to
changes in the UIsBusiness roles assigned to transactions and requirements
for authorizations and training Relevant KPIs for data volume management
and system monitoring Organizational or process changes_x000D_
A critical review of the identified initial backlog follows in the activity GAP
Validation.
_x000D_
The objective of this task is to run the Fit Gap Workshop for your business
priorities, end-to-end solutions, and other functionality to be
implemented._x000D_
Procedure_x000D_
For each Line of Business, end-to-end solution, and application in scope for
implementation, schedule Fit Gap workshops and document the
results._x000D_
The workshop schedule should follow the SAP product road map along with
the respective available Best Practice scope. A complete list of scope items
per end-to-end solution can be found in the “SAP Best Practices for SAP
S/4HANA 1809 - Customer scope presentation” (accelerator
section)._x000D_
Besides the topics specific to the business priorities it is important to define
one area, where general settings that might be even client independent will
be discussed, described and agreed (e.g. factory calendar)._x000D_
The accelerator links lead to the following information for each Best Practice:
General Description of the Best Practice and key process steps Process
Diagram Test script_x000D_
SAP supports this activity with the “Fit Gap Analysis and Delta Design”
service component which follows the 8-step activity sequence listed above.
_x000D_
Gaps identified during the fit gap workshops (see chapter Fit Gap-Analysis –
Solution Validation) often require an initial classification with important
criteria. This initial classification and documentation will be performed by
the responsible lead for the respective area (for example: An organizational
change management issue identified in core finance usually would be
described from the business key user for Core Finance). Requirements and
Constraints_x000D_
This activity is required for all scenarios.Procedure GAP Documentation /
Specification
_x000D_
The goal of this task is to have an initial classified backlog available as input
for the next step (prioritization)._x000D_
Procedure_x000D_
The following aspects should be classified and documented for each gap:
Short and Long Description Reason, what would happen, if this will not be
realized Numbering logic Priority, e.g.: Must have (e.g.
mandatory changes from simplification list) Must have after go-live
(e.g. for the first month end closure) Important but not mandatory
Nice to have Gap Type, e.g.: Configuration
Requirements
Gaps that can be realized leveraging SAP Standard Customizing.
Configuration Gaps will consider the following aspects:
Documentation of the complete organizational structure according to the
enterprise structure Documentation of customizing required to
configure all master data aspects Documentation of customizing
required, which is not pre-configured by SAP Best Practice
WRICEF Gap
All adjustments or extensions on workflows, reports, interfaces,
conversions, enhancements and forms. Those gaps require specific
development knowledge for realizing them. In some projects, a specific
governance / approval procedure is required to approve those types of gaps
as a huge number of those gaps might affect implementation effort as well
as maintenance effort afterwards. Development Gap
Significant new developments for functionality that might not be
available within SAP standard - we recommend to leveraging specific teams
like SAP IBSO to execute those, especially when critical business processes or
real innovations beyond the SAP Standard capabilities are required. UX
Gap
The minimal information required for the UX gaps are the name of
the app (according the naming in the App Library) and a short description of
the detected gap. Organizational Change Management Gap
Ownership Assignment to respective scope item or solution capability
Initial complexity judgment
_x000D_
Before moving ahead specifying the solution within the delta design
documents, it is important to sort out, which gaps are relevant to fulfill the
project objectives, and to perform a dedicated quality review. This is
presented in “Step B” of the figure below which again shows the complete
Fit-Gap / Delta Design procedure._x000D_
_x000D_
Figure: Individual activities of Fit Gap / Delta Design_x000D_
_x000D_
A specific UI session (Deep Dive) needs to be scheduled to further validate
and qualify any Fiori and/or SAP GUI related gaps. The extend and scope of
the session depends upon the UI gaps on the backlog list._x000D_
Procedure Prioritize Delta Scope
_x000D_
Based on the initial backlog and the classification, quality checks are
required with respect to completeness._x000D_
Procedure _x000D_
This step should be performed by a project role that has the overall
customer SAP S/4HANA solution architecture in mind, and a common
understanding of the project objectives (Solution Architect and Project
Management Team). Gaps might be also reviewed critically from that
team._x000D_
Complexity parameters (very high, high, medium, low) can be assigned to
each identified gap, which enables the project management team to get an
initial effort estimate based on T-Shirt sizes._x000D_
The combination of priorities, complexity and other parameters helps to
cluster the gaps into different sprints. In some cases, a governance body, like
a steering committee will be involved for decision making procedure
_x000D_
This activity performs a quality review of identified gaps by a project
independent instance._x000D_
Gaps have been identified and documented before as a result of the Fit Gap
workshops._x000D_
Procedure Validate identified and documented gaps
_x000D_
The objective of this task is the validation of the identified gaps._x000D_
Procedure _x000D_
Validation of gaps should consider the aspect of keeping to the SAP standard
as closely as possible: Manage all deviations from SAP standardKeep the
number of modifications and custom code to a minimum Communicate
with experts at SAP to identify the bestpossible functionality in SAP standard
software for the project and to suggestbest practices and architectural
guidance for custom enhancements. This task can be supported by SAP
IBSO._x000D_
Innovation Control Center_x000D_
During the execution of implementation projects for SAP Premium
Engagement customers, an Innovation Control Center (ICC) focuses on
designing and creating solutions as close to the standard as possible. An
innovation control center is responsible for managing any deviations from
standard SAP software. SAP experts, both on site and at SAP, work together
to show how solutions to perceived functional gaps can be
implemented._x000D_
As part of the “Zero Modification” service available to SAP Premium
Engagement customers, SAP validates all modifications that are required to
fill functional gaps. An ICC uses SAP Solution Manager to evaluate functional
gaps and monitor project status. Specifically, an ICC uses the SAP Solution
Manager functional gap (SMFG) transaction type to collect
requirements._x000D_
The ICC and SAP Global Backbone use SAP Solution Manager to work
seamlessly together. The IT Service Management WebClient UI is enhanced
by an add-on to process the functional gap transaction type, which is based
on the incident transaction type, and dashboards display the relevant
information._x000D_
SAP further supports this activity with the “Gap Validation” service
component. See accelerator section for details.
_x000D_
The purpose of delta design is to detail and document solutions for those
gaps that were identified and prioritized during the fit-gap session. This leads
to finalizing the respective delta design documents in a format suitable for
communication as well as for formal sign-off._x000D_
Procedure_x000D_
For each relevant solution capability (or scope item) the following criteria
should be described in a delta design document:_x000D_
Short description of the process (project and SAP S/4HANA specific)
General business requirements Process flow diagram
Baseline is always the Best Practices process flow chart. Only the
adjustments should be documented in SAP Solution Manager User roles
Requirements for the authorization concept Necessary IT systems,
e.g. interfaced systems to SAP S/4HANA Identification of gaps
Solution for gaps Important customizing Developments
Organizational aspects Process quantification (data volume)_x000D_
For identified gaps regarding critical business processes or Innovations
beyond the SAP Standard capabilities, you can leverage SAP IBSO to fill
them._x000D_
Besides the topics mentioned above, that need to be covered on solution
capability level, it is mandatory to describe general settings, organizational
units and master data requirements._x000D_
The level of detail of each delta design document should be in a way, that
configuration can start based on the description.
_x000D_
The purpose of this task is to continue collecting input and finalize the delta
design document for your business priorities, end-to-end solutions, and
functionality in scope for implementation, in a format suitable for both
communication as well as for formal sign-off purpose. The documented delta
design provides an understanding of the essential processes at the end-to-
end solution (level 2) and provides all requirements on a solution capability
level._x000D_
Procedure _x000D_
The structure of the delta design document depends on the application in
scope for implementation._x000D_
For example, the structure for Core Finance can look like this: E2E
Solution: Accounting and Financial Close General Ledger
Asset Accounting Inventory Accounting ….
Financial Reporting E2E Solution: Cost Management and
Profitability Analysis Cost Management ….
_x000D_
Depending on the complexity of the project, it is recommended to have
individual delta design documents on Level 2 (end-to-end solution). _x000D_
Finalize the delta design documents of your business priorities and
applications in scope for implementation.
_x000D_
This activity performs a quality review of delta design documents from a
project independent instance._x000D_
SAP supports this activity with the “Design Evaluation” service component.
_x000D_
This task performs a quality review of delta design documents from a project
independent instance._x000D_
Procedure _x000D_
The design review should include criteria like: Completeness of design
documents Sufficient quality to start configuration afterwards
Management of solution integration Leverage the SAP standard as closely as
possible: Manage all deviations from SAP standard Keep the
number of modifications and custom code to a minimum
Communicate with experts at SAP to identify the best possible functionality
in SAP standard software for the project and to suggest best practices and
architectural guidance for custom enhancements _x000D_
SAP supports this activity with the “Design Evaluation” service
component._x000D_
In case there is uncertainty on the design of complex processes at net new
or existing customers, or there are concerns on robustness, operability and
sustainability of a process and solution design for a new or already
implemented SAP solution, SAP offers the “Application Architecture
Evaluation” as an additional service component. Industry experienced
solution architects review the core business processes and supporting
master data, identified gaps and planned development requirements. The
solution landscape is analyzed on a high-level including interfaces, data
volume and custom development aspects. The business blueprint is
evaluated, and SAP portfolio alternatives are presented under consideration
of latest product road maps. A final report summarizes the covered areas,
core processes and the SAP recommendations._x000D_
See accelerator section for details._x000D_
_x000D_
The purpose of verify and accept is to obtain a form approval for all created
documents during fit gap / delta design.
_x000D_
The goal of this task is to perform validation and approval sessions._x000D_
Procedure _x000D_
All relevant stakeholders from business and IT departments are signing off
the respective document. With the sign off, all stakeholders agree that
completeness is given and the solution proposals for respective
requirements are understood and accepted. Issues identified during
acceptance need to be documented and classified._x000D_
Based on the approved design documents, the backlog will be updated and
now represents the product backlog for the realization phase. The updated
product backlog is the baseline for the sprint planning for the realization
phase. _x000D_
As this is usually one of the last activities within the explore phase, it is
highly recommended to perform a lessons learned session.
_x000D_
The objective of this activity is to determine the difference between the SAP
standard configuration for Fiori and customer specific requirements._x000D_
A sandbox with standard Fiori configuration will be set-up as the basis for
comparison. A series of workshops allows the identification and validation of
customer specific requirements (”gaps”), hence the deviation from the
standard. Potential solution approaches will be drafted and prioritized as
input for later development._x000D_
Requirements and Constraints Transition planning and phase preparation is
done UX Readiness analysis is done Relevant scope of Fiori is available
from the planning service upfront UX responsible from the customer is
determined Sandbox with SAP S/4HANA is available SAP Solution
Manager 7.2_x000D_
Results Fiori's within scope are activated in the sandbox according to the
SAP standard Gaps and requirements are confirmed and described and
confirmed Topics per gap are determined: Theming / branding,
personalization, adaptation, UI extensibility, new app (HTML5, Screen
Personas) Mock-up of the solution(s) is drafted Prioritization is
established_x000D_
SAP offers the “UX Activation and UX Design” service component which
supports all the activities described in this activity._x000D_
Alternatively, the SAP service “Implementation of User Experience in SAP
S/4HANA” can be used. This service consists of various scope options that
allow tailoring to the required scope. This service also covers the UX
activities that follow the steps described in this activity. It particularly covers
the detailed specification of the UX enhancements and its implementation,
the UX set-up in development, and the move to quality assurance and
production._x000D_
The “UX Advisory Service for Business Value” complements planning and
design activities for User Experience. It also allows to address strategic
aspects related to User Experience._x000D_
It is also highly recommended to make yourself familiar with SAP Fiori, e.g.
by studying the expert SAP Blogs from the Regional Implementation Group
(RIG): SAP Blog “Essential Roles for S/4HANA Fiori Projects” introduces
the roles & associated responsibilities of S/4HANA projects implementing
Fiori user experiences SAP S/4HANA -; How to Create and Generate Backend
Security Authorizations for SAP Fiori 2.0” which provides a step-by-step
_x000D_
The objective of this task is the preparation of the sandbox with Fiori apps to
ensure readiness for Fit / Gap workshops: The sandbox can be based on an
appliance (CAL, BluRay), on an SAP Model Company, or on activation using
SAP Best Practices. For new implementation: Appliance or SAP Model
Company set-up; Fiori check to ensure readiness for workshops System
Conversion: Activation of SAP Best Practices. App-specific configuration for
the in-scope Fiori and setting up Fiori Roles and Users for System
Conversion_x000D_
Procedure (for System Conversion)_x000D_
First of all, become familiar with the Fiori Apps Reference Library, by reading
the SAP blog “How To Explore “Fiori Apps Reference Library” For SAP S/4
HANA Apps” from the SAP RIG team._x000D_
A relevance analysis for Fiori apps based on the usage of the existing system
allows a first UI scoping. Using a list of transaction codes uploaded to the
SAP Fiori apps reference library, the “Relevance and Readiness Analysis”
(open the SAP Fiori App Reference Library, and click on “Learn more” on the
left side of the screen; see accelerator section) provides a list of SAP Fiori
apps that fit the business processes in scope._x000D_
All app-specific prerequisites need to be available according to the
information in the Fiori App Reference Library before carrying out the
following; Creating Fiori Users Connecting SAP Gateway to SAP S/4
HANA SystemConfiguring SAP Web Dispatcher (Fact sheets only) Setting
up the Fiori Launchpad and Launchpad Designer Generic Configuration for
Fact Sheet Generic Configuration for Analytical App Review basic security
set-up and configuration._x000D_
Note that some of the configuration differs between an embedded
landscape (backend and frontend in the same machine) and a Central Hub
set-up (having frontend and backend separated). SAP recommends a Central
Hub deployment._x000D_
Regarding content activation, please look at the blog series Fiori for S/4HANA
-; New Rapid Content Activation on S/4HANA 1809 & 1709.
_x000D_
The following applies to both scenarios, new implementation and system
conversion._x000D_
The objective of this task is: The identification of customer specific
requirements that cannot be solved with an SAP standard configuration for
Fiori. The review of these customer specific UX requirements in more
detail. The drafting of potential solutions (mock-ups). The qualification
and prioritization of the solution. An initial effort estimation for design
and development as a basis for planning and decision making._x000D_
Procedure_x000D_
The Fit Gap / Delta Design Phase is divided into two steps: Fit Gap Analysis
and Solution Validation _x000D_
The Fit-Gap workshops are conducted to validate the predefined scenarios
and processes and to identify deviations from the standard configuration.
The Fiori apps that fit the customer business processes will be selected.
These are not specific UX workshops but generic fit-gap workshops covering
all potential deviations. Delta Design _x000D_
_x000D_
The UX gaps will be validated in specific UX sessions followed by a high-level
solution design. This ensures that the identified gaps get addressed properly
in detail and that the required knowledge is present in the workshops. To
prepare the UX specific validation sessions the following activities need to be
carried if not already done previously. The series of activities
Initial categorizing of the gaps according to complexity Workshops
and/or discussions depending upon complexity Effort estimates for
UX enhancements; definition of enhancements that need additional
evaluation to come up with effort estimates (custom specific development,
effort estimate is not part of this deep-dive session) Capture UI
information in a tool for complex gaps (Build is recommended) For
process/screen optimization: requirements defined, prioritization, initial
high-level effort estimate, low-fidelity mock-ups _x000D_
Additional tasks depending upon the project planning Identification of end-
user roles and their tasks to design the Fiori Launchpad role-based
experience Identification of set-up of tiles (Launchpad Home Page vs.
relegated to the App Finder; grouping, naming, roles) Draft design for
analytical tiles_x000D_
_x000D_
Based on the categorization and defined priorities, design and development
_x000D_
In the security design phase you will create a specific road map for the
security topics that have to be covered during the transition to SAP S/4HANA
according to the customer requirements._x000D_
Requirements and Constraints Mandatory requirements: User
management has to be implemented (see chapter 4 of the SAP Security
Guide, and “Assigning business roles to a user” in the Administration Guides
for details) Authorization management has to be implemented
(authorization management for application users and database users). Look
up the following information: “Creating basic settings for
using SAP Fiori Launchpad” in the Administration Guide
“Creating back-end authorization roles” in the Administration Guide
Chapter 4 of the SAP Security Guide Upgrade of
the authorizations according to the SAP S/4HANA technology (see
“Configuring Roles with Launchpad Start Authorizations” in the SAP Online
Help Portal. Recommended: Redesign of authorization
management Redesign of authorization concept Mitigate risks in
the current concept and implement proper Segregation of Duty (SoD) rules
(GRC) (see “The Segregation of Duties Concept” in the SAP Online Help
Portal) Definition of processes for SAP Auditing, Logging, and
Monitoring (see “Auditing and Logging” in the SAP Online Help Portal)
RFC-Security Service (see SAP Thought Leadership Paper on “Securing
Remote Function Calls” for details) _x000D_
_x000D_
Procedure_x000D_
Planning/Scoping of the activities as prioritized by the customer
(mandatory/recommended/optional) to create a detailed security road map
within the overall transition project._x000D_
Results_x000D_
“Go” or “No-Go” decision for security activities in the scope of the transition
project. In case of “Go”, the result will be a road map that defines the exact
scope of the security design activities._x000D_
SAP supports this activity with the “Security Design” service
component._x000D_
Security Design consists of two parts: The “SU25 Authorization Upgrade”
part executes the mandatory adjustments of existing roles during. It is
required for SAP S/4HANA system conversion and landscape transformation
_x000D_
Define all required security topics concerning infrastructure security,
covering network security, operation system and database security; and
frontend security._x000D_
Requirements and Constraints Required: Define
communication security Plan the implementation of SAP HANA
Security following the SAP HANA Security Guide Define authentication
mechanisms Recommended: Adapt authorizations to
user requirements and roles Plan the implementation of Single Sign-
On Define processes for SAP Auditing, Logging, and Monitoring
Plan security of IT Infrastructure RFC-Security Service;
Gateway Security; Patching Services Sec Notes Advisory; Custom
Code Security Service _x000D_
Procedure _x000D_
Define the security infrastructure that will be setup and configured in the
security implementation activities during the realize phase._x000D_
Results_x000D_
The definition of Security activities in the scope of the S/4HANA conversion
project which will be implemented during the realize phase.
_x000D_
A special case of SAP S/4HANA is the implementation of Central
Finance._x000D_
With Central Finance, customers can transition to SAP S/4HANA Finance, on-
premise edition without disruption to their current system landscape, which
can be made up of a combination of SAP systems of different releases and
accounting approaches and non-SAP systems. Central Finance allows
customers to create a common reporting structure. See accelerator section
for more details._x000D_
This activity is only relevant in case you would like to set up Central Finance
(selective data transition scenario)._x000D_
Procedure Run Central Finance Design
_x000D_
The objective of this task is to design Central Finance._x000D_
SAP helps customers to deep dive into the topic of Central Finance with the
‘Central Finance Design’ service component._x000D_
The following service components are available: _x000D_
Central Finance Overview _x000D_
Discover the innovative features and key benefits of SAP S/4HANA for central
finance foundation and its universal journal. Explore the benefits of a non-
disruptive digital transformation by offering a harmonized common reporting
structure on real-time data across the numerous systems within the
organization. Gain insight into various use cases and implementation options
and learn more about all available central finance capabilities. This service
component complements the “Value and Implementation Strategy” service
component. _x000D_
Central Finance Evaluation _x000D_
The Central Finance Evaluation service enables customers to assess and
examine Central Finance as a potential deployment option for SAP S/4HANA
Finance. Before investing in a proof of value or starting an implementation,
customers can explore and select specific business processes and value
scenarios to address their specific needs and determine how to proceed
regarding the creation of technical design and business case. This service
component complements the “Transition Planning for New Implementation”
service component. _x000D_
Central Finance Design_x000D_
The Central Finance Design service supports preparations for the follow-on
implementation of SAP S/4HANA for central finance foundation. It integrates
the SAP Landscape Transformation Replication Server, the accounting
interface framework, and the connection of source systems to enable real-
time reposting of defined financial transactions into the central finance
instance._x000D_
For detailed information, see accelerator section and talk to your SAP
contact.
_x000D_
The purpose of this activity is to agree on a data volume management
strategy that defines which data is stored in which storage location and for
how long (i.e. defining the residence and retention time). This considers and
includes aspects of the data owners like: External reporting requirements
(tax audits, product liability) Internal reporting requirements, i.e. fraud
detection Business process requirements Data Privacy Dependencies
between data archiving and document management_x000D_
…but also defines more IT-organization related aspects such as:
Operation and Monitoring of data archiving and deletion jobs, i.e. in which
sequence data archiving objects should best be scheduled and related to
other archiving objects Infrastructure, e.g. Content Server to store the
archive files_x000D_
As data avoidance (i.e. deactivating the creation of data by customizing
changes) and data summarization (i.e. aggregating data at higher level) will
only have future effects, in a conversion scenario you should focus on the
following techniques. Data Deletion_x000D_
Deleting out-of-date records from the online database that are no longer
used by the business nor required for legal compliance (e.g. spool data)
Data Archiving_x000D_
Transferring data with a long retention period (e.g. legal compliance, product
liability data, etc.) from the online database to an alternative storage
medium, which provides display access to the transferred data_x000D_
For those customers that have already set up DVM they need to look into
this activity for these reasons: With SAP Simple Finance SAP has introduced
a new concept called Data Aging (see Accelerators section for details) for
finance data replacing the Data Archiving concept in this space. Data Aging
offers you the option of moving large amounts of data from working memory
to disk within SAP HANA to gain more working memory. You use the
relevant SAP application to move data from the current area to the historical
area on disk. You control the move by specifying a “data temperature” for
the data. The move influences the visibility when data is accessed. Due to
the massive change of the FIN data model with SAP Simple Finance reload of
accounting data that has been archived with archiving object FI_DOCUMNT
prior to the conversion is no longer possible after conversion. (See SAP Note
53064 - which clearly states: “Reloading data across releases is generally not
allowed”) Also, existing archiving strategies need to be checked. E.g. in
future, table COEP entries will be saved partly in table ACDOCA and / or in
_x000D_
The objective of this task is to identify data, which could be easily
reorganized or deleted because they are temporary or basis table
data._x000D_
This task is only relevant for system conversion._x000D_
Procedure_x000D_
There is a Guided Self Service available in the DVM Work Center of SAP
Solution Manager to provide detailed analysis of your data and useful
background information on the most commonly growing tables._x000D_
In case the possible quick-win tables have been identified already in the task
DVM Planning, you can run the Guided Self Service specifically focusing on
those manually entered and selected tables._x000D_
Alternatively there is an option to schedule the Guided Self Service
automatically focusing on Basis and temporary tables that could be subject
for archiving or deletion without effecting business processes (i.e. DVM quick
wins)._x000D_
Based on the analysis results and the recommendations, define and agree
with all stakeholders on your own residence time._x000D_
See also SAP note 706478 -; “Preventing Basis tables from increasing
considerably” for options to reduce the size of Basis tables._x000D_
The DVM work center also offers beneficial insights and transparency when
finally executing the archiving and deletion jobs and allows the monitoring
and tracking of success._x000D_
Results_x000D_
There is now transparency on the DVM quick wins of SAP HANA.
_x000D_
Setting up and executing a DVM strategy is often time-consuming. One
reason is that data residence time (i.e. time the data resides on the database
before archiving) and the retention time (i.e. total lifetime of the data before
its destruction) need to be defined based on legal and business
requirements together with the Business Owners from the Lines of
Businesses._x000D_
This task is of particular interest for system conversion._x000D_
Procedure _x000D_
In the context of a system conversion project, SAP recommends to at least
discuss SAP note 2154712 -; “Archive transaction data of deactivated
company codes” to shut down and archive inactive company codes before
conversion starts._x000D_
Results_x000D_
You have started with the execution of a DVM strategy to reduce system size
and required downtime during system conversion._x000D_
SAP offers holistic support to create and execute a DVM strategy. In
particular SAP offers the “Data Volume Design” service component.
Customers can either contact the SAP Technical Quality Manager or Client
Partner for ordering details. Alternatively, customers can use the contact
form to request an SAP Value Assurance service package offer._x000D_
SAP Enterprise Support customers can find information and services on data
volume management in the context of SAP S/4HANA (e.g. CQC Data Volume
Management, Guided self-service) in the “Become competent” section of
the “Explore” learning journey.
_x000D_
Open business documents cannot be archived from the SAP system. To
reveal additional reduction potential, you need to get insights into the
current status of open business documents._x000D_
This task is of particular interest for system conversion._x000D_
Procedure_x000D_
It is difficult to collect the open business documents yourself with acceptable
efforts. SAP recommends ordering a Business Process Analysis service that
provides a snapshot for business metrics._x000D_
Once you have gained transparency on the number of open business
documents, you can start clarifying the status together with the Business
Data Owners from the Lines of Businesses. The aim is to close as many open
business documents as possible, and have them archived before the system
conversion._x000D_
Please note that the Business Process Analysis is a one-time health check
only. For a continuous root cause analysis and improvement of business
processes, Business Process Analytics in SAP Solution Manager can be used.
This tool provides benchmarking, advanced benchmarking, value
benchmarking, age analysis as well as trend reporting. For more information,
please see Accelerator’s section._x000D_
Results_x000D_
You have gained transparency on open business documents._x000D_
SAP offers a Business Process Analysis service that provides a snapshot for
business metrics like: ”Sales orders overdue for delivery“ “Outbound
deliveries overdue for GI posting” “Deliveries overdue for billing” “Open
& overdue items in Accounts Receivables” “Open & overdue purchase
requisitions” “Open & overdue purchase order items” “MM invoices blocked
for payment” “Open & overdue items in Accounts Payable”
“Production/Process orders overdue for deletion flag” “Inbound deliveries
overdue for GR posting”_x000D_
All available metrics are documented in a KPI catalog. For details, see
Accelerator’s section._x000D_
As a much more comprehensive approach, SAP offers a “Business Process
Improvement” service component. The service component typically starts
with a remote Business Process Analysis to learn fact based on the current
status quo, and to have a baseline measurement from where to start the
_x000D_
The objective of this task is to adjust your DVM strategy according to the
new options and requirements of SAP S/4HANA._x000D_
This task is important for all scenarios._x000D_
Procedure_x000D_
Proceed as follows: Inform yourself. The SAP Online Documentation
provides a good introduction into classic data archiving with SAP S/4HANA.
SAP Note 2416490 - FAQ: SAP HANA Data Aging in SAP S/4HANA” gives you a
lot of information on the Data Aging concept, and its impact on DVM as
such. There are already books available on this new topic (e.g. from SAP
Press, see accelerator section). For all available Data Aging objects please
look at the collective SAP note 2315141 -; “Collective note for Data Aging
Framework”. This SAP Note is regularly updated when new information
becomes available. Together with your Data Volume Management head,
and the Business Data Owners, clarify which data should be archived before
the system conversion, and if and how Data Aging should be configured as
part of the conversion. Please also consider the options your SAP S/4HANA
release offers for classical data archiving. As mentioned in the SAP note,
please make sure to properly adapt custom code that accesses archived
data, or in future aged data from the history space._x000D_
Results_x000D_
The DVM strategy has been adjusted with respect to the options and
requirements of SAP S/4HANA._x000D_
SAP supports you with respect to Data Volume Management. In particular
SAP offers the “Define Data Volume Design” service component which is part
of the “Build Design” service.
_x000D_
In this activity the transfer of business data from legacy systems to the newly
implemented SAP S/4HANA system is designed._x000D_
This activity covers both the simple scenario, where standard tools or best
practices concepts are sufficient, and the complex LT scenario._x000D_
This activity is required for new implementation and landscape
transformation scenarios in case data needs to be transferred from legacy
systems._x000D_
Procedure_x000D_
The procedure differs depending on the implementation scenario._x000D_
For new implementations, the procedure during the explore phase is as
follows: Prepare and conduct data migration Assessment Data audit
Prepare and present data migration scope and requirements document
Data migration approach and strategy document Test data management
Define specifications for data migration_x000D_
Look up the SAP Blog “Migrating data to your (new) SAP S/4HANA” to learn
about the ways in which your business data can be migrated to your newly
deployed SAP S/4HANA system (on premise or cloud)._x000D_
For selective data transition scenarios (client transfer, system merge,
company code transfer, and Rapid Data Migration to SAP S/4HANA), the
procedure is as follows: Run a landscape transformation assessment for
the specific scenario together with your LT implementation partner or
SAP_x000D_
Ideally, a first assessment on data migration design has been performed in
the Prepare phase of the project already (e.g. as part of the “Transition
Planning for New Implementation” service component, or as a dedicated
“Data Migration Architecture” assessment; see Transition Planning service
component for more details)._x000D_
Finally, and depending on your scenario it may be required to install
additional data migration software: Landscape transformation software in
case of a selective data transition scenarios Data migration services for
new implementation scenarios
_x000D_
The purpose of this task is to explain the typical SAP data migration
approach and tools available and to understand the customer’s legacy data
systems, business priorities, and technical infrastructure. The outcome
should be a definition of the relevant data objects required in the new
solution in this phase._x000D_
During the Fit/Gap analysis, the project team validated the predefined
scenario provided by the S/4HANA solution. The documented fits and gaps
between out-of-the-box S/4 HANA Best Practices and customer's business
requirements will dictate what kind of data objects will be migrated to the
new system._x000D_
Procedure_x000D_
During the Fit/Gap analysis, the project team validated the predefined
scenario provided by the S/4HANA solution. The documented fits and gaps
between out-of-the-box S/4 HANA Best Practices and customer's business
requirements will dictate what kind of data objects will be migrated to the
new system. Scenario 1a: Fit -; use of SAP S/4HANA Migration Cockpit and
SAP S/4HANA Migration Object Modeler_x000D_
In the SAP S/4HANA Migration Cockpit, templates are available that specify
the relevant data for each migration object. SAP provide templates
(Microsoft Excel XML files) that can be used for each migration object. If a
template does not meet the business requirement (for example if the
relevant Microsoft Excel XML file does not contain all the fields that are
needed for the target structure), the SAP S/4HANA Migration Object
Modeler can be used to adjust the relevant migration object._x000D_
Scenario 1b: Fit -; use of Rapid Data Migration to SAP S/4HANA, on-premise
edition
Rapid Data Migration to SAP S/4HANA, on-premise edition is an SAP Best
Practices package that offers out-of-the-box solution to migrate 40+ data
objects. In the Content Library, the project team members can select from a
list of pre-defined scope options to filter the data objects for their project.
Please note, such a Rapid Data Migration package is designed to load only
limited types of legacy data that are required to support a SAP Rapid Data
Migration to SAP S/4HANA deployment. Please see accelerator section for
details. Scenario 2: Gap
In case the data migration targets on the types of legacy data are not
covered by the Rapid Data Migration package, it is necessary to document
_x000D_
The purpose of the data audit is to identify the legacy systems that will
supply data for the SAP applications and to profile the quality of the legacy
data. Data profiling is the process of analyzing the legacy source data to
detect anomalies and of validating the business rules._x000D_
Procedure _x000D_
In the data audit, the focus is on conducting a high-level summary analysis,
looking for typical problems such as missing data and column names that are
inconsistent with content._x000D_
The data audit involves working with the business users to help map out the
gap between the existing and required levels of data quality._x000D_
The Rapid Data Migration package provides two tools to assist with data
profiling on some master data objects (e.g. customer, vendor, business
partner, etc.):Data Services - provides a basic profiling capabilityInformation
Steward - provides different types of profiling Columns Address Dependency
Redundancy Uniqueness SAP Best Practice_x000D_
Data Quality for Data Migration (listed in accelerator) provides more
details._x000D_
The project team can use below accelerators to capture data profiling
information on all needed data objects whether they are covered by the
Rapid Data Migration package or not._x000D_
SAP offers a “Data Migration Assessment“, where data auditing is discussed.
_x000D_
The purpose of this task is to prepare the data migration scope document,
risk and issue document._x000D_
Procedure_x000D_
The content of this document should be based on findings from the data
migration workshop and data audit. The project team can use below
accelerators as a starting template._x000D_
SAP offers a “Data Migration Assessment“, where major aspects of a data
migration scope and requirements document are discussed. The creation of
the document is not part of the service, but in the responsibility of the
customer or implementation partner.
_x000D_
The purpose of the data migration approach and strategy document is to
capture and communicate the approach and strategy for the legacy data
migration._x000D_
Procedure _x000D_
This deliverable is intended to align all project team members and obtain
customer sign-off on the data migration framework and
methodology._x000D_
Some of the most important parts of this document are listed below.Strategy
and Approach: it describes priorities and timescales of the achievable goals
of data migration Data Assessment: this section builds on top of the data
migration scope and requirements document. It should contain specification
of the data to be migrated and a data dictionary that describes all the details
of the data objects. Data Quality and Cleansing: this part contains an
abstraction of data audit's findings and extend it to capture the appropriate
data cleansing plan ETL Methodology: it describes an iterative four-stage
approach - analyzing the data, extracting and transforming the data,
validating the data, and loading it into targets with testing._x000D_
The Data Migration Strategy and Approach Sample document below is a
good demonstration of how these parts can be laid out._x000D_
migration approach and strategy document are discussed. The creation of
_x000D_
This is part of the data management that focuses on the data to be created
in development and quality assurance systems.Procedure _x000D_
The different characteristics and requirements of the test data should be
weighted, in order to choose the proper method and tool for data creation.
_x000D_
Besides, one should also take into consideration that certain data,
particularly business-critical and personal data, should be kept protected,
before entering it in development and quality assurance systems.
_x000D_
The purpose of this task is to define the specifications (functional, technical)
for data migration (extraction, transformation, validation, load, etc.) for both
automated process and manual process._x000D_
Procedure _x000D_
The overall objective of the automated data migration design is to deliver
clean, load-ready data as input to the standard SAP load utilities. However,
there are cases that the automated programs are not available, or the data
volume does not justify the investment in developing such
programs._x000D_
For example, due to the low data volumes, it is quicker to convert certain
types of master data (bank, cost center, and profit center) through a manual
process. Certain types of transactional data, such as open orders (sales,
service) need to be manually created by running SAP transactions in the
target system. In many cases legacy data may include sensitive or classified
information that requires special handling procedures._x000D_
The project team must identify the data sets, determine the customer’s
security policies and develop a solution that will isolate this information from
the non-secured data sets._x000D_
For automated migrations, the security requirements can be met through
techniques or methods, such as file and database privileges or the
deployment of an isolated migration environment._x000D_
For manual migrations, the recommended solution is to have the business
owners that have access to that data perform the manual migration._x000D_
The end deliverable is a Data Security Design document. The project team
also needs to construct a Testing Strategy document detailing information
such as Test Cycle Definition, Roles and Responsibilities, etc._x000D_
migration approach and strategy document are discussed. The creation of
_x000D_
Changing business requirements continuously drive organizations to realign
and restructure their business. As a consequence, the transformation of SAP
landscapes has become an ongoing business for SAP customers with a
strategic importance to stay agile and competitive. Instead of replacing
legacy environments by using generic or self-made tools and technologies,
SAP customers can use SAP Landscape Transformation as a cost-efficient and
secure alternative. SAP customers can manage their SAP-related
transformation requirements in a holistic manner - reflecting organizational
changes, acquisitions of companies, divestitures, or the harmonization of
processes and data in their existing SAP system landscape._x000D_
The objective of this task is to run a landscape transformation assessment
together with SAP. The scenarios in scope are: Client transfer
Consolidation of several ERP systems into one S/4HANA target system
(System merge) Company code transfer to S/4HANA target systems
Data migrations based on preconfigured objects_x000D_
The “Data Migration Assessment” service component helps customers
during the preparation of the transformation to the SAP S/4HANA
environment, and as such complements the SAP S/4HANA migration options
“New Implementation” and “System Conversion”._x000D_
The Data Migration Assessment service component provides assessments for
the execution of the technical landscape transformation scenarios listed
above (more information provided in the Realize phase of this road map):
_x000D_
Depending on the scenario, additional SAP LT software needs to be
installed._x000D_
The Data Migration Assessment service component has been delivered
already (initial planning part)._x000D_
Procedure _x000D_
Details on what needs to be installed and when, are defined in the activity
Data Migration Design in this phase of the project. Please note that
additional license costs may apply._x000D_
General information on the SAP LT software can be found in the Accelerator’s
section.
_x000D_
In case of a new installation scenario critical master and transactional data
objects like material master, profit center group, business partner and sales
orders, purchase orders, contracts and more need to be transferred from the
legacy system to SAP S/4HANA. If the migration objects are limited to the
available migration objects and no data cleansing/data quality checks are
required, you can use the built-in SAP S/4HANA Migration Cockpit out of the
box. Required changes, for example adding fields, can be managed by the
SAP S/4HANA Migration Object Modeler. For a list of available migration
objects that are supported with SAP S/4HANA 1809, see SAP Help Portal and
search for Migration Cockpit -> Transferring Data to SAP S/4HANA Using Files
or Transferring Data Using Staging Tables -> Available Migration
Objects._x000D_
In all other cases, make use of the Data Migration Services._x000D_
Procedure _x000D_
The rapid data migration to SAP S/4HANA, on-premise edition allows you to
extract and analyze selected data from virtually any source system. By
cleansing, validating, transforming, and migrating your data from any system
to SAP S/4HANA, on-premise edition, you will have high quality legacy data
in your SAP solution._x000D_
See Accelerators section for more information, what additional software
needs to be installed to transfer the data. The RDM package contains
detailed information, and a quick guide which explains installation and
configuration of the required software._x000D_
Please note that additional license costs may apply.
_x000D_
As part of the transition to SAP S/4HANA, customers need to identify code,
that has to be adjusted (“must-do’s”), and those that should be adjusted
(“should-do’s”)._x000D_
This activity is relevant in case own code needs to be made ready for SAP
S/4HANA (e.g. the system conversion case)._x000D_
A first analysis of the custom code situation should have been done in the
Prepare phase already._x000D_
Procedure Empowering on Custom Code Management Tools Create a
Custom Code Work List_x000D_
Results_x000D_
There is a documented work list of custom objects which are subject for
adjustment stored centrally in SAP Solution Manager._x000D_
SAP has published excellent blogs on custom code management in the
context of a system conversion: To learn about the challenge, start with the
SAP Blog “SAP S/4HANA System Conversion -; Challenge for your custom
code”. To understand the necessary adaption process for your custom
code, look at: The SAP Blog “SAP S/4HANA System Conversion -;
Custom code adaptation process” The SAP Blog “ABAP custom code
adaptation for SAP HANA -; The efficient way” What you can (or
better: should) do well upfront of a planned system conversion is
documented in the SAP Blog “What can you do today to prepare your
custom code for SAP S/4HANA”. Finally, there is a blog series describing all
relevant expert tools required for analysis. The first issue is the SAP Blog
“Remote Code Analysis in ATC -; One central check system for multiple
systems on various releases”._x000D_
You will find all links in the accelerator section._x000D_
Customers can order a “Custom Code Impact Analysis” service component
which offers transparency on the existing custom code situation including
customer objects and modifications. It helps to evaluate the impact of
changes on custom code. With the results of the analysis, the adjustments
on custom code can be reviewed and mitigated at an early stage. It helps
customers to reduce efforts for change adoptions and facilitates a smooth
completion of the identified adjustments._x000D_
The “Custom Code Impact Analysis” is also available as an expert-guided
implementation for SAP Enterprise Support customers. See the “Become
_x000D_
The goal of this task is to make you familiar with the tools for custom code
management._x000D_
Procedure _x000D_
Relevant expert tools around custom code management are documented in
a blog series. The first issue is the SAP Blog “Remote Code Analysis in ATC -;
One central check system for multiple systems on various releases” (ATC,
SCI…), and “What can you do today to prepare your custom code for
SAP S/4HANA” (SCMON, SQLM)._x000D_
Read the blogs and make yourself familiar with the tools._x000D_
How to use the expert tools is documented in: The SAP Blog “SAP
S/4HANA System Conversion -; Custom code adaptation process” The SAP
Blog “ABAP custom code adaptation for SAP HANA -; The efficient
way”_x000D_
In case you don’t have an ATC of sufficient release in your landscape, and
don’t have access to a remote ATC running in the cloud: Consider using an AS
ABAP developer edition. Look at the SAP Blog “AS ABAP 752 SP04, developer
edition, to download -; COMING SOON!”, which gives you the option to run
the custom code impact check with a pre-configured ATC on AS ABAP
7.52._x000D_
In addition, there are even more tools and transactions you should be
familiar with: Depending on start release, customers may have to upgrade
your SAP system first, or may have to install some additional EHP’s. In case
customers modified an SAP program, and SAP comes with a new version of
this program as part of the upgrade or EHP, they will need to adjust their
custom code and their modifications. Once customers have done the
upgrade or the EHP installation, they will see all modified objects that need
to be technically adjusted in the transactions SPDD, SPAU or SPAU_ENH.
There are two additional interesting options they should be aware of:
The Upgrade / Change Impact Analysis as part of CDMC is a way to
estimate and manage the technical adjustment effort by comparing systems
before & after upgrade, and analyzing the corresponding objects (e.g.
referred SAP objects in custom code). The Scope and Effort Analyzer
(SEA) in SAP Solution Manager is also estimating the technical adjustment
effort caused by EHP installation, by comparing the custom object and
modified object list with the Technical Bill of Material (TBOM) of an EHP
(thus this is doable in front of the EHP installation), and evaluating the
adjustment costs and effort with information provided by SAP’s backend.
_x000D_
Create a list of custom objects which are candidates for adjustment._x000D_
You are familiar with the SAP tool set on custom code._x000D_
Procedure_x000D_
Use all tools listed in the task before, and create a list of custom objects
which are affected: Modifications affected by upgrade or enhancement
pack installation Custom code affected by the database change to SAP
HANA Custom code affected by the change of the simplified data model
coming with SAP S/4HANA Custom code affected by the simplification of
business processes and applications coming with SAP S/4HANA_x000D_
Analyze all custom objects from the list, and prioritize with respect to
business criticality and urgency._x000D_
Results_x000D_
There is a documented and prioritized list of custom code objects which
need to be adjusted as part of the transition project.This also includes
custom code objects which should be re-implemented on SAP Cloud
Platform (e.g. SAP Fiori UI’s or for integration with other SAP and non-SAP
systems)._x000D_
See Custom Code Impact Analysis service component in the activity
description.
_x000D_
The purpose of the integration design activity is to detail and document all
integration aspects of the project, that have been identified in the Prepare
phase._x000D_
Important topics for the integration design are i.e.: Design of the to-be
system & solution landscape with interfaces (scoped i.e. in the SAP S/4HANA
Transition to New Implementation (TNI) workshop -; see activity Transition
Planning in the Prepare phase for details). All other technical, non-
business priority specific topics._x000D_
This leads to finalizing the respective design document in a format suitable
for communication as well as for formal sign-off._x000D_
This activity is recommended for all scenarios._x000D_
Further requirements: To-be system and solution architecture with interfaces
has been defined and fixed. Interface architecture has been defined as
scope and fixed. All other integration aspects and requirements have been
discussed._x000D_
Procedure_x000D_
The level of detail in integration design specification should be in such a way,
that configuration and development can start based on the description. This
activity should be executed in close cooperation with the Fit Gap / Delta
Design activities of the Application: Design & Configuration work
stream._x000D_
This activity is structured into two tasks: Define Interface Architecture
Prepare Integration Design_x000D_
Results_x000D_
The result is a finalized, reviewed and singed integration design.
_x000D_
SAP and non-SAP systems use interfaces to communicate to other system in
the solution landscape. The interface architecture displays the interfaces and
indicates additional attributes i.e. the used technology (i.e. middleware),
protocol type, frequency- and direction of communication._x000D_
The objective of this task is to prepare a system & solution architecture with
interfaces._x000D_
Prerequisites As a prerequisite, the customer needs to have a clear vision of
the to-be system and solution architecture. An interface register that
represents the current interface scope needs to be defined (see activity
Transition Planning in the Prepare phase)If the interface scope or the system
and solution architecture changes it might be necessary to adapt the
interface architecture._x000D_
Procedure Define initial interface register to fix scope Define to-be
system and solution architecture Create to-be system and solution
architecture with interfaces_x000D_
Results_x000D_
The result of this task is a to-be system and solution architecture with
interfaces, which is referenced in the scope statement._x000D_
SAP supports this activity with the “SAP S/4HANA Transition for New
Implementation (TNI)” service component. The service components provide
a system & solution architecture with interfaces as one of its deliverables.
Please note, that a filled interface register is key to have for integration setup
and design (see also tasks “Prepare Interface Register” and Run a Legacy
Impact Analysis on the Interface Inventory” from the Plan phase of the
project)_x000D_
The SAP S/4HANA Value Assurance service package component “Technical
Architecture & Infrastructure (TAI)”provides as main deliverable a design of a
new -; or review of an already existing -; technical architecture for an SAP
solution.See accelerator section for details.
_x000D_
The purpose of the integration design activity is to detail and document the
different integration aspects, that were identified during the preparation of
the to-be system & solution Landscape with interfaces and the interface
This leads to finalizing the respective design documents in a format suitable
for communication as well as for formal sign-off._x000D_
Prerequisites To-be system and solution architecture with interfaces has
been defined in scope and signed off. Interface architecture has been
defined in scope and signed off._x000D_
Procedure_x000D_
For each relevant integration aspect, the following criteria should be
described in one overall integration delta design document:Short description
of the integration aspect (project and SAP S/4HANA specific) General
business requirements (i.e. frequency of replication, required fields)
Necessary IT systems e.g. interfaced systems to SAP S/4HANA
Identification of integration gaps (i.e. reference to gap backlog) Solution for
gaps (used middleware, field mapping, required configuration, used best
practices) Important customizing Developments Organizational
aspects Process quantification (e.g. expected data volume)_x000D_
The level of detail of each integration design document should be in a way,
that configuration can start based on the description._x000D_
Results_x000D_
The result is a finalized, reviewed and signed integration design._x000D_
SAP supports this activity with the “SAP Interface Management” service
component. The SAP Interface Management service component analyzes
and optimizes the design, configuration, and operation of interfaces that are
essential to your core business processes. The analysis of the interface
design and configuration in the context of a core business process is also
covered by the SAP Value Assurance service component “Integration
Validation”._x000D_
SAP supports this activity with the “SAP S/4HANA Transition to New
Implementation (TNI)” service component. The creation or review of the to-
be system & solution architecture with Interfaces is part of this service
component. This service component includes the determination of the
interface scope._x000D_
You should also look up the SAP API Business Hub where you can discover
_x000D_
Within the Analytics Design activity customers can further enhance their
analytics infrastructure with regards to new reporting options that have been
introduced with SAP S/4HANA. New operational reporting methods can be
added to the existing analytics solutions, and data from SAP S/4HANA can be
provisioned to existing Enterprise Data Warehouses for further analysis. All
available SAP analytics solutions should be discussed for strategic and
business value._x000D_
This activity follows up and integrate with the “Define the Analytics
Architecture” task from the Discover Phase of the road map, with the
objective to provide a more detailed analysis of the most important analytics
business cases and further detail out the target analytics architecture and
define a transition project plan._x000D_
This activity is optional, but highly recommended. If you could not take the
opportunity to review your company’s analytics strategy in the discovery
phase of the road map, you can start it here or alternatively evaluate and
plan the identified options in more detail.
_x000D_
Procedure_x000D_
Please refer to the task “Define the Analytics Architecture” (activity
"Strategic Planning" in the discover phase) for information about the
procedure. This activity will be similar in terms of procedure and content,
however it will focus only on the relevant solution components (potentially
identified in the earlier activity) and create a more concrete target
architecture and migration path based on the most important analytic
business processes, requirements and influencing factors, such as: Real-time
reporting, data retention policies, data governance and ownership, new
technologies and options_x000D_
Please check the Accelerators section for further information about SAP’s
roadmaps for the strategic solutions and details about the product options,
especially: SAP S/4HANA Embedded Analytics SAP BW/4HANA and SAP
BW SAP Analytics Cloud and Digital Boardroom SAP BusinessObjects BI
Suite_x000D_
See also the tasks for designing analytics architecture (recommended), and
designing a SAP Digital Boardroom (optional).
_x000D_
The objective of this task is to fine-tune the analytics architecture._x000D_
To support the analytics design activity, SAP offers an “Analytics Design
Workshop”: As a follow-up or deep dive on the “Analytics Strategy Service”,
this service component should help define the actual implementation
aspects for the analytics infrastructure, depending on what components for
analytics will be used. The service component provides guidance for SAP
BW/Mixed/HANA modelling. It identifies the ideal choice for data modeling
in an SAP Enterprise Data Warehouse (BW / HANA), which is either SAP BW-
centric, mixed or SAP HANA centric. The decision is based on the customer
infrastructure (e.g. data sources, or ETL tools etc.), and business
requirements (e.g. with respect to real time). The service component
empowers on the practical use of CDS views in SAP S/4HANA. Prototyping
can be provided for reporting applications for analytical Fiori apps, or SAP
S/4HANA Embedded Analytics. The service component provides guidance
on embedded BW usage, and how LSA++ should be applied to the customer
EDW model in SAP S/4HANA (for both, SAP BW and HANA native)._x000D_
_x000D_
_x000D_
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._x000D_
The following key elements of the test planning must be documented in the
test strategy: Project Testing Objectives & Assumptions, e.g.
Unit Testing is only required for delta functionality Unit Testing is
complete before Integration Testing Test Scope Types of Testing,
e.g. Unit Testing Business Process (String) Testing
Integration testing Data Conversion Testing User Acceptance
Testing Testing Approach 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 Testing Deliverables, e.g. Test
processes per phase, test environment, test tools Test Automation
Testing Tools Which tools will be used to perform different
tests (e.g. SAP Solution Manager) Defect Management
Description of how defects will be documented (e.g. Test Workbench in
SAP Solution Manager) Roles and Responsibilities
Description of required test roles and responsibilities, e.g. Test Lead and
responsibilities of individual project team members related to testing
This activity is required for all scenarios.Procedure Make yourself
Familiar with the Tools in Test Management, and Set Up Test Management in
SAP Solution Manager Test Scope Determination Detailed Test PlanningHow
SAP Can Support_x000D_
SAP's strategy for test management is guided by establishing SAP Solution
Manager as the central platform for E2E process testing. SAP Solution
Manager delivers all major functions to handle all aspects of test
management for SAP-centric solutions. This can be using either its own tools
or those of integrated partner solutions. SAP’s Support Standard for Test
Management describes tools and scenarios in Test Management with SAP
Solution
_x000D_Manager._x000D_
The goal of this task is to make you familiar with the test tools in SAP
Solution Manager, and their setup._x000D_
SAP Enterprise Support customers can find a lot of information and services
on the SAP Test Suite in SAP Solution Manager, and how to create and
execute test cases in the “Become competent” section of the “Realize”
learning journey.
_x000D_
The scope of testing for a project, regardless if the project is executed
independently or as part of a release, needs to be determined early in order
to ensure the testing environments and materials are available for execution.
With such a variety of testing cycles (e.g. integration, regression,
performance, cutover, user acceptance, etc.) available, it is important to
define the cycles that are required to support the planned conversion
event._x000D_
The prerequisite is here that the test and quality management processes and
procedures are already in place._x000D_
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. The results from the
Delta Design activity serve as the input. 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. With the scope of the
transition project, it’s important to identify test cases and scripts related to
the financial solution, however it’s also important not to neglect or
underestimate the testing requirements in other parts of the solution. This
holds true especially with the migration from any DB to SAP HANA and/or
the inclusion of changes to the software levels. 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_x000D_
_x000D_
Results_x000D_
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.
_x000D_
Scoping and planning the tests required for the transition project is a
requirement regardless if the project is executed as a “pure” technical
conversion, or as a combined conversion project with the enablement of
new functionality, or as a new implementation project._x000D_
The focus is to determine which of the required 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._x000D_
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. 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.
_x000D_
The purpose of this activity is to technically set up a sandbox environment.
The sandbox is later on finalized by functional experts (see activity Activate
Solution) to serve for Fit/Gap activities. The procedure to create a sandbox
depends on the scenario._x000D_
Procedure Set Up SANDBOX (System Conversion scenario only)
Downtime Optimization Preparation (System Conversion scenario
only)_x000D_
or Set Up SANDBOX (New Installation scenario only)_x000D_
Please note: Before converting an SAP system, or installing a fresh one, you
will need to download SAP software from SAP Service Marketplace. The
planning of such a change event is done in the Maintenance Planner. After
entering the required data, the Maintenance Planner fills your download
basket, and creates a control file (“stack-xml”), which is later on required for
the conversion and installation tools. The Maintenance Planner has been
described in the activity Transition Planning of the Explore phase - Please
make yourself familiar with the tool, enter the required information, and
download the corresponding software including stack-xml. See accelerator
section for details.
_x000D_
This task covers the provisioning of a sandbox environment in a conversion
scenario._x000D_
It is important to migrate and convert sandbox copies of production early in
the project. The migration and conversion of the sandbox systems will
provide valuable insights including confirmation of the planned conversion
approach, potential business downtime, required prerequisites, and
experience in the nuances and the functionality of each system._x000D_
The prerequisite is that you have defined the conversion scope in the
planning phase and that you fulfilled all application prerequisites identified
in the SAP Readiness Check for SAP S/4HANA. Additionally you have already
set up the required technical infrastructure._x000D_
Procedure _x000D_
This is how you should perform SANDBOX migrations and conversions as
copies from production: Evaluate the conversion approach, the
conversion guide and heterogeneous system copy guides (if required) to
determine the necessary steps to achieve the end-state. Review related
SAP Notes for the migration to the target platform. Perform
homogeneous system copies to establish the environment that represents
the initial-state. Dependent upon the scope of the project, the system
sequence, and the high-level plan; the initial sandbox migration could
include the full scope or just the first system planned for migration. Execute
the mandatory preparation steps which have not been done already upfront.
Typically, many SI-checks executed by SUM will report issues, which need to
be addressed (partly in the production system) before the system conversion
can start -; so the first sandbox run will take longer. See activity Transition
Preparation in the Prepare phase of the project. Establish a software
repository on a file server to create a central location for all files used in the
migration process. Execute the conversion of the sandbox system(s)
using the process intended for the production systems. Document what
preparatory steps still need to be done in production, before the conversion
of the supporting system starts. Document every step of the conversion to
build a cookbook specific to the environment in scope. The intent of such a
document is the make the process resource independent. For contingency
purposes, all knowledge required for the conversion should be captured in
the cookbook. The document should be validated and extended in further
test conversion. The cookbook should include every step in the process,
_x000D_
Depending upon the downtime requirements of the business and the
downtimes already achieved during the test migrations, there may be the
need to execute iterative testing cycles to optimize the migration and
conversion procedures. The time required for this task should be planned for
as a contingency when building the project plan, but in a best case never
utilized. In that best case scenario, where the downtime meets the
downtime requirements of the business, this time can be reallocated to
other aspects of the project._x000D_
During this task the timings of each part of the migration and conversion
needs to be carefully evaluated to determine opportunities for
optimization._x000D_
As the overall duration has many influencing factors (e.g. database size,
network throughput, CPU speed, disk IO, etc…), there are some
constraints on what can be done to reduce the downtime. Therefore it is
important to manage the expectations of the downtime, with the business
early in the project. If the business offers only a limited downtime window,
this should be discussed early in the project planning phase with a contact
from SAP_x000D_
The conversion for SAP S/4HANA requires additional downtime for the
application data model conversion, in addition to the downtime for the
system ramp-down, S/4HANA software implementation, HANA migration,
and ramp-up). Data volume in conversion relevant tables Data quality
- specifically the data consistency and data diversity of the financial tables
BSEG and COEP Memory capacity for data migration Number of parallel
jobs (option to split into smaller packages based on company code and fiscal
year) Overall system performance (I/O, CPU, memory, tuning,
etc…)_x000D_
For systems larger than 2 Terabyte, a downtime minimized approach may be
required to support the data model conversion within the permitted
business downtime._x000D_
A good general overview of the Downtime Optimization options can be
retrieved from SAP blogs (see Accelerator’s section). Their availability
depends on various factors (e.g. do you start from SAP ERP, or SAP Suite on
HANA? Is SAP executing the conversion or not?). Ask your SAP TQM for more
information in case there are indications for additional downtime
optimization._x000D_
Procedure_x000D_
_x000D_
The purpose of this task is to setup the sandbox system -; ideally with all the
capabilities that are delivered by either Best Practices, Model Company or
RDS package(s) -; to start with a system which is already pre-configured. In
case this is not possible (e.g. because no best practice content is available for
the functionality in scope), a new (and empty) SAP S/4HANA system needs
to be installed._x000D_
Once the Sandbox environment is setup, the project team will prepare it for
the fit/gap analysis workshops. This typically includes the adjustments to
organizational structure, changes to the master data and potential
configuration of additional functionality that is critical to be included in the
fit/gap analysis._x000D_
Procedure _x000D_
There are several cases to distinguish. A software appliance can be used,
because SAP best practice content may fit to the functional scope
_x000D_
Using a software appliance for sandbox is the fastest way to provide a pre-
configured environment to the functional project team. _x000D_
The appliance can be consumed in three ways: 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 a cloud provider
(for instance 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 (exact costs to be determined, should be in the range of 3-5 USD
per uptime hour). If the customer opts to go beyond the 30-day limit, an SAP
CAL subscription license and a regular SAP S/4HANA license is required.
Besides the SAP S/4HANA backend, the customer also receives access to a
MS Remote Terminal Server (WTS) with the pre-configured Fiori Launchpad
URL, SAP GUI logon, and other useful frontend software. 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 (in this case, an SAP HANA and a Linux platform are
required on-site). In addition, a service relationship with SAP and a regular
SAP S/4HANA license is required. Details can be found in SAP notes 2041140
(for partners) and 2202234 (for customers). In case of an on-premise
installation, customers can also decide to install an empty SAP S/4HANA
system, without pre-configuration. The SAP Model Company is the third
_x000D_
Before configuration and development work starts in the Realize phase, the
development system (DEV) needs to be set up. It depends on the scenario
how this is done._x000D_
Please note: This road map documents the setup of a DEV and a QAS system.
Of course, the design of the production support landscape depends on
customer requirements for change management. It is possible that
additional supporting systems need to be set up (e.g. pre-production or
training). In those cases, the project plan template needs to be adjusted
accordingly._x000D_
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._x000D_
Procedure DEV Setup (New Implementation)_x000D_
or DEV Setup (System Conversion)_x000D_
Once the DEV system is available, please check the integration setup as
documented in the Integration design activity._x000D_
basket, and creates a control file (“stack-xml”), which is later required for the
conversion and installation tools. The Maintenance Planner has been
section for details._x000D_
SAP offers the provisioning of the DEV environment for both scenarios as
part of the “Platform Execution” service.Please ask your SAP contact (e.g.
SAP Client Partner) for more information. This is a dedicated scope option
(System Conversion for SAP S/4HANA and System Installation for SAP
S/4HAHA). The setup of the technical Fiori components is covered by scope
option SAP Fiori Platform Setup. However, the configuration of the Fiori UIs is
not included in this scope option. See accelerator section for more
information._x000D_
_x000D_
The goal of this task is to provide a viable, correctly configured technical
development environment that is available for use by the project team to
begin the realize phase._x000D_
Procedure_x000D_
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.
Please note: A sandbox which has been set up by using a software
appliance on-premise, and which is used as a DEV system afterwards may
have activated business functionality which is subject to additional licensing.
In addition, the SAP BluRay comes with an embedded landscape for Fiori
(backend and frontend in the same machine) whereas SAP recommends a
Central Hub set-up (having frontend and backend separated) for productive
systems. Therefore, SAP recommends to not use an SAP appliance as a DEV
system, but to do a fresh SAP S/4HANA installation. Execute the technical
installation of the required SAP Products for DEV environment as
documented in the technical design document. See the “Installation Guide
for SAP S/4HANA” how to install the components. Based on the outcome the
decision will be taken to either use SAP Best Practice content or not:
In the case of not using SAP Best Practice content: Create a new client
and start configuration from scratch using transaction SPRO. In the
case of using SAP Best Practice content: Follow the instructions given in the
“Administration Guide for the Implementation of SAP S/4HANA”. This will
guide you through the technical setup, and the configuration process on top
of the newest SAP Best Practice content. The technical setup consists of
three main steps: Import newest reference content into
your newly created development client Select the scope
Activate the scope _x000D_
The figure below shows these three steps in a sequence._x000D_
_x000D_
Figure: The three steps required to activate best practices content_x000D_
This activity is done by the functional project team members._x000D_
Results_x000D_
Finally, the DEV environment is ready for configuration._x000D_
SAP offers the installation of a sandbox as part of the Platform Execution
service. Please ask your SAP contact (e.g. SAP Client Partner) for more
_x000D_
development environment that is available for use by the project team to
begin the realize phase. DEV is not installed newly -; instead, the old DEV
system is converted to SAP S/4HANA._x000D_
The prerequisite is that the migration approach that has been validated in a
sandbox environment (see activity SANDBOX System Setup / Conversion in
the Explore phase), a detailed migration plan is in place, and the required
hardware for hosting the SAP S/4HANA DEV system is already available and
set up._x000D_
Procedure _x000D_
Convert the DEV system according to the migration plan (which is based on
the “Conversion Guide for SAP S/4HANA”). Depending on the transport
landscape configuration, there may be a need to perform multiple iterations
of the conversion to solidify and finalize the cutover plan. Executing test
migrations will validate the end-state of the conversion, as well as provide
the figures for expected system downtime (see activity Downtime
Optimization Preparation for details). Depending on the approach and the
transport landscape configuration, there may be a requirement to execute
additional sandbox conversions to optimize the cutover procedure._x000D_
Please note: In case of a system conversion, the old DEV system will stay for
production support of PRD if PRD is not converted. Take care to properly
retrofit changes performed in the production support landscape to the new
DEV system to ensure the latest business requirements are accounted for
within the project landscape. Depending on the changes, those retrofit
activities may require special attention, because transports between classic
SAP ERP and SAP S/4HANA may cause inconsistencies (see SAP Note
2192251 in the accelerator section)_x000D_
Results_x000D_
Finally ,the DEV environment has been converted to SAP S/4HANA. It is
ready for further configuration._x000D_
SAP offers the DEV conversion as part of the “Platform Execution” service.
Please ask your SAP contact (e.g. SAP Client Partner) for more information.
This scope option is called “System Conversion to SAP S/4HANA” -; see
accelerator section for more information. The setup of the Fiori platform can
be supported as well (scope option “SAP Fiori Platform Setup”). However,
_x000D_
Run a capacity estimation on the required hardware for application server
and databases (CPU, RAM, storage, network)._x000D_
There are several levels for sizing: Budget sizing for smaller companies,
using very simple algorithms. Advanced sizing for medium to large
companies, using throughput estimates, questionnaires, formulas. Advanced
sizing uses standard tools (e.g. Quick Sizer) and focusses on core business
processes. Expert sizing is based on a custom capacity model which for
instance may also include custom coding._x000D_
Timing: Explore phase (non-production systems), realize phase (production
and production-like systems)_x000D_
_x000D_
There is an implementation plan available which provides first information
about the target solution._x000D_
Procedure_x000D_
_x000D_
_x000D_
Perform / Check Initial Sizing
Results_x000D_
There is a documented estimate on the required hardware, which can be
discussed with the hardware vendor.
_x000D_
The objective of this task is to either perform a sizing, or in case a first
estimate has been provided check the initial sizing._x000D_
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 a
system conversion, the sizing report should be executed periodically in the
productive system throughout the project to check on the growth of the
source system._x000D_
Results_x000D_
A sizing has been performed and is documented._x000D_
SAP can perform this task with the “Advanced Sizing” service component
which 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.
_x000D_
To be able to provide a detailed definition of the technical target architecture
and infrastructure, you will first need to clarify the technical boundary
conditions. This is the basis for the creation of the Technical Solution
Blueprint._x000D_
Within the IT Infrastructure definition, customers need to create a detailed
infrastructure design. This includes the selection of hardware vendors for
servers and storage, mapping of technical components, network design and
the definition of cloud integration options._x000D_
There is an implementation plan available which provides initial information
about the target solution._x000D_
Procedure Discover Technical Boundary Conditions Create Technical
Solution Map Decide on Integration with Cloud Applications Hardware
Selection and Utilization Develop Virtualization Strategy Design Network
Test Preparation_x000D_
Results_x000D_
As a result, there is a documented technical solution map and an IT
infrastructure definition available in SAP Solution Manager._x000D_
To minimize the effects of unplanned down times, a comprehensive High
Availability and Disaster Recovery architecture is essential, as well as reliable
backup and recovery procedures,considerations about tools available, and
test procedures. The “Technical Platform Definition” service component
supports in these tasks._x000D_
Moreover, the selection and proper configuration of the technical platform is
the foundation to achieve a flexible and scalable execution environment for
the new system. The “Technical Platform Definition” service component also
supports in the selection of the right IT infrastructure which is the basis for
the vendor-selection process, and provides Best Practices formapping the
SAP software components on it.
_x000D_
The technical boundary conditions are input into the technical design
document, which is the basis for the subsequent Data Center service setup.
In many cases these conditions are already defined by the customer._x000D_
Procedure_x000D_
The Technical Boundary Conditions in scope are: Technical solution map
Non-production system landscape Sizing DC strategy Availability
requirements_x000D_
All information needs to be stored in the Project Management space of SAP
Solution Manager for central access._x000D_
Non-production System Landscape 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._x000D_
DC Strategy Collect initial assumptions of the DC provider, topology, and DC
roles. The information can be derived from the existing DCs. Alternatively
run a design workshop for a new DC strategy. Timing: Explore phase (non-
production systems), realize phase (production and production-like
systems)_x000D_
DC Strategy - Example_x000D_
The figure below shows as an example four options for a DC strategy. They
distinguish in setup, which leads to differences in risk mitigation, operational
complexity, and IT costs._x000D_
_x000D_
Figure: Different options for the data center setup (example only)_x000D_
_x000D_
Availability Requirements Collect availability information on:
SLAs for unplanned downtimes (HA/DR). SLAs for planned downtimes
(maintenance). Classification of systems according the SLA.
_x000D_
The information can often be derived by using existingSLAs in the context of
the new solution. Alternatively run aworkshop for a high-level SLA definition
(as part of the “Technical Architecture” workshop and the “Technical
Platform Definition”service component). Timing: Realize phase._x000D_
Availability Requirements -; Example_x000D_
The following figure shows exemplarily different definitions of “Mission
_x000D_
The objective of this task is to update technical solution map of the target
The technical boundary conditions have been documented._x000D_
Procedure_x000D_
Proceed as follows: Collect information on installable technical
components, required integration technology between them, and non-
functional req. of the integration technology. Collect information on the
component deployment model (on-premise, cloud / SaaS). The information
is usually provided by architects of the application work stream. The
Technical Solution Map should also cover: Minimum release
levels Dependencies between software releases / SAP Support
Package Stacks Minimal Browser versions If required: the
outline that a Dual Stack split needs to be included in the conversion project
If required: List dependent SAP NetWeaver Hub systems, and their
minimal release (See “Version Interoperability” at the Accelerators section)
Update the technical solution map (see accelerator section for
a template in case it is not available), and store it centrally in SAP Solution
Manager._x000D_
Results_x000D_
There is a technical solution map of the target architecture available in SAP
Solution Manager._x000D_
To minimize the effects of unplanned downtimes, a comprehensive High
Availability and Disaster Recovery architecture is essential, as well as reliable
backup and recovery procedures, considerations about tools available, and
test procedures. The “Technical Platform Definition” service component
supports in these tasks._x000D_
Moreover, the selection and proper configuration of the technical platform is
the foundation to achieve a flexible and scalable execution environment for
SAP the new system. The “Technical Platform Definition” service component
also supports in the selection of the right IT infrastructure which is the basis
for the vendor-selection process, and provides Best Practices for mapping
the SAP software components on it.
_x000D_
The objective of this task is to decide on the integration with cloud
applications._x000D_
Procedure _x000D_
In case cloud applications are in scope as well as for the implementation
project, backend integration with these must be discussed. For instance,
available bandwidth, peak times, availability requirements and recovery
procedures might be a limiting factor here._x000D_
Cloud applications could also be FIORI UIs running in the SAP Cloud Platform,
which are connected to the SAP backend landscape via the SAP Cloud
Connector._x000D_
Results_x000D_
As a result, a technical architecture for the integration of on-premise and
cloud-solutions must be created
_x000D_
Within this task, customers decide on server and storage hardware._x000D_
As a prerequisite, the sizing results including the software change
management landscape must to be mapped to possible hardware and/ or
virtual container sizes._x000D_
Procedure_x000D_
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
The hardware requirements must be mapped to project phases afterwards
and planned together with the hardware vendor._x000D_
Results_x000D_
As a result, there is a documented deployment plan which includes the
definition of the hardware._x000D_
_x000D_
_x000D_
_x000D_
The objective of this task is to develop a virtualization
strategy.Procedure_x000D_
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._x000D_
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._x000D_
_x000D_
Results_x000D_
As a result, a general technical architecture of the new systems in virtualized
environments must created/adapted. In addition, general technical
configuration rules for the SAP S/4 HANA must be considered.
_x000D_
A network design for the new system must be created_x000D_
Procedure_x000D_
The network design needs to include data center inter connectivity as well as
network zones. For instance, isolation of different network zones from a
performance perspective is crucial to rely on system replication for high
availability. The figure below shows some examples of requirements and
network segments._x000D_
_x000D_
Figure: Bandwidth requirements per network type (example only)_x000D_
Sizing rules for LAN and WAN segments must be applied. In case of limited
bandwidth or high latency, WAN acceleration solutions must be
considered._x000D_
Results_x000D_
As a result there is a network design document stored in SAP Solution
Manager.
_x000D_
After the clarification of the target technical architecture including hardware
and virtualization platform, meaningful test cases must be created._x000D_
The target technical architecture has been designed and
documented._x000D_
Procedure_x000D_
Prepare test cases for: Landscape flexibility and workload management
Technical configuration verification HA / DR Backup and restore_x000D_
Results_x000D_
As a result, as test plan including a timeline and test case description has
been created.
_x000D_
This activity creates a technical design document._x000D_
This task is recommended for all implementation scenarios._x000D_
The technical architecture, and the IT infrastructure has been designed and
documented._x000D_
Procedure_x000D_
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
planExpert sizing & scalability verification Technical architecture for
production systems Technical infrastructure Deployment patterns and
deployment plans DC integration 3rd party integration_x000D_
The aspects have dependencies to each other, and to the boundary
conditions. Some of them need to be considered iteratively._x000D_
The Technical Architecture Workshop (see activity Technical Architecture in
the Discover phase) should have touched many of the aspects from
above)._x000D_
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_x000D_
A technical solution design document is available in SAP Solution Manager
for central access.
_x000D_
The objective of this task is the creation of a technical solution
blueprint._x000D_
Procedure_x000D_
Take the appropriate “Technical Solution Blueprint Template” from the
accelerator section, and tailor it to your project requirements._x000D_
Define & document the following areas:_x000D_
Technical components: Determination of required technical components for
the SAP solution, and their deployment options._x000D_
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)._x000D_
Scalability and load balancing concept: Determine how applications in the
SAP solution can grow from workload & data footprint perspective._x000D_
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). _x000D_
Backup concept: Definition of the backup infrastructure and backup
execution strategy for each persistency type._x000D_
Backup concept - Example_x000D_
The figure below shows an example for a backup concept of DB data files,
log, files, and configuration files._x000D_
_x000D_
Figure: Backup concept (example only)_x000D_
Procedure Clarify available backup methods per storage type.
Determine appropriate backup types (full, incremental, differential) for each
component type. Determine retention times. Design the technical
architecture for the backups. Timing: Discovery phase (non-prod), realize
phase (prod). _x000D_
HA/DR concept: Definition of the technical architecture for high availability
(SPOF protection) and disaster recovery (data protection, recovery
procedures)._x000D_
HA/DR Concept - Example_x000D_
The figure below shows the exemplary HA / DR setup with two DCs._x000D_
_x000D_
_x000D_
With the introduction of a new solution like SAP S/4HANA, the current IT
support framework will change. The impact of the new solution on the
support framework varies based on customers' current support framework
and on the way how customers plan to use the new solution. Example
scenarios include the following: On-premise solution_x000D_
IT is responsible for the entire solution and needs to learn about the
technical and functional specifications of the solution. Hosted
solution_x000D_
IT is responsible for monitoring application performance, troubleshooting,
and all application support activities. Cloud-based solution_x000D_
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_x000D_
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_x000D_
All the topics mentioned in this activity are relevant for “Greenfield”
customers. The effort to prepare for the support of SAP S/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, and 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 S/4HANA.
_x000D_
The technical solution design document (see activity Technical Design 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
_x000D_
The objective of this task is to evaluate the impact on IT operations when
implementing SAP S/4HANA._x000D_
Procedure _x000D_
During the Operations Impact Evaluation activity, the SAP S/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. For example, in case SAP Fiori Apps are
newly introduced, the administration and operation of the Frontend Server
needs to be defined and set up, and resources need to be trained on the
systems involved and their configuration. In addition, support processes like
incident management need to be able to handle the new component. Are
existing, but must modified. For example, daily backup routines need to be
adjusted to properly fit the new SAP S/4HANA solution. Support tools like
monitoring, troubleshooting or software logistics tools need to be in place.
Processes like Master Data management need to be revisited to define new
policies required by the major changes in the Master Data structure. Can be
retired. For example, DB routines and scripts for AnyDB can be retired.
AnyDB monitoring set up should be retired as well._x000D_
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 S/4HANA solution, the processes/procedures, the operations
documentation and the enabling support tools._x000D_
SAP can support you in all these activities with a systematic approach to
operational activities will ensure you analyze all the changes in IT operational
activities caused by the new solution._x000D_
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
_x000D_ education of current operational resources, training, hands on and
Management plans developed during the project prepare phase 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.
_x000D_
The purpose of this task is to update the project management plan and the
subsidiary plans based on the changes agreed during the projects change
management process.
_x000D_
The purpose of this task is to ensure that the project is executed according to
what was agreed to in project charter, scope statement and project
management plan.
_x000D_
The purpose of this task is to plan, setup and conduct various SCRUM
meetings to keep the project teams aligned around common vision, share
information amongst the SCRUM teams and align individuals within each
team. The purpose of these standard meetings is to inform others about the
work that individual team members do on a given day and surface any
blockers that team members need help addressing. In agile implementation
project, the teams conduct the following meetings:_x000D_
1. Daily SCRUM meeting
short (about 15 minutes) session within each SCRUM team facing the
SCRUM board team members report to the team about what they are
working on and whether they are encountering any issues that they need
help with. The objective of this session is to inform and align the team
work._x000D_
2. Regular SCRUM of SCRUMs meeting
session in which SCRUM Masters from individual SCRUM teams share
information about what each SCRUM team works on, surface any cross-team
alignment topics and resolve any issues that arise between the teams. The
session is very similar to integration team meetings conducted in traditional
projects. Note: Cadence of these sessions needs to be calibrated, but they
should be done on at least a bi-weekly basis. The more often they are done
the shorter they can be._x000D_
3. Sprint Demo
the purpose of this meeting is to demonstrate the results of the sprint to the
customer and obtain acceptance to release the features developed during
the sprint. The meeting is attended by the Product Owner team, End users
and SCRUM team. It is conducted at the end of sprint._x000D_
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.
_x000D_
scheduled project activities (and tasks) and that work is progressing and
_x000D_
The purpose of this activity is to capture and manage project issues and risks
and changes related to those e.g. changes of project scope, timeline, costs
etc.
_x000D_
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.
_x000D_
The purpose of this deliverable is to refine the Initial Release Plan that was
defined earlier. At this time the team also defined sprint plan for the first few
iterations. 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 SAP Solution Manager Focused Build accelerator. The
Focused Build material currently relates to SAP Solution Manager 7.1
functionality and the above training materials will be updated for SAP
Solution Manager 7.2. In this update step there will be opportunity to create
greater alignment with existing WBS. Project managers may also want to
consider more significant updates to the WBS to align with the project
approach of the Focused Build approach.
_x000D_
The purpose of this task is to update the backlog with delta requirements /
gaps and to prioritize the backlog items by business importance. The SAP
Activate Methodology recommends using the MSCW prioritization
framework (e.g. the Must-Have, Should-Have, Could-Have, Would-Have) for
an initial grouping of the backlog requirements. The business process owner
is responsible for determining the relative priority of each requirement.
Once the requirements are assigned to the appropriate group, the business
owner needs to determine a sequence of requirements in each of those
groups. This will help the project team to understand the relative priority of
items in each group and this will facilitate selection of the high priority items
during the sprint planning in the Realize phase. During prioritization the
following dimensions need to be considered:_x000D_
Dependencies and Integration
The project team will help business owner assess the impact of the
requirement on other requirements (technical risk, dependencies,
integration points);_x000D_
Scale
The desirability of the feature to a broad base of users (business impact,
acceptance);_x000D_
Importance
The desirability of the requirement to a small number of important users or
customers (influencing key stakeholders, business value)._x000D_
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). The 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. The
secondary step is to rank items within the same priority group.
_x000D_
The objective of this task is to estimate effort for the backlog items. This
activity is done by the project team that has the expertise to estimate the
effort required to complete the backlog items (requirements) from the
backlog. For the project team it is critical to understand when we consider
the backlog item done. The definition of done must be clearly understood by
everybody involved in the project. See examples below for recommended
definitions. The project team needs to ensure that the estimates in the
backlog include all activities required for completion of the item in the sprint
and for completion of the item in the release. Project team should follow
these guidelines during the estimation process: 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 a later
time.
_x000D_
The objective of this task is to prepare release a and sprint plan that will
guide the project team in building the requirements in the backlog into a
fully functional and integrated solution that supports customer’s business.
The starting point for the release and sprint planning is the prioritized and
estimated backlog (activities covered in the previous tasks)._x000D_
The image below shows an example of the iterative agile approach to build
functionality for one release._x000D_
_x000D_
Release represents functionality that is deployed to the 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)_x000D_
During each sprint the project team conducts the following activities:
Sprint Planning Meeting Sprint Execution Activities Daily Stand-up
Meeting Sprint Demo Sprint Retrospective_x000D_
During the project the team will run two types of sprints: Build sprints -
the goal of these sprints is to build and unit test the new capabilities 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
_x000D_
The purpose of this task is to review the release and sprint plans against the
statement of work(SoW). The objective of this task is to identify any new
features that have been surfaced during the baseline build that may not be
part of the original scope and may require amendment of the SoW or
Change Request. It is important to ensure that the project manager validates
that the requirements and user stories in the backlog document are in
alignment with the scope of the project as it is reflected in the SoW and
other contractual documents. The project manager (PM) should also ensure
the alignment of the release and sprint plan with the high level plan covered
in the SoW. In case any discrepancies are discovered the PM needs to take
appropriate corrective action, like raising a change request according to the
integrated change request management plan defined in the Prepare phase.
_x000D_
The purpose of the Change impact analysis deliverable is to ensure that the
organizational and technical changes in business processes have been
identified and documented by comparing the as-is and the to-be business
processes.
_x000D_
The purpose of this task is to validate the chosen approach with key
stakeholders for the continued project execution.
_x000D_
The purpose of this task is to define the baseline for where organizational
change management starts and against which progress and success of the
OCM-activities are measured.
_x000D_
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
_x000D_
_x000D_
The purpose of the Quality Gate is to ensure that both compliance and
project management standards are being upheld within projects. A Quality
Gate is a checklist milestone at the end of a project phase. Prior to moving
into the next phase each project manager demonstrates that they have been
compliant with the mandatory deliverables associated with a methodology
while ensuring best practice standards have been applied to ensure
quality._x000D_
A Quality Gate looks at the following topics in detail: 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._x000D_
Note: New additional key deliverables need to be added in the quality gate
checklist by the project manager to the different project types.
_x000D_
The purpose of this task is to conduct retrospective meeting with the SCRUM
team to identify potential improvements of the SCRUM process. The
objective of this task is to serve as continuous improvement mechanism for
the team to adjust to changing project environment and needs. The team
will select one or two key improvements to implement in the next iteration
and handles them as user stories that are added to the product backlog,
prioritized and tracked along with other user stories.
_x000D_
_x000D_
_x000D_
The purpose of this task is to obtain customer approval (sign-off).
_x000D_
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. The activities of the Realize phase are displayed in the
following figure._x000D_
_x000D_
Figure: Activities in the Realize phase_x000D_
In the Solution Adoption work stream, the training for the end users is
prepared._x000D_
In the Application design and configuration work stream, the functional
changes (general configuration, master data, and core / delta) and security
changes are implemented as defined in the delta design document.
Additional applications, like Central Finance in a selective data transition
scenario, or the SAP Digital Boardroom, are set up as planned. In the
Extensions work stream, program enhancement like reports, or Fiori User
Interfaces, are developed accordingly. Existing custom code is adjusted to be
ready for SAP S/4HANA. SAP can safeguard the activities via the “Integration
Validation” offering, which covers key aspects like Business Data Consistency,
Exception Management, Integration, and Performance and Scalability.
._x000D_
Application changes are thoroughly tested in the Testing work
stream._x000D_
In the Integration work stream, all required interfaces are implemented as
designed in the Explore phase. Further integration setup is done for the
quality assurance system, and for the production system (if already available,
and new implementation only)._x000D_
In the Data Management work stream, data aging and data archiving are
configured for business objects according to the DVM strategy. Load and
verification runs ensure that business data can be migrated with acceptable
time and quality._x000D_
The technical infrastructure is set up in the Technical Architecture and
Infrastructure work stream, according to the technical design document. The
transition of the quality assurance system takes place according to the
detailed transition plan, and technical adjustments may be implemented as
part of the activity. In parallel, the sizing of the productive instance is
verified._x000D_
According to the Operations Impact Evaluation, the operations
implementation (people, processes tools) takes place in the Operations &
_x000D_
The purpose of this deliverable is to formally recognize that a new project
phase starts._x000D_
Tasks Review Deliverables of Realize Phase Review Acceptance
Criteria Review RACI Chart for Realize Phase with Customer
_x000D_
The purpose of this task is to review all Deliverables of the Realize Phase
with the customer.
_x000D_
The purpose of this task is to review the acceptance criteria with the
customer.
_x000D_
The purpose of this task is to review the R.A.C.I Chart for the Explore Phase
with the Customer. It is important to clarify roles and responsibilities in
completing tasks and deliverables during this phase
_x000D_
The purpose of this activity is to define plans for Sprints, Solution Reviews
and prepare all business-process-related tests according to customer-
specific configurations.
_x000D_
The purpose of this task is to plan Sprints and prepare to evaluate the
proposed solution.
_x000D_
The purpose of this task is to plan the test sessions from a Project
Management point of view._x000D_
Procedure Review Test entry and exit criteria with customer Schedule
Test Sessions and Plan Resources
_x000D_
In this activity the training material for end user will be created._x000D_
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._x000D_
Procedure Train your Key User Create Training Material for End
User_x000D_
Results_x000D_
At the end of this activity, the training for the end user is ready to be
delivered (including systems, demo data etc.).
_x000D_
The goal of this task is to train the key user as planned in the activity
Learning Design in the Explore phase._x000D_
Procedure_x000D_
Train your key user as planned in the Explore phase. Training could happen
e.g. via class room training, or on the sandbox system._x000D_
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._x000D_
Results_x000D_
Key users are trained._x000D_
SAP can support the training of key users as part of an individual offer from
SAP Education. See accelerator section for details.
_x000D_
The goal of this task is to create the required training material according to
the training concept (see activity Learning Design in the Explore
phase)._x000D_
Procedure_x000D_
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._x000D_
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._x000D_
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._x000D_
The following list describes possible end user training documents required to
be developed for every training:Course Concept_x000D_
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_x000D_
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
_x000D_
The purpose of this task is to initiate sprint in a formal Sprint Planning
Meeting.
_x000D_
The purpose of this task is to initiate sprint by selecting the set of user
stories that will be implemented in the sprint (scope of the sprint). During
the sprint planning meeting the SCRUM team estimates the stories and
clarifies with the product owner team any questions that may still remain
open. The team commits to deliver a set of the highest priority stories from
the backlog. This meeting formally sets the scope for the sprint. This meeting
is conducted at the beginning of each sprint.
_x000D_
The purpose of this deliverable is to execute the work defined in the Realize
Phase and manage the Sprints and Testing according to previously defined
plans. During test execution all issues must be logged and documented in
the system for traceability purpose.
_x000D_
The purpose of this task is to ensure consistent execution and monitoring of
sprint activities.
_x000D_
The purpose of this task is to properly manage the Unit/Spring Test. During
the test all issues must be logged and documented in the system for
traceability purpose.
_x000D_
The purpose of this task is to properly manage the integration test. During
the test all issues must be logged and documented in the system for
traceability purpose.
_x000D_
The purpose of this task is to properly manage the security test. During the
test all issues must be logged and documented in the system for traceability
purpose.
_x000D_
The purpose of this task is to properly manage the User Acceptance test
(UAT). During the test all issues must be logged and documented in the
system for traceability purpose.
_x000D_
The purpose of this activity is to configure the mandatory settings, according
to the delta design defined and agreed during the Explore phase (see
activities Fit Gap / Delta Design / Backlog for details). The delta design
documents contain changes related to both the implementation of new
functionality, and the mandatory configuration adjustments._x000D_
Procedure _x000D_
This road map describes the execution of configuration work in an agile
implementation model. However, customers who prefer the classic water fall
implementation model can follow the same approach, by assuming the
number of sprints equals 1._x000D_
The purpose of the configuration activities is to use a series of iterations to
incrementally build and test an integrated business and system environment
that is based on the business scenarios and process requirements identified
in the previous phase._x000D_
Accordingly, configuration steps will be executed in different iterations
(sprints) starting from general settings per Line of Business up to detailed
configuration for each area._x000D_
For each cycle the following steps will apply (example for configuration in six
business priorities is shown in the figure below):_x000D_
_x000D_
_x000D_
Figure: Individual steps within each configuration cycle (sprint)_x000D_
Sprints are time boxed two-week cycles. Each sprint will consider system
configuration, documentation and unit testing based on the delta backlog
identified during explore phase._x000D_
Sprint 1 considers the finalization of the core configuration. For example,
during design only one legal entity was activated -; however, according to the
design in total 5 legal entities might be activated. For System Conversion
scenarios, mandatory changes must be finalized according to the prioritized
backlog. All general settings and organizational structures need to be
configured. Master data settings are prepared, and core processes are
configured._x000D_
Sprint 2 considers the realization of gaps maintained in the delta backlog.
Further sprints may follow based on customer requirements._x000D_
In case of a newly implemented business process, configuration data will be
taken from Best Practices content from SAP Activate (if available, and if
appropriate)._x000D_
_x000D_
The purpose of this activity is a structured handover from the design team
(in charge of the delta design documents) to the configuration
team._x000D_
Procedure _x000D_
This activity is executed per Line of Business / end-to-end solution and
sprint. Run Handover Session
_x000D_
The objective of this task is to properly hand over all required material from
the design team to the configuration team._x000D_
Prerequisite_x000D_
The solution design is properly documented and approved._x000D_
Procedure_x000D_
Run a hand-over workshop to pass all important design documents for a
business priority / end-to-end solution from the design team to the
configuration team. Required documents are for instance: To-Be Design
Role Mapping to Security Important CustomizingMaster Data Specifications
Organizational Structure Specification Functional Specification per
WRICEF Object Solution Manager usage guideline (if appropriate)
Configuration guideline_x000D_
SAP supports this task with the “Configuration” scope option as part of the
Build Execution service. Please see “SAP Advanced Deployment” link below
and ask your SAP contact (e.g. SAP Client Partner) for more information.
_x000D_
The purpose of this activity is to perform the necessary customizing in the
Development system according to the agreed business process
scope._x000D_
Procedure_x000D_
sprint. Perform Main Configuration
_x000D_
The objective of this task is to perform the main configuration of the Line of
Business / end-to-end solution. In case of an agile implementation, the first
sprint usually focuses at the core configuration whereas subsequent sprints
provide the delta configuration._x000D_
Prerequisite_x000D_
Design documents have been handed over to the configuration
team._x000D_
Procedure_x000D_
The main configuration is structured into: Configuration of general
settings and organizational structure_x000D_
As an example, for Core Finance, typical entities are (besides others):
Chart of Account VAT Numbers Company codes Controlling area
Configuration of master data_x000D_
As an example, for Core Finance, this covers (besides others): Profit
center Cost center Bank directory SAP Business Partner Core / Delta
configuration of the application_x000D_
Typical configuration items for Core Finance are (besides others):
Document types Localization settings (e.g withholding tax)Correspondence
Document splitting Statistical key figures Payments (ingoing /
outgoing) Clearing Dunning Month end closure procedures (periodical
processing)_x000D_
See the SAP Best Practice Explorer for configuration items structured by Line
of Business / end-to-end solution. Also, the Product Assistance section in the
SAP Online Help Portal describes application specific configuration in
detail._x000D_
Properly record configuration changes in transport requests._x000D_
_x000D_
The purpose of this activity is to unit test the newly configured functions in
the Development system._x000D_
Procedure_x000D_
sprint. Run Unit Test
_x000D_
The objective of this task is to properly unit test the newly implemented
functions in the Development system, and to properly log issues in the
project issue list._x000D_
Prerequisite_x000D_
Functionality has been implemented and configured in the Development
system._x000D_
Procedure Run unit tests on the newly implemented configuration and
functionality in the Development system.Document test execution properly.
Issues should be corrected either directly (same day), or in case this is
not possible logged in the project issue list._x000D_
See SAP Best Practice Explorer for test script examples._x000D_
_x000D_
The purpose of this activity is to test an initial solution integration within the
business priorities / end-to-end solutions in scope. This is not a fully loaded
integration test (see activity Test Execution later in this phase)._x000D_
Procedure_x000D_
sprint. Run String Test
_x000D_
The objective of this task is to run a first test on solution integration within
the business priorities / end-to-end solutions in scope._x000D_
Prerequisite_x000D_
Unit tests have been completed._x000D_
Procedure_x000D_
Run an initial test on solution integration within the business priorities / end-
to-end solutions in scope. Since the full integration test is executed later in
this phase, the recommendation is to only test with manually created test
data, and to focus on SAP functionality only (no testing of customer specific
WRICEF objects)._x000D_
Test execution and results should be properly documented and stored in SAP
Issues should be corrected either directly (same day), or in case this is not
possible, logged in the project issue list._x000D_
See SAP Best Practice Explorer for test script examples._x000D_
Build Execution service.Please see “SAP Advanced Deployment” link below
_x000D_
The purpose of this activity is to have an early knowledge transfer from the
configuration team._x000D_
Procedure_x000D_
sprint. Run Solution Walk-Through
_x000D_
The aim of this task is to present the new solution capability to the
corresponding project team members for early knowledge transfer._x000D_
Prerequisite_x000D_
String tests have been completed._x000D_
Procedure_x000D_
Proceed as follows: Run a session per Line of Business / end-to-end
solution, and present the new functionality from an application perspective.
Explain the required configuration from an IT perspective. Log issues in
the project issue list, which have been identified during solution walk-
through._x000D_
_x000D_
The purpose of this activity is to resolve issues identified during the unit and
string test or solution walk-through._x000D_
Procedure_x000D_
sprint. Resolve Identified Issues
_x000D_
The aim of this task is to resolve and correct issues which have been
identified during tests and solution walk-through._x000D_
Prerequisite_x000D_
Solution walk-through has been completed._x000D_
Procedure Resolve issues which have been identified in the unit / string
test and solution walk-through, and which have been documented in the
project issue list. Properly record corrections in transport requests._x000D_
Build Execution service.Please see “SAP Advanced Deployment” link below
_x000D_
The purpose of this activity is to document the configured settings and
upload the results in SAP Solution Manager._x000D_
Procedure_x000D_
sprint. Document Configured Settings
_x000D_
The objective of this task is to properly document the configuration
settings._x000D_
Prerequisite_x000D_
Bug fixing has been completed._x000D_
Procedure Extend the design documents, by properly documenting the
configuration settings in SAP Solution Manager. Add further information on
detailings and agreed changes_x000D_
_x000D_
With Central Finance, customers can transition to SAP S/4HANA Finance, on-
premise edition without disruption to their current system landscape, which
can be made up of a combination of SAP systems of different releases and
accounting approaches and non-SAP systems. Central Finance allows
customers to create a common reporting structure. See accelerator section
for more details._x000D_
This activity is only relevant in case you would like to set up Central Finance
(selective data transition scenario).
_x000D_
The activity Product Enhancements covers the development of custom code
to close the gaps identified in the Fit / Gap activities in the Explore
phase._x000D_
It further covers the adjustment of already existing custom code identified in
the activity Custom code impact._x000D_
Procedure Adjust affected existing custom codeDevelopment of WRICEF
objects Development of user interfaces (e.g. FIORI) Custom
Developments_x000D_
Before developing new code in SAP S/4HANA your developers should be
aware of programming best practices coming with new SAP NetWeaver
releases. Look for instance at the SAP Blog “Best Practices for ABAP
Development on SAP Netweaver 7.5x” from the SAP RIG team._x000D_
However, SAP recommends to explore the options for the agile creation of
customer innovations using the extensibility capabilites of SAP S/4HANA and
SAP Cloud Platform. This is of particular interest for : SAP Fiori and the
mobile journey in the SAP Cloud Platform (decoupling custom user interface
development from the stable SAP S/4HANA core, when developing mobile
apps for B2B, B2C, C2B) Agile data mart: Running SAP BI and Predictive
Self-Services in an SAP Cloud Platform sidecar_x000D_
The usage of the SAP Cloud Platform has two additional benefits: You can
run innovations in parallel to the S/4HANA conversion project You can
consume innovations without upgrading the stable SAP S/4HANA core (e.g.
LoB Finance innovations delivered via SAP Cloud Platform
applications)._x000D_
You will find helpful information resources in SAP whitepaper and blogs (see
“Extensibility of SAP S/4HANA -; Helpful Links” in the accelerator section).
Look up also training courses on SAP Cloud Platform at openSAP._x000D_
See the accelerator section for more information.
_x000D_
The goal of this task is to adjust custom code and make it ready for SAP
S/4HANA._x000D_
This activity is relevant in case own code needs to be made ready for SAP
S/4HANA (e.g. the system conversion case). In case of a new
implementation, or a selective data transition, some custom code from an
old SAP ERP system might be in scope to be used in the new SAP S/4HANA
system._x000D_
The custom code work list of affected objects has been created (see activity
Custom code Impact)._x000D_
The development system has been converted to SAP S/4HANA._x000D_
Procedure_x000D_
To adjust custom code that is affected by the conversion to SAP S/4HANA
project, proceed as follows: Make sure your developers have the
required skill set to adjust your custom code for SAP S/4HANA. There are
multiple options for developer training (e-learnings, classroom). Please see
accelerator section for more information. Make sure you have the
prioritized list of custom objects requiring adjustment (see activity Custom
Code Impact for details). Wait until your DEV system has been converted
to SAP S/4HANA. Adjust custom code objects in the converted DEV system
according to the prioritized custom object list. For standard known issues
which do not require a change of the application logic, SAP is providing a
constantly growing list of “Quick Fixes” which can be triggered from the
ABAP Test Cockpit. Quick fixes automatically adapt your custom code to
minimize your adjustment efforts. All changes are logged in transport
requests. See accelerator section for more information. Transport your
changes to QAS, once it has been converted to SAP S/4HANA. Test your
changes in QAS. In case corrections are required, perform the corrections in
DEV and transport to QAS again. All transport requests should then be
populated in the PRD buffer, ready for import during the Go-Live._x000D_
Please note: In case of a system conversion, the old DEV system will stay for
production support of PRD as long as PRD is not converted. Take care to
properly retrofit changes performed in the production support landscape to
the new DEV system to ensure the latest business requirements are
accounted for within the project landscape._x000D_
Results_x000D_
All custom code is adjusted to function properly with SAP S/4HANA._x000D_
_x000D_
The purpose of this task is to provide coded enhancements within the
defined project scope and specified from a functional perspective during the
Explore phase._x000D_
WRICEF is defined as follows: W = workflow R = reports I = interfaces
C = conversions E = enhancements F = forms_x000D_
Procedure_x000D_
Development of WRICEF objects is following the procedure:_x000D_
Step 1: Technical Design_x000D_
Based on the functional requirements described in the delta design
document, the purpose of this task is to specify the WRICEF object from a
technical perspective. A detailed technical specification will be provided. This
comprises of ABAP developments development details like entry point in the
system, enhancement logic, process flow diagram, data model and required
authorizations._x000D_
WRICEF objects are new objects or objects to be adjusted, identified during
the explore phase, e.g. a requirement for a new workflow or form
identified._x000D_
All information will be documented in a technical specification document
(see Accelerator’s section for details)._x000D_
For each enhancement, the appropriate test case(s) will be defined and
documented. The final documents will be stored in SAP Solution Manager for
shared access._x000D_
Step 2: Development of WRICEF objects_x000D_
The developer is in charge to realize the requirement, which includes the
development itself but for sure also documentation and unit
testing._x000D_
Step 3: Unit testing for all developed objects_x000D_
The purpose of this task is to perform a unit test of the developments. The
objective is to resolve any issues identified during the WRICEF object(s) test.
It is crucial that the issues are solved, and re-tested by users that reported
them (or designated re-testers) and that they are confirmed._x000D_
Additionally, during this task, a final code review of the development objects
will be performed and readiness for transport into QAS has to be
confirmed._x000D_
SAP supports this activity with the “WRICEF Developments” service as part
of SAP Professional Services._x000D_
_x000D_
The purpose of this task is to provide UI enhancements within the defined
project scope and specified from a functional perspective during the Explore
phase._x000D_
Procedure_x000D_
Configuration and development of customer-specific user interfaces, such as
SAP Fiori UX or Screen Personas._x000D_
Development of user interfaces follows in general the procedure described
in the task before:Technical Design DevelopmentUnit Test_x000D_
Examples: Extend an existing SAP Fiori App Configuration,
hide / add fields by use of configuration framework, UI enhancements using
backend configuration Enhancements through Fiori extension points
UI changes & backend extensions; change of "look & feel" and backend
functionality of a standard application Full screen modifications
UI enhancements using functional customizations Development of new
Fiori Apps Create new FIORI launch pads and catalogues_x000D_
SAP supports this activity with the “Fiori Enhancement Pack” service or with
SAP Custom Development. These services are not part of the SAP Value
Assurance, but are available as an SAP Professional Service offering._x000D_
SAP Value Assurance offers the “Technical Performance Optimization”
service component: This service component can also deal with the
performance of your Fiori applications, with the following focus points:
Interfaces & Integration (ODATA Services) and Code Check & Best Practices
(SAPUI5 / Fiori Frontend). Typically, the service starts with baseline
measurements, followed by an iterative optimization & tuning phase. See
activity “Integration Validation” in this phase for more details._x000D_
Look up the SAP Blog “SAP S/4HANA -; How to Create and Generate Back-
end Security Authorizations for SAP Fiori 2.0” which provides a step-by-step
instruction on how to create and generate SAP Back-end authorizations for a
SAP S/4HANA system based on SAP Fiori 2.0 Front-end Server Catalog
information. In the accelerator section, you will also find an SAP Blog series
from the SAP RIG team on how to deal with user default values in the
context of SAP Fiori apps, and how to troubleshoot SAP Fiori apps.
_x000D_
For development requirements exceeding a certain threshold (which is
project specific) or considering those as critical for the project, it is
recommended to manage those as custom developments._x000D_
Procedure_x000D_
Custom development follows in general the same procedure as described in
the task Development of WRICEF objects: Technical Design
DevelopmentUnit Test_x000D_
With SAP’s IBSO SAP is able to develop one-of-a-kind solutions that help you
thrive in the digital economy. Conceptualize, design, build, and maintain
custom applications that run on any device -; and in on-premise, cloud, or
hybrid environments -; with help from the SAP IBSO team. Speed mission-
critical app development with agile development methods and by reusing
existing software Develop on a variety of SAP platforms, including those
from SAP companies Hybris, Ariba, and SuccessFactors Be a leader in your
industry with individualized solutions that support innovation and the
continuous transformation of your business_x000D_
_x000D_
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.
_x000D_
The purpose of this task is to demonstrate the results of the sprint to the
product owner team, key users and key project stakeholders. The results of
the demo are either acceptance of the backlog item or in case the feature is
not accepted, the user story is amended by the product owner team,
prioritized, and remains in the product backlog ready for next sprint planning
meeting. The demo in sprint review meeting serves as an input to formal
sign-off for the sprint.
_x000D_
The purpose of this task is to obtain formal acceptance and signoff of the
sprint results following the sprint review meeting. The product owner team
is the party that provides the sign-off to the project team. In case some
features are not accepted they are brought back into the product backlog as
requirement, properly prioritized and included in planning for the next
sprint.
_x000D_
In the security implementation activity, the customer specific results from
the Security Design phase are implemented. All required and planned
security tasks are now initiated._x000D_
Procedure Implement security
_x000D_
In the security implementation activity, the customer specific results from
the Security Design phase are implemented. All required and planned
security tasks are now initiated._x000D_
Procedure Implement security
_x000D_
Based on the analysis conducted in the Explore phase of the project (see
activity Data Volume Design), Data Volume Management is configured in the
Realize phase of the project._x000D_
This activity is required for all scenarios. Prerequisites are as
follows._x000D_
Prerequisites for Data Aging are as follows: The DVM strategy has been
adapted in agreement with the business, to include the options SAP
S/4HANA offers for data archiving and data aging The development system
is already converted to SAP S/4HANA. In case you would like to use data
aging, you have switched on the data aging (DAAG_DATA_AGING) business
function. In addition, you have entered profile parameter abap/data_aging.
You are familiar with data aging procedure, and the limitations around
data aging._x000D_
The following table gives an overview on available data aging
objects._x000D_
_x000D_ _x000D_
If not already Aging
startedObject Availability
earlier in the project (see task Cleanup or archive data
_x000D_
in the Prepare phase): In this task you clean up or archive data in the
productive SAPApplication Logs it gets converted).
system (before SAP NetWeaver 7.40 SPS 08section
See the accelerator
for a procedure _x000D_
description._x000D_
Requirements Intermediate Documents (IDocs)
and Constraints_x000D_ SAP NetWeaver
7.40 task
This SPS 08 _x000D_
is of particular interest in case of a system conversion
scenario._x000D_ Change Documents SAP NetWeaver 7.40 SPS 12
There is a documented _x000D_
strategy on DVM, which defines the residence time
Workflow
definition of business data._x000D_ SAP NetWeaver 7.40 SPS 12
Data volume_x000D_
planning (as part of Transition Planning activity) has indicated
the need for dataFI Documents SAP Simple Finance add-on 1.0
cleanup and archiving._x000D_
_x000D_
Cleanup or archiving has not started yet._x000D_
Procedure_x000D_ Unified Journal Entry SAP S/4HANA Finance 1503
SPS 03 as follows:
Proceed Archive business data as defined in the DVM strategy.
Set up the write SAPand
S/4HANA -; 1511
delete jobs update in the DVM Best
as described _x000D_
Practice Guide
Material Documents
(accelerator section). Run housekeeping jobsSAP e.g.S/4HANA - 1511
on the SAP Spoolupdate
_x000D_in the DVM Best Practice Guide (accelerator
environment as described
section)._x000D_ Purchase Order SAP S/4HANA -; 1610
_x000D_
Results_x000D_
_x000D_
The goal of this task is to configure data archiving and data aging as
described in the SAP Help Portal._x000D_
Procedure _x000D_
Configure data archiving and data aging as described in the SAP Help Portal
(see accelerator section)._x000D_
Results_x000D_
Data archiving and data aging has been configured for the business objects
in scope._x000D_
SAP can perform this task with the “Data Aging Configuration” scope option,
which is part of the “Build Execution” service. The scope option provides
knowledge transfer, and data aging is configured and executed in a test or
QA system. Based on this task the application team can agree on residence
times, (i.e. at which point in time can business data be aged). The outcome
of the service component is an agreed configuration ready to be transferred
to production, and a skilled customer team. Please ask your SAP contact (e.g.
SAP Client Partner) for more information.
_x000D_
After you have configured data archiving and data aging, you can test your
configuration as described in the SAP Help Portal._x000D_
Configuration of data archiving and data aging has finished_x000D_
Procedure _x000D_
Test your data archiving settings._x000D_
Test data aging as described in the SAP Help Portal (see accelerator
section)_x000D_
Results_x000D_
Data archiving and data aging has been configured and tested successfully
for the business objects in scope.
_x000D_
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._x000D_
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”)._x000D_
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._x000D_
Besides others, IV addresses the following aspects:_x000D_
Data consistency:_x000D_
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 must be
monitored._x000D_
Business process monitoring and exception management: _x000D_
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._x000D_
Performance and scalability: _x000D_
Response time for defined critical transactions should be lower or equal to
_x000D_
The goal of this task is to identify the scope of Integration Validation in the
context of the implementation of new functionality or embedded
solutions._x000D_
Procedure _x000D_
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._x000D_
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:_x000D_
The critical core business processes, including all relevant interfaces and the
underlying software landscape_x000D_
Volumes of data to be processed for the critical business process, including
peak volume_x000D_
Performance KPIs (transactional, batch, and batch window)_x000D_
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._x000D_
See accelerator section for more details._x000D_
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._x000D_
However, in the context of an implementation of new functionality or an
embedded solution, Integration Validation is usually focusing on
performance related aspects of newly implemented core business
functionality._x000D_
Results_x000D_
The scope of Integration Validation in the context of the project has been
_x000D_
Based on the IV scope which has been defined before, the goal of this task is
to initiate the corresponding support activities._x000D_
The scope of IV has been defined._x000D_
Procedure _x000D_
Initiate appropriate IV activities for your implementation project. In case SAP
supports the implementation via SAP Value Assurance service components
are provided like those listed under “How SAP can Support”._x000D_
Performance optimization is often an IV topic. Customers should study the
collective SAP note 2689405 - FAQ: S/4HANA Performance Best Practices for
known SAP S/4HANA problem areas and resolution proposals. Regarding SAP
HANA, SAP note 2000000 - FAQ: SAP HANA Performance Optimization is
recommended._x000D_
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 Performance Optimization
service component: When response times are not meeting business needs -;
sometimes despite extensive hardware, the service component analyzes
critical business process steps and recommends how to optimize them.
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. Interface
_x000D_
The SAP GoingLive Check safeguards your SAP solution to a smooth start of
production, which is the final milestone of a successful implementation
project. The goal of this task is to request the right SAP GoingLive
Check._x000D_
The SAP GoingLive Check is recommended for all scenarios._x000D_
Procedure _x000D_
There are three different SAP GoingLive Checks available: SAP OS/DB
Migration Check _x000D_
This check is for system conversion scenarios, where the start database is on
any database except SAP HANA._x000D_
SAP Enterprise Support customers can use the Continuous Quality Check
(CQC) OS/DB Migration Check instead. SAP GoingLive Functional
Upgrade Check _x000D_
This check is for system conversion scenarios, where the start database is on
SAP HANA. _x000D_
(CQC) for Upgrade instead. SAP GoingLive Check _x000D_
This check is suitable for new installations. _x000D_
(CQC) for Implementation instead. _x000D_
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._x000D_
See the “Realize” and “Deploy” learning journeys for more information.
Schedule the appropriate service for the SAP system, and additionally for the
SAP Gateway in case it runs as a separate instance._x000D_
Results_x000D_
You have successfully requested the correct SAP GoingLive Check._x000D_
The SAP TQM will order the correct check for you. Customers without TQM
can contact the SAP CIC for ordering.
_x000D_
For large systems, the conversion using standard tools may exceed the
available downtime window. In this case the “Minimized Downtime Service
(MDS)” service from SAP Professional Services supports performing the
conversion within the given constraints. This method uses a clone of the
production system for performing the conversion activities outside of the
production and in parallel, records the changes on the production system.
These changes are replicated to the target system after the completion of
the conversion on the clone system. An appropriate preparation of this
method for the production cut-over requires the corresponding verification
of the end-to-end procedure in so called Load & Verification runs. These
activities are planned along the project and using data from the production
system, they are mocking the cut-over steps. During these runs the
validation of the procedure is done and the final timings for the production
cut-over are determined._x000D_
For new implementations, this activity develops, implements, and tests the
data migration programs and processes defined in the Explore phase. This
activity consists of iterative development and testing cycles focused on the
analysis of data, refinement of business rules, and deployment of migration
programs and processes designed to move, cleanse, transform, and enrich
legacy data required to support the various test cycles and ultimately the
production cutover. The test cycles enable the migration team to improve
data quality to an acceptable production level, develop a detailed cutover
sequencing plan, and exercise data reconciliation and validation processes
required to support the production cutover._x000D_
In case of selective data transition, the tasks within this activity largely
depends on the scenario. In case of client transfer, system merge, company
code transfer harmonization and adjustment tasks (e.g. for customizing and
repository objects) need to be performed before data can be successfully
transferred. Test runs ensure that the target state is consistent._x000D_
Procedure Legacy Data Migration (New Implementation)_x000D_
or Perform Load & Verification Runs (System Conversion)_x000D_
or Perform Client Transfer (Selective Data Transition -; Client Transfer)
Perform System Merge (Selective Data Transition -; System Merge) Perform
Company Code Transfer (Selective Data Transition -; Company Code Transfer)
_x000D_
The purpose of this task is to develop, implement, and test the data
migration programs and processes defined in the Explore phase. This task
consists of iterative development and testing cycles focused on the analysis
of data, refinement of business rules, and deployment of migration programs
and processes designed to move, cleanse, transform, and enrich legacy data
required to support the various test cycles and ultimately the production
cutover. The test cycles enable the migration team to improve data quality to
an acceptable production level, develop a detailed cutover sequencing plan,
and exercise data reconciliation and validation processes required to support
the production cutover._x000D_
Procedure _x000D_
Proceed as follows: Develop the specific architecture, programs, and
processes that support the extraction, validation, harmonization,
enrichment, and cleansing of the legacy data based on the data migration
specifications from the Explore phase (see activity Data Migration Design).
The programs and processes directly depend on the tools and utilities
deployed and available for the engagement. These deliverables can range
from fully automated programs based on an extract, transform, and load
(ETL) software platform to a series of manual processes based on tools such
as Microsoft Excel and Microsoft SQL Server. Provide source legacy data in a
format that supports the standard SAP load utilities or data readily available
for manual creation in the new system Also provide templates and
instruction for data loads. Execute multiple test rounds of data migration.
Obtain data migration test results (see accelerator section):_x000D_
The purpose is to obtain the results of the various test cycles so the team
can monitor the accuracy and efficiency of the data migration solution. The
data migration test results are statistics that provide a detailed account of
data load issues and successfully loaded data. The metrics should be
available at summary and detailed levels. The test results are a
subcomponent of the overall test reporting process. By completing this task,
the project team gains visibility into the progress for each of the data
migration iterations and gains the information to determine the level of
readiness of the data. The test results can be stored in SAP Solution Manager
to track the issues history and progress. Conduct final data quality
assessment:The purpose is to provide one final assessment at the end of the
Realize phase to report on the quality of the loaded data.Once all tests and
queries have been conducted, the data migration team compiles the results
_x000D_
The Load & Verification Run is a task, which belongs to the best practice of
the SAP Downtime Minimization Service._x000D_
This task is always planned in projects using the clone based Near-Zero
Downtime method._x000D_
In general, two Load & Verification Runs are performed within the
“Minimized Downtime Service”:Run 1: _x000D_
During this run, the correctness of the conversion procedure is verified
based on the data from the production system. Therefore, it is a very realistic
simulation of the actual cut-over. It includes: efficient creation of
the production clone correct conversion of the system to SAP S/4HANA
on the clone appropriate recording of changes on the production
system correct and efficient synchronization of the recorded data
detailed verification of the final conversion result _x000D_
This run offers an opportunity to create the detailed and realistic step
description (runbook) including actual system names and timings for the
execution of the procedure in the production cut-over. Run 2:
_x000D_
This run is the second iteration of the Load & Verification Run. It belongs to
the best practice of the SAP Downtime Minimization Service. This task is
always planned in projects using the clone based Near-Zero Downtime
method. This is the final end-to-end verification of the cut-over procedure
including the technical and human aspects. In this run all parties planned for
the production cut-over are involved. The dress rehearsal is executed based
on the runbook finalized in the Load & Verification Run 1. Besides the
confirmation of items verified in the first run it provides information about:
detailed timing of the individual steps finalization of the
required hand-over procedures _x000D_
The findings of this run provide information for the fine tuning of the
runbook._x000D_
Based on the both Load & Verification Runs the risks in the production cut-
over can be considerably reduced. _x000D_
Results_x000D_
As the result the production cut-over is executed according to the well
described and practiced procedure.
_x000D_
The “Client Transfer” service component as part of the “Data Migration
Execution” service helps customers to move clients from one SAP instance to
an SAP S/4HANA system. The SAP Landscape Transformation client transfer
functionality used in this service component moves one or more complete
clients (including customizing, master,and transactional data) from one or
more sender systems to a single SAP S/4HANA receiver system. It allows
customers to combine consolidation, upgrade, Unicode conversion and
database change to HANA in one step. In addition, it ensures process
continuity and can consolidate data from more than one sender system in
the SAP S/4HANA system._x000D_
However, because a client transfer affects many areas in your system
landscape, it can be realized only if the repository and client-independent
customizing and settings are compatible at system level._x000D_
The client transfer analysis which is part of the Landscape Transformation
Assessment service component (see Explore phase) reveals any data
conflicts and determines all data that requires harmonization at system level.
The activity is only relevant in case of landscape transformation scenarios,
where clients need to be transferred across systems._x000D_
Procedure _x000D_
Proceed as follows:_x000D_
1.Perform Cross-Client Customizing Harmonization_x000D_
In this task, customers harmonize the cross-client customizing for the
following areas: Basis, cross application and additional topics Logistics
Accounting_x000D_
2.Perform Repository Harmonization_x000D_
The goal of this task is the harmonization of the sender system and the SAP
S/4HANA receiver system repositories: Use the repository comparison
results from the Data Migration Assessment service component to define the
repository harmonization activities.Note that additional harmonization
activities are necessary if a Unicode conversion is required. Business process
requirements of the sender and SAPS/4HANA receiver systems, as well as
any redesigned business processes can be relevant for harmonization.
Determine the required harmonization strategy for the relevant objects, and
also define the technical procedure for the harmonization strategy (the steps
involved). For complex conflicts without a standard harmonization
strategy, also create specifications. Create design documents for the
specifications, if required. Plan the necessary activities for implementing
_x000D_
The SAP Landscape Transformation system merge methodology used in this
service merges business data of two or more clients from one or more
sender systems to a single, empty SAP S/4HANA receiver system. It allows
you to combine consolidation, data model conversion, Unicode conversion,
and database changes to HANA in one step. In addition, it ensures process
continuity and can consolidate data from more than one sender system in
the SAP S/4HANA system._x000D_
However, because a system merge affects many areas in your system
landscape, it can be realized only if the repository, client-independent and
client dependent customizing and settings are compatible at system level
and at client level._x000D_
The system merge analysis carried out during the data migration Design
reveals any data conflicts and determines all data that requires
harmonization at system and at client level._x000D_
This chapter describes only the tasks relevant for the execution of the tasks
specific for the LT scenario. Other tasks relevant for moving to SAP S/4HANA
are still relevant, such as topics to be addressed as outcome of the SAP
Readiness Check for SAP S/4HANA._x000D_
Procedure _x000D_
Proceed as follows: _x000D_
Create future development and production systems _x000D_
The future development system for the SAP S/4HANA or S/4HANA Finance
landscape can be created in two ways: Installation from scratch
LT shell creation as a copy of repository and Customizing out of one
of the existing systems _x000D_
The missing Customizing and repository from the additional source systems
and also the future Customizing resulting out of the harmonization blueprint,
need to be implemented manually in the target development system.
_x000D_
The target test systems and future production can either be created out of
the development box. Alternatively it can be created in the same way as
described above and then supplied with the customizing and repository
delta by transports. _x000D_
Perform cross-client customizing harmonization _x000D_
The objective is to harmonize the cross-client customizing for the following
areas: Basis, cross application, and additional topics Logistics
_x000D_
The Company Code Transfer service helps you to transfer company code
related data from the ECC 6.0 system in use to a new, empty SAP S/4HANA
system. It is a service covering a selective migration of company
codes._x000D_
The following use cases can be differentiated: Company Code Transfer
(Complete History): The data migration covers master data and
transactional data, optional also Customizing Full data history will be
migrated Customer-specific tables can be handled as well
Company Code Transfer (Shell): Company code Customizing is
covered, and optional master data Customer-specific tables can be
handled as well _x000D_
Procedure _x000D_
Proceed as follows: _x000D_
Check tables in use _x000D_
Especially customer-specific tables have to be evaluated and discussed in
regards to selection and migration rules. Afterwards they have to be added
to the tool to make sure they are in scope of the data migration. This task
will be supported by analysis tools provided by SAP. _x000D_
Alignment of Target Organizational Structure (only Relevant for Company
Code Transfer Shell) _x000D_
The objective is to align the organizational structure in the target.
_x000D_
The full history company code transfer migrates data without any changes. If
only a shell of a company code has to be moved, the target organizational
structure has to be defined. _x000D_
Example:Source system: Company code 1000 has two plants: 1100 and 1200.
In the target system it should look like: Company code 1000 with three
plants: 1500, 1600,and 1700. _x000D_
Perform dictionary and repository harmonization during the project
_x000D_
The objective is to harmonize dictionary and repository between source and
target. _x000D_
Company code transfer projects last several months. In this time frame
changes are usually applied to the source system. To make sure that all
relevant data will be moved during the different test cycles and especially
during go-live, it is essential to keep dictionary and repository of source and
target
_x000D_system in sync. _x000D_
This activity implements the required quality level for custom
coding.Procedure_x000D_
Establish / Adjust Custom Code Quality
_x000D_
The objective of this task is to establish custom code quality as part of the
SAP S/4HANA implementation project.Procedure_x000D_
Before development starts (see activity Product Enhancements in this
phase), SAP recommends establishing the required quality as part of the
software development process._x000D_
Aspects which should be considered: Create / enrich / update your
development guidelines for SAP S/4HANA, SAP HANA and SAP Cloud.
Empower and train your development teams according to your development
guidelines. Ensure the new / changed rules and regulations are checked in
your development process (e.g. via peer quality reviews, periodic use of the
ATC)Enable custom development quality measures in your software
development process (e.g. to limit the number of SAP modifications) Support
the future readiness of your code, e.g. by using cloud extensions, or white-
listed API’s Constantly rethink and question your custom code concept to
enable a modern and innovative custom development environment.
_x000D_
In the activity integration implementation, the customer specific integration
design from the Explore phase is implemented._x000D_
Procedure_x000D_
This activity should be executed in close cooperation with the Configuration
and Product Enhancement activities of the Application: Design &
Configuration work stream._x000D_
The activity is structured into two tasks: Implement the integration design
Validate integration implementation_x000D_
Results_x000D_
As the result of the integration implementation the integration design has
been fully implemented and validated.
_x000D_
The integration design documents the planned concept in order to realize
the integration architecture requested by the customer._x000D_
This may require the following types of activities: Configure and customize
SAP standard integration Implement existing best practice scoping items
for specific integration scenarios Develop new or enhance existing
development objects (i.e. interfaces) as defined in the integration
design_x000D_
The integration activities have been fully defined and documented (i.e. write
technical design/WRICEF). See activity Integration Design in the Explore
phase. All required activities have been included in the project
schedule._x000D_
Procedure Realize the integration activities as planned Unit testing of
implemented integration activities Document the results of the integration
activities implementation_x000D_
Results_x000D_
As the result of the integration implementation all the planned and defined
integration activities are initiated and in realization._x000D_
SAP supports this activity with the “WRICEF Developments” service as part
of SAP Professional Services.
_x000D_
The objective of integration validation is to ensure technical readiness of the
entire solution for Go-Live. It includes analysis of critical business processes
and interfaces validating scalability, performance, data consistency and
exception management. A comprehensive status (at least on monthly basis)
of technical go-live readiness for core business processes (integration
validation matrix) is recommended._x000D_
This topic is already handled in detail in this road map in the activity
Integration Validation._x000D_
See activity Integration Validation in the Realize and Deploy phase._x000D_
Procedure_x000D_
See activity Integration Validation in the Realize and Deploy phase._x000D_
Results_x000D_
As the result of this activity, integration validation activities have been
planned, documented and initiated. They will continue across the Deploy
phase._x000D_
SAP supports this activity with the “Integration Validation” service
component.
_x000D_
This activity implements and configures the analytics architecture as part of
the transition project. SAP has plans to describe this activity in detail in
future. Furthermore SAP has plans to support this activity with an “Analytics
Execution” service. Within this activity, this version of the road map
describes the implementation of the SAP Digital Boardroom._x000D_
The configuration of SAP Analytics Cloud SAP Digital Boardroom is based on
SAP Best Practices packages, and on results of other service components like
“Content Orchestration for SAP Digital Boardroom” in the Explore
phase._x000D_
Procedure Configure Analytics & Digital Boardroom
_x000D_
The objective of this task is to configure analytics and the SAP Digital
Boardroom._x000D_
Procedure_x000D_
Configure analytics functionality as designed in the Explore phase._x000D_
In case of the SAP Digital Boardroom, SAP recommends to implement this
product together with SAP (see section How SAP Can Support)._x000D_
SAP offers two “Quick-start services” from SAP Professional Services: Quick-
start service for SAP Analytics Cloud: This service helps our customers to
have a quick implementation for using SAP Analytics Cloud. Quick-Start
Service for SAP Digital Boardroom: This service helps customers to have a
fast start for using SAP Digital Boardroom based on SAP Analytics
Cloud._x000D_
The “Implementation of Analytics with SAP S/4HANA” service is also from
SAP Professional Services. The service enables customers to get started with
SAP S/4HANA embedded analytics, and integrate with best in class analytical
platform and solutions from SAP (like SAP BI platform, SAP HANA Cloud
Platform, SAP BW and SAP Analytics Cloud). The service component:
Identifies any major prerequisites Defines project phases to be used
Validates and demonstrates the solution in a workshopProvides an
implementation example Provide knowledge transfer to key users for the
SAP Best Practice processes._x000D_
In case customers are interested in setting up a digital boardroom, SAP
recommends to study the information on the SAP Digital Boardroom which is
available in the Public Web as a first step. See Accelerator’s section for
details. In particular, and highly recommended, SAP has provided an
“Implementation Check List” for the SAP Digital Boardroom, which provides
information on the general concept, SAP Digital Boardroom content and the
setup._x000D_
SAP offers a “Content Orchestration for SAP Digital Boardroom” service
which is delivered by SAP Professional Services. This service helps customers
to identify and harmonize the KPIs and master data that are relevant for a
successful implementation of SAP Digital Boardroom. Customers can contact
the Client Partner for ordering details._x000D_
Through it SAP provides recommendations to customers to:Run a real-time
analytics scenario during board meetings to understand company-wide
business situations and make decisions based on facts. Visualize the top KPIs,
_x000D_
The objective of this task is to train business analysts and end users on the
SAP Analytics Cloud and SAP Digital Boardroom._x000D_
The SAP Digital Boardroom has been set up and configured._x000D_
Procedure_x000D_
The SAP Digital Boardroom is a new product. SAP recommends to implement
this product together with SAP (see section How SAP Can Support)._x000D_
SAP offers the “Enablement service for SAP Analytics Cloud and & SAP Digital
Boardroom” service from the SAP Professional Services organization. The
intent of this service is to: Support project team members with the required
knowledge of SAP Analytics Cloud and SAP Digital Boardroom. Familiarize
key users with SAP Analytics Cloud and SAP Digital Boardroom
functionalities._x000D_
In sum this service component is a five day engagement. 3 days thereof are
being used to work with the customer onsite on their SAP Analytics Cloud
System. The remaining 2 days are being delivered remotely to answer
questions from customers related to the training exercises._x000D_
The onsite part is structured into: A hands-on training session for data
loading and connecting to one SAP HANA database. A hands-on training
session to create models, visualizations, and stories for SAP Analytics Cloud.
A hands-on training session to create agendas for SAP Digital
Boardroom.
_x000D_
The purpose of this activity is to prepare all business-process-related tests
according to customer- specific configurations._x000D_
Tasks Prepare Tests_x000D_
SAP supports this activity with the “Test Preparation” scope option as part of
the Build Execution service. This scope option component assists the
preparation and planning of the Integration and User Acceptance tests for all
business areas based on the customer specific configurations. The test
framework, defined in the test planning service during the Build Design
phase, determines the scope for this service component. Please see “SAP
Advanced Deployment” link below and ask your SAP contact (e.g. SAP Client
Partner) for more information.
_x000D_
As determined in the evaluation of the existing test materials and
documented within the testing plan, additional assets may need to be
developed to support the execution of the testing cycles. Develop the
missing test materials and test scripts in accordance with the detailed test
plan._x000D_
Procedure _x000D_
Within in each implemented solution scope, the following steps need to be
executed: Extend best-practice test cases Develop delta process test
cases Finalize integration and user-acceptance test cases and plan
Prepare approval procedure Prepare tool adaption and delta user
acceptance test training_x000D_
The best-practice test scripts are part of the solution scope description and
can be found in SAP Best Practices Explorer. See the screen shot figure for an
example. Please note that test scripts -; together with a process flow
diagram -; are provided per scope item._x000D_
_x000D_
See accelerator section for the link to the screen above.
_x000D_
In this activity, integration test, regression test and user acceptance test take
place._x000D_
The unit test has been done as part of the development process in the DEV
system already._x000D_
Procedure _x000D_
Prepare a test environment with the required test data as defined in the
activity Test Planning._x000D_
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 must 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._x000D_
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._x000D_
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._x000D_
_x000D_
The goal of this task is to perform an integration test, regression test and
user acceptance test._x000D_
Procedure _x000D_
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._x000D_
How to proceed for Integration Test: Prepare Integration Test plan:_x000D_
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. Prepare and document
Integration Test Case #1 -; n:_x000D_
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. Execute Integration Test Case #1 -;
n:_x000D_
Perform the Integration test according to the previously defined plan. During
test execution all issues must be logged and documented in the system for
traceability purpose. Perform defect resolution for Integration
Test:_x000D_
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. Obtain Integration Test Sign-
Off:_x000D_
Obtain customer approval (sign-off) of the integration test._x000D_
_x000D_
The transition to the new system may impact productive business processes
following even a successful cutover. 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._x000D_
How to proceed for Regression Test: Prepare a detailed regression test plan
with test cases and test scripts. Set up test management procedures to track
_x000D_
This activity sets up a quality assurance environment (QAS). It depends on
the scenario how this is done._x000D_
Please note: This road map documents the setup of a DEV and a QAS system.
Of course, the design of the production support landscape depends on
customer requirements for change management. Additional supporting
systems may need to be set up (e.g. pre-production or training). In those
cases, the project plan template needs to be adjusted accordingly._x000D_
which need to be installed / updated._x000D_
The DEV environment has been set up successfully._x000D_
Procedure QAS Setup (New Implementation)_x000D_
or QAS Setup (System Conversion)_x000D_
Once the QAS system is available, please check the integration setup as
documented in the Integration design activity (see also activity Integration
Implementation in this phase for more information)._x000D_
basket, and creates a control file (“stack-xml”), which is later on required for
the conversion and installation tools. The Maintenance Planner has been
section for details._x000D_
SAP offers the provisioning of the QAS environment for both scenarios as
part of the “Platform Execution” service. Please ask your SAP contact (e.g.
SAP Client Partner) for more information. This is a dedicated scope option
(System Conversion for SAP S/4HANA and System Installation for SAP
S/4HAHA). The setup of the technical Fiori components is covered by scope
option SAP Fiori Platform Setup. See accelerator section for more
information. However, the configuration of the Fiori UIs is not included in
this scope option but is part of the functional setup.
_x000D_
quality assurance environment that is available for use by the project team
to test configuration and development in a “production like”
environment._x000D_
Procedure_x000D_
Proceed as follows: Execute the technical installation of the required SAP
Products for QAS environment as documented in the technical design
document. See the “Installation Guide for SAP S/4HANA” how to install the
components. Run the technical system setup as documented in the
“Administration Guide for the Implementation of SAP S/4HANA”.
Transport development and configuration changes from DEV to QAS.
Consider also the manual rework activities as described in the
“Administration Guide for the Implementation of SAP S/4HANA”. Check
to what degree the Fiori apps require additional configuration in
QAS._x000D_
Results_x000D_
Finally, the QAS environment is ready for testing._x000D_
SAP offers the installation of a QAS as part of the Platform Execution service.
This scope option is called “System Installation for SAP S/4HANA” -; see
accelerator section for more information. The setup of the Fiori platform can
be supported as well (scope option “SAP Fiori Platform Setup”). However,
the configuration of the Fiori UIs is not included in this scope option but is
part of the functional setup.
_x000D_
The goal of this task is to provide a viable, correctly configured quality
assurance environment that is available for use by the project team to test
configuration and development in a “production like” environment. QAS is
not installed as new -; instead, the old QAS system is converted to SAP
S/4HANA._x000D_
The prerequisite is that the migration approach has been validated in a
sandbox environment (see activity SANDBOX System Setup / Conversion in
the Explore phase), a detailed migration plan is in place, and the required
hardware for hosting the SAP S/4HANA DEV system is already available and
set up._x000D_
Furthermore, the cleanup of the productive system is already underway or
has been finished (see tasks Clean up or Archive Data in the Prepare and
Realize phases for details)._x000D_
Procedure _x000D_
Convert the QAS system according to the migration plan (which is based on
the “Conversion Guide for SAP S/4HANA”). Depending on the transport
landscape configuration, there may be a need to perform multiple iterations
of the conversion to solidify and finalize the cutover plan. Executing test
migrations will validate the end-state of the conversion, as well as provide
the figures for expected system downtime (see activity Downtime
Optimization Preparation for details). Depending on the approach and the
transport landscape configuration, there may be a requirement to execute
additional sandbox conversions to optimize the cutover procedure._x000D_
Transport development and configuration changes from the new DEV to
QAS._x000D_
Check to what degree the Fiori apps require additional configuration in
QAS._x000D_
Check the SAP Note 2669901 -; SAP S/4HANA 1809 -; application specific
notes in system conversion/upgrade follow-on phase._x000D_
Results_x000D_
Finally, the QAS environment has been converted to SAP S/4HANA. It is
ready for further configuration._x000D_
SAP offers the QAS conversion as part of the “Platform Execution” service.
This scope option is called “System Conversion to SAPS/4HANA” -; see
_x000D_
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.Requirements and Constraints_x000D_
This activity is optional for all scenarios._x000D_
There is a documented sizing estimation from the Explore phase stored in
SAP Solution Manager.Procedure Optional: Perform Sizing
VerificationOptional: Perform Scalability Verification
_x000D_
The goal of this task is to validate the sizing estimation from the Explore
phase based on the planned application design._x000D_
There is a documented sizing estimation from the Explore phase stored in
SAP Solution Manager._x000D_
There is a pre-production system already available._x000D_
Procedure _x000D_
To validate the sizing projections, SAP proposes a two-fold approach:Load
testing of the pre-production systemWorkload analyses across all systems on
the critical path in production._x000D_
The latter is based on technical resource consumption monitoring, the sizing
report and application workload analysis._x000D_
Results_x000D_
The sizing estimation for the productive system has been validated._x000D_
SAP can perform this task with the “Advanced Sizing” service component.
_x000D_
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 must be compared against the
predefined performance baseline._x000D_
There is a test system available which has comparable hardware with the
future productive system._x000D_
Procedure _x000D_
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.Define the success factor for the load tests Perform
mass load testing Report and review process Optimization, Re-design and
Re-test identified components according to the predefined performance
baseline Communication of the results and possible changes in the
production environment_x000D_
The results will be measured over the defined timeframe and compared to
the baseline._x000D_
Results_x000D_
The performance gain has been properly measured and documented in SAP
SAP can provide support for the test and optimization of the Volume Test,
and/or provide specific business case optimization where required. Please
contact the embedded support team for more details.
_x000D_
In the Realize phase the technical infrastructure must 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._x000D_
A technical design document has been created and stored in SAP Solution
Manager._x000D_
Procedure_x000D_
Set Up IT Infrastructure Test IT Infrastructure_x000D_
Results_x000D_
The technical infrastructure has been properly tested.
_x000D_
The goal of this task is to set up the IT infrastructure. It covers (besides
others): 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._x000D_
_x000D_
The IT infrastructure components are available and ready for setup._x000D_
Procedure_x000D_
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._x000D_
The IT infrastructure is often setup by the hardware partner._x000D_
Results_x000D_
The IT infrastructure is set up.
_x000D_
Once set up, the IT Infrastructure should be tested thoroughly._x000D_
The IT infrastructure has been set up._x000D_
Procedure_x000D_
Proceed as follows: Execute the infrastructure tests based on the test
cases and test plan. This should include the following scenarios:
Performance Flexibility procedures (e.g. by moving system load to other
hosts (e.g. by using virtualization technics), adding instances, changing
instances) High Availability Disaster Recovery Backup and
Restore 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._x000D_
Results_x000D_
The IT infrastructure has been tested properly.
_x000D_
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._x000D_
The documented results of the Operations Impact Evaluation (Explore phase)
are stored in SAP Solution Manager._x000D_
Procedure Collect detailed Operations Requirements Roles and
Responsibilities Support Processes and Procedures Operations Support
Tools Operations Documentation Knowledge Transfer_x000D_
Results_x000D_
IT support operations have been prepared to operate SAP S/4HANA as of Go-
Live._x000D_
How SAP can Support_x000D_
SAP can support this task with the service component “Operations
Implementation”. Based on the outcome of the Operations Impact
Evaluation from the Explore phase, this activity will include all steps required
to fulfill the operational requirements of the target SAP solution in the areas:
“Roles and Responsibilities” “Support Processes and Procedures”
“Operations Support Tools”“Operations Documentation” “Knowledge
Transfer”. _x000D_
Operations Implementation is a collection of operations services. The
detailed content and the effort of Operations Implementation depend on the
results of the Operations Impact Evaluation. See accelerator section for more
details._x000D_
SAP has multiple offerings to SAP Enterprise Support customers with respect
to operations implementation: SAP strongly recommends configuring SAP
EarlyWatch Alert, which provides a comprehensive monitoring report.
Join the Expert Guided Implementations on troubleshooting and
administering the SAP HANA databse. There is information and service
available on security, data volume management, and performance
optimization for SAP HANA, SAP S/4HANA and Fiori._x000D_
You will find all offerings “Realize”, “Deploy” and “Run” learning journeys.
Please check pages periodically, because information and service content is
continuously extended.
_x000D_
The Operations Impact Evaluation main outcome is the definition of a list of
relevant changes to the current support framework with the corresponding
project activities that will support the implementation of those changes. This
list is based on the future customer support strategy and deployment model,
as well as on the current support framework and the solution that is
implemented._x000D_
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._x000D_
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, and potential 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._x000D_
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._x000D_
The Operations Impact Evaluation has taken place and the detailed activities
necessary
_x000D_ to ready the future IT support framework for the operations of the
Whatever the current IT support framework is: Operational activities are
handled by support personnel organized in roles. These personnel belong to
different groups and even different companies when a service provider is
engaged, with responsibilities and skill levels that help them in the execution
of their activities. _x000D_
When you implement SAP S/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
S/4HANA solution), and on your deployment strategy (cloud vs on-
premise).How SAP Can Support_x000D_
SAP has a lot of experience and recommendations on the roles and
responsibilities design including all steps required to define in detail the roles
and responsibilities of the different support resources that are required for
the efficient support of the new solution. Please contact SAP for a tailored
offering in case you need support.
_x000D_
With the implementation of SAP S/4HANA, the IT support processes may
need to be modified to reflect new operational requirements. The changed
IT support processes need to be documented and
tested.Prerequisites_x000D_
are stored in SAP Solution Manager.Procedure _x000D_
The following IT support processes are potentially affected with the
implementation of SAP S/4HANA:Event Management: Analyze process
change in event management caused by new/modified/retired
monitorsRetire obsolete monitors, and monitor templates (in SAP Solution
Manager)Retire obsolete manual monitoring proceduresIncident
Management: Update assignment groups, review incident triage (e.g. for
Fiori support)Update support resourcesUpdate incident categorization
Process flow and escalation management including partners and SAPRemove
obsolete incident attributesProblem Management: Update problem
management process to include new analysis tools_x000D_
Service Level Management: Update SLAs if required (due to changed
business KPIs)Update SLA reporting Access Management:Access for new
solution / tools granted to new support team members including partner
resourcesNew/changed access management process for new/changed
solution items (e.g. SAP HANA database, Fiori)Change Management: Update
support resources including requesters and new approversUpdate
categorization, if requiredProcess flow including partners and escalation
managementInclude project defects in incident databaseRemove obsolete
change attributesEvaluate current change process to include Fiori and SAP
HANA changesTest Management:Test library should include new test
plans/scriptsJob Management: 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: Changed tools and activities due to new concepts in data
volume management (e.g. data aging)Adapt process in those areas where
classic data archiving is no longer availableSystem Recovery: Adapt system
recovery process to reflect the changed HA/DR architecture _x000D_
_x000D_
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). _x000D_
_x000D_
Based on the results of the Operations Impact Evaluation, requirements on
IT operational support tools need to be finalized to safely operate the new
solution (this may also include surrounding components like the Fiori Front
End Server). The tools need to be adjusted or newly set up. Deprecated IT
operational tools need to be carved out, and IT operational procedures must
be adjusted accordingly._x000D_
For “Greenfield” customers, the effort required to implement the tools will
be much higher. This will require additional effort for the support resources
to learn how to use the tools, especially SAP Solution Manager._x000D_
Procedure _x000D_
With the introduction of SAP S/4HANA, it may be required to adjust existing
IT operational support tools (e.g. adjust change management tools to be
able to handle Fiori objects for the first time), or to set up new tools (e.g.
SAP HANA cockpit in case this is the first system on top of SAP
HANA)._x000D_
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. SAP has
dedicated offerings to support this task. Adjust SAP Solution Manager
configuration with respect to: General system management
(“Managed System Setup”) Monitoring elements (e.g. critical interfaces,
critical batch jobs, End-User-Experience, SAP HANA DB), and monitoring
customizing (e.g. alert thresholds) Change Request Management and
CTS+ (e.g. to be able to handle SAP HANA and/or Fiori objects in a
synchronized way) Adjust SAP HANA tools: HANA
Cockpit to manage the SAP HANA database SAP HANA Studio e.g. for
HANA programming, or HANA dictionary SAP DB Control Center for
central & aggregated DB monitoring DBA Cockpit e.g. for running DB
administration activities _x000D_
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.
_x000D_
IT operations documentation should be stored centrally in an operations
documentation repository, which is then shared across all operational
support teams._x000D_
Procedure _x000D_
Adapt all operational documentation that changes with SAP S/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._x000D_
Store the updated operations handbook centrally, either in a company
Content Management System, or in SAP Solution Manager._x000D_
Based on activity Operations Impact Evaluation, and on activity Operations
Support Tools, the operational procedures are updated in the operations
handbook._x000D_
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
_x000D_
The primary goal of this activity is to analyze all the aspects of the
knowledge required to sustain the implementation of the SAP solution, and
to ‘grow and groom’ the future SAP IT support resources to effectively and
efficiently support the solution._x000D_
Additional goals of the strategy are to: 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_x000D_
The objectives of the knowledge transfer are to: Identify roles and
responsibilities involved in the knowledge transfer process Transfer
knowledge, skills and abilities required to provide solution life cycle support
Develop a formal process for monitoring and evaluating the
effectiveness of the knowledge transfer process based on objectives and
performance metrics_x000D_
Procedure _x000D_
To define the Knowledge Transfer Approach for the new solution, 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_x000D_
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
_x000D_ critical reports are available Knowledge transfer is documented
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._x000D_
This activity is required for all activities. However, preparation steps are
scenario specific._x000D_
which
_x000D_ need to be installed / updated._x000D_
Procedure_x000D_
The goal of this task is to provide a viable, correctly configured production
Production
environment thatSystem SetupforCreate
is available use byCutover Planteam
the project (Newto execute final Go-
Implementation)_x000D_
Live simulations. This environment will be used as the future production
or
systemCreate Cutover
(PRD) Plan (System Conversion)_x000D_
as of Go-Live._x000D_
or Create Cutover
Prerequisites_x000D_ Plan (Selective Data Transition)_x000D_
This task is required for those scenarios which set up a new production
SAP can support the creation of a cut over plan as part of the Build Execution
system._x000D_
service. Please
Prerequisite ask your
is that SAP contact
the productive (e.g. SAPisClient
hardware Partner)
already for and
available moreset
information.
up._x000D_
Procedure Execute the technical installation of the required SAP Products
for PRD environment as documented in the technical design document. See
the insalltion guide for 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._x000D_
Results_x000D_
Finally, the PRD environment is ready for final Go-Live simulations._x000D_
_x000D_
The objective of this task is to create the cutover plan. The plan is based on
the learnings from the legacy data migration runs which have been
performed so far._x000D_
Procedure _x000D_
Execute Go Live Simulations 1 -; n_x000D_
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._x000D_
These simulations help determine data load efficiency, timing, and
sequencing and foster an understanding of requirements for the detailed
cutover schedule._x000D_
The number of simulations varies from project to project, so do the
objectives for each simulation._x000D_
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._x000D_
A new implementation may require three simulations: Technical -; Project
team participation only for the purpose of validating steps Dry run -; Full
execution of the cutover schedule with the entire team for the purpose of
validating steps and data Final -; Full execution of the entire cutover
schedule for the purpose of flawless execution to obtain exact
timings_x000D_
Results_x000D_
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._x000D_
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.
_x000D_
The objective of this task is to create the cutover plan. The plan is based on
the learnings from the load & verification runs which have been performed
so far._x000D_
Procedure _x000D_
The conversion of the production system requires a clearly defined cutover
plan and will typically be controlled by a cutover manager._x000D_
You can look up a sample cutover plan for system conversion in the
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:
Prerequisite steps for the production conversion Ramp-down activities (e.g.
batch jobs, interfaces, etc.) Pre-conversion validation reports End-user
lockout Technical migration and business data conversion Post conversion
changes (e.g. transports, parameter changes, etc.) Technical post conversion
validation reports (e.g. checking for business data consistency) Business
driven system validation and comparison of the pre and post conversion
reports Go/No-Go decision Ramp-Up activities (e.g. batch jobs,
interfaces, etc.) User unlock_x000D_
The next picture sequences cut-over activities for a multi-TB SAP ERP system
on a time line (example only, not complete, needs to be adjusted to the
customer specific situation)._x000D_
_x000D_
Figure: General sequence of activities for a multi-TB SAP ERP system during
cut-over weekend_x000D_
Please note: The SUM should start preparation days in front of the real
system conversion. Please make sure mandatory preparation activities like
CVI (see activity Transition Preparation in the Prepare phase for details)
which are check via SI-Checks by SUM have been finished. Otherwise SUM
will stop. SAP’s recommendation is having those activities finished not later
than two weeks before cutover weekend._x000D_
The cutover plan does not detail the technical conversion to the level that is
captured in the cookbook. It is common to highlight specific tasks from the
cookbook within the cutover plan to ensure the process is on
schedule._x000D_
Every task within the cutover plan should have an assigned owner, estimated
duration, and identified dependencies. Whenever possible, assign a name to
_x000D_
The purpose of the “Productive Migration Plan” is to schedule the main
steps for the productive migration as well as to ensure the logistics and the
communication for the productive migration. In addition, a period of hyper
care that follows the go live needs to be planned as well._x000D_
The activity is only relevant in case for selective data transition scenarios,
where clients need to be transferred across systems._x000D_
Procedure_x000D_
It is important to plan the sequence and the dependencies of all technical
steps to be taken for the productive migration. This starts with the closure of
the system for users, the stop of all batch-programs and ends by releasing
the new system._x000D_
It is also important to plan back-up and recovery strategies._x000D_
The necessary technical steps vary depending on the project. Therefore, this
document does not cover every possible step, but focuses on these most
important steps: Closing the sender and S/4HANA receiver system, and
stopping interfaces Performing a backup of the receiver system (this
creates a fallback solution in case the project fails) Preparing final test cases
Activating table count for the sender and receiver system Executing
the migration (details see the task Perform Technical Migration in the
Productive Cutover) Executing post-processing programs Executing the
table counter for the sender and receiver systems again to verify
completeness of the migration Testing Obtaining final approval from the
test team in order to release the system Restarting the interfaces from the
receiver system Redirecting interfaces from the sender system
Releasing system to end users, and communicating the Go Live
status_x000D_
Customers can find further information about the cutover preparation in the
‘Client Transfer’ Product Road Map of SAP Landscape Transformation
software, Refer to phase ‘4 Final Preparation for Productive
Migration’._x000D_
Results_x000D_
Finally the PRD environment is ready for final Go-Live simulations._x000D_
SAP supports the creation of a cutover plan as part of the Data Migration
Execution service. Please ask your SAP contact (e.g. SAP Client Partner) for
more
_x000D_ information.
The purpose of this deliverable is for the project the team to carry out the
planned and approved project work and measures project performance to
identify variances from the plan. Executing manages the scope of the work
to be done, while monitoring the execution, identifies variances from the
plan, monitors quality results, controls progress against the plan, controls
changes throughout the project, assesses and responds to risks, and
communicates project status. _x000D_
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.
_x000D_
The purpose of this task is for the project manager and the project team to
execute the project management plan and to accomplish the work defined
in the project scope statement.In executing the project work, the project
team will perform the following types of activities: Perform project tasks
to reach project objectives Expend effort and funds to accomplish project
objectives Staff, train, and manage the project team members assigned to
the project Obtain, manage, and utilize resources Implement and
execute the planned methods and standards Create, control, verify, and
validate project deliverables Manage the scope of the approved work
Manage risks and implement risk response activities Manage issues to
closure Adapt approved changes into the scope, plans, and project
environment Establish and manage internal and external communications
Collect project data and report on progress and performance In
monitoring/controlling work results, the project team performs the following
types of activities:Compare actual project performance to the project
management planAssess performance to determine whether corrective or
preventive actions are necessary Monitor and control project risks
Provide metrics to support progress and performance reporting and
forecasting Monitor implementation of approved changes Take
corrective action as needed 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.
_x000D_
The purpose of this task is to ensure that the project manager keeps the key
project management documents up-to-date. This task includes refinement of
the project schedule, refinement of the project budget, and appropriate
updates to the management plans, scope document and business case to
reflect the detailed scope information created during the project._x000D_
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._x000D_
This task includes updates to: Project management plan Project WBS
Project schedule Project budget Business caseScope document Backlog
document (created in Explore phase)
_x000D_
The purpose of the Manage Project Issues, Risks, and Changes task is to have
a consistent, comprehensive approach to managing project issues as a
critical component of an effective project management system. Effective
issue management involves the appropriate level of management making
decisions on issues and tracking progress on issue resolution in accordance
with the project issue management procedure. Identified issues are
maintained in one, central environment._x000D_
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._x000D_
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._x000D_
The Issue Management handling involves the following steps: An issue is
raised and properly classified as it is related to the system conversion,
solution implementation, or solution operations of an SAP solution or
technology. It is created in the issue tracking tool, either by SAP, a customer
or a system integrator. 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._x000D_
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._x000D_
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._x000D_
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.
_x000D_
The purpose of this task is to communicate project status and progress.
Throughout the project, several project performance reports need to be
produced for different purposes and audiences, as defined in the project
communication plan. The project manager and project team are responsible
for clearly communicating the progress of the key activities, completion of
the deliverables, and status against the schedule and budget._x000D_
The project teams typically prepare: 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._x000D_
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.
_x000D_
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)._x000D_
_x000D_
Figure: Sprint execution_x000D_
During each sprint the project team conducts the following
activities:_x000D_
Sprint Planning Meeting_x000D_
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._x000D_
Sprint Execution Activities_x000D_
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._x000D_
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._x000D_
Daily Stand-up Meeting_x000D_
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
_x000D_
SCRUM of SCRUMs Meeting is conducted to coordinate the work between
different project SCRUM teams. SCRUM of SCRUMs meetings allows teams
to discuss their work, focusing especially on areas of overlap and integration.
The meeting cadence is defined for the entire project and follows the same
structure. Some teams conduct daily SCRUM of SCRUMs meeting while
others consider weekly meeting sufficient. The main driver for the meeting
cadence is the level of collaboration between the individual SCRUM teams
and level of dependencies between the features built in each SCRUM team.
_x000D_
The purpose of this deliverable is to identify and assess other Organizational
Change Management activities related to the OCM execution plan.
_x000D_
The purpose of this task is to understand the testing strategy, validate its
alignment with the project charter, and to identify any potential roadblocks
or risks associated with functionality not working as expected. Any deviation
from expectations should be communicated to project management and
project sponsors._x000D_
Procedure: Perform Assessment of Testing Strategy and Execution Capture
Feedback from Testing Team
_x000D_
The purpose of this task is to understand the data migration strategy,
validate its alignment with the project charter, and to identify any potential
roadblocks or risks associated with data quality or availability that are not as
expected. Any deviation from expectations should be communicated to
project management and project sponsors._x000D_
Procedure: Perform Assessment of Data Migration Strategy and Execution
Capture Feedback of Data Migration Team
_x000D_
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
_x000D_
project management standards are being upheld within projects. A Quality
Gate is a checklist milestone at the end of a project phase. Prior to moving
into the next phase each project manager demonstrates that they have been
compliant with the mandatory deliverables associated with a methodology
while ensuring best practice standards have been applied to ensure
quality._x000D_
Procedure: 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 project deliverables._x000D_
Note(s): New additional key deliverables need to be added in the quality
gate checklist by the project manager to the different project types.
_x000D_
prioritized and tracked along with other user stories._x000D_
_x000D_
_x000D_
The purpose of this task is to obtain the customer approval (sign-
off)._x000D_
Procedure: Obtain customer approval (sign-off).
_x000D_
Once Q3 -; Realize-to-Deploy has been passed successfully, the final
preparation for Go-Live starts in the Deploy Phase. The activities of the
Deploy phase are displayed in the following figure._x000D_
_x000D_
_x000D_
_x000D_
End users are trained for the new SAP S/4HANA solution in the Solution
Adoption work stream._x000D_
In the Application design and configuration work stream, the
implementation activities will come to an end. Integration validation ensures
the required performance._x000D_
Testing (in particular regression and user acceptance testing) is taken care of
in the 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 Extensibility work stream in the Deploy phase._x000D_
The final rehearsal of the cut-over procedure will take placeThe
implementation of the productive SAP S/4HANA will be finalized (for new
implementation and selective data transition)._x000D_
Operations & support ensures the IT operations team is ready to operate the
new SAP S/4HANA 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._x000D_
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 SAP S/4HANA system with the production cutover at the Go-Live
weekend._x000D_
The weeks after Go-Live are called “Hyper Care”, where the new system is
further stabilized and optimized. When finished, the Deploy phase ends. The
transition project comes to an end when finally, operational responsibility
has been handed over to the production support team._x000D_
Please note: The order activities are explained in this document / road map
viewer, is not necessarily the order how they are later executed in the
project! However, there can be dependencies between activities. In case you
are interested in time dependencies / relationships between activities, look
into the project file template of this road map.
_x000D_
The purpose of the phase initiation deliverable is to formally recognize that a
new project phase starts.
_x000D_
The purpose of this task is to confirm resource availability for the particular
phase.
_x000D_
The purpose of this task is to ensure the involvement of the team and other
key resources and their commitment to the project schedule. The meeting is
also used to examine the approach for the specific project phase.
_x000D_
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._x000D_
The development of learning material has finished._x000D_
Procedure Create Training Execution Plan Execute End User
Training_x000D_
Results_x000D_
The end users have been trained. They are enabled to use the new system.
_x000D_
Create a training execution plan._x000D_
Procedure _x000D_
The training execution plan is based on the results as of the training concept,
the Learning Needs Analysis, and the end user assignment. The training
execution plan should include: The scheduling of the trainings The training
approach and method (as of the concept) The assigned participants
(Key / End Users) Trainer, location, date and time Required training material
(content) Training system information (access information, exercises,
etc.)_x000D_
The training execution plan should include all planned trainings and courses
across the project phases, roles, functions and processes for a complete
overview of all training course activities.
_x000D_
Based on the results of the Learning Needs Analysis and the training
concept, the end user training covers the training needs for all end
users._x000D_
A training execution plan has been created before._x000D_
Procedure _x000D_
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: Language of the trainings (i.e. English).
Maximum number of participants per training course (i.e. max. 12-15
participants). Training location of the training course. Customer SAP
training system_x000D_
Results_x000D_
As a result, end users are trained. SAP recommends issuing participation
certifications, and collecting end user feedback.
_x000D_
The Integration Validation activities initiated in the Realize phase, are
continued and finalized in this activity.Requirements and
Constraints_x000D_
This activity is recommended for all scenarios.Procedure_x000D_
Finalize the Integration Validation activities which have started in the Realize
phase (see activity Integration Validation).Results_x000D_
As the result of this activity, integration validation has been finished.
_x000D_
The goal of this task is to finish IV activities before Go-Live._x000D_
Integration Validation has started in the Realize phase._x000D_
IV is usually executed with SAP participating. The SAP TQM will initiate the
right IV support activities from SAP: 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
Performance Optimization service component: When response times are not
meeting business needs -; sometimes despite extensive hardware, the
service component analyzes critical business process steps and recommends
how to optimize them.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.Interface Management service component: The SAP
Interface Management service component helps analyze and optimize the
performance and stability of critical interfaces as part of business process
steps. Technical Performance Optimization service component: This
service component can also deal with the performance of your Fiori
applications, with the following focus points: Interfaces & Integration (ODATA
Services) and Code Check & Best Practices (SAPUI5 / Fiori Frontend).
Typically, the service starts with baseline measurements, followed by an
iterative optimization & tuning phase. Volume Test Optimization service
component: The SAP Volume Test Optimization service component ensures
that the results of volume testing for implementation or conversion projects
are reliable. With reliable test results, you can determine with confidence
whether your hardware resources are sufficient, and the system
configuration is suitable for a Go-Live. Empowering service component:
This service component supports you in case of general empowering
_x000D_
This activity checks the customer’s ability to operate SAP HANA and SAP
S/4HANA as of Go-Live._x000D_
Procedure_x000D_
Operational Readiness (System Conversion)_x000D_
_x000D_
or Operational Readiness (New Implementation)
_x000D_
In case of a system conversion where the customer operated a productive
SAP ERP system over a longer period of time and standard IT support
processes (e.g. change management, event management) have been
designed and operated for SAP already. Therefore, the customer knows
already how to operate SAP and only the delta to safely operate SAP
S/4HANA needs to be checked._x000D_
Procedure_x000D_
Check if all operational aspects have been implemented as planned (see
Operations Implementation activity in the Realize phase). This covers:
Roles and Responsibilities Support Processes and Procedures Operations
Support ToolsOperations Documentation Knowledge Transfer_x000D_
_x000D_
Results_x000D_
The IT support organization is ready to operate SAP S/4HANA as of Go-
Live._x000D_
SAP offers an “Operations Readiness” check. The scope covers tools for
monitoring, troubleshooting, and software logistics. It also includes a status
review of the IT Operations changes defined during the Operations Impact
Evaluation. Ideally the check is performed a couple of weeks before Go-Live.
_x000D_
In case the customer knows already how to operate SAP ERP, then again only
the delta to safely operate SAP S/4HANA needs to be checked in this task.
However, in case of a new SAP customer, all core IT support processes (as
documented in the SAP Support standards) need to be checked with respect
to SAP S/4HANA._x000D_
Procedure_x000D_
For customers who know how to operate SAP ERP already: Check if all
operational aspects have been implemented as planned (seeOperations
Implementation activity in the Realize phase). This covers: Roles and
Responsibilities Support Processes and Procedures Operations Support
Tools Operations Documentation Knowledge Transfer_x000D_
For new SAP customers: 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 S/4HANA operations (see SAP Support
Standards). Check if primary CCOE certification has been gained._x000D_
SAP offers an “Operations Readiness” check. The scope covers tools for
monitoring, troubleshooting, and software logistics. It includes a status
review of the IT Operations changes defined during the Operations Impact
Evaluation. Ideally the check is performed a couple of weeks before Go-Live.
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.
_x000D_
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._x000D_
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._x000D_
Prerequisite for this activity is: The detailed cutover plan with owners,
dependencies and durations fully documented. The involvement of all
task owners. A test environment representative of the source and target
platforms for production. The technical cookbook, which details all of the
required technical migration steps._x000D_
Procedure _x000D_
Finalize IT Infrastructure _x000D_
Perform Cut-Over Rehearsal _x000D_
_x000D_
Due to cost saving reasons the hardware for production is set up just in front
of Go-Live (system conversion case). In case of a new implementation, it
might be required to have the hardware ready by the end of the Realize
phase (see activity Cutover Preparation). In this activity all remaining items
required to finalize the (productive and supporting) IT infrastructure need to
be completed._x000D_
The goal of this task is the completion of the IT infrastructure setup._x000D_
Procedure_x000D_
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)._x000D_
Results_x000D_
As a result, the IT infrastructure is ready for hosting production.
_x000D_
The goal of this task is to execute an end-to-end dress rehearsal of the
cutover procedures._x000D_
Procedure_x000D_
Execute the cutover plan in its entirety in a non-productive environment,
which is representative of the current state and end-state of
production._x000D_
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._x000D_
It is also very critical to communicate the latest plan to related parties to
ensure a smooth Production Cutover for the last time._x000D_
SAP offers the provisioning of a dress rehearsal as part of the “Platform
Execution” service -; Please ask your SAP contact (e.g. SAP Client Partner) for
more information._x000D_
_x000D_
Management plans developed during the project preparation phase 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.
_x000D_
The purpose of this task is to update the project management plan and the
subsidiary plans based on the changes agreed during the projects change
management process._x000D_
_x000D_
The purpose of this activity is to ensure that the project is executed
according to what was agreed to in project charter, scope statement and
project management plan.
_x000D_
scheduled project activities (and tasks) and that work is progress, and
_x000D_
The purpose of this task is to capture and manage project issues and risks
and changes related to those e.g. changes of project scope, timeline, costs
etc.
_x000D_
This is the final Quality Gate in front of the cutover. The purpose of this
Quality Gate is to ensure that the project is ready for Go-Live (“Go / No-Go
decision”). A Quality Gate is a checklist milestone. Prior to Go-Live each
project manager demonstrates that they have been compliant with the
mandatory deliverables associated with a methodology while ensuring best
practice standards have been applied to ensure quality._x000D_
_x000D_
The purpose of this task is to make sure that project stakeholders are aware
of status and progress of the project including potential disturbances due to
existing risks and issues.
_x000D_
The purpose of this deliverable is to formally close the release and prepare
for next release and/or sprint planning meeting.
_x000D_
The purpose of this task is to 'groom' the product backlog. Product Owner
Team needs to detail the user stories to ready them for next release/sprint
planning meeting. The stories need to meet definition of Ready for Build so
they are understood by the SCRUM team and can be estimated during the
sprint planning meeting.
_x000D_
The purpose of this task is to conduct retrospective meetings with the
project team to identify potential improvements of the SCRUM process. The
objective of this task is to serve as a continuous improvement mechanism for
the team to adjust to a changing project environment and needs. The team
_x000D_
The purpose of this task is to update the Release and Sprint Plan according
to changed priorities and focus of the team. It is the responsibility of a
Product Owner to maintain the Release and Sprint plan and keep it current
during the project.
_x000D_
The purpose of this deliverable is to perform the cutover to the production
software and go live._x000D_
At this point, the organizational, business, functional, technical, and system
aspects of the project are ready to be used in production._x000D_
This activity is mandatory for all scenarios. The steps being performed are of
course scenario specific._x000D_
Procedure Convert Productive System (System Conversion)_x000D_
or Production Cutover (New Implementation)_x000D_
or Production Cutover (Selective Data Transition)_x000D_
Results_x000D_
After completion of this activity, the productive SAP S/4HANA system is
available for the end users._x000D_
The “SAP Going Live Support” service component is based on a standardized
method to support critical situations during production cutover. SAP experts
contribute their knowledge and expertise remotely to minimize the risks for
the Go-Live. Dedicated support during out-of-office hours can be ordered via
the “On Call Duty” service component._x000D_
Sudden slowly running applications in the new productive SAP S/4HANA
system are addressed by a Technical Performance Optimization service
component (SAP Enterprise Support order the CQC for Technica
lPerformance Optimization (TPO) instead): 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._x000D_
SAP Enterprise Support customers can request a Continuous Quality Check
(CQC) for “Going-Live Support”._x000D_
See the “Deploy” and “Run” learning journeys for details on the CQCs, or ask
your SAP Enterprise Support Advisor for details.
_x000D_
The goal of this task is to convert the productive system._x000D_
Procedure_x000D_
Proceed as follows: Request Restore Point of Production System Prior to
Final Cutover ActivitiesExecute the conversion of the production system
following the tasks defined in the cutover plan. Document the actual
duration of each step to support future projects. Capture any variances to
the plan along with the decision maker who approved the change. The
cutover manager(s) should proactively notify task owners of upcoming tasks,
to ensure their availability. Regularly communicate status to stakeholders.
After conversion has finished (including mandatory post-processing
activities), the system must be tested and validated Obtain system sign-
off_x000D_
Results_x000D_
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._x000D_
SAP offers the PRD conversion as part of the “Platform Execution” service.
The setup of the Fiori platform can be supported as well (scope option “SAP
Fiori Platform Setup”).
_x000D_
The goal of this task is to cut over production._x000D_
Procedure Execute the cutover following the tasks defined in the cutover
plan. This includes the final production data load. Document the actual
duration of each step to support future projects. Capture any variances to
the plan along with decision maker who approved the change. The cutover
manager(s) should proactively notify task owners of upcoming tasks, to
ensure their availability. Regularly communicate status to stakeholders.
After the data is loaded, testing and data reconciliation must be
completed. Obtain system sign-off_x000D_
Results_x000D_
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_x000D_
SAP offers the PRD installation as part of the “Platform Execution” service.
_x000D_
In accordance with the productive cut-over plan, the migration and upgrade
process begin._x000D_
Procedure_x000D_
The production cutover procedure depends on the selective data transition
scenario._x000D_
For Client Transfer, proceed as follows:_x000D_
Examples of these settings include table and field mappings, exclusion of
table entries, domains, rules, and mapping values. It is important to
remember that a lot of the SAP LT Client Transfer activities can be executed
well in advance of the actual downtime, which gives customers some more
flexibility. A copy of the SAP LT Client Transfer package is created from
the dress rehearsal to take over all the settings from the previous package.
All users beside the technical migration and upgrade team are locked,
when the downtime period starts. This also includes stopping all interfaces,
as defined. Reschedule any batch jobs that are scheduled for the downtime
period. Customers need to ensure that they can restore the system status
of the S/4HANA receiver system to the status at the start of the downtime
period, in case the migration fails. The system settings of the receiver
system are changed as required. Customers need to consider the following:
Archive logging Dropping indexes Parameterization of the database
The required delta customizing need to be identified during the various
project phases and implemented in the target system. Continuation of the
migration and upgrade process, in accordance with the Productive Migration
Plan. Monitoring of the migration and upgrade process in SAP LT Client
Transfer - If problems occur during the migration and upgrade process that a
customer cannot resolve (problems that would result in an inconsistent
receiver system), the original receiver system state must be restored.Once
the migration upgrade is complete, the log files in SAP LT Client Transfer
should be checked._x000D_
Customers can find further information about the productive migration in
the ‘Client Transfer’ Product Road Map of SAP Landscape Transformation
software, Refer to phase ‘5 Productive Migration and Upgrade’._x000D_
For System Merge, proceed as follows: A copy of the SAP LT system merge
package is created from the last test cycle to take over all the settings from
the previous package. It is important to remember that a lot of the SAP LT
system merge activities can be executed well in advance of the actual
downtime, which gives customers some more flexibility. All users beside
_x000D_
After the Go-Live it is important to verify how the new workload behaves as
opposed to the old system, and to use the Hyper Care phase to improve
system performance._x000D_
Workload analysis_x000D_
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 should 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)._x000D_
Health check and scalability analysis_x000D_
The scalability analysis contains system health checks (DB buffer, wait time,
etc.) as well as the identification of statements that cause bottleneck
situations._x000D_
Sizing verification_x000D_
Customers should monitor the technical KPIs in terms of CPU and memory
consumption to assess the actual usage vs. the deployed hardware._x000D_
Precondition is that the Monitoring Infrastructure (SAP Solution Manager
preferred) is already set up._x000D_
Procedure Monitor Resource ConsumptionAnalyze Workload Check
System Scalability Run Going-Live Service (Verification Session)_x000D_
Security Activities _x000D_
All the required Security Activities must be finalized.The Status Check is
supported by: Go-Live Checks SAP Go-Live Support_x000D_
The Security Procedures must to be established to stay“Clean”. These
procedures can be achieved by: Security Monitoring Security Incident
Management_x000D_
SAP can join the hyper care phase by continuing the ”SAP Going Live
Support” and the “Technical Performance Optimization” service
components. With the monitoring of the core business processes and the
system environment of the new SAP S/4HANA system, SAP experts
contribute their knowledge remotely to minimize the risk for instable
operations
_x000D_ and performance. SAP experts will also work on open issues and
The objective of this task is to identify the resource consumption after Go-
Live and to manage it permanently to answer questions like: What is the
current workload profile? Is the resource consumption at a reasonable ratio
to the business logic and value? Is the resource consumption stable or does it
increase even though there is no additional functional or business load in
the system?_x000D_
Procedure_x000D_
The following KPIs are to be measured: Physical CPU consumption over
time (SAP application and DB server): [average per month / week / day]
Workload profile (SAP application and DB server): [peaks, averages, load
balancing] Consider seasonal fluctuations: [e.g. period end closing]
Memory consumption (SAP application and DB server): [buffer settings and
usage
_x000D_
Workload analysis first has the goal to provide information which
applications, transactions, jobs and processes dominate the workload
consumption. Then, in the second step, candidates for performance
optimization will get identified and prioritized._x000D_
Procedure_x000D_
You measure the following KPIs Resource consumption per task type: [#steps
* (CPU time + DB time)] Resource consumption per transaction/process:
[#steps * (CPU time + DB time)] Duration of background jobs: [seconds]
Response time per dialog transaction: [average time, time distribution]
Most expensive SQL statements : [#executions, elapse time]_x000D_
Create a list of the top consumers and the most important SQL statements.
Decide which item should be checked and further optimized._x000D_
SAP can support both the code analysis and the optimization.
_x000D_
A system scalability check has the goal to understand the top resource
consumers with respect to:_x000D_
Adequacy and optimization potential on a technical level Adequacy
and optimization potential on a service level Adequacy and optimization
potential on a business level_x000D_
The scalability check focuses on identifying the resources that form the
bottleneck for a further increase of the load. It helps to guarantee that the
system is not laid out for irrelevant tasks and to identify the load drivers from
the business._x000D_
Procedure _x000D_
Proceed as follows:_x000D_
Sort the list of top consumers by the consumption of the resource that
is the largest bottleneck. Check, starting with the largest resource
consumer: _x000D_
Whether it is possible to reduce the resource consumption by
optimizing the database or the coding that is responsible for the resource
consumption. Whether it is possible to avoid the bottleneck by
optimizing load balancing and scheduling of services. Whether the
business value obtained from the service justifies the resource consumption.
_x000D_
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.
_x000D_
Depending on the project scope, you have either ordered the analysis
session of an SAP OS/DB Migration Check, or an SAP GoingLive Functional
Upgrade Check, or an SAP GoingLive Check for Implementation (see activity
Integration Validation in the Realize phase for details)._x000D_
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._x000D_
Procedure_x000D_
Proceed as follows: SAP runs the GoingLive Check. Follow up and solve
all yellow and red issues identified in the service report._x000D_
SAP delivers the SAP GoingLive Check ( verification session) in this task.
_x000D_
Obsolete data originates from Data model simplifications in many
application areas (MM, FIN, SD, EHS, Retail/Fashion, CWM, Classification,
PLM…) Omitted functionality in SAP S/4HANA (compared to SAP ERP)
Temporary data stores that are created during SAP S/4HANA system
conversion_x000D_
Data is typically not deleted during SAP S/4HANA system conversion as it
increases the business downtime and prevents diagnostics of errors after the
conversion. Thus, converting SAP ERP systems to SAP S/4HANA results in
likely 5-10% memory overhead from obsolete data._x000D_
With SAP S/4HANA release 1809 the “Obsolete Data Handling Tool” -;
report/TA code ODH_Data_processing - is shipped initially in a reduced
scope and is available on request. SAP note 2661837 explains how to request
the enabling of the obsolete data deletion report and how to use the
tool._x000D_
Procedure_x000D_
Execute the deletion rules that are delivered by SAP in your productive
system, without any business downtime, after completing following points:
Successful validation of system conversion Testing the deletion rules
in an appropriate test system (copy of production) Backup of the database
prior to executing the deletion rules in your system_x000D_
The deletion is cross client, which means that irrespective of the client in
which you execute the report, the data is deleted across all clients. With this
report, you can delete data in the following ways depending on the S/4HANA
data model change: Rows that contain obsolete data Columns that
contain obsolete data Entire table that contains obsolete data_x000D_
Note: You can only delete the data directly from the table, the report for
release 1809 does not provide any backup options. Please note that once
you delete the data, there is no option to retrieve this data or build it back
into the original table using this report.
_x000D_
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_x000D_
Tasks Prepare End-User Training for Scope Option Deliver End-User
Training for Scope Option Collect Training Evaluations Feedback Perform
People Readiness Assessment
_x000D_
This purpose of this task is to adapt available training material and make it
suitable for End User training
_x000D_
This task executes the delivery of EU training as well as capturing feedback
on both the training session and the trainer.
_x000D_
The purpose of this task is to capture feedback on both the training session
and the trainer delivering the material.
_x000D_
This task checks how prepared the people in the organization are with
regards to the identified changes and received EU training.
_x000D_
Once the hyper care phase ends it is important to fully enable the regular
support organization at the customer site to safely and securely operate the
new SAP system. This includes (but is not limited to): The finalization of
system documentationThe finalization of operational procedures as part of
the operations handbook The check of the customer support
organization.Procedure Resolve and Close Open Issues Handover
Operations ResponsibilityHow SAP Can Support_x000D_
SAP supports this activity with the “Handover to Support” scope option as
part of the Build Execution service. The Handover to Support scope option:
Evaluates process management framework quality like documentation,
configuration, testing validation, or authorization management Evaluates
process management knowledge transfer and IT support team capabilities
for future maintenance Evaluates handover protocol procedures Builds
handover conditions, recommendations, and supports customer adoption
activities_x000D_
The Handover to Support scope option builds on top of deliverables created
in the functional design and execution services._x000D_
_x000D_
The purpose of this task is to achieve a closure of all open project issues
which is a prerequisite for the final project closure.Procedure_x000D_
The purpose of this task is to achieve a closure of all open project
issues._x000D_
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.
_x000D_
In this task, operations responsibility is formally handed over from the team
who operated the new SAP S/4HANA system (usually a mix of resources from
the project team and IT support) to the IT support operations team._x000D_
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 S/4HANA 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._x000D_
Procedure_x000D_
Hand over operations responsibility to the IT support operations team.
_x000D_
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
_x000D_
_x000D_
project management standards are being upheld within our projects. 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._x000D_
_x000D_
_x000D_
The purpose of this task is to achieve a closure of all open project issues
which is a prerequisite for the final project closure.
_x000D_
The purpose of this task is to document the results of the project, both
regarding achieved objectives, deliverables as well as adherence to schedule,
costs and delivered value.
_x000D_
The purpose of this activity is to formally close the project by obtaining
customer signatures on dedicated deliverables/documents e.g. Project
Quality Gate, Project Closeout Report.
_x000D_
The transition project has ended with the Deploy phase. The activities of the
Run phase are displayed in the following figure._x000D_
In the Run phase, the aim is to establish a 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._x000D_
[image6]_x000D_
Figure: Activities in the Run phase_x000D_
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.
_x000D_
With project end, the customer support organization is responsible to
operate the new solution. The aim of this activity is to ensure efficient daily
operations. This affects IT support people, IT support processes, and tools. In
addition, the customer support organization should seek for continuous
improvement._x000D_
Go-Live and hyper care has finished successfully. The customer support
organization is responsible for operating the new solution._x000D_
Procedure _x000D_
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. Safely and Efficiently Operate the new Solution Continuously
Optimize IT Operations_x000D_
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.
_x000D_
The purpose of this task is to safely and efficiently ensure business continuity
and the operability of the solution. Operability is the ability to maintain IT
systems in a functioning and operating condition, guaranteeing systems
availability and required performance levels to support the execution of the
enterprise’s business operations._x000D_
Procedure _x000D_
Operating an SAP solution can easily fill an own road map. Therefore, this
task can only list the most important aspects to consider: Install and
configure the solution operation platform if not already done. In case you
have used a cloud image for your implementation project, now it is time to
set up and configure SAP Solution Manager 7.2 on-premise to support most
of your core IT support processes. Although there are many partner products
in the market, SAP recommends using SAP Solution Manager If not yet
done configure core IT support processes like: Incident and
Problem Management Change Management _x000D_
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, you COE needs to be “Primary Certified”.
Configure efficient system management - SAP has developed a
concept called “Run SAP like a Factory”. Core elements are:
Application Operations Business Process Operations
_x000D_
See SAP Support Portal (accelerator section) for getting an overview about all
capabilities including offline demos. Operations Control Center (OCC)
_x000D_
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. _x000D_
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. _x000D_
SAP has a large set of offerings to SAP MaxAttention customers with respect
to safe and efficient operations. For example, SAP can configure Application
Operations in your environment, and trains your IT support experts in using
the tools. See the information on End-to-End Hybrid Operations in the
_x000D_
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)._x000D_
Procedure _x000D_
This task can only name some out of the many improvement options:
_x000D_
Advanced Customer Center of Expertise (aCCOE) _x000D_
An alternative approach to improve IT operations is to set up an aCCOE. The
advanced certification for Customer COEs covers the full spectrum of SAP
solution operations. Based on the SAP standards for solution operations and
the Run SAP methodology, a team with advanced certification has integrated
quality management in place, bringing transparency to the challenges and
issues faced by the organization as a whole. This is paramount for mission
critical operations. Visibility, alignment, and a common understanding of
those top issues are enabled through the center's ability to maintain a single
source of truth - one central area where everything is tracked and from
which all information flows. See accelerator section for details.
_x000D_
Regular assessments of IT operations _x000D_
Run regular assessments and review on IT operations efficiency._x000D_
SAP supports a tailored creation of an OCC for SAP Premium Engagement
customers, and the advanced certification for customer COE’s. See service
component information on End-to-End Hybrid Operations in the accelerator
section, or contact your TQM for details._x000D_
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).
_x000D_
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.For all solutions realized by
SAP IBSO, the SAP IBSO Support protects and runs these solutions through
ongoing support and through continuous improvement services._x000D_
Procedure Periodically update your SAP system Initiate a new innovation
cycle
_x000D_
The goal of this task is to keep the SAP system current, by implementing
innovations and corrections from SAP in a timely manner. This is handled by
an efficient maintenance management process._x000D_
Procedure _x000D_
Implement a maintenance management process for your SAP system, and
implement feature and support packs from SAP in a timely manner: For SAP
S/4HANA on-premise edition, SAP is currently delivering 1 new key release
per year, and some successive Feature Pack Stacks (FPS). Then comes the
next key release, followed by several FPSs. An FPS may contain non-
disruptive, non-mandatory features. Support Pack Stacks (SPS) are shipped
for a given release once the N+1 release is made available, until the end of
the mainstream maintenance._x000D_
Please note: The maintenance of SAP S/4HANA will be handled in a
dedicated road map._x000D_
Please make yourself familiar with the SAP Release and Maintenance
Strategy (accelerator section)._x000D_
SAP offers the planning and execution of SAP maintenance via Proactive
Solution Maintenance as part of SAP Application Management Services. See
accelerator section for details.
_x000D_
The goal of this task is to close the loop but initiate a new innovation
cycle._x000D_
Procedure _x000D_
Innovation is not a one-step-process, but a continuous journey. Your SAP
system runs stable and is updated with the latest innovations from
SAP._x000D_
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._x000D_
Adjust your innovation strategy accordingly and start the next round by
entering the Design phase of the next innovation project._x000D_
There are multiple options on how SAP can support your innovation and
improvement journey, for instance: 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 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 which provides 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._x000D_
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.
Duration
680,5 days
70 days
60 days
20 days
40 days
5 days
10 days
50 days
15 days
15 days
5 days
15 days
10 days
10 days
0 days
0 days
56,5 days
11 days
1 day
1 day
1 day
5 days
5 days
0 days
0 days
23 days
5 days
5 days
5 days
5 days
5 days
10 days
10 days
3 days
3 days
5 days
5 days
5 days
3 days
2 days
12 days
0 days
0 days
0 days
0 days
10 days
2 days
5 days
1 day
0,5 days
0,5 days
1 day
1 day
2 days
3 days
2 days
1 day
1 day
3 days
3 days
2 days
2 days
2 days
2 days
2 days
1 day
1 day
2 days
8,5 days
2 days
0,5 days
1 day
5 days
3 days
2 days
2 days
2 days
2 days
3 days
3 days
2 days
2 days
1 day
1 day
1 day
6 days
3 days
3 days
4 days
1 day
2 days
1 day
1 day
294 days
4 days
2 days
1 day
1 day
20 days
20 days
23 days
20 days
1 day
5 days
3 days
30 days
30 days
10 days
20 days
30 days
30 days
5 days
5 days
5 days
5 days
5 days
5 days
30 days
30 days
1 day
1 day
10 days
10 days
80 days
10 days
20 days
30 days
30 days
0 days
0 days
103 days
5 days
20 days
10 days
20 days
90 days
20 days
10 days
10 days
10 days
20 days
20 days
60 days
5 days
5 days
25 days
5 days
20 days
40 days
20 days
20 days
30 days
30 days
214 days
10 days
5 days
5 days
5 days
0 days
5 days
5 days
15 days
10 days
15 days
10 days
10 days
50 days
20 days
10 days
10 days
2 days
3 days
10 days
10 days
20 days
20 days
10 days
10 days
2 days
1 day
2 days
1 day
1 day
1 day
1 day
8 days
2 days
2 days
2 days
2 days
0 days
0 days
0 days
6 days
1 day
2 days
1 day
1 day
1 day
1 day
198 days
4 days
2 days
1 day
1 day
6 days
3 days
3 days
30 days
20 days
30 days
5 days
5 days
5 days
1 day
1 day
1 day
1 day
1 day
0 days
5 days
5 days
50 days
50 days
15 days
15 days
15 days
15 days
5 days
5 days
15 days
15 days
5 days
5 days
0 days
20 days
20 days
20 days
20 days
0 days
3 days
1 day
1 day
1 day
30 days
30 days
20 days
20 days
10 days
10 days
45 days
10 days
30 days
5 days
45 days
40 days
40 days
40 days
40 days
40 days
10 days
10 days
50 days
30 days
20 days
35 days
30 days
5 days
20 days
20 days
40 days
40 days
10 days
5 days
10 days
5 days
5 days
5 days
30 days
20 days
10 days
30 days
10 days
10 days
10 days
10 days
10 days
10 days
50 days
10 days
10 days
10 days
10 days
2 days
2 days
0,5 days
0 days
1 day
1 day
1 day
108 days
0 days
0 days
5 days
1 day
1 day
1 day
1 day
1 day
1 day
78 days
2 days
2 days
1 day
30 days
10 days
20 days
10 days
10 days
10 days
5 days
10 days
10 days
10 days
10 days
13 days
0,5 days
2 days
1 day
2 days
2 days
1 day
4 days
2 days
1 day
1 day
3 days
3 days
3 days
3 days
20 days
20 days
20 days
5 days
5 days
2 days
11 days
2 days
5 days
2 days
2 days
41 days
30 days
10 days
7 days
1 day
1 day
1 day
2 days
2 days
1 day
0 days
0 days
0 days
0 days
0 days
0 days
0 days
Start Finish Predecesso
18 July 2019 08:00 24 February 2022 12:0
18 July 2019 08:00 23 October 2019 17:00

18 July 2019 08:00 09 October 2019 17:00
18 July 2019 08:00 14 August 2019 17:00
15 August 2019 08:00 09 October4
15 August 2019 08:00 21 August 4
15 August 2019 08:00 28 August 4
15 August 2019 08:00 23 October 2019 17:00
15 August 2019 08:00 04 Septemb4
15 August 2019 08:00 04 Septemb4
15 August 2019 08:00 21 August 4
05 September 2019 08:00 25 Septemb10
26 September 2019 08:00 09 October12
10 October 2019 08:00 23 October13
04 September 2019 17:00 04 September 2019 17
04 September 2019 17:00 04 Septemb9
23 October 2019 17:00 10 January 2020 12:00
18 November 2019 13:00 03 December 2019 12:
18 November 2019 13:00 19 Novembe

73

78
73

21
26 November 2019 13:00 03 Decembe

22
23 October 2019 17:00 23 October 2019 17:00
73
27
02 December 2019 13:00 09 Decembe
28
28
28
28
28
32
28
28
28
28
28
28
19 December 2019 12:00 06 January 26
31;30;29;28
34
30
30
02 January 2020 13:00 06 January 46
24 October 2019 08:00 30 October 2019 17:00


31 October 2019 08:00 04 November 2019 17:
31 October 2019 08:00 01 Novembe

54

56
01 November 2019 08:00 05 November 2019 17:

58

58

58
58

58

58

58

58

58

68;67;66;65

70

71

72

73
73
73
73
73

73

71

71

71

71

71
87
06 January 2020 13:00 10 January 2020 12:00
06 January 2020 13:00 08 January 26;41

10 January 2020 13:00 25 February 2021 12:0
10 January 2020 13:00 16 January 2020 12:00


16 January 2020 13:00 13 Februar 95
16 January 2020 13:00 13 Februar 159
23 January 2020 13:00 24 January 161

24 January 2020 13:00 31 January 103
13 February 2020 13:00 18 Februar 102;103
18 February 2020 13:00 31 March 2101
18 February 2020 13:00 31 March 2020 12:00

18 February 2020 13:00 03 March 2101
03 March 2020 13:00 31 March 2108

31 March 2020 13:00 12 May 2020 12:00
31 March 2020 13:00 12 May 202109
12 May 2020 13:00 19 May 2020 12:00

12 May 2020 13:00 19 May 202111
19 May 2020 13:00 26 May 2020 12:00

19 May 2020 13:00 26 May 202113
26 May 2020 13:00 02 June 2020 12:00

26 May 2020 13:00 02 June 20 115
15 September 2020 13:00 27 October 2020 12:00
15 September 2020 13:00 27 October115;117;12
27 October 2020 13:00 28 October 2020 12:00

28 October 2020 13:00 11 November 2020 12:

121
18 February 2020 13:00 09 June 2020 12:00
18 February 2020 13:00 03 March 2101
12 May 2020 13:00 09 June 20 111
12 May 2020 13:00 23 June 2020 12:00
12 May 2020 13:00 23 June 20 111
02 June 2020 12:00 02 June 2020 12:00

02 June 2020 12:00 02 June 20 115;117
16 January 2020 13:00 09 June 2020 12:00
23 January 2020 13:00 20 Februar 132
23 January 2020 13:00 06 Februar 132
12 May 2020 13:00 09 June 20 111
12 May 2020 13:00 15 September 2020 12
12 May 2020 13:00 09 June 20 111
09 June 2020 13:00 23 June 20 137
23 June 2020 13:00 07 July 202138

07 July 2020 13:00 21 July 202139
21 July 2020 13:00 18 August 140

18 August 2020 13:00 15 Septemb141
12 May 2020 13:00 04 August 111
04 August 2020 13:00 11 August 143

04 August 2020 13:00 11 August 143
23 January 2020 13:00 20 Februar 147;44
12 May 2020 13:00 07 July 2020 12:00
12 May 2020 13:00 09 June 20 111
09 June 2020 13:00 07 July 202150
12 May 2020 13:00 23 June 2020 12:00
12 May 2020 13:00 23 June 20 111
16 January 2020 13:00 11 November 2020 12:

155;121
156
16 January 2020 12:00 23 January 2020 12:00

16 January 2020 13:00 23 January 159
161;123
123;159
23 December 2020 13:00 06 January 2021 12:00
23 December 2020 13:00 06 January 123;169;32
11 November 2020 13:00 20 January 2021 12:00
123;32
168

150;123
06 January 2021 13:00 08 January 169;166
08 January 2021 13:00 13 January 171;169

06 January 2021 13:00 20 January 170;173

06 January 2021 13:00 03 Februar 173;170;16
03 February 2021 13:00 17 February 2021 12:0
03 February 2021 13:00 17 Februar 123;31;176
16 January 2020 13:00 20 January 2020 12:00



123;182
187
188

189

123

192
19 February 2021 13:00 22 Februar 196

17 February 2021 13:00 19 Februar 100;119;13

03 February 2021 13:00 08 November 2021 12:
25 February 2021 13:00 03 March 2021 12:00
25 February 2021 13:00 01 March 2200

01 March 2021 13:00 02 March 2203
02 March 2021 13:00 03 March 2204
03 March 2021 13:00 11 March 2021 12:00
03 March 2021 13:00 08 March 2205
08 March 2021 13:00 11 March 2207
03 March 2021 13:00 14 April 2021 12:00

03 March 2021 13:00 31 March 2202
03 March 2021 13:00 14 April 20 202
08 March 2021 13:00 15 March 2021 12:00

08 March 2021 13:00 15 March 2207
15 March 2021 13:00 22 March 2021 12:00
15 March 2021 13:00 16 March 2213
16 March 2021 13:00 17 March 2215
17 March 2021 13:00 18 March 2216
18 March 2021 13:00 19 March 2217
19 March 2021 13:00 22 March 2218

22 March 2021 12:00 22 March 2214
22 March 2021 13:00 29 March 2021 12:00

22 March 2021 13:00 29 March 2214;123
29 March 2021 13:00 07 June 2021 12:00

29 March 2021 13:00 07 June 20 222;123
07 June 2021 13:00 28 June 2021 12:00

07 June 2021 13:00 28 June 20 224
28 June 2021 13:00 19 July 2021 12:00

28 June 2021 13:00 19 July 202226
19 July 2021 13:00 26 July 2021 12:00
19 July 2021 13:00 26 July 202228

26 July 2021 13:00 16 August 2021 12:00
26 July 2021 13:00 16 August 230
16 August 2021 13:00 23 August 2021 12:00
16 August 2021 13:00 23 August 230;232;22

29 March 2021 12:00 29 March 2222;123
29 March 2021 12:00 26 April 2021 12:00

29 March 2021 13:00 26 April 20 222;262;14
29 March 2021 13:00 26 April 20 123;222
29 March 2021 13:00 26 April 20 123;222
29 March 2021 12:00 29 March 2123;222
23 August 2021 13:00 26 August 2021 12:00
23 August 2021 13:00 24 August 228;230;23
24 August 2021 13:00 25 August 242

25 August 2021 13:00 26 August 243
03 March 2021 13:00 14 April 2021 12:00
03 March 2021 13:00 14 April 20 202
03 March 2021 13:00 31 March 2021 12:00
03 March 2021 13:00 31 March 2202

03 March 2021 13:00 17 March 2135;202
17 March 2021 13:00 31 March 2249

16 August 2021 13:00 18 October 2021 12:00
16 August 2021 13:00 30 August 123;232;23
30 August 2021 13:00 11 October252
10 March 2021 13:00 12 May 2021 12:00
10 March 2021 13:00 05 May 202274;142
17 March 2021 13:00 12 May 202275;160
17 March 2021 13:00 12 May 202143;273
17 March 2021 13:00 12 May 202143;273
17 March 2021 13:00 12 May 202143;273
03 March 2021 13:00 17 March 2021 12:00

03 March 2021 13:00 17 March 2202
07 June 2021 13:00 16 August 2021 12:00

07 June 2021 13:00 19 July 202273;224;15
19 July 2021 13:00 16 August 264

07 June 2021 13:00 26 July 2021 12:00
07 June 2021 13:00 19 July 202273;224;15

19 July 2021 13:00 26 July 202267
19 July 2021 13:00 16 August 2021 12:00

19 July 2021 13:00 16 August 157;226;22
16 August 2021 13:00 11 October 2021 12:00
16 August 2021 13:00 11 October270
03 March 2021 13:00 17 March 2021 12:00
03 March 2021 13:00 10 March 2163;202
03 March 2021 13:00 17 March 2164;202
11 October 2021 13:00 18 October 2021 12:00

11 October 2021 13:00 18 October234;166;27
11 October 2021 13:00 18 October234;166;27

03 February 2021 13:00 17 March 2021 12:00
03 February 2021 13:00 03 March 2176

03 March 2021 13:00 17 March 2280;202
03 March 2021 13:00 14 April 2021 12:00
03 March 2021 13:00 17 March 2178;123;20
17 March 2021 13:00 31 March 2283

17 March 2021 13:00 31 March 2283
17 March 2021 13:00 31 March 2283
17 March 2021 13:00 31 March 2283
31 March 2021 13:00 14 April 20 284;287;28
23 August 2021 13:00 01 November 2021 12:

281;277;27
23 August 2021 13:00 06 Septemb234;274;25
23 August 2021 13:00 06 Septemb275;234;25
23 August 2021 13:00 06 Septemb258;234;26
03 March 2021 12:00 05 March 2021 12:00

03 March 2021 13:00 05 March 2202
03 March 2021 13:00 03 March 2202

03 March 2021 12:00 03 March 2202
03 March 2021 13:00 04 March 2202
03 March 2021 13:00 04 March 2202
03 March 2021 13:00 04 March 2202
12 May 2021 12:00 11 October 2021 12:00

11 October 2021 12:00 11 October192;202;27
12 May 2021 12:00 12 May 202192;202;25

306
211;241;24

306

307

308
309
08 November 2021 13:00 24 February 2022 12:0

310
310

312
316

253;312

268;312
268;312
281;312

281;293;29

312

327

328

329
330;325

331

306;312;24
334

335

331
331
331
337

338;339;34
338;339;34

338;339;34
254;340;33

338;339;34
22 December 2021 13:00 06 January 2022 12:00

317

348
04 January 2022 13:00 06 January 350
29 December 2021 13:00 24 Februar 337

29 December 2021 13:00 09 Februar 338;339;34




Outline Level Workstream Activity Group
1
2
Analytics,Application System Conversion,New
Design and Configuration Implementation,Selecti
ve Data Transition
3
Application Design and System Conversion,New
Configuration Implementation,Selecti
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
Analytics Selective Data
Transition,System
Conversion,New
Implementation
4
ve Data Transition
3
ve Data Transition
4
Configuration Implementation
4
Data Management System
Conversion,Selective
Data Transition
4
ve Data Transition
4
Data Management System Conversion,New
Implementation,Selecti
ve Data Transition
4
ve Data Transition
4
Implementation
3
Data Management
4
2
Solution Adoption System Conversion,New
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
Application Design and
Configuration
4
Analytics,Application System Conversion,New
Design and Implementation,Selecti
Configuration,Data ve Data Transition
Management,Operations
and Support
3
Data Transition
4
ve Data Transition
4
ve Data Transition
4
Extensibility System
Data Transition
4
Operations and Support System Conversion,New
ve Data Transition
4
Technical Architecture and System Conversion,New
Infrastructure Implementation,Selecti
ve Data Transition
4
Data Management New
ve Data Transition
4
Data Management
4
Data Management
4
Integration System Conversion,New
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
Data Management System Conversion
4
ve Data Transition
3
ve Data Transition
4
Data Management
4
Data Transition
4
Data Transition
4
ve Data Transition
4
ve Data Transition
4
Project Management System Conversion,New
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
2
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
Solution Adoption
4
Application Design and New Implementation
Configuration
3
Application Design and System Conversion
Configuration
4
Configuration
4
Configuration
4
Configuration
4
3
3
4
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
4
ve Data Transition
3
4
3
4
ve Data Transition
3
Configuration
4
Configuration
4
Configuration
4
ve Data Transition
4
Data Management New
ve Data Transition
3
Data Management New Implementation
4
4
4
4
4
4
4
Data Management Selective Data
Transition
4
Data Management
4
Data Transition
3
Data Transition
4
Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
Analytics System Conversion,New
ve Data Transition
3
ve Data Transition
4
Testing System Conversion,New
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
Testing Selective Data
Transition,System
Conversion,New
Implementation
4
ve Data Transition
3
Data Management
4
4
Data Management New
ve Data Transition
4
ve Data Transition
3
Technical Architecture and New
ve Data Transition
4
Technical Architecture and System
Infrastructure Conversion,Selective
Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
Technical Architecture and
Infrastructure
4
Technical Architecture and
Infrastructure
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
2
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
Implementation
3
Implementation
4
Testing,Project System Conversion,New
Management Implementation
3
Implementation
4
Implementation
4
Implementation
4
Implementation
4
Implementation
4
3
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
Extensibility System Conversion,New
Implementation
3
4
Implementation
4
Implementation
4
Implementation
4
Implementation
3
Implementation
4
Implementation
4
Implementation
4
ve Data Transition
3
Configuration
4
ve Data Transition
3
4
Configuration,Data Implementation,Selecti
Management ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
4
4
Transition
4
Transition
4
Transition
4
Data Management
3
Data Management
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
Implementation
3
Implementation
4
Implementation
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
3
Technical Architecture and New
ve Data Transition
4
Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
Analytics,Integration,Exte System Conversion,New
nsibility,Data Implementation,Selecti
Management,Technical ve Data Transition
Architecture and
Infrastructure
3
Analytics,Integration,Exte System Conversion,New
nsibility,Data Implementation,Selecti
Management,Technical ve Data Transition
Architecture and
Infrastructure
4
Data New Implementation
Management,Technical
Architecture and
Infrastructure
4
Analytics,Integration,Exte System Conversion
nsibility,Data
Management
4
Transition
4
Project Management Selective Data
Transition,System
Conversion,New
Implementation
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
Implementation
4
Implementation
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
2
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
Implementation
3
Operations and Support System Conversion
4
Operations and Support New Implementation
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
Data System Conversion,New
Management,Technical Implementation,Selecti
Architecture and ve Data Transition
Infrastructure
3
Data System Conversion
Management,Technical
Architecture and
Infrastructure
4
4
Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
Data Management
4
Implementation
3
Implementation
4
Implementation
4
Implementation
4
Implementation
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
ve Data Transition
4
2
ve Data Transition
3
ve Data Transition
4
ve Data Transition
4
ve Data Transition
3
ve Data Transition
4
ve Data Transition

Project-Plan en 19Q3-Activity and Task-Level

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Project-Plan en 19Q3-Activity and Task-Level

Încărcat de

Drepturi de autor:

Formate disponibile

Sequence

Conduct Agile Training for the Project Team

Conduct SAP Solution Manager Training

Conduct Project Team Enablement prior to Fit-Gap Analysis

Conduct Key User Training

Conduct Handover Meeting(s) from Opportunity Phase

Set Stakeholder Expectations for Agile Project

Create Project Charter

Establish Project Governance

Define Roles and Responsibilities

Define Project Organization

Create Scope Statement

Create Project Schedule

Plan Stakeholders Management

Project Kick-Off and On-Boarding

Conduct Kick-off Meeting

Prepare Team On-boarding Document

On-board Project Team

Define Project Standards

Setup and Test Remote Support

Direct and Manage Project Execution

Monitor and Control Project Activities

Manage Issues, Risks and Changes

Communicate Status and Progress to Project Stakeholders

Organizational Change Management Roadmap

Prepare Organizational Change Management Roadmap

Phase Closure and Sign-Off Phase Deliverables

Conduct Knowledge Management Gate

Conduct Project Quality Gate

Conduct Project Management Review Service

Review Acceptance Criteria

Review RACI Chart for Explore Phase

Reconfirmation of Scope for Activation (New Implementation only)

Fit-Gap / Delta Design: Finalize System Setup

Enhance system setup with additional configuration

Fit-Gap / Delta Design: Gap Identification

Fit-Gap / Delta Design: Delta Scope Prioritization

Fit-Gap / Delta Design: Verify and Accept

Perform Validation and Approval Sessions

Fit-Gap / Delta Design- Central Finance Design

Prepare and Present Data Migration Scope and Requirements Document

Test Data Management

Set up Landscape Transformation Software (Selective Data Transition only)

Sandbox Setup / Conversion

Decide on Integration with Cloud Applications

Develop Virtualization Strategy

Execution / Monitoring / Controlling Results

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

Update and Prioritize Backlog

Validate Release and Sprint Plan Against SoW

Validate Organizational Alignment Approach

Establish Baseline of Current State

Phase Closure and Sign-Off phase Deliverables

Conduct Knowledge Management Gate

Execute Baseline Retrospective

Conduct Project Management Review Service

Manage Fulfilled Contracts

Review Deliverables of Realize Phase

Review RACI Chart for Realize Phase

Plan Realize Phase