- Part1 – how to test odata service generated by CDS view
- Part2 – what objects are automatically generated after you activate one CDS view
- Part3 – this blog
- Part4 – how does annotation @OData.publish work
- Part5 – how to create CDS view which supports navigation in OData service
- Part6 – consume table function in CDS view
- Part7 – unveil the secret of @ObjectModel.readOnly
- Part8 – my summary of different approaches for annotation declaration and generation
- Part9 – cube view and query view
- Part10 – How does CDS view key user extensibility work in S4/HANA
- Part11 – CDS view test double framework
- Part12 – CDS view source code count tool
- Part13 – CDS view authorization
Let’s review what we have learned so far. Through SQL trace and debugging, we have learned below:
1. When we click activate button in ABAP development tool ( I call it Eclipse now in this blog ), there are several corresponding ABAP objects generated and table entries inserted. Through debugging we know lots of related logic are implemented in package SDDL.
2. When we test read & search function against the odata service created on top of the CDS view, the operation is delegated to CL_SQL_STATEMENT~EXECUTE_QUERY.
And now I ask myself, since what we have typed in Eclipse is pure text, how does ABAP backend interpret the text and convert it into ABAP DDIC objects? The only hint we have is the SDDL package. There are more than 10 classes in it. Although an experienced ABAP developer can easily identify which class is responsible for the text->ABAP view conversion just according to the class name and description, whereas ABAP newbies need more time to practice their intuition.
The tip here is, if you are not sure which class is what you are looking for, then always start with what you have already known. In our case it is CL_SQL_STATEMENT~EXECUTE_QUERY. Set breakpoint on this method and type some more characters in Eclipse, the breakpoint is triggered immediately.
From the callstack, we know that every time after you type something in Eclipse, it will fire Syntax check request to ABAP backend.
You can observe this via in the bottom part of your Eclipse.
From the callstack we find a class CL_DD_DDL_HANDLER which implements interface IF_DD_DDL_HANDLER which seems is what we look for. Open this class and there is a method GET_VIEWDEF_FROM_SRC, which indicates the method converts the SouRCe code to ABAP VIEW–DEFinition. Set breakpoint in it and click activate button again in Eclipse.
This class will parse source code:
From the code, it is very clear that the parse output, view definition in ABAP format is used to generate ABAP database view.
There is also another approach which can allow you to get a clearer view:
Open the “ABAP Communication Log” view:
Switch on Logging:
Then make some dummy change on your view, then you can observe the following six requests sent to ABAP backend.
The highlighted “abapCheckRun” is just the syntax check we already learned.
Double click on the request to see request detail. Here the view source code is encoded in Base64 format stored in chkrun:content.
We can of course see the original text from some decode-encode online conversion website:
When you click activate button in Eclipse, you can know that a syntax check is always performed before the real activation.