How To Fix FAGL_MIG146 - No active BAdI implementation with missing doc. split fld &1 in ledger &2

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 146

• Message text: No active BAdI implementation with missing doc. split fld &1 in ledger &2

What causes this issue?

There is no active implementation for the Business Add In (BAdI)
<DS:SIMG.FAGL_MIGR_SUBST>FAGL_MIGR_SUBST</>. However, in New General
Ledger Accounting, at least one of the document splitting
characteristics defined <ZH>cannot</> be derived directly from the
source ledger in Special Purpose Ledger.

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?

First create an implementation and then activate it.

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_MIG146 - No active BAdI implementation with missing doc. split fld &1 in ledger &2 ?

  The SAP error message FAGL_MIG146 indicates that there is no active Business Add-In (BAdI) implementation for handling the missing document splitting field in the specified ledger. This error typically arises during the migration process to the new General Ledger (G/L) accounting in SAP, particularly when document splitting is involved.
  Cause:
  
  Missing BAdI Implementation: The error suggests that there is no active implementation of the BAdI that is required to handle the document splitting for the specified ledger.
  Configuration Issues: The ledger may not be properly configured to support document splitting, or the necessary BAdI implementations have not been activated.
  Custom Development: If there are custom requirements for document splitting that are not met by standard SAP functionality, a custom BAdI implementation may be needed.
  
  Solution:
  
  
  Check BAdI Implementations:
  
  Go to transaction code SE18 to check the BAdI definition related to document splitting.
  Use transaction code SE19 to see if there are any active implementations of the BAdI. If not, you may need to create one.
  
  
  
  Activate BAdI Implementation:
  
  If a suitable BAdI implementation exists but is not active, activate it.
  If no implementation exists, you may need to create a new one. This may require ABAP development skills to implement the necessary logic for document splitting.
  
  
  
  Review Ledger Configuration:
  
  Ensure that the ledger configuration supports document splitting. Check the settings in the configuration for the ledger in transaction OBY6 or OBY7.
  Make sure that the document splitting settings are correctly defined in the relevant controlling area and company code.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to document splitting and BAdIs for any specific requirements or additional steps that may be necessary.
  
  
  
  Testing:
  
  After implementing or activating the BAdI, perform tests to ensure that the document splitting works as expected without generating errors.
  
  
  
  Related Information:
  
  BAdI Documentation: Familiarize yourself with the specific BAdI documentation related to document splitting in SAP. This can provide insights into the expected behavior and implementation details.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide guidance on document splitting and BAdI implementations.
  SAP Community: Engage with the SAP Community forums for additional insights or similar experiences from other users.
  
  If you are not familiar with ABAP or BAdI implementations, it may be beneficial to involve a technical consultant or developer who can assist with the necessary changes.