Skip to Content
author's profile photo Former Member
Former Member


Hi All,

I have a general query.

1) What are the different documents to be prepared in different phase of implementation? At which phase which documents are prepared?

2) What is Business Process aster List(BPML)?

3) What are different documents prepared durin differnt phase of support project,roll out project and upgradation project?

At which phase which documents are prepared?

Reward points for helpful answer.



Add comment
10|10000 characters needed characters exceeded

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Apr 02, 2008 at 08:58 AM

    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. These Documents are AS-IS Document, TO-BE Document, Gap Analysis, Minutes of Meetings & so on.... 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)._The Documentation here are Unit Testing Results, Integration Testing results, User testing results & so on..._

    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.


    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.

    Reward points if helpful.


    Rajesh Banka

    Edited by: Rajesh Banka on Apr 2, 2008 10:58 AM

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      2) And What is Business Process aster List(BPML)?

      BPML as the name suggest is a complied list of all the Business Process, which are mapped during the Implementation Stage.

      3) What are different documents prepared during different phase of support project,roll out project and upgradation project?

      At which phase which documents are prepared?

      In support Project, the documentation to be prepared are regarding how ticket handling. It is also recommended to prepare document on how the ticket was resolved.

      Handling tickets is called Issue Tracking system. The errors or bugs forwarded by the end user to the support team are prioritized under three seviority High, Medium and Low. Each and every seviority as got its time limits before that we have to fix the error.

      The main job of the supporting consultant is to provide assistance on line to the customer or the organisation where SAP is already implemented for which the person should be very strong in the subject and the process which are implemented in SAP at the client side to understand,to analyse,to actuate and to give the right solution in right time.This is the job of the support consultant.

      The issues or the tickets(problems) which are arised is taken care of on priority basis by the support team consultants.

      The work process in support projects are given below for your reference.

      1. The customer or the end user logs a call through any tool or by mail (RADIX).

      2. Each one of the support team is a part of support group.

      3. Whenever a customer logs a call he /she has to mention to which work group (by name).

      4. Once the calls came to the work group the support consultant or the team need to send an IR (Initial Response) to the user depending upon the priority of the calls. (Top,High,Med,Low,None)

      5. Then the error is fixed, debugged by the support consultant or the team. Then after testing properly by generating TR(Transport Request through the basis admin)

      6. Then it is informed to the end user/customer/super user about the changes which have moved to the production server by CTS process.

      These are the process. In summary, what I understand is that if any configuration or customization is required to solve the issue, then the consultant have to work on DEV Client, then the end user will test it in the QA client and after approval the BASIS consultant has to transport it to the PRODUCTION client.

      An example:

      Tickets in SD can be considered as the problems which the end user or the employee in the company face while working on R/3. Tickets usually occur during the implementation or after theimplementation of the project. There can be numerous problem which can occur in the production support and a person who is working in the support has to resolve those tickets in the limited duration, every ticket has the particular deadline alert so your responsibility is to finish it before that deadline.

      To begin with , we should give "TICKET" to you for not knowing it.

      Here is an eg of a ticket raise:

      End user is not able to

      1. Create Sales order for a customer from a New plant , since shipping point determination is not happened . ( Without Shipping point the document becomes INCOMPLETE and he will not be able to proceed further like DELIVERY, BILLING).

      He raises a ticket and the priority is set in one of the below:

      1. Low 2. Medium 3. High.

      Now you need to solve this ticket. You would analyze the problem and identify that the SP configuration has to be done for the new plant.

      You would request a transport for DEV CLIENT to BASIS. You do the change and Request one more Transport to BASIS for QA client. The End user will test the same by creating a sales order for the new plant and approve it.

      Finally, you request a transport to move the changes to PRODUCTION. Once the change is deployed in production the TICKET is closed. What I have given is a small example. You would get some real issues with severity HIGH in your day-day support.

      In RollOut Projects, we require to document the configuration document, as user manual can be reusable.


      Rajesh Banka

  • author's profile photo Former Member
    Former Member
    Posted on Feb 20, 2012 at 01:00 PM


    Add comment
    10|10000 characters needed characters exceeded