You are on page 1of 57

SAP Business Warehouse

Training Program

Course I Objectives
Describe the architecture and advantages of using BW
Get familiar with BW terminology
Manage Meta Data and define new Info Objects, Data
Sources and Info Sources
Create Transfer Rules and Update Rules

Create Info Cubes and ODS Objects


Concept of Business Content / Activating the Business Content
Schedule and Monitor Data Loads
Create and Execute Queries in BEX Analyzer

Slide 2

Scenario

Aggregates

Queries

ODS
Object

Authorizations

GR##CUBE1

Rules

Update

Rules

Texts

BCT InfoSource
0CO_OM_CCA_1
Comm.

Hierar chies

Attribs

InfoObject
COSTC##
13-Figure
Transfer Routine

Master Data
InfoSource
COSTC##

Struct .

Comm.

Struct .

Comm.

Update

Rules

InfoSource
GR##ISCCA
Struct .

Comm.

Struct .

Transfer Rules

Transfer Rules

Transfer Rules

Transfer Rules

Transfer

Struct .

Transfer

Struct .

Transfer

Transfer

Transfer

Struct .

Transfer

Struct .

Extract
COSP

Struct .
COSS

SAP
Source
System

Extract
CSKS

Struct .
CSKT

Generic
DataSource

Business Content
DataSource

Update

InfoObject
AMOUNT##

BW System

Struct .

Struct .

Texts

Hierarchies
Attributes

Cost Accounting
Transaction
Data

External Data

Slide 3

BW Architecture
Business Information Warehouse Architecture

Client

RFC

BW SERVER

Business Explorer
OLAP
Processor

InfoCubes

BAPI

ODS

InfoCubes

Metadata Repository
Master Data

Administrator Workbench

BAPI

Source
S ystems :
Components

Slide 4

Multi Dimensional Data Model


Data Modeling
l

for the Data Warehouse

The aim of a multidimensional data model:


n

A data model that provides users with information


corresponding to his or her business processes, meaning a
data model that allows users to look at his or her performance
indicators from the point of view of how these key figures
influence the company.

Slide 5

Entity Relationship Model (ERM)


Basic
Modeling
Steps
(I)
The Entity
Relationship
Model

(ERM)

An entity relationship model allows you to better understand the


structure of the business processes in your source systems
The following steps are involved in developing an ERM:
l

Determine the entities that belong to a process your basic business terms

Determine the relationships between these entities

Determine information about the attributes for each entity

Determine the degree of

normalization

Slide 6

ERM - Strong Entities


ERM:

Strong

Entities

Customer

Material

Sales Person

Relationships Key:
1:1
1:n
n:m

Slide 7

ERM Relationships between Entities

ERM: Relationships Between Entities

Material Group

Sales
Organization

Customer
Material

Sales
Person

Sales
Transaction
Intersection Entity

Slide 8

ERM Attributes and Normalization


ERM: Attributes and

Normalization
Attributes of the
Strong Entities

Normalization

Material Group
Sales Org.Location

Region
City

Color

Material Type

Customer

Material

Sales Org.
Sales Person

Price
Transaction
l
l
l
l
l
l
l
l
l
l

Date
Sales Order #
Sales Order Item #
Sales Document #
Customer #
Material #
Sales Person #
Amount
Quantity
Currency

STRONG ENTITIES

Intersection Entity
n Normalization means that information about regions and cities is not stored with the information in the sales transactional table.
This would mean that the information about a customers region and city would have to be repeated each time the customer placed
a new order for a product. Instead, the relevant region appears in the city table and the city appears on the customer table. Other examples
of normalization are also shown.
Slide 9

Multi Dimensional Model


The Multidimensional Model (MDM)

MDM
Sales Area

Material ID

ID

Material Name
Material Type
Material Group

Sales Person
Sales Organization

Sales Area Dimension

Sales Order Data


Material ID
Sales Area
Time ID
Customer ID

Customer ID
Customer Name
City
Region
Office Name

