ASAP Roadmap Methodology

ASAP Roadmap Methodology

The Accelerated SAP (ASAP) Roadmap, which originated in 1996, is still the backbone of more advanced and similar project methodologies – it can be downloaded as a PDF Here

Or referenced as an overview below:

Phase 1: Project Preparation
Phase 2: Business Blueprint
Phase 3: Realization
Phase 4: Final Preparation
Phase 5: Go Live & Support

Phase 1: Project Preparation

In this phase of the ASAP Roadmap, decision-makers define clear project objectives and an efficient decision-making process. Here Project Organization and roles are defined and implementation scope is finalized.
System landscape and Technical Requirement

  • Infrastructure need (Hardware/interfaces)
  • System Landscape
  • High level strategies for client
  • Archiving strategy

Issues Database:
Issues must be resolved before phase completion ot before beginning of the next phase. The issues can be

  • Unanticipated tasks
  • Normal tasks that can not be completed
  • External factors that need to be dealt with.

Issues database allows the project team to enter, track and report on project issues.

Phase 2: Business Blueprint

In this phase scope of the R/3 implementation is defined & Business Blueprint is created. Business Blueprint is a detailed documentation of company’s requirements.

Various tools are used in this phase.

  • AcceleratedSAP Implementation Assistant
  • Question & Answer Database (Q&Adb)
  • Business Process Master List (BPML)
  • R/3 Structure Modeler
  • Business Navigator and external modeling tools

Project Management:
Activities in this work package are:

  • Conducting Status meeting for project team
  • Conducting steering committee meetings
  • General project management
  • Addressing organizational issues relating to organizational change management.

Other activities include:

  • Project Team Training
  • Developing the System Environment
  • Defining Organizational Structure
  • Defining the Business processes

R/3 reference model can be used for

  • Comparing the standard functionality with your companies own organizational requirements
  • Creating documentation for the conceptual design
  • Optimizing business processes
  • Training the project team and users
  • Writing user documentation

Question and Answer Database can be used to determine

  • The Baseline Scope
  • Cycle Plan
  • Integration test Plan

Phase 3: Realization

The purpose of Phase 3 is to configure the R/3 system. The configuration is carries out in two steps; baseline configuration & Final configuration.
Business Process Master List (BPML) is created in phase 2 as a report from Q&A database. It is used to identify, plan, schedule and monitor the configuration and testing of all R/3 scenarios and processes within the scope of an implementation. BPML is a representation of the R/3 business and transactions that are contained within the scope of the project. BPML is feeds all business information to all subsequent worksheets.
Implementation Guide (IMG): It is the main tool for setting the parameters to configure or ‘Customize’ R/3 during the realization phase. IMG reflect the chronological order in which the customizing activities are carried out.
The following aspects of configuration are also to be considered:

  • Defining authorizations in the R/3 system
  • Defining workflows
  • Creating user documentation

System Manager Procedures

  • Developing system test plans
  • Defining service level commitment
  • Establishing system administration functions
  • Setting up Quality Assurance environment
  • Defining the design of the productive system
  • Defining system management procedures for the productive system
  • Setting up the productive environment

At the end of this phase, Project Manager must check the status of deliverables for completeness and accuracy. This internal quality check should be carried out in addition to an external, independent third party Quality Audit.
Preparation for end-user training needs to be gone through and approved at and of this phase.

Phase 4: Final Preparation

The purpose of this phase is to complete the final preparation of the R/3 system for going live. This includes testing, user training, system management and cutover activities, to finalize your readiness to go live.
In this phase the R/3 system is handed over to individual departments for productive operation. This includes preparation of end-user documentation and training the end-users. The technical environment is installed on production system & is tested. Project managers prepare plans for going live, transfer of legacy data and support at early stages.
End-user training is a critical activity for success of the project. InfoDB may be used to plan for the User Training activities. Computer Center Management System (CCMS) must be set at this time. Simulation of productive operation system & testing the same is of great important.
The test plan contains the following activities

  • Testing conversion procedures and programs.
  • Testing interface programs
  • Conducting volume & stress testing
  • Conducting final user acceptance testing
  • Developing a final go-live strategy.

The Computer Aided Test Tool (CATT) can be used to automate test sequences for key business processes.
Phase 4 also provides for the testing of the disaster recovery plan for the productive environment. Disaster downtimes are verified and details on de-escalation.

Phase 5: Go Live & Support

This phase is concerned with supporting and optimizing the operative R/3 system.
Following activities are carried out

  • Production support facilities are defined.
  • Validation of business processes and their configuration.
  • Follow-up training for users
  • Signoffs etc.

During phase 5, the first EarlyWatch session should be held, where experts from SAP analyze the system’s technical infrastructure. The aim is to ensure the system functions as smooth as possible.
Version upgrades should be planned whenever found necessary. AcceleratedSAP contains a continuous roadmap, with standard activities necessary after implementation. The tasks in that structure provide solutions for all known types of continuous change: Business changes, technology changes or changes in user community.

4 Comments

  1. Santhira June 1, 2011 at 10:58 pm · Reply

    Where can I get ASAP Methodology for XI/PI implementation. Unable to retrieve file from SAP Service marketplace(apparently expired)
    thanks

    • admin June 4, 2011 at 1:42 am · Reply

      Hi Santhira,

      ASAP is a methodology which can be used for most projects. If you have a SAP Solution Manager system you can access a SAP roadmap and methodology using transaction RMMAIN.

  2. shibankur August 2, 2011 at 2:22 pm · Reply

    Sir,
    how I will access to the sap functional(sap-erp,sd)documents(need user id & password)?

    • admin August 3, 2011 at 10:41 am · Reply

      Hi Shibankur,

      You can use the links on the right side of this page:

      “SAP Links”

      SAP BPX Community
      SAP Business Objects Community
      SAP Community Network Home Page
      SAP Developer Network Forums
      SAP ECC6 Help
      SAP Help
      SAP Notes
      SAP Official Training Courses
      SAP User Groups

      Some of them are closed groups where you need a user name and password and others are open groups, where anyone can register.

Leave a Reply