cancel
Showing results for 
Search instead for 
Did you mean: 

implementation

Former Member
0 Kudos
99

what are the steps involved in implementation project?

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Reward suitable points.

  • How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

Former Member
0 Kudos

Refer link below for a brief ASAP stages

<a href="http://en.wikipedia.org/wiki/SAP_Implementation">ASAP SAP IMPLEMENTATION</a>

Former Member
0 Kudos

Dear Ramesh,

AcceleratedSAP (ASAP) is SAP's standard implementation methodology. It contains the Roadmap, a step-by-step guide that incorporates experience from many years of implementing R/3. Along with that, AcceleratedSAP contains a multitude of tools, accelerators and useful information to assist all team members in implementing R/3. Quality checks are incorporated at the end of each phase to easily monitor deliverables and critical success factors. ASAP is delivered as a PC-based package, so that - if required - an implementation project can begin prior to having an R/3 System installed.

AcceleratedSAP (ASAP): A comprehensive solution for the introduction of the R/3 System in your enterprise. ASAP and most of its tools can be used independently of an R/3 installation.

The tools available for AcceleratedSAP are:

The <b>Project Estimator</b>, an internal SAP tool which enables SAP consultants to accurately gauge the required resources, the costs and the time frame of implementation. The Project Estimator takes into account the project scope and several project and risk factors.

The <b>Concept Check Tool</b>, a tool enabling you to carry out quality checks on the project preparation, technical infrastructure and R/3 configuration settings. This is done mainly during the first two implementation phases of the R/3 project. In this way you are alerted to potential data volume and configuration conflicts that could lead to performance issues if not addressed.

The <b>Implementation Assistant</b>: The ASAP navigation tool that accompanies you through the five phases of implementation down to the task level. It includes a description and a detailed "how-to" for each task in the Roadmap. Along with that, many tools, templates and documents are hyperlinked to the task. The Implementation Assistant contains the following elements:

<b>ASAP Implementation Roadmap</b> and <b>Project Plan</b>. The Roadmap contains the five phases, from which you can drill down into work packages, activities and tasks. The Project Plan contains three components, a budget plan, a resource plan and a work plan. These are explained in more detail in the next chapter.

The ASAP Roadmap is the successor of the R/3-based Procedure Model, which was used until Rel. 3.1 in R/3 implementation projects.

<b>Knowledge Corner</b>, containing tips and tricks for configuration from consultants, detailed documentation on SAP’s implementation services, information on technical tools, as well as simplification guidebooks and R/3 Customizing wizards.

<b>Question and Answer Database (Q&Adb)</b>. Using the R/3 Reference Model structure, the Q&Adb is used to assist in gathering requirements for business processes, conversions, reports, interfaces, enhancements and authorizations. The database provides useful questionnaires to help you define the process needs and also serves as a repository for all this information. Since it is a database, it allows for flexible reporting. The business requirements generated from the Q&Adb are collectively known as the Business Blueprint.

<b>Business Process Master List</b>, to manage configuration, testing and the creation of end user documentation. The Business Process Master List is linked to pre-written Business Process Procedures (BPPs), detailled end-user documentation for R/3 transactions.

<b>Issues Database</b>: supporting project management, this database supports the entering, monitoring and managing of issues that come up during the project.

Introduction:

http://www.sapfans.com/sapfans/asap/be_01_e.htm

Accelerated SAP:

http://www.sapfans.com/sapfans/asap/be_02_e.htm

Phase 1 : Project preparation

http://www.sapfans.com/sapfans/asap/be_03_e.htm

Phase 2 : Business Blueprint

http://www.sapfans.com/sapfans/asap/be_04_e.htm

Phase 3: Realization

http://www.sapfans.com/sapfans/asap/be_05_e.htm

Phase 4 : Final Preparation

http://www.sapfans.com/sapfans/asap/be_06_e.htm

Phase 5 : Go Live and Support

http://www.sapfans.com/sapfans/asap/be_07_e.htm

http://en.wikipedia.org/wiki/SAP_Implementation

http://www.sapfans.com/sapfans/asap/be_01_e.htm

http://www.sap-basis-abap.com/sapgeneral/what-is-asap.htm

Pl go thr below links on ASAP Methodology:

ASAP METHODOLOGY:

http://help.sap.com/saphelp_47x200/helpdata/en/48/623972d55a11d2bbf700105a5e5b3c/frameset.htm

