Regrd the ASAP methodology in detail

Hi
iam new to sap bi i want to know the asap metholodogy,how we will prepare tech and functional specs,how do we test etc.
points will be assigned full.
regards
sapbi2009

hi,
Plz refer:
https://websmp105.sap-ag.de/asap
u will get lot of information from privious threads:
ASAP
ASAP methodologies
ASAP METHODOLOGY
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30d4a91c-a9ac-2a10-57b3-84817be370b8
Regards,
Archana

Similar Messages

Whar are the ASAP methodologies?

hi
what are the ASAP methodologies, and what are the steps(technical) involved in that?
thanks in advance,
bye

HI,
Project plan, Business Blue print, Realization, Final preparation & Go-Live - support.
1. Project Preparation: In this phase, decision makers define clear project objectives and an efficient decision making process (i.e. Discussions with the client, like what are his needs and requirements etc.). Project managers will be involved in this phase (I guess).
A Project Charter is issued and an implementation strategy is outlined in this phase.
2. Business Blueprint: It is a detailed documentation of your company's requirements. (i.e. what are the objects we need to develop are modified depending on the client's requirements).
3. Realization: In this only, the implementation of the project takes place (development of objects etc) and we are involved in the project from here only.
4. Final Preparation: Final preparation before going live i.e. testing, conducting pre-go-live, end user training etc.
End user training is given that is in the client site you train them how to work with the new environment, as they are new to the technology.
5. Go-Live & support: The project has gone live and it is into production. The Project team will be supporting the end users.

Implementing ASAP Methodology using SAP Solution Manager

Hi All,
Can any one help me with any documentation regarding ASAP methodology implementation using Solution Manager.
The step by step process and transaction codes used for implementing it are there any guides provided by SAP for implementing the ASAP methodology in Solman.
It's an implementation project that we would like to track each phase in Solman.
Kindly help me to get more details.
Thanks in advance.

Hi,
There are the 'ASAP Implementaion Roadmaps' wheras the latest available
is the 'ASAP Methodology for Implementation 7.0' Roadmap, and there are
the 'Upgrade Roadmaps' wheras teh lastest one of them is:
'Upgrade Roadmap (V3.2)'.
If you are on ST-ICO 150 SP24 both of these Roadmaps
should be available in your system.
There are two ways to display the roadmaps in RMMAIN.
One is to choose a project in RMMAIN, then the roadmap assigned to
the project in SOLAR_PROJECT_ADMIN is displayed.
The other one is to display any available roadmap in the system
To display one of the available roadmaps (without a project) choose
the button 'Other Roadmap' in RMMAIN and in the upcomming popup
hit the button 'No Project'.
After that you should get an addtional button besides the Project
button called Roadmaps (Other Roadmap).
When you hit now this button you will get a list of all available
roadmaps.
Some further notes for referencing (although they can be old but still helpful)
644651 How to find the Reference Model in Solution Manage
826586 ASAP Implementation Roadmap
Hope this helps.
Cheers
SH

ASAP Methodology

Hi all,
I have to do a business study for an implementation project,,, can anyone tell me where can i get the details of ASAP methodology.
regards,
urendra
[email protected]

Dear Urendra,
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 Project Estimator, 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 Concept Check Tool, 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 Implementation Assistant: 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:
ASAP Implementation Roadmap and Project Plan. 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.
Knowledge Corner, containing tips and tricks for configuration from consultants, detailed documentation on SAPs implementation services, information on technical tools, as well as simplification guidebooks and R/3 Customizing wizards.
Question and Answer Database (Q&Adb). 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.
Business Process Master List, 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.
Issues Database: 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 hardwares 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.

BW in asap methodology

hai Experts ,
can any one explain me where the BW team will involve in which phase in asap methodology.And what is the work of bw team in each phase of asap metholody.
infact i have some documents regarding the asap methodology but no doc provides me where exactly the bw work is involved...plz provide me the details where the bw team in ASAP methodology..
its urgent requirement for me....................
regards,
Suri

