Skip to Content

HREF from BSP ignores specified Flavor, always returns default

I've created a customised Flavor for transaction CJ02 and assigned it to my user. I'm then trying to call the customised Flavor from a BSP using the link:


This successfully calls CJ02, but always calls this transaction for whichever Flavor is specified as the default, irrespective of which code I pass in the sap-personas-flavor parameter. So, if the standard screen is the default, that will come up, whereas my customised Flavor will only come up if I switch that to be the default instead.

I get the same issue if I run /PERSONAS/ADMIN or /PERSONAS/FLAVORS from SAPGUI, select my customised Flavor and then press the 'Launch Flavor' button - a web browser session opens, but with the default Flavor for CJ02.

I can call the correct Flavor directly using /PERSONAS/LAUNCH either via SAPGUI or via the BSP link:


However, this isn't ideal for my purposes because ultimately I want to pass a Project Code to whichever Flavor of CJ02 is called and, as I understand it, screen parameters can only be specified for the first transaction / dialog box the transaction call encounters. In other words, if I call CJ02 directly, I can set a value for PROJ-PSPID in the link parameter list to populate the Project Code field, but I couldn't call /PERSONAS/LAUNCH for my chosen CJ02 Flavor, pass an OK Code to force that Flavor to run, and then be able to populate PROJ-PSPID for that Flavor.

Any help much appreciated.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Aug 08, 2016 at 02:21 PM

    Hi Vincent,

    I tested this in the latest patch level of Kernel 742 and seems to work correctly. What Kernel and PL is your system on?

    Do you get a transport organizer popup (with information on transport errors) when you login to the system? There is a known issue with flavor selection when such a popup is displayed. If this is the case, you can either disable the popup using the parameter ~NO_LOGON_USEREXIT set to 1 in SICF GUI configuration of the personas service or create an incident with BC-PER as the component and we will get back to you.

    Best regards


    SAP Screen Personas Team

    Add a comment
    10|10000 characters needed characters exceeded

    • After further experimentation, I have found a workaround for this - go to /PERSONAS/ADMIN for the Flavor, then use the 'Create transaction variant' command. The Flavor can then always be called via the transaction code specified for the new variant, instead of via the base transaction with the sap-personas-flavor parameter set (which wasn't working for me).

      However, this has its own quirk. I mentioned above that I wanted ultimately to pass a field parameter as part of the call. Turns out this works for the base transaction, but not the Flavor variant, e.g.:

      This call to CJ02 successfully populates the Project Code field:

      /sap/bc/personas?sap-client=500&sap-ie=edge&~transaction=CJ02 *PROJ-PSPID=<%=lc_projcode%>

      This call to a Flavor variant of CJ02 fails to populate the Project Code field:

      /sap/bc/personas?sap-client=500&sap-ie=edge&~transaction=ZRSP_CJ02 *PROJ-PSPID=<%=lc_projcode%>

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.