How To Fix APERB210 - Restart required in period &1 &2 in ledger group &3

APERB210 - Overview

• Message type: E = Error

• Message class: APERB - Error Messages for Periodic Posting Run

• Message number: 210

• Message text: Restart required in period &1 &2 in ledger group &3

What causes this issue?

In Customizing for <LS>Asset Accounting</> you changed the <LS>
Alternative Fiscal Year Variants</> indicator, although a restart of a
previous depreciation run was necessary.

System Response

You <ZH>cannot</> execute any depreciation runs as long as the restart
does not take place under the old Customizing settings.

How to fix this error?

Contact your system administrator.

Procedure for System Administrators

Proceed as follows:
In Customizing for Asset Accounting under
<DS:SIMG.FIAA_BEW_GJAHR_NEWGL_DC>Allow Differing Variants for
Depreciation Areas with G/L Integration</>, take back the change of the
<LS>Alternative Fiscal Year Variants</> indicator.
Execute the restart.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message APERB210 - Restart required in period &1 &2 in ledger group &3 ?

  The SAP error message APERB210 "Restart required in period &1 &2 in ledger group &3" typically indicates that there is an issue with the financial closing process in the specified period and ledger group. This error often arises during the execution of financial processes such as closing entries, balance carryforward, or other period-end activities.
  
  Cause:
  
  Incomplete Processes: The error may occur if there are incomplete or interrupted processes in the specified period. This could be due to a previous run that did not finish successfully.
  
  Configuration Issues: There may be configuration issues in the ledger group or the financial settings that prevent the process from completing.
  Data Consistency: There might be inconsistencies in the data that need to be resolved before the process can continue.
  Locking Issues: If another user or process is currently accessing the same data, it may lead to this error.
  
  
  Solution:
  
  Check Previous Runs: Review the logs of previous runs to identify if