GRC AC 5.3 - RAR Parameters

Hello,
I have the following 8 queries related to GRC AC 5.3 RAR parameters
When I go into RAR -> Configuration -> Miscellaneous, I see the following entries.
Maximum Display Lines For Print Preview 
This parameter specifies the maximum number of lines to be displayed in print preview mode; the default value is 500
1- What is the Print Preview of the lines for? Can I make it 10000 instead of 500. Is there a performance impact?
Background Job Spool File Location 
This parameter specifies the location where the background job spool files are stored Note: You need to restart the server
2- Why do I need the Background Job Spool File location? Is it when I use Default Logger parameter as SAP Logger? Currently we are using the Default Logger parameter as Java Logger
Alert Log File Name and Location 
This parameter specifies the location where the action usage purged data files are stored
3- Whey do I need this Alert Log file parameter for? I mean how is the Alert Log file generated in RAR 5.3
SAP Application Server Location 
Enter SAP application server location here
4- Why do I need SAP Application Server Location, when I have installed SAP GRC 5.3 on standalone SAP JAVA Stack?
FTP Site Location 
Enter FTP site location here
5- What should the FTP site location be given as? Should I give a fully qualified domain for a particular host for the FTP of above RAR background job log files and RAR Alert log files?
6- Do we have the background job log files FTP into another host, if Default Logger parameter is chosen as SAP Logger?
FTP Site User Name 
Enter FTP site User Name here
7- What is the best practice for specifying a FTP User? I mean what is the username normally given in RAR environment?
8- Is there any OSS Note, SAP Help URL which  describes about RAR parameters in detail?
Thanks,
Haleem

Hi,
> Maximum Display Lines For Print Preview 
>  This parameter specifies the maximum number of lines to be displayed in print preview mode; the default value is 500
>
> 1- What is the Print Preview of the lines for? Can I make it 10000 instead of 500. Is there a performance impact?

You should used 500 only.
> Background Job Spool File Location 
> This parameter specifies the location where the background job spool files are stored Note: You need to restart the server
>
> 2- Why do I need the Background Job Spool File location? Is it when I use Default Logger parameter as SAP Logger? >Currently we are using the Default Logger parameter as Java Logger

No, background job spool file location is something different from logger. Background spool file location is the location where
spool file of your background job will be generated.
Diferent between Java Logger and SAP Logger is that if you choose SAP Logger then log file of your RAR will be generated in NWA. But if you will choose as Java Logger then log file will be generated as separate file as ccappcomp.<n>.log which you will see in CC debugger.
> Alert Log File Name and Location 
> This parameter specifies the location where the action usage purged data files are stored

> 3- Whey do I need this Alert Log file parameter for? I mean how is the Alert Log file generated in RAR 5.3
>
check below link:
Compliance Calibrator Alert Generation Issue
> SAP Application Server Location 
>  Enter SAP application server location here

> 4- Why do I need SAP Application Server Location, when I have installed SAP GRC 5.3 on standalone SAP JAVA Stack?
>
> FTP Site Location 
>  Enter FTP site location here
>
> 5- What should the FTP site location be given as? Should I give a fully qualified domain for a particular host for the FTP of above RAR background job log files and RAR Alert log files?
> 6- Do we have the background job log files FTP into another host, if Default Logger parameter is chosen as SAP Logger?
>
> FTP Site User Name 
>  Enter FTP site User Name here
>
> 7- What is the best practice for specifying a FTP User? I mean what is the username normally given in RAR environment?
The following new reports can have long runtimes:
- User Authorization Count
- Role Authorization Count
- List Expired and Expiring Roles for Users
- For that reason These jobs run on ABAP side and produce a spool file. An icon is displayed on the front-end for the jobs that complete. (If you run jobs on all systems and it finishes on one system before another the icon will display for the finished system first)
- The report directory on the SAP Enterprise Resource Planning (ERP) application servers. This is the temporary storage location for spool files generated by these background jobs.
- The same directory name is used for all SAP backend systems.
- The location, user name, and password for FTP of security reports generated by backend SAP ERP systems.
> 8- Is there any OSS Note, SAP Help URL which  describes about RAR parameters in detail?
Note 1121978 - Recommended settings to improve peformance risk analysis
Check below link for performance optimization of RAR:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90aa3190-8386-2b10-c4ba-ced67322ea6d?quicklink=index&overridelayout=true
Thanks
Sunny

