In the result list of the where-used list, you can display source code in different ways. In addition to the immediate display of a strictly limited part (for example, a line of ABAP code), you can extend this part by expanding it, and you can then view it in its context. However, from the result list of a where-used list, you can also go to display mode or change mode for a hit. This takes you to the relevant processing tool for the workbench object. These tools also often have separate transaction codes. In many cases, you can access them only using the Object Navigator (transaction SE80).

Therefore, the authorization to execute transaction SE80 is of central importance for the assignment to developer profiles.

Even before calling the where-used list, both when directly calling it in transaction SE84 and when calling it from other transactions (for example, transaction SE16N), the system therefore checks
whether an authorization to start the Object Navigator (transaction SE80) is assigned to your user profile.