10e98930-6924-2d10-c286-921f20e21f15

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15

http://slidepdf.com/reader/full/10e98930-6924-2d10-c286-921f20e21f15 1/38

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

© 2010 SAP AG

Applies to:

SAP BusinessObjects Process Control 3.0

Summary

This documentation provides the tips and tricks for Portal Installation for SAP BusinessObjects ProcessControl 3.0

Authors: Jennifer Cha and Debraj Roy

Company: Regional Implementation Group

Governance, Risk, and Compliance

SAP BusinessObjects Division

Created on: April 1st, 2010

Version 1.1

SAP BusinessObjects Process

Control 3.0 Portal Installation

Tips and Tricks

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15



© 2010 SAP AG

Document History

Document Version Description

1.10 Update after the review

1.00 First official release of this guide

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15



© 2010 SAP AG

Typographic Conventions

Type Style Description

Example Text Words or characters quoted

from the screen. Theseinclude field names, screen

titles, pushbuttons labels,

menu names, menu paths,

and menu options.

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

Icons

Icon Description

Caution

Note or Important

Example

Recommendation or Tip

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15



© 2010 SAP AG

Table of Contents

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

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

3. Prerequisites....................................................................................................................1

4. Connect Single Portal to Multiple Process Control Systems ........................................2

4.1 Create Custom Portal Content ..................................................................................2

4.1.1 Copy Portal Content .....................................................................................2

4.1.2 Set Permission for the Copied Portal Content ...............................................9

4.1.3 Configure Portal Content ............................................................................ 12

4.2 Create Groups with GRC PC Roles ......................................................................... 20

4.3 Assign User to Different User Group ....................................................................... 22 4.4 System Connection to PC Systems ......................................................................... 24

5. Default System Alias and Usage Type BI Java ............................................................ 31

5.1 Default System Alias ............................................................................................... 31

5.2 Usage Type BI Java ................................................................................................ 31

6. FAQ ................................................................................................................................ 31

7. Comments and Feedback ............................................................................................. 32

8. Appendix ........................................................................................................................ 33

9. Copyright ....................................................................................................................... 33

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


1. Business Scenario

SAP BusinessObjects Process Control 3.0 uses Enterprise Portal as user interface for enabling

members of audit and internal control teams to gain better visibility into key business processes, and

to ensure a high level of reliability in financial statement reporting.

2. Background Information

This documentation provides the tips and tricks for Portal Installation for SAP BusinessObjects

Process Control 3.0 to optimize the landscape with the existing hardware infrastructure. Such as

Single portal to multiple Process Control clients/systems*

Default system alias

Usage Type BI Java

*Note: It is recommended to have one portal connected to one PC system. SAP is only responsible

for the standard delivered portal content. Customers have to maintain all modified contents when

applying support packages and doing system upgrade.

3. Prerequisites

All the pre-requisites are checked and fulfilled according to “SAP BusinessObjects Process Control 3.0 Pre

Installation Guide”. And SAP BusinessObjects Process Control 3.0 has been installed or upgraded

successfully. Please refer to “SAP BusinessObjects Process Control 3.0 Post Installation Guide for New

Installation“ and “SAP BusinessObjects Process Control 3.0 Post Installation Guide for Upgrading from PC 2.5”.

http://www.sdn.sap.com/irj/bpx/go/portal/prtroot/docs/library/uuid/f031ea79-9d46-2c10-348e-fad341c7f3cb




http://www.sdn.sap.com/irj/bpx/go/portal/prtroot/docs/library/uuid/30ae9468-8c89-2c10-338b-af5a0d05cd03




http://www.sdn.sap.com/irj/bpx/go/portal/prtroot/docs/library/uuid/00ae81d5-3e8a-2c10-61b7-af280b77ecd5








8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


4. Connect Single Portal to Multiple Process

Control Systems

There are two scenarios of PC systems to connect to one single portal.

Scenario I: PC systems with different SID connects to one portal

Ex: GRD 100 and GRQ 100

Scenario II: PC systems on different clients of the same SID to one portal

Ex: GP5 100 and GP5 300

The following example uses scenario II for demonstration. And it is also suitable for scenario I.

Please see Section 6 FAQ for further detail discussion concerning support pack update, user store

synchronization and others.

4.1 Create Custom Portal Content

Copy the pre-delivered Process Control portal content to customer folder. Then perform the

configuration.

4.1.1 Copy Portal Content

Copy the pre-delivered Process Control portal content to customer folder.

1. Log on as Portal Super Administrator with Portal Content Admin, System Admin, and User Adminauthorization.

PC System 1(ex. GRD 100)

