{"id":3225,"date":"2017-05-30T20:47:42","date_gmt":"2017-05-30T19:47:42","guid":{"rendered":"http:\/\/www.hackingsap.com\/blog\/?p=3225"},"modified":"2017-05-30T20:47:42","modified_gmt":"2017-05-30T19:47:42","slug":"sap-analytics-hub-a-first-look","status":"publish","type":"post","link":"https:\/\/www.hackingsap.com\/blog\/sap-analytics-hub-a-first-look","title":{"rendered":"SAP Analytics Hub – A first look"},"content":{"rendered":"

In my previous post<\/a> on the new names for the SAP BI products, the list (in the tweet) also included a new product: SAP Analytics Hub<\/strong>. Unfortunately I don’t have access yet, and there is also not that much material available on this product, but enough to at least get an idea of the purpose and direction. So let’s have a look.<\/p>\n

It is common for an\u00a0organization to have multiple places or platforms to\u00a0host reports. Even within SAP-only environments we see this: BI Launchpad, Fiori Launchpad,\u00a0Analytics Cloud, BEx Web. For the end-user this is of course an awful\u00a0experience, as he has to switch between different platforms to get to all his reports, and needs to ‘learn’ where to find what.<\/p>\n

\"sapanalyticshub4\"<\/a><\/p>\n

The SAP Analytics Hub is advertised as\u00a0the single platform and entry point for\u00a0users, where they can find\u00a0all\u00a0<\/strong>their reports. At my current project we positioned and setup the\u00a0BI Launchpad for this, but we had to use a bunch of workarounds and have to live with all the limitations of the\u00a0tool.<\/p>\n