PC10 Proc Integrtn

Using the Process Integration
Subscenario for Continuous

Monitoring in Process Control
Process Integration
Applies to:
SAP Process Control 10.0
Summary
This User Guide provides information about Process Integration subscenario architecture, implementation
requirements, configuration instructions, and use case.
Team:
Governance, Risk, and Compliance
Created on:
24 Oct 2012
Version 1.1
SAP COMMUNITY NETWORK

2012 SAP LABS
SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
Using the Process Integration-Driven Monitoring Subscenario
Document History
Document Version
Description
1.00
Initial Draft
1.10
Added notes emphasizing the significance of the valid from date of data
sources and business rules

2012 SAP LABS
Typographic Conventions
Icons
Type Style
Description
Icon
Example Text
Words or characters quoted

from the screen. These
include field names, screen
titles, pushbuttons labels,
menu names, menu paths,
and menu options.
Description
Caution
Note or Important
Example
Recommendation or Tip
Cross-references to other
documentation
Example text
Emphasized words or
phrases in body text, graphic
titles, and table titles
Example text
File and directory names and

their paths, messages,
names of variables and
parameters, source text, and
names of installation,
upgrade and database tools.
Example text
User entry texts. These are

words or characters that you
enter in the system exactly as
they appear in the
documentation.
<Example
text>
Variable user entry. Angle

brackets indicate that you
replace these words and
characters with appropriate
entries to make entries in the
system.
EXAMPLE TEXT
Keys on the keyboard, for

example, F2 or ENTER.

2012 SAP LABS
Table of Contents
1.
Business Scenario............................................................................................................... 1
2.
Background Information ..................................................................................................... 1
3.
Prerequisites ........................................................................................................................ 1
4.
Step-by-Step Procedure ...................................................................................................... 2
5.
4.1
Post-Installation Steps .................................................................................................. 2
4.2
Activating the PC Application ....................................................................................... 2
4.3
Review Master Data ..................................................................................................... 3
4.4
Creating Continuous Controls Monitoring Data ............................................................ 6

4.4.1
Creating Data Source for PROCESS INTEGRATION ..................................... 6
4.4.2
Creating a Business Rule for Process Integration ......................................... 10
4.4.3
Assigning the Business Rule to Controls ....................................................... 13
4.4.4
Creating a Job in Automated Monitoring ....................................................... 15
Copyright ............................................................................................................................ 22

2012 SAP LABS
1.
Business Scenario
This User Guide describes the Process Integration-driven monitoring subscenario with implementation
requirements and configuration instructions.
2.
Background Information
SAP GRC solutions can monitor non-SAP applications, and the Process Integrator-based data source
is one of several suitable for this purpose.
SAP Netweaver Process Integrator (PI, formerly known as Netweaver XI) is SAPs preferred platform
for integrations. PI supports common protocols such as JDBC and ODBC, and customers who have
non-SAP applications in their system landscape can use PI to either query directly against the
underlying databases of these applications via JDBC/ODBC, or even integrate at the code level, if
appropriate.
The implementation for Process Integration monitoring consists of several steps.
3.
Prerequisites
The system requirements for the Process Integration subscenario are as follows:
PC 10.0 is based on SAP NetWeaver 7.02 SP 06 (or above) ABAP stack.
SAP PI system and Process Control 10.0 have been set up successfully
You have completed the following steps:
You have created and configured regulation(s)
You have created corporation and organization units
You have created the central process, subprocess, and controls
You have assigned proper regulation(s) to the control
You have assigned subprocesses or controls to the corporation or organization unit
You have configured connectors

For more information about configuring connectors in the IMG, refer to the Creating
Connectors in PC 10.0 document at http://help.sap.com/pc.
You have created the following data:
The SAP NW Process Integrator system is ready.
The connection between GRC to PI system is created.
Process Integration proxy development is done.
The proxy must contain both import and export parameters.
The proxy import parameters are not table type.
October 2012
4.
Step-by-Step Procedure
4.1
Post-Installation Steps
Activate the PC application
Configure controls and business rules
4.2
Activating the PC Application
Complete the following steps to activate the process control application:

1. Log on to the NetWeaver ABAP server, and open the SAP Reference IMG by choosing
Tools > Customizing > IMG > Project Administration (transaction SPRO).
2. Display the SAP Reference IMG.
3. Choose Governance, Risk and Compliance.
4. Execute Activate Applications in Client.
To activate an application component:

1. Choose the New Entries pushbutton.
2. Select the application component from the dropdown list.
3. In the Active column, you must specify whether the application component is to be activated.
October 2012
4.3
Review Master Data
1. The Sales Quotation subprocess and the Verify order control have been created, and assigned to
the organization.
October 2012
Organization
The following graphic illustrates that the Wind Wagon Energy Ltd (China) organization has been
created.
The following graphic illustrates that the Verify order control has been created and assigned to the
Wind Wagon Energy Ltd (China) organization.
October 2012
The following graphic illustrates that the SOX regulation has been created and assigned to the
Verify order control.
The following graphic illustrates that the Sales Quotation subprocess has been created, and then
assigned to the Wind Wagon Energy Ltd (China) organization.
October 2012
4.4
4.4.1
Creating Continuous Controls Monitoring Data

Creating Data Source for PROCESS INTEGRATION
1. Navigate to Rule Setup > Continuous Monitoring > Data Source.

2. Choose Create button.
3. On the General tab, enter the Data Source name, and then set the Status field to In Review.
Note: Ensure that the Valid From date is correct. We recommend that you set it as the
valid from date of the master data.
4. On the Object Field tab, select Process Integration in the Sub Scenario field.
October 2012
5. Choose Proxy Lookup.

The Lookup window appears. The data is populated from the Process Integrator with existing
proxies.
6. Choose OK.
7. Choose Select Fields.
October 2012
8. In the window that appears, select fields for the Data Source that you want to monitor ensuring
that the query parameters and deficiency fields are selected, and then choose OK.
9. Choose Save.
10. Set the new data source as Active.
Choose the newly created data source.
Choose Open.
On the General tab, set the Status field to In Review and then Active.
Choose Save.
October 2012
The following graphic depicts the General tab of the data source.
The following graphic depicts the Object Field tab of the data source.
October 2012
4.4.2
Creating a Business Rule for Process Integration
1. Navigate to Rule Setup > Continuous Monitoring > Business Rules

2. Choose Create.
3. In the start window, choose Search Data Source.
Select Process Integration in the Sub Scenario field.
Search for, and then choose the data source you created in the previous section.
4. Choose Start.
5. Enter the Name, Description, Valid from, Valid to, Analysis Type, Deficiency Type fields.
Note: Ensure that the Valid From date is correct. We recommend that you set it as the
valid from date of the master data.
6. Set the Status field to In Review.
October 2012
10
7. Set the Filter Value for each Filter Field.

Note: The filter values are the input parameters for Process Integration Engine. Use
Empty to query all.
October 2012
11
8. Set Deficiency Criteria.
9. Create the SAP Process Integration Business Rule Output Format by selecting which fields
are visible and which are hidden from the output result.
October 2012
12
10. In the Technical Settings phase, choose Edit to modify the Max. No of Records to Analyze.
11. SAP Process Integration Business Rule Ad-hoc Query

a. You can test the Business Rule by running it from the Ad-hoc Query.
b. Enter Quarterly for the Timeframe and click Start
c.
Check the data to verify the rule setup.
12. You can upload a file or add a URL to this business rule object by choosing the Attachments
and Links phase.
13. Choose Save.
14. In the Confirmation phase, open the newly created business rule to make any additional
changes.
15. Set the new business rule status to Active.
Choose the newly created business rule.
Choose Open.
On the Basic Information tab, set the Status field to Active.
Choose Save.
4.4.3
Assigning the Business Rule to Controls
1. Navigate to Rule Setup > Continuous Monitoring > Business Rule Assignment.
2. Choose the organization by using F4 help.
3. Choose Search.
4. Choose the control Segregation of duties (Automated).
5. Choose Modify.
The Business Rules section will be in edit mode.
6. Choose Add, and then select the business rule you created in the previous section.
7. Choose Maintain Frequencies.
8. Choose both Monitoring and Compliance for Any Frequency
9. Choose Save.
October 2012
13
The following graphic depicts the result of the business rule assignment.
The Common Business Rules tab
October 2012
Data here could be shared by the regulations of this control.
14
The Regulation-Specific Business Rules tab
You can set one regulation to use its own specific business rules, or to use Common
Business Rules.
Relationship between Control and Business Rule Control Object View
Open the Control Object.
Go to the Business Rules tab of the control.

All business rules assigned to this control are listed here.
Relationship between Control and Business Rule Business Rule Object View
Open the Business Rule Object.
Go to the Controls tab of the business rule.

All controls with this business rule assigned are listed here.
4.4.4
Creating a Job in Automated Monitoring
1. Navigate to Rule Setup > Scheduling > Automated Monitoring.

2. Choose Create Job.
3. Choose Automated Monitoring Job for Job Type.
October 2012
15
4. Choose Start.
5. Enter the Job name, Execution Type, Frequency, Test Period From and Test Period To.
6. Select one Regulation from the drop down list.

