Compliance Calibrator 5.2 Alert Generation

When we start the alert generation report it seems that the job that runs in the back-end ECC-6 system starts in the foreground and after awhile, system parameter is set for 15 minutes, times out.
1. Has anyone used this, the Alerts Generation successfully? And if so what configuration settings and connecter settings are used?
2. Has anyone else had this issue and how did they fix it?
And we have used the Alerts Generation troubleshooting guide, but to no avail.
Any input/help well be much appreciated since, as of now, SAP has not been able to help us figure this out.

Hi Clark,
Im also facing the same issue. When we contacted SAP they said that first upgrade the SP levels, then they said that install also HR component since we have HR system.
Thats how i got stuck up here! Once i install the HR component also then i think i can crack and solve this problem
Regards,
Faisal

Similar Messages

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

Compliance Calibrator 5.2 RTA for Non-SAP Apps

Hi all,
Can SoD rules be written for analyzing a Users access to SAP and NON-SAP applications across the enterprise?
If yes will CC RTA need to be installed on the NON-SAP application?
If yes are there any requirements that need to be met by NON-SAP application and is there a list of NON-SAP applications (other than-Peoplesoft, Oracle, Hyperion, JD Edwards) that CC has an RTA for?
Is there any documentation specific to aplications that can support CC RTAs and installation on these?
-Cheers

Hi,
Yes SoD rules can be written for analyzing user accesses to SAP and non-SAP applications.
Basically there is no other application for which an RTA exists, but there is a documentation discussing the technical requirements for file generation from the non-SAP systems for integration of non-SAP Systems with SAP Compliance Calibrator.
This documentation is available in <a href="http://service.sap.com/rkt-grc">http://service.sap.com/rkt-grc</a>
under SAP GRC Access Control 5.2 -> SAP GRC Compliance Calibrator 5.2 -> Step2: Prepare for your project -> Cross Application Material
You'll need your OSS user-id to access that page; in case you cannot access it, please post a message in the OSS.
Rgds,
Karim

Does CC alert generation take into account 1/ act or 2/ act+perm ?

Dear Forum,
Can somebody shed some light on how alert generation works ? Are only the entries in the action tab of a function relevant ?
1. Suppose you have alertlog.txt
$ cat Alertlog.log
SYS-001 JDOE SM30 2008-07-28 09:15:07 ENDUSER
SYS-001 JDOE SU01 2008-07-28 09:45:24 ENDUSER
2. critical action rules
a) SM30 S_TABU_DIS 02 FC31 = open and close FI posting period
b) SU01 S_USER_GRP ACTVT 06 = Delete users
---> will the "Search Critical Action Alerts" functionality report JDOE or not ? That is, will SAP GRC take the permissions into account yes or no ? If not, than we have false positives.
Thanks - Sam

Simon,
Thanks for the reply
Can we conclude as follows :
"SAP GRC Risk and Remediation alert monitoring and alert notification do not take into account any function permissions settings before, during or after alert analysis. By this logic, users will be reported as soon as alertlog.txt line items correspond with items from the action tab as part of functions, regardless the fact those users' user buffer does not have the necessary permissions as specified within that same function."
I have noticed your email suffix sap.com --> Can I consider your answer as an official answer from SAP to my question ?

Short dump while executing job SM:EXEC SERVICES for EWA alert generation

Hello All,
I'm getting short dump error while executing job SM:EXEC SERVICES for EWA alert generation.I'm using EHP1@SP22 of Sol Man.
Please find the logs
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RDSVASCABAP_TRANS__________073
" in include "RDSVASIABAP_TRANS__________073 " in
line 1782:
"Field "STATEMENT_SUMMARY001019" is unknown. It is neither in one of th"
"e specified tables nor defined by a "DATA" statement. "DATA" statement"
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
If anyone came across such kind of dump, please reply asap, due to this, i could not generate EWA report for R/3 system 6.04.
Thanks,
Anand.

>
Anand Tigadikar wrote:
> Thx Paul, but i already did checked this note and its not solving my issue
Dear Anand,
Did you perform a complete service definition replacement for SDCC/SDCCN as described in the note?
These are manual steps you need to perform on the system and are not code corrections.
I would suggest you perform it, if you have not, and check the SDCCN logs to review the process ran cleanly.
Note: Please make sure SDCC_OSS is functioning and a connection to SAP can be made before
deleting the service definitions.
If you have already replaced the service defintions on the Solution Manager system, then no point doing it again. However checking a note and applying it are not the same thing. So I am uncertain if you replaced the service definitions or not. The dump you are getting in SM:EXEC SERVICES suggests its due to a problem with the service definitons. The recommendation is to replace them according to the process described in SAP Note 727998. If you have not done so please do so.
If you have successfully replaced the service definitions are you still getting the same dump, or has it possibly changed?
Regards,
Paul

