Program name change in transaction

[former_member193190]

Hi All,

We have created a flavor of a Y transaction in one client, we are observing that the Dynpro program name is getting changed for this Y transaction in other client, so what is happening is the flavor for this Y transaction is working in the client where we have developed it but not working in other client as the Dynpro program  name is changing. I have seen there is an option related to change in program name in the same client but do you have any solution for the above scenario where program name is changing in different client for the same Y transaction and how can we build and export flavor for this in Personas.

[chinthan_yajamaan]

Personas uses tcode+program name+screen number to identify flavor. So if program name or screen number changes dynamically in a system then it is not possible to use flavor with such a transaction. But if program name is Y1 in system1 and Y2 in system2 and is not dynamic in nature, then you can create screen overwrite rule in source system as

tcode     -         Y1         -         scr num          -              Y1                - scr num

and in target system create screen overwrite entry as

tcode        - Y2              - scr num                 -               Y1                - scr num

and then if required, create your control overwrite entries using Y1

Hope that helps.

[Mohanraj]

Hi,

Please refer to below link and create overwrite rules for your transaction to fix this issue.

http://scn.sap.com/community/gui/blog/2014/04/12/sap-screen-personas-screen-id-and-control-id-overwr...

If you not able to create one, please create an OSS message with R3 and HTTP connections open.

Regards,

Mohan