Material Dimension
ID

Dimension
Keys
Time ID

Sales Quantity
Quantity
Unit Price

Year
Fiscal Year
Quarter
Month
Day of the Week

Facts
Customer Dimension
Time
Dimension

Slide 10

ERM to MDM
From ERM to MDM
Aim of the MDM: To focus on analytical needs without
complicating the data model unnecessarily
Material Group
Sales Org. Location

Region

Color

City

Customer

Sales Org.

Material Type

Material

Sales Person

Price

Sales Order

Entity Relationship Model

Sales Area

ID

Material ID

Sales Person
Sales Org.
Sales Area
Dimension
Customer ID
Customer Name
City
Region

Material Name
Material Type
Material Group
Material ID
Sales Area
ID
Time ID
Customer ID
Amount
Quantity
Price

Fact Table

Material Dimension
Time ID
Year
Fiscal Year
Quarter
Month
Day

Customer Dimension
Time Dimension

Multidimensional Data Model

Slide 11

9 points to remember..always
The nine crucial points ...
... in a comprehensive database concept for a data warehouse*
1.

The basic business processes and the identity of facts in the fact
table (a fact table - an InfoCube) ->
Intersection entities

2.

The dimensions for each fact table ->

3.

The dimension attributes with complete descriptions and proper


terminology ->
Attributes of the entities

4.

The granularity (level of detail) of each fact table

5.

The facts, including pre-calculated facts

6.

The tracking options for historical data ->


change slowly

7.

The aggregations, heterogeneous dimensions, mini-dimensions,


query modes, and other decisions about the physical storage of
data

8.

The life-span of the database (archiving aspects)

9.

The time frame in which data is extracted and loaded into the
data warehouse

Strong

entities

Dimensions that

*Ralph Kimball

Slide 12

Star Schema Properties


Star Schema Properties

One process is

A star schema
optimizes
storage of data for reporting
purposes

modeled

at a time

Characteristics are structured


together in related branches
called dimensions

The key figures and other


calculations form the facts

This structure is identical for all


application areas

the
Dimension 2
Dimension 1

Dimension 3

Facts

Dimension n

Dimension 4

Slide 13

Data Model Example


Example: Sales - Data Model

Who have we sold to?

What have we sold?

Who sold it?

How much have we sold?

Who were our competitors?

When have we sold?

Material
Dimension
Customer
Dimension

Sales Area
Dimension

Quantities
Revenues
Costs

Time Dimension

Competition
Dimension

Slide 14

Dimension Tables
Dimension Tables

Dimension tables are groupings of related characteristics.

A dimension table contains a generated primary key and


characteristics.

The keys of the dimension tables are interpreted as foreign keys in


the fact table.

Customer Dimension
C

Customer #

Region

13970522

West

...

Material Dimension
M

Material #

Material

2101004

Screens

Grp

Time Dimension

...

Period

Fiscal Year

10

1999

...

Slide 15

Example : Sales Dimension


Example: Sales - Dimensions

Customer Dimension

Material Dimension

Time Dimension

Customer number

Material number

Calendar day

Customer name

Material description

Calendar year / week

Customer category

Division

Calendar year / month

Customer subcategory

Industry

Fiscal year

Industry key

Material type

Fiscal year / period

Business partner

Material group

Fiscal year variant

Address

Category

Location

Subcategory

Postcode

Manufacturer

State

Manufacturer part number

Country

Market key

Region

Price class

Currency

Valuation class

VAT #
Incoterms
Price group
Account assignment group
Delivering plant
Customer classification
Customer market
Customer statistics group

Slide 16

Fact Tables
Fact Tables
l

Central intersection entities, meaning N:M relationships between


strong entities, are converted into fact tables

The individual data records in the fact table are identified uniquely
by the keys of the dimension tables

The fact table is maintained when transaction data is loaded

Fact tables have a relatively small number of columns (key figures)


and a large number of rows

Fact Tables
M C

Quantity

Sales

