package

[Former Member]

while saving a report why do the system asks for a package.This is an important interview question faced.Please reply an exact answer.I am very thankful to those who have done it.

[Former Member]

A Package is the only possible way of transporting the Report from one system to other.

Example. We develop report in development system. If we dont assign that to a package then we cant assign that to a transport request. It is must that the report must be under one package for transporting the report. Then only we can transport report to Quality system and then to Production.

$tmp is the package which can not be transported. That is Local Objects package. It is predefined SAP Package. all other packages can be transportable.

[Former Member]

Hi

when your creating a report it asks for the package and transport request

after you develop program

when ever you click on save or activate button there it did't ask any package again because , your already saved under a package name

once if you release that object to the next server (releasing trasport request )

after that if do any changes at that time it will ask you the package name and trasport request

beacuse you had released the trasport request

i think you understood this

simply once you saved a program under a package it won't ask you every time about package name to be entered when you press SAVE button

once if you realeased that object then next time if you want to change that object and click on save button it will ask package name at that time

Rewar dif usefull

[Former Member]

Hi,

<b> Package</b>

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.

<b> Use</b>

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.

<b>Reward with points if helpful/</b>

Regards,

Vijay

[Former Member]

Coz any objects assigned to a package can be transported, If you give local object also it will work fine, later if u want to transport you will ahve to assign package.