ARIS Solution Scenario: SAP Implementation
SAP Implementation
How can the gap between business requirements, business process design, and SAP implementation be closed? How can organizations ensure that the blueprint truly corresponds to the current installation and that business processes are optimized and standardized before the next implementation project?
When implementing the SAP solution, the reference content provided by SAP can be used for process definition in ARIS for SAP NetWeaver. Based on the business process scenarios defined there, it is then possible to transfer configuration-relevant requirements to SAP Solution Manager. Key to successful completion of this type of project is that all the deployed tools and procedures complement each other properly.
The ARIS Value Engineering (AVE) for SAP methodology adds value here by guiding the customer through each phase of the project, leveraging the functionalities of ARIS for SAP NetWeaver and SAP Solution Manager to maximum effect.
Key Benefits
- Use of SAP reference content in ARIS
- Transfer of configuration-relevant requirements to SAP Solution Manager
- Helps non-expert users to define commercial requirements in a process-oriented way
- Optimization and standardization of business processes before the next upgrade or implementation project
- ARIS for SAP NetWeaver connects the process and SAP worlds
Scenario Overview
The SAP Implementation Scenario is a holistic, model-based approach that encompasses all key aspects of an implementation project, such as, processes, systems, data, and organization. The SAP solution is implemented in ARIS for SAP NetWeaver using the SAP reference processes. After relevant process areas have been analyzed, the detailed processes are synchronized with SAP Solution Manager. The AVE for SAP methodology ensures that user requirements are correctly mapped in the SAP environment and any non-standard features are identified.
ARIS Value Engineering covers every phase of the Business Process Management lifecycle: strategy, design, implementation, and controlling. Standardized work packages and products are defined for each phase. These build on each other and are created in ARIS for SAP NetWeaver and SAP Solution Manager.
Strategy Phase
Before commencing an SAP deployment project, it is important to define the exact objectives, based on the organization’s business, process, and IT strategy. During the strategy phase, the company can then obtain information about the relevant solutions available from SAP. The ability to evaluate a desired business scenario without defining individual components, or to create custom scenarios, enables an early insight into the way SAP sees the individual processes and which SAP products are needed in order to support the planned scenario.
Design Phase
In the design phase, strategic requirements are turned into specific business process models. This involves using the ARIS for SAP NetWeaver interface to access the SAP reference processes contained in Solution Composer and SAP Solution Manager. When an SAP customer has finished choosing the components, they can continue working with the relevant Solution Manager content (SAP reference processes) and create a blueprint.
Implementation Phase
SAP Solution Manager plays the lead role during the deployment phase. To enable configuration of the individual processes, the user can go straight from a structure element in ARIS to the SAP Solution Manager configuration view. Test scenarios can now also be created in Solution Manager based on the end-to-end scenarios defined in ARIS. In a later phase of the project, the intended users of the SAP system will be trained on how to handle transactions in the context of the business processes.
Controlling Phase
Implementation is followed by the controlling phase, in which business, system, and organizational performance can be monitored. A cost/benefit calculation is conducted at the same time to allow any necessary corrective action to be taken.
Back
