Checking of modified SAP standard objects in RFC context doesn't work

[ConjuringCoffee]

Currently it is not possible to check most modified SAP standard objects when the ATC check is called via RFC.

The cause is this logic within method INFORM of ZCL_AOC_SUPER:

        SELECT SINGLE cnam FROM reposrc INTO lv_cnam
          WHERE progname = p_sub_obj_name AND r3state = 'A'.
        IF sy-subrc = 0
            AND ( lv_cnam = 'SAP'
            OR lv_cnam = 'SAP*'
            OR lv_cnam = 'DDIC' ).
          RETURN.
        ENDIF.

In an RFC context, any information contained in table REPOSRC is irrelevant to this check.

Unfortunately, I don't have a good idea on how to solve this yet.

[ConjuringCoffee]

@larshp, do we even need this piece of logic? You introduced this logic in commit 8314019, but I don't really understand why. Do you still remember over 10 years later?

I've performed some more intensive tests and the logic even removes some results on the local system where it isn't supposed to. I thought CNAM in REPOSRC refers to the person who last updated the object, but it seems to refer to the creator of the object instead. So it seems like this check isn't about modifications, but simply about detecting SAP standard objects. This means modifications to SAP standard objects aren't always checked.

At least on my 7.58 setup, SAP standard must already be performing a check like this. I can't get results for SAP standard objects even if I wanted to. I'm getting the best results if I simply disable this logic entirely.

My suggestion would be to remove it.

[ConjuringCoffee]

Wait, no, I am getting results for a single SAP standard object, MM06EF0B_BUCHEN_2. No idea why.

Adapting the check to use UNAM instead of CNAM would then be my suggestion.