Example Message Determination: Processing Condition Component Hierarchies 
If a business application transfers a procedure for message determination to Message Control, all output types in the procedure are searched. The following diagram shows the output types Order confirmation and Internal mail in the procedure Order.

During message determination for an output type, the access sequence is processed, i.e. all condition tables in this access sequence are accessed sequentially.
In the above example, there are two condition tables (001 and 002) for the access sequence 0001 and therefore for the message Order confirmation.
The order confirmation access sequence refers successively to the tables listed below with the corresponding keys:
Table |
Key |
Indic. "Exclusive" |
Condition table 001 |
Sales organization customer number |
According to strategy:set or not set |
Condition table 002 |
Sales organization |
No difference in example |
Condition table 001 therefore contains more specific conditions (sales organization / customer number) than condition table 002 (only sales organization) for the sending of an order confirmation. In the case of an exclusive exit strategy for table 001, table 002 is no longer accessed when a condition from table 001 has been met. As there is not a third table behind table 002 in the access sequence, it makes no difference in this example if the exit strategy for this table is inclusive or exclusive.
You can assign the following condition components with conditions written in ABAP:
The value of the system return code at the end of the condition determines whether the condition table of this output type is accessed. If the result is negative (Return code <> 0), processing in the procedure continues, that is to say, the next output type in the procedure is processed.
If the system return code is <> 0 at the end of the condition, processing of the access sequence continues.