Previous | Next | Contents | Index | Navigation | Glossary | Library |
Before you define an event alert, make sure you do the following:
Attention: You cannot use a view as the event table for your alert.
Attention: Do not define an event alert on the table FND_CONCURRENT_REQUESTS. Oracle Alert submits a concurrent request to the concurrent manager when an event alert is triggered by an insert or update to an event table. For concurrent processing to occur, every submitted concurrent request automatically gets inserted as a row in the FND_CONCURRENT_REQUESTS table. If you define an event alert on this table, you create a situation where the event alert will cause an exception to occur recursively. See: How Oracle Alert Checks Alerts.
Attention: The SQL Select statement must be less than 64K.
Suggestion: If you want to use an input value in an action for this alert, select the input into an output. Then you can use the output when you define actions for this alert.
Attention: You must include :ROWID in your event alert's Select statement Where clause, or Oracle Alert will not be able to locate the row where the event transaction occurred.
Attention: The inputs :MAILID and :ROWID are reserved terms that you should not use for anything other than their intended purposes.
SELECT user_name, :MAILID INTO &NEWUSER, &USER FROM fnd_user WHERE rowid = :ROWID
Note: Although Oracle Alert does not support PL/SQL statements as the alert SQL statement definition, you can create a PL/SQL packaged function that contains PL/SQL logic and enter a SQL Select statement that calls that packaged function. For example, you can enter a SQL Select statement that looks like:
SELECT package1.function1(:INPUT1, column1) INTO &OUTPUT1 FROM table1
In this example,package1is the name of the PL/SQL package andfunction1is the name of user-defined PL/SQL function stored in the package.
To ensure that your PL/SQL function is callable from a SQL statement, verify that the packaged function meets the requirements listed in your PL/SQL Release 2.1 and Oracle Precompilers Release 1.6 Addendum.
Attention: The file you import must be less than 64K.
Creating an Action Set for an Alert
Transferring Alert Definitions
Previous | Next | Contents | Index | Navigation | Glossary | Library |