How To Fix T7035 - No successor exists

T7035 - Overview

• Message type: E = Error

• Message class: T7 - Forex entry

• Message number: 035

• Message text: No successor exists

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 T7035 - No successor exists ?

  The SAP error message T7035 "No successor exists" typically occurs in the context of project management or when dealing with task dependencies in SAP. This error indicates that the system is unable to find a successor task for a given predecessor task in a project network or scheduling scenario.
  
  Cause:
  
  Missing Successor Task: The most common cause is that the task you are trying to link does not have a defined successor. This can happen if the task is not properly set up in the project structure.
  Incorrect Task Relationships: The relationships between tasks may not be correctly defined, leading to the system being unable to identify a successor.
  Project Structure Issues: There may be issues with the overall project structure, such as missing or incorrectly configured project elements.
  Data Inconsistencies: There could be inconsistencies in the data that prevent the system from recognizing the successor.
  
  
  Solution:
  
  Check Task Configuration: Verify that the task you are working