Cred .Memos

Open Orders

250

$ 500,000

$ 50,000

$ 280,000

50

$ 100,000

$ 7,500

$ 60,000

...

Slide 17

Example Sales facts


Example: Sales - Facts

Facts
Quantity of incoming orders
Value of incoming orders
Sales quantity
Sales
Quantity of open orders
Value of open orders
Quantity of returns
Returns receipt value
Credit memo quantity
Credit memo
List price
Discount
Invoice price

Slide 18

Star Schema
Star Schema
l

The combination of fact tables and dimension tables is


called a star schema.
Customer Dimension
C

Customer #
13970522

Quantity

Region

West

...

Sales

CreditMemos

250

$ 500,000

$ 50,000

$ 280,000

50

$ 100,000

$ 7,500

$ 60,000

Open Orders

...

Fact Table
M

Material #

Material

2101004

Screens

Material D

imension

Grp

...

Period
10

Fiscal Year
1999

...
...

Time Dimension

Slide 19

Example Sales Star Schema


Example: Sales - Star Schema
Material Dimension
Material number

Customer Dimension

Material description

Customer number

Division

Customer name

Industry

Customer category
Customer subcategory
Industry key

Material type

Facts

Material type
Customer

Business partner
Address
Location

Subcategory

Time

Manufacturer

Quantity of incoming orders

State

Value of incoming orders

Region
Currency
VAT #

Category

Material

Postcode
Country

Material group

Sales quantity

Manufacturer part number


Market key
Price class
Valuation class

Sales
Quantity of open orders

Incoterms

Value of open orders

Price group

Quantity of returns

Account assignment group

Returns receipt value

Delivering plant

Credit memo quantity

Customer classification

Credit memo

Calendar day

List price

Calendar year / week

Discount

Calendar year / month

Invoice price

Fiscal year

Customer market
Customer statistics group

Time Dimension

Fiscal year / period


Fiscal year variant

Slide 20

The Terminology - differences


Differences in Terminology

Basic Star Schema

BW Star Schema

Fact

Key Figure

Fact Table

Fact Table

(Dimension) Attribute

Characteristic
Navigation Attribute
Display Attribute
(External) Hierarchy

Dimension (Table)

Dimension Table
Attribute Table
Text Table
Hierarchy Table
(SID Table)

Slide 21

Meta Data Types of Data in BW


Different Types of Data in BW

InfoObjects:
Transaction
Data

Key Figures:
Amount
Quantity

InfoCubes

Number
...

Master
Data

Characteristics:
Cost Center

ODS

ControllingArea

PSA

Cost Element
...

Attributes
Texts

Hierarchies

Slide 22

What is an Info Object ?


What is an InfoObject?
l

The various OLTP data models are unified in BW

Business objects / data elements become InfoObjects

R/3
OLTP

CO
Controlling
Controlling

HR
Human
Human
Resources
Resources

BW Extractor

Table of cost
COST

centers
...

DataSource
for
Cost Center

InfoObject
0COSTCENTER

Table of employees
EMPLO

COST_CENTER ...

InfoObjects are unique across


different application components

Slide 23

Types of Info Objects

Characteristics: Evaluation groups such as cost center


product group , and material
n

Discrete values are stored in each master data table


(for example, the characteristic
r egion has the values
South , and so on )
Special types of characteristic:

w
w
l

North ,

Time-characteristics like

f iscal year and calendar year

Unit-characteristics including currencies and units of


measure such as
or Kg .
l ocal currency (DEM)

Key figures: Continually updated numerical fields such as


amounts and quantities (for example,
revenue and s ales
quantity )

Slide 24

Creating Info Objects - Characteristic


Creating a Characteristic
Characteristic

COSTC##

LongDescrptn

Cost Center

ShortDescrptn

CostCntr

Version
Object Status

New
Inactive, non-executable

General

(13-Figure)
With hierarchies?
Version-dependent?
Time-dependent?
Intervals allowed?

(13-Fig.)

