How To Fix FCC0728 - Start of period (period 2) was set to &1 &2

FCC0728 - Overview

• Message type: E = Error

• Message class: FCC0 - Messages in Financial Closing Cockpit

• Message number: 728

• Message text: Start of period (period 2) was set to &1 &2

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 FCC0728 - Start of period (period 2) was set to &1 &2 ?

  The SAP error message FCC0728, which states "Start of period (period 2) was set to &1 &2," typically occurs in the context of financial closing processes or when dealing with fiscal periods in SAP. This error indicates that there is an issue with the configuration of the fiscal year variant or the period settings in the system.
  
  Cause:
  
  Incorrect Period Settings: The start date for the specified period (in this case, period 2) may not be correctly configured in the fiscal year variant.
  Fiscal Year Variant Configuration: The fiscal year variant may not be set up properly, leading to inconsistencies in the period definitions.
  Posting Periods: The posting periods may not be open for the specified period, preventing transactions from being processed.
  Date Mismatch: The date being used for transactions may fall outside the defined periods in the fiscal year variant.
  
  
  Solution:
  
  
  Check Fiscal Year Variant:
  
  Go to the transaction code OB29 to check the fiscal year variant