Some strange behavior/checks of ATC

[DanielB]

Hello,

we're using ATC for a few weeks now and I've some questions about specific checks.

1. "WRITE ... TO" can often be replaced by string templates for example, but how to replace a "WRITE ... TO ... UNIT" or an "WRITE ... TO ..." for a field with conversion routine "CUNIT"?
2. Why is a "LOOP AT ... GROUP BY ..." with a "LOOP AT GROUP ..." considered as nested loop?
3. I splitted a SELECT statement with a sub select on a buffered table into two separate SELECT statements (2nd one with "FOR ALL ENTRIES"), because sub selects ignore DDIC buffering. But now that I have two SELECT statements ATC says that I could transform the two SELECT statements to a single one. Shouldn't ATC check the buffer setting in DDIC and then suppress this message?

We're using ATC in Version 7.52 SP2

Thanks
Daniel

[DanielB]

Ok, for 2. (LOOP AT GROUP) I found a note: 2642712 - ABAP Test Cockpit meldet LOOP AT GROUP

For the other two problems I'm still lookin for a solution.

[former_member184455]

Hi Daniel,

I now asked development whether they want to suppress the message if any of the involved tables is buffered.
From performance point of view the situation is not straightforward if a buffered table is involved in SELECT + SELECT ... FOR ALL ENTRIES. Response time in comparison to a JOIN will depend on whether the buffer can be used at all, the type of buffering, the number of read lines, etc. In performance-critical code one should compare both versions.

Best Regards, Randolf