In this blog we have discussed the logic how the correct UI view configuration is chosen by framework in the runtime.

You may have observed that for each field, there is the attribute “Label Origin”, which indicates where the label text comes from.

There are three types of text origin and their determination priority are sorted in the descending order:

Text Repository

Design layer

ABAP Dictionary

See an example:
I just create a simple component with component set PROD_ALL loaded, and add two fields from Genil Model node Product: PRODUCT_ID and OBJECT_FAMILY_DESC.
For PRODUCT_ID, I don’t change its label so its Label Origin is “Data Dictionary”.

for the latter, I change the default one to “Description 1”, so the origin changes to “Text Repository”, since it has higher priority.

If I assign the context node to the Design layer object PRD_MATSRV as below,

and make some changes on the design object entity:

the origin for PRODUCT_ID changes to “Design layer”, since it has higher priority than “ABAP Dictionary”.

To debug the label determination logic yourself, you can set BP in method below. The logic is the same as UI configuration determination logic – customer stuff always precedes SAP stuff.

or use transaction code WCF_FA to get field origin overview of a given UI component:

要獲取更多Jerry的原創文章，請關注公眾號"汪子熙":

總結

以上是生活随笔為你收集整理的SAP WebClient UI页面标签的决定逻辑介绍的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。