Do you have any question about this error?
Message type: E = Error
Message class: FDT_EXPRESSIONS - Formula & Derivation Tool: Expressions
Message number: 346
Message text: Start 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_EXPRESSIONS346
- Start node &1 from connector &2 does not exist ?The SAP error message FDT_EXPRESSIONS346 indicates that there is an issue with a start node in a connector within the context of SAP's Flexible Data Import (FDI) or similar data processing scenarios. Specifically, the error states that the start node referenced in the connector does not exist, which can occur for several reasons.
Causes:
- Missing Node Definition: The start node that is being referenced in the connector may not have been defined or created in the data flow or expression.
- Incorrect Configuration: There may be a misconfiguration in the connector settings, leading to a reference to a non-existent node.
- Changes in Data Model: If the data model has been modified (e.g., nodes added, removed, or renamed), the connector may still reference the old node names.
- Transport Issues: If the configuration was transported from one system to another, there may be inconsistencies in the node definitions between the systems.
Solutions:
- Check Node Definitions: Verify that the start node referenced in the error message exists in the data flow or expression. If it does not exist, you may need to create it.
- Review Connector Configuration: Go through the connector settings to ensure that all references are correct and that the start node is properly linked.
- Update Data Model: If there have been changes to the data model, update the connector to reflect these changes. Ensure that all nodes are correctly defined and referenced.
- Transport Consistency: If the issue arose after a transport, check the source and target systems for consistency in the configuration. Ensure that all necessary objects were transported correctly.
- Debugging: Use debugging tools available in SAP to trace the execution and identify where the reference to the non-existent node is being made.
Related Information:
If the problem persists after trying the above solutions, consider reaching out to SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
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_EXPRESSIONS344
Connector &1 does not have an end point
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FDT_EXPRESSIONS347
End 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_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...
Click on this link to search all SAP messages.