How To Fix /SCMTMS/FAG_MSG729 - Charge usage for agreement and calculation sheet don't match

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/FAG_MSG -

• Message number: 729

• Message text: Charge usage for agreement and calculation sheet don't match

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/FAG_MSG729 - Charge usage for agreement and calculation sheet don't match ?

  The SAP error message /SCMTMS/FAG_MSG729 indicates a mismatch between the charge usage defined in a transport agreement and the charge usage calculated in the calculation sheet. This error typically arises in the context of SAP Transportation Management (TM) when there is a discrepancy in the expected and actual charge calculations for transportation services.
  Cause:
  
  Data Mismatch: The charge usage defined in the transport agreement does not align with the charge usage calculated in the calculation sheet. This could be due to incorrect data entry or configuration.
  Changes in Conditions: If there have been changes in the conditions or parameters used for calculating charges after the agreement was created, this can lead to discrepancies.
  Incorrect Configuration: The configuration settings for charge calculation might not be set up correctly, leading to different interpretations of the charge usage.
  Versioning Issues: If there are multiple versions of agreements or calculation sheets, it’s possible that the wrong version is being referenced.
  
  Solution:
  
  Review Agreement and Calculation Sheet: Check the transport agreement and the calculation sheet to ensure that the charge usage is consistent across both. Look for any discrepancies in the charge types, rates, or conditions.
  Update Charge Usage: If the charge usage in the calculation sheet is incorrect, update it to match the agreement. Conversely, if the agreement is outdated, consider updating it to reflect the current charge usage.
  Check Configuration: Review the configuration settings for charge calculation in SAP TM. Ensure that all relevant parameters are correctly set up and that there are no conflicting settings.
  Recalculate Charges: After making any necessary adjustments, recalculate the charges in the calculation sheet to ensure they align with the transport agreement.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on charge calculation and agreements in SAP TM.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP TM, such as /SCMTMS/AGREEMENT for managing transport agreements and /SCMTMS/CALC for charge calculations.
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide additional insights or patches that address known issues.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, providing insights or solutions from other users’ experiences.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve the mismatch in charge usage.