Show TOC

 Naming Conventions for PackagesLocate this document in the navigation structure

General recommendations

  • Do not use technical concepts like original system, release, and so on
  • Identifiers in names should be carefully chosen so that they do not become obsolete quickly. Do not include attributes that could change in the near future
  • Names should be made up of English identifiers.

Packages

The following namespaces are available for packages:

Package names beginning with a letter from A to S, or from U to X.

Package names beginning with these letters are reserved for objects of the SAP standard system from the SAP namespace. You cannot create customer objects or objects from prefix namespaces in these packages.

Note that the package name must be no more than 30 characters long. The name of the main package should reflect the content of the package Adjacent packages should have similar names.

The Transport Organizer records changes to objects in these packages, so that they can be transported. These packages belong to the "SAP" transport layer and are assigned to an SAP software component (such as SAP_BASIS, SAP_APPL).

Package names beginning with Y or Z

You can create customer-specific objects from the customer namespace in these packages. The Transport Organizer records changes to objects in these packages, so that they can be transported, provided the SAP System has been set up appropriately. (For more information, see Setting the System Change Option ).

These packages are assigned to the software component HOME.

Package names beginning with T (private test packages)

These packages allow you to create objects for customers, from the customer namespace, or object from the prefix namespace (which is installed in your SAP System with the role "producer"). See also Releasing Namespaces .

When you create a private test package, specify whether or not you want to link it to the Transport Organizer. If you do, the objects that the Transport Organizer processes are recorded in local requests that are not transported. This package does not belong to a transport layer.

Objects in these packages can only be transported to other SAP Systems using a special transport request (transports of copies, or relocation transports).

Newly installed SAP Systems contain a private test package, TEST, which is not connected to the Transport Organizer.

These packages are assigned to the software component LOCAL.

Package names beginning with $ (local packages)

These packages allow you to create objects for customers, from the customer namespace, or object from the prefix namespace (which is installed in your SAP System with the role "producer"). See also Releasing Namespaces .

The Transport Organizer does not record changes to objects in these packages. These packages do not belong to a transport layer, so the object cannot be transported.

Newly installed SAP Systems contain a local package, $TMP.

Packages belong to a prefix namespace.

Like other Repository Objects, packages can belong to a prefix namespace, provided the appropriate namespace is installed in your SAP System.

The prefix namespace affects packages as follows:

  • The package name begins with a namespace prefix, enclosed in slashes (/).

  • You can create customer-specific objects from the customer namespace in these packages. The Transport Organizer records changes to objects in these packages, so that they can be transported, provided the SAP System has been set up appropriately.

Packages Interfaces

  • Each interface name must be unique. This means that, if you want to use several interfaces to extend visibility over several levels, you must use a different name at each level.

  • The interface name should clarify whether the interface is functional or descriptive.