SAP HANA Transport for ABAP

Karin Spiegel, SAP

September 2015

PUBLIC
Notes

SAP has deprecated SAP HANA extended application services, classic model, and SAP HANA Repository and
advises you to transition to SAP HANA extended application services, advanced model.

If you are still using SAP HANA Transport for ABAP for your SAP HANA Repository content, this presentation
is still available for your reference.

However, we recommend that you move to SAP HANA extended application services, advanced model and
use HTA for HDI. Please refer to SAP Notes 2465027 - Deprecation of SAP HANA extended application
services, classic model and SAP HANA Repository for details

More information is available on the SAP Help Portal:

• HTA for HDI: https://help.sap.com/viewer/6811c09434084fd1bc4f40e66913ce11/7.52.latest/en-

US/c001a13d204a4831a068629f3934df45.html.

• HTA: https://help.sap.com/viewer/6811c09434084fd1bc4f40e66913ce11/7.52.latest/en-
US/ff7652bd542849b18b218efe8d2f2373.html

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Agenda

Transport Options for SAP HANA

When Should SAP HANA Transport for ABAP be Used?

How Does it Work?

Which Tools are Involved?

If You Already Know SAP HANA Transport Container

From SAP HANA Transport Container to SAP HANA Transport for ABAP

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Transport Options for SAP HANA
 Transport Options for SAP HANA Repository Content

Use case: Source Target Transport Offering

SAP HANA Content
SAP HANA Application Lifecycle Management
…in a stand-alone  SAP HANA stand-alone transport management
setup  No need for ABAP-footprint
 Lightweight and easy-to-use transport tool

Enhanced CTS (CTS+)

…on a dedicated
 Transported as any other non-ABAP content
system with ABAP
 Integrated in existing CTS mechanisms
background
 Integrated in SAP process tools (ChaRM, QGM)

Change and Transport System (CTS)

…exclusively  SAP HANA Transport for ABAP (HTA) if CDS or
used by ABAP AMDP do not support your object types
(ABAP for SAP HANA)  SAP HANA Transport Container (HTC)
 Integrated in SAP process tools (ChaRM, QGM)
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5
When Should SAP HANA Transport for
ABAP be Used
When should SAP HANA Transport for ABAP be used?

When SAP HANA Transport for ABAP can be used:

• SAP HANA Transport for ABAP is first delivered with SAP NetWeaver 7.40 SP 11

• Whenever your ABAP system runs on SAP HANA as primary DB

• you need to create SAP HANA repository objects as CDS and AMDP are not an option (either because
the required object types or some properties are not supported)

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

How Does it Work?
How SAP HANA Repository Objects are added to a Transport Request

source system
SAP HANA ABAP

Synchronize Add to TR

HTA Repository Transport Request

Repository

• Create your packages • Decide what to • Manage your

To Do: synchronize Transport Request
• Develop your objects

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

How SAP HANA Repository Objects are Imported

target system
ABAP SAP HANA

Objects are Objects are de-

imported ployed (=imported
and activated)
Import Queue HTA Repository
Repository

To Do: • Import your

Transport Request

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

Which Tools are Involved?
Which tools are involved?

SAP HANA Studio or WebIDE – for development

Transaction SCTS_HTA (in ABAP) – for synchronization

Transaction SE09 – for releasing tasks and transport requests

Transaction STMS – for executing the import

(or Tools like Change Request Management or QGM to manage your project / transport process)

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12

Which tools are involved?
The sequence

Select objects / packages

Develop your application Manage your transports
to be transported

SAP HANA Studio

Or
SAP HANA Web-based Transaction SCTS_HTA Transaction SE09 on source
Development Workbench and STMS on target system

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13

Tools in Detail
SAP HANA Studio or SAP HANA Web-based Development Workbench

Develop your application

Save and Activate
Nothing special to be done for SAP HANA
Transport for ABAP

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14

Tools in Detail
Transaction SCTS_HTA
Open transaction SCTS_HTA

Enter your package (case sensitive!)

Include sub-packages if needed

Select what you would like to synchronize

New / changed objects are selected by default
Differences are marked in blue
You will be asked for an ABAP package (when
first synchronizing an SAP HANA package)
and a transport request

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 15

Tools in Detail
Transactions SE09 and STMS

