SAP guided workflow in IBM BPM

© 2015 Copyright IBM Corporation
Lab BTA-1301
Exploring SAP Guided Workflow Feature of IBM
Business Process Manager
Author: Paul Pacholski, IBM Smarter Process
February 2015
Copyright IBM Corporation
1301
Business Process Manager
Smarter Process for SAP Lead Designer
Copyright IBM Corporation Page 2 of 52

© 2015 Copyright IBM Corporation Page 3 of 52
Notices and Disclaimers
Copyright © 2015 by International Business Machines Corporation (IBM). No part of this document may be reproduced or transmitted in any
form without written permission from IBM.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM.
Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for
accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to
update this information. THIS document is distributed "AS IS" without any warranty, either express or implied. In no event shall IBM be liable for
any damage arising from the use of this information, including but not limited to, loss of data, business interruption, loss of profit or loss of
opportunity. IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided.
Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice.
Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as
illustrations of how those customers have used IBM products and the results they may have achieved. Actual performance, cost, savings or
other results in other operating environments may vary.
References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or
services available in all countries in which IBM operates or does business.
Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the
views of IBM. All materials and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal
or other guidance or advice to any individual participant or their specific situation.
It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the
identification and interpretation of any relevant laws and regulatory requirements that may affect the customer’s business and any actions the
customer may need to take to comply with such laws. IBM does not provide legal advice or represent or warrant that its services or products will
ensure that the customer is in compliance with any law.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly
available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance,
compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products. IBM does not warrant the quality of any third-party products, or the ability of any such third-party products to
interoperate with IBM’s products. IBM expressly disclaims all warranties, expressed or implied, including but not limited to, the implied
warranties of merchantability and fitness for a particular purpose.
The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents, copyrights,
trademarks or other intellectual property right.
• IBM, the IBM logo, ibm.com, Bluemix, Blueworks Live, CICS, Clearcase, DOORS®, Enterprise Document Management System™,
Global Business Services ®, Global Technology Services ®, Information on Demand, ILOG, Maximo®, MQIntegrator®, MQSeries®,
Netcool®, OMEGAMON, OpenPower, PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®, PureData®,
PureExperience®, PureFlex®, pureQuery®, pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, SoDA, SPSS, StoredIQ,
Tivoli®, Trusteer®, urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and System z® Z/OS, are trademarks of
International Business Machines Corporation, registered in many jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark
information" at: www.ibm.com/legal/copytrade.shtml.

