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

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

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 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.

Problem with FocusTraversalPolicy.. need help asap!!!!

I have Panel with six text fields. I have another subpanel with another three text fields placed on this main panel. I want to create a FocusTraversalPloicy in a way .. that the focus goes to the first field in the subpanel from the third text field of the main panel. And from the last text field of the Subpanel the focus should go to the 4th text field of the Main Panel. Help needed asap.
TIA,
BT

Hi,
main panel
- text field 1
- text field 2
- text field 3
- text field 4
- text field 5
- text field 6
- sub panel ( text field 7, text field 8, text field 9 )
focus seguence:
text field 1 ->text field 2 ->text field 3 ->
text field 7 ->text field 8 ->text field 9 ->
text field 4 ->text field 5 ->text field 6 ...
//----------------- CODE ----------
import java.awt.*;
import javax.swing.*;
public class TraversalPolicyDemo1 extends JFrame
JPanel mainPanel = new JPanel();
JTextField txtField1 = new JTextField();
JTextField txtField2 = new JTextField();
JTextField txtField3 = new JTextField();
JTextField txtField4 = new JTextField();
JTextField txtField5 = new JTextField();
JTextField txtField6 = new JTextField();
JPanel subPanel = new JPanel();
JTextField txtField7 = new JTextField();
JTextField txtField8 = new JTextField();
JTextField txtField9 = new JTextField();
public TraversalPolicyDemo1()
this.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
this.mainPanel.setFocusCycleRoot(true);
this.subPanel.setFocusable(false);
this.mainPanel.setFocusTraversalPolicy(new MyFocTrPol());
init();
private void init()
JPanel contentPane = (JPanel) this.getContentPane();
GridLayout gridLayout = new GridLayout();
gridLayout.setRows(7);
gridLayout.setColumns(1);
gridLayout.setHgap(10);
gridLayout.setVgap(10);
mainPanel.setLayout(gridLayout);
txtField1.setText("11111");
txtField2.setText("22222");
txtField3.setText("33333");
txtField4.setText("44444");
txtField5.setText("55555");
txtField6.setText("66666");
txtField7.setText("77777");
txtField8.setText("88888");
txtField9.setText("99999");
this.subPanel.add(txtField7);
this.subPanel.add(txtField8);
this.subPanel.add(txtField9);
mainPanel.add(txtField1, null);
mainPanel.add(txtField2, null);
mainPanel.add(txtField3, null);
mainPanel.add(txtField4, null);
mainPanel.add(txtField5, null);
mainPanel.add(txtField6, null);
mainPanel.add(subPanel, null);
contentPane.add(mainPanel, null);
public static void main(String[] args)
try
UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName());
catch(Exception e)
e.printStackTrace();
TraversalPolicyDemo1 frame = new TraversalPolicyDemo1();
frame.pack();
frame.setVisible(true);
}// end class TraversalPolicyDemo1
import javax.swing.*;
import java.awt.*;
public class MyFocTrPol extends LayoutFocusTraversalPolicy
public Component getComponentAfter(Container focusCycleRoot, Component aComponent)
Component ret=null;
Component first = focusCycleRoot.getComponent(0);//txtField1
Component second = focusCycleRoot.getComponent(1);
Component third = focusCycleRoot.getComponent(2);
Component fourth = focusCycleRoot.getComponent(3);
Component fifth = focusCycleRoot.getComponent(4);
Component sixth = focusCycleRoot.getComponent(5);//txtField6
Container seventh = (Container)focusCycleRoot.getComponent(6);//sub panel
Component sub_first = seventh.getComponent(0);//txtField7
Component sub_second = seventh.getComponent(1);//txtField8
Component sub_third = seventh.getComponent(2);//txtField9
if (aComponent.equals(first))
ret = second;
else if (aComponent.equals(second))
ret = third;
else if (aComponent.equals(third))
ret = sub_first;
else if (aComponent.equals(fourth))
ret = fifth;
else if (aComponent.equals(fifth))
ret = sixth;
else if (aComponent.equals(sixth))
ret = first;
else if (aComponent.equals(sub_first))
ret = sub_second;
else if (aComponent.equals(sub_second))
ret = sub_third;
else if (aComponent.equals(sub_third))
ret = fourth;
return ret;
}// end getComponentAfter
public Component getComponentBefore(Container focusCycleRoot, Component aComponent)
Component ret=null;
Component first = focusCycleRoot.getComponent(0);//txtField1
Component second = focusCycleRoot.getComponent(1);
Component third = focusCycleRoot.getComponent(2);
Component fourth = focusCycleRoot.getComponent(3);
Component fifth = focusCycleRoot.getComponent(4);
Component sixth = focusCycleRoot.getComponent(5);//txtField6
Container seventh = (Container)focusCycleRoot.getComponent(6);//sub panel
Component sub_first = seventh.getComponent(0);//txtField7
Component sub_second = seventh.getComponent(1);//txtField8
Component sub_third = seventh.getComponent(2);//txtField9
if (aComponent.equals(first))
ret = sixth;
else if (aComponent.equals(second))
ret = first;
else if (aComponent.equals(third))
ret = second;
else if (aComponent.equals(fourth))
ret = sub_third;
else if (aComponent.equals(fifth))
ret = fourth;
else if (aComponent.equals(sixth))
ret = fifth;
else if (aComponent.equals(sub_first))
ret = third;
else if (aComponent.equals(sub_second))
ret = sub_first;
else if (aComponent.equals(sub_third))
ret = sub_second;
return ret;
}// end getComponentBefore
public Component getDefaultComponent(Container focusCycleRoot)
return focusCycleRoot.getComponent(0);//txtField1
public Component getFirstComponent(Container focusCycleRoot)
return focusCycleRoot.getComponent(0);//txtField1
public Component getLastComponent(Container focusCycleRoot)
return focusCycleRoot.getComponent(5);//txtField6
public Component getInitialComponent(Window window)
Component def = getDefaultComponent(window);
if (def == null && window.isFocusableWindow())
def = window;
return def;
}// end class MyFocTrPol

