How To Fix /SCMTMS/TSPS063 - Cannot read carrier &1; carrier is not considered for &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TSPS -

• Message number: 063

• Message text: Cannot read carrier &1; carrier is not considered for &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/TSPS063 - Cannot read carrier &1; carrier is not considered for &2 ?

  The SAP error message /SCMTMS/TSPS063 indicates that the system is unable to read the specified carrier (denoted as &1 in the message) and therefore, the carrier is not considered for the specified operation (denoted as &2). This error typically occurs in the context of SAP Transportation Management (TM) when the system is trying to process transportation planning or execution tasks.
  Causes:
  
  Carrier Not Defined: The carrier may not be defined in the system or may not be active.
  Carrier Status: The carrier might be inactive or blocked, preventing it from being used in transportation planning.
  Master Data Issues: There could be issues with the master data related to the carrier, such as missing or incorrect information.
  Authorization Issues: The user may not have the necessary authorizations to access the carrier data.
  Configuration Issues: There may be configuration issues in the Transportation Management settings that prevent the carrier from being recognized.
  
  Solutions:
  
  
  Check Carrier Definition:
  
  Go to the carrier master data in SAP and verify that the carrier is defined correctly.
  Ensure that the carrier is active and not blocked.
  
  
  
  Review Carrier Status:
  
  Check the status of the carrier in the system. If it is inactive, you may need to activate it.
  
  
  
  Validate Master Data:
  
  Ensure that all required fields in the carrier master data are filled out correctly.
  Check for any missing or incorrect entries that could lead to the carrier being unreadable.
  
  
  
  Authorization Check:
  
  Verify that the user has the necessary authorizations to access and use the carrier data.
  If needed, consult with your SAP security team to adjust user roles and permissions.
  
  
  
  Configuration Review:
  
  Review the configuration settings in SAP TM to ensure that the carrier is properly integrated into the transportation planning process.
  Check for any settings that might restrict the use of certain carriers.
  
  
  
  Logs and Traces:
  
  Check the application logs and traces for more detailed error messages that could provide additional context on why the carrier cannot be read.
  
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like /SCMTMS/TS for transportation planning or /SCMTMS/TC for carrier management to access relevant data.
  SAP Notes: Look for SAP Notes related to this error message for any known issues or patches that may resolve the problem.
  Documentation: Refer to the SAP Help Portal for documentation on Transportation Management and carrier management processes.
  
  If the issue persists after checking the above points, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.