Strategy "Inclusive Access Sequence" 
Consider the following access sequence
Table |
Key |
Indic. "Exclusive" |
001 |
Sales organization customer number |
not set |
002 |
Sales organization |
not set |
with access to the following two condition tables:
Condition table 001
Sales organization |
Customer |
Partner function |
Transmission medium |
Language |
Processing time |
0001 |
Company1 |
Sold-to party |
2 Fax |
English |
Immediately |
0002 |
Company2 |
Sold-to party |
6 EDI |
German |
Night |
Condition table 002
Sales organization |
Partner function |
Transmission medium |
Language |
Processing time |
0001 |
Sold-to party |
1 Print |
German |
Immediately |
0002 |
Sold-to party |
1 Print |
English |
Immediately |
This definition of the condition components leads to the following scenario at message determination:
In sales organizations 0001 and 0002, the order confirmation is normally printed in German immediately at order entry, and is addressed to the sold-to party. If, however, the sold-to party in sales organization 0001 is "Company 1," a fax is also sent in English. If the sold-to party in sales organization 0002 is "Company 2," an order confirmation will also be sent in German via EDI that night.

Documents of one output type which are sent at the same time must differ from each other with regard to at least one of these attributes (key for the table of the
·
Partner function·
Partner·
LanguageIf the attributes are not different and multiple processing is still required, several output types must be defined in the procedure.
The "inclusive access sequence" strategy has the results described above because the message status records found at the same time have different language attributes.
Condition table 001 is evaluated before condition table 002 at message determination. A diagram illustrating this example can be found in:
Message determination: Processing condition component hierarchies