Naming Conventions in ABAP: Short Guide

A naming convention specifies the set of rules used to identify development objects. SAP plays a role in the setting of the rules insofar it enforces its own recommendations. (See the following the section called Customer Name Space ID). In the ABAP environment the non-reserved aspect of a custom repository object name (and the names of any custom internal components) are arbitrary. The overall responsibility for the enforcement of the naming conventions lies with the individual developers.

What is prescribed in the following sections ensures: (1) a distinction between SAP standard code, partner code, and customer code and (2) meaningful names for custom developed objects that promote ease-of-identification.

As part of the delivery process Code Inspector (Transaction code “SCII”) will be used to check whether programs adhere to naming conventions or not. (A Global Variant will be created called ‘SSC_DEFAULT’ to aid the developers.

Customer Name Space ID

Name space identification is the means SAP uses to segment development objects in the repository. SAP has reserved name ranges for customer objects and SAP objects. SAP reserves the “Z” and “Y” repository name spaces for its customers that ensure that objects created in this space are preserved from patching and upgrades. Companies adopt the policy of naming test-related objects in the “Y” name space and Production-related objects in the “Z” namespace in general. The customer name space identifier always occupies the first character in the name of a custom development.
Beware that SAP does deliver a few system objects with names that fall within the customer name space. These objects are listed in table TDKZ.

Process Area/Application ID

The process area/application ID identifies the relevant business domain for custom development. It is represented by a two character code which logically groups related development objects together.