How To Fix FAGL_MIG273 - No uniquely assigned account exists for old account &1

FAGL_MIG273 - Overview

• Message type: E = Error

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

• Message number: 273

• Message text: No uniquely assigned account exists for old account &1

What causes this issue?

In the new Customizing settings for FI-AA, no new account is uniquely
assigned to the old account &V1& in account determination &V3& from
chart of accounts &V2&.

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?

Proceed as follows:
In the new Customizing settings, ensure that there is a unique
relationship between the old account and the new account.
Run the check again.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

FAGL_MIG273 - Details

• The SAP error message FAGL_MIG273 indicates that during the migration process from the classic General Ledger (G/L) to the new G/L, the system could not find a uniquely assigned account for the old account specified in the error message. This typically occurs when there are issues with the mapping of accounts between the old and new G/L systems.
  
  Cause:
  
  Missing Mapping: The old account does not have a corresponding new account assigned in the mapping table.
  Multiple Assignments: There may be multiple new accounts assigned to the old account, leading to ambiguity.
  
  Configuration Issues: The configuration settings for the migration might not be set up correctly, leading to inconsistencies in account assignments.
  Data Inconsistencies: There may be inconsistencies in the master data or the migration data that prevent the system from finding a unique mapping.
  
  
  Solution:
  
  
  Check Account Mapping:
  
  Go to the transaction code OBY6 (or the relevant transaction for your version) to check the mapping of old