How To Fix /SCWM/MFS357 - Telegram &1 was sent. Retry: &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/MFS -

• Message number: 357

• Message text: Telegram &1 was sent. Retry: &2

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 /SCWM/MFS357 - Telegram &1 was sent. Retry: &2 ?

  The SAP error message /SCWM/MFS357 Telegram &1 was sent. Retry: &2 is related to the integration between SAP Extended Warehouse Management (EWM) and the Material Flow System (MFS). This error typically indicates that a telegram (a message or command sent to the MFS) was sent, but there was an issue that requires a retry.
  Cause:
  
  Communication Issues: There may be a communication problem between SAP EWM and the MFS, such as network issues or configuration problems.
  MFS Configuration: The MFS may not be properly configured to handle the telegram being sent.
  System Load: High system load or performance issues may cause delays in processing the telegram.
  Telegram Format: The telegram format may not be recognized or may contain errors.
  MFS Status: The MFS might be in a state that does not allow it to process the telegram (e.g., it might be down or in maintenance mode).
  
  Solution:
  
  Check Communication: Verify the network connection between SAP EWM and the MFS. Ensure that both systems can communicate without issues.
  Review MFS Configuration: Check the configuration settings in the MFS to ensure that it is set up correctly to receive and process telegrams from EWM.
  Monitor System Performance: Look at the performance metrics of both SAP EWM and MFS. If there are performance bottlenecks, consider optimizing the system or increasing resources.
  Examine Telegram Content: Review the content of the telegram being sent. Ensure that it adheres to the expected format and contains valid data.
  Check MFS Status: Ensure that the MFS is operational and not in a maintenance state. If it is down, restart the MFS or resolve any issues preventing it from running.
  Retry Mechanism: If the error indicates a retry, ensure that the retry mechanism is functioning correctly. You may need to manually trigger a retry if automatic retries are not working.
  
  Related Information:
  
  Transaction Codes: Use transaction codes like /SCWM/MFS to access MFS-related settings and logs.
  Logs and Traces: Check the application logs and traces in both EWM and MFS for more detailed error messages that can provide insights into the issue.
  SAP Notes: Look for relevant SAP Notes that may address known issues or provide patches related to this error message.
  Documentation: Refer to the official SAP documentation for EWM and MFS for detailed configuration and troubleshooting steps.
  
  If the issue persists after following these steps, consider reaching out to SAP support for further assistance.