Professional Documents
Culture Documents
Agenda
Background
The Right Design
Agenda
Background
The Right Design
17
InfoCubes
Multicubes
ODS
1
Ledger
Within typical design parameters
Approaching recommended regular configuration parameters
Not frequently used design parameters
BW InfoCubes Observations
Infocubes
Available options
Jobcost history cube
Options sold
MH AP line item cube
MH AR line item cube
MH general ledger cube
Cost cube
MH property master (LOT) cube
Purchasing item data
Inventory cube
PS controlling MH
PS dates MH
PS controlling and dates cube
Earnest money estimation cube
MHSD overview
SD commissions cube
Record Complexity
length
Moderate Moderate
High
High
Low
Low
High
High
Low
Low
Low
Low
Low
Low
Low
Low
Low
Low
Low
Low
High
Moderate
Moderate
Low
High
Low
Moderate
High
High
High
High
High
Characteristics
BW InfoCubes Observations
Infocubes
Available options
Jobcost history cube
Options sold
MH AP line item cube
MH AR line item cube
MH general ledger cube
Cost cube
MH property master (LOT) cube
Purchasing item data
Inventory cube
PS controlling MH
PS dates MH
PS controlling and dates cube
Earnest money estimation cube
MHSD overview
SD commissions cube
Characteristics Navigational Time char- Hierarchies Dimensions Key figures Record Complexity
attributes
acteristics
length
20
4
4
2
9
4
Moderate Moderate
High
57
0
1
0
12
1
High
23
19
4
1
11
14
Low
Low
52
13
4
3
10
15
High
High
Low
29
0
4
1
8
20
Low
Low
30
2
5
6
8
9
Low
Low
14
0
3
2
8
2
Low
24
2
4
1
11
7
Low
Low
13
10
5
3
11
15
Low
Low
Low
33
4
2
3
9
23
Low
High
44
37
5
10
12
35
Moderate
Moderate
25
19
5
4
8
17
Low
High
34
48
3
5
9
30
Low
40
24
5
7
13
16
Moderate
High
High
49
28
5
7
13
27
High
High
51
22
4
4
10
21
High
Key figures
While no limitations are imposed by BW in terms of number of key
figures (measures), typical implementations contains 1 to 20 of these.
While a higher number of these may be required, there a are
significant tradeoffs of load performance when a high number records
are loaded (these are loaded with each transaction).
11
Record Length
Record length
In general, as the record length of an InfoSource increases, more data
may be populated to the InfoCube.
Since an InfoCube might have more that one InfoSource, the length of
each may be an indicator of the InfoCube growth size as the company
rolls out BW to other divisions.
You should review of the design of InfoSources with large record
lengths to determine the true need of including all the fields in the
InfoCube vs. using alternate fields i.e. short text or codes, or removing
them from the system..
Data Loads
BW Sources to InfoCubes/ODS and MultiCubes
Sources
Infocubes
Available options
Jobcost details multicube*
Jobcost history cube
Options sold
Pending close multicube (new)*
MH AP line item cube
MH AR line item cube
MH general ledger cube
General ledger line item ODS
Cost cube
MH property master (LOT) cube
Purchasing item data
Inventory cube
Inventory multicube*
PS controlling MH
PS dates MH
PS controlling and dates cube
Earnest money estimation cube
MHSD overview
SD commissions cube
Number
1
2
1
1
2
N/A
1
1
2
1
1
1
2
2
5
1
4
1
2
1
Complexity
Low
Low
High
Moderate
Low
High
Moderate
Low
High
Low
Low
Low
Moderate
Low
High
Moderate
High
Moderate
High
Moderate
Indexes
Statistics
Aggregates
Ledger
BW index diagnostic
BW diagnostic of statistics that is recommended to be updated
User designed aggregates (performance & existence)
Explore the use line item dimensions for fields that are frequently
conditioned in queries. This model change can yield faster queries
15
Validate the high-cardinality of the data and reset the flag if needed
this will give a better index type and performance
16
Since SAP BW 3.0B SP14 , you can change the default value of 30,000 rows Refer to SAP Note 629541, SAP Note 622841, SAP Note 607164, and SAP Note
630500
20
SAP suggests that this will make the maintenance is easier since
any remodeling only need to change the reference structure.
SPOs can be added to MultiProviders for simpler
query administration and to mask complexity
21
Agenda
Background
The Right Design
22
This places heavy demand on database and memory resources and may impact
other BW processes
A query read mode can be defined on an individual query or as a default for new
queries (transaction RSRT)
BENEFIT: This results in a smaller initial result set, and therefore faster
query processing and data transport as compared to a query where all
characteristics are in rows
Examine the
request status
when reading
the InfoProvider
Filters in Queries
28
29
We
Wecan
cansee
seethat
thatthe
thesystem
systemcreates
createsaayellow
yellow
flag
flagfor
forthe
the66base
basecubes
cubesininthe
theMultiProvider
MultiProvider
and
andthe
theyellow
yellowflag
flagfor
forthe
the14
14free
freechars.
chars.
34
Agenda
Background
The Right Design
37
38
Agenda
Background
The Right Design
41
Distribution Types
43
Agenda
Background
The Right Design
44
When
What
t-code
Default Flatfile
RSR_CACHE_DBS_IX
RSR_CACHE_DB_IX
Binary Large
Optional Objects (blob)
RSR_CACHE_DBS_BL
RSR_CACHE_DB_BL
Availabl
e since
BW 7.0 Blob/Cluster
SP 14
Enhanced
No central cache
directory or lock
concept (enqueue). The
mode is not available
by default.
Set
RSR_CACHE_ACTIVATE_
NEW RSADMIN
VALUE=x
Source: SAP AG 2010.
47
Agenda
Background
The Right Design
49
Architectural Drivers
1990
2010
Improvement
CPU
0.05
253.31
MIPS/$
MIPS/$
5066x
Memory
0.02
50.15
MB/$
MB/$
Addressable
Memory
216
264
Network
Speed
100
100
Mbps
Gbps
2502x
248x
1000 x
1990
2010
Disk-based data
storage
In-memory data
stores
Simple
consumption of
apps (fat client
UI, EDI)
Multi-channel
UI, high event
volume, cross
industry value
chains
Generalpurpose,
applicationagnostic
database
Applicationaware and
intelligent data
management
Disk
Data Transfer
600
MBPS
MBPS
120x
51
Information Broadcasting /
Precalculation
Query Cache
Query Cache
Aggregates
SAP BW Accelerator
InfoProvider
Query Execution
Without SAP NetWeaver
BW Accelerator
Query Execution
With SAP NetWeaver
BW Accelerator
Number of Queries
Number of Queries
Seconds
Seconds
The major
improvement is
to make query
execution more
predictable and
overall faster
54
55
56
57
Agenda
Background
The Right Design
58
59
Agenda
Background
The Right Design
60
This
Thiscustomer
customerneeded
needed
totoimprove
improvethe
the
hardware
hardwaretotoget
getthe
the
query
queryperformance
performancetoto
an
anacceptable
acceptablelevel
level
62
In this example, we see that the EarlyWatch report found many known
issues at the Oracle level that should be implemented before the
performance tuning effort started.
Before the patches were applied it took 24 to 26 minutes to execute
some queries, after the fixes, the queries ran at less then two minutes.
63
More at:
Performance tuning presentations, tutorials & articles
www.ComeritInc.Com
Questions
and
Answers
Dr. Berg
bberg@ComeritInc.Com
65