SAP BW WORKSHOPS

DATA MANAGEMENT AND BUSINESS INTELLIGENCEJANUARY 2009

AGENDASESSIO

NACTIVITY SCHEDULE

1Introduction

W1= 60 min SAP Business Information Warehouse Navigation

2W2P1= 40 min Part 1: Crash course reportingW2P2= 60 min Part 2: Query definition

3 W3= 90 min Exception reporting4 W4= 90 min Creating SAP InfoObjects5 W5= 60 min Creating SAP InfoCubes6 W6= 90 min Flexible Master Data Staging7 W7= 90 min Loading Transaction Data

8W8P1= 60 min Part 1: Visualising DataW8P2 = 30 min Part 2: Analysing Data

SAP INTRODUCTION

Overview

BW: an end-to-end data warehousing solution which can: Gather information Merge and transform information Manage that information Present, analyse and exploit

information Lead to better business decisions

Introduction

Who uses SAP BI? Why do they want it?

Use of Data Reporting from many sources The devolution of decision making

Reporting Availability Ability to create their own reports “NOW” in a self service

environment Removing the ABAP backlog for R/3 reporting Reducing reliance on IT

One version of the truth Common business definitions Common results – reconciliation

Consumer70%

Analyst20 %

Author10%

Introduction

Business Intelligence SAP Netweaver BI SAP NetWeaver BI is a web-based, open

integration and application platform that serves as the foundation for enterprise service-oriented architecture (enterprise SOA)

Allows the integration and alignment of people, information, and business processes across business and technology boundaries.

Utilizes open standards to enable integration with information and applications from almost any source or technology.

Introduction

Data Warehouses1. A data warehouse is a central repository for all or

significant parts of the data that an enterprise's various business systems collect.

2. A data warehouse is a copy of transaction data specifically structured for querying and reporting.

3. A collection of data designed to support management decision making. Data warehouses contain a wide variety of data that present a coherent picture of business conditions at a single point in time.

4. “A data warehouse is a subject-oriented, integrated, nonvolatile, time-variant collection of data in support of management’s decision. (Bill Inmon definition)”

Introduction

Data Warehouse / Business Intelligence

Introduction

mySAP ERP SOLUTION MAP (1)

END-USER SERVICE DELIVERY

Internet

Sales

Business Warehous

e

Financial Supply Chain

Mgmt

Collaborative Project Manageme

nt

Analytics

Manager &

Employee Self

Services

Introduction

Subareas of SAP NETWEAVER™

CollaborationPortal

Knowledge Management

Business Intelligence

Business Process Management

Integration Broker

ABAP

Com

posi

te A

pplic

ati

on

Fra

mew

ork

Life

Cycl

e M

anagem

ent

PEOPLE INTEGRATION

INFORMATION INTEGRATION

PROCESS INTEGRATION

APPLICATION PLATFORMJ2EE

DB & OS Abstraction

SAP NETWEAVER ‘04™

Multichannel Access

Master Data Management

DB & OS abstraction

IBM Web Sphere

Microsoft .NET

…

J2EE

Introduction

• Provides core functions for the infrastructure of the business in 4 subcomponents

• Not all SAP solutions are based on Netweaver (e.g. SAP Business One)

SAP Netweaver Integration

mySAP SCM

mySAP

CRMmySAP ERP

mySAP PLMLife-Cycle data, Project-

Quality and Asset Management

Inventory and Warehouse Management Manufacturing and

Transportation

Pu

rch

ase

ord

er

req

uis

itio

ns

Sale

s ord

ers

Inte

rnet S

ale

s

SAP BISAP

Enterprise Portal

PEOPLE INTEGRATION (SA EP)

INFORMATION INTEGRATION (SAP BW)

PROCESS INTEGRATION (SAP XI)

APPLICATION PLATFORM (SAP Web AS)

SAP NETWEAVER™

mySAP Business

Suite

mySAP ERP

ECC

Introduction

Structure of SAP BW

Introduction

SAP BW Front end options

BEx Analyzer

•BEx Web

•Data Mining

