The rule engine is the validation routine which checks values entered by the operator based on a set of rules. Actions are then performed automatically depending on whether the rule criteria are fulfiled. For example, data values can be set or calculated automatically, or alternatively, error messages can be displayed so that the operator is forced to amend an incorrect data entry value.

Discuss in forum
SunSystems contains functions that validate data from manual input, such as from transaction entry functions. You can define business rules by using the functions:

In this example we are going to create an Event Profile that checks if a function is Ledger Entry. Then it fires up a rule set, which checks if an account enetered is 11000 and if so it will insert a PROJECT code (Ledger Analysis 3) "P001".
The first step in defining a validation business rule is to set up an event profile.

An event profile is a set of conditions that determines when, and under what circumstances, a particular process occurs. Event profiles help to ensure that only relevant process rules, defined using rule sets, are started when a particular function is run or a particular call point is used.

The conditions of an event profile begin with an IF statement which can apply to all entry and import functions.

Once a function code is defined, other conditions can be added that must apply before this profile is invoked. For example, you can specify that a profile only applies if a specific business unit code is used. You must build your profile from a series of IF and OR command statements as required.

There is no limit to the number of event profiles you can define. However, a maximum of 1000 relevant profiles are loaded and filtered at run time. Only those events and rules relative to the current process are loaded into memory, therefore careful and concise structure of an event profile can control a process more efficiently and improve performance significantly.
Click here to see the screenshot.

Event Code
Enter a unique code to identify this profile.

Description
Enter a description for this profile.

Event Status
Select Suspended if you want to suspend processing of this profile or select Open if active. The default is Open.

Event Period From/To/All
Enter the effective range of accounting periods for this record, or select the All check box to select all periods. This determines the period of time that the event profile remains valid.

Event Date From/To/All
Enter the effective range of dates for this record. To select a specific date, click the drop down box and use the calendar to navigate to the required date. Alternatively, select the All check box to select all dates. This determines the period of time that the event profile remains valid.

Click the Details button to create the conditions for the event profile:

Click here to see the screenshot.

In this example we are going to create an Event Profile that checks if a function is Ledger Entry.
Event Code
Displays the event code created on the previous form.

Command
Select an IF or OR command.

Data Item
Select the record type from the Data Dictionary Lookup window, which lists the valid record types available. Once you have selected the record type, you can choose from a list of data items associated with that record type.

Operand
Enter an operand to be used for this statement. When creating a line for a system function, only '=' equals to can be entered.

Date Item or Value
Select the data item from the Data Dictionary Lookup window, which lists the valid data items available. The list displayed is based on the selection you made in the Data Item field.
Note: The first line statement must be entered as "IF Function Code ="