Difference between Development class and Package and transport

hi there is no diff between development class and package. when ever you create a new package, a pop up comes requesting for a request number, its left to you to creata new one or use the exisiting request number.

Hi,

Development class and Package are almost same. Those two things are nothing but folders. In that particular folder we can maintain reports, transactions,ztables etc.

In realtime for our reference we are maintaining the separate packages for different modules thats'all.

Transport Number is nothing but reuest number to save particular things in sap, we are creating the request number and save that particular details. After using this request number only we can transport that things from development server to production server.

Thanks,

Shankar

hi,

A development class is nothing more than a organizational unit. Objects are organized by developement classes and these development classes are tied to transport layers. This defines that when you create an object under a certain developement class, that object may or may not be transported. It depends on how the development class is defined. In newer version, development classes go away and the "Package" is implemented, in Netweaver , the package heirarchy is introduced which allows you to better organize the developement objects.

We require transport request for transporting the program to Quality and production systema nd to maintain versions of the program.If you do not want to maintain the versions and transport the program then you can save the program in $tmp develpment class / Package or else you need to use the Custom development class.

Reward useful points.

SIva

Message was edited by:

SivaKumar

hi,

development class - is related objects from the ABAP/4 repository are assigned to the same development class.This enables you to correct and transport related objects as a unit.

http://help.sap.com/saphelp_46c/helpdata/en/4c/174b6e5733d1118b3f0060b03ca329/frameset.htm

Development classes collect together development environment objects that can be considered as a unit and should therefore also be corrected and transported together. A development class can, for example, consist of a transaction or a group of related transactions

A development class is nothing more than a organizational unit. Objects are organized by developement classes and these development classes are tied to transport layers. This defines that when you create an object under a certain developement class, that object may or may not be transported. It depends on how the development class is defined. In newer version, development classes go away and the "Package" is implemented, in Netweaver , the package heirarchy is introduced which allows you to better organize the developement objects.

You can say in simple word, Development class is like Folder which will have the collection of objects(Report, class etc) for a assigned Proejcts.

local objects(dev class $TMP) are independent of correction and transport system.

Package : crerate your own packeg while saving the lock object that you have created,sometime it maynot allow to save in $TEM,so it would be better to create your oRelated 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:

o Transaction SE80 -> Enter package -> Double-click the package

o 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:

o Packages can be nested.

o Packages can contain their 'visible development objects' (visible

outside of the package) in package interfaces.

o Packages can have use access defined for other package interfaces.

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:

o 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.

o 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 ).

o 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.

o 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.

o 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.

transport:

If you have created a transport under your user name:

1. Goto SE09 or SE10 and enter your username. You will find corresponding transport which you may have created.

or

2. goto Utilities->Version->Version Management. Double click on the task, this will take you to the actual transport number.

Check this link for gaining more info about CTS:

http://www.planetsap.com/cts.htm

________________________________________________________________

Transporting a report from DEV to Quality

1. go to se01 0r se09

2. select the workbench request and modifiable check box and click display

3. select the sub request number (assigned to u r report ) Eg, DV3K918930

4. Click the release directly button ( truck symbol ) which is present in u r application

toolbar.

5. select the parent request number Eg, DV3K918929

6. Click the release directly button ( truck symbol ) which is present in u r application

toolbar.

7. Send a mail to the basis team or testing team by giving u r request numbers u have released.

If u have access to the quality server then repeat the above steps to transport u r report to Production system , otherwise the quality people will be taking care of sending it to production once testing of u r report is done in quality.

___________________________________________________________________

Hi Kp,

A transport request created in the SAP Development environment keeps a record of the related modifications, corrections, configuration, objects, and documentation.

http://help.sap.com/saphelp_sm40/helpdata/en/b5/90cd3a21873650e10000000a11402f/content.htm

http://web.mit.edu/ist/org/admincomputing/dev/qa_tr_faq_production.shtml

http://help.sap.com/saphelp_nw04/helpdata/en/3b/dfba3692dc635ce10000009b38f839/content.htm

http://www.planetsap.com/cts.htm

http://www.sapbrain.com/TOOLS/CTS/CTS.html