Show TOC

Procedure documentationManaging Transports of Non-ABAP Objects Locate this document in the navigation structure

 

You can transport non-ABAP objects in Workbench requests. You use Transport Organizer Web UI for the creation and administration of transport requests for non-ABAP systems. Transport Organizer Classic UI (transaction SE09) is only suitable for ABAP-only systems and dual-stack systems.

For closely coupled applications, you can call the Transport Organizer Web UI directly from the application, as of SPS 14 of SAP NetWeaver 7.0 depending on the application.

You import transport requests containing non-ABAP objects, as before, in TMS (transaction STMS).

Prerequisites

You have performed the configuration steps for non-ABAP transports.

For more information, see Executing Configuration Steps for Non-ABAP Transports.

Procedure

Note Note

The steps described in this procedure represent an example scenario.

End of the note.

  1. Start Transport Organizer Web UI

    You must start Transport Organizer Web UI before you can begin organizing your transport requests. You can also add Transport Organizer Web UI to your favorites.

    For more information, see Starting Transport Organizer Web UI and Transport Organizer Web UI.

  2. Create transport requests that contain non-ABAP objects.

    Depending on the system type, you can create your requests in Transport Organizer Classic UI or in Transport Organizer Web UI.

    For more information, see CreatingTransport Requests for Non-ABAP Objects.

  3. Optional: Preselect the transport request (in Web UI only)

    For more information, see Preselecting Transport Requests.

  4. Attach non-ABAP objects to a transport request.

    You have two options, depending on your application:

    • Directly in the application

      If you want to attach a file to a transport request in an SAP NetWeaver Portal, PI, NWDI, or SLD system, you can do this directly in your application without switching to the Transport Organizer UI. These SAP system types are closely coupled to CTS and can create and release transport requests automatically.

      For more information, see Attaching Non-ABAP Objects Directly in Application.

    • Using a file system

      You can attach objects to a transport request from a file system. To do this, you must first export your objects as a file and save the file to a file system. This process enables you to transport application objects even if the application is not yet connected directly to the CTS system (this could be the case for applications in older releases).

      You must use Transport Organizer Web UI to attach non-ABAP objects to transport requests. Transport Organizer Classic UI is only suitable for ABAP systems and dual-stack systems.

      For more information, see Attaching Non-ABAP Objects Using File System.

  5. Optional: Add additional users to a transport request (in Web UI only).

    To enable multiple users to use the same transport request, you can use the Team tab page in Transport Organizer Web UI to assign all these users to the request.

    For more information, see Adding Users to a Transport Request.

  6. Release the transport requests that contain non-ABAP objects.

    You can release transport requests in Transport Organizer Classic UI and in Transport Organizer Web UI.

    In contrast to pure ABAP transports where every owner of a task that relates to a transport request first has to release that task before the request owner can release the entire request, there are no tasks for individual team members with non-ABAP transports. The transport request is released immediately as soon as a team member releases the transport request. If not all team members are to be allowed to release requests, you can grant the authorizations to the team members accordingly.

    For more information, see Releasing Transport Requests with Non-ABAP Objects.

  7. Optional: Display the transport status and transport logs (only in Web UI)

    Once you have released a transport request, you can monitor its status by viewing its transport logs in Transport Organizer Web UI.

    For more information, see Displaying the Transport Status and Transport Logs.

  8. Import the transport requests that contain non-ABAP objects.

    Transported objects are not available in a target system until you import them into the system using transaction STMS.

    For more information, see Importing Transport Requests with Non-ABAP Objects.