Skip to Content

SAP Screen Personas 3.0 Is Generally Available, including Service Pack 1

On behalf of the entire SAP Screen Personas product team, I am very excited to announce that we have completed our ramp-up process and SAP Screen Personas 3.0 is now generally available. In addition, we have introduced SAP Screen Personas 3.0, Service Pack 1 (SP1), which includes all the SAP Notes we released during the ramp-up period, along with a few improvements that customers requested during ramp-up.

/wp-content/uploads/2015/07/twitter_740921.pngBest SAP Screen Personas ever. Version 3.0 is now generally available. Run Simple.

What’s New in SAP Screen Personas 3.0?

This is a completely new version of SAP Screen Personas, rewritten from the ground up in HTML5 as part of the SAP GUI for HTML (Web GUI). The fundamental value of the product remains the same – to allow your employees to be more productive in their roles with personalized and simplified SAP GUI screens. By becoming an integrated part of Web GUI, the product gains several advantages:

  • Ability to render personalized screens directly in SAP GUI for Windows
  • Simpler administration
  • Tighter integration into other SAP UX solutions
  • No Silverlight dependency

In addition, we added two major enhancements, both of which were requested by customers of earlier versions of SAP Screen Personas.

  • More powerful scripting, based on JavaScript (suggested by developers)
  • More intuitive editor (suggested by designers)

Let’s examine each of these in more detail, followed by a success story from one of our ramp-up customers, and some possible next steps that you can take.

Ability to render personalized screens directly in SAP GUI for Windows

With SAP Screen Personas 3.0, we changed the architecture, moving more of the processing into the ERP server away from the browser (see diagram below). The impact of having all the screen calculations done on the server is that any rendering engine has access to this information. So, any screens you edit in Web GUI (where we have built the editor using SAP UI5 libraries) can eventually be rendered in any of the members of the SAP GUI family – SAP GUI for Windows (SAP GUI), SAP GUI for HTML (Web GUI), SAP GUI for Java (Java GUI).

Running SAP Screen Personas in the Web GUI will provide system performance comparable to Web GUI performance. Running simplified screens in SAP GUI will have performance similar to SAP GUI. You can choose where to deploy your SAP Screen Personas screens based on your business needs.

For now, the rendering works best in Web GUI, with the other GUIs lagging by several months. So, our recommendation is to focus on the SAP GUI for HTML for most of your scenarios and use SAP GUI only for testing. If you want to know whether a specific screen will work in SAP GUI, read our SAP GUI for Windows supported features note, or just try it. We are working on getting the functionality in SAP GUI for Windows / Java as close as possible to SAP GUI for HTML, but that there will always be limitations as there are some differences in the underlying technologies. For example, SAP GUI does not understand Web-based standards such as cascading style sheets (CSS). We are continuing to work closely with the GUI teams to provide consistent performance with personalized screens across all types of controls.


Simpler administration

Since SAP Screen Personas is now part of Web GUI, you can use the existing roles and authorizations that you have defined in SAP. Once you build a flavor for a specific user or job function, you can just assign it to a role that already exists in your system. You no longer need to maintain a parallel set of groups just for SAP Screen Personas and synchronize them with your main SAP roles. Although we have automated the synchronization process in SAP Screen Personas 2.0 SP3, SAP Screen Personas 3.0 removes this one additional step, simplifying deployment in large environments.

Tighter integration into related SAP products

We often received customer inquiries about whether SAP Screen Personas 2.0 could integrate with NWBC, SAP Portal, or the Fiori Launchpad. (The answer is yes to all.) While the process was generally very straight forward, now it is even easier. You just follow the existing process for integrating Web GUI into one of these shells; there is no special process for SAP Screen Personas now.

No Silverlight dependency

This one is pretty self-explanatory. Although Microsoft announced that it will support Silverlight through 2021, we are already seeing backing from other vendors starting to decline. Recent versions of Google Chrome no longer support the Silverlight plug-in.

More powerful scripting, based on JavaScript

Scripting has long been one of the most popular and powerful features in SAP Screen Personas. Automating keystrokes allows you to skip over screens, suppress pop-ups, and move information between different screens or even different transactions. But, some customers wanted more. So, in SAP Screen Personas 3.0, we made the scripting engine even more powerful.

The new scripting engine is based on JavaScript and now includes looping, nested IF conditions, and logging capabilities. For simplicity, we are keeping the record and playback capabilities, but now this generates the JavaScript you need. We now maintain scripts independently of the buttons, so it will become much easier to reuse scripts within a screen. Feedback from ramp-up customers was very positive about the new scripting. I have already blogged about how to get started with JavaScript:

More intuitive editor

In earlier versions of SAP Screen Personas, we learned that, in many cases, designers are building screens or at least creating templates that business analysts will later modify. The designers had specific requests for SAP Screen Personas to include some of the functionality they typically found in their design tools. So, we added new features such as the ability to clone controls, line up buttons, and select colors from a pre-defined corporate palette.

