SAP SOLUTIONS FOR GOVERNANCE,RISK, AND COMPLIANCE

Process Control 2.5 WorkflowCustomizing

SAP GRC Regional Implementation Group

Applicable Releases:

SAP GRC Process Control 2.5

Topic Area:GRC / Process Control

Capability:GRC / Process Control

Version 1

June 2008

© Copyright 2008 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 containedherein may be changed without prior notice.

Some software products marketed by SAP AG and itsdistributors contain proprietary software components of

other software vendors.

Microsoft, Windows, 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, z/OS, AFP,

Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,i5/OS, POWER, POWER5, OpenPower and PowerPC are

trademarks 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 WebConsortium, 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 andimplemented 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 registered trademarks of SAP AG in

Germany and in several other countries all over the world.

All other product and service names mentioned are thetrademarks of their respective companies. Data contained

in this document serves informational purposes only.

National product specifications may vary.

These materials are subject to change without notice.

These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes only,

without representation or warranty of any kind, and SAP

Group shall not be liable for errors or omissions with

respect to the materials. The only warranties for SAPGroup products and services are those that are set forth in

the express warranty statements accompanying such

products and services, if any. Nothing herein should be

construed as constituting an additional warranty.

These materials are provided “as is” 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 not be liable for damages of any kind including

without limitation direct, special, indirect, or consequential

damages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of the

information, text, graphics, links or other items contained

within these materials. SAP has no control over the

information that you may access through the use of hot

links contained in these materials and does not endorse

your use of third party web pages nor provide any warranty

whatsoever relating to third party web pages.

SAP NetWeaver “How-to” Guides are intended to simplify

the product implementation. While specific productfeatures and procedures typically are explained in a

practical business context, it is not implied that those

features and procedures are the only approach in solving a

specific business problem using SAP NetWeaver. Should

you wish to receive additional information, clarification or

support, please refer to SAP Consulting.

Any software coding and/or code lines / strings (“Code”)

included in this documentation are only examples and are

not intended to be used in a productive system

environment. The Code is only intended better explain andvisualize the syntax and phrasing rules of certain coding.

SAP does not warrant the correctness and completeness of

the Code given herein, and SAP shall not be liable for

errors or damages caused by the usage of the Code, except

if such damages were caused by SAP intentionally or

grossly negligent.

Disclaimer

Some components of this product are based on Java™. Anycode change in these components may cause unpredictable

and severe malfunctions and is therefore expressively

prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is only

to be used by SAP’s Support Services and may not be

modified or altered in any way.

4/9/2008 1

Document HistoryDocument Version Description

1.00 Document created

Table of Contents1 Introduction .................................................................................................. 2

1.1 About this document ............................................................................ 21.2 Information Available on SAP Service Marketplace ............................. 3

2 Technical System Landscape ..................................................................... 52.1 Process Control Architecture ............................................................... 52.2 Software Component Matrix ................................................................ 6

3 Workflow Customizing ................................................................................ 73.1 Automatic Workflow Customizing ........................................................ 83.2 Event Linkage Agents and Workflow ................................................... 103.3 Task specific customizing .................................................................... 123.4 Event Queue ........................................................................................ 153.5 Register Workflow System in qRFC Monitor ........................................ 18

4/9/2008 2

1 Introduction

1.1 About this document

SAP GRC Process Control is an enterprise software solution for internal controls management. Itenables organizations to document their control environment, test and assess controls, track issuesto remediation, and certify and report on the state and quality of internal controls. Using acombination of data forms, automated workflows, certification and interactive reports, this solutionenables members of internal control, audit and business process teams to effectively managecompliance activities. SAP GRC Process Control features ERP integration and automated controltesting and monitoring, which may help to reduce audit cycles and cost of compliance, as well asprovide a higher degree of reliability and integrity in financial statements.

SAP solutions for governance, risk, and compliance are powered by the SAP NetWeaver® platform.SAP NetWeaver unifies technology components into a single platform, allowing organizations toreduce IT complexity and obtain more business value from their IT investments. It provides the bestway to integrate all systems running SAP or non-SAP software. SAP NetWeaver also helpsorganizations align IT with their business. With SAP NetWeaver, organizations can compose andenhance business applications rapidly using enterprise services. As the foundation for enterpriseservice-oriented architecture (enterprise SOA), SAP NetWeaver allows organizations to evolve theircurrent IT landscapes into a strategic environment that drives business change.

