User Interface for Hybrid Providers
My First Impressions of the new Interface for creating HybridProviders;
From transaction RSA1 there is a new option to create hybrid provider which brings me to the screen above.
There are two types of HybridProviders, based either on a Datastore Object or on a Virtual Provider. There is always an infocube associated with one of these objects.
In the latter type, the Virtual Provider will contain the same objects as the infocube.
For the first type, it is possible to have more objects in the DSO than in the infocube. This is to allow for scenarios where data can be loaded with more detail in the DSO, then aggregated in the Infocube. So the question was how the user interface would handle this;
Above is the Datastore view, here you can define the structure of the object just like creating a standard DSO. Nothing new here. When you have entered the required InfoObjects you click on the infocube button in the “View “field to switch to Infocube maintanance;
There is a new field “Contained in Datastore Only”. This folder contains all of the objects that you have defined in the datastore but have yet to be assigned to the dimensions or key figures of the cube. Its easy to create the dimensions and key figures by drag and drop from this folder, similar to creating a cube from scratch. You can still activate the HybridProvider if there are objects contained in this folder.
If you assign an infoobject to a dimension and this infoobject is not known in the DSO, you are faced with the following when you return to the DSO view;
In this case it is not possible to activate the HybridProvider until the infoobject is assigned to the key fields or datafields of the DSO. The exclamation mark highlights this point!
On activating the HybridProvider, the system also generates the transformation required to load data between the DSO and infocube. This is not required if the infocube data is stored persistently in BWA.
Finally some details on the database tables, which may be useful for troubleshooting in the future;
You can search for Hybrid providers using RSDCUBE-CUBETYPE = H
Here you can see the relation between HybridProvider, Infocube and DSO. My HybridProvider is VJHPR1, the infocube is VJHPR1I and the DSO is VJHPR1O.
The HybridProvider itself does not have dimension tables but instead takes the dimensions from the underlying infocube VJHPR1I.
So all in all its a simple process to create and maintain the HybridProvider. Lets see what kind of issues will arise