Total Pageviews

Saturday, 3 August 2013

Upgrade of GRC AC 5.3 to 10.1


The main steps to upgrade from 5.3 to 10 for Access Control are listed below: 
SAP provides a migration tool with capability to export data from existing Access Control 4/5.3 to Access Control 10.0
• Java-based versions 5.2/5.3 cannot be upgraded directly to ABAP-based version 10.0 due to the difference in platform
• The migration tool provides following functionalities:
- Automated process with limited manual effort
- Ability to transfer configuration data, which includes SAP connectors, RAR configuration parameters, ERM configuration parameters, as well as CUP configuration parameters
- Export master data, including user roles and rule sets
- Ability to export data onto a spreadsheet and customize it before import
- Flexibility to filter and modify data before export
• Ensure SAP NetWeaver is at least 7.0 SP11 and AC 5.3 SP13
• Access Control 5.2 will first need to be upgraded to version 5.3
• Complete the configuration in IMG for the SAP connectors and new components
- Refer to the GRC 10.0 Configuration Guide for more information
• Create appropriate owners/users within Access Control 10.0
• Create the appropriate Org. Unit to import the RAR data
• Before migrating CUP and ERM data, manually create all AC 5.3 custom fields in GRC 10.0 using identical names
• Activate Business Configuration Sets (BCSETS) for 10.0 based on details in the migration guide
• Upgrade the RTA in the ERP back end to the new GRC 10.0 plug-ins
For Process Control, it is a direct upgrade to the NW 7.02/7.31 and then the GRC 3.0 --> 10 upgrade.  There is a guide from SAP with all the details for PC 3.0 --> 10 upgrade. 

Thursday, 1 August 2013

Business Benefits of using GRC 10 over 5.3

GRC 10 provides the following advantages over 5.3 and can be presented as business case scenario ::
1.Only ABAP System All 3 Components ( AC,RM & PC) will be deployed in only one system
2.A lot of sharing now for Master Data , IMG Activities in between them because of the common technical platform NetWeaver ABAP.
3.Less Maintenance due to only ABAP System and more stability
4.Auditor’s delight as it includes all the features to track changes related to critical roles , profiles and transaction usage
5.SAP GRC Access Control 10.0 gives us a lot of flexibility to shape up a report in fact the view of the report in the system as well to fit our requirements or the viewer’s profile
6.Added flexibility to retrieve the data in form of pdf and crystal reports
7.Reduction in Total Cost of ownership for maintenance and support
8.Enhanced workflow management for User Access Provisioning
9.Reduction of servers

Configure Enterprise Portal with GRC 10.0

Steps to be followed for Configuring SAP Enterprise Portal connector in GRC
Access Control 10.0
1.Download GRC AC 10.0 software from Service Market Place.
2.Extract component GRCPIEP00_0.sca and deploy to the EP system using SDM.
3.Once deployed, you will see a web service called
GRACAuthMgmtServiceOutBinding in Web Service Navigator.
4.Now create a SM59 'G' type connector to point to the EP server.
5.Now create a SM59 'G' type connector to point to the EP Server but this
connector will point to the SPML service running on EP Server.
6.Maintain the logical port which point to the webservice
GRACAuthMgmtServiceOutBinding and will be used by SM59 connector created in
step 4 to locate the exact web service in EP.
7.In logical port, point the HTTP Destination to the connector created in
step 4.
8. Create two GRC connectors in IMG
a) Connector created in step 4 will have logical port created in step 6
as its 'Logical Port'.
b) Connector created in step 5 will have same name for 'Logical Port'.
9. Connector created in step 8.a will have connector created in step 8.b as
it's subsequent connector.

Extension of GRC 5.3 Warranty until 12/2015

Details for Product Version SAP GRC ACCESS CONTROL 5.3
Official Name: SAP GRC Access Control 5.3
Product: SAP ACCESS CONTROL
Type of Product Version: Add-On
Release Type: Standard Current
Status: Unrestricted available End of Mainstream Maintenance: 12/31/2015