Professional Documents
Culture Documents
30
InfoProviders
December, 2010
Contents
3. Summary
Accelerated
Reporting
requirements
Decrease
Complexity
SPO
High effort
for manual
Logical Split
modeling
Source1 Source2 Source3 for parallel
processing
High Data
Volume
Definition
The 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.
Advantages
Enables an (enterprise) data warehouse to handle mass data in a better way to improve the
staging performance
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
Leverages SAP NetWeaver BWA as well as partition pruning when accessing partitioned
InfoCubes
Define partitions by customer coding (Business Add-Ins) e.g. flexibly apply rolling time
window scenarios to partitions
3. Summary
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)
Definition
The 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.
Query Runtime
BWA
Query Kyf1 Kyf2
Analytic Engine
Key1
HybridProvider
Key2
InfoCube
DataStore Object
The system automatically determines
whether the data resides in InfoCube or
DataStore Object (Change log) Change Active
Log Records
AIM Delta
Delta Queue DataSource RDA Daemon
Activation
OLTP PSA
Queue
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
Automated update of InfoCube only for RDA loads (normal DTP have to
be scheduled)
Misc A HybridProvider can be part of a MultiProvider. The query-pruning via
RRKMULTIPROVHINT does only work on InfoCubes
3. Summary
Accelerated/
Enterprise BW Accelerated/
Lean
Lean BW
Enterprise BW
Easy modeling environment inside the data warehouse for the IT department for rapid
prototyping with SAP BW Accelerator (BWA)
Conclusion Ad-hoc reporting (Quick temporary scenarios delivered by IT for the business
departments)
Combination of data (e.g. BW data + Flat files)
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
BEx Query
Advantages
Combination of data of Analytical Indexes in BWA via UNION, inner and left outer JOIN
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)
Data types for characteristics in the AI are STRING, DATS and TIMS
Misc Data types for key figures in the AI are Fixed-point and Floating-point
number and Integer
3. Summary
Definition
InfoProvider 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.
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 either
o 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
SAP BW
ERP
ETL
BEX Query MDX BICS (Data Services, )
TransientProvider
Classic
InfoSet ODP Framework
BW DataSource
Advantages
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.)
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
3. Summary
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
The Analytical Index stores its data in a star schema (contains facts,
characteristic (called dimensions) with attributes and authorization data)
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
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)
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 MultiProvider
Features
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
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)
InfoCube BWA
(Definition)
BW
Source System
Advantages
Saving memory
Move of the reporting layer to the BWA server (not the warehouse layer!)
3. Summary
Merging of data
Support of
AdHoc Reporting
No Data
Persistency
Mass data NA
capability
Inclusion of real-
time data
Implementation
Effort
Prototyping
BWA relevant
want performant want to handle high data ... Want to do rapid proto-
reporting on near volumes for staging and/or typing and easily create
real time data reporting ad-hoc scenarios with the
BW Accelerator
want to minimize
are confronted with high
manual modeling times Without the need to extend
volume of (historical) data
existing data models
want to avoid a complex want to speed up With the need to easily
staging mechanism to design changes for combine data models via
cater for the above logical separated data UNION or JOIN
scenario targets
... Want to perform ... Want to do rapid proto- ... Want to benefit from
operational reporting typing and easily create the BW Accelerator
ad-hoc scenarios with the not only in terms of query
... Without replicating the BW Accelerator performance but also for
model and data to SAP BW saving database memory
... Without the need to extend
... With no data latency for the ... Want to structure your data
existing data models
end user model only according to
... Without the need for data semantic criteria
consolidation and stable
warehouse loading ... Want to move the
processes reporting layer to the
BW Accelerator
3. Summary
2
the TCO / TCD of your BW
implementation
Think first before your start
Check which InfoProvider is the most
suitable one to support your scneario /
3
requirements
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.