Consuming SAP HANA views or database procedures in ABAP code creates dependencies between the ABAP code and the SAP HANA artifacts. This holds true when consuming the artifacts using native SQL and is made more evident when working with proxies.

Transporting the dependent ABAP code so that it can be imported into target systems successfully requires the referenced SAP HANA content to be transported before or with the ABAP code. One way to achieve this is to transport the SAP HANA delivery units using the Enhanced Change and Transport System( CTS+).

An easier way may be to make use of SAP HANA Transport containers.

SAP HANA Transport containers are a new ABAP repository object introduced with SAP NetWeaver 7.31 that allows for the transport of SAP HANA content with an ABAP transport request, provided the ABAP system uses SAP HANA as its primary database. Basically, it points to and represents a delivery unit.

Proper use of SAP HANA Transport Containers

To create and maintain an SAP HANA Transport Container (HTC), use the ABAP development tools (ADT) as follows:

• In the context menu of the ABAP project or an ABAP package, Select New ->[Other] ABAP Repository Object.
• Choose Others -> HANA Transport Containers
• Specify the ABAP package and the name of the SAP HANA delivery unit for which you want to create a transport container. Note the HTC name is automatically derived from the name of the delivery unit.

When you create an SAP HANA Transport Container, you take a snapshot of the full content of the corresponding SAP HANA delivery unit and store a copy of it in the ABAP transport request.

The snapshot stored in the SAP HTC must be kept in sync manually. To do so, open the SAP HANA HTC and choose to Take snapshots and Save. You have to activate the SAP HTC before you can transport it.

When transported and imported into a target system, the snapshot is unpacked and the SAP HANA content is deployed into the SAP HANA database and activated.