Hi
1.Porject Preparation
2. Blue print
3. Realization
4. Final preparation
5. Go live and support
From realisation onwards to go live and support the BW team is involved

BPP's / ASAP Methodology

Does anyone know where I can find BPP's? I have seen a few threads talk about Solution Manager, but I can't find BPP's there. I need BPP's for R/3 4.6C and 4.7
Or is there a version of the ASAP Methodology that can be downloaded?
Thank you,
Kathy

ASAP Methodology (additional Infirmation):
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 hardwares 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

ASAP methodology & Levels of support

HI experts,
For support analyst:
1.what is meant by level 1,2 &3 support in MM....
2. Can someone kindly brief me the diffrent phases of ASAP methodology in detail pls
Regards
Gandharva

Hi
Basically it depends on the SLA , the most of the company follow as below
L1 - Production issue - to be closed within - 1hour, 4 hours or 8 hours - Changes can be done in PRD itself or changes movd from Development - QAS - Production.
L2 - Medium changes - to be closed within the time frame based on the change request - It might be 2 days, 4 days or 1 week - Changes will be test in DEV and Moved to QAS for UAT and then it will be moved to PRD.
L3 - Set of changes - which means it is mini project, all the changes will be done within the duration, ex: 2 months. The changes will be moved to QAS for UAT and integration testing, finally all the changes will be moved to PRD, it has Go-live date and so on. this is kind of Mini projects.
ASAP
Refer following link;
ASAP Roadmap
http://help.sap.com/saphelp_47x200/helpdata/en/48/623972d55a11d2bbf700105a5e5b3c/content.htm
SAP Projects are implemented as per ASAP Methodology.
The ASAP solution was developed to ensure the successful, on-time delivery of a project. SAP delivers the AcceleratedSAP (ASAP) methodology for project management and system implementation.
Developed by SAP to optimize the success of implementing the SAP Business Suite, ASAP streamlines the implementation by providing templates, methods, tools, and accelerators that have been built on the success of thousands of previous SAP implementations. The ASAP methodology adheres to a specific road map that addresses the following five general phases:
1. Project Preparation, in which the project team is identified and mobilized, the project standards are defined, and the project work environment is set up;
2. Business Blueprint, in which the business processes are defined and the business blueprint document is designed;
3. Realization, in which the system is configured, knowledge transfer occurs, extensive unit testing is completed, and data mappings and data requirements for migration are defined;
4. Final Preparation, in which final integration testing, stress testing, and conversion testing are conducted, and all end users are trained; and
5. Go-Live and Support, in which the data is migrated from the legacy systems, the new system is activated, and post-implementation support is provided.
ASAP incorporates standard design templates and accelerators covering every functional area within the system, as well as supporting all implementation processes. Complementing the ASAP accelerators, the project manager can create a comprehensive project plan, covering the overall project, project staffing plan, and each sub-process such as system testing, communication and data migration. Milestones are set for every work path, and progress is carefully tracked by the project management team. Effective CommunicationWeekly update meetings ensure full communication between the project team, the client project team, and project management. These meeting are used not only to update on project status, but also to identify any issues or risk areas that may threaten the project. By identifying these problems early, they are more easily mitigated and resolved, reducing their impact on the project timeline. Ensuring Quality and Mitigating RiskProject quality is verified near the completion of each project phase. Using existing ASAP checklists, these quality checks ensure that all tasks for the phase have been completed properly, that all relevant documentation has been kept, and that all tasks required to commence the next phase of the project have been completed. In addition to the specific project team, companies may use Quality Assurance reviews on all of its projects to ensure that experience gained on other projects has been taken into account and that the optimum system design has been utilized.
What ASAP stands for ?
ASAP: Accelerated Systems Application and Products in Data Processing
All implementation projects have the following phases:
Scoping - What is to be implemented i.e. which sub modules 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 BPO collect all the ISO-documentation (if client is ISO certified), reports and forms at this stage and you analyze 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 - In Parallel 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, there can more than one), BPO involvement is required as he may be able to tell you his requirements better. Once you do the business modeling you will also be made aware of the gaps between as-is and to-be, here decisions have to be made as to whether an 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 give 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 transported 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 configuration is transported to the production server.
Go live preparations 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 methodology means nothing but standard process for implementation of SAP, It consists of 5 phases.
1. Project preparation - consists of identifying team members and developing strategy as how to go.
2. Business Blue Print - consists of identifying the client current process, requirement and how SAP provides solution. Consists of detailed documentation
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
Hope it clarifies.
Thanks & Regards
Kiran