Significant Computer Window Focus Problem With Verizon Access Manager 7.7.1.0 (2707e)

With the newly released Verizon Access Manager 7.7.1.0 (2707e) there is a significant computer focus problem with it.
What I mean by this is that if I am using ANY application on my computer with the Verizon Access Manager minimized to the Windows System Tray, something will go on with the Verizon Access Manager and it steals the window focus - I am unable to work in the other application unless I click on the application to use it again.
An example of this would be my typing to post a message in this forum. Something occurs in the Verizon Access Manager and my typing is rendered useless unless I click with my mouse on the browser window to be able to use it again.
I'm highly suspecting whenever networks are coming and going in the Access Manager is when the problem occurs.
This problem did not exist in the previous version of the Access Manager I was using.
This is extremely annoying - please issue a fix for this ASAP!

I have found by not minimzing the Verizon Access Manager 7.7.1.0 (2707e) the focus problem does not occur - it appears to be a problem when the app is minimzed to the system tray.

Live Scenario Please Reply ASAP

Dear Gurus
There is a live scenario. As you all must be knowing that the exchange rate changes every day.
I will explain the whole scenario.
The sales order was prepared on an exchange rate of Rs 46 for one Dollar. But when i am billling the exchage rate has changed to Rs 48 for one Dollar. How can it be changed automatically with out updation in the T Code 0B08 i.e. T Curr
Please guide and any further clarifications please revert back
Satish Kullu

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 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

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.

ASAP vs. Soution Manager

Hi,
I know what ASAP is and its phases. Can you please tell more on the differences between ASAP and Solution Manager? What does solution manager phases include? Why do they use Solution Manager over ASAP?
[email protected]
Thanks a lot.

HI REFER BELOW
refer the link:<a href="http://www.saptechies.com/category/sap-solution-manager/">SOLUTION MANAGER</a>
REWARD IF HELPS
The SAP Solution Manager offers a variety of services to manage production systems during
the operations phase. For example, the Self-Service procedures of the Service Level
Management framework and the SAP EarlyWatch Alert analyze the operational status of
mySAP.com solutions and trigger alerts and messages that reflect the state of the entire
solution. To help anticipate potential problems these Self-Services automatically trigger
recommendations for specific remote services and Self-Services in the SAP Solution
Manager.
The SAP Solution Manager will be the necessary platform for all related SAP Service and
Support issues. All customers who benefit from SAP Global Support offerings (for example,
TeamSAP Support Services, Solution Management Optimization and Solution Management
Review Services) will also benefit from the SAP Solution Manager. The main focus of
development in the SAP Solution Manager will be further enhancement in Business Process
Monitoring such as background job scheduling, and checks for data consistency, process
performance, and throughput
Best Practices for Solution Management
Best Practices for Solution Management are composed and developed by SAP using the
experience of thousands of customer installations and implementation projects. In general,
Best Practices are structured and delivered in different forms:
The SAP Solution Manager is available as technical add-on and is designed to run either on
mySAP Workplace 2.11 (with SAP Basis 4.6D), SAP R/3 4.6C or SAP Web Application
Server 6.10. The SAP Solution Manager will be shipped as one single add-on together with
the SAP Solution Architect for the new SAP Web AS 6.10 at the beginning of 2002.
What are the Benefits of the SAP Solution Manager?
November 8th, 2005
The SAP Solution Manager lowers the cost of ownership of the mySAP.com solution, optimizes system performance and ensures for smooth core business processes and extensive knowledge transfer to the customer through:
System and Application Management / Monitoring
Service Level Management / Reporting
Software Change Management for the entire solution
Bridging the gap between functional / application and system operations
Safeguarding and Back office support (expertise on demand)
Continuous technical improvement (saving costs)
Optimal SAP Support with integrated Support Desk
Permanent link to this post (77 words, estimated 18 secs reading time)
Message was edited by:
SHESAGIRI GEDILA