This guide provides guidelines and GRC best practices for the implementation of the SAP GRCProcess Control. Implementation is the process of understanding customer requirements and helpsto lay a firm groundwork for successful implementation of the Suite.

4/9/2008 3

1.2 Information Available on SAP Service Marketplace

More information is available as follows on SAP Service Marketplace

Documentation

Description Internet Address Title

The security guide describes thesettings for a medium securitylevel and offers suggestions forraising security levels. A collectivesecurity guide is available for SAPNetWeaver.

http://service.sap.com/securityguide SAP GRC ProcessControl Security Guide

The master guide is the startingpoint for implementing an SAPsolution. It provides scenario-specific descriptions ofpreparation, execution, and follow-up of an implementation. It alsoprovides references to otherdocuments, such as installationguides, the technical infrastructureguide and SAP Notes.

http://service.sap.com/instguides SAP GRC Process MasterGuide

The operations manual is thestarting point for operating asystem that runs on SAPNetWeaver. The manual refersusers to the tools anddocumentation that are needed tocarry out various tasks, such asmonitoring, backup/ restore,master data maintenance,transports, and tests.

http://service.sap.com/instguides SAP GRC ProcessControl Operations Guide

The SAP Library (users guide) is acollection of documentation forSAP software covering functionsand processes.

On SAP Help Portal at http://help.sap.com(also available as documentation DVD) SAP GRC Process

Control Users Guide

The installation guide describesthe technical implementation of aninstallable unit, taking into accountthe combinations of operatingsystems and databases. It doesnot describe any business-relatedconfiguration.

On SAP Service Marketplace at

http://service.sap.com/instguides

SAP NetWeaverInstallation Guide

4/9/2008 4

General Quick Links

Description Internet Address

SAP Help Portal http://help.sap.com

SAP Notes http://service.sap.com/notes

Released platforms and operating systems http://service.sap.com/platforms

System sizing http://service.sap.com/sizing

Security http://service.sap.com/security

4/9/2008 5

2 Technical System Landscape

2.1 Process Control Architecture

The following is an overview of the technical system landscape.

4/9/2008 6

2.2 Software Component Matrix

This is an overview of all the software components used by GRC Process Control. For moreinformation, refer to the SAP GRC Process Control Installation Guide at service.sap.com/instguides.

4/9/2008 7

3 Workflow Customizing

Many activities in Process Controls are workflow supported and therefore essential for theapplication to run smoothly. To customize the workflow engine you have to perform several steps toset up process controls workflow functionalities. All required steps can be found within the imgcustomizing (GRC Process Control Workflow).

4/9/2008 8

3.1 Automatic Workflow Customizing

The first activity is to run the automatic workflow customizing. Run transaction SWU3 or enter theautomatic workflow customizing via img GRC Process Control Workflow AutomaticWorkflow Customizing.

4/9/2008 9

Within the automatic workflow customizing you schedule all necessary jobs for the workflows aswell as the basic settings of the workflow engine. Expand the knot “Maintain Runtime Environment”to see all entries in the list. Select the knot “Maintain Runtime Environment” and press the “PerformAutomatic Workflow Customizing”, see red marked button. All required jobs are scheduledautomatically.

All entries under “Classify Tasks as General” should also be green.

4/9/2008 10

3.2 Event Linkage Agents and Workflow

Activating the event queue is advisable if many workflows are generated. In the case of fewworkflows, processing is quicker if you do not activate the event queue.

To activate the Event Linkage for the GRC Process Controls activities run transaction SWE2.Please check that the Type linkage for the object types GRPC* are activated. SAP recommendsactivating the event queue at least for the object types GRPC_CASEA and GRPC_CASET becausethis is where a large number of workflows are generated.

4/9/2008 11

To enable the Event linkage for an object type, make sure that you are in change view mode, andthen double click on the object type you want to change. Within the Event Type Linkage Details youcan activate the Linkage as well as the Event Queue by setting the flag as shown below. Finallysave you changes.

4/9/2008 12

3.3 Task specific customizing

In this activity you make all the settings required to adapt the SAP tasks and SAP workflowssupplied. Only carry out this activity if you want to use the scenarios supported by SAP.

