What is ASAP Focus Methodology

Can someone provide some PDF/DOC on what is "ASAP Focus Methodology"?
I do have link to SAP Consulting ASAP Focus.
Regards,
Jayant Chhallani

Hi Jayant,
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 - 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, the 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 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 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 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.
Regards
Tushar
P.S. Reward points for useful answer.

Similar Messages

  • ASAP Focus methodology in Solution Manager 4.0

    Hi
    I got a request about including the ASAP Focus methodology into Solution Manager. I have found the ASAP Focus Implementation .zip file, and I have unpacked it on the Solution Manager server. My question is how (and if) I can upload this information into Solution Manager 4.0?
    Thanks for your input!
    Best Regards,
    Thomas

    Dear Thomas,
    "ASAP Focus Methodology Implementation Roadmap" can be found from
    http://service.sap.com/solutionmanager -> Download -> Other content
    After download it, you can import it into your system via STMS.
    Note 826586 can be reviewed for further details.
    Hope this answers your query.
    Regards
    Amit

  • Does anyone know what the close focus is on the iPhone 4s?

    I was just wondering if anyone knew what the close focus on the iPhone 4s is? I want to get as close to something and want to know what too close is.
    Thanks

    I am far from certain but I believe it is the power management unit (PMU) reset switch a/k/a Cuda switch: http://support.apple.com/kb/HT1939
    Do not press it when the computer is on.

  • Metodología ASAP Focus

    ¿Alguien me podría facilitar algún manual o documentación de la metodología ASAP Focus en Español?
    Que contenga el mayor detalle posible de cada fase, con los entregables que se esperan por cada una de dichas fases.
    Desde ya muchas gracias!

    Este es un link de un libro en linea aunque se puede descargar
    http://www.buscador.iumx.eu/leer-online/?t=metodologiaproyectosasap+PDF&d=http://e-archivo.uc3m.es/bitstream/10016/6250/1/FTC_PFC_Final.pdf
    Se refiere a una implementacion de soluciones SAP para el mercado de Telecomunicaciones siguiendo la metodologia ASAP.
    Espero le sirva la informacion
    Saludos

  • 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

  • ASAP- Implementation Methodology??

    Hi experts
    I am going to work on a implementation project for the first time.  ASAP will be use as an implementation methodology. So, if i can get any document or material explaining how to work on this methodology will be of a great help.
    Ur replies will be rewarded with full points
    Thanks

    Hi
    Refer
    http://help.sap.com/saphelp_46c/helpdata/EN/fc/5dc13690581b20e10000009b38f839/frameset.htm
    Regards

  • What is the best methodology to handle database schema changes after an application has been deployed?

    Hi,
    VS2013, SQL Server 2012 Express LocalDB, EF 6.0, VB, desktop application with an end user database
    What is a reliable method to follow when there is a schema change for an end user database used by a deployed application?  In other words, each end user has their own private data, but the database needs to be expanded for additional features, etc. 
    I list here the steps it seems I must consider.  If I've missed any, please also inform:
    (1) From the first time the application is installed, it should have already moved all downloaded database files to a separate known location, most likely some sub-folder in <user>\App Data.
    (2) When there's a schema change, the new database file(s) must also be moved into the location in item (1) above.
    (3) The application must check to see if the new database file(s) have been loaded, and if not, transfer the data from the old database file(s) to the new database file(s).
    (4) Then the application can operate using the new schema.
    This may seem basic, but for those of us who haven't done it, it seems pretty complicated.  Item (3) seems to be the operative issue for database schema changes.  Existing user data needs to be preserved, but using the new schema.  I'd like
    to understand the various ways it can be done, if there are specific tools created to handle this process, and which method is considered best practice.
    (1) Should we handle the transfer in a 'one-time use' application method, i.e. do it in application code.
    (2) Should we handle the transfer using some type of 'one-time use' SQL query.  If this is the best way, can you provide some guidance if there are different alternatives for how to perform this in SQL, and where to learn/see examples?
    (3) Some other method?
    Thanks.
    Best Regards,
    Alan

    Hi Uri,
    Thank you kindly for your response.  Also thanks to Kalman Toth for showing the right forum for such questions.
    To clarify the scenario, I did not mean to imply the end user 'owns' the schema.  I was trying to communicate that in my scenario, an end user will have loaded their own private data into the database file originally delivered with the application. 
    If the schema needs to be updated for new application features, the end user's data will of course need to be preserved during the application upgrade if that upgrade includes a database schema change.
    Although I listed step 3 as transferring the data, I should have made more clear I was trying to express my limited understanding of how this process "might work", since at the present time I am not an expert with this.  I suspected my thinking
    is limited and someone would correct me.
    This is basically the reason for my post; I am hoping an expert can point me to what I need to learn about to handle database schema changes when application upgrades are deployed.  For example, if an SQL script needs to be created and deployed
    then I need to learn how to do that.  What's the best practice, or most reliable/efficient way to make sure the end user's database is changed to the new schema after the upgraded application is deployed?  Correct me if I'm wrong on this,
    but updating the end user database will have to be handled totally within the deployment tool or the upgraded application when it first starts up.
    If it makes a difference, I'll be deploying application upgrades initially using Click Once from Visual Studio, and eventually I may also use Windows Installer or Wix.
    Again, thanks for your help.
    Best Regards,
    Alan

  • I have a 2-gen iTouch that I love.  Thinking of buying a 4-gen.  Can I transfer my apps and the results to a new iTouch?  What I'm focused on is a solitaire app that I've played more than 1000 games on with a 69% win rate.  I know it's crazy but I want to

    ... continue that.

    Yes. Make a new backup of your current iPod Touch in iTunes.  See this article for whats included in a backup.
    http://support.apple.com/kb/ht1766
    When the new iPod Touch arrives, plug it in and register it, and then restore the iPod from that backup to retain all your App data.
    http://support.apple.com/kb/ht1414
    Items such as your Apps, music, movies, etc. should all still be in your iTunes library, so you should just be able to configure the new iPod to sync these items.
    B-rock

  • What is the best methodology to build modular applications?

    Hello,
    I am working on a project that uses database access quite heavily.
    Now, as I am a beginner, I wanted to go a very modular approach by building one module at the time and then assemble it in the overall application.
    I tried to use <SWFLoader> to do this assembly work. I have a top level file where I load teh module when needed and render them visible (or invisible) which worked nicely.
    Now, with some recent problems with release builds and putting the finished application from the localhost  to the real URL, I am not so sure that this is the best.
    The alternative would be of course to do a single project and work with states, but this will make the project more difficult to oversee (maybe I miss something)
    Can somebody suggest something and hint where the best resources (tutorials, book, demo applications...) for my problem can be found.
    Many thanks
    peter

    If I were just starting out I would forego using modules at all.  Chances are your application isn't going to be big enough to warrant the usage of modules.  Other problems such as architectural ones will crop up long before it does get that big.

  • Focus ASAP

    What is the difference between ASAP & Focus ASAP Methodology? Advatages of Focus ASAP?

    check these,
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/501c66ff-c31c-2a10-62ad-9588691d78ae
    Re: What is ASAP Focus Methodology
    for advantages refer this
    http://www.sap.com/asia/industries/pdf/che_BWP_SB_Accelerate_Implementation.pdf
    Regards,
    Ravi

  • 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 <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.
    Hope this will help.
    Regards,
    Naveen.

  • What isASAP methodology?

    Hi
    What is  ASAP methodology?
    What is the use of ASAP?
    What is the Diff b/w Solutiona manager and ASAP?
    Thanks.

    Dear Swaroop,
    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.
    Hope this will help.
    Regards,
    Naveen.

  • What exactly are the SAP Testing Methodologies?

    Hi,
    I am researching on the various testing methodologies in SAP and came across a couple of discussions such as this link:  
    testing methodologies in sap
    It mainly discusses:
    AcceleratedSAP (ASAP) methodology, and tools available for AcceleratedSAP such as Project Estimator, ASAP Implementation Roadmap and Project Plan, etc
    I do not see those as TESTING more so as approaches for implementation such as SDLC or the Accenture Development Life Cycle.
    1. Am I misunderstanding what they mean in the SAP environment as u201CSAP Testing Methodologiesu201C ?
    2. What does it mean when a job description indicates
         "Knowledge of software development and testing methodologies (S/W life cycle)"
       ii.  Also, what is "S/W life cycle"
    Thanks
    Edited by: AmandaBaah on Jan 15, 2010 4:53 PM

    Some useful links related to this topic
    http://www.sap-img.com/general/role-of-sap-consultant-in-testing.htm
    Check Page 4 in following link
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0b3c59d-7248-2c10-4694-f9eb30e94c38?quicklink=index&overridelayout=true
    --Project Estimator, ASAP Implementation Roadmap, Project Plan etc are for complete SAP project and NOT particular to Testing.
    http://help.sap.com/printdocu/core/print46c/en/data/pdf/SVASAPE/SVASAPE_01.pdf
    http://www.sap-basis-abap.com/sapgeneral/what-is-asap.htm
    http://www.slideshare.net/arun_bala1/asap-methodology
    http://www.sap-img.com/sap-catt.htm

  • 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

  • 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

