Do you have any question about this error?
Message type: E = Error
Message class: FDT_EXPRESSIONS - Formula & Derivation Tool: Expressions
Message number: 347
Message text: End node &1 from connector &2 does not exist
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_EXPRESSIONS347
- End node &1 from connector &2 does not exist ?The SAP error message FDT_EXPRESSIONS347 indicates that there is an issue with a data flow or expression in the context of SAP's Flexible Data Import (FDI) or Flexible Data Transfer (FDT) framework. Specifically, the error states that an "end node" referenced in a connector does not exist. This typically occurs when there is a misconfiguration in the data flow or when the expected nodes in the data structure are not properly defined.
Cause:
- Missing End Node: The end node that the connector is trying to reference does not exist in the data flow definition. This could be due to a deletion or a misconfiguration.
- Incorrect Connector Configuration: The connector may be incorrectly set up, pointing to a non-existent or incorrectly named end node.
- Data Model Changes: If there have been recent changes to the data model or structure, the end node may have been renamed or removed.
- Version Mismatch: If there are multiple versions of the data flow or connector, there may be inconsistencies between them.
Solution:
- Check Data Flow Definition: Review the data flow definition to ensure that the end node referenced in the error message exists. If it does not, you may need to create it or correct the reference.
- Validate Connector Configuration: Go through the configuration of the connector to ensure that it is correctly pointing to the existing end node. Update the configuration if necessary.
- Review Recent Changes: If there have been recent changes to the data model or flow, check to see if any nodes were renamed or removed. Revert or adjust as needed.
- Test the Data Flow: After making corrections, test the data flow to ensure that it runs without errors.
- Consult Documentation: Refer to SAP documentation or help resources for guidance on configuring data flows and connectors properly.
Related Information:
If the issue persists after following these steps, consider reaching out to SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
FDT_EXPRESSIONS346
Start node &1 from connector &2 does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FDT_EXPRESSIONS345
End node ID &1 of connector &2 is not a valid UUID
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FDT_EXPRESSIONS348
End node &1 is not connected
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FDT_EXPRESSIONS349
Connector &1 starts at end node &2
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.