Attila, S/4HANA, BTP Fullstack Developer (EN, DE, HU)

Where-Used-List update by package
Purpose
This tool updates the where-used-list for ABAP repository objects in a package.
It can process:
- single package
- package including all subpackages recursively
Use it when where-used information is missing, outdated and you do not want to run full system index. Handy for sandbox systems, local Docker ABAP Trial instances.
Supported Object Types, ABAP Code:
- CLAS
- INTF
- FUGR
- PROG
Option 1 – Report
Use when
- background processing is required, due volume
- you want to enter the package at runtime
- you want a simple executable tool
- you prefer a classic SAP GUI style entry point
Execute report ZSAPDEV_WULU_RUN.
Input Fields
- Package: technical package name to process
- Recursive: checkbox to include subpackages recursively
Execution Modes
- Recursive not selected Only the entered package is processed.
- Recursive selected The entered package and all subpackages are processed recursively.
Result
- Success message is shown.
Notes
- Recursive processing may take longer, depending on package size. Schedule a background job using the report.
Option 2 – ADT Class Runner Usage
Use when
- you work mainly in Eclipse / ADT
- you want quick online developer execution
- hard-coded input values are acceptable
Run class ZCL_SAPDEV_WULU_RUN in Eclipse / ADT as ABAP Console Application. (Windows Keyboard Shortcut: F9)
The runner uses constants inside the class:
- package name
- recursive mode flag
Before running, maintain these values in the source code.
Example
CONSTANTS package_name TYPE devclass VALUE 'SALV_DYNPRO'.
CONSTANTS recursive_processing TYPE abap_bool VALUE abap_false.This processes one package only.
If you set:
recursive_processing = abap_true
the runner processes the package hierarchy going down recursively.
Result
Installation
abapGit: https://github.com/attilaberencsi/abapwulu.git
Summary
This utility provides a simple way to refresh where-used information for ABAP package content.


