How To Fix 61739 - Sales order item &1 &2 is not MRP-relevant

SAP Error Message - Details

• Message type: E = Error

• Message class: 61 - Fehlermeldungen fuer Bedarfsplanung

• Message number: 739

• Message text: Sales order item &1 &2 is not MRP-relevant

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 61739 - Sales order item &1 &2 is not MRP-relevant ?

  The SAP error message 61739 indicates that a specific sales order item is not relevant for Material Requirements Planning (MRP). This can occur for various reasons, and understanding the cause is essential for resolving the issue.
  Cause:
  
  
  Item Category Settings: The item category of the sales order item may be configured in such a way that it is not considered MRP-relevant. Certain item categories are designed for non-stock items or services, which do not require MRP processing.
  
  
  Material Master Settings: The material associated with the sales order item may have settings in the material master that exclude it from MRP. This could include settings like "MRP Type" being set to "ND" (No MRP) or "E" (External Procurement).
  
  
  Sales Order Type: The sales order type may not be configured to allow MRP relevance for certain items. Some sales order types are specifically designed for non-MRP items.
  
  
  Availability Check: The availability check configuration may also affect whether an item is considered MRP-relevant. If the availability check is set to a type that does not consider MRP, the item may be excluded.
  
  
  Solution:
  
  
  Check Item Category: Review the item category of the sales order item. If it is set to a non-MRP-relevant category, consider changing it to a category that is MRP-relevant.
  
  
  Review Material Master: Go to the material master record for the item in question and check the MRP-related fields. Ensure that the MRP type is set appropriately (e.g., "PD" for MRP) and that the material is set up for stock management if necessary.
  
  
  Sales Order Type Configuration: Check the configuration of the sales order type being used. Ensure that it is set up to allow MRP relevance for the items being sold.
  
  
  Availability Check Settings: Review the availability check settings in the sales order. Ensure that the check is configured to consider MRP.
  
  
  Consult Documentation: If you are unsure about the settings, consult the SAP documentation or your SAP support team for guidance on how to configure item categories, material masters, and sales order types for MRP relevance.
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like MM02 (Change Material), VA02 (Change Sales Order), and OVL2 (Define Item Categories) to make the necessary changes.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to MRP relevance and error message 61739.
  Testing: After making changes, create a test sales order to verify that the issue has been resolved and that the item is now MRP-relevant.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.