Understanding Table Event Rules

Use table event rules to attach database triggers (or programs) that automatically run whenever an action occurs against the table. An action against a table is called an event. When you create a database trigger in Oracle's JD Edwards EnterpriseOne, you must first determine which event activates the trigger and then use Event Rules Design to create the database trigger.

Table event rules provide embedded logic at the table level. Table event rules have their own location, events, and system functions. When you use table event rules, neither the calling application nor the user is notified of changes or events to the table. No form or report interconnect is available with table event rules.

You can use table event rules for data integrity. For example, when you delete a record in Oracle's JD Edwards EnterpriseOne Address Book, you might want to delete all associated records, such as phone and category codes. You can also use table event rules for currency. The Currency Conversion is On event rule handles currency information in table event rules.

You can attach event rules on a table-by-table basis to these events:

• After Record is Deleted

• After Record is Fetched

• After Record is Inserted

• After Record is Updated

• Before Record is Deleted

• Before Record is Inserted

• Before Record is Updated

• Currency Conversion is On

This table describes the functions that you can use in table event rules:

Functions	Description
Assignment\Expression	Enables you to create assignments and complex expressions.
If\While	Enables you to create IF/WHILE conditional statements.
Business Function	Enables you to call existing business functions.
System Function	Enables you to attach existing JD Edwards EnterpriseOne system functions.
Variables	Enables you to create Event Rule variables.
Else	Enables you to insert an ELSE clause, which is only valid within the boundaries of IF and ENDIF.
Table I/O	Enables you to create event rules used for database access. Performs table input and output, data validations, and record retrieval.

You do not need to create and associate data structures to table event rule functions. The table itself is the data structure that is passed to the table event rule function.