Scribd
Upload
2 views

ASAP

The ASAP methodology consists of five phases: Project Preparation, Business Blueprint, Realization, Final Preparation, and Go Live and Support, each focusing on specific tasks to ensure successful SAP implementation. Key activities include defining project goals, understanding business requirements, configuring the system, conducting testing and training, and transitioning to a live production environment. The methodology also emphasizes quality checks, milestone deliverables, and the integration of various SAP products into a cohesive implementation roadmap.

Uploaded by

HARISH VERMA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
2 views

ASAP

The ASAP methodology consists of five phases: Project Preparation, Business Blueprint, Realization, Final Preparation, and Go Live and Support, each focusing on specific tasks to ensure successful SAP implementation. Key activities include defining project goals, understanding business requirements, configuring the system, conducting testing and training, and transitioning to a live production environment. The methodology also emphasizes quality checks, milestone deliverables, and the integration of various SAP products into a cohesive implementation roadmap.

Uploaded by

HARISH VERMA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 5

ASAP METHODOLOGY NOTES

ACCELERATED SAP:

Phase 1: Project Preparation - The primary focus of Phase 1 is getting the


project started, identifying team members and developing a high-level plan.

Phase 2: Business Blueprint - The primary focus of Phase 2 is to understand


the business goals of the enterprise and to determine the business requirements
needed to support these goals.

Phase 3: Realization - The purpose of this phase is to implement all the


business and process requirements identified in the Business Blueprint. You
configure the system step-by-step in the work packages Baseline and Final
Configuration.

Phase 4: Final Preparation - The purpose of this phase is to complete testing,


end-user training, system management and cutover activities. Critical open
issues are resolved. When you have successfully completed this phase, you will
be ready to run your business in your production system.

Phase 5: Go Live and Support - Transition from a project-oriented, pre-


production environment to a successful and live production environment.

The new ASAP Roadmap (available as of Release 4.6A), helps integrate all
existing ASAP Roadmaps into one "configurable" one. It is based on the products
R/3, BW (Business Information Warehouse), APO (Advanced Planner &
Optimizer), CRM (Customer Relationship Management encompassing Mobile
Sales/Mobile Services), and B2B (Business to Business Procurement) and
provides a single implementation solution within ASAP for all SAP software.

The road map defines control points/milestones and also specifies the major
deliverables with in each milestone.
In road map we identifies few activities with in each phone and assign dates to
there milestones.

At the end of each phase we come up with deliverables / work packages


At the end of each phase we perform quality check
Phase 1 : Project preparation

We define project goals and identified the scope of project

Scope of the Project : Identifying the business process that we want to map
into SAP ,which modules we are going to use and which functionality we are
going to use for each modules then we decide whether we are going to go live by
big bank implementation or phased implementation . Which can be described in
EASD (ENTERPRISE AREA SCOPE DOCUMENT)

We develop the structure of the project organization and identify the member to
be including in the steering committee for the project.

Assigning the resources to work on the project

Identify the proper hardware to be able to support development work on sap r/3

Preparing the development server Planning for giving training for project people

Identifying the business and project measurements establishing standards. (For


proper documentation reporting frequency and hierarchy communication
between team members ) .

Identifying the persons to give authorization to access OSS note, early watch and
going live check.

Having assistance from independent party to conduct, audit/quality checks.


Developing landscape that in defining client-instance strategy
Defining our system upgrade strategy.
Defining procedures to use and manage transport requests.
Organizing kick off meeting is which we declare the structure roles and
responsibilities.

Perform quality checks and sign off.

“concept check tools” can be used in then project.

PHASE: 2-BLUE PRINT: In a document that specifies all requirements of our


client with in identified scope of the ASAP project.

Conceptual design phase of the project in which project team defines current
business process on the ‘AS – IS’ business process, project team develops “
SHOULD-BE “ process by using business re-engineering technique
Mainly in this phase where we identify the requirements, perform re-engineering
and record what our SAP system to deliver.

In this phase we identify the “ BASELINE SCOPE “

In order to determine business requirements we integrate with endures. We use


SAP TOOL that in “ Q&A “ THAT IS GENERATED from the EASD. Q& A
database contains questions about our organizational structure. Q& A database
includes “ issue database “ where issues project can be logged and get the re-
solutions. From project management. Q&A database we can generate reports

When the Q& A database we also identify the base wise scope (80% of
requirements)

The entire realization phase can be divided based line scope period , one to four
unit that cycle and two integration that cycles .

We could use two of the four unit test cycles to complete our 20% configuration.

Based on the transaction that we identify in scope, we can specify which are
applicable to which cycle. This input is trigger pointer generation of the “ business
process master list “ (MS-EXCEL)

Based on the questions that we entered, team sap member enter answers in the
form of analysis of requirements, that we can generate business blue print itself.
Implementing the initial stages of the system landscape and develop
environment.

System administration work starts here so that development environment is


ready with
Login.

Finalize the technical design of hardware architecture

Establishing transport request management and release strategy

Remote connection to sap , installing SAP GUI.

Deciding the two/three-tire architecture and setting up database and application


layers accordingly.

Establishing sap clients and their purposes

Develop and finalize the training strategy


PHASE 3 REALIZATION: The purpose of this phase in to implement all
documented requirements in the business blueprint.

Performing integration testing

Getting ready of sap system to productive operation.


This phase is sub divided in to

Baseline phase: (configuration): by considering business process transactions


identified in the business process master lines, team sap member perform
configuration. While they doing the system configuration, developing programmer
and interface, we can send project member to get the training. In their
configuration, minor critical process is implemented in r/3.
Demonstrate the functionality of system to team.

Configuration: in this step team sap will go back a little bit and allow the project
team to complete 20% project

The work that is done at base line configuration can be refined in this phase

Unit / cycle tests are developed processes.

Problems are fixed solving of they we found any errors, before moving to
realization phase.

The business master list contains the lists of transactions that need to be tested
and that nerve as a guideline for our unit tests.

Their two phases can be used to develop designed reports and transactions, test
interface test and develop all forms and data conversation programmer.

Developing quality assurance system where all integration tests would be


performed.

Integration test: performing tests on cross – modular process or those process


that involve more than one module of sap to complete.

Integration test phase of contains on transaction, which involve a data flow from
one module to another module.

Integration test phase 2 is to execute back process as of the entire process was
entirely with in one module.

If any error finds that should be fixed. and documented .


Technical team defines authorization for end-users.
Functional team creates user –specific menus.

Technical team procure / plan for productive environments, and archiving


strategy also should be defined.
Identifying the end users and impart training

Phase 4 Final preparations: this phase is to finalize our entries system


configuration and environment, including tests, user training, and productive
system setup.

Developing cutover plan.

Scheduling the going hire check it is a service provided by sap in which sap
employed experts logon into sap and check for factors that could be effect
system performance .by doing test on the scope of the project, and they give
advices is a report to improve / fine there system configuration.

Setting up the help desk facility (single level / two level)

Finally short the conversion of data from legacy system to productive system.
This requires downloading the data from legacy to proper format and then
uploading the data into r/3. Data can be uploaded by manually or data
conversion programmer.

Phase 5 go live and support: the purpose of this phase is to go productive


with production system, dismantle existing system

Endures starts their transaction in R/3 .

You might also like