[From our online lectures at the University of Duisburg-Essen] Accelerated SAP (ASAP) is a collection of methods and tools for the efficient introduction, upgrade, and release change of SAP software. The ASAP component was used by SAP for the first time in 1996 and is based on the experience gained from previous projects. ASAP is delivered independently of SAP R/3 and thus allows you to start the implementation project before the SAP system is installed.
What is Accelerated SAP ?
Accelerated SAP – ASAP is a process model that is designed to provide a quick introduction to the SAP ERP implementation project. The standardized procedure is designed to keep time, resources and financial resources as low as possible. In addition, a defined procedure helps to meet the individual requirements of the individual SAP implementing companies. The basis of ASAP are graphically prepared checklists to determine individual requirements. The component also offers a number of different tools, templates, etc., which should significantly facilitate project work from project planning to the productive start of the SAP system. With Accelerated SAP, companies develop their own version for business processes and organizational structures and determine their target concept (Business Blueprint) from the “Best Business Practices” provided. The two most important tools are the “Implementation Assistant” with the ASAP Roadmap and the “Question and Answer Database”, with which the project scope is defined and the Business Blueprint can be generated with the SAP reference structure as a basis.
An ASAP project consists of five phases:
Phases of SAP-ASAP
Project preparation: A clear project objective and an efficient approach are defined by the decision makers. The project order is created, the implementation strategy is defined and the project team and working environment are formed.
This includes the following tasks:
- 1. determine required systems
- Define 2nd client strategy
- 3. define release strategy
- 4. define transport system
A graphical representation of the above aspects of the system landscape using the Structure Modeler helps to ensure that no essential system requirements are forgotten and that all changes in Customizing and development are documented and distributed to the relevant systems.
Target concept: The documentation and definition of the SAP ERP implementation, the so-called Business Blueprint, is created. The Business Blueprint serves to understand the process flow in SAP ERP. This means that the project team develops a concept for what the action product should look like or how the service will be implemented and what the solution path will look like.
The activity contains the four tasks.
- Plan Enterprise Structure Workshop
Distribute recommendations on corporate structure
Carry out Enterprise Structure Workshop
Recommend and coordinate corporate structure
Realization: The aim of this phase is to customize the SAP ERP system in order to find a solution that meets the business requirements. The purpose of this activity is to set the organizational units in your R/3 System using the Implementation Guide (IMG). You made these settings in Phase 2: Business Blueprint. The settings for the organizational units are of central importance for configuring the processes and functions of your system. Use the documented R/3 organizational structure in your company as an input for the configuration.
Production preparation: Testing and user training prepare the ERP system for the productive phase.
Production : In this phase, follow-up projects are already underway to implement new application components or automate and improve business processes.