View
213
Download
0
Category
Preview:
Citation preview
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
1/127
0
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
2/127
2009 Wellesley Information Services. All rights reserved.
Building or OptimizingCockpits or Dashboards?What Every SAP Customer Now Needs to Know!
Dr. Bjarne BergComerit Inc.
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
3/127
2
What Well Cover
Dashboards, scorecards, and cockpits The SAP BusinessObjects toolset The traditional SAP toolset SAP NetWeaver Visual Composer A guided tour and demo Performance and optimization of dashboards Using BEx Broadcaster with dashboards SAP NetWeaver Portal integration The good, the bad, and the ugly Examples
Cockpit management and third-party cockpits Wrap-up
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
4/127
3
Dashboard Scorecard Cockpits
Purpose Displays performance Displays progress Displays status and events
Usage Performance monitoring Performance management Performance managementUpdates Real-time feeds Monthly snapshots Daily snapshotsData Events Summaries Summaries and eventsMeasures Metrics KPIs Metrics & KPIsContext Exceptions/alerts Targets and thresholds TrendsSource Linked to systems Linked to plans Linked to BI systems
Sources: Wayne Eckerson, 2005;Bjarne Berg 2006
Background and Terminology
Many companies and people confuse the concepts of dashboards,scorecards, and cockpits
They vary in terms of purpose, usage, source, data, etc. Most BI systems fall into the cockpits category
These are typical parameters, and some may be slightly different (e.g., some metrics in a cockpit may only be updated monthly).
However, such deviations should be exceptions.
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
5/127
Scorecard Example Operational Data
Business needed a wayto pull data fromseveral different multi-providers into onereport
Business also neededthe flexibility to export,print, share, and savereport results
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
6/127
5
Scorecard Example Jump-To a Query
A jump-to is hyperlink that allow users to navigate to more detailedreports associated with that key figure.
Most of our key figures have jump-to links attached to them allowingthe user to see more detailed information with out having to search
for other reports.
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
7/127
6
The Hierarchy of a Good Web Cockpit
1. Develop Management Story
2. Develop Primary KPI andSecondary KPIs
3. Group KPIs into KPI Themes
How Do You Manage? Three Components of a Management Story Primary Outcome: KPI Identify Service Requirements (accuracy, timeliness, quality,
volume) Manage Resources to Meet Service Requirements (people, tools,
process, communicate with funding source)
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
8/127
7
Encourage Wide Array of Measures The Three Types of Indicators
Lagging - historical look at past performance (quarterly revenue,
hours off due to job related injury, employee turnover) Leading - predictive of future results (safety training completion rate,scheduled maintenance compliance rate, grievances)
Real-Time where things are right now (inventory levels, employee
count, contractual obligations outstanding)
4 Signs of a Good Indicator
Tracks mission critical outcomes and activities Is influenced by productive behavior but cant be easily
manipulated by your team Something that all team members can focus their efforts on Value of measuring exceeds cost of measuring
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
9/1278
What Well Cover
Dashboards, scorecards, and cockpits The SAP BusinessObjects toolset The traditional SAP toolset SAP NetWeaver Visual Composer A guided tour and demo Performance and optimization of dashboards Using BEx Broadcaster with dashboards SAP NetWeaver Portal integration The good, the bad, and the ugly Examples
Cockpit management and third-party cockpits Wrap-up
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
10/1279
SAPs Premium Offerings
SAP formally acquired Business Objects in 2008 and is working on
integrating SAP BusinessObjects into the core SAP NetWeaver
BWofferings.
Source: SAP
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
11/12710
SAP BusinessObjects Capabilities Dashboards and Reports
Crystal Reports for pixel formatted reports hasbeen available with SAP NetWeaver BI/BWsince 2002 This tool can be integrated into your tool
portfolio using existing SAP NetWeaver BWqueries
Dashboards can be built using Xcelsius Xcelsius+ will be launched in 2009, and
will be the flagship product for datavisualization & dashboards
Source SAP AG,2009
(NOTE: Crystal & Crystal Base will be the coretools for formatted reports starting 2010)
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
12/127
11
SAP BusinessObjects Capabilities Analysis, Ad Hoc, and Widgets
The SAP BusinessObjects WebIntelligence tool is a tool for ad-hoc, Web-based reporting, query, and analysis
It is intended for end users and canleverage queries to both relational andOLAP sources
It will be the core offering for ad-hoc enduser analysis starting 2009
With the current SAP BusinessObjectsofferings, you can use Desktop Widgets toplace BI content direct onto a PC desktopand monitor reports and KPIs
Source SAP AG, June 2009
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
13/127
12
New Tools Roadmap
Source SAP, June 2009
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
14/127
13
The New SAP BusinessObjects Explorer and SAP NetWeaver BWAccelerator The new SAP BusinessObjects Explorer (not SAP BEx) brings together the in-
memory processing of SAP NetWeaver BW Accelerator with the SAPBusinessObjects BIs search engine
Users can search and explore large volumes of enterprise data to answer onthe fly questions, discover relationships, and uncover root cause
All business users gain immediate insight without needing assistance frombusiness analysts or IT No training required
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
15/12714
Xcelsius Dashboards Overview
There are three tiers in the Xcelsius dashboards
1. The Data Source for access2. The Connectivity for navigation3. The Visualization for image rendering
Required software for SAPNetWeaver BW
SAP BusinessObjects Live Office SAP BusinessObjects Integration SAP BusinessObjects XI 3.1
Data
Connectivity
Visualization
DataSource Webi Universe CrystalReports
QaaWsAdobe
LifeCycleDataservice
LiveOffice
Xcelsius Enterprise
Note: QaaWs = Query as a Web Service
Via QaaWs, you can directly linkdata from SAP NetWeaver BWdata into a dashboard in Xcelsius.
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
16/127
15
Xcelsius Dashboards Step-By-Step
Universe Designer 1. Create Universe
Connect to the SAP NetWeaver BW systemNavigate by InfoCube and select queryInput connection settings (i.e., when data is retrieved)
2. Give the uiverse a name and save the definition
Connectivity QaaWs3. Log on to QaaWs and give the service a name
This name is seen in Xcelsius. Make sure the name is logical and includes time(i.e., Mfg_costs_2010)
4. Click on the universe you created and select the fields you want to make accessiblein the web service
5. Keep the web service as lean as possible. Too much data will perform poorly6. Preview the web service and publish (get an URL)
I.e., http://Bobj:8080/dswsbobj/qaawsservices/portal_2009?def
Step-by-Step idea: Joerg Boeke, 2009
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
17/127
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
18/127
17
Problem: In the new SAP BusinessObjectslandscape there are two ways to build a
semantic layer (universes) for implementingdata access. Each has its own limitations andbenefits.
The first is an MDX-based universe for OLAPconsumers. This is easy to create and isbased on an SAP NetWeaver BW query.However, it is hard to merge external (nonSAP NetWeaver BW) data using this method.
The alternative is to build a traditional SQL- based
universe, but it is very hard to get access to SAPNetWeaver BW data since this by-passes the BIanalytical engine inside SAP NetWeaver BW.
Solution: Implement SAP NetWeaver BW Accelerator + Facade and you can build SQL universes with SAPNetWeaver BW and external data.
Universes The Key Area of SAP BusinessObjects Integration
Source SAP AG, July 2009
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
19/127
Real Experience. RealAdvantage.
18
BW
Data Federator
RDBMS Analytic Engine
OLAP BAPI ODBOXMLA
UniversesQT ODA
SQL Access MDX Access
WebI Crystal Reports XcelsiusQaaWS
BWA
Options for SAP BusinessObjects Cockpit Access to SAPNetWeaver BW 7.0
WebI = SAP BusinessObjects Web Intelligence,BWA = SAP NetWeaver BW AcceleratorODA = Object Discovery AgentQT = A Multithreaded access method based on libraries
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
20/127
Real Experience. RealAdvantage.
19
BW DF Facade
Data Federator
RDBMS Analytic Engine
OLAP BAPI ODBOXMLA
UniversesQT ODA
SQL Access MDX Access
WebI Crystal Reports XcelsiusQaaWS
cells
rows
rows
rows
cells
BWA rowsrows
Options for SAP BusinessObjects Cockpit Access to SAP NetWeaver BW 7.0 (cont.)
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
21/127
SAP NetWeaver BW Server Feature MDX SQL
BW Hierarchies
Restricted and Calculated Key Figures
Security
BW Variables
Currency and Unit Conversion
Exceptions, Conditions
SUM, MIN, MAX Aggregations
AVG, COUNT, COUNT DISTINCT, Aggregations
OLAP Cache
Navigational Attributes
Mass Data Enabled
Federation (e.g. BW RDBMS, BW BW)
= fully supported
= limited support / workaround
Comparison
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
22/127
Expert Hint to Bypassing the Universe for Xcelsius
You can also connect Xcelsius directly to your BI system using the SAPprovided web service QUERY_VIEW_DATA
This will remove the need for a universe
SAP NetWeaver BW1. Create a query view
2. Create a binding URL using the transaction SOAMANAGER maintenancefor Xcelsius
3. In Xcelsius, go to Data Manager and click Add Query as a web service4. Paste your URL
5. Add the name of the query view and data provider
Ref: See Mohan Kumar (SAP) blog at:sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/11574
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
23/127
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
24/127
23
Known Data Federator Limitations and Workarounds
BW Server Feature Workaround
Calculated Key Figures, Formulas Define calculated measures in Universes / WebI
BW VariablesDefine @prompt in Universes or WebI Query Panel; doesnot work for exit variables or variables filled throughauthorizations
Currency and Unit Conversion Simulate via joins in SAP BusinessObjects Data Federator
Exception Aggregations SQL standard aggregations (AVG, COUNT DISTINCT)available via Data Federator processing
Display Attributes Define joins (in DF) from InfoProvider to master data
InfoProvider tablesConditions Use filters on measures
BW Hierarchies No workaround
Non-Cumulative Key Figures No workaround
Source SAP AG, July 2009:www.sapbipartnerinfo.com/resources/docs/SBOP_Part_II_Best_Practices_BI.ppt
WebI = SAP BusinessObjects Web Intelligence
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
25/127
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
26/127
25
News: SAP Is Making the MDX Work Faster Improvements
Avoid unnecessary sorting
MDX standard imposes results to be sortedHowever, those sorts are typically ignored or not required by SAPBusinessObjects Web IntelligenceSorting can be avoided by using a new UNORDER() function in the SAP MDX
Leaner memory consumption during flattening
Optimized flattening algorithmNon-standard result structureLeaner communication ODA OLAP BAPI
Use compressed data exchange via binary XML Availability
SAP NetWeaver BW 7.01 SP 3SAP BusinessObjects Enterprise XI3.0/XI3.1
XI3.0: Fix Pack 2 w/ LAFix2.1XI3.1: Fix Pack 1.2SAP Integration Kit Fix Pack 2 w/ LAFix2.1
SAP B i Obj t W b I t lli SAP N tW BW
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
27/127
SAP BusinessObjects Web Intelligences SAP NetWeaver BWInteroperability via ODA (MDX)Architectural Overview
Functionlibrary
Executioninstance
Parser
Query execution controller
MetadataBAPIs
RowsetAPIs
DatasetBAPIs
MDX engine
Analytic Engine
BWA or RDBMS
ODA
RFC
Implementationof Unorder()function for
optimizing Sorting
Optimizationof memory
consumption
Optimization ofthe exchange
protocoal(binary XML)and format(rowsets;
internal API)
Adapt MDXand Flatteningto new Format
Source SAP, June 2009
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
28/127
27
What Well Cover
Dashboards, scorecards, and cockpits
The SAP BusinessObjects toolset The traditional SAP toolset SAP NetWeaver Visual Composer A guided tour and demo Performance and optimization of dashboards Using BEx Broadcaster with dashboards SAP NetWeaver Portal integration The good, the bad, and the ugly Examples Cockpit management and third-party cockpits Wrap-up
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
29/127
28
Cockpits with BEx Web Application Designer for SAP NetWeaver 7.0
New items include improved tab strip container in SAP NetWeaver 7.0
for designing BI Web applications Reduces the
amount of custom coding
required withthe help of commandwizards, auto
complete, andsupport for HTML tags
BE Web Application Designer for SAP NetWea er 7 0 Ne
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
30/127
BEx Web Application Designer for SAP NetWeaver 7.0 NewFeatures Web Items: Tab Pages, Button, Script Item (SAP NetWeaver 7.0
Support Package Stack 7) Drag and drop using Analysis item New chart types (heat map, Gantt, milestone trend analysis) Export BI Web applications in PDF format Command wizard for generating Web
API commands Integration with SAP NetWeaver 7.0
BEx Report Designer for formatted
reports
29
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
31/127
BI Web API Commands
You can use BI Web API commands for carrying out certain
actions in BI Web ApplicationsExport to Excel, PDF, etc.OLAP functions: Apply filter values, remove drill downs
Command wizards guide you through the steps for creating a BI
Web API command Commands appear together for easy access
Data Provider Web Items
Web Templates
30
Web cockpits developed by Web ApplicationDesigner in SAP NetWeaver 7.0 can beinteractive, include many data sources, andthey can also be very flexible
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
32/127
31
Command Wizard and JavaScript
Use the command wizard for generating JavaScript code for the
Script Item to use in custom cockpit applications
This is a great feature for building custom features into
your cockpits based onstandard JavaScript
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
33/127
32
The Move from BEx Web Application Designer Toward Pioneer
Code name Pioneer (for 1st Quarter 2010release) provides a superset of the capabilities inBEx Analyzer (Excel), BEx Analyzer (Web), andSAP BusinessObjects Voyager.
Voyager customers migrate to Pioneer BEx Analyzer and BEx Web Analyzer customers
migrate to Pioneer. (Note: SAP BEx is planned togo into regular maintenance)
Webbased
Excelbased
Source SAP, June, 2009
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
34/127
33
BEx Web Application Designer
OLAP Processor
BEx Web ApplicationDesigner
BEx Analyzer/Query Designer
Web Service
Charting Engine
Web Browser
HTLM Templates InfoProvider
BEx Web ApplicationDesigner is an intuitivetool to build powerfulweb applications and tointeract with portals andcustom templates
BW queries can bemanipulated in BEx WebApplication Designer for
better display
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
35/127
Source: SAP 20009
Product Directions for BI Solutions
Enterprise DataWarehousing& BI Platform
Advanced
Analysis
EnterpriseReporting
Dashboards,Visualization
Ad-hocQuery &
Reporting
SAP BEx AnalyzerSAP BEx Analyzer VoyagerVoyager
Web App DesignerWeb App Designer
PredictivePredictive
Report DesignerReport Designer
Web IntelligenceWeb Intelligence
Crystal ReportsCrystal Reports
XcelsiusXcelsius
BI WidgetsBI Widgets
Web ServicesWeb Services
And Much
More
PolestarPolestar
Mobile BIMobile BI
BusinessObjects EnterpriseBusinessObjects EnterpriseSAP NetWeaver BW and BWASAP NetWeaver BW and BWA
BWA = SAP NetWeaver BW Accelerator
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
36/127
35
BI Web Application Designer Roadmap
InfoView /SAP NetWeaver Portal
SAP BOEPlatform
SAP NetWeaver BW
BEx WebTemplates
Pioneer WebServer
WorkspacePIO Web
TabBEx Web
Tab
BI Consumer Services
BEx Queries/InfoProviders
Pioneer Web Client
BEx WebApp
Designer
SAP BOEPlatform
Pioneer Web Server
WorkspacePIO Web
TabBEx Web
Tab
BI Consumer Services
Pioneer Web Client
Pioneer Designer/ SDK
SAP NetWeaver BW
BEx WebTemplates
BEx Queries/InfoProviders
BEx WebApp
Designer
Migration optionsvia Pioneer SDK
InfoView /SAP NetWeaver Portal
Planned 2010 Future
SAP BOE = SAP BusinessObjects Enterprise
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
37/127
36
What Well Cover
Dashboards, scorecards, and cockpits
The SAP BusinessObjects toolset The traditional SAP toolset SAP NetWeaver Visual Composer A guided tour and demo Performance and optimization of dashboards Using BEx Broadcaster with dashboards SAP NetWeaver Portal integration The good, the bad, and the ugly Examples Cockpit management and third-party cockpits Wrap-up
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
38/127
You can look at existing queries developed
by others.In this example we will create a web cockpitbased on two SAP NetWeaver BW queries
More advanced developers can call aBusiness Application ProgrammingInterfaces (BAPI), which is deliveredwith SAP NetWeaver BW to buildcomplex applications
Step 1: Find the Data You Want to Model
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
39/127
1. After the query is selected, the metadata istransferred to the model
2. We select one query as the starting point andcan require users to use a prompt (in thisexample we will leave this blank)
Step 2: Selecting the Queries and Defining a Starting Point
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
40/127
1. We add a table view and select thefields we want from the query
2. We give the table view a
meaningful business name
Step 3: Adding a Table View Based on Query Data
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
41/127
1. We add a chart view based on the querydata
2. We decide to make it a column chart3. The fields that we want to graph are
selected
4. We add animation to the column chart
Step 4: Adding a Chart View Based on Query Data
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
42/127
l f h
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
43/127
We can suppress the sum rows from the query, so that thegraphs are more meaningful and the tables are less cluttered
Step 6: Suppressing Zero Values from the Query
S 7 Addi N i i Li ki T bl O h Q i
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
44/127
1. When a user selects a row in the countrytable, we want to show all the customers inthat country and their sales
2. We link the output from the country tableview to the customer query and map thecountry-key value between the two objects
Step 7: Adding Navigation: Linking Tables to Other Queries
S 8 Addi N i i Li ki G h O h Q i
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
45/127
1. We also want to give the users the optionof clicking on a country in the graph andseeing all the customers sales
2. Again, we link the output from thecountry graph to the customer query andmap the country-key value between theobjects
Step 8: Adding Navigation: Linking Graphs to Other Queries
S 9 Addi T bl Vi f C S l D
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
46/127
Previously we added a table and a graph of country sales. Now we want to add similar
views for customer sales.1. First we add a table view2. We select the fields to be displayed
from the query
3. We give the table a meaningful name
Step 9: Adding a Table View for Customer Sales Data
S 9 Addi Pi Ch f C S l D
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
47/127
Now we add a pie chart
1. First we add a graph view
2. We select the pie chart type and the fields to be graphed
3. We give the field a meaningful business name
Step 9: Adding a Pie Chart for Customer Sales Data
St 10 S i Z V l f th Q
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
48/127
Again, we suppress the sum rows from the query, so that thegraphs are more meaningful and the tables are less cluttered.
Step 10: Suppressing Zero Values from the Query
St 11 L t d C ili f D hb d
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
49/127
In the layout section we arrange the objects and resize themso that they look good. We also compile the model and can
now view it in the SAP NetWeaver Portal.
Step 11: Layout and Compiling of Dashboard
Th R lt Th W b C k it i th SAP N tW P t l
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
50/127
All country sales are displayed based on the first query.
The Result: The Web Cockpit in the SAP NetWeaver Portal
The Res lt: Na igation Bet een the Graphs
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
51/127
By clicking on the country ineither of the top views, thebottom views display sales forthose customers.
The Result: Navigation Between the Graphs
Placing SAP NetWeaver Visual Composer Models in Xcelsius
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
52/127
51
Since SAP NetWeaver Visual Composerenhancement pack 1 for SAPNetWeaver Composition Environment(SAP NetWeaver CE) and Xcelsius(2008), you can integrate the SAPNetWeaver Visual Composer models intoXcelsius by implementing Flash Islandsand drive data directly into the SWF file.
Source: Emily Mui, SAP, 2009
Placing SAP NetWeaver Visual Composer Models in Xcelsius
Visual Composer Dashboard in 8 minutes
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
53/127
52
Visual Composer Dashboard in 8 minutes
What Well Cover
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
54/127
53
What We ll Cover
Dashboards, scorecards, and cockpits
The SAP BusinessObjects toolset The traditional SAP toolset SAP NetWeaver Visual Composer A guided tour and demo Performance and optimization of dashboards Using BEx Broadcaster with dashboards SAP NetWeaver Portal integration The good, the bad, and the ugly Examples Cockpit management and third-party cockpits Wrap-up
Cockpit Performance Details
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
55/127
Cockpit Performance Details
Performance Issues and Tips
MultiProviders and PartitioningAggregatesQuery Design and CachingHardware and Servers
Designing for PerformanceInfoCubes and DSOs
SAP NetWeaver BW Accelerator Sizing and ImplementationManagement and Costs
EarlyWatch ReportsLack of performance is the#1 complaint among usersand why many cockpitprojects fail
Tip 1: MultiProviders and Hints
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
56/127
55
Problem: To reduce data volume in each InfoCube,data is partitioned by time period.
A query now has to search in all InfoProviders to findthe data (i.e., billing docs from 2007). This is very slow.
Solution: We can add hints to guide the query execution. In the
RRKMULTIPROVHINT table, you can specify one or severalcharacteristics for each MultiProvider which are then used topartition the MultiProvider into BasicCubes.
If a query has restrictions on this characteristic, the OLAP processor is checked to see which part of the cubes can return data for thequery. The data manager can then completely ignore the remainingcubes.
An entry in RRKMULTIPROVHINT only makes sense if a few attributes of thischaracteristic (that is, only a few data slices) are affected in the majority of, or
the most important, queries(See SAP Note 911939, SAP Note 954889, and SAP Note 1156681)
Tip 1: MultiProviders and Hints
2002 2003 2004 2005 2006 2007 2008
Tip 2: The Secret About MultiProviders and Parallel Processing
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
57/127
56
Tip 2: The Secret About MultiProviders and Parallel Processing
To avoid an overflow of the memory, parallel processing is
cancelled as soon as the collected result contains 30,000 rows or more and there is at least one incomplete sub process
The MultiProvider query is then restarted automatically andprocessed sequentially
What appears to be parallel processing, is actually sequentialprocessing plus the startup phase of parallel processing.
Generally, its recommended that you keep the number of
InfoProviders of a MultiProvider to no more than 10However, even at 4-5 large InfoProviders you may experienceperformance degradation
MultiProviders and Parallel Processing
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
58/127
57
MultiProviders and Parallel Processing
Consider deactivating parallel processing for those queries thatare MultiProvider queries and have large result sets (and hintscannot be used)
With SAP BW 3.0B SP14 (SAP BW 3.1 SP8 and later versions),you can change the default value of 30,000 rows
Refer to SAP Note 629541, SAP Note 622841, SAP Note607164, and SAP Note 630500
A larger number of base InfoProviders is likely to result in ascenario where there are many more base InfoProviders thanavailable dialog processes, which results in limited parallelprocessing and many pipelined sub-queries
You can also change the number of dialogs (increase the use of parallel processing)in RSADMIN by changing the settings for QUERY_MAX_WP_DIAG.
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
59/127
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
60/127
Tip 3: Building Aggregates Is Easy Propose fromS i i
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
61/127
60
Statistics
Select the run time of queries
to be analyzed (e.g., 20 sec) Select the time period to
be analyzedOnly those queries executed inthis time period will be reviewed
to create the proposal
This example shows how tobuild aggregates by using
system statistics to generateproposalsNote: To make this work, the BWstatistics must be captured
Correct Aggregates Are Easy to Build Propose fromQ
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
62/127
61
QueryWe can also create proposalsfrom the query user statistics
To make this work, arepresentative number of queries must be executed togather the statistics to optimizefrom
We can also createproposals for aggregatesbased on individual queriesthat are performing poorly
Tip 4: Reduce the Number of Overlapping Proposals
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
63/127
62
Tip 4: Reduce the Number of Overlapping Proposals
High valuation and high usage is what we are looking for. This indicates high reductionof records in aggregate and high benefits to users .
.
We reduce the overlapping proposalsby optimizing them
This may reduce the proposals from 99to less than a dozen
When using third-party query tools and ODBC to query directly intothe DSO, you are bypassing the OLAP Processor. Therefore, youcannot accurately performance tune the system using aggregates
(statistics), nor will the third-party tool benefit from aggregates .
Activate the Aggregate
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
64/127
Activate the Aggregate
1. Click on Jobs tosee how theprogram isprogressing
The process of turning on theaggregates is simple
Fill the Aggregate with Summary Data
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
65/127
Fill the Aggregate with Summary Data
Cockpit Performance Details
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
66/127
Cockpit Performance Details
Performance Issues and Tips
MultiProviders and PartitioningAggregatesQuery Design and CachingHardware and Servers
Designing for PerformanceInfoCubes and DSOs
SAP NetWeaver BW Accelerator Sizing and ImplementationManagement and Costs
EarlyWatch Reports
Tip 5: Use the Right Read Mode for Queries
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
67/127
66
Tip 5: Use the Right Read Mode for Queries
Select the right read mode. Three query read modes in SAPNetWeaver BW determine the amount of data to be fetched from adatabase:
Read all data (all data is read from a database and stored inuser memory space)Read data during navigation (data is read from a database onlyon demand during navigation)Read data during navigation and when expanding the hierarchy
Reading data during navigation minimizes the impact on theapplication server resources because only data that the user requires will be retrieved
Source: Catherine Roze, MyITgroup
Tip 6: Query Read Mode for Large Hierarchies
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
68/127
67
Tip 6: Query Read Mode for Large Hierarchies
For queries involving large hierarchies with many nodes, it would be wise toselect Read data during navigation and when expanding the hierarchy option to
avoid reading data for the hierarchy nodes that are not expanded. Reserve the Read all data mode for special queries for instance, when a
majority of the users need a given query to slice and dice against alldimensions, or when the data is needed for data mining
This mode places heavy demand on database and memory resources and
might impact other SAP NetWeaver BW processes and tasks A query read mode can be defined either on an individual query basis or as a
default for new queries using the query monitor (transaction RSRT) SAP's recommendation for OLAP universes
Use of hierarchy variable is recommendedHierarchy support in SAP BusinessObjects Web Intelligence for SAPNetWeaver BW is limited
The Use Query Drill option in SAP BusinessObjects Web Intelligencessignificantly improves drilldown performance
Source: Catherine Roze, MyITgroup
Tip 7: Condition and Exceptions
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
69/127
68
p : Co d t o a d cept o s
Minimize conditions-and-exceptions reportingConditions and exceptions are usually processed by the SAPapplication server
This generates additional data transfer between database andapplication servers
If conditions and exceptions have to be used, the amount of data
to be processed should be minimized with filtersWhen multiple drilldowns are required, separate the drilldownsteps by using free characteristics rather than rows andcolumns
This strategy results in a smaller initial result set, and thereforefaster query processing and data transport as compared to aquery where all characteristics are in rows
This strategy does not reduce the query result set. It just separatesthe drilldown steps. In addition to accelerating query processing, it
provides the user more manageable portions of data. Source: Catherine Roze, MyITgroup
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
70/127
Tip 8: Filters
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
71/127
70
p
Leverage filters as much as possibleUsing filters contributes to reducing the number of database
reads and the size of the result set, thereby significantlyimproving query runtimes
Filters are especially valuable when associated with bigdimensions where there is a large number of characteristics
such as customers and document numbersIf large reports have to be produced, leverage the BExBroadcaster to generate batch reports and pre-deliver them each morning to their email, PDF, or printer.
Tip 9: Use Transaction RSRT to Examine Slow Queries
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
72/127
71
p Q
P1 of 3
Look for Patterns and See the Performance Details
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
73/127
72
P2 of 3
In this real case, aggregateswas needed for those cubesflagged
Look at the Query Details for Each Slow Query
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
74/127
73
Q y Q y
Notice the yellow flag for the 6 basecubes in the MultiProvider and theyellow flag for the 14 free chars
(Note: No hints were used in this MultiProvider,which led to very poor performance)
You can also trace the front-end datatransfers and OLAP performance by usingRSTT in SAP NetWeaver BW 7.0
(RSRTRACE in SAP BW 3.5)
Tip 10: Debugging Queries RSRT
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
75/127
74
p gg g Q
Here you can execute the queryand see each breakpoint, therebydebugging the query and seeingwhere the execution is slow
Worth a try: Try running slowqueries in debug mode withparallel processing deactivatedto see if they run faster
Tip 11: Upgrade to AS-Java Service Pack 14 ASAP
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
76/127
75
The implementation of service pack 14 is highlyrecommended by SAP for these performance reasons. Whenimplemented, the Java execution will also improve.
p pg
In service pack 14, there are several performance improvementsincluding:
Better Java execution and performanceIncreased OLAP cache abilities (enhanced cluster table - BLOB)
In SAP NetWeaver BW 7.0, for all service packs up to number 14,
it is also impossible to populate the OLAP cache by broadcastingquery viewsIf you use earlier service packs, you may be forced to createmany different queries to provide this performance
A Real Example
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
77/127
76
This company saw a
39% decrease in queryexecution time after implementing SP14.
They had 38 cockpitsand 82 queries that improved substantially without any further changes
Cockpit#of
QueriesBaseline4/18/08
SP 14(4/21/08)
Improvement
Expense Query for Detailed program 1 145 9 94%Financial dashboard expense (actual vs. target) 7 150 18 88%Financial dashboard [expense] 2 70 12 83%Financial dashboard [non-earnings] 2 42 13 69%Expense Query for Detailed org objective 1 31 10 68%Financial dashboard [workforce costs] 6 50 17 66%Expense Query for Detailed 1 36 14 6 1%Capital Query for Detailed work type 1 22 9 59%
Financial performance 9 43 21 51%Workforce financials 9 29 16 45%Expense query for detailed 1 16 9 44%Balance Query for Detailed program 1 14 8 43%Balance Query for Detailed cost element 1 14 8 43%Balance Query for Detailed MWC 1 14 8 43%Non-earnings Query for Detailed org objec tive 1 14 8 43%Financial dashboard (other balance) 7 29 17 41%Balance query for organization detailed 1 13 8 38%Balance Query for Detailed work type 1 13 8 38%Non-earnings Query for Detailed cost element 1 13 8 38%Capital Query for Detailed cost elem ent 1 14 9 36%Labor query for detailed org 1 14 9 36%Standard costs variance detailed report 1 20 13 35%Financial dashboard (non-earnings) 7 30 20 33%Non-earnings Query for Detailed program 1 12 8 33%Balance Query for Detailed org objective 1 13 9 31%Capital Query for Detailed MW C 1 14 10 29%
Non-earnings query for organization detailed 1 12 9 25%Non-earnings Query for Detailed work type 1 12 9 25%Financial dashboard [workforce cost] 2 23 18 22%Capital Query for Detailed org objective 1 15 12 20%Financial dashboard [other balance sheet] 2 21 17 19%Labor query for detailed cost element 1 12 10 17%Expense Query for Detailed cost elem ent 1 13 11 15%PCC Expense Query for detailed 1 14 12 14%Headcount detail fin-DB 1 15 13 13%Capital - Actual Vs. Target 7 24 22 8%Financial dashboard capital trend 2 13 12 8%
Non-earnings Query for Detailed MWC 1 13 13 0%Average 27.95 12.03 39%
p
Tip 12: Restrictive Key Figures and Line Item Dimensions
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
78/127
77
When Restrictive Key Figures (RKF) are included in a query, conditioning isdone for each of them during query execution
This is very time consuming and a high number of RKFs can seriously hurtquery performance
Recommendation: Reduce RKFs in the query to as few as possible. Also, definecalculated and RKFs on the InfoProvider level instead of locally within thequery
Why?
Good: Formulas within an InfoProvider are returned at runtime and held incacheBad: Local formulas and selections are calculated with each navigationstep
SAP's recommendation for OLAP universes:RKF and Calculated Key figures (CKF) should be built as part of the
underlying BEx query to use the SAP NetWeaver BW back-end processingfor better performanceQueries with a larger set of such Key Figures should use the Use Selectionof Structure Members option in the Query Monitor (transaction RSRT) toleverage the OLAP engine
Tip 12: Restrictive Key Figures and Line Item Dimensions (cont.)
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
79/127
78
Line item dimensions are basically fields that are transaction oriented and therefore,once flagged as a line item dimension, are actually stored in the fact table. Thisresults in faster query access (no table join).
Explore the use of line item dimensions for fieldsthat are frequently conditioned in queries.
SAP's recommendation for Key Figures in OLAP universes:A large number of Key Figures in the BEx query will incur a significantperformance penalty when running queries, regardless of whether the Key Figuresare included in the universe or used in the SAP BusinessObjects Web IntelligencequeryOnly include Key Figures used for reporting in the BEx queryThis performance impact is due to time spent loading metadata for units, executedfor all measures in the query
NOTE: Starting with SAP BusinessObjects Enterprise XI 3.1 FP 1.1, the impact of large number of key figures has been reduced by retrieving metadata information
only when the unit/currency metadata info is selected in the Web Intelligence Query
Tip 13: Reducing the Query Processing Time in Cockpits
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
80/127
79
Problem: Calculated Key Figures (CKFs) are computedduring run-time, and a many CKFs can slow down thequery performance.
Solution: Many of the CKFs can be done during data loads and physicallystored in the InfoProvider. This reduces the number of computations andthe query can use simple table reads instead. Do not use total rows whennot required (this requires additional processing on the OLAP side).
Problem: Sorting the data in reports with large result sets can be time
consuming.
Solution: Reducing the number of sorts in the default view can improvethe report execution and provide the users with data faster.
PS! Reducing the text in query will also speed up the processing some.
Tip 14: Make Your Cockpit Web Templates Smaller
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
81/127
80
Web templates in SAP NetWeaver BWcan become really large. Since theycontain both scripts and CascadingStyle Sheets (CSS), the code canbecome really comprehensive.
To reduce the CSS, you can try several
compression tools that may help youlimit the overall size of your Webtemplates.
There are no lack of free tools available,and the quality varies. Therefore youmust remember to test, test, and test(but the benefits can also be great).
Compression tools for CSS and Java scripts can reduce the overall Web
template size. If you have thousands of users, this can be a life saver.
CSSTidy
Cockpit Performance Details
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
82/127
Performance Issues and TipsMultiProviders and PartitioningAggregatesQuery Design and CachingHardware and Servers
Designing for PerformanceInfoCubes and DSOs
SAP NetWeaver BW Accelerator Sizing and ImplementationManagement and Costs
EarlyWatch Reports
Is the Memory Cache Set Too Low?
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
83/127
82
Cache has a system default of 100 MB for local and 200 MB for globalcache. This may be too low for a system that can be optimized via BExBroadcaster.
The cache is not used when a query contains a virtual keyfigure or virtual characteristics, or when the query isaccessing a transactional DSO or a virtual InfoProvider.
Review the settings with theBasis team and look at theavailable hardware.
Use the transaction codeRSCUSTV14 in SAP NetWeaver BW to increase the cache. Focus
particularly on the global cache.
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
84/127
Tip 16: The Right OLAP Cache Persistence Settings
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
85/127
84
CACHE OLAP Persistence Settings
Note When What T-code
Default Flatfile
Change the logical fileBW_OLAP_CACHE wheninstalling the system (notvalid name) FILE
Optional Cluster table Medium and small result setsRSR_CACHE_DBS_IXRSR_CACHE_DB_IX
OptionalBinary Large Objects(blob) Best for large result sets
RSR_CACHE_DBS_BLRSR_CACHE_DB_BL
SP 14
Blob/ClusterEnhanced (new inSAP NetWeaver BW7.0)
No central cache directory orlock concept (enqueue). Themode is not available bydefault.
SetRSR_CACHE_ACTIVATE_NEWRSADMIN VALUE=x
Source: SAP AG 2008.
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
86/127
Tip 17: Avoid Outdated Indexes and Database Statistics
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
87/127
Database statistics are used by the optimizer to route queries. Outdatedstatistics leads to performance degradation. Outdated indexes can lead
to very poor search performance in all queries where conditioning isused (i.e., mandatory prompts).
For high volume InfoCubes, or cubes that have a high number of users, thepercentage used to build the DB stats can be increased from the default 10%to 20%. This may yield more accurate query routing and better query
performance (consider this especially for cubes with old data partitioned)
Name Tech-Nm Object Indexes DB stats% used to
create statsVendor history closed XFIAP_C10 Infocube 10%AR customer XFIAR_C10 Infocube 10%FIAR line items 0FIAR_C03 Infocube 10%FIAR Payment history 0FIAR_C05 Infocube 10%
FIAR: Transaction data 0FIAR_C02 Infocube 10%Multicube AR&billing XSDARBIL Infocube n/a n/a n/aBilling cube custom for AR trade XSDBILITM Infocube 10%Sales contract cube - anticipated billing XSDCN_C10 Infocube 10%Service orders - ZSLM ZCSCBZSLM Infocube 10%Performance cube ZCSCBPER Infocube 10%Headcount and personnel actionas ZHRPA_C02 Infocube 10%Cycle count XMMWM_C10 Infocube 10%MM LIO interface infocube XLIO_C01 Infocube 10%Material aging ZMMCBMAAG Infocube 10%
Lead time cube ZMMLTCUBE Infocube 10%
Tip 18: Avoid Building Cockpits on DSOs and InfoSets
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
88/127
It is tempting to load cross-reference tables and do lookups inside SAP NetWeaver BW instead of extending extractors. This creates DSOs that cannot be queriedefficiently without many table joins. In this example, of all DSOs contains less thannine fields, and six have less than four.
Programs that can help you monitor the system design:
1. SAP_ANALYZE_ALL_INFOCUBES2. ANALYZE_RSZ_TABLES3. SAP_INFOCUBE_DESIGNS
As much logic as possible should be moved to the extraction,and needed data fields should be denormalized and stored inlogically organized ODSs and Infocubes.
Killing Cockpit Performance InfoCube Design and Indexes
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
89/127
88
When you flag a dimension as high cardinality SAP NetWeaver
BW will use a b-tree index instead of a bit-map index This can be substantially slower if the high cardinality does not
exist in the data in general (star-joins cannot be used with b-trees)
Info Cube Line Itemdims
DIM 1 DIM 3 DIM 6 DIM 8
CBBL_CB02 0 HCBPD_CB06 0 HCBPR_CB11 0 HCBPR_CB18 0 HCBSV_CB01 0 HCBSV_CB02 0 H
Validate the high cardinality of the data and reset the flag ifneeded This will give a better index type and performance
Cockpit Performance Details
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
90/127
89
Performance Issues and TipsMultiProviders and PartitioningAggregatesQuery Design and CachingHardware and Servers
Designing for PerformanceInfoCubes and DSOs
SAP NetWeaver BW Accelerator Sizing and ImplementationManagement and Costs
EarlyWatch Reports
TIP 19: Use SAP NetWeaver BW Accelerator for Large Cockpits or WhenYou Have Many Users
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
91/127
y
The SAP NetWeaver BW Accelerator makes cockpit
response time 10xto 10,000x faster
You use process
chains to maintainthe engine after each data load
HP, Sun, and IBM have standard solutions ranging from $32K to $250K+ that can be installed and tested in as
little as 2-4 weeks (+ SAP license fees)
SAPNWBW
Anytool
NB! 32 GB blades arecertified by SAP
Performance Benchmarks for SAP NetWeaver BW Accelerator
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
92/127
91
SAP NetWeaver BW Accelerator Currently reads data from InfoCubes. DSOs and InfoObjects are still read from base/physical tables (even when the InfoObject
is indexed as part of master data).
SAP NetWeaver BW Accelerators
strength resides in its near-linear
scalability Performance is measured in terms
of:1. SAP NetWeaver BW Accelerator
index creation time2. Multi-user throughput per hour 3. Average report response time4. Average number of records
touched by each report
Cockpit Performance Details
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
93/127
Performance Issues and TipsMultiProviders and PartitioningAggregatesQuery Design and CachingHardware and Servers
Designing for PerformanceInfoCubes and DSOs
SAP NetWeaver BW Accelerator Sizing and ImplementationManagement and Costs
EarlyWatch Reports
Tip 20: Cockpit Performance Monitoring Using EarlyWatch Reports
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
94/127
93
EarlyWatch reports provide asimple way to confirm how your
system is running and to catchproblems
A goldmine for systemrecommendations
Run them periodically and readthe details
This is a real EarlyWatch reportfrom a mid-sized company thathas been running SAP BW for the
last four yearsOn a large global project, system issuescan be hard to pin-down without accessto EarlyWatch reports. The monitoringreports allows you to tune the systembefore the user community gets access
and complaints arise.
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
95/127
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
96/127
What Is BEx Information Broadcasting ?
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
97/127
96
Its a standard part of SAP BW 3.5 and the latest version of SAPNetWeaver. It lets you send reports, BEx queries, Workbooks, andWeb Applications to a variety of recipients, i.e:
Email addresses,BW users, BW
roles SAP NetWeaver
PortalManagementfolders
SAP NetWeaver Portal
Image: SAP AG
SAP NetWeaver 7.0: Query Performance
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
98/127
97
To increase the performance of key queries, youcan fill the OLAP cache or the MDX cache. This isuseful if you have large numbers of usersaccessing a query, or you have a query thataccesses a high volume of data.
The Fill Precalculation Store distribution typeallows you to precalculate Web templates, and thePrecalculate Value Set option allows you to fillprecalculated value set variables with values for
characteristic values. The precalculated valuesets are then available as variable values in BExqueries.
What Well Cover
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
99/127
98
Dashboards, scorecards, and cockpits The SAP BusinessObjects toolset The traditional SAP toolset SAP NetWeaver Visual Composer A guided tour and demo Performance and optimization of dashboards
Using BEx Broadcaster with dashboards SAP NetWeaver Portal integration The good, the bad, and the ugly Examples Cockpit management and third-party cockpits Wrap-up
Web Cockpit in the SAP NetWeaver Portal
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
100/127
99
Integrate queries and Webapplications into the portalthrough publishing,broadcasting, or Web calls
The portal can either receivedesigned pages passively or actively create communities,Web pages, collaborationrooms, or cockpits
Broadcasting
Publishing
SAP NetWeaver Visual Composer 7.0 Portal Publishing
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
101/127
100
SAP NetWeaver VisualComposer design-timetool deploys SAPNetWeaver VisualComposer models directlyas iViews to the Portal
Content Catalog You can then use SAP
NetWeaver VisualComposer iViews in portal
pages, roles, etc.
Building a Web Cockpit in the SAP NetWeaver Portal
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
102/127
101
The trick in developing custom Webcockpits in the portal is to managethe real estate carefully
Most pure iView-based cockpits arecluttered and hard to read andnavigate
1. Start with logical groupings of items (sales, finance, e.g.)
2. Limit colors to complementaryformats (we will look at theselater)
3. Share the same navigation menusand tabs as the portal
4. Avoid running text, flashes,animations, layering, and scrollingtext (this is an absolute no-no)
What Well Cover
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
103/127
102
Dashboards, scorecards, and cockpits The SAP BusinessObjects toolset The traditional SAP toolset SAP NetWeaver Visual Composer A guided tour and demo Performance and optimization of dashboards
Using BEx Broadcaster with dashboards SAP NetWeaver Portal integration The good, the bad, and the ugly Examples Cockpit management and third-party cockpits Wrap-up
War Rooms and External Access
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
104/127
103
External access to information is more common.Vendors and customers love it!
You can build war rooms for collaborativedecision making using cockpits
Shared cockpits are mostuseful
Cockpits require a true BI infrastructure. It is tempting to jumpstraight to the cockpit development, but it is almost impossiblewithout a well-architected SAP NetWeaver BW system to support it.
A Good Cockpit Is Simple
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
105/127
104
The majority of usage of cockpits is in user segments 1 and 5.You should use BW queries and OLAP for the other segments.
Segment 1: Trackers - 37%Tracking - Characterized by low durationoverall.
Segment 2: Reservers - 3%Low duration per page view.
Segment 3: Uncommitted - 10%Characterized by long duration.
Complex decisions.
Segment 4: Info Gatherers - 4%Concentrated in information areas.Rarely reach transaction areas.
Segment 5: Single-clickers - 32%Visit homepage only.
Segment 6: Wanderers - 15%Very few, very random pages.
Few hits, but long duration per pageview. Example source: Dr. Paul Strupp, Sun Microsystems
The average manager navigates in no more than 7 dimensions and only 2 levels deep(49 views). Therefore, the majority of users of cockpits need a few, simple, but highly
informative, views. The other user community is best served by OLAP queries.
Use of Color
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
106/127
105
Colors share a powerful connection withemotions, so you want to be conservative
Colors on opposite sides arecomplementary and looks good together in a cockpit
Sir Isaac Newton developed thefirst circular diagram of colors in1666 and identified 12 basic colors
Color definitions:Shade: Base color mixed with blackTint: Base color hue mixed with whiteTone: Base color + gray or another base color +
a complementary color Source: Bob Marteal, Cornell Univ.2005, Susan M. Raymond, WHS
How Do You Pick Your Web Cockpit Colors?
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
107/127
106
This uses a single pure color with a number of tints andshades to provide variety
Pros: Extremely unified and harmonious; effective for establishing an overall mood
Cons: Can be dull because of the lack of variation andtherefore can lose the interest of the viewer
Monochromatic scheme
Any three colors which are side by side on a color wheel,
Pros: Great selection of possible combinations makesthis scheme versatile. The similarity makes the schemesharmonious with great results because it is soothing andrestful.
Cons: The use of more than three colors can dilute the
overall effect of this scheme.
Analogous scheme
How Do You Pick Your Web Cockpit Colors? (cont.)
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
108/127
107
Pick any three colors on a triangle. This scheme is veryappealing and well balanced.
Pros: Extremely stable, each color perfectly balances with theother. It is useful for presenting information in bold, decisivepatterns.
Cons: The vibrancy may be too much and detract from themessage.
Triadic scheme
Any two colors that are side by side on a color wheel
Pros: This scheme has more variety than a simplecomplementary color scheme
Cons: It is less vibrant and eye-catching; it is difficult toharmonize the colors
Split scheme
A Colorful Example of What not to Do
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
109/127
108
Colors that are so similar that noteveryone will be able todistinguish them (blendsinformation)
Distracting color that breaks thecolor scheme and attracts
attention for no apparent reason
Split schemebackground colorsthat are unattractive
Use of Real Estate Symmetry, Graphs, and Colors
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
110/127
109
Consistent use of graphs is visually pleasing. Hereare three types of graphs and a map.
Background colors are amonochromatic schemein blue
Bars and lines are limitedto the same color schemewith few additional colors
Symmetry is visually pleasing and makes the cockpit easy to read.Here we have 3 walls, 4 frames in the outer walls, and a central section.
Filling the white space by either enlarging the map, or adding a
message board would improve this cockpit
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
111/127
SEM-CPM Rules for Graphs and Real Estate
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
112/127
111
111
Try to avoid empty spaces, but dont force unrelated measuresinto the cockpit view it confuses users
Dont use as many types of graphs as possible,and never mix more than 3 types of graphs. If youuse more, users have to interpret the pictures as well as thedata
Missing datapoints addirritation(it is hard tohide bad data
in a cockpit) 111
What Well Cover
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
113/127
112
Dashboards, scorecards, and cockpits The SAP BusinessObjects toolset The traditional SAP toolset SAP NetWeaver Visual Composer A guided tour and demo Performance and optimization of dashboards
Using BEx Broadcaster with dashboards SAP NetWeaver Portal integration The good, the bad, and the ugly Examples Cockpit management and third-party cockpits Wrap-up
Change Management Process
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
114/127
113
ChangeRequest form
Complete?No
Reviewrecommended?
Submission
ChangeRequest form
No
Yes
Approved?
No
Scheduled
Developed Unit TestedDevl. environment
System testedDevl. environment
Integration testedQA environment
Approved?
Approved?
Approved?
Moved toproductionNo
No
No
Yes
Yes
Yes Yes
Yes
IT responsible
Business responsible
Sr. mgmt. responsible
The Change Management Form Page 1
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
115/127
114
To make this process work, you need a formal instrument The instrument can be online (i.e., a Web page), electronic (Word
document), or a paper-based system The form should contain at least these fields
The front pagethat the
requestor fillsout
Requestor Name:Department
Phone number / email
Describe the change requested, bedetailed
Why is it needed
How important is it that thechange occur? (how would you
manage if this is not done)
TBD Whenpossible
Futurerelease
Date Break-fix(right now)
When is the change needed
Change Request Form
The Change Management Form Page 2
h d b h d h
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
116/127
115
115
This page is used by the system administrator or theproject team
The purpose is to have controlled changes that arescheduled and tested appropriately
The back pagethat the system
admin andapprover fill out
Received date:Reviewed by:
Comments/recommendation
Pending Not-Approved Futurerelease
Approved Break-fix(right now)
Approval status:
Approved by:Approved date:
Assigned to:Due date:
Pending Prototyped In QA Tested In Production
Development status:
For internal use only
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
117/127
Third-Party Cockpits (cont.)
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
118/127
117
Other BI and cockpit companies areactively working on creating cockpittools for SAP NetWeaver BW
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
119/127
BI Java SDK-Based Cockpits
SAP N W D l S di d l BI J SDK b d
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
120/127
119
SAP NetWeaver Developer Studio can develop BI Java SDK-basedapplications
Can use along with SAP Java Web Dynpro
Interested developersshould familiarizethemselves with SAPNetWeaver Developer Studio
What Well Cover
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
121/127
120
Dashboards, scorecards, and cockpits The SAP BusinessObjects toolset The traditional SAP toolset SAP NetWeaver Visual Composer A guided tour and demo Performance and optimization of dashboards
Using BEx Broadcaster with dashboards SAP NetWeaver Portal integration The good, the bad, and the ugly Examples Cockpit management and third-party cockpits Wrap-up
Resources
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
122/127
121
http://help.sap.comSAP BusinessObjects top level navigation tab
http://boc.sdn.sap.comSAP BusinessObjects Developer Community on SDNCommunities, Beta Product downloads, Webinar information, E-Books,Developer Conference 2007 slides, Free Trial downloads, more!...Check out the blogs and forums there is already some great contentposted
https://wiki.sdn.sap.com/wiki/display/profile/Ingo%20Hilgefort
Ingo Hilgeforts blog SAP NetWeaver Business Warehouse Roadmap and Roadmap FAQ
http://www.sdn.sap.com/irj/boc/business-objects-for-sap-faq http://www.comeritinc.com/Downloads.htm
Online material, presentations, and downloads
New SAP Press Book
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
123/127
Ingo Hilgefort, Integrating
BusinessObjects XI 3.0 BI Toolswith SAP NetWeaver, SAP Press,ISBN 978-1-59229-274-5
Great resource for technical
installation, implementation,and integration information
http://sap-press.com/product.cfm?accou
nt=&product=H3034
7 Key Points to Take Home
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
124/127
123
There are many ways to build Web cockpits and SAP has tools for them all
Look at in-house Web skills before you decide on the tool
SAP Performance Management is a great tool for those withlimited Web skills, but requires consistency in performancemeasures (roll-ups) and structured navigation
SAP NetWeaver Visual Composer is great for simple graphing
BEx Web Application Development is the tool of choice byexperienced Web programmers who want total design freedom
7 Key Points to Take Home (cont.)
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
125/127
Third-party tools for Web cockpits are emerging and some arequite advanced
While all the tools give you a great deal of flexibility, it is the useof the real estate, colors, graphs, and consistency that is going todetermine if your cockpit is successful: Spend serious timedesigning instead of coding!
Your Turn!
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
126/127
125
How to contact me:Dr. Bjarne Berg
bberg@comeritinc.com
Disclaimer
SAP R/3 mySAP mySAP com SAP NetWeaver Duet PartnerEdge and other SAP products and services mentioned herein as well as their
8/7/2019 Jumpstart_Building_or_optimizing_cockpits_or_dashboards_v9
127/127
SAP, R/3, mySAP, mySAP.com, SAP NetWeaver , Duet , PartnerEdge, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other productand service names mentioned are the trademarks of their respective companies. Wellesley Information Services is neither owned nor controlled bySAP.
Recommended