Re: How to find the fields that are made 'Required' in screens modified by a Support Pack Upgrade

That's a really titanic task, I don't think it's the usual way to do it; I'm pretty sure there are "release" notes about the general functional changes. After that, all batch input custom programs should be tested again to make sure they work.

Note that relying on the "required" attribute is not sufficient. There are probably as many checks inside the ABAP code as via the dynpro attribute.

In solution manager, there's a tool (CDMC - change impact analysis), but I remember this kind of analysis did not exist when I looked at it (in 7.1 or 7.2).

Anyway, you are the last one to decide. You should debug SE51 to see how the version comparison is achieved. I guess you should use SVRS_GET_VERSION_DIRECTORY_46 (valid in 7.4), to get each version (equivalent to the internal statement IMPORT DYNPRO, but the function module is for versions). You get the dynpro in an obscure format ("required" is in bit 3 of FLG3 of D021S table), so you may prefer using the function module RPY_DYNPRO_CVT_INTO_EXTFORMAT to convert this obscure format in a more readable format.

As I said previously, I think it will take you much more time to develop and analyze, than solving the probable very few issues in the test system or even in the production system.