Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

development class

Former Member
0 Likes
1,722

Hi,

what is the use of development class.?

8 REPLIES 8
Read only

Former Member
0 Likes
1,520

development class is nothing but a package of all development objects. It can also be called as a package.

Here is an excerpt of what sap says about a package:

Package

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.

Read only

uwe_schieferstein
Active Contributor
0 Likes
1,520

Hello Kan

A development class or nowadays package groups development objects that are used together to perform certain functionalities. Since SAP release 6.20 it is possible to create package hierarchies. The simplest use of such a hierarchy would be to break up a large development project into smaller pieces an assign each of them to a separate package (e.g. package Z_APPLICATION may contain two sub-packages Z_APPL_SERVER and Z_APPL_CLIENT for server and client related objects).

Regards

Uwe

Read only

anversha_s
Active Contributor
0 Likes
1,520

hi,

se80

select package

click on the triangle next to the glasses

click on SAP applications (F6)

Also press F1 on the field below package, this is very well documented by SAP

rgds

Anver

Read only

Former Member
0 Likes
1,520

HI Kan

To keep it simple i would say development class is similar to FOLDERS in windows which we use in SAP to group objects.

Kind Regards

Eswar

Read only

Former Member
0 Likes
1,520

Hi

Development class is nothing but the package which will be popup when u create a program and save it.For local objects we give as &tmp.

examples of package are VL,VA etc.

Creating a new development class

Transaction SE80 now has an “Edit Object” button. You can use it to create a new development class. The name must start with Y or Z.

check this links

http://sap-img.com/abap/how-to-change-the-development-class.htm

if it helps give points

-charitha.

Read only

Former Member
0 Likes
1,520

in plain words it is just s'th like ur folders in ur desktop.

regards

naren

Read only

Former Member
0 Likes
1,520

Hi,

Development class means, u r developing some object u want to save that object because u want to release that object into QA.

So that we r using development class

Read only

Former Member
0 Likes
1,520

Hi,

Development class for Transport Organizer

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

The development classes are described in table TDEVC. They can be maintained in the following transactions:

Transaction SE80 -> Enter development class -> Double-click the development class

Transaction SM30 - Table/view name V_TDEVC

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

Use

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

The representation of the object tree in the ABAP Workbench (Transaction SE80) uses the development class 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 development classes with the same transport layer and distributing the objects to the new classes on the basis of the areas they belong to.

There are the following naming conventions for development classes which determine the class' functions:

Development class begins with A-S or U-X:

These classes are for SAP standard objects. Customer objects cannot be created in them. Changes to objects of these classes are recorded by the Transport Organizer (Request management) and can be transported (s. field transport layer.

Development class begins with Y or Z:

Customer objects can be created in such classes. Changes to objects in these classes are recorded by the Transport Organizer (Request management). The objects can be transported to other SAP Systems (see the field transport layer).

Development class begins with T (private test class):

When such a class is created, 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 class does

not belong to a transport layer. Objects can only transported to other SAP Systems if a transport request is created.

Development class begins with $ (local class):

Changes to objects are not recorded by the Transport Organizer. The class does not belong to a transport layer. The objects cannot be transported.

Development class begins with a namespace prefix:

If you have reserved a namespace, then you can create development classes (and other objects) whose names begin with the namespace prefix.

(Example of a namespace prefix /COMPANY/, example of a corresponding development class /COMPANY/DEVCLASS)

Changes to these development classes are recorded by the Transport Organizer, and can be transported.

Thanks

Manju