Skip to Content
Jan 31, 2017 at 04:56 PM

How to convince management to test everything when applying support packages?


As a basis administrator, I can see into the support package stacks and see hundreds of thousands of objects contained in them. Management keeps asking for release notes and asking what has changed with these support packages. The answer from a technical perspective is that everything gets touched. All transactions make a call to the kernel which will be updated. If the ALV (screen display), RFC, or output management code is touched (which it usually is), then that touches pretty much all transactions.

I am looking for recommendations that don't involve implementing a testing tool (long story - but not an option.) The side effect report tells you what the support packages break, not what they change.

How do you explain it to the managers and functional teams so they understand?