An Overview of the New Harmonized Version 10.0 of SAP BusinessObjects GRC Solutions

  • by Frank Rambo, PhD, Director, Customer Solution Adoption (CSA), EMEA
  • July 7, 2011
Learn about key improvements of version 10.0 of SAP BusinessObjects GRC solutions. They include the considerably simplified system architecture, owing to recoding of the SAP BusinessObjects Access Control application on the ABAP stack, the harmonization across all levels from the look and feel of the user interface to the data model, and even deeper integration of the components coming with many new features.
Key Concept
With version 10.0 of SAP BusinessObjects GRC solutions, the release cycles of all SAP BusinessObjects GRC applications have been synchronized for the first time, and the SAP BusinessObjects Access Control application has been recoded and brought back to the ABAP stack without losing any of its version 5.3 features.

Companies that want to implement multiple SAP BusinessObjects GRC applications may be able to lower their total cost of ownership (TCO) by reaping the following benefits offered by version 10.0 of SAP BusinessObjects GRC solutions’ significantly simplified system component architecture:

  • Delivery of version 10.0 of SAP BusinessObjects Access Control, version 10.0 of SAP BusinessObjects Process Control, and version 10.0 of SAP BusinessObjects Risk Management as a single highly harmonized software component running on a single server.
  • No SAP NetWeaver Portal is required.
  • No SAP BusinessObjects server components such as SAP BusinessObjects Explorer (BOE) XI 3.1 for Crystal Reports are required anymore because the required server components for standard reporting were embedded in SAP NetWeaver Application Server ABAP 7.0 Enhancement Pack (EHP) 2.
  • SAP BusinessObjects Process Control and SAP BusinessObjects Access Control share the same plug-ins in your target SAP systems.
  • There are fewer individual system components to patch.

In addition to a simplified overall architecture, the SAP BusinessObjects Access Control application has internally been harmonized. The former release’s redundancies have been removed, including multiple creation of connectors pointing to the same system or master data elements (e.g., business processes or functional area) in risk analysis and remediation (RAR), compliant user provisioning (CUP), enterprise role management (ERM), and superuser privilege management (SPM). The four constituent application components run now as different capabilities in a single monolithic application. They can’t be distributed over multiple application servers anymore, as was formerly possible in release 5.3. Thus, the names RAR, CUP, ERM, and SPM have been retired. The capabilities are now referred to as Access Risk Analysis, Access Request Management, Business Role Management, and Emergency Access Management, respectively.

Frank Rambo, PhD

Frank Rambo, PhD, is managing a team within SAP’s Customer Solution Adoption (CSA) organization working with customers in the SAP analytics area with the objective to drive adoption of new, innovative solutions. Prior to this position, he worked eight years for SAP Germany as a senior consultant focusing on SAP security and identity management. Before he joined SAP in 1999, Frank worked as a physicist in an international research team. He lives in Hamburg, Germany.

See more by this author


Comments

No comments have been submitted on this article. 


Please log in to post a comment.

To learn more about subscription access to premium content, click here.