Compliance Calibrator Job Run

Hi;
I have submitted a job to run in Compliance Calibrator as job type = immidiate, but the job does not appear to start and sits in ready status in State column. Can anyone guess, what the problem can be?
Regards;
Sumanta

Hello,
This is known issue with GRC AC, please stop and start application "sap.com/grc~ccxsysbgear " from Visual Administrator - then you need to wait for some time and it should be started.
Visual Administrator --> Server -->Services --> Deploy --> Choose Application --> sap.com/grc~ccxsysbgear -
> Stop and then Start.
Hope this helps.
Thanks
Davinder

Similar Messages

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

Compliance Calibrator: Background jobs didn't bring in the correct data.

Hi Gurus;
In Compliance Calibrator; background jobs were last run on 5/27/09 but the management report shows that the summary is as of 5/20/09. That should have been updated uptill 5/27/09 and the new number of conflicts should have come up, which it didn't. What can be the problem?
Thanking you;
Raja

Hi Harleen;
This job was actually set by the client. So when I went to check the parameters of the jobs, I found that the field MGR_ANALYSIS consists of Field value "N". Does this mean that the Management Analysis box was not ticked when this job was scheduled?
Regards;
Raja

Issue with Compliance Calibrator 5.2 SP9 Background Jobs

Hello,
I'm having an issue with Compliance Calibrator 5.2 SP9 where If I run a role analysis as a background job that has the same parameters as a previously run role analysis background job, the second job that is run will display a failure message. It does not appear to matter if the similar background jobs were run by the same individual or separate individuals. As long as the job that was previously run is still in the background job history, than any job with the same parameters run by a user will fail.
Is this normal operation for CC?
Is there a configuration change that could allow a job to be rerun in the background multiple times?
Is there a fix for this issue in a later support pack or with upgrade to 5.3?
Thanks for the help it's much appreciated,

To better clarify what is occurring, the 1st job will run and complete successfully and return/display the appropriate results correctly. The 2nd job will than be subsequently kicked off and finish same as with the previous job except when you open the background results no data is displayed and the message at the bottom reads: Failed to display result. To make more sense of what Iu2019m doing, these are the logical steps Iu2019m following:
1. Select Role Level analysis
2. Enter parameters for analysis
3. Schedule background job to run immediately
4. View background job results (successful job and correct results)
5. Select Role Level analysis (with same or any other user)
6. Enter same parameters as step 2 for analysis
7. Schedule background job to run immediately
8. View background job results (successful job, but the error message: u2018Failed to display resultu2019, instead of seeing the CC reports)
I believe the error is somewhere in the running of a job with the same parameters (Same Role and same Report Type). If I delete the previous jobs from the background history that have the parameters Iu2019m using and try the analysis again, a third time, with the same parameters as before, it will run successfully and display the correct results.
Is this normal and acceptable operation for CC5.2 SP9?
Is there a configuration change that would allow a job to be run in the background multiple times with the correct CC results?
Is there a fix for this issue in a later support pack or with upgrade to 5.3?

Custom Risks in Compliance Calibrator?

Hello,
Can someone please verify this process for me?
My understanding is that once you create and configure a custom risk in Compliance Calibrator 5.2, you simply click generate and can then immediately run a risk analysis using the new custom risk.
Is there any kind of a background job required to synchronise the new custom rule prior to running a risks analysis or any steps that I'm missing?
Thanks your help is much appreciated,

Hi Adamo,
This is the exact process you need to follow. Once you create main risk and generate rules, you should be able to see the risk in CC. Have you enabled the particular risk? You can go to informer and try to run a simulation or ad-hoc analysis on that particular risk.
Regards,
Alpesh

Upload spreadsheet into Compliance Calibrator

Hey Experts....
Does anyone know how to upload a large amount of Users and Roles into Compliance Calibrator to do a simulation for SOD analysis?
I have about 500 Users I need to run CC against in Production and don't want to do them manually.
Any help would save a lot of time/$$.
Thanks.
Chris

