Beruflich Dokumente
Kultur Dokumente
The SAP Solution Manager is the central application management platform that customers can run in their solution landscape to help them efficiently implement, operate, monitor, and support their SAP solutions. SAP Solution Manager is thus used for both Implementation and Operational Functions. The SAP Solution Manager provides tools, content, and a gateway to SAP that helps to: Optimize the management of your SAP solution Ensure reliability of your SAP solution Ensure efficient operations Ease implementation and upgrades Continuously adapt and improve your solution
helping to reduce the time for support, notes access, and so on.
Minimize risk during implementation Avoid inconsistencies Resolve issues quickly resulting in less down time More efficient implementation and change management projects Reduced cost of implementation and continuous improvement Reduce cost of process design technical setup, business setup, support and operations, testing, and knowledge transfer Centralized project handling blueprinting, configuration, and testing Reduces the costs of upgrades or continuous improvement projects.
Reduced cost of operation Provides central point of control for multi-component environments. Facilitates technical and application integration. More leverage from IT investments Integrates with IT landscapes that include both SAP and non-SAP Applications
To learn more about the each roadmap, move your pointer over the name of the item you want to learn more about. ASAP roadmaps outline the activities involved in implementing, upgrading, or enhancing SAP solutions. These roadmaps are enriched with set of deliverables, accelerators, role descriptions, and additional guides. The five standard roadmaps are listed below. To learn more about the functions of each, move your pointer over the name of the item you want to learn more about. Implementation Roadmap Solution Management Roadmap Global Template Roadmap Upgrade Roadmap Other Roadmaps
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.
The ASAP Implementation Roadmap provides a work breakdown structure that can be used to plan and track the underlying activities and tasks of the implementation; however, it is not meant to be characterized as a project management tool. In fact, there are links to Microsoft Project from the roadmap, allowing a project manager to download the entire structure into an MS Project plan. Each phase of the roadmap provides a list of list of general project management activities, such as project team status,
scope management,training plan management and so on
This screen describes the various elements of the Implementation Roadmap. These elements are the roadmap structure, the viewing area and the attachment area. As the graphic illustrates, the Roadmap Structure is located on the left-hand side of the screen and gives the project a list of items that outlines what to do and when to do it. The viewing/text area, on the upper right side of the screen, displays procedural guides, prerequisite information, and deliverables of the highlighted structure items. Finally, the attachments area on the lower right-side of the screen displays various items, such as accelarators, issues, supplemental documentation, and project team members responsible for the tasks listed in the roadmap structure. The main elements of the Implementation Roadmap are: Roadmap structure Viewing/text area Attachments area The roadmap structure gives the project team a list of what to do and when to do it. This appears on the leftside of the screen displayed. The roadmap structure can be filtered by roles so that each team member can focus only on those items requiring their attention. The viewing/text area, on the upper right-side of the screen, displays procedural guides, prerequisite information, and deliverables of the highlighted structure items on the leftside of the screen. The attachments area on the lower right-side of the screen displays various items, such as accelerators, issues, and supplemental documentation. In this area you can also carry-out various tasks, such as assigning project team members and tracking the status of the highlighted item in the roadmap structure.
establish the structure is found in the Business Process Repository. The business structure displayed on this screen is based on Business Scenarios. The business scenarios are defined first. Then, supporting business process groups are chosen from the Business Process Repository, based on those scenarios. On the right side of the screen, associated items are available to support the line-items in the structure on the left. Additional features, such as project documentation, transaction assignments and graphical flow of processes are also available. Once the blueprint structure is finalized, the blueprint document can be generated and becomes the master plan for the realization phase of the project. The Business Blueprint structure is displayed on the left side of the screen. This structure is developed through the business process workshops; all requirements gathered are recorded and associated with a structure item. The content used to establish the structure is found in the Business Process Repository (BPR). The business structure displayed on this screen is based on a business scenario. The business scenarios are first defined, and then supporting business process groups are chosen from the BPR based on those scenarios. These decisions are based upon the activities outlined in the Business Blueprint phase of the Implementation Roadmap, where workshops are organized with the purpose of defining the business process needs of the project. On the right side of the screen, associated items are available to support the line items in the structure on the left. Additional features such as project documentation, transaction assignments, and graphical flow of processes are also available. Once the blueprint structure is finalized, the blueprint document can be
generated and becomes the "master plan" for the realization phase of the project.
Functions of Configuration
Using the blueprint document generated in the Business Blueprint phase, the project team will go into the Configuration transaction in the SAP Solution Manager to customize the attached development system. Customization is the configuration of the Implementation Guide (IMG) objects in the target system. The blueprint structure is replicated in the configuration screen. The associated items on the right side of the screen provide a place for documentation, administration, tracking, IMG objects to be configured, test cases, and team members assigned.
interfaces to third-party testing tools. The figure depicts the integration of the testing tools provided by the SAP Solution Manager.
Solution Monitoring
Audio Transcript The increasing number of IT solutions is a growing challenge for the administration team in a computer center. As a result, computer center managers demand a monitoring method that is centralized (with all information in one tool), yet can be extended to cover new components. Instead of classic system monitoring of individual system components, we now talk about solution monitoring, where entire business processes can be monitored across multiple components. This concept is realized through the following three monitoring sections within the SAP Solution Manager: Business Process Monitoring, Central System Monitoring, and Service Level Management. The continually increasing number of IT solutions and components is a growing challenge for the administration team in a computer center. The number of components has increased from what was required with SAP R/3 (including SAP
instances, database, hardware, and operating system) to include an ever-growing range of technologies. As a result of this development, computer center managers demand a monitoring method that is centralized (with all information in one tool), yet can be extended to cover new components. Instead of classic system monitoring of individual system components, we now talk about Solution Monitoring, where entire business processes can be monitored as a whole across multiple components. This concept is realized through the following three monitoring sections within the SAP Solution Manager: 1. Business Process Monitoring 2. System Monitoring: Central System 3. Service Level Management
Monitoring Recommendations
Use Service Level Management in the SAP Solution Manager to lay the foundation for setting up the correct procedures for monitoring of your SAP solution. The recommended technique is to define an explicit monitoring concept for central system monitoring using the Computing Center Management System (CCMS) in conjunction with the SAP Solution Manager. This form of system monitoring, that starts with monitoring all business-process-relevant system components, is known as the inside-out approach. The complementary outside-in approach involves using tools from third-party manufacturers. To achieve comprehensive monitoring, SAP recommends using both approaches simultaneously.
a Message handling process a Customer solution database SAP Notes Management Solution Manager Diagnostics Now that we have talked about some of the features of solution monitoring, we will look at another component of the SAP Solution Manager: Service Desk. The service desk offers a complete infrastructure for organizing and operating a solution-wide support organization at your site. Features include: Message handling process Customer solution database Managing SAP Notes Solution Manager diagnostics
Message Handling Process:- End user can create messages that automatically collect systems and context data. An interface for third-party messaging tool is also included. Customer solution database:- Allows customer to build a history data base for future troubleshooting. Managing SAP Notes:- Integrated notes search from the SAP service market place, as well as the ability to implement the notes via the SAP Notes Assistant. Solution Manager Diagnostics:- Provides all functionality to centrally analyze and moniter a complete SAP.
End-to-End Root Cause Analysis and Solution Monitoring with SAP Solution Manager
and efficiency. Solution Manager diagnostics provides all functionality to centrally analyze and monitor a complete SAP solution. It also reduces the time needed to train a support consultant in root cause analysis.