Showing results for 
Search instead for 
Did you mean: 

package name in business content

Former Member
0 Kudos

when i am trying to activate a cube in business content,when i click install and transport,i am getting a pop up window asking for a package name

can somebody please give me some info on this,what is a package name,is it just like a folder or anything else

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi.....Is the same concept of R3 the package is a configuration that could be created in SE80 and allows to configure the source and destination of the SAP objects that needs to be transported into other system....for example when you create a transport request for a program and you need to pass it from DEV to QAS you must use a package created for this and that has in its configuration both systems...

In BW you have to do the same have a package that allows you to transport requests from BWD to BWQ.


Former Member
0 Kudos

thank you oscar

is there anywhere i can read more about it

Answers (1)

Answers (1)

Former Member
0 Kudos

You can go to se80 and open any Package and F1 over the name of the package and you can see the sap Help...


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.



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.


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.