in my Job as SAP BI Instructor I regularly get questions like the ones below from my participants.
“What is the future of BEx Query Designer?”
“Which BO client will replace BEx Query Designer?”
“Do I need to learn BEx Query Design if we are using BO clients against our BW system?”
Are you also wondering about that? Are you also uncertain about the use of BEx Query Designer in future?
Here is what I explain my customers…
You might know that the BEx Reporting clients will no longer be enhanced as they all have a Premium Alternative client in the BI client family. Check Table below for details:
|BEx Client||Premium Alternative|
|BEx Web Application Designer||SAP BusinessObjects Design Studio|
|BEx Analyzer||SAP BusinessObjects Analysis, edition for Microsoft Office|
|BEx Web Analyzer||SAP BusinessObjects Analysis, OLAP edition|
|BEx Report Designer||SAP Crystal Reports|
You see that the BEx Query Designer is not part of the list… why?
Most of us BW user would say that the Query Designer is also a frontend client because it comes with the frontend installation. BUT it is not a reporting client. SAP puts the Query Designer to the BW backend because it is a tool that models data for reporting purposes. That is also the reason why you do not find a roadmap for that in the BI clients part at http://service.sap.com/roadmap
As we learned the Query Designer belongs to the BW backend so lets take a look that the corresponding roadmap. Go to http://service.sap.com/roadmap > Database & Technology > Product Roadmaps > SAP NetWeaver Business Warehouse and open that file. On page 9 you will find an entry called “Eclipse based modeling environment in BW (e.g. BW Query Designer, CompositeProvider)“.
Hey what’s that…? BW will get a new BEx Query Designer! Eclipse based like the SAP HANA Studio or Design Studio.
I also found a twitter entry on that with a screenshot in it https://twitter.com/tfxz/status/322677745937178624
So YES the Query will stay THE object you use to create reporting scenarios on BW data. Of course you can connect to an infoprovider directly for ad-hoc scenarios.
Check Creating a Query Using Eclipse Based Query Designer to get a first impression…
Hope that helps.