What Curtis Stone and Lumira 2.0 have in common ......... let's cook with Beef Wagyu

Now that SAP Lumira 2.0 is very soon available to all of us, I want to recap some of its basic principles. Why ... well, because they are so damn good !

When developing Lumira 2.0, SAP luckily didn't forget its merits: SAP Lumira 2.0 Discovery still has that splendid simple way of working when creating a storyboard or dashboard ..... 4 steps ... nothing more .. nothing less:

  1. Acquire: connect to source(s) of data, and link, merge of blend them

  2. Enrich: enrich the data with data cleansing, new formulas, groupings or hierarchies

  3. Visualize: choose the chart-types and start analyzing and composing your story

  4. Share: share your content on with others on the BI Platform or export to external formats

It's like a cook, isn't it? Curtis Stone also starts opening his fridge first taking out the ingredients he wishes to use on that specific day - acquire. Once done so he starts cleaning, cutting, chopping, mixing and seasoning his ingredients - enrich. Curtis' next step is the actual cooking in his pots and pans; this goes quick but is done very precisely and in an orchestrated order. Same way with Lumira 2.0: once the data acquisition and - enrichment is done, creating the visualizations and storyboards is relatively easy but lay-outing excels with an eye for detail. At the very end Curtis serves his plate: either to an individual who asked for an à la carte dinner, or Curtis shares his plate on the buffet so others can consume as needed. the buffet in this case is the equivalent of the SAP BI Platform.

If have written about this cooking concept in Lumira in previous articles. Next to interoperability, this concept is for me really about winning the end users .... there is no easier and simpler way available in the current BI market to create your own insights than the 4-step-cooking workflow of Lumira 2.0. In the end you BI infrastructure is as strong as its returning number of users. Providing end users with a workflow that is easy to understand and adopt is more important than the last property and whistle on the feature-list.


Now there is quite some stuff going on with Curtis' favorite ingredient Beef Wagyu; the by far best beef available in the world (read about Beef Wagyu here).... WikiPedia:" .. the meat from such wagyu cattle is known for its quality.. let's phrase to beef wagyu in our analogy as BW/4HANA. It has stunning quality and performance and my customers are always talking about connecting to it using Lumira 2.0. So let's focus on that: connect to BW/4HANA using Lumira 2.0.

First we look at the different scenarios to access BW, BW on Hana or BW/4HANA data using SAP Lumira 2.0. Below scenarios apply for both SAP Lumira 2.0 Discovery as SAP Lumira 2.0 Designer. Scenarios set up with Discovery can seamlessly be re-used in Designer using the interoperability between them.

  • Live or Remote connection: with this type of connection, no source data is replicated to Lumra 2.0. The source data stays where it is and queries against it are handled by the BW(/4HANA) system. If the BW Infoprovider or Bex queries has hierarchies embedded, these hierarchies are also available in Lumira 2.0. With this type of connection, blending or merging with other data at Lumira 2.0 level, is not possible. This live connection to BW(/4HANA) is new in SAP Lumira 2.0 and wasn't available in Lumira 1.3x.

  • Offline or Acquired connection: the acquisition-connection accesses BW(/4HANA) and duplicates the data into SAP Lumira 2.0. At any moment in time, the connection can be refreshed (manually or scheduled) so the latest data comes in. If the BW Infoprovider or Bex queries has hierarchies embedded, these hierarchies are also available in Lumira 2.0. With this type of connection, blending or merging with other data at Lumira 2.0 level, is perfectly possible. With this connection type, Lumira 2.0 has a safety belt when it comes to the amount of data

What type of connection to BW/4HANA to use when? In what case do you use a live connection, and in what one you'd prefer the acquired one?

  • We use the Live connection to BW, BW/4HANA or BW on HANA is we require every single detail of the source data in our analyses.

  • We use the acquired or offline connection when we want to investigate a cross-section of the source data and maybe even blend/link/merge that cross-section with data from other sources (SQL db, HANA Offline, other BW, csv or xlsx to name a few)

Below is a little video where I show the new live connector to SAP BW and SAP BW/4HANA using Discovery. The interoperability scenario allows to re-use this connection with a single click in Designer. Pretty cool stuff if you'd ask me!

Video: showing a Live connection to BW/4HANA

Use case: SAP BW/4HANA or BW data source combining with a master reference file

In all discussions I have with customers, I often hear the scenario of using a master reference file in combination with BW. Why this scenario?

Well think of for example reporting units that roll up the teams, into groups, into market units and finally into regions. Quite often this "roll-up" changes; a reporting unit can be requested to report into another team, or a market unit is assigned to another region. These changes are not always possible or processed into the BW system. By maintaining a master file with the correct roll-up and blend that file with the BW data using SAP Lumira 2.0, correct insights are always available. I simulated this scenario in below video using the acquired connection to BW/4HANA. You'll notice that changing the master file and refreshing it in Lumira 2.0, easily ensures proper reporting on the BW data.

Use case: hierarchies embedded in SAP BW/4HANA or BW

The same video below also shows how the new connectors to BW(/4HANA) now respects BW-embedded hierarchies. This is a big enhancement. In the past these hierarchies where often flattened and required some rework in Lumira. Now this is solved. In below video showcasing the master file scenario, you'll notice I use some dimensions with embedded BW hierarchies. Works flawless and again a very nice addition to the Lumira functionality.

Video: showing the re-use of BW/4HANA Hierarchies, and showing using a master file as reference

tweet this article

Share on Facebook

Highlighted articles
Recent articles
Search by tag
Search by category
Follow Me
  • Twitter - Grey Circle
  • LinkedIn - Grey Circle
  • Google+ - Grey Circle
  • Facebook - Grey Circle
  • Blogger - Grey Circle