How To Fix FIPL_SAFT209 - New General Ledger Accounting is not active in company code &

SAP Error Message - Details

• Message type: E = Error

• Message class: FIPL_SAFT - SAFT: Message Class

• Message number: 209

• Message text: New General Ledger Accounting is not active in company code &

What causes this issue?

New General Ledger Accounting is not active for the specified Company
Code.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

It is not possible to extract GL Entries/FI Invoices for this G/L View
in this Company Code.

How to fix this error?

If you wish to extract data for New General Ledger Accounting, then you
must first activate New General Ledger Accounting in your system, for
this Company Code. Otherwise, the system will only carry out data
extraction for Classic G/L.

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 FIPL_SAFT209 - New General Ledger Accounting is not active in company code & ?

  The SAP error message FIPL_SAFT209 indicates that the New General Ledger Accounting (New G/L) is not active for the specified company code. This error typically arises when you attempt to perform operations that require New G/L functionality, but the company code in question is still using the classic General Ledger.
  Cause:
  
  New G/L Not Activated: The primary cause of this error is that the New General Ledger Accounting has not been activated for the specified company code.
  Configuration Issues: There may be configuration issues or incomplete settings in the system that prevent the activation of New G/L.
  Legacy System: The company code may still be operating under the legacy system (classic G/L) if it has not been migrated to the New G/L.
  
  Solution:
  To resolve this error, you need to activate the New General Ledger for the affected company code. Here are the steps to do so:
  
  
  Check Current Settings:
  
  Go to transaction code OBY6 (Activate New G/L).
  Check if the company code is listed and whether the New G/L is activated.
  
  
  
  Activate New G/L:
  
  If the New G/L is not activated, you can activate it by selecting the company code and following the prompts to enable New G/L functionality.
  Ensure that all necessary prerequisites are met before activation.
  
  
  
  Review Configuration:
  
  After activation, review the configuration settings to ensure that all necessary parameters are set correctly for the New G/L.
  This includes settings for document splitting, ledger configuration, and other related settings.
  
  
  
  Testing:
  
  After activation, perform tests to ensure that the New G/L is functioning correctly and that the error does not reoccur.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or guides on activating New G/L for detailed steps and considerations.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  OBY6: Activate New G/L
  OB52: Open and close posting periods
  OBY1: Company code settings
  
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or fixes related to this error.
  Migration Considerations: If you are migrating from classic G/L to New G/L, ensure that you follow the proper migration steps and guidelines provided by SAP.
  
  If you continue to experience issues after following these steps, it may be beneficial to consult with your SAP Basis or Finance team, or reach out to SAP support for further assistance.