How To Fix S95_MESSAGES013 - Order number &1: Control recipe &2 does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: S95_MESSAGES - S95 Message Processing

• Message number: 013

• Message text: Order number &1: Control recipe &2 does not exist

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 S95_MESSAGES013 - Order number &1: Control recipe &2 does not exist ?

  The SAP error message S95_MESSAGES013 indicates that a control recipe associated with a specific order number does not exist in the system. This error typically occurs in the context of production planning and execution, particularly when dealing with process orders in the SAP system.
  Cause:
  
  
  Non-Existent Control Recipe: The control recipe that is being referenced does not exist in the system. This could be due to:
  
  The control recipe was never created.
  The control recipe was deleted or archived.
  The order number or control recipe number is incorrect or mistyped.
  
  
  
  Incorrect Order Status: The order may not be in a status that allows for the creation or referencing of a control recipe.
  
  
  Configuration Issues: There may be configuration issues in the system that prevent the control recipe from being generated or linked to the order.
  
  
  Solution:
  
  
  Verify Control Recipe: Check if the control recipe exists in the system. You can do this by:
  
  Navigating to the relevant transaction (e.g., COR1 for creating control recipes) and searching for the control recipe number.
  Ensuring that the control recipe is correctly linked to the order.
  
  
  
  Check Order Details: Verify the order number and ensure that it is correct. Check the status of the order to ensure it is in a state that allows for control recipe processing.
  
  
  Create Control Recipe: If the control recipe does not exist, you may need to create it manually. This can typically be done through the appropriate transaction codes (e.g., COR1 or COR2).
  
  
  Review Configuration: If the issue persists, review the configuration settings related to control recipes in the SAP system. This may involve checking the settings in the production planning module or consulting with a functional consultant.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for additional guidance on control recipes and their management.
  
  
  Contact Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as COR1 (Create Control Recipe), COR2 (Change Control Recipe), and COR3 (Display Control Recipe).
  SAP Notes: Check for any SAP Notes related to control recipes and the specific error message for potential patches or updates.
  User Authorization: Ensure that you have the necessary authorizations to create or modify control recipes in the system.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.