Define Naming Standards
Use
The purpose of this task is to define the naming standards to avoid naming conflicts in a distributed development environment or caused by the combination of several applications in one system (delivery, installation, upgrade). Name clashes between SAP Repository objects and objects in the common customer name range are avoided by development workbench checks.
SAP Note 16466 delivers an overview of all of the current naming convention for Repository objects in the common customer name range (normally a Y or Z at the beginning of the name).
The following scenarios can lead to naming conflicts and must be managed by administrative measures:
In development scenarios with more than one development system, naming conflicts can occur between customer Repository objects of the different development systems, for example, with a global template and local developments. Customers can prevent this by reserving naming conventions for development areas within the customer name range. The Workbench Organizer uses the entries in view V_TRESN to ensure that the development follows the defined naming conventions. The naming conventions must be defined centrally and distributed to all development systems.
In the case of a distribution of the development among a global and several local places, where a central coordination of the naming conventions is not possible, it is recommended that you reserve and use a development namespace for the global application parts, and use the common customer name range for the local development.
Naming conflicts that occur (e.g. when loading Complementary Software from SAP partners into an SAP standard system) can be solved only by reserving development namespaces in the SAP Online Service System. To do this, the SAP partner can apply for a name prefix in the SAP Online Service System that is then used in the names all of that partners’ Repository objects.
Development namespaces can be reserved from SAP Release 4.0 on. However, certain requirements must be fulfilled to receive a development namespace (see below).
Procedure
Consider the use of a development namespace.
Development namespaces should be considered in two cases:
You must have an ABAP/4 Development Workbench license for the customer number under which you request a reservation.
SAP only issues namespaces that contain a recognizable reference to the customer’s or partner’s company or product name.
Each corporate enterprise or development partner receives one namespace only.
A formal namespace agreement must be signed and returned to SAP.
Beside these criteria, development namespaces are not designed for:
It includes creating, changing and status monitoring of namespaces and the registration on individual installations.
For details about the process, read SAP Notes 84282 and 105132. An overview about development namespaces can be found in the white paper Development Namespaces for SAP Release 4.0.
Naming conventions apply in cases of distributed development. They do not apply if the development is made in only one development system.
To avoid naming conflicts, you must define a standard generic naming convention (that is, determine the beginning of the object name) for all objects of a development class. If you store this specification in all development systems (enter using extended table maintenance in table V_TRESN, see online documentation on the Workbench Organizer), the development workbench prevents use of the convention by other projects, that is, assignment to other development classes is refused.
Note that naming conventions may apply in a development namespace as well.
Result
Naming convention for customer Repository objects
Also refer to the following documentation: