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 to the DataStore object in delta mode. The daemon activates the data immediately. Next the data is loaded from the change log of the DataStore object to the InfoCube. The InfoCube acts as an aggregate for the DataStore object.
If you create a process chain to transfer data into the DataStore object of the HybridProvider, 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. Since it uses an InfoCube, the system does not take as long to access data for analysis and reporting purposes.
Changeability
The 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 separately, that is, independent of the HybridProvider.
Constraints
Since the HybridProvider is a combination of a DataStore object and an InfoCube, the constraints that apply to the InfoProvider apply equally 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 its own transport object. 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 recommend, therefore, that you delete data from the HybridProvider if it exceeds a certain age or store it elsewhere.