标题：One order extensibility in S4HANA for Customer Management

In SAP CRM we use Application Enhancement Tool(AET) to create extension field in a very convenient way.

When I was working on SAP CRM, I have also made some research on AET. Here below are some of my blogs in SAP community:

Insight into calculated fields created by AET
How extension field created by AET is rendered in Web Client UI
Define your extension field with custom behavior in AET
Create extension field with type Code List via AET
How to create new table as assignment block in service order overview page via AET
Inside AET: why “create field” button is visible in some UI while invisible in others?

In S/4HANA for Customer Management(called S4CRM for short in the following part of this blog), AET should no longer be used, since S/4HANA has its own extensibility tool, which instead should be used to create extension fields on S4CRM model like Product and One Order.

We are aware of the fact that there are indeed some features supported by CRM AET which is not available in current S/4 Key User Extension tool(KUT).
For example, there are some field type provided by CRM AET but not possible in S/4 KUT:

However this small limitation could never become a real showstopper in business process, so currently we leave it in S/4HANA for Customer Management 1.0.

How to create extension field using S/4HANA extension tool

Click tile “Custom Fields and Logic”:

Create a new extension field:

Specify field detail. The field creation UI looks almost the same as the one in CRM AET:

Select the created extension field and press “Publish” button in footer toolbar, which works as the “Save and Generate” button in CRM AET. Once done, the status should become “Published”.

Check CRMS4D_SERV_H in backend to ensure that the extension field appears in persistence table successfully.

Why the extension field is visible in CRMS4D_SERV_H? Launch S/4HANA tcode SCFD_REGISTRY, and double click the Business Context CRMS4_SERV_H, which is actually the technical model for business context “Service Header” visible in S/4HANA extension field UI.

The persistence include CRMS4S_SERV_H_INCL_EEW_PS is defined in this business context, and is included by CRMS4D_SERV_H. As a result, whenever an extension field is created based on business context CRMS4_SERV_H, the extension field will be available in include structure CRMS4S_SERV_H_INCL_EEW_PS and then automatically available in CRMS4D_SERV_H.

How to put S/4HANA extension field to CRM WebClient UI

In S/4HANA for Customer Management, all custom fields added through S/4HANA Extensibility tool will only be available in Customer_H/Customer_I BOL Component or context nodes.

However if you open BT116H_SRVO/Details in SAP CRM, you find that by default context node CUSTOMERH is not exposed.

Please follow the blog Enhancing a UI Component in CRM Web UI to expose CUSTOMERH in CRM UI component workbench. Use tcode SM34 and maintain view Cluster BSPWDVC_CMP_EXT to define an enhancement set ZCRMS4.

Expose context node CUSTOMERH and store the enhancement to this enhancement set.

Now you can see the created extension field under context node CUSTOMERH.

Make it visible via UI configuration as usual in SAP CRM:

Now maintain some value in the extension field and save the change:

The value is successfully saved in CRMS4D_SERV_H:

With the same approach you can also create extension field on Product via S/4 extension tool and make it visible in Product search view and search result view in CRM WebUI:

How to read the extension field value via One Order API

Use CRM One Order API CRM_ORDER_READ:

DATA: lt_guid       TYPE crmt_object_guid_tab,lt_customer_h TYPE crmt_customer_h_wrkt.APPEND 'E04F430697291EE7AEAA0367A1F2DB37' TO lt_guid.CALL FUNCTION 'CRM_ORDER_READ'EXPORTINGit_header_guid = lt_guidIMPORTINGet_customer_h  = lt_customer_h.

The extension field value is stored in component CUSTOMER_H of One Order model:

Jerry’s other blogs on S/4HANA for Customer Management

S/4HANA for Customer Management 1.0 introduction from technical point of view
CRM One Order Model Redesign in S/4HANA for Customer Management 1.0 – Part 1
CRM One Order Model Redesign in S/4HANA for Customer Management 1.0 – Part 2
Create Mass Products by code in S/4HANA for Customer Management
Create Mass Service document in S/4HANA for Customer Management
One order extensibility in S4HANA for Customer Management

要获取更多Jerry的原创文章，请关注公众号"汪子熙":

SAP S/4HANA Customer Management(CRM)模块的扩展性设计相关推荐

SAP S/4HANA Service Management和SAP FSM基于CPI的集成场景介绍
本文作者是我的同事,Song Hao(宋浩),SAP成都研究院S/4HANA Service Management的开发人员. 项目背景相信大家已经知道,2018年6月份,SAP收购了一家专注于Fi ...
SAP S/4HANA Customer Vendor Integration-CVI锁机制的实现
Created by Wang, Jerry, last modified on May 12, 2016 要获取更多Jerry的原创文章,请关注公众号"汪子熙":
SAP S4 Material Management 库存模块 MARD 数据库表读取技术细节介绍
SAP ERP 6.0 库存管理数据模型由两个文档表 MKPF(用于文档抬头信息)和 MSEG(用于文档项目数据)组成. 此外,在多个表中存储了汇总的实际库存数量数据. 其中一些表还存储物料主数据属性 ...
Hello World, S/4HANA for Customer Management 1.0
SAP CRM的前世今生在我之前的微信公众号文章 SAP的这三款CRM解决方案,您能区分清楚么我曾经提到过我作为成都SAP研究院CRM产品开发团队的一员工作过一段时间. 我向在SAP德国总部工作的德 ...
S/4HANA for Customer Management里的搜索分页处理
这篇文章的英文版我发在了SAP Community上:Paging Implementation in S/4HANA for Customer Management https://blogs.sa ...
S/4HANA for Customer Management里的搜索分页处理 1
这篇文章的英文版我发在了SAP Community上:Paging Implementation in S/4HANA for Customer Management https://blogs.sa ...
Hello World, S/4HANA for Customer Management 1.0 1
SAP CRM的前世今生在我之前的微信公众号文章 SAP的这三款CRM解决方案,您能区分清楚么我曾经提到过我作为成都SAP研究院CRM产品开发团队的一员工作过一段时间. 我向在SAP德国总部工作的德 ...
SAP CRM 和 SAP Cloud for Customer 的表格列项目宽度调整的原理介绍
这是 Jerry 2021 年的第 37 篇文章,也是汪子熙公众号总共第 313 篇原创文章. Jerry 之前的文章一个 SAP 开发工程师十余年的技术写作之路回顾曾经提到,知乎上安晓辉老师的一 ...
SAP Cloud for Customer 如何直接消费S/4HANA API
最近有朋友在微信上问我本文标题这个需求,如何在 SAP Cloud for Customer 里实现.正好我在 2018年底参加的 SAP 和沈阳自动化研究所合作设计的一个工业 4.0 示范系统 PO ...

SAP S/4HANA Customer Management(CRM)模块的扩展性设计