design consideration for 7.30 info providers

42
Customer Design Consideration for 7.30 InfoProviders Andreas Keppler, Regional Implementation Group December, 2010

Upload: marc-mennereau

Post on 28-Nov-2014

109 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Design Consideration for 7.30 Info Providers

Customer

Design Consideration for 7.30

InfoProviders

Andreas Keppler, Regional Implementation Group

December, 2010

Page 2: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 2

Contents

1. Design Guidelines for the new 7.30 InfoProviders

Semantic Partitioned Object (SPO)

HybridProvider

CompositeProvider

TransientProvider

Miscellaneous

2. Which InfoProvider for which scenario?

3. Summary

Page 3: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 3

Motivation

Logical Split

for parallel

processing

High effort

for manual

modeling

High Data

Volume

Decrease

Complexity

Accelerated

Reporting

requirements

SPO

Source1 Source2 Source3

Sem

an

tic

Part

itio

ned

Ob

ject

(SP

O)

Page 4: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 4

General description

The components of the SPO are

o the so-called MasterProvider (InfoProvider that is maintained by the end user and used as a template object (InfoCube or DataStore Object)

o the so-called PartProviders (Homogeneous set of InfoProviders with properties copied from the MasterProvider)

o InfoSources (used as interface objects to embed the SPO into the data flow)

o Transformations (Used to link the InfoSources internally with the PartProviders)

An SPO partition is characterized by partitioning criteria (max 5 characteristics) which have to be disjoint across SPO partitions (no overlap)

Can be combined with the native database partitioning criteria (most restrictive criteria pervails)

The semantic partitioning is a property of the respective basis InfoProvider

DefinitionThe Semantic Partitioned Object (SPO) comprises

multiple InfoCubes or DataStore Objects that are

logically partitioned.

It is capable to handle mass data (and data flows)

more efficiently.

Page 5: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 5

The SPO and its Components

Page 6: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 6

Main Advantages

Advantages

Enables an (enterprise) data warehouse to handle mass data in a better way to improve the

staging performance

Reduces time needed to make data available for reporting

Involves the creation of multiple structurally identical data targets (meta data objects) instead

of using one data target that stores a huge amount of data

Avoid errors during manual creation of the partitioned objects. The consistency will be

controlled by the system

Wizard supported maintenance

Leverages SAP NetWeaver BWA as well as partition pruning when accessing partitioned

InfoCubes

Is integrated into Data Archiving / NLS concepts

Define partitions by customer coding (Business Add-Ins) e.g. flexibly apply rolling time

window scenarios to partitions

Page 7: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 7

Restrictions / Limitations

The usage of the SPO requires SAP NetWeaver BW 7.30Prerequisites

Up to 99 partitions can be created.

Up to 5 dimensions (partition characteristics) can be chosen as combined

split criteria

Only 6 characters available to define SPO name

Partitioning characteristics for SPOs based on DataStore Objects have to

be part of the key of the DataStore Object

Modeling

One interval or one list of single values per dimension

No ‘’Exclusion’ option for selection in partition definition

No Migration option for existing data models

No overflow partition (use BAdI or modeling to cater for)

No re-partitioning with automatic data transfer / adjustment

Features

New InfoProvider ‘InfoCube BWA only’ is not supported

DataStore Object for Direct Update is not supportedMisc

Page 8: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 8

Contents

1. Design Guidelines for the new 7.30 InfoProviders

Semantic Partitioned Object (SPO)

HybridProvider

CompositeProvider

TransientProvider

Miscellaneous

2. Which InfoProvider for which scenario?

3. Summary

Page 9: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 9

Motivation

The HybridProvider addresses

High performance near real time reporting on large volume of data. Large volume

derives from the amount of historic information that has to be taken into consideration and/or

the amount of data provided near real time

High performance reporting accross data from different sources where at least one

source deliver the data near real time (thus no operational reporting on OLTP possible)

Page 10: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 10

General Description

Is a combination of two InfoProviders

o One InfoProvider (leading) manages near real time data loads. It can be either A DataStore Object loaded via Real Time Data Acquisition (RDA) or

A Virtual Provider via Direct Access of source data (only for selected DataSources)

o One InfoProvider manages historic data. It can be either A Standard InfoCube and aggregates (relational data base only) or

A Standard InfoCube with BWA Index (relational data base and BWA index) or

A BWA InfoCube only (no persistency in BW database - BW 7.30)

Leading DataStore Object can be an existing one (conversion to HybridProvider)

Data flow between objects (DTP and Process Chain) generated on activation (including

population of DataStore Object)

Synchronisation (real time data InfoCube) / transparent access performed by the

system

Maintenance in toggle mode between InfoCube and DataStore Object

DefinitionThe HybridProvider is a combination of two

InfoProviders (InfoCube for historic & DataStore

Object / VirtualProvider for near real time data).

To the end user it acts as one consistent object for

querying and transformation.

Page 11: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 11

HybridProvider

HybridProvider

- Structure and data flow

AIM Delta

Delta Queue

OLTP

DataSource

PSA

DataStore Object

Activation

Queue

Change

Log

Active

Records

RD

A D

aem

on

Query Runtime

………

………

……Key2

……Key1

Kyf2Kyf1Query

Analy

tic E

ngin

e

The system automatically determines

whether the data resides in InfoCube or

DataStore Object (Change log)

InfoCube

BWA

Page 12: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 12

Main Advantages

Advantages

The HybridProvider provides high performance analytics on large volume of real time &

historic data

Low TCD as all dependent meta data (InfoCube, Transformation, DTP, Process chain) are

generated

The HybridProvider is treated (in the system) / maintained (by the end user) as single object

(though technically two objects)

The HybridProvider with BWA InfoCube needs little maintenance efforts and thus, lower the

TCO

Page 13: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 13

Restrictions / Limitations

SAP BWA has to be in place to guarantee high performance reporting

The DataSource must be RDA enabled or direct access capablePrerequisites

Existing DataStore Objects or VirtualProvider will lose its independency

No other DTPs and Transformations possible to the InfoCube than the

generated ones

Only available for DataStore Objects that are SID-enabled

Inherits the limitations (non-cumulatives, aggregation, etc.) of its

underlying InfoProviders.

Queries may not use key figures with aggregation MAX or MIN.

For InfoCubes with BW persistency remodel single dimension model

Modeling

Not available based on write-optimized DataStore Objects

No read via RSDRI read interface.

Direct Access only for DataSources that offer a valid delta criteria and

guarantee acceptable transfer time.

Direct access does not support DataSources, which use the delta queue

Features

Automated update of InfoCube only for RDA loads (‚normal‘ DTP have to

be scheduled)

A HybridProvider can be part of a MultiProvider. The query-pruning via

RRKMULTIPROVHINT does only work on InfoCubes

Misc

Page 14: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 14

Contents

1. Design Guidelines for the new 7.30 InfoProviders

Semantic Partitioned Object (SPO)

HybridProvider

CompositeProvider

TransientProvider

Miscellaneous

2. Which InfoProvider for which scenario?

3. Summary

Page 15: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 15

Motivation

Enterprise BWAccelerated/

Lean

Enterprise BW

Accelerated/

Lean BW

Enterprise BW

Standard offering

Combines Enterprise scenarios

& departmental / short term

needs addressing issues of

Enterprise BW scenarios through

central IT work packages

lean, extended modeling

Less persistence through new CompositeProvider

Lean data provisioning

Less administration (BWA)

Enterprise BW

Extended offeringDepartmental BW

Coming Soon…Enterprise BW scenarios

EDW, Architected DM, LSA

standard reports & analytics

central IT projects

stable, long term, standardized

high availability, robust

Issues:

time to market

overall flexibility

covers 60%-90% of business

needs

Easy modeling environment inside the data warehouse for the IT department for rapid

prototyping with SAP BW Accelerator (BWA)

Ad-hoc reporting (Quick temporary scenarios delivered by IT for the business

departments)

Combination of data (e.g. BW data + Flat files)

Conclusion

Page 16: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 16

General description

Definition

In a CompositeProvider you can join existing Analytical Indexes via

UNION, inner and left outer JOINS. The calculation is done on the

fly at query run-time.

CompositeProviders are exposed to all BI clients as any other

standard InfoProvider via the BEx Query Designer.

Contains 1:n Analytical Indexes (no technical limit of number of objects to be joined),

built with the Analysis Process Designer (APD), and published

As a first step an object (AnaIytical Index) has to be selected as a basis for the

CompositeProvider

Joins of existing Analytical Indexes via UNION, inner and left outer JOIN

Facilitated modeling capabilities on basis of field names (no keys, no temporal joins)

Semantic definition/combination without data persistency (calculation on the fly at

query run-time)

The user interface for modeling is the SAP GUI Lean Modeler

Description of the data model via a BWA CalculationScenario¹

When the CompositeProvider is activated, it is converted into a BWA

CalculationScenario and created in the BWA

Page 17: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 17

Structure and Modeling UI

(flexible) In-Memory Join

with CompositeProvider

BEx Query

Page 18: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 18

Main advantages

Advantages

Combination of data of Analytical Indexes in BWA via UNION, inner and left outer JOIN

Quick creation of temporary scenarios (prototyping)

For all BI clients CompositeProviders are exposed as standard BW InfoProviders via BEx

Query Designer (and can be called via MDX, BICS like any other InfoProvider)

No creation of InfoObjects for characteristics and key figures needed

Page 19: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 19

Restrictions / Limitations

SAP BW Accelerator has to be in place

Access to BW Backend is neededPrerequisites

A CompositeProvider is mainly the combination of data models, not only

single tables

Modeling a CP is always on basis of an Analytical Index/Transient

InfoProvider created via APD

A CompositeProvider cannot be used as InfoProvider (Component) within

another CompositeProvider (transitive usage)

Modeling

An assignment of different referenced InfoObjects to one column in the

CP currently leads to the fact that no attributes will be displayed

No possibility to create temporal joins (like with InfoSets; InfoSets are

currently not available in the BWA)

The functionality of the Lean Modeler is currently quite basicFeatures

Data types for characteristics in the AI are STRING, DATS and TIMS

Data types for key figures in the AI are Fixed-point and Floating-point

number and IntegerMisc

Page 20: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 20

Contents

1. Design Guidelines for the new 7.30 InfoProviders

Semantic Partitioned Object (SPO)

HybridProvider

CompositeProvider

TransientProvider

Miscellaneous

2. Which InfoProvider for which scenario?

3. Summary

Page 21: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 21

Motivation

Minimize the need

for SAP BW skills

in the operational

environment

Provide the

benefits of SAP

BW reporting to

operational (ECC)

users (OLAP,

multi-dimensional,

formatted

reporting etc.) in

their system

Have one unified

UI for most of the

reporting needs

Reduce the

overhead

generated by

replicating the data

to SAP BW

Eliminate the

redundancy of

storing the data in

SAP BW and ECC

No separate SAP

BW system needed

(only SAP

NetWeaver)

No data latency for

the end user

Apply

performance

boosts by using

BW Accelerator

on ECC data

Page 22: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 22

General description

Reporting is performed directly on the Business Suite tables using the BEx tools (or

another reporting tool – MDX and BICS capable)

The source of the data can be eithero a classic InfoSet (based on DDIC tables or logical databases) (main focus of this

presentation)

o a DataSource (via ODP¹ framework) in the Business Suite system OR

o an Analytical Index build with the Analysis Process Designer (APD) OR

o Fast Search Index(FSI)-Views (only for SAP Business ByDesign)

A TransientProvider does not have any persistent BW meta data (no InfoObjects,

etc. visible in Data Warehouse Workbench).

If applicable, for BW InfoObjects, all options for reporting (text, master data,

hierarchies) are available

Potentially, data can also reside in a BW Accelerator index (depends on the

implementing application)

1) ODP – OperationalDataProvisioning – future Extraction framework

