‎2020 May 18 3:13 PM
Hi,
We have deleted a table extension and due to a misunderstanding we have not cleaned up all dependencies before. Re-implementing the enhancement to delete the dependencies encounters a problem because the deletion was created in a repair order. Is there a way to delete the remaining dependencies at a deeper level?
‎2020 May 18 3:21 PM
Hi nw.
If these dependencies are in a separate Z* table, then you could probably use SE14 transaction to clear all data in the table. You'd need access to the SE14, obviously.

‎2020 May 18 3:31 PM
Hi Mateusz,
It was a standard SAP enhancement CI_PRPS. With se14, I can only edit the table itself (PRPS).
‎2020 May 18 3:40 PM
Hi Nadine,
I understood the dependencies as records in the DB, which were dependent on the data from the deleted enhancement.
This is not the case, correct?
What are these dependencies you mentioned?
Regards,
Mateusz
‎2020 May 19 7:22 AM
Hi Mateusz,
Yes, the dependencies are not in the table itself. The deleted extension was still used in other places. So I'm thinking about how I can find out where it was used and SAP stores everything in tables, so I assume that the connections are stored somewhere. It should be able to delete them.
‎2020 May 19 7:44 AM
Hi Nadine,
Did you have custom data elements in this extension? If yes, and if you did not delete them, then I would look using the Where-Used option of these.
When it comes to ABAP source codes, these are stored in a table named REPOSRC. The codes are compressed and you won't be able to access them via SQL or other tools. You could use report RPR_ABAP_SOURCE_SCAN to search for the use of the removed fields in any source code.
Regards,‎2020 May 19 8:00 AM
Hi,
That sounds like a possibility, I'll look into it. Thanks for the tip.
‎2020 May 19 12:59 PM
You say: "Re-implementing the enhancement to delete the dependencies encounters a problem because the deletion was created in a repair order."
I don't see why it would be a so big problem. Can you clarify?