How To Fix FINS_ACDOC_CUST377 - Migration of G/L Cust. not performed due to errors prior to migration

FINS_ACDOC_CUST377 - Overview

• Message type: E = Error

• Message class: FINS_ACDOC_CUST - Unified Journal Entry - Customizing

• Message number: 377

• Message text: Migration of G/L Cust. not performed due to errors prior to migration

What causes this issue?

The system did <zh>not</> perform the migration of the General Ledger
Customizing.
As preparative step for the migration the system automatically performed
the IMG activity <DS:SIMG.FINS_MIG_CHECK_LDGR>Check Customizing Settings
Prior to Migration</> to check whether the prerequisites are fullfilled.

System Response

Some errors occurred in the IMG activity
<DS:SIMG.FINS_MIG_CHECK_LDGR>Check Customizing Settings Prior to
Migration</>. As a consequence the migration was not performed.

How to fix this error?

Correct the errors and start the migration of the General Ledger
Customizing again.

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 FINS_ACDOC_CUST377 - Migration of G/L Cust. not performed due to errors prior to migration ?

  The SAP error message FINS_ACDOC_CUST377 indicates that there were issues encountered during the migration of General Ledger (G/L) customer data, which prevented the migration from being completed successfully. This error typically arises in the context of the SAP S/4HANA migration process, particularly when transitioning from an older version of SAP or from a different system.
  Causes:
  
  Data Inconsistencies: There may be inconsistencies or errors in the data that is being migrated. This could include missing mandatory fields, incorrect data formats, or invalid references.
  
  Configuration Issues: The configuration settings in the system may not be aligned with the requirements for migration. This could involve settings related to the G/L accounts, customer accounts, or other related configurations.
  Custom Code or Enhancements: If there are custom developments or enhancements in the existing system, they may not be compatible with the new system or may cause issues during migration.
  Missing Master Data: Required master data (like customer master records)