SAP PP IMPLENTATION PROJECT STEPS.

1. We will follow ASAP Metholodlegy, its having 5 steps.

A. Project preparation
B. Business blue print(BBP)
C. Realization.
D. Final prepararion
E. Go live support.
F. Post Production support.

A.Project preparation: SAP Team, Business heads, are Involved in this phase. Here AS-IS, To-BE, After
completion of these documents we will go for Sign Off.(CTM s(Core team members, client IT Manager,
Funtional heads, sap Team manager, functional consultants are involved.

ASAP stands for Accelerated SAP. Its purpose is to help design SAP implementation in the most efficient
manner possible. Its goal is to effectively optimize time, people, quality and other resources, using a
proven methodology to implementation

B. Business blue Print Phase (BBP): Before prepare the document we had a meeting with business
team,Funtional heads, sap Team manager, functional consultants are involved,client side IT manager
involed in this meeting,here we will disciuss GAP analaysis in business process.

This Document contains Entire client business process,GAP analaysis ,SAP functional process.
After that we will GO for sign OFF.

C. Realization:Here we will configure the sap system as (BBP)per client requirement after configuration
we will do unit testing,after unit testing we will integration testing with other modules

The purpose of this phase is to implement all the business processes based on the Business Blueprint.
The system configuration methodology is provided here in two work packages: Baseline (major scope)
Final configuration (remaining scope)

Final Preparation: In this phase we will do cut over activity by using lsmw or BDC.(cut over activity
means uploading master data into sap.)
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 purpose.
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.

Golive Support:

What Is ASAP Methodology?

ASAP stands for Accelerated SAP. ASAP Methodology is one of the important Software Development Life
Cycles (SDLC) used for SAP Implementation projects. SAP is one of the best ERP systems, and ASAP
Methodology is the way SAP implementation happens.

SAP projects are long and intense. They require lots of effort and many resources from developers and
managers. It can be really tricky if SAP projects are not planned in a proper form. SAP itself gives a
proper methodology to design the project so it will give reliable results.

The ASAP methodology provides the proper framework for an implementation roadmap. SAP
Implementation consists of several phases that include every stage of software development lifestyle
(SDLC) for SAP implementation. ASAP Methodology divides a project according to these vital phases.
Each phase is considered a milestone. The project management team can concentrate on the current
phase and start preparing for the next phase. This also provides a better roadmap and work distribution.
The ASAP methodology provides a framework for SAP projects for implementation and enhancement as
well for the customization needed for production support.

SAP Implementation Phases

Here are the six phases of a SAP implementation project:

Project Preparation

Business Blueprint

Realization

Final Preparation
Go Live

Post-Production Support

ASAP Methodology—SAP Implementation Phases

Which Phase of ASAP Methodology is Most Important?

Top of Form

Business Blueprint

Realization

Go Live

See results

Bottom of Form
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:
Presales, Preparation, Business Blueprint, Realization, Going Live, and Post-Production. Here we are
going to discuss all the steps in details.

Presale of ERP. In this presale phase, ERP (SAP) try 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.

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.

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.

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
purpose. 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 are testing happen at this stage.
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.

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.