The ABAP RESTful Application Programming Model (RAP) is at the heart of the new ABAP Cloud development model for building transactional OData-based SAP Fiori apps and Web APIs on the SAP BTP ABAP environment and SAP S/4HANA, in the cloud and on-premises.
Join this session to learn more about recently delivered RAP features.
Speaker: André Fischer, SAP
After watching the session, be sure to complete the validation tutorial to earn points for Devtoberfest! https://developers.sap.com/tutorials/devtoberfest2023-week2-abap-cap-whatnewrap.html
Nice session Andre!
Do you know when to expect the Deep Update feature without the need of intercepting the PATCH or without using an action? In other words, when would OData version be upgraded to version 4.1?
The presentation was nice, I hope we will see an example of consuming locally events from SAP standard objects for example from Sales Order without Event Mesh. I do not understand in this case how exactly is the event (for example Sales Order Created) propagated to the local handler.
I did some research and I doubt that the scenario with extension/derivation of event Created for Sales Order is possible. When I look at root entity R_SalesOrderTP, I cannot see any "Created" event. If I want to extend/derive something it has to exist. It seems to me, that SAP public API is built over CDS views, but Business Events are currently built over classical SWO1 Objects or its classes equivalent. For classic Events (like BUS2032->Created) are somehow wrapped and propagated further as Business Events and consumed by Event Mesh. Because of the fact that such events are not part of OData, it limits its local usage in OData behavior. You can somehow consume them in classical way on premise using custom receiver type. Please correct me if I am wrong.