Access HANA tables created by SAP RIVER Code in SAP Lumira
Correction: This blog as earlier stated not using OData, instead we are using to access the HANA catalog tables created by the SAP River program.
RIVER code when activated creates tables and oData for the entity. The table created by RIVER code will be used to get the data from SAP HANA into SAP Lumira for preparing dataset. This dataset will be used for Visualization.
Only SAP HANA Analytic Views can be used in SAP Lumira for preparing datasets.
In this blog we will use HANA tables created by SAP RIVER in SAP Lumira for preparing data sets.
Creating a file with extension .RDL in RIVER environment.
Activate the RIVER file. Now there will be three to ‘Generate Test Data’, ‘Data Preview’, ‘Odata Calls’
Click on Generate test data.
Specify Sample Data
I have selected ‘values from file’. To look a reasonable data, I have prepared a TEXT file with comma separated.
Values for YEAR
Data Preview
Check the oData by clicking on ‘oData Calls’
Go to SAP Lumira to create a DATASET
Choose SAP HANA database and click on NEXT for establishing a connection
Give the credentials to connect to HANA System and click on ‘Connect’
Shortlist the table by using a keyword. Select the columns which are required by checking/unchecking the box. Click on create to create a DATASET.
Click on ‘Prepare’
Prepare the data, Define Measures, Time and Geographic Hierarchy
Create ‘Geographic Hierarchy’ for CITY
Create ‘Time Hierarchy’ for YEAR
Hide the duplicate fields(CITY and other fields) from the dataset panel
Hide the fields which are not required and save the file. You can save it in ‘Local’ or “Cloud’.
Now Click on “Visualize”. Select DONUT CHART for Visualization
Donut Chart – Sales Revenue by City
Donut Chart – Sales Revenue by City – Year on Year by using TRELLIS option
Sources:
This is really cool. One thigI dont understand is the 'OData Call'. Is it a file generated when you activate your .rdl file? Can you please give more details?
Benedict
Yes Benedict, the Odata documentation is generated automatically on activation. You can think of it as a human-readable version of $metadata (which is the XML representation).
SAP River is naturally exposed via OData. Any OData services that are specified in the SAP River code are also generated. In the Code i have defined it as @ oData
At runtime, a client makes OData calls to retrieve and update data.