PC System 2(ex. GRQ 100)

Portal

PC System 1(ex. GP5 100)

PC System 2(ex. GP5 300)

Portal

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


2. Navigate to Content Administration > Portal Content > Browse > Portal Content.

3. Create a new Folder and put a custom folder name such as “GRCPC”. You could name it according

to customer’s system naming convention.

4. Click on Finish and close the wizard.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


5. Copy the GRC Process Control folder under “Portal Content > Content Provide by SAP” to the newly

created GRCPC folder.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


6. Copy the content once more time for the second PC system.

7. Finish and close.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


8. Update the folder name for different PC systems.

9. Change the folder name for first PC system. Save and Close.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


10. Change the folder name for second PC system. Save and Close.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


4.1.2 Set Permission for the Copied Portal Content

1. Open the Permissions object for the custom folder.

2. Search for the Groups of everyone.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


3. Add permission to Everyone Group and save.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


Click on Yes.

4. All folders should inherit the permission for Everyone Group. Here is the check for the permission of

the sub-folder.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


4.1.3 Configure Portal Content

Configure Portal Content to be used by different PC 3.0 systems.

4.1.3.1 System Alias

In order to distinguish the connection to different PC systems, the system alias has to be defined for

each PC system. The system alias information is kept inside the property of Web Dynpro iView

template.

1. Change the system alias of first PC system from the Web Dynpro iView template.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


2. Change the system to SAP_GRCSPC_100 and save.

3. Now we have done for Client 100 as shown in the above steps, we are going to perform the same

for Client 300.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


2. Open the Property Category of Information.

3. Change the Name for the role.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


4. Save and Close.

5. Perform the name changes for all other roles for first PC system.

6. Repeat the steps to perform the roles name change for second PC system.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


2. Double click on “GRC Process Control” to show the property.

3. Open the Property Category of Information and change the name.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


4. Save and Close.

5. Repeat the above step to perform the tab name change for all roles for both PC systems.

Example for PC system one:

Example for PC system two:

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


4.2 Create Groups with GRC PC Roles

...

1. Log on as Portal Super Administrator with Portal Content Admin, System Admin, and User Admin

roles.

2. Navigate to User Administration -> Identity Management. Create the groups for different PC

systems and assign the proper roles for the different groups.

3. Click on Create Group and put in the Unique Name and Description.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


4. Click on “Assigned Roles” tab.

5. Search for the “*GRC*ALL*” role. The default role, PC system one role, and PC system two role will

show up. Mouse over to the description of the role. The role tool-tip will show the full name of the

role.

6. Select the role and add.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


7. Save.

8. Repeat the above steps to create the groups for different PC systems with different roles.

4.3 Assign User to Different User Group

1. Log on to Portal with Portal Content Admin, System Admin, and User Admin authorization.

2. Navigate to User Administration > Identity Management. And search for the user that you want to

perform the assignment.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


3. Select the user and click on “Modify”.

4. Access Assigned Groups tab. Search for groups that this user should have.

5. Select the groups. Add and Save.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


6. Log on to Portal with this user. This user should have both tabs to access both PC systems.

sd

4.4 System Connection to PC Systems

The system connection has to be established from Portal to the two PC systems.

1. Log on to Portal with Portal Content Admin, System Admin, and User Admin authorization.

2. Navigate to System Administration > System Configuration -> System Landscape -> Browse ->

Portal Content.

3. Create the system under the custom folder.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


4. The following Property Categories and information have to be maintained:

Connector

User Management

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


Web Application Server (Web AS)

System Aliases

Note: Use the system alias that has been created for the different PC system.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


Permissions

Note: Double check to make sure the system could be access by Everyone Group.

5. Install Portal Certificate to PC systems. Please refer to “Section 4.3.3 Portal Certificate to GRC PC

System” of documentation SAP BusinessObjects Process Control 3.0 Post Installation Guide for New

Installation.







8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


6. Perform Connection Tests after the certificate of portal has applied to PC system.

7. Repeat the above steps to set up the system for second PC system.

Note: Make sure the system alias for the second PC system matches with name of the

customization. For example “SAP_GRCSPC_300”.

Tip: You could make a copy of first PC system connection and change the client number to point to

second PC system.

Here is the screen shot for the system connection test for second PC system.

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


5. Default System Alias and Usage Type BI Java

5.1 Default System Alias...

Here is the list of default system alias for Process Control, Risk Management, and BOE.

PC 3.0 RM 3.0 BOE

Default System Alias SAP_GRCSPC SAP_GRM For releases SP1 (and

below)

SAP_GRC_BOE

For RM releases SP2

(and higher)