ASAP doccuments for SAP BW Implimentation

Hi,All!
           I am new to the job.pls send the SAP BW I mplementation doccuments to the mail ID give3n below.
    Mail ID : [email protected]
Thanks & Regards
      Sneha.

hi
Accelerated SAP (ASAP)
Project preparation:
intial stuff -- Do a conceptual review after this phase
Requirements gathering
Business blueprint:
Functional spec-- Do a design review after this phase
Realization : Develop; Do a configuration review after this phase
Final Preparation :QA and Other final stuff before moving to production, Do a performance Review after this phase
GoLive and support : to production and supprot
AcceleratedSAP (ASAP) Roadmaps
The ASAP Roadmaps provide you with proven, practical, comprehensive, repeatable, and rich implementation methodologies that enable speedy, focused implementation of SAP Solutions. ASAP Roadmaps cover the most important aspects and phases of a SAP solutions implementation, enhancements, or upgrade following the AcceleratedSAP (ASAP) principles.
The roadmaps are available for browsing and offline use on this site and also delivered as standard component of SAP Solution Manager - the implementation and operations platform.
ASAP Roadmaps
Deliver transparent, proven approach helping the project team to reduce implementation time, costs and risks throug efficient implementation process
Achieve better results by leveraging the experiences of other successful projects
Knowledge management - use the Implementation Roadmap for SAP Solutions to gather knowledge on how to organize and run your implementation projects
Benefits
Provide proven, practical and cost-effective project implementation approach. Flexible, scalable and tailorable to meet Project and Customer needs.
Leverage SAPs vast experience in the implementation, upgrade and operations of its Solutions as well as industry recognized best practices for effective Business Solutions.
Extends across all aspects of the solution life-cycle; from strategic reviews and analysis, to design, implementation, training and post project support.
Is scalable and can be tailored to meet customer and project specific requirements and constraints.
Supports different project types (single-site, multi-site, template, prototype, upgrade, evaluation, etc.)
Has been developed over many years to deliver cost-effective and successful implementation and is being continually enriched with content based on the experiences gained in implementing SAP Solutions

ASAP Method

Hi,
I would appreciate if somebody can tell me What is ASAP Methodology and what are the steps involved in it? What are the tools used for Testing and in which stage Enduser training is performed?
Thanks as always.
Naveen

Hi,
Please go through
ASAP methodology is traditional methodology, which follows certain steps & documentation is a manual activity.
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 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.
Thanks,
Sree.Manam

ASAP for BW

Hi gurus
Would you pl advise me the ASAP methodology for BW . If possible pl advise the no.of members required for an ideal project and their roles in BW implementation.
Thanks in advance

HI
Accelerated SAP (ASAP)
Project preparation:
intial stuff -- Do a conceptual review after this phase
Requirements gathering
Business blueprint:
Functional spec-- Do a design review after this phase
Realization : Develop; Do a configuration review after this phase
Final Preparation :QA and Other final stuff before moving to production, Do a performance Review after this phase
GoLive and support : to production and supprot
AcceleratedSAP (ASAP) Roadmaps
The ASAP Roadmaps provide you with proven, practical, comprehensive, repeatable, and rich implementation methodologies that enable speedy, focused implementation of SAP Solutions. ASAP Roadmaps cover the most important aspects and phases of a SAP solutions implementation, enhancements, or upgrade following the AcceleratedSAP (ASAP) principles.
The roadmaps are available for browsing and offline use on this site and also delivered as standard component of SAP Solution Manager - the implementation and operations platform.
ASAP Roadmaps
Deliver transparent, proven approach helping the project team to reduce implementation time, costs and risks throug efficient implementation process
Achieve better results by leveraging the experiences of other successful projects
Knowledge management - use the Implementation Roadmap for SAP Solutions to gather knowledge on how to organize and run your implementation projects
Benefits
Provide proven, practical and cost-effective project implementation approach. Flexible, scalable and tailorable to meet Project and Customer needs.
Leverage SAPs vast experience in the implementation, upgrade and operations of its Solutions as well as industry recognized best practices for effective Business Solutions.
Extends across all aspects of the solution life-cycle; from strategic reviews and analysis, to design, implementation, training and post project support.
Is scalable and can be tailored to meet customer and project specific requirements and constraints.
Supports different project types (single-site, multi-site, template, prototype, upgrade, evaluation, etc.)
Has been developed over many years to deliver cost-effective and successful implementation and is being continually enriched with content based on the experiences gained in implementing SAP Solutions
i sent to some documents to ur id
Regards,
A.M.S