7. Search for, and then select the Verify order control.
October 2012
16
8. Choose Save.
After choosing Save, the newly created Job Steps appear in Automated Monitoring Jobs list, as
shown in the following graphic:
October 2012
17
Alternately, choose Job Step Log to see job step execution details.
To view the Job Step results for Process Integration in Job Monitor:
1. Navigate to Rule Setup > Scheduling > Job Monitor.
2. Enter search criteria.
3. Enter the name of your job in the Job Name field, and then enter the Execution Date From and
Execution Date To.
4. Choose Search.
October 2012
18
5. Choose the Job Step you created for Process Integration.

6. Choose View Results to see the results of Process Integration analysis.
7. Choose Business Rule.

The business rule detailed information window appears.
October 2012
19
8. Click the hyperlinks in the Control and Issue Priority columns to see the Control and Issue
details.
Control Details:
October 2012
20
Issue Details:
October 2012
21
5. Copyright
2012 SAP AG. All rights reserved.
SAP Library document classification: PUBLIC
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 be changed 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, PowerPoint, Silverlight, and Visual Studio are registered
trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z,
System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems,
POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System
Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX,
Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered
trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered
trademarks of Adobe Systems Incorporated in the United States and other countries.
Oracle and Java are registered trademarks of Oracle and its affiliates.
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.
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri,
and Xcode are trademarks or registered trademarks of Apple Inc.
IOS is a registered trademark of Cisco Systems Inc.
RIM, Blackberry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch,
BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are
trademarks or registered trademarks of Research in Motion Limited.
Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile
Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google
Voice, Google Mail, Gmail, YouTube, Dalvik, and Android are trademarks or registered trademarks of
Google Inc.
INTERMEC is a registered trademark of Intermec Technologies Corporation.
Wi-Fi is a registered trademark of Wi-Fi Alliance.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
Motorola is a registered trademark of Motorola Trademark Holdings LLC.
Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, SAP HANA, 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 other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions,
Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as
well as their respective logos are trademarks or registered trademarks of Business Objects Software
Ltd. Business Objects is an SAP company.
October 2012
22
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products
and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Sybase, Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are registered trademarks of Crossgate
AC in Germany and other countries. Crossgate is an SAP company.
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.
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 SAP Group 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.
October 2012
23

PC10 Proc Integrtn

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PC10 Proc Integrtn

Uploaded by

Copyright:

Available Formats

Using the Process Integration

Subscenario for Continuous

Governance, Risk, and Compliance

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

Using the Process Integration-Driven Monitoring Subscenario

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

Using the Process Integration-Driven Monitoring Subscenario

Words or characters quoted

File and directory names and

User entry texts. These are

Variable user entry. Angle

Keys on the keyboard, for

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

Using the Process Integration-Driven Monitoring Subscenario

Background Information ..................................................................................................... 1

Step-by-Step Procedure ...................................................................................................... 2

Post-Installation Steps .................................................................................................. 2

Activating the PC Application ....................................................................................... 2

Review Master Data ..................................................................................................... 3

Creating Continuous Controls Monitoring Data ............................................................ 6

Creating Data Source for PROCESS INTEGRATION ..................................... 6

Creating a Business Rule for Process Integration ......................................... 10

Assigning the Business Rule to Controls ....................................................... 13

Creating a Job in Automated Monitoring ....................................................... 15

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

Using the Process Integration-Driven Monitoring Subscenario

PC 10.0 is based on SAP NetWeaver 7.02 SP 06 (or above) ABAP stack.

You have completed the following steps:

You have created and configured regulation(s)

You have created corporation and organization units

You have created the central process, subprocess, and controls

You have assigned proper regulation(s) to the control

You have assigned subprocesses or controls to the corporation or organization unit

You have configured connectors

You have created the following data:

The SAP NW Process Integrator system is ready.

The connection between GRC to PI system is created.

Process Integration proxy development is done.

The proxy must contain both import and export parameters.

The proxy import parameters are not table type.

Using the Process Integration-Driven Monitoring Subscenario

Activate the PC application

Configure controls and business rules

Activating the PC Application

Complete the following steps to activate the process control application:

To activate an application component:

Using the Process Integration-Driven Monitoring Subscenario

Review Master Data

Using the Process Integration-Driven Monitoring Subscenario

Using the Process Integration-Driven Monitoring Subscenario

Using the Process Integration-Driven Monitoring Subscenario

Creating Continuous Controls Monitoring Data

1. Navigate to Rule Setup > Continuous Monitoring > Data Source.

Using the Process Integration-Driven Monitoring Subscenario

5. Choose Proxy Lookup.

Using the Process Integration-Driven Monitoring Subscenario

Choose the newly created data source.

Using the Process Integration-Driven Monitoring Subscenario

Using the Process Integration-Driven Monitoring Subscenario

Creating a Business Rule for Process Integration