Professional Documents
Culture Documents
W ASAP and ACTIVATE Methodology
W ASAP and ACTIVATE Methodology
ASAP Methodology
We know this process very well because, this one using form many years.
In this we have five phases
project preparation
Business blue print
Realization
Final preparation
Go live and support
ASAP methodology
Business
Realization
blue print
Phases for ASAP methodology
Project preparation :In this phase we defined the project goals and objectiv es, the scope of
implemenations,the project schedule and resources.
Business blue print: We create blue print sap questions and answers, it contains the business blue
processes and organizational structure that will be represented in the SAP system.
Realization :considering the business blue print we configure the requirements in to the system,
also during this phase we perform integration test and create the end user documentation
Final preparation:Testing,end user training and cutov er activities before go liv e.
Go live & support: Mov e the pre production env ironment to liv e system, basically end users using
this system
Activate Methodology
SAP activate is a methodology used in S/4 HANA and is a unique combination of SAP best
practices,methodology,and sap guided configuration delivered with a reference
solution.
It enables to start fast, build smart, and run simple while continuously innovating in the
cloud and anywhere.
It is base line for S/4 HANA contain complete and consistent configuration settings, it
includes.
Business process structure with technical steps that include finance and logistics
Integration information with other cloud solutions, such as success factor employee
central or ariba network
Migration documents which help to migrate either form non SAP
Systems or from legacy SAP systems
Graphical representation of all business processes
Pre defined test scripts
Testing automation process available in S/4 HANA.
Guided configuration
It is a set of tools, assets and accelerates which assist the implementation SAP S/4 HANA,
this will help right from the initial setup all through after go live support, this one helps to
to bridge the gap between business and IT groups to have a successful implementation, the
entire process of collaboration will be recorded, thus supplying a configuration history.
One methodology: It is used for initiating any implementation of SAP S/4 HANA and
usage of SAP’s premium engagements.
How does SAP activate be deployed
ASAP 8 will be replaced with activate, this will supported in SAP S/4 HANA and
business suite
New implementation: In this scenario you are installing a new S/4 HANA and migrating
your data, client will benefit from new implementation.
System conversion :In this scenario you are already using SAP business suite or HANA
database and want to migrate to S/4 HANA, they can migrate data without
reimplementation and there is no effect on business process and existing process and
process flows.
How does SAP activate be deployed
Landscape transformation :In this scenario you might have complex requirements
Consolidation of current regional SAP business suite landscape into one global SAP
HANA system .
For each of the each scenarios, will go through four phases
1.prepare
2.Explore
3.realize
4.Deploy
Phases for activate methodology
Explore
Prepare Realize Deploy
Phases for activate methodology
Prepare: start with best practices by using re-using knowledge assets and pre build content
Explore: Moving in to pre assembly, solution validation workshops and delta backlog
Realize :In this phase iterative delta and scope implementation and E2E integration testing
Deploy: This is the final phased where the roll out is done.
Activate methodology with new implementation
Activate methodology for system conversion
Landscape conversion
Agile methodology and Water fall
Waterfall:
It is sequential approach, if project in realization phase, customer want to change the
current requirement again we do documentation and testing, it take time
It focus on process and documentation
We cannot change the plan means company showing contract between client and company
about time lines, it is not good.
Agile:
Fast process, there is no importance for documentation
Sprit planning section, scrum meeting and requirements
Customer collaboration is important not on contract.
Differences
Activate ASAP
It is based on agle/lean approach It is based on rigid/waterfall implementation.
using of blue print using blue print
reduced project life cycle It has more phases
Up to key deliverables per phase, thus easier It has phases but it is not accurate as activate
access to key guides and accelerates
It has waterfall
Blue print activities replaced with solution
It is not available on cloud
validation
Agile implementation is default
Using in cloud and on premise
Thank you