Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CTS-ORG (Application Component) Transport Organizer⤷
SCTS_CAT (Package) CTS: Object Directory & Packages
Basic Data
| Data Element | DEVCLASS |
| 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
Objects of the ABAP Workbench that belong together are contained in a package. The assignment of an object to a package is recorded in the object directory (TADIR). The transport layer of the package specifies the transport attributes of the object.
The table TDEVC contains the description of the packages. The packages can be edited by using the following transactions:
- Transaction SE80 - enter package - double-click the package
- Transaction SM30 - table/view V_TDEVC
Packages are also objects in ABAP Workbench. They are always the packages of themselves.
Unlike their predecessors, the development classes, packages have the following additional features:
- Packages can be nested.
- In package interfaces, packages can contain visible development objects of the package.
- Packages can provide use access to package interfaces of other packages.
Use
When creating a new object in ABAP Workbench, a dialog box appears in which you must assign the object to an existing package. The package describes the work area of the object.
The package can also be used as a navigation criterion for displaying the object tree in ABAP Workbench (transaction SE80).
If there are many objects of one object type (such as ABAP programs) in the same package, the display of the object tree becomes very complex and it becomes difficult to use ABAP Workbench. We recommend that you create new packages with the same transport layer and distribute the objects to the packages according to the subject matter.
The following naming conventions apply for packages and specify the functional characteristics of the package:
- Packages starting with A-S or U-X:
These packages are reserved for objects from the standard SAP system. User-defined objects cannot be created in these packages. Any modifications made to objects of these packages are recorded by the Transport Organizer and can be transported (see the field Transport Layer)
- Packages starting with Y or Z:
User-defined objects can be created in these packages. Any modifications made to the objects of the packages are recorded by the Transport Organizer. These objects can be transported to other SAP systems (see the field Transport Layer).
- Packages starting with TEST (local packages):
When creating these packages, you can decide whether or not change recording is turned on. In this case, objects are recorded by the Transport Organizer in local requests when edited.
This package does not belong to a transport layer. The transport of these objects is only possible if a transport request into other SAP systems is created.
- Packages starting with $ (local packages):
Modifications to the objects of these packages are not recorded by the Transport Organizer. The package does not belong to a transport layer. The objects cannot be transported.
- Packages starting with a namespace prefix:
If you reserved a namespace, you can use it to create packages (and other objects) that have names starting with the namespace prefix.
(Example of a namespace prefix: /COMPANY/; example of the corresponding package: /COMPANY/DEVCLASS)
Modifications to objects of these packages are recorded by the Transport Organizer and they can be transported.
Procedure
Examples
Dependencies
Supplementary Documentation - DEVCLASS 0000
Use
Development class for which the evaluation is to be made.
Procedure
Examples
Dependencies
Supplementary Documentation - DEVCLASS 0001
Use
Selection by development class
Procedure
In the field Development class, enter the development class for which you wish to generate statistics. Generic entries ("*", right-justified) are allowed.
If you wish to generate the statistics online, you may only enter the character "*" in the third or fourth position.
If you want to enter the character "*" in the first or second position, please create a variant for the program and run this variant in the background.
Entry of a range
If you want to analyze a range of development classes rather than making a generic analysis, enter the lower limit of the range in the field Development class and the upper limit in the field To development class.
In this case, a generic entry is not possible.
Examples
Dependencies
Supplementary Documentation - DEVCLASS 0002
Use
Indicates which development class is to be analyzed.
Procedure
Enter a development class. Generic entry ("*", right-justified) is possible from the third position if you are carrying out analysis online. If you want to perform a generic analysis with "*" in the first or second position, create a variant and start it in the background.
Examples
Dependencies
Supplementary Documentation - DEVCLASS 0022
Use
s
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in |
