HANA Change Management Strategies/Comparisons/Use cases

[nicholas_chang]

 

would like to share my recently research on currently available SAP HANA change Management mechanism. I've compiled them into table below. Information might not be 100% accurate but hope it'll be useful for reference point when deciding a change management strategy for development on HANA landscape.

 

Any valuable input & correction, additional info and etc are mostly welcome and appreciate.

 

	Export/Import Functionality (Studio, HALM)	HALM	CTS+	HTC (Hana Transport Container)	HTA (Hana Transport for ABAP)
Use case	SAP HANA standalone transport management   Cross HANA product system transport (eg: BW to Suite on HANA)	SAP HANA standalone transport management no SOLMAN/ CTS+ domain controller in existing landscape	existing SOLMAN/ CTS+ domain controller in the landscape	ABAP on HANA SAP HANA object need to be transported together with ABAP Object synchronously.     *Delivery Unit (1:1 ratio)	ABAP on HANA Bundle transport of ABAP and HANA Content object   *successor for HTC
ABAP Footprint	No	No	No	Yes	Yes
Activation	Yes	Yes	Yes	Depends on setting in SNHI_DUP_PREWORK	Yes
Minimum Requirement		HANA SPS06	SPS09 (CTS+ without JAVA) SPS05 (CTS+ with JAVA)	SAP NW 7.31 SP5 and higher or SAP NW 740 and higher	HANA SPS09 on at least NW 740 SPS11
Control	No central change process control	No central change process control	Better control as once “Enable CTS Transport” checked, no more native SAP HANA Transport in this system allowed	Better control and integration between ABAP objects and HANA content changes, and transport via classis ABAP STMS	Better control and integration between ABAP objects and HANA content changes, and transport via classis ABAP STMS
How to configure?	N/A	http://scn.sap.com/docs/DOC-48356	http://scn.sap.com/docs/DOC-8576#HANA	http://scn.sap.com/docs/DOC-43035	http://scn.sap.com/docs/DOC-64633
Summary on how it works.	Export/Import feature in Studio or HALM	Registered source into target’s ALM and execute transport in target.	Export: HANA Studio or HALM (SPS08 and above) Import: CTS+ domain controller	Development via ABAP development tools, eg: Studio with eclipse plug-in Create HTC and assign delivery unit SE09 to release and target STMS to import	Development via ABAP development tools, eg: Studio with eclipse plug-in ABAP Transaction SCTS_HTA to select Hana object/packages to synchronize and transport SE09 to release and target STMS to import
Delivery Unit or only Changed object?	Delivery Unit	Individual Changed Object with “Enable Change Recording”	Individual  Changed Object with “Enable Change Recording”	Delivery Unit	Individual Changed Object / packages
Configuration effort	No	Minor	Moderate	No	No
Integration with Charm/QGM	No	No	Yes	Yes	Yes
Pros	Quick and simple	Light weight, Easy to use & setup, no additional system needed	Central management tools to manage; transport and distribute changes in a complex system landscape Transport History available	HANA artifacts are integrated in Standard ABAP request, no additional systems needed. Synchronization between HANA content and ABAP content Transport History available	HANA artifacts are integrated in Standard ABAP request, no additional systems needed. Synchronization between HANA content and ABAP content Transport History available Shorter duration as individual objects/packages imported compare to whole delivery unit in HTC
Cons	No import history/ version tracking	No central management of extended system landscapes No transport synchronization to non-hana content (ABAP)	Usage of CTS system separate import of SAP HANA content and other content type (ABAP)	SAP HANA content is part of ABAP software components	SAP HANA content is part of ABAP software components

Cheers,

Nicholas Chang