Dong - ASAPnew Roadmaps

8/16/2019 Dong - ASAPnew Roadmaps

1/3

ASAP Roadmap Enhancements

Purpose: Use this job aid to examine the changes that have been made to enhance ASAP

Roadmap.

1. SolMan and changes to ASAP

AcceleratedSAP (ASAP) is the widely accepted implementation methodology developed by SAP

for SAP projects. It is based pon standard templates! tools! training! and processes that help a

company optimi"e resorces in the implementation of an SAP R#$ system.

%ecase the methodology is based on rigid phases! new deployment methodologies & sch as

'ontinos %siness Improvement and Evalation & have more recently been created to

provide a more fleible approach. SAP Soltion anager (Solan) was released in *++, at the

same time that SAP released -eb Application Server (-ebAS). Solan evolved to inclde

mltiple implementation roadmaps and even new content. ew templates! a repository for

standardi"ed bsiness processes! and enhanced project management tools are some of the

improvements.

Soltion anager fnctions as a separate mySAP application system based on SAP -ebAS.

-hereas Solan did not ship as part of SAP R#$! it is now inclded with SAP ERP /.+! and se

of it is now inclded in maintenance fees.

eanwhile! the basis behind ASAP has changed. -ith SAP ERP /.+! ASAP is based on a

different for0step process1

,. Project Preparation

*. %siness %leprint

$. 'onfigration

2. 3esting

1. Project Preparation

In the Project Preparation phase! yo define the project and set p the system landscape. 3his

phase roghly aligns with the project preparation phase in the ASAP methodology of SAP R#$.


2/3

2. Business Blueprint

In the %siness %leprint phase! yo define the SAP soltion based on SAP processes.

4efining the soltion in this way aids in the overall docmentation of the implementation from a

project management perspective becase it more clearly ties yor bsiness processes to the

SAP soltion yo5re implementing. 3his phase roghly aligns to the original ASAP bsiness

bleprint phase. 6sing Solan greatly eases the process by providing the %siness Process

Repository (%PR) which incldes relevant docments! transactions! and configration spport

based on specific bsiness scenarios! and has seen mltiple improvements between SAP R#$

and ERP /.+.

3. Configuration

In the 'onfigration phase! yo configre bsiness processes and coordinate cstomi"ations to

match particlar bsiness processes to SAP best practices settings. %ased on the

docmentation developed dring the %siness %leprint phase! this is accomplished in two sb0

phases1

• baseline configration! which defines approimately 7+8 of yor specific

configration! and

• fine0tning! the remaining approimately *+8 of yor specific docmentation which

was not covered in the baseline configration

It is also dring this phase that yo begin wor9ing throgh the SAP Implementation :ide(I:).

4. Testing

In this final phase! yo perform testing of all bsiness processes. 3his incldes final testing and

what was the :o0;ive phase in the original ASAP methodology.

e! road"aps in SAP #$P %.&

SAP contines to evolve its implementation roadmaps by offering new methodologies as newprodcts are developed. Some of the new methodologies inclde

• ASAP roadmap for SAP Enterprise Portal

• ASAP implementation roadmap for SAP Echange Infrastrctre


3/3

• Soltion anager Roadmap

• :lobal 3emplate Roadmap! and

• 6pgrade Roadmap

2. 'ther considerations for SAP #$P %.&

-hen defining yor project team! yo typically want to have eperts from varios fields. -ith

SAP ERP /.+! yo mst consider adding the

Documents

Dong - ASAPnew Roadmaps