Flavor-Assignment specific for Program and Screen

[robinwennemuth]

Dear Experts,

in a customer project for SAP HCM we need to assign Personas-Flavors to Roles (or Users) specific for Program and Screen.

Currently in /PERSONAS/ADMIN I am able to assign a Flavor based on a Trasaction Level.

Did I just miss something? If not, this would be a great Feature for future releases, from my point of view.

Why this?

In SAP HCM there are a couple of Programs and Screens running under the same transaction ID.

For example when using Fast Entry of Actions, the user opens Transaction PA42 and selects an action. He is "redirected" to a specific implementation (ABAP program) for this purpose. So when we provide a Button in a Personas Flavor, leading a User directly into the action program, a Flavor assigment on transaction level is not sufficient anymore, if more than one action (and therefore more than one Flavor) exists. We have to change the Flavor using Personas Scripting, but this overrides the rules maintained in Backend and is just a Workaround. The better solution would be an assingment on Program and even Screen Level.

Why even Screen Level?

In HCM, country-specific requirements for HCM Infotypes are often implemented in specific screens for a country. These screens run within the same program and transaction (PA20/PA30) as the main screen, e.g. infotype MP0006xx. So if you use your solution for several countries, you will not only have to maintain a Flavor for every country-specific screen, you would also have to create a large switch/case-Script for the selection of the right Flavor for a country. And this even not the full truth, as the backend implements a complex logic to find the correct screen for an employee, depending on multiple customizing settings.

Do you see a possibility to provide a solution for these cases in HCM?

Thanks in adavance!

Robin

[TobiasQueck · Accepted solution]

Hi Robin,

I am not fully sure I understand the request.

A flavor is transaction specific - as you correctly said, a flavor consists of multiple screens (each screen in the corresponding transaction that has been personalized) and finally each screen contains a list of changes.

So, if the main program or screen number changes depending on a selected infotype or other business specific parameters then the Personas backend will provided different changes - the changes that are assigned to the currently active screen (identified by main program name and screen number).

As result, if I read your scenario correctly, then you need exactly one flavor to cover all your screens.

I am assuming here that your scenario description is slightly incorrect, and that you do not have different main programs, but that there is a subscreen that dynamically changes and you currently use scripting to identify the difference. If this is correct, then scripting is really the only option for you because we do not have access to the subscreens in our Personas backend coding.

Cheers!

--

Tobias Queck

SAP Screen Personas

Lead Architect

[robinwennemuth · Accepted solution]

Hi Tobias,

thanks a lot for answering so fast.

This lightens things up for me much more.

On the one hand maybe we thought too complicated, providing a separate Flavor for every Business Process that is working within the same transaction - this fits for the PA42 example. So there would not have been the need to separate the flavors as we did. Maybe we thought too much from the PFCG role perspective, where you rather separate the roles from each other.

But on the other hand we have two other examples:

• In HCM Infotype 0105 (MP010500/2000) stores the entities User-ID, E-Mail-Address and Telephone Number in different subtypes (0001, 0010, 0020). If we want to use a specific flavor for every entity, we do not get around to change the flavor from the navigation trigger (Script Button), right?
• We have Processes consisting of several transactions, e.g. starting in A, navigating to B, then to C or D and then back again. In these cases we create a flavor for every transaction involved (A, B, C, D). The role assignment works fine if a user has only this one process (Process 1) utilizing these transactions. But now if we set up a Process 2 with the same transactions involved, separate Flavors for A, B, C and D are created. Is there any possibility to link the Flavors to each other without scripting?

Thanks for your feedback again!

Cheers,

Robin