CDS BOPF as the new paradigm for creating Fiori OData services - or is it?

[js2]

We are being presented with the new ABAP Development technique from ABAP 7.50 for OData services of using CDS views and annotations to generate BOPF objects for the write-side.

What has me scratching my head with this whole CDS/BOPF thing is that it seems to be designed around completely separate custom data tables as the data source.

The reality of real-life is that you nearly always need to integrate with standard sap business processes... For example you will need to call BAPI's to post purchase orders or goods movements or whatever... Not just on the write-side either - often its far easier to get the correct data out of the system by calling a bapi like BAPI_PR_GETDETAIL for example (just try reading PR's, PO's that have service entries, etc).

It seems that this technique of using CDS annotations to auto-generate a BOPF object will not work for these more real-life scenarios... Or am I missing something and it is just that all tutorials on this subject are extremely basic using a Z table?!?

Is there an "extension" concept for these generated BOPF objects so that you can code your own ABAP update routines?

Because... if there isn't then this whole CDS/BOPF is purely academic. Great for creating mars explorer demos at a TechEd keynote... but thats about it... 😉

[former_member86745]

My question is that for using CDS view, we need to know the SAP tables inside and out for all the fields for a table and rules but then it wouldn't count the customer enhancements. Can we build CDS views with BAPI call to check the output? I've always used BAPI or FM to report. This way all the customer enhancement at least at the Business Object layer include automatically in the reporting. Is this something in plan with SAP?