Académique Documents
Professionnel Documents
Culture Documents
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.
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
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
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.
Core User Is The Employee Of The Company Who Has Good Experience & Exposure In
Client Business Process.
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.
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.
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.