Example of Execution of Several
Rules
A product is managed in several locations. If a requirement is produced for this product, you should check according to the logic of the product availability check if the product is available in a location at the requested time. If this is not the case, a confirmation should be made at the end of the checking horizon. The aim is that the sales order is fully confirmed.
This request cannot be represented via a single location determination. Taking the checking horizon into account, the system will propose the first substitution with confirmation at the end of the checking horizon. No more substitutions are checked. If you were to work in this case without a checking horizon, the sales order would have an unconfirmed partial quantity.
For this reason, two almost identical rules are created that differ simply in the maximum delay permitted in the calculation profile. A calculation profile can only allow a delay of 0 days. Only the ATP quantity is thereby taken into account for the material availability date; that is, the system prevents the confirmation that is produced via the ATP check using the checking horizon from being accepted.
When assigning the rule strategy you should ensure that the handling of the calculation profile is set to replacement. Via the condition technique you must ensure that both rules are used and that the rule that has the restriction regarding the maximum delay is used first.

The maximum delay must not be 0. It is sufficient if it is shorter than the minimum checking horizon.

In the check instructions the Start immed. indicator must be set.
· Product P1
· Location L1
· Check mode 031 (product availability check, rules-based ATP).
· Check instructions: product availability check, rules-based ATP and start immediately
· Check control; checking horizon switched on
· Business Event A
· Requirements date 20.07.2000
· Requirements quantity 300,000.000
· Rule 1: location substitution: L1 by L2, calculation profile: allowed delay = 0 is valid
· Rule 2: location substitution: L1 by L2; no calculation profile
· Combination of rules via two condition types
Hierarchical Display
Requirements Group |
Product/Location |
Date/Time |
Requirement Quantity |
Confirmed Quantity |
Symbol |
1. Requirements Group |
P1/ L1 |
20.07.2000 |
300.000,000 |
2013 |
|
|
P1/ L2 |
20.07.2000 |
297.987 |
0 |
|
2. Requirements Group |
P1/ L1 |
20.07.2000 |
297.987 |
0 |
|
In the second requirements group P1/L1 is confirmed for 20.07.2000 with 0; there is, however, a confirmation proposal (green light), that proposes 297,987 pieces for 18.09.2000 (at the end of the checking horizon or replenishment lead time).
Confirmation proposal 1
Product/Location |
Material Availability Date |
Confirmed Quantity |
P1/ L1 |
20.07.2000 |
2.013 |
Confirmation proposal 2
Product/Location |
Material Availability Date |
Confirmed Quantity |
P1/ L1 |
18.09.2000 |
297.987 |
See also:
Product Availability
Check Using the Checking Horizon