This blog discusses the use case where we can use list of values generated in SAP Business Objects Information Design Tool’s (IDT) data foundation layer for SAP HANA input parameters (from SAP HANA information view).
As we know that we can map SAP HANA input parameters to universe parameters in data foundation layer of IDT and this can be done by creating derived table in IDT. If you are not sure how to achieve that then please refer to document here. You would need to write a SQL statement to create derived table in IDT. I would like to suggest you to look at SQL statement generated in HANA studio when you preview your data. You can copy the part in green and then use it in IDT (as shown below).
SQL Statement in SAP HANA Studio:
SQL Statement in IDT:
When we use SAP HANA input parameters in Information Design Tool then the list of values created in SAP HANA doesn’t come along. For example, following is the input parameter created in SAP HANA information view (using SAP HANA studio). We are using other HANA information view (see “View/Table for value help:*”) which contains text attribute for distribution channel.
When we preview data in SAP HANA studio then the we can select from list:
However, this list is not visible or comes along with input parameter in IDT.
In this case, we can create list of values from same HANA information view or data model, which contains text attribute of distribution channel in data foundation layer of Information Design Tool. Please use following steps:
Click on “List of value based on SQL” under “Lists of Values” section in IDT’s data foundation
Write the SQL statement and hit “Save” to save data foundation layer.
Once list is created then use it to map with distribution channel parameter.
Now, you should be able to carry this list as well as input parameters to IDT Business Layer and use them as universe prompts. Please note if you are using HANA variables then these variables are visible in data foundation layer and we can use them as Universe prompts as well. HANA variables did not have this issue/gap. So, you can use variables instead of input parameter based on your use case.