How To Fix FDT_EXPRESSIONS358 - Conn &1 at gateway &2 branch order &3 has a different starting point &4

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_EXPRESSIONS - Formula & Derivation Tool: Expressions

• Message number: 358

• Message text: Conn &1 at gateway &2 branch order &3 has a different starting point &4

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_EXPRESSIONS358 - Conn &1 at gateway &2 branch order &3 has a different starting point &4 ?

  The SAP error message FDT_EXPRESSIONS358 typically indicates an issue related to the configuration of a branch order in the system. This error occurs when there is a mismatch in the starting points of the connection (Conn) at the gateway for a specific branch order.
  Cause:
  The error message suggests that the connection (Conn) at the specified gateway (gateway &2) for the branch order (branch order &3) has a different starting point than expected. This can happen due to several reasons, including:
  
  Configuration Issues: The branch order may not be properly configured, leading to discrepancies in the starting points.
  Data Inconsistencies: There may be inconsistencies in the data related to the branch order or the connections defined in the system.
  Changes in the System: Recent changes or updates in the system might have altered the expected starting points for the connections.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Configuration: Review the configuration settings for the branch order and ensure that the starting points for the connections are correctly defined. Make sure that the branch order is set up according to the business requirements.
  
  
  Validate Data: Check the data associated with the branch order and the connections. Look for any inconsistencies or errors in the data that might be causing the mismatch.
  
  
  Review Recent Changes: If there have been any recent changes to the system, review those changes to see if they might have affected the branch order or the connections.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to this error message for any specific guidance or recommendations.
  
  
  Contact SAP Support: If the issue persists after checking the configuration and data, consider reaching out to SAP support for further assistance. They may provide insights or patches that can help resolve the issue.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error message or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with transaction codes related to branch orders and connections, such as FDT1 (for branch order management) or FDT2 (for connection management).
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.