How To Fix 6E035 - Error while deleting the conditions

SAP Error Message - Details

• Message type: E = Error

• Message class: 6E - Messages for EMU currency conversion in Treasury

• Message number: 035

• Message text: Error while deleting the conditions

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 6E035 - Error while deleting the conditions ?

  The SAP error message 6E035 typically indicates that there is an issue when trying to delete condition records in the pricing procedure. This error can occur in various scenarios, such as when the condition records are locked, when there are dependencies on other records, or when the user does not have the necessary authorizations.
  Causes of Error 6E035
  
  Locked Condition Records: The condition records you are trying to delete may be locked by another user or process.
  Dependencies: There may be dependencies on the condition records you are trying to delete, such as being part of a pricing procedure that is still in use.
  Authorization Issues: The user may not have the necessary authorizations to delete the condition records.
  Data Integrity Issues: There may be inconsistencies or integrity issues in the database that prevent the deletion of the records.
  
  Solutions
  
  
  Check for Locks:
  
  Use transaction code SM12 to check if the condition records are locked by another user. If they are, you may need to wait for the lock to be released or contact the user who has the lock.
  
  
  
  Review Dependencies:
  
  Ensure that the condition records are not being used in any active transactions or pricing procedures. You may need to deactivate or remove dependencies before attempting to delete.
  
  
  
  Authorization Check:
  
  Verify that the user has the necessary authorizations to delete condition records. This can be checked in transaction code SU53 or by consulting with your SAP security team.
  
  
  
  Data Integrity Check:
  
  If you suspect data integrity issues, you may need to run consistency checks or consult with your SAP Basis team to investigate any underlying database issues.
  
  
  
  Use Transaction Codes:
  
  You can use transaction codes like VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) to manage condition records. Ensure you are following the correct procedures for deletion.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  
  
  Related Information
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11, VK12, VK13, and SM12 for managing condition records and checking locks.
  SAP Documentation: Review SAP documentation related to pricing and condition records for a deeper understanding of how they work and how to manage them effectively.
  SAP Community: Engage with the SAP Community forums for insights and solutions from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to escalate the issue to your SAP support team or consult with an SAP expert for further assistance.