HybridProvider Structure Based on a DataStore Object
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
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 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.
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.