Expand +



Guidelines for consolidating SAP BusinessObjects GRC solutions

by The Tip Doctor

September 10, 2010

This tip was taken from the presentation “Technical Landscape and Architecture Requirements for Implementing SAP BusinessObjects GRC Solutions,” presented by Kurt Hollis, Deloitte Consulting, at the GRC 2010 conference in Orlando. 

There’s good news for customers who are running multiple SAP BusinessObjects SAP solutions and wish to consolidate them.  In the past, running the full suite of GRC solutions required 6 separate systems to accommodate ABAP and Java stacks individually.  Now, common components can be consolidated.  ABAP and Java components, while still separate stacks, can share the same server. This greatly simplifies the tasks of preparing and maintaining the SAP landscape for GRC solutions.

 SAP BusinessObjects GRC applications can run together as follows:

SAP BusinessObjects Process Control and SAP BusinessObjects Risk Management may run on a physical server with other applications, as long as the server has the resource capacity available to handle the sizing load for the customer need overall, plus any other applications running on that server.

SAP BusinessObjects Process Control 3.0 and SAP BusinessObjects Access Control 5.3 can run together on the same SAP NetWeaver system (separate stacks!) provided that the server has adequate resources to handle the additive sizing load calculated for each system. NOTE: Be sure to consider the memory size!

SAP BusinessObjects Process Control and SAP BusinessObjects Risk Management require a Java stack for SAP NetWeaver Portal support,  which can reside and share the same Java stack running Acce ss Control.

SAP BusinessObjects Process Control and SAP BusinessObjects Risk Management portal applications can be deployed on existing SAP NetWeaver Portals; otherwise, a separate portal installation is required.

One important thing to note: Sharing Java stacks may require the installation of additional usage types such as BI Java, EP, or EP Core if they are not currently installed.

There are special considerations you must keep in mind if you are running global trade services (GTS) functionality:

Best practice is to install a separate SAP NetWeaver 7.0 system for GTS as recommended by SAP

GTS SLL-LEG main core component is only supported on SAP NetWeaver 7.0 currently, not on SAP enhancement package 1

GTS SLL-LEG depends on SAP AP_700 component which must be installed first

A possibility exists to install GTS into a separate client in an existing SAP ERP system

SAP ERP system needs to be SAP ERP 6.0 based on SAP NetWeaver 7.0

Life cycle of SAP ERP and GTS may change and a need to upgrade to different SAP NetWeaver versions in the future may occur

GTS SLL-PI supported on all SAP ERP systems from 4.6C to SAP ERP 6.0 EHP4 +

SAP enhancement packages can also affect your GRC landscape.  They are compatible with SAP BusinessObjects GRC solutions as follows:

The Process Control RTA is currently compatible with SAP ERP 6.0 and SAP enhancement package 2, 3, or 4

SAP BusinessObjects Access Control RTA:

VIRSANH – Supported on SAP NetWeaver 7.0, 7.01, 7.10 based systems and supported with ERP EHP 2, 3, or 4

VIRSAHR – Supported on SAP ERP 6.0 with EHPs because SAP_HR remains 600 version

Global Trade Services SLL PI – Supported on SAP ERP 6.0 with EHP 2, 3,
or 4

You should install the core SAP BusinessObjects GRC solutions components on SAP NetWeaver 7.0 SAP enhancement package 1 system (except for Global Trade Services)

Find out how you can take advantage of additional GRC education at the upcoming GRC 2010 event in Barcelona ( or GRC 2011 US conference in Las Vegas (

An email has been sent to:

More from SAPinsider


Please log in to post a comment.

No comments have been submitted on this article. Be the first to comment!