Introducing ASAP 8 Methodology For HANA Implementation

Jim Sun

ASAP stands for "Accelerated SAP", the ASAP 8 Methodology provides a well documented method for a SAP client to perform an implementation project. The success of an SAP project can be predicted by effectiveness and speed of the implementation, since the longer the implementation takes, the higher cost a client will incur and the longer an investment will take to be returned. So it is quite important for the client to make sure that the implementation can be finished within the scheduled time with high quality. This is also why SAP introduced their Rapid-Deployment Solution (a.k.a. RDS). The ASAP 8 Methodology is the basis of the methododolgy you will need for implementing an RDS based solution.

Typically, during the ASAP 8 Methodology, these phases include:

  • Phase 1: Project Preparation---this phase defines the general information for the whole project, including project objectives, project scope, priorities, deliverables, project initiation, governance and so on. Also, deliverables including business process maps and business scenarios are the key outputs to be finished in this step. As far as HANA system's functionality goes, often the top priority is to increase the performance of the legacy system and decrease the response time. It is important to specify targeted reports/data cubes to be improved. If are any support tools or systems are required for the project, this is also the time to set them up.
  • Phase 2: Blueprint---The purpose of this phase is to achieve a clear understanding of how the whole organization intends to run the system to support the business. Functional and technical specifications, as well as any other details on how exactly the system will be blended into organization's operations should be defined at this stage.
  • Phase 3: Realization---Using the blueprint and functinonal/technical specifications developed in phase 2, the technical team begins configuring the system. IT follows the guidance from the documents that have been developed earlier to configure the system and also starts putting the educational content for the end-user training together.
  • Phase 4: Final Preparation---before wrapping up the development, project managers and directors need to evaluate the readiness of the solution and supporting tools to prepare for a go-live. During this stage the client works with the consultants team while going through a final HANA system test, end-user training, and evaluation of HANA system management and data migration requirements.
  • Phase 5: Go Live Support---after going live, there might be some bugs or technical issues in a newly set up HANA system. Although most bugs are easy fixes, the client may require additional production support, business process monitoring, and technical support in order to ensure the best performance possible.
  • Phase 6: Operation---upon completion of the step 5, HANA system is considered being initially set up and client can move on to setting up the automation processes.


A successful HANA implementation is not only about the powerful features brought by HANA itself, but also about successful project management. The ASAP 8 Methodology represents a strategic outline of the project management that SAP encourages its customers to use for any SAP product implementation. To learn more or to explore a case study of SAP HANA implementation performed by ATCG Solutions, please click the button below.

Have you ever read a blog and wanted to bookmark it but forgot? Or maybe you're like a lot of people and tend to keep dozens of windows open, only to experience a crash or otherwise lose track of what you were doing? Simple solution is to print this out, and that is why we provide a PDF version for later use, which you can get by pressing the button below.

Please check the latest information on sap s4hana here /s4hana-question-answers