Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-TWB-TST-ECA (Application Component) eCATT Extended Computer Aided Test Tool⤷
SECATT_DDIC (Package) eCATT ABAP Dictionary Objects
Basic Data
| Data Element | ETIDEVCLAS |
| Short Description | Target Package by User Entry |
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 | Trg.Packge |
| Medium | 15 | Target Package |
| Long | 25 | Target Package of User |
| Heading | 20 | Target Package |
Documentation
Definition
Objects of the ABAP Workbench that belong together are merged in a package. The assignment of an object to the package is recorded in an object catalog (TADIR). The Transport Layer of the packacke specifies the transport attributes of the object.
The TDEVIC table contains the description of the packages. The packages can be maintained by using the following transactions:
- Transaction SE80 - enter package - doubleclick the package
- Transaction SM30 - table/view V_TDEVC
Packages are also objects of the ABAP Workbench. They are always the packages of themselves.
In contrast to their predecessors, the development classes, the 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 of the ABAP Workbench, an input window 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 object tree in the ABAP Workbench (transaction SE80).
If there are many objects of one object type - e.g. ABAP programs - in one package, the display of the object tree becomes very complex and makes it difficult to use the 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 to specify the functional characteristics of the package:
- Packages starting with A-S or U-X:
These packages are restricted for objects of the SAP standard. User-defined objects cannot be created in these packages. Modifications of objects of these packages are recorded by the Transport Organizer and these objects can then be transported (see the field Transport Layer)
- Packages starting with Y or Z:
User-defined objects can be created in these packages. Modifications of the objeckts of the packages are recorded by the Transport Organizer. The transport of objects to other SAP systems is possible (see the field Transport Layer)
- Packages starting with TEST (private packages):
When creating this package, you can decide whether or not change recording is turned on. In this case objects are recorded by the Transport Organizer in local orders during processing.
This packages does not belong to a transport layer. The transport of these objects is only possible if a transport request for other SAP systems is created.
- Packages starting with $ (local packages):
Modifications of the objects of this package are not recorded by the Transport Organizer. The package does not belong to a transport layer. The transport of objects is not possible.
- Packages starting with a name space prefix:
If you reserved a name space, you can use it to create packages (and other objects) that have names starting with the name space prefix.
(Example for a name space prefix: /COMPANY/, example for a corresponding package: /COMPANY/DEVCLASS)
Modifications of objects of these packages are recorded by the Transport Organizer and their transport is possible.
Procedure
Examples
Dependencies
Supplementary Documentation - ETIDEVCLAS0000
Use
Package for which the evaluation is to be executed.
Procedure
Examples
Dependencies
Supplementary Documentation - ETIDEVCLAS0001
Use
Restricting the evaluation by package.
Procedure
In the Package field, specify the package for which you want to create the evaluation. You can also make a generic entry ((*) right-justified).
If you want to execute the evaluation online, you can use (*) only as the third or fourth character.
If you want to use (*) as the first or second character, create a variant for the program and start the variant in the background.
Area Selection
If you want to evaluate a range of packages instead of executing a generic evaluation, enter the lower limit of the range in the Package field and the upper limit of the range in the To Package field.
In this case, a generic entry is not possible.
Examples
Dependencies
Supplementary Documentation - ETIDEVCLAS0002
Use
Specifies which package should be evaluated.
Procedure
Specify a package. A generic entry ((*) right-justified) is possible when using (*) as third or fourth character in the online mode. When executing a generic evaluation using (*) as the first or second character, create a variant and start it in the background.
Examples
Dependencies
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 620 |
