SAP ABAP Data Element DMC_DEVCLASS (Package (development class))
Hierarchy
☛ DMIS (Software Component) DMIS 2011_1
   ⤷ CA-EUR (Application Component) European Monetary Union: Euro
     ⤷ CNV_DMC_UTIL (Package) Data Mapping and Conversion: Utilities
Basic Data
Data Element DMC_DEVCLASS
Short Description Package (development class)  
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

If you here keep the default $TMP, that means, that the objects that are being created (e.g. in the course of a copy) are not assigned to a real package (development class) and therefore will not be transported to another system.

If you want your objects to be transported to another system (included in a transport request), assign a real package to these objects, along with a transport request number.

Find below the SAP standard definition for packages:

Related objects in the ABAP Workbench are grouped together in a package. The assignment of an object to a package is entered in the object directory (TADIR). The package determines the transport layer that defines the transport attributes of an object.

The packages are entered in the table TDEVC. They can be maintained in the following transactions:

  • Transaction SE80 -> Enter package -> Double-click the package
  • Transaction SM30 - Table/view name V_TDEVC

The packages are themselves objects of the ABAP Workbench. They belong to their own packages.

In contrast to its predecessor, the development class, a package has the following additional characteristics:

  • Packages can be nested.
  • Packages can contain their 'visible development objects' (visible outside of the package) in package interfaces.
  • Packages can have use access defined for other package interfaces.

Use

When an ABAP Workbench object is created, the system prompts you to assign it to a package. The package should describe the area that the object belongs to.

The representation of the object tree in the ABAP Workbench (transaction SE80) uses the package as a navigation aid. If there are more than 100 objects of a certain type (that is, ABAP programs), the object tree can no longer be clearly represented and it becomes increasingly difficult to use the ABAP Workbench. In this case, we recommend creating new packages with the same transport layer and distributing the objects to the new packages on the basis of the areas they belong to.

The following naming conventions for packages determine the packages' functions:

  • Package begins with A-S or U-X:
    These packages are for SAP standard objects. Customer objects cannot be created in them. Changes to objects of these packages are recorded by the Transport Organizer (Request management) and can be transported (see field transport layer.

  • Package begins with Y or Z:
    Customer objects can be created in these packages. Changes to objects in these packages are recorded by the Transport Organizer (Request management). The objects can be transported to other SAP Systems (see the field transport layer ).

  • Package begins with T (private test package):
    When you create a package of this type, you can specify whether you want changes to be recorded. If so, objects that are edited are recorded in local requests by the Transport Organizer. This package does not belong to a transport layer. Objects can only be transported to other SAP Systems if a transport request is created.

  • Package begins with $ (local package):
    Changes to objects are not recorded by the Transport Organizer. The package does not belong to a transport layer. The objects cannot be transported.

  • Package begins with a namespace prefix:
    If you have reserved a namespace, then you can create packages (and other objects) whose names begin with the namespace prefix.
    (Example of a namespace prefix /COMPANY/, example of a corresponding package /COMPANY/DEVCLASS)
    Changes to these packages are recorded by the Transport Organizer, and can be transported.

Procedure

Examples

Dependencies

History
Last changed by/on SAP  20141029 
SAP Release Created in 620