How To Fix /SCMTMS/TC_SCALE070 - Price unit not expected

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TC_SCALE -

• Message number: 070

• Message text: Price unit not expected

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/TC_SCALE070 - Price unit not expected ?

  The SAP error message /SCMTMS/TC_SCALE070 Price unit not expected typically occurs in the context of SAP Transportation Management (TM) when there is a mismatch or inconsistency in the pricing conditions related to the transportation charges. This error indicates that the system is expecting a certain price unit for a specific condition, but the provided data does not meet that expectation.
  Causes:
  
  Incorrect Configuration: The pricing procedure or condition types may not be configured correctly in the system.
  Data Inconsistency: There may be inconsistencies in the master data, such as the material master, vendor master, or customer master, which can lead to incorrect pricing information.
  Missing or Incorrect Condition Records: The condition records for pricing may be missing or incorrectly maintained, leading to the system not finding the expected price unit.
  Unit of Measure Issues: There may be discrepancies in the units of measure used in the pricing conditions and the units of measure in the transaction data.
  
  Solutions:
  
  Check Pricing Procedure: Review the pricing procedure assigned to the relevant transaction and ensure that it is correctly configured to handle the expected price units.
  Review Condition Records: Verify that the condition records for the relevant pricing conditions are correctly maintained. You can do this using transaction codes like VK11 (Create Condition) or VK12 (Change Condition).
  Validate Master Data: Ensure that the master data (material, vendor, customer) is correctly maintained and that the relevant units of measure are consistent.
  Adjust Unit of Measure: If there are discrepancies in the units of measure, ensure that the units used in the pricing conditions match those used in the transaction data.
  Consult Documentation: Refer to SAP documentation or help resources for specific details on the pricing conditions and how they should be configured.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO (Customizing), VK11, VK12, and VT01N (Create Transportation Order).
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance on this error message.
  Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary corrections to resolve it.