Introduction to SAP BW

Confidential

Content

1.
1. SAP
SAP BW
BW Overview
Overview

2.
2. Multi
Multi Dimensional
Dimensional Modeling
Modeling in
in SAP
SAP BW
BW

3.
3. Administrator
Administrator Workbench
Workbench

4.
4. Common
Common Object
Object in
in SAP
SAP BW
BW

Confidential

Content

1.
1. SAP
SAP BW
BW Overview
Overview
2. Multi Dimensional Modeling in SAP BW
3. Administrator Workbench
4. Common Object in SAP BW

Confidential

1.1 R/3 Analytical Reporting Evolution

2006
1998

Release of Business Information Warehouse

(BW)

1996

BAPIs enable 3rd party presentation tools

to access OIW data

1995

Open Information Warehouse - the integration

framework for the different Information Systems (xIS)

1993
1992

Page 4

Release of SAP NetWeaver

Business Intelligence

Release of Information Systems (xIS) for Financials,

Logistics, Human Resources and Executive Environment
Launch of the R/3 Business Application Software

Confidential

1.1 R/3 Analytical Reporting Evolution

Open Information Warehouse

Logistics
IS

Controlling
IS

Financial
IS

Human Res.
IS

Enterprise
IS

Logistics

Controlling

Finance

Human
Resources

Enterprise
Controlling

SAP - R/3
Page 5

Confidential

1.1 R/3 Analytical Reporting Evolution

Pros
Standard structures delivered with the system
Limited OLAP capabilities and drill-down to transaction level and
documents
Security in Standard Analysis
Exception reporting

Cons
Limited number of dimensions and
Use of many structures (or high volumes) impact performance
Standard Information Structures not always usable
Level of effort to create and test Info Structures
Security in Flexible Analysis is weak

Page 6

Confidential

1.2 BW Overview and Concepts

BW is SAPs entry into the Data Warehousing market. It is

designed to provide corporate reporting and Data
Warehousing solutions for SAP customers

BW is an end-to-end data warehousing solution that uses

preexisting SAP technologies.

BW is part of the strategic initiatives of SAP New Dimension Products and Business Framework

BW is SAPs answer to the limitations (product gaps) of the

prior R/3 reporting Information Systems

BW is dynamic evolving product: BW Version started from 1.2

A and now the latest version is NetWeaver BI 7.40

Page 7

Confidential

1.3 What is Data Warehousing ?

Data Warehouse can:

Pool data from different, mostly heterogenous sources
Overcome this heterogeneity on different levels (system, schema, and data)
Stage data in the form required by the user

What we expect from Data Warehouse:

Standardized structuring and presentation of all company information
An easy-to-use, single-point of access to all company information
Sophisticated business reporting methods for self-service analysis at all levels
Fast and cost-effective installation
A high performance environment
Data staging from heterogeneous environment
Release of source systems and IT organization
Data access that is independent of the source system
Analysis of data over a specific period of time, and the storage of historical
information (time-dependent master data)

Page 8

Confidential

1.3 What is Data Warehousing ?

Differences between OLTP and OLAP

Page 9

Confidential

1.3 What is Data Warehousing ?

Page 10

Confidential

1.4 SAP Business Warehouse Architecture

The SAP BW allows you to analyze data from operational SAP

R/3 applications or any other business application. You can
also extract and analyze data from external sources.

The system (data storage, loading, and reporting), which is

preconfigured by Business Content for core areas and
processes , allows you to examine the relationships in every
area of your company.

Page 11

Confidential

1.4 SAP Business Warehouse Architecture

Page 12

Confidential

1.5 BW Standard Business Content:

BW Standard Business Content: is delivered by SAP

One of the BW's strongest selling points is its Business

Content.

Business Content is a complete set of BW objects developed

by SAP based on predefined business roles to support the
OLAP tasks.

It contains roles, workbooks, queries, InfoCubes, key figures,

characteristics, update rules, InfoSources, and extractors for
SAP R/3, and other mySAP solutions.

Page 13

Confidential

1.5 BW Standard Business Content:

Supported R/3 Modules

BW includes standard business content for R/3

Financials and Controlling
Logistics (SD, MM, PP)
Human Resources
Asset Management
Plant Maintenance
Service Management
Quality Management
Project Systems

Page 14

Confidential

1.3 BW Standard Business Content:

Supported Module Details

Financials
Accounts Receivable

Accounts Payable

General Ledger

Special Ledger

Controlling
Profitability Analysis

Product Costing

Overhead Management

Profit Center Account

Logistics
Sales & Distribution
Inventory Management

Purchasing

Warehouse Management

Manufact.Req. Plan

Human Resources
Personnel Admin.
Time Management
Payroll

Page 15

Confidential

1.5 BW Standard Business Content:

SAPs Strategy
SD

MM

PP

Sales &
Dist.

Service
Mgmt.

QM

Quality
Mgmt.

PM

Plant
Maint.

SAP
SAP BI
BI
WM

Warehouse
Mgmt.

BW

Audit

SAP B2B
Procurement

Tax

SAP
SAP SCM
SCM
SAP APO

Management
Cockpit

PS

Project
Systems.

CO

Controlling

SAP Marketing SAP Service

Info DB
SAP
Strategic
Enterprise
Management

SM

Financial
Acct.

SAP
SAP CRM
CRM

Materials
Mgmt.

Production
Plan

FI

SAP Sales

SAP Logistics
Execution
System

Tech

HR
Human
Resources

SAP projects new applications will account for more than

30% of its business by 2001.
Forrester, Packaged Applications Strategies, vol 3 # 14, Nov 30, 1998

Page 16

Confidential

Content

1. SAP BW Overview

2.
2. Multi
Multi Dimensional
Dimensional Modeling
Modeling in
in SAP
SAP BW
BW
3. Administrator Workbench
4. Common Object in SAP BW

17

Confidential

2.1 Classic Star Schema

Page 18

Multi-dimensional data models are needed for the creation of

data warehousing or OLAP applications, in other words, for
analytical applications. The classic star schema is the most
frequently used multi-dimensional model for relational
databases. This database schema classifies two groups of
data: facts (sales or quantity, for example) and
dimension attributes (customer, material, time, for
example)

Confidential

2.1 Classic Star Schema

Page 19

Confidential

2.2 SAP BW Star Schema

The multi-dimensional model in SAP BW is based on the SAP

BW star schema, which was developed as an enhanced
(refined) star schema as a response to problems experienced
with the classic star schema.

In the SAP BW- star schema, the distinction is made between

two self-contained areas:
InfoCube
Master Data Tables/Surrogate ID (SID-) Tables

Page 20

Confidential

2.2 SAP BW Star Schema

Page 21

Confidential

2.2 SAP BW Star Schema

Page 22

Confidential

2.2 SAP BW Star Schema

InfoCubes are the central objects of the multi-dimensional model in

SAP BW. Reports and analyses are based on these. From a reporting
perspective, an InfoCube describes a self-contained data set within a
business area, for which you can define queries.

An InfoCube (BasisCube) consists of a number of relational tables

that are combined on a multi-dimensional basis. In other words, it
consists of a central fact table and several surrounding
dimension tables.

Master data information is stored in separate tables, that is

independent of InfoCube, in what are called master data tables
(separately for attributes, texts and hierarchies)

Master data contain the following type:

Attribute
Text
Hierarchy

Page 23

Confidential

2.2 SAP BW Star Schema

Page 24

Connecting Master Data Tables to an Info Cube

Confidential

2.2 SAP BW Star Schema

Page 25

Info cube-Independent use of Master Data

Confidential

2.2 SAP BW Star Schema

Advantages and Disadvantages of the Classic Star

Schema
Advantages:
Data access runs performantly due to the small number of join
operations (there are only join operations between the fact tables
and the involved dimension tables).
Disadvantages:
Redundant entries exist in the dimension tables
In contrast to the historization of fact data (the time reference is
given implicitly via the time dimension table), historization of
dimensions ( slowly changing dimension) is not easy to model.
The multi-lingual capability is cumbersome.
Modeling some hierarchy types (parallel and imbalanced hierarchies
for example) in a dimension can lead to anomalies.
Query performance is also made worse, since aggregates and Basis
fact data are stored in the same table (fact table).

Page 26

Confidential

2.2 SAP BW Star Schema

Advantages of the SAP BW Star Schema

The use of automatically generated INT4 keys I (SID keys, DIMID keys)
enables faster access to data than via long alpha-numeric keys. Thanks to
the excavation of master data from the dimension tables using the SID
technique, the following modeling possibilities exist :
Historizing dimensions
Multi-lingual capability
Cross-InfoCube use of master data ( shared dimensions)
The query performance is improved here as aggregated key figures can
be stored in their own fact tables.

Page 27

Confidential

Content

1. SAP BW Overview
2. Multi Dimensional Modeling in SAP BW

3.
3. Administrator
Administrator Workbench
Workbench
4. Object in SAP BW

28

Confidential

3. Administrator Workbench

The AWB is the primary administration-, control-, and

monitoring tool in BW, and so is the data warehouse manager
of SAP BW. You can use AWB to manage, control and monitor
all relevant objects and processes in SAP BW. As well as
defining all relevant meta objects, you can also use the AWB
to plan load processes using a scheduler, and monitor them
using a monitor. Assistants can be used to analyze the load
process comprehensively. These can especially help you to
find the cause of any errors very quickly.

T-code for Administration Workbench RSA1

Page 29

Confidential

3. Administrator Workbench

Page 30

Confidential

3. Administrator Workbench

Tcode RSA1 will take us to modeling section of administration workbench

Page 31

Confidential

Content

1. SAP BW Overview
2. Multi Dimensional Modeling in SAP BW
3. Administrator Workbench

4.
4. Common
Common Object
Object in
in SAP
SAP BW
BW

32

Confidential

4.1 Common Object in SAP BW

Below is list of common object that used in SAP BW :

Info

Info

Info

Info

Object
Characteristic
Key Figure
Object Catalog
Use to group the info object (same like folder)
Source
Transfer rule
Transfer structure
Communication Structure
Area