BEx MasterData

/ Txt

Hierarchy

Attributes

Compound

Higher-Level InfoObjects

Data Type
Length
Conversion
Routine

CHAR-sequence
13
ALPHA

Transfer Routine
X

With master data?


With text?
Text length?
Language-dependent?
Time-dependent?

List of associated
InfoObjects display or navigation?

Display parameters
BEx Map

Transfer routine
available

Slide 25

Texts
Texts
Texts for characteristic: COSTC##
Cost Center

Texts

Master
Data / Texts

EXT0000001200

Cost Center
Short Text (20)

Cafe

Medium Text (40)

Cafeteria

Long Text (60)

Cafeteria

Language-dependent

Time-dependent

from 01.01.1994 to 31.12.9999

You can choose short, medium, and long texts for each characteristic.

Texts can be language-dependent.

Texts can be time-dependent.

Slide 26

Navigation and Display Attributes


Navigation Attributes and Display Attributes
Attributes for characteristic: COSTC##
Cost

Center

Attributes

Navigation

Display

Time-Dependent

Attributes

Business area

Company code

Person responsible
Profit

center

Strategic business unit

...

You use the


navigation attributes
of a characteristic in the analysis
(execution of queries) for navigation purposes.
n

Usability for navigation purposes is similar to the other characteristics in the


queries

Can be used to build aggregates (time-independent attributes only)

You use

display

attributes in the analysis only as descriptive information.

Slide 27

Hierarchies
Hierarchies
Hierarchy for characteristic: COSTC##
Cost Center Hierarchy
Version 01
Hierarchy
Company 1000
Corporate

Admin. & Finance

Executive
Board

Internal
Services

Admin Finance

Corporate
Services

Cafeteria

Telephone

Human Resources

Hierarchies are used in the analysis to describe alternative views of the data.

Hierarchies consist of a series of nodes that are joined hierarchically to one


another.

Usually, the leaves of a hierarchy are represented by values from characteristics.

Slide 28

Summary - Characteristics
InfoObjects: Characteristic

BW term for a business-evaluation object

A unique name containing technical information and


business logic

Components of characteristics:
n

Technical definition (length, format, check routines, and so


on)

BEx usage

Master data, texts

Attributes

Hierarchies

Information on compounding

Slide 29

Creating Key Figures


Creating a Key Figure
Key Figure

AMOUNT##

LongDescrptn

Amount ##

ShortDescrptn

Amount ##

Version
Object Status

New
Inactive, non-executable

Type/Unit

Aggregation

Data Type

Extra Properties
Aggregation
Exception Aggregation

Type / Data Type


Amount
Amount

BEx display parameters


Misc . (data element)
Last changed by / on

Number
Integer

Date
Time

CURR- currency field, stored as DEC

Currency/Unit
Fixed Currency
Fixed Quantity
Unit / Currency

0CURRENCY

Slide 30

Summary - Key Figures


Info Object: Key Figure

BW term for a business-evaluation object

A unique name containing technical information and


business logic

Components of key figures:


n

Technical definition (data type)

Key figure type

Currency/unit

Aggregation

BEx usage

behavior

Slide 31

Key Figures Aggregation Options


Aggregation Options for Key Figures

Time period and aggregation structures may cause key


figures to behave differently
n

No aggregation (price)

MAX,MIN,SUM (normal situation)

One characteristic may require a different type of


aggregation (for example, non- cumulative , noncumulative values, and so on). This characteristic is the
reference for the exception aggregation.

Exception aggregation provides many types of


aggregation: SUM, MAX, MIN, different average values
and counters, FIRST, LAST, deviation, and so on.

Slide 32

BW
InfoCube
Components
BW InfoCube
Components
l

Central data stores for reports and evaluations

Contain two types of data:

Key figures

Characteristics

1 fact table and up to


16 dimension tables
n

3 of these dimensions are defined by SAP


n

Time

Unit

InfoPackage

Slide 33

InfoCube in BW