Contents
EXPLORING SAP GUIDED WORKFLOW FEATURE OF IBM BUSINESS PROCESS MANAGER............................................. 2
CONTENTS 5
LAB INTRODUCTION..................................................................................................................................................................... 6
1.1 ABSTRACT .............................................................................................................................................. 6
1.2 LAB INTRODUCTION.................................................................................................................................. 6
1.3 LAB OVERVIEW........................................................................................................................................ 7
SETUP 8
1.1 START PROCESS SERVER ........................................................................................................................ 8
1.2 START INTEGRATION DESIGNER ................................................................................................................ 8
1.3 START PROCESS DESIGNER ..................................................................................................................... 8
IMPORT A PROCESS FROM SAP SOLUTION MANAGER TO IBM BPM PROCESS DESIGNER ............................................. 9
1.1 IMPORT THE CREATE SALES ORDER PROCESS ........................................................................................... 9
EXAMINE THE GENERATED BPM GUIDED WORKFLOW ........................................................................................................ 12
1.1 EXAMINE THE IMPORTED PROCESS.......................................................................................................... 12
1.2 SAP GUIDED WORKFLOW TOOLKIT ......................................................................................................... 14
CONFIGURE SAP SERVER FOR EXECUTION OF SAP GUIDED WORKFLOW....................................................................... 16
1.1 EXAMINE HOW PROCESS STEPS ARE ASSOCIATED WITH SAP SERVERS...................................................... 16
1.2 CONFIGURE SAP SERVERS .................................................................................................................... 16
1.3 START CREATE ORDER PROCESS INSTANCE ............................................................................................ 17
ENABLE BIDIRECTIONAL VARIABLE SUPPORT BETWEEN SAP SCREENS AND BPM PROCESS.................................... 21
1.1 INITIALIZE SAP SCREEN DATA FROM BPM VARIABLES – VA01 TRANSACTION............................................. 21
1.2 MAP PROCESS VARIABLES – VA01 TRANSACTION .................................................................................... 25
1.3 INITIALIZE SAP SCREEN DATA FROM BPM VARIABLES – VA03 TRANSACTION............................................. 25
1.4 MAP PROCESS VARIABLES – VA03 TRANSACTION .................................................................................... 27
1.5 START A PROCESS INSTANCE TO TEST OUR CODE .................................................................................... 28
EXAMINE THE COMPLETE SOLUTION...................................................................................................................................... 32
1.1 OPEN PROCESS APPLICATION CONTAINING A FULL SOLUTION.................................................................... 32
1.2 EXAMINE THE ADDITIONAL ENHANCEMENTS.............................................................................................. 32
1.3 EXAMINE 4 (SAP SYSTEM QUERY SERVICE) IN PROCESS DESIGNER.......................................................... 33
1.4 EXAMINE 4 (SAP SYSTEM QUERY SERVICE) IN INTEGRATION DESIGNER..................................................... 34
1.5 TEST THE SAP SYSTEM QUERY SERVICE ................................................................................................ 36
1.6 EXAMINE 5 (ILOG DECISION SERVICE).................................................................................................... 37
TEST THE FULL SOLUTION IN PROCESS PORTAL ................................................................................................................. 39
1.1 START THE PROCESS AND PROVIDE INITIAL SALES ORDER INFORMATION [WENDY] ...................................... 39
1.2 REVIEW SALES ORDER INFORMATION [PAUL] ........................................................................................... 41
1.3 CHANGE SALES ORDER [WENDY]............................................................................................................ 43
1.4 REVIEW SALES ORDER INFORMATION [PAUL] ........................................................................................... 43
1.5 CREATE OUTBOUND DELIVERY [ALLEN] ................................................................................................... 45
EXAMINE HISTORICAL PROCESS PERFORMANCE DATA FOR PROCESS IMPROVEMENT............................................... 47
1.1 SET UP PROCESS OPTIMIZER.................................................................................................................. 47
1.2 WAIT TIME VIEW.................................................................................................................................... 48
1.3 PROCESS PATH VIEW ............................................................................................................................ 49
1.4 REWORK VIEW ...................................................................................................................................... 51
SUMMARY 53

Lab Introduction
1.1 Abstract
IBM BPM is one of the key enablers to help deliver on IBM’s vision for Active Business Performance
Optimization for business applications. IBM BPM enhances the user experience and productivity for the
native SAP interface by providing powerful process context and collaboration capabilities, while
delivering automatically generated process orchestration to deliver the process optimization offered by
IBM BPM.
1.2 Lab Introduction
IBM BPM provides bidirectional exchange Business Process Hierarchy (BPH) information in SAP
Solution Manager with IBM BPM Process Center. From a SAP BPH imported it is possible to
automatically generate a process orchestration that uses the native SAP HTML Graphical User Interface
(SAP Web GUI). This innovative new IBM BPM capability opens up the world of process orchestration
with only minimal IT intervention. These IBM BPM capabilities, with minimal business investment, can
improve the visibility, flexibility, agility and control of your SAP processes.
In this lab you will learn how a fictitious company Global Communications Inc. automated their SAP
Sales Order Process.
The as-is Sales Process is defined in SAP Solution Manger.h
It is not automated. Each step in the process is executed by manually and there with no orchestration.
The onus is on the business user to know when and what process s step to execute next. The rules that
determine the next step in the process are not formalized. Each process instance may be executed
differently according to the implicit rules known only to the process “experts”. Finally, there is no visibility
into current or completed process instances. As a result the management is unable to ensure operational
execution efficiencies and learn from the past to improve the process. One of the key requirements for
the to-be automated process is that the users should not fundamentally change the way they interact
with the process to avoid costly re-training.

