Skip to Content
Author's profile photo Nicolas Busson

Tip n°1: how to “fix” the where-used-list


The “where-used-list” is supposed to tell you where an object (structure, table, function module, you name it) is being used in SAP. But you may have noticed that most of the time the results are not really accurate for SAP standard objects:


This is indeed the intended behavior 😉 because this functionality is based on index tables that are delivered almost empty by SAP to avoid unnecessary data load in production systems. But you may want to start program SAPRSEUB to fill up those index tables completely in your development system… and the where-used-list will work fine for SAP standard objects too!

To get more information

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

Note 18023 – Jobs EU_INIT, EU_REORG, EU_PUT

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Martin Steinberg
      Martin Steinberg

      Hi Nicolas,

      thank you for sharing this notes. We started the report today, let's see how long it takes (in the note they talk about five days...).

      Best regards,


      Author's profile photo Nicolas Busson
      Nicolas Busson
      Blog Post Author

      Hi Martin,

      On SAP Netweaver ABAP 7.02 SCN Trial edition running on my laptop it was pretty fast (less than 6 hours if I remember well). But as I'm asking our basis team to run this report each time we install a new dev system, I can't tell you how long it takes to complete on a "real" SAP system. But for sure it's worth the extra disk space required 🙂



      Author's profile photo Luís Pérez Grau
      Luís Pérez Grau

      I just schedule the Job, I will keep this updated, but I can advance  there's a very nice note which improves the performance:

      1917231 - Runtime improvement for where-used list; job EU_INIT, table WBCROSSGT

      Let's see how it goes 😉

      Author's profile photo Nicolas Busson
      Nicolas Busson
      Blog Post Author

      Thanks a lot for the tip! I've just implemented this note to see how it goes...



      Author's profile photo Luís Pérez Grau
      Luís Pérez Grau

      Finished! In my dev system it took 1,5 days (CRM 7.0 Ehp2 SP Basis 5 SP CRM 4) I must say is a brand new system with few Z developments (Between 100 and 300).

      Another Point I would add is once the report is finished you must ask to Basis guys to launch stadistics on table WBCROSSGT, otherwise when you activate new objects you can have serious performance problems even time out dumps befor the object can been even activated.

      Author's profile photo Andrei Vishnevsky
      Andrei Vishnevsky

      This blog post made my life easier in SAP CRM long back ago. Thank you Nick!

      I just want to mention here another note in case any of readers running the system on MS SQL database. The note is 1554667 - Where-used list: Index creation performance in MSSQL.