Maybe you are looking for

  • Parse error when using  ojspc SAMPLE.WAR

    Hi, I am facing oracle.jsp.parse.JspParseException while using ojspc SAMPLE.WAR Parse error in index.jsp: oracle.jsp.parse.JspParseException: /index.jsp: Line # 20, <%@ taglib uri="/tags/struts-logic" prefix="logic" %> Error: org.apache.struts.taglib

  • CF7 and JDK 1.4.2 - EV SSL Certificate Issue

    Let me start off by telling the group that we do not use CF for any of our applications.  We are a payments company that hosts a .NET API in IIS that 100's of thousands of customer use.  We have one particular customer using CF7 and JDK 1.4.2 who is

  • Enhancement for PO creation in EBP

    Hi , When I create a PO and shopping cart in EBP,the Goods recepient is not transferred to R/3. Can anyone suggest a proper user-exit/BADI to transfer this to R/3 while creating PO in EBP? Thanks, Sandip.

  • Do any of you know how to use NetBeans?

    I downloaded NetBeans 4.0 and tried to start a new project and entered my Hello World code in the code window but it said something like "No main class set". I was wondering if someone could post some step by step instructions of how to create a simp

  • JTextfield:  Changing focus, then doing stuff

    So I have 3 JTextFields that are essentially "connected" (I automate tabbing and such back and forth). I have no problem gaining focus, whether it be transferFocusBackward(), or whatever else. My problem is when getting the focus I cannot do anything