cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Can Screen Personas 3 be used with the standard WebDynpro HRESS_A_PTARQ_LEAVREQ_APPL application?

dr_ajt
Participant
0 Likes
924

I've a very simple requirement to remove the New button from the SAP standard HRESS_A_PTARQ_LEAVREQ_APPL application if the user making the request is involved in a termination process.

This feels like a perfect use case for Screen Personas 3.0. All I want to do is:

  1. Capture their logon name
  2. Check it against InfoType Records via an RFC call
  3. If there is no termination process in progress do nothing
  4. If there is a termination process in progress hide the New button and show some text asking them to contact HR

This seems an absurdly simple request, and while I can create flavor and hide the button and add the text easily enough the scripting engine is utterly unstable and unusable.

The system is a recently updated ECC platform, running a fairly recent NetWeaver stack. Other Personas 3 screens are working fine, but they are all classic dynpro based, and this is the first WebDynpro one to be attempted and also the first in the HR ESS space.

I'm aware that there are limitations with Personas and Web Dynpro, but I don't believe that this should be an issue here. My basic problems are that I can't save a script, it just saves nothing. I can't assign a global script even if one exists. It is so buggy and unstable that I can't believe that this is an undetected bug. The Personas health check is all green for services, green for system status (except two unrelated roles), and even the notes status is almost entirely up to date.

Accepted Solutions (1)

Accepted Solutions (1)

kmagons
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi Adam,

For the best experience I highly recommend to consider the Floorplan Manager (FPM) as the go-to solution for general Web Dynpro ABAP (WDA) application customisations. The known SAP Screen Personas WDA limitations are documented in SAP Note 2181980

A typical issue is an outdated SAPUI5 version that is deployed on your ABAP system because SAP Screen Personas uses the SAPUI5 runtime library that is loaded in a single page application environment by the WDA components. We recommend SAPUI5 version 1.84 for the latest SAP Screen Personas SP13 release.

Also please note that SAP Screen Personas cannot be used to simplify WDA screens that feature Html Island controls.

In general, for the reported SAP Screen Personas WDA scripting issues, I recommend to open a BC-PER incident ticket and consider providing an HTTP support connection along the steps to reproduce the reported problem.

Thank you!

Krists Magons

SAP Screen Personas Dev Team

dr_ajt
Participant
0 Likes

Okay, thanks, I suspect that was probably the case, but it's hard to know what you can and can't do with such sprawling technology.

We'll look at the FPM for this then.

Answers (0)