Skip to Content

Basic understanding on ASAP Methodology for beginners

Hi All,

This document will help in getting basic understanding on ASAP Methodology.

We’ll discuss below points:

1- What is ASAP Methodology?

2- Phases of ASAP Methodology

3- Brief explanation of each phase

1-      What is ASAP Methodology?

  •   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.

1-      Phase of ASAP Methodology

ASAP focuses on tools and training, wrapped up in a five-phase process oriented road map for guiding implementation.

The road map is composed of five well-known consecutive phases

•        Phase 1 Project Preparation
•        Phase 2 Business Blueprint
•        Phase 3 Realization
•        Phase 4 Final Preparation
•        Phase 5 Go-Live and support

Brief explanation of each phase

ASAP Methodology  – Phase 1 : Project Preparation

Phase-1 initiates with a retrieval of information and resources. It is an important time to assemble the necessary components for the implementation. Some important milestones that need to be accomplished for phase 1 include


•        Obtaining senior-level management/stakeholder support
•        Identifying clear project objectives
•        Architect an efficient decision-making process
•        Creating an environment suitable for change and re-engineering
•        Building a qualified and capable project team.

ASAP Methodology – Phase 2- Business Blueprint

SAP has defined a business blueprint phase to help extract pertinent information about your company that is necessary for implementation. These blueprints are in the form of questionnaires that are designed to probe for information that uncovers how your company does business. As such, they also serve to document the implementation.

Each business blueprint document essentially outlines your future business processes and business requirements. The kinds of questions asked are germane to the particular business function, as seen in the following sample questions:

1)     1)  What information do you capture on a purchase order?

2)     2)  What information is required to complete a purchase order?

ASAP Methodology – Phase- 3 – Realization

With the completion of the business in phase 2, “functional” experts are now ready to begin configuring SAP.

The Realization phase is broken in to two parts.

1)   1)  Your SAP consulting team helps you configure your baseline system, called the baseline configuration.

1)   2) Your implementation project team fine-tunes that system to meet all your business and process requirements as part of the fine tuning configuration.

The initial configuration completed during the base line configuration is based on the information that you provided in your blueprint document. The remaining approximately 20% of your configuration that was not tackled during the baseline configuration is completed during the fine tuning configuration.

Fine tuning usually deals with the exceptions that are not covered in baseline configuration. This final bit of tweaking represents the work necessary to fit your special needs.

Configuration Testing-
With the help of your SAP consulting team, you segregate your business processes into cycles of related business flows. The cycles serve as independent units that enable you to test specific parts of the business process. You can also work through configuring the SAP implementation guide (IMG). A tool used to assist you in configuring your SAP system in a step by step manner.

Knowledge Transfer-
As the configuration phase comes to a close, it becomes necessary for the Project team to be self-sufficient in their knowledge of the configuration of your SAP system.

Knowledge transfer to the configuration team tasked with system maintenance (that is, maintenance of the business processes after Go-live) needs to be completed at this time. In addition, the end users tasked with actually using the system for day-to-day business purposes must be trained.

ASAP Methodology – Phase 4 – Final Preparation

As phase 3 merges into phase 4, you should find yourselves not only in the midst of SAP training, but also in the midst of rigorous functional and stress testing.

Phase 4 also concentrates on the fine tuning of your configuration before Go-live and more importantly, the migration of data from your old system or systems to SAP.

Workload testing (including peak volume, daily load, and other forms of stress testing), and integration or functional testing are conducted to ensure the accuracy of your data and the stability of your SAP system. Because you should have begun testing back in phase 2, you do not have too far to go until Go-live.

Now is an important time to perform preventative maintenance checks to ensure optimal performance at your SAP system. At the conclusion of phase 4, take time to plan and document a Go-live strategy. Preparation for Go-live means preparing for your end-users questions as they start actively working on the new SAP system.

ASAP Methodology – Phase 5 – Go-live and Support

The Go-live milestone is itself is easy to achieve; a smooth and uneventful Go-live is another matter altogether. Preparation is the key, including attention to what-if scenarios related not only to the individual business processes deployed but also to the functioning of technology underpinning these business processes and preparation for ongoing support, including maintenance contracts and documented processes and procedures are essential.

Thanks & Regards,

Anamika Jain

You must be Logged on to comment or reply to a post.
  • Doesn’t matter if it is old or new. I had no idea what ASAP meant and after googling it, this is the first document that came up. At least I have an idea now what it is all about.It is explained properly for beginners. Thanks Anamika Well done.

  • In Business Blueprint: as is and to be mapping is done on excel files – journal entries are penned down. The Solution architect will be mapping the various interfaces and the impacts.


    Arvind Leo Pereira


    ASAP Methodology (Accelerated SAP) is a standard SAP related project preparation and systems implementation method, developed and updated by consultants that are involved in implementing SAP software products. This methodology is also useful for project managers and others who implement systems that support business processes.

    The purpose of ASAP is to help project management design SAP implementation in the most efficient manner possible, by effectively optimizing time, people, quality, and other resources. Using the ASAP methodology, project management provides the roadmap for optimizing and continuous implementation of SAP systems in business processes. This solution was developed to guarantee a successful, cost-effective and on-time delivery of all project solutions. Developed by SAP (System Applications and Products) in order to optimize business suites, this framework streamlines the use of methods, tools, accelerators, and templates that were originally developed for SAP projects.

    What is the ASAP Methodology Framework?

    The Accelerated SAP methodology framework consists of five phases of implementation; each phase of the roadmap provides detailed plans to assist in documentation, recommendations, and implementation of SAP systems. Each phase of the process ends with a quality check that helps monitor the deliverables and other factors of critical success. Below is a brief description of each phase of the ASAP methodology roadmap

    Phase 1: Project Preparation

    This phase focuses on the initial planning and preparation to set ASAP goals. The phase typically follows these three steps:

    1. Clarify scope of implementation
    2. Establish the team — committees, teams (core, project and consulting)
    3. Define the sequence of project implementation

    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. The Business Blueprint is a detailed document containing all requirements derived during initial brainstorming and initiation meetings. This is also where the project team revises its objectives and goals while setting a schedule for each.

    Phase 3: Realization

    This phase builds on Phase 2; it’s focused on implementing all business process requirements. In this phase, project managers should attain signoff from stakeholders. Two work packages define the system configuration methodology:

    1. Baseline, concerned with the major scope.
    2. Final Configuration, concerned with the remaining scope.

    Phase 4: Final Preparation

    The final preparation involves testing, system management, cut over activities, end-user training, and all other tasks that are required to go live. Successful completion of Final Preparation ensures that the organization is ready to begin using the new 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 are related to production support setup, monitoring system transactions, and optimizing system performance.

    Advantages of ASAP Methodology

    The ASAP Methodology covers the entire project lifecycle from the initial evaluation through post-project management. The ASAP roadmap also ensures a transparent value delivery system that consistently reflects upon business care while acting as a guide for SOA (Service Oriented Architecture) and BPM (Business Process Management).

    • Proven, transparent approach that facilitates the project team to collaborate efficiently—reducing implementation costs, time, and risks
    • Sensible risk management
    • Better knowledge management: ASAP helps project management organize, implement, and meet business objectives
    • Steering committee tools
    • Better results because ASAP methodology is based on the experience of others—the roadmap requires both soft skills and hard facts
    • Project times may be reduced
    • Better communications planning
    • Combination of best practice tools including ITIL, PMI, Internal SAP, and others