How To Fix FAGL_MIG126 - The documents listed have been included in the Customizing table

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 126

• Message text: The documents listed have been included in the Customizing table

What causes this issue?

The listed documents have been included in the Customizing table for
maintaining document-specific business transaction assignments.
Previously existing entries for the document keys were <ZH>not</>
overwritten. All entries transferred start off with the status
<LS>Inactive</>.

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?

In the case of documents containing errors, make the correct assignment
to a business transaction/business transaction variant under
<DS:SIMG.FAGL_V_FAGL_MIG_PROC>Define Alternative Business Transaction
Assignment</> and set the entry to status <LS>Active</>.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FAGL_MIG126 - The documents listed have been included in the Customizing table ?

  The SAP error message FAGL_MIG126 indicates that certain documents have been included in the customizing table, which typically relates to the migration of financial documents in the context of the New General Ledger (New GL) functionality in SAP. This error often arises during the migration process when the system detects that specific documents are already accounted for in the customizing settings, which can prevent further processing or migration.
  Cause:
  
  Existing Entries in Customizing Table: The error usually occurs when there are entries in the customizing table that conflict with the documents being processed. This can happen if the documents have already been migrated or if there are inconsistencies in the configuration.
  Incorrect Configuration: If the customizing settings for the New GL are not properly configured, it can lead to this error.
  Data Integrity Issues: There may be issues with the data integrity of the documents being migrated, such as duplicates or inconsistencies.
  
  Solution:
  
  Check Customizing Settings: Review the customizing settings related to the New GL and ensure that they are correctly configured. This includes checking the relevant tables and entries that may be causing the conflict.
  Review Migration Documents: Identify the specific documents listed in the error message and verify their status. Ensure that they have not already been processed or migrated.
  Data Cleanup: If there are duplicates or inconsistencies in the data, perform a cleanup to resolve these issues. This may involve deleting or correcting erroneous entries.
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide solutions or workarounds for known issues.
  Use Transaction Code: You can use transaction code FAGL_MIGRATION to check the migration status and see if there are any additional details or logs that can help diagnose the issue.
  Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance. They can provide more specific guidance based on your system configuration and the details of the error.
  
  Related Information:
  
  Migration to New GL: Understanding the migration process to the New General Ledger is crucial. Familiarize yourself with the steps involved and the prerequisites for a successful migration.
  Customizing Tables: Knowledge of the relevant customizing tables (e.g., T001, T003, etc.) and their significance in the New GL setup can help in troubleshooting.
  Documentation: Refer to SAP documentation and guides related to New GL migration for best practices and common pitfalls.
  
  By following these steps, you should be able to identify the root cause of the FAGL_MIG126 error and implement a solution to resolve it.