Remote Code Analysis in ATC – Scanning customer extensions
This is the seventh blog of the blog series about Remote Code Analysis in ABAP Test Cockpit (ATC).
See also blogs:
You used various extensions in your custom code and want to include your modified source code objects into ATC check runs.
With SAP NetWeaver AS ABAP 7.52 we widened the ATC scan scope to support all customer extensions:
- All kinds of modifications
- Explicit Enhancements
- Implicit Enhancements
- User Exits, like SAPMV45A, CMOD
Note: modified source code objects can be checked only from the central ATC system remotely. On the development system ATC checking of modified source code objects is not yet supported until further notice.
The central ATC check system must be on the SAP_BASIS 7.52 and set up and configured in your system landscape: see Remote Code Analysis in ATC – Technical Setup Step by Step. In the central ATC check system implement the SAP Notes 2524014 and 2519807. In the remote checked systems implement the SAP Notes 2485231, 2270689 and 2451683.
Quality Expert: Include modified objects into ATC check runs
When you configure ATC check run series in the ATC transaction (click ATC Administration > Runs > Schedule Runs > Create, more on this in the Configuring Run Series in the Central System) you can include all your modified objects using the Include Modified Source Code Objects checkbox on the Modified Objects tab (default choice for ATC mass runs).
Alternatively you can specify the subset of modified objects by packages (modifications may be located in SAP packages) and object types on the Modified Objects tab.
Developer: View modified objects in ATC results
After you execute an ATC check run, you can see the ATC findings in your modified objects like in this example:
awesome news. Finally this is something I waited for years.
I hope you do have a session at Teched to get my hands dirty on that topic and also get an update on the next steps in this area.
nice to hear that 🙂
We will have both lecture (S4H130) and hands-on (S4H164) at the TechEd, focused on the whole custom code adaptation process (incl. ATC). Hopefully we can do also Networking session in Barcelona (Thomas does it in Las Vegas), where you can also get news and plans regarding ATC.
how can we avoid checking generated Coding like Function Group for Table Maintenance ? We need this to be excluded in single Developer Checks and Task Release Checks.
Before the actual version of ATC we have implemented an "implicit Enhancement" to achieve this goal. But as far as I have read the Blogs and News about the Central ATC Server, this must be possible now within the Standard, isn't it ?
yes, ignoring generated code is possible with central ATC check system on SAP NetWeaver AS ABAP 7.52.
I followed these steps and they work great the VMOD package.
But I try the LVS package where I was expecting results at least for the function group XLTO, but I'm not getting any objects analyzed.
Am I doing something wrong for this package?
João Paixão Silva
please provide a couple of examples of the modified objects in LVS, so that we can try to reproduce the behavior. Preferably with a ticket to SAP on the component BC-DWB-TOO-ATF.
Thank you for the quick reply.
I've opened the ticket 764701 / 2022.
Please let me know if you need anything else.
João Paixão Silva.