Transport Scenarios for SAP HANA Content

SAP HANA content for ABAP for SAP HANA applications is usually transported together with ABAP objects, since the development objects are closely-connected in terms of content. The following methods can be used to transport this SAP HANA content:

• SAP HANA Transport for ABAP (HTA)

  HTA can be used to synchronize objects and packages from the SAP HANA repository to ABAP and add them to a default ABAP transport request. Before synchronizing them, you select SAP HANA packages and objects that you can transport together with the associated ABAP objects. When the transport request is imported into the target system:

  • The ABAP objects in the transport request (including the HTA objects) are imported into the ABAP system.
  • The SAP HANA packages and objects are imported into the SAP HANA repository of the target system and activated there.
• HANA Transport Container (HTC)

  The HTC is a logical transport object that is transported with the standard ABAP transport tools. An HTC always contains all SAP HANA repository objects of a delivery unit. The HTC is attached to a standard ABAP transport request and transported together with the associated ABAP objects. When the transport request is imported into the target system:

  • The ABAP objects in the transport request (including the HTC objects) are imported into the ABAP system.

  • The SAP HANA repository objects in the DU are imported into the SAP HANA repository. The import is performed with or without activation, depending on the system settings of the associated ABAP software component of the HTC.

This transport scenario is integrated into the existing CTS transport landscape and into the SAP tools for change control (Change Request Management and Quality Gate Management in SAP Solution Manager) For mixed content, you can reuse transport routes configured for transports of ABAP objects.

Content for native SAP HANA applications is SAP HANA content that is developed exclusively for SAP HANA systems. You can use the extended Change and Transport System (CTS+) to transport SAP HANA content for native SAP HANA applications, or for non-ABAP applications that are based on SAP HANA. It is particularly well-suited to heterogeneous transport landscapes in which CTS+ is already in use. From an administrative point of view, the SAP HANA content is another object type that can be transported with the CTS in the same way as other non-ABAP objects. The effort required for configuration is low, and the transport tools are already familiar. In particular, you can use CTS+ if you want to transport SAP HANA content as part of an SAP solution (such as SAP BI, Mobile, and so on), since in this case, you often need to create a link between the SAP HANA content and other non-ABAP development objects and non-SAP HANA development objects.

This transport scenario is integrated into the existing CTS transport landscape and into the SAP tools for change control (Change Request Management and Quality Gate Management in SAP Solution Manager) You can configure the transport routes for the systems in question in Transport Management System. The transport is performed in the same way as for any other non-ABAP application that is integrated into CTS+.

For more information about the configuration of SAP HANA for CTS+, see the SAP Community Network under Resources on CTS+ -> SAP HANA.

If CTS+ is not in use, you can use SAP HANA Application Lifecycle Management to transport SAP HANA content for native SAP HANA applications. You can use SAP HANA Application Lifecycle Management to perform transports and monitor transport processes.

SAP HANA Application Lifecycle Management is particularly well-suited to SAP HANA transport landscapes with no ABAP development (without CTS+) and with no requirement for synchronizing transports with other non-HANA content.

For more information, see SAP HANA Application Lifecycle Management Guide .