目录
- Part1 – how to test odata service generated by CDS view
- Part2 – what objects are automatically generate after you activate one CDS view
- Part3 – how is view source in Eclipse converted to ABAP view in the backend
- 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 – this blog
- Part11 – CDS view test double framework
- Part12 – CDS view source code count tool
- Part13 – CDS view authorization
There is a good blog regarding key user extensibility tool in S4 written by Thomas Schneider.
One of supported feature is customer can easily add new fields to extensible CDS view without knowing technical detail.
For example, if a given CDS view is marked as “UI Reports” extensible in extensibility registration tcode SCFD_REGISTRY,
it means this CDS view would be visible in key user extensibility tool in S4, in tab “UIs and Reports”, so that end user can simply click “Enable Usage” button to add extension field to the view. In the screenshot below, it shows my Extension field “JDK Minimum version” has already been extended to view I_PRODUCTWD.
Now, just use the single line below, and you can read all fields of this view, standard fields and extension fields:
SELECT SINGLE * INTO @DATA(ls_data) FROM i_productwd WHERE
product = 'JAVA'.
So this CDS view extensibility is really easy to use for application developer.
However, how all these whole scenario work under the hood?
When trying to search the source code of extended CDS view by fragment of extension field name JDK, nothing found. This makes sense since none of SAP extensibility tool will directly MODIFY standard object.
Hover the mouse to this small icon in CDS view and you can see lots of extension view, which holds extension fields created by key user tool.
However how could I quickly locate which extension view holds my extension field “JDK Minimum Version”?
Open the SQL view of CDS view I_PRODUCTWD, it is IPRODUCTWD in SE11. Search by keyword JDK and I find the extension field is added to this SQL view via append ZZ1_2CC44DDD3F1C.
Double click this append, then you can find the name of CDS extension view which holds this extension field: ZZ1_PRE47GXHDI6P2ZLO3ADGY4HHFE
Now go back to ABAP studio, locate CDS extension view ZZ1_PRE47GXHDI6P2ZLO3ADGY4HHFE and open it:
Here you can see that in this automatically generated CDS extension view, my extension field are there.
The standard view I_PRODUCTWD is extended by extension view ZZ1_PRE47GXHDI6P2ZLO3ADGY4HHFE via key word “extend view”, as a result the extension field ZZ1_JDKMinimumversion_PRD in ZZ1_PRE47GXHDI6P2ZLO3ADGY4HHFE will also be visible in view ZZ1_PRE47GXHDI6P2ZLO3ADGY4HHFE.
Last question, how and when the extension view ZZ1_PRE47GXHDI6P2ZLO3ADGY4HHFE is generated? We can simply do testing by disable the usage of my extension field on view I_PRODUCTWD by click button “Disable Usage”.
Once done, the extension field disappears from view I_PRODUCTWD,
This observation proves that the extension view will only be generated after we click “Enable Usage” and publish the change. When we click publish button, there are totally 10 enhancements to be generated for my extension field:
The first three rows are CDS extension view to be generated. Double click each and write down detail:
And extension view ZZ1_PRE47GXHDI6P2ZLO3ADGY4HHFE will be generated to extend I_PRODUCTWD:
The left code is responsible to generate extension view which I am not intrested in. What I am curious about is how the internal table mt_enhancements of CL_CFD_ENHANCEMENT_ITERATOR is filled. It is filled in method determine_generation_scope:
In this method, the task to generate CDS extension view for view I_PRODUCTWD is added to enhancement scope, which will be executed later.
All these ten instances will be generated, to make the whole CDS view extensibility work.
要获取更多Jerry的原创文章,请关注公众号"汪子熙":
相关推荐
SAP S/4HANA and SAP S/4HANA Cloud Extensibility for Customers and Partners September 2018 The experience gained from various customer and partner projects has made one thing very clear: Most SAP S/4...
sap press doc 解压密码:abap_developer
可扩展性 WixToolset.Extensibility-用于扩展WiX工具集的接口
使用Managed Extensibility Framework方便的扩展应用程序
JMP Extensibility Synergy with MATLAB JMP 可扩展性与 MATLAB 的协同作用.pdf
Pro ASP.NET Extensibility
很棒的Visual Studio可扩展性 Visual Studio可扩展性资源真棒列表。 扩展名 在开发VS扩展时特别有用的VS扩展: —帮助最小化内存流量(又称GC压力)。 较小扩展名的通用礼节,较大扩展名的必要性。 指导方针和出版 ...
QTP WEB Extensibility的视频教程.rar
The API includes extensibility points that enable third parties to author custom cache implementations and make them available through a common set of APIs. Additionally the tentative plan is to ...
Neos UI的可扩展性示例 请参阅“资源/专用”和Configuration / Settings.yaml中的示例。 要查看API,请检查。 安装 cd Packages/Application/ git clone git@github....
XAML Designer可扩展性文档和示例从Visual Studio 2019版本16.3开始,XAML设计器支持两种不同的体系结构:设计器隔离体系结构和更新的表面隔离体系结构。 详细解释了这些更改。 文件夹包含演示如何使用XAML设计器可...
QTP9.5 Web Extensibility WebEvent视频教程截图.rar
兽人可扩展性 姓名 徽章 聊天 资料下载 稳定版 不稳定版本 该库提供了一些类来支持应用程序内部的可插拔组件(发现,实例化等)。 有关文档,请访问
Professional Visual Studio 2008 Extensibility,网上最清晰资源!
Visual Studio 扩展性示例 这些示例演示了如何自定义 Visual Studio IDE 和编辑器的外观和行为。 以下是扩展 Visual Studio 的一些方法: 向 IDE 添加命令、按钮、菜单和其他 UI 元素 为新功能添加工具窗口 在 ...
Microsoft.Windows.Design.Extensibility.dll
Professional VS 2008 Extensibility是讲如何扩展VS 2008的好书。
office open xml官方文档的第5部分,Markup Compatibility and Extensibility
Managed Extensibility Framework(MEF)是.NET平台下的一个扩展性管理框架
需要写visualstudio插件的同学可以看看