Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

CC 5.2 Alert Generation - Not extracting any data from SAP

Former Member
0 Kudos

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----


4 REPLIES 4

Former Member
0 Kudos

Hi,

You might get a faster answer in the GRC forum

0 Kudos

Hi Alex,

Thanks for your note. I have actually posted in that forum as well but not getting any response. I have seen a reply from Laziz Turakulov in previous posting in this forum & hope that by posting here, I could get some feedback from all of you as well. We have tried all possible methods but our alert generation in CC just not extracting any data from SAP. Thanks.

0 Kudos

sorry - didn't realise you had posted there. Good luck getting an answer.

Former Member
0 Kudos

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