How To Fix /SAPCND/MASTERDATA112 - Cond. record which had status 'released' is found with deleted marked.

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/MASTERDATA -

• Message number: 112

• Message text: Cond. record which had status 'released' is found with deleted marked.

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/MASTERDATA112 - Cond. record which had status 'released' is found with deleted marked. ?

  The SAP error message /SAPCND/MASTERDATA112 indicates that there is a condition record in the system that has a status of 'released' but is marked as deleted. This situation can occur in various scenarios, particularly when dealing with condition records in pricing, discounts, or other master data related to sales and distribution (SD) or materials management (MM).
  Cause:
  
  Data Inconsistency: The condition record may have been marked for deletion in the database, but the status has not been updated accordingly. This can happen due to manual changes, data uploads, or inconsistencies during data migration.
  System Errors: There may have been an error during the processing of condition records, leading to a mismatch between the status and the deletion flag.
  Custom Development: If there are custom programs or enhancements that manipulate condition records, they might not handle the deletion flag correctly.
  
  Solution:
  
  Check the Condition Record: Use transaction codes like VK13 (Display Condition) or VK12 (Change Condition) to check the status of the condition record in question. Verify if it is indeed marked as deleted.
  Restore or Delete the Record: If the condition record is needed, you may need to restore it by removing the deletion flag. If it is not needed, you should delete it properly to ensure consistency.
  Consistency Check: Run consistency checks for condition records using transaction SDBA or similar tools to identify and correct any inconsistencies in the database.
  Review Custom Code: If there are custom developments, review the code to ensure that it correctly handles the deletion flags and statuses of condition records.
  Consult SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide guidance on handling condition records.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes related to condition records, such as VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition).
  SAP Documentation: Refer to SAP Help documentation for detailed information on condition records and their management.
  Support: If the issue persists, consider reaching out to SAP support for assistance, especially if it involves complex data integrity issues.
  
  By following these steps, you should be able to resolve the error and ensure that your condition records are consistent and correctly managed in the SAP system.