We have all worked on Composite Providers and usually might end up hitting some problem or the other. The performance improvement of composite provider also brings along various limitations. In this blog, we will detail some of the most common limitations and how to break them!
1) When using Binding Type Union, in a composite Provider, it cannot a have Binding Type Join as one of the part providers. Meaning, only unions among datasets is possible.
Workaround: Create a separate join based composite provider and then add that composite provider under a new composite provider based on the union.
2) When using Binding Type Union or Join, in a composite Provider, it cannot have “External SAP HANA View” generated from a BW Info Provider as a part provider.
Workaround: Instead of using “External SAP HANA View” generated from a BW Info Provider, we can use the active table/inbound table in a Calculation View and in turn consume it in a Composite Provider.
3) An ADSO of template “Write optimized DSO” cannot be added to the composite provider as a part provider.
Rationale: Staging Data Store Object with Inbound Queue Only or Compress Data option, is used in the Staging Layers in BW, which is essentially the replica of the source data and does not add much of business value. In case you would like to do reporting out of Staging Data Store Object, Reporting Enabled option must be enabled.
4) A composite provider that is enabled with “This Composite provider can be added to another composite provider” having Binding Type Union, cannot be used as a right part provider in new composite provider.
Workaround: For Inner join, switch Inputs to make the composite provider as the left part, as results will not be impacted.
If it’s the case of a left outer join, then a composite provider cannot be used as Right provider. Instead, the union of the same can be done and joined as shown below.
5) The “Use this Composite Provider in another Composite Provider” becomes inactive when we create a Composite Provider based with Join Binding Type containing Union as part providers.
Workaround: We can create a composite provider with union type with needed ADSO and then add the same as the left end to the new composite provider based on join with needed conditions.
6) When the composite provider is of binding type “Inner Join”, then it cannot have part providers of type “Left outer”.
Workaround: We can create a left outer join composite provider and enable the option “This composite provider can be used in another composite provider” and then use this under another composite provider of type “Inner Join”.
It’s not the end, there are more to it! Please check the space for the next blog, which details them.
Know more about Visual BI Solutions SAP BW Services offerings here.