How To Fix DO935 - & DDL sources were deleted

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 935

• Message text: & DDL sources were deleted

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 DO935 - & DDL sources were deleted ?

  The SAP error message DO935 typically indicates that there is an issue related to Data Dictionary (DDL) sources being deleted. This can occur in various contexts, such as when working with database objects, transport requests, or during system upgrades.
  Cause:
  
  Deleted DDL Sources: The primary cause of the DO935 error is that the DDL sources (like database tables, views, or other objects) that are referenced in your program or transport request have been deleted or are no longer available in the system.
  Transport Issues: If you are trying to transport objects that depend on DDL sources that have been deleted in the target system, this error can occur.
  Inconsistent State: The system may be in an inconsistent state due to incomplete transports or failed updates.
  
  Solution:
  
  Check Object Existence: Verify if the DDL sources that are causing the error still exist in the database. You can do this by checking the Data Dictionary (SE11) for the relevant objects.
  Restore Deleted Objects: If the objects were deleted accidentally, you may need to restore them from a backup or recreate them if possible.
  Transport Request Review: If the error occurs during a transport, review the transport request to ensure that all necessary objects are included and that there are no missing dependencies.
  Rebuild DDL Sources: If the DDL sources are part of a development object, you may need to rebuild them in the development environment and re-transport them to the target system.
  Check for Dependencies: Ensure that all dependent objects are also present and correctly configured in the system.
  System Consistency Check: Run consistency checks in the system to identify and resolve any inconsistencies that may be causing the error.
  
  Related Information:
  
  Transaction Codes: Use transaction codes like SE11 (Data Dictionary), SE80 (Object Navigator), and SE09/SE10 (Transport Organizer) to investigate and manage the objects and transport requests.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  System Logs: Review system logs (SM21) and short dumps (ST22) for any additional error messages or context that may help in diagnosing the issue.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.