Possible agents must be specified for each task in order to clearly define the organizationalresponsibility for processing.

Workflows can only be started in dialog by their possible agents. If a scenario requires that therelevant workflow be started in dialog, this workflow must be assigned to its possible agents.

4/9/2008 13

Any task not labeled as background task should be a “General Task”.

A task or workflow can be started as a reaction to events created by the application functionality.For this, specific events are declared as triggering events for the task or workflow. Activate thislinkage between triggering event and task or workflow if you really want to create the linkagebetween event and task or workflow as suggested by SAP.

4/9/2008 14

4/9/2008 15

3.4 Event Queue

In this IMG activity, you can make specific settings towards improving performance for workflowprocessing since many dialog processes are utilized during workflow generation. If the settings arenot changed, receivers of events (such as workflows) are started directly in the standard version.This may lead to a high system load if the number of events is large. To avoid this, events fordefined event linkages can be written into the event queue.

For background information on event queue administration, see the SAP Library for the SAPBusiness Workflow under Reference Documentation -> Workflow System Administration -> EventManager Administration.

Enter the Event Queue via transaction SWEAD or via img GRC Process Control WorkflowEvent Queue Administration. On the tab first tab “Overview” you should see the number of Eventlinkages activated for the Event Queue from chapter 3.2.

4/9/2008 16

Switch to the tab “Basic data” and determine the Administrator as well as the system behavior incase of errors (SAP recommends selecting the Deactivation of Linkage option from the dropdownlist).

Switch to tab “Activation” to activate the Event Queue.

4/9/2008 17

In the Background Job tab, you should adjust the settings for Number of events per read accessand Time interval between two read accesses to suit your system capacity. It is recommended toenter about 12 read accesses per minute. This means that 12 workflows are sent per minute foreach work process (if there are 10 work processes, 120 workflows are sent per minute). When usedin the context of the outbound queue in the IMG activity Register Workflow System in qRFCMonitor, individual workflows for which the event queue is not activated are also sent with theothers. Hence, if an additional single workflow needs to be sent during the mass generation ofworkflows, the workflow is processed after one minute as opposed to at the end of massprocessing.

By choosing Display Background Job, you can monitor the logs of the executed jobs.

In the Event delivery tab page, SAP recommends retaining the following default settings:

Processing of events: Sequential

Start of receivers: Asynchronous

4/9/2008 18

From the same tab page, you should make the settings for the server groups by choosing theServer Group Definition pushbutton. Pay particular attention to the setting made for the parameterMinimum Number of Free WPs: The smaller the value you specify, the greater the speed with whichthe events are processed

3.5 Register Workflow System in qRFC Monitor

To improve the performance of workflow processing, you can register the logical RFC destination used by theworkflow (WORKFLOW_LOCAL_<client>) in the qRFC outbound queue in the qRFC monitor.

4/9/2008 19

Use the “Registration” button for Registration.Enter WORKFLOW_LOCAL_<client> under Destination.Under MAXCONN, you can specify how many connections the queue may open to the system behind thedestination. The number specifies how many dialog processes should be stored.Under MAXTIME, specify for how many seconds the system should process the destination if the queuecontains several destinations. You can keep the default value (60). If one of the destinations should be thepreferred destination, you can increase the value for this destination.You must not set the NO_TRFC indicator because the workflow uses tRFC.

4/9/2008 20

4/9/2008 21

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components ofother software vendors.

Microsoft, Windows, 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 are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks ofAdobe 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 orregistered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide WebConsortium, 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 inventedand 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 servicesmentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world. All other product and service names mentioned arethe trademarks of their respective companies. Data contained in this document serves informational purposesonly. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and itsaffiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of anykind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The onlywarranties for SAP Group products and services are those that are set forth in the express warrantystatements accompanying such products and services, if any. Nothing herein should be construed asconstituting an additional warranty.This document was created using stylesheet 2006-12-31 (V5.1beta [= 6.0 for E3]) and XSLT processorSAXON 6.5.2 from Michael Kay (http://saxon.sf.net/), XSLT version 1.

DisclaimerSome components of this product are based on Java™. Any code change in these components may causeunpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation ofthese components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and maynot be modified or altered in any way.