Skip to Content
Technical Articles

Simple Data Explorer

Recently I have to work not only with my native SAP HR. And there is a need to be aware of unfamiliar data models from other modules as soon as possible. I made a small application – Simple Data Explorer. It may be useful for consultants, architects, developers of all SAP systems with ABAP.

Basic capabilities:

Multiple windows – you can open as many tables as you need or as much as your monitor resolution allows. You can open the same table multiple times.

Each table has its own selection parameters. It opens, closes with arrows icons. All standard search tools are connected, including specials for table numbers and organizational management objects.

Reactivity – update data as soon as you press Enter, select a function or select multiple data. You do not need to take a step back and lose context to change the selection conditions.

There is a lot of information in SAP, so the empty columns are hidden by default. You can display them if you like. Comparison of visual size of the same table.


Multilingualism. All languages installed in the system are supported. Column and table names are translated into the selected language. In addition, you can select technical field names as headings.


Graphical visualization of table links as in SE11 transaction.


To speed up the writing of technical tasks, the information about the fields from Data Dictionary is displayed. The SE11 transaction will be opened by clicking on it.


Double click on the selection field will open the standard help.


If you need to quickly track the relationships of several tables, you can select the entire column with the data of one table and drag it to the selection field of another table. The data in the source table columns are turned into buttons. In the receiver table, an inheritance indicator appears next to the column. In this way, you can revive a data model from several tables in just a minute.


Double click on all fields (blue link) will open a reference table with the contents by external key. The green links imply special processing:

Double click on the personnel number will open the PA30 transaction.

Double click on the organizational management object will open the PP02 transaction.

From table PA0001 you can go to HRP1000 by clicking on Org.Units, positions or jobs.

In the HRP1001, a double click on a linked object will automatically select it in the search parameters, allowing you to navigate through all internal objects links.

Links to additional information on connecting objects in Organizational Management, as well as HRP1002 – HRT1002 connection are supported.

It supports drag & drop. You can drag one or more selected values from the table contents to the selection options of any table.

Easy installation. Source in one file. You have to create a program in SE38 or SE80 transaction, copy the code, activate and Run it. I hope it is really сonvenient and easy to use data tool.

Abap 7.50 version

Abap 7.02 version

Detailed description in Russian


Payroll Clusters view added from table HRPY_RGDIR

You must be Logged on to comment or reply to a post.
  • Good stuff, looks like a great productivity tool that makes many tasks I preform quite frequently simpler and more efficient!




  • Yurij Sichov

    Hi Yurij,

    thanks for making what looks like a neat tool available for us! I already put it into a NW750 sandbox-system (with SP16 & EHP8) to see how it works. Unfortunately, I get a somewhat weird dump:

    I don’t quite get why e_ucomm – which contains “HIDE” is checked against the language (“H” then)?

    From the HEX format, it looks okay, and the CASE-Statement a bit earlier in the code gets carried out properly, so it doesn’t seem to be an issue where a letter in the literal ‘HIDE’ looks correct but is actually a cyrillic version of the Latin one (like the “trick” played in the ABAP code challenge recently):

    Any ideas what might be causing this and how to fix it?

    Thanks much and Cheers



    • Hi Barbel. Thanks for testing and sorry for the error.

      The language code automatically enters the e_ucomm. The field ‘SPRAS’ was 1 byte long and therefore e_ucomm was converted to 1 byte. So ‘H’  = ‘Hide’. Repaired.


  • Hi Yuri,


    very nice, Thanks.

    Any chance that you provide a proper abapGit repo? It would make installation a bit easier and people could participate and create pull requests for your project.