Migration of Native SAP HANA Database Objects
In SAP HANA databases, native SAP HANA database objects are stored in the SAP HANA repository 1.0, also known as _SYS_BIC. To ensure a proper encapsulation of the source and target releases during updates with ZDO, the database objects and database artefacts are cloned.
The users of the bridge subsystem that runs on the source release do not see the updated database artifacts, which are prepared for the target release when the objects are cloned. However, SAP HANA repository 1.0 does not provide the functionality to ensure the isolation of the source and target release.
To prepare an SAP S/4HANA system for updates with ZDO, all objects stored in _SYS_BIC must be migrated to new containers based on the HTA for HDI technology (SAP HANA Transport for ABAP (HTA) for SAP HANA Deployment Infrastructure (HDI)).
To prepare an SAP S/4HANA system for updates with ZDO, all objects stored in _SYS_BIC must be migrated to new containers that are based on HTA for HDI technology. HTA for HDI means SAP HANA Transport for ABAP (HTA) for SAP HANA Deployment Infrastructure (HDI). For more information, see the HTA for HDI documentation on the SAP Help Portal.
The following figure shows a typical SAP S/4HANA database architecture:
-
All objects stored in _SYS_BIC and used by business processes:
Applications such as SAP BPC and SAP Real-Time Consolidation have provided migration reports. For these application-specific migration reports, see the following SAP Notes: -
All custom objects that are used by business processes:
Use the SAP HANA XS Advanced Migration Assistant for the migration of customer objects. For more information, see the SAP HANA XS Advanced Migration Guide .
See the following tutorial for the correct naming of the native SAP HANA objects: Tutorial: Developing and Consuming HDI Objects in ABAP

