Technical Articles
Remote Code Analysis in ATC – How to check Smart Forms and Adobe Forms
This is the tenth blog of the blog series about Remote Code Analysis in ABAP Test Cockpit (ATC).
See also blogs:
Motivation
You want to check your custom code Smart Forms and Adobe Forms with remote ATC. In this blog we will check a Smart Form and an Adobe Form for the SAP S/4HANA readiness for example.
Prerequisites
The central ATC check system SAP_BASIS >=7.52 must be set up and configured in your system landscape: see Remote Code Analysis in ATC – Technical Setup Step by Step.
For executing remote ATC checks from your development system use prerequisites from Remote Code Analysis in ATC for Developers.
For Smart Forms: in the remote checked systems implement the SAP Notes 2558283, 2613349.
For Adobe Forms: in the central ATC check system implement the SAP Note 2629856. In the remote checked systems implement the SAP Notes 2617401, 2613349 and 2617830.
Execute remote ATC check on your central system
In the ATC transaction just configure ATC check run series (click ATC Administration > Runs > Schedule Runs > Create (more on this in the Configuring Run Series in the Central System) over the package in your remote checked system, which contains your custom Smart Forms and/or Adobe Forms, which you want to check for SAP S/4HANA readiness:
Schedule the remote ATC run.
The SAP S/4HANA incompatibilities in the custom Adobe Form and Smart Form in the remote check system will be displayed in the ATC results and can be analyzed in detail:
Execute remote ATC check on your development system
If you are on your development system and want to check your custom Smart Forms and Adobe Forms objects for incompatibilities with SAP S/4HANA for example, you can run remote ATC checks in the ABAP Development Tools in Eclipse.
Just select the package containing your Smart Forms and/or Adobe Forms and use the context menu Run As -> ABAP Test Cockpit With… and specify the ATC check variant (e.g. S4HANA_READINESS_REMOTE).
The SAP S/4HANA incompatibilities in the custom Adobe Form and Smart Form will be displayed in the ATC results and you can analyze them.
Hi Olga,
My Central ATC system is on sap basis 7.51 SP4. So can I apply these notes?
Thanks
Srinivas
Hi Srinivas,
you need SAP_BASIS 7.52 (see "Prerequisites" chapter of the blog).
Regards,
Olga.
Hi Olga
As smartforms are generated every time, there is no version management. Therefore, I assume there is no option of using the baseline with them?
Can you confirm?
Thanks
Ian
Hi Ian,
there is no restriction for using baseline with Smartforms. Baseline has nothing to do with the version management. You can can change the code many times, and if it still looks the same after your changes, then the baseline remains valid. So if newly generated Smartforms have the same code, then they stay in the baseline.
Regards,
Olga.
Hi Olga,
In ATC check configuration screen, there is a checkbox called 'Calculate Quick Fix Proposals'. What exactly is the functionality of this checkbox?
I was expecting the ATC result set to suggest the possible errors which could be corrected using quick fix feature when I select this checkbox 🙂
Thanks,
Muralikrishnan
Hi Muralikrishnan,
thank you for this remark. This checkbox is only relevant for the ATC runs in the context of the SAP Fiori App Custom Code Migration, since the App needs to calculate the Quick Fix filter in order to show, which ATC findings can be adjusted manually and which ATC findings can be adjusted by Quick Fixes. For all other use cases this checkbox should not be used. We will correct the SAP Help documentation regarding this.
Regards,
Olga.
Hello All,
What is the benefit of "Calculate Quick Fix Proposals" in ATC. Is it related to Eclipse ADT Quick fix.?
Please suggest.
Thanks,
Sampat
Hi Sampat,
please see my reply to Muralikrishnan above, it answers your question.
Regards,
Olga.
Hi Sampat,
just to let you know: we have updated the documentation and issued the correction SAP Note 3000103. You can implement it to make the checkbox “Calculate Quick Fix Proposals” in ATC invisible.
Regards,
Olga.
Dear Olga,
does this also cover AIF interfaces (adobe interactive forms) from object type R3TR SFPI?
Since source code can be written in the initialization block, there could also be findings, that may cause problems when switching to the HANA DB (HANA code compliance) and/or to S/4HANA.
So far we have not found a way to scan the interfaces as well.
I am thankful for any advice.
Martin Reichenecker
Hello Martin,
When you check an Adobe Form (SFPF Object) the corresponding Interface (SFPI) is checked. Technically speaking the corresponding generated Function Group /1BCDWB/SAPLSM00000xxx is checked. The generated function group include the custom code from “Initialization” and “FORM routines” blocks.
Best regards,
Mikhail
Dear Mikhail, this helps a lot. Thank you!