How To Fix FSH_ARUN_MSG263 - PO: No entries found for OTD date; system will use the default date

FSH_ARUN_MSG263 - Overview

• Message type: E = Error

• Message class: FSH_ARUN_MSG - ARUN Message Class

• Message number: 263

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

  The SAP error message FSH_ARUN_MSG263 indicates that the system could not find any entries for the specified OTD (Order to Delivery) date in the context of a Purchase Order (PO). As a result, the system defaults to using a predefined date instead.
  
  Cause:
  
  
  Missing Data: The primary cause of this error is that there are no entries in the relevant database tables for the specified OTD date. This could happen if:
  
  The data has not been maintained for the specified date.
  The entries have been deleted or not yet created.
  The date being referenced is outside the range of valid entries.
  
  
  
  
  Configuration Issues: There may be configuration settings in the system that are not set up correctly, leading to the absence of expected data.
  
  
  Incorrect Date Input: The date being used may be incorrect or not aligned with the expected format or range.
  
  
  
  Solution:
  
  
  Check Data Entries: Verify that the necessary data for the OTD date exists in the