How To Fix 60335 - Conditions with date & already exist

60335 - Overview

• Message type: E = Error

• Message class: 60 - Real Estate

• Message number: 335

• Message text: Conditions with date & already exist

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message 60335 - Conditions with date & already exist ?

  The SAP error message 60335, which states "Conditions with date & already exist," typically occurs in the context of pricing or condition records in SAP. This error indicates that there is an attempt to create or modify a condition record (such as pricing, discounts, etc.) for a specific date that already has an existing condition record.
  
  Cause:
  
  Duplicate Condition Records: The most common cause is that there is already a condition record for the same key (e.g., material, customer, pricing type) and the same validity date range.
  Incorrect Date Entry: The date you are trying to enter may overlap with an existing record's validity period.
  Data Entry Errors: Mistakes in data entry, such as entering the wrong date or condition type.
  
  
  Solution:
  
  
  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.
  Verify if there is already a record for the date you