How To Fix /SCMTMS/OM090 - Recalculated charges donÆt match; check them and send the document again

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/OM -

• Message number: 090

• Message text: Recalculated charges donÆt match; check them and send the document again

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/OM090 - Recalculated charges donÆt match; check them and send the document again ?

  The SAP error message /SCMTMS/OM090 typically occurs in the context of SAP Transportation Management (TM) when there is a discrepancy between recalculated charges and the expected charges for a transportation document. This can happen during the process of charge calculation, where the system recalculates the charges based on the defined conditions, and the recalculated values do not match the original or expected values.
  Cause:
  
  Data Inconsistency: There may be inconsistencies in the data used for charge calculation, such as incorrect master data (e.g., condition records, pricing procedures).
  Changes in Conditions: If there have been changes to the conditions or pricing that affect the charge calculation after the initial calculation was performed.
  Configuration Issues: Incorrect configuration in the pricing procedure or condition types can lead to discrepancies.
  Manual Adjustments: Manual changes to charges or conditions that are not reflected in the recalculation logic.
  Missing or Incorrect Master Data: Missing or incorrect master data related to the transportation charges can lead to mismatches.
  
  Solution:
  
  Review Charge Conditions: Check the charge conditions and ensure that they are correctly defined in the system. Verify that the condition records are accurate and up to date.
  Recalculate Charges: Trigger a recalculation of the charges in the transportation document to see if the issue persists. This can often be done through the relevant transaction in SAP TM.
  Check Configuration: Review the configuration settings for the pricing procedure and condition types to ensure they are set up correctly.
  Analyze Logs: Check the logs for any additional error messages or warnings that may provide more context on the issue.
  Consult Documentation: Refer to SAP documentation or notes related to the specific error message for any known issues or additional troubleshooting steps.
  Test in a Sandbox: If possible, replicate the issue in a sandbox environment to test different scenarios and configurations without affecting production data.
  Contact SAP Support: If the issue cannot be resolved internally, consider reaching out to SAP support for assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP TM, such as /SCMTMS/OM for managing transportation charges.
  SAP Notes: Search for SAP Notes related to the error message for any patches or updates that may address the issue.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.