Vous êtes sur la page 1sur 5

CLASS-1

ASAP
ASAP Methodology
The ASAP (Accelerated SAP) methodology provides the roadmap for optimizing &
continuous implementation of SAP system in business process. This solution was developed to
generate a successful, Cost efficient & on time delivery of all project solution it provides the
whole team with a project management roadmap & real-time technology to deliver well
acknowledged project strategies in global standards.

ASAP Methodology Roadmap


The ASAP methodology roadmap constitutes a stepwise guide incorporating project
experience right from the start of R/3. It brings in a multiple number of tools, information &
acceleration to assist team member with the implementation of R/3. Each phase of the process
ends with a quality check that helps monitor the deliverable & other factor of critical Success.

Advantages Of ASAP Methodology


1. Proven & Transparent approach that facilitates the project team to collaborate efficiently
thus reducing implementation costs, time, risks.
2. Sensible Risk Management
3. Better knowledge mgt. wherein SAP solutions help to organize, implements, & meet
business objector.
4. Project time one almost brought down to half.
Implementation
5 Phase Of Implementation
1. Project Preparation
2. Business Blueprint
3. Realization
4. Final Preparation
5. Go Live & Support
Project Preparation – It’s primary focus is getting the project Started, identifying team
members & developing a high level plan (GAP Analysis, 13% activities).
Business Blueprint – To understand the business goals of the company, to determine the
business requirements needed to support these goals.
Realization – To implement all the business & process requirements based on the business
blueprint. You customize the system step by step into work packages, Baseline & Final
Configuration.
Final Preparation – It’s purpose is to compute testing, End User testing, system
management & cutover activities. Critical open issues are resolved. Upon the successful
implementation of the phase, you will be ready to run your business in your productive R/3
System.
Go Live & Support –T from a project oriented, pre productive environment to be successful
& live productive operation.

1. Project Preparation (12% activities) : We are going to collect business requirement of


the client e.g.: Business Process, Business area, Department, Customer, Future business
places, Previous product, Standard SAP & Actual requirement of client is GAP. When
something is needed for business require is GAP – understands in this Phase.
AS IS – Study of the existing business process of the client. SAP consultant is suppose to
go client place, study thoroughly their way of working & is needed to prepare a
document of their existing business process in details.

1
Once this is done, the consultant has to provide the client with the solution to improve
their way by inducing new process/ new functionality or by improving the existing
process which will help to reduce their cost of operation in future & improve their
operation. This is called “TO BE” Process % takes care the client’s future business
requirement. It is a part of Blue print phase.

1. Business Blueprint (13%): Segregating all the information & Mentioning step by step.
Preparing the designed & Diagrammatic document in BPDD (Business Process Designed
Document), Based on BPDD, Blueprint is prepared for individual modules.

BP FICO

BPDD BP SD

BP MM

Specific information of an individual module full detail with resolution in document in


second Phase (GAP), here we decide team size, allocated task, assignment of
consultants.

2. Realization (45%): Divided into 3 Parts :-


i. Base Configuration – B/ Area, F/Area, COA,
FYV. ii. Main Configuration – Sub Modules, AR,
AP, AF.
iii. Integration Configuration – Combination between 2
or more modules.
 Unit Testing: Development Server but client different, all configuration &
Customization in development server.

3. Final preparation (14%): Once client get start testing & Get any bugs by the end user,
they forward to the consultants by the emails, End user testing, Regression testing,
System testing, Integration testing, Cut over activities are done. Testing from the client
hide.
 Cutover Activates : Uploading all the master transaction data from Non
SAP to
Quality Server

Session method

BDC

Call Transaction

1st configuration & Customization data moved to production server, then


cut over activities.
 Sign off Meeting: Senior member from vendor and client side decides
date & time even entire data by transport request quantity to
production. System ready to use.

2
2. Go Line & Support (16%): Senior level of end user will test system is ready or not. But
there should be strong support from consultants. BAU – Business As Usual should be
started, then all support activity should be started to fix the error.