We also added a global theming editor to make it easier to create a design once and reuse on multiple flavors or transactions. With a Fiori theme (part of our Rapid Deployment Solution for SAP Screen Personas 3.0), you can provide a Fiori design to all your SAP GUI transactions at once.

Ramp-up success story: Hunter Douglas Simplifies Order Process

Hunter Douglas, a global manufacturer of premium window coverings, was part of the SAP Screen Personas 3.0 ramp-up program. They used SAP Screen Personas 3. 0 to simplify their Remake Orders Process and streamline transactions SMEN and VA01. Previously, their customer service representatives (CSRs) used a “swivel chair” process, which was cumbersome and time consuming. They had several paths that the CSRs would take through the system. They created different flavors for each scenario.

For their project, they used around 45 scripts to power the simplified screens. The scripts move information between screens, bring up color charts on the screen, and selectively hide information based on context. People access the streamlined transactions through an intuitive launch pad.

They started their simplification process in mid-January and went live in mid-May. The team consisted of a business analyst, architect, project manager, JavaScript developer, user experience designer, and basis expert. The Hunter Douglas customer service representatives were also involved in the project, as they are the ultimate users of SAP, entering transactions while they are on the phone with customers.

You can learn more details about their deployment and the business impact at SAP TechEd in the fall.

Of course, the business value of SAP Screen Personas remains the same.

  • Improve SAP adoption by making screens easier to use
  • Increase employee productivity by simplifying screens to reduce typing
  • Reduce training costs by making SAP more intuitive
  • Enhance data quality by reducing free text entry

Next Steps

Take a free OpenSAP class.

Learn more from our knowledge base.

Download SAP Screen Personas 3.0 SP1 (requires valid NetWeaver License)

Sign up for push notifications related to support (new SAP Screen Personas Notes, kernel recommendations)

Check out the new Rapid Deployment Solution, which contains several pre-built flavors and a Fiori design guideline

Speeding Adoption

To accelerate your screen simplification project, the SAP Screen Personas Rapid Deployment Solution (RDS) provides free SAP best practices for deployment, configuration, and operation. It includes pre-built business content to ensure fast and predicatble results.

Kernel Recommendation

As you can see in the architecture diagram above, SAP Screen Personas works with several other components, especially the kernel, to deliver productivity through personalization. So, it is very important to remain on a recent version. The minimum Kernel Patch required for SAP Screen Personas 3.0 SP1 is SAP kernel 7.42 patch level 200

Read about the minimum system requirements to use SAP Screen Personas 3.0 SP1.

Read the main SAP Screen Personas 3.0 SP1 Note that covers all relevant notes for the product.

Migrating to SAP Screen Personas 3.0 from 2.0

We have built a migration utility into SAP Screen Personas 3.0. Watch this video to see how easy it is to migrate your flavors.

Attention SAP Screen Personas Customers

Want to hear how other customers are using SAP Screen Personas to make their users more productive? We have two monthly (virtual) meeting in which companies share their best practices and take questions from the attendees. Usually, there is a customer demo and/or a tutorial from an SAP product expert.

SAP Screen Personas 2.0 Practitioner Forum is on the 2nd Wednesday of each month.

SAP Screen Personas 3.0 Practitioner Forum is on the 3rd Wednesday of each month.

Learn how to register for the Practitioner Forum.

For the SAP Screen Personas product team, Peter Spielvogel.

