How To Fix FAGL_MM_RECON110 - Period start &1 (MM) does not match period start for ledger &2

FAGL_MM_RECON110 - Overview

• Message type: E = Error

• Message class: FAGL_MM_RECON - MM-GL Reconciliation

• Message number: 110

• Message text: Period start &1 (MM) does not match period start for ledger &2

What causes this issue?

The specified period &V1& in Materials Management starts on &V3&.
However, the related posting period &V2& of the selected ledger starts
on &V4&.

System Response

It is <ZH>not</> possible to reconcile the periods because they do <ZH>
not</> cover the same period.

How to fix this error?

For the comparison, select objects with compatible periods.

Procedure for System Administrators

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 FAGL_MM_RECON110 - Period start &1 (MM) does not match period start for ledger &2 ?

  The SAP error message FAGL_MM_RECON110 indicates a mismatch between the period start date in the Material Management (MM) module and the period start date in the General Ledger (GL) for a specific ledger. This error typically arises during the reconciliation process between MM and FI (Financial Accounting) when the periods do not align.
  
  Cause:
  
  
  Period Variance: The period start date in the MM module does not match the period start date in the GL for the specified ledger. This can happen if:
  
  The periods have been opened or closed at different times in MM and FI.
  There are discrepancies in the configuration of the fiscal year variant between MM and FI.
  Changes were made to the period status in one module without corresponding changes in the other.
  
  
  
  
  Configuration Issues: There may be configuration issues in the fiscal year variant settings or the posting periods for the ledgers.
  
  
  
  Solution:
  
  
  Check Period Status:
  
  Go to the transaction code OB52 to check