Let’s join the development team at Global Communmications Inc to now emabrk on BPM jurney to buld
the to-be version of the Sales Order Process.
1.3 Lab Overview
The high level steps in this lab are as follows:
1. Import a process from SAP Solution Manager to IBM BPM Process Designer
2. Examine the generated BPM Guided Workflow process
3. Configure SAP Server for execution of SAP Guided Workflow
4. Enable bidirectional variable support between SAP screens and BPM process
5. Examine the SAP BAPI integration service implementation
6. Test the full solution in Process Portal
7. Examine Historical Process Performance Data for Process Improvement

Setup
1.1 Start Process Server
__1. Ensure DB2 has started before you go to the next step. Wait until the red square on the DB2 green
icon disappears.
__2. Locate SERVERS folder on the desktop. Then double click ERVERS > Start PC Server
__3. Wait for the DOS Command window to close before proceeding to the next step.
1.2 Start Integration Designer
__1. From the desktop double-click TOOLS > IBM Integration Designer 8.5
__2. On Secure Storage window enter Password of admin and click OK.
__3. Minimize Integration Designer. You will be using in the last part of this lab.
1.3 Start Process Designer
__1. Switch back to the TOOLS. Then double-click TOOLS > IBM Process Designer 8.5
__2. Login using admin/admin
__3. On Security Alert window click Yes
__4. On the second Security Alert window click Yes

Import a Process from SAP Solution Manager to IBM BPM Process
Designer
In this part of the lab you will use the SAP Solution Manage import feature of IBM Process Designer. You
will connect to SAP Solution Manager and import Create Sales Order process from a BHP defined in
SAP Solution Manager.
1.1 Import the Create Sales Order Process
__1. In Process Designer click Import Process App
__2. Select SAP Solution Manager and click OK
__3. Note that the login credentials were already set for you. Click the Change the location to see what
they are

__4. Examine the login information and click Next to continue.
__5. Select PROCESSES project and click Next

© 2015 Copyright IBM Corporation Page 11 of
52
__6. Select Sales Order Process, select Generate a Guided Workflow and click Import
__7. On the Summary of the import results pane click OK

Examine the Generated BPM Guided Workflow
In this section, you’ll examine how from a static picture in Solution Manager the import action created a
ready to execute BPM process.
1.1 Examine the Imported Process
Let’s examine and compare the Sales Order Process defined in SAP Solution Manager with the one
created via import in IBM Process Designer.
__1. Click Open in Designer to open the PROCESSES Process App you have just imported.
__2. Click Processes, then double-click Sales Order Process

52
__3. Compare the Sales Order Process representation in IBM Process Designer and SAP Solution
Manager by inspecting and comparing Figure 1 and Figure 2 below
Figure 1. Create Sales Order Process in IBM Process Designer
Figure 2. Create Sales Order Process in SAP Solution Manager
__4. Click Create Sales Order (first activity in the process).
__5. Click Properties tab then click Custom tab

__6. Compare the Transaction properties representation in IBM Process Designer and SAP Solution
Manager by inspecting and comparing Figure 3 and Figure 4 below. Specifically, note that the
SAP transaction code (VA01) was transferred to the Custom tab!
Figure 3. SAP Transaction Information in IBM Process Designer
Figure 4. Transaction Information in SAP Solution Manager
The SAP Guided Workflow features uses the transaction code stored the Object column to dynamically
build SAP Web GUI screen.
1.2 SAP Guided Workflow Toolkit
This is a new toolkit introduced on IBM BPM 8.5.0.1. This toolkit contains all the artifacts required to
automated SAP processes.
__1. Notice the SAP Guided Workflow (8.5.0.1) toolkit
Because, during the import from SAP Solution Manager you selected Generate a Guided Workflow
checkbox, the SAP Guided Workflow toolkit was added for you.

52
__2. Expand the Guided Workflow Toolkit > User Interface and notice the Default SAP Transaction
Human Service.
This Human Service does all the work of converting SAP transaction code (i.e. VA01) to a runnable SAP
Web GUI user interface.
__3. Ensure Create Sales Order task is still selected and then click Properties > Implementation
Notice that the the Default SAP Transaction Human Service is the implementation of the Create Sales
Order task. In fact all the task in this process are implemented using the Human Service.

