SAP Note 28022 - Customer system: Where-used list of SAP objects

Symptom:

1. The where-used list for SAP objects is incomplete in the customer system.

2. The supporting program list for an SAP include is incomplete.

Other terms

() EUNOTE, EUWORKBENCH, ES244

Reason and Prerequisites

In a customer system, you cannot be sure that the where-used list for SAP objects is complete. The where-used list is normally only set up for customer-specific objects and is updated incrementally (see Note 18023).

Solution
If required, the necessary index can also be created for the where-used list of SAP objects. To do this, you must start the report SAPRSEUB (in the background). Note that when you execute the report, you must have generated all programs. If necessary, start a mass generation in advance using transaction SGEN.
Also make sure that the job EU_INIT does not run in parallel.

Due to the size of the index, we recommend that you set up the index in development systems only.
In releases up to and including 46D, the report runs for about 6 to 7 hours. The additional memory required is approximately 100 MB.
A more detailed index is set up as of Basis Release 610; this makes it possible to find a global use of types in programs. This also includes uses of table fields and data elements. The additional memory required for this is 1 GB. The report has a very long runtime and can run up to 100 hours (5 days).

In general, the following applies: A new upgrade does not automatically update the index for the where-used list. You may have to start the report SAPRSEUB again.