SAP ABAP Data Element HRNAMESPACE_DEVCL (Package)
Hierarchy
☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-BMT-OM-GRF (Application Component) Structural Graphics
     ⤷ SP0U (Package) HR: Basis General Tools
Basic Data
Data Element HRNAMESPACE_DEVCL
Short Description Package  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type DEVCLASS    
Data Type CHAR   Character String 
Length 30    
Decimal Places 0    
Output Length 30    
Value Table TDEVC    
Further Characteristics
Search Help: Name DEVCLASS    
Search Help: Parameters DEVCLASS   
Parameter ID DVC  
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Package 
Medium 15 Package 
Long 20 Package 
Heading 8 Package 
Documentation

Definition

ABAP Workbench objects that logically belong together are grouped together in a package. The assignment of an object to a package is stored in the Object Directory (TADIR). The package determines the transport properties of the object based on the transport layer.

The package description is stored in table TDEVC. You can maintain packages in the following transactions:

  • Transaction SE80 - Enter package - double-click on package
  • Transaction SM30 - Table/View V_TDEVC

Packages are ABAP Workbench objects and, as such, always include themselves as a package.

In contrast to their predecessors, development classes, packages also have the following additional properties:

  • Packages can be encapsulated
  • Packages can include visible development objects of the package in package interfaces
  • Packages can include use access for the package interfaces of other packages

Use

When you create a new object in the ABAP Workbench, an input window is displayed in which you must assign the object to an existing package. The package should describe the application area to which the object belongs.

The package acts as a navigation criterion when the object hierarchy is displayed in the ABAP Workbench (transaction SE80).
If a particular package contains a high number of objects of the same type (such as ABAP programs), the object hierarchy is no longer easy to read and this makes it more difficult to work with the ABAP Workbench. If this is the case, SAP recommends you create new packages with the same transport layer and redistribute the objects according to thematic criteria to the new packages.

The following naming conventions exist for packages that determine the functional properties of the package:

  • Package starts with A-S or U-X:
    These packages are for standard SAP objects only. Customer-specific objects cannot be created in these packages. Modifications made to the objects in these packages are recorded by the Transport Organizer and can be transported (see field Transport Layer)

  • Package starts with Y or Z:
    Customer-specific objects can be created in these packages. Changes made to the objects in these packages are recorded by the Transport Organizer. The objects can be transported to other SAP systems (see field Transport Layer)

  • Package starts with TEST (private package):
    When you create this package, you can define whether change recording is to be activated. If you activate it, the Transport Organizer saves the objects in local requests during processing.
    This package does not belong to a transport layer. If you want to transport the objects in this package to other SAP systems, you must create a transport request.

  • Package starts with $ (local package):
    The Transport Organizer does not record changes made to the objects in this package. The package does not belong to a transport layer. You cannot transport the package.

  • Package starts with namespace prefix:
    If you have reserved a namespace, you can create packages (and other objects) that have names starting with the namespace prefix.
    (Example of namespace prefix /COMPANY/, example of package belonging to namespace /COMPANY/DEVCLASS)
    The Transport Organizer records changes made to these objects and they can be transported.

Procedure

Examples

Dependencies

History
Last changed by/on SAP  20041216 
SAP Release Created in 700