How To Fix WRF_DISPRO060 - Overlap for &1, &2, between &3 and &4 was resolved

SAP Error Message - Details

• Message type: E = Error

• Message class: WRF_DISPRO -

• Message number: 060

• Message text: Overlap for &1, &2, between &3 and &4 was resolved

What causes this issue?

The time-dependent minimum and maximum stock levels for promotions in
the time period specified overlap for the combination of material and
plant.
For the combination of material and plant for different promotions, you
have entered time-dependent data for overlapping time periods
(transaction WRF_DISP_PROMO).

System Response

The standard method was used to resolve the overlap.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WRF_DISPRO060 - Overlap for &1, &2, between &3 and &4 was resolved ?

  Certainly! Here's a detailed explanation for the SAP error message:
  
  SAP Message:
  WRF_DISPRO060
  Text: Overlap for &1, &2, between &3 and &4 was resolved
  
  1. 
  Cause:
  This message typically occurs in the context of SAP Variant Configuration (VC), specifically during the processing of dependencies or characteristic value assignments in the configuration model.
  
  The message indicates that there was an overlap detected between two intervals or ranges for a characteristic or a dependency condition.
  For example, if two dependencies or characteristic value assignments have overlapping validity intervals or overlapping value ranges, SAP detects this conflict.
  The system then automatically resolves this overlap to maintain consistency in the configuration model.
  The placeholders (&1, &2, &3, &4) represent:
  &1: Object type (e.g., characteristic, dependency)
  &2: Object name or identifier
  &3 and &4: The overlapping interval or range boundaries
  
  
  
  
  2. 
  Solution:
  
  Review the overlapping intervals or ranges in the configuration model:
  Check the characteristic value assignments or dependencies that are causing the overlap.
  Adjust the intervals or ranges to avoid