Efficient usage of BW InfoProviders Webinar · SAP AG2004, Efficient u sage of BW Inf P rvide /5...

Efficient usage of BW InfoProviders

Product Management SAP NetWeaver / BISAP NetWeaver Regional Implementation Group - BISAP AG

SAP AG 2004, Efficient usage of BW InfoProviders / 2

§§ OverviewOverview

§§ Analyzing business and technical requirementsAnalyzing business and technical requirements

§§ Using ODS Objects the right wayUsing ODS Objects the right way

§§ Modeling data flowsModeling data flows

§§ BW InfoProviders with precalculated dataBW InfoProviders with precalculated data

§§ Efficient usage of BW MultiProvidersEfficient usage of BW MultiProviders

ContentsContents

Contents


DW Layers in SAP BW

Data Warehousen Non volatilen Granularn Integratedn Historical foundationn Built with ODS Objects

Operational Data Storen Operational Reporting n Near Real-Time / Volatilen Granular n Built with ODS Objects

Multidimensional Modelsn Multidimensional analysisn Aggregated viewn Integratedn Built with InfoCubes

... to provide the right information for all users


InfoProvider in SAP BW: Overview

OLAPEngine

BusinessExplorer

Info

Prov

ider

Inte

rface

MultiProviders

Basic InfoCube

InfoObjects

ODS Object

Dat

a C

onta

ined

Virtual InfoCubes

InfoSet


Scope: Efficient usage of BW InfoProviders

Modeling (single) BW InfoProviders

Building your DW and EDW strategy

In between these two concepts you have to decide on:

nWhat BW InfoProvider types to use

n How many BW InfoProviders you will use

n How to model these BW InfoProviders in data flows

nWhen and how to use BW MultiProviders

Project

Project

Project








ContentsContents

Contents


The following selected areas from your business blueprint have to play an important role when deciding on BW InfoProviders:

Granularityn How do you want to look at the data? Daily? Monthly? Quarterly?n What level of analysis needs to be done? Aggregated or detailed?n Are snapshots of the data needed? Does data need to be restated?

Data Volumesn How many line items are there? How many products do we have?

How many years of data do we need to house? What data history doyou want to keep in your data warehouse ?

Analysis aspectsn How is data being analysed? OLAP analysis including navigation on

data or “flat list” reporting?n What response times do my users expect to return their results? How

quickly do they need access to the data?

Analyzing business and technical requirements I


Data Sourcesn How much transformation of the data is required? Does this need to

take place at multiple times during the data loading process? Is the data going to be reported on throughout the transformation process?

n Structure of source data: Does the source system send normalized(“document like”) or already pre-aggregated data? Is delta calculation required on source data?

Analyzing business and technical requirements II

Knowing about your business requirements and your technical environment (e.g. data volumes and data sources) is the basis for

all high level and low level modeling in SAP BW.

The quality of the implemented data models and data flows is thebasis for all administration and performance tuning in SAP BW.








ContentsContents

Contents


n ODS objects serve to store consolidatedand cleansed data on a document level from one or more InfoSources. Usage examples:

n Updating further data targets n Data validation

n Data in an ODS object can be analyzed by the Business Explorer mainly to support operational reporting.

n ODS Objects can support calculations on document level or calculation of delta on source data

nThink of deleting (calculated) delta records from your change log table that are not needed anymore.

n ODS Objects can support central master data consolidation

Using ODS Objects the right way

Check your business requirements against ODS Object features:


Using ODS Objects – bad example

ODS Object: Cost Centre ControllingActual Data

ODS Object: Cost Centre ControllingPlan Data

Customer Data Source delivering delta records

Redundant storage of data on same level of

granularity

InfoCubeCost Centre Controlling

No document like data, no delta

calculation required

Additional benefit of second

ODS Object?No transformations


Using ODS Objects – good example

ODS Object: Sales OrdersItem Level

ODS Object: DeliveriesItem Level

Build DWH layer that

stores document data for

reference

ODS Object:Document flow in sales & distribution

InfoCube:Sales analysis

Flat List Reporting on consolidated

data

Calculations on document level

Data Mart for OLAP analysis on

aggregated data








ContentsContents

Contents


Modeling data flows

Design your data flows according to business and technical requirements. This has to include:

n Knowing about your source data and the needed levels of granularity in your BW data flow

n Deciding on what level of granularity transformations have to occur

n Avoiding redundant data storage in order to optimize disk space

n Reducing complexity of your data flow for improved performance and administration

n Implementing data validationprocedures where needed

KISS - Keep it small and simple!

L


Example on data flow modeling - before

All DataSource / PSA information is kept in the ODS Object


PSA for DataSource „Sales Order Items“ and Source system ERPCLNT100



Reloading data only occurs on very last requests. Building or Rebuilding InfoCubes is done based on ODS Object