Chris,
What version of CC do you have? What do you mean by doing it manually? If you have SAP 4.6C and above, you should be able to schedule background job to syn users, roles etc.
Please provide more details.
Regards,
Alpesh

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 5.1 Alert File generation

Greetings,
I would like to understand how the Compliance Calibrator (CC) 5.1 Alert Generation File is created. I specify a file name in 'Configuration/Miscellaneous/Alert Log Filename & Location', and schedule the job via 'Configuration/Background Job/Alert Generation'. The file is updated daily, but where is the data pulled from? It looks like the data is sorted daily by User ID and tcode. The data looks like it could come from the Security Audit Logs on ABAP instance, but would this be required?
Any technical information would be helpful.
Thank you,
Rob

Hi Rob,
There are different types of alerts, which can be generated by Compliance Calibrator:
a) system finds that certain mitigation reports were not run in time;
b) end users executed critical transaction, listed in one of your risks;
c) end user executed conflicting transactions, lsited in one of your risks.
So, the data is pulled from your ABAP system. And it explains why you get the list of user IDs and tcodes.
Please, advise whether it asnwers your question ? And if yes, award the points accordingly
Best regards,
Laziz

SAP GRC Access Control - Compliance Calibrator - License Cost

Dear all,
I have some questions on Compliance Calibrator implementation.
1. Do we have to pay additional cost for the license to implement Compliance Calibrator?
2. Since SAP GRC 5.3 is just released, which one do you recommend? SAP GRC 5.2 or 5.3?
3. What would be the major difference between Compliance Calibrator in GRC 5.2 and 5.3?
Best regards,
Rolando

Hi Rolando-
1. Yes, there lies some license cost and the amount should not as much as taking SAP R/3 license. I am not sure of exact amount but its nominal as compared to other SAP products.
2. SAP always recommend for the latest version available and why not one would go for latest version if you are paying something for that.
Also, it depends on your existing R/3 version and its compatibility. In short run, you can choose per your existing versions but in long run everyone has to move to latest version. Say for example whoever is using SAP R/3 technology with whatever version, they all need to upgrade to ECC6.0 by 2011 with extension upto 2013. I am not sure of any such information about GRC AC though.
3. Some enhancement have been done with CC 5.3. Those features include-
1. Risk analysis for SAP Enterprise Portal and UME
2. BI integration for custom reporting
3. Reporting enhancement features include additional auditor, business manager and IT reports
4. SOD management by exception. Can be integrated with workflow.
5. Import/Export of configuration data
6. Migration scripts
7. Download and print capability on every report.
Some performance improvements-
1. Concurrent risk analysis.
2. batch mode risk analysis
3. Improved memory mgmnt etc.
Hope it gives you now some more visibility.
Cheers!
Ashok

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.

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

Compliance Calibrator 5.2

Hi,
Does anyone has configuration guide to compliance calibrator 5.1 or 5.2? All the rule architect is empty. Please advice. Thanks.
Regards
Flo

Hi Florence,
I was out of the office for a while and because of that could not access this forum.
As you use CC 5.2, there are slight changes in the way you configure the link in comparison to version 4.0 and below.
- all of your target R/3 systems need to be registered in your SAP SLD;
- NW server running CC engine should be aware of your SLD Supplier as well;
- On your NW server open JCo maintenance and create two connections to your target server: for Metadata and for Model. Server details will be obtained from SLD;
- login to your CC 5.2 Web site and in Configuration section click "Connection" tab. You'll need to activate connection for each R/3 backend. Use "Adaptive RFC" option for SAP links and in fact it'll be your required RFC connection.
There is no need to setup any RFC connections via SM59 now.
Hope this helps. Please, award the points if your consider this answer to be useful.
Thanks,
Laziz

Compliance Calibrator Job Run

Similar Messages

Maybe you are looking for