How To Fix FSH_ARUN_MSG240 - ReturnPO: No entries found 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: 240

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

  The SAP error message FSH_ARUN_MSG240 indicates that the system could not find any entries for the specified OTD (Order to Delivery) date when processing a Return Purchase Order (ReturnPO). 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 be due to:
  
  No purchase orders or deliveries created for that date.
  Incorrect date format or date range specified in the transaction.
  Data not being updated or missing in the system.
  
  
  
  Configuration Issues: There may be configuration settings in the system that do not align with the expected data for the OTD date.
  
  
  Timing Issues: If the OTD date is set to a future date or a date that falls outside the range of available data, the system will not find any entries.
  
  
  Solution:
  
  
  Check Data Entries: Verify that there are valid entries in the system for the specified OTD date. You can do this by:
  
  Checking the relevant purchase orders and deliveries in the system.
  Ensuring that the date you are using is correct and falls within the range of available data.
  
  
  
  Adjust Date: If the OTD date is incorrect or not available, consider adjusting it to a date for which there are valid entries.
  
  
  Review Configuration: If the issue persists, review the configuration settings related to Return Purchase Orders and OTD dates. Ensure that the settings are correctly aligned with your business processes.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific details on how OTD dates are managed in your version of SAP.
  
  
  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 that may help in troubleshooting, such as ME23N (Display Purchase Order) or ME2N (Purchase Orders by PO Number).
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide additional insights or patches that could resolve the issue.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the cause of the error and implement a suitable solution.