CREATING HYBRIDPROVIDERS

PDF download from SAP Help Portal: http://help.sap.com/saphelp_nw74/helpdata/en/4a/0905c133e00890e10000000a421937/frameset.htm Created on February 10, 2014
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

Note This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2014 SAP AG or an SAP affiliate company. 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. National product specifications may vary. 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. SAP 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. Please see www.sap.com/corporateen/legal/copyright/index.epx#trademark for additional trademark information and notices.

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 1 of 5

TABLE OF CONTENT
1 Creating HybridProviders 1.1 HybridProvider Structure Based on a DataStore Object 1.2 Structure of HybridProviders Based on Direct Access

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 2 of 5

1 Creating HybridProviders
Use Due to its 'hybrid' architecture, the HybridProvider provides faster access to data when you analyze data in queries. "Hybrid" means that historic data is combined with a small set of new data. This ensures good system performance, for example, when you analyze data in a query that has real-time data. There are two types of HybridProvider: HybridProviders based on a DataStore object and HybridProviders based on direct access. The HybridProvider based on a DataStore object is a combination of DataStore object and InfoCube. The newest data here is in the DataStore object. The InfoCube serves as an aggregate. By storing the InfoCube data in the BW Accelerator, you indirectly index DataStore object data there too. The HybridProvider on direct access is based on a combination of VirtualProvider and InfoCube. The newest data is not replicated into BW. It is read directly in the source system using the VitualProvider instead. Differences between the two types of HybridProvider: HybridProviders based on a DataStore object: You should use a HybridProvider based on a DataStore object as the InfoProvider when you load data using real-time data acquisition. A data transfer process for real-time data acquisition fills the DataStore object in the HybridProvider with current data in real time. The daemon for real-time data acquisition activates this data, ensuring that the data is immediately available for analysis purposes. However, it can also be used independent of real-time data acquisition. You can load data from any type of source. All of the data is stored in the BW system or in the BW Accelerator. More information: HybridProvider Structure Based on a DataStore Object Real-Time Data Acquisition HybridProviders based on direct access: You have access to real-time data without having to set up real-time data acquisition. There is no wait time as compared to real-time data acquisition, where the data is available in real time but not immediately. You can load data from a specific DataSource only. More information: Structure of HybridProviders Based on Direct Access Procedure 1. Follow the general procedure for creating an InfoProvider. All HybridProvider-specific settings are described below. More information: Creating InfoProviders
2.

On the screen for creating the InfoProvider, you can choose whether the data of the relevant InfoCube is stored in the BW system or in the BW Accelerator. More information: InfoCube with Data Persistency in the BWA

3.

Choose the HybridProvider type: Either based on a DataStore object or direct access, that is, based on a VirtualProvider. You can create a new object or choose an existing one. You should choose an existing object if you want to extend an existing InfoProvider into a HybridProvider with environment (possibly data, transformation rules, queries, and so on).

Note
If you choose an existing DataStore object (DataStore object or VirtualProvider), it is no longer an independent object. It can only be used as part of the HybridProvider.
4. 5.

Choose

Create.

The remaining procedure is the same as that for creating DataStore objects and InfoCubes (VirtualProviders are created in the same ways as InfoCubes). See: Creating DataStore Objects Creating InfoCubes When you create new objects, the HybridProvider initially does not contain any InfoObjects. If the underlying InfoProvider already exists, the HybridProvider contains these InfoObjects and can be extended to include further ones. The associated, required InfoCube is created in any case. There are two views for modeling a HybridProvider based on a DataStore object: A DataStore view and an InfoCube view. You can switch between the two views by choosing Settings View . If you add or delete InfoObjects in one view, the system automatically applies the change to both objects. Both objects contain the same InfoObjects. There is one exception to this: The DataStore object can contain additional InfoObjects that are not included in the InfoCube. In the InfoCube view, you assign these InfoObjects to the Contained in DataStore Only folder. These InfoObjects are no longer available in the Query Designer.

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 3 of 5

HybridProviders based on direct access do not have two views because the two InfoProviders in question are identical.

Note
Note that key figures with the aggregation MAX or MIN cannot be used in HybridProvider queries. For this reason, you receive a warning if you attempt to add one of these key figures to a HybridProvider.
6.

Save the HybridProvider and activate it. When HybridProviders based on a DataStore object are activated, the data transfer process, transformation between the two objects, and the associated process chain are generated at the same time.