SAP_GRC_RM_BOE

For PC releases SP2(and higher)

SAP_GRC_SPC_BOE

5.2 Usage Type BI Java...

In order to print the PDF report file from the ALV output data, usage type BI Java has to be installed.

You could use http://<hostname>:<port>/utl/UsageTypesInfo to check if usage type BI Java is

installed and refer to SAP Note 968236 Installing usage type BI Java subsequently/iView not found.

In case the BI Java usage type is not installed and you want to install it subsequently, please refer

to SAP Note 883948 NW 7.00(2004s): Inst.Add.Java Usage Types/Software Units.

6. FAQ

1. Is there any negative impact in having more that 2 PC systems/clients? Or this is a limitation?

[Feedback] There is no limitation on how many PC systems/clients that one portal could be

connected to. In a normal PC implementation system landscape design, use one portal to

connect to both DEV and QAS PC is doable. And it is recommended to use single production

portal for production PC system. Please refer to portal sizing documentation for hardware

requirement and the performance impact.

2. Is there any way to synchronize the user master from one PC client?

[Feedback] You could use Central User Management. Use the referenced PC client as the main

user store. Portal and other PC systems/clients will synchronize users automatically from the

reference PC client.

3. Will the portal be used for GRC only or it could be used for other than GRC solution? How will it be

impacted in applying support pack to the same portal system?

8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


[Feedback] As long as the portal has met the PC prerequisite, there is no limitation for GRC usage

only. And since the portal has meet PC prerequisite, there should be no impact for applying

Support pack to the portal.

4. Assume that PC client 100 is used for DEV and PC client 200 is used for QA. But, customer has a

restriction in applying the support pack for QA till certain time. How to overcome with such

situation?

[Feedback] This scenario will impact PC system more than Portal system. Portal is used as user

interface for PC. And there will not be any update for portal package after SP3. During the

system landscape design, customer’s change management process has put into consideration.

5. Should I perform backup for Portal before implementation any customizing?

[Feedback] Yes. It is common sense to backup the system before implementing the

customization.

6. Is it possible to undo the configurable and have only one portal support one PC system?

[Feedback] Yes. It is. Say, you only want to keep PC system one and delete the connection to PC

system two. You should do the following:

Unassign all portal user group of PC system two to users.

Delete all portal user group related to PC system two.

Delete the system to PC system two.

Delete the custom folder of PC system two.

7. Comments and Feedback

Your feedback is very valuable and will enable us to improve our documents. Please take a few

moments to complete our feedback form. Any information you submit will be kept confidential.

You can access the feedback form at:

http://www.surveymonkey.com/s.aspx?sm=stdoYUlaABrbKUBpE95Y9g_3d_3d

Both comments and feedback are very welcome. Please send them to:

Jennifer Cha RIG Process Control [email protected]

Debraj Roy RIG Process Control [email protected]



mailto:[email protected]





8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


8. Appendix

Appendix A – Guides

The documentation for SAP BusinessObjects Process Control 3.0 is available to customers on theSAP Help Portal at http://help.sap.com/BU, and includes: Application Help (PlainHTML)

Master Guide, Installation Guide, Operations Guides, Security Guides, UpgradeGuides, and Migration Guides in compliance with the SAP Documentation Standard.

You can also find this documentation on SAP Service Marketplace at:

http://service.sap.com/instguides -> SAP BusinessObjects -> Process Control -> Release 3.0

Release Notes

You can also find this documentation on SAP Service Marketplace at:

http://service.sap.com/releasenotes -> SAP BusinessObjects -> SAP BusinessObjects governance, risk, compliance (GRC) -> SAP BusinessObjects GRC Process Control -> Release

Notes SAP GRC Process Control 3.0

9. Copyright

© 2010 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 be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other softwarevendors.

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 of Adobe SystemsIncorporated 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 registeredtrademarks 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 byNetscape.

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 wellas 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 the trademarks of their respective companies. Data contained inthis document serves informational purposes only. National product specifications may vary.

http://help.sap.com/BU



http://service.sap.com/instguides


http://service.sap.com/releasenotes





8/8/2019 10e98930-6924-2d10-c286-921f20e21f15


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 beliable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are thosethat are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein shouldbe 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, theimplied 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 damagesthat 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 withinthese materials. SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third partyweb pages.

Any software coding and/or code lines/strings (“Code”) included in this documentation are only examples and are not intendedto be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasingrules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not beliable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

https://www.sdn.sap.com/irj/bpx/grc



10e98930-6924-2d10-c286-921f20e21f15

Documents

Transcript of 10e98930-6924-2d10-c286-921f20e21f15