How To Fix /SCWM/LM_LDP058 - No fitting historical records found to execute forecasting

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/LM_LDP -

• Message number: 058

• Message text: No fitting historical records found to execute forecasting

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 /SCWM/LM_LDP058 - No fitting historical records found to execute forecasting ?

  The SAP error message /SCWM/LM_LDP058 No fitting historical records found to execute forecasting typically occurs in the context of SAP Extended Warehouse Management (EWM) when the system is unable to find sufficient historical data to generate a forecast for a particular product or location. This can happen for several reasons, and understanding the cause is crucial for resolving the issue.
  Causes:
  
  
  Insufficient Historical Data: There may not be enough historical sales or inventory data for the product in question. This could be due to a new product that has not yet had any sales or a lack of data for the specified time period.
  
  
  Data Configuration Issues: The configuration settings for the forecasting process may not be set up correctly, leading to the system not being able to access the necessary historical data.
  
  
  Data Deletion: Historical data may have been deleted or archived, making it unavailable for forecasting.
  
  
  Incorrect Selection Criteria: The selection criteria used for the forecasting process may be too restrictive, resulting in no matching records.
  
  
  Master Data Issues: Problems with the master data (e.g., product master, location master) can also lead to this error if the data is incomplete or incorrect.
  
  
  Solutions:
  
  
  Check Historical Data: Verify that there is sufficient historical data for the product. You can do this by checking sales history, inventory levels, and any other relevant data.
  
  
  Review Configuration Settings: Ensure that the forecasting configuration is set up correctly. This includes checking the forecasting model, parameters, and any relevant settings in the SAP system.
  
  
  Data Recovery: If historical data has been deleted, check if it can be restored from backups or if it can be re-entered.
  
  
  Adjust Selection Criteria: Review and possibly broaden the selection criteria used for the forecasting process to ensure that it captures all relevant historical records.
  
  
  Validate Master Data: Check the master data for the product and location to ensure it is complete and accurate. Correct any discrepancies found.
  
  
  Run Data Consistency Checks: Use SAP tools to run consistency checks on the data to identify any issues that may be causing the error.
  
  
  Related Information:
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions to common problems.
  
  
  Documentation: Review the SAP EWM documentation for guidance on forecasting processes and requirements.
  
  
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  
  Consult SAP Support: If the issue persists after trying the above solutions, consider reaching out to SAP support 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.