SAP ASAP Methodology

Any client if they want to implement SAP, they will follow this methodology
ASAP: Accelerated SAP
ASAP methodology further classifies into 5 phases:
1. Project preparation
2. Business Blueprint
3. Realization
4. Final preparation
5. Go Live and Support

1. Project Preparation
As Consultant we don’t involve in project preparation phase only the
management from implementation and the management from client will involve
in project preparation phase.
Implementation partner CLIENT
Delivery Head Vice president IT
Project Manager Vice president Finance
Technical Expert Project Manager
Technical Lead

Activates in Preparation Phase:-

1. License
Any Client if they want to implement SAP then they have to purchase
license from SAP based on number of users they decide how many licenses
to be purchased from SAP

2. Landscape
 Land scape means the arrangement of servers
Any client if they want to implement SAP then they have to purchase
servers client’s landscape 4 servers
1) Sandbox (R&D)
2) Development server
3) Quality Server
4) Production Server
Only Consultants will have authorization to Development server
Quality server will be used by consultant and core users
Production Server will be used by users
3. Infrastructure
- How many new computers to be purchased to meet the number of
licenses
- Server environment (where to keep servers, temperature requirement,
security )
- VPN Connectivity
This network will help to connect the servers kept at different location

4. Consultant Facilities
Implementation partner will list out all the consultants who are going to
involve in this project and client will list out all the core users who are
involve in this project

Core users has to explain the client business process to the consultant and
consultant will configure it into SAP

Core users is the employee of the client who is having good experience and
exposure to the client’s business process
EX: Senior Manager

IF it is a domestic project all consultants will go to client’s place to

implement sap
 IF it is a foreign project each module one person will go to the client’s place
and remaining people work from offshore
2. Business blueprint:
After project preparation phase implementation partner management will
conduct kickoff meeting
In kickoff meeting they will invite all the consultants who are going to
involve in this project

In kickoff meeting:
 they give introduction about client
 rules and regulations of client
 Go live Date
 Starting Date
After Kickoff meeting all the consultant will go to client’s place (Frist functional
consultants will go after the technical team will go (ABAPERS, BASIS) to
implement SAP
When all consultants will go to our clients place to implement SAP then we start
business blueprint phase as a consultant our role starts from business blueprint
phase
On first day of clients visit we will have introduction with core users
Then core users will take consultant for manufacturing plant visit and explain the
end to end process , after plant visit we will start requirement Gathering

I. Requirement gathering
- Based on the questionnaire we gather the requirement from core users
- Questionnaire will be provided by implementation partner
- Questionnaire differs from module to module and questionnaire differs
from industry to industry
- Every day consultants will go to the core users place and ask the
questions then the core users will explain
- Whenever core user explain we have to record it and simultaneously we
have to note it down
 - Every day after completion of requirement gathering consultant will go
back and explain the same to associate consultant and trainee
consultant
- The we prepare the AS-IS Document
- AS-IS document consists of the present business process of the client
which core user explained
II. BBP document preparation and sign off
 BBP document consist of as is document and to be
 To Be Document consist of how the present business process of
client is going to be in sap
 After preparing BBP document we will send this to core users for sign off
then the core users has to go through the document and if everything is
fine then the core users will give BBP sign off
 After BP sign off, we will move to the next phase of ASAP methodology
that is Realization
 Time period for BBP document preparation & sign off is 1 month
 The total time period of business blueprint is 3 months
 When preparing to-be document if you find a gap then we have to prepare
the Gap analysis document
GAP: any client’s requirement for which there is no solution from SAP then
we treat it as GAP
GAP analysis consist of
- Clear description of gap
- Alternate solution
- Efforts
Functional man days
Technical man days
 3. Realization
Realization means configuring the client’s business process into SAP or
mapping TO-BE process into SAP
The time period of realization phases 2 months
In realization phase we will have access to sandbox and dev server
Development Server
100 200 300
Client Client
Client Configuration Concept Testing Technical consultant

Development server Quality Server Production Server

The T Code to display the request number SE09

The T code to import the request SCC1
The T code to transport the request STMS
We have two types of transport request
- Work Bench request
- Customizing request
In Realization Phase we will enter into development server to configure the
client’s business process into SAP
Configurations is two types
1. Base line configuration
2. Final Configuration
Base line Configuration is the configuration which is specific to one module
EX: pricing, partner determination, item category determination
Final Configuration is the configuration which you have to depend on other
consultants
EX: Revenue Account determination, credit management, availability check
-First we complete baseline configuration the we do final configuration
-after completion of all the configuration we will release all the requests in SE09
And send the request number to basis consultant then the basis consultant will
transport all the request from dev server to Qos server

In Quality server we do testing, we have two types of testing:

- Unit testing
- Integration testing
1. Unit testing: it is the testing which is specific to one module
2. Integration testing: it is the testing for which you have to depend on other
module consultants
Ex: Credit Management, Revenue account determination, availability check

 In realization phase testing will be done by consultants

 Before testing we have to prepare test case document
 Test case document consists of what to test, how to test, expected result,
actual result, testing document number and status
Test Case document
What to test
How to test
Expected result
Actual result
Testing document num
Status
 - Once testing activity is completed in quality server then we prepare user
manual document
- User manual document consist of step by step process of creating
master data and transaction data along with the screenshots
- After that we prepare configuration document
- Configuration document consists of screenshots of all the configuration
which we did for particular client
- After preparing user manual document and configuration document we
will give this to core users
- The purpose of configuration document is KT “ knowledge transfer “
- User manual document is the guidelines to end user
- In realization phase during configurations we prepare FS document
- FS document means Functional Specification document
- Any client requirement for which you require the help of the ABAPers
then we prepare FS document

In Realization phase we prepare 4 documents

 FS document
 Test case document
 User manual document
 Configuration document

4. Final Preparation (1month)

i. User training
We give training to core users on creating master data and transaction data
The time period of user training 10 days
We give training to core users and core user will give training to their end users
ii. UAT sign off (user acceptance test)
Here we will ask the core users to test all scenarios and confirm. Then core users
has to test all the scenarios in quality server and if everything is fine then core
users will give UAT sign off
 iii. After UAT sign off we will ask Basis Consultant to transport all the
requests from quality server to production server

iv. Cut over activity

Cut over activity means uploading of master data and open

transaction data from legacy to SAP “legacy means non SAP“

 AS SD Consultant will upload customer master and condition

master
 AS SD Consultant we upload open inquires, open quotations,
open contracts and open orders

The Tools to upload the data from legacy to SAP:

LSWM (Legacy System Migration Workbench)
BDC (Batch Data Communication)
BAPI (Business Application Programing Interface)

- Cutover strategy
It is a planning on when to upload the data from legacy to SAP and
during that period clients has to stop the business to avoid data
mismatch or data discrepancy

- Cutover period
It is the time taken to upload the data from legacy to SAP
Generally, we take 2 days to upload the data from legacy to SAP

5. GO-Live and Support

- after uploading the data from legacy to SAP we declare GO-Live
- Go-Live means Handing over SAP client that is from that date onwards
client will start using sap
- After Go-live next 3 months we will give post production support
- Before we Go-Live we prepare BPML (Business process master list)
Which users should have authorization to which T-codes