How To Fix /SCMTMS/MC_CON_CACHE085 - Connection type &1: &2 unique keys

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/MC_CON_CACHE -

• Message number: 085

• Message text: Connection type &1: &2 unique keys

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/MC_CON_CACHE085 - Connection type &1: &2 unique keys ?

  The SAP error message /SCMTMS/MC_CON_CACHE085 typically indicates an issue related to the configuration of connection types in the SAP Transportation Management System (TM). The message states that there are unique key constraints being violated for a specific connection type.
  Cause:
  The error is usually caused by one of the following:
  
  Duplicate Entries: There are duplicate entries in the configuration for the specified connection type. This can happen if the same unique key is being used for multiple entries.
  Incorrect Configuration: The configuration for the connection type may not be set up correctly, leading to conflicts in unique keys.
  Data Consistency Issues: There may be inconsistencies in the data stored in the database, possibly due to manual changes or data migration issues.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Configuration:
  
  Go to the configuration settings for the connection type in SAP TM.
  Verify that there are no duplicate entries for the unique keys associated with the connection type.
  
  
  
  Identify Duplicates:
  
  Use transaction codes like SE16 or SE11 to check the relevant database tables for duplicate entries.
  Look for tables related to connection types, such as /SCMTMS/CONN_TYPE or similar.
  
  
  
  Correct Data:
  
  If duplicates are found, you will need to delete or modify the duplicate entries to ensure that each unique key is only used once.
  Ensure that the data is consistent and adheres to the defined constraints.
  
  
  
  Transport Requests:
  
  If the issue arose after a transport request, check if the transport included any changes to the connection type configuration that might have caused the duplicates.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific version of SAP TM you are using for any known issues or additional guidance.
  
  
  
  Testing:
  
  After making the necessary corrections, test the connection type to ensure that the error no longer occurs.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any specific notes related to this error message. SAP frequently updates their knowledge base with solutions for common issues.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SCMTMS/CONN_TYPE for managing connection types.
  Support: If the issue persists after following the above steps, consider reaching out to SAP support for further assistance.
  
  By following these steps, you should be able to identify and resolve the issue causing the /SCMTMS/MC_CON_CACHE085 error message in SAP TM.