DefinitionInfoProvider that allows analysis and reporting with

BI tools (including BW OLAP functionalities) on top of

an application (e.g. Business Suite system). It is not

modeled in the Data Warehousing Workbench of BW

and the data is not replicated.

Page 23: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 23

ERP

TransientProvider

High-level view (including Operational Data Provisioning)

ODP Framework

(Data Services, …)BEX Query²

ODP (Operational Data

Provider) + associations

ODP Services• Operational DeltaQueue

BW DataSource

TransientProvider

SAP BW

BICS²MDX²

Classic

InfoSet

FSI (future suite

infrastructure)

ETL

2) Via underlying SAP NetWeaver stack

Page 24: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 24

Main Advantages

Advantages

Executed in the Business Suite system, no separate SAP BW system needed

Operational reporting tailored for the applications

Real-time data access (zero latency)

No duplication of data / objects necessary. For scenarios like merging of data or large scale

reporting applications, replication and transformation of the data to an EDW is still

feasible.

No BW metadata model

Complete set of Analytical Functions (Restricted / Calculated key figures, Exceptions, etc.)

Pre-delivered content by SAP (which might be embedded in the operative transaction)

Page 25: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 25

Restrictions / Limitations

Installation of BI client necessary

The usage of the TransientProvider requires ERP 6.0 EhP 05

