Skip to content
IT Canvass
Menu
ServiceNow
SailPoint
SAP
TutorialsContact
SAP best practices · Lesson

Naming standards

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.

Want to learn this properly?

Our live, instructor-led SAP Training covers this hands-on, with real projects and a certification path.

See the courseAsk a question

Check your understanding

  1. Which statement is true of Naming standards?

    • A. It is a small discipline with a big maintainability payoff.
    • B. Returns processing in SD handles goods coming back from customers, return orders, return deliveries, and…
    • C. NetWeaver release notes cover the classic application-server platform underpinning many SAP products (ECC…
    Show answer

    A. It is a small discipline with a big maintainability payoff.

    Covered in the “Why it matters” section of this lesson.

  2. Which of these also applies to Naming standards?

    • A. Using float (f) for money, use packed/currency types.
    • B. Standardise configuration keys (org units, document types) meaningfully.
    • C. Learning features, not the end-to-end process.
    Show answer

    B. Standardise configuration keys (org units, document types) meaningfully.

    Covered in the “Key practices” section of this lesson.

  3. Which part of the Learn SAP curriculum covers Naming standards?

    • A. SAP troubleshooting
    • B. SAP how-to guides
    • C. SAP best practices
    Show answer

    C. SAP best practices

    This lesson sits in the SAP best practices section of the Learn SAP course.

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.
CallWhatsAppEnquire