Personas 2.0: How to "Transport" the whole Personas app to QA sys?

[Former Member]

Hi Personas experts,

I have developed some Personas (2.0) apps on Sandbox/Devlopment sys. Now I want to "move" the whole program to QA sys for testing. Can anyone give some details about how to use SAP transpotation to move the "Whole" app?

I am thinking that the followings need to be moved (pls correct me):

1. The configuration of Personas (eg, made by tcode spro) - can this part to be transported directly?

2. The settings such as users, groups made by admin_ui. Can this be transported directly?

3. The app impelmentations - such as all the flavours. Can this part be transported directly? If so, how?

Thanks a lot in advance!

Best regards,

Dong Zhu

[tamas_hoznek · Accepted solution]

Technically speaking it IS possible to transport the configuration in SPRO or even what is done in the Admin transaction since everything is stored in various DB tables. So while some of this is rather tedious, you can build the necessary transport entries manually.

I did the same at a customer where I used the Profile Wide Settings to create a theme and I didn't feel like recreating all that in each target client (plus introduce a lot of possibility for making a mistake). The trouble with this was that the settings are linked to the originating system with a GUID and it was necessary to patch this (with an ABAP program) in the target system after transport so that my theme would show up.

Transporting users and groups is not recommended... even though the possibility is provided, it's still better to build the groups in each client since the users and their authorizations / roles will likely be different.

As Neil mentioned, flavors and media files are easily transported but the system association of flavors has to be adjusted manually in the target system.

[Former Member · Accepted solution]

Hi Tamas,

Could you please explain what is difference between import a flavor and Tranport Objects? Eg, I have a flavor using 5 images. What I found annoying is that each time after importing the flavor, I got also 5 new image objects so my image gallery has more duplicated objects. Event annoying is that the control which uses the same image but different instance is not shown on UI, so after I remove some of the duplicated image objs in gallery, I would have UI contrl missed icon etc so I have to redo adding icon. Any good idea to not get doplicated image objs after importing flavor? Thx.

Dong

[tamas_hoznek · Accepted solution]

This sounds like a problem with the Import feature.

I'd suggest opening an OSS incident if you have such a reproducible use case.

[Former Member]

Hi Dong

To answer your questions:

1. The configuration of Personas (eg, made by tcode spro) - can this part to be transported directly?

     No this is not transportable ... not in our system anyway ... we had to do this config manually in each client

2. The settings such as users, groups made by admin_ui. Can this be transported directly?

    No, users are setup in each client and assigned their Personas roles per client, groups however are transportable

3. The app impelmentations - such as all the flavours. Can this part be transported directly? If so, how?

     Flavours, groups and media files are transportable via /persos/admin_ui, you must use the 'Transport Objects' option in the 'General Actions' folder.... here you specify each object to be transported and create a transport to include them. Note, if you are using a unique SAP ITS and Personas backend per client, after transporting the object, you will need to go and assign each flavour to your new system in the admin_ui tcode.

Hope this helps,

Neil

[Former Member]

Hi Neil,

Thansk for the info. It seems there is no other ways than what I have to do all these manual tasks. By the way, just to share the info, all the images used, eg., as the button icons, are lost after the import. They have to be set manually again.   I close this thread.

Best regards,

Dong