How To Fix COM_PME_DEPEDI036 - Error when deleting: Dependency '&' was not saved

SAP Error Message - Details

• Message type: E = Error

• Message class: COM_PME_DEPEDI - Dependency Editor Messages

• Message number: 036

• Message text: Error when deleting: Dependency '&' was not saved

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 COM_PME_DEPEDI036 - Error when deleting: Dependency '&' was not saved ?

  The SAP error message COM_PME_DEPEDI036 typically occurs when you attempt to delete a dependency in the Product Master or similar areas, and the system indicates that the dependency was not saved. This can happen for several reasons, and understanding the cause is crucial for finding a solution.
  Cause:
  
  Dependency Not Saved: The dependency you are trying to delete may not have been saved properly in the first place. This could be due to a previous error during the creation or modification of the dependency.
  Data Integrity Issues: There may be data integrity issues or inconsistencies in the database that prevent the deletion of the dependency.
  Authorization Issues: The user may not have the necessary authorizations to delete the dependency.
  System Locking: The dependency might be locked by another user or process, preventing deletion.
  Configuration Issues: There may be configuration settings in the system that restrict the deletion of certain dependencies.
  
  Solution:
  
  Check Dependency Status: Verify if the dependency you are trying to delete exists and is in a valid state. You can do this by navigating to the relevant transaction and checking the dependency details.
  Re-save the Dependency: If the dependency was not saved correctly, try to re-save it and then attempt to delete it again.
  Check Authorizations: Ensure that you have the necessary authorizations to delete dependencies. You may need to consult with your SAP security team.
  Unlock the Dependency: If the dependency is locked, you may need to wait for the other user to finish or contact your system administrator to unlock it.
  Review Configuration Settings: Check if there are any configuration settings that might be preventing the deletion of dependencies. This may require assistance from your SAP Basis or configuration team.
  Consult SAP Notes: Look for any relevant SAP Notes that might address this specific error. SAP frequently updates its knowledge base with solutions for known issues.
  Debugging: If you have access to debugging tools, you can analyze the program flow to identify where the error is occurring.
  
  Related Information:
  
  Transaction Codes: Depending on where you are encountering this error, you may be using transaction codes like C223 (Change BOM) or C201 (Create BOM).
  SAP Support: If the issue persists, consider reaching out to SAP Support for further assistance. Provide them with the error message and any relevant details about the steps leading to the error.
  Documentation: Review SAP documentation related to Product Master Data Management and dependencies for additional context and troubleshooting steps.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution.