Hybrid provideer

of 13 /13
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com © 2011 SAP AG 1 All You Need to Know about HybridProvider in BW 7.30 Applies to: BW 7.30 Summary This paper provides a detailed description of the Semantically Partitioned Object (SPO), released as part of BW 7.30. Author: Rakesh Dilip Kalyankar Company: SAP Global Delivery Created on: 14 November 2011 Author Bio Rakesh is a BW/HANA consultant working with SAP Global Delivery and has extensive BW implementation experience. Prior to SAP Global Delivery, Rakesh was part of the BW R&D team in SAP Labs since 2006; he has worked on the SDLC of latest BW releases like BW 7.30, 7.31 and was responsible for quality of many components of the the EDW.

description

 

Transcript of Hybrid provideer

Page 1: Hybrid provideer

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 1

All You Need to Know about

HybridProvider in BW 7.30

Applies to:

BW 7.30

Summary

This paper provides a detailed description of the Semantically Partitioned Object (SPO), released as part of BW 7.30.

Author: Rakesh Dilip Kalyankar

Company: SAP Global Delivery

Created on: 14 November 2011

Author Bio

Rakesh is a BW/HANA consultant working with SAP Global Delivery and has extensive BW implementation experience. Prior to SAP Global Delivery, Rakesh was part of the BW R&D team in SAP Labs since 2006; he has worked on the SDLC of latest BW releases like BW 7.30, 7.31 and was responsible for quality of many components of the the EDW.

Page 2: Hybrid provideer

All You Need to Know about HybridProvider in BW 7.30

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 2

Table of Contents

Background & Introduction ................................................................................................................................. 3

Use cases for a HybridProvider .......................................................................................................................... 3

Metadata Model .................................................................................................................................................. 3

Components of a HybridProvider ....................................................................................................................... 4

Naming Conventions .......................................................................................................................................... 4

Modeling ............................................................................................................................................................. 5

HybridProviders based on DSO ...................................................................................................................... 5

Hybrid Provider Based on Virtual Provider ................................................................................................... 10

Usage of HybridProviders ................................................................................................................................. 11

Related Content ................................................................................................................................................ 12

Copyright........................................................................................................................................................... 13

Page 3: Hybrid provideer

All You Need to Know about HybridProvider in BW 7.30

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 3

Background & Introduction

The HybridProvider is a new type of InfoProvider introduced with the BW 7.30. HybridProviders are Multiproviders which can hold exactly 2 BW infoproviders. HybridProviders are virtual in sense that they don‟t have separate tables for storing transaction data. In fact, they reuse the InfoCube‟s RSD* tables for metadata management. HybridProviders are typically used for operational reporting and allow reporting on data in a more real-time scenario.

Use cases for a HybridProvider

HybridProviders are useful where reporting needs are real-time. In case of HybridProvider based on a DSO, the DSO can be connected to a real-time datasource and a daemon can fetch data at real-time from the source. The generated DTP (process chain) would push data to the cube and make data available for reporting. With the virtual provider based scenario, both the standard cube and the virtual provider would be connected to a direct access enabled source, and data would be extracted from the standard cube wherever data existed, else data would be extracted from the virtual provider in a direct access mode.

Metadata Model

HybridProviders can be of two types o HybridProvider based on DataStore Object (used in real-time reporting scenario) o HybridProvider based on Virtual Provider (used in direct access reporting scenario)

The HybridProvider has its own TLOGO object – „HYBR‟

A standard InfoCube is always part of the HybridProvider. The cube can be store data on the BW database or can store only on the BW Accelerator (new feature with BW 7.3)

HybridProviders can be created by extending an existing DSO or Virtual provider, or can be created from scratch

If a HybridProvider is created by extending an existing DSO or a virtual provider, they are no longer independent objects. They can only be maintained via the HybridProvider maintenance screen

The DSO included as part of the HybridProvider doesn‟t support non-cumulative KeyFigures

InfoCubes which are part of the HybridProvider support Keyfigures with the SUM aggregation type only

Metadata of the HybridProvider is stored in existing RSDCUBE table, with the CUBETYPE field set to „H‟

