How To Fix /SAPCND/DD_CUSTOMIZE114 - Condition table &1 is still being used, and was therefore not deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/DD_CUSTOMIZE -

• Message number: 114

• Message text: Condition table &1 is still being used, and was therefore not deleted

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/DD_CUSTOMIZE114 - Condition table &1 is still being used, and was therefore not deleted ?

  The SAP error message /SAPCND/DD_CUSTOMIZE114 indicates that a condition table (identified by &1) is still in use and cannot be deleted. This typically occurs in the context of customizing condition tables in the SAP system, particularly when working with pricing, discounts, or other condition-based functionalities.
  Cause:
  
  Active Usage: The condition table is currently being used in one or more condition records. This means that there are existing entries that reference this condition table, preventing its deletion.
  Dependencies: The condition table may be linked to other objects or configurations, such as pricing procedures, access sequences, or condition types.
  Custom Code: There may be custom code or enhancements that reference the condition table, which would also prevent deletion.
  
  Solution:
  To resolve this error and successfully delete the condition table, follow these steps:
  
  
  Check Usage:
  
  Use transaction code SE11 (Data Dictionary) to check the condition table's usage. You can look for any existing condition records that reference this table.
  Use transaction code VK13 (Display Condition) to see if there are any condition records associated with the table.
  
  
  
  Delete Condition Records:
  
  If you find that there are condition records using the table, you will need to delete these records first. Use transaction code VK11 (Create Condition) or VK12 (Change Condition) to manage these records.
  
  
  
  Review Dependencies:
  
  Check if the condition table is part of any pricing procedures or access sequences. You can do this by navigating to the relevant configuration areas in the SAP IMG (Implementation Guide).
  If the table is linked to any pricing procedures, you may need to remove it from those procedures before attempting to delete it.
  
  
  
  Custom Code Review:
  
  If there is custom code that references the condition table, you will need to modify or remove that code to allow for the deletion of the table.
  
  
  
  Retry Deletion:
  
  Once you have ensured that the condition table is no longer in use, you can attempt to delete it again using transaction code SE11.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SE11: Data Dictionary
  VK11: Create Condition
  VK12: Change Condition
  VK13: Display Condition
  
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or updates related to this error message.
  Documentation: Review SAP documentation on condition tables and their management for best practices and additional insights.
  
  By following these steps, you should be able to identify the cause of the error and take the necessary actions to resolve it.