| Oracle® Retail Active Retail Intelligence User Guide Release 14.0 E49474-01 |
|
 Previous |
 Next |
The Event Manager dialog is used to define, view, and maintain events.
The Event Viewer displays all the events of a particular event type that are assigned to you. The Event Viewer has several parts:
Event Type and Event State
At the top of the screen are the event type and state.
Events Assigned to You
Below the event type and event state are listed the events of that type that have been assigned to you. This part of the Event Viewer includes several items:
List of Events
The top portion of the Event Viewer lists the events of a particular event type assigned to you, along with the critical details of the event. The most important of these details is the event priority of the event. High-priority events are indicated by an exclamation mark on an envelope. Normal priority events are indicated by a plain envelope with no exclamation mark.
You can sort these events by parameter, by clicking on the column headings for the event details.
Reevaluate Events Button
Clicking the Reevaluate Events button below the event list checks the events list to ensure that all your events are current and should still be assigned to you.
Refresh Events Button
Refreshes the display of the event list.
User Events Button
Clicking the User Events button displays all events assigned to you by the Active Retail Intelligence administrator.
Supervised Events Button
Clicking the Supervised Events button displays events assigned to you as an Active Retail Intelligence supervisor. This button is activated only if you have Active Retail Intelligence supervisor user privileges.
Event Messages
Below the event list are messages about the event selected in the list. The messages include such things as why the event was created, a list of every user who has forwarded the event, messages included with the forwarded event, and errors encountered during the event's lifecycle.
Details of Event
At the bottom left corner of the screen are further details about the selected event. The event details tell you more about the event and allow you to go to the event's source.
The event details are displayed with a label for the detail in the left column, and the detail value in the right column.
If the event detail is an image or a long-text file, the detail's value in the right column is a hypertext link. Clicking the hypertext link displays the image or text file in a separate viewer.
Expand Button
If the text of the details is cut off, click the Expand button to display the event details in a larger window. Pressing F9 with focus on an event detail does the same thing.
In the Detail section of the Event Viewer, there are two types of details that display differently than normal details.
Images, or pictures attached to the event.
Long text, or text over 2,000 characters and under 65,534 characters that is attached to the event. Long text is usually text such as articles or long descriptions.
Images and long text have special viewers. Clicking the hypertext link in the value column, or pressing F9 when the focus is in the hypertext link, displays the image or long text in these special viewers.
Both long text and images show a hypertext link in the value column. You click this hypertext link, or press F9 when you are in the field, to go to the image viewer or the long text viewer.
Within the Image Viewer window, the image is displayed as well as possible within the limits of the window space available.
Once the image viewer is open, you can save the image to a file for further manipulation. To do this, type a valid Windows filename in the filename box and select a file type from the file type drop-down list. Then click the Save button to save the image.
For text displayed in the long text viewer, you can select the text and use the Edit-Copy function to copy it into the Windows clipboard and then paste it into your favorite word processing application.
The bottom right corner of the event viewer displays a list of actions associated with the selected event type, version, and state. These actions are set up by Active Retail Intelligence administrators when defining events.
Actions are performed by selecting an action from the list and clicking the Do Action button.
One action commonly found on events is the close action, which deletes the event. Deleting the event is useful if you wish to ignore the event or act on the event outside of the Event Viewer, perhaps in a way not specified in the list of actions.
Performs the selected action. Actions can vary greatly by event, and are set up by the business analysts at your site. The action may take you to portions of the merchandising system to perform actions such as approving purchase orders or creating new purchase orders, or cause a message about the action to be displayed.
The Event Type Revalidation Schedules screen is used to add, edit, and delete schedules for reevaluating the event type. The schedules are subject to the start and end date constraints that you specify on this screen. The active link period means that this schedule will be used to drive periodic reevaluation of this event (according to the schedule) between the link start and end dates. If there is no end date then the reevaluation will continue indefinitely. The link period start and end dates are editable provided they are not in the past, and in no case can they be set before the current date.
The screen is divided into several sections:
Event Type Header
The header section displays information about the current event type. These fields are read-only.
Available Schedules
Available Schedules shows a list of all schedules that are available to attach to the schedule. To attach them to the event type, click the Down button.
Active Link Period
The Active Link Period establishes how long the schedule is attached to the event type. This period is defined by start and end dates and times.
The active link period must fall within the event type's active period and the start date/time cannot be set to be before the current date (sysdate). Also, the link period cannot overlap any periods already established for the same schedule.
When removing a schedule, its active link period is copied into this active link period section and that schedule is selected in the Available Schedules list, unless it has become inactive before it is removed, in which case it is simply removed.
Schedules
The Schedules part of the screens shows all the schedules currently attached to the event type. To add an available schedule to this list, click the Down button. To remove a schedule from this list, click the Add button.
The Event Type State - Action screen defines the actions associated with the event state. This screen is divided into five sections.
Header
The header section is read-only.
Actions
The Actions section shows actions currently mapped to the state.
The up and down arrows can be used to reorder the actions. The resulting order will be used when displaying the list of actions in both the Event Manager and the Event Viewer.
Add/Remove Actions Buttons
The Left Arrow button and Right Arrow buttons in the middle of the screen are for adding and removing actions for the event state.
Available Actions
The available action section shows actions that can be added. The parameter mapping area shows how event parameters have been mapped to add the currently selected action to the event.
Actions can be added or removed at any time. However, removing and action may modify an attribute rule by removing it from being an auto-action for that rule. In this case, you are notified and prompted to proceed. Adding an action opens the Parameter mapping screen, unless all of the parameters of the action are override, error, or current user parameters.
For the actions that are already mapped to the event state, the action names are editable at any time. These action names must be unique within a given event type, state, and action designation. Uniqueness is necessary to allow an action to be added multiple times (potentially with different overriding parameter values).
Parameter mappings can be edited by invoking the parameter mapping screen, but only if there are any parameters that can be mapped (not having at least one override/error/current user parameter).
The Event Type Header screen defines header information, such as the event name, its lifecycle, and start and end times. The Event Type Header has the following fields:
Event Type Name
A unique name for the event type.
Version Number
The version number of the event.
Time to Live
The number of days that the event "lives" after it is closed. This will prevent a creation of an identical even during this period.
History Retention Days
The number of days that history for the event is retained in the Active Retail Intelligence database.
Start Date and Time
The date and time at which the event becomes active.
End Date and Time
The date and time at which the event becomes obsolete.
Event Type Description
A text description of the event and its purpose, including such information as what the event type does, or the exceptions to which the event type is mapped. The comments button on the right side of the description opens a comment window for entering or editing the description.
Notification Checkbox
Indicates whether the event supports email notification when the event occurs.
Creating Event Types
When you are creating version one of a new event, the following fields are all enabled and editable: Event Type Name, Time to Live, History Retention Days, Event Type Description, and Start Date and Time, and End Date and Time are all enabled and editable.
Except for End Date and Time, all of these fields are required, as is Version Number, which is given a value of 1.
Editing Event Types
For future event types, all displayed fields except Version Number are editable. For active event types (start date has passed), the Start Date and Time is not editable.
Viewing Event Types
When viewing event types, all fields are read-only.
Cloning Event Types
Cloning acts like Edit mode, except that you are working on a new record that has been created and manually populated with a version number of one and the name is left blank.
Versioning Event Types
During versioning based on an event that is not in Disabled (D) status, versioning acts just like cloning, except that the version number is the next highest version number based on the event type's highest existing version number, also, start and end date are both blank.
During versioning that is to be the next version of an event type, but is not directly based on a known event type (because previous versions have been disabled), versioning acts like New mode (new version). This second kind of versioning can be either in standard or wizard format and is in all ways just like New mode, except that the event type ID and version number are known.
Start Date, End Date, and Versions
In every case, start dates cannot be set to be before or equal to the current date or before or equal to the end date of the previous event version, whichever is greater. End dates cannot be set later than or equal to the start date of the next version, if one exists, and also become required fields if a later version exists. When creating a new version, if not already set, the previous version's end date is updated to one second less than the new start date of the new version and the user is notified of the update. Changing start and end dates map impact mapping to schedule, exceptions, and related events, and this must be addressed when changes are saved to the screen (OK, NEXT, BACK). These date related items must be dropped if they fall out of range, or updated accordingly if they are still partially within range. Ideally any tracking tables used by various linking processes (re-evaluation, and so on) would be updated as well.
When you choose a parameter from a realm outside of the event realm, or one that can be mapped in multiple ways, The Event Type Parameter Mapping screen is displayed to illustrate how the parameter will be queried.
The left side of the Event Type Parameter Mapping screen displays a list of the key parameters of the newly mapped parameter's realm. The right side shows the parameters of the event that are of the appropriate types to make the mapping. The event type parameters are displayed using the event parameter name (alias).
Note that in several cases this screen is shown even when there is only one mapping combination. This is so that you can be clear about how the data-model navigation is occurring, even when there is only the one mapping option.
Using the LOV, you can select from all of the parameters or parameter types of the type needed for the key parameters of the realm being mapped. However, the combination must ultimately be unique to allow the completion of the parameter mapping. For key parameters that have only one mapping option from the set of event type parameters, that value is automatically filled in.
The reason for overriding an event parameter with an exception parameter, when the event parameter is not required to come from the exception, is that the event may be linked to multiple exceptions. In some cases, the information on one of the exceptions may be seen as more up-to-date than whatever data the event would have re-queried had it been caused by its other driving exception.
For example, an external data source exception and an internal exception may both cause the same event, but the one from the external data source provides information which is more accurate than the internal system (such as a recalculated open-to-buy). In this case, you might prefer to use the external calculation as opposed to the internally accessible data when the event is generated from the external data source. Note, however, that if the internal exception occurs later than the external one, the value will be overwritten with the newer internal value anyway. Thus in cases where parameters other than event key parameters come from two different exceptions, it is best to use a one-to-one exception-event mapping to ensure that the external data source values are maintained in the rare cases where preserving those values is critical.
The Event Type Parameters screen is used to add, edit, and delete parameters associated with an event. The screen is divided into six main sections.
Available Realms/All Parameter Types/Exception Context Buttons
This section of the dialog is a set of radio buttons for switching between editing parameters or purely parameter types. Your choice here affects what is displayed in the list in the middle center of the screen.
Available Realms: Displays realms from which parameters may be selected and added to the event type.
All Parameter Types: Displays a list of all parameter types in the system.
Exception Context: Displays the parameters of a specific exception. However, only these parameters' types are actually of interest. Any parameter type can be added to an event. However, since parameter types play a critical role in exception mapping, the exception mapping context can be useful for restricting the list.
The parameter type list is queried each time the exception context is changed. It is also queried every time the radio group is set to either Exception context or All Parameter Types. Parameter names are blank when All Parameter Types is selected and use the exception parameter names when exception context is selected.
Available Realms List
The Available Realms section displays realms from which parameters can be selected and added to the event type.
Parameters List
The section in the top center displays the parameters of the currently selected realms or all parameter types or the parameters of the specified exception, depending on the radio group selection.
Event Key
This field helps determine to which exception type the event type can be mapped. The exception must possess the same parameter types as those parameter types to which the event type's key parameters belong.
Display
Determines whether a parameter should be shown in the header or in the detail section of the Event Viewer. If header is chosen, the parameter will be a field that can be sorted in the Event Viewer.
Parameter Alias
An alias for the parameter.
It is possible to add the same parameter twice using a different mapping each time. To distinguish these parameters from one another later, when building conditions, the option of creating an alias for each parameter is provided.
Unavailable Realms List
The unavailable realms list shows realms from which parameters could be selected if the appropriate driving parameters already had been added to the event type. Double-clicking a realm or pressing F9 displays a list of needed parameter types to be able to access an unavailable realm.
Parameters
The Parameters section shows the parameters already mapped to the event.
Parameter Mapping Link
The Parameter Mapping Link section shows the link basis by which a given parameter is mapped to the event. That is, it shows the mapping dependencies of the selected parameter. The mappings are displayed as the key parameters for the parameter's realm, and the number of the event type parameter used to invoke each key parameter. To modify the parameter mappings, click the Edit button.
Adding Parameters to Event Types
Any available parameter or parameter type can be added to the list of parameters on the event type by using the down (add) arrow. Event type parameters must have unique names. If no alias is specified, the parameter name is used unless it is a parameter type out of exception context. In this case, the parameter type name is used. When adding a parameter, the mapping for the parameter must be specified. If it can only be specified one way (based on existing parameter types and those required by the realm), then the mapping is performed automatically. Otherwise, the parameter-mapping screen is invoked.
Several special conditions apply when adding a parameter:
Parameters that are added from the this event realm require no special mapping.
Parameter types do not require mapping.
When automapping parameters, unique names must be derived. The Display attribute is set to Detail and the Event Key attribute is set to No.
Removing Parameters and Parameter Types from Event Types
By pressing the up (remove) arrow, you can remove parameters from the event type. However, removing parameters/types has several implications. Specifically, when a parameter or parameter type is removed, the following must also occur:
Actions mapped with parameters that cannot be overridden must be removed.
States that have all actions removed must be removed from the state rules. If that means the default state is removed, all state rules must be removed.
Conditions of attribute rules must be removed and the entire rule must be removed if no conditions remain and it is not the default (rule #0).
Conditions of state rules must be removed, and if no conditions remain and it is not the default state rule, the entire state rule must be removed.
Related event links must be removed if no parameter relation remains.
Exception mappings must be removed if no parameter mappings remain.
Conditions of closure rules must be removed.
If an attempt to remove a parameter affects dependent parameters, conditions, or event types, a warning is displayed asking whether you want to continue with the removal.
The Event Viewer Layout screen defines the layouts for instances of this event type when the events are displayed in the Event Viewer. Each layout can be used as the default layout for one or more Event States.
The Add button adds a new layout. The Delete button deletes a new layout. You cannot delete a layout if it is selected as the default layout for any Event Type State.
For each layout you can adjust the column width and order of the header columns, and determine which header columns will be displayed by default. As you change the layout for a header column, the Preview area at the topic of the screen shows how the parameter will look in the Event viewer. Users can adjust all of the settings in the Event Viewer.
You can also select which parameters will be displayed in the detail section and the order in which they will be displayed. The detail settings are not adjustable in the event viewer.
You can adjust the order of both the header and detail parameters by using the up and down arrows next to the appropriate block. For each layout you must specify at least one header parameter and one detail parameter to be displayed in order to exit this screen.
The Event Type - Exception Type Link screen is used to add, edit, and delete links between an event type and exception types.
To link an event to an exception, the exception must be able to provide parameter mappings (by parameters of the same type) for all of the event's parameters that are declared as coming from an exception context. Optionally, additional parameters can be fed to the event from the exception, overriding whatever method the event would normally use to fetch those other values. For more information on this, see the Event Parameters Screen section of the Event Manager dialog.
Other conditions for triggering an event from an exception are that the active dates must overlap and the definition of the event being mapped must be complete. All of these factors determine whether an event will show in the available or unavailable mapping area, or not at all. Also, there is no simple window that can be popped up to explain that a mapping cannot be made as there is for parameters with the Needed Parameter Types window.
The screen is divided into several sections:
Header
The header section displays information about the current event type. None of these fields are editable.
Available Exception Types
The Available Exception Types list shows exception types that are valid to link to the event type. These exception types have some overlap in their start and end dates with those of the event type, and for which the exception type has appropriate parameter types to map to the events key parameters. The comments button in this section displays the exception type description in a pop-up comments window.
Unavailable Exception Types
Unavailable exception types are like available exceptions with respect to validity and an existing overlap period, but they are missing one or more of the event's key parameter types. Double-clicking or pressing F9 on an unavailable exception type displays a list of needed parameter types.
Down Arrow and Up Arrow Buttons
The Down button adds an available exception type to the list of linked exception types. The Up button removes the selected exception type from the linked exception types list and returns it to the list of available exception types.
Active Link Period
The active link period is an editable pair of dates that are used when the event type and exception type are linked to set the active period of the mapping. These dates are used with the Down button.
An event type can be mapped to an exception type more than once and the validation for these dates is somewhat complicated. In every case, it is necessary to account for the fact that a null end date acts like an infinity end date. The start and end dates must be between the minimum of the event type and exception types end dates and the maximum of its start dates. The start date is further restricted in that it must be later than the current date. Finally, if the exception type is already mapped to the event type, the start and end dates must define a period that does not overlap with an existing mapping. If valid dates have been entered, the link mapping screen is invoked to complete the process of specifying how the key event type parameters will be populated from the exception type.
Linked Exception Types
The Linked Exception Types section shows already mapped exception types. The Link Period and Exception Active selections toggles the display between link period dates and exception type activity dates.
The only editable fields in this list are the link start date and end dates. These dates are subject to the date rules for the Active Link Period, and the Start Date is editable only if the date is later than the current date. Once the start date had passed, only the end date is editable; in this case, the end date cannot be set earlier than the current date.
When editing already linked exceptions, if you try to choose a date outside the start and end dates, an error is displayed. Only exceptions that have not entered the active link period (that is, exceptions for which the mapping start date has not yet passed) can be removed. If the end date has passed, both dates are read-only.
Parameter Mapping
The parameter mapping section shows which event type parameters are mapped from which exception type parameters. The mapping is editable only before the start date of the linkage has passed. Clicking the Edit button displays the Exception-Event Link Mapping screen, where you can edit the link mapping for the selected event type-exception type pair.
The Event Type - State Rules screen is used to add, edit, and delete rules to assign to an event's state, and to change the conditions that make up those rules. The result of a set of rules being true is that a state is assigned to the event.
When the screen is launched, if a default rule does not already exist, one is added by clicking on the Add in the Edit Control button. A state must be assigned for each rule. The default state cannot be deleted or moved, though buttons allow changing the order of all other rules. Except for the default state, all rules must have at least one condition. When you click the OK, Next, or Back button on this screen, the rules are checked to determine whether they have at least one condition. This check is done by looping through all rules and offering to delete any but the default that do not have conditions.
The screen is divided into several sections:
Event Type Information
The top of the screen displays the name and version number of the event type associated with the state rules.
State Assignment Rules
The second section lists the states that will be assigned and the sequence in which the rules to assign those states will be tested.
Conditions
This section is used for adding, editing, and deleting the conditions that make up the state rule. It consists of a condition editor, controls for moving conditions into and out of the condition editor, and a list of conditions currently defined for the state rule.
Condition Editor
The condition editor is for defining conditions that make up the state rule. For more information on setting up conditions for an event type, click the following link.
Event Type Rule Condition List
This section lists the conditions of the rule selected in the State Assignment Rules list.
The Event Type States screen and the set of screens associated with it is used to maintain or add, edit, and delete, the states names of an event and the layouts of the state.
As the data set of an event refreshes, it may be that the data set changes in a way that the event is used to track several stages of a process. For each state a layout must be selected. It will be used as the default layout when events in that state are displayed in the event viewer.
Typically at each step in a process, different actions are appropriate. Also, the rules used to assign the events priority, routing, and any automatic actions may be different at each step of the process. States provide the functionality to support tracking multi-stage processes.
From the Event Type States screen, you can create the event states. On subsequent screens, you define actions to be mapped to the states, and attribute rules defined to dynamically assign priority, routing method, assignment group, and automatic action attributes that apply whenever the event is re-evaluated.
The screen is divided into three sections: States, Actions, and Attribute Rules.
States
The States section displays the state names of the event. State names are editable at any time.
The Add button adds a new state.
The Delete button deletes the selected state.
Actions
The Actions section displays the actions of a given state. Using the Edit Control button, you can edit the actions.
Attribute Rules
The Attribute rules section displays the attributes that could be assigned to the event and the order in which the underlying rules used to assign the attributes are evaluated. Using the Edit Control button, you can edit the attribute rules.
Adding and Deleting States
States can be added or deleted directly on this screen. Deleting a state that is used in a state rule results in deleting the rule as well. If this implies deleting the default rule, then all exception mappings must be removed from the event. A different warning should be given to you in each case, asking whether you would like to proceed.
When you click OK on the dialog, Next, or Back when using the event wizard, a message displays indicating that any states that do not have at least one action and a default attribute rule will be deleted.
The event summary screen displays all the exception types defined in your system. All the information in this screen is read-only.
Filtering the View of Events
This view may be filtered. Using the radio buttons and the Filter button, you can choose to display all events, including expired events, or only active and future events. The Clear button clears any active filter.
Event Types List
The top part of the screen lists all the event types in summary form. All the information in this screen is read-only. From this summary list, you can create new exceptions and edit existing exception definitions.
Several action buttons are available on this screen that allow creation, editing and deletion of event types.
From left to right the buttons are used to:
The Wizard button starts the wizard for creating a new event type. This button is active at all times.
The Add button creates a new event type manually. This means you work through the screens of the Event Manager yourself to define the new event type, rather than using the wizard. This button is active at all times.
The Version button creates a new version of an existing event type, and establishes a date and time for the new version to take effect. The Version button is available at all times that an event is displayed in the summary list.
The Cloning button clones, or copies, an existing event type.
The Edit button edits an exception type that is not yet active.
The Delete button deletes an expired or not-yet-active event type.
The Information button displays additional header information about an existing event type.
The lower half of the screen shows details about the currently selected event in the top half of the screen, depending on which button is selected in the center of the screen: parameters, states, state assignment rules, schedules, exceptions, or closure rules.
The first stacked detail screen for the bottom half of the summary view is the parameters screen. This screen is the default when the form is first launched. This screen shows the parameters for the selected event type and has a button for accessing the add/edit/delete parameters screen. This button is available for the same records that the edit button for the header is available for and disabled for past and active events. The info button is available whenever the Version button is available.
The Layouts detail lists the layouts that have been set up for displaying instances of this event type in the Event Viewer.
The States detail displays states and state rules defined for the event type. The Edit Control button displays the state editing screen. The Information button is enabled whenever the versioning button is available. The Edit button is enabled only for future exceptions.
Clicking the Actions button displays all of the actions associated with the event state on the right side of the state detail.
Clicking the Attribute Rules button displays the possible results of conditional evaluations in terms of priority assignment, routing method, automatic action and, behind the comments button, group assignments.
The state assignment rules detail shows both the evaluation sequence and the state that is assigned if all of the conditions are true.
The Schedules for Revalidation detail shows which schedules are attached to the event type, and which of them are active now, in the future or in the past. These values for active are updated using the view the schedule block is based on each time the query is performed.
Schedules can be added/edited/deleted for all active and future active event types. The comments box displays the schedule description. The button is available when the selected event type is not blank.
The Exception Types detail shows the exception types that are linked to the event type and the window when the link will be valid. Like schedules, exception type mappings may be edited in for all event types that are active and future active. The comments button displays a comments window with a description of the exception type.
The Closure Rules detail shows the conditions evaluated to determine whether the event is closed. The evaluation sequence is just a rule number and the order of evaluation is not important since if any of the sets of conditions is true the event will be closed. Closure rules cannot be edited for active exceptions.
The Needed Types window is displayed in several situations when defining and editing event types:
When defining event parameters and parameter types, this window is available from the Event Type Parameters screen. In this case, this window shows a list of additional parameter types needed to make that realm available.
When defining event-exception links, this window is available from the Exception Type - Event Type Link Parameter Mapping screen. In this case, the window shows which parameters are needed on an exception to make a given event available for mapping.
Several exception and event management screens involve defining conditions associated with the exception or event, including
Exception Type Conditions
Event Type State - Event Attribute Rules
Event Type - State Rules
Event Type - Closure Rules
Following is a description of how to create and edit conditions on these screens.
In all the screens that involve conditions, you use the Condition Editor to add, edit, and delete conditions showing that a parameter changes or that a relationship exists between two parameters or a parameter and a value. The basic layout of a condition is a comparison between a parameter and a value or another parameter, using an operator such as = or >. Exception definitions have an additional setting for the condition, Monitor Change, which specifies whether you want to be notified when the parameter change occurs. It is also possible for a parameter to change and have a relationship condition simultaneously.
All conditions must be between a parameter and a value or two parameters, but never between two constant values. At least one parameter must be chosen, so when the condition editor is empty only the first parameter field and its LOV are enabled. Once a parameter is selected (only varchar2, date, number, and Boolean data types are available in the LOV), the other fields are enabled. When the first parameter field is cleared, the condition editor reverts to the original state.
Once the condition is defined, you add it to the list of exception or event-rule conditions below the editor by clicking the button. When you need to change a condition, you click the button to move the condition into the editor, and when done changing the condition, you click the to move it back into the condition list for the exception or rule.
The conditions defined for an exception or event are treated as logical AND conditions. That is, when a monitor detects candidate exception instances, or when an event is evaluated against the rules defined for it, the exception or event is tested against all of these conditions. If they are not all true, the candidate is discarded and ignored without further processing. For example, if all the conditions for candidate instance are true, then the candidate instance becomes an actual exception instance, at which time linked events are created.
The condition editor is displayed above the list of existing conditions, and consists of the following fields and controls.
Parameter
The parameter on which the condition is based. This parameter is compared to a value or another parameter. Click the LOV button to display allowable parameters for the exception or event.
The parameter chosen to drive the condition determines:
Which operators are available
For exceptions, whether the exception can be monitored online
Whether other parameters or special values can be used for the comparison created.
All parameters allow comparison to NULL values. Only parameters from the monitored realm, if the realm can be monitored in real time, allow change detection. Some parameters have a constrained set of valid values that can be used for comparison, such as the store number parameter only allowing valid store numbers. Also, the data type of the parameter, character, Boolean, date, or number, determines which comparisons can be made to other parameters (that is, those of the same data type). Actually, many times such comparisons are not meaningful, unless the two parameter types are the same, such as comparing two store numbers, as opposed to comparing a dollar amount and a store number.
Monitor Change (for Exception Type Conditions Screen Only)
The monitor change radio button indicates whether or not the condition will be real-time monitored. In other words, do we want to monitor the field changing to the entered value (for example, order status changing to 'S') or all fields that contain that value (for example, order status = S).
Monitoring a change is only possible on parameters that come from the monitored realm, and even then only on a realm with active, query-able data. So, monitoring change is impossible for external systems. For internal systems, however, whether an exception monitors transactions online or through a nightly batch sweep depends on whether at least one of the conditions is set to monitor a change.
Operator
The operator used to compare the parameter with a value or another parameter.
For Exceptions only, an operator is required for all conditions except for those in which a change is being monitored.
Available operators depend on the data type of the specified parameter. Specifically, text parameters do not support inequality operators. In addition, any exception parameters with a Long or Long Raw Data type are not available for defining conditions, since they cannot be used to perform comparisons anyway. The only reason to add such parameters to an exception is to pass them from a non-queried data source through to an event as additional information to present to users in the event interface.
For all data types, if you use the operators IS and IS NOT, the value must be specified as NULL.
For varchar2 and Boolean data types, the only other options are = and !=.
For date and number data types, the operators <, <=, >, >=, =, and != are also available.
Character and Boolean parameters allow = and != operators.
Numbers and dates allow inequality operators as well.
Specifies whether the selected parameter is being compared to a parameter or a parameter value. The default setting is Value, with the Value field set up for the appropriate data type.
A parameter can only be compared to another parameter when a parameter of the same type exists on the exception or event (that is, if there are available parameters to compare the parameter against). Otherwise, the parameter must be compared to a value.
Parameter or Value
This field specifies the parameter or value to which the selected parameter is being compared.
Depending on the data type of the parameter, the controls on this field change. In some cases, when making a value comparison, a list item, a date button, or an LOV button is available to help you choose an appropriate value. For example, for dates, a date button is displayed to enable entering a date. For parameters with a code type, clicking the LOV button displays a list of appropriate code values from which you can choose.
Down Arrow Button
The Down button adds the condition in the condition editor into the condition list for the exception or rule. The fields of the condition editor remain filled with the values for the condition. You can either continue to define more conditions on the same parameter, or click the Clear button to clear the fields.
Up Arrow Button
The Up button removes the condition from the condition list, and puts it in the condition editor. Click this button to edit or delete existing conditions.
Clear Button
The Clear button clears the condition editor fields.
Below the condition editor is a list of the conditions currently defined for the exception or rule. The conditions defined for an exception or event are treated as logical AND conditions, as described earlier in this topic.
Adding a Condition
Choose a parameter from the list.
(For exceptions only) Specify whether you want to be notified of the change to the parameter.
Choose an operator from the list.
Choose whether you want to compare the parameter to a value or another parameter.
Specify the value or parameter to which the parameter will be compared.
Click the button. The condition is added to the condition list below the editor.
Editing a Condition
Select the condition from the condition list.
Click the button to move it into the condition editor.
Modify the definition as needed, for example, changing the operator or the value to which the parameter is compared.
When done, click the button to add the condition back to the condition list for the exception or rule.
Deleting a Condition
Select the condition from the condition list.
Click the button to move it into the condition editor. The exception condition is left in the edit section, since the only way to edit a condition is remove it, change it, then add it back to the exception conditions.
If you want to remove an exception condition and then add another, remove the condition, and then change the first parameter. Or, click the button to clear the fields and start with a new exception condition.
|
 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
