SAP HANA
Transport for ABAP
SAP HANA Transport for ABAP makes it possible to synchronize objects and packages from the SAP HANA repository to the SAP HANA Transport for ABAP repository (HTA repository) in the ABAP system and add them to a transport request.
SAP HANA Transport for ABAP can be used when development objects in ABAP and SAP HANA have closely linked content and need to be transported together. The prerequisite is that the ABAP system is running on a SAP HANA database. HTA is the successor to HANA Transport Container (HTC), which was used up to SAP NetWeaver 7.4 SPS 10 to transport SAP HANA content for ABAP for SAP HANA applications and can be used to transport full delivery units (DUs) only.
More specifically, HTA is available for scenarios for which other technologies, such as ABAP Managed Database Procedures (AMDP) or Core Data Services (CDS), are not sufficient.
. You can use HTA for transports of SAP HANA content for ABAP for SAP HANA applications.
These are ABAP-based applications that are optimized for SAP HANA databases. More specifically, these are applications that use code pushdown, where performance-intensive calculations are moved from the application program (in ABAP) to the database level (for example, in views).
If you develop or run native SAP HANA applications in the same system landscape as ABAP for SAP HANA applications, you can also use HTA to transport SAP HANA content for these applications. More specifically, this includes native SAP HANA applications that reference ABAP tables. In this case, you can use the existing infrastructure of the system landscape for transports with HTA, even if CTS+ or SAP HANA Application Lifecycle Management is recommended for transports of SAP HANA content for native SAP HANA applications.
For more information, see Transport Scenarios for SAP HANA Content.
Synchronization of objects and packages in the SAP HANA repository from SAP HANA to ABAP (transaction code SCTS_HTA)
The system shows the synchronization status of the SAP HANA objects and packages for one or more selected SAP HANA packages in the SAP HANA repository and in the HTA repository (in ABAP) and proposes modified objects to be synchronized. When they are synchronized, the selected objects and packages are written to the HTA repository and added to a transport request. The synchronization always used the active versions of objects in the SAP HANA repository.
The texts in the SAP HANA objects are synchronized in the original language of the SAP HANA package by default and can be translated with the standard ABAP translation tool (transaction SE63).
More information about language support can be found under Language Support with SAP HANA Transport for ABAP.
In the SAP HANA development environment, no further action is required to add the objects to a transport request.
For more information about the transport process with HTA, see Description of the Transport Process.
Integration into Change and Transport System (CTS) in AS ABAP
When objects are added to an ABAP transport request, SAP HANA content can be transported through the entire system landscape using the tried and tested ABAP transport mechanisms.
For more information about Change and Transport System, see Change and Transport System.
Options for Transporting Individual SAP HANA Objects and Packages
You can transport individual objects and packages from the SAP HANA repository.
If you previously transported complete SAP HANA delivery units (DUs) with HTC, you can migrate the transport method to HTA. You can then transport the packages and objects using HTA. For more information, see Migrating the Transport Method from HTC to HTA.
RestrictionIf you want to group your development activities, you can use change recording in your SAP HANA development environment and record your changes in changelists.
We advise against using change recording, however, when making transports using SAP HANA Transport for ABAP. The way objects are grouped in changelists does not determine which objects need to be transported together using HTA. The changelists are ignored when objects and packages are synchronized. Also, imports of SAP HANA objects and packages into target systems where change recording is enabled can produce inconsistent system states.
Subsequent deployment of imported SAP HANA objects and packages to the SAP HANA repository of the target system
Usually, SAP HANA packages and objects are deployed automatically after the transport request is imported in the target system. If this is not the case, you can deploy the SAP HANA packages and objects subsequently in the target system. This may be necessary, for example, if the settings in HTA stipulate that a package can only be deployed once prework has been completed. Redeployment may also be necessary due to errors in other objects or missing settings in SAP HANA.
For more information, see Manually Deploying SAP HANA Objects and Packages.