Data Type Mapping and Miscellaneous
When using the OLAP-based access, the SAP Vora Table is created based on the data types used for displaying the content. This creates a certain inexactness (especially for time-related values which are stored as VARCHAR).
When using the view-based access, the SAP Vora Table is created based on the data types specified in the SAP HANA View. This enables a very precise mapping of the data types. However, it is not possible to rename columns or change the order of columns in the target.
The table below lists the data type mapping between SAP BW and SAP Data Hub.
| SAP BW Type | SAP Data Hub Type |
|---|---|
| STRING, NUMC, LINE_STRING, MULTI_LINE_STRING, LOWER_CASE_STRING, UPPER_CASE_STRING, URI | STRING |
| DOUBLE | DOUBLE |
| PERCENT, QUANTITY, AMOUNT, PRICE, DECOMAL_FLOAT | DECIMAL |
| INTEGER | INTEGER |
| BOOLEAN | BOOLEAN |
| CALENDAR_DAY, DATE | DATE |
| DATE_TIME | DATETIME |
| TIME, TIMESPAN | TIME |
| LONG | INTEGER |
By default, the data transfer operation generates two coloumns per dimension. The internal key is used for the data transfer. The text is written into a separate column (as can be seen in the UI). It is currently not possible to change the type of the text or key.
For more information on SAP BW INA, see 2415249 
Due to the table format in the target the result will be flattened. Meaning all structures and hierarchies are disabled.