Sap GRC Access Control and Configration
Sap GRC Access Control and Configration
First of all you have to import the SAP GRC Enterprise Role Management roles.
Next you have to handover the ERM Admin Role to the administrator.
After that you have to import the initial SAP GRC Enterprise Role Management configuration data.
Next you have to connect a standalone j2eee system to the remote SAP Server.
As soon as you are done with the installation process and after that you have to start the SAP Net Weaver J2EE server again, SAP GRC Enterprise Role Management will be installed and later it will start working.
If you want to import the SAP GRC Enterprise Role Management user roles with the help of UME you would have to do the following steps:
First of all you have to initiate the UME, now you ought to use the web browser which will further help you to connect and to log on to the SAP Net weaver J2 EE server.
After than you must have to click on the user management if you want to login in to the UME. Now click import. Now go to the directory in to which you have stored the SAP GRC Enterprise Role Management installation files with the help of using any kind of text editor. At last you have to open the file named re_ume_roles.txt. Now from there you have to select and copy all the contents of the file.
Hope this article might help you to understand the above issue.
As soon as you are done with the SAP GRC Risk Analysis and Remediation you must have to complete the following steps if you want to use it:
First of all you have to generate the SAP Java Connector (JCO) connections to the backend. After than you have to import the model data and Meta data for each and every single JCO end point with the help of SAP Net weaver Content administrator which is being included in the WebDynpro tools. Now generate the SAP UME which is known as User Management Engine and then allocate it to a user. Next you have to generate a master user source. Now initiate the background job daemon.
If you want to generate the JCo Connections to backend systems, you would have to generate one or more backend server connections, moreover there are too many ways to connect :
Three SAP Risk Analysis and Remediation 5.3 RTA backend SAP HR systems Three SAP GRC Risk Analysis and Remediation 5.3 RTA non-HR backend systems such as SAP Customer Relationship Management, SAP Product Lifecycle Management, and SAP Supply Chain Management. Fifteen SAP GRC Risk Analysis and Remediation Real-Time Agents (RTAs) To join numerous backend systems to your installation, you have to create a distinct JCo Comprises model data and metadata for every of those systems. destination
this you have to do the below steps 1. Allocate all SAP Process Control and SAP Risk Management users to the role SAP_GRC_FN_BASE to permit them to contact the SAP Process Control or SAP Risk Management applications. 2. Allocate the SAP_GRC_FN_ALL role to the user doing the Modifying of the product. This role is the power user role. It gives the chosen user the skill to see and do all without being allocated to an exact SAP Process Control or SAP Risk Management role. This role is characteristically allocated to the person who generates the organization assemblies and allocates business roles to all the other users. It covers all of the approvals from the role SAP_GRC_FN_BUSINESS_USER in addition to the following authorizations: Managerial functions in the SAP Process Control Implementation Guide (IMG), and the SAP Risk Management IMG Structure setup in skilled style Data upload for structure setup modifying table conservation for SAP Process Control and SAP Risk Management 10.1 Start of role task techniques Generating the First User in the ABAP System The role does not comprise the approvals for Workflow Modifying, Case Management, or Web services activation. For these approvals, use the role SAP_GRC_SPC_SETUP. Next you have to allocate the SAP_GRC_FN_ALL carefully, as soon as use is allocated to the role that is making universal alterations 3. If you want to generate the user you must have to use the transaction 4. If this user wants to obtain workflow announcements through e-mail, on the Address data tab, allocate an email address and a Comm. Meth of E-Mail to the user. 5. On the Roles tab, allocate the roles SAP_GRC_FN_BASE and SAP_GRC_FN_ALL to this user. This user can now use transaction SPRO to finish the configuration steps such as triggering the BC sets and allocating roles to other users.