Hi all,
A couple of questions we're debating internally about the future direction/role of SAP HANA Studio for use with SAP apps on HANA.
With all the new features in SP5 for ABAP on HANA development, is that the future direction and eventually the only supported approach for SAP application development? i.e. do all the development for managed DB Procedures, CDS Views in the app layer and remove the need for Studio access to the db directly?
Will SAP consider now or in the future letting development folks have HANA Studio access is a bit of a back door to the database and circumventing the application level controls around security, lifecycle management etc? Or will it just be to left to each customer site to see if they are more comfortable with a top down approach (app layer development) or they can create db objects in Studio and equivalent data definition entries so the ABAP layer can work with them?
Next question is around XS custom access to the HANA db that is controlled by a SAP app. We have some XS apps right now that have dml access to custom objects in our HANA sidecar implementation, and in the next 6-9 months we hope to consume the replicated schema and custom development objects inside a BW on HANA database. Again if we're allowing a custom application with dml access to a SAP app HANA db (either a different schema or even SAP<SID schema) that has a different security model, independent db users that aren't replicated in the SAP app layer , will this be an issue for SAP support?
We’re trying to minimize re-work so any help here appreciated..
Thanks,
Sean.