Configure SAP Server for Execution of SAP Guided Workflow
1.1 Examine how Process Steps are Associated with SAP Servers
__1. Click Properties > Custom tab
Notice the Logical Component. It was defined in Sap Solution Manager. Each SAP Logical Component is
associated wih a SAP Server. In fact each SAP task can be executed on a diffeent SAP server!
1.2 Configure SAP Servers
__1. Select Process App Settings
__2. Click Servers tab, then click SAP-ECC (SAP ECC) server and notice the SAP_ECC server
associated with the SAP ECC Logical Component.

52
__3. Configure the SAP Server SAP location as shown in the table below
Location vm142.aimsrv.net
Client 800
Port 8010
__4. Press Ctrl-s to save your changes.
1.3 Start Create Order Process Instance
The process is now ready to execute! Let’s run an instance in the Process Designer’s Inspector.
__1. Switch to Sales Order Process view
__2. Click the orange Run Process icon.
__3. If you see On Switch View? Window, select Remember decision? and click Yes
__4. Select Step: Create Sales order and click the orange Runs the selected task icon
__5. On Pick Users From Team select admin and click OK
Since we have not explicitly defined any teams to execute tasks, the system admin user admin is
selected.

__6. You are just about to login to SAP EPR server. Ask you instructor for your user id and
password.
The user id format is eccuserX and password is passXword. Your instructor will give the value of
X (a number between 1 and 10 inclusive).
__7. Notice the SAP Server logon screen. You will need to enter here the SAP server user credentials.
Follow these steps exactly (to avoid possible login issues we been having with this driver):
• For User Name enter eccuserX
• For Password enter passXword
• Switch the focus back to User Name
• Click OK.

52
__8. Notice that you are now displaying Web user interface for the VA01 SAP transaction – Figure 5.
The SAP technology we are using to display transactions is SAP Web GUI. The SAP Guided Workflow
Toolkit includes a Coach View that is capable of displaying the SAP Web GI URL in an iframe. Notice the
Complete button. This button is outside of the SAP Web GUI iframe and can be used to close that task
when the SAP transaction is completed.
Figure 5. Coach View Displays SAP Web GUI in an iframe
__9. Click the Complete button (as if you have competed this SAP transaction)
__10. Switch back to Process Designer
__11. Click the yellow Refresh button
__12. Notice that the first task is now completed and we are just about to execute the next step: Verify
Sales Order

__13. Select Step: Verify Sales and click the orange Runs the selected task icon
__14. Notice that now you were not asked for the SAP user credentials. This is because BPM
“remembered” and retrieved the SAP user credentials associated with BPM user admin and
autumnally used them to login to SAP.
__15. By now you portably now have a good grasp how BPM wraps SAP Web GUI screens end
executes them as process steps. The term SAP Guided Workflow comes from this concept. SAP
user is guided by BPM process steps through SAP user interface screens! On Display Sales Order
transaction Coach click Complete

52
Enable Bidirectional Variable Support between SAP Screens and
BPM Process
You may have noticed that the Create Sales Order SAP Web GUI screen had some uninitialized entry
fields. One of the key features of SAP Guided Workflow is that the SAP Web GUI screens can be
initialized from BPM process variables!
Let’s explore how this is done.
1.1 Initialize SAP Screen Data from BPM Variables – VA01 Transaction
__1. Click the Designer tab
__2. Click the Create Sales Order step
__3. Click the Properties tab then the Custom tab
__4. Select the VA01 transaction row and then click Add Business Object button
__5. Notice that Process Designer knows about the variable types associated with all standard SAP
transactions. In this case these are the VA01 transaction variables. They can be used to initialize
the VA01 transaction Web GUI screen.

__6. Click the Add button
__7. In the blank space type SalesOrderNumber. We will need this variable later on to retrieve the
sales order number when the VA01 transaction is completed.
__8. Select Create a private variable and click Finish.

52
__9. You were taken to Business Object editor. Note that a new type VA01 was created. Select
SalesOrderNumber
__10. Click Edit
__11. Replace the text with a CSS selector with the code in file C:LABS1824.txt. This CSS selector
retrieves and format the Sales Order Number from VA01 transaction screen
selector=span[id*='MessageBar']
input=false
required=true
extractRegex=d+
format=d+
__12. Click OK

