How To Fix FSH_ARUN_MSG028 - STO: 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: 028

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

  The SAP error message FSH_ARUN_MSG028 indicates that the system could not find any entries for the specified OTD (Order to Delivery) date in the context of a Stock Transport Order (STO). As a result, the system defaults to using a predefined date instead.
  Cause:
  
  
  Missing Data: There may be no entries in the relevant tables for the specified OTD date. This could be due to:
  
  Incorrect date range specified in the STO.
  No relevant stock transport orders created for that date.
  Data not being updated or maintained properly in the system.
  
  
  
  Configuration Issues: The configuration settings for the STO process may not be set up correctly, leading to the system not being able to find the necessary entries.
  
  
  Data Migration Issues: If data was recently migrated or updated, there may be inconsistencies or missing entries in the database.
  
  
  Solution:
  
  
  Check the OTD Date: Verify the OTD date you are using. Ensure that it is correct and falls within the expected range of dates for the STO.
  
  
  Review STO Entries: Look into the relevant tables (e.g., EKKO, EKPO) to see if there are any entries for the specified OTD date. You can use transaction codes like SE16 or SE11 to check the data.
  
  
  Update Configuration: If the issue is related to configuration, review the settings in the customizing transaction (SPRO) for Stock Transport Orders and ensure that all necessary configurations are in place.
  
  
  Data Maintenance: If there are missing entries, you may need to create or update the relevant data in the system to ensure that the OTD date has corresponding entries.
  
  
  Consult Documentation: Check SAP documentation or notes related to this error message for any specific recommendations or patches that may address the issue.
  
  
  Contact Support: If the problem persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME21N (Create Purchase Order), ME22N (Change Purchase Order), and ME23N (Display Purchase Order) to manage STOs.
  SAP Notes: Search for SAP Notes related to this error message in the SAP Support Portal for any known issues or fixes.
  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 solution to resolve it.