How To Fix /SCMTMS/FAG_MSG358 - No rate data found

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/FAG_MSG -

• Message number: 358

• Message text: No rate data found

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_MSG358 - No rate data found ?

  The SAP error message /SCMTMS/FAG_MSG358 No rate data found typically occurs in the context of SAP Transportation Management (TM) when the system is unable to find any rate data for a specific transportation scenario. This can happen during the planning or execution of transportation processes, such as when trying to create a freight order or when calculating freight costs.
  Causes:
  
  Missing Rate Data: The most common cause is that there is no rate data defined for the specific transportation lane, which includes the origin, destination, and transportation mode.
  Incorrect Configuration: The configuration for the transportation management system may not be set up correctly, leading to the absence of relevant rate data.
  Inactive Rate Agreements: The rate agreements may be inactive or not valid for the selected transportation scenario.
  Data Inconsistencies: There may be inconsistencies in the master data, such as incorrect or missing information in the business partners, locations, or transportation lanes.
  Date Validity: The rate data may not be valid for the date of the transportation request.
  
  Solutions:
  
  Check Rate Data: Verify that the rate data is correctly defined in the system. This includes checking the transportation lanes, rate agreements, and ensuring that the rates are active and valid.
  
  Navigate to the relevant transaction in SAP TM to review the rate data.
  
  
  Create or Update Rate Agreements: If no rate data exists, you may need to create new rate agreements or update existing ones to include the necessary transportation lanes and conditions.
  Review Configuration: Ensure that the configuration settings for transportation management are correctly set up. This may involve checking the customizing settings in SPRO.
  Validate Master Data: Check the master data for any inconsistencies. Ensure that all relevant business partners, locations, and transportation lanes are correctly defined and active.
  Check Validity Dates: Ensure that the rate data is valid for the date of the transportation request. If the rates are time-sensitive, make sure they cover the required date range.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like /SCMTMS/RA (Rate Management) to manage and review rate agreements.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to rate data in SAP TM.
  Documentation: Refer to the SAP Help Portal for detailed documentation on configuring and managing rate data in SAP Transportation Management.
  Support: If the issue persists after checking the above points, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.