How To Fix FDT_SERVICE143 - Processing started for objects marked for deletion

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 143

• Message text: Processing started for objects marked for deletion

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_SERVICE143 - Processing started for objects marked for deletion ?

  The SAP error message FDT_SERVICE143 indicates that there are objects in the system that have been marked for deletion, and the processing of these objects has started. This message is typically related to the SAP Fiori Design Time (FDT) service, which is used for managing UI elements and other related objects in SAP Fiori applications.
  Cause:
  The error message is triggered when:
  
  Objects (like UI elements, configurations, or other related entities) have been flagged for deletion in the system.
  The system is attempting to process these objects, but since they are marked for deletion, it cannot proceed as expected.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check for Marked Objects:
  
  Use transaction codes like SE80 (Object Navigator) or SE11 (Data Dictionary) to check for objects that are marked for deletion.
  You can also use transaction SE37 to check function modules or SE24 for classes that might be involved.
  
  
  
  Review Deletion Flags:
  
  Identify the specific objects that are marked for deletion. You can do this by checking the relevant tables or using the appropriate transaction codes.
  If the deletion was unintentional, you may need to remove the deletion flag from these objects.
  
  
  
  Restore or Delete Objects:
  
  If the objects are still needed, restore them by removing the deletion flag.
  If they are no longer required, ensure that they are properly deleted from the system.
  
  
  
  Check Dependencies:
  
  Ensure that there are no dependencies on the objects marked for deletion. If other objects depend on them, it may cause issues in processing.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to FDT and the specific objects you are working with. There may be specific guidelines or known issues that can provide further insight.
  
  
  
  System Logs:
  
  Check system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  
  
  
  Contact SAP Support:
  
  If the issue persists and you cannot identify the cause, consider reaching out to SAP support for assistance. Provide them with the error message and any relevant details about the objects involved.
  
  
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  Fiori Documentation: Review the SAP Fiori documentation for best practices on managing UI elements and configurations.
  Community Forums: Engage with the SAP Community or forums where other users may have encountered similar issues and can share their solutions.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.