How To Fix GU978 - You cannot delete the pools since pooled tables are still used

SAP Error Message - Details

• Message type: E = Error

• Message class: GU - FI-SL utilities

• Message number: 978

• Message text: You cannot delete the pools since pooled tables are still used

What causes this issue?

It is not possible to delete the pools if pooled tables are still being
used in FI-SL (see table T800A).

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?

Convert the pool tables to transparent tables in accordance with the
conversion guidelines and delete the installation of these tables from
FI-SL.
You can then delete the pools.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GU978 - You cannot delete the pools since pooled tables are still used ?

  The SAP error message GU978 indicates that you are trying to delete a pooled table or a pool, but there are still references to that pooled table in the system. This typically occurs when there are still active database objects or dependencies that rely on the pooled table you are attempting to delete.
  Cause:
  
  Active References: The pooled table is still being used by other database objects, such as views, indexes, or other tables.
  Data Dependencies: There may be data in the pooled table that is still being referenced by other applications or processes.
  Open Transactions: There might be open transactions or sessions that are currently accessing the pooled table.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Dependencies:
  
  Use transaction code SE11 (Data Dictionary) to check for any dependencies on the pooled table. Look for views, indexes, or other tables that reference the pooled table.
  You can also use transaction code SE80 (Object Navigator) to explore the object dependencies.
  
  
  
  Remove References:
  
  If you find any dependent objects, you will need to either delete or modify them to remove the references to the pooled table.
  Ensure that there are no active views or other database objects that are still using the pooled table.
  
  
  
  Check for Open Transactions:
  
  Ensure that there are no open transactions or sessions that are currently accessing the pooled table. You can check this using transaction code SM12 (Lock Entries) to see if there are any locks on the table.
  
  
  
  Delete Data:
  
  If the pooled table contains data that is no longer needed, you may want to delete the data first before attempting to delete the table itself.
  
  
  
  Retry Deletion:
  
  Once you have ensured that there are no dependencies or active references, you can attempt to delete the pooled table again.
  
  
  
  Related Information:
  
  Pooled Tables: Pooled tables are a type of database table in SAP that allows multiple logical tables to share the same physical table in the database. They are used to optimize database storage and performance.
  Transaction Codes:
  
  SE11: Data Dictionary - to view and manage database objects.
  SE80: Object Navigator - to explore object dependencies.
  SM12: Lock Entries - to check for locks on database objects.
  
  
  Documentation: Refer to SAP Help documentation for more details on managing database objects and understanding pooled tables.
  
  If you continue to face issues after following these steps, consider reaching out to your SAP Basis team or consulting SAP support for further assistance.