Implementation Steps For Oracle Alert Module
Implementation Steps For Oracle Alert Module
Implementation Steps For Oracle Alert Module
Modified 22-feb-2011
In this Document
Applies to:
Oracle Alert - Version: 11.5.10.2 to 12.1.3 - Release: 11.5.10 to 12.1
Information in this document applies to any platform.
Goal
What are the steps to create a simple Periodic or Event Alert to send an email?
How to check if Oracle Alerts formulated the email?
Solution
PERIODIC Alert
1. Using Alert Manager responsibility, navigate to Alert > Define
Enter a simple alert as follows:
Note:
Select Statement: Example shown is to ensure to receive one row / exception.
Click 'Run' to see the expected number of rows.
Click 'Verify' to check the Select syntax.
Keep Days: Enter a number greater than zero to capture history / diagnosis information.
Last Checked: This will populate with a date when the Alert is successfully run.
2. Select Actions button:
Note:
Enter a simple 'an1' action name, click 'Action Details'.
Text: Display the variable &OUTPUT1 defined in the Select Statement.
3. Select Action Sets button:
Note:
Inputs tab will be empty.
Outputs tab will show &OUTPUT1.
Choose a different action set name than the action name to better distinguish between the
two.
Do not select 'Exit Action Set Successfully'.
4. Select Alert Details button:
Note:
Inputs tab will be empty.
Outputs tab will show &OUTPUT1.
'APPS' should only show for the Oracle ID. The Operating Unit is not needed for
Periodic Alerts.
Done entering Alert, click 'save' and exit.
5. Navigate to Request > Check
Click Submit. Note Request ID.
Note:
Enter Application and Alert name from the definition.
EVENT Alert
1. Using Alert Manager responsibility, navigate to Alert > Define
Enter a simple alert as follows:
Note:
Select Statement: Example shown is to ensure to receive one row / exception.
Click 'Run' to see the expected number of rows.
Click 'Verify' to check the Select syntax.
Keep Days: Enter a number greater than zero to capture history / diagnosis information.
Last Checked: This will populate with a date when the Alert is successfully run.
You can choose either After Insert, After Update or both.
2. Select Actions button:
Note:
Enter a simple 'an1' action name, click 'Action Details'.
Text: Display the variable &OUTPUT1 defined in the Select Statement.
3. Select Action Sets button:
Note:
Inputs tab will be empty.
Outputs tab will show &OUTPUT1.
Choose a different action set name than the action name to better distinguish between the
two.
Do not select 'Exit Action Set Successfully'.
4. Select Alert Details button:
Note:
Inputs tab will be empty.
Outputs tab will show &OUTPUT1.
'APPS' should only show for the Oracle ID. The Operating Unit is required for Event
Alerts.
To determine which OU to choose, navigate to the form where the event table will be
changed. Then from the Menu: Edit / Preferences / Profiles, query: MO%.
Done entering Alert, click 'save' and exit.
5. To trigger the table ALR_DISTRIBUTION_LISTS
Navigate to Distribution Lists
Query any defined list, change the description, save.
Make sure the MO profiles match that of the organization unit defined under Installation
tab.
Menu: Edit / Preferences / Profiles
BASIC TROUBLESHOOTING:
1. There will be a concurrent request generated for the Alert. Navigate to Request >
View.
Review Concurrent Request.
Request OUT:
Note:
This shows typical output with the action and action set being executed.
2. Navigate to Alert History
Query the Alert name that ran. Data will show completely here if the Keep Days field on
the Alert Define is set to 1 or more days.
Select Find Checks
Note:
See the request id, time it ran and how many exceptions (rows) and actions performed.
3. Select Find Exceptions, Click OK
Note:
Here you see the values of the variables that were found from the Select statement.
4. Select Find Actions, Action Log
Note:
If the email is formatted and shown in the Action log, then Oracle Alerts has successfully
sent the email to the email client.
Check the Workflow Mailer if email has not arrived in the Inbox.