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

what is methodology in sap

what is methodology in sap

Add a comment
10|10000 characters needed characters exceeded

Related questions

7 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jul 25, 2007 at 06:36 AM

    Hi friends,

    Where can we get the ASAP Methodolgy.

    I have seen that only the roadmap is available. The implementation tools are not available on the Service Marketplace.

    Earlier the ValueSAP was available for download, but now I am not able to locate it.

    Can you please send me the ASAP methodolgy, I require it urgently.

    Thanks

    Dinesh R

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Apr 28, 2007 at 03:24 PM

    Hi siva,

    Its <b>ASAP (AcceleratedSAP) is a step-by-step methodology</b> for speeding up the implementation of an SAP R/3 system. The components of ASAP, which can be used together or individually, are called accelerators. Accelerators are based on the best practices of SAP customers from around the world and consist of a number of templates, questions, and scenarios that require user input to help the user determine the best way to implement their R/3 system. According to SAP literature, ASAP can reduce the time required to implement an R/3 system by as much as 50%.

    Pl reward if it helps.

    Thanks,

    Sadhu Kishore

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Apr 28, 2007 at 03:26 PM

    Hi,

    Welcome to SDN.

    The ASAP Roadmap provides the methodology for implementing and continuously optimizing your SAP System. It divides the implementation process into five phases.

    Phase 1: During this phase the team goes through initial planning and preparation for SAP project.

    • Define project goals and objectives

    • Clarify the scope of implementation

    • Define project schedule, budget plan, and implementation sequence

    • Establish the project organization and relevant committees and assign resources

    Phase 2: Business Blueprint

    The purpose of this phase is to achieve a common understanding of how the company intends to run SAP to support their business. Also, to refine the original project goals and objectives and revise the overall project schedule in this phase. The result is the Business Blueprint, a detailed documentation of the results gathered during requirements workshops.

    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). Other key focal areas of this phase are conducting integration tests and drawing up end user documentation.

    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. The most important elements include setting up production support, monitoring system transactions, and optimizing overall system performance.

    For any help on the ASAP methodology you can refer to the links.

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

    http://service.sap.com/asap

    http://service.sap.com/roadmaps

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

    http://www.tojet.net/e-book/SAPBook.pdf

    http://www.uky.edu/IT/AdminApps/IRISTechPortal/Presentations/Presentations.htm

    http://iris.tennessee.edu/sap_project.htm

    Regards,

    Ferry Lianto

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Apr 28, 2007 at 09:31 PM

    Methodolgy for SAP Implementation Project is as under:

    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

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 25, 2007 at 06:39 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. 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

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 22, 2007 at 06:34 AM

    Hi

    ASAP Methodology:

    Phase 1- Project preparation: initial planning and preparation.

    Phase 2 - Business Blueprint: documentation of the business process requirements of the company.

    Phase 3 - Realization: implement all business and process requirements based upon the business blueprint.

    Phase 4 - Final Preparation: complete testing, user training, system management and cut-over activities.

    Phase 5 - Go-Live & Support: transition from implementation to production

    Send me ur mail id i will send u pdf document on SAP methodologies

    Regards

    anand Yadav

    <b><REMOVED BY MODERATOR></b>

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 22, 2007 at 09:30 AM

    hello siva

    The ASAP methodology is recommended by SAP for implementation planning and system implementation. It has the following phases.

    Project Preparation - The primary focus of Phase 1 is getting the project started, identifying team members and developing a high-level plan.

    Business Blueprint - The primary focus of Phase 2 is to understand the business goals of the company and to determine the business requirements needed to support those goals.

    Realization - The purpose of this phase is to implement all the business and process requirements based on the Business Blueprint. You customize the system step by step in two work packages, Baseline and Final configuration.

    Final Preparation - The purpose of this phase is to complete testing, end-user training, system management and cut over activities. Critical open issues are resolved. Upon the successful completion of this phase, you will be ready to run your business in your productive R/3 system.

    Go Live and Support - Transition from a project oriented, pre-productive environment to a successful and live productive operation

    rewards if it helps

    siva

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.