Only InfoSets which are client independent are available

Operational System (InfoSets) and BW installation have to be in the same

system, no remote scenario

Prerequisites

No merging of data from multiple source systems (consolidation)

Initially, no customer/partner modeling (only SAP delivered content)

No enhancements of TransientProvider (add additional fields from

DataSource or populate fields bia BAdI)

Characteristics and key figures are derived from the underlying model

(Classic InfoSet, ODP, etc.). Hence, specific properties can not be applied

to them.

Modeling

No (external) hierarchies, navigation attributes

Derived characteristics do not support text or attributes (text only via

textfield in InfoSet definition)

Only some field types, e.g. DATS and TIMS, use standard BW

InfoObjects to provide value help and hierarchies

Features

Authorizations from the operational System (Analysis Authorization are

currently not relevant, since the InfoObjects are derived)

Authorizations from the Business Suite system are taken into accountMisc

Page 26: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 26

Differentiation

VirtualProvider

o Access to the remote data via Data Transfer Process (DTP) for access to DataSources or InfoProviders in other

systems

BAPI for external (Non-SAP) systems or

Function Module for custom-defined implementation

Universal Data Integration (UDI)

o As VirtualProvider based on a DataSource

Direct Access

o For InfoObjects as InfoProviders or direct hierarchy access

