Phase 1: Project Preparation - The purpose of this phase is to provide initial planning and preparation for your SAP project. Phase 2: Business Blueprint - The purpose of this phase is to achieve a common understanding of how the company intends to run its business within the SAP System. The result is the Business Blueprint, a detailed documentation of the results gathered during requirements workshops. The Business Blueprint document represents the business process requirements of the company. It is the agreed statement of how the company intends to run its business within the SAP System. Phase 3: Realization - The purpose of this phase is to implement all the business process requirements based on the Business Blueprint. The system configuration methodology is provided in two work packages: Baseline (major scope); and Final configuration (remaining scope). Phase 4: Final Preparation - The purpose of this phase is to complete the final preparation (including testing, end user training, system management and cutover activities) to finalize your readiness to go live. The Final Preparation phase also serves to resolve all critical open issues. On successful completion of this phase, you are ready to run your business in your live SAP System. Phase 5: Go Live & Support - The purpose of this phase is to move from a project-oriented, pre-production environment to live production operation.

1. SAP Project
Implementation
Phase
Strategy • Roadmap
Ainul Hossain Tushar
Associate Consultant – PP
ainul.tushar@exzatech.com

2. © 2016 Exzatech. All rights reserved.
ghts reserved.
Mission and
objective of the
SAP project
Project initiation
and planning
Critical success factor
Implementation
Strategy
Project Management
SAP Implementation
Methodologies
SAP
Implementation

3. © 2016 Exzatech. All rights reserved.
ghts reserved.
Implementation strategy
Big Bang Implementation of SAP
Modules
Base Modules Implemented First
Implementation of SAP Standard
Functionality
Pilot Site Implementation Followed By
Rollouts at Other Sites
Utilize External Consultants to
Primarily Train in In-House Consultants
Centralize or Decentralized SAP
Configuration
User-Driven Functionality

4. © 2016 Exzatech. All rights reserved.
ghts reserved.
Project Management Committee
Program Manager Braknet Program Manager Client
Project Manager
Brcknet
Client
QA review team
Quality, Competency &
Delivery Framework
Quality Manager
Delivery Manager
CoE Lead
Steering Committee
. . .
Project Manager
Development
Lead
Functional &
Technical Lead
Functional
Consultants (Leads)
IDE / Interface
Lead
Middleware
lead
ABAP Developers
Functional
Consultants
IDE
developers
Middleware
Developer
BASIS
Domain
Expert
Typical Organization Structure for Implementation Projects

5. © 2016 Exzatech. All rights reserved.
ghts reserved.
Implementation
Roadmap
Phase 2
Business Blueprint
Phase 3
Realization
Phase 4
Final Preparation
Phase 5
Go Live & Support
Phase 1
Project Preparation
1
2
3
4
5

6. © 2016 Exzatech. All rights reserved.
ghts reserved.
Goal settings
Define the project goals and objectives
Team
Core Team+ Project Team+ Consultant Team
Implementation strategy
1.Clarify the scope of implementation
2.Establish the project organization and relevant committees and assign resources
Sign off
At the end of phase every above step will be documented and will sign off with client
Implementation Sequence
Define sequence of the project has to be executed

7. © 2016 Exzatech. All rights reserved.
ghts reserved.
The purpose of this phase is to achieve a common understanding of
how the company intends to run SAP to support their business.
Also, To refine the original project goals and objectives and revise the
overall project schedule in this phase.
The result is the Business blueprint, a detailed documentation of the
results gathered during requirements workshops

8. © 2016 Exzatech. All rights reserved.
ghts reserved.
Scope Document
This Document will consists of questionnaire of entre Business process
AS IS
1.Understanding the Business process from Core Team
2.Based on the Input AS IS document has to be created according to module wise
TO BE
1.In this process you will map the Business Process in SAP based on ASIS
2. Module wise TOBE document has to be created
GAP Analysis
1.The GAP b/w AS IS process and TO BE process is called GAP analysis i.e. The input
or business process which can’t be mapped in standard SAP will be analyzed here
2. GAP documents has to be created
Sign Off
Each process above has to be taken sign off from client

9. © 2016 Exzatech. All rights reserved.
ghts reserved.
The system configuration methodology is provided in two work
packages.
Baseline (manner scope) &
Final configuration (remaining
scope).
The purpose of this phase is to implement all the business process
requirements based on the Business Blueprint.
In this phase also we have create documentation for the
configuration implemented & it has to be taken sign off from client.

10. © 2016 Exzatech. All rights reserved.
ghts reserved.
Sl. No Process Description
1. Unit testing Testing with each module
2.
Integration
testing
Integrate testing of module i.e., combine
testing of all the modules which is
implemented
3.
User training
and testing
End users of each module will be provided
training by corresponding module consultant.
End user training document and user manual
has to be prepared . This document has to be
taken sign off from the client.
4.
Cut over
strategy
Before Go live phase there will cut-over period
for business process is carried . During cut over
period the master data and transaction data
from legacy system will be migrated to SAP
system . There are various tools for this
purpose LSMW, SCAT, BDC

11. © 2016 Exzatech. All rights reserved.
ghts reserved.
The purpose of this phase is to move from a project-oriented, pre-
production environment to live production operation.
The most important elements include setting up production
support, monitoring system transactions, and optimizing overall
system performance.
Support
• After Go-live the system is kept under motoring for
support for a small period.