How To Fix 60656 - A condition already exists per & (Change valid-from date)

SAP Error Message - Details

• Message type: E = Error

• Message class: 60 - Real Estate

• Message number: 656

• Message text: A condition already exists per & (Change valid-from date)

What causes this issue?

A condition record already exists which should be valid later than the
date which you have just specified for the rental agreement.

System Response

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

How to fix this error?

Select a valid-as-from date which is after the date entered.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 60656 - A condition already exists per & (Change valid-from date) ?

  The SAP error message 60656, which states "A condition already exists per & (Change valid-from date)," typically occurs in the context of condition records in SAP, particularly when dealing with pricing, discounts, or other condition types in the Sales and Distribution (SD) or Materials Management (MM) modules.
  Cause:
  This error arises when you attempt to create or change a condition record with a validity period that overlaps with an existing condition record. Specifically, it indicates that there is already a condition record for the same key (e.g., material, customer, pricing type) that has a valid-from date that conflicts with the date you are trying to set.
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Existing Condition Records:
  
  Use transaction codes like VK13 (Display Condition) or VK12 (Change Condition) to view existing condition records for the relevant condition type.
  Identify any overlapping records that may be causing the conflict.
  
  
  
  Adjust Validity Dates:
  
  If you find an existing condition record that overlaps with the new record you are trying to create or change, you can either:
  
  Change the validity dates of the existing record to avoid the overlap.
  Delete the existing record if it is no longer needed (ensure this is in line with business processes).
  
  
  
  
  
  Create New Condition Record:
  
  After resolving the conflict, you can proceed to create or change the condition record with the desired valid-from date.
  
  
  
  Consult Documentation:
  
  If you are unsure about the implications of changing or deleting condition records, consult your organization's documentation or speak with a functional consultant.
  
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  VK11 (Create Condition)
  VK12 (Change Condition)
  VK13 (Display Condition)
  
  
  
  Condition Types: Understand the specific condition type you are working with, as different condition types may have different rules and implications.
  
  
  Authorization: Ensure you have the necessary authorizations to view, change, or delete condition records.
  
  
  Business Impact: Consider the business impact of changing condition records, especially if they are related to pricing agreements or contracts.
  
  
  By following these steps, you should be able to resolve the error and successfully manage your condition records in SAP.