Slow Where-Used in ADT

[Jeansy]

Dear all,

do you also have the same experience that the usage of the where-used-list is much slower in ADT compared to the backend (via classical ABAP Workbench)?

We discuss this currently as well in the DSAG-call related to the ABAP Development Tools together with thomasfiedler .

Kind regards
Jens

[abo]

Even more annoying is that it won't work on inactive objects, whereas in GUI it does (EDIT: wrong, see later). Granted, the results might not be accurate in that case, but it's a lot better than nothing most of the time.

[michael_gutfleisch]

> Even more annoying is that it won't work on inactive objects, whereas in GUI it does
That's not true. Where-used search in ADT is able to find references in inactive versions.

In general inactive versions of classes, programs and function modules for example are considered, while they are not considered for dictionary objects like structure, tables and cds views.In this sense, ADT and SE80 behave identically.

[abo]

If the objects are merely inactive, michael.gutfleisch is right: as jzaehringer noted, it is slower but eventually an answers comes.

If the objects are inactive and syntactically incorrect (I added a FIXME string in both files), then the fact that the previously active version had a functioning where-used list is not considered by ADT. To be absolutely fair, neither does SE80.

[MatthiasH]

This ultra slow performance happens to me as well (at least at the first time I execute the Where-Used list). In 7.54 systems as well as in 7.40 systems.

This is why I sometimes open a separate SAP GUI for a Where-Used search, which is really annoying.

[ThFiedler]

Hi Jens,

what is the main scenario where you face the slow performance of Where-Used?

Do you search for references of SAP Objects or custom objects?

Regards,

Thomas.

[Jeansy]

Hi Thomas,

this happens in both scenarios.

Kind regards
Jens