Understanding Event Rules

You create event rules in Oracle's JD Edwards EnterpriseOne Report Design Aid (RDA) using the Event Rules Design form. You create event rules by selecting from available components. The event rules are embedded in the report template; they cannot be used anywhere else in the system.

Event rules can be written on any event. However, you must understand the order in which the events are processed to determine the correct event on which to place event rules.

If the event rules affect an individual field, you can place the event rules on one of that field's events or on one of the section events. Typically, event rules are placed on section events for more efficient performance.

This table identifies the types of event rule statements that you can create:

Event Rules Components	Description
If/Else/While Statements	Enable you to define the criteria for which the logic should be processed. The first line of an If/While statement typically begins with the If operator. Subsequent lines begin with either an And or an Or operator. An else statement is used to link two options. For example: If Search Type is equal to E or Search Type is equal to C <do this> Else <do that>. You can embed multiple If statements in event rules and other statements inside of the if statement.
Assignments and Expressions	Enable you to assign a value to a field. For example: RV Business Unit = PC Business Unit. Also enable you to create expressions to populate fields.
System Functions	Enable you to use special functions that are provided by the system. Only system functions that are relevant to the report component and event are presented for use.
Business Functions	Enable you to use logic that is provided by the system. Business functions are either C business functions or business function event rules that can be called from an event.
Event Rules Variables	Enable you to create variables that can be used inside event rules. These variables are typically used to store values to be used in event rule logic.
Table I/O	Enables you to use special table input and output functions that are provided by the system to fetch and update data.
Report Interconnects	Enable you to call another report from event rules.

Fields that are available for use in event rules are represented by a two-character, alphabetical code. This code indicates the source of the field and determines how the field data is used at runtime. Field types that are available for event rules depend on the fields that are included in the report section.

This table describes the field types that could be available in Event Rules Design:

Prefix Code	Description
BC	Business view columns. Columns that are included in the attached business view. These columns are populated with values from the database when a fetch is performed, and those values are the values that are saved when you add or update.
PC	Previous business view columns. Columns that are included in the attached business view. However, these fields are populated with the previous value for the selected business view field.
PO	Processing option fields. Values that are passed from processing options.
PV	Previous report variables. Fields that are populated with the previous value for the selected report variable.
RC	Report constants. Column headings in columnar sections and constants in group sections.
RS	Report sections. Values that are not typically used when you are creating event rule assignments.
RV	Report variables. Column variables in columnar sections and variables in group sections.
SL	System values. Values that are fetched by the system and include information such as user IDs, environment names, version names, and report names.
TV	Text variables. Fields that you create from the Section menu prior to creating the event rules. These fields are used in assignments.
VA	Event rule variables. Variables that you define in event rules using data items. These fields are used in assignments for storing values for further processing.