You must be Logged on to comment or reply to a post.
  • There has been a delay in the release of Kernel 742 PL200. SAP Screen Personas 3.0 SP01 also works with Kernel 742 PL123.

    If you want to start your Personas project now, then please apply PL123. For the best experience please upgrade to PL200 once it is available. If you prefer not to exchange your kernel twice, please wait for PL200.


    Your SAP Screen Personas Team.

  • Hi Peter,

    Awesome product!

    Just adding that you can use the same menu to migrate a flavor from SAP Screen Personas 1.0 to 3.0 (SP1). I tested and it works fine.



  • Hi all,

    Is there any requirement to be on Unicode for Personas 3.0?  I remember this previously being mentioned (I think in one of the Personas practitioner forums) but there's nothing about it on the system requirements link.



  • Hi,

      can we install this on gateway server and connect to backend ECC system to personalize the screen? Or we need to install it as an add on the ECC only?

      • Hi Peter,

               With S4 Hana(Simple Finance/logistics), how would it effect our screen designed with Screen personas 3.0. I assume lots of screens going to change with S4HANA. Would it be ideal to change the major tcodes with Screen Personas 3.0?

        Please suggest.



        • Hi Gopi,

          Congratulations on moving to SAP S/4HANA. This will provide you access to new functionality that is only available on SAP HANA.

          As a first step, I recommend you check the Fiori app library to see if there is an app (Smart Business Cockpit, Analytical app, or Transactional app) that meets your needs. There are currently over 550 Fiori apps for a variety of user roles, industries, and lines of business.

          If there is not a Fiori app that meets your requirements, then SAP Screen Personas 3.0 is a great way to simplify the S/4 transactions you need for your specific business. SAP Screen Personas 3.0 can modify S/4 HANA systems running on premise. You would simplify the Web GUI transaction as you do today.



          • Thanks for the response Peter. We have not yet moved to S4HANA.

            Assume we have spent time in modifying a transaction using Screen personas 3.0. But with S4 HANA if that transaction is already modified then wouldn't be our efforts wasted?



          • Hi Gopi,

            I recommend checking first to see if the transaction you want is to modify is already changed in S/4. Some of the Fiori apps cover pieces of a transaction, so there is not a 1:1 mapping between Fiori apps and classic SAP transaction codes.



  • Hi, I would be very interested in the ramp up scenario of Hunter Douglas regarding VA01 Transaction. Is there any presentation and/or screenshots available?



  • Hi all

    We have EHP7 current sp stack and we are going to have personas 3.0.

    I selected personas 3.0 from solution manager MOPZ but it is bringing

    persos 2.0 addons also. Do we need persos 2.0 also or only personas 3.0

    required for EHP7


    Suresh Daniel.

  • Hi,

    For those who used the Ramp-up version, do we need to do a fresh install of Screen Personas 3.0, and then install SP1+following notes, or can we continue with our version and just proceed by install SP1+following notes ?

    Thanks in advance for answer.


  • Hi Experts,

    Why SAP is not releasing a web browser which can support well for all the SAP products.

    Many of the SAP products require web browsers like solution manager, portal, fiori

    and personas we waste a quite a lot of time in setting the browser to work.Also we

    spend a lot of time in troubleshooting web browser issue for customers. Though the

    SAP product may be working fine but due to the web browser issue we get bad feedbacks.

    Is there any possibility that this request can be taken forward?


    Suresh Daniel.

    • Why would SAP even think of developing yet another web browser? Would that make sense? Do you think that companies would change their policy and adopt a different browser than what is their company standard?

      For any browser-specific issue, blame the browser for not adhering to web standards.

      If you have something that doesn't work with one of the major browsers and works with the others, then create an OSS incident so that the Personas development team can take a look at the problem.

      • Hi Tamas,

        You are not looking at it from a consultant point of view. You are saying easily to raise

        OSS message but actually these browser issues by us  are classified as low or medium and a newbie will take up the issue and it never get resolved. Somehow we have

        to find our own solution to save our head.

        Even if I agree with your point all SAP components which generates a webpage(solman,

        portal or personas) it takes lot of time . It is not at all quick comparing with other products.


        Suresh Daniel.

        • Suresh,

          Just so you know, I used to be a consultant for about two decades before joining the Screen Personas team last year, so I like to think that I know exactly what a consultant's viewpoint is 🙂

          Be assured that in the Personas team OSS incidents are not processed by newbies, regardless of the priority. Actually most of the time, incidents are responded to by the very same people who developed the product, and they are certainly not beginners. We take customer support very seriously.

          Now if the issue is out of the Personas realm (like this may happen often with browser-related issues), then the situation may be different but as long as the problem is caused by anything related to the Personas product, the team will investigate and provide a solution. So this is why I suggested that if you find something that works differently depending on what browser is Personas running in, the best course of action is the incident route. Developing a new browser to combat such problems wouldn't solve anything and would just increase clutter and confusion.

          I'm not sure I understand correctly what you mean with your last statement but if you have performance issues in Personas compared to other browser-based SAP products, the development team would like to know about it. I'm not saying you'll receive a magic solution that makes everything a lot quicker but it will be looked into if it can be resolved in Personas.



          • Hi Tamas,

            Thanks for your long reply.  I am not asking SAP to release a global

            browser. But a web browser which can support only its products. Like an app.

            Thats it. Which will help people who go for demo or do RDS.


            Suresh Daniel.

  • Is Personas 3.0 supported by CBTA?  Apparently Personas 2.0 uses Microsoft Silverlight for rendering.  Silverlight is not supported by CBTA test automation through Solution Manager.  Since 3.0 doesn't use Silverlight does that mean you can record and playback automated test scripts using CBTA?

  • Hi Tamas Hoznek,

    I want flavor should apply in SAP GUI for HTML only not in SAP GUI for Windows, how can we control it?

    I created flavor for tcode and defaulted it, so when i run that tcode in SAP GUI personas flavor applying default.

    Please suggest me.

  • Hi Peter,


    I am not expert in Screen Personas. But one question.. with Java Script capabilities that you've described in this blog and other blogs, can make a call to external systems within Java Script code?

    Meaning, when somebody enter something on the screen, when they hit on 'Submit' or 'Display' button which is going to trigger code on the server/application logic, I want to add custom java script code that is going to trigger client side pass that data to external system and validate it there and get response back. In my requirement, if validation is not success then I am going to wipe out/clear that value show message within java script code.

    Though this code reside on server, in run time - server will not be having any clue on what was entered on the UI.

    (Yes, I want to use Java Script in screen personas UI same as in Fiori or any other Web App).

    Let me know if you need any other details.