Difference b/w development class and package

[Former Member]

<b></b>hi,

can any body tell me what is the difference between development class and package?

thanx in advance,

sunil

[Former Member]

Packagae or the dev class means the group of related objects in SAp

for example all th objects related Sales module are grouped together under a package called ZSD, when you assign a package a request is created which is used to tranport the object to other systems.

You can create any number of fields in a table.

Package is a place where we can group our objects.For eg we can create our own package ZMM -to store MM related objects.ZSD -to store SD Related objects...

Development class is called as Package from release 4.7e onwards.

Thanks and Regards,

pavankumar

[Former Member]

hey sunil

Packages emulates the functionality of development classes in earlier R3 releases.

Developments are assigned to packages that represent similar business processes.

Cheers

shivika

[Former Member]

there is no diffrence ,

upto 4.6C ,we used call development class.

from 4.7 ,5.0,6.0 version onwards we used call package

[Tamas_Hoznek]

Actually there is a difference - packages have more features than development classes. The help explains it a bit more:

*****

Packages extend the concept of development classes to improve modularization, encapsulation, and decoupling in the SAP System.

Development classes, used until now, are simple containers for development objects, provided with a transport layer that specifies how they were to be transported. As an enhancement to development classes, packages include the following attributes: nesting, interfaces, visibility, and use accesses.

Nesting is the ability of a package to include other packages within the package hierarchy.

Visibility is an attribute of package elements. A development element can be visible from outside the package. (It is always visible inside its own package, though not necessarily all the packages embedded in this package). A development element is visible externally if it is included in at least one package interface.

The use access gives a package the right to use the development elements in the package interface of another package. Note that this right is one-way only.