- 如何使用代码创建和读取 SAP CRM 订单的 Text 数据
- SAP CRM Fiori 应用 My Note 里创建 Not
- 从SAP客户主数据里直接创建商机(Opportunity)
- 在 SAP CRM Fiori 应用上给 Opportunity
- SAP CRM Fiori 应用 My Opportunity
- 点击 Fiori Launchpad tile 后报错的处理方法
- SAP CRM Fiori应用My note的技术实现
- SAP CRM Fiori 应用 my Opportunitie
- SAP Fiori 的附件处理(Attachment handl
- SAP UI5和Angularjs事件处理机制的实现比较
Now I found root cause.

and this note Z004 has been successfully created in the buffer, not persisted to Database yet.
Then during order save, there is one BAdI implementation done by Zeiss:

And there is a logging rule defined by Zeiss:



And in My Opportunity, only the text type with Log type ( column Changes = P ) or edit type ( column Changes = " " ) are supported.
And in customizing, only text type ZR00 and Z004 can be supported in Fiori. Even all the content of Z004 has been copied to 0004, since 0004 is neither log type nor edit type, it will completely be ignored by Fiori. And the content of Z004 is deleted by BAdI on purpose, so finally no text is displayed in UI.

This behavior can also be observed in Webui:

After I click save button, the content of Z004 is merged into 0004. Z004 is gone from UI:


My question is: why Zeiss didn't use the standard log type? Is there any specific function gap they found against the standard log type?

Anyway, if they would like to still use current solution, please clear the checkbox in column CLEAR_SOURCE_ID, then they can see the internal note in Fiori. At that time the internal note in Fiori will behave exactly the same as "Reason note".

更多Jerry的原创文章,尽在:"汪子熙":

网友评论