SAP best practices · LessonReviewed by Ravi M, SAP Trainer, 10 yrs · Updated · Published · SAP S/4HANA 2023 · all levels
SAP Naming standards
Consistent naming standards make objects findable, understandable and safe to work with, from custom programs to configuration keys.
Quick answer
SAP naming standards put every custom object in the Z or Y customer namespace, which upgrades never overwrite, use consistent prefixes such as lv_, ls_ and lt_ in ABAP and Z_ for views, name objects for their purpose rather than in cryptic abbreviations, give configuration keys meaningful values, and document the convention so the whole team applies it.
Key takeaways
- Watch out: a naming standard agreed after the first fifty objects exist is a migration, not a standard.
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.