How To Fix FAGL_MIG144 - Document splitting field &1 of ledger &2 not used in GL Accounting

FAGL_MIG144 - Overview

• Message type: E = Error

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

• Message number: 144

• Message text: Document splitting field &1 of ledger &2 not used in GL Accounting

What causes this issue?

In the source ledger in Special Purpose Ledger, the field &V1& is used
as a document splitting characteristic. In Customizing for New General
Ledger Accounting, however, this field is <ZH>not </>defined as a
document splitting characteristic.

System Response

The data for this document splitting characteristic will <ZH>not </>be
transferred to New General Ledger Accounting during the migration.
Consequently, the data is <ZH>not </>available in the target ledger.

How to fix this error?

Check whether it is necessary to transfer the document splitting
information for this field. Where appropriate, change the Customizing
settings in New General Ledger Accounting before performing the
migration.

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.

FAGL_MIG144 - Details

• The SAP error message FAGL_MIG144 indicates that there is an issue with document splitting in the context of General Ledger (GL) accounting. Specifically, it means that a document splitting field (denoted as &1) for a specific ledger (denoted as &2) is not being utilized in the GL accounting configuration. This can occur during the migration process or when trying to post documents that require document splitting.
  
  Cause:
  
  Configuration Issue: The document splitting field specified is not activated or configured for the ledger in question. This can happen if the field is not part of the splitting characteristics for the ledger.
  Inconsistent Settings: The settings for document splitting may not be consistent across different ledgers or may not align with the requirements of the posting.
  Migration Settings: If you are migrating data from an older version of SAP or from another system, the migration settings may not have been properly aligned with the new document