How To Fix /SCMTMS/TEND335 - More than one business doc. with base BTD ID &1 and type code &2 exists

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TEND -

• Message number: 335

• Message text: More than one business doc. with base BTD ID &1 and type code &2 exists

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/TEND335 - More than one business doc. with base BTD ID &1 and type code &2 exists ?

  The SAP error message /SCMTMS/TEND335 indicates that there are multiple business documents associated with the same base Business Transaction Document (BTD) ID and type code. This situation typically arises in the context of SAP Transportation Management (TM) when the system expects a unique business document but finds duplicates.
  Cause:
  
  
  Duplicate Entries: The primary cause of this error is the existence of multiple entries in the database for the same BTD ID and type code. This can happen due to:
  
  Incorrect data entry or system configuration.
  Data migration issues where duplicates were introduced.
  Inconsistent data updates or processing errors.
  
  
  
  Configuration Issues: There may be issues in the configuration of the business processes that lead to the creation of multiple documents for the same transaction.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Identify Duplicates:
  
  Use transaction codes like SE16 or SE11 to query the relevant database tables (e.g., /SCMTMS/TEND or similar) to find the duplicate entries for the specified BTD ID and type code.
  Check the logs or transaction history to understand how these duplicates were created.
  
  
  
  Data Cleanup:
  
  Once you identify the duplicates, you may need to delete or archive the unnecessary entries. Ensure that you have proper backups and that you follow your organization's data management policies.
  If the duplicates are due to a data migration issue, consider re-running the migration process with checks to prevent duplicates.
  
  
  
  Review Configuration:
  
  Review the configuration settings in SAP TM to ensure that the processes are set up correctly to prevent the creation of duplicate documents.
  Consult with your SAP functional team to ensure that the business processes are aligned with the system's capabilities.
  
  
  
  Testing:
  
  After making changes, conduct thorough testing to ensure that the issue is resolved and that no new duplicates are being created.
  
  
  
  Consult Documentation:
  
  Refer to SAP Notes or the SAP Help Portal for any specific notes related to this error message. There may be patches or updates that address known issues.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might provide additional insights or solutions for this specific error.
  Transaction Codes: Familiarize yourself with transaction codes related to Transportation Management, such as /SCMTMS/PRC for processing and monitoring.
  Support: If the issue persists, consider reaching out to SAP Support for assistance, providing them with detailed information about the error and the steps you have taken.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.