http://www.sapfans.com/sapfans/asap/be_01_e.htm

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

.

ASAP Roadmap (SAP Help)

http://help.sap.com/saphelp_47x200/helpdata/en/48/623972d55a11d2bbf700105a5e5b3c/content.htm

ASAP Methodology & ASAP Roadmap (SAP Service Marketplace) - Requires OSS Login

http://service.sap.com/asap & http://service.sap.com/roadmaps

Overview of the ASAP methodology - Richard W. Vawter, University of Southern California

http://www-rcf.usc.edu/~anthonyb/itp320/ASAP.ppt sd-fi integration

Some additional Infomation on ASAP methodology:

Phase 1 - Project Preparation

Change Charter - Goals and objectives of Organizational Change? Management

Project Plan - This is a first cut focusing on milestones and? Work Packages; details to come.

Scope - Sets the initial definition of the? project; input from sales cycle.

Project Team Organization - Sets the who? of the project: Standards & Procedures - Sets the why and how of the project.

Phase 2 - Business Blueprint - Requirements reviewed for each SAP Reference Structure item and defined using CI Templates (in the Q&Adb). Business Blueprint - This is the output of the Q&Adb and is the key document for Phase 3.

Phase 3 - Realization - Master Lists - Define business scenarios and R/3 transactions to be realized in the system. BPP - Business Process Procedures representing R/3 transactions; used for unit testing & documentation. Planning - Defines how the configuration will be done and how it will be tested. Development Programs - Provides details of the external programming requirements. EU Training Material - End User training material and process documentation.

Phase 4 - Final Preparation Stress & Volume Tests - Plans for confirming the production hardware’s capabilities

Cutover Plan - The details of how to move to the production environment and go live

Conduct End User Training - Delivery of the necessary levels of R/3 End User training prior to going live

Phase 5 - Go Live & Support: Ensuring system performance through SAP monitoring and feedback.

Hope this will help.

Regards,

Naveen.

Former Member
0 Kudos

Five Phases of ASAP methodlogy.

Phase 1: Project Preparation - The purpose of this phase is to provide initial planning and preparation for your SAP project.

Phase 2: Business Blueprint - The purpose of this phase is to achieve a common understanding of how the company intends to run its business within the SAP System. The result is the Business Blueprint, a detailed documentation of the results gathered during requirements workshops. The Business Blueprint document represents the business process requirements of the company. It is the agreed statement of how the company intends to run its business within the SAP System.

Phase 3: Realization - The purpose of this phase is to implement all the business process requirements based on the Business Blueprint. The system configuration methodology is provided in two work packages: Baseline (major scope); and Final configuration (remaining scope).

Phase 4: Final Preparation - The purpose of this phase is to complete the final preparation (including testing, end user training, system management and cutover activities) to finalize your readiness to go live. The Final Preparation phase also serves to resolve all critical open issues. On successful completion of this phase, you are ready to run your business in your live SAP System.

Phase 5: Go Live & Support - The purpose of this phase is to move from a project-oriented, pre-production environment to live production operation.

Additionally:

Some additional Infomation on ASAP methodology:

Phase 1 - Project Preparation

Change Charter - Goals and objectives of Organizational Change&#61550; Management

Project Plan - This is a first cut focusing on milestones and&#61550; Work Packages; details to come.

Scope - Sets the initial definition of the&#61550; project; input from sales cycle.

Project Team Organization - Sets the who&#61550; of the project: Standards & Procedures - Sets the why and how of the project.

Phase 2 - Business Blueprint - Requirements reviewed for each SAP Reference Structure item and defined using CI Templates (in the Q&Adb). Business Blueprint - This is the output of the Q&Adb and is the key document for Phase 3.

Phase 3 - Realization - Master Lists - Define business scenarios and R/3 transactions to be realized in the system. BPP - Business Process Procedures representing R/3 transactions; used for unit testing & documentation. Planning - Defines how the configuration will be done and how it will be tested. Development Programs - Provides details of the external programming requirements. EU Training Material - End User training material and process documentation.

Phase 4 - Final Preparation Stress & Volume Tests - Plans for confirming the production hardware’s capabilities

Cutover Plan - The details of how to move to the production environment and go live

Conduct End User Training - Delivery of the necessary levels of R/3 End User training prior to going live

Phase 5 - Go Live & Support: Ensuring system performance through SAP monitoring and feedback.

Reward points if helpful.

Regards,

Rajesh Banka