How to improve SU25 activities and duration?

[Former Member]

Our company heavily leverages SU24. As a result, we spend a decent amount of time reviewing the roles and transaction usage every time we execute SU25. We have about 10 ABAP production systems, but ECC is typically the biggest impact. On top of that, the bigger enhancement pack upgrades add to the complexity just due to the increase in changes and new auth object/field values.

For a smaller support pack upgrade it's taken our group about 100 hours, and for larger support packs double to even more for hours. Out of curiosity, how long does your group spend reviewing SU25 changes and updating SU24/roles? Have you found any useful documentation tips, so future SU25 activities have a good reference for accepting/rejecting SAP values vs your own companies values for SU24 changes?

We've found changes not documented in the 2b,2c,2d steps and sometimes have to compare roles with production to see if there's changes. It can be quite manual and time consuming so I'm sure others may have suggestions to improve workflow. Cheers.

[Former Member]

I have it down to 1 manday and am also a big believer in SU24.

Trick is to consider SU25 step 2b when buildind the roles and maintaining SU24 for core transactions should be given preference over myriads of parameter transactions.

Then a job well done in step 2b means that you can sail through 2c very fast because you know what is going to be the impact.

We also have a tool which we built (it is also used by SAP now for maintaining RFCs in SU24 - see note 1682316) which can programmatically work out how SU24 can be optimized and simulates upgrades and changes to SU24 or menus to see what the functional impact is on the roles. You can then perform step 2c before 2a, before 2b and any time after a bigger decision is made in 2b comparisons. 2c can then be performed with a blind fold on..  🙂

Cheers,

Julius