Skip to Content
Author's profile photo Sylvia Barnard

SAP Screen Personas: where is tab caching in version 3?

Combining information from multiple tabs is one common way customers improve usability with SAP Screen Personas. This eliminates keystrokes and allows organizations to present information in a more intuitive way. In SAP Screen Personas 2.0, we accomplished this by caching all the content in each tab that contained information that you wanted to display. In SAP Screen Personas 3.0, we use a different approach – without caching.

In SAP Screen Personas 2.0, we gave developers the ability to use tab caching to pre-load and pre-fetch data from the backend. This means that if five tabs are cached, the information of all five tabs is retrieved from the backend and stored in the browser. The content within the tabs has a significant impact on performance. A tab with a few information fields will probably not cause performance problems. A tab that contains a large table – such as those common in sales order or material master transactions – is more likely to slow performance if you cache it.

In SAP Screen Personas 3.0, we changed the underlying architecture so that tab caching is no longer necessary. Tabs are now merged so you can display information from multiple tabs on a single screen as before, but without caching. You define the information you want on the screen, the backend stores the field codes, and renders them at runtime using the incremental loading that is already part of the Web GUI (SAP GUI for HTML).

As we learned from SAP Screen Personas 2.0 extensive tab caching can cause performance issues, so we no longer allow the pre-loading and pre-fetching of data from the backend in SAP Screen Personas 3.0. This proves to be much more effective with fewer calls to the backend and much less data transfer. Overall, this new approach has a positive influence on the performance when merging tabs.

The complimentary openSAP class starting March 31st ( will also include a section on tab merging which will demonstrate how you can quantify the expected performance impact result from the use of tab merging in SAP Screen Personas 3.0.


For the SAP Screen Personas product team, Sylvia Barnard


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Kapil Changrani
      Kapil Changrani

      Hi Sylvia ,

      We are trying to merge tabs(basic data, payment and details tab) of transaction FB60 in Screen personas 3.0.

      While doing so, we are getting exceptions and screen errors , if tab caching is not available in 3.0, can you please guide how can we achieve this functionality?

      Author's profile photo Sylvia Barnard
      Sylvia Barnard
      Blog Post Author

      Dear Kapil,

      Tab merging is available in Personas 3.0 and working. However, when merging tabs in a complexe transaction like FB60 you have to ensure that you can navigate freely between tabs, that you do not get stuck at mandatory data input fields, that all pop-ups are out of the way, etc. So it is advisable to know the technical behaviour of the transaction into its last corner.

      I would like to point you to an article on the Personas Knowledge Base: which deals with blocking input validations.

      Another article is the one about the screen and control overwrite entries:

      Here one of the symptoms might be that controls disappear when you change tabs.

      If this does not solve your problems, please open a ticket so that we will be able to look into your issues in detail.

      Best regards,


      Author's profile photo Kapil Changrani
      Kapil Changrani

      Thanks Sylvia, that helps. FB60 has required fields on tab one Basic Data Tab like vendor number, invoice date etc, after I input these fields and try to bring fields from Payment Tab and Details on to Basic Tab it still gives an exception.

      Is there any way to work around this, or this is just how the Personas tool is designed, that it won't allow to merge tabs, even if the mandatory fields are filled with data, because at the very beginning of transaction we cannot directly go to Tab2 and Tab3 without filling required fields in Tab1?

      Is this a correct understanding?