Professional Documents
Culture Documents
To print: Select File and then Print from your browser's menu
--------------------------------------------------------------
This story was printed from CNETAsia.
--------------------------------------------------------------
You're familiar with the rationale behind business information (BI) warehousing, and there's no question that it will greatly enhance your
enterprise business performance. But if your ERP world is SAP R/3, a BI warehouse may be closer than you think.
Understand that you don't have to make SAP BW your warehousing software if you're running SAP R/3. Nor do you have to be running SAP
R/3 to run SAP BW; it's standalone, and you can run it on top of anything, including Oracle.
Right away you're ahead of the game with SAP BW. The tasks above are facilitated by SAP BW's integrated architecture, which provides
utilities for metadata services and Extract-Transform-Load (ETL). You also have an Administrator Workbench, which facilitates data
modeling, testing, reporting, and monitoring of your warehouse.
Within ETL services, SAP BW provides you with a staging engine for managing the transport of data into the warehouse from diverse
sources. This engine will do all the required massaging of inbound data. It also gives you a DataSource Manager for managing the different
interfaces required for importing data from both SAP and non-SAP sources (these can include XML and DB Connect interfaces, along with
file interfaces and SAP-based APIs).
In short, SAP BW is designed to give you one-stop shopping. These implementation/development tools are complemented with the SAP suite
of process development features, described below.
Multilayered architecture
Understanding the highly refined and integrated nature of data culled from data warehouses for business information analytics, SAP BW
creates a layered architecture that applies physical, logical, and business-level services to stored data in a manner that is at once efficient and
flexible. As you might guess, it's extremely hard to achieve this when building from scratch. The layers include, from start to finish:
● ETL Services
● Storage Services
● Analysis and Access Services
● Presentation Services
Necessarily integrated into each of these layers are the Administrative Services and Metadata Services.
This style of architecture is fairly typical of data warehouses in general. It's particularly well implemented for SAP BW because of the Web
Application Services fringe benefits, which include interfaces for various operating systems and databases, integration with third-party portal
infrastructures, heavy Java support, and full support for open protocols (HTTP, HTML, XML, SOAP and others)—all of which accrue to
SAP BW. Consider the advantages in making your warehouse available via the Internet.
You'll need to rely on users in various departments to develop the analytics that will deliver reliable metrics for performance at their level
(and you'll ultimately base companywide performance monitoring on these lower-level metrics). The problem is they'll define it as they go—
it won't happen overnight. On the other hand, their analyses will grow better and better over time.
In such an iterative process, your best friend is a set of analytical and presentation tools that accepts a wide range of data structures and offers
a wide range of query, processing, and report interface options.
OLAP
Online analytical processing (OLAP), the core of any data warehouse analysis capability, is complemented in SAP BW by a high-efficiency
query repository that defines and stores all queries, regardless of presentation source, for ready access by the OLAP engine. This metadata
repository speeds data reads and collation and helps you optimize warehouse performance, particularly in a high-volume user environment.
Report-to-Report interface
This is the true gem in SAP BW and may be a decision driver for you. The Report-to-Report Interface (RRI) enables you to jump from query
to query. This means you can link information together by context. This is a tremendous time-saver and organizational tool for end users.
How does it work? Analysis paths can be linked to receiver objects or other queries. But a receiver object can also be a SAP transaction, a
Web application, even a remote Web link. You can use this mechanism to do Web navigation, to dump information into a report you're
compiling, to build case studies—there is almost no limit to the flexibility of this feature. And the power it gives your data warehouse in
servicing users and customers via the Internet is obvious.
You'll have to hit the books to fully strategize how to make SAP BW work best in your house, but as an enterprise-driven business
intelligence framework, it is worthy of candidacy in your list of data warehouse possibilities.