SAP best practice and ASAP methodology

Hi,
        Can any body please explain me
                                                      1. What is SAP best practice?
                                                       2. What is ASAP methodology?
Regards
Deep

Dear,
Please refer these links,
[SAP best practice |http://www12.sap.com/services/bysubject/servsuptech/servicedetail.epx?context=0DFA5A0C701B93893897C14DC7FFA7D62DC24E6E9A4B8FFC77CA0603A1ECCF58A86F0DCC6CCC177ED84EA76F625FC1E9C6DCDA90C9389A397DAB524E480931FB6B96F168ACE1F8BA2AFC61C9F8A28B651682A04F7CEAA0C4%7c0E320720D451E81CDACA9CEB479AA7E5E2B8164BEC98FE2B092F54AF5F9035AABA8D9DDCD87520DB9DA337A831009FFCF6D9C0658A98A195866EC702B63C1173C6972CA72A1F8CB611798A53C885CA23A3C0521D54A19FD1B3FD9FF5BB48CFCC26B9150F09FF3EAD843053088C59B01E24EA8E8F76BF32B1DB712E8E2A007E7F93D85AF466885BBD78A8187490370C3CB3F23FCBC9A1A0D7]
[ASAP methodology|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/asap%2bfocus%]
ASAP methodology is one methodlogy used in implementing SAP .
The ASAP methodology adheres to a specific road map that addresses the following five general Phases:
Project Preparation, in which the project team is identified and mobilized, the project Standards are defined, and the project work environment is set up;
Blueprint, in which the business processes are defined and the business blueprint document is designed;
Realization, in which the system is configured, knowledge transfer occurs, extensive unit testing is completed, and data mappings and data requirements for migration are defined;
Final Preparation, in which final integration testing, stress testing, and conversion testing are conducted, and all end users are trained; and
Go-Live and Support, in which the data is migrated from the legacy systems, the new system are activated, and post-implementation support is provided.
ASAP incorporates standard design templates and accelerators covering every functional area within the system, as well as supporting all implementation processes. Complementing the ASAP accelerators, the project manager can create a comprehensive project plan, covering the overall project, project staffing plan, and each sub-process such as system testing, communication and data migration. Milestones are set for every work path, and progress is carefully tracked by the project management team.
Hope it will help you.
Regards,
R.Brahmankar

Reg, Documentation for a New Implementation using ASAP Methodology

Hello,
Will you pl, help me in getting complete documentation (Std / Template)for all stages of ASAP methodology, for a new module. If you provide at least URL, it will be of great help.

Hi Rao,
The ASAP Methodology has five phases:
1. Project Preparation project formally initiated and planning well under way.
2. Business Blueprint project team gathers requirements and conducts conceptual design of the solution.
3. Realization system solution is built and integration tested, end users trained
4. Final Preparation final check before cut over to new system solution
5. Go Live & Support solution confirmation, on-going support in place and project closing
http://media.sdn.sap.com/html/submitted_docs/Implementation_Roadmap_XI/index.htm
https://websmp105.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000420636&_SCENARIO=01100035870000000202
http://www.misa.bc.ca/docs/pdfs%2FMISA%20NEWS/Making%20ERP%20Work%20for%20Small%20Government.pdf
Hope this helps...
Best Regards,
DMK
*Assign points if it serves your purpose...

SAP BI Project ASAP Methodology

Hi Experts
Correct me if i was wrong,With regrads to the steps followed in ASAP Methodology
1)Requirements Gathering
2)GAP Analysis
3) FUNCTIONAL SPECIFICATIONS DOCs
4) Technical Specificaion Docs
5) Build
6) Test
7) Golive

