How To Fix MD151 - No data saved. Please evauluate the scenario for the PURCHI first

SAP Error Message - Details

• Message type: E = Error

• Message class: MD - Material Requirements Planning (MRP)

• Message number: 151

• Message text: No data saved. Please evauluate the scenario for the PURCHI first

What causes this issue?

In the structure of the purchasing info system, no data exists from
long-term planning.

System Response

No evaluation can be carried out due to a lack of data.

How to fix this error?

You should first set up the data for the purchasing info system from
the planning scenario. Here, all planned orders with external
procurement are evaluated for the planning scenario and the info
structure of the purchasing info system is updated.
If you are dealing with a large amount of data, it is best to carry out
the corresponding report in background mode.
Alternatively, you can set the system so that it determines the data
for the selected selction criteria dynamically from the planning
scenario. This provides you with the advantage that you receive
up-to-date data. For large amounts of data, for example, the evaluation
of a complete plant, you must be prepared to accept longer run times.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MD151 - No data saved. Please evauluate the scenario for the PURCHI first ?

  The SAP error message MD151 ("No data saved. Please evaluate the scenario for the PURCHI first") typically occurs in the context of Material Requirements Planning (MRP) when there is an issue with the planning run or the data related to purchasing. Here’s a breakdown of the potential causes, solutions, and related information for this error:
  Causes:
  
  
  Missing or Incomplete Data: The purchasing information (PURCHI) might be incomplete or missing for the materials being processed. This could include missing purchasing info records, source lists, or vendor data.
  
  
  Planning Parameters: The planning parameters for the materials might not be set correctly. This includes settings in the material master or MRP views.
  
  
  MRP Type: The MRP type assigned to the material may not be appropriate for the purchasing scenario. For example, if the material is set to "ND" (no planning), it won't generate any purchase requisitions.
  
  
  Stock Levels: If the stock levels are sufficient to meet demand, the system may not generate any new purchase requisitions, leading to the error.
  
  
  MRP Run Issues: There may have been issues during the MRP run that prevented data from being saved, such as system errors or configuration issues.
  
  
  Solutions:
  
  
  Check Purchasing Data: Verify that all necessary purchasing data is complete and accurate. This includes checking the material master for purchasing info records, source lists, and vendor assignments.
  
  
  Review MRP Settings: Ensure that the MRP type and other relevant settings in the material master are correctly configured. If necessary, change the MRP type to one that allows for purchasing.
  
  
  Evaluate Stock Levels: Check the current stock levels and demand forecasts to ensure that there is a need for new purchase requisitions. If stock levels are adequate, the system will not generate new requisitions.
  
  
  Run MRP Again: If the initial MRP run encountered issues, try running it again after addressing any identified problems.
  
  
  Check MRP Logs: Review the MRP logs for any warnings or errors that could provide more context on why no data was saved.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on the MD151 error and related MRP processes.
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MD01 (MRP Run), MD04 (Stock/Requirements List), and ME51N (Create Purchase Requisition) to help diagnose and resolve issues.
  
  
  Material Master Views: Understand the different views in the material master, especially the MRP and Purchasing views, as they contain critical data for MRP and purchasing processes.
  
  
  SAP Notes: Check for any SAP Notes related to the MD151 error, as there may be specific patches or updates that address known issues.
  
  
  User Roles and Authorizations: Ensure that the user executing the MRP run has the necessary authorizations to access and modify the relevant data.
  
  
  By following these steps, you should be able to diagnose and resolve the MD151 error in SAP effectively.