revisiting sap business workflow€¦ · ¤sap ag 2006 guided procedures vs. workflow use sap...
TRANSCRIPT
Revisiting SAP BusinessWorkflowSAP NetWeaver Product Management
When building your first workflowNew recommended workflow featuresExtended Notifications, Outlook, and Lotus NotesRecommendations for Universal WorklistUsing BI for monitoringGuided ProceduresResources to help you
Laying the ground work
When building your first workflowNew recommended workflow featuresExtended Notifications, Outlook, and Lotus NotesRecommendations for Universal WorklistUsing BI for monitoringGuided ProceduresResources to help you
Laying the ground work
SAP AG 2006
1995
EP 5.0
2003
SAP NetWeaver ‘04
SAP NetWeaver 2004s
BusinessWorkflow
UniversalWorklist
+ CollaborationTasksBPM
+ GuidedProcedures
Workflow is evolutionary
…
SAP AG 2006
Business Department
“We need to supplementthe companies coreprocesses with ourown departmentalprocedures.”
Central IT
“We need to createflexible, robust andhighly scalablestandardized processes”
Individual
“I want to delegatesome of my tasksto colleagues, andtrack their progress.”
Centralized vs. Decentralized Process Control
SAP AG 2006
Guided Procedures vs. Workflow
Use SAP Business Workflow where:Procedure is SAP-system centricProcedure is deeply integrated into a single SAP systemDetailed audit requirements are criticalProcedure is long term and well-definedMinimal changes expected in the short/medium termCreated and maintained by Workflow Developer
Use Guided Procedures where:Procedure is non-SAP-centric or involves a heterogeneous mix ofsystemsSAP solutions with no ABAP stack (e.g. xPD)Procedure is short term and unclearMany changes expected in the short/medium termCreated and maintained by Business Expert
When building your first workflowNew recommended workflow featuresExtended Notifications, Outlook, and Lotus NotesRecommendations for Universal WorklistUsing BI for monitoringGuided ProceduresResources to help you
Laying the ground work
SAP AG 2006
Before you build…
How to know if a workflow for your scenario exists:Online help – http://help.sap.com
SRM - Scenario Independent functionsERP – Scenarios in ApplicationsCRM – Components and Functions – Basic Functions – BusinessWorkflow
Workflow explorer – SWDMApplication hierarchy, local objects, task groups searchObject-based search for single-step tasks
Other options:ABAP Interface IF_WORKFLOW – where-used list for ABAP OOworkflowsBusiness Object Repository (BOR), transaction code SW01Use the event trace, transaction code SWELS
After turning on the trace, do the action you would like to start a workflow(create a material, update a project, etc.)Use transaction code SWEL to see if an event has occurredIf so, you already know the business object you need and you know you havean event tied to the application
SAP AG 2006
Workflow Builder
22
11
33
Drag & Drop
Tip: It’s usual to spend more timedesigning and prototyping thebusiness process than developingthe workflow that implements it.
When building your first workflowNew recommended workflow featuresExtended Notifications, Outlook, and Lotus NotesRecommendations for Universal WorklistUsing BI for monitoringGuided ProceduresResources to help you
Laying the ground work
SAP AG 2006
ABAP OO for Workflow 6.40
SAP Business Workflow now supports two object repositoriesBOR (Business Object Repository)SE24 (ABAP Objects)
Any ABAP Programmer becomes a Workflow Programmer! (worksalongside Workflow Developer)
Simple to code, faster to code, fewer restrictions than BORMultiple inheritance, true generic programming possibleFull support in containers, expressions, tasks, events, exceptions, bindingsCan make existing ABAP Classes workflow-readyCan mix ABAP OO with BOR objects – using data type SIBFLPORB
Some applications slow to catch upNot much provided business content as yet – existing BOR objects not re-codedEvents raised by change documents supported, but not other configurable eventraising mechanisms as yet (status management, HR events)
SAP AG 2006
More Web-relevant features 6.20
Calling an SAP type transaction from the UWLTransaction SWFVISU for basic configurationUWL XML Configuration for detailed configuration
Calling any URL from UWL or SBWP (SAPGUI Inbox)Transaction WF_EXTSRV – configure URL, import/export parameters,and call type (dialog/batch, synchronous/asynchronous), Wizard helpTasks generated automatically – to repoint, maintain tableSWLWPTSSIDWorkflow handlers must be configured (transaction WF_HANDCUST,service ws_handler activated in SICF)Transaction WF_WSDL – create task from WSDL
Forms – recommendation: AdobeRequires WebDynpro application to run the form – provided by ISR/PCRtechnique in ECC5 onwards – otherwise create your own WebDynpro
SAP AG 2006
More support for special features 6.20
Workflow level events to Cancel, Cancel and Restart, Re-evaluateagents of active work items
Set re-evaluate agents at the work/sub-flow in which the step to bereassigned existsRe-evaluate agents – add escalators to existing work without affectingdeadlines or removing the original agent; reassign agents in responseto system activity
BindingsMore options:
AssignAppendHandle errors as warning (e.g. for narrowing cast)Map to structure
SAP AG 2006
Re-implementation of the Container 6.20Complete reimplementation of container technology
No restrictions concerning data typesDDIC types with arbitrary lengthsBinary dataStructures with arbitrary depth and complexityABAP OO references
Container is by default stored as XML documentFacilitates diversity of supported data typesSaves storage space (especially for large containers/structures)
No database entry for each structure field required anymoreEntails serialisation / deserialisation effortReplace old reports reading SWCONT, SWCONTOB tables with Workflow APIcalls
Old container persistence (SWCONT, SWCONTOB) still supportedCompatibility modeWorkflow Builder setting
SAP AG 2006
Other bits and bobs 6.20
More Workflow APIsWorkflow APIs (SAP_WAPI_* function modules) for administrativefunctions
Work item Forward by AdministratorRe-evaluate Agents – e.g. add escalators to existing work
Workflow APIs to control substitution
More Administration ToolsRe-execute rules on active work itemsAdministrator ForwardAdministrator actions automatically marked on workflow logWork items with Deleted users (6.40)Restart Suspended workflows/deadlines (6.40)
When building your first workflowNew recommended workflow featuresExtended Notifications, Outlook, and Lotus NotesRecommendations for Universal WorklistUsing BI for monitoringGuided ProceduresResources to help you
Laying the ground work
SAP AG 2006
Email Notifications of Work Items
Replacement for SAP MAPI is provided (Support ends 10/2005)Client-based MS Outlook integration of SAP Business Workflow
New solutionsServer-based (zero footprint)Mail client independentCovers 90% of workflow-related MAPI customer scenarios
Extended Notifications (releases 6.40+)Server notification framework (read note 627397)Supports Web UI and SAPGUIHighly Configurable – Transaction SWNCONFIG or SWNADMINEasy to enhance – e.g. to include non-workflow tasks/mailsCan be used INSTEAD of an SAP workflow inbox!
Report RSWUWFML2 (releases 4.6C to 6.20)Polling report sending email notifications
6.20
SAP AG 2006
Extended Notifications: Basic Features
Notify users about work items that need to be processedSend workitems to groupware (e.g. MS Outlook or Lotus Notes)carrying direct callbacks to backend transactions
Execution of web-based work items (Web Dynpro, People centric UI, …)Execution of work items via SAP GUI for Windows or Web links
6.40
When building your first workflowNew recommended workflow featuresExtended Notifications, Outlook, and Lotus NotesRecommendations for Universal WorklistUsing BI for monitoringGuided ProceduresResources to help you
Laying the ground work
SAP AG 2006
Universal Worklist Purpose
Aggregate task items from multiple and different systems into onelist
SAP Business WorkflowCollaboration Tasks, Alert Management SystemKnowledge ManagementNotifications (including SAP Office Mail with SONiC Connector)Guided Procedure ActionsNon-SAP tasks (with UWL API)
Universal Worklist API (requires Java programming)E.g. SONiC Connector for SAP Office Mail – watch for a Blog on SDN soonFurther info:
SAP Note: 921758BLOG on SDN: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3172
SAP AG 2006
Universal Worklist: Unified and Centralized access to Work
UWL is part of the standard End User role, accessed via Home - Work
Hint: To Refresh your lists of tasks, use the dropdown menu near the Hide Preview link.
Tip: Give it a FULL PAGE inthe Portal
SAP AG 2006
UWL Provides Task List, Execution, and Context
Task Context
Task List
Task Execution
Note: Lots of special features available – e.g. note entered with userdecision, multi-item approval/rejection, decline, personalization
Note: As of EP 7.0, attachments and user view ofworkflow log supported natively
SAP AG 2006
Launch Work Transaction
Parameterized launching forBSPiViewURLWeb Dynpro (Java/ABAP)SAP GUI (for HTML)Object links (EP 7.0 SP8)
Note:Enables you to add new UI’s forlegacy SAP tasks (use WebDynpro to launch existing task ina 4.6C system).Currently piloting API to enableexternal tasks to appear in UWL
SAP AG 2006
Standard Task Views & Filters
Hint XML-based configuration enables specificviews for specific tasks – wizard help in NW04s.
Hint: Can also function as an application-specific inbox – applications can bypasshaving to implement their own inbox. Some examples provided, e.g. MSS/ESS.
When building your first workflowNew recommended workflow featuresExtended Notifications, Outlook, and Lotus NotesRecommendations for Universal WorklistUsing BI for monitoringGuided ProceduresResources to help you
Laying the ground work
SAP AG 2006
BI Integration for SAP Business Workflow (1)
The Workflow Information System (WIS) has become obsolete withWAS release 610
Customers do their reporting using BI
Workflow projects with BI requirementscould not use standard workflow-related data extractionhad to implement their own extraction logic for workflow data
This gap has now been closedTechnical work item data is available in BI as infocubeHow many workflows of type ‘xy’ were executed?What is the average processing time for a given workflow (step)?How many steps of type ‘xy’ were executed by org unit ‘abc’?
Workflow and Business Objects worlds are linked by work item toobject relation information available
NW04s
SAP AG 2006
BW Integration for SAP Business Workflow (2) NW04s
When building your first workflowNew recommended workflow featuresExtended Notifications, Outlook, and Lotus NotesRecommendations for Universal WorklistUsing BI for monitoringGuided ProceduresResources to help you
Laying the ground work
SAP AG 2006
Guided Procedures – Definition
offers a flexible, functional process environment
that enables users without specialized softwaredevelopment skills to easily set up and executecollaborative business processes
by providing reusable templates, assisting userswith data proposal and allowing ad-hoc changes atruntime
enables offline process execution via InteractiveForms
NW04s
SAP AG 2006
Guided Procedures – Design Time NW04s
SAP AG 2006
Guided Procedures – Run Time NW04s
When building your first workflowNew recommended workflow featuresExtended Notifications, Outlook, and Lotus NotesRecommendations for Universal WorklistUsing BI for monitoringGuided ProceduresResources to help you
Laying the ground work
SAP AG 2006
The bestselling Workflow book
• Setting up workflow• Agent assignment• Workflow administration• Building workflows• Using forms• Custom programs• Defining requirements• Work item delivery• Reporting
• Setting up workflow• Agent assignment• Workflow administration• Building workflows• Using forms• Custom programs• Defining requirements• Work item delivery• Reporting
http://www.sap-press.com/product.cfm?account=&product=H950
SAP AG 2006
Further Information
SDNBlog series on ABAP OO and Workflow by Jocelyn DartSeveral blogs on UWL configuration by Ginger GatlingBPM Forum for all other questionsBlog series on Extended Notifications plannedSAP Notes with official recommendations:
98407: Performance Workflow322526: Analysis of workflow problems
Public sites and training Opportunitieshttp://www.sap.com/education/BIT600, BIT601, BIT603, BIT610
SAP AG 2006
Copyright 2007 SAP AG. All Rights Reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may bechanged without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p,System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC aretrademarks or registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express priorwritten permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments,and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that thisdocument is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other itemscontained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability,fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. Thislimitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained inthese materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.