SE93 — Maintain Transaction Codes

SE93 defines and edits the entry that lets someone type a short string into the command field and land on a specific screen. The tcode itself contains no logic; it is a row pointing to a program and screen number, a report program, a BOR object method, or to another transaction with fixed parameter values layered on top (a parameter transaction or a variant transaction). The structural fact that causes most confusion: one program can be reached by several different tcodes, each with different default values, different skipped initial screens, or different attached authorization objects. Two people debugging the 'same' tcode can be looking at different behaviour entirely because the tcode, not the program, carries the authorization object and the parameter defaults.

Used whenever a custom report or dialog program needs a callable entry point, and whenever someone needs to find out what a tcode actually executes before touching the underlying program. Common uses: creating a tcode for a new Z-report, creating a parameter transaction that opens an existing transaction with a screen skipped and a value defaulted, checking which authorization object a standard or custom tcode carries by default, and comparing a customer-copied tcode against the SAP original to see what was changed. Consultants reach for SE93 specifically to inspect or build the tcode object; for editing the program behind it they go to SE38 or SE80, and for a Fiori-based process there is usually no tcode involved at all on the front end.

In SE16 on TSTC, filter on TCODE to confirm PGMNA (program) and DYPNO (screen) match what is expected; a blank or unexpected program name confirms a mapping problem rather than a program bug. Check TSTCT for the same TCODE to confirm the description matches what users see. If the symptom involves a wrong default value or a skipped screen, check TSTCP for that TCODE and read the parameter ID and value fields. Cross-reference TADIR with PGMID equal to R3TR and OBJECT equal to TRAN, OBJ_NAME equal to the tcode, to confirm it exists in a transportable package rather than sitting locally.

SE93 is unchanged on S/4HANA and continues to govern classic dialog and report transactions, including wrapper transactions built for compatibility or batch input use. Fiori apps are not tcodes and are not maintained here; the mapping from a launchpad tile to its backend service lives in the Fiori Launchpad configuration, separate from anything SE93 controls, even when a Fiori app internally still calls a classic transaction.

Development team problem: the developer creating the report or dialog program owns the SE93 entry for it. Basis owns transport movement and transaction locking. Functional consultants care about the authorization object assigned, since it drives role design. A clean handover states the tcode name, its type, the transport request it travelled in, and the authorization object attached, if any.

SE80 is the broader development workbench and shows the same tcode information alongside the program and screens it points to, useful for seeing the whole object in one place. SE41 is where the underlying menu and screen layout for a dialog transaction is built, relevant when the tcode calls a custom screen. SE54 generates maintenance-view transactions automatically, producing SE93 entries as a byproduct, useful to understand when troubleshooting a generated maintenance tcode. SE09 covers the transport organizer, relevant whenever a tcode created in one system needs to be confirmed as correctly transported to another. SE91 covers message classes, relevant when a tcode call raises a specific error message that needs tracing back to its source.