How To Fix /UI2/FDM407 - Successor &1&2: Not Found

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/FDM -

• Message number: 407

• Message text: Successor &1&2: Not 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 /UI2/FDM407 - Successor &1&2: Not Found ?

  The SAP error message /UI2/FDM407 Successor &1&2: Not Found typically occurs in the context of SAP Fiori applications and indicates that a successor (or dependent) object that is expected to be found in the system is missing or not available. This can happen in various scenarios, such as when navigating between applications or when trying to access a specific functionality that relies on a predecessor-successor relationship.
  Causes:
  
  Missing or Inactive Object: The successor object (like a Fiori app, tile, or service) may not be activated or could be missing from the system.
  Authorization Issues: The user may not have the necessary authorizations to access the successor object.
  Configuration Issues: There may be a misconfiguration in the Fiori Launchpad or the underlying OData services.
  Transport Issues: If the application was recently transported from one system to another, the successor object may not have been included in the transport.
  System Errors: There could be underlying system errors or inconsistencies in the database.
  
  Solutions:
  
  Check Object Activation: Ensure that the successor object is activated in the system. This can be done through the SAP Fiori Launchpad or the relevant transaction codes.
  Verify Authorizations: Check the user’s roles and authorizations to ensure they have access to the required objects.
  Review Configuration: Look into the Fiori Launchpad configuration and ensure that all necessary tiles and target mappings are correctly set up.
  Transport Validation: If the issue arose after a transport, verify that all necessary components were included and activated in the target system.
  Check OData Services: Ensure that the OData services related to the application are properly registered and active in the system.
  System Logs: Review system logs (transaction SLG1) for any additional error messages or warnings that could provide more context about the issue.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for the error message or related keywords in the SAP Support Portal.
  Fiori Launchpad Configuration: Familiarize yourself with the Fiori Launchpad configuration and troubleshooting guides available in the SAP Help Portal.
  Community Forums: Engage with the SAP Community or forums where similar issues may have been discussed, and solutions shared by other users.
  
  If the issue persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.