HybridProviders are part of the ODS layer and contains operational data. Generally, history data should not be stored in HybridProviders

The transformation between the DSO and the InfoCube cannot be changed

New transformations and DTP‟s cannot be created to the InfoCube

Changes to the metadata of the HybridProvider results in deletion and recreation of the transformations & DTP‟s

Page 4: Hybrid provideer

All You Need to Know about HybridProvider in BW 7.30

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 4

Components of a HybridProvider

When a HybridProvider is activated, the following components are created: o HybridProvider o InfoCube o DSO/Virtual Provider

Along with the above objects, there are a few other objects which are generated by default:

Transformation between the DSO and the InfoCube DTP between the DSO and the InfoCube

Process chain which includes the DTP‟s generated, and supporting objects

Naming Conventions

The technical name of the HybridProvider must contain between 3 and 8 alphanumeric characters

Name of the DSO (generated) = <HYBR Name>O

Name of the Virtual Provider (generated) = <HYBR Name>R

Name of the InfoCube = <HYBR Name>I

Process chain = 8DS<HYBR Name>O

The generated process chains are created automatically and placed under application component

“Created by HybridProvider”

Page 5: Hybrid provideer

All You Need to Know about HybridProvider in BW 7.30

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 5

Modeling

HybridProviders based on DSO

HybridProviders can be created by using the context menu option on an infoarea in rsa1

Page 6: Hybrid provideer

All You Need to Know about HybridProvider in BW 7.30

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 6

Choose the HybridProvider Type as with DSO, and either enter a template DSO, or choose New DSO to model from scratch

Page 7: Hybrid provideer

All You Need to Know about HybridProvider in BW 7.30

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 7

A warning pops up which says the DSO will be integrated with the HybridProvider and can no longer be used independently

Page 8: Hybrid provideer

All You Need to Know about HybridProvider in BW 7.30

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 8

There are two views of the HybridProvider, the InfoCube view (default) and the DSO View. The views display the metadata of the objects. There is a dropdown tab which displays the InfoObjects which are part of only the DSO (or InfoCube, in the DSO View)

Toggle view to maintain DSO metadata

Page 9: Hybrid provideer

All You Need to Know about HybridProvider in BW 7.30

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 9

Activate The HybridProvider can now be connected in a dataflow by creating a transformation between the

source and the DSO part of the HybridProvider HybridProvider in rsa1 and process chain structure

Entries in Table RSDCUBEMULTI

Page 10: Hybrid provideer

All You Need to Know about HybridProvider in BW 7.30

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 10

Hybrid Provider Based on Virtual Provider

Create a new HybridProvider and select the type as with Virtual Provider – New Virtual Provider. The name for the virtual provider is proposed by the system according to the naming conventions

Define the metadata. Note that there are no separate views for the standard cube and virtual provider. All InfoObjects must be present in both the part providers

Page 11: Hybrid provideer

All You Need to Know about HybridProvider in BW 7.30

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 11

Activate To include the HybridProvider in a dataflow, create a transformation and DTP from the source to the

Standard InfoCube A remote DTP is created automatically by the system for the Virtual provider. The transformation

between the source and the Standard cube will be used. Note that the transformation has to be created from the context menu of the source. This option is not enabled from the context menu of the standard InfoCube

Only DataSources can be connected to this HybridProvider Structure of the HybridProvider in rsa1

Usage of HybridProviders

HybridProviders can be used as independent reporting objects and can be used in queries which can then be used in complex web applications. They can be integrated in multiproviders as source objects. HybridProviders cannot be used as source objects in a dataflow.

Page 12: Hybrid provideer

All You Need to Know about HybridProvider in BW 7.30

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 12

Related Content

HybridProvider reference 1 HybridProvider Reference 2 HybridProvider Reference 3

Page 13: Hybrid provideer

All You Need to Know about HybridProvider in BW 7.30

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 13

Copyright

© Copyright 2011 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, 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 Oracle Corporation.

JavaScript is a registered trademark of Oracle Corporation, 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 warranty.