Accelerated SAP (ASAP) Methodology Prepared by Arun eased CR *Brief about the presentation* This documents are prepared in Vanilla SAP Standards -- Things differ from one implementation partner to another, Since Companies who implement they will incorporate their quality process with standard ASAP methodology. *Please place your commentsASAP-Accelerated SAP methodology Introduction Accelerated SAP (ASAP) is SAP's standard implementation methodology. It contains the Roadmap, a step-by-step guide that incorporates experience from many years of implementing R/3. Accelerated SAP contains a multitude of tools, accelerators and useful information to assist all team members in implementing R/3. Quality checks are incorporated at the end of each phase to easily monitor deliverables and critical success factors. ASAP is delivered as a PC-based package, so that - if required - an implementation project can begin prior to having an R/3 System installed.ASAP-Accelerated SAP methodology Introduction * The ASAP Roadmap provides the methodology for implementing and continuously optimizing your SAP System. It divides the implementation process into five phases and offers detailed Project Plans to assist you (in Microsoft Project format). * The documentation stored at each level of the Roadmap tree structure contains recommendations on implementing your SAP System and links to helpful tools and accelerators. Click here to know more (ENASAP-Accelerated SAP methodology Introduction * SAP delivers the Accelerated SAP (ASAP) methodology developed by SAP to optimize the success of implementing the SAP Business Suite. ~ + ASAP streamlines the implementation by providing templates, methods, tools, and accelerators that have been built on the success of thousands of previous SAP implementations. * The ASAP methodology adheres to a specific road map that addresses the following five general phases: Project Preperation Business _—Reallization” Blueprint Final a Preparation Go Live & ‘SupportAccelerated SAP(ASAP) Methodology Phase 1: Project Preparation During this phase the team goes through initial planning and preparation for SAP project Click here to know more [EE Note: The above steps are standard steps involved in this phase. Depending upon the Implementation partner quality procedure will be added to the above procedureethodology Phase 2: Business Blueprint The purpose of this phase is to achieve a common understanding of how the company intends to run SAP to support their business. Also, to refine the original project goals and objectives and revise the overall project schedule in this phase. The result is the Business Blueprint, a detailed documentation of the results gathered during requirements workshops. Click here to know more [EEPhase 2: Business Blueprint SCOPE DOCUMENT 1.This document will consists of questionnaire of entire business process J ASIS L.Understanding the business Process from the core team. 2.Based on the input ASIS document has to be created according to module wise q TOBE Lin this process u will map the business pro based on ASIS 2.Module wise TOBE document has to be created in SAP GAP ANALYSIS 1.The GAP b/w ASIS process & TOBE process is called GAP analysis ie., The inputs or the business process which can't mapped into standard SAP will be analyzed here 2.GAP document has to be created SIGN OFF Each process above has to be taken sign off from client Note: The above steps are standard steps involved in this phase. Depending upon the Implementation pariner quality procedure will be added to the above procedurePhase 3: Realization The purpose of this phase is to implement all the business process requirements based on the Business Blueprint. The system configuration methodology is provided in two work packages: 1.Baseline (major scope) & 2. Final configuration (remaining scope). In this phase also we have create documentation for the configuration implemented & it has to be taken sign off from client. Click here to know more be Note: The above steps are standard steps involved in this phase. Depending upon the Implementation pariner quality procedure will be added to the above procedurePhase 4: Final Preparation com ee * The purpose of this phase is to complete the final preparation, which includes to the following [End users of each module will be provided training by corresponding module consultant. End user traning document & user manuals has to be [Before Golive phase there will cut-over period for business process B carried. During Cut-over period the master data & transaction data from legacy system will be migrated to SAP system. There are various tools avilable for this purpose LSMW,SCAT,BDC Click here to know more Note: The above steps are standard steps involved in this phase. Depending upon the Implementation pariner quality procedure will be added to the above procedure= Phase 5: Go Live & Hyper care oO The purpose of this phase is to move froma _project-oriented, pre-production environment to live production operation. The most important elements include setting up production support, monitoring system transactions, and optimizing overall system performance. Hyper care After Go live the system is kept under motoring for support for a small period, “Hyper care” a, << Yn) x9 a t Wn 3 oO Ss o Click here to know more =Thank You Abolopouyew (dySV)dVS pa}esajas0y