Creating HybridProviders 
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.
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.
More information:
HybridProvider Structure Based on a DataStore Object
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
Follow the general procedure for creating an InfoProvider. All HybridProvider-specific settings are described below.
More information: Creating InfoProviders
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
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.
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:
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 . 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.
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.
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 .
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.