When the development is being carried out by a reserved namespace within a Development Workbench few of the symptoms are occurring.
The Object editor is not accepting namespace as prefix in object name.
Usage of object names with namespace as prefix is causing an errors.
With the release of 4th version it becomes possible for reversing the personal namespace of the developments that are being delivered for the independent third parties. The name that is conflicting that is avoided with delivery provides the following reasons:
The object types are not capable for supporting the namespaces.
Tools that are being used not enough for converting the object names with namespace for prefix.
The concept for the development regarding the namespace came into existence with the release of 4.0. The Restrictions having the namespace for development can become intentional. In other cases the results for development of the tools become incorrect for the namespace concept.
The object types in which the concepts for the development applies a namespace:
All types of the central ABAP of Repository objects are enough to support the namespace.
The Client-specific objective types, the objective types which can't be transported, and the objects having the catalog entries that are incapable for supporting have the following reasons:
The Client concept is allowing for the protection for a customer and for client dependent objects only by storing the data in another file.
The local objects that have restriction to be transported, these objects do not need namespace protection. The reason for this is that they are not having any kind of danger of being overwritten.
Those object types that are not been listed in object directory cannot be transported. They are either client specific or having the sub-objects for the directory capable objects.
The exception is there that the table fields are supporting the namespaces.
Examples:
The Lock object uses regular naming convention type /<prefix>/*, but the SAP recommends in using /<prefix>/E* -
The help view follows regular name convention type of /<prefix>/*, where /<prefix>/H_* is option that can be used.
The including names are:
<prefix>/SAPL* or /<prefix>/L* for function group of name /<prefix>/*.
/<prefix>/SAPDB* or /<prefix>/DB* for logical database of name /<prefix>/*.
/<prefix>/SAPM* or /<prefix>/M* for module pools.
Function modules use /<prefix>/ is optional.
BAPI structures and BAPI function modules are subjected for name convention /<prefix>/*.