Why are the ATC-result lists different dependent on how the checks get triggered?

[BaerbelWinkler]

Hi Folks,

I have a weird and somewhat hard to grasp issue with the ATC-result lists. Apparently dependent on how the ATC-checks get triggered, there's a difference in which findings show up as exempted even though the same central check-variant is used.

When a colleague tried to release a task from development, he got this list of unresolved findings (not all priority 3 messages are shown):

When the transport is checked via a report-program utilising cl_satc_object_set_factory (based on this Q&A) the result list looks like this for unresolved findings:

Listing unresolved and exempted findings for this result has the long list:

The "Select-Statement can be transformed ..." findings are all included in the baseline I created in August 2018, so it's weird that they get shown as unsresolved during task-release. The "Changing Access..." findings are correctly shown as this check was left out of the baseline-check on purpose.

I've noticed this odd behaviour a few times during the last couple of months and have a hunch that it might be related to a support-package update we did in early December from NW 750 EHP8 SP 07 to 13. Why this hunch? Because it seems to only happen for Z-code somewhat related to SAP-code as in this case where user-exits in FG XLOI are impacted.

Has anybody else run into this? I may end up creating an OSS-message but it'll be difficult to prepare in a way that's reproducible as the results are obviously moving targets and won't stay around for long.

[BaerbelWinkler]

thomasfiedler olga.dolinskaja

Hi Thomas, hi Olga,

sorry to ping you directly, but questions in "ABAP Testing and Analysis" regularly seem to "fly below the radar" judging from the number of views they get.

IIRC from the DSAG-development meeting in December, the issue descrbed seems to have already been noticed but I couldn't find anything about it. At the moment, my only question is if I should move this to an OSS-message even if the issue will not be easy to reproduce or if there are other options to have somebody look into it?

Thanks much and Cheers

Bärbel

[BaerbelWinkler]

Just a quick update that I opened an OSS-message about this on February 4.

[BaerbelWinkler]

The SAP-Team provided a Note to resolve this issue:

2752191 ATC: Duplicate ATC Findings for Function Module Exits

Update: the note needs to be applied in the system from where the ATC-checks get triggered, so in our case the satellite-systems.