ASAP

ASAP: Accelerated Systems Application and Products in Data
Processing
ASAP methodology means nothing but standard process for
implementation of SAP, It consists of 5 phases.

1. Project preparations - consists of identifying team members and
developing strategy as how to go.

In this phase of the ASAP Roadmap, decision-makers define clear
project objectives and an efficient decision-making process. A project charter
is issued, an implementation strategy is outlined, and the project team as well
as its working environment are established.

The first step is for the project managers to set up the implementation
project(s). They draw up a rough draft of the project, appoint the project team
and hold a kickoff meeting. The kickoff meeting is critical, since at this time
the project team and process owners become aware of the project charter and
objectives and are allocated their responsibilities, lasting throughout the
project.


2. Business Blue print - consists of identifying the client current
process, requirement and how SAP provides solution.Consists of detailed documentation
In this phase you document and define the scope of your R/3 implementation and create the Business Blueprint. The Business Blueprint is a detailed documentation of your 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 requirements-gathering 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.

The project team selects the processes that best fit your business from R/3’s functional offering, using the following tools:

3. Realization -The purpose of this phase is to implement all the
business and process requirements based on the Business Blueprint.Unit Test and String Tests are performed followed by documentation of UTR/UTP's and Test Cases. Business Acceptance Test (BAT)

The purpose of Phase 3 is to configure the R/3 System, in order
to have an integrated and documented solution which fulfills your business process
requirements.

In this phase, configuration of your system is carried out
in two steps: Baseline and Final Configuration. The Baseline configuration is
designed to configure about 80% of your daily business transactions and all
of your master data, and organizational structure. The remaining configuration
is done in process-oriented cycles. The Business Blueprint is used as the guide
for the system configuration, done using the Implementation Guide, which will
be described in detail in this chapter. After this, data transfer programs,
as well as interfaces, need to be tested.

4 Final Preparation - The purpose of this phase is to complete
testing, end-user training.

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. 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.

In Phase 4, your end users go through comprehensive training.
The last step will be to migrate data to your new system. In particular a going-live
check is carried out and an R/3 Help Desk set up.

5 Go Live and Support
All the functional consultants need good rape with Abaper’s

Now you are ready to go live with your productive system! Afterwards,
the project team focuses on supporting the end users, for which training may
not be completed. It is also necessary to establish procedures and measurements
to review the benefits of your investment in R/3 on an ongoing basis. Key SAP
Services to support you in this phase include

The Online Service System (OSS)
Remote Consulting
EarlyWatch® Services
These services encompass a series of remote analyses of specific R/3 System
settings, with recommendations for improving system performance.
Development QA/ Testing Production



1. Project
preparation
2. Business Blue
print
3. Realization
4. Testing/QA
5. Go Live

Few Documents that are to be recorded in these phases are.

1. Functional Specifications.
2. Technical Specifications.
3. UTR/UTP
4. Test Cases
5. Delivery Documents