Warning eMails

To control critical issues and secure the environment emails are used very often. To send an email via Oracle there are various methods; workflow, trigger or alert. Alerts play an important role because they can be easily defined by technical or functional consultants though it has the disadvantage limited ability. For example alert mails have a plain format and does not offer options. On the other hand it provides some flexibility such as; periodic or event alert, alert action levels. Periodic alerts check the query and takes the required action though event alerts take action at the moment of event (Work like a trigger). Alert action levels are listed below for an example and defines the resulting actions of alert;

Ex1: (From 11i eBusiness Suite Instructer Guide)
"Inform the account manager of invoices on hold" alert
• Detail Action: Send a separate e-mail message for each invoice that meets the search
criteria of invoices on hold.
• Summary Action: Send a single e-mail message listing all invoices that meet the search
criteria, or send one summary for each vendor.
• No Exception Action: Send an e-mail message stating that nothing in the database is on
hold.

summary example:
Invoice Number Hold Type Hold Reason
=**= Enter summary template below this line =**=
**&Invoice_Number &Hold_Type &Hold_Reason
=**= Enter summary template above this line =**=

Ex2: "Indexes near maximum extents" alert can be checked for a relevant example; it sends a list of indexes near maximum extents as summary or sends an email stating that there is no index near the maximum extent.