How To Fix GI128 - Ledger & is still using a pool table; see long text

SAP Error Message - Details

• Message type: E = Error

• Message class: GI - FI-SL update

• Message number: 128

• Message text: Ledger & is still using a pool table; see long text

What causes this issue?

You are attempting to post to an FI-SL pooled table. However, FI-SL
pooled tables are not to be used since Release 30F because they have
significant disadvantages compared to transparent tables (in terms of
performance and restricted functions, for example).

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?

Check whether you really use the ledger with the pooled table. Often,
the ledger L0 for pooled table GLT1 delivered by SAP is updated without
actually being used or valuated. Bear in mind that updating this type of
ledger unnecessarily costs both performance and memory space.
If the ledger is no longer required, deactivate it with Customizing
transaction GCL2. To do so, select the ledger and first delete all
activity assignments (both assignments directly to the ledger and
assignments to the ledger/company code or ledger/company combination).
Then deactivate the 'Ledger Posting Allowed' indicator in 'Additional
Settings' on the ledger master data screen. From now on, the ledger will
not be posted.
If the ledger for the pooled table is still required, convert to a
transparent table as soon as possible by implementing SAP Note 1014076.
In the exceptional case that you still want to use the ledger with the
pooled table and no longer want to see this information message when
posting, you can deactivate message GI128 with transaction OBA5 by
making a corresponding entry in table T100C.

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 GI128 - Ledger & is still using a pool table; see long text ?

  The SAP error message GI128 indicates that a ledger is still using a pool table, which is not recommended in the context of the new General Ledger (G/L) accounting. This error typically arises when there are inconsistencies in the configuration of the ledgers and the underlying database tables.
  Cause:
  
  Legacy Configuration: The ledger in question may have been configured to use a pool table, which is a legacy approach that is not compatible with the new G/L functionality.
  Migration Issues: If your organization has migrated from an older version of SAP to a newer one, some ledgers may not have been properly updated to use the new structure.
  Customizations: Custom developments or modifications in the system may have led to the ledger still referencing a pool table.
  
  Solution:
  
  
  Check Ledger Configuration: 
  
  Go to the configuration settings for the ledger in question (Transaction Code: OB22).
  Ensure that the ledger is set up to use the appropriate line item table (e.g., ACDOCA for the new G/L) instead of a pool table.
  
  
  
  Update Ledger Settings:
  
  If the ledger is still using a pool table, you may need to create a new ledger that uses the correct line item table and migrate the data from the old ledger to the new one.
  
  
  
  Data Migration:
  
  If necessary, use data migration tools or programs to transfer data from the old ledger to the new ledger structure. This may involve using tools like LSMW (Legacy System Migration Workbench) or custom ABAP programs.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific version of SAP you are using for any additional steps or considerations.
  
  
  
  Testing:
  
  After making changes, ensure to test the new configuration thoroughly to confirm that the error is resolved and that the ledger functions correctly.
  
  
  
  Consult SAP Support:
  
  If the issue persists or if you are unsure about making changes, consider reaching out to SAP support for assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OB22 (for ledger configuration) and ACDOCA (for line item display).
  SAP Notes: Check for any SAP Notes that may address this specific error or provide guidance on transitioning from pool tables to the new G/L structure.
  Documentation: Review the SAP Help Portal for information on the new General Ledger and its requirements.
  
  By addressing the configuration of the ledger and ensuring it aligns with the new G/L standards, you should be able to resolve the GI128 error.