Creating Connectors in

Process Control 10.0

Applies to:
SAP BusinessObjects Process Control 10.0

Summary
Most continuous monitoring scenarios require the creation and configuration of Remote Function Call (RFC)
destinations (or connectors).

Team:

Governance, Risk, and Compliance

SAP BusinessObjects Division

Created on:

14 February 2012

Version 1.0

SAP COMMUNITY NETWORK

2011 SAP AG

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

Document History
Document Version

Description

1.00

Initial release

SAP COMMUNITY NETWORK

2011 SAP AG

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

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.

SAP COMMUNITY NETWORK

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

Table of Contents
1.

Business Scenario ..........................................................................................................1

2.

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

3.

Prerequisites....................................................................................................................1

4.

Creating Connectors .......................................................................................................2

4.1

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

4.1.1 ABAP Report Subscenario ............................................................................6
4.1.2 SoD Integration Subscenario ........................................................................7
4.1.3 BW Query Subscenario ................................................................................8
4.1.4 Configurable Subscenario .............................................................................9
4.1.5 Event-Driven Monitoring Subscenario .........................................................10
4.1.6 External Partner Integration Subscenario ....................................................10
4.1.7 Process Integration Subscenario.................................................................11
4.1.8 Programmed Subscenario ..........................................................................11
4.1.9 SAP Query Subscenario .............................................................................12

SAP COMMUNITY NETWORK

2011 SAP AG

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

Creating Connectors in Process Control 10.0

1.

Business Scenario

This document contains instructions for creating connectors.

2.

Background Information

In Process Control 10.0, creating and configuring connectors is a prerequisite to using many of the
continuous monitoring subscenarios. There are different types of connectors:
Local system connectors are used to integrate with the Access Control application for
monitoring segregation of duty violations.
Web service connectors are used for external partner data sources.
SAP system connectors are used in all other cases.

3.

Prerequisites

The system requirements to create connectors are as follows:

Process Control 10.0
Monitored system must be based on NetWeaver (4.6c to 7.10) with the SAP GRC 10.0
NetWeaver plug-in installed

Februar 2012

Creating Connectors in Process Control 10.0

4.

Creating Connectors

A Remote Function Call (RFC) is an interface for communication between an SAP client and server to
external programs and data. The interface can enable function calls to SAP systems or external
systems.
Most subscenarios for Continuous Monitoring require a connector. The general steps are outlined in
the next section, followed by any specific steps required for each subscenario.

4.1
1.
2.
3.
4.
5.

Post-Installation Steps
Open the SAP Reference IMG by entering the transaction code SPRO in the PC backend.
Display the SAP Reference IMG.
Choose Governance, Risk and Compliance.
Choose Common Component Settings, and then choose Integration Framework.
Choose Create Connectors (transaction code SM59).

The Configuration of RFC Connections window appears.

Februar 2012

Creating Connectors in Process Control 10.0

This an example of an ABAP Connector.

After creating connectors, verify that Connection Test and Remote Logon are functional.
6. Once the connectors are created from the PC to the RTA system and from the RTA system to
the PC system, verify that they are functional. To do this, choose Maintain Connectors and
Connection Types (transaction SPRO in the PC backend).

7. Choose Connection type definition.

Februar 2012

Creating Connectors in Process Control 10.0

NOTE: Choose Create New Entries to first define the Connection Type.
8. Select SAP as the Connection Type for the ABAP report, Configurable, Programmed, SAP
Query, and BI Query subscenarios. The following example creates an ERP system connector.
9. Choose Save.

10. Choose Define Connectors.

11. Choose the New Entries pushbutton.
12. Define your ERP system as the Target Connector and your PC system as the Source
Connector.
The Target Connector is the system you need to monitor. The Source Connector is the PC
system, which is required in asynchronous communication for the Target system to call back
to the PC system.

Februar 2012

Creating Connectors in Process Control 10.0

13. Choose Save.

14. Choose Maintain Connection Settings.

The Determine Work Area Entry window appears.

Februar 2012

Creating Connectors in Process Control 10.0

15. Enter AM in the Work Area field of the Determine Work Area Entry screen.
16. Choose the Continue pushbutton.

17. Choose Subscenario Definition.

18. Choose the New Entries pushbutton.
19. Define the subscenario and its descriptive text, and then choose Save.

4.1.1

ABAP Report Subscenario

To create and configure connectors for the ABAP Report subscenario, first follow steps 119 in
section 4.1.
1. Select the ABAP_REPORT subscenario.

Februar 2012

Creating Connectors in Process Control 10.0

2. Choose Scenario-Connector Link. The settings are automatically populated by the system.
3. Enter target connectors and system type for the ABAP REPORT subscenario.
4. Choose Save.

4.1.2

SoD Integration Subscenario

To create and configure connectors for the SoD Integration subscenario, first follow steps 119 in
section 4.1.
1. Select AM_SOD. The settings are automatically populated by the system.

2. There is no SoD connector since it uses the local system.

Februar 2012

Creating Connectors in Process Control 10.0

4.1.3

BW Query Subscenario

To create and configure connectors for the BW Query subscenario, first follow steps 119 in section
4.1.
1. Select BW Query.

2. Select Scenario-Connector Link, and then enter the connectors and system type which have
BW query installed. (In this example, enter PE2, Q76, Q78, and R51.)

3. Choose Save.

Februar 2012

Creating Connectors in Process Control 10.0

4.1.4

Configurable Subscenario

...

To create and configure connectors for the Configurable subscenario, first follow steps 119 in section
4.1.
1. Select the Configurable sub scenario.

2. Choose Scenario-Connector Link.

3. Enter the connectors which are set to the subscenario. The example connectors are shown
below.

Februar 2012

Creating Connectors in Process Control 10.0

4. Choose Save

4.1.5

Event-Driven Monitoring Subscenario

...
no acti onn eed edf or c onnector s fo reve nt- base d m onito ring.

No action is needed for connectors for event-driven monitoring.

4.1.6

External Partner Integration Subscenario

...

To create and configure connectors for the External Partner Integration subscenario, first follow steps
119 in section 4.1.
1. Select GL_MQT.

2. Choose Scenario-Connector Link.

3. Enter the Target Connector and Connection Type.

Februar 2012

10

Creating Connectors in Process Control 10.0

4. Choose Save.

4.1.7

Process Integration Subscenario

...

There is no Scenario Connector Link for the Process Integration subscenario

4.1.8

Programmed Subscenario

...

To create and configure connectors for the Programmed subscenario, first follow steps 119 in section
4.1.
1. Select Programmed.

2. Choose Scenario-Connector Link.

3. Enter the Target Connector and Connection Type.

4. Choose Save.

Februar 2012

11

Creating Connectors in Process Control 10.0

4.1.9

SAP Query Subscenario

...

To create and configure connectors for the SAP Query subscenario, first follow steps 119 in section
4.1.
1. Select SAP Query.
2. Choose Scenario-Connector Link.
3. Enter the Target Connector and Connection Type.

4. Choose Save.

Februar 2012

12

Creating Connectors in Process Control 10.0

5. Copyright
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 United States and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are 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, iPod, 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

Creating Connectors in Process Control 10.0

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.
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 AG 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.