How To Fix /SCMTMS/TEND345 - XML Tag '&1' is not supported; Message is rejected

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TEND -

• Message number: 345

• Message text: XML Tag '&1' is not supported; Message is rejected

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 /SCMTMS/TEND345 - XML Tag '&1' is not supported; Message is rejected ?

  The SAP error message /SCMTMS/TEND345 XML Tag '&1' is not supported; Message is rejected typically occurs in the context of SAP Transportation Management (TM) when there is an issue with the XML data being processed. This error indicates that the XML message being sent or received contains a tag that is not recognized or supported by the system.
  Cause:
  
  Unsupported XML Tag: The XML message includes a tag that is not defined in the expected schema for the transaction or process being executed.
  Version Mismatch: The XML structure may be based on a different version of the schema than what the SAP system is configured to accept.
  Configuration Issues: There may be configuration settings in SAP TM that do not align with the XML message being processed.
  Data Mapping Errors: If there are custom mappings or extensions in place, they may not be correctly defined or implemented.
  
  Solution:
  
  Check XML Structure: Review the XML message being sent to ensure that all tags are valid and supported by the SAP TM system. Compare it against the expected XML schema.
  Update Configuration: If the XML message is valid but still causing issues, check the configuration settings in SAP TM to ensure they are set up to accept the tags being used.
  Version Compatibility: Ensure that the version of the XML schema being used matches the version expected by the SAP system. If there are updates or patches available for SAP TM, consider applying them.
  Debugging: Use transaction codes like SLG1 (Application Log) to check for more detailed error logs that can provide additional context on the issue.
  Consult Documentation: Refer to SAP documentation or the relevant API documentation for the correct XML structure and supported tags.
  Contact SAP Support: If the issue persists and you cannot identify the unsupported tag, consider reaching out to SAP support for assistance.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address known issues or provide updates related to XML processing in SAP TM.
  Integration Scenarios: If this error occurs during integration with other systems (e.g., EDI, third-party logistics), ensure that the integration mappings are correctly defined.
  Testing: If possible, test with a simplified XML message to isolate the problematic tag and identify which part of the message is causing the rejection.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.