South

Customer
G roup
Dept.Store

North

Region

East

InfoCube: Example

Wholesale

Retail
Glass Ceramics Plastics Clay Copper

Tin

Division
Slide 34

InfoCube in BW Multi Dimensional Analysis


Multdimensional

Analysis

Product group
Customer group
Division
Area
Company code
Region
Period
Profit center
Business area

Ceramics

Plastics

Division

Ceramics

Ceramics

Division

Plastics

33 Analysis of the

South East

Division

Division and the


Region

Customer
Group
DeptStores
Wholesale
Retail Trade

North

South East

DeptStores
Wholesale
Retail Trade
Glass

22 Analysis of the
Plastics

Customers
Group

North

Region

Division

Region

11 Analysis of the

Glass

Ceramics

Division

Plastics

Plastics
South

East

DeptStores
Wholesale
Retail Trade

Region

East
South
Glass

InfoCube

Characteristics:

Customer
Group

North

Region

Query Cache

Customer
Group

North South

InfoCube:

DeptStores
Wholesale
Retail Trade
Glass

Ceramics

Plastics

Division

Slide 35

InfoCube Data Slice


InfoCube: Characteristics and Key Figures

Region

Customer
Group
1
100
RT-0001

North
Plastics
Retail Trade

Sales
Hours
worked

4.000.000
1.300.000

Chars

Key Figs.

Division

Key figures are stored for a unique combination of characteristic


values

Number of dimensions is the degree of granularity / summarization


level of the dataset

Slide 36

From Data Model to Database


From Data Model to Database
Terminology used to describe the
multidimensional
modeling of a business process.

Customer
Dimension

Sales
Dimension

Quantities
Revenues
Costs
Rev./Group

Material Dimension

Material
Dimension

Customer Dimension

Time
Dimension

Competition
Dimension

InfoCube

Star Schema
Real interconnected database tables on a BW
database server.
Slide 37

Steps to Create an InfoCube

7. Activate
6. Choose Key Figures
5. Choose Time-Characteristics
4. Assign Characteristics to Dimensions
3. Create User-Defined Dimensions
2. Choose Characteristics Specified in the Data Model
1. Create New InfoCube Name in Selected InfoArea

Slide 38

Star Schema
Star Schema
l

The combination of fact tables and dimension tables is


called a star schema
Customer Dimension
C

Customer #
13970522

Qty

Sales

Region

West

...

Cred . Mems

Open

Orders

250

$ 500,000

$ 50,000

$ 280,000

50

$ 100,000

$ 7,500

$ 60,000

...

Fact Table
M

Material #
2101004

Material D

Material
Screens

imension

Group

...

Period
10

Fiscal Year
1999

...
...

Time Dimension

Slide 39

Problems with Basic Star Schema


Problems with the Basic Star Schema
l

Multilingual descriptions for attributes in the dimension


tables are not supported.

Secondary indexes for the data are stored as alphanumeric


fields in comprehensive tables.
This makes it more difficult
to access the data.

If attributes of the dimensions change over time, there is no


way of maintaining the old and new values for the attribute.

Even if the majority of a company s master data is used


across the different business processes, each star schema
must duplicate all of the data that is required for all of the
possible user-reports that might be generated.

All hierarchy relationships for the data must be modeled as


attributes (characteristics) of a dimension table. It is not
possible to generate user-defined hierarchy types.

Slide 40

Extending the Star Schema


Extending the Star Schema

A basic star schema has the following restrictions:


l

Only characteristics from the dimension tables can be used to


access the facts.

No structured drilldowns can be generated.

Supporting a large number of languages is difficult.

In BW the
access:

extended star schema

enables you to

Master data tables and their associated fields (attributes)

Text tables with extensive multilingual descriptions

External hierarchy tables for structured access to the data

Slide 41

Master Data Outside the Dimension


Attributes within the dimension

Attributes separate from the dimension

Customer
Dimension
Customer
number
Customer name
Customer category

