PC10 Proc Integrtn

8/16/2019 PC10 Proc Integrtn

1/27

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2012 SAP LABS

Applies to:SAP® Process Control 10.0

SummaryThis User Guide provides information about Process Integration subscenario architecture, implementationrequirements, configuration instructions, and use case.

Team: Governance, Risk, and Compliance

Created on: 24 Oct 2012

Version 1.1

Using the Process IntegrationSubscenario for ContinuousMonitoring in Process Control


2/27

Using the Process Integration-Driven Monitoring Subscenario

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

© 2012 SAP LABS

Document History

Document Version Description

1.00 Initial Draft

1.10 Added notes emphasizing the significance of the „valid from‟ date of datasources and business rules


3/27



© 2012 SAP LABS

Typographic Conventions

Type Style Description

Example Text Words or characters quotedfrom the screen. Theseinclude field names, screentitles, pushbuttons labels,menu names, menu paths,and menu options.

Cross-references to otherdocumentation

Example text Emphasized words orphrases in body text, graphictitles, and table titles

Example text File and directory names andtheir paths, messages,names of variables andparameters, source text, andnames of installation,upgrade and database tools.

Example text User entry texts. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, forexample, F2 or ENTER .

Icons

Icon Description

CautionNote or Important

Example

Recommendation or Tip


4/27



© 2012 SAP LABS

Table of Contents

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

2. Background Information ..................................................................................................... 1 3. Prerequisites ........................................................................................................................ 1

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

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

5. Copyright ............................................................................................................................ 22


5/27


October 2012 1

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 sourceis one of several suitable for this purpose.

SAP Netweaver® Process Integrator (PI, formerly known as Netweaver XI) is SAP„s preferred platformfor integrations. PI supports common protocols such as JDBC and ODBC, and customers who havenon-SAP applications in their system landscape can use PI to either query directly against theunderlying 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 CreatingConnectors 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.

http://help.sap.com/pchttp://help.sap.com/pchttp://help.sap.com/pchttp://help.sap.com/pc


6/27


October 2012 2

4. Step-by-Step Procedure

4.1 Post-Installation Steps Activate the PC application Configure controls and business rules

4.2 Activating the PC ApplicationComplete the following steps to activate the process control application:

1. Log on to the NetWeaver ABAP server, and open the SAP Reference IMG by choosingTools > 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.


7/27


October 2012 3

4.3 Review Master Data

1. The Sales Quotation subprocess and the Verify order control have been created, and assigned tothe organization.


8/27


October 2012 4

Organization

The following graphic illustrates that the Wind Wagon Energy Ltd (China) organization has beencreated.

The following graphic illustrates that the Verify order control has been created and assigned to theWind Wagon Energy Ltd (China) organization.


9/27


October 2012 5

The following graphic illustrates that the SOX regulation has been created and assigned to theVerify order control.

The following graphic illustrates that the Sales Quotation subprocess has been created, and thenassigned to the Wind Wagon Energy Ltd (China) organization.


10/27


October 2012 6

4.4 Creating Continuous Controls Monitoring Data

4.4.1 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. N o t e : 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.


11/27


October 2012 7

5. Choose Proxy Lookup .

The Lookup window appears. The data is populated from the Process Integrator with existingproxies.

6. Choose OK .

7. Choose Select Fields .


12/27


October 2012 8

8. In the window that appears, select fields for the Data Source that you want to monitor ensuringthat 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 .


13/27


October 2012 9

The following graphic depicts the General tab of the data source.

The following graphic depicts the Object Field tab of the data source.


14/27


October 2012 10

4.4.2 Creating a Business Rule for Process Integration1. Navigate to Rule Setup > Continuous Monitoring > Business Rules2. 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.

N o t e : 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.


15/27


October 2012 11

7. Set the Filter Value for each Filter Field .N o t e : The filter values are the input parameters for Process Integration Engine. UseEmpty to query all.


16/27


October 2012 12

8. Set Deficiency Criteria .

9. Create the SAP Process Integration Business Rule Output Format by selecting which fieldsare visible and which are hidden from the output result.


17/27


October 2012 13

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 Attachmentsand 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 A c t i v e .

Choose Save .

4.4.3 Assigning the Business Rule to Controls1. 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.


18/27


October 2012 14

The following graphic depicts the result of the business rule assignment.

The Common Business Rules tab

– Data here could be shared by the regulations of this control.


19/27


October 2012 15

The Regulation-Specific Business Rules tab

– You can set one regulation to use its own specific business rules, or to use CommonBusiness 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 Monitoring1. Navigate to Rule Setup > Scheduling > Automated Monitoring.

2. Choose C reate Job .

3. Choose Automated Monitoring Job for Job Type.


20/27


October 2012 16

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.


21/27


October 2012 17

8. Choose Save .

After choosing Save , the newly created Job Steps appear in Automated Monitoring Jobs list, asshown in the following graphic:


22/27


October 2012 18

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 .


23/27


October 2012 19

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.


24/27


October 2012 20

8. Click the hyperlinks in the Control and Issue Priority columns to see the Control and Issuedetails.

Control Details:


25/27


October 2012 21

Issue Details:


26/27


October 2012 22

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 theexpress 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 softwarecomponents of other software vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registeredtrademarks 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, SystemStorage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX,Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registeredtrademarks 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 registeredtrademarks 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 aretrademarks 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.

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 aretrademarks 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, GoogleVoice, Google Mail, Gmail, YouTube, Dalvik, and Android are trademarks or registered trademarks ofGoogle 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 theirrespective 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 aswell as their respective logos are trademarks or registered trademarks of Business Objects SoftwareLtd. Business Objects is an SAP company.


27/27


Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase productsand services mentioned herein as well as their respective logos are trademarks or registeredtrademarks 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 specificationsmay vary.

These materials are subject to change without notice. These materials are provided by SAP AG andits affiliated companies ("SAP Group") for informational purposes only, without representation orwarranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to thematerials. The only warranties for SAP Group products and services are those that are set forth in theexpress warranty statements accompanying such products and services, if any. Nothing herein shouldbe construed as constituting an additional warranty.

Date post:	05-Jul-2018
Category:	Documents
Upload:	sankar-nayak
View:	224 times
Download:	0 times

PC10 Proc Integrtn

Documents