How To Fix /PF1/MSG_EOD036 - No data found with message_kind '&1'

/PF1/MSG_EOD036 - Overview

• Message type: E = Error

• Message class: /PF1/MSG_EOD -

• Message number: 036

• Message text: No data found with message_kind '&1'

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 /PF1/MSG_EOD036 - No data found with message_kind '&1' ?

  The SAP error message /PF1/MSG_EOD036 No data found with message_kind '&1' typically indicates that the system is unable to find any data related to the specified message_kind. This error is often encountered in the context of end-of-day (EOD) processing or reporting, where the system is expected to retrieve specific messages or data entries based on the provided criteria.
  Possible Causes:
  
  Incorrect Message Kind: The message_kind parameter may be incorrectly specified or does not exist in the system.
  Data Not Available: There may simply be no data available for the specified message_kind in the relevant tables or data sources.
  
  Configuration Issues: There could be configuration issues in the EOD processing setup that prevent the system from retrieving the expected data.
  Timing Issues: The data may not have been generated or processed yet, especially if the EOD process is still running or has not been executed.
  
  Solutions:
  
  Verify Message Kind: Check the value of message_kind being passed to ensure