Customer Number:
Attribute
Customer Dimension

Customer number

Customer subcategory

Customer number

Customer name

Industry key

Incoterms

Customer category

Business partner

Price group

Customer subcategory

Address

Account assignment group

Industry key

Location

Delivering plant

Business partner

Postcode

Customer classification

Address

State

Customer market

Location

Country

Customer statistics group

Postcode

Region

State

Currency

Country

VAT #

Region

Incoterms

Currency

Price group

VAT #

Account assignment group


Delivering plant
Customer classification
Customer market
Customer statistics group

Slide 42

Extended Star Schema


Extended Star Schema
Sales hierarchy
Area 1

Area 2

District 1
Territory

Customer Master Data


Customer
Customer ##

Territory

Territory

District

Territory

District
Territory

: Attributes

Name
Name

Location
Location

Area 3
3

Territory

District
6

Territory

District
7

Territory

5
Territory

Sales Hierarchy

Industry
Industry Key
Key

Customer Dimension

Fact Table

C
C

M
M

C
C

Customer
Customer ##

Area
Area

TT

Sales
Sales Qty
Qty

Sales
Sales

Chain
Chain

Store
Store

Disc.
Disc.

Sales InfoCube

HeadOffice
HeadOffice

Sales
Sales Overheads
Overheads

Stock
Stock Value
Value

Time Dimension
TT

Material D
M
M

Period
Period

Fiscal
Fiscal Year
Year

imension

Material
Material ##

Mat
Mat .. Grp
Grp

Material
Mat
Mat .. Nbr
Nbr

Master Data
Language
Language

Brand
Brand

Catgry
Catgry

Texts
Material
Material Description
Description

Slide 43

Modeling Attributes - Decisions


Modeling

Attribute

s : Decisions

Settings for attributes:


l

InfoObject
n

Navigation or display

Time-independent or time-dependent

Navigational name/description for the user to see on


queries

InfoCube
n

Activate navigation attribute

Slide 44

Modeling Attributes - Results


Modeling

Attribute

s : Results

Results:
l

Display attributes:
n

Can be used only as descriptive information

Navigation attributes:
n

Can be used for navigation purposes similar to the other


characteristics in the queries (dimension characteristics)

Can be used to build aggregates (time-independent attributes only)

Slide 45

BW Star Schema
SAP BW: Extended Star Schema
Master

Text

SID Table

Master

Text

SID Table

Hierarchy

Hierarchy

Dimension
Table

Master

Text

SID Table
Dimension
Table

Fact
Table

Master
SID Table

Hierarchy

Text
Hierarchy

Dimension
Table
Master

Text

SID Table
Dimension
Table

Hierarchy

Dimension
Table
Master
SID Table

Text
Hierarchy
Dimension
Table

Master
SID Table

Master
SID Table

Text
Dimension
Table

Hierarchy

Text
Hierarchy

Master
SID Table

Text
Hierarchy

Dimension
Table

Fact
Table

Dimension
Table

Dimension
Table

Slide 46

Source System, Data Sources and Info Sources


ETL Overview
BW Server

InfoCubes
Update Rules

InfoSource

Communication
CommunicationStructure
Structure

Transfer Rules
Transfer
Transfer Structure
Structure

Transfer Rules
Transfer Rules
Transfer
Transfer Structure
Structure

Transfer
Transfer Structure
Structure

Transfer
Transfer Structure
Structure

Transfer
Transfer Structure
Structure

Extraction
Extraction Source
Source Structure
Structure

Flat File Source System

mySAP

DataSource
(Replica)

DataSource

Extraction
Extraction Source
Source Structure
Structure

System

Source System - Any system which sends data to the BW system.


Transfer Structure - consists of all the fields of the Extract Structure in Source System Transfer Rules will Apply
Communication Structure Link between Transfer Structure and Info Cube/ODS Update Rules will Apply
Slide 47

Replicating Data Sources for R3 Systems

Replicating DataSources for R/3 Source Systems

