Composition of the ASAP Methodology Framework

SAP leverages a core set of methodologies and tools designed to deliver rapid, reliable results,
and to help our customers get the most from their solutions. These include the ASAP
Methodology framework.

Phase 1: Project Preparation

This phase is about the initial planning and preparation to set ASAP goals. The phase follows the
following three steps:
1. Clarifying scope of implementation
2. Establishing the team committees, teams (core, project and consulting)
3. Defining the sequence of project implementation
These are standardized steps of Phase 1. However modifications (additions) can be made as per
quality procedures of the partner.

Phase 2: Business Blueprint

The aim of this phase is to arrive at a common understanding concerned with the procedures
intended to support the project and run SAP. The Business Blueprint is a detailed documentation
of all requirements arrived at during the initial brainstorming and initiation workshops. This is
also where the project team revises its objectives and goals while setting a schedule for each.
Phase 3: Realization

This phase is concerned with implementation of all business process requirements and is based
upon Phase 2. Two work packages define the system configuration methodology: Baseline,
concerned with the major scope and Final Configuration, concerned with the remaining scope.

Further, project managers need to come up with configuration documentation to be signed off by
the client.
Phase 4: Final Preparation

The final preparation involves testing, system management, cut over activities and end user
training that showcases the teams readiness to go live. This phase serves to answer all critical
issues concerning the project management. Successful completion of Final Preparation ensures
that the business ready to be run on the live SAP System.
Phase 5: Go Live and Support

This phase is the journey from a pre-production environment to a live project operation. The
most critical elements in this phase concerns with the setting up of production support, monitor
system transactions and optimize the system performance.

Phase 6: Operate
In this phase user will start working on the production system.
Implementation
Typical Customer Use Cases
who is involved in the project?
(For example: Does business reengineering require that the business process experts are
Involved with requirements and design?)
When have the deliverables to be generated?
(For example: Deliverables across heterogeneous teams require templates to provide a common
Understanding on tasks and activities.)
What has to be done by whom?
(For example: Complex business teams require clear work lists and strong and transparent
Planning.)
How to control and report the progress of
each phase?
Unstandardized business processes across scattered business landscapes
Different implementation approaches
and strategies
Missing link between business process documentation and technical
realization
No flexibility for business process adjustments leads to a long time to
benefit
No harmonized Release- and
Version Management across the application landscape