Delivery instruction combinations
By defining delivery instruction combinations, you can control which delivery instructions may be combined with each other, i.e. assigned to the same business object at the same time.
Combinations of delivery instructions selected for a business object are not automatically checked, when a delivery instruction is added.
Instead, an action (Prüfe die Lieferhinweiskombinationen) has to be triggered explicity, i.e. by an event handler
Delivery instructions can be defined in the dynamic enumerations (Delivery instruction).
(1) New, Delete, Cancel, Copy, Save: The values for delivery instruction combinations can be saved in the database.
(2) Owner: The owner of the delivery note combination.
(3) Name, Description: The name and description of the delivery instruction combination.
(4) Assign: The selected delivery instruction combination can be assigned to association criteria. This way, you can configure the combination to be checked or selected (see Association criteria).
►IMPORTANT◄ Should no delivery instruction combination be found, then all such combinations are allowed.
(5) The list of defined delivery instruction combinations.
The image shows the dialog for configuring rules for the combinations of delivery instructions in a matrix formed by displaying all delivery instructions as rows (1) and columns (2). Each intersection point in the cross table thus spanned corresponds to a specific combination of two delivery notes, which is either allowed (green tick) or not (red 'X').
►IMPORTANT◄ Whether two delivery notes, e.g. 'A' and 'B', may be combined with each other applies without consideration of the order. Specifically: If 'A can be combined with B' applies, 'B can be combined with A' also applies.
In the matrix, both variants nevertheless appear as independent 'boxes' that can be selected or deselected. Any change for one combination is automatically assigned in the matrix also for the opposite combination, so that no conflicting rules can be configured.
The boxes along the diagonal (from top left to bottom right) are meaningless because they would formally concern the combination of a particular delivery instruction 'with itself' and this situation cannot occur in practice. The same delivery instruction cannot be assigned to the same business object more than once in any case.
In connection with the extension keys (Ctrl, Shift, Alt) mass changes are possible by mouse click in the matrix. The value (allowed
or forbidden
) at the mouse cursor position is toggled on click and transferred to all target fields (see table).
Shortcut |
Pattern |
Target range |
Strg + C l ick |
|
from mouse cursor to the right |
Strg + Shift + C l ick |
|
from mouse cursor to the left |
Alt + C l ick |
|
from mouse cursor down |
Alt + Shift + C l ick |
|
from mouse cursor up |
Shift + C l ick |
|
from mouse cursor diagonally down/right |
Alt + Strg + C l ick |
|
from mouse cursor area right/below |
Alt + Strg + Shift + C l ick |
|
from mouse cursor area left/above |