How To Fix FSH_ARUN_MSG005 - Sales order: No entries for OTD date; system will use the default date

SAP Error Message - Details

• Message type: E = Error

• Message class: FSH_ARUN_MSG - ARUN Message Class

• Message number: 005

• Message text: Sales order: No entries for OTD date; system will use the 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_MSG005 - Sales order: No entries for OTD date; system will use the default date ?

  The SAP error message FSH_ARUN_MSG005 indicates that there are no entries for the Order to Delivery (OTD) date in the sales order, and as a result, the system will default to a standard date. This typically occurs in the context of sales order processing, particularly when dealing with delivery schedules or planning.
  Cause:
  
  Missing OTD Date Entries: The sales order does not have any specified OTD dates, which are necessary for the system to determine when the order should be delivered.
  Configuration Issues: There may be configuration settings in the system that are not set up correctly, leading to the absence of OTD date entries.
  Data Entry Errors: During the creation or modification of the sales order, the OTD date may not have been entered or was inadvertently deleted.
  Master Data Issues: Related master data (like customer or material master) may not have the necessary information that influences the OTD date.
  
  Solution:
  
  Check Sales Order Details: Review the sales order to ensure that the OTD date is correctly entered. If it is missing, you can manually enter the appropriate date.
  Review Configuration Settings: Check the configuration settings in the SAP system related to sales order processing and delivery scheduling. Ensure that the OTD date is being derived correctly based on the settings.
  Update Master Data: Ensure that the relevant master data (customer, material, etc.) is complete and accurate. This may involve checking the delivery plant, shipping conditions, and other related fields.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on how to set up and manage OTD dates in your system.
  Contact Support: If the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert to investigate further.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like VA03 (Display Sales Order) to view the sales order details or VA02 (Change Sales Order) to make necessary adjustments.
  SAP Notes: Check for any relevant SAP Notes that might address known issues or provide patches related to this error message.
  User Exits and BAdIs: If custom logic is involved in determining the OTD date, review any user exits or BAdIs that might be affecting the process.
  
  By addressing the underlying causes and following the suggested solutions, you should be able to resolve the error message and ensure that the sales order processing continues smoothly.