•Bex Mobile Intelligence

•Bex Report designer •Visual Composer

Introduction

SAP Business Information Warehouse Navigation

Workshop 1

BW AccessSAP NETWEAVER

‘04™

Workshop 1

Client: 800System: BW Brunel (G90)

USER: XBUSER-1-XXINITIAL PASSWORD: init

“XX“ is a number between 0-30. This number will be or has been assigned to each student. The system will ask for a new password once you login for first time.

BW Access / Naming conventionsSAP NETWEAVER

‘04™

Workshop 1

Please remember to use the naming convention set up for this module, which is as follows:

The institution’s unique code letter = XBThe current course’s unique number = Y Substitute Y with the number 1 assigned to NITH courses

Each participant’s unique number = XXSubstitute XX with the number assigned to you at the start of the session

 For example, if you see XBYXX and you are in training assigned number 10, you would type XB110.

XB = Institution1 = Course Number for NITH10 = Student No. 10

The abbreviations for actions within the exercises are:Right mouse click = RMDouble click = DC

SAP Business Information Warehouse Navigation

Start workshop 1 / 60 min

Part1: Crash Course Reporting

Workshop 2

Working area / Data source reporting

Workshop 2

SAP BW ToolsSAP NETWEAVER

‘04™

Workshop 2

Multidimensionality

Workshop 2

TYPES OF NAVIGATION

Workshop 3

•Pivoting means turning the data cube

•Slicing means filters are set to create a “slice”of data

•Dicing means creating a “smaller”data cube by slicing an interval

•Drilldown generally means adding information to a report

•Roll up = opposite of drilldown

•Drill across is when the x-and y-axes are switched

Query Areas

Workshop 2

TYPES OF NAVIGATION (Exercise)

1. Slicing: Display all results generated in the Munich, London and Berlin sales organizations. Return to the default state.

2. Dicing: Limit the report to the first half of the year 2003.

3. Pivoting: You now want to display the report according to material and time. Turn the data cube accordingly so that you swap sold-to party with material.

4. Roll Up: You are not concerned about time (calendar year/month) right now. Aggregate your report accordingly.

5. Drilldown: You now want to work with key figures according to material and distribution channels. Add the distribution channel as additional information to your report. Go back one display.

Workshop 2

Part1: Crash Course Reporting

Start Part 1 of workshop 2 / 40 min

Part 2: Query Definition

Workshop 2

Working area / Query definition

Workshop 2

Meta Data Model for Query Definition and Query

InfoCube Query

definition supplies data 0,n 1,1 Workbook

(xls file)

em- bedded query

0,n 0,m

Save as

view

View

• BEx Analyzer is used to generate queries (query definitions) that always refer to exactly one InfoProvider and that represent the InfoProvider’s data in a suitable form.

• The OLAP processor ensures that the queries are forwarded to BW.• The query definition is stored on the BW server. Whereas the query

definition to a certain extent can be interpreted as a class definition, a query is stored in an Excel Workbook as an instance of this class and saved with the workbook SAP is not always consistent in differentiating between query definitions and embedded queries.

OLAP Engine

Workshop 2

Data Source of reporting

Workshop 2

Query designer toolbar

Workshop 2

Using drag and drop for your query definition

Workshop 2

Part 2: Query Definition

Start Part 2 of workshop 3 / 60 min

Exception Reporting

Workshop 3

Working area / Query definition with exceptions

Workshop 3

Exception Reporting Scenario

You must be in a position to identify and remedy potential problems in a organization early on. Analyses that are carried out at regular intervals can help identify weak points. Exception reporting, which has been implemented in BW, enables you to recognize, select and highlight unusual deviations from predefined key figure values in the query result

Workshop 3

Exception Reporting steps

1.Define the exception2.Output: highlighted in colour in

the query worksheet3.Define Reporting Agent settings4.Schedule5.Output: alert Monitor and

messages

Workshop 3

Exception Reporting

Workshop 3 / 90 min

Creating SAP InfoObjects

Workshop 4

Working area / InfoObjects

Workshop 4

Definitions INFOOBJECT: are the basic stores of information of

BW. They are used for the creation of data targets such as InfoCubes.

KEY FIGURES: form the content of the cells of multidimensional data cubes and thus are the central element of each MDM

DIMENSIONS: viewpoints of analysis for multidimensional data basis. Highest level of a data consolidation path. For BW, dimensions are summarisation of contents of the

characteristics that constitute them. CHARACTERISTICS: components that are caused of

analysis. E.G. time, value types, students, customer, etc.

Workshop 4

InfoObjects Infoobject

Characteristic E.g. Customer,

Product

Infoobject: Key Figure E.g. Sales, Costs Numerical and

additive if possible

Workshop 4

From Star schema to InfoObjects

Every field of a dimension becomes a characteristic

Each key figure of the fact table becomes a key figure

Workshop 4

Facts

Sales Costs

Quantity

Customer

Customer Region Product

Product Division

Time

Day Month

Important properties of a Characteristic Name Data type Length Master data

Text Short: 0TXTSH Medium: 0TXTMD Long: 0TXTLN

Attributes It is a InfoObject

itself (Characteristic or Key Figure)

Hierarchies

Workshop 4

InfoCube Architecture

Workshop 4

ACTIVITIES FOR THIS WORKSHOP

1. Create an InfoObject.2. Check: InfoObject is checked

for correct syntax.3. Save: Definition is saved.4. Activate: Database tables are

generated.

Workshop 5

InfoCube Architecture for Workshop 5

Facts

Sales Costs

Quantity

Customer

Customer Region Product

Product Division

Time

Day Month

Workshop 4

Creating SAP InfoObjects

Workshop 4 / 90 min

Creating SAP InfoCubes

Workshop 5

Working area / InfoCubes

Workshop 2

DEFINITIONS DATA CUBES: are the central stores for all

analyses and reports (in SAP!) and are stored in Infoareas. From the physical point of view the infocube and

relevant dimension tables are connected each other relationally using dimension keys.

Formed from key figure and characteristic data types.

Three dimensions are already defined with TIME, UNIT and INFOPACKAGE.

Workshop 6

LOGICAL VIEW OF AN INFOCUBE

Workshop 6

InfoCube Architecture

Workshop 6

ACTIVITIES FOR THIS WORKSHOP

1. Create InfoCube2. Add key figures3. Add characteristics4. Create dimensions5. Sort characteristics into

dimensions6. Check, save, activate

Workshop 6

STAR SCHEME FOR INFOCUBE SALES

Workshop 6

Facts

Sales (AYXX_SA Costs (AYXX_CO) Quantity (AYXX_QU)

Customer

Customer (AYXX_CU) Region (AYXX_RE) Product

Product (AY_PR) Division (AY_DV)

Time

Day (0CALDAY) Month (0CALMONTH)

Creating SAP InfoCubes

Workshop 5 / 60 min

FLEXIBLE MASTER DATA STAGING

Workshop 6

Working area / Flexible master data staging

Workshop 6

Loading data in SAP BW There are two types of application data in BW

Master data: are the segments, attributes, texts and hierarchies introduced in the analysis of the extended star schemas

Transactional data: data records of an InfoCube fact table Data in BW

Metadata Application Data

Specialist Metadata

Technical Metadata

Transaction- Data Master Data

Attributes Texts Hierarchies

Workshop 6

Staging scenarios Staging scenarios with

transient data store Data is always

collected anew and only kept in the BW systems for the duration o a given transaction

Staging scenarios with persistent data store

Data loaded from the source system into the SAP BW system is stored even after a transaction has been concluded

Workshop 6

Persistent Staging Scenario

Workshop 6

For this workshop

FlatFiles as source system Source systems

are all systems that stage data doe SAP BW, this includes: FLATFILEs in

which the metadata is maintained manually and the data is transferred using a data interface to the SAP BW

Workshop 6

Structure of flatfiles

Structure of Attributes FlatFiles

Structure of Text FlatFiles

Workshop 6

Update types

Flexible Updating Direct Updating

Transaction data Master data

= with update rules

Master data only

= without update rules

• Update rules specify how data (KF, Characteristics, time characteristics) are updated from an InfoSource communication structure to the data targets

• They connect an InfoSource with an InfoCube, Characteristic or ODS object

Workshop 6

InfoSource, Transfer rule & PSA definitions Infosource describes the amount of all available data

for a business process or a type of business process. It is a unit of logical associated information that is of

InfoObjects and can refer data from one or more DataSources.

The structure of an InfoSource is called the communciation structure.

Transfer rules determine how and which field in the source system-dependet tranfer structure are transferred to which field in the source system-independent communication structure.

PSA is the initial storage are of SAP BW for requested data from different source systems.

Workshop 6

Activities for this workshop (2)

1. Insert characteristic as a data target

2. Define InfoSource for master data3. Assign source system and

DataSource(s)4. Maintain transfer structure and

transfer rules5. Create update rule6. Create and schedule InfoPackage

Workshop 6

Example of data flow for uploading Master data from flat files

Source System

DataSource

BufferPersistent Staging

Area

InfoSource

Customer Characterist

ics

Workshop 6

FLEXIBLE MASTER DATA STAGING

Workshop 6 / 90 min

LOADING TRANSACTION DATA

Workshop 7

Loading data in SAP BW There are two types of application data in BW

Master data: are the segments, attributes, texts and hierarchies introduced in the analysis of the extended star schemas

Transactional data: data records of an InfoCube fact table

Workshop 7

Data in BW

Metadata Application Data

Specialist Metadata

Technical Metadata

Transaction- Data Master Data

Attributes Texts Hierarchies

Persistent Staging Scenario

Workshop 6

For this workshop

Transaction vs Master data Loading the master data and then the transaction

data is more common since: Characteristic values are assigned to SIDs during

loading processes, if the transaction data were loaded first, a temporary SID would need to be assigned that would be corrected later.

Referential integrity with the master data can be ensured when loading the transaction data. This means that transaction data records that refer to non-existent characteristic values can be rejected.

Workshop 7

FlatFiles as source system Source systems

are all systems that stage data doe SAP BW, this includes: FLATFILEs in

which the metadata is maintained manually and the data is transferred using a data interface to the SAP BW

Workshop 8

Structure of Transaction Data flatfiles

• Maintain consistent order• Do not use titles if possible• Give data in the YYYYMMDD format

Workshop 7

Activities for this workshop (1) Data coming from Master data will uploaded

into our InfoCube Sales. Master data is therefore not updated in the

InfoCubes like transaction data. The master data tables of a characteristic are

supplied by the master data InfoSource of the respective characteristic. For this example we are using Text files.

Workshop 8

Phases of the staging Process from Flat Files

Workshop 7

Example of data flow for uploading Transaction data from flat files

Source Syste

m

DataSource

BufferPersistent Staging

Area

InfoSource

Sales

Cube

Workshop 7

LOADING TRANSACTION DATA

Workshop 7 / 90 min

VISUALISING DATA

Workshop 8

Diagrams vs Words

Workshop 8

GEO-Characteristics

Many of the BW characteristics, such as customer, sales region, state or country, also have geographical significance.

•You can evaluate geographic information together with the business-relevant key figures in BExMap.

•BExMap is the geographical information system (GIS) of BW that is integrated in Business Explorer (BEx).

Workshop 8

Activities for this workshop Identify characteristic as geographically

relevant Load geographic data into BW

This will load the maps available asshape filesinto the BW system and assign them to the respective characteristic

Download “geo-data”: Downloads the master data of the characteristic. Important: SAPBWKey

Open the DBF file of geo-data and enter the SAPBWKey Upload modified shape files

Insert BExMap into the query Define a query with geo-characteristics and insert it into a

workbook. After you attach a map, it displays query data of geographical relevance. You can navigate through the map to further evaluate geo-relevant data

Workshop 8

VISUALISING DATA

Workshop 8 part 1/ 60 min

ANALYSING DATA

Workshop 8 part 2/ 30 min