documentation

[Former Member]

what are the different types of documents involved in an implementation project, how are they prepared and who prepares them?

[Former Member]

Dear Sadu,

Visit the following wiki link for SAP Implementation:

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

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.

Regards,

Naveen.

[Former Member]

Hi,

In Implementation Each and every Phase needs to be documented. In Phase1 about the total Project Plan and Procedures are need to be documented. this is taken care by Project High Level Authorities. in Business Blue Print Phase total Business Process needs to be documented this is taken care by Functional Consultants and Business Process Owners with the help of QADB and CI Templates. The Output Of this Phase is BBP. with the help of BBP we do Configuration and Customization accordingly. In realization Phase we do Documentation for what we Configured and Prepare test cases for each and evry process. In Final Preparation Stage Project High Level Autho's do the Cut Over Plan and Documentations.

And Some more Documents involved in each and every phase . but as per my knowledge and in our project we do generated the docs as above mentioned.

Reward If Helpful.

Regards,

Praveen Kumar. D

[Former Member]

A functional consultant evaluates the demands in talking with the customer's representatives, transforms the essence into an abstract and algorithmic business model. Hence, he identifies the use cases and transforms them into logical and technical views.

Then the main task starts: customizing the respective business area and making sure the system reacts in the manner according to the constraints of the requested use case.

The consultant documents the settings and prepares proper guidelines that allow other consultants to do further changes or repairs with due efforts.

The consultant takes care that proper training is given to the users and that the system is usable, performing appropriately and the business flow is complete and correct.

During go live he assists the technical staff by testing the behaviour of the system.

After go live he guarantees that the procedures remain usable and consistent in real live situation and proposes enhancements.

The main duty of a consultant is to transfer external know-how to the client. It is not manpower that counts but intelligence, understanding of processes, a feeling for defects and general a common sense.

Role of a Functional Consultant in an End To End Implementation

When you talk about the role of a Functional consultant in an end to end implementation, I think it won't be possible for me or anybody to define everything but I will try to summarize it:

1. Functional consultant is expected to generate knowledge about the current business process, design current business flows, study current business processes and its complication, in all we can say getting through with current business setup. Flow diagrams and DFD are prepared, most of the time in Vision format, all this forms the part of AS IS document.

2. Everything configured has to be documented as per their categories in the form of predefined templates, these have to be then approved by the team leads or who ever the consultant is reporting to.

3. Mapping and GAP analysis is done for each module, I have seen people defining integration after mapping, gap analysis and configuration is done, but as per my experience in implementation, it is a simultaneous process.

4. Before starting configuring future business processes in SAP, the DFD/ERD are prepared, this documentation is called TO BE, which can be also siad as the result of mapping and gap analysis.

5. Sometimes Functional consultants are also expected to prepare test scripts for testing the configured scenarios.

6. End user manual and user training is also expected from F.Consultants.

The project normally starts off with a Kick off meeting in which the team size, team members, reporting system, responsibilities, duties, methodlogy, dates and schedules, working hours which have been predicided are formally defined.

ASAP, it won't be possible for me to explain it here, but all I can tell you about it is that it is SAP standard implementation methodology, which SAP prescribes but is not mandatory for any company to follow, such as IBM follow some blue Methodlogy, some companies follow typical SDLC steps, ASAP stands for Accerlated SAP, you can find all the steps on SAP site, through google, reading it from there won't give you a great knowledge about ASAP but will obviously get you to know the definitions of various term.

Regards,

Rajesh Banka