Here are the steps in the ASAP Methodology:
Project Preparation
Project team identified and mobilized
Project standards defined
Project work environment setup
Blueprint
Business processes defined and documented
Business requirements defined
Gap Analysis
Business Blueprint document created and published
Realization
Functional Specification documents, including data mappings and data requirements, created and published
Configuration
Technical Specification documents created and published
Development
Unit Testing
Mock data migration or ETL
Final Preparation
Integration Testing
System Testing
User Acceptance Testing
End-User Training
Final mock data migration or ETL
Knowledge transfer
Go-Live and Support
Data migration or ETL
Application made available to general end-user population
Post-Implementation (Warranty) Support by development team
Turnover to Production Support team for steady-state support

Role of a Functional Consultant in each phase of ASAP Methodology

Hi
Can anyone Provide me details on Role of a Functional Consultant in each phase of ASAP Methodology.
Thanking you in advance
chan

Chan,
Below are some of main responsibilities of FC-
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.
REWARD POINTS IF U FINDS THIS USEFUL...
Regds
MM

Can anyone explain steps in ASAP Methodology

Can anyone explain steps in ASAP Methodology

Hi,
What is ASAP?
ASAP: Accelerated Systems Application and Products in Data Processing
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.
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
Reward If Helpfull,
Naresh

Difference between ASAP methodology and ASAP Road Map

hi
Difference between ASAP methodology and ASAP Road Map
amk

ASAP Roadmap
The ASAP Roadmap provides the methodology for implementing and continuously optimizing your SAP System. It divides the implementation process into five phases and offers detailed Project Plans to assist you (in Microsoft Project format). The documentation stored at each level of the Roadmap tree structure contains recommendations on implementing your SAP System and links to helpful tools and accelerators.
Check the following link:
http://help.sap.com/saphelp_47x200/helpdata/en/48/623972d55a11d2bbf700105a5e5b3c/content.htm
ASAP Methodology:
Accelerated SAP Deals with the Implementation Process Cycle in 5 Different Process...!!!
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.

Documents in ASAP Methodology

Hello Gurus
Could anyone please let me know what are the doccuments created in an implementation project in ASAP methodology?
like BPML......what other doccuments and their relevance?
Thank you verymuch your help in advance
M Reddy

Dear Reddy,
AcceleratedSAP (ASAP) is a comprehensive solution for efficiently implementing and continuously optimizing SAP software. It has a detailed, business-oriented structure and allows you to design implementation projects flexibly.
Implementation Considerations: AcceleratedSAP is currently a PC-based solution and is shipped independently of the R/3 system, allowing you to prepare for your implementation project before you have installed the SAP System.
You can use ASAP to:
(1) Implement the R/3 System
(2) Implement mySAP.com components (APO, BW, Business-to-Business Procurement, CRM)
(3) Upgrade
Following documents are generated during E2E Project Implementation;
(1) Project Charter
(2) Scope List
(3) AS IS / Legacy business process
(4) Business Blueprint / TO BE Document
(5) Business Process Master List
(6) Unit Test script
(7) Integration test scripts
(8) End user training plan and manuals
(9) Cutover strategy Document
(10) Custominzation document
(11) Master Data Goverance Strategy documents
Hope this information will be useful.
Bye,
Muralidhara

What is ASAP Methodology?

dear experts
i am very new to sap fico
just i wanted to know the process of getting/ starting an sap project' as i come to know the terminology of ASAP METHODOLOGY, GAP Analysis, BLUE PRINT............
JUST I want to knoe these terms in a sap- project nd its process

Introduction to ASAP Methodology
Accelerated SAP methodology is proven, repeatable and successful approach to implement SAP solutions across industries and customer environments.
It provides content, tools and expertise from thousands of successful implementations.
Phase 1: Project Preparation :
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.
Regards,
Meenakshi

Regrd the ASAP methodology in detail

Similar Messages

Maybe you are looking for