SAP TCodes · LessonReviewed by Anitha M, SAP Trainer, 13 yrs · Updated · Published · SAP S/4HANA 2023 · all levels
SAP SE38
SE38 is the SAP transaction code for ABAP Editor (ABAP). It opens the ABAP Editor to create, edit, run and analyse ABAP programs (reports), a core development transaction (alongside SE80 and modern ADT).
Quick answer
SE38 opens the ABAP Editor to create, edit, run and analyse ABAP programs (reports), a core development transaction (alongside SE80 and modern ADT).
Key takeaways
- Watch out: dialog work processes time out, so long reports belong in background.
Purpose
It opens the ABAP Editor to create, edit, run and analyse ABAP programs (reports), a core development transaction (alongside SE80 and modern ADT).
Key fields and screen
- Program name.
- Source code editor.
- Execute (F8), and variants for selection screens.
- Where-used, syntax check, and debugging entry.
Tips
- For modern development prefer ADT (Eclipse); SE38 remains common.
- Use the syntax check and extended check before running.
- Create variants for reports with selection screens.
Common errors
- Syntax errors on activation.
- Running resource-heavy reports online (use background).
- Editing standard SAP programs (modifications).
Common pitfalls
- Running online what belongs in background. The dialog work process has a time limit, and running it again after a timeout wastes the same time twice.
- Not saving a variant. Twenty selection fields retyped every run is both slow and a source of inconsistent results between people.
- Testing against development data volumes. A report that returns in seconds on two hundred rows behaves differently on two million, and nothing in the editor warns you.
- Editing a program somebody else has open. The lock exists for a reason, and overriding it loses work.
- Executing an unfamiliar Z program in production to see what it does. Read it first. Some of them post.