Valid for all options above: Not mass data capable Performance penalties might

be experienced

Also exposed to query definition as TransientProvider

o Analytical Index

o CompositeProvider

o BW Accelerator with Data Services (Index Designer) Using BusinessObjects Data Services to populate the BW Accelerator

Starting with Data Services release XI 3.2

The target schema is limited to a single fact table

Page 27: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 27

Contents

1. Design Guidelines for the new 7.30 InfoProviders

Semantic Partitioned Object (SPO)

HybridProvider

CompositeProvider

TransientProvider

Miscellaneous

2. Which InfoProvider for which scenario?

3. Summary

Page 28: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 28

General description

– Analytical Index

Definition

An Analytical Index (or the resulting TransientProvider, respectively)

is an InfoProvider defined via the Analytical Process Designer or

published from a logical BWA Index without any data persistency in

the database of the BW system. You can report on it like on every

other InfoProvider. Furthermore, it is used as basis for modeling a

CompositeProvider.

An Analytical Index is a data container in the Analysis Process Design use case

(results calculated from an APD process) whose data is stored directly in the

BW Accelerator In prior releases data could only be persisted in DataStore Objects with option ‘direct

update’ or in a file

A TransientProvider is derived from the Analytical Index

The Analytical Index stores its data in a star schema (contains facts,

characteristic (called dimensions) with attributes and authorization data)

There is an option to define keys for updates of data records

Page 29: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 29

Creation of an AI for Facts via APD

Page 30: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 30

Main advantages

Advantages

Persistency of results generated via APD not only in DataStore Objects with option ‘direct

update’ or in files but directly in an Analytical Index that can immediately be used for

reporting (exposed as TransientProvider to define Queries on)

Ad-hoc reporting on combined data (e.g. BW data + Flat files); Joins via CompositeProvider

directly on Analytical Indexes

Usage for quick and easy prototyping (automatic derivation of InfoObjects )

Creation of Analytical Indexes in a productive environment (no impact on live scenarios)

Creation of ‘volatile’ data that can easily be deleted if not used anymore

Usage of Query with property flag ‘Query is used as InfoProvider’ as a source in the APD

(OLAP features + package-wise read)

Store the result of queries (Cache pre-calculated queries)

Page 31: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 31

Restrictions / Limitations

SAP BW Accelerator has to be in place

Access to BW Backend is neededPrerequisites

After an Analytical Index has been created in a structure, it cannot be

changed anymore

Note New dimensions or attributes (but: copy functionality is available)

cannot be added

Modeling

Do not use the APD/ Analytical Index process if you need proper staging

mechanisms with

An Analytical Index cannot be used as an object in a MultiProviderFeatures

No restore process available for Analytical Indexes

The definition of the Analytical Index is saved in the BW system but is

currently included in CTS

APD is a tool more suited for the technical business analyst (rather in

IT than in the Business Department)

Misc

Page 32: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 32

General description

- BWA only InfoCube

Transaction data is stored on the BWA server and not in the database of the BW

system

The packet dimension index is the only table also filled in BW when transactional

data is loaded (needed to manage requests on BI side)

The master data is saved in the BW system and in the BW Accelerator

The data of the F fact table and E fact table is solely stored in the BW Accelerator

The fact table index is flat (master data SIDs are directly written to the fact index

without dimension indexes except for packet dimension)

SID creation takes place when data is replicated to BWA

