How To Fix GI129 - Ledger & for table & is no longer updated

SAP Error Message - Details

• Message type: E = Error

• Message class: GI - FI-SL update

• Message number: 129

• Message text: Ledger & for table & is no longer updated

What causes this issue?

You are trying to post a ledger to table GLT1 or GLT2. However, these
obsolete (pooled) tables are no longer used since Release 30F because
they have significant disadvantages compared to transparent tables (in
terms of performance and restricted functions, for example).

System Response

As of Release 618, ledgers are no longer updated in tables GLT1 and GLT2
and they can no longer be edited or analyzed using FI-SL functions.

How to fix this error?

Check whether you really need the ledger in question. It is often the
case that the ledger L0, which is delivered by SAP for table GLT1, is
updated without ever being used or analyzed.
If the ledger is no longer required, you can deactivate message GI129 by
using transaction OBA5 to make a suitable entry in table T100C.
If the ledger is still required, create a customer message for component
FI-SL-SL.

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 GI129 - Ledger & for table & is no longer updated ?

  The SAP error message GI129 typically indicates that a ledger is no longer being updated for a specific table. This can occur in the context of Financial Accounting (FI) or Controlling (CO) modules, where certain ledgers are configured to be updated based on specific criteria or conditions.
  Cause of GI129 Error
  
  Configuration Issues: The ledger may have been configured incorrectly, or the settings may have changed, leading to it being marked as inactive or not updated.
  Data Consistency: There may be inconsistencies in the data that prevent the ledger from being updated.
  Period Closing: If the financial period is closed, the system may prevent updates to certain ledgers.
  Authorization Issues: Lack of proper authorizations for the user trying to perform the update can also lead to this error.
  Customizations or Enhancements: Custom code or enhancements may inadvertently affect the updating of the ledger.
  
  Solution
  
  Check Configuration: Review the configuration settings for the ledger in the SAP system. Ensure that the ledger is set to be updated and that all necessary parameters are correctly configured.
  Data Consistency Check: Run consistency checks on the relevant tables to identify any discrepancies that may be causing the issue.
  Open Periods: Ensure that the financial periods are open for posting. If the period is closed, you may need to reopen it or post to a different period.
  User Authorizations: Verify that the user has the necessary authorizations to update the ledger. This may involve checking roles and permissions in the SAP system.
  Review Custom Code: If there are any custom enhancements or modifications, review them to ensure they are not interfering with the ledger updates.
  Consult Documentation: Refer to SAP documentation or notes related to the specific error message for additional guidance and troubleshooting steps.
  
  Related Information
  
  Transaction Codes: You may need to use transaction codes like OB52 (to manage posting periods) or SPRO (to access configuration settings) to investigate and resolve the issue.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the cause of the GI129 error and implement a solution to resolve it.