1
The structure of the
source of the extraction is
used as a template for the
transfer structure in BW
Function:
Replicate DataSources

BW Server

Transfer Structure

DataSource

2
Transfer Structure
Replicating the transfer
structure
(BW -> Source
System) by activating the
transfer structure in BW
Function:
Activate
Transfer Rules

Extraction
Source-Structure

R/3 Source System

Slide 48

Info Sources
Info Source Types

Master Data Info Source

Attributes

Texts

Hierarchies

Transaction Data Info Source

Info Source Components

Transfer Structure

Communication Structure

Transfer Rules

and is assigned to a Source System

Slide 49

Transfer Rules & Update Rules


Transfer Rules are defined for a Info Source and a Data Source

They are Link between a Transfer Structure and a Communication Structure.


Type of Transfer Rules:
Field to Field mapping
Fixed Value
Create and assign Transfer Routines (ABAP Code)

Update Rules are defined for an Info Source and Info Provider which can
be a ODS or an Info Cube.
Types of Update Rules:
* Simple Move
* Start Routine (ABAP)
* Routine
* Formula
* Constant
Slide 50

PSA

PSA stands for Persistent Staging Area.

Flat tables which hold raw data coming from source systems before
The data is transformed. Meaning before transfer rules are applied.
PSA remains in the system till the administrator deletes it on a periodic
Basis.
Major advantage of PSA Re-Extraction of data is not necessary if there
is a data loss.
Therefore the Data Flow from Source System to BW is..
Data Source in Source >> Transfer Structure in BW >> Transfer Rules are applied >>
Communication Structure >> Update Rules >> InfoCube/ODS.
Slide 51

Extracting data from multiple sources

Extraction from Multiple Sources

InfoCube

Update Rules

Business
Information
Warehouse
Server

InfoCube

Update Rules

Update Rules

InfoSource
InfoSource

InfoSource
InfoSource

Transfer Rules

Transfer Rules

Non-SAP
Non-SAP
Extraction
Extraction Tool
Tool
Data
Data Extraction
Extraction
Sales
Sales Europe
Europe

Data
Data Extraction
Extraction
Sales
Sales America
America

R/3 System

Non-SAP System

Source
Systems
Market
Market
Info
Info

Data Provider

ASCII
ASCII
Data
Data

File interface

Slide 52

Scheduler
Scheduler
l

InfoPackage
n

Parameterized

w
w
w

extraction job with

InfoSource
Source system
Selection criteria including variables

User-friendly

Consistency achieved through


extraction

synchronized

One-off or repeated extraction jobs


n

InfoPackage groups

R/3 job scheduling

Triggered by events or time

Slide 53

Monitor
Monitor
l

InfoI Docs sent between the BW and the source system


to monitor the data requests and the processing of data
(traffic light status in the monitor)

All the data requests that you want to


in a tree structure

Header data for the request is displayed

analyze

Technical names of all the objects involved in the data


flow

Option of branching to the maintenance screens of the


individual objects

Runtime analysis

are listed

Detailed display of the individual extraction and


processing steps enables targeted control

Slide 54

Data Loading Status Indicators in the Monitor


Data Loading: Status Indicators in the Monitor
l
Green

Status

Successful

No errors occurred

Data has been updated successfully

Status

Not yet completed/Warning

Yellow

l
Red

Data update process is still running

Invalid number of data packages (updated

Invalid data request (scheduler)

No data in the source system

Status

IDocs

Incorrect (Errors)

Errors in the source system

Data loaded with errors

Indeterminate status after time-out

Slide 55

Step by Step Extraction of Data from Source System


Step-by-Step Extraction

1. Create source system in BW


2. Replicate DataSource from the source system
(Template for the
InfoSource
in BW)
3. Prepare the InfoSource in BW
(transfer rules, extraction methods)
4. Create update rules for the data target (InfoCube)

5. Create InfoPackage and schedule it for update


6. Use the control options in the monitor

Slide 56

Slide 57