Incidents.
Tickets
Service.

SLA – Service Level Agreement


Example:
P1 P2 P3 P4
Response 30 min 1 hr - -
Resolution 2 hr 4hr 16 hr 24 hr

Core User Is The Employee Of The Company Who Has Good Experience & Exposure In
Client Business Process.

Development Server: - Development Server Will Be Used To Configure The Client


Business Process Into Sap. Development Server Will Be Used By Consultants Only.

Quality Server: - Quality Server Will Be Used To Test The Scenarios. Quality Server Will Be
Used By Consultants And Core Users.

Production Server: - Production Server Is The Live Server, Where End User Will Do Day To
Day Transactions In Sap. Production Server Will Be Used By End Users And Core Users.
Consultants Will Not Have Access To Production Server. Users Will Not Have Access To
Development Server.

1. Base Line Configuration: - It Is The Configuration For Which, We Don‟T Depend


On Other Module Consultant (It Is A Configuration Which Is Specific To One Module).

2. Final Configuration(Integration Between Modules): - It Is The Configuration For


Which We Need To Depend On Other Module Consultants(MM,PP,FI). This Configuration We
Can‟T Do On Our Own. Ex- Credit Management, Third Party.

In Sap Whenever We Are Saving The Configuration, We Need To Save It In A Particular


Transport Request Number. Request Number Will Help To Transport The Configuration From
One Server To Another Server.

3
Testing

Acceptance Testing is a level of the software testing where a system is tested for
acceptability with respect to user needs, requirements, and business processes conducted to
determine whether or not a system satisfies the acceptance criteria and to enable the user,
customers or other authorized entity to determine whether or not to accept the system.

• Internal Acceptance Testing (Also known as Alpha Testing) is performed by members of


the organization that developed the software but who are not directly involved in the
project
(Development or Testing). Usually, it is the members of Product Management, Sales
and/or Customer Support.
• External Acceptance Testing is performed by people who are not employees of the
organization that developed the software.

Customer Acceptance Testing is performed by the customers of the


organization that developed the software. They are the ones who asked the
organization to develop the software. [This is in the case of the software not
being owned by the organization that developed it.]

User Acceptance Testing (Also known as Beta Testing) is performed by the end
users of the software. They can be the customers themselves or the customers’
customers.

System Testing is a level of the software testing where a complete and integrated
software is tested.

The purpose of this test is to evaluate the system’s compliance with the specified
requirements.

Regression testing is the process of testing changes to computer programs to make sure
that the older programming still works with the new changes. Regression testing is a normal
part of the program development process and, in larger companies, is done by code testing
specialists.

GAP Analysis
Through GAP analysis will identify the gaps between how the business operates as its
needs against what the package can’t do. For each GAP there will be one of three outcomes
which must be recorded & actioned. GAP must be closed & customized software can be
developed to close the GAP. GAP means small Cracks. In SAP, In IT GAP analysis is the study of
the difference between two different information system or application (legacy system with

4
client are new in SAP) often for the purpose of determining how to get from one state to new
state. It’s the phase where we are & where we want to be. It’s undertaken for bridging the
space. It’s true consuming and plays a vital role in blueprint stage.
GAPs can differ from company to company. Most commonly missing Functionality is industry
specific.

EG:- In Customer Master data the client requirement needs Legacy customer no. which can be
solved out with user exit. In sales order we need customer phone no, we can use user exit. If
client wants new Fields in customer master like nearest Fire station. GAP analysis is done in
blueprint stage. It’s aim to understand what can be done in std. SAP & how the client actually
wants a particular scenario to be processed. An understanding of GAP between the Actual &
Required scenarios. The difference between agreed work & completed work is GAP analysis. To
Fill this GAP we can use the enhancements. These enhancements divide into Exits like User
Exits, Field Exits, Screen Exits & Menu Exits. These enhancements are used to update the Std.
program in it’s respective business. Transaction used as a gateway to meet client requirements.

Vous aimerez peut-être aussi