ARIS Integration With SAP Framework and Benefits

ARIS Integration with SAP Framework and Benefits

Applies to:

Any Industry which wants to define their business requirements in a process-oriented way.

For more information, visit the Business Process Modeling homepage.

Summary

This article focuses on the framework and benefits of ARIS Integration with SAP and the phases of Business Process Management (BPM) with ARIS Value Engineering approach (AVE). It shows how ARIS for SAP NetWeaver enables individual departments to define their business requirements in a process-oriented way. In addition to mapping business logic, these models can include other relevant business information, such as, data flows, roles and responsibilities, process interfaces, the underlying system landscape, and manual, system-independent activities. Using SAP Solution Manager Reference processes for business process modeling ensures a more accurate and effective integration between a company’s business requirements and the SAP solution portfolio.

The SAP content in these processes (transactions, CI templates, BC Sets, implementation guides, test cases, etc.) also delivers huge cost and time savings during the project. The end-to-end view of a company’s processes remains available in the corporate process architecture in ARIS for SAP NetWeaver throughout the project and after completion. This ensures that the company’s requirements are in line with corporate reality, the blueprint, and the corresponding implementation. The elements of these end-to-end processes that are significant for specific system configuration are synchronized with SAP Solution Manager. In the subsequent course of the project, the company can make full use of SAP Solution Manager content and tools, including adding process models to this content.

Author: Kasi Viswanath Duppanapudi

Company: Intelligroup Asia Pvt. Ltd.,

Created on: 29 October 2008

Author Bio

Kasi Viswanath Duppanapudi is working as a SCM-Manager with Intelligroup and has been part of SAP SCM competency since March 2002.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 1

https://www.sdn.sap.com/irj/sdn/nw-processmodeling


Table of Contents

Introduction .........................................................................................................................................................3 ARIS Value Engineering Approach ....................................................................................................................4 Strategy Phase ...................................................................................................................................................5 Design Phase .....................................................................................................................................................5 SAP Reference Processes .................................................................................................................................6 Creating New Scenarios in ARIS........................................................................................................................7 Transfer of Process Structures from ARIS to Solution Manager........................................................................7 Entering Services in ERP ...................................................................................................................................8 Steps to Transfer Process Structures from ARIS to Solution Manager..............................................................9 Completing the Blueprint in Solution Manager ...................................................................................................9 Deployment Phase ...........................................................................................................................................10 Conclusion ........................................................................................................................................................10 Related Content................................................................................................................................................11 Disclaimer and Liability Notice..........................................................................................................................12



Introduction ARIS Business Architect for NetWeaver is a full-blown modeling environment that supports business-level modeling and management as well as tight integration with the SAP NetWeaver platform. ARIS is integrated with the SAP Solution Manager as well as SAP Exchange Infrastructure which makes it a very useful and lucrative tool for your implementation and continuous improvement projects like upgrades etc. It provides the following functionalities and benefits:

• Synchronize ARIS with SAP Solution Manager Projects and the other way round i.e. from Solution Manager to ARIS.

• We can maintain the contents of company business processes in the ARIS databases and import the contents of ARIS databases into SAP Solution Manager.

• We can edit the company specific scenarios and graphic models as well as Solution manager Processes to meet company requisites.

• We can create extensive, yet customizable reports of our process repository.

• Displays the relationships between objects in a table.

• Administer ARIS databases (define user accounts and access; establish modeling standards via method filters.

This article also focuses on synchronization capabilities of data between SAP and ARIS systems. When you synchronize data via SAP Solution Manager, all documents that are maintained in the SAP Solution Manager project on the General documentation and Project documentation tabs are automatically transferred, updated or deleted. You can open these documents from within ARIS. The following discussion shows how these tools are used in an SAP project when utilizing the AVE for SAP approach.



ARIS Value Engineering Approach The ARIS Value Engineering approach developed by IDS Scheer AG for handling SAP implementation and upgrade projects (AVE for SAP) is a holistic, model-based framework that covers all key aspects of an ERP implementation (processes, systems, data, organization). AVE for SAP is not just a framework; rather it is a complete cycle that includes every phase of business process management, i.e., strategy, design, implementation, and monitoring. 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. The result is an exact definition of the content required in the individual phases of the project, the form in which it needs to be created, and of the tools that support each of the phases. This ensures a consistent approach and a process-oriented view. The procedure and specified work packages can also be adapted to suit individual customer situations and needs. Deployment of ARIS for SAP NetWeaver and SAP Solution Manager ensures that the required information is centrally documented, re-used where possible, and properly structured.

X Apps Legacy ERP

SAP NetWeaver Platform

ARIS for NetWeaver

Company Value Chain

Process Design & Analysis

Business Processes, components and objects

SAP XI

Integration Scenarios and processes

Solution Manager

Figure: ARIS Business Architect for NetWeaver

Since the documentation includes a description of how the requirements to be met by the company’s business processes are realized in terms of software, it also needs to be available to the customer after deployment as user documentation that is updated on an ongoing basis, making it a valuable information resource when making subsequent changes. Further in this article, we would try to explore more on the phases of business process management, i.e., strategy, design, implementation, and monitoring.



Strategy Phase Before commencing an implementation or upgrade project, it is important to define exactly which objectives the company intends to achieve by introducing an SAP system, based on its business, process, and IT strategy. The company’s market positioning plays a key role here, but consideration should also be given to possible scope for improvements in other areas. This involves understanding which processes underpin the company’s operations and assessing the importance of these processes. The existing business processes can be evaluated using qualitative and quantitative analysis. Based on the results, processes can be optimized, standardized, and redefined in accordance with business process transformation methods. This should initially take place independently of the planned SAP scenarios, thereby ensuring that the business processes in question remain the strategic focus of the deployment project and are not subordinated to the requirements of the new IT system. If the implementation of the SAP solution needs to follow specific standards, this is taken into account in the process design phase. During the strategy phase, the company can obtain information about the solutions available from SAP using the SAP Solution Composer. This tool presents the web-based software solution offered by SAP in the form of “solution maps” providing both industry-specific and product-focused views. It enables SAP customers to evaluate a desired business scenario without defining individual components or to create their own scenario. SAP customers can therefore identify the SAP view of the individual processes at an early stage and establish which SAP products are required to support the desired 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. The component-independent view provided by Solution Composer can simplify an organization’s choice of the right SAP solution. In addition to process documentation, Solution Composer makes other information available that supports SAP customers during deployment projects: detailed process descriptions, key performance indicators, and business objectives and goals. When an SAP customer has finished choosing the components, they can continue working with the relevant Solution Manager content (SAP reference processes).



SAP Reference Processes The reference processes provided by SAP are structured into three layers, comprising scenarios, processes, and process steps, which can be assembled from a component/product view and from an industry view. The reference content also includes the SAP-relevant system organization structures and master data elements. Additionally, the reference content is enriched with information needed to create blueprints (IMGs, documentation, CI templates, BC Sets). In our example, the company has chosen to implement the SAP scenario “Inventory Management” in the supply management process area. An overview model is used to evaluate how this scenario can best be integrated into the business process architecture of the company. The scenario, and the processes and process steps it contains, can now be imported into ARIS for SAP NetWeaver via the interface to SAP Solution Manager. There are several ways of using the SAP reference content in the project, depending on the scope required. Because SAP Solution Manager needs the relevant system landscape as the context, in many projects the environment is defined in SAP Solution Manager first and then the scenarios supported using the selected components are identified in SAP Solution Manager and loaded into ARIS for SAP NetWeaver as part of the project structure. Another option is to import the entire SAP Business Process Repository, comprising all the processes and process steps available from SAP. The SAP Business Process Repository is divided into process groups (e.g. Procurement, Production, Sales, etc.). These configuration-relevant processes and process steps can then be integrated into company-specific, self-defined business scenarios using input from the relevant departments. If there is no specific information available yet about the system landscape to be used, scenarios can be downloaded regardless of context and then used in a project. However, it should be noted that a specific system landscape must be defined at some point in the project in order to ensure that the relevant system release offers the necessary content. By way of the defined project structure, a link is then established between SAP Solution Manager and ARIS for SAP NetWeaver. In the blueprinting phase that follows, the company’s future processes are described. This involves adapting the SAP reference models to the company’s business process architecture, always remembering to work within the structural layers of Solution Manager (scenario, process, process step). To perform this task, the business process analyst needs to understand the company’s business processes (e.g., by studying process models) and to have the necessary knowledge of the SAP processes to be implemented. The result is a dedicated, process-oriented blueprint containing both the configuration requirements and the process documentation. Any additional business process-relevant information that may be required can also be added.



Creating New Scenarios in ARIS Since the scenarios provided by SAP do not always fully correspond to the workflows needed by a specific company or do not cover the entire scope of a project, ARIS for SAP NetWeaver provides companies with the functionality to create their own scenarios. To enable this, new objects can be modeled in ARIS, or partial processes or individual process steps from existing SAP reference content can be used. ARIS for SAP NetWeaver incorporates an assistant that supports the modeling of these self-defined scenarios. The assistant takes care of the attributes required for consistent data exchange with SAP Solution Manager and also creates models and group structures. This ensures that ARIS for SAP NetWeaver delivers SAP-compliant process designs.

Transfer of Process Structures from ARIS to Solution Manager When the blueprint has been created, the process structure can be transferred to SAP Solution Manager ready for the next stage. Both existing process structures used and any newly created process structures are transferred. If name changes have been made to existing structures, these are also migrated. Where objects from the SAP reference processes have been used, the relevant documents provided by SAP are automatically included in the project. We will see an example of a simple process structure of “Entering Services in ERP” transferred from ARIS to Solution Manager:



Entering Services in ERP 1. As and when the vendor performs the services, the designated user will create a service entry sheet with

reference to the purchase order. 2. Detail data, account assignment will be copied from purchase order to the service entry sheet. 3. Services rendered will be entered and accepted in the service entry sheet.

Upon acceptance of service entry sheet relevant G/L accounts will be updated.

ServicesPerformed

Create ServiceEntry Sheet with

reference toPurchase Order

RequestingDepartment

Services notmatching with

Purchase Order

Servicesmatching with

Purchase Order

Update ServiceEntry Sheet

Service EntrySheet Updated

Accept and PostService Entry Sheet

Service EntrySheet Accepted

and Posted

Invoice Processing


Purchase OrderProcessing



Check & matchServices

performed withPurchase Order

Figure: Process structure of “Entering Services in ERP”



Steps to Transfer Process Structures from ARIS to Solution Manager 1. Start the ARIS Business Architect for SAP NetWeaver. Open the ARIS explorer and double click on

a project and navigate to the process models.

2. Select any process for making changes and additions. Save the changes to the model. Now we can synchronize/transfer this to the SAP Solution Manager.

3. Select the Process Model and right click and select SAP→Synchronization. Or if it is a new scenario to be transferred to Solution Manager then select SAP→Transfer Scenarios.

4. In the subsequent pop-up, select “Data Transfer from ARIS to Solution Manager”. Select the direction of the data flow i.e. ARIS to SAP and check “Consider Subordinate Items”.

Completing the Blueprint in Solution Manager Now that the structures have been created, available transactions can be added to the structure elements or removed from the focus of the project. In the case of new process structures created to meet a company-specific need, existing SAP standard transactions from the reference content can be used or new transactions can be defined using ARIS for SAP NetWeaver. After completing the blueprint in SAP Solution Manager, it needs to be synchronized with ARIS for SAP NetWeaver ready for the next stage of the project. This is an important step, allowing the business view to be aligned with the configuration view and the project documentation to be updated. Synchronization is required at intervals as the project progresses, in both directions, and it is important to be aware of which of the two systems is the lead system at any given time. The business description of the processes in ARIS is used as the basis for the process architecture, with the detailed information needed for configuration being added in SAP Solution Manager. Changes to the process architecture arising in the individual company departments during the course of the project are initiated via ARIS by modifying the business processes. The transactions involved and the associated documentation can be viewed in ARIS (Function Allocation Diagram). The business processes defined by departments across the company are then published using ARIS Business Publisher. The published models allow users to navigate directly into the process structure in SAP Solution Manager. This process structure is particularly important for defining test cases, with the different options in the ARIS process models being used to determine the end-to-end company scenario where the individual process steps and transactions are used. Finally, the published business process models can be added to the project structure in SAP Solution Manager.



Deployment Phase SAP Solution Manager plays the lead role during the deployment phase. To enable configuration of the individual processes, the user can navigate from a structure element in ARIS for SAP NetWeaver to the SAP Solution Manager Configuration view. Test scenarios can now also be created in SAP 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 need to be trained on how to handle transactions in the context of the business processes. To simplify user training, the ARIS models are utilized, providing a convenient overview of the process and a better understanding of individual roles in the process.

The ability to call transactions from within ARIS for SAP NetWeaver provides valuable support here. The ARIS model can be used to help define a training strategy based on the modeled roles and responsibilities. Similarly, ARIS allows centralized access to the project documents transferred during synchronization. In this way, the ARIS models that are eventually published can contain the centralized user documentation and give users better support, together with the process models. Documents from various sources are made available directly by the published ARIS models. ARIS for SAP NetWeaver also makes it possible to incorporate information from the ARIS database into the SAP Help.

Conclusion The transparent, business-oriented view of the processes in ARIS for SAP NetWeaver makes communication between the individual departments and the project team easier, facilitating the ongoing involvement of end users in the SAP Upgrade or implementation phase. After completion of the project, the processes continue to be an important source of information and can be used for other application scenarios (e.g., enterprise architecture, process performance management, compliance management, etc.), as well as for supporting users. The business process knowledge documented in ARIS for SAP NetWeaver is also a vital resource for companies wishing to create and introduce an enterprise SOA of the kind that SAP intends to adopt in the coming years. For the first time, customers will have the ability to connect the modeling and optimization of business processes with the physical configuration and execution of these processes.



Related Content www.ids-scheer.com

www.bitpipe.com

www.changeware.net

www.sap.com

For more information, visit the Business Process Modeling homepage.


www.ids-scheer.com

www.bitpipe.com

www.changeware.net

www.sap.com

https://www.sdn.sap.com/irj/sdn/nw-processmodeling



Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.