Is Compliance Calibrator the same as GRC Access Control?

I have been asked to look at Compliance Calibrator 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 "SAP GRC Access Control" 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 Access Enforcer 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

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

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

How to add my own iview in Compliance Calibrator

Hi Experts,
can plaese tell me how to add my own iview in Compliance Calibrator 5.1.

Anubha,
If you are trying to add an iview or URL to Compliance Calibrator you have to login as an administrator go into the configuration tab, and go to Custom tabs toward the bottom of the left screen. Here you can add custom URL links that will appear as tabs in Compliance Calibrator.
Hope this helps
Gabe

CC 5.2 Alert Generation - Not extracting any data from SAP

Hi there,
We are trying to use the alert function for critical transactions in CC 5.2. We have set the relevant parameters in CC. The Alert_Log.txt is created successfully but it is not extracting any data from SAP. Is there any settings that I am missing here, both in R/3 and CC 5.2? I really appreciate your help. Below is the Alert_Log.txt for your review.
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
FINEST: Analysis Daemon started background Job ID:41 (Daemon ID D:\usr\sap\CC1\DVEBMGS00\j2ee\cluster\server0\. Thread ID 0)
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
INFO: -
Scheduling Job =>41----
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob run
INFO: --- Starting Job ID:41 (GENERATE_ALERT) - AlertGeneration_Testing
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob setStatus
INFO: Job ID: 41 Status: Running
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob updateJobHistory
FINEST: --- @@@@@@@@@@@ Updating the Job History -
1@@Msg is AlertGeneration_Testing started
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
INFO:
Background Job History: job id=41, status=1, message=AlertGeneration_Testing started
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob alertGen
INFO: @@@ Alert Generation Started @@@
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob alertGen
INFO: @@@ Conflict Risk Input has 1 records @@@
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob alertGen
INFO: @@@ Critical Risk Input has 1 records @@@
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob alertGen
INFO: @@@ Mitigation Monitor Control Input has 1 records @@@
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface alertGenerate
INFO: @@@@@ Backend Access Interface execution has been started @@@@@
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface alertGenerate
INFO: @@System=>R3
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface alertGenerate
INFO:
No of Records Inserted in ALTCDLOG =>0 For System =>R3
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface append_TcodeLogFile
INFO: *********SOD Tcode Size=>0**************
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface append_TcodeLogFile
INFO: *********Alert Tcode Log File=>D:\cc_alert_log\cc_alert_log1.txt is created**************
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface alertGenerate
INFO:
File Output Log File Size ==>0----
For System =>R3
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface alertGenerate
INFO: -
Conf Last Run Date=>2007-12-12--Conf Last Run Time=>12:45:11--
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface alertGenerate
INFO: ==$$$===Notif Current Date=>2007-12-20==$$$==Notif Current Time=>14:27:32===$$$===
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface send_AlertNotification
INFO: ****************** send Notification Alert Type=>1
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface send_AlertNotification
INFO: ******Alert Notification=>CONFALERTNOTIF==LastRunDate:=>2007-12-20==LastRunTime:=>00:00:00==Curr Date=>2007-12-20==Curr Time=>14:27:32*********
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface send_AlertNotification
INFO: ****************** send Notification Alert Type=>2
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface send_AlertNotification
INFO: ******Alert Notification=>CRITALERTNOTIF==LastRunDate:=>2007-12-20==LastRunTime:=>00:00:00==Curr Date=>2007-12-20==Curr Time=>14:27:32*********
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface send_AlertNotification
INFO: ****************** send Notification Alert Type=>3
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface send_AlertNotification
INFO: ******Alert Notification=>MITALERTNOTIF==LastRunDate:=>2007-12-20==LastRunTime:=>00:00:00==Curr Date=>2007-12-20==Curr Time=>14:27:32*********
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.mgmbground.dao.AlertStats execute
INFO: Start AlertStats.............
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.mgmbground.dao.AlertStats execute
INFO: start:Sat Dec 01 14:27:32 CST 2007
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.mgmbground.dao.AlertStats execute
INFO: now:Thu Dec 20 14:27:32 CST 2007
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.mgmbground.dao.AlertStats execute
INFO: end: Tue Jan 01 14:27:32 CST 2008
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.mgmbground.dao.AlertStats execute
INFO: Month 2007/12
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob alertGen
INFO: @@@=== Alert Generation Completed Successfully!===@@@
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob setStatus
INFO: Job ID: 41 Status: Complete
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob updateJobHistory
FINEST: --- @@@@@@@@@@@ Updating the Job History -
0@@Msg is Job Completed successfully
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
INFO:
Background Job History: job id=41, status=0, message=Job Completed successfully
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
INFO: -
Complted Job =>41----

