Overview ASAP Methodology

Phase 1- Project Preparation Phase 2- Business Blueprint Phase 3- Realization Phase 4- Final Preparation Phase 5- GO-Live and Support

ASAP Methodology Phase 1- Project Preparation

Objects and Scope of Project
Which business process to map into SAP
Eg: Make to Stock ( MTS ) Purchase to Pay ( PTP ) Order to Cash ( OTC ) Which modules are used

ASAP Methodology Phase 1- Project Preparation

Objects and Scope of Project (Cont. )
What functionality of each module is to be used

ASAP Methodology Phase 1- Project Preparation

Big-Bang implementation or Phased Implementation Project Steering Committee
decide on project organization struc -ture and identify the members who would be on the steering committee

ASAP Methodology Phase 1- Project Preparation

Assign resources that would be required to work on the project Plan for proper working environment for project team Plan for hardware and location of shared resources within project room You need to size your system at least for the development servers Need to develop a plan to train users on the SAP R/3 functionality

ASAP Methodology Phase 1- Project Preparation

Identify the business and project measurements To establish standards in the project
eg : for proper documentation, reporting frequency, hierarchy and communication between team members are absolutely critical to be set-up so that the entire project team follows a definite pattern right from the start

ASAP Methodology Phase 1- Project Preparation

To-set up a strategy to manage project issues and define escalation rules so that decision making process are expedited Identify who in the project team needs to be given access to the OSS

ASAP Methodology Phase 1- Project Preparation

Developing a R/3 landscape Organize Project kick-off meeting where in you declare : structures, roles and responsibilities, goals and scope of the project business and project measurements and project standards

ASAP Methodology Phase 1- Project Preparation

Sign-off on certain acceptance forms

ASAP Methodology Phase 2- Business Blueprint

A business blueprint is a document

that specifies all process requirements of client within the identified scope of the ASAP Project In this phase , client requirements are identified, complete business reengineering and record what SAP R/3 system to deliver

ASAP Methodology Phase 2- Business Blueprint

Identify clients Baseline scope Baseline scope is defined as about 80% of the project deliverables and 100% of clients organization structure and master data.

ASAP guidelines recommend that TeamSAP members configure for the deliverables for the baseline scope

ASAP Methodology Phase 2- Business Blueprint

Description You would need to conduct workshops with the concerned people in order to identify client business requirements and suggestions to improve the efficiency of the process

ASAP Methodology Phase 2- Business Blueprint

Description (Continued ) ASAP offers Q&A Database which is generated from the EASD Q&A Database contains questions about organization structure and business process requirements

ASAP Methodology Phase 2- Business Blueprint

Description (Continued ) The Q&A Database also contains an Issue data base where open issues or business decisions relating to the project can be logged and a resolution sought from the project management

ASAP Methodology Phase 2- Business Blueprint

Description (Continued ) The Q&A Database also has the provision to generate reports on all information that you log into the database When you answers questions, you can also identify the baseline scope

ASAP Methodology Phase 2- Business Blueprint

Description (Continued ) Based on the transactions that you have identified in the scope, you can specify which transactions are applicable to which testing cycle. This triggers business process master list

ASAP Methodology Phase 2- Business Blueprint

Description (Continued ) If you can wait a little longer till the consultants enter their analysis of the requirements, you can generate the business blue print itself. This document contains an exhaustive list of all the identified requirements and the suggested configuration

ASAP Methodology Phase 2- Business Blueprint

Description (Continued ) This phase also requires the implementation of system land scape and development environment System administrator activities starts here itself, so development system is ready with necessary user logins

ASAP Methodology Phase 2- Business Blueprint

Description (Continued ) Transport request management and release strategy shall be established Remote connection to SAP should be setup and printer services installed.

ASAP Methodology Phase 2- Business Blueprint

Description (Continued ) As far as the SAP severs are concerned, it has to be decided on a two or three-tier architecture and setup database and application servers accordingly. Furthermore, SAP clients are to be setup and establish the purpose of each of them

ASAP Methodology Phase 2- Business Blueprint

Description (Continued ) Finally, to develop and finalize the training strategy of client employees

ASAP Methodology Phase 3- Realization

Purpose of this phase

to implement all documented requirements in the Blueprint perform integration testing get system setup ready for productive operation

ASAP Methodology Phase 3- Realization

This phase is subdivided into:

The Baseline configuration Phase The Final Configuration Phase The Unit Testing Phase The Integration Testing Phase

ASAP Methodology Phase 3- Realization

The Baseline configuration Phase
The system is configured according to the transactions identified in the Business Process Master List. Simultaneously develop necessary programs, interfaces and the employees for their SAP training The baseline configuration is such that all mission critical processes are implemented and offers a solid foundation for the forthcoming final configuration phase

ASAP Methodology Phase 3- Realization

The Baseline configuration Phase
This phase also requires to create process test plans It is also required to conduct workshops on the system configuration to demonstrate the functionality to the client people, both within the project team and outside the team.

ASAP Methodology Phase 3- Realization

The Final configuration Phase
It allows SAP trained employees to complete what is left out of the scope of the project This phase also includes unit tests of developed processes Any problem found from such tests should be fixed in the system configuration before moving onto the next stage of the realization phase

ASAP Methodology Phase 3- Realization

The Final configuration Phase
In the base line and Final configuration phases , the project team develops customized reports, transactions, develop and test interfaces to external programs. This is the time for BASIS team to develop quality assurance systems where all integration tests would be performed

ASAP Methodology Phase 3- Realization

The Integration Test Phase
It requires to perform tests on cross-modular process. Any errors found in the process should be documented and fixed in this phase This phase can also be used to perform volume and stress tests or even tests on external interfaces on your configured system

ASAP Methodology Phase 3- Realization

The Basis team is to work on authorization that end users need to have in the productive environment . For this purpose functional consultants shall cooperate with BASIS Team. Preparation of End user documentation Preparation for End User training

ASAP Methodology Phase 4- Final Preparation

This phase is to finalize entire system configuration and environment, including tests, user training and setup of productive environment Cut-over plan This phase also requires you schedule a Going Live Check

ASAP Methodology Phase 4- Final Preparation

You can consider settings up a Help Desk facility to help your new users in the system Finally, you start converting data from your legacy system into the productive R/3 system

ASAP Methodology Phase 5 GO-Live and Support

The purpose of this phase is to go productive with your production system, dismantle your existing system. You should perform system audit and identify transactions that are making a heavy impact on system performance. It might be required to take some measures to improve and optimize performance