How To Fix FAGL_MIG066 - Not possible to reset clearing with clearing date before migration date

SAP Error Message - Details

• Message type: E = Error

• Message class: FAGL_MIG - Migration to New General Ledger Accounting

• Message number: 066

• Message text: Not possible to reset clearing with clearing date before migration date

What causes this issue?

You have performed a migration into New General Ledger Accounting for
ledger &V4& in company code &V3&. This means that it is no longer
possible to reset the clearing of an item with a clearing date (&V1&)
<ZH>prior to</> the migration date (&V2&).
You can only reset clearing actions that were posted <ZH>after </>the
migration date &V2& in New General Ledger Accounting.

Procedure for System Administrators

You can change this error message into a warning message instead.
However, to do this, you first need to ensure that the open items are
also included in the worklist for open items after the clearing has been
reset (see <DS:SIMG.FAGL_MIG_OPITEMS_FIL>Create Worklist for Open Items
</>).
To change the message, choose in the Implementation Guide for the Global
Settings in Financials <DS:SIMG.SIMG_CFORFBOBA5BELE>Change Message
Control for Document Processing</>.
You can find the work area and message number in the technical
information.

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_MIG066 - Not possible to reset clearing with clearing date before migration date ?

  The SAP error message FAGL_MIG066 indicates that there is an attempt to reset a clearing document with a clearing date that is earlier than the migration date. This typically occurs during the migration process to the new General Ledger (G/L) accounting in SAP, particularly when using the New G/L functionality.
  Cause:
  The error arises because the system enforces a restriction on clearing documents that were created before the migration date. The migration date is the point in time when the system transitioned from the classic G/L to the new G/L. Any clearing documents with dates prior to this migration date cannot be reset or modified, as it would violate the integrity of the financial data post-migration.
  Solution:
  To resolve this error, consider the following steps:
  
  
  Check Migration Date: Verify the migration date set in your system. This date is crucial as it marks the point after which all transactions are considered in the new G/L.
  
  
  Review Clearing Documents: Identify the clearing document you are trying to reset. Check its clearing date and ensure it is not earlier than the migration date.
  
  
  Adjust Clearing Date: If you need to reset a clearing document, ensure that the clearing date is on or after the migration date. If necessary, you may need to adjust your processes to ensure that any clearing operations respect this constraint.
  
  
  Consult Documentation: Review SAP documentation or notes related to the migration process and the handling of clearing documents in the new G/L. This can provide additional insights into best practices and potential workarounds.
  
  
  Seek Help from SAP Support: If the issue persists and you believe it should not be occurring, consider reaching out to SAP support for further assistance. They may provide specific guidance based on your system configuration and version.
  
  
  Related Information:
  
  Migration to New G/L: Understanding the migration process and its implications on financial transactions is crucial. Familiarize yourself with the steps involved in migrating to the new G/L and the associated restrictions.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FAGL_MIGRATE for migration activities and FBRA for resetting clearing documents.
  SAP Notes: Check for any SAP Notes related to FAGL_MIG066 for updates or patches that may address this issue.
  
  By following these steps, you should be able to address the FAGL_MIG066 error effectively.