OracleApps88 - Oracle Alerts PDF
OracleApps88 - Oracle Alerts PDF
Overview:
Oracle Alert is your complete exception control solution.
Oracle Alert facilitates the flow of information within your organization by letting you create entities called
alerts to monitor your business information and to notify you of the information you want. You can define one
of two types of alerts: an event alert or a periodic alert.
An event alert immediately notifies you of activity in your database as it occurs. When you create an event alert,
you specify the following:
A database event that you want to monitor, that is, an insert and/or an update to a specific database
table.
A SQL Select statement that retrieves specific database information as a result of the database event.
Actions that you want Oracle Alert to perform as a result of the database event. An action can entail
sending someone an electronic mail message, running a concurrent program, running an operating script, or
running a SQL statement script. You include all the actions you want Oracle Alert to perform, in an action set.
A periodic alert, on the other hand, checks the database for information according to a schedule you define.
When you create a periodic alert, you specify the following:
Defining Alerts:
Navigator: Alert Vision Manager USA
To define Alerts
Types of Alerts:
1. Periodic Alerts
Periodic alerts periodically report key information according to a schedule you define.
1. Select a frequency for your periodic alert. You can choose from nine frequency options:
2.
Frequency :
Every N Business Day: It will fire once in each three business day.(It will not count the holidays)
Every Other Business Day: It will fire in an alternative business (working) day.
i.e It will not consider holidays
Import : We can import the files(which contain the query) if the query size is big, if it exceed the memory.
After writing the Query in Select Statement area click on Verify to verify the query and
After Click on Verify Button the following message will come.
Click on OK and Save
Click on Run button , the following screen will come. And click on OK.
2 . Click on Actions Button and enter the Action information like following screen
Details Action perform once for each exception found,
Summary Action perform once for all exception found
No exception performs when no exception was found.
To create an event alert, you perform the following tasks in the order
listed:
2. In the Inputs tabbed region, Oracle Alert automatically displays the inputs used in your Select statement,
unless they are the implicit
• ROWID—Contains the ID number of the row where the insert or update that triggers an event alert occurs.
• MAILID—Contains the email username of the person who enters an insert or update that triggers an event
alert.
• ORG_ID—Contains the organization ID that is selected when the alert runs.
• DATE_LAST_CHECKED—Contains the date and time that the alert was most recently checked.
3. You can optionally add a description for each input, but you must specify the data type (either character,
number, or date) for the input, because Oracle Alert uses the data type to validate the default values for inputs
you enter in the Default Values field and in the Action Set Inputs tabbed region of the Action Sets block.
4. Enter a default value for your input. You can enter up to 240 characters. This value automatically becomes the
default value for your input in each action set you define.
5. In the Outputs tabbed region, Oracle Alert automatically displays the outputs used in your alert Select
statement without the ampersand (&) and any numbering format. You can add meaningful descriptions for the
outputs.
6. You can specify the maximum number of output characters you want to display in your detail or summary
message actions. See: Formatting Summary Message Actions:
7. If your output value is numeric, enter the SQL*Plus format mask in the Number Format field.
8. You can also check the Check for Duplicates check box to customize the combination of outputs you want to
verify as a possible duplicate exception each time the alert is checked. A duplicate exception is an exception that
existed in your database during previous alert checks. You can define Oracle Alert to perform certain actions
based on the presence of these duplicate exceptions.
9. In the Installations tabbed region, specify an Oracle ID if you want Oracle Alert to check your alert against
that specific Oracle ID. You can select only those Oracle IDs that are associated with the application that owns
your alert.
If you do not specify an Oracle ID in this region, Oracle Alert checks your alert against all installations in your
database of the application that owns your alert.
10. If you have multiple organizations defined in your Oracle Applications schema, you must specify the
organization you want the alert to run against in the Operating Unit field.