Only transformations on material level. No transformation on sales order item level.


Example on data flow modeling - after



ODS Object might respond to all administrative needs. Another option would be to use PSA, but to keep only very recent data in it.

Possible modeling as aggregate of other InfoCube as nearly on same level of detail

PSA for DataSource „Sales Order Items“ and Source system ERPCLNT100

If no transformationsoccur between ODS Object and InfoCube, they can be loaded in parallel

If transformations occur, this

pragmatic approach should not be

chosen in order to keep the “single point of truth”








ContentsContents

Contents


BW InfoProviders with precalculated data

A BW InfoProvider contains transformed

and integrated data for multiple OLAP analysis

Exceptionally, a BW InfoProvider can contain

precalculated, “query like” data in order to support

advanced analysis

BW Information Consumers can receive

precalculated query documents using BEx

Broadcaster

Query Design and OLAP Analysis

Potential for the Information Consumer

Scope of this presentation

“Degree of Precalculation”


Example 1: Inventory Management and Snapshots

ODS Object: Actual stock quantity on material level

Snapshot scenarios can be an alternative to non cumulative key figures and non-cumulative InfoCubes if:n High number of movements on object for which the stock has to be

calculated = Stock quantity changes frequentlyn High number of objects for which a stock quantity has to be calculatedn Frequent analysis using averages or historic stock values à See “How to …Handle Inventory Management Scenarios in BW” on

http://service.sap.com/bw

InfoCube:Stock quantity on material level (end of month)

InfoCube:Actual stock quantity

on material level

Daily refresh (full upload)Update of month end “snapshot” once a month

Opening balance Material movements

Stock is kept and calculated in ODS Object, not in OLAP



The Analysis Process Designer allows you to…n Access and transform information using a single data process

u combining different sources and different analysis steps

n Deploy key performance indicators and analytical results to certain BW InfoProviders or to your operational processes in SAP CRM

Example 2: Analysis Process Designer

Simple Example: Send query results to a transactional ODS Object (and from there to further BW InfoProviders in your data flow)








ContentsContents

Contents


BW MultiProviders are used for…n Combining and analyzing heterogeneous business data (different key

figures) out of different BW InfoProviders using common characteristics

n Splitting data of one business scenario to separate Basic InfoCubes (“Logical Partitioning”)uPossible partitioning criteria: year, plan/actual, regions, business areauUse MultiProviders to cut large amounts of data into chunks

Efficient usage of BW MultiProviders I

Sales Costs Forecast

2002 2003 2004


Efficient usage of BW MultiProviders II

BenefitsnNo additional data storagenSingle InfoProviders smaller, less complex and less sparsely filled

than one big InfoProvidern(Parallel) Data load into individual InfoProvidersnBetter performance in administration on Basic InfoProvidersnIn most cases, queries are split automatically and distributed to

InfoProviders (for more details on parallel execution see SAP Service Marketplace note 629541)nCentral interface for querying even if underlying data models change

DisadvantagesnAdministration (with aggregates)nIncreasing number of InfoProviders to be administrated


Efficient usage of BW MultiProviders III

Europe Sales

America Sales

MultiProvider

MultiProvider

Asia Pacific Sales

Make sure that your BW MultiProviders only retrieve data out of relevant InfoProviders at query runtime.

By using characteristic 0INFOPROV when designing a query on the MultiProvider. Example: 0INFOPROV = ‘ZEUSALES’

0REGION = ‘AMERICAS’

0REGION = ‘APA’

0REGION = ‘EMEA’

0AMOUNT

Europe Inventory

0REGION = ‘EMEA’

0QUANTITY

By using constants in the design of Basic InfoProviders (to be specified at implementation time)

By using different key figures in your Basic InfoProviders

0AMOUNT 0AMOUNT


è Public Web:www.sap.com > Solutions > SAP NetWeaver

è SAP Service Marketplace:

http://service.sap.com/bwlBW InfoIndex – ODS FunctionslBW InfoIndex – Enterprise Data WarehousinglBW InfoIndex – Data ModelinglBW InfoIndex – Non-cumulativeslFolder “Performance”http://service.sap.com/educationlBW330 BW – Modeling (3 days)lBW360 BW Performance & Administration (5 days)

Further Information

è …coming soonhttp://service.sap.com/bwl Services & Implementation

l How to... Efficient Usage of BW InfoProviders

http://www.sap.com


http://service.sap.com/education



Copyright 2003 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are trademarks of their respective companies.

Efficient usage of BW InfoProviders Webinar · SAP AG2004, Efficient u sage of BW Inf P rvide /5...

Documents

Transcript of Efficient usage of BW InfoProviders Webinar · SAP AG2004, Efficient u sage of BW Inf P rvide /5...