SAPu00AE COMPLIANCE CALIBRATOR BY VIRSA SYSTEMS

Hello all,
My company are thinking of implementing the above for auditing purposes to comply with Sarbanes-Oxley and compliance. I have read some documentation from the SAP website and this documentation states that:
"Because SAP Compliance Calibrator by Virsa Systems is embedded in your SAP system, no additional hardware or software is required."
Has anyone implemented this soultion? If so is there any additional documentation available for it?
Cheers,
Bernard.

David,
As We are in the process of implementing this virsa tool but we are not sure as to what are the exact steps that we should extract  to. Do you have a step by step guide (apart from the VIRSA install guide) which would guide us through the complete install and configuration. We have ECC 6.0 ,Portal,BI 7,CRM 5
Would you be kind enough to send the information to me asap.
Please forward me the doc to following id , I will be very much appreciate if you could do the help ..
[email protected]
Thanks
Laxmi

Similar Messages

  • Why upgrade from Compliance Calibrator to GRC?

    Hello Experts- My company has yet to implement GRC 5.3. We already utilize SAP Compliance Calibrator by Virsa Systems 4.0, which works fine, so what would be the benefit of upgrading to GRC? Is it really necessary? Is it just to stay current? Also, is it true that GRC will be moving from Java back to an ABAP stack? If so, when is the new ABAP version of GRC set to be available?
    Thanks for your advice and opinions.

    Regarding the upgrade from 4.0 to 5.3 I concur with Alpesh and Varun.
    Regarding the upgrade to 10.0, current plans are for Ramp-up to be available in December 2010 with general release scheduled for mid 2011.
    According to the latest material from SAP, they are only supporting a migration path as follows:
    4.0 -->5.3 --> 10.0
    There is no supported upgrade path from 4.0 directly to 10.0.
    It should be noted that it is a significant change in architecture and therefore not a simple migration path. SAP are recommending an upgrade to 5.3 followed by a migration to 10.0 for the technical side of things.
    5.3 does still have some significant advantages over 4.0 and therefore is still an option. owever, if you wish to register your interest, SAP are seeking ramp up customers so I would suggest you contact your Consultants or account management within SAP to discuss the options if you are considering it.
    Simon

  • 4.6C to ECC 6.0 upgrade - Issue with Virsa Compliance Calibrator

    The issue is that phase IS_SELECT during the PREPARE is not detecting VIRSA as an add-on. This of course will result in VIRSA not being upgraded and the system will be unstable ( note 989368 ). Also, I can't choose to delete the add-on either.
    We installed the compliance calibrator before SAP purchased VIRSA. So, the tool was installed through transports, not SAINT. I assume this is why phase IS_SELECT is not seeing the tool.
    Any ideas?
    -Scott

    Received a reply from SAP. Since VIRSA was installed through STMS the IS_SELECT phase will not see the add-on. I had to do the ECC 6 upgrade as normal and then install VIRSA 4.0 for SAP 700 systems through SAINT.
    I had to clear SPDD and SPAU as much as possible for /VIRSA/* objects. However, there were six objects I could not clear. This did not cause any issues.
    Notes 1006083 and 985617 are needed for this procedure.
    Thanks for all the suggestions.
    -Scott

  • Update on Management View in VIRSA Compliance Calibrator 5.2

    Hello,
    is there a way to delete the Data for the Management View in VIRSA Compliance Calibrator 5.2 and then make a full new data load.
    When I select Full Synchronisation and Management Reports in the Schedule Analysis, the system does not update the Management View correctly, the Management Report shows still roles which are already deleted in the SAP-System.
    Thanks

    Hi,
         You can do a Full sync of Users and Roles first which will be ovewrite and then run the Batch Risk Analysis Management Reports.
          You can try this exercise first if it does not work then go ahead with Alpesh's advice.
    Thanks
    Darshan

  • Anyone have Virsa/SAP Compliance Calibrator documentation?

    I'd really like a Virsa "Owners Manual", but for now I'd just settle for an explanation of all the parameters contained in table /VIRSA/ZVRATCNFG.  Some are self explanatory, some are not.  To maintain this table do the following:
    1.  tcode /n/virsa/zvrat
    2.  execute
    3.  menu:  compliance calibrator > configuration option
    I'd like to know what each parameter does, the possible entries, and the cause and effect result of each entry.  Any help will be appreciated. 
    Thanks,
    Marshall

    Dave,
    It appears to me that the only credentials required to access that site are SAP Service Marketplace logon (the so-called 'S number').  You can obtain these from the person in your company that administers your SAP licence (usually a basis person).  Or, you can apply yourself at http://service.sap.com/request-user .
    It is forbidden in this forum to send copywrited documents from user to user.
    Best Regards,
    DB49

  • Re: Virsa Compliance Calibrator & Pre-defined SOD Rule Set

    Hi All,
    We have installed the Virsa Compliance calibrator 5.1 in our sandbox environment. When we goto the "Rule Architect" tab under Compliance calibrator using tcode /virsa/zvrat it brings up the page with Rules information.
    Per the Virsa documents that i read they have mentioned that there are pre-defined SOD Rules (Transaction codes and Tcode objects) that we can use in the Rule Architect.
    My question is how do i enable and use those pre-set SOD Rules that Virsa provides by default. I do not see them under the Rule architect tab though. Can someone give some pointers to use these pre-set SOD rules.
    Thanks & Regards
    -Murali

    Hi Laziz,
    Thanks for your patience in replying to my CC 5.1 queries. I did follow your steps for the Generate Rule & Background Job-> Schedule Analysis and scheduled the job immediate.
    However, when i looked up the status of the scheduled analysis Background Job-> Search pulls up the job i scheduled at the top it reads "Job scheduler Status: unknown error" . I clicked on "View Log" button and it shows some messages as shown below (Note: I am just posting some parts of the error msgs below. but it still goes for 1 page...)
    May 16, 2007 1:09:07 PM com.virsa.cc.xsys.bg.BgJobDaemon init
    INFO: *** BgJobDaemon loaded
    May 16, 2007 1:11:09 PM com.virsa.cc.common.util.ConfigUtil setDefaultJ2EEParam
    WARNING: Cannot get Application URL: null. PLEASE SET 'Background Daemon URL' IN CONFIGURATION TAB
    java.lang.NullPointerException
         at com.virsa.cc.common.util.ConfigUtil.setDefaultJ2EEParam(ConfigUtil.java:203)
         at com.virsa.cc.common.util.ConfigUtil.getBgJobStartURL(ConfigUtil.java:192)
         at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:45)
         at java.lang.Thread.run(Thread.java:534)
    May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
    FINEST: class name: com.virsa.cc.extreport.ReportPack50SP1_01.ReportPack50SP1_01 class: com/virsa/cc/extreport/ReportPack50SP1_01/ReportPack50SP1_01.class
    May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
    FINEST: Jar Entry length=1568 compressed size=1568 actual read=1568
    May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
    FINEST: class name: com.virsa.cc.extreport.ReportPack50SP1_01.CrtActbyRsk_Act_RskLvl class: com/virsa/cc/extreport/ReportPack50SP1_01/CrtActbyRsk_Act_RskLvl.class
    May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
    FINEST: Jar Entry length=13210 compressed size=13210 actual read=13210
    May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
    FINEST: class name: com.virsa.cc.extreport.ReportPack50SP1_01.CrtRolbyRsk class: com/virsa/cc/extreport/ReportPack50SP1_01/CrtRolbyRsk.class
    May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
    FINEST: Jar Entry length=19287 compressed size=19287 actual read=19287
    May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
    FINEST: class name: com.virsa.cc.extreport.ReportPack50SP1_01.CrtProfbyRsk class: com/virsa/cc/extreport/ReportPack50SP1_01/CrtProfbyRsk.class
    May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
    FINEST: Jar Entry length=12807 compressed size=12807 actual read=12807
    May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
    FINEST: class name: com.virsa.cc.extreport.ReportPack50SP1_01.UsersbyOrgLevels class: com/virsa/cc/extreport/ReportPack50SP1_01/UsersbyOrgLevels.class
    May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
    FINEST: Jar Entry length=18557 compressed size=18557 actual read=18557
    May 16, 2007 1:24:59 PM com.virsa.cc.common.util.ConfigUtil setDefaultJ2EEParam
    WARNING: Cannot get Application URL: null. PLEASE SET 'Background Daemon URL' IN CONFIGURATION TAB
    java.lang.NullPointerException
    I am not sure whats causing this and it's been 2hrs since i scheduled the user analysis but i don't see any data still appearing in the fron-end..Any pointers again???
    Thanks
    -Murali

  • Compliance Calibrator v4.0 - Cross System SoD Analysis

    Hi all,
    I'm looking to run SoD analysis across BI7 and ERP using Compliance Calibrator v4.0.  I can see the Parameter in the config overview, and have set it to yes is both systems.  But there is nothing else in the documentation as to what other config etc is needed.  Does anyone now the steps involved or could you point me in the direction of documentation.
    Thanks in advance,
    Fiona

    Hi,
    there is a difference only if you have created and assigned mitigation controls to users.
    In that case, you can decide to see the report of SOD conflicts with or without mitigation controls:
    - Either you see all SOD conflicts including these that are mitigated (it is however clearly stated in the report whether a mitigation control exists or not)
    - Or you see all SOD conflicts excepted these that are mitigated (we consider thus that mitigated conflicts should not appear in the report)
    Rgds,
    Karim

  • Virsa compliance calibrator

    Hi All
    Can anyone help. I want to know if anyone has any documentation/ and or screen shots on Versa, as I know nothing about it.
    Thanks in advance. You can send info to [email protected]
    Mark

    Hi Leandro
    Thank you for your reply. I require as much info on 5.1 as you can get. I know nothing about the compliance calibrator and I want to rectify that.
    Thanks
    Mark

  • Is Compliance Calibrator the same as GRC Access Control?

    I have been asked to look at<b> Compliance Calibrator </b>and am getting confused about what functionality is offered. I have done the basic e-learning course for Compliance Calibrator (GRC200): this was all about separation of duties etc. Fair enough. But I also have a Document called "<b>SAP GRC Access Control</b>" which talks about the same S.O.D compliance functionality but also talks of "roles triggering workflows", "users creating roles", "automated approvals for roles" eg:
    "SAP GRC Access Control streamlines access requests by filling each request automatically with user identity information from a lightweight directory access protocol (LDAP) directory or HR database, thereby eliminating the need for user intervention. Approvers receive an e-mail with a direct hyperlink to the request inside the application, where they can easily view and approve the request. The application then checks for security violations before updating accounts  automatically."
    None of this was covered on the Compliance Calibrator course, so what product offers this? I can see another product by Virsa called <b>Access Enforcer</b> but have no info on this... can anyone enlighten me?

    SAP GRC Access Control is the SAP application that comprises the former Virsa products Compliance Calibrator, Access Enforcer, Risk Terminator, Firefighter and Role Expert.

  • Custom report on Compliance Calibrator Job scheduler

    Currently in compliance calibrator it is not possible for a user to view the status, success or otherwise, of another users scheduled job or sync unless granting that user full administrator rights.
    Please advise if it's possible to expose the underlying scheduled job table for a given system via a custom built static html web page. Can you advise of the table that results would need to be displayed from and whether there would be any drawbacks of this approach, or if others have somehow solved this problem with another solution, please share?!
    What are SAP's timeframe's for finer grained security in CC?

    below are the tables used for CC:
    VIRSA_CC_ACTRULE               SAPSR3DB                                        
    VIRSA_CC_ACTRULHDR             SAPSR3DB                                        
    VIRSA_CC_ACTVL                 SAPSR3DB                                        
    VIRSA_CC_ADMIN                 SAPSR3DB                                        
    VIRSA_CC_ALLASTRUN             SAPSR3DB                                        
    VIRSA_CC_ALLISTDTL             SAPSR3DB                                        
    VIRSA_CC_ALLISTHDR             SAPSR3DB                                        
    VIRSA_CC_ALTCDLOG              SAPSR3DB                                        
    VIRSA_CC_AUTHHT                SAPSR3DB                                        
    VIRSA_CC_AUTHMAP               SAPSR3DB                                        
    VIRSA_CC_BKGINP                SAPSR3DB                                        
    VIRSA_CC_BUAPPVR               SAPSR3DB                                        
    VIRSA_CC_BUMONITOR             SAPSR3DB                                        
    VIRSA_CC_BUSPRC                SAPSR3DB                                        
    VIRSA_CC_BUSPRCT               SAPSR3DB                                        
    VIRSA_CC_BUSUNIT               SAPSR3DB                                        
    VIRSA_CC_BUSUNITT              SAPSR3DB                                        
    VIRSA_CC_CDHDR                 SAPSR3DB                                        
    VIRSA_CC_CDPOS                 SAPSR3DB                                        
    VIRSA_CC_CGROUP                SAPSR3DB                                        
    VIRSA_CC_CONFIG                SAPSR3DB                                        
    VIRSA_CC_CRACT                 SAPSR3DB                                        
    VIRSA_CC_CRACTT                SAPSR3DB                                        
    VIRSA_CC_CRACTVL               SAPSR3DB                                        
    VIRSA_CC_CRPRM                 SAPSR3DB                                        
    VIRSA_CC_CRPRMVL               SAPSR3DB                                        
    VIRSA_CC_CRPROF                SAPSR3DB                                        
    VIRSA_CC_CRPROFT               SAPSR3DB                                        
    VIRSA_CC_CRROLE                SAPSR3DB                                        
    VIRSA_CC_CRROLET               SAPSR3DB                                        
    VIRSA_CC_CRROLEVL              SAPSR3DB                                        
    VIRSA_CC_DATAEXD               SAPSR3DB                                        
    VIRSA_CC_DETDESC               SAPSR3DB                                        
    VIRSA_CC_FLDMAP                SAPSR3DB                                        
    VIRSA_CC_FUNC                  SAPSR3DB                                        
    VIRSA_CC_FUNCACT               SAPSR3DB                                        
    VIRSA_CC_FUNCBP                SAPSR3DB                                        
    VIRSA_CC_FUNCPRM               SAPSR3DB                                        
    VIRSA_CC_FUNCSYS               SAPSR3DB                                        
    VIRSA_CC_FUNCT                 SAPSR3DB                                        
    VIRSA_CC_GENACT                SAPSR3DB                                        
    VIRSA_CC_GENOBJ                SAPSR3DB                                        
    VIRSA_CC_GENOBJT               SAPSR3DB                                        
    VIRSA_CC_GENPRM                SAPSR3DB                                        
    VIRSA_CC_GENUSR                SAPSR3DB                                        
    VIRSA_CC_GPRMLIST              SAPSR3DB                                        
    VIRSA_CC_GSEQ                  SAPSR3DB                                        
    VIRSA_CC_JOBHST                SAPSR3DB                                        
    VIRSA_CC_LASTRUN               SAPSR3DB                                        
    VIRSA_CC_LOCKTABLE             SAPSR3DB                                        
    VIRSA_CC_LSYSGRP               SAPSR3DB                                        
    VIRSA_CC_MGALERTS              SAPSR3DB                                        
    VIRSA_CC_MGCRTR                SAPSR3DB                                        
    VIRSA_CC_MGMTBU                SAPSR3DB                                        
    VIRSA_CC_MGMTTOT               SAPSR3DB                                        
    VIRSA_CC_MGRISKD               SAPSR3DB                                        
    VIRSA_CC_MGRISKS               SAPSR3DB                                        
    VIRSA_CC_MICCTLDTL             SAPSR3DB                                        
    VIRSA_CC_MICCTLDTT             SAPSR3DB                                        
    VIRSA_CC_MICEXLOG              SAPSR3DB                                        
    VIRSA_CC_MICORGDTL             SAPSR3DB                                        
    VIRSA_CC_MICORGDTT             SAPSR3DB                                        
    VIRSA_CC_MICPRCDTL             SAPSR3DB                                        
    VIRSA_CC_MICPRCDTT             SAPSR3DB                                        
    VIRSA_CC_MICRMAP               SAPSR3DB                                        
    VIRSA_CC_MICUMAP               SAPSR3DB                                        
    VIRSA_CC_MITHROBJ              SAPSR3DB                                        
    VIRSA_CC_MITMON                SAPSR3DB                                        
    VIRSA_CC_MITPROF               SAPSR3DB                                        
    VIRSA_CC_MITREF                SAPSR3DB                                        
    VIRSA_CC_MITREFT               SAPSR3DB                                        
    VIRSA_CC_MITRISK               SAPSR3DB                                        
    VIRSA_CC_MITROLE               SAPSR3DB                                        
    VIRSA_CC_MITRPT                SAPSR3DB                                        
    VIRSA_CC_MITUSER               SAPSR3DB                                        
    VIRSA_CC_MITUSRORG             SAPSR3DB                                        
    VIRSA_CC_MONAPV                SAPSR3DB                                        
    VIRSA_CC_MSG                   SAPSR3DB                                        
    VIRSA_CC_MSGPRMS               SAPSR3DB                                        
    VIRSA_CC_MSGTYP                SAPSR3DB                                        
    VIRSA_CC_OBJTEXT               SAPSR3DB                                        
    VIRSA_CC_ORGRULE               SAPSR3DB                                        
    VIRSA_CC_ORGRULEM              SAPSR3DB                                        
    VIRSA_CC_ORGRULET              SAPSR3DB                                        
    VIRSA_CC_ORGUSERS              SAPSR3DB                                        
    VIRSA_CC_PRMRULE               SAPSR3DB                                        
    VIRSA_CC_PRMVL                 SAPSR3DB                                        
    VIRSA_CC_RISK                  SAPSR3DB                                        
    VIRSA_CC_RISKFUNC              SAPSR3DB                                        
    VIRSA_CC_RISKOWN               SAPSR3DB                                        
    VIRSA_CC_RISKRS                SAPSR3DB                                        
    VIRSA_CC_RISKT                 SAPSR3DB                                        
    VIRSA_CC_ROLEVL                SAPSR3DB                                        
    VIRSA_CC_RTMAP                 SAPSR3DB                                        
    VIRSA_CC_RULESET               SAPSR3DB                                        
    VIRSA_CC_RULESETT              SAPSR3DB                                        
    VIRSA_CC_SAPOBJ                SAPSR3DB                                        
    VIRSA_CC_SCHEDULER             SAPSR3DB                                        
    VIRSA_CC_SUPP_DET              SAPSR3DB                                        
    VIRSA_CC_SUPP_HDR              SAPSR3DB                                        
    VIRSA_CC_SUPP_TEXT             SAPSR3DB                                        
    VIRSA_CC_SYSCRACT              SAPSR3DB                                        
    VIRSA_CC_SYSHMAP               SAPSR3DB                                        
    VIRSA_CC_SYSRULE               SAPSR3DB                                        
    VIRSA_CC_SYSSAPOBJ             SAPSR3DB                                        
    VIRSA_CC_SYSTEM                SAPSR3DB                                        
    VIRSA_CC_SYSTEMC               SAPSR3DB                                        
    VIRSA_CC_SYSTEMT               SAPSR3DB                                        
    VIRSA_CC_SYSUSR                SAPSR3DB                                        
    VIRSA_CC_TEXTKEY               SAPSR3DB                                        
    VIRSA_CC_THREAD                SAPSR3DB                                        
    VIRSA_CC_USRMAP                SAPSR3DB                                        
    VIRSA_CC_VARIANT               SAPSR3DB                                        
    VIRSA_CC_VARVAL                SAPSR3DB                                        
    VIRSA_CC_WFOBJ                 SAPSR3DB                                        
    VIRSA_CC_XSRULEMAP             SAPSR3DB                                        
    VIRSA_CC_XSYSGRP               SAPSR3DB                                        
    You can go and check which one contains the scheduling info (VIRSA_CC_SCHEDULER ??)
    Hope this helps

  • Convert from Compliance Calibrator 4.0 to Risk Analysis and Remediation 5.2

    Hello Forum,
    I'm looking for other opinions on converting Compliance Calibrator (CC) 4.0 to Risk Analysis and Remediation (RAR) 5.2 (formerly CC)
    I have inherited responsibility for RAR and need to upgrade it to the 5.2 level; our current ECC level prevents us from going to 5.3
    I found a process that will unload the data from CC 4.0 and be imported into RAR 5.2
    I want to understand the definitions that comprise the RAR and was thinking about recreating the definitions in 5.2 based on what is already defined in the CC 4.0 system; I have time to do this since there is no definitive deadline that would make it impossible to meet
    Currently, I have the following definitions:
    Business Process 6 entries
    Functions 47 entries
    Risks 147 entries
    Mitigating Controls 40 entries
    Would others find this approach acceptable and reasonable even though I would be entering all the information? Basically, it would be like defining the data for the very first time if this was NEW software
    I would expect to come away with a good understanding of how everything ties together; at this point, I am only looking to create the necessary data that would allow for producing SOD reports that show all users with "risks" have been mitigated with acceptable controls
    Thanks for your responses in advance
    Jerry
    Ryerson, Inc
    630-758-2021

    Thanks for the reply
    I have the migration guide and have reviewed it; I have actually played around a bit with obtaining the file from CC 4.0; I found that the data records may need some adjustments to be compatible with RAR 5.2; one of the reasons that may be leading me to do everything from scratch
    The definitions currently defined were completed by an outside source and the mitigated controls were defined by the Internal Audit area
    I'm not sure if they were mixed with the defaults
    I'm not sure at this point what impact or changes I would experience if I use the "default" supplied rules set but I expect to find out
    Thanks again for your reply
    Jerry

  • Need some practical Scenarios to test Compliance Calibrator, FF and AE

    Hi Experts,
    I have installed Compliance Calibrator 5.2 / Access Enforcer and Firefighter on a test System. However i am looking for some practical scenarios / Examples to test the functionlity of these installations. If any of you is currently working on these technologies i appreciate if you c an provide 2 3 scenarios to test my installation and functionality .
    Thanks in advance.
    Your help is much apprecaited..
    SK

    Hi SK,
    Testing the functionality of CC
    1. I would recommend to create some test roles where in you plug in some conflicting tcodes
        which can pose a sure SoD Risk, lets say Create Vendor Invoice(FB01) and Make an
        Automatic Payment(F110).
    2. Now run the Risk Analysis by choosing the Default SAP GRC ruleset library and do a  
        Role level Analysis.Then Assign the Test Roles to Test Users and then do a User Level Analysis.
    3. You may have create some Custom Rule sets with appropriate naming of Conflicting functions
        like Creation of Purchase Order (P001), Approve Purchase Order(P002)
        in different Application Areas like Purchase 2 Pay(P2P), Order 2 Cash (O2D) and try to do
        the same as above two steps.
    4. Test the functionality of Risk Remediation by removing the conflicting tcodes and do the
        Risk Analysis.Your previous Risk Roles must not appear
    5. Test the functionality of Risk Mitigation by placing a mitigation Control on the Conflicting tcodes
       and do the Risk Analysis.Your previous Risk Roles must not appear if you have properly
        configured your CC
    Testing the functionality of FF
    1. I would say create a few Firefighter IDs in different functional areas like FI, SD, MM, and then
       create some test users for Firefighter Owners, Controllers and Firefighters who can use
       the functionality of FF.
    2. Create some FF roles which have exceptional access in those functional areas
        encompassing transaction codes and authorization objects that are not used in normal incidents.
    3. Assign each of the FF roles to the respective FF IDs and then to the test Firefighters.
    4. Pull the log reports in FF and see if it gives exact details of the FF usage.
    5. You may have take some assistance of the Functional team members to do the testing.
    Testing the functionality of AE
    1. Create a workflow scenario of hiring a new user.
    2. Create the request under a test requestor. Assign the request to some test approver
    3. Also Assign some roles and test the functionality.
    Hope this helps for a good start
    Regards,
    Kiran Kandepalli.

  • Updating Compliance Calibrator Rule Set

    The business has decided to change a few rules by removing a couple of custom tcodes from the rule set.  In DEV I go into the Function and remove the objects associated with the tcode and disable the tcode.  After running the rule set update there is still some sort of tie.  I have created a test ID in DEV with a known issue around each of the changes.  I'm not getting a different result when running compliance calibrator.
    Any ideas?
    We are running R/3 4.6C and compliance calibrator 4.0

    Can you please check the following demo?
    [Virsa Compliance Calibrator Application for SAP v5.1 Demo|http://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/d2f1cf9c-0d01-0010-2dac-aedd3c4f7f5b&overridelayout=true]
    Please give more details on the step where you got stuck.
    Regards,
    Dipanjan

  • Configuring Role Expert Web services for Compliance Calibrator

    Hi @all,
    performing the configuration of Virsa Role Expert I've got a question regarding the settings for the various Web Service Info. for the Compliance Calibrator.
    Apart from the Web Service URL, user name and password need to be declared. The user guide names 'sapgrc' and 'webuser' as account names.
    My question: How do I setup these accounts? Is this an UME-Job - if so: what are the required roles and authorizations for these accounts?
    Kind regards,
    Martin

    Hi,
    the Web Services URLs are:
    Web Service Info. for CC Risk Analysis:     http://SERVER_NAME:PORT/VirsaCCRiskAnalysisService/Config1?wsdl&style=document
    Web Service Info. for CC Transaction Usage: http://SERVER_NAME:PORT/VirsaCCActionUsageService/Config1?wsdl&style=document
    Web Service Info. for CC Mitigation Control: http://SERVER_NAME:PORT/VirsaCCMitigation5_0Service/Config1?wsdl&style=document
    Web Service Info. for CC Functions: http://SERVER_NAME:PORT/VirsaCCFunction5_0Service/Config1?wsdl&style=document
    Web Service Info. for AE Workflow: http://SERVER_NAME:PORT/AEWFRequestSubmissionService_5_2/Config1?wsdl&style=document
    Does that answer your question?
    Regards,
    Martin

  • Deleted Roles appearing in Compliance Calibrator (Informer Tab)

    Hi
    We had deletd some roles from SAP . These roles still show up on complaince calibrator as having high risk violations.
    This role was delted a month ago and we also have completed as full sync of the system . Still the roles are appearing in compliance calibrator in the informer tab.
    Coudl you please let me know how we can avoid this?

    instead of running a full synch I would attempt running an incremental synch and run the management reports again.  I believe this should do it.  I am not sure why the full synch would not work.

Maybe you are looking for