How To Fix FAGL_MIG119 - &1 migration object(s) for account type &2 determined

FAGL_MIG119 - Overview

• Message type: E = Error

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

• Message number: 119

• Message text: &1 migration object(s) for account type &2 determined

What causes this issue?

Depending on the program control settings, the number of migration
objects is determined in one of the following ways:
Determination of the open items to be migrated:
The complete dataset of the items that were open on the migration date
is determined.
Determination of the documents to be migrated:
When you execute the program for the first time (that is, the worklist
of documents to be migrated is empty), the system determines the
complete dataset of documents starting from the migration date.
If you have set the <LS>Read Completely</> indicator, the system also
determines the complete dataset of the documents from the migration date
when program execution is repeated. If you have <ZH>not </>set the <LS>
Read Completely</> indicator, the system determines just those documents
that were posted since the system time of the document that was included
last in the worklist.

System Response

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

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

FAGL_MIG119 - Details

• The SAP error message FAGL_MIG119 typically occurs during the migration process to the new General Ledger (G/L) accounting in SAP. This error indicates that there are migration objects for a specific account type that have been identified, but there may be issues with the data or configuration that need to be addressed.
  
  Cause:
  The error message FAGL_MIG119 is usually triggered by one or more of the following reasons:
  
  Missing Configuration: The account type specified in the error message may not be properly configured in the system for migration.
  Data Inconsistencies: There may be inconsistencies or missing data in the source system that prevent the migration from proceeding.
  Incorrect Mapping: The mapping of accounts from the old G/L to the new G/L may not be correctly set up, leading to issues in identifying the migration objects.
  Authorization Issues: The user executing the migration may not have the necessary authorizations to access the required data or perform the