Package and TR

[Former Member]

Hi ,

In the SAP R/3 system, how to check in which transport request the package is saved?

Regards,

Yogita

[Former Member]

Is this package or project?

Basically, a TP# is tied up to a project. If you want to see the project, just double click on TP and in properties tab you can see the project.

An object is assigned to package. This can be seen in attributes tab.

Thanks,

SKJ

[Former Member]

This is a package created using SE21.

For example : I have created a package Z123 in Development system and had transported it in test system.

Now after some time, I want to refer same transport request to transport package Z123 to other system.

How can I search in which Transport request the package is saved? I check the version management for package but it's greyed out.

Please help.

[Former Member]

Okay...

The packages in each system are group under one transport layer.

You may have to use STMS t-code.

Refer below:

Transport Layer in ABAP Workbench

The Change and Transport System supports the distribution of development work on large projects across multiple SAP Systems.

The packages in each development system are grouped into one transport layer.

The transport layer determines whether objects are assigned to a local or transportable change request.

Use

Each of your SAP development systems is assigned a transport layer as its standard transport layer. If you use Extended Transport Control, you can assign different standard transport layers to certain clients.

You can define at the most one consolidation target for each SAP System and transport layer.

When you create a package, it is assigned the standard transport layer of the SAP System.

If you want to assign a different transport layer to a package, you require the administration authorization for the Change and Transport System.

The objects in a package automatically have the transport attributes defined for the corresponding transport layer.

If a consolidation route originating in their SAP System is defined, then the objects are assigned to a transportable request, and transported into the consolidation target when it is released.

If a consolidation route is not defined, the objects are assigned to a local request, and are not transported.

Customizing settings are not assigned to a package. They have the transport attributes of the standard transport layer of the system or client.

It is best to assign a package a standard transport layer for which a consolidation route originating in the development system is defined.

To display and maintain the transport layers and routes, use the Transport Management System (transaction STMS).

Only the system adminstrator can make changes.

Caution:

The tables TSYST, DEVL, TWSYS, TASYS are no longer productive as of Release 4.0A and cannot be maintained.

Thanks,

SKJ

[GauthamV]

hi,

u can check the package in particular request in se03 tcode.

generally transport requests r stored in e070 and e071.so

u can check those tables also.

hope this helps u.

reward points if useful.

[Former Member]

thanks