Use to manage the object in SAP BW (same like folder)

Data Store Object (DSO)
Detail level of Data Store like flat table in SAP
Info Cube
Multi Dimensional Table
Update Rule specifies how data will be updated into their targets

Page 33

Confidential

4.1 Common Object in SAP BW

Get Familiar with the icon in SAP BW

Info Area

is folder like. It uses to manage all the component in SAP BW.

Info Object Catalog. It uses to manage the info object. It is divided into 2
types:
Characteristic Info Object Catalog: uses to store and manage all the
characteristic Info object
Key Figure Info Object Catalog: Uses to store and manage all the key
figure info object.

Info Object: Its the smallest object in SAP BW that can store data. Its divided
into 2 types:
Characteristic: it store all the business element. Such as: Employee NIP,
Company code, Calendar day, etc
Key Figure: uses to store the measurement of a data. Such as: Amount and
Quantity

Page 34

Confidential

4.1 Common Object in SAP BW

Get Familiar with the icon in SAP BW (Cont.)

Info Source

is a quantity of information that logically belongs together,

summarized into a single unit. It prepares consolidated data for updating to the data
targets. Info Sources contain either transaction data or master data (attributes, texts
and hierarchies).
Transfer Structure is the structure in which the data is transported from the
source system into the SAP Business Information Warehouse
Communication Structure is the structure underlying the InfoSource
Transfer Rule uses to determine how you want the transfer structure fields to be
assigned to the communication structure InfoObjects. You can arrange for a 1:1
assignment. You can also fill InfoObjects using routines, formulas, or constants.

Data Store Object (DSO)

is a BW architectural component located between

PSA and InfoCubes that allows BEx reporting. It is not based on the star schema and is
used primarily for detail reporting, rather than for dimensional analysis.

Info Cube
Page 35

is a fact table and its associated dimension tables in the star schema.

Confidential

4.1 Common Object in SAP BW

Info Object
InfoObjects are the smallest available information modules (= fields) In SAP BW:
These can be uniquely identified with their technical name.
As components of the Metadata Repository, InfoObjects contain the technical and
specialist information for master- and transaction data in SAP BW.
InfoObjects are used throughout the system to create structures and tables. These
enable information to be modeled in a structured form in SAP BW.
InfoObjects are used for the definition of reports, to evaluate master- and
transaction data.

InfoObjects are divided into the following classes:

Key Figure
Key figure InfoObjects provide the values to be evaluated.
Examples:
Quantity ( 0QUANTITY)
Amount (0AMOUNT)

Page 36

Confidential

4.1 Common Object in SAP BW

InfoObjects are divided into the following classes (cont.):

Characteristic
Characteristic InfoObjects are business reference objects, which are used to analyze key

figures..
Examples:
Cost center (0COSTCENTER)
Material (0MATERIAL)

Time Characteristics
Time characteristics form the time reference frame for many data analyses and

evaluations. They are delivered with Business Content. It it not possible to define your
own time characteristics.
Examples:
Time characteristic with the largest granularity: Calendar Day (0CALDAY)
Time characteristic with the smallest granularity: Calendar Year (0CALYEAR) or Fiscal Year
(0FISCYEAR).

Units
Unit InfoObjects can be specified alongside the key figures. They enable key figure values

to be partnered with their corresponding units in evaluations.

Examples:
Currency unit ( 0CURRENCY)
Value unit ( 0UNIT)

Page 37

Confidential

4.1 Common Object in SAP BW

InfoObjects are divided into the following classes (cont.):

Technical Characteristics
These characteristics have an organizatorial function within SAP BW.
Examples:
Request ID (0REQUID)
Change ID (0CHNGID)

InfoObject 0REQUID delivers the numbers the system allocates when loading
requests; InfoObject 0CHNGID delivers the numbers allocated during
aggregate change runs.

Page 38

Confidential

4.1 Common Object in SAP BW

Info Provider
An InfoProvider is an object for which queries can be created or executed in BEx.
InfoProviders are physical objects or sometimes logical views that are relevant
for reporting.

InfoCubes
InfoCubes are the primary objects used to support BI queries. They are designed to
store summarized and aggregated data, for long periods of time. Your goal in
designing a warehouse is to ensure that most queries initially target this type of
database object

DataStore Object
DataStore objects are another primary physical database storage object used in BI.
They are designed to store very detailed (transaction level) records.

Page 39

Confidential

4.2 Integration of Info Provider in SAP BW

Page 40

Confidential

4.3 ABAP use

ABAP use for BW focus from report creation to data

preparation and preprocessing functions during ETL process
in BW

Six places during extraction, including creating custom

DataSources, enhancing DataSources, and data selection in
InfoPackages

Six places during staging, including currency/units of measure

conversions, transfer routines, and update rules

Four places during reporting, including generating systementered variables and the report/report interface

Also used at Open Hub Service transformations, building

authorization values, process chains, and virtual InfoCubes
with services.

Page 41

Confidential

41

4.3 ABAP use

Page 42

Confidential

42

Content

Any Questions ?

43

Confidential