Show TOC

Object Name CategoriesLocate this document in the navigation structure

Use

The object name categories for the name prefixes are implemented as CIM classes (see Common Information Modell ). The global uniqueness of prefixes is guaranteed by using Internet domains or by using a prefix that has been reserved at SAP.

You reserve a prefix globally on SAP Service Marketplace at http://s ervice.sap.com/namespaces (see SAP Note 105132). The syntax for a prefix that is reserved globally on SAP Service Marketplace is a string of three to eight characters, which are enclosed between slashes (/).

This section describes all object name categories that are available and their syntax rules. The syntax rules are important when you define a new name prefix (see Defining Name Prefixes for Development) .

Object Name Categories and Syntax Rules for Non-ABAP Objects

Object Name Category

Usage

Prefix Naming Convention

Syntax Rules

Application Context Root

Names of Java EE applications. Defines the first path component in the URLs of the application.

x

Hierarchical name in lowercase as a first name component separated by a slash (/). For example, x/... .

DB Field Name

Field names of any database (DB) tables. Developers of different DB tables can reuse field names. Name prefixes can be separated according to vendor in this category.

X_*

The prefix must have a trailing asterisk (*) to allow more than one single name. In front of the asterisk (*), you have to insert an underscore (_) to separate the name prefixes. Any string of uppercase letters and digits may be inserted in front of the underscore (_) and the asterisk (*). The minimum length is 1. For example, X_* . Do not insert an underscore (_) in the prefix string as this will be ambiguous.

DB Object Name

Names of DB tables and DB indexes.

X_*

See above.

DB Pool Name

Names of DB pool aliases. These aliases are used by Java EE applications to refer to a DB connection, including the physical DB, the DB schema, and access rights.

X/P_*

The prefix must have a trailing asterisk (*) to allow more than one single name. In front of the asterisk (*), you have to insert an underscore (_) to separate the name prefixes. Any string of uppercase letters, digits, and a slash (/) may be inserted in front of the underscore (_) and the asterisk (*). The minimum length is 1. For example, X/P_* . Do not insert an underscore (_) in the prefix string as this will be ambiguous.

Design Time Package

Names of Java packages.

<rid>

Reverse Internet domain (rid). For example, sap.com is the normal Internet domain and the reverse is com.sap .

Development Component Name

Names of the smallest reusable software bundles (development components).

<id>

Internet domain (id). Hierarchical name separated by a slash (/). The file path in the Design Time Repository (DTR) is preceded by a vendor path that belongs to the development component name. The vendor path at SAP is sap.com . For example, sap.com/* .

Installation Unit Name

Names that identify any type of installation unit (executable, dynamically linked library, archive, VB module, and so on). The type is designed mainly for file system elements but not necessarily restricted to them. To avoid name reservation conflicts, do not assign the same name to elements of different types.

X_*

See above.

Software Component Name

Names of the smallest shipped software bundles. These bundles contain many development components.

<id>

Software components that have sources in the DTR have to follow the same naming rules as for development components. For example, sap.com/* .