Business Contexts

Use

To group exceptions and define their validity, you assign them to a business context in each case. The business context defines the circumstances in which the exception can be set. Each exception is valid in one certain business context only. You should not use the exception Communication point locked on a communication channel, for example, or HU errors on a storage bin.

The execution step is a further characteristic enabling you to regulate the validity of exceptions. In the MFS, the following execution steps are defined:

  • A0 - Processing in background (for example, inbound telegram)

  • A1 - Processing at desktop

The system always sets execution step A0 if processing triggered by a PLC telegram results in the occurrence of an exception.

The execution step A1 applies to events triggered by an operator action (for example, at the warehouse management monitor).

If you want it to be possible for an exception to be set by an operator, you must define it for the execution step A1.

If the exception (and the follow-on processing linked to it) is to have validity in the case of an automatic event, you must define it for the execution step A0.

The following table contains situations in which errors are liable to occur (for which you should therefore define exceptions) and the context used by the program in each case.

Context

Description

Situation in which the system sets the context

MF1

MFS - Communication channel

  • If the confirmation telegram contains a communication error

  • If it is not possible to send a telegram

    The system chooses the exception maintained on the communication channel.

  • When the status on the communication channel is set or released.

    At the time of status setting, the system chooses the exception maintained on the communication channel. At the time of status release, the system chooses the exception assigned to the internal exception MFS6.

MF2

MFS - Transportation segment/group

  • When the status on the conveyor segment is set or released. At the time of status setting, the system chooses the exception determined on the basis of the telegram error or entered by the user. At the time of status release, the system chooses the exception assigned to the internal exception MFS2.

  • When the status on the conveyor segment group is set or released.

    At the time of status setting, the system chooses the exception determined on the basis of the telegram error or entered by the user. At the time of status release, the system chooses the exception assigned to the internal exception MFS2.

MF3

MFS - Telegram

  • If an error code is detected in the telegram in the action modules

    The system uses the exception that it determined on the basis of the telegram error.

  • If an error telegram is to be sent due to a semantic or syntactical error in the telegram received.

    The system determines a telegram error via the error type (for example, start sequence incorrect, sequence number incorrect) and the exception via the telegram error.

  • If the system recognizes the internal exception MFS7 - Unknown HU reported

MF4

MFS - Resource

  • When the status on the resource is set or released.

    At the time of status setting, the system chooses the exception determined on the basis of the telegram error or entered by the user. At the time of status release, the system chooses the exception assigned to the internal exception MFS4.

MF5

MFS - Communication point

  • When the status on the communication point is set or released.

    At the time of status setting, the system chooses the exception determined on the basis of the telegram error or entered by the user. At the time of status release, the system chooses the exception assigned to the internal exception MFS5.

MF6

MFS - Telegram for Case Conveyor System

  • If an error code is detected in the telegram in the action modules.

    The system uses the exception that it determined on the basis of the telegram error.

Reading of Table: Example:

If you define an exception that is to lay down a reaction to an error code in an incoming confirmation, you must use the context MF1 and execution step A0 for this purpose. Otherwise, the EWM system is not able to find the exception and the desired reaction cannot occur.