How To Fix FDT_CORE337 - Object &1 cannot be imported; problem in deleting object physically

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_CORE - Formula & Derivation Tool: Core

• Message number: 337

• Message text: Object &1 cannot be imported; problem in deleting object physically

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_CORE337 - Object &1 cannot be imported; problem in deleting object physically ?

  The SAP error message FDT_CORE337 indicates that there is an issue with importing an object due to a problem in physically deleting it. This error typically arises in the context of the SAP Fiori Design Time (FDT) or when dealing with the transport of objects in the SAP system.
  
  Cause:
  The error can occur due to several reasons, including:
  
  Object Locking: The object you are trying to import may be locked by another user or process, preventing its deletion.
  Transport Issues: There may be inconsistencies or issues with the transport request that contains the object.
  Database Constraints: There could be database constraints or dependencies that prevent the object from being deleted.
  Authorization Issues: The user may not have the necessary authorizations to delete the object.
  Corrupted Object: The object itself may be corrupted or in an inconsistent state.
  
  
  Solution:
  To resolve the FDT_CORE337 error, you can try the following steps:
  
  
  Check Object Lock:
  
  Use transaction code SM12 to check if the