Professional Documents
Culture Documents
Implementation Phases
1. Project Preparation
2. Business Blueprint
3. Realization
4. Final Preparation
5. Go Live
6. Post-Production Support
Realization
Go Live
See results
Phases of ASAP Methodology
The ASAP methodology prescribes a correct pathway for SAP implementation projects. It consists of
six steps, the 6 major phases of SAP implementation:
Pre-sales, Preparation, Business Blueprint, Realization, Going Live, and Post-Production. Here we
are going to discuss all the steps in detail.
1. Pre-sale of ERP. In this pre-sale phase, ERP (SAP) tries to get the project from the client.
Most clients consider more than one option for their business and then give all options a try to
see which one provides the best result. In most cases, clients get the ERP software license
directly from the software companies. This step may or may not include a test to check which
ERP system is most suitable for the client.
2. Preparation. Once a client decided has decided on its ERP system, then they prepare the
landscape of the project. In this step, server information, project cost, resources, Subject Matter
Experts (SME), and business teams are decided by the PMO (the Project Management
Organization). It consists of project managers, a steering committee, core business members,
and sponsors. A project team studies legacy systems and gathers information regarding core
systems, interfaces, what interfaces the client wants, what is necessary, what is nice to have,
etc. The core team carries out "as-is" studying, a study of the current system and its processes.
The project management team also hires resources and carries out project planning and
outline.
3. Business Blueprint. In this phase, the core team does "GAP analysis," an analysis of the
differences between the system as is and the system to be studied. Allocated resources write
down the rules and requirements for the new system. Integration points, interfaces and process
maps are finalized. Functional consultants write the functional specification. If needed technical
specifications are written down for developers to do further configuration. A testing team also
started working on preparing testing steps and scenarios. Financial specifications and technical
specifications are created in this step for further development and configurations.
4. Realization. In the realization step, functional consultants carry out configuration. Development
is done for the required customization. Testing is carried out by the core team. Basis
configuration is carried out by the security team. A basis team moves all configurations from
one server to another for testing purposes. Testing is mostly done in the quality control server.
All the configurations upload master data across all modules (sample load of few parts or entire
data end as per client wants). Unit testing and integration testing has been done by the testing
team. Unit testing, integration testing, and day-in-the-life testing happen at this stage.
5. Pre-Goes-Live Phase In this step, all configurations from the golden client will be moved to
other services. Uploading master data into the new system is done mostly using LSMW, BAPI
or BADI. Cut-over activities are done only when we stop the legacy system and start using the
SAP system. End-user training and user documentation are carried out in this pre-go-live stage.
After all cut-over activities, SAP implementation goes live in a production environment.
6. Post-Production Support. In this step, the team helps the client to solve if any production
issue came regarding configuration, master data change, or transaction issues. Also, the team
will provide training to users and super-users. All the support documentation work has been
completed in this step.
In a Nutshell
ASAP Methodology is just a project implementation methodology created by SAP itself. In ASAP
methodology, the project is broken down into six phases. This provides ease in completion and gives
an easy focus for the project management team.