In Product Interchangeability, determining when a product can be used as a substitute is just as important as determining which product can be used.
Business scenarios such as product phase-ins, phase-outs, inventory depletion, and successor product introductions often require substitution decisions to be based on specific dates. To support these requirements, Product Interchangeability provides flexible Date Usage options that define how substitute validity is calculated during Alternative-Based Confirmation (ABC).
In this blog, we will explore the available Date Usage options and understand how they influence substitution determination.
Why Do We Need Date Usage?
Consider a scenario where Product A is being replaced by Product B.
Although Product B has already been introduced, the business may still want to continue selling the remaining inventory of Product A until existing stock is exhausted. In other situations, planning dates generated by planning systems may need to drive substitution validity.
To support these varying requirements, Product Interchangeability allows different methods for calculating substitution validity periods.
The behaviour is controlled using the Date Usage field maintained at the collection level.
Note: Date Usage is mandatory for aATP-relevant collections.
Available Date Usage Options
Let’s understand the different options available with an example.
Example: Consider the below chain with the following attributes maintained.
Use Validity Dates (V)
This option uses:
- Valid From
- Valid To
- Use-Up Strategy
- Use-Up Date
to determine substitute validity
In the above example substitution between V1 and V2 Valid from indicates the time from when V2 is valid to substitute V1 and valid-to indicates the time-period until when V2 can substitute V1
When a successor product becomes available, the predecessor product can be handled in different ways. Use-up helps to handle these cases effectively
Use-Up Options:
- 1. Use-Up = Yes
The predecessor product can continue to be used indefinitely.
- 2. Use-Up = No
The predecessor product can no longer be used once the successor becomes valid. The predecessor immediately becomes unavailable once the successor reaches its validity start date.
- 3. Use-Up = Restricted
The predecessor product can be used until the specified Use-Up Date. Use-up date is mandatory for Use-up restricted
Note: Use-up takes the precedence over the valid-to defined for a product
Applying the rules described for the above example, the dates for the substitutes are as follows:
Product | Valid from | Valid to |
V1 |
|
|
V2 | 01-01-2026 | 10-07-2026 |
V3 | 15-05-2026 | 31-12-2026 |
V1:
Valid from: The first product in the chain is active and in use, therefore it is already valid
Valid-to: Valid-to for V1 would be based on the use-up maintained in the attributes for V1 to V2. Since the use-up is empty Valid to indicates an indefinite usage of V1
V2:
Valid from: V2 is valid for substitution from 01-01-2026
Valid-to: At first glance, the valid-to date might appear to be 01-06-2026, but substitution V2 to V3 has use-up defined and as use-up is applicable for the predecessor until when it can be used. The valid-to of V2 is 10-07-2026 rather than 01-06-2026
V3:
Valid from: V3 is valid for substitution from 15-05-2026
Valid-to: As there are no substitutions defined further to read the use-up, valid to is the date time defined on the substitution
Use Planning Dates (P)
This option uses:
- Successor Product Planning Date (SPPD)
- Stock Exhaustion Date (SED)
Calculation Logic
- SPPD determines the validity start for the successor.
- SED determines the validity end for the predecessor.
This approach is useful when planning services generate milestone dates.
Applying the logic for the above example, the dates for the substitutes are as follows:
Product | Valid from | Valid to |
V1 |
| 30-01-2026 |
V2 | 05-01-2026 |
|
V3 | 31-05-2026 |
|
V1:
Valid from: The first product in the chain is active and in use, therefore its already valid
Valid-to: SED defined on the substitution V1 to V2
V2:
Valid from: V2 is planned from 05-01-2026 by the definition of SPPD
Valid-to: SED is not defined on the substitution V2 to V3 indicating an indefinite usage
V3:
Valid from: V3 is planned from 31-05-2026 by the definition of SPPD
Valid-to no subsequent substitution exists from which an SED can be derived, therefore, the product remains valid indefinitely
Planning Dates with Higher Priority (F)
This option prioritizes planning dates and automatically falls back to validity dates when planning dates are not available.
Priority Logic
- Use planning dates if maintained.
- If planning dates are unavailable, use validity dates
Applying the prioritization for the above example, the dates for the substitutes are as follows
Product | Valid from | Valid to |
V1 |
| 30-01-2026 |
V2 | 05-01-2026 | 10-07-2026 |
V3 | 31-05-2026 | 31-12-2026 |
V1:
Valid from: The first product in the chain is active and in use, therefore its already valid
Valid-to: SED defined on the substitution V1 to V2 [Planning]
V2:
Valid from: V2 is planned from 05-01-2026 by the definition of SPPD [Planning]
Valid-to: SED is not available and therefore derived validity date is used [Validity]
V3:
Valid from: V3 is planned from 31-05-2026 by the definition of SPPD [Planning]
Valid-to: There are no substitutions defined further to read the SED, therefore the fall-back validity date is used [Validity]
Conclusion
Different Date Usage options can produce different validity windows for substitute products. Selecting the appropriate configuration ensures accurate substitution determination and more effective order fulfillment. Proper master data maintenance is therefore essential for achieving optimal business outcomes
Learn more:
- Product Interchangeability in S/4HANA
- Product Interchangeability in ABC
- Product Interchangeability: Substitute Sequence Determination in ABC
Source link
