Skip to Content

Migrated flavours are not working in personas 3.0

Hi Personas Experts,

Great day to all of you 😊😊

As we are in to personas 3.0 version now.. so all the flavours we have migrated from Personas 2.0 to 3.0 version..after migrating all flavours all are showing in the personas 3.0

But the problem is that individual flavour navigation is not happening for the transaction codes which already flavour is having i.e. one flavour is having 3 transactions with 3 different tabs

if I click on individual transaction code system is not going in side the transaction

so please suggest any configuration or note has to be implemented for this

Regards,

Venkatesh..

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Posted on Jan 12, 2016 at 10:23 AM

    The Personas 2 to 3 migration process doesn't guarantee to produce Personas 3 flavours that work fully. You have to test each one and will likely need to apply manual changes - to the layout, or scripting, or maybe both - to get them working properly. How much manual work is required will depend on the flavours themselves. Some may not require any, some quite a bit.

    You're now going to have to debug your flavours! Start by reading this wiki page - Debugging options in SAP Screen Personas 3.0 - to see how to go about that.

    Steve.

    Add a comment
    10|10000 characters needed characters exceeded

    • I confess I'm a little out of touch with the migration process these days - I haven't had to use it for a while. There are no notes for SP03 that make any changes to the migration process, as far as I am aware.

      After going through my migration process, my conclusion was that the best thing was to re-write everything and not use the migration process at all. It takes a little while, but not a huge amount of time as Personas development is relatively quick and you've done all the design work already. There are several reasons for this, but in the context of your question I'd say that manually re-writing complex scripts will produce a result much, much better than the migration process would. You can use the full feature set of Javascript and all of its proper control flow. You can use the much nice BAPI calling process instead of webRFCs. And for the visuals, you can use the new theming for your flavours instead of building those things into each flavour. All-in-all the final result should be much better.

      If you have a big Personas development, this might sound like a lot of work, but compared to debugging and tidying up the results of automatic migration it wouldn't surprise me if it is actually quicker.

      That said, I'm sure SAP are still interested in improving the migration process so if you have specific issues, I suggest creating support incidents for them to see if they can be fixed.

      Steve.

  • Posted on Aug 12, 2016 at 03:48 PM

    HI Michael,

    The most common step which is missed is the migration mapping. I have seen this with so many customers. Please refer to the migration guide.

    Also, migration is just a data transfer. If there is bug in lets sayd kernel patch which prevents tab merging, with or without migration flavor will fail. SO keep your installation up to date based on the main note.

    Other very common missing issue is the pre-migration check (which you should anyways do even for creating personas 3 new flavors), like checking screen and control overwrite entries..

    Regards,

    Sushant

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 15, 2016 at 09:14 PM

    Hi,

    I had similar problems in my first migration run.

    I solved this kind of problems by processing the "Create migration mappings" actions.

    Please have a look at the following URL:

    Getting Started - Personas 2.0 to 3.0 Flavor Migration - SAP Imagineering - SCN Wiki

    Regards Matthias

    Add a comment
    10|10000 characters needed characters exceeded

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.