3404200 - Transport request released in ABAP Environment not visible in Import Collection app in test tenant - Developer extensibility - SAP S/4HANA Cloud

After creating and releasing a transport request in ABAP Environment (3-System Landscape - Development tenant), the transport request cannot be found in the Import Collection app in test tenant.

SAP S/4HANA Cloud

[CASE1]

1. Creating a package ZPACKAGE1 in ABAP Environment with Software Component ZLOCAL.
2. Creating a transport request XYZA123123 or selecting an existing one.
3. Adding a development object.
4. Releasing the transport request to transport the objects to the test tenant.
5. Issue: the transport request does not appear in the Import Collection app in test tenant.

[CASE2]

1. Creating a package ZPACKAGE2 in ABAP Environment with Software Component ZCUSTOM_DEVELOPMENT.
2. Creating a transport request XYZB123123 or selecting an existing one.
3. Adding a development object.
4. Releasing the transport request to transport the objects to the test tenant.
5. Issue: the transport request does not appear in the Import Collection app in test tenant.

[CASE1]

Transport request XYZB123123 is a local transport request and does not have a transport target defined.

Package ZPACKAGE1 has no superpackage or has ZLOCAL as superpackage and no transport layer assigned.

[CASE2]

Transport request XYZB123123 is a local transport request and does not have a transport target defined.

Package ZPACKAGE2 has no superpackage and no transport layer assigned.

If you create packages that aren't sub packages of ZCUSTOM_DEVELOPMENT, you need to make sure to maintain the correct software component and transport layer. However, we recommend creating packages as sub packages of ZCUSTOM_DEVELOPMENT.

For more information, please refer to Software Components and Packages.

You can check your transport requests by accessing the Transport Organizer. You will notice that local transport requests are under folder "Local Change Requests". If you double click on them, you will see that Target is empty for this type of transport requests.

You can move objects from a local package to a package that is in transportable software component as long as the local transport request where the objects are recorded is released.

However, it is not possible to move packages. You need to create the package again under the right superpackage ZCUSTOM_DEVELOPMENT(recommended option) or with the right properties assigned, software component ZCUSTOM_DEVELOPMENT and transport layer "YDEV". At this point, you should already be asked to assign an existing transport request or create a new transport request.

Then, if the transport request is already released, you should be able to reassign the objects from package ZPACKAGE1/ZPACKAGE2 to the new package, as per Changing the Package Assignment of Development Objects.

Limitations:

1. Currently, it is not possible to select multiple objects for a package reassignment.
2. If the source package is in the software component ZLOCAL and the target package is in a transportable software component, the following rules apply:
   • It is not possible to move SOAP consumption models.
   • Service bindings need to be unpublished before they can be moved.
3. BSP applications deployed from SAP Business Application Studio cannot be moved from a local package to a package that is in transportable software component. In this case, you will need to re-deploy the BSP application from SAP BAS again.
4. It is not possible to move objects between packages that reside in transportable software components to ZLOCAL.
5. It is not possible to move objects between packages that reside in different transportable software components.

3-System Landscape and Transport Management

Transport Management

Software Components and Packages

Changing the Package Assignment of Development Objects

Tools and Apps

Transport Organizer

Import Collection

3SL, ADT, ABAP Environment, 3-System Landscape, SAP S/4HANA Cloud, transport management, change package assignment, local transport request, ZCUSTOM_DEVELOPMENT, ZLOCAL, Software Component, Local Change Requests, released, developer extensibility , KBA , BC-SRV-APS-EXT-SL , Manage and Import Software Collections , Problem