One Personas question I’ve been asked several times now is, “How is Personas affected by ERP upgrades?” That is, what happens to your flavours and scrips when you upgrade or patch ERP6? Do they carry on working or is re-development work needed? My answer has always been that it depends on whether or not the underlying dynpro screens have been changed. If the screens are unchanged the flavours and scripts will just work. If the screens are changed in any way, the flavours and/or scripts may need changing to match. That’s always been a theoretical answer though – I’ve never been through an ERP upgrade in a system with Personas installed. Until now. We are now in the middle of upgrading our ERP6 system from EHP5 to EHP7 and so I can finally answer that question from personal experience!
The good news is that my answer is correct. Where the underlying screens didn’t change at all, my flavours and scripts continued to work unchanged. But how much did change so that flavours needed tweaking? I can only speak for the transactions used by the only Personas scenario we have live currently, the one described here: Putting everything together – the finished Personas project. There are a total of 23 transactions used in that scenario and only two of them were changed by EHP7 such that Personas was affected. Transaction KS03 has a pop-up that appears in some circumstances. It looks like this:
|EHP5 Version||EHP7 Version|
The visual difference is subtle, but actually the visual difference isn’t what matters to Personas. Each element on the screen has an id that identifies it to Personas. This id comes from the structure of the screen and how the various toolbars, menus, screens, sub-screens and other containers are arranged. The id for the “Choose” button in the EHP5 version is ‘ses/wnd/tbar/btn’. The id for the green tick in EHP7 is ses/wnd/tbar/btn. Again, a subtle difference but this time an important one. This broke my flavour for transaction KS03 because I have a script that pushes that button. The fix is the obvious one.
The other transaction affected was a purchasing report, ME2K. In particular, my script was manipulating some of the search parameters on the selection screen via the usual search help pop-ups. These pop-ups in EHP7 have changed in the same way as above – the id for the “execute” button on the popup changed from ‘ses/wnd/tbar/btn’ to ‘ses/wnd/tbar/btn’. It seems this is a common theme with pop-ups in EHP7. This time, however, the popups look visually identical.
The lesson from this is that changes in enhancement or support packs that affect Personas flavours are not very common, but they can turn up anywhere. You’d have thought transaction KS03 was pretty stable by now, but it is still changing. Also, the changes that matter are not the visual ones. In the examples above there was a subtle visual change in one case but no visual change in the other. The changes that matter to Personas are potentially invisible – you can’t tell by looking. You just have to test everything.
In my case the changes needed were very simple, but my flavours are built on long-standing and relatively stable (you’d think) transactions. If you are personalising other transactions you might have more widespread affects. Or none at all. I’m not sure it is easy to predict.