BO Dashboards 4.0 - Data binding options with Bex Queries

[Former Member]

Hello, BO experts.

I am currently analyzing connectivity options between BO Dashboards 4.0 (ex-Xcelsius) and BW Bex queries. Our client´s requirement is to leverage as much as possible the investment they already have in Bex Queries. I hope you can help me to further understand the data binding possibilities/limitations that I have for this scenario.

Based on my initial analysis I found 2 ways to connect Bex Queries to BO Dashboards:

- BICS (Sap Netweaver BW Connection)

- BO Query Browser *NEW feature in Dashboards 4.0*

It would be nice to use the new feature u201CBO Query Browseru201D to implement direct data binding from queries to components in the canvas (avoiding ranges in the spreadsheet). However, it looks that it is only possible to use the u201CBO Query Browseru201D on available .unx BO Universes (cannot connect directly to the Bex Query). Furthermore, these .unx Universes can only be based on the fact/master/text tables of an InfoProvider (a universe can no longer be based on a BEx query).

Question 1) It looks that I cannot use the u201CBO Query Browseru201D with the existing Bex Queries; I would have to create a .unx based on an InfoProvider (not Bex). Do you have a different view/experience on this?

My conclusion is that -based on the requirement to leverage as much as possible the investment on Bex Queries- the only option that would work is the BICS connection. This option cannot leverage the direct data binding available for the u201CBO Query Browseru201D (avoiding the spreadsheet) and I have also found some other cons: 1) there are problems with hierarchies; 2) Deploying BO Dashboards to BO Enterprise using BICS not possible yet (Dashboards could be deployed via NW Portal Bex iViews).

Question 2) Have you already explored the BICS connection in BO Dashboards 4.0? Could you share your findings/conclusions/workarounds?

Many thanks in advance.

Leticia

[Former Member · Accepted solution]

Dear Leticia

I would also like to add a special warning.

If you decide to use the so called direct BW connectivity (from SAP menu of Xcelsius and so on...) you will not be able to

publish anymore the dashboard to the BO portal Launch Pad.

This is strange but it looks to be a key point: unfortunately we have to have a clear mind on where we will publish the dashboard (and this from the beginning).

Think about it.

best regards

Luca

[Former Member · Accepted solution]

Hi Luca, thanks for your input.

I am aware of the publishing limitations you mention. I will analyze my proof of concept scenario considering the publishing environment and test the options you mentioned.

Your answers helped me a lot so far. I will close this thread and assign points.

[Former Member]

Dear Leticia

I would like to underline that the Live Office - Interactive Analysis document with BICS connection IS a BICS

approach and this is the most promising approach in terms of performance and closest to SAP roadmap.

The Quaaws approach should work as well but it would imply the Universe maintenance.

On my opinion this is not best practice even if I cannot provide you with a SAP statement.

If Hingo Hilgefort should read this thread he could state it.

best regards

Luca

[Former Member]

Dear Leticia

you have raised "huge" questions.

I hereby share our current experience and understanding on this topic that is not currently well explained.

We have just installed 4.0 SP02 patch 4 on top of BW 7.01 SP07.

Two considerations:

1) the so called direct BW connectivity looks reserved to pubblication on SAP EP (Enterprise Portal) and only that.

It requires the BW java runtime environment and also pubblication to power point looks inhibited.

Therefore if you have to publish the dashboard on EP this is the way.

2) Someone defines the above mentioned approach as the BICS connectivity. This can be misleading because the BICS

connectivity can be applied also in another scenario: if you have to publish the dashboard on Launch Pad (formerly called Infoview) or to power point the approach should be the following:

a) definition of a BICS connection by means of the new client tool IDT (Information Designer Tool); take a look at:

http://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/60ad3c37-b90f-2e10-da88-cbadc6f6fed1

b) definition of an Interactive Analysis document within the Launch Pad portal: in practice hereby you create a WEBI

report with NO need of a Universe: the BICS connection defined at point a) permits a direct connection to the Bex Query.

c) from within Dashboard Design you have to use Live Office as additional tool: from the bar of Live Office version 4.0 you

will recognize the Interactive Analysis button: this will permit a binding to the Interactive Analysis document.

As a reference please also take into account note 1464937 that states how important is the Live Office role.

hope this helps

Luca

[Former Member]

Hi Luca, many thanks for your reply.

In fact, yesterday was suggested to me to try to use a Webi report as my source in Xcelsius instead or BICS connection (exactly as you explained it). This would indeed solve my problem if we decide to publish in the BO portal instead of BW.

Some other colleague also suggested QaaWS instead of BICS. Do you know if this would allow the publication in the BO portal too?

Thanks again, your answer was very helpful !

Leticia