SAP TCodes · LessonBy Arjun, SAP Solution Architect · Published · SAP S/4HANA 2023 · all levels
SE11
SE11 is the SAP transaction code for ABAP Dictionary (ABAP/Basis). It opens the ABAP Dictionary to view/maintain database tables, data elements, domains, views and other dictionary objects, the reference for SAP’s data structures.
Quick answer
SE11 opens the ABAP Dictionary to view/maintain database tables, data elements, domains, views and other dictionary objects, the reference for SAP’s data structures.
Key takeaways
- Object type (table, data element, domain, view).
- Table fields, data types, keys and indexes.
- Technical settings (buffering, size category).
- Watch out: Using the wrong variant (create vs change vs display).
Purpose
It opens the ABAP Dictionary to view/maintain database tables, data elements, domains, views and other dictionary objects, the reference for SAP’s data structures.
Key fields and screen
- Object type (table, data element, domain, view).
- Table fields, data types, keys and indexes.
- Technical settings (buffering, size category).
- Where-used and documentation.
Tips
- Use SE11 to understand a table’s structure before querying it.
- Follow a field to its data element and domain.
- Check indexes when troubleshooting query performance.
Common errors
- Editing dictionary objects without proper change management.
- Confusing transparent tables with pooled/cluster tables.
- Missing authorization to change dictionary objects.
Common pitfalls
- Using the wrong variant (create vs change vs display).
- Missing prerequisite master data or authorization.
- Not checking the resulting document/log.
Practice challenge
+0 XPStreak ×0
Question 1 of 2
Which statement is true of SE11?
Frequently asked questions
What does SE11 stand for in SAP?
SE11 is the SAP transaction code for ABAP Dictionary (ABAP/Basis). It opens the ABAP Dictionary to view/maintain database tables, data elements, domains, views and other dictionary objects, the reference for SAP’s data structures.
Which related transactions work alongside SE11?
Use SE11 to understand a table’s structure before querying it. Follow a field to its data element and domain. Check indexes when troubleshooting query performance.
What is worth remembering about SE11 in practice?
Object type (table, data element, domain, view). Table fields, data types, keys and indexes. Technical settings (buffering, size category).
What tends to go wrong with SE11?
Using the wrong variant (create vs change vs display). Missing prerequisite master data or authorization. Not checking the resulting document/log.