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

ASAP

what is meant by ASAP?

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Dec 01, 2007 at 10:09 AM

    hi vinothini,

    <b>ASAP: Accelerated Systems Application and Products in Data Processing</b>

    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.

    Read ASAP methodology for more details you will understand better.

    ASAP methodoligy means nothing but standard process for implementation of SAP, It consists of 5 phases. <b>summary detail:</b>

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

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

    Consists of detailed documentaion

    3. <b>Realization</b> -The purpose of this phase is to implement all the business and process requirements based on the

    Business Blueprint.

    4 <b> Final Preparation</b> - The purpose of this phase is to complete testing, end-user training,

    5<b> Go Live and Support</b>

    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

    Warm Regards,

    s.suresh.

    reward if useful..

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 02, 2007 at 07:02 AM

    Hi

    ASAP: Accelerated Systems Application and Products in Data Processing

    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

    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.

    Hope this is helpful.

    http://training.saptechies.com/category/sap-asap-documentation/

    http://searchsap.techtarget.com/sDefinition/0,,sid21_gci871489,00.html

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

    Check these posts

    asap-methodology

    asap

    <b>Reward if usefull</b>

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 01, 2007 at 09:26 AM

    Accelerated SAP, otherwise known as ASAP, is a methodology developed by SAP to speed up the implementation of ERP projects. One of its main goals, other than speeding up the integration, is to lower costs while not interfering with the ERP implementation and incorporation.

    Accelerated SAP, otherwise known as ASAP, is a methodology developed by SAP to speed up the implementation of ERP projects. One of its main goals, other than speeding up the integration, is to lower costs while not interfering with the ERP implementation and incorporation.

    http://training.saptechies.com/acceleratedsap/

    check the link for details

    Message was edited by:

    Abhishek Jolly

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 01, 2007 at 09:26 AM

    ASAP Methodology:

    Project Preparation:

    The first step in ASAP is Project Preparation. In this step the Functional Consultant will analyse the business process and define the system for SAP and will give the time line for the project. The Manpower required and the budgets are also considered in this step.

    Blue Print Preparation:

    This is second step in ASAP Methodology. In this step the Project Preparation scenarios are finalised. A out line of the Project is given in this step.

    Realisation:

    In this step actual development is taken place. The ABAPer is responsible for this step.

    Testing:

    In this step the development done by the abaper is being tested. This is the area where the Unit Test Document is prepared (i.e. Positive Testing and Negative Testing).

    GO live and Support:

    This is the final stage where the project is running in the live environment. In this step the bugs if any that are found in the go live procedure are fixed and the project will be considered as support project.

    Rewards if useful.

    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.