I'd like to find documents about how SADL works in details?

[cain_sun]

Hi experienced ABAPers,

recently, I am studying the new programing model of CDS and ABAP 7.5 and the concepts of stateless/ful. After some demos to show data on UI5, draft BO table for flights soft bookings, questions occur to me that how these annotations works in CDS view, which create BO, ODATA service automatically. In the ADT help content, I found these annotations will be consumed by SADL in runtime. But I failed to find any details about SADL. I am interested in how this new engine works. Such as:

1 what is the framework/component diagram of it?

2 How does it work with ODATA or BOPF? how does it work in runtime?

3 Any limitations of it? such as update? or deep data model(sub BOs)?

4 Does it only work with CDS view? CDS view is the source or importing data of the SADL? And SADL will generate corresponding design time objects like BO or ODATA later automatically? How can I know which annotation will lead to which action/creation?

thanks and regards.

[UweFetzer_se38]

A good starting point you can find in the SAP Help Library already: Consuming Business Entities with SADL

[cain_sun]

Thank you!

[cain_sun]

Currently, I think SADL is a group of classes which interpret ODATA request into SQL statements based on the type of binding of ODATA entity. It is used to meet the code push down model and triggered by ODATA DPC. In other words, it is some dynamic run time adapter for data model like DDIC, CDS or BOPF to manipulate the data requested by ODATA service.