How To Fix CN807 - Relationship cannot be deleted, it is currently being processed

SAP Error Message - Details

• Message type: E = Error

• Message class: CN - Meldungen für Netzpläne

• Message number: 807

• Message text: Relationship cannot be deleted, it is currently being processed

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 CN807 - Relationship cannot be deleted, it is currently being processed ?

  The SAP error message CN807 ("Relationship cannot be deleted, it is currently being processed") typically occurs in the context of project management or network activities within SAP, particularly in the Project System (PS) module. This error indicates that there is an attempt to delete a relationship (such as a dependency between tasks or activities) that is currently being processed or is locked by another transaction.
  Causes:
  
  Active Processes: The relationship you are trying to delete is currently being used by an active process, such as a background job or a transaction that is still running.
  Locking Mechanism: SAP uses a locking mechanism to prevent data inconsistencies. If another user or process is accessing the same relationship, it cannot be deleted until that process is completed.
  Incomplete Transactions: If there are incomplete transactions or updates related to the project or network, it may prevent the deletion of relationships.
  User Authorizations: Sometimes, insufficient authorizations can lead to issues when trying to modify or delete relationships.
  
  Solutions:
  
  Check Active Processes: Verify if there are any active processes or transactions that are using the relationship. You can use transaction codes like SM50 (to check active work processes) or SM66 (to check global work processes) to identify any locks.
  Wait and Retry: If the relationship is being processed by another transaction, wait for that transaction to complete and then try deleting the relationship again.
  Release Locks: If you have the necessary authorizations, you can use transaction code SM12 to check for and release any locks that may be preventing the deletion.
  Check for Incomplete Transactions: Use transaction codes like CJ20N (Project Builder) or CN41 (Network Overview) to check for any incomplete transactions or inconsistencies in the project structure.
  User Authorizations: Ensure that you have the necessary authorizations to delete relationships. If not, contact your SAP security administrator to review your permissions.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CJ20N (Project Builder), CN41 (Network Overview), SM12 (Lock Entries), SM50/SM66 (Work Process Overview).
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message. You can search the SAP Support Portal for updates or patches.
  Documentation: Review SAP documentation related to Project System and network management for best practices on managing relationships and dependencies.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or technical support team for further investigation.