The processing following an exceptional situation defined as an exception recognized by the Early Warning System can be undertaken by a workflow. This exception must trigger an event entered as a triggering event of a workflow.

The Early Warning System is based on the key figures of the Logistics Information System (LIS). The Early Warning System can be used in decisions to make selections and check weak points within Logistics. The Early Warning System enables you to search for exceptional situations, thus helping you to recognize and rectify potential problems at an early stage.

You define the exceptional situations as exceptions within the Early Warning System. An exception consists of the specification of characteristics and/or characteristic values (such as vendor, material) and conditions. Conditions can be created as threshold values (such as materials/vendors with an order value greater than $5000), as trends (such as a positive trend in the order value) or as planned/actual comparisons.

This function is not available in a separated Basis system.

The assignment between an exception and a business object type/event must be maintained in a system table. Then the system creates the event when an exception is recognized.

In connection with the event creation, the system fills the event container with the following information about the exception at runtime:

• The characteristic values when the exception was triggered
• The key figures when the exception was triggered

To enable you to define a binding, with which this information is brought from the event container to the workflow container, you must define the characteristics and key figures as event parameters for the event in the Business Object Builder.

You make entries in a control table to define which LIS exception is assigned to which object type/event.