Professional Documents
Culture Documents
© SAP AG
CASE STUDY
Process Overview
Learning Objective Get familiar with data analysis and visualization. Time 75 min
Scenario Every day, Global Bike Inc. employees use various standard sales reports implemented
both in SAP ERP and SAP BW. In addition to that, some operational problems and management
requests need flexible ad-hoc reporting.
Employees involved Hanna Ortmann (Sales Manager Hamburg)
Alex Kuhn (Vice President Marketing US)
Andrea Marino (Sales Manager US)
Report 1 Hanna Ortmann (Sales Manager Hamburg) needs an ad-hoc Scenario details
report on bike sales amounts in a given year for a given customer.
Report 3 Andrea Marino (Sales Manager US) and Hanna Ortmann (Sales
Manager Hamburg) would like to compare the average time span (in days)
between quotation and payment for sales orders in eight GBI sales areas in
the US and Germany.
© SAP AG Page 2
CASE STUDY
Task Calculate how many bikes were sold in 2011 to customer “Alster Cycling”. Time 15 min
Short Description Use SAP Lumira to create a report to visualize in a column chart the number
of bikes sold to Alster Cycling in 2011.
Name (Position) Hanna Ortmann (Sales Manager Hamburg)
First of all, to visualize data in SAP Lumira you need to select a chart type Column chart
(the default chart type is Column Chart). In our case, we will keep the
Column Chart default.
Option 1 Select Quantity (sales quantity) from the Measures list. Quantity measure with
sum aggregation function
© SAP AG Page 3
CASE STUDY
Then, drag and drop the Quantity measure into the Y Axis.
Option 2 Click on the icon next to the Y Axis field to add the measure.
Note Before you continue please check whether the aggregation function
of this measure is set to Sum since the overall quantity is needed.
Since amounts of bikes sold are required for the visualization, before Filter Material Group
Description
adding the Material Group Description to the Legend Color field a filter
needs to be applied on the Material Group Description. Then, select
Finished Bikes
Finished Bikes as the sold material group. This can be achieved in two
different ways.
© SAP AG Page 4
CASE STUDY
© SAP AG Page 5
CASE STUDY
Add the Material Group Description dimension into the Legend Color Add Material Group
Description Dimension into
field by either drag & drop … Legend Color field
… or by clicking on the icon next to the Legend color field, and then
select the dimension from the dimensions list.
After filtering the material group description, for your task another filter Filter Customer Name
(Customer Name) needs to be added and Alster Cycling needs to be Alster Cycling
selected as a value for Customer Name dimension. Then add to the Legend
Color field as well. This can be achieved in two different ways:
© SAP AG Page 6
CASE STUDY
Add the Customer Name dimension into the Legend Color field by either Add Customer Name
Dimension into Legend
drag & drop … Color field
… or by clicking on the icon next to the Legend color field, and then
select the dimension from the dimensions list.
As a last step, filter the Year dimension to retrieve data which is related to Filter year
the year 2011 only. This can be achieved in two different ways: 2011
© SAP AG Page 7
CASE STUDY
Move the year domain to be referring only to year 2011, then click on the
OK button.
Add the Year dimension into the X Axis by either drag & drop … Add Year Dimension into
X axis field
…or by clicking on the icon next to the X Axis field, and then select the
dimension from the dimensions list.
© SAP AG Page 8
CASE STUDY
Once the measures and dimensions are dragged & dropped, the chart input
should look like the screenshot below.
Entry check
The task result should look like the screenshot below. Result
© SAP AG Page 9
CASE STUDY
Task Is there any material that does not display seasonality? Time 30 min
Short Description Use SAP Lumira to visualize in a line chart the achieved revenue per month
compared to the average revenue for each material.
Name (Position) Alex Kuhn (Vice President Marketing US)
First of all, to visualize data in SAP Lumira, you need to select a chart type Line chart
(the default chart type is the column chart). In this case, we will choose a
Line Chart type where seasonality can be best represented.
In order to display Seasonality, the Revenue measure needs to be used. Revenue measure with
sum aggregation function
There are two different options to achieve this.
© SAP AG Page 10
CASE STUDY
Then, drag and drop the Revenue measure into the Y Axis.
OPTION 2 Click on the icon next to the Y Axis field to add the
measure.
Note Before you continue please check whether the aggregation function
of this measure is set to Sum since the overall revenue is needed.
Seasonality in general means periodicity on a given calendar or calendar Add Month Dimension into
X axis field
period. Thus, the Month dimension needs to be used as well. There are two
different options to achieve this.
© SAP AG Page 11
CASE STUDY
Then, drag and drop the Month dimension into the X Axis.
OPTION 2 Click on the icon next to the X Axis field to add the
dimension.
For illustration purposes of Seasonality, the average of the achieved Calculate average of
revenue measure
revenue needs to be calculated and added into the Y Axis aligned with the
total revenue. This can be achieved as follows:
© SAP AG Page 12
CASE STUDY
After the addition, the average revenue will be show in the Y Axis.
The report question is based on material seasonality. In other words, the Add the Material Master
Description into the
revenue and the average revenue per month for each material need to be TRELLIS-Rows
visualized. Therefore, the Material Master Description dimension needs
to be used. There are two different options to achieve this.
Then drag and drop the Material Master Description dimension into the
TRELLIS-Rows.
© SAP AG Page 13
CASE STUDY
OPTION 2 Click on the icon next to the Rows field within the
TRELLIS section to add the dimension.
Once the measures and dimensions are dragged & dropped, the chart input Entry check
should look like the screenshot below.
On the chart “Option”, select Show Data Labels to display values upon Show Data Labels
the created chart.
© SAP AG Page 14
CASE STUDY
The task result should look like the screenshot below. Result
Note By scrolling through the material seasonality charts you will be able
to notice that Air Pump, Elbow Pads, First Aid Kit, Knee Pads, Off Road
Helmet, Repair Kit, Road Helmet, T-shirt, Water Bottle, and Water Bottle
Cage don’t display seasonality.
© SAP AG Page 15
CASE STUDY
Task Calculate the average number of days between quotation and payment Time 30 min
per sales area excluding the results of year 2013.
Short Description Use SAP Lumira to visualize in a column chart the average number of days
between the quotation and payment receipt for each sales area excluding the 2013 result from the
presented values.
Name (Position) Andrea Marino (Sales Manager US)
Hanna Ortmann (Sales Manager Hamburg)
Average number of days between quotation & payment per sales area
(exclude year 2013)
First of all, to visualize data in SAP Lumira you need to select a chart type Column chart
(the default chart type is Column Chart). In our case, we will keep the
Column Chart default.
© SAP AG Page 16
CASE STUDY
Click on “Option” next to the Quote Date dimension, then select Create Create calculated
dimension
Calculated Dimension.
Name the new dimension Days Diff between Quote & Payment.
© SAP AG Page 17
CASE STUDY
Date dimension.
On the formula working space, delete the word start and replace it by
{Quote Date} either by manual writing or by a double click on the Quote
Date dimension in the Dimensions list.
Analogous to the previous step, delete the word end and replace it by
{Payment Receipt Date} either by manual writing or by a double click on
the Payment Receipt Date dimension in the Dimensions list.
Dimension formula
© SAP AG Page 18
CASE STUDY
Create a measure based on the created dimension. Click on “Option” next Create a measure
to the Days Diff between Quote & Payment dimension, then select Create
a measure.
After you have the dimension as a measure within the Measure list, change Average aggregation
function
the aggregation function of this measure to be set to Average. This can be
achieved through clicking on “Option” next to the added measure, then
select Change Aggregation Average.
© SAP AG Page 19
CASE STUDY
Note Before going to the next step, ensure that the aggregation function of
the Days Diff between Quote & Payment measure is set to Average.
There are two different options to add the Days Diff between Quote & Add measure to Y axis
Payment measure into the Y Axis.
OPTION 1 Select Days Diff between Quote & Payment (Average Days
Difference between the Quotation and Payment) from the Measures list.
Then drag and drop the Days Diff between Quote & Payment into the Y
Axis.
OPTION 2 Click on the icon next to the Y Axis field to add the
measure.
© SAP AG Page 20
CASE STUDY
A list of available measures will appear. Select the Days Diff between
Quote & Payment measure.
The average days difference is required per sales area. In other words, the Add Sales Area
Description into Legend
result needs to be grouped by sales area. Therefore, the Sales Area Color field
Description is used. There are two different options to achieve this.
Then, drag and drop the Sales Area Description dimension into the Legend
Color field.
OPTION 2 Click on the icon next to the Legend Color field to add
the measure.
© SAP AG Page 21
CASE STUDY
After the selection, sales area description is shown in the Legend Color
field.
As a last step, filter the Year dimension to exclude data which are related Exclude Year 2013 from
result
to 2013 only. This can be achieved in two different ways:
Move the year domain to exclude the year 2013, then click on the OK
© SAP AG Page 22
CASE STUDY
button.
Once the measures and dimensions are dragged & dropped, the chart input Entry check
should look like the screenshot below.
On the chart “Option”, select Show Data Labels to display values upon Show Data Labels
the created chart.
The task result should look like the screenshot below. Result
© SAP AG Page 23
CASE STUDY
© SAP AG Page 24