__13. Select Sales Order Process to return to Process editor
__14. Click Variables tab
__15. Select VA01 Private variable (Recall that you were asked to create it in the previous step) and
select Has Default
__16. Add the following initialization values for the parameters in the VA01 transaction inside the quotes.
Label SAP Variable Value
Order Type VBAK_AUART OR
Sales Organization VBAK_VKORG 1000
Distribution Channel VBAK_VTWEG 10
Division VBAK_SPART 00
Sales Office VBAK_VKBUR 1010
Sales Group VBAK_VKGRP 111

52
__17. Press Ctrl-s to save your changes
1.2 Map Process Variables – VA01 Transaction
You will now map the VA01 variable to initialize the VA01 SAP transaction and to the result of the
transaction (sales order number).
__1. Click Diagram tab to return to Process editor
__2. Select Create Sales Order task
__3. Select Properties > Data Mapping and click Select a variable icon to map transactionBO (ANY)
__4. Select and double-click VA01
__5. Map output (ANY) to VA01. This will retrieve the sales order number from the SAP screen to the
process variable VA01.
1.3 Initialize SAP Screen Data from BPM Variables – VA03 Transaction

__1. Click Verify Sales order step
__2. Click Properties tab then Custom tab
__3. Select the VA03 transaction row and then click Add Business Object button
__4. Select Create a private variable and finally click Finish button.
__5. Click the X button to close the Business Object editor.
__6. Click Variables tab

52
__8. Select VA03 Private variable (Recall that you were asked to create it in the previous step) and
select Has Default
1.4 Map Process Variables – VA03 Transaction
You will now map the VA01.SalesOrderNumber returned by the VA02 SAP transaction to an appropriate
field in the VA03 variable and then map that variable to the input of the VA03 SAP transaction.
__1. Click the Diagram tab
__2. Select Verify Sales order task
__3. Select Properties > Pre & Post and click the Pre Assignment + button
__4. Use the Select a variable icon to map the Sales Order Number returned by the VA01 transaction
(tw.local.VA01.SalesOrderNumber) as input to the VA03 transactions
(tw.local.VA03.VBAK_VBELN)
__5. Select Properties > Data Mapping and click Select a variable icon to map transactionBO (ANY)

__6. Select and double-click VA03
__7. Similarly map output (ANY) to VA03
1.5 Start a Process Instance to Test our Code
Because, during the import from SAP Solution Manager you selected Generate a Guided Workflow
checkbox, the SAP Guided Workflow toolkit was added.
__1. Click the orange Run Process icon.
__2. Select Step: Create Sales order and click the orange Runs the selected task icon
__4. You should now see the initialized values. Set focus inside in one of the entry fields in the Web
GUI screen and press Enter key

52
__5. In the Create Standard Order: Overview screen enter
Sold-To Party 301349
Material M-12
Order Quantity 1
__6. Ensure the focus is on the Order Quantity field. Press Enter key. SAP will now recalculate and
validate all the fields.
__7. Hover the mouse over the Complete button. Notice it is disabled! This is one of the key features of
BPM Guided Workflow! You cannot complete the BPM task until the SAP transaction is completed.
__8. Click the Save button to complete the SAP transaction
__9. Notice the sales order number in the bottom of the Sap Web GUI screen.

__10. Now that we completed the SAP transaction (note the generated sales order number), the
Complete button is enabled. Click the Complete button.
__12. Click the yellow Refresh button
__13. Notice that the first task is now completed and we are just about to execute the next step: Verify
Sales Order
__14. Select Step: Verify Sales and click the orange Runs the selected task icon

52
__16. Notice that the Order field in Display Sales Order (VA03) transaction has been initialized.
Recall that this Sales Order Number was generated by the first step in the Sales Order Porcess (Create
Sales Order task) and transferred as input to the second task (Verify Sales order)
Figure 6. Sales Order Number Transferred from VA01 to VA03
As shown if Figure 6, the Sales Order Number generated by the VA01 transaction was transferred to the
next SAP screen. This ability to retrieve data generated by one SAP transaction and transfer it to another
one is key feature of SAP Guided Workflow!
__17. Close Firefox Web Browser

