Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
Former Member

Aggregations of stores selected in a map

The purpose of this project was to test the geographic capabilities of SAP HANA, the goal was to get information of sales grouped by their geographic location with a familiar interface like Google Maps, the project is available in GitHub: christianladron/Geo_Aggs-Map.

The motivation of the development was to create a way to get information of sales by region independent of the previously defined on the system, allowing to monitor the sales of a set of stores contained in an arbitrary region of the map, in this case defined with a polygon, the which can be defined in a familiar Google Maps interface clicking on the locations of its vertices.

Definition of the geographic selection:


This was solved using the geographic objects of HANA and its methods to generate the content, an XS service to response the results involving geographic queries and SAP UI5 to create the components of the interface, the geographic objects of HANA can be exported to the WKT standard, incompatible with Google maps, so we used the Wicket library ( for the translation between these formats.

First we created the tables of Sales, Stores and Categories filled with random data, the table stores has the fields Latitude and Longitude of each store, the table Sales has all the data records of each sale, including the store, and it's corresponding category, and the table Categories include the different categories that groups the sales.

Sales table definition:

table.schemaName = "GEO_AGG";

table.tableType = COLUMNSTORE;

table.columns = [{name="ID";sqlType=INTEGER;nullable = false;},

{name="STORE";sqlType=INTEGER;nullable = false;},

{name="CATEGORY";sqlType=INTEGER;nullable = false;},

{name="VOLUME";sqlType=DOUBLE;nullable = false;},

{name="UNITS";sqlType=BIGINT;nullable = false;},

{name="PROMOS";sqlType=DOUBLE;nullable = false;},

{name="PREDICTION";sqlType=DOUBLE;nullable = false;}];


Stores table definition:

table.schemaName = "GEO_AGG";

table.tableType = COLUMNSTORE;

table.columns = [{name="ID";sqlType=INTEGER;nullable = false;},

{name="STATE";sqlType=SHORTTEXT;nullable = false;length=100;},

{name="LONGITUDE";sqlType=DOUBLE;nullable = false;},

{name="LATITUDE";sqlType=DOUBLE;nullable = false;}];


Categories table definition:

table.schemaName = "GEO_AGG";

table.tableType = COLUMNSTORE;

table.columns = [{name="ID";sqlType=INTEGER;nullable = false;},

{name="CATEGORY";sqlType=SHORTTEXT;nullable = false;length=100;},

{name="DESCRIPTION";sqlType=SHORTTEXT;nullable = false;length=250;}];


Then was created the view Geo_Stores, this has two calculated fields, Location with a ST.Point object, and the other with the location of the point in standard format WKT.

Geo_Stores view definition:


query="SELECT *, NEW ST_POINT(Latitude,Longitude) AS Location, NEW ST_POINT(Latitude,Longitude).ST_AsWKT() AS Location_txt \

FROM \"GEO_AGG\".\"mexbalia.Geo_Agg.DB::Stores\"";

The view Aggregations calculates the sum of all the sales grouped by the store and category, this view was created to simplify the query used in the SX service.

Geo_Stores view definition:


query="select \"STORE\",\


sum(\"VOLUME\") AS \"VOLUME\",\

sum(\"UNITS\") AS \"UNITS\",\

sum(\"PROMOS\") AS \"PROMOS\",\


from \"GEO_AGG\".\"mexbalia.Geo_Agg.DB::Sales\" GROUP BY \"STORE\",\"CATEGORY\" ORDER BY \"STORE\" ASC";

Then the services  for web consumption was created, one is the file Services.xsodata, this service provides the information of the table Categories. The service Stores_Coords.xsjs accepts as parameters a definition string of a polygon in format WKT and a string with a list of the category id's of interest, the response of the service is a list with the stores contained in the polygon and the sum of all the sales that satisfies to be in one of the selected stores and to be in one of the categories selected.

OData service definition:

service {

        "GEO_AGG"."mexbalia.Geo_Agg.DB::Categories" as "categories";


Stores_Coords.xsjs service definition:

var polygon = $.request.parameters.get("polygon");

var categories = $.request.parameters.get("categories");

if (categories=='()'){categories = '(0)';}


var connection = $.db.getConnection("mexbalia.Geo_Agg.UI::Anonymous_Access");

var GetStores = connection.prepareStatement( "SELECT * FROM \"GEO_AGG\".\"mexbalia.Geo_Agg.DB::Geo_Stores\" WHERE NEW ST_Polygon(?) .ST_Contains( location )=1" );


var ResultRow =GetStores.executeQuery();

var StoresResponse=[];

var current_object={};

var StoresList = [];


var StoreID = ResultRow.getString(1);





var StoresList_str = '('+StoresList.toString()+')';

if (StoresList.length == 0){StoresList_str='(0)';}

var AggregationsResponse=[];

var GetAggregations=connection.prepareStatement("select sum(Sales.volume) as volume,sum(TO_BIGINT(Sales.units)) as units,sum(Sales.promos) as promos,sum(Sales.prediction) as prediction "+

"from \"GEO_AGG\".\"mexbalia.Geo_Agg.DB::Aggregations\" as Sales where in "+StoresList_str+" and Sales.category in "+categories);

var ResultRow =GetAggregations.executeQuery();

var current_object={};

$.response.contentType = "json";





var respuesta = {map:StoresResponse,table:AggregationsResponse};






else{$.response.contentType = "text";

$.response.setBody('Invalid Categories List');


The most important part of the process is the Stores_Coords.xsjs service, it executes a query creating an object of class polygon with the WKT string parameter, and using the return of it's function CONTAINS as a condition for the where clause, the result is a selection only of the stores inside of the polygon defined.

This is the query used to get the contained stores:

SELECT * FROM "GEO_AGG"."mexbalia.Geo_Agg.DB::Geo_Stores" WHERE NEW ST_Polygon( 'WKT Polygon definition' ) .ST_Contains( location )=1

The results of this query are used to create an expression list with the ID's of the contained stores, the next query calculates the aggregations needed using this list with the expression list of the input parameter categories.

select sum(Sales.volume) as volume,sum(Sales.units) as units,sum(Sales.promos) as promos,sum(Sales.prediction) as prediction from "GEO_AGG"."mexbalia.Geo_Agg.DB::Aggregations" as Sales where in (Expression list of stores) and Sales.category in (Expression list of categories)

The first result of these queries are the response of the Service, this service is requested b y the interface trough an XHR call and the response is sent to a WKT->GMaps converter called Wkt_conv to get the locations in a GMaps format and add them to the map, the second result is  bound to the bar graph.

Example of WKT to Google conversion:'WKT geometry definition');

var GoogleObj = wkt_conv.toObject();

Example of Google to WKT conversion:


var Wkt_string = wkt_conv.write();

The input parameter categories of the stores_Coords.xsjs service is generated with the checkboxes of the UI, and the parameter polygon is generated with the information of the polygon defined by the user in the map, and converted to WKT using Wkt_conv.

This is a simple way to solve the problem when the number of stores is small, supportable for a browser, the creation of a grid and usage of the ST_SnapToGrid function becomes necessary in the case of a large number of stores. 

Labels in this area