ASAP roadmaps outline the activities involved in implementing, upgrading, or enhancing SAP solutions.

Each roadmap has a set of deliverables, accelerators, role descriptions and additional guides. The five standard roadmaps are listed on this screen. The Implementation Roadmap for SAP Solutions provide the methodological framework for the project team during the implementation of an SAP solution. The Solution Management Roadmap provides a methodology for the implementation of the technical infrastructure and its operation. The Global Template Roadmap describes how to organize and run a project where a corporate template is developed. The Upgrade Roadmap is designed to help you carry out the customizing activities required for an upgrade. There are also other roadmaps, such as the Enterprise Portal and Exchange Infrastructure roadmaps, but we do not go into detail on these here..

The implementation roadmap consists of five phases. The first phase is Project Preparation. This is the initial planning for the customers' SAP project. The activities include general project management requirements, an issues management plan, an organizational change management plan, and the establishment of other policies and procedures for running the project. This phase must be completed before the next phase begins. The next phase, the business blueprint phase, comprises activities for aligning the customers business and technical requirements to the SAP standard software. Just as a blueprint of a house is a plan by which an architect conveys the building requirements to the contractor, so the business blueprint in ASAP becomes the plan for the eventual configuration of a customers SAP software solution. This phase concludes with the approval of a business blueprint document. The realization phase comprises the building and testing of the solution as prescribed by the business blueprint document. Activities in this phase include customizing in the Implementation Guide of the associated development systems. The realization phase also includes software enhancements, special progamming, building and executing test plans, and finally, signing-off the configured system. During the final preparation phase many crucial tasks remain, such as acceptance testing of the production system hardware, the completion of end-user training, and plans for transfer to the production system. The final phase is Go Live and Support. During this phase, items such as service level agreements and help-desk procedures are established and tested. The conclusion of this phase is the hand-over to the operations and monitoring staff.

 Let's walk through the test workflow outlined on this screen. First, a project structure is created and test cases are collected. In the second step, the collected test cases are assigned to different test packages in the project structure. Then, the test packages are given to the assigned testers the project. The test packages are executed and then the test results are analyzed. The benefits of this systems are: Fast test preparation and execution A single point of access to the complete system landscape Central storage of testing material and test results and Re-use of existing testing material