Warum wir es brauchen
Jedes Projekt hinterlässt einen Friedhof kleiner Z-Tabellen.
In jedem langlaufenden SAP-Projekt fügt jeder Change Request ein weiteres kleines Customizing-Objekt hinzu — einen Schalter, eine Werteliste, eine einzelne Konstante — und die meisten werden still zu Waisen, an die sich in sechs Monaten niemand mehr erinnert.
-
Dozens of custom
Z*/Y*tables get created as configuration for individual customer programs — each in its own DDIC namespace, each with its own SM30 view. - Most of them hold one or two rows. A whole transparent table for a single boolean flag or a tiny value list — overkill, but the pattern keeps repeating.
-
They get lost in the documentation.
After a year, nobody can tell what
Z_OLD_CONST_47is for, who owns it, or whether it's still used. - Hardcoded constants live inside the source. Changing a single digit means a development ticket, a transport, and a release — for what is functionally just a configuration value.
- No way to ask "where is this used?" A value lives in a Z-table, but the program that reads it is on the other side of the system — and finding callers means a manual code search every time.