Hi,
we have ran into similar issue of alert log being not displayed accurately in CC 4.0 version and we implemented the Note 1044393 - CC5.1 Alerts, it did work for us, as you are using CC5.2, I would recommend you to check the code and then try this note. But iam still skeptical whether this note will be helpful to you or not.
Thanks,
Kavitha

Compliance Calibrator SOD Conflict (FI01 and FB05)

I was hoping that someone could provide some insight as to why the "FI01 - Create Bank" and "FI02 - Change Bank" transactions would create a risk (in Compliance Calibrator) when coupled in the same security role with the "FB05 - Post with Clearing" transaction. The risk description given by Compliance Calibrator is "Maintain bank account and post a payment from it".
The FI01 and FI02 t-codes appear to only create/change routing numbers or addresses for banks. There is no ability to create or change an actual bank account. This alone doesn't seem to create a conflict when coupled with a posting transaction. Is there possibly some functionality that I am missing?

Hi Joshua,
I strongly agree with you that there is no SOD conflict technically with FI01, FI02 with FB05 although the wording of the SOD conflict in a business sense meaning Maintain Bank Accounts vs Posting Payments sounds more like a Conflict.
I dont see by anyway how you can maintain actual bank account in either FI01, FI02.
FI01 and FI02 - Maintain Bank Info like Bank Address, Bank Key and soforth.
FB05 - Make Payments to various accounts.
Regards,
Kiran Kandepalli.

Compliance Calibrator v.4.0 Installation Guide?

Does anyone have a Compliance Calibrator v.4.0 Installation Guide? I cannot find one on SAP Service Marketplace.
I have found a Security Guide, User Guide Supplement, User Guide, but no installation guide.
Thank you!

Hi there,
I have the guide, and I can give it to you.
Reach out to me at [email protected] and I'll get it to you.
Thanks,
Santosh

SAP GRC 5.2 Compliance Calibrator rule sets for HR module

HI All,
The company i am working for has done installation of GRC 5.2. I would like to download the SAP out of box Compliance Calibrator rule sets for HR function module in a spreadsheet format.
I would like to download the rule set for risks at Function level, Tcode level and also at authorization object level in ABAP and Roles, actions and permissions in JAVA.
I will discuss with the BPAs, internal auditors and come up with a new rule set exclusively for my company needs with the help of the above spreadhseet.
Please tell me what steps i need to do to get this thing done.

Please go through the process but save these as txt files for UNIX. I am not sure about 5.2 but CC4 was not uploading rule files correctly if file was not saved for TXT for UNIX.
Regards,
Harry Sidhu

Alert generation in PI

Hi Experts,
I want to generate alerts when a message fails in PI. I am checking SXMB_MONI for message failures.
I have setup following to generate alerts.
1. Alert category in ALRTCATDEF and fixed receipients
2. Activated the Alert rule in RWB (Alter Config)
3. SMTP setup is present in SCOT
4. alertinbox service is activated in SICF.
Even after doing these, alerts are not getting generated as I cannot see alerts in Alert Inbox and I am not getting alert emails.
Please let me know if I am missing anything else required or any additional steps are required for alert generation.
Thanks,
Deepak

Check the following.
1)Check Exchange profile parameters 'Central Monitoring Server':
in section RuntimeWorkbench
com.sap.aii.rwb.server.centralmonitoring.r3.ashost
com.sap.aii.rwb.server.centralmonitoring.r3.client
com.sap.aii.rwb.server.centralmonitoring.r3.sysnr
Ensure they are filled with the information of the PI system where the
Central Monitoring Server is.
2)Go to tcode sm59 and check RFC Destination
'CentralMonitoringServer-XIAlerts'.
Under 'Technical Setting' the same host and system number as parameter
com.sap.aii.rwb.server.centralmonitoring.r3.ashost/r3.sysnr in the
exchange profile should be maintained.
Under 'Logon&Security' the same client as from parameter
com.sap.aii.rwb.server.centralmonitoring.r3.client should be
maintained.
If they are not the same/matching, delete the destination. It will be
created automatically with the correct parameters when the next alert
is created.
3)Run these reports to ensure all the necessary ICF
services are running?
RSXMB_ACTIVATE_ICF_SERVICES
RSALERT_ACTIVATE_ICF_SERVICES

Compliance Calibrator 5.2 Alert Generation

Similar Messages

Maybe you are looking for