on 12-19-2022 9:18 PM
Hi, Would like to get some firm definition or thoughts from other developers out there on this CDS Query vs BEx Query tug of war.
Been trying to stick with CDS Query building, but finding too many deficiencies when compared to BEx Query!
My feeling is that SAP would really like us to use the CDS Analytical Query Road.
The only direction I can find is to use CDS Query as an initial effort and then BEx Query for anything where CDS Query cannot provide the needed functionality. This seems to have been the route for quite a few years now so I don't know if SAP is making an effort to level the playing field between the two.
My biggest probs with CDS View the dynamic periods columns like BEx can do.
So I'm considering all out BEx Query effort going forward for my team due to the CDS Query shortcomings.
To justify this I have a couple of questions I'd like to get from the community
1. Are you using both CDS and BEx Query strategy?
2. Is SAP trying to level the functionality gap between CDS and BEx Query? Been sooo long.
3. Will it be a problem going all BEx Query Development down the line somehow?
(Like from a security method or converting from BEx to CDS Query later on)
Thanks for any input!
Hi Kenneth,
A few months back I worked on an S4 Implementation on an existing SAP landscape containing ECC and BW. There are a few reasons why the client could not move away from BW - mostly related to 2 reasons : existing end-user reporting tool deployment and data lineage - some non-SAP systems.
But with the analytical reporting we needed in S4, CDS was the way to go. Those primarily covered finance analytical reporting over 1m-5m records per hit. The frontends were the Analytical Query Tool, Custom Fiori Apps, KPI reporting. There were a few cases, where we needed to deliver reporting to non-S4 users and we had CDS exposed as Transient Providers to BI and then Bex Query from there.
Anyway, CDS is primarily an S4 solution. If your data is primarily residing in S4, it would be the preferred solution. On BI assets - Bex would be the main frontend. And like my client - there would be business cases for that. It would also make sense to have other reporting tools outside of that scope within the Enterprise.
Hope the perspective helped,
regards,
Wilbert 🙂
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
79 | |
9 | |
9 | |
7 | |
7 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.