How To Fix /SCMTMS/TOR_INT012 - Business document with base BTD ID &1 and type code &2 does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TOR_INT -

• Message number: 012

• Message text: Business document with base BTD ID &1 and type code &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 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/TOR_INT012 - Business document with base BTD ID &1 and type code &2 does not exist ?

  The SAP error message /SCMTMS/TOR_INT012 indicates that a business document with a specific Base Transport Document (BTD) ID and type code does not exist in the system. This error typically occurs in the context of SAP Transportation Management (TM) when there is an attempt to reference a document that cannot be found.
  Cause:
  
  Missing Document: The specified business document (e.g., a transportation order, shipment, etc.) may not have been created or may have been deleted.
  Incorrect BTD ID or Type Code: The BTD ID or type code provided in the request may be incorrect or misspelled.
  Data Synchronization Issues: There may be issues with data synchronization between different systems (e.g., between SAP TM and SAP ERP).
  Authorization Issues: The user may not have the necessary authorizations to access the document.
  System Configuration: There may be configuration issues in the SAP TM system that prevent the document from being recognized.
  
  Solution:
  
  Verify Document Existence: Check if the business document with the specified BTD ID and type code exists in the system. You can do this by using transaction codes relevant to the document type (e.g., /SCMTMS/TO for transportation orders).
  Check Input Parameters: Ensure that the BTD ID and type code being used in the transaction or program are correct. Double-check for any typos or formatting issues.
  Review System Logs: Look at the application logs (transaction SLG1) for any additional error messages or warnings that might provide more context about the issue.
  Data Synchronization: If the system is integrated with other systems, ensure that data synchronization processes are functioning correctly. Check for any errors in the middleware or integration layer.
  Authorization Check: Ensure that the user has the necessary authorizations to access the document. You can check this using transaction SU53 after the error occurs.
  Consult Configuration: If the issue persists, consult with your SAP Basis or TM configuration team to review the system settings and ensure that everything is configured correctly.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes for managing transportation documents in SAP TM, such as /SCMTMS/TO, /SCMTMS/SH, etc.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Documentation: Review the SAP Help documentation for Transportation Management to understand the expected behavior and configuration settings related to business documents.
  
  If the issue continues after following these steps, it may be necessary to engage SAP support for further assistance.