Examine the Complete Solution
So far we have shown you how to import a SAP process from SAP Solution Manager to IBM Process
Designer and quickly convert it from a “picture of a process” to a fully functional execution-ready process.
You have learned about bidirectional data transfer future of SAP Guided Workflow. Specifically you
learned how to initialize SAP screens from process variable and how to retrieve data from SAP screens
tonto process variables
In this section you will examine a fully completed solution. Specifically you will explore how we can use
an automated service to retrieve net order value from a SAP Sales order and how to implement an ILOG
rule to create a decision service to decide if a sales order review step is required.
Finally you will run a Sales Order Process instance in IBM Process Portal to see how real business user
would interact with the Sales Order Process.
1.1 Open Process Application Containing a Full Solution
__1. Click Process Center icon (upper right corner)
__2. For GC SAP Sales Order Process App click Open in Designer
1.2 Examine the Additional Enhancements
__1. Select Processes and double click Create Sales Order

52
__2. Let’s highlight the additional enhancements over what you have authored so far in the lab…
Figure 7. Create Sales Order Process - Full Solution
1
Swim-lanes. Each swim-lane defines a team of business users that can execute tasks in given swim-lane.
Each team also has a manager that can supervise and manage the tasks and the users using BPM Process
Portal.
2
Rework loop. We added a decision node to ensure Sales Managers that inspect Sales Order (VA03)
transaction can decide if the Sales Order must be altered (VA03) or is ready for further processing.
3
This is an automated Service that accepts Sales Order Number from VA02 and Delivery Number from
VL01N and processes it.
4
This is an automated step that accepts the Sales Order Number and returns the sales order amount for use
in the decision service.
5
This is a decision mode that invokes ILOG Rule (using embedded in BPM ILOG Rules Engine). This rule
determines if a sales order review is required (VA03) or we go straight to creating delivery (VL01N)
Let’s first examine in more detail:
• 4 - SAP System Query
• 5 - (ILOG Denison Service
1.3 Examine 4 (SAP System Query Service) in Process Designer
This is an automated step that accepts the Sales Order Number and returns the sales order amount for
use in the decision service

__1. Click SAP System Query task
__2. Select Properties > Implementation tab and click getNetOrderValue to open the Advanced
Integration Service editor.
__3. Note the input parameter orderNumber. This is the sales order number returned from the first step
in the process. Also note the output parameter netOrderValue. This output parameter is used by
the ILOG rule that determines if the sales order requires a review.
__4. Also note that this service is not implemented in Integration Designer. Unlike Process Designer
which can be used by business users, Integration Designer is a tool for use by highly skilled IT
developers. It is best suited for developing technical services such as this one.
1.4 Examine 4 (SAP System Query Service) in Integration Designer
Let’s investigate how the getNetOrderValue service was implemented!
__1. Switch to Integration Designer.

52
__2. Let’s examine how the getNextOrderValue service was implemented
1 This is the representation of the getNextOrderValue service you have seen in Process Designer
2
This is a BPEL process that orchestrates the steps required to get the data from SAP server and return it to
getNextOrderValue service. The purpose of the BPEL component is to invoke the SAP Adapter Service and
mediate between the simple types of the getNetOrderValue parameters and the complex SAP BAPI data
types used in SAP Adapter Service.
3
This is the SAP Adapter outbound J2C Adapter service. It retrieves the data from SAP BAPI
SalesOrderGetStatus
__3. Double-click the I icon on getNetOrderValue Service
__4. Notice the input and out parameters on the interface to tis service. They are exactly the same as
you saw in Process Designer.
__5. Click X button to close the Interface editor.
__6. Double-click the I icon on GetSalesOrderInformation SAP Adapter Service
__7. Notice the complex BAPI types representing the interface to the SAP Adapter service.
__8. Click X button to close the Interface editor.
__9. Double click the GetNetOrderAmount BPEL component

__10. Examine the BPEL process flow
1
These two activities format the complex SAP BAPI type, initialize it and inject
the SalesOrderNumber to the SAP BAPI input parameter.
2 This activity invokes the SAP Adapter.
3
These two activities extract from the complex AP BAPI (returned by the SAP
Adapter call) the NetOrderAmount value.
1.5 Test the SAP System Query Service
Let’s test the implementation of the getNetOrderValue to open the Advanced Integration Service editor.
__1. Click X button to close the BPEL editor.
__2. Right click GetNetOrderAmount and select Test Component
__3. For orderNumber enter 11368. This sales order number exists in the SPP server used for this lab.

52
__4. Click the green Continue button
__5. Note in the left pane, the trace showing how the various component in including the steps in the
BPEL process. Also note in the right pane the returned Net Order Value
__6. Minimize Integration Designer
1.6 Examine 5 (ILOG Decision Service)
__2. Click Verify Order? decision gateway
__3. Select Properties > Decision and note the input variable to this decision gateway. This variable is
the output if the SAP System Query Service. It returns the net order value for a sales order. Recall
that you examined the implementation of this service in the previous step.

__4. Click the Decision Service verificationReuired
__5. Click Variables tab and note the input is the netOrderValue and the output a decision
verifcationReuired
__6. Click the Decisions tab and examine the simple ILOG rule authored in the BAL (Business Action
Language) language. The rule states that if order amount is greater than 10,000 for
verificationRequired return true.
__7. Click X to close the Decision Service
__8. Click Implementation tab and note how the output of the Decision Service verificationRequired is
used to determine which process branch to take. In this case if order amount is greater than
10,000 we navigate to Verify Sales Order Details VA03 task.

52
Test the Full Solution in Process Portal
So far you run some process instances as developer would to test the process in the Process Inspector
in Process Designer. Now let’s run a process instance like a business users would to complete a sales
order.
Before we proceed let’s review what business user are assigned to perform process steps. To simplify
the lab we assigned a single user to each swim-lane.
1.1 Start the Process and Provide Initial Sales Order information [Wendy]
__1. Open Firefox browser from the desktop.
__2. Click Process Portal form the bookmarks toolbar
__3. Login as wendy and use password of abc

__4. Click Create Sales Order to start a new instance of the Sales Order Process
__5. Follow these steps exactly (to avoid possible login issues we been having with this driver):
• For User Name enter eccuserX (use the user id you got from the instructor)
• For Password enter passXword (use the password you got from the instructor)
• Click OK
__6. On Create Sales Order: Initial Screen (note the initialized Organization Data) press Enter key.
__7. In the Create Standard Order: Overview screen enter
Sold-To Party 301349
Material M-12
Order Quantity 20
__8. Set focus inside in one of the Order Quantity entry field and press Enter key. SAP will now
recalculate and validate all the fields. Notice the Net value exceeds 10,000 according to the ILOG
rule you examined in previous section, management review will be required.

52
__10. Click the Complete button.
1.2 Review Sales Order Information [Paul]
__1. Logout from Process Portal
__2. Login as paul / abc.

__3. Notice that Paul has the review task to complete! From the drop-down select View Process
Diagram (Note the tsk can be in either Due Today or Overdue dropdown section)
Notice that path taken. Recall that the order Net Value was .
Therefore since the amount exceeded 10,000 management review is required.
__4. Click X button to close the process diagram.
__5. Click Verify Sales Order: DetailsVA03 task to claim it
• Click OK
__7. Note the Order field has been initialized. The sales order number was passed from the previous
step in the process.
__8. On Display Sales Order screen press Enter key

52
__9. Scroll down to the bottom (use scroll bar) and Enter a comment: Quantity cannot exceed 15 and
then click Complete
1.3 Change Sales Order [Wendy]
__2. Login as wendy and use password of abc
__3. Click Change Sales Order VA02 task to claim it
__4. On Change Sales Order screen press Enter key.
__5. Change Order Quantity to 15
__6. Press Enter key
__8. Click the Complete button.
1.4 Review Sales Order Information [Paul]
__2. Login as paul / abc.

Diagram
Notice that path taken. Now that Wendy has changed the order quantify and now the prcess navigated to
Verify Sales Order Details task. Paul needs to review the sales order again.
__5. Click Verify Sales Order: DetailsVA03 task to claim it
__6. On Display Sales Order screen press Enter key. Note the Order field. The sales order number was
passed from the previous step in the process.

52
__7. Note that Wendy adjusted the Order Quantity to 15. Click Complete. Do not eneter any
commnets!
1.5 Create Outbound Delivery [Allen]
__2. Login as allen / abc.
Diagram
Notice that path taken. Now since Paul did not enter any comment the task now moved to the next step:
Create Outbound Delivery.

__5. Click Create Outbound Delivery: VL01N task to claim it
• Click OK
__7. Click date selector for Selection date
__8. Select a date at least a month later from the current date.
__9. After selecting delivery date, back on the Sales Order Data screen, press Enter key.
__10. Note the Delivery Create: Overview click Save button
__11. Note that the Delivery number was generated, the SAP transaction has been compled and the
Complete button is noe enabled! Click Complete.

52
Examine Historical Process Performance Data for Process
Improvement
In this part of the lab you will explore the process optimization feature of Process Designer. Once the
Create Sales Process has been deployed and in production the Optimizer will start providing us with
insights into the historical process runtime statistics. This is a key value of automating SAP based
applications. We can get insight into how the process instances are performing in a production
environment and from this gained knowledge we can optimize the process and achieve significant cost
savings!
1.1 Set up Process Optimizer
__1. Switch to Process Designer
__2. From the main toolbar click Optimizer.
__3. For Mode select Single Historical, and then click Select…
__4. Select Sales Order Process Optimizer. Note that this Historical Analysis Scenario was already
created for you. It simply specifies that we want to monitor the data from the Sales Order Process.

__5. Click the Calculate button to gather the historic process instance data.
__6. Wait until scenario results are computed (bottom right corner of the screen)
Note that we have run several instances of the process for you. That is way you now are seeing some
data in the Optimizer.
1.2 Wait Time View
Note that by default the Optimizer shows the Wait Time view.
__1. In the Smart Start tab click More…

52
__2. Note the average wait time for all the activities in the process.
We can conclude that two tasks: Verify Sales Order Details and Create Outbound Delivery have by far
the longest wait time and incease sinificantly the average process completion time. Looks like the
Optimzer already is pointeing out some good opportunities to speed up the process!
__3. Also note that the average wait time is visualized in the process diagram. The brighter the halo the
longer the wait time!
__4. Hover over the Verify Sales Order Details VA03 task and notice the two graphs (trend and
distribution).
1.3 Process Path View
__1. In the Heatmap Settings tab click Wait Time and select Path

__2. Note the information about the process path distribution. Note that not all (100%) of process
instances are completed. Some are still in flight!
__3. Take a look at the Live Reports tab. The reports contain detailed statistics about all process
instances.

52
1.4 Rework View
__1. In the Heatmap Settings tab click Path and select Rework
__2. Note that two tasks in this process fall into the “rework” category.
“Rework” means that in the same process instance a tasks are executed more than once. The intensity
of the red halo corresponds to the number of iterations. The Optimizer shows that too often it takes more
than one cycle to ensure sales order details are correct!
__3. Click the Verify Sales Order Details VA03 task.

__4. Examine the Recommendations tab.
Note the Bypass Wizard. This wizard will suggest how to optimize the process. It can recomad a rule
which can be used to filter instances (based on the process data) where the review step is not
necessary. This optimization will bypass review step where it is not necessry!

52
Summary
In this lab you have learned how to convert a process definition (a picture) in SAP Solution Manager onto
an executable BPM process. You saw the benefits of automation and also the value hat process
optimization can bring. All performed in a single tool and runtime: IBM BPM Advanced
Recall the high level you performed:
1. Import a process from SAP Solution Manager to IBM BPM Process Designer
2. Examine the generated BPM Guided Workflow process
3. Configure SAP Server for runtime execution of SAP Guided Workflow
4. Enable bidirectional variable support between SAP screens and BPM process
5. Examine the SAP BAPI integration service implementation
6. Test the full solution in Process Portal
7. Examine Historical Process Performance Data for Process Improvement
.

SAP guided workflow in IBM BPM

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Destaque

Destaque (20)

Semelhante a SAP guided workflow in IBM BPM

Semelhante a SAP guided workflow in IBM BPM (20)

Mais de sflynn073

Mais de sflynn073 (20)

SAP guided workflow in IBM BPM