The above query works totally fine when we check from backend. When we create a sample scenario it did insert a row. But the alert is not fired. I guess something is wrong with rowid. How can we diagnose if alert is fired or not? How can we properly use query with group by clause.
Verify whether or not the alert trigger is enabled ->
Event Alert Does Not Fire Or Check Event Alert ( ALECTC ) Concurrent Request Does Not Start (Doc ID 1261925.1)
*select dba_triggers.table_name, dba_triggers.trigger_name,
from user_objects, dba_triggers
where dba_triggers.trigger_name = user_objects.object_name and
user_objects.object_type = 'TRIGGER' and
user_objects.object_name like 'ALR_%'
=> One can add the first characters of the table you defined the trigger on.
e.g user_objects.object_name like 'ALR_FND_PROFILE%' , but don't use the full table_name as the trigger name doesn't contain the full table name.
*Verify that the concurrent request ; 'Check Event Alert' has been started and completed normal.
where Concurrent_program_id = (select Concurrent_program_id from fnd_concurrent_programs_tl where
USER_CONCURRENT_PROGRAM_NAME = 'Check Event Alert') order by request_date desc;
Also take a look at this note:
Steps Needed to Setup For Event Alert (Doc ID 577392.1)
I will surely look into these documents. But we have other alerts too and they are triggering normal. I have issue with this alert only. Also when i make this alert on demand periodic the alert fire fine.
How to take the correct table for event alerts. what is the correct way.