Activate and Fit-Gap

SAP ACTIVATE
Road Map for SAP S/4HANA Implementation

The purpose of the road map “SAP S/4HANA Implementation” is to support “on-premise”
implementation projects to SAP S/4HANA, in order to eliminate related risks - manage them
proactively - and to make such an implementation project predictable - create transparency
about all involved tasks and roles and thus create viable foundation. SAP offers additional road
maps for cloud implementation projects.
The structure of the road map is release-independent. Release information is given explicitly in
case a certain activity or task is only required for a dedicated release (e.g. SAP Simple Finance
on-premise edition 1503).
SAP sees three implementation scenarios to SAP S/4HANA:

 New Implementation:
For customers, who would like to implement a new instance of SAP S/4HANA, by either
migrating a legacy system, or by running a net-new SAP S/4HANA installation
 Landscape Transformation:
For customers, who would like to consolidate the existing SAP landscape – or carve out
selected entities or processes – as part of their move to SAP S/4HANA
 System Conversion:
For customers, who would like to convert the existing SAP ERP system to SAP S/4HANA
on-premise including business data and configuration.
© vCentric Technologies (P) Limited Page 1 of 9

SAP ACTIVATE
This road map mainly focuses on the scenarios “Landscape Transformation” and “System
Conversion”. The “New Implementation” scenario will be fully included with the next version of
this roadmap.
With this road map, SAP Digital Business Services addresses SAP S/4HANA implementation
projects holistically, covering all project phases and work streams, in alignment with SAPs latest
implementation methodology called SAP Activate. It addresses questions including the
following:
 How do I get an ideal SAP S/4HANA strategy, which identifies the value for my company?
What is my customer specific road map for SAP S/4HANA?
 What simplifications are ideal for my company? What can I implement as part of the
project?
 How do I identify custom code that needs to be adjusted for SAP HANA and SAP
S/4HANA?
 Will the SAP database seamlessly fit into the existing infrastructure?
 What does this change mean for the operations team?
 What is the overall project duration, what are related efforts?
 What are potential risks and how can they be mitigated?
 What trainings are needed for my team and which training strategy fits best into the
company requirements?
This road map is the backbone of an SAP offering that consists of methodologies and best
practices (“accelerators” referenced from the road map). The road map supports you in running
SAP ACTIVATE
the implementation project yourself, together with your software and hardware partner, and
together with SAP. The accelerators are stored in various places, for instance Public web, SAP
Community Network, SAP Service Market Place, and SAP Enterprise Support Academy. You may
need to register, or may have SAP Enterprise Support status to get access.
The road map documents an SAP S/4HANA implementation project, and as such provides a
structured read-through documentation for Project Managers. In case it is used as the
foundation for a specific implementation project, then it must be tailored to customer’s specific
business and IT requirements, because not all activities documented here are required in all
implementation cases.
Prerequisites
The prerequisites for using this road map depends on the implementation scenario.
Customers who are interested in Landscape Transformation or System Conversion, start from an
SAP ERP system on-premise, whereas the New Implementation scenario can also start from a
legacy system.
For System Conversion and Landscape Transformation, the start release may also have impact
on the steps required to go to SAP S/4HANA. For System Conversion, the road map assumes
that the start release of SAP ECC is release 6.0. Upgrade from older releases could be included
into this change event as well. Customers who are on SAP Suite on HANA already, can skip
references to the OS/DB migration part of the road map.
This road map is designed to be used in conjunction with SAP Premium Engagement offerings
for SAP S/4HANA. SAP has designed four unique packages for Premium Engagement and
MAXATTENTION customers, which can be tailored to project scope and requirements, to assist
in the implementation to SAP S/4HANA. Throughout the road map there are references to SAP
services and offerings that can be requested as part of these packages. Please note that SAP
S/4HANA implementation services will not be offered individually on a pick-and-choose basis,
but only as part of a SAP S/4HANA service packages. Customers who are interested in accessing
the full capabilities of this road map should contact the local SAP sales representative to find out
which SAP S/4HANA service package can best support the implementation project needs.
Procedure
The SAP S/4HANA Implementation road map is time-wise structured in phases:
 Discover
 Prepare
 Explore
 Realize
 Deploy

SAP ACTIVATE
 Run
The phase names are in alignment with SAP’s new implementation methodology called “SAP
Activate” (see Accelerator’s section).
Discover Phase: Discover the value of SAP S/4HANA
In the Discover phase, customers create an overall strategy for the digital transformation, and
an implementation plan for the next couple of years. SAP S/4HANA will play a key role within
this strategy – therefore it is important to make customers familiar with the benefits and the
value of SAP S/4HANA. The experience of a “cloud trial” may help in this context. Next
customers need to identify at a high-level the areas of the existing solution landscape that can
benefit from the move to SAP S/4HANA. Additionally, this phase will also help to shed light on
any potential problematic areas with the implementation, based on the current system state
and usage patterns.
Then SAP recommends to create a value-based and company specific implementation strategy
for SAP S/4HANA. This includes the decision on the implementation scenario (e.g. the decision
to either convert the existing system, or to install a new one), and a high-level road map that
sequences the innovation steps related to SAP S/4HANA on a time line.
Last, the impact on the technical architecture and IT infrastructure is evaluated, which is –
together with the implementation strategy - the foundation of the business case.
Prepare Phase: Start the implementation project
Once the business case has been approved, the project is officially initiated in the Prepare
phase. A first version of an implementation plan includes the findings from the Discover Phase,
and sets the stage for the entire project (Note: There are also customers who create a first
version of the implementation plan at an earlier point in time, and as a necessary input for the
Business Case).
Common project preparation activities, like staffing, governance, or reporting requirements,
take place here as well.
Explore Phase: Define all details
As of the Explore phase, the implementation project split into several work streams:
 Project Management work stream: Performs common project and quality management
