Choropleth Layer integration with SAP BW Live Connection in SAP Analytics Cloud
Geo Maps are a good way to visualize relationships of larger datasets. These chart types are known to be most convenient to understand and process information quickly.
SAP Analytics Cloud provides different Geo Maps related to either point based or shape based layers.
Point based layers refer to a certain geographical point in the landscape like a customer address or a plant location. SAP Analytics Cloud offers three chart types to display geographical information:
- Bubble Layer
- Heat Map Layer
- Flow Layers
Shape based layers display a geographical area or a polygon, like a sales region or a zip code area. The information is saved in a shape file and in SAP Analytics Cloud, it can be consumed via a Choropleth layer.
The idea of a Choropleth layer is to display aggregated information via regions that are based on hierarchies. This offers a drill down functionality.
Update: new Blog online about Custom Choropleth Layer integration with SAP BW Live Connection
In SAP Analytics Cloud, point based layer types can be used out of the box, whereas Choropleth layers using an SAP BW Live connection need additional backend configuration.
This blog post shows the different backend configuration steps needed.
Before jumping into the detailed steps, the following prerequisites need to be fulfilled:
- SAP HANA is required for enabling Geo Maps with BW Live
- For SAP HANA SPS 11, minimum version is 112.07
- For SAP HANA SPS 12, minimum version is 122.03
- SAP BW 7.5 SP16 on HANA or SAP BW/4HANA 2.0 SP4 as a minimum
The Choropleth scenario does not require an additional license, see SNote 2395407.
As a first step, create a Spatial Reference Identifier (SRID) and set it to “3857” which is required by SAP Analytics Cloud. You can do this via SQL console. Detailed steps can be found in SNote 2395407.
Afterwards, download the Spatial Data Delivery Unit (DU) from the SAP Support Portal (search for “GEO CONTENT ANALYTICS“). The package contains two .tgz files which can be imported into your SAP HANA system. Before you start the import process, please make sure to increase the memory size of your SAP HANA Studio installation. This can be done via hdbstudio.ini file (values Xmx = 8192m, XX:MaxPermSize=5120m).
The DU contains approximately 200.000 regions including information of their geographical shapes and locations and the hierarchy, for example that Baden-Württemberg belongs to Germany.
That’s all you need to do on your SAP HANA system.
On the SAP BW side, activate the following BI-Content InfoObjects (in that order):
- 0LATITUDE (latitude information)
- 0LONGITUDE (longitude information)
- 0GSHAPE3857 (used to request shape information)
- 0GEOFEATID (link to the regions stored in SAP HANA)
Next, flag the characteristic as a geo dimension.
This can be done by selecting “Point Data (Attributes 0Longitude and 0Latitude)” on tab “BI Clients”, section “Geographical” of the characteristic.
Afterwards, the following InfoObjects will be assigned automatically to the characteristic as attributes:
In case some of them are missing after switching the Geographical Type, you can also manually add them to the characteristic.
Important: Please make sure that 0GEOFEATID is checked as a navigational attribute!
Next, update your master data.
After loading data into 0LATIDUDE and 0LONGITUDE, run the ABAP report “RSD_GEO_SYNC_ATTR”. The report performs the translation of 0LATIDUDE and 0LONGITUDE into SAP HANA ST_POINT format, which will lead to an optimisation of the runtime performance via the SAP HANA Spatial Engine.
Also, point coordination information will be mapped to regions (on lowest granularity) and the Region ID will be stored in 0GEOFEATID.
Important: The report needs to be executed after every master data update.
Run the ABAP report “RSD_GEO_SYNC_HIER”, which creates the content Hierarchy “SAPBWWORLDHIERARCHY”. The Hierarchy is used by the 0GEOFEATID and will be derived from the SAP HANA DU (Country/State/District). This is a one-time step.
As a last step, you need to maintain the corresponding Composite Provider and Query by adding the geo enabled characteristic as well as the navigational attribute of the characteristic (0GEOFEATID).
Now the backend system is prepared and you can start analysing your data via Choropleth layer in SAP Analytics Cloud!
Do you want to display information from your custom hierarchy like your own sales regions in SAP Analytics Cloud? Stay tuned for more technical blogs 🙂