How To Fix FDT_CORE345 - Object(s) with errors found; erroneous objects not imported

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 345

• Message text: Object(s) with errors found; erroneous objects not imported

What causes this issue?

During the XML import of a deployed service, the system has determined
that one or more of the objects to be imported contain errors. These
erroneous objects have been excluded from the import.
As opposed to that, objects that are free of errors have been imported
successfully.

System Response

Due to object errors, the import is incomplete.

How to fix this error?

Check the detailed error messages that the system has raised during the
import.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FDT_CORE345 - Object(s) with errors found; erroneous objects not imported ?

  The SAP error message FDT_CORE345 indicates that there are issues with certain objects during the import process, and as a result, those erroneous objects are not being imported. This error typically occurs in the context of SAP Fiori or SAP UI5 applications, particularly when dealing with the Fiori Development Tools (FDT) or when importing transport requests.
  Causes:
  
  Validation Errors: The objects being imported may not meet the required validation criteria. This could be due to missing dependencies, incorrect configurations, or incompatible versions.
  Transport Request Issues: The transport request may be incomplete or corrupted, leading to errors during the import process.
  Object Locking: The objects may be locked by another user or process, preventing the import from completing successfully.
  Missing Authorizations: The user performing the import may not have the necessary authorizations to import certain objects.
  Inconsistent Data: There may be inconsistencies in the data or configuration settings that are causing the import to fail.
  
  Solutions:
  
  Check Logs: Review the detailed logs for the import process to identify specific objects that are causing the error. This can provide insights into what needs to be fixed.
  Validate Objects: Ensure that all objects being imported are valid and meet the necessary criteria. This may involve checking for missing dependencies or correcting configurations.
  Transport Request Review: Verify the transport request for completeness and integrity. If necessary, recreate the transport request or re-export the objects.
  Unlock Objects: If objects are locked, coordinate with other users or administrators to unlock them before attempting the import again.
  Authorization Check: Ensure that the user has the appropriate authorizations to perform the import. If not, request the necessary permissions from an administrator.
  Test in Development: If possible, test the import in a development environment first to identify and resolve issues before moving to production.
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to FDT_CORE345 for any specific patches or updates that may address known issues.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  Documentation: Review the official SAP documentation for Fiori and FDT to ensure compliance with best practices during the import process.
  
  By following these steps, you should be able to identify the root cause of the FDT_CORE345 error and implement a solution to successfully import the objects.