Title: Urgent Help Needed: Cannot Delete Custom Table – Referenced Include No Longer Exists

[#1]

Dear SAP Experts,

I urgently need your help with an issue in SAP S/4HANA 1809 (SAP_BASIS 753).

I created a custom transparent tableZTB_BC_ENH_SWIand generated its maintenance dialog using SE54.

After deleting the maintenance dialog and its function group, I tried to delete the table in SE11.

However, SAP still reports that the table is being used by Include LZFG_BC_ENH_SWT00

The strange part is that this Include no longer exists!

My investigation:

1. SE38: Include does not exist.

2. TRDIR: No corresponding record.

3. SE11 Where-Used List: Still shows the deleted Include.

4. WBCROSSGT: Contains two references to the deleted Include.

5. EU_REORG: Completed successfully, but the issue remains.

Could anyone please advise on a safe, SAP-standard solution to remove these obsolete references?

I would like to avoid rebuilding the entire where-used index or manually modifying SAP system tables.

Your urgent assistance would be greatly appreciated!

Thank you very much in advance.

[AlexandrePassarelli]

Hi,

Good news: I don't think that include is really blocking you.

For SE11, a reference from a program or an include is only a warning. In RS_DD_DELETE_OBJ, form CHECK_OBJECT_USE, the deletion is blocked only when the table is used by another dictionary object (a view, a structure, a search help, a table type and so on). In that case the popup comes without the Delete button. When the users are programs, you get the popup "Object still in use" with the where-used list, but the Delete button is there and you can go on.

I tested it on a 2020 system (7.55). I created a test table and a small program with TABLES for it, the same way the T00 include of a maintenance dialog does. WBCROSSGT got the same kind of entry you see (TY, the table name, the program name). Then I deleted the table from ADT: the deletion check said "used by 1 other object" only as a warning (0 strong references, 1 weak), and the table was deleted.

So in SE11, when the popup lists LZFG_BC_ENH_SWT00, press Delete instead of Cancel. If the popup has no Delete button, then the list also has a dictionary object using the table, and that one is the real blocker.

About the two old entries in WBCROSSGT: they belong to the include, not to the table, so deleting the table doesn't remove them. In my test the entry was still there after the table was gone, and it only disappeared when I deleted the program. Since your include no longer exists, they are just orphan rows pointing to a table that no longer exists either. They would only show up again in a where-used list if you create a table with the same name later. SAPRSEUC won't clean them, because it only re-indexes customer programs that still exist in TRDIR.

Your system is 7.53 and I read the code on 7.55. This part of RS_DD_DELETE_OBJ is old code, so I expect the same behavior, but I didn't check it on a 7.53.

Hope it helps!