How To Fix RM136 - No planned orders exist for the selection criteria

SAP Error Message - Details

• Message type: E = Error

• Message class: RM - Messages for Repetitive Manufacturing

• Message number: 136

• Message text: No planned orders exist for the selection criteria

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 RM136 - No planned orders exist for the selection criteria ?

  The SAP error message RM136 ("No planned orders exist for the selection criteria") typically occurs when you are trying to execute a transaction or report that requires planned orders, but there are no planned orders available that meet the specified selection criteria. This can happen in various contexts, such as when using transaction codes like MD04 (Stock/Requirements List) or MD05 (Individual Display of MRP List).
  Causes:
  
  No Planned Orders Created: There may simply be no planned orders created for the material or plant you are trying to analyze.
  Selection Criteria Mismatch: The selection criteria you have entered (such as material number, plant, or date range) may not match any existing planned orders.
  Data Deletion: Planned orders may have been deleted or archived, making them unavailable for the current selection.
  Incorrect MRP Settings: The Material Requirements Planning (MRP) settings for the material may not be configured correctly, leading to no planned orders being generated.
  Time Frame Issues: The time frame you are looking at may not include any planned orders, especially if you are looking at a future date where no orders have been planned yet.
  
  Solutions:
  
  Check for Existing Planned Orders: Use transaction codes like MD04 or MD05 to check if there are any planned orders for the material and plant in question.
  Review Selection Criteria: Ensure that the selection criteria you are using are correct. Double-check the material number, plant, and any other filters you have applied.
  Create Planned Orders: If no planned orders exist, you may need to create them manually or run the MRP process to generate them.
  Check MRP Settings: Review the MRP settings for the material in the material master (transaction MM03) to ensure that they are set up correctly.
  Adjust Time Frame: If you are looking at a specific date range, try expanding it to see if planned orders exist outside of your current selection.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MD01 (MRP Run), MD02 (Single-item, Multi-level MRP), and MD04 (Stock/Requirements List).
  MRP Configuration: Understanding MRP configuration in SAP can help in troubleshooting issues related to planned orders.
  Material Master Data: Ensure that the material master data is complete and accurate, as this can affect MRP results.
  SAP Notes: Check SAP Notes for any known issues or updates related to planned orders and MRP processes.
  
  If the issue persists after checking these aspects, it may be beneficial to consult with your SAP support team or refer to SAP documentation for further assistance.