How To Fix /SCMTMS/FAG_MSG329 - Cannot find matching rates

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/FAG_MSG -

• Message number: 329

• Message text: Cannot find matching rates

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_MSG329 - Cannot find matching rates ?

  The SAP error message /SCMTMS/FAG_MSG329 Cannot find matching rates typically occurs in the context of SAP Transportation Management (TM) when the system is unable to find a suitable rate for a transportation scenario. This can happen during the planning or execution of transportation processes, such as freight order creation or shipment processing.
  Causes:
  
  Missing Rate Records: There may be no rate records defined for the specific transportation lane, which includes the origin, destination, and transportation mode.
  Incorrect Rate Configuration: The rate configuration might be incorrect or incomplete, leading to the system's inability to match the transportation requirements with the available rates.
  Invalid Parameters: The parameters used in the rate determination process (like weight, volume, or service type) may not match any existing rate records.
  Inactive Rate Agreements: The rate agreements may be inactive or not valid for the specified time period.
  Transportation Lane Issues: The transportation lane may not be properly defined or may not exist in the system.
  Master Data Issues: Problems with master data, such as incorrect or missing data for the business partners, locations, or transportation modes.
  
  Solutions:
  
  Check Rate Records: Verify that the necessary rate records exist for the transportation lane in question. You can do this by navigating to the rate management area in SAP TM.
  Review Rate Configuration: Ensure that the rate configuration is complete and correctly set up. This includes checking the conditions and parameters that define the rates.
  Validate Parameters: Check the parameters being used for rate determination to ensure they align with the available rate records.
  Activate Rate Agreements: If the rate agreements are inactive, activate them or create new ones as needed.
  Examine Transportation Lanes: Ensure that the transportation lanes are correctly defined and that they match the origin and destination of the transportation request.
  Check Master Data: Review the master data for business partners, locations, and transportation modes to ensure they are correctly set up and active.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like /SCMTMS/RA for rate management or /SCMTMS/TL for transportation lanes to check configurations.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Refer to the SAP Help Portal for detailed documentation on rate determination and configuration in SAP TM.
  Debugging: If the issue persists, consider debugging the rate determination process to identify where the failure occurs.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.