- SAP Community
- Products and Technology
- Additional Q&A
- Compliance Calibrator Alert Generation Issue
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Compliance Calibrator Alert Generation Issue
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-04-2008 9:05 AM
We are now on the SAP GRC project for our client and trying to create the rule sets and critical transactions for analysis. The client also requested to have the feature alert log to generate the logs when a person perform the Tcode defined in critical transactions. We created an alert log file in Compliance Calibrator under Configuration > Miscellaneous > Alert Log filename & Location. Initially we came across into access right except before and we have fixed it by allocating FULL access to this file by the user account who is running the Netweaver service in windows. However, when we attempted to use the critical transaction or conflicting functions to generate Alert, there were NO logs generated without any error message.For detailed system log, please see below,thanks!
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----
Accepted Solutions (0)
Answers (3)
Answers (3)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
I think, that the origin of this problem could be related with installation or not of ABAP environment on GRC machine. If you access via SE16 to /VIRSA/ALTCDLOG (Alert Tcode Log) to your back-end, you'll see that the table exists but it's empty.
The reason to think this it's that in my last customer GRC machine had ABAP installed, and Alert Monitor worked properly. In my actual customer, this feature was not installed and Alert Monitor dont generate anything (Flat "Alert_Log.txt").
I suspect that Compliance Calibrator stores the information on /VIRSA/ALTCDLOG table of ABAP GRC machine, but I can't check this now, because I can't go back to my last customer.
Liping, can you confirm if you have ABAP installed on your GRC machine? Any new idea?
Hope this helps,
Regards
Ps. My job ends in only 2 seconds, no errors, but like in Liping case obtain a flat "Alert_Log" file
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Dear John,
Thanks for your kindly reply.
When the Alert Generation Job completed, we didn’t capture any data into the flat file (that is, the size for Alert_Log.txt is zero).
On the Alert Generation selection screen, we selected the right system ID and Risk ID, but we couldn’t get any alert information in log file. We also tried set risk ID as “*” for all risks alert, but still didn’t get any alert.
Moreover, we used TCode STAD to check STAT information in R/3 Backend environment; we noted that user access information were properly record in STAT tables.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
A couple questions:
When this job completed, had any data actually been written to the flat file?
On the Alert Generation selection screen, did you check the right boxes and properly identify the risk for which you wanted the alert to be generated?
Were the transaction(s) in question actually executed in the backend system?
Is STAT running on the backend system?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
We have actually found the root cause to the problem. SAP OSS has confirmed it. There is a bug in SAP function module /VIRSA/ZCC_GET_STATREC_DATA. This FM is called when we generate the alert log function. There is a sub-function within this FM called SAPWL_STATREC_READ_FILE where due to patch, it has changed parameter ‘read_continue_recordno’ is ‘1-’ from 0, which causes the program raise wrong_parameter_combination and not call function ‘SAPWL_STATREC_DIRECT_READ’. During debug, if you change the value to 0, your alert generation will return records.
OSS mentioned that this bug will be fixed in the next release but we have not heard from them.
Hope this helps.
- GRC Tuesdays: Takeaways from the 2024 Internal Controls, Compliance and Risk Management Conference in Financial Management Blogs by SAP
- IoT - Ultimate Data Cyber Security - with Enterprise Blockchain and SAP BTP 🚀 in Technology Blogs by Members
- SAP Document and Reporting Compliance - 'Colombia' - Contingency Process in Technology Blogs by SAP
- CAP LLM Plugin – Empowering Developers for rapid Gen AI-CAP App Development in Technology Blogs by SAP
- SAP Commerce Cloud Q1 ‘24 Release Highlights in CRM and CX Blogs by SAP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.