Note
If the system does not generate the relevant objects automatically, you can generate them manually. To do so, choose Environment Generate Data Flow Environment . Next Step: For HybridProviders based on DataStore objects, see Real-Time Data Acquisition. For HybridProviders based on direct access: Link the HybridProvider to a DataSource. You access this function in the context menu for the InfoCube of the HybridProvider in the InfoProvider tree. Create a transformation and data transfer process for this. The system creates a second data transfer process that links the VirtualProvider of the HybridProvider to the DataSource using the same transformation.

Note
Only DataSources are available as sources for the HybridProvider based on direct access. You can create only one data transfer process and transformation for this.

1.1 HybridProvider Structure Based on a DataStore Object

Use The HybridProvider based on a DataStore object is a combination of DataStore object and InfoCube. When this HybridProvider is activated, the objects required to control the data flow are also generated at the same time: the data transfer process and the transformation between DataStore object and InfoCube, as well as the associated process chain. The graphic below shows the data flow in a HybridProvider based on a DataStore object:

The data transfer process for real-time data acquisition loads the data into the DataStore object in delta mode. The data is then activated immediately by the daemon. The data is then loaded from to the InfoCube the DataStore object's change log. The InfoCube acts as an aggregate for the DataStore object. When the query is executed on the HybridProvider, the system by default only reads data from the InfoCube. To read the delta from the DataStore object, you need to change the request status in BEx Query Designer. To do this, choose are read. If request status 7 or 9 is set, the system only reads the delta from the DataStore object. If you create a process chain to transfer data to the HybridProvider's DataStore object, the system automatically proposes the generated process chain, which updates the data to the InfoCube, as the subsequent process. The system starts this process chain automatically when the request in the DataStore object closes. The HybridProvider is part of the operational data store layer. Using an InfoCube reduces access times for analysis and reporting. Changeability Transformation between a DataStore object and an InfoCube is a 1:1 assignment. This assignment cannot be changed. Properties Advanced in BEx Query Designer and select request status 2. With this request status, both the data in the InfoCube and the data in the DataStore object

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 4 of 5

You cannot manually create additional data transfer processes or transformations for the InfoCube. Data transfer to the InfoCube can only be performed using the generated objects. If you change the HybridProvider and reactivate it, the system deletes the related data transfer process and transformation and regenerates them. You cannot edit the InfoProviders associated with the HybridProvider independently of the HybridProvider. Constraints Since the HybridProvider is a combination of a DataStore object and an InfoCube, the constraints that apply to the InfoProvider also apply to the HybridProvider. The DataStore object does not support non-cumulative key figures. The InfoCube only supports key figures with aggregation type SUM. Transport The HybridProvider is a transport object in its own right. The metadata of a HybridProvider comprises the properties of the InfoCube and the properties of the DataStore object/VirtualProvider. Information Lifecycle Management HybridProviders are part of the operational data store layer. This layer should only contain data that is relevant to operational transactions. It should not contain the entire history of the data. We therefore recommend deleting data from the HybridProvider or storing it somewher else once it exceeds a certain age.

1.2 Structure of HybridProviders Based on Direct Access

Concept The HybridProvider on direct access is based on a combination of VirtualProvider and InfoCube. Both objects have the same structure. When you edit the HybridProvider, you edit both InfoProviders in the same way. The data is loaded using a data transfer process that you create from the InfoCube of the DataSource. The system also creates a data transfer process between VirtualProvider and DataSource, that uses the same transformation. The graphic below shows the data flow in a HybridProvider based on direct access:

When the query is executed on the HybridProvider, most of the data is read from the InfoCube. The most up to date data is also read from the source system using the VirtualProvider. Only the data that has not been loaded into the InfoCube is read. In BEx Query Designer, go to Properties Advanced and set the request status Hybrid Delta. The request status Hybrid Delta is not supported by all DataSources that can be connected to a HybridProvider however. In other words, you cannot always read the most up to date data from the source system due to technical reasons. However the use of a HybridProvider based on a direct access is still recommended. In this case, use the request status Switch. This means that the data is read either from the InfoCube or from the VirtualProvider. Using a variable, you can control what data is read while the query is running. With the HybridProvider based on direct access, you can only load data from a single DataSource. The DataSource must fulfill the following requirements (depending on the read mode being used): Switch: The DataSource must support direct access. Hybrid delta: The DataSource must support direct access. The DataSource must be a generic DataSource with generic delta and meet the following conditions: You cannot maintain the lower safety interval due to the risk of duplicate data records. The delta must be InfoCube-enabled. For more information on the generic delta, see Delta Transfer Settings. The source system of the DataSource must have PI_BASIS 7.02 or higher.

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 5 of 5