Hi i need an example or a document to make an ASAP methodology

Hi all,
i m looking for an ASAP methodology, if you have one, i'll be really glad of starting mine, please send it to this direction: npi2004@hotmail , thanks guys !

Hi Jorge,
AcceleratedSAP (ASAP) Roadmaps provide you with proven, practical, comprehensive, repeatable, and rich implementation methodologies that enable speedy, focused implementation of SAP Solutions. ASAP Roadmaps cover the most important aspects and phases of a SAP solutions implementation, enhancements, or upgrade following the AcceleratedSAP (ASAP) principles.
The roadmaps are available for browsing and offline use on this site and also delivered as standard component of SAP Solution Manager - the implementation and operations platform.
ASAP Roadmaps
Deliver transparent, proven approach helping the project team to reduce implementation time, costs and risks throug efficient implementation process
Achieve better results by leveraging the experiences of other successful projects
Knowledge management - use the Implementation Roadmap for SAP Solutions to gather knowledge on how to organize and run your implementation projects
Benefits
Provide proven, practical and cost-effective project implementation approach. Flexible, scalable and tailorable to meet Project and Customer needs.
Leverage SAPs vast experience in the implementation, upgrade and operations of its Solutions as well as industry recognized best practices for effective Business Solutions.
Extends across all aspects of the solution life-cycle; from strategic reviews and analysis, to design, implementation, training and post project support.
Is scalable and can be tailored to meet customer and project specific requirements and constraints.
Supports different project types (single-site, multi-site, template, prototype, upgrade, evaluation, etc.)
Has been developed over many years to deliver cost-effective and successful implementation and is being continually enriched with content based on the experiences gained in implementing SAP Solutions
Please have a look at below links..
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/501c66ff-c31c-2a10-62ad-9588691d78ae
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30d4a91c-a9ac-2a10-57b3-84817be370b8
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50766901-7be7-2a10-1e99-d6723d46f696
https://service.sap.com/roadmaps
I hope this helps you..
Regards,
Ramki.

JRadioButton not getting the Focus Back

Hi,
I am having a problem with the RadioButtons. I have a panel and have three radio buttons belonging to a group. I have selected the third button and saved it to the database. When I came back to the panel, I have the third button selected.But the focus( Rectangle around the text) is on the first button. If I click on the third button then the focus came to the third button. I tried using requestFocus() but its not at all working. Some one please help me asap.
Example of Code...
if(selButton =1)
rb1.setSelected(true);
else if(selButton = 2)
rb2.setSelected(true);
else
rb3.setSelected(true);
TIA,
CK

Did you try:
if(selButton =1) {
rb1.setSelected(true);
rb1.requestFocuse();
} else if(selButton = 2) {
rb2.setSelected(true);
rb2.requestFocuse();
} else {
rb3.setSelected(true);
rb3.requestFocuse();
}Doesn't work ?

Firefox loses window focus when flash reloads

This is an old problem that has NOT been solved by Mozilla/Adobe. If you load a flash web page, do nothing involving flash for a few minutes, and then load a new flash page in a different FF window, application focus will get yanked to the OLD window (the one you haven't touched in minutes). This problem was documented here as far back as June 2012. But for some reason the thread was closed even though the issue has not been fixed.
This issue has nothing to do with extensions or outdated plugins, as I can replicate it with a fresh copy of FF on a brand new Win7 machine with no options changed on FF. Yes, I am using the very latest Flash plugin, which works fine with the exception of this persistent and annoying issue. The issue does not exist with Chrome, and therefore it should be a priority for Mozilla to work with Adobe to fix it ASAP.

Sorry, solutions to problems such as that don't come from this support forum. Bugzilla is the place to report Bugs like that. 
https://bugzilla.mozilla.org/ 
First search for an existing Bug, then if none is found file your own report providing as much information as you can about your issue.
https://developer.mozilla.org/en/Bug_writing_guidelines

Focus ASAP

Similar Messages

Maybe you are looking for