Similar Messages

  • Running Analysis in GRC AC 5.3  - RAR

    Hi,
    Can anyone let me know how to resolve the issue.
    When i run the Risk Analysis in GRC AC 5.3 - RAR
    Informer>Risk Analysis> Role Analysis--> Execute
    This is the error message it gives:-
    *VIRSAHR_01: Cannot execute BAPI RoleList: Error connecting using JCO.Client: null: Could not create JCOClientConnection for logical System: VIRSAHR_01_MODEL - Model: class com.virsa.cc.modelvirsahr_01.BAPI_VIRSAHR_01. Please assure that you have configured the RFC connections and/or logical system name properly for this model!: Error while obtaining JCO connection.: Failed to resolve JCO destination name 'VIRSAHR_01_MODEL' in the SLD. No such JCO destination is defined in the SLD. *
    Please indicate what could be the possible solution for it.
    Thanks in advance.
    Nazeer

    HI ,
    Why dont you check the SLD is running fine or not.These are the steps to be followed ,
    Check out the URL : http:
    <localhost>:50000/sld
    When you enter the sld screen then click on administration and there you will see whether sld server is running or not.If it is stopped then start.
    Then check whether in visual administrator check for sld data supplier under server node under services node.There on the top there will be a button as trigger sld data supplier .We should get a succesul message.
    In the Jco connections click on test option one should get a test message succeful.To see the JCo connections path launch j2ee home page URL : http:
    <localhost>:50000/.After that click on web dynpro then on content administrator and then maintain JCo connections.There check out the JCo connections.IF the JCo connections are not working fine then check out the RFC 'c configured in the backend system are testing successfully.
    SLD_UC
    SLD_NUC
    LCRSAPRFC
    SAPSLDAPI
    If u still face any problem plz let me know.

  • SAP GRC AC 5.3 RAR Background jobs are cancelled

    Hi Experts,
    we have newly implemented theS AP GRC AC 5.3 RAR  Help me in troubleshooting the Background jobs cancellation in SAP GRC AC5.3 RAR.. we have reported this issue to customersupport they asked us to upgrade the front end  patch level to Sp15, even we upgraded still i have the same problem.. later we upgraded the backend patch  according to the SAP Note. still the problem is not resolved.
    Latest recommendation they are asking us to uninstall the SMD agent.. and also my java control.exe is showing yellow color
    help me how to resolve the issue.??
    Edited by: n.s.k mohan on May 10, 2011 6:21 AM

    Hi,
    Could you please first change RAR log settings to Java logger then take a restart of the system. After that log for your background will start coming in RAR. Then schedule the job if it fails then paste background job log here.
    Also, in future, please raise GRC related issue in GRC forum so that you can get more replies.
    Thanks
    Sunny

  • GRC-AC 5.3 RAR Management view error - Expired users not cleaned-up.

    Hello Gurus,
    I have a problem in RAR Management View:  Users who was valid have been analyzed and their conflicts considered in statistics, but when they become expired, their conflicts remain in the statistics forever, because they are not re-analyzed neither in Full nor in Incremental sync.    Even if all roles are removed from the user in backend, the conflicts remain in Management View.
    I think the Full Batch Risk Analysis should clean-up all users violations from current period statistics before recording the new analysis results. 
    Did you have this problem too?  Am I missing something? 
    I appreciate your thoughts about it.
    Vaner

    Hello Nuno,
    Thanks for your comments.
    My release is 5.3 SP 16.2.
    I also think the full sync should be enough but I already find about 20 users with problems, in 4 different backend and in 2 GRC (Tests and Production)
    I think that depending on some procedures done in the back-end the full sync do neither re-analyze the user nor clean-up previuos statistics, for example:
    1. A user was delete and recreated again with option to maintain old data, and he already had expiration date.
    2. A sand-box environment was created as copy of production, users were created valid but already with expiration date.
    I observed that for these scenarios, there was no Change Document for field "valid to", my guess is that Full Sync process relies on Change Documents to do its job.
    I already opened a message in SAP for this, first level could not solve it, It is in Development Team now.
    Vaner

  • Query on Installation of GRC AC 5.3 RAR component

    Hi,
    We are implementing SAP GRC 5.3 - RAR Component. Can the tool needs to be implemented in the SAP Server itself or can it be installed in a different server other than SAP.
    Can GRC tool be installed in a different server but falling under the same system landscape directory?
    In future  we are also planning to go for the other components of GRC like CUP, SUPM & ERM. In that scenario, does these components also needs to be installed in SAP Server itself.
    Please suggest the SAP best practice of installation of SAP GRC 5.3
    Request the experts to reply at the earliest.
    Thanks and Best Regards,
    Srihari.K

    Hi Srihari,
    I agree with Frank and you need to go to SAP Service Market Place and check out the Installation and Configuration guides for SAP GRC 5.3 at https://service.sap.com/instguides.
    I also recommend to go through these articles published on SDN.
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/408bd039-d9c1-2a10-0fab-a92b97c7cd25
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a07b4cc8-1a57-2b10-1798-d2fec068473a
    Hope this helps as a good starting point for learning about SAP GRC Installation reqs.
    Regards,
    Kiran Kandepalli.

  • Moving connections of GRC AC 5.3 RAR with R/3 ABAP Client (same SID)

    Dear All,
    Please can someone assist me with the documentation for the movement of the connection of AC 5.3 RAR based on Java, from one client in R/3 ABAP to another.
    For e.g. if GRC AC 5.3 is connected to QAS Client 101 on ABAP side, how to move the connection to Client 102 on the same system (SID).Also, mention please, if there are any specific steps to carried out for removal of existing connection.
    Regards,
    Prashant

    Usually you don't move a connection, as the analysis results and the naming reflect the target system.
    I don't know your specific context, but let's asusme you're finished working with the test system and want to add the production system.
    From SP10, RAR has a feature to delete a connector and all related data (Careful! Be sure to back up your rule set before you do that!).
    You would then create the new connector, add it to the logical system, create the rules, plan the sync and analysis jobs and you're good to go.
    If that's not what you're looking for, please tell us a few nmore details.
    Frank.

  • GRC AC 5.3 RAR: Change system connector entry

    Just a tip:
    I had a problem after upgrading from RAR 5.2 where the previous connector entry wasn't named the same as it is in the SLD, so I had to change the connector.  We have a lot of information in our RAR system, so I didn't want to clean the database and start over, I just wanted to change the name of the connector.  Therefore, I used the following SQL query to rename it across the whole application.  You can input the RENAMED SYSTEM to whatever you want your rename to be, and of course input the SID of the system for the database schema.  This is for SQL Server 2005, but you can adapt it to your flavor.
    update SAP<SID>DB.VIRSA_CC_ACTRULE set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ACTUSAGE set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ACTVL set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ALLASTRUN set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ALLISTDTL set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ALTCDLOG set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ANLACT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ANLPRM set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_AUTHMAP set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRACT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRACTT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRACTVL set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRPRM set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRPRMVL set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRPROF set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRPROFT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRROLE set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRROLET set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRROLEVL set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_DATAEXD set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_EXLOBJ set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_FLDMAP set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_FUNCACT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_FUNCPRM set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_FUNCSYS set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_GENACT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_GENOBJ set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_GENOBJT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_GENPRM set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_GENUSR set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_GPRMLIST set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_LASTRUN set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_LSYSGRP set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_LSYSGRP set LVSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_MGALERTS set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_MGCRTR set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_MGMTBU set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_MGMTTOT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_MGRISKD set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_MGRISKS set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_MITRPT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_MTGENOBJ set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_MTGENOBJH set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ORAEXT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ORGUSERS set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_PRMRULE set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_PRMVL set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ROLEVL set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SCHEDFORK set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SUPP_DET set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SUPP_HDR set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SUPP_TEXT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SYSCRACT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SYSCRACT set PVSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SYSHMAP set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SYSRULE set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SYSSAPOBJ set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SYSTEM set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SYSTEMC set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SYSTEMT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SYSUSR set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_TEXTKEY set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_USRMAP set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_XSRULEMAP set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_XSRULEMAP set PVSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_XSRULEMAP set LVSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_XSYSGRP set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_XSYSGRP set XVSYSKEY = 'RENAMED SYSTEM'

    Just a tip:
    I had a problem after upgrading from RAR 5.2 where the previous connector entry wasn't named the same as it is in the SLD, so I had to change the connector.  We have a lot of information in our RAR system, so I didn't want to clean the database and start over, I just wanted to change the name of the connector.  Therefore, I used the following SQL query to rename it across the whole application.  You can input the RENAMED SYSTEM to whatever you want your rename to be, and of course input the SID of the system for the database schema.  This is for SQL Server 2005, but you can adapt it to your flavor.
    update SAP<SID>DB.VIRSA_CC_ACTRULE set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ACTUSAGE set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ACTVL set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ALLASTRUN set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ALLISTDTL set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ALTCDLOG set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ANLACT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ANLPRM set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_AUTHMAP set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRACT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRACTT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRACTVL set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRPRM set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRPRMVL set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRPROF set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRPROFT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRROLE set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRROLET set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_CRROLEVL set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_DATAEXD set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_EXLOBJ set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_FLDMAP set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_FUNCACT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_FUNCPRM set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_FUNCSYS set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_GENACT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_GENOBJ set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_GENOBJT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_GENPRM set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_GENUSR set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_GPRMLIST set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_LASTRUN set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_LSYSGRP set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_LSYSGRP set LVSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_MGALERTS set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_MGCRTR set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_MGMTBU set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_MGMTTOT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_MGRISKD set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_MGRISKS set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_MITRPT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_MTGENOBJ set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_MTGENOBJH set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ORAEXT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ORGUSERS set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_PRMRULE set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_PRMVL set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_ROLEVL set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SCHEDFORK set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SUPP_DET set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SUPP_HDR set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SUPP_TEXT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SYSCRACT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SYSCRACT set PVSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SYSHMAP set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SYSRULE set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SYSSAPOBJ set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SYSTEM set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SYSTEMC set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SYSTEMT set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_SYSUSR set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_TEXTKEY set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_USRMAP set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_XSRULEMAP set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_XSRULEMAP set PVSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_XSRULEMAP set LVSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_XSYSGRP set VSYSKEY = 'RENAMED SYSTEM'
    update SAP<SID>DB.VIRSA_CC_XSYSGRP set XVSYSKEY = 'RENAMED SYSTEM'

  • GRC AC 5.3 - RAR executing a simulation

    Hi All,
    In the risk analysis simulation , what is the meaning of field "Exclude Values:"
    Thanks
    Yudit

    Hello Yudit,
    This functionality is used for cleaning the Roles. By cleaning I mean, making the Risk free, so that when you do analysis using RAR, it should show 'No Conflict found'.
    So suppose you are doing SOD analysis of a BASIS role which show conflicts due to cretain tcode.
    Then rather than going to PFCG and removing that tcode and then again doing SOD analysis, you can use EXCLUDE functionality.
    So when you Simulation using Exclude option, you need to give name of Tcode which should be excluded from the role. So when doing Simulation, RAR will remove that tcode and all the object which comes from SU24 (CM)
    Hope this help. Please let me know if any doubt
    Regards,
    Surpreet Singh Bal

  • SAP GRC AC 5.3 - RAR Risk analysis Error Log

    Hi
    i have scheduled the background job for full sync risk analysis for the first time . the job ended with status error . critical analysis, user,role and profile action analysis is shown 100% . but the user permission analysis shows 49% , role and profile permission analysis show 97% each . where can i check the log for the errors . do i need to run the whole risk analysis job again ? when i check the management reports , risk violations are shown as zero . Please let me know how i can proceed at this stage . thanks
    Regards
    Prasad

    Thanks.
    First time please do for all users. I assume this was first time and it failed, so i will suggest you scheudle for all.
    once these are done, then periodic jobs should be increamental.
    few tips :
    - schedule user sync separate job and once it finish only then scheudle role sync and when role sync finishes, only then schedule profile sync
    - always select system ids from search help (which is F4 in ABAP)
    - best scheudle one job per system id, so that when failure occurs, so that error analysis is easy
    regards,
    Surpreet

  • List of Issues/ problems in SAP GRC AC 5.3 Implementation

    Hello,
    Can anyone provide me with the list of most commonly occurring problems related to
    1- SAP GRC Suite Installation
    2- RAR Module implementation
    3- CUP Module implementation
    4- ERM Module implementation
    5- SPM Module implementation
    6- SAP PC 2.5 implementation
    7- SAP RT Module implementation
    8- SAP GRC Suite Upgradation.
    Thanks in advance!!!

    Hi Abdul,
    As such there are no issues in implemeting the AC modules.
    Just make sure that you undeploy previously installed SP before deploying the new Support packages.
    1. You have to upload the initial file (xml files) again in CUP and ERM. These files should be corresponding to latest support pack.
    2. upload the CC 53_Messages.txt file in RAR with every upgrade.
    Also restart the server after deploying any following the above steps.
    For RT you can follow the note 1225960, 1060673 and make sure to restart the server after configuring the SAP Adapter.
    Regards,
    shweta

  • Critical Roles & RAR Background Jobs Question

    Hello,
    I have the following queries, related to GRC AC 5.3 RAR.
    1- I would like to include all roles starting with S* into critical roles.
    My question is can I say S* in critical roles, OR do I have to manually enter each & every role starting with S* (Please note that currently we have around hundreds of roles starting with S and entering each of them manually is a tedious task).
    2- We have several background jobs scheduled in RAR and when I click search button, I get a list of around 600 jobs executed in the past few months.
    My question is can I purge the background jobs history in such a way that, when I click "SEARCH" button, I get only those background jobs, which have been executed in the past 1 week?
    Thanks,
    Haleem

    Hi Varun,
    I created message with SAP in the component GRC-SAC-SCC and below is the response.
    Dear Customer,
    You have to manually enter each & every role in critical roles section and the exclude objects in management report section.
    SAP GRC AC 5.3 SP11 does not support wildcard operations in critical roles/ profiles and exclude objects of management reports. We will support the wildcard in future SAP Versions of GRC.
    Thanks
    Based on the above message, I understand that I will have to enter all the roles manually for critical roles in critical roles section of RAR -> rule architect and exclude objects  of management report section.
    Thanks,
    Haleem

  • Program batch risk analysis offline GRC AC 10.0

    Hello consultant:
    We have configurated GRC AC 10.0 RAR , when we executed risk analysis for Tx:NWBC  , the system run analysis(foreground or background) correctly but when we executed analysis for Tx:SPRO->Governance Risk and compliance->Access control->Batch Risk Analysis , the system run two jobs E:GRAC_SOD and GRAC_SOD but the jobs run only 1 second and finished sucesffully but the system no run analysis.
    Please could you help me?
    Thank you very much

    Please check view details in NWBC.
    or go to abap and select option and run it..
    and u can monitor the same using
    the tcode batch job for GRc monitor tcode dont remember u can check in guide.
    there it can show details.
    need tcodes and all ,please post
    Regards,
    Prasant

  • Automated process to get files from iScala System to GRC system

    Hi,
    iScala connector program run on local iscala servers.files are zipped up and place on ftp sites to download.once downloaded basis team copy the contents of zip files to IN Directory on GRC server.comparision utility is then run to move the files from IN directory to OUT directory.data extractors for each iScala connector are then run.Once extractors are done job scheduled to update the management report.i need more automated manner process and easy way process.
    Thanks

    As mentioned by Alpesh, for non RTA system there isn't any automated way to load data to GRC apart from using RAR Data extraction functionality.
    However you can look into possibility of using Greenlight technologyu2019s solutions to see if they provide any RTA to iScala system. They have about 25+ out of box RTAs to different non-SAP systems. Also they have RTA Design Studio which you can use to create a custom RTA specific to your ERP/Legacy application.
    Regards,
    Amol

  • Cannot find FF info in  ERM, CUP and RAR (GRC5.3)

    I can only find FF info on the ABAP system txn  /VIRSA/VFAT.
    But on the ERM, CUP and RAR (GRC5.3), I cannot find any info about FF.
    Which menu path/tab should I go search?
    Thanks!

    Hi Crishty,
    GRC AC contains four components RAR(CC),CUP(AE),ERM(RE) and SPM(FF).
    These seperate component have four seperate URL, so you will not get FF in ERM,CUP & RAR.
    Here are the URL to access these grc component,
    URL for RAR(CC)-
    http//<hostname>:<portnumber>/webdynpro/dispatcher/virsa/ccappcomp/ComplianceCalibrator
    URL for CUP(AE)-
    http://<hostname>:<portnumber>/AE
    URL for ERM(RE)-
    http://<hostname>:<portnumber>/RE
    URL for SPM(FF)-
    http://<hostname>:<port>/webdynpro/dispatcher/sap.com/grc~ffappcomp/Firefighter
    Thanks,
    Sudip

  • Scope of GRC for Functional Guy...

    Helo ,
    I am SAP SD guy ..I have 2.5cyrs. of experience in SAP SD  but right this moment i am into SAP GRC implementation project. Is there any bright scope for SAP GRC or else after this impelmentation project i have to go back to SAP SD to for my bread...
    David...

    Hello David,
    Below are some general scope for SAP GRC Access Control.
    RAR
    1) GRC Configuration
    2) Ruleset Design
    3) Ruleset Configuration
    4) Mitigation Process Design
    5) Ruleset Changes Process Design
    6) User Training
    CUP
    1) Workflow Design
    2) Workflow Configuration
    3) Approver List Process Design
    4) Testing Workflow
    5) Mitigation Approval
    There's more things that I cannot think of at the moment. If you wish to know more, I suggest you read some articles on the phases involved in GRC components. Basically anything requires GRC, and you can be doing audit on CRM solutions with SD knowledge or designing process control, or even designing the ruleset that is used in SAP GRC Access Control. I hope this helps a little.

Maybe you are looking for