For each package processed by DTP one check record is written in the F fact table

(Data Consistency)

Definition

A BWA only InfoCube is an InfoCube with the transaction

data persisted in the BWA only as a flat fact table index to

avoid data redundancy. With this you can save memory in

the BW database and remove load from it

Page 33: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 33

Structure

BW

Source System

BWAInfoCube

(Definition)

Page 34: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 34

Main advantages

Advantages

Saving memory

Avoid data redundancy

Reducing load on database and save system resources for processing

Move of the reporting layer to the BWA server (not the warehouse layer!)

No need to create dimensions according to performance criteria (only for semantic

structuring)

Flat F table index may speed up data-staging (no DIMIDs)

Page 35: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 35

Restrictions / Limitations

SAP BW Accelerator has to be in placePrerequisites

No possibility to create a real-time InfoCube as used in Integrated

Planning which stores data in BWA only (due to open requests)

No automatic recovery mechanism (use DataStore Object as data layer)Modeling

No selective deletion / archiving (also no drop and rebuild)

Usage not feasible when request-wise deletion is done frequently

No compression

o It is not recommended to use this object when many changes are

loaded (reverse bookings)

o If changes are significant, re-index on a regular basis from the

source DataStore Object (data is compressed in active table)

o You cannot use compression with zero elimination

o Not recommended to use with non-cumulative key figures

Features

Misc

No parallel load via DTP (parallelization only inside the DTP)

No possibility to stage with SAP BW 3.x data staging / data flow

mechanisms

Page 36: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 36

Contents

1. Design Guidelines for the new 7.30 InfoProviders

2. Which InfoProvider for which scenario?

3. Summary

Page 37: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 37

The InfoProvider Matrix

SPO Hybrid

Provider

Composite

Provider

Transient

Provider

Analytical

Index

InfoCube

BWA only

Classicfication

in LSA

Merging of data

Support of

AdHoc Reporting

No Data

Persistency

Mass data

capability

Inclusion of real-

time data

Implementation

Effort

Prototyping

BWA relevant

NA

Fully supportedNot supported ….

Operational Data

Store (ODS)

Reporting

Layer

Reporting

Layer

Reporting

Layer

Reporting

LayerAll Layers

Page 38: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 38

If you ...

…want to handle high data

volumes for staging and/or

reporting

…want to minimize

manual modeling times

…want to speed up

design changes for

logical separated data

targets

... then use a

Semantic Partitioned

Object (SPO)

If you...

… want performant

reporting on near

real time data

… are confronted with high

volume of (historical) data

… want to avoid a complex

staging mechanism to

cater for the above

scenario

... then use a

HybridProvider

Which InfoProvider to use in which scenario

If you ...

... Want to do rapid proto-

typing and easily create

ad-hoc scenarios with the

BW Accelerator

… Without the need to extend

existing data models

…With the need to easily

combine data models via

UNION or JOIN

... then use a

CompositeProvider

Page 39: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 39

If you ...

... Want to do rapid proto-

typing and easily create

ad-hoc scenarios with the

BW Accelerator

... Without the need to extend

existing data models

... Without the need for data

consolidation and stable

warehouse loading

processes

... then use an

Analytical Index

If you ...

... Want to perform

operational reporting

... Without replicating the

model and data to SAP BW

... With no data latency for the

end user

... then use a

TransientProvider

Which InfoProvider to use in which scenario?

If you...

... Want to benefit from

the BW Accelerator

not only in terms of query

performance but also for

saving database memory

... Want to structure your data

model only according to

semantic criteria

... Want to move the

reporting layer to the

BW Accelerator

... then use an

InfoCube BWA only

Page 40: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 40

Contents

1. Design Guidelines for the new 7.30 InfoProviders

2. Which InfoProvider for which scenario?

3. Summary

Page 41: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 41

Key takeaways

1The new InfoProviders

are tailored for mass data, facilitate

sophisticated modeling and lower

the TCO / TCD of your BW

implementation

2Think first before your start

Check which InfoProvider is the most

suitable one to support your scneario /

requirements

3The big one and the small ones

Whereas the Sematic Partitioned Object and HybridProvider will

be widely used in an EDW implementation, the CompositeProvider

and TransientProvider, etc. are new approaches to get faster

insight to your data in various places (BWA, Business Suite, etc.)

Page 42: Design Consideration for 7.30 Info Providers

© SAP AG 2010. All rights reserved. / Page 42

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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States 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, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C 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.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warrant.

© Copyright 2010 SAP AG

All Rights Reserved