After your BW database is migrated to a HANA database, you might wish to push your BW transformations to HANA. After migrating to HANA, there is an option available in the Transformations which you can select. This blog describes the different limitations that are there in making transformations HANA enabled.
Part of the SAP Migration Cockpit, you get the SAP program ZBW_TRANSFORM_FINDER that helps us find out which transformation can/cannot be HANA enabled. From this program we already understand the i) limitations in making BW transformations HANA enabled. However, there are also ii) cases where the Program says" transformations can be processed in HANA", but there are still other limitations. These are described below:
i) Limitations/errors thrown by the Program
Transformation can be HANA enabled by selecting option available on each transformation (aside the Name of the transformation). We can check if transformation can be enabled, by choosing the "Check" button
Transformations of below types cannot be processed in HANA. (Below is not a complete list)
This is a result given by the Program ZBW_TRANSFORM_FINDER or by choosing the "Check" button
1.Transformation with sourcetype as DI_SOURCE Datasource (Data Services datasource) is not supported
2.Transformation with Target provider type as 'InfoCube' is not supported
3.Transformation with Target provider type as 'InfoObject' is not supported
4.Transformation with Rule Types (Start& End Routine) not supported
5.Transformation with Rule type (Field Routine) is not supported
6.Transformation with Conversion exit PERI7 is not supported
7. Transformation with Expert routine is not supported
8. Source provider type 'InfoObject' is not supported
9. Source provider type 'Query Element' is not supported
10. Open hub transformations with destination type 'File' is not supported
11. ABAP datatype 'RAW' of fields in SAP ECC datasources is not supported
ii) Other extra Cases/Limitations
Below are cases where a transformations cannot be made HANA enabled though the program says so
For a HANA Enabled transformation to be processed on "HANA Processing mode" it is mandatory that the related DTP (DTP that uses this transformation) has to be HANA enabled. Unless the DTP is HANA enabled, there is no use in converting a transformation to "HANA enabled"
In other words, only DTPs that has the option "SAP HANA execution" checked will use the HANA enabled transformation. Else it would continue to use the ABAP based transformation.
By using the option "Check Availability", we can know if the DTP can be used in HANA processing mode
So we have to understand the limitations in making the DTPs as "HANA enabled"
Limitations in making DTPs process on HANA mode
- HANA enabled DTPs will not support Error handling
Below options cannot be used then
2. HANA enabled DTPs will not support SemanticGroups
3. When underlying transformations cannot be HANA enabled, then the DTP cannot be HANA enabled
Lets consider below example. Though the Transformation from Infosource to DSO can be processed in HANA, you cannot make the DTP process on
HANA as the underlying transformation from datasource to Infosource cannot be HANA enabled. Please see details below
Checking the DTP (0BBP_TD_QUOT_1 / AHMED1C100 -> 0BBP_QUO) that loads DSO 0BBP_QUO gives below message.
But as we can see Transformation TRCS 0BBP_QUO_TD_1 -> ODSO 0BBP_QUO is already HANA enabled
Because transformation RSDS 0BBP_TD_QUOT_1 E6SCLNT300 -> TRCS 0BBP_QUO_TD_1 cannot be HANA enabled, the DTP gives such a message.
Transformation RSDS 0BBP_TD_QUOT_1 E6SCLNT300 -> TRCS 0BBP_QUO_TD_1 cannot be process in HANA because it has Field routines
So, Only in a flow where all Transformations can be processed in HANA, we can enable DTPs to process on HANA mode.
This means we cannot all transformations to HANA enabled though the Program says so or if the Check passes. We have to consider the above scenarios with DTPs also.
Hope this blog gives you a very crisp overview of the limitations in making transformations HANA enabled. All findings above are based out of hands on checkings in the system. If there are corrections, please keep me informed
