How To Fix FSH_ARUN_MSG266 - Prod. order: No entries found for OTD date; system will use default date

SAP Error Message - Details

• Message type: E = Error

• Message class: FSH_ARUN_MSG - ARUN Message Class

• Message number: 266

• Message text: Prod. order: No entries found for OTD date; system will use default date

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 FSH_ARUN_MSG266 - Prod. order: No entries found for OTD date; system will use default date ?

  The SAP error message FSH_ARUN_MSG266 indicates that the system could not find any entries for the specified Order-to-Delivery (OTD) date for a production order. As a result, the system defaults to using a predefined date instead. This message typically arises in the context of production planning and order management within SAP.
  Cause:
  
  
  Missing Data: There may be no entries in the relevant tables for the specified OTD date. This could be due to:
  
  The production order not being scheduled correctly.
  Missing or incorrect configuration in the production planning settings.
  The OTD date not being set or being outside the valid range.
  
  
  
  Configuration Issues: The settings for the production order or the related master data (like material master, routing, etc.) may not be properly configured.
  
  
  Data Consistency: There may be inconsistencies in the data that prevent the system from finding the appropriate entries for the OTD date.
  
  
  Solution:
  
  
  Check Production Order: Verify the production order details to ensure that it has been created and scheduled correctly. Check the OTD date and ensure it is valid.
  
  
  Review Configuration: 
  
  Check the configuration settings in the production planning module to ensure that the OTD date is being calculated correctly.
  Ensure that the relevant master data (like material master, BOM, routing) is correctly set up.
  
  
  
  Data Maintenance: 
  
  If necessary, maintain the relevant data entries for the OTD date in the system. This may involve creating or updating records in the relevant tables.
  Ensure that the production order is linked to the correct planning data.
  
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific details on how to handle OTD dates and production orders.
  
  
  System Logs: Check system logs for any additional error messages or warnings that may provide more context about the issue.
  
  
  Contact Support: If the issue persists, 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 CO01 (Create Production Order), CO02 (Change Production Order), and CO03 (Display Production Order) to manage production orders effectively.
  Master Data: Understand the importance of maintaining accurate master data in SAP, including material master records, BOMs, and routings, as they directly impact production planning and scheduling.
  SAP Notes: Check for any SAP Notes related to this error message for potential patches or updates that may resolve the issue.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to prevent it from occurring in the future.