Skip to Content

This is part of a multi-part series addressing myths about SAP Screen Personas.

/wp-content/uploads/2013/10/myth2_292095.png

When people talk about “improving SAP”, this can take a number of different dimensions. It could be usability, it could be aesthetics, or it could be performance. The myth about SAP Screen Personas improving SAP performance could be a misinterpretation of how it actually changes the product and user experience.

SAP Screen Personas is a screen personalization solution that allows companies to personalize their SAP ERP screens for different user roles. The focus of the product is on allowing people to make screens more intuitive, thereby improving user productivity. Since people are faster at performing their job functions by using Personas, this could be perceived as improving the overall system performance.

When you talk about SAP “performance,” you should consider a system that includes both user time and computer time. To measure this, observe a person user completing a transaction or series of transactions to complete a typical business process on an unmodified SAP screen. Then, measure the person again running the business process using SAP Screen Personas.

Which will be faster in this case? It depends.

  • How well does the person know the transaction codes and keyboard shortcuts required to complete the transaction?
  • How much time does the person need to spend entering the same data for multiple transactions that comprise the end-to-end business process?
  • How much time does the person need to learn all the transactions?
  • How much time downstream is needed to correct mistakes that the original person introduced by entering bad data or leaving out critical information?

 

/wp-content/uploads/2013/10/image_myth2_292097.png

The Underlying Architecture Determines Performance

Both SAP Screen Personas and SAPGUI for HTML (WebGUI) are user interfaces build on the internet transaction server (ITS). Historically ITS connected to the application server through an AGate component while the HTML output was created using a component called WGate – nowadays ITS is generally used as an integrated ITS running inside the application server. This improved the performance of SAPGUI for HTML greatly.

Architecturally ITS still translates the SAPGUI screens into an HTML stream – which in turn is send to the client. The time this takes depends greatly on the amount of information required to render the screen. If you are looking for the best possible SAP Screen Personas performance you should always start out by ensuring that large tables and value sets are reduced to the necessary minimum – to ensure fast processing by the ITS.

Generally the amount of data transmitted and the ITS processing time (see ITS sizing guide) are comparable between SAPGUI for HTML and SAP Screen Personas.

Scripting Speeds Performance

If you execute a script that automates a number of server actions using scripting in SAP Screen Personas you might see a surprising jump in performance. This is caused by executing numerous steps entirely within the ITS without requiring additional round trips. Since the intermediate screens don’t need to be send to the client their processing is minimal and performance improves.

What are some of the ways that Personas can make SAP run faster than an un-modified screen?

Reducing round trips to the server to retrieve data

  • Automating a series of keystrokes to skip over screens and eliminate round trips to the back end
  • Caching information in tables to avoid multiple calls to the back end
  • Merging tabs so all key information appears on a single screen rather than distributed in tabs that require multiple clicks, scrolling and calls to the back end

  Making the user faster in their work

  • Launching transactions with clearly labeled buttons rather than typing transaction codes that the user must memorize or look up.
  • Prefilling fields to avoid typing the same information more than once
  • Using pull-down menus to speed entry of a limited set of data, which also eliminates keying errors

So, does SAP Screen Personas improve SAP Performance? Yes, but not necessarily in the way you may have thought about this.

/wp-content/uploads/2013/10/conclusion_true_292096.png

In the next post, we will explore myth 3, about which screens Personas can modify.

For SAP Imagineering, Peter Spielvogel.

Read the entire SAP Screen Personas Myth vs. Truth series

Introduction

Myth 1

Myth 2 (this post)

Myth 3

Myth 4

Myth 5

Myth 6

Myth 7

Myth 8

Myth 9

Myth 10

Myth 11

To report this post you need to login first.

1 Comment

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

  1. Oliver Betz

    Hi Peter,

    thanks for the post. Very valuable insights. So far I looked at scripting only at a way to reduce the required user interaction (less clicks). But you are right – as the screens do not need to be rendered it also reduces the number of round trips and therfore boosts performance.

    Oliver

    (0) 

Leave a Reply