To specify the alert details for an event or periodic alert:Once you define an event or periodic alert in the Alerts window, you need to display to the Alert Details window to complete the alert definition. The Alert Details window includes information such as which Application installations you want the alert to run against, what default values you want your inputs variables to use, and what additional characteristics you want your output variables to have.
To specify the alert details for an event or periodic alert:With your alert definition displayed in the Alerts form, choose Alert Details. The Alert Details window that appears contains three tabbed regions: Installations, Inputs, and Outputs.
In the Inputs tabbed region, Oracle Alert automatically displays the inputs used in your Select statement, unless they are the implicit inputs: :ROWID, :MAILID, :ORG_ID and :DATE_LAST_CHECKED. The values of the implicit inputs are as follows:
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.
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.
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.
For example, if you have an input APPLICATION_NAME, and you give it the default value "Oracle General Ledger," Oracle General Ledger will also be the value for the input in each action set you define, unless you change it in the action set to another value like "Oracle Payables."
Note: When you change an input value in an action set, you simply change the value for that action set. The new value does not get propagated as a new default value for other occurrences of that input.
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.
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.
If your output value is numeric, enter the SQL*Plus format mask in the Number Format field.
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.
Note: You must save history for your alert to use duplicate checking. See: Overview of Oracle Alert History.
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.
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.
If you do not specify an operating unit for a multiorg schema, then:
your event alert will run for the operating unit from which the event alert is triggered, as specified in the MO: Operating Unit profile option.
your periodic alert assumes a non-multiorg schema and simply runs for the Oracle Alert Manager's operating unit.
If you want your alert to run against several operating units of the multiorg schema, you must enter them individually in the Installations tabbed region. Delete any records in this region that do not have a valid Oracle ID and operating unit.
Check the Enabled field if you want your alert to run against the specified Oracle ID.
Save your changes and close the window.
Once you finish specifying the details for your alert definition, you need to create the actions for your alert. .
