Event action – Abstract
Purpose: Checks whether the combination of the delivery instruction attributes selected for the reference object is permissible against the background of applicable Delivery instruction combinations (matrix), if any.
Tooltip
Usage: Executed in the context of a reference object, the event action checks its delivery instruction attributes for invalid Delivery instruction combinations.
Output: Error message (abort/exception with rollback of the transaction), with a listing of all invalid Delivery instruction combinations for the reference object.
Note: Delivery instruction attributes are available only for Shipments and Orders, not for Common business object and Manifests.
See also: Delivery instruction, Delivery instruction combinations
The event action Check delivery instruction combinations checks whether the combination of delivery instruction attributes selected for the reference object is permissible against the background of any applicable Delivery instruction combinations (matrix).
Delivery instruction attributes can only be used for the business transaction object types Orders and Shipments. They are not available for Manifests and Common business object.
The matrix of Delivery instruction combinations determined according to the best-matching principle via Association criteria is always decisive for the check.
If no Delivery instruction combinations are applicable on the basis of the Association criteria to be met in the data context, all associations shall be deemed permissible.
If the reference object has at least one pair of two 'non-combinable' delivery instruction attributes, this triggers an error message that causes the event handling to be aborted and, if necessary, also causes a rollback of the transaction.
The error message lists all combinations of delivery instructions that are considered incompatible, based on the applicable matrix of Delivery instruction combinations (see the example below).
Configuration
The business transaction object to be checked must exist as a reference object for the event action.
The event action does not use any parameters.
Example
For a given type of Orders, the following matrix for Delivery instruction combinations is applicable:
Specifically, this means that only two of the three available delivery instructions may be combined, namely 'Same Day Delivery' and 'Notification by driver (...)'.
'Same Day Delivery' and 'Click And Collect' concern an exclusive selection (correspondingly: EITHER delivery OR pickup).
In connection with a pickup stated by the delivery instruction 'Click And Collect', the instruction 'Notification by driver (...)' is meaningless.
Technically, the delivery instructions in the input form for purchase orders should initially be able to be freely combined and saved in a Repeatable element container without any restrictions.
The valid combination of delivery instructions should only be checked in the course of the 'release' of a purchase order. The working state 'Released' should only be assigned with a combination of permissible delivery instructions.
Configuration:
To check the delivery instruction combinations for an order 'in the course of release', an event handling is created and configured as shown on the right:
â–ºNOTEâ—„ If further checks that issue confirmations are relevant for the release, these should be placed before the event action Check delivery instruction combinations, since this reacts to any conflicts by 'error', which causes the immediate cancellation of the event handling (and if necessary a rollback of the transaction). |
|
Runtime example:
When attempting to assign the working state 'Released' to a purchase order for which all three available delivery instructions are used, the following error message appears:
