How To Fix FDT_SERVICE405 - Deleted object is still used in undeleted object: &1, &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_SERVICE - Formula & Derivation Tool: Services

• Message number: 405

• Message text: Deleted object is still used in undeleted object: &1, &2

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 FDT_SERVICE405 - Deleted object is still used in undeleted object: &1, &2 ?

  The SAP error message FDT_SERVICE405 indicates that there is a deleted object that is still being referenced by another object that has not been deleted. This typically occurs in the context of the SAP Fiori Design Time (FDT) or when working with UI5 applications, where objects such as fields, data elements, or other components may have dependencies on one another.
  Cause:
  
  Deleted Object Reference: The primary cause of this error is that an object (e.g., a field or a UI component) has been deleted, but another object still references it. This can happen if the deletion was not properly propagated or if the dependent object was not updated to remove the reference.
  Inconsistent State: The system is in an inconsistent state where the metadata or configuration does not align with the actual objects present in the system.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Identify the Objects: The error message will provide you with identifiers for the objects involved (e.g., &1, &2). Use these identifiers to locate the objects in the SAP system.
  
  
  Check Dependencies: Review the dependencies of the object that is still in use. You can do this by checking the configuration or metadata of the object to see what references it has.
  
  
  Update References: If you find that the deleted object is still referenced, you will need to update the dependent object to remove the reference to the deleted object. This may involve:
  
  Modifying the configuration of the dependent object.
  Re-creating the deleted object if it is still needed.
  Adjusting any related settings or properties.
  
  
  
  Re-activate Objects: After making the necessary changes, you may need to re-activate the objects involved to ensure that the changes take effect.
  
  
  Check for Transport Issues: If this issue arises after a transport, ensure that all objects were transported correctly and that there are no inconsistencies between the development and production environments.
  
  
  Consult Documentation: If the issue persists, refer to SAP documentation or community forums for additional guidance specific to the objects you are working with.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Transaction Codes: Use transaction codes like SE80 (Object Navigator) or SE11 (Data Dictionary) to inspect the objects and their relationships.
  Debugging: If necessary, you can enable debugging to trace the execution and see where the error is being triggered.
  
  By following these steps, you should be able to resolve the FDT_SERVICE405 error and restore consistency in your SAP environment.