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 |
|
|
MF2 |
MFS - Transportation segment/group |
|
|
MF3 |
MFS - Telegram |
|
|
MF4 |
MFS - Resource |
|
|
MF5 |
MFS - Communication point |
|
|
MF6 |
MFS - Telegram for Case Conveyor System |
|
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.