Do you have any question about this error?
Message type: E = Error
Message class: FDT_CORE - Formula & Derivation Tool: Core
Message number: 346
Message text: Object(s) in XML file is inconsistent
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.
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.
FDT_CORE346
- Object(s) in XML file is inconsistent ?The SAP error message FDT_CORE346 indicates that there is an inconsistency in the XML file related to the Field Data Tool (FDT) framework. This error typically arises when the structure or content of the XML file does not conform to the expected schema or contains invalid data.
Causes:
- Schema Mismatch: The XML file may not adhere to the expected schema defined for the FDT objects.
- Missing Elements: Required elements or attributes may be missing from the XML file.
- Invalid Data Types: The data types of certain fields may not match the expected types defined in the schema.
- Duplicate Entries: There may be duplicate entries or conflicting definitions within the XML file.
- Corrupted XML: The XML file may be corrupted or improperly formatted, leading to parsing errors.
Solutions:
- Validate XML Structure: Use an XML validator to check the structure of the XML file against the expected schema. This can help identify any structural issues.
- Check Required Fields: Ensure that all required fields and elements are present in the XML file.
- Correct Data Types: Verify that the data types of the fields in the XML file match the expected types. For example, if a field expects an integer, ensure that it does not contain a string.
- Remove Duplicates: Check for and remove any duplicate entries or conflicting definitions in the XML file.
- Recreate XML File: If the XML file is corrupted, consider recreating it from scratch or exporting it again from the source system.
- Consult Documentation: Refer to the SAP documentation for the FDT framework to understand the expected structure and requirements for the XML file.
Related Information:
If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance, providing them with the XML file and any relevant logs or error messages.
Get instant SAP help. Start your 7-day free trial now.
FDT_CORE345
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...
FDT_CORE344
Object(s) in XML file is consistent
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FDT_CORE347
Application &1 is not changeable in this system
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FDT_CORE348
Enqueue failed on object with ID &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.