(Called Development Classes in pre 4.6 versions)

Packages are the successors to Development classes in older versions. They are closer to alignment with UML packages. Packages are containers used to collect all development types and classify them as to their purpose. Packages should describe the functions within a project.
There are some restrictions imposed by SAP itself as follows:
  • SAP Standard object use Package names starting with A-S or U-X. Customer objects cannot be added to these Packages.
  • Custom developed, permanent, objects use package names starting Y or Z.
  • Like other repository objects, packages can belong to a prefix namespace if the relevant namespace is installed in your R/3 system. Packages begin with a namespace prefix enclosed in slashes(/). In a package of this type you can only create object that belong to the same prefix namespace.
  • Package names can be up to 30 characters long.
Note packages can be nested thus allowing a fair amount of classification. In the example above within the BestPractices Init project could be further packaged into Finance, Logistics etc.

Suggested Naming Standard


Package Name <Prefix><Application Area><Separator><Description>

Z,Y or namespace

Normal customer developed objects should be prefixed with Z. Y should only be used when a object is local and will not be transported. When a namespace is involved that would be used as a prefix. i.e. "/Prefix/FIDEV"

Application Area FI,PP.MM etc.

Functional Application Area, Note it is typical to use SAP's Application Areas but others work as well.

Seperator  "_" use an underscore

Description of package data / Project












A custom package for development of a finance initiative.
A package being used for local development that will not be transported. (Note we do not recommend the use of the Y prefix, rarely is there a need for a local object.
A package being developed in a custom namespace for the Acme company
Note when using a custom namespace the Z or Y prefix is no longer needed.
Go To Top