How To Fix /SCDL/TS058 - No successor documents to be deleted found

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCDL/TS -

• Message number: 058

• Message text: No successor documents to be deleted found

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 /SCDL/TS058 - No successor documents to be deleted found ?

  The SAP error message /SCDL/TS058 No successor documents to be deleted found typically occurs in the context of document management or workflow processes within SAP, particularly when dealing with the deletion of successor documents in a document lifecycle management scenario.
  Cause:
  This error message indicates that the system is unable to find any successor documents that are linked to the document you are trying to delete. This can happen for several reasons:
  
  No Successor Documents Exist: The document you are trying to delete may not have any successor documents associated with it.
  Incorrect Document Reference: The document reference you are using may be incorrect or may not exist in the system.
  Document Status: The document may be in a status that does not allow for deletion or may not have been properly processed in the workflow.
  Configuration Issues: There may be configuration issues in the document management system that prevent the identification of successor documents.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Document Links: Verify if there are any successor documents linked to the document you are trying to delete. You can do this by checking the document's properties or using transaction codes related to document management.
  
  
  Review Document Status: Ensure that the document is in a status that allows for deletion. If the document is locked or in a workflow state that prevents deletion, you may need to change its status first.
  
  
  Correct Document Reference: Double-check the document reference you are using to ensure it is correct and exists in the system.
  
  
  Consult Documentation: Review SAP documentation or help resources related to document management and workflows to understand the expected behavior and any prerequisites for deleting documents.
  
  
  Check Configuration: If you have access, review the configuration settings for document management in your SAP system to ensure that everything is set up correctly.
  
  
  Contact Support: If the issue persists, consider reaching out to your SAP support team or consulting with SAP support for further assistance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SCDL for document lifecycle management, SCDO for document object management, or other related codes that may help in managing documents.
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide specific fixes or patches that address known issues.
  User Permissions: Ensure that you have the necessary permissions to delete documents in the system, as lack of permissions can also lead to errors.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.