How To Fix /SAPCND/MASTERDATA035 - Cond. record was not deleted successfully from the condition table

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/MASTERDATA -

• Message number: 035

• Message text: Cond. record was not deleted successfully from the condition table

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 /SAPCND/MASTERDATA035 - Cond. record was not deleted successfully from the condition table ?

  The SAP error message /SAPCND/MASTERDATA035 indicates that a condition record was not deleted successfully from the condition table. This error can occur in various scenarios, particularly when dealing with pricing conditions, discounts, or other condition records in SAP.
  Causes:
  
  Authorization Issues: The user may not have the necessary authorizations to delete condition records.
  Data Integrity Constraints: There may be dependencies or constraints that prevent the deletion of the condition record. For example, if the condition record is being used in an active sales order or contract, it cannot be deleted.
  Technical Issues: There could be a technical issue, such as a database lock or a problem with the underlying data structure.
  Incorrect Condition Table: The condition record may not exist in the specified condition table, or the table may not be correctly configured.
  Custom Logic: Custom enhancements or user exits may be preventing the deletion of the condition record.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to delete condition records. This can be checked in transaction SU53 after the error occurs.
  Check Dependencies: Verify if the condition record is being used in any active documents (like sales orders, contracts, etc.). If it is, you will need to remove or change those documents before deleting the condition record.
  Review Logs: Check the application logs (transaction SLG1) for more detailed error messages that can provide insights into why the deletion failed.
  Database Locks: Ensure that there are no database locks on the condition table that might be preventing the deletion. You can check for locks using transaction SM12.
  Custom Code Review: If there are any custom enhancements or user exits related to condition records, review them to ensure they are not interfering with the deletion process.
  Use Transaction Codes: Use transaction codes like VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) to manage condition records properly.
  Consult SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide patches or updates.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes related to condition records, such as VK11, VK12, VK13, and VK31 (for mass changes).
  Condition Tables: Understand the structure and configuration of condition tables in your SAP system, as this can impact how condition records are managed.
  SAP Documentation: Refer to SAP Help documentation for detailed information on condition records and their management.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP Basis or technical team for further investigation.