Skip to Content

When you define UI structures, e.g. for a customer specific form or list UIBB or tab or something else, it is convenient to include e.g. the underlying backend node structure so that you have all potential relevant fields available.

Performancewise you ( or actually your end users 😉 ) pay a high price for it, as the number of fields included in the structure (even if not visible to the user) has a huge impact on the rendering time.

This is even getting more relevant as FBI adds additional technical fields to the generated UI structure. Here is an example:

The actual  UI structure looks as follows:

ui_struc1.PNG

36 actual fields (include itself is also counted but is of course not relevant as such). If you now look at the FBI structure (which is the strucure used by Web Dynpro) you see this additional include here:

ui_struc2.PNG

So for nearly all fields (I think key is excluded here) a structure /BOFU/S_FBI_TECHNICAL_FIELDS is added.

And this structure has 4 components (reference fields for enabled, visible, read-only and mandatory):ui_struc3.PNG

So for every actual field you add to the UI structure, 5 fieldsare technically added to the WebDynpro context.

So, think which fields are really make sense for the UI and only include those fields!

PS: You may also listen to the TMP podcast episode about TM UI technology: TMP006 TM UI basics

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Dawson Wang

    if we don’t specify UI structure in FBI view, then all the node fields will be added to WebDynpro context, so to specify UI structure in FBI view is preferable, isn’t it?

    (0) 

Leave a Reply