Documente Academic
Documente Profesional
Documente Cultură
1
What Well Cover
Difference between evolutionary DW architecture and a design
Data marts vs. Data warehouses
Real-time Data warehousing
The many mistakes of EDWs
Successes and failures of six large-scale SAP BI-EDWs
SAP NetWeaver BI architecture & Corporate Info. Factory (CIF)
Wrap-up
2
Evolution of Data Warehousing
Emerging
(1st generation)
Emerging Vertical approach
(1st generation) (2nd generation)
Interactive Mgmt.
reporting (OLAP, MQE)
Toolsets &
Level of Pre-delivered Content Analytical applications
accelerators
for specific industries
Source: Mike Schroeck, David Zinn and Bjarne Berg, Integrated Analytics Getting Increased Value from
Enterprise Resource Planning Systems, Data Management Review, May, 2002;
Adapted: Bjarne Berg How to Manage a BW Project, BW & Portals Conference, 2007, Miami
3
A General Conceptual Enterprise DW Architecture
Metadata
Operational Data
Source Data Extract Data Store Transform Warehouse BI Applications
Functional Area Custom
Invoicing Developed
Systems Purchasing
Applications
Purchasing Marketing
Systems Data and Sales Data
Extraction Translate Mining
Corporate
General Integration Segmented
Information Attribute
Ledger and Data Subsets
Cleansing Statistical
Processes Summation Calculate
Other Internal Programs
Systems Product Line Derive
Summarized
External Data Summarize Data Query Access
Sources Location Tools
Synchronize
UDI
SAP DB Service
JDBC XMLA ODBO Data Warehouse BAPI File XML/A
Query Connect API
Source: SAP AG
SAPs EDW Enablers - Query optimization
SAP Any
BW tool
Analytic
The SAP BI
Engine
accelerator makes
query response time
50-10,000 faster.
In NW2004s you get a new tool to add characteristics and key figures to
your model.
In older BW versions,
if you forgot to
include a field in your
infocube, the rework
was quite substantial
and often involved
reloading the
infocube as well.
10
What Well Cover
Difference between evolutionary DW architecture and a design
Data marts vs. Data warehouses
Real-time Data warehousing
The many mistakes of EDWs
Successes and failures of six large-scale SAP BI-EDWs
SAP NetWeaver BI architecture & Corporate Info. Factory (CIF)
Wrap-up
11
Design Vs. Evolution
12
ODS Vs. Data Warehouse Vs. Data Marts
To Understand the differences between DSO, Data Warehouses and Data Marts we
can examine them in terms of usage, modeling and purpose:
Identifying and defining data from many different sources creates opportunities for
users and sponsoring departments to disagree. The ultimate business goals may be
overshadowed by the technical and political difficulties of building the large
warehouse. Starting small with a data mart, experimenting, and using the
implementation as a learning experience, will reduce the risk and may actually result
in a higher quality deliverable.
16
Major Risks of building the Data Marts first
Data marts do not replace data warehouses.
The data mart is not the next step in data warehouse evolution. It must
be planned and implemented as part of the overall architectural vision.
To be effective, you must maintain centralized control of data distribution
to the mart in order to support the enterprises overarching warehouse
goals of data quality, consolidation, and sharing.
Data marts also increase the complexity of the data warehouse
environment with multiple extract, transform, and transfer routines.
The bottom line is plan and build a reusable data and technical
foundation (technology standards, data modeling principles, and
integrated databases).
20
Real-time SAP Enterprise Data warehousing gets better
NW 2004s has more features for updates that does not follow the
typical asynchronomous (batch) updates. This include:
21
Limitations of Real-time SAP Enterprise Data warehousing
There are some limitations depending on the version of SAP BI/BW you
use. For versions 3.5 and higher, there are few limitations and they
include:
You can only use real-time to load ODSs or PSA
A normal delta update and a real-time update cannot happen at the
same time for the same DataSource and/or ODS
For data targets that subsequently store the real-time-supported ODS
objects, real time data transfer cannot be used
InfoPackages that use real-time updates cannot be associated with
InfoPackage Groups or Process Chains
23
Common EDW Mistakes Not Using Standard SAP Solutions
In the 1950s, you could buy a standard Sears house for $2,065 and pay
$935 more to have it implemented on your own land
The customers who selected to buy
the standard house were either
extremely happy or totally
disappointed.
Customizing lower
level objects will cause
Cockpits
Workbooks 2,211
???
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
Calendar day
LEGEND
Map functional requirements to
the standard content before Delivered in standard extractors
Delivered in LO extractor
you make enhancements Not in delivered Content -but in R-3 26
Common EDW Mistakes No Tailored Approach
TOP-DOWN APPROACH BOTTOM-UP APPROACH
CONTINUE
CHANGE
Build a global data warehouse Focus on a bottom-up approach where
for the company, and proceed the BW project will prioritize supporting
sourcing data from old legacy and delivering local BW solutions,
systems driven from a top- thereby setting the actual establishment
down approach. of the global Data Warehouse as
secondary, BUT not forgotten.
AA Z0986 Query
28
Common EDW Mistakes Lack of environment management
As a result, their
architecture often looks
like mix-and-match of
systems that was
acquired to put out
urgent needs.
In these organizations,
multiple portals are
common and overlapping EDWs are like marriages between IT and
reporting systems is the Business. You have to work at it constantly,
rule, not the exception. give it attention, and be faithful to the solution.
29
Common EDW Mistakes lack of transport controls
32
SAP EDW in 6 large Companies - Overview
33
SAP as the EDW in an Insurance Company
Organization Company 1
Industry Insurance Go-live Year: 2003 (BW v. 3.0b)
System BW 3.5
Number of Executive Users* 25
Number of Casual users* 952 Mistakes Made: Under estimated the time it would
take to get the staff up to speed and trained in
Number of Power users* 34
Number of non-SAP sources 6
Number of SAP sources
EDW data content (0-100%)**
31
80%
BW. Had no SAP web skills in-house and went
Lessons learned "Start with content with the wrong portal choice (non-SAP)
in finance and do
few enhancements
in the beginning"
Successes: Built foundation data stores first (AP,
AR, GL, etc. before we started the individual
Overall satisfaction*** 7
BI Accelerator and department needs. This created a real EDW
Future Plans
web cockpits
foundation instead of data marts. Now we are
* = actual users logged in within a 30 days period building more multiproviders and fewer new
data stores. Because we built the EDW first, we
** = estimated % of org. reporting done with EDW data
*** = Scale 1 to 9 (9 being highest and 5 being neutral)
Next Steps: Add more Technology Challenges: Data integration was the
functionality (purchasing) hardest. We had to spend most of our project
and rollout to purchasing time on masterdata mapping & consolidation.
group and the sales reps. 37
SAP as the EDW in a High-Tech Company
Go-live Year: 2003 (BW v. 3.1c)
Organization Company 5
Industry High-Tech
System BW 3.5
Number of Executive Users* 42
Number of Casual users*
Number of Power users*
1,122
89
Mistakes Made: User interface was not prioritized
Number of non-SAP sources 13 high enough. Executives and casual users
Number of SAP sources 144 hated BEx workbooks. We had to relauch the
EDW data content (0-100%)** 50%
Lessons learned "Users look at the EDW in 2006 with a new web interface.
query tools &
don't care about
the EDW. Use
web tools"
Successes: After the relaunch we have had success
with user adaptation and have a functional
Overall satisfaction*** 7 steering committee and CFO sponsorship.
Rollout and add
subsidiarie's Closing the financial books have gone from 5
Future Plans content days to 3.
* = actual users logged in within a 30 days period
** = estimated % of org. reporting done with EDW data
*** = Scale 1 to 9 (9 being highest and 5 being neutral)
Technology Challenges: Was unsure on how to
interface our existing portal with SAP BI
Next Steps: Add 2 more content (SSO). Security setup was hard and
acquired companies to advise was too divergent. Process chains ran
SAP R/3 and BI. very slow until we tuned the ABAP.
38
SAP as the EDW in a Government Organization
Go-live Year: 2005 (BW v. 3.5)
Organization Company 6
Industry Gov.
System BI 7.0
Number of Executive Users* 6
Number of Casual users*
Number of Power users*
409
7
Mistakes Made: Source data was in too many diverse
Number of non-SAP sources 24 old system with no real standards. We under
Number of SAP sources
EDW data content (0-100%)** 30%
9
estimated the time it would take in integrate
Lessons learned "Data integration is nine different mainframes, some that was 20+
70% of the project.
Look at source
years old. Should not used a big-bang go-live.
systems early"
40
The Corporate Information Factory (CIF)
In 2001, Bill Inmon (the father of DW) and Claudia Imhoff
proposed a reporting architecture known as the CIF.
At the heart CIFs reporting strategy
is the EDW. It is the source of:
SOA / WS
Distributed
2. Consolidates the
platform TCO =
Cost of Applications
SAP NetWeaver
2008
3. Simplifies the
platforms for
web access, security,
reporting and analysis. CIF provides a corporate framework for the EDW;
NetWeaver provides the capabilities to do so with
one platform
Solution 42
SAPs Conceptual Enterprise Data Warehouse Architecture
SAP recognizes that we do not build EDWs, we are doing Enterprise
Data warehousing. This is an on-going activity that merges information
systems, people and processes.
Knowledge Management
Information
Content Management
Integration
Consolidation
and Reporting
Plan/Forecast
Modeling and
Ad Hoc Query
Optimization
Scorecard
Reporting
Statutory
Balanced
Budget
People
Integration
Process
Integration
44
Resources
45
7 Key Points to Take Home
Plan Your Target EDW Architecture before you start the project.
Enforce Standards and pick the right tools for the job
SAP BI has many new tools that will enhance the front-end for end
users. Your EDW will need them