Académique Documents
Professionnel Documents
Culture Documents
Introduction
Scoping the SAP NetWeaver BI project
Getting the project started
Designing InfoCubes the good, the bad, and the ugly
Improving Performance what to do, and how to do it
Understanding the curse of MultiProviders
Cleaning up and ODS management
Considering global integration points
Wrap-up
2
Introduction
3
BI Has Grown Up and Is Now a Core Infrastructure Requirement
BI competency center
BI governance program
No plans
Enterprise Info. strategy Within 2009
Currently have
Information quality program
Introduction
Scoping the SAP NetWeaver BI project
Getting the project started
Designing InfoCubes the good, the bad, and the ugly
Improving Performance what to do, and how to do it
Understanding the curse of MultiProviders
Cleaning up and ODS management
Considering global integration points
Wrap-up
5
Global Master Data Integration and SAP NetWeaver BI
Security 7.62
High
Low
Low High Source: Bjarne Berg, DM 11
Impact of Failure Review 2004
Tip 3: Report Dispositioning: Dont Throw Every Report into BI
Portal Developer(s)
Introduction
Scoping the SAP NetWeaver BI project
Getting the project started
Designing InfoCubes the good, the bad, and the ugly
Improving Performance what to do, and how to do it
Understanding the curse of MultiProviders
Cleaning up and ODS management
Considering global integration points
Wrap-up
21
Tip 8: In the Blueprinting Phase: Model Your Global Solution
1. Create a model based on pre-delivered SAP NetWeaver BI content
2. Map your data requirements to the delivered content, and identify gaps
3. Identify where the data gaps are going to be sourced from
Unit
Logistics
Material
Currency Key Billing information
Plant Unit of Measure
Material number
Shipping/receiving point Base unit of measure
Material entered Billing document
Material group Sales unit of measure
Billing item
Item category Volume unit of measure
Billing type
Product hierarchy Weight unit of measure
Billing category
Storage EAN/UPC Billing Billing date
Creation date
Requirements
Cancel indicator
Number of billing documents
Customer Output medium
Number biling line items ~ Batch billing indicator
Billed item quantity Debit/credit reason code
Sold-to Net weight Biling category
Ship-to Subtotal 1 Reference document
Bill-to Subtotal 2 Payment terms
Payer Subtotal 3 Cancelled billing document
Subtotal 4 Divison for the order header
Customer class
Customer group Subtotal 5 Pricing procedure
Subtotal 6
+
~ Customer country
~ Customer region Subtotal A Document details
~ Customer postal code Net value
~ Customer industry code 1 Cost
End user Tax amount Sales order document type
Volume Sales deal
Sales docuement
Organization
Company code
Division
Personnel Accounting
Time Storage
Standard Content
Distribution channel
Sales organization
Sales group
Sales rep number Cost center
Profit center
Controlling area
Calendar
Calendar
year
month
Objects
Account assignment group Calendar week
23
Tip 10: Meet Local and Global Requirements
*
*
FI
es
gm
ry
g
M
M
io
AP
in
to
Sa
E
ut
CR
m
ur
n
SC
rib
ve
t
y
ac
lit
In
st
uf
a
Di
Qu
an
M
Introduction
Scoping the SAP NetWeaver BI project
Getting the project started
Designing InfoCubes the good, the bad, and the ugly
Improving Performance what to do, and how to do it
Understanding the curse of MultiProviders
Cleaning up and ODS management
Considering global integration points
Wrap-up
26
Tip 12: InfoCube Design Making the Right Design Decisions
Dimensions
BI allows you to create up to 16 dimensions in a single InfoCube (13
are free)
However, using all 16 on a first implementation limits any future
extensions without major redesign of the system
Line item dimensions increase query performance
These are physically stored in the fact table and therefore have
fewer table joins
Key figures
While no limitations are imposed by BI for the number of key
figures, typical implementations contain 1 - 25
While a higher number may be required (i.e. CO-PA), youll
notice tradeoffs of load performance when many records
are loaded
While more than 45 key figures are not necessarily wrong, it might
be considered unusual you should perform an impact study of
the extract on SAP R/3
27
Tip 12: InfoCube Design General Guidelines
Navigational attributes
Lends flexibility to the way users can access data
Common configuration consists of 1 - 35 attributes
While technically not incorrect you should review InfoCubes that do
not contain any navigational attributes
Review any InfoCube that contains more than 60
This may be an indicator that too much information is being
placed in a single InfoCube
Hierarchies
Hierarchies are ways for users to drill-down into the data for
analysis purposes
Typical configurations tend to have 1 - 8 hierarchies
Review any InfoCube with no hierarchy (or with more than 8) to
validate the design with end-user navigation
For global projects you need to consider global and local currencies as well as
various units of measures (e.g., lbs, kilo, tons, gallons, liters). Once decided
upon, these units of measures should be available in all relevant InfoProviders.
28
Tip 12: InfoCube Design Evaluating Designs (Real Example)
Name Type Tech_nm Dims* Characteristics Largest dim # KF # info. Nav
(all) total of Char Sources attributes
Billing documents condition values Infocube ZSD_C15 10 47 11 3 1 107
Customer Infocube 0SD_C01 8 14 5 16 1 5
Delivery service Infocube 0SD_C04 9 23 5 15 2 10
Invoice summary Infocube ZSD_C06 16 55 11 19 4 116
Order summary Infocube ZSD_C03 16 62 13 23 5 96
Sales order condition value Infocube 0SD_C15 10 41 10 2 1 0
Sales overview Infocube 0SD_C03 11 34 7 17 7 16
Profitability analysis Infocube Z_COPA_X 15 56 14 85 1 70
Inventory mgmt plant summary Infocube MRP_MATL 6 9 3 22 1 16
Material stock/movements Infocube 0IC_C03 9 18 4 24 - 5
Plant & periodic plant stocks Infocube 0IC_C01 8 15 5 21 - 15
Ad-hoc query order line details MC ZSD_M01 7 14 3 6 - 0
Conditions order & billing document MC OSD_MC01 4 66 56 2 - 0
Order and Invoice summary MC ZSD_C04 16 72 20 24 - 88
SD Pricing order & billing docs MC ZSD_M02 12 53 12 3 - 94
Campaign management Infocube ZDM_C006 15 56 19 29 9 109
Commissions Infocube ZDM_C003 14 34 14 8 4 0
Daily management Infocube ZSD_C01 9 31 8 10 6 6
Disposition summary Cubes with many red
Infocube ZDM_C001 9 16 4 1 1 0
Inquiry summary Infocube ZDC_C005 15 22 4 1 1 29
Matrix or yellow codes
Infocube ZDM_C002 10 16 3 141 1 0
Monthly management report
Program summary
should be examined
Infocube
Infocube
ZDM_C005
ZDM_C004
7
16
9
23
3
4
6
12
1
8
0
1
30
Tip 13: Partitioned InfoCubes That Are No Longer the Same
Sales Order: LPD 2007 ZCORD_L07 15 5 40 9 59 Added 'Created by' as a Dimension(instead of field in
Date dim)
Sales Order History: ACD 2006 ZCODI_A06 15 13 58 39 66
Sales Order History: ACD 2007 ZCODI_A07 15 13 60 9 66 1) Removed 30 Key Figures, 2) Added field "Date for
inv/bill index and print out" to Date dimension 3) added
field "Customer purchase order type" to business reason
dimension
Sales Order History: LPD 2006 ZCODI_L06 15 13 58 39 66
Sales Order History: LPD 2007 ZCODI_L07 15 13 60 9 66 1) Removed 30 Key Figures, 2) Added field "Date for
inv/bill index and print out" to Date dimension 3) added
field "Customer purchase order type" to business reason
dimension 31
Tip 14: Naming Conventions Should Be Followed
InfoCube Supply Chain Mgmt - Inventory Mgmt. Cube for Risk Management ZRISK
InfoCubes should
InfoCube Supply Chain Mgmt - Inventory Mgmt. Material stocks/movements (as of 3.0B) 0IC_C03
InfoCube Industry Sectors - Oil & Gas - Exchanges Exchange balance 0OI_EXC01
InfoCube Industry Sectors - Retail Retail Competitor Pricing ZRTL_C01
be named: InfoCube
InfoCube
Non SAP Area - Marine Services
Non SAP Area - Marine Services
PEDCO DTHEAD_DTTAIL
PEDCO LOGSUM
ZPDCO_C01
ZPDCO_C05
0ABC_C01 or InfoCube
InfoCube
Non SAP Area - Marine Services
Non SAP Area - Marine Services
PEDCO MTHEAD_MTTAIL
PEDCO RCHEAD_RCTAIL
ZPDCO_C03
ZPDCO_C02
ZABC_C02
InfoCube Non SAP Area - SFIO SFIO Movement Position ZSDMVMPOS
InfoCube Non SAP Area - SFIO SFIO Movement Position History ZSDMVMHIS
InfoCube Non SAP Area - SFIO SFIO OIPR ZSD_OIPR
InfoCube Non SAP Area - SFIO SFIO OIPR History ZSD_OIPHS
InfoCube Non SAP Area - EPM (Ent. project mgmt) EPM Cube II ZEPM_C02
named:
InfoCube Monthly Operation Planning 3 MOP3 Pricing Marker ZMOP_CMKR
InfoCube Monthly Operation Planning 3 Monthly Operation Planning 3 ZMOP_P01
InfoCube Fin. Mgmt & Controlling - Profit Center Acct. Margin Analysis ZPCA_C04
0ABC_O01 or InfoCube
InfoCube
Fin. Mgmt & Controlling - Profit Center Acct.
Fin. Mgmt & Controlling - Profit Center Acct.
PCA: Summary 1
PCA: Summary 1 History
ZPCA_C03
ZPCA_C03H
ZABC_O02 InfoCube
InfoCube
Fin. Mgmt & Controlling - Profit Center Acct.
Fin. Mgmt & Controlling - Profit Center Acct.
PCA: Transaction data
Profit Center Accounting - Customer
0PCA_C01
ZPCA_C09
InfoCube Fin. Mgmt & Controlling - Profit Center Acct. Profit Center Accounting - Other ZPCA_C10
InfoCube Fin. Mgmt & Controlling - Profit Center Acct. Profit Center Accounting - Periodic Balance ZPCA_C05
InfoCube Fin. Mgmt & Controlling - Profit Center Acct. Profit Center Accounting - Planning Items ZPCA_C06
MultiProviders InfoCube
InfoCube
Fin. Mgmt & Controlling - Profit Center Acct.
Fin.
Cust.Mgmt & Controlling
Rel.Mgmt- - Profit Center
CRM Analytics- Acct.
Cross-Scenario
Profit Center Accounting - Summary
Profit Center Accounting - Vendor
ZPCA_C07
ZPCA_C08
0ABC_M01 or
InfoCube SAP
ERP R/3 SD Sales & Distribution Analyses -
Analytics- Billing Cube ZSD_CVF0
InfoCube SAP
ERP R/3 SD Sales & Distribution Analyses -
Analytics- Billing Cube - History ZSD_CVFH1
InfoCube SAP
ERP R/3 SD Sales & Distribution Analyses - Billing Summary
ZABC_M02
Analytics- ZSD_C17
InfoCube SAP R/3 SD Sales & Distribution Analyses -
ERP Analytics- Billing: Condition Data Cube ZSD_C06
InfoCube SAP
ERP R/3 SD Sales & Distribution Analyses -
Analytics- Billing: Tax Conditions Cube ZSD_C06C
InfoCube SAP
ERP R/3 SD Sales & Distribution Analyses -
Analytics- Daily Lift Report ZSD_ZS561
InfoCube SAP
ERP R/3 SD Sales & Distribution Analyses -
Analytics- Delivery Cube ZSD_CVL0
InfoCube SAP
ERP R/3 SD Sales & Distribution Analyses -
Analytics- Delivery Cube - History ZSD_CVLH1
InfoCube SAP R/3 SD Sales & Distribution Analyses -
ERP Analytics- PAWS: Pricing Analysis ZPAWS
InfoCube SAP
ERP R/3 SD Sales & Distribution Analyses -
Analytics- PAWS: Pricing Analysis (1) ZPAWS1
InfoCube SAP
ERP R/3 SD Sales & Distribution Analyses -
Analytics- PAWS: Pricing Analysis Archive ZPAWS2
ODS = Operational Data Store InfoCube Commercial Excellence
Strategic Enterprise Mgmt - BPS - Capital CE Pricing Log 32
ZCE_C01
InfoCube Investment Planning Capital Investment Planning ZBPS_P05
What Well Cover
Introduction
Scoping the SAP NetWeaver BI project
Getting the project started
Designing InfoCubes the good, the bad, and the ugly
Improving Performance what to do, and how to do it
Understanding the curse of MultiProviders
Cleaning up and ODS management
Considering global integration points
Wrap-up
33
Global Performance Issues
36
Tip 15: Performance Enhancements Correct Aggregates Are
Easy to Build
This example shows the benefits of aggregates by
using system statistics to generate proposals
This very large InfoCube had over 160 queries attached to
it and only one aggregate
Distribution Types
Introduction
Scoping the SAP NetWeaver BI project
Getting the project started
Designing InfoCubes the good, the bad, and the ugly
Improving Performance what to do, and how to do it
Understanding the curse of MultiProviders
Cleaning up and ODS management
Considering global integration points
Wrap-up
41
Tip 19: Avoid Swiss Army Knife MultiProviders: It Will Be Slow!
42
Tip 19: Swiss Army Knife MultiProviders and Parallel Processing
43
Tip 19: Swiss Army Knife MultiProviders and Parallel Processing
(cont.)
Consider deactivating parallel processing for those queries
that are MultiProvider queries and have large result sets
With SAP BW 3.0B SP14 (SAP BW 3.1 SP8), you can change the
default value of 30,000 rows refer to SAP Notes 629541, 622841,
607164, and 630500
A larger number of base InfoProviders is likely to result in a
scenario where there are many more base InfoProviders than
available dialog processes, resulting in limited parallel
processing and many pipelined sub-queries
44
What Well Cover
Introduction
Scoping the SAP NetWeaver BI project
Getting the project started
Designing InfoCubes the good, the bad, and the ugly
Improving Performance what to do, and how to do it
Understanding the curse of MultiProviders
Cleaning up and ODS management
Considering global integration points
Wrap-up
45
Tip 20: Clean Up Old Objects That Are No Longer Used
14
system to become a 10
replication of the 8
transaction system, 6
merely because that 4
is what your 2
developers know. 0
0-5 6-10 11-15 11-20 21-30 31-40 41-50 51-60 61-70 71-80 81-90 90+
47
Tip 22: Avoid Direct Querying of ODS
Introduction
Scoping the SAP NetWeaver BI project
Getting the project started
Designing InfoCubes the good, the bad, and the ugly
Improving Performance what to do, and how to do it
Understanding the curse of MultiProviders
Cleaning up and ODS management
Considering global integration points
Wrap-up
49
Tip 23: Be Aware of Divergent Country Accounting Rules
Introduction
Scoping the SAP NetWeaver BI project
Getting the project started
Designing InfoCubes the good, the bad, and the ugly
Improving Performance what to do, and how to do it
Understanding the curse of MultiProviders
Cleaning up and ODS management
Considering global integration points
Wrap-up
53
Resources
54
Resources (cont.)
Where
to
FIND it
55
7 Key Points to Take Home
56
Your Turn!