tasks, including project reporting. The Technical Quality Manager (TQM) from SAP is
included in all SAP S/4HANA service packages. The TQM is part of this work stream, and
jointly works together with the project manager (from the customer and/or the
implementation partner).
 Application: Solution Adoption work stream: This work stream handles Organizational
Change Management (OCM). In addition the training strategy and the learning paths for
the project team, key users, and end users are defined. The training of the project team
members takes place in this phase as well.

SAP ACTIVATE
 Application: Design & Configuration work stream: Identifies and designs functional
changes based on a Fit / Gap analysis, and SAP S/4HANA functionality in scope of the
implementation project. Moreover, it could be advisable to reduce data volumes before
converting to SAP S/4HANA to lower hardware resources and to help reduce downtime
in a system conversion scenario.
 Application: Testing work stream: Covers test planning and execution (integration,
regression, user acceptance).
 Analytics & Digital Boardroom work stream: Covers the analytics aspects of an SAP
S/4HANA implementation project.
 Custom Code Extensions work stream: Custom code potentially needs adjustment to
function properly with SAP S/4HANA. Affected custom code in productive use has to be
identified, and code adjustment has to be planned and executed accordingly.
 System & Data Migration work stream: The implementation of the SAP S/4HANA
systems (sandbox, copies of production, supporting non-production systems (e.g. DEV,
QAS, PRE…), and production) is planned in this work stream. Depending on the scenario,
it includes the migration from any database to SAP HANA, the implementation of SAP
S/4HANA, the conversion of business data into the new and simplified business data
model, or landscape transformation activities.
 Technical Architecture & Infrastructure work stream: SAP S/4HANA comes with SAP
HANA as the underlying database. The introduction of SAP HANA in customer’s data
center needs to be properly planned based on business and IT requirements.
 Transition to Operations: IT Operational procedures and tools need to be adjusted
before Go-Live to ensure safe operations. IT support experts need to be trained as well.
By the end of the Explore Phase, all technical and functional aspects of the implementation
project (e.g. solution scoping and content activation) are fully planned and documented in
detail, and ready for execution.
Realize Phase: Implement technical and functional changes
In the Realize phase, the technical architecture and infrastructure is prepared and set up for SAP
S/4HANA. Supporting systems are either set up or converted according to SAP best practices,
and according to the implementation plan. Custom code is adjusted to run on SAP S/4HANA.
Application and analytics functionality are implemented, configured and tested. Integration
Validation supports the Realize phase, e.g. by solving performance problems of key business
processes. In parallel IT can adjust operational tools and procedures to be prepared to operate
SAP S/4HANA. Finally, end user training including project specific training material, and team
setup are prepared as required. Key users are enabled for performing the end user training.
Deploy Phase: Prepare for Go-Live
The purpose of the Deploy phase is to finalize the readiness for SAP S/4HANA and the business
processes for production go live. This includes final testing, cut-over rehearsal, and IT
infrastructure and operations finalization. End user trainings are delivered by the enabled key

SAP ACTIVATE
users or by SAP trainers. Finally the implementation of the productive SAP S/4HANA takes place
on the Go-Live weekend.
Run Phase: Optimize the operability of SAP S/4HANA
With Go-Live, SAP S/4HANA is available for business users to log in and for productive use. IT
operations is further optimized (e.g. bug fixing, system availability, performance) with the help
of the project team and SAP. This phase is called “Hyper Care” before operational responsibility
is fully transferred to the production support team.
How SAP can help
The business transformation agenda is different from customer to customer. There are
customers who would like to understand their options first, and the opportunities deriving from
the discussion. Other customers have already decided to enter the transformation to SAP
S/4HANA. In all cases, SAP ensures that customer expectations are properly addressed with a
meaningful number of offerings that allow sufficient flexibility to support an agile
transformation.
That´s why SAP has structured all services supporting the implementation of SAP S/4HANA into
four service packages.
 SAP ActiveEmbedded for Planning & Safeguarding of SAP S/4HANA:

This package is for customers who would like to properly plan the digital transformation
together with SAP. The project execution is supported and safeguarded by SAP, but
executed by the customer and/or the implementation partner. As part of the
engagement foundation a Technical Quality Manager (TQM) supports the customer
project manager throughout the project, and builds the bridge to the Mission Control
Center at SAP. The technical and functional implementation is done by the customer
and/or the implementation partner.

SAP ACTIVATE
 SAP ActiveEmbedded for Technical Implementation of SAP S/4HANA:
On top of Planning & Safeguarding, SAP supports in defining the technical platform, and
runs the technical conversion of SAP ERP to SAP S/4HANA according to SAP Best
Practices. The functional design and implementation is done by the customer and/or the
implementation partner.
 SAP ActiveEmbedded for Functional Implementation of SAP S/4HANA:
On top of the Technical Implementation, SAP supports in the design of business priorities
(e.g. financial business processes of SAP S/4HANA). The functional implementation itself
is done by the customer and/or the implementation partner.
 SAP MaxAttention for Innovation with SAP S/4HANA:
This package is for SAP MaxAttention customers who would like to collaborate with SAP
and innovate beyond the conversion to SAP S/4HANA to start and transform their
company to e.g. “consumer first, smart services, Internet of Things, Boardroom of the
future and Re-Platforming your business” with SAP S/4 HANA. Functional gaps can be
addressed by co-innovation. Besides technical and functional implementation, SAP is
also supporting the adapting of custom code to SAP S/4HANA.
All service packages can be tailored to customer requirements. A short description of the entry
package calculation can be found in the Accelerator’s section.
The SAP S/4HANA service packages are built up by “services”. A service may support customers
in executing one or several activities. The following services have been newly designed to
support customers in an SAP S/4HANA implementation:
 Engagement Foundation
 Planning the Digital Transformation
 Build Design Support
 Build Execution Support
 LT (Landscape Transformation) Design Support
 LT Execution Support
 Analytics Design Support
 Analytics Execution Support
 Custom Code Management
 Platform Design Support
 Platform Execution Support
 Transition to Operations
 Safeguarding
 Hyper Care
Some of the services listed here are offered as fixed-price “Engineered Services”.
A service consists of one to many service components. This road map provides information how
a certain service component supports the implementation of an activity or task.
SAP ACTIVATE
The following picture shows the relationship between services and activities as part of the SAP
S/4HANA Implementation road map.
See the Accelerator’s section for a description of services and service components. Customers
who are interested in the SAP service packages can either contact their main SAP contact person
(SAP TQM in case of an SAP Premium Engagement customer, or the SAP Client Partner).
Alternatively customers can also ask for a tailored offer based on a scenario specific scoping (see
Accelerator’s section for contact form details).
In addition to the SAP S/4HANA service packages, SAP Enterprise Support customers should also
check the “Value Map for SAP HANA and SAP S/4HANA” (see Accelerator’s section), which lists
service offerings and learning modules for SAP Enterprise Support customers, as well as a
community environment for discussions and asking questions to SAP topic experts.
Accelerators:
 SAP S/4HANA
o Discover SAP S/4HANA
o SAP S/4HANA at SCN
o SAP S/4HANA Cookbook
 SAP S/4HANA Service Packages for SAP S/4HANA Implementation
o SAP S/4HANA Landing Page
o Service Entry Package Information
o Service Package – Overview information
o Service / Service Component Descriptions One-sliders
o Contact Form to Request Service Package Offer
 SAP Enterprise Support Value Maps

SAP ACTIVATE
o Value Maps
 SAP Activate
o General Information
o Solution Brief
o Methodology
o FAQ
Arun Obilisetty, Senior Director, S4H Program Management & Solution Delivery at vCentric
Technologies (P) Limited, India. A hands-on Project Manager and a Program Director with
19 years hands-on experience in SAP technology and 27 years of overall cross-functional
experience.
Arun is a SME, Solution Architect cum Process Specialist and a seasoned Delivery
Manager.

How to Approach Fit/Gap Analysis Workshops on-
premise
SAP Activate
SAP Activate Methodology
Fit/Gap Workshops in Explore Phase
Execute
Q-Gate Execute
Q-Gate Execute
Q-Gate
Execute
Q-Gate 
PREPARE EXPLORE REALIZE DEPLOY
Project Management
Initiation Proj Governance Project execution, Monitoring and Controlling Project Close
Proj Charter Proj Plan/Sched Baseline Cust Presentation Sprint Management Improvement
Kickoff WS Scope Stmt Rel/Sprint Plan Roadmap
Operational Std
Application: Solution Adoption
Onboard Proj Team
Value Determination Value Realization Comm Plan Value Audits Org Alignment Edu Readiness Knowledge Txfr End User Training Sup Readiness Survey
Change Mgmt Roadmap Stakeholder Analysis Training Content
Change Impact Analysis Value Realization
Application: Customer Team Enablement
Training Plan Project Team Training
Application: Design/ Fit-Gap
Scope Validation & Configuration
Analysis
Biz Proc Map Scope Validation Detailed Design Activate General Settings/MDO/Core/Delta Config
Biz Scenario (Workshop A) (Workshop B)
Biz Proc Procedure
Biz Solution Design Visualization
Pre-assem Demo Sprint Review Demo
Application: Integration
Pre-assem Demo Sprint Review Demo QAS Env PRD Env Failover Env
Application: Testing
Prepare Testing Policy Testing Strategy Scenario Test Int Test UAT Sys & Perf Test Tech Sys Test
Custom Code Extensions
Enhancements Detailed Design Enhancement Dev SOA/Composite App Dev
Technical Architecture & Infrastructure
Tech Req Proj Tools Tech Design Access & Security DEV Env QAS Env PRD Env Failover Env Go-live Check Go-live Verification
H/W Sizing Demo Env
System & Data Migration
DM Strategy Legacy Data Migration and Data Archive Prod Cutover
Cutover Plan Tech Integration Chk Post Go-Live Support
Phases
Work Streams Transition to Operations
Deliverables Tech Ops & Handover Plan Prod Support Transition Setup OCC
© 2016 vCentric Technologies (P) Limited. All rights reserved. 2

Purpose of Fit/Gap Analysis
 The primary objective is to have an updated and approved Scope

Baseline to move into the Realization phase
 Validate pre-activated or pre-assembled solution in Sandbox system
 Drive towards adopting SAP standard processes
 Ensure that SAP implementation meets customer’s business needs
 Discover, clarify and negotiate solution design
 Identify and capture delta business requirements and gaps (on top of the
initial Sandbox system)
 Prioritize delta requirements and gaps
 Prevent the need for rework during Realization

What happens during Fit/Gap analysis?
Workshop Type A Workshop Type B 7. Release &

Sprint Planning
Solution Validation Workshop Delta Design Workshop
1. Reference Value
• Provide Process, Value and
Strategic Context
• Set boundaries and expectations
• Tie to Business Case & Value
Drivers
6. Verify & Accept
• Verify process and solution
2. Validation of SAP design
Solution • Drive acceptance for release
and sprint planning
• Show and tell SAP
standard key design
elements
5. Delta Design
3. GAP Identification • Update Business Models
and Process Design for
• Identify and document delta requirements
gaps to standard;
• Solution Design and
• Log additional scope Visualize for the gaps
items 4. Backlog / Gap
Prioritization

Conduct Fit/Gap Analysis in Explore Phase
Outline of key steps
Prepare for Fit/Gap Analysis
 Download and review Best Practices documentation relevant for the project (based on SOW and Scope Statement)
 Setup Sandbox System based on CAL appliance (http://cal.sap.com) (or Activate Best Practices if not using CAL)
 Consultants to review Best Practices functionality in Sandbox and configure system for workshops (quick wins,
customer specific org. units and master data)
Conduct WS A – Validate Solution
 Set expectations with the business users; tie all discussion to business value and benefits
 Demonstrate the standard processes and guide customer towards adopting standard
 Identify and document delta requirements and gaps
 Prioritize all delta requirements and gaps
Conduct WS B – Conduct Delta Design Workshops
 Prepare solution design for the identified delta requirements and gaps
 Visualize application for areas that require changes
Prepare Release and Sprint plan for Realize phase
 Prioritize Backlog with delta requirements and gaps
 Estimate relative effort of all changes
 Prepare Release and Sprint plan for Realize phase
Validate Solution– Key Example
Explore
Prepare for Fit/Gap Solution Validation Identify Deltas / Prioritize Design Solution
Workshops Workshops Make key Decisions Deltas for Deltas
Complete
Realize documentation
Execute
Phase Closure Roadshow Set up DEV
Cleanse communications
and Sign-off system for
data plan
configuration
Design and
set-up user Deploy
roles and
security Set up QA system User Integration Design end-user Roadshow Phase Closure
environment for Testing training and begin and Sign-off
integration testing documentation

Critical Path Documentation and Dependencies
Scope Solution Validation Delta Design Solution Build & Test

(WS A) (WS B)
Business
Authorization
Process
Concept
Config. Procedures
Gap List /
Business Process Business Scenario
Requirements Document /
Case Maps Scen. Des. Test Scripts
Rational
OCM &
BP Key Decision Process OCM & Unit
SOW Training
Hierarchy Document Flow Training Test Scripts
Strategy
Functional
BP Test WRICEF Technical
Specs /
Scripts List Specs
UX Design
Data
BP Process Master data
Migration
Flows Design
Design
Org. Technical Development Quality

Sandbox Structure Integration System System
System Design Design (DEV) (QAS)
(SND)
Prepare Explore Realize

Critical Path Documentation Location and Links
SAP Best Practices in SAP Best SAP Activate Methodology in SAP Solution Manager
Practices Explorer Roadmap Viewer
Download BP content from SAP Best Practices Understand the SAP Activate approach Download Best Practices for SAP S/4HANA
Prepare
Explorer • Review Transition to SAP S/4HANA roadmap in content into SAP Solution Manager 7.2
Roadmap Viewer
• Go through ACT10e (SAP Activate course)
Review Best Practices content Download templates for WS A and WS B: Capture Business Requirements in Solution
• Business Process Maps • Key Decision Document (A & B) Manager 7.2, attach process documents like
• Scope Item Descriptions • Business Scenario Design (B) Business Scenario Design, Functional Specs,
Explore
• Test Scripts (BPP like documents) • WRICEF List (B) etc.

• Organization Structure and Master Data • Functional Specifications (B) Update Process Models in Solution Manager
Optional: Gap List / Requirements (A & B) – capture

results from WS before transfer to SAP Solution
Manager 7.2
Realize
Activate Best Practices in DEV environment Capture technical design documents,

Finalize Technical Design
• Scope determined in Explore during Fit/Gap configuration documentation and key decisions
• Technical Specifications
Analysis inside SAP Solution Manager.

Prepare for Fit/Gap Workshops
Checklist: Prepare for Fit/Gap Analysis Workshops
1. All project team members need to understand the scope of the project (review SOW and Scope
Statement)
2. Download and review Best Practices documentation relevant for the project (based on SOW and
Scope Statement)
3. Setup Sandbox System based on CAL appliance (or Activate Best Practices if not using CAL). Activation
guidance using both methods can be found in the “Activate Best Practices” pages in the Reference Guide
4. Consultants to review Best Practices functionality in Sandbox and configure system for workshops
(quick wins, customer specific org. units and master data). Additional details can be found in the “Test
SAP Best Practice Activation” page in the Reference Guide.
5. Schedule workshops (book rooms, invite participants, explain purpose/goals)
6. Prepare workshop materials (templates to document results, slides to run workshop, confirm system is
configured, and confirm access to process flows)*
* Refer to Slide 8 for links to templates

Understand the SAP Best Practices
Content in 3 Layers
EDITION
A selection of scope items that cover the scope of the next-generation S/4HANA Business Suite or other leading
industry or Line of Business segments. Editions are available on cloud or on-premise and can be implemented
fully or partially.
Currently the following editions are available: on-premise Enterprise Edition, Cloud Enterprise Edition, Cloud
Marketing Edition and Cloud Professional Services Edition.
SCOPE ITEMS
Typically a pre-defined business process, such as sales order processing. They represents a Best Practice
implementation choice for a customer. Each scope item has a set of accelerators delivering detailed
documentation that is used during the implementation project. Scope items require specific building blocks to
be implemented.
BUILDING BLOCKS
A set of configuration for a piece of business content such as credit management. The accelerators include the
configuration content to implement the scope item(s) and project documentation for the building block.

SAP Best Practices Content
Example Project Accelerators
Example Accelerators
EDITION • Customer presentation: overview presentation of Edition

• Content Library: web page with links to all the content in the Edition
• Project schedule: example implementation project schedule
• Prerequisite matrix: relationship between Scope Items and Building Blocks
Edition • Delivery supplement: key implementation information
• Admin Guide for SAP S/4HANA & SAP Note *: detailed instructions
• Software and delivery requirements *: precise software releases required
• Master Data Overview: describes master data used in the Edition
SCOPE ITEMS
• Scope-item fact sheets: scope description of each scope item
• Process diagrams: graphical BPML process diagram with roles
• Test scripts: step by step process documentation with data
• Building-block fact sheets: description of each building block

BUILDING BLOCKS • Activation content*: content to automate the configuration
• Configuration guides: detailed documentation of configuration settings
* on-premise edition only

Documentation of SAP Best Practices for SAP S/4HANA
Process diagrams – how to access
Process Documentation
SAP Solution Manager
SAP Best Practices

Explorer

SAP Best Practices Content
Assets in SAP Solution Manager - Example
• Process models
Get a head start in defining your solution by
selecting from a SAP Best Practices process
library complete with process models,
process diagrams, test scripts, and links to
executables, such as Fiori apps, in your
solution.
• Configuration
Understand and document how SAP Best
Practices are configured in the configuration
guides and activate or adjust the
configuration in your solution.
• Project guidance
Import (WBS) templates based on SAP
Activate* to understand the typical project
tasks and prepare your own projects.
Import SAP Best Practices easily and at no extra

cost in the Solution Administration app in your
SAP Solution Manager 7.2 system.
Solution documentation with SAP Best Practices in SAP Solution Manager 7.2

Understand Key Functions of SAP Solution Manager
Customers can choose which capabilities
of SAP Solution Manger to use in their Details provided in Reference
project. The following capabilities may be Guide under Introduction ->
used any on-premise or hybrid Tools -> SAP Solution
implementation: Manger.
• Business requirements and IT

requirements: central storage of
requirements along the SAP
S/4HANA implementation lifecycle.
• Project management: plan and
manage the schedule and resources
for your implementation.
• Process management: SAP
Solution Manager 7.2 provides a new
way to manage your business
processes with a new user interface
and integrated process diagram
editor.
• Change and release management:
provide change deployment control
and risk mitigation.
• Test management: test and deploy
your SAP S/4HANA solution keeping
track of all test scripts, test cases and
test results

Schedule Workshops
Sample Fit/Gap Workshop Schedule
Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Week 9

M T W T F M T W T F M T W T F M T W T F M T W T F M T W T F M T W T F M T W T F M T W T F
Joint Team WS A: Solution Validation Workshops WS B: Delta Design Final review
preparation Workshop and approval
Gap assessment, definition, prioritisation

Validation WS output finalisation & signoff
Team enablement WS approach
Joint workshop preparation
Documentation & housekeeping
Org Structure workshop
Financial Accounting (FI)
Management Accounting (CO)
Sourcing, Procurement and Supply Chain (MM)
Sales (SD)
Manufacturing (PP)

Schedule Workshops
Validation Workshops Example - Finance
Workshop Workshop Scope Scope items to be covered
Focus
Finance Finance
Enterprise Structure / Chart of Accounts
General Ledger
Accounts Payable & Receivable J59, J60
Credit Management BD6
Period End Closing FI Accounting J58
Cash Management J78,J77
Asset Management J62
Cost Center Planning BEX,J54
Internal Order BEU, BEV
Standard Cost Calculation (Plan) BEG
Period End Closing "General" Plant BEI
Inventory Valuation for Year End Closing-IFRS BEJ
Profitability and Cost Analysis J55
Revenue Planning BEA
Reporting on Accounting BHA

Schedule Workshops
Validation Workshops Example – Sales & Procurement

Focus
Sales Sales
Sales Master Data
Sales Quotation BDG
Sales Order Processing BD3, BDH, BDK, BKJ, BKX, BKZ
Sales Order processing BD9, BDA, BDN, BKA,
Memo's BDQ, BKL
Returns and returnables BDD, BDW
Period End Closing Operations BKK
Sourcing, Sourcing, Procurement and Supply Chain

Procurement Procurement Master Data
and Supply
Chain Operational Procurement BMR,BNX, J45
Inventory and Basic Warehouse Management BMC, BMK, BML
Procurement Contract BMD

Schedule Workshops
Validation Workshops Example – Manufacturing and Services
Focus
Manufacturing Manufacturing
Manufacturing Master Data
Manufacturing Planning J44
Manufacturing Execution BJ5, BJ8, BJH, BJK, BJN, BJQ

WS A: Solution Validation WS
What happens during Solution Validation work shops (WS A)

Sprint Planning
Solution Validation Delta Design
1. Reference Value
Strategic Context
• Set Boundaries
• Tie to Business Case, Value
Drivers
6. Verify & Accept
• Verify process & solution
2. Validation of SAP
design
Solution
• Drive Acceptance
standard key design
elements
5. Delta Design
and Process Design
• Identify and Document
gaps to Standard Log
Visualize
additional scope items
4. Backlog / Gap
Prioritization

WS A: General Solution Validation Workshop Flow
Meetings for Customer First workshops Second workshops

to introduce their validate process and define gaps and
business roles validates process steps
Gaps refined
during realize
Detail workshop plan
Demo Demo
and preparation
Solution Solution
Inputs Outputs
• Contract Scope Document • Updated Backlog / Gap List
• Development System • Decision, assumptions and business impacts
• Best Practice process diagrams • Process diagrams updated by customer
• Test Scripts
• Gap list from bid phase

General Validation Workshop Principles
Workshop best practice should still be followed:
 Preparation meetings with customer business leads to allow them to introduce their business and
processes. Allow consultants to prepare workshops (not a detailed as-is analysis).
 Plan in detail with templates for workshop inputs and outputs.
 Set boundaries at start of each workshop.
 Provide process, value and strategic context at start of each workshop.
 Focus on business value and tie to business case and value drivers.
 Ensure process diagrams include roles (swim lanes): this helps business to engage.
 Prioritize scope and gaps.
 Document decisions, assumptions and business impacts of new processes.
 Produce detailed documentation immediately.
 Formal sign-off of the Gap List before realize phase starts.

Gap Definition – Gap types
Gap = Any item that is not part of the standard service scope
1. Process gap
 Process is not part of the preconfigured best practices
 Predefined process needs to be adjusted
2. Reporting gap - standard baseline report is not adequate or does not exist
3. All non-standard interfaces
4. All workflows
5. Any enhancements to standard software
6. Organizational structure not included in the SAP Best Practices
7. Changes to standard predefined authorization roles or new business roles
8. Forms – any changes to the standard predefined forms – apart from company logo and address data
9. Data migration and conversion

Demo Solution based on SAP Best Practices
Walk through Process and Demo SAP

 Make sure business SMEs understand our SAP standard
solution
 Show predefined process flows / SAP Solution Manager
Process Hierarchy and Best Practices Documentation
 Show Standard functionality in Sandbox System
 Dry Run process walk through prior to session, add
customer specific data where applicable
Workshop Efficiency
 Time is limited
 Require participants to review BPDs and Process flows
prior to workshop to make informed decision
 Solution Validation is not a training session
 Time box to drive decision making
 Table parking lot items

Using Test Scripts for Demo Purposes
Access the Scope Item Process

Diagram, Process Model and
Test Scripts within the Best
Practices Explorer in the Scope
Item details to explain and demo
the S/4HANA solution
functionality.
Please refer to the Best Practice

Explorer for details.
You can download the complete

BP package from BP Explorer
and use documentation locally.

Download BP Documents from BP Explorer
1. Access Best Practice

materials in BP
Explorer.
2. Click on the
download button to
access Download
Manager and start
download of the
package
documentation.

Documentation of SAP Best Practices for SAP S/4HANA
Process diagrams – how to access
SAP S/4HANA Process Documentation

Implementation Cockpit
SAP Solution Manager
SAP Best Practices in

SAP Service Marketplace
SAP Best Practices

solution builder

Capture Gaps in Backlog list during WS A
Identify Gaps - Listen, Learn, Challenge and Complement

 Once you identify gasp, challenge them, drive customer to
adopt SAP standard process where possible
 Capture and validate gap requirements in Backlog template
– What do you need to do?
– How does that work?
– Why is that important?
 Determine Requirement / Gap Owner
Gap
 Close the loop to the Business Case (how does the gap tie to
value?)
 Leverage parking lot to table discussion and drive time line
Tool Set / Methodology
 Solution Manager – Requirements Mgmt., Business Process Hierarchy, BP Models
 Backlog / Gap List
 Key Decisions Documents (optional)

Gap Handling and Documentation
Gap Type Workshop A Workshop B

Process gap Provide details in Business Scenario Design Document
(load into Solution Manager) and update Process Models in
Solution Manager
All Workflows Provide details in the “FS-Workflow” template from the

Functional Specifications zip file and load into SM
Reporting gap Provide details in the “FS-Reports” template from the

All non-standard interfaces

Capture requirement in Backlog Provide details in the “FS-Interfaces” template from the
Template, confirm with customer Functional Specifications zip file and load into SM
Data Migration and conversion and then create corresponding Provide details in the “FS-Conversions” template from the
business requirement in SAP
Any enhancements to software Solution Manager + attach all Provide details in the “FS-Enhancements” template from
the Functional Specifications zip file and load into SM
additional documentation
Forms Provide details in the “FS-Print Forms” template from the
Organizational structure not included in Best Practices Enhance Best Practices documentation with customer
specific org structure
Changes to standard predefined authorization roles or new Define Business User Role Document and create role
business roles authorization matrix (i.e. Role Mapping Sample)

Process Validation Approach
Process Covered by Best Practices or RDS

SAP Best Practices exist for the process then utilize the test scripts, business process model and scope item
description to determine if there is a need for delta requirements of if a gap exists. See the details on preceding
pages.
BP or RDS do not cover the process, but standard practice is known

If process is not covered by SAP Best Practice or RDS then determine if standard process practices (i.e.
common consulting knowledge/experience around a business process) can be used to address the required
functionality.
Determine if you can prototype the process/functionality in Sandbox system or if you need to prepare off-line
demo or visualization of the functionality for WS A. Also refer to solution documentation, help files and
compatibility list for SAP S/4HANA.
Known Gaps
Capture the requirement in the backlog and defer any detailed solution design to Workshop B for further
analysis.

Solution Manager: Requirement and Gap Documentation
The new requirements and gaps,

identified during the workshops should
be documented in SAP Solution
Manager 7.2. Additional information
about the business requirement should
be recorded in the appropriate
templates and loaded into Solution
Manager. Please refer to the Reference
Guide (Explore -> Analyze the Business
Processes ->Document New
Requirements and Gaps) for detailed
instructions.

WS A: Validate Solution – Summary
Prepare for Fit/Gap Solution Validation Identify Deltas /

Workshops Workshop A Make key Decisions
SOW Process Map Business Scope Item Backlog / GAP Key Decision
Scenario Process Flows List – as Document
requirements
in Solution
Business Manager
Process
Hierarchy
Deploy
Upload to Solution
Manager
Store in project
repository * Refer to slides #29-31 for links to templates
Key Components of WS A to Validate Solution
Reference / Set Expectations Review Process Demo Solution
Drive towards Standard, Identify Gaps, Log Parking Lot Items

Backlog / Gap List Prioritization
What happens during Backlog / Gap Prioritization

Sprint Planning
1. Reference Value
Strategic Context
• Set Boundaries
Drivers
6. Verify & Accept
design
Solution
standard key design
elements
5. Delta Design
and Process Design
Visualize
4. Backlog / Gap
Prioritization

Prioritize Backlog with Gaps
Prioritize Gaps in the Backlog

 Business users (gap owners) are responsible for setting
the priorities
 Project Team provides technical and application insight
to support prioritization – e.g. reflect the technical and
functional dependencies
 The backlog will provide input into scheduling the delta
design workshops – it will help define the schedule of
WS B and focus.
 Backlog Completion Considerations
– Identification of delta requirements and gaps /
requirements
– Assign Owner
– Association with SAP business process
– Prioritization of log items

Gap Validation
For customers with SAP Premium Engagement Services
Validate Gaps with SAP’s Control Centers
Within Premium Engagement projects, the Innovation

Control Center (ICC ) enables the project team to
validate integration projects and prepare for smooth
operations, enabling agile & continuous deployment of
changes to the customer system.
Customers can use the innovation control center

dashboard to easily access an overview of the ICC
project status, view message details, and create a work
list to search and filter messages. In addition, project
teams can submit gaps to the MCC for validation using
transaction SMFG.
For additional details about working With Functional

Gap Messages and Incidents in the ICC Dashboard
access the ICC Help File .

WS B: Delta Design
What happens during Delta Design Workshop (WS B)

Sprint Planning
1. Reference Value
Strategic Context
• Set Boundaries
Drivers
6. Verify & Accept
design
Solution
standard key design
elements
5. Delta Design
and Process Design
Visualize
4. Backlog / Gap
Prioritization

Delta Design for Gaps (WS B)
Delta Design for Functional Gaps

 Design for prioritized Backlog items (Gaps and Requirements)
 Drive solution design actively – steer to standard if possible, aim to
minimize the impact of modifications with outlook to the future
 Pick-up where you left off in WS A – leverage process flows
 Visualize solution design for functional gaps
 Capture requirements based on feedback
 Create Scenario/Process design documentation and store
Functional Specifications in SAP Solution Manager
Gap
 Consider integration aspects of the solution
 Drive early approval
 Expect iterations

Delta Design – Key Example
Backlog / GAP
Delta Design
List – as Scope Item
Workshop
requirements in Process Flow
Agenda
Solution
Kickoff Solution Solution Validation Identify Deltas / Prioritize Design Solution
Validation Workshops, AP 158 Make key Decisions Deltas
Manager 7.2 for Deltas
Details provided in Reference Guide Workshop B
under Explore -> Analyze the
Business Processes -> Document
New Requirements and Gaps:
Reference Guide
Realize
Complete
documentation
Organization Business Business Master Data WRICEF List Functional

Structure Process Process Flow Specification
Final Prep
Upload to Solution
Manager

Take Away
Take Away - Recommendations
 Use of the pre-delivered content and solution is key to executing the fit/gap analysis workshops…
– “This process is developed using SAP Best Practices”
– “This is delivered out of the box functionality”
 Get confirmation of the process during the workshop and note gaps as applicable; don’t try to solve the gap during the
solution validation workshop (WS A)… Note it only and move on or you won’t finish….
 Answer questions phrased with “Can the system do this?” carefully… you need to ascertain if it’s a real business
requirement quickly or note it as a gap and move on….
 The workshops are process driven and more time needs to be spent clarifying master data requirements.. You may pay for
lack of attention to this later with extra work on master data conversions….
 Scheduling workshops can be difficult with a wide audience that has other priorities besides SAP implementation. PMO and
Customer Mgmt. need to emphasize clearing of calendars and 100% attendance.
 Get to know your customer team and align planned time requirements for each member before the workshops to insure
positive attendance and commitment
 Need to plan more effectively for integration workshops to cover key integration process such of OTC (Create Order,
Delivery, Billing, A/R collection), PTP (Create Purchase Order, Receive product, Pay Vendor) and PTM (Plan Output, MRP,
Create and Execute Order, Settle Order)

Activate and Fit-Gap

Uploaded by

Copyright:

Available Formats

Activate and Fit-Gap

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Activate and Fit-Gap

Uploaded by

Copyright:

Available Formats

What are the different SAP S/4HANA implementation scenarios discussed in the document?

What are the different SAP S/4HANA implementation scenarios discussed in the document?

What methodology does SAP recommend for SAP S/4HANA implementations and what does it cover?

What methodology does SAP recommend for SAP S/4HANA implementations and what does it cover?

SAP ACTIVATE

Road Map for SAP S/4HANA Implementation

SAP sees three implementation scenarios to SAP S/4HANA:

© vCentric Technologies (P) Limited Page 1 of 9

© vCentric Technologies (P) Limited Page 3 of 9

© vCentric Technologies (P) Limited Page 4 of 9

© vCentric Technologies (P) Limited Page 5 of 9

 SAP ActiveEmbedded for Planning & Safeguarding of SAP S/4HANA:

© vCentric Technologies (P) Limited Page 6 of 9

© vCentric Technologies (P) Limited Page 8 of 9

© vCentric Technologies (P) Limited Page 9 of 9

© 2016 vCentric Technologies (P) Limited. All rights reserved. 2

 The primary objective is to have an updated and approved Scope

© 2016 vCentric Technologies (P) Limited. All rights reserved. 3

Workshop Type A Workshop Type B 7. Release &

© 2016 vCentric Technologies (P) Limited. All rights reserved. 4

© 2016 vCentric Technologies (P) Limited. All rights reserved. 6

Scope Solution Validation Delta Design Solution Build & Test

Org. Technical Development Quality

Prepare Explore Realize

© 2016 vCentric Technologies (P) Limited. All rights reserved. 7

• Test Scripts (BPP like documents) • WRICEF List (B) etc.

Optional: Gap List / Requirements (A & B) – capture

Activate Best Practices in DEV environment Capture technical design documents,

© 2016 vCentric Technologies (P) Limited. All rights reserved. 8

5. Schedule workshops (book rooms, invite participants, explain purpose/goals)

© 2016 vCentric Technologies (P) Limited. All rights reserved. 10

© 2016 vCentric Technologies (P) Limited. All rights reserved. 11

EDITION • Customer presentation: overview presentation of Edition

• Building-block fact sheets: description of each building block

* on-premise edition only

© 2016 vCentric Technologies (P) Limited. All rights reserved. 12

SAP Solution Manager

SAP Best Practices

© 2016 vCentric Technologies (P) Limited. All rights reserved. 13

Import SAP Best Practices easily and at no extra

© 2016 vCentric Technologies (P) Limited. All rights reserved. 14

• Business requirements and IT

© 2016 vCentric Technologies (P) Limited. All rights reserved. 15

Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Week 9

Gap assessment, definition, prioritisation

© 2016 vCentric Technologies (P) Limited. All rights reserved. 16

© 2016 vCentric Technologies (P) Limited. All rights reserved. 17

Workshop Workshop Scope Scope items to be covered

Sourcing, Sourcing, Procurement and Supply Chain

© 2016 vCentric Technologies (P) Limited. All rights reserved. 18

© 2016 vCentric Technologies (P) Limited. All rights reserved. 19

Workshop Type A Workshop Type B 7. Release &

© 2016 vCentric Technologies (P) Limited. All rights reserved. 21

Meetings for Customer First workshops Second workshops

© 2016 vCentric Technologies (P) Limited. All rights reserved. 22

Workshop best practice should still be followed:

© 2016 vCentric Technologies (P) Limited. All rights reserved. 23

© 2016 vCentric Technologies (P) Limited. All rights reserved. 24

Walk through Process and Demo SAP