In Transaction SE09
• Release tasks
• Release transport requests
• Check export logs if needed

In Transaction STMS
• Select the import queue
• Import transport requests
• Check import logs if needed

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 16

If You Already Know HTC
 If you already know HTC

HTC
• still exists
• Bugs will be fixed
• New development is invested in SAP HANA Transport for ABAP

Differences between SAP HANA Transport Container and SAP HANA Transport for ABAP

SAP HANA Transport Container SAP HANA Transport for ABAP

Granularity of Complete delivery unit (DU) Individual objects and / or packages
Transport
Add to Transport In ADT when creating or updating the In SAP GUI when synchronizing (Transaction
Request HTC (take snapshot and save) SCTS_HTA)
Packages and DUs Packages need to be assigned to DU No DU needed.
Activation If configured in SNHI_DUP_PREWORK Always

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 18

From HTC to SAP HANA Transport for ABAP
From HTC to SAP HANA Transport for ABAP

How to migrate the transport method from HTC to SAP HANA Transport for ABAP
▪ Follow these steps:
1. Identify all packages that were previously transported via HTC (as part of the DU)
2. Use transaction SCTS_HTA to synchronize these packages and the contained objects and add them to a
transport request
3. Delete the HTC (for this DU) in ABAP in Eclipse and make this deletion part of the same transport request
as the packages
After that, do not transport (this DU) via HTC any more

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 20

Follow us

www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/copyright for additional trademark information and notices.
SAP folgen auf

www.sap.com/germany/contactsap

© 2021 SAP SE oder ein SAP-Konzernunternehmen. Alle Rechte vorbehalten.

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer,
ohne die ausdrückliche schriftliche Genehmigung durch SAP SE oder ein SAP-Konzernunternehmen nicht gestattet.
In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Die von SAP SE oder deren
Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten. Produkte
können länderspezifische Unterschiede aufweisen.
Die vorliegenden Unterlagen werden von der SAP SE oder einem SAP-Konzernunternehmen bereitgestellt und dienen ausschließlich
zu Informationszwecken. Die SAP SE oder ihre Konzernunternehmen übernehmen keinerlei Haftung oder Gewährleistung für Fehler
oder Unvollständigkeiten in dieser Publikation. Die SAP SE oder ein SAP-Konzernunternehmen steht lediglich für Produkte und
Dienstleistungen nach der Maßgabe ein, die in der Vereinbarung über die jeweiligen Produkte und Dienstleistungen ausdrücklich
geregelt ist. Keine der hierin enthaltenen Informationen ist als zusätzliche Garantie zu interpretieren.
Insbesondere sind die SAP SE oder ihre Konzernunternehmen in keiner Weise verpflichtet, in dieser Publikation oder einer
zugehörigen Präsentation dargestellte Geschäftsabläufe zu verfolgen oder hierin wiedergegebene Funktionen zu entwickeln oder zu
veröffentlichen. Diese Publikation oder eine zugehörige Präsentation, die Strategie und etwaige künftige Entwicklungen, Produkte
und/oder Plattformen der SAP SE oder ihrer Konzernunternehmen können von der SAP SE oder ihren Konzernunternehmen jederzeit
und ohne Angabe von Gründen unangekündigt geändert werden. Die in dieser Publikation enthaltenen Informationen stellen keine
Zusage, kein Versprechen und keine rechtliche Verpflichtung zur Lieferung von Material, Code oder Funktionen dar. Sämtliche
vorausschauenden Aussagen unterliegen unterschiedlichen Risiken und Unsicherheiten, durch die die tatsächlichen Ergebnisse von
den Erwartungen abweichen können. Dem Leser wird empfohlen, diesen vorausschauenden Aussagen kein übertriebenes Vertrauen
zu schenken und sich bei Kaufentscheidungen nicht auf sie zu stützen.
SAP und andere in diesem Dokument erwähnte Produkte und Dienstleistungen von SAP sowie die dazugehörigen Logos sind Marken
oder eingetragene Marken der SAP SE (oder von einem SAP-Konzernunternehmen) in Deutschland und verschiedenen anderen
Ländern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen.
Zusätzliche Informationen zur Marke und Vermerke finden Sie auf der Seite www.sap.com/corporate/de/legal/copyright.html.