How To Fix DO936 - DDL source & is still referenced

SAP Error Message - Details

• Message type: E = Error

• Message class: DO - Dictionary: Mass activation of domains and data elements

• Message number: 936

• Message text: DDL source & is still referenced

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 DO936 - DDL source & is still referenced ?

  The SAP error message DO936 indicates that a Data Definition Language (DDL) source is still being referenced, which typically means that there are database objects (like tables, views, or indexes) that are dependent on the DDL source you are trying to modify or delete. This can occur in various scenarios, such as when you attempt to delete or modify a database object that is still in use or has dependencies.
  Cause:
  
  Dependencies: The DDL source you are trying to change or delete is still being referenced by other database objects.
  Active Sessions: There may be active sessions or transactions that are using the DDL source.
  Incorrect Deletion Order: Attempting to delete or modify objects in the wrong order can lead to this error.
  
  Solution:
  
  Check Dependencies: Use transaction codes like SE11 (Data Dictionary) or SE14 (Database Utility) to check for dependencies. Look for any objects that reference the DDL source.
  Remove References: If there are dependent objects, you will need to either drop or modify those objects before you can proceed with the changes to the DDL source.
  Check Active Sessions: Ensure that there are no active sessions or transactions that are using the DDL source. You can use transaction code SM12 to check for locked entries.
  Use the Right Order: If you are performing multiple changes, ensure that you are following the correct order of operations. For example, drop dependent objects before dropping the DDL source.
  Transport Requests: If the DDL source is part of a transport request, ensure that the transport is not currently being processed.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE14 (Database Utility), and SM12 (Lock Entries).
  Documentation: Refer to SAP documentation for more details on managing database objects and understanding dependencies.
  SAP Notes: Check for any relevant SAP Notes that might provide additional insights or solutions for this specific error.
  
  If the issue persists after following these steps, consider reaching out to your SAP Basis team or consulting SAP support for further assistance.