SAP

[Former Member]

WHAT IS THE ASAP METHODOLOGY

[Former Member]

Hello Satish Kotte,

ASAP methodoligy means nothing but standard process for implementation of SAP, It consists of 5 phases.

1. Project preperation - consists of identifying team members and developing strategy as how to go.

2. Business Blue print - consists of identifying the client current process, reqeirement and how SAP provides solution.

Consists of detailed documentaion

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

All the functinal consultatns need good rapo with Abapers. right from uploading of legacy data, devoloping customised reports, BDC's, Forms etc, here functinal consultatns need to give guidence as to get the requried data for reports and all.. like the table name, fields etc

Now ASAP is absolute as SAP released Solution Manager.

Thanks,

Greetson

[Former Member]

ASAP methodology

AcceleratedSAP (i.e. ASAP) methodology/roadmap is a proven, repeatable and successful approach to implement SAP solutions across industries and customer environments. ASAP is widely used for SAP Business Suite (SAP ERP, SAP CRM, SAP SCM, SAP PLM, SAP SRM), SAP xApps, SAP NetWeaver and SAP Solutions for Mobile Business among many other solutions. The methodology covers the necessary project management, the configuration of business processes, testing and training aspects as well as technical implementation activities.

In order to ensure central data access, the ASAP roadmap and tools have become a standard component in SAP Solution Manager (service.sap.com/solutionmanager) - the implementation and operations platform. In addition, ASAP is available for browsing and offline use on Service Market Place. From tool perspective, the SAP Solution Manager implementation function is the successor to the ASAP tools, hence some tools such as the Implementation Assistant, Q&Adb, and the Master Lists are replaced by Solution Manager Implementation Function.

ASAP Roadmap

Use

The ASAP Roadmap provides the methodology for implementing and continuously optimizing your SAP software. 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 software and links to helpful tools and accelerators.

Purpose

When you install the Implementation Assistant you can choose from several Roadmap types and flavors. You can select one of the following flavors:

• R/3 - Implementation and Continuous Improvement

• APO - Advanced Planner & Optimizer

• BW - Business Information Warehouse

• B2B - Business to Business

• CRM - Customer Relationship Management

Features

Implementation of SAP software 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:

− Define your project goals and objectives

− Clarify the scope of your implementation

− Define your project schedule, budget plan, and implementation sequence

− Establish the project organization and relevant committees and assign resources

2. Business Blueprint

In this phase you create a blueprint, which documents your enterprise’s requirements and establishes how your business processes and organizational structure are to be represented in SAP software. 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 R/3 System continuously.

These phases are the main milestones for implementing SAP software. 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.

Check this AcceleratedSAP document.

http://help.sap.com/printdocu/core/print46b/en/data/en/pdf/SVASAP.pdf

Check this PDF document.

http://hosteddocs.ittoolbox.com/CM021805.pdf

Also check this too.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a32662d9-0b01-0010-a588-ccd23adf...

[Former Member]

Hi,

ASAP: Accelerated Systems Application and Products in Data Processing

All implementation projects have the the following phases:

Scoping - What is to be implemented i.e. which submodules 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 BPOcollect all the ISO-documentation (if client is ISO certified), reports and forms at this stage and you analyse 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 - Parallely 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, ther can more than one), BPO involvement is required as he may be able to tell you his requirements better. Once you do the business modelling you

will also be made aware of the gaps between as-is and to-be , here decisons have to be made as to wether a 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 gove 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 trasported 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 config is transported to the production server.

Go live preparation

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.

steps to implementit:

It would be helpful to go through the help document of ASAP Methodology.

The following information may clarify some doubts/requirements you have.

Generating the Project IMG through ASAP:

After you have set the project scope, the next step is to generate the Project IMG. From the Business Process Master List (BPML), you can directly access the IMG activities relevant for configuring each process.

BPML: The Business Process Master List, along with the Business Blueprint, is a key result of the second phase of the Roadmap. Microsoft Excel tables contain the SAP scenarios, process groups, and processes that have been set in scope in the SAP Reference Structure, and are crucial for configuring your SAP System. In Realization, the third phase of the Roadmap, the BPML provides the basis for monitoring and steering test activities and for configuring your SAP System. It contains the titles of the structure items, and displays the status, the owner, links to documentation and links to the SAP System. Amongst other things, the BPML allows you to:

1) Set your baseline and final scope. These are used for baseline and final configuration.

2) Access the Project IMG and specific IMG activities assigned to structure items.

3) Access integration test plans, which help you carry out all required integration tests.

The Prerequisite is you have set the project scope.

Process Flow to use the Business Blueprint as a basis for configuring your SAP System:

1) Set the project scope.

2) Generate the Project IMG.

3) Generate the BPML.

4) From a specific processes in the BPML, you can go to the relevant IMG activities and make Customizing settings.

regards,

vineela.

[Former Member]

hi...

plz see it...

The ASAP solution was developed to ensure the successful, on-time delivery of a project. SAP delivers the AcceleratedSAP (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. 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.

ASAP incorporates standard design templates and accelerators covering every functional area within the system, as well as supporting all implementation processes. Complementing the ASAP accelerators, the project manager can create a comprehensive project plan, covering the overall project, project staffing plan, and each sub-process such as system testing, communication and data migration. Milestones are set for every work path, and progress is carefully tracked by the project management team.

Effective Communication

Weekly update meetings ensure full communication between the project team, the client project team, and project management. These meeting are used not only to update on project status, but also to identify any issues or risk areas that may threaten the project. By identifying these problems early, they are more easily mitigated and resolved, reducing their impact on the project timeline.

Ensuring Quality and Mitigating Risk

Project quality is verified near the completion of each project phase. Using existing ASAP checklists, these quality checks ensure that all tasks for the phase have been completed properly, that all relevant documentation has been kept, and that all tasks required to commence the next phase of the project have been completed.

In addition to the specific project team, companies may use Quality Assurance reviews on all of its projects to ensure that experience gained on other projects has been taken into account and that the optimum system design has been utilized.