Roles & Responsibilities of MM Consultant during Full Life Cycle Implementation:

Implementation of SAP MM Module in integration with SD, FI/CO, PP, QM according to ASAP methodologies.
u2022 Study of Business Process & formulating AS-IS study
u2022 Preparation of TO-BE Business Blueprint
u2022 GAP Analysis
u2022 Realization & Configuration of SAP MM Module
u2022 Preparations of User manuals, Testing Documents and approval of the same
u2022 Preparation of Configuration Document, Functional and Technical Specifications, etcu2026
u2022 Providing Training to Key Users
u2022 Collection of Master Data, Testing of BDC/LSMW and uploading the same in Development, Quality and
Production Servers
u2022 Post Go-Live Support
http://help.sap.com/saphelp_47x200/helpdata/en/48/623972d55a11d2bbf700105a5e5b3c/content.htm
ASAP Roadmap
The ASAP Roadmap provides the methodology for implementing and continuously optimizing your SAP System. It
divides the implementation process into five phases and offers detailed Project Plans to assist you (in Microsoft
Project format). The documentation stored at each level of the Roadmap tree structure contains recommendations on
implementing your SAP System and links to helpful tools and accelerators.
Purpose
When you install the Implementation Assistant you can choose from several Roadmap types and flavors.
Roadmap types Roadmap flavors
Implementation R/3 System (Continuous Improvement)
BW
APO
Business-to-Business Procurement
In your implementation project (Roadmap type: Implementation), you can bring together several Roadmap flavors in
one Roadmap. The Implementation Assistant also helps you to implement a combination of software implementation
projects.
Features
The implementation of your SAP System covers the following phases:
1. Project Preparation: In this phase you plan your project and lay the foundations for successful
implementation. It is at this stage that you make the strategic decisions crucial to your project:
o Define your project goals and objectives
o Clarify the scope of your implementation
o Define your project schedule, budget plan, and implementation sequence
o Establish the project organization and relevant committees and assign resources
2. Business Blueprint: In this phase you create a blueprint using the Question & Answer database (Q&A db),
which documents your enterprises requirements and establishes how your business processes and organizational
structure are to be represented in the SAP System. You also refine the original project goals and objectives and
revise the overall project schedule in this phase.

3. Realization:
In this phase, you configure the requirements contained in the Business Blueprint. Baseline configuration (major
scope) is followed by final configuration (remaining scope), which can consist of up to four cycles. Other key focal
areas of this phase are conducting integration tests and drawing up end user documentation.

4. Final Preparation:
In this phase you complete your preparations, including testing, end user training, system management, and cutover
activities. You also need to resolve all open issues in this phase. At this stage you need to ensure that all the
prerequisites for your system to go live have been fulfilled.

5. Go Live & Support:
In this phase you move from a pre-production environment to the live system. The most important elements include
setting up production support, monitoring system transactions, and optimizing overall system performance.
After your system has gone live, you can use a separate Roadmap with six work packages, in order to optimize your
SAP System continuously.
These phases are the main milestones for your SAP System implementation project. Each phase has:
Work Packages, which consist of activities, for which project teams are responsible.
Activities, which consist of tasks, which are processed by one or more team members.
Tasks, which are carried out by a project team member. You can also access the How-to sections and
accelerators at this level.
The ASAP solution was developed to ensure the successful, on-time delivery of a project. SAP delivers the
Accelerated SAP (ASAP) methodology for project management and system implementation.
Developed by SAP to optimize the success of implementing the SAP Business Suite, ASAP streamlines the
implementation by providing templates, methods, tools, and accelerators that have been built on the success of
thousands of previous SAP implementations. The ASAP methodology adheres to a specific road map that addresses
the following five general phases:
1. Project Preparation, in which the project team is identified and mobilized, the project standards are defined, and
the project work environment is set up;
2. Business Blueprint, in which the business processes are defined and the business blueprint document is
designed;
3. Realization, in which the system is configured, knowledge transfer occurs, extensive unit testing is completed, and
data mappings and data requirements for migration are defined;
4. Final Preparation, in which final integration testing, stress testing, and conversion testing are conducted, and all
end users are trained; and
5. Go-Live and Support, in which the data is migrated from the legacy systems, the new system is activated, and
post-implementation support is provided.



What ASAP stands for? ASAP: Accelerated Systems Application and Products in Data Processing
All implementation projects have the following phases:
Scoping - What is to be implemented i.e. which sub modules are to be implemented some clients may not require
credit management for example. Look at the project scope document carefully it will tell you what SAP sub-modules in
SAP you should be prepared for. Usually the sales people along with project manager do it.
As is - Here you understand the existing business processes of the client. Your BPO collect all the ISO-
documentation (if client is ISO certified), reports and forms at this stage and you analyze how and when the
reports/forms are generated, where the data is coming from. You also do a Level -2 training for your BPO so he is
made aware of all the required transactions in SAP.
Once this is over BPO can start learning with the consultants help more about SAP. This is crucial because if you
miss out any transactions the BPO may forget about some of his Business processes which may come up later. It is a
good practice to ask the BPO to make flow charts to explain business processes.
To-Be - In Parallel you map these processes to SAP. Processes that you are not sure of as to whether they are
present in SAP or not you try to do a configuration of those processes, and along with the BPO(Business process
owner he is the clients employee who knows about the clients business processes probably a middle management
guy, there can more than one), BPO involvement is required as he may be able to tell you his requirements better.
Once you do the business modeling you will also be made aware of the gaps between as-is and to-be, here decisions
have to be made as to whether an ABAP development/system modification is required or not and so on. Involve the
BPO as much as possible and document everything it is good practice do not be lazy about it.
Business blueprint: Here the as-is and to-be and gap analysis is explained. This is the document that you will be
using to do your configuration in the realization phase.
Realization phase: Here you do the configuration in the development server (there are three clients -development,
quality, production). You also decide on the master data format, so that BPO can go collect the master data. You also
give ABAP specifications for forms, reports etc, system modifications etc. Unit testing: Your BPOs and a few key
users sit down and test your configuration in your module only. It is good to test the BDCs that you need for uploading
data at this stage so you have more realistic data and your BDCs are tested.
Integration testing: Once all modules unit testing is over then the configuration is transported to the Quality server,
where testing for all the modules is done by BPOs and end user, this is to check if any problems are there in
integration between various modules. Once all is okay from the QA server configuration is transported to the
production server.
Go live preparations Data uploading: The collected master data is checked and the uploaded into production server
(sever and client I have used interchangeably). Now you are ready for go live i.e. users can now use the production
server.
Read ASAP methodology for more details you will understand better.
ASAP methodology means nothing but standard process for implementation of SAP, It consists of 5 phases.
1. Project Preparations - consists of identifying team members and developing strategy as how to go.
2. Business Blue Print - consists of identifying the client current process, requirement and how SAP provides
solution. Consists of detailed documentation
3. Realization - The purpose of this phase is to implement all the business and process requirements based on the
Business Blueprint.
4 Final Preparation - The purpose of this phase is to complete testing, end-user training,
5 Go Live and Support