How To Fix /SCMTMS/TCCS036 - Resolution base type &1 is incompatible with header resol. base type &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TCCS -

• Message number: 036

• Message text: Resolution base type &1 is incompatible with header resol. base type &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 /SCMTMS/TCCS036 - Resolution base type &1 is incompatible with header resol. base type &2 ?

  The SAP error message /SCMTMS/TCCS036 indicates that there is a mismatch between the resolution base type of a transport request and the header resolution base type. This typically occurs in the context of SAP Transportation Management (TM) when trying to process a transport request that has incompatible data types.
  Cause:
  
  
  Incompatible Data Types: The error arises when the resolution base type defined for a specific transport request does not match the expected header resolution base type. This can happen if:
  
  The transport request was created with a different configuration or settings.
  There are inconsistencies in the data model or configuration settings in the system.
  
  
  
  Configuration Issues: If the system configuration has been changed or if there are inconsistencies in the transport management setup, it can lead to this error.
  
  
  Custom Developments: If there are custom developments or enhancements that modify the behavior of transport requests, they may inadvertently cause this mismatch.
  
  
  Solution:
  
  
  Check Configuration: Review the configuration settings for the transport management system. Ensure that the resolution base types are correctly defined and consistent across the relevant objects.
  
  
  Review Transport Request: Examine the transport request that is causing the error. Check the resolution base type and ensure it aligns with the expected header resolution base type.
  
  
  Adjust Data Types: If you have access to the relevant configuration, you may need to adjust the data types to ensure compatibility. This may involve changing settings in the customizing or configuration tables.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the specific version of SAP TM you are using. There may be specific guidelines or patches available that address this issue.
  
  
  SAP Support: If the issue persists after checking the configuration and transport request, consider reaching out to SAP Support for assistance. Provide them with the error message details and any relevant context to help diagnose the issue.
  
  
  Related Information:
  
  SAP Notes: Check for any SAP Notes related to this error message. SAP frequently releases notes that address known issues and provide solutions or workarounds.
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP TM, such as /SCMTMS/ related transactions, to help navigate and troubleshoot the issue.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed. Other users may have encountered the same error and can provide insights or solutions.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.