How To Fix F6073 - End date of the fiscal year could not be determined

SAP Error Message - Details

• Message type: E = Error

• Message class: F6 - Funds Management Master Data Maintenance

• Message number: 073

• Message text: End date of the fiscal year could not be determined

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 F6073 - End date of the fiscal year could not be determined ?

  The SAP error message F6073, which states "End date of the fiscal year could not be determined," typically occurs in the context of financial transactions or reporting when the system is unable to identify the end date of the fiscal year for a particular company code or controlling area. This can happen for several reasons, and here are some common causes, solutions, and related information:
  Causes:
  
  Missing Fiscal Year Variant: The fiscal year variant may not be properly assigned to the company code or controlling area.
  Incorrect Configuration: The fiscal year variant may not be configured correctly in the system, leading to issues in determining the end date.
  Data Inconsistencies: There may be inconsistencies or missing data in the configuration tables related to fiscal years.
  Period Locking: If the periods are locked or not open for posting, it may lead to this error.
  Company Code Not Defined: The company code for which the transaction is being processed may not be defined correctly in the system.
  
  Solutions:
  
  
  Check Fiscal Year Variant Assignment:
  
  Go to the transaction code OB29 to check the fiscal year variant assignment for the company code.
  Ensure that the fiscal year variant is correctly assigned to the relevant company code.
  
  
  
  Review Fiscal Year Variant Configuration:
  
  Use transaction code OB37 to review the configuration of the fiscal year variant.
  Ensure that the start and end dates of the fiscal year are correctly defined.
  
  
  
  Check for Data Inconsistencies:
  
  Use transaction code OB52 to check if the posting periods are open for the relevant fiscal year.
  Ensure that there are no inconsistencies in the configuration tables.
  
  
  
  Verify Company Code Settings:
  
  Check the company code settings in transaction code OBY6 to ensure that the company code is properly defined and configured.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to this error message.
  
  
  
  Testing in a Development Environment:
  
  If possible, replicate the issue in a development or test environment to further analyze the problem without affecting production data.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  OB29: Assign Fiscal Year Variant to Company Code
  OB37: Define Fiscal Year Variant
  OB52: Open and Close Posting Periods
  OBY6: Define Company Code
  
  
  
  SAP Documentation: Refer to the official SAP documentation for detailed information on fiscal year configuration and related financial settings.
  
  
  SAP Community: Engage with the SAP Community forums for insights and solutions from other users who may have encountered similar issues.
  
  
  By following these steps, you should be able to identify the cause of the F6073 error and implement the necessary solutions to resolve it.