SAP best practices · LessonBy Ravi M, SAP Trainer, 10 yrs · Published · SAP S/4HANA 2023 · all levels
Naming standards
Consistent naming standards make objects findable, understandable and safe to work with, from custom programs to configuration keys.
Quick answer
Good naming prevents clashes with SAP standard (customer namespace is protected from being overwritten in upgrades), makes objects self-describing, and keeps a large landscape navigable.
Key takeaways
- Use the customer namespace (Z/Y, or a registered namespace) for all custom objects.
- Adopt consistent prefixes/conventions (e.g. lv_/ls_/lt_ in ABAP; Z_ views).
- Name objects for their purpose, not cryptic abbreviations.
- Watch out: Skipping the discipline under delivery pressure.
Key practices
- Use the customer namespace (Z/Y, or a registered namespace) for all custom objects.
- Adopt consistent prefixes/conventions (e.g. lv_/ls_/lt_ in ABAP; Z_ views).
- Name objects for their purpose, not cryptic abbreviations.
- Standardise configuration keys (org units, document types) meaningfully.
- Document and enforce the naming convention across the team.
Why it matters
Good naming prevents clashes with SAP standard (customer namespace is protected from being overwritten in upgrades), makes objects self-describing, and keeps a large landscape navigable. It is a small discipline with a big maintainability payoff.
Common pitfalls
- Skipping the discipline under delivery pressure.
- Not documenting decisions.
- Ignoring the clean-core principle.
Practice challenge
+0 XPStreak ×0
Question 1 of 3
Which statement is true of Naming standards?
Frequently asked questions
What does the term Naming standards refer to in SAP?
Consistent naming standards make objects findable, understandable and safe to work with, from custom programs to configuration keys.
What is the practical takeaway on Naming standards?
Good naming prevents clashes with SAP standard (customer namespace is protected from being overwritten in upgrades), makes objects self-describing, and keeps a large landscape navigable.
What is worth remembering about Naming standards in practice?
Use the customer namespace (Z/Y, or a registered namespace) for all custom objects. Adopt consistent prefixes/conventions (e.g. lv_/ls_/lt_ in ABAP; Z_ views). Name objects for their purpose, not cryptic abbreviations.
What tends to go wrong with Naming standards?
Skipping the discipline under delivery pressure. Not documenting decisions. Ignoring the clean-core principle.