The author is an online writer, blogger, and enthusiastic learner sharing her experience and knowledge in various areas.
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 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 the 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 as the customization needed for production support.
SAP Implementation Phases
Here are the six phases of a SAP implementation project:
- Project Preparation
- Business Blueprint
- Final Preparation
- Go Live
- Post-Production Support
More Reading About SAP
- SAP Order-to-Cash Cycle—FI-SD Integration and Configuration
Everything you need to know about the SAP Order-to-Cash cycle (SAP OTC). This includes FI-SD integration and configuration.
- What is SAP? Everything You Need to Know About SAP software
What is SAP? How does SAP software work? Why is SAP is one of the top ERP systems? Different SAP modules.
Phases of ASAP Methodology
The ASAP methodology prescribes a correct pathway for SAP implementation projects. It consists of six steps, the six 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.
- 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.
- 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 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 have been done by the testing team. Unit testing, integration testing, and day-in-the-life 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 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.
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.
This article is accurate and true to the best of the author’s knowledge. Content is for informational or entertainment purposes only and does not substitute for personal counsel or professional advice in business, financial, legal, or technical matters.
Christina Tilly on January 22, 2020:
Thanks for sharing the valuable information. You explained the important points.
Alba (Austria) on August 06, 2019:
Thank you for an insightful article. May I consult your expertise on a relevant SAP topic?
How is the total investment in a SAP S/4 transformation project (greenfield/bluefield) distributed across the project life cycle usually?(percentage of the total project costs)
1 PREPARE ( ? %)
2 DEFINE ( ? %)
3 DESIGN & BUILD ( ? %)
4 INTEGRATION TEST ( ? %)
5 ACCEPTANCE TEST ( ? %)
6 DEPLOY ( ? %)
7 HYPER CARE / HAND OVER ( ? %)
Total = 100 %
I hope you / the community can help!
pathuri satish MBA on February 02, 2019:
Thank you for sharing about asap methodology. i am learned sap fi/co thank you for giving brief information abut asap.its so clear.
Kadri Mohammed Azharuddin on January 18, 2019:
Thank you for sharing about ASAP methodology - although i only knew about traditional waterfall method and AGile methodology - Nice article
Kadri Mohammed Azharuddin
Globalteckz - Official Odoo partners
For more info visit our website https://www.globalteckz.com/solutions/business-sol...
sphinax info on December 12, 2018:
Thanks for sharing the valuable information. We are also expert in SAP implementation and support services. For more details visit our website.
anilbabu konda on October 09, 2018:
thanks a lot
Mahesh reddy on August 08, 2018:
Thank you for giving a brief idea about ASAP methodologies.
Narayan on July 09, 2018:
Thank you provided information.............
Vinay on February 06, 2018:
Thanks for this.........
SIVA REDDY on November 10, 2017:
Nice to see this document...
Harish verma on April 03, 2017:
Very well explained, thank you for the post