SAP ASAP METHODOLOGY

ASAP

ASAP

(Accelerated SAP) is a step-by-step methodology for speeding up the implementation of an SAP R/3 system

ASAP
The

components of ASAP, which can be used together or individually, are called accelerators

ASAP
Accelerators are based on the best practices of SAP customers from around the world and consist of a number of templates, questions, and scenarios ASAP is shipped automatically with every R/3 delivery and upgrade. There is no charge for ASAP.

ASAP
ASAP

can reduce the time required to implement an R/3 system by as much as 50%. ASAP divides the SAP Project into a Road Map Consisting of 5 Phases

ASAP
ASAP METHODOLOGY IS CHARACTERISED BY: ROAD MAP DIVIDED INTO PHASES EACH PHASE HAS : WORK DELIVERABLES DOCUMENTATIONS IS CONTROLLED BY QUALITY ASSURANCE HAS STANDARDS HAS START AND END TIME SIGN - OFFS

ASAP ROAD MAP

Project

Preparation, Business Blueprint, Realization, Final Preparation and, Go live and support continuous change.

ASAP ROAD MAP

PROJECT PREPARATION

ROAD MAP-PROJECT PREPARATION

In this phase of the ASAP Roadmap, decisionmakers define clear project objectives and an efficient decision-making process A project charter is issued An implementation strategy is outlined, Project team as well as its working environment are established The Phase ends with a Kick off Meting

ROAD MAP-PROJECT PREPARATION

One of the first work packages in Phase 1 is the definition of the overall project team and the specification of project roles to be assumed during implementation . Project Team Includes: Project manager Application Consultant Business Process Team Lead Technical , System administration Lead Development Project Lead

Accelerator : Project Staffing User Guide

ROAD MAP-PROJECT PREPARATION

DOCUMENT Phase 1 includes a scoping document called the Enterprise Area Scope Document, Document can be generated using the Project Estimator. It contains high-level user-defined views of the scope of the project. This scoping document maps to the Question & Answer Database (Q&Adb), which is used in Phase 2 to determine the detailed process and development requirements

ROAD MAP-PROJECT PREPARATION

System Landscape and Technical Requirements The project team decides on the system landscape, as well as on the high-level strategies for creating R/3 clients, implementing new releases and transporting system settings. Infrastructure needs (Hardware / Interfaces)Quick Sizing Tools Archiving Strategy

ROAD MAP-PROJECT PREPARATION

ISSUE DATABASE The Issues Database allows the project team to enter, track, and report on project issues.
The data base supports: Priority Project phase Status People responsible Date required for solution Date resolved

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

ASAP ROAD MAP PHASES

BUSINESS BLUE PRINT

ASAP-BUSINESS BLUE PRINT

Document and define the scope of R/3 implementation and create the Business Blueprint. The Business Blueprint is a detailed documentation of company's requirements in WinWord format. Application consultants and the Business Process Teams achieve a common understanding of how the enterprise intends to run its business within the R/3 System, by carrying out requirementsgathering workshops. During Phase 2, the project team completes R/3 Level 2 training; this is recommended as early as possible and before the workshops start.

ASAP BUSINESS BLUE PRINT

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

ASAP-BUSINESS BLUE PRINT

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

ASAP-BUSINESS BLUE PRINT

OTHER WORK PACKAGES

PROJECT TEAM TRAINING

DEVELOPING THE SYSTEM ENVIRONMENT TECHNICALLY CONFIGURE THE DEVELOPMENT AND QUALITY ASSURANCE SYSTEMS SET UP OSS LINK BETWEEN THE CUSTOMER AND SAP DEFINING THE ORGANIZATION STRUCTURE DEFINING THE BUSINESS PROCESSES

ASAP-BUSINESS BLUE PRINT

ORGANIZATION STRUCTURE Questionnaires and a graphic display support the discussion on organizational units between SAP consultants and their customers In order to create structure scenarios, SAP has developed the R/3 Structure Modeler, included in Accelerated SAP. It offers comprehensive support due to its extended graphic functionality (creation, naming and allocating of new instances of the R/3 System, consistency checks, definition of views, scenariospecific documentation, help files).

ASAP-BUSINESS BLUE PRINT

Defining the Business Processes Activities

Conducting business process workshops Completing the Business Blueprint, reviewing it and obtaining management signoff Setting up an end user training schedule

ASAP-BUSINESS BLUE PRINT

BUSINESS PROCESS WORKSHOPS

FUNCTIOANLITY REQUIREMENTS Reporting requirements Interface requirements Conversion requirements Enhancement requirements Authorization requirements

ASAP-BUSINESS BLUE PRINT

QUESTION & ANSWER DATA BASE The Question & Answer Database (Q&Adb) contains technical and general business questions, the answers to which are the input for the creation of the Business Blueprint. The questions are designed to determine the enterprise's detailed business requirements in an integrated environment. In conjunction with the Business Process Master List, the Q&Adb is also used to determine the baseline scope, cycle plan and integration testing scenarios used in later phases.

ASAP ROAD MAP-PHASES

REALIZATION PHASE

ASAP-REALIZATION

In this phase, configuration system is carried out in two steps: Baseline and Final Configuration. The Baseline configuration is designed to configure about 80% of daily business transactions and all of master data, and organizational structure. The remaining configuration is done in processoriented cycles. The Business Blueprint is used as the guide for the system configuration,

ASAP-REALIZATION

The Business Process Master List (BPML) is initially created in Phase 2 as a report from the Q&Adb. It is used to identify, plan, schedule, and monitor the configuration and testing of all R/3 business scenarios and processes within the scope of an implementation. The Business Process Master List is comprised of Excel worksheets that collectively facilitate the configuration and testing of R/3. BPML is used to load the Project Scope in the Project -IMG

ASAP-REALIZATION
Further Aspects of the Realization Phase

Defining authorizations in the R/3 System Defining workflows Creating user documentation System Management Procedures

ASAP-ROAD MAP

FINAL PREPARATION PHASE

ASAP-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 readiness to go live. This Final Preparation phase also serves to resolve all crucial open issues. On successful completion of this phase, you are ready to run your business in your productive R/3 System

ASAP-FINAL PREPARATION
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. Cut Over Plan

ASAP-FINAL PREAPARTION

TESTING Testing conversion procedures and programs Testing interface programs Conducting volume and 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.

ASAP-GO LIVE

This phase is concerned with supporting and optimizing the operative R/3 system Production support facilities are defined, for example, checking system performance on a daily basis Validation of business processes and their configuration Follow-up training for users Signoffs, etc

ASAP-GO LIVE
During

phase 5, the first Early Watch session is held, where experts from SAP analyze the systems technical infrastructure. The aim is to ensure the system functions as smooth as possible