How To Fix FR573 - Enter a key date

FR573 - Overview

• Message type: E = Error

• Message class: FR - Messages for FI Reporting

• Message number: 573

• Message text: Enter a key 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.

FR573 - Details

• The SAP error message FR573 "Enter a key date" typically occurs in the context of financial transactions, particularly when dealing with asset accounting or financial reporting. This error indicates that a key date, which is necessary for processing the transaction or report, has not been provided.
  
  Cause:
  
  Missing Key Date: The most common cause of this error is that the user has not entered a key date in the relevant field. The key date is essential for determining the validity of the transaction or report.
  Incorrect Transaction Type: Certain transactions require a key date to be specified, and if the transaction type does not align with the requirements, this error may occur.
  
  Configuration Issues: There may be configuration settings in the SAP system that require a key date for specific processes, and if these are not set correctly, it can lead to this error.
  
  
  Solution:
  
  Enter a Key Date: The most straightforward solution is to enter