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