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.