How To Fix /SCMTMS/SCH138 - Cost unit is not defined

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/SCH -

• Message number: 138

• Message text: Cost unit is not defined

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/SCH138 - Cost unit is not defined ?

  The SAP error message /SCMTMS/SCH138 Cost unit is not defined typically occurs in the context of SAP Transportation Management (TM) when the system is unable to find a cost unit for a specific transportation planning or costing scenario. This can happen for various reasons, such as missing configuration or data in the system.
  Cause:
  
  Missing Cost Unit Definition: The cost unit (e.g., cost center, internal order, etc.) has not been defined in the system for the relevant transportation planning object.
  Incorrect Configuration: The configuration settings for cost units in the Transportation Management module may not be set up correctly.
  Master Data Issues: The relevant master data (like transportation lanes, freight agreements, etc.) may not have the necessary cost unit information.
  Transport Planning Object: The transport planning object (like a shipment or freight order) may not be linked to a valid cost unit.
  
  Solution:
  
  
  Define Cost Unit:
  
  Go to the relevant configuration settings in SAP TM and ensure that the cost unit is defined. This can typically be done in the customizing settings under the Transportation Management module.
  Check the transaction codes related to cost unit configuration, such as SPRO, and navigate to the relevant sections to define or adjust cost units.
  
  
  
  Check Master Data:
  
  Review the master data related to the transportation planning object. Ensure that all necessary fields, including cost units, are filled out correctly.
  If you are using freight agreements or transportation lanes, ensure that they are properly configured with the necessary cost unit information.
  
  
  
  Review Configuration:
  
  Ensure that the configuration for cost calculation in SAP TM is correctly set up. This includes checking the settings for cost elements and cost components.
  Validate that the relevant customizing settings for cost determination are in place.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test run to see if the error persists. Create a new transportation planning object and check if the cost unit is now being recognized.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific guidance on cost unit configuration in your version of SAP TM.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO for configuration, SE11 for data dictionary, and SE16 for table data checks.
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide additional insights or patches that address known issues.
  Community Forums: Engage with SAP community forums or support channels for additional help and shared experiences from other users who may have encountered the same issue.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.