Cross-Organisational Business Processes - Enabling Technologies and Tools

1. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

2. Course Structure • Recall of Concepts + Scenario Introduction • ATHENA CBP Modelling Tool Maestro • ATHENA CBP Enactment Tool Nehemiah

3. Recall of Concepts + Scenario Introduction

4. View Process Approach The view processes are then linked up in cross-organizational business processes modelling the cooperation between partners. One view process can be used in different cross-organizational business processes. One cross-organizational business process links the view processes from two or more partners. View processes provide an abstraction of the private processes that allows hiding internal data that must not be revealed by default. The information contained in the view processes must be sufficient to coordinate internal actions with activities of external trading partners. As shown in organization B different view processes can be created as abstractions from the same private processes allowing the partners to keep their internal processes static while being able to interact with different partners in different contexts. CBP: Cross-OrganizationalBusiness Processes VP: View Processes PP: Private Processes AS: Applications and Services CBP1 CBP2 CBP3 Organization A Organization B Organization C VP1 VP2 VP3 VP4 VP5 VP6 PP1 PP2 PP4 PP5 PP3 AS AS AS The process view approach provides a systematic way to selectively expose internal information and interweave process steps to cross-organizational business processes. View processes are introduced as an additional layer above the private processes of an organisation.

5. 3-Level Modeling Approach • Business level: • business view on cooperation • processes are not executed • Technical level: • specifies complete control and message flow • platform independent • Execution level: • executable business processes • platform specific

6. ATHENA CBP Approach

7. View Processes Repository (VPs) CBP Repository (CBPs) Enactment Architecture: Big Picture Contain all building blocks which are encapsulated inside the company and which are not accessible by partners. For instance, these are all components that are linked to the modelling and execution of private processes or to the invocation of internal applications Company Internal Components CBP Components Interface Components CBP and View Modeling Tool CBP Monitoring and Analysis Enactment Engine View Processes Event and Document Correlation Represent the information that is published by the companies in order to take part in CBPs, for instance view processes of the partners’ private processes. Represent the information that has to be shared between partners in order to define and execute CBPs. They can also contain information that is necessary to monitor and analyze the CBP execution if this is required in a particular business scenario.

8. Architecture Alternatives Cross-Organizational Business Processes View Process Engine View Process Engine View Process and Private Process Implemented in one Engine Private Business Process Engine Application Components with Embedded Private Business Processes Business Services Application Components Application Components Database Database Database

9. Integrated Repository (PP, VP) ATHENA View Process Engine The ATHENA View process engine can be used in a mediated as well as in a peer-2-peer physical architecture. In a peer-to-peer distribution, each partner would run an ATHENA view process engine and the engines would communicate with each other as shown above. If a mediator is needed the engines would not communicate directly but through the mediator. The mediator would forward the messages and status updates between the partners. If total anonymity is needed and the partners should not be informed about the status of the other partners, this information can be suppressed by the mediator. Company Internal Components Partner Interface Components Interface Components Private Process Modeling Tool Enactment Engine View Processes Event and Document Correlation Internal Applications / Business Services This engine executes private processes and view processes and invokes internal applications directly. It is provided as a complete tool that has to be set up and customized to link it appropriately with the existing applications.

10. R1: Request for Quotation R2: Quotation M1: Request for Quotation R3: Order M2: Quotation M3: Order M4: Order Confirmation R4: Order Confirmation Interior Decoration Project RETAILER SUPPLIER MANUFACTURER Furniture eProcurement • 4 Participants: • Retailer • Manufacturer Sales • Manufacturer Procurement • Supplier • 2 Sub processes: • Selling Process • Procurement Process

11. Selling Process MANUFACTURER R1. Request for Quotation R2. Quotation R3. Order R4. Order Confirmation Delivery R5. Delivery Note RETAILER

12. ATHENA CBP Modelling Tool Maestro

13. Maestro ATHENA CBP Approach Maestro is a Business Process Modeling Tool on a technical level, that allows for modeling of private processes, view processes, CBPs and their links. Processes modeled can be exported into Nehemiah and run in this business process engine. You will learn how to use Maestro in the Maestro_Basic SAP Tutor session. Maestro offers functionality to manage business partners. Partners can be added and changed in Maestro and are directly updated in the Nehemiah repository. You will learn how to use Partnermanagement in the Maestro_Partnermanagement SAP Tutor session.

14. Modelling Processes in Maestro • Model private process • Generate a view process from the private process • Combine task of private process to view tasks • Take the view process of the partner and create a CBP from the view processes of the two partners • link up the tasks in the appropriate sequence • Create the messaging task in the CBP (automated) • Propagate the messaging tasks to the viewprocesses of the partners

15. Modelling Elements • The rectangle represents an activity. • Insert Activity • In order to insert an activity into a business process, drag it from modelling element area into the drawing area (business process). Note, the left mouse button has to be pressed. • Name Activity • Each activity needs to be marked with a unique name. A name can be entered by double clicking on the rectangle symbol. • Begin – End Constellation • Each business process has to start with a Begin coordinator and to stop with the End coordinator. Thus the Begin and End coordinator enclose the actual private process. • Fork – Sync. Constellation: • Fork initiates a parallel split of a process. A parallel process has to be finished with the coordinator Sync. • The oval is a notation for coordinators. • Insert Coordinator • Inserting works the same way as for activities. • Choose Operator • Maestro offers several types of coordinators; the most popular are Begin, End, Choice, Merge, Fork, Synchronize (Sync). Just double click on the coordinator and a drop down menu allows appropriate selection. • Choice – Merge Constellation • The Choice coordinator initiates a decision within the process. In order to consolidate the choice process again, the Merge coordinator has to be inserted. • Loop - Constellation: • A Loop is modelled by using the Merge – Choice Operator. Edges connect activities and coordinators with each other. You can draw edges by activating the drawing mode toggle edge icon. After creation of edges deactivate the toggle edge icon to return to the regular modus.

16. Export into Nehemiah Runtime -> Save Choose processes and press save.

17. Maestro Tool Training with SAP Tutor: • Modeling of Private Processes, Views and CBPs (sap tutor Maestro_Basic) • Partner Management in Maestro (sap tutor Maestro_Partnermanagement)

18. ATHENA CBP Enactment Tool Nehemiah

19. Architecture Alternatives Nehemiah is a Business Process Management Engine, that executes CBPs in a distributed environment and supports the process view approach. Nehemiah provides a Web front end for controling and monitoring CBP execution. You will learn how to use Nehemiah in the Nehemiah SAP Tutor session. Cross-Organizational Business Processes View Process Engine View Process Engine View Process and Private Process Implemented in one Engine Nehemiah Private Business Process Engine Application Components with Embedded Private Business Processes Business Services Application Components Application Components Database Database Database

20. Nehemiah Options Standard: Executes private, internal processes. Standard BPM Engine functionality. CBP (by process):Simulate the whole business scenario with all partners which are involved in the process. CBP (by partner role):Offers one partner the possibility to maintain his own processes rather than give access to every role involved in the scenario.

21. Nehemiah Process Status The activity is not available for execution, i.e. the control flow has not yet reached the activity or it has been skipped. The activity has been running and has been temporarily suspended. It will be resumed later. The activity has been terminated by a user. That means it is terminated immediately together with the process instance. The activity has been finished successfully. The activity is available for execution, but has not been started yet. The activity has been aborted by a user. That means it is stopped when possible after a user has aborted the process instance. The activity is running.

22. Nehemiah Process Execution You can start a CBP by clicking the Start Button. This part of the screen contains the CBP Model. This part of the screen shows the view process that has been derived from the private process and is part of the CBP. Here you see the executed private process. This part is always visible. With these buttons you have the option to view and hide the view diagram and the CBP diagram.

23. Private Steps and View Steps The red edge around the activities shows which private activities belong to which view activity.

24. Nehemiah Tool Training • Execution of CBP in distributed environment (SAP Tutor Nehemiah)

25. Exercise