Skip to Content
Technical Articles

Remote Code Analysis in ATC – Technical Setup step by step

This is the second blog of the blog series about Remote Code Analysis in ABAP Test Cockpit (ATC).

See also blogs:

 

Technical Requirements

To use Remote Code Analysis in ABAP Test Cockpit (ATC) you need to install and configure one ATC central check system SAP_BASIS 7.51 or >=SAP_BASIS 7.52. Depending on how many custom objects you need to consider, SAP recommendation for system sizing is about 1 CPU and 4GB RAM per 16000 objects and day, for data volume on the DB about 400kB per object.

The systems, which you want to check in your landscape, must be on SAP_BASIS 7.00, 7.01, 7.02, 7.30, 7.31, 740 or 7.50 releases.

The RFC destinations for all checked systems must be provided in the ATC central check system and RFC-stubs must be implemented in all checked systems.

Depending on your support package level you need to apply the respective SAP Notes for using ATC to perform remote analysis. See the collective SAP Note 2364916.

If you intend to run ATC for the objects in your own custom namespaces (other as Z* or Y* namespaces), you will need to register custom namespaces of the checked systems at the central ATC system.

You would also need authorizations for administrative and quality assurance activities. See Authorizations for the ABAP Test Cockpit.

Please also assign your RFC user the corresponding roles as described in SAP Note 2672703 Authorization roles for remote check scenarios

PLEASE NOTE: The ATC central check system can only analyze systems at the same or lower software levels.

1. Setup System Role

By setting up the system role you can specify the current system as a central check system for remote ATC checks.

Log on to the ATC central check system as ATC administrator and call transaction ATC. Under ATC Administration -> Setup double-click the Set System Role entry:

Switch to change mode, choose ATC Checks by Object Providers Only option and click Save button.

This option defines that the current system takes the role of the ATC central check system and ATC is used to analyze development objects in remote systems.

 

2. Define RFC destinations for checked systems

Use transaction SM59 to create RFC destinations for each ABAP system, which will be checked in the current central ATC system.

 

3. Maintain Object Providers

While ATC check runs in the central system, the ATC framework uses RFC connections to the remotely checked systems to extract a model from the custom code for analysis. Object Providers define these RFC connections and therefore they must be configured for usage.

Every Object Provider must be assigned to a System Group, therefore before you configure Object providers, you need to create System Groups. A System Group contains multiple SAP systems of the same SAP release. It can be helpful to define more than one System Group (e.g. for each subsidiary of your company with its own custom code). In the central check system ATC exemptions are valid only for the whole relevant System Group.

To create a System Group, in the ATC transaction, under ATC Administration -> Setup double-click Maintain Object Providers and then double-click the item System Groups for selection. Switch to change mode, click the New Entries button in the toolbar and enter an ID and short Description for the new system group to be added.

Now you can maintain Object Providers. Select RFC Object Providers by double-clicking, switch to change mode and click the New Entries button. Specify ID, Description, System Group and the valid RFC destination to the remote SAP system. Repeat these steps for each Object Provider you want to set up.

Correction Systems define RFC connections which can be used to view and change the source code.

 

4. Configure Run Series

Now you need to configure ATC run series for remote ATC checks. In the ATC transaction under ATC Administration -> Runs double-click Schedule Runs and click the Create button in the toolbar. Enter the name for the series in the dialog and click Enter. Specify the data for the new series configuration: Description, Check Variant (global Code Inspector Variant), Object Provider and Object Selection (choose the packages or the object set in the remote system.). Save your configuration.

 

5. Schedule Run Series

Now you can schedule ATC check run in a central system to check remote systems. In the ATC transaction, in der Overview, under ATC Administration -> Runs double-click the Schedule Runs entry. Select the run series in question from the list with run series and click the Schedule button in the toolbar. Choose Execute (or F8) to run ATC checks.

 

6. View Results

After successful execution of the ATC run, the check results from the remotely checked SAP systems will be available in the ATC central check system for analysis.

Now you can logon to ATC central check system as developer, and view the ATC results in the ATC Result Browser (switch to the ATC Result Browser in the SE80).

In the ATC Result Browser, choose Results by system group, select the relevant system group and display its ATC run series.

Double-clicking the node of the run series allows to view the list of findings. Double-click a finding to view the details. And now you can examine the finding in detail, access the related documentation with information on how to correct it, navigate to the relevant source code line and correct the finding or request an exemption. That’s it.

 

118 Comments
You must be Logged on to comment or reply to a post.
  • This will create a one time run. However what if you want this to run every 30 days? How would you automate this so that you would not have to manually schedule this to run each time?

  • Dear Olga,

     

    Thank you presenting a series of detailed step by step ATC set up.

    We have Evaluation system set up done and SAP Notes implemented on source ECC system. But when we run remote ATC check from evaluation system, we observe considerable number of tool failures. Along with priority 1,2 & 3, the number in tool failure is in hundreds. The error listed is primarily  “Prerequisites not met”.

    Could you please let us know what action needs to be taken to address this issue.

    • Hi Ilyas,

      Did you also process the manual post-implementation steps mentioned in the SAP Notes you applied? E.g., did you execute program RS_ABAP_INIT_ANALYSIS as menitoned in SAP Note 2270689?

      Michael

       

      •  

        Hi Michael,

         

        Yes I ran program RS_ABAP_INIT_ANALYSIS in check system. If I were to run the program again, the message says “Tables have already been created”.

        Our check system is SAP_BASIS 701. So I don’t know if there needs to be any additional notes applied. Could you please suggest..

         

        FYI, I can confirm below SAP notes are applied in check system:

        2270689, 2011106.

         

        Below manual activity is also done:

        Create the function group SABP_COMP_PROCS_E in the package SABP_COMPILER (the master language is German – DE).
        Activate the whole function group immediately after the creation.

         

  • Hi,

    i already implement this solution on different sap servers, but with one i had aproblem that I always get the exception CX_SY_IMPORT_MISMATCH_ERROR.

    Code:
    import SYMBOLS = P_SYMBOLS CHECKSUM = P_CHECKSUM from data buffer L_SCR_ABAP_SYMB-CONTENT accepting padding.

    Is there any solution for this problem? I couldn’t find something at SDN or in support.sap.com

  •  

    Hello,

    after a hard and long way to bring this bird to fly we received our first scan result. But a lot of tool failures attend the scan result.

    One tool error I do not understand:

    It seams that the name of report is not forwarted to the message. There is a blank between the dot (.) and “program”

    The note 2270689 is already implemented.

    Also the message type (others) and the check title (unavailable) are not really precise.

     

    But which exception or runtime error raise this message? What is the cause for this error? How can I analysis this?

     

    Many thanks in advance.

     

    with kind regards

    Stephan Scheithauer

    /
      •  

        Hello Michael,

         

        thanks for your reply Michael.

         

        Yes, the report was executed. At least I could see, that the tables were created and also filled.

        When I start the report again, I get the message, that the report did already run.

         

        Could the report RS_ABAP_INIT_ANALYSIS be really the reson why I did not receive remote data?

        Other reports was checked correctly (at least over 2000). So this is not a general issue but I want to understand the issue and how to fix it so that I can check the rest of the reports.

         

        Thanks in advance

         

        With Kind regards

        Stephan Scheithauer

        • Hello Stephan,

           

          did you find a solution? I encounter the same issue and would like to know how to analyze the messages with check title ‘Unavailable’.

           

          Best regards

          David

  • Hello there,

    I have 2 questions re the setup of such a ATC system and performing the custom code check for S/4 adaptation.

    1. Am I correct in assuming that no HANA database is required for the ATC system?
    2. If the ATC system is running using a cloud hosted platform (Azure, AWS, etc), are any parts of the analysed custom code transferred from the target system to the cloud-based ATC system? This is particularly relevant in terms of security and Intellectual Property (IP).

    I would be grateful for any clarifications!

    Thanks,

    Michael

    • Hi Michael,

      1. yes, HANA database is not required for the central ATC system.

      2. custom code is not transferred and is checked by the central ATC system remotely (RFC).

      Regards,

      Olga.

      • Hi Olga,

         

        Thanks for your response.

        If the ATC check is done remotely without the (even temporary) transfer of custom code, doesn’t this mean that the check might as well be done in the target system itself?

        Sorry to be specific here, but from the viewpoint of where the Intellectual Property (IP) even temporarily resides -esp when the ATC central system is cloud-based- is important to us.

         

        Thank you!

        M

        • Hi Michael,

          the ATC check is RFC-based, it is executed in the ATC central system for remote systems, the underlying Code Inspector check variant must consist of RFC-based checks only. See also Remote ATC checks in the SAP Help.

          Best regards,

          Olga.

  •  

    Hi Olga,

    We have configured the central ATC system – SAP_BASIS 7.52 and able to get S4H ATC violations from checked system (SAP_BASIS 7.40, SP17). Applied notes as stated in #2364916. Any how we are getting few “Check Failures” message along with ATC result. Can you plz suggest how it can be remediated.

    In addition – if we need to run ATC on code base in system configured as central system how can it can be performed. Do we need to define current system in object provider?

     

    Thanks & Regards

    Rajesh

    • Hi Rajesh,

      did you also process all manual post-implementaton steps as stated in the applied SAP notes?

      You cannot check the ATC central check system itself with the remote ATC infrastructure. You need to check it locally (switch the system role to “Local ATC Checks only”).

      Regards,

      Olga.

      • Thanks Olga for responding,

        We are getting tool failure for only 8 objects. Yes we had implemented manual corrections as stated in notes. Only 2270689 is pending as we are not able to download this note. Is this can be reason for tool failure?

        Thanks & Regards

        Rajesh Dadwal

        •  

          Thanks Olga for responding,

          We are getting tool failure for only 8 objects. Yes we had implemented manual corrections as stated in 2364916. Only 2270689 is pending in checked system as we are not able to download this note.  But report RS_ABAP_INIT_ANALYSIS is available and we executed it.

          Thanks & Regards

          Rajesh Dadwal

          • Hi Rajesh,

            yes, the 2270689 is relevant for RFC extractor, it must be implemented in the checked system. See “Technical requirements” chapter of the blog.

            Regards,

            Olga.

          • Thanks Olga,

            As you suggested, Now we have enabled remote ATC check. The remote ATC output received was not consistent with results earlier extracted using custom code migration worklist (Using – SYCM*) . Result from remote ATC are fewer in violation count & SAP notes #.

            Can you suggest what can be the possible reason. Right now remote ATC is not giving all results as compare to Custom code migration worklist.

             

            Thanks & Regards

            Rajesh

             

          • Hi Rajesh,

            generally it should not happen.

            Maybe you have your own custom namespaces (other as Z* or Y* namespaces) to be checked with ATC? Then you need to register custom namespaces of the checked systems at the central ATC system.

            Otherwise if you could provide a concrete example of the findings detected with SYCM and not found with remote ATC, please open the OSS ticket. It must be looked at in detail.

            Hope this helps.

            Best Regards,

            Olga.

          • Hi Olga,

            Yes, we have custom namespace. I can only see 2 namespace in this report which are not registered but anyhow Remote ATC is still showing the violation from these unregistered packages.

            • Remote ATC result-set is showing more violations count coming from couple packages
            • SYCM* result-set – showing less violation count coming from many packages.

            One question – customer name space role is ‘C’ in current source system.It can be the possible issue? and need to be changed to ‘P’. But these settings are same for both approach. Please suggest.

             

            Thanks & Regards

            Rajesh

          • Hi Olga,

             

            This seems to be possible issue. When we are running ATC remotely it is only getting violations for package marked with role (P) in sub-system. All these packages are for custom development (Non Y* / Z*). However with SYCM extract based approach it is giving simplification violation.

            I have changed role for few packages and now its giving results thou ATC run. Still output is not exact same as compared to SYCM.

            I checked few programs which were giving issues in SYCM but if run ATC on same program in Central system locally (without remote ATC) it is not giving any violations.

            As ATC variants is recommended approach, so believe better is trust on ATC results.

             

            Thanks & Regards

            Rajesh Dadwal

  • Hi,

    I could make all the configurations and installed many notes. So far so good, I also could check the test remote system (C13) with Z check variants.

    But when I select one of these variants FUNCTIONAL_DB or PERFORMANCE_DB, then I get a syntax error:

    But: When I switch off the first 4 of 5 checks in this variant, then the error disappears.

    I was searching the SAP knowledge database and also the internet, but nothing helps me to solve this problem.

    Can you explain and solve for me what might be the problem?

    Regards, Frowin

    /
  • Hi,

    We have many SAP systems in the company on different SAP_BASIS levels: 7.11, 7.31, 7.40.

    Currently we could establish remote ATC connections to systems with SAP_BASIS 7.31 and 7.40, and also we could run remote ATC tests successfully.

    Unfortunately in the technical requirements is written SAP_BASIS 7.11 is no supported.

    These systems with SAP_BASIS 7.11 are our main system with target to do remote ATC, because we will upgrade for SAP S4/HANA in near future. Remote ATC would be a great help to do this Job.

    Questions:

    • Will this SAP_BASIS 7.11 level be supported in the near future?
    • What is the reason for not being supported for remote ATC? But SAP_BASIS 7.02 is being supported!

    Any help for that?

    Regards

    Frowin

    /
    • Hi Frowin,

      unfortunately, the SAP_BASIS 7.11 is not supported due to the technical feasibility in this particular release. Please consider, 7.11 is not the underlying release for SAP ERP and therefore the SAP S/4HANA conversion path doesn’t exists for 7.11 and consequently S/4HANA related custom code checks with remote ATC don’t make any sense.

      Best Regards,

      Olga.

  • Hello,

    we have set up an ATC Central System (SAP_BASIS 7.52). With this central ATC we want to check a remote system for S/4 HANA readiness.
    Which Variant do i need for the Checkrun? I found the following variants:
    S4HANA_READINESS_REMOTE and S4HANA_READINESS_1709 , which is the right one?

    As the Object Provider i use the remote system.

     

    Gruß
    Toni

     

    • Hi Toni,

      the S/4HANA release specific variants check for the simplification items of the corresponding S/4HANA releases. For example the S4HANA_READINESS_1610 checks all relevant simplification items for S/4HANA 1610 and so on.

      If you need to check for S/4HANA 1709 readiness, you can use either S4HANA_READINESS_REMOTE or S4HANA_READINESS_1709. Both would be correct.

      Viele Grüße,

      Olga.

      • Thanks,

        i did now the remote S/4 HANA Checks with the ATC and also with the SCI.

        I wonder why do I get different results?

        ATC = 168 “Errors”

        SCI = 25 “Errors”

         

        Gruß
        Toni

          •  

            OK,

            thank you for the Info, that ATC should be used if possible.

            One Question again. During the upgrade process to S/4 HANA via SUM, the code will also be checked, right?
            Which mechanism does the SUM use?

             

            Gruß

            Toni

          • During the system conversion from ERP to S/4HANA (we call it system conversion, not an upgrade, because S/4HANA is a different product family) the SUM executes different tasks: database migraton, software update to S/4HANA, tables content conversion to the S/4HANA data model, but doesn’t check custom code.

            If you mean SAP Readiness Check, which runs in the preparation phase before SUM, then it uses Code Inspector and Custom Code Analyzer (SYCM), but delivers only high- level overview over the affected custom code by the S/4HANA simplifications, for a deep-dive analysis still the remote ATC must be used.

            Regards,

            Olga.

  • Hi Olga,

    Just wanted to say thanks for this informative blog.

    I would like to ask if could we use a SAP CAL system as the central ATC check system or do we have to have to install a standalone SAP NetWeaver system (SAP_BASIS >=7.51) as we only require to do the S4 HANA checks as a one-off exercise.

    if we can use a SAP CAL system do you have any links which I can reference.

    Thanks, Raj

     

  • Hi Olga/All

    I’m facing an issue with viewing code in the remote system.

    For the Object Provider I have configured an RFC Destination with a Service User and in the Correction Systems I have configured an RFC Destination with a normal dialog user (me).

    I am assuming that when I try to view the source code of a finding then the Correction System RFC destination would be used?

    However it appears that the Object Provider is used.

    Can you confirm if my thinking is correct.

    Thanks

    Ian

     

    • Hi Ian,

      Did you try to change the target system for navigation to the correction system in the ATC result list as shown in the screenshot below?

      If you did not change this setting, the target system for navigation would be the checked system.

      Kind regard,
      Michael

      /
      • Hi Michael

         

        No I hadn’t!  Many thanks for this. I’d obviously not seen or certainly understood the option.

        Problem solved!

         

        Cheers

        Ian

         

  • Hi Martin/All

    As a follow on question, how have you defined the user for the RFC Destination for correction system? Do you use the current user, a specified dialog type user or a system user?

     

    Thanks

    Ian

  • Hi Olga,

    Thanks for this informative blog.

    We have 3 HANA systems with NW 740 SP13, NW 750 SP003. In all these systems I want to run ATC check on MV45AFZZ to analyse the custom code written in its subroutines.Could you please elaborate on how to run the ATC check on Include MV45AFZZ in all these systems?

    Thank you

    • Hi  Saurabi,

      which SAP_BASIS version does your central ATC check system have? User exits get scanned by ATC starting with NW AS ABAP 7.52.

      Best Regards,

      Olga.

  • Thanks Olga for your response.

    I tried to run ATC check in NW 752 as well. But since package of the include MV45AFZZ is VMOD, ATC doesn’t accept it as it is SAP standard.

    • Hi Saurabi,

      actually user exit must be scanned by ATC 7.52. It sounds like a bug. Could you please open a ticket to SAP and provide details?

      Thanks and Regards,

      Olga.

  • Olga Dolinskaja

    Hi Olga,

    after switching to “block on errors” end of last week in our ATC-setup, one of our developers in Brazil ran into a rather nondescript “tool failure” error. As this caused a priority 1 finding, it prevented the transport’s release.

    When I had checked the same transport manually, no tool failure occured. After some more trial and error, plus the information from the developer that he could release his transport when logged in with language “EN” but not with “PT”, I checked if I could even login to the central system with “PT”. I couldn’t as it wasn’t one of the installed languages.

    After discussing options with my colleague from the basis team, we decided to simply set the trusted RFC-connection to default language “EN” (instead of installing multiple and not really needed additional languages in the system). That got rid of the tool failure immediately.

    How about updating what you have in the blog post, with the tip to take language(s) into account for the system- or RFC-setting?

    2. Define RFC destinations for checked systems

    Use transaction SM59 to create RFC destinations for each ABAP system, which will be checked in the current central ATC system.

    Cheers

    Bärbel

  • Hello Olga, hello everyone,

    thanks for the great step-by-step guide to the Remote ATC Check.

    We set up the ATC central check system and implemented the SAP Notes in the Remote check system. After we performed an remote ATC-Check (from the ATC central chek system), we observe a significant number of dumps:

    Syntax Error in CL_ABAP_COMP_PROCS_E=============CP_ABAP_COMP_PROCS_E==========CP
    Note 2270689 (running program RS_ABAP_INIT_ANALYSIS) and Note 2527903 solved the dump.

    When we now start an Remote-ATC-Check we get some tool failtures with exception: CX_SY_IMPORT_MISMATCH_ERROR.


    I couldn’t find any suitable notes for this.

    The SCI Code Inspector->Management of->Test
    Check Class “CL_CI_TEST_FIELD_EXT” of Note 2272014 exists (active) in both systems.

    Are there any further notes other than those listed in the collective note 2364916?

    Our ATC Central Check has the SAP_BASIS Version 751 0004 – SAPK-75104INSAPBASIS

    and the Remote Check System SAP_BASIS 750 0008 – SAPK-75008INSAPBASIS

     

    Many thanks

    Michael

    /
    • Hi Michael,

      the second SAP note 2527903 must be implemented in the ATC central check system. The error indicates that this SAP note could has been implemented in the remote check system, where it brings nothing. The line number 89 of the crash speaks for it too. You also implemented SAP note 2272014 in both systems (central check ATC system and remote check system). This is only necessary in the ATC central check system.

      Best regards,

      Olga.

    • I have been trying to schedule a sci job and getting an error message, as shown in the attached screenshot.

      I also tried to implement sap note # 2270689, 2485231 manually uploading from the system, directly using download option but didn’t find the mentioned note in the snote list as no error appears at the end and it took longer to upload and download. I also increase the profile parameter for snote.

       

      Something wrong with note implementation, could anybody please guide how to rectify this?

       

      Regards

      Abbas

       

      /
  • /
      • Thank you so much Olga,

        I assumed it, so I asked it because we haven’t set the baseline check at any time and the results are so differents between them.

        For instance, for “QT0_1809_3” (without consider baseline flag) & “QT0_1809_4” (with consider baseline flag) runs, the unique difference is the “consider baseline” flag when I schedule the run and without set any baseline. The runs were executed at the same time and object provider.

        Anyway, thank you for your comments and blog, we have opened an incident to SAP in order to obtain more info.

        Regards.

        /
        • Hi Olga,

          Just to clarify the SAP solution to the incident that I opened regarding to the misunderstanding with baselines.

          The problem was that the object provider QT0 shared the same system group that the object provider QP0 (different systems but the same release), and as the QP0 object provider had a baseline the ATC linked the baseline to the system group.

          We solved it creating a new one system group for QT0.

          Thanks for your help.

  • Hi Olga,

    Thanks for the suggestions and your detailed explanation on setting up ATC. It is very helpful.

     

    We have ensured the setup exactly as suggested in the note 2364916. We have downloaded & implemented note 2270689 in checked system and also executed the program RS_ABAP_INIT_ANALYSIS. Still after that we observe too many check failures in the result. My system is on SAP_BASIS 7.52 SP01. Could you please throw some insight what might have went wrong?

    Best Regards,

    Kamal.

    /
  • Hi Olga,
    I’m a little confused about the RFC destinations.
    I would have assumed that the RFC connection of the correction system and not that of the object provider was used for navigation from the result display in the remote ATC system to the development system. However, a test shows that the provider destination is being used. Or is a fallback logic built in here?
    The system is a 752 SP0, grade 2600034 is built in.

    My idea was to set up the object provider as a named RFC destination with communication user and the correction system RFC Destination as a trusted RFC destination, since our user admins do not like to create service users and dialog users are relatively often subject to password changes. Does this work? I thought I’d found once a documentary somewhere here, but I can’t find it right now anymore.

    greetings
    Jürgen

  • Thank you for the useful blog post!

    According to this document, checks in the SCI can also be performed offline, by extracting code from the source system and uploading it to the target system.

    Can the inspection you described be done similarly?

    In the ATC I have to enter Object Provider which is defined with an RFC destination, so I guess it can’t be performed offline.

    I extracted code from the source system and uploaded it to the target as described in the link, defined an object set and tried to execute SCI inspection with that object set and Check Variant S4HANA_READINESS / S4HANA_READINESS_REMOTE, and got an error with both of them:

    Cannot perform inspection: Check ‘CL_CI_TEST_S4H_DD_ENHANCEMENTS’ is not extract-based

    Is there any way to perform this code analysis with extracted code?

    Thanks!

    • Hello Arik,

      you cannot check for S/4HANA readiness using an SAP NetWeaver 7.4 system as a target system. This is only for SAP HANA readiness. To check your custom code for S/4HANA readiness you need at least an SAP NetWeaver 7.50 system in combination with Custom Code Migration Worklist.

      But we recommend to set up an SAP NetWeaver AS ABAP 7.52 system with remote ATC as described in the blog, since ATC not simply detects all usages of S/4 simplifications in your custom code, but delivers the exact list of critical issues which must be fixed in your custom code if moving it to SAP S/4HANA.

      Best regards,

      Olga.

      • Thank you for your response.

        The target system is SAP NetWeaver AS ABAP 7.52, and I’m able to perform the code analysis for other systems via RFC successfully.

        I want to know if it’s possible to do not via RFC, but by extracting code from the source system and uploading it to the target system.

        • Hi Arik,

          no, the SYCM-based (extract-based) approach of SAP NetWeaver 7.50 doesn’t work anymore in 7.51/7.52. You need to use remote ATC infrastructure.

          Regards,

          Olga.

  • in our central ATC system with NW-7.52_SPS03

    in Configure Run Series, we got error ”

    Check ‘CL_CI_TEST_DYNPRO_USAB_ACC’ is not RFC-based”

     

    what does that mean, what to do ?

    sapnote 2532627 is  already installed (in SPS01) 

     

     

    • Hi Christoph,

      please verify your Code Inspector check variant: all its checks must be RFC-enabled to be executed by the remote ATC.

      Regards,

      Olga.

      • Hi, Olga,

        thanks for your quick answer, (great blog and great hints)

        to maintain the variant is under “Quality Governance” and “Manage Check Variants” ?

        Regards,

        Christoph

        • Hi Christoph,

          yes, correct. Then you are in the Code Inspector and can change/create check variants there. You need to consider: the “green arrow” means the check ist RFC-enabled:

          Best regards,

          Olga.

          /
  • Dear Olga,

    we want to use quick fixes. As I understand, these are only available as of NetWeaver 7.53 – which is part of S/4 1809 and not available as standalone. As we don’t have HANA licensed yet (since we’re still analyzing the impact), is there any way to access NW 7.53 with an SAP on Oracle contract?

    Any input is appreciated.

     

    Best regards,

    Daniel Lippmann

    • Hi Daniel,

      unfortunately not: SAP S/4HANA product family is shipped only on HANA DB, and AS ABAP 7.53 is a part of SAP S/4HANA 1809.

      Best regards,

      Olga.

  • No new ATC results in Solution Manager System

    Hello Olga. Excellent blogs in your web!!

    We setup a Remote ATC system on base of SAP NetWeaver 7.53 in our Integration System (ECI) where we have scheduled Series Runs in background weekly jobs.

    And the scheduled series run :

    We have SAP SOLUTION MANAGER 7.2 SP7:

    But from SAP SOLUTION MANAGER – Work Center, we no see the last ATC results in Quality Cockpick tile. We select a project:

    Then I click in “ATC Supervision” button where I see the historic evolution of ATC results:

    The last plotted ATC result is for May 18th. We have ATC results for the last days. The ATC results from April 30th to May 18th that you can see in the graph, were created when in the SAP interface we can distribute the central ATC run. Since several days, probably after implement same notes, in Remote ATC system there are no possiblity of distribute the ATC results.

    I have configured the development and integration system with the recommended SAP notes. Maybe I have to implement other notes in our systems? What must we do to see the recent ATC results obtained in the central ATC system?

    Greetings.

  • Hello,

    can someone explain the following settings to me, what does this mean when I define an ATC run?

    • Analyze generated code
    • Consider Baseline
    • Calculate Quick Fix Proposals

     

    Thanks

    Toni

  • >The systems, which you want to check in your landscape, must be on SAP_BASIS 7.00, 7.01, 7.02, 7.31, 740 or 7.50 releases.

    I guess ATC should be extended to newer releases over time. Are there note describing versions requirement for central and source systems?

    Am having errors CX_SY_IMPORT_MISMATCH_ERROR with 7.51 as central system, and 7.53 (S4HANA 1809) as source, but not sure should this combination work at all. 🙂

    • Hi Ruslan,

      the ATC central check system can only analyze systems at the same or lower software levels. This is the rule. Thank you for this remark. I will take it over in the blog.

      Regards,

      Olga.

  • Hello,

    Since we have no ATC system with our customer, we want to use the following method:

    https://help.sap.com/doc/saphelp_nw75/7.5.5/en-US/92/b9263c6a6f4f8e888ced5632372d23/frameset.htm

    1. We want to run the SYCM_DOWNLOAD_REPOSITORY_INFO report  in the customer system.
    2. we analyze and import the zip-file in our ATC system via SYCM_UPLOAD_REPOSITORY_INFO.

    I know that this is no longer recommended by SAP and that you should use ATC Check. But we have no other option.
    What are the main differences in the evaluation?

     

    Gruß
    Toni

    • Hi Toni,

      the custom code analysis with Custom Code Migration Worklist is only offered on a SAP NetWeaver AS ABAP 7.50 system. It is not provided anymore on >7.50 releases and was replaced by the remote ATC. Technically the Custom Code Migration Worklist approach is based on the SYCM tool. The difference to ATC is, that SYCM is based purely on where-used list, meaning it finds e.g. all usages of simplified SAP standard code in your custom code but doesn’t analyze if this usage is critical, therefore the false-positive rate is extremely high. The analysis if the usage is critical can do only ATC.

      Best regards,

      Olga.

  • Hello Olga,

    We are setting up Remote ATC Check in Satellite system (SAP BASIS 7.31 SP17) & Central Check system (SAP BASIS 7.51 SP0).

    We have successfully implemented the notes for satellite system, but while implementing SAP Notes for Central Check system Note 2375864 is resulting in syntax errors.

    Implementing notes based on 2364916 ~ SAP NetWeaver 7.51 (SP0)

    • 2375864 – ATC: Remote checks – developer scenario
    • 2378425 – No Customizing of Priorities for Code Inspector Tests
    • 2381471 – ATC/CI: Internal error during determination of objects to be checked prevents check run
    • 2389855 – Remote Navigation for check “Search problematic statements for result of SELECT/OPEN CURSOR without ORDER BY”
    • 2391534 – ATC: Creation of Exemption not possible / Referred object does not exist

    Can you please guide how to proceed.

     

    Thanks

    Sudipta

  • Hi Olga

    Just wondering if there was a ‘Heath Check’ item on your Central ATC backlog? After seeing the one for the Personas 3.0 implementation, it would seem a good idea to have a central note check facility as well as remote notes/RFC destinations/user checks?  As more and more systems get added to our CATC, the harder it will be to keep track of notes implementations etc.

    Regards

    Ian

    /
  • Hello Olga,

     

    we want to export the ATC Check results to xml and to export to Readiness Check 2.0

    We have implemented the SAP Note

    2781766 – Enabling ATC check result export for SAP Readiness Check 2.0

    But… we do not found the button or menü, where we can export the Check in the ATC System to xml ???

     

    Gruß
    Toni

    • Hello Toni,

      in the ATC transaction just select your result in the “Manage Results” screen and use the context menu “Export File for -> SAP Readiness Check for SAP S/4HANA” as shown on the screenshot:

      The colleagues will also document this procedure in the SAP Note 2781766, sorry for the inconvenience.

      Regards,

      Olga.

      /
  • Hi Olga,

    We are running ATC from central system with SAP_BASIS 752, can’t we enable “Check for S/4 related syntax errors ” in the variant S4HANA_READINESS_REMOTE?

    I see this is not marked for RFC. In that case how we can perform “Check for S/4 related syntax errors ” in custom objects for S/4 related syntax errors through ATC running from central system?

    We can’t run ATC locally since our checked system is with SAP_BASIS 750.

     

    /
    • Hi Selva,

      in the documentation of this check you can read that “this check executes the Syntax-Check operation for a certain set of objects. The findings are tried to be matched to SAP notes describing simplification items. We use a heuristic method to search relevant SAP notes that might be related to the syntax-error, that’s the reason why note-findings might be incomplete or have some overabundance”. You can use S4HANA_READINESS_REMOTE without this check.

      Regards,

      Olga.

  • Hi Olga,

    Thanks for your detailed blog.

    We are in the preparation for ERP6 EHP8 to S/4 1809 system conversion and doing custom code impact analysis for S/4 1809.

    We performed Custom code migration work list(SYCM) check, SCI and now ATC check from central system.

    What are the recommended SAP tools to be used for Custom code impact analysis to S/4 1809?

    Thanks,
    Selva.

     

  • Hi Olga,

    last week, I ran S/4HANA Readiness Checks in our central system (NW 7.52) and while looking at the results, thought that it might be good to make these results available to developers. From the description for the “Activate” check box in the “Manage Results” screen, it looks as if I only have to set this flag for the specific result in order to have those results show up in SE80 of the checked satellite system (which is a development system in our case). This however doesn’t seem to be enough as I don’t see the specific run series in the ATC result browser – what am I missing? Is there something else which needs to be in place or executed?

    This is what the help documentation shows:

    “An active ATC result is the central result that has been designated as the current, official result.

    An active result is usually published to the satellite development systems of a central quality-checking system. Developers use the active result to see what needs correction and to apply for official exemptions.”

    Thanks & Cheers

    Bärbel

  • Hi Olga,

    I have activate ATC in remote mode and ATC remote system configuration is ok!

    Master System ATC analyzer now execute a correct remote check and I can browse the remote results with Master System ATC.

    My question is: With remote ATC settings and Eclipse IDE 2019-09 (connected with Master System ATC – SAP_BASIS 753-0000),  can I browse my remote systems ATC results (Eclipse –> Windows –> Show View –> ATC Result Brower) ?

    If it’s possible… what’s missing in my SAP ATC remote Master system ATC to activate Eclipse access?

     

    In my Eclipse on “ATC result Browser” appears this system information message “System doesn’t support result browsing”.

     

    I add this:

    https://blogs.sap.com/2016/12/22/remote-code-analysis-in-abap-test-cockpit-atc-faq/#

    on 2nd October 2019 User Baajeerao Dabhade wrote for same problem, but this functionality doesn’t work! Why?

  • Dear Olga,

    We are in the pre-implementation planning stages for S/4HANA and are working on setting up a remote ATC central system (NW 7.52).  When we execute a check in the central ATC against a test system (NW 7.50), we get the message that ” No Initializaiton (report RS_ABAP_INIT_ANALYSIS) was performed”. The message also refers to note 2270689.  There are so many message/blogs on the ATC that it is difficult to determine what is current and what is old and should be ignored. I am hoping that you can point me in the right direction.

    • Do I apply note 2820446 in the central ATC (NW 7.52) and note 2820873 in the checked system (NW 7.50)?  It seems that note 2270689 should NOT be implemented in either system.
    • Should program RS_ABAP_INIT_ANALYSIS be executed in the central ATC and in the checked system?   There are several blogs that say to run It in the source system but I am not sure if source system means the ATC or the check system.

    Thank you for any guidance you can provide.

     

     

    • Hi Joyce,

      this blog is up-to-date and correct. Please follow it starting with the chapter “Technical Requirements”:

      Depending on your support package level you need to apply the respective SAP Notes for using ATC to perform remote analysis. See the collective SAP Note 2364916.

      This SAP Note provides clear guidance and lists all notes, you need to implement in “Checked System”(=your 7.50 system) and “Central Check System”(=your ATC system 7.52).

      Best regards,

      Olga.

       

      • Hi Olga,

        Note 2364916 says to implement note 2270689 in the Checked System. Note 2270689 then states, “Release 7.50: 2820873 Remote Analysis (for source system, Release 7.50). If Note 2270689 is implemented, please de-implement it.”  I was asking for clarification as my understanding from this is that we apply 2820873 in the Checked System. It does not say if Note 2270689 should be de-implemented before note 2820873 or after.

        Note 2270689 refers to the “Source System”.  Is Source System always the Checked System, not the Central ATC Check System?  The change in terminology is confusing.

        Is program RS_ABAP_INIT_ANALYSIS ran only in the Checked System?

        Is note 2190420 the correct collective note to following for the ATC central system to determine what notes to apply there?

        We are trying to make sure that our checked system and central ATC check system have all of the relevant notes applied before starting our analysis.

        Your blogs have been extremely helpful. Thank you for all of the information and guidance that they provide.

        Thank you,

        Joyce

        • Hi Joyce,

          yes, the change in terminology is a bit confusing, since different developers have compiled these notes, sorry for that. Source system is always checked system (if you look at the pdf document attached to the note 2270689, you would understand it as well). I would recommend to de-implement first the note 2270689 and then to implement the 2820873.

          RS_ABAP_INIT_ANALYSIS must be run in the checked system (as also stated in the 2270689).

          The note 2190420 provides only information. Please refer to the collective note 2364916 as I provided you and the relevant paragraphs there for the “Central Check system” (related to your release 7.52).

          I hope it helps.

          Best regards,

          Olga.

          • Hi Olga,

            This blog is informative, thank you so much for detailed ones.

            We upgraded 1709 to 1809, note 2270689 was appeared in SPAU – when we executed; implementation status got changed to ‘Obsolete version implemented’ in S4 system cleared from SPAU notes section but in MDG system same note got changed to ‘Completely implemented’ status and its displaying in SPAU saying ‘Partly obsolete’.

            Could you please share your thoughts will this cause any issue; both are in 1809 and implementation status are different in S4 and MDG systems.

            Thanks,

            Shruthi

          • Hi Shruthi,

            the note 2270689 is only an informational note. For the 1809 system (SAP_BASIS 7.53) the note 2752728 should be implemented. See also within the note 2270689:

            Release 7.53: 2752728 Remote Analysis (for source system, Release 7.53). If Note 2270689 is implemented, please de-implement it.

            Regards,

            Olga.

  • Hi Olga,

    now I open ATC result on Eclipse Version: 2019-12 (4.14.0) and ADT 3.8.1.

    All red errors, are without lightbulb icon and so are without “Quick fix”. It’s impossible are ALL without quickfix?

    Example in SELECT instruction with red-icon: “Compare length conflict (DOMA MATNR, Note: 0002215424) 40 <-> 18”

     

    I with to have a quick fix to insert pseudo comment to suppress next atc check.

    I don’t understand, becouse in another system conversion I can used the quick FIX to add Pseudo comment…. it’s very important function to make the ATC job easier.

    It’s a problem of ATC settings? Or Ecplise addon version?

     

    Thank you.

     

    • Hi Enrico,

      On which SAP S/4HANA release you execute ATC run? Please note, in order to get Quick Fixes, you need to execute ATC run in ADT locally on the SAP S/4HANA system. Do you do it so?

      Please also note, that inserting pseudo comments is not the way to go to correct ATC findings for SAP S/4HANA and must be used only in exceptional cases. We have heard from customers that developers misuse pseudo comments and suppress findings instead of correcting them. As a result the code remains not corrected.

      Kind Regards,

      Olga.

  • Hi Olga,

    We have implemented one central check System for multiple systems on various releases except release 730. None of the ATC related OSS notes are applicable for release 730.

    Except 2270689 “RFC Extractor for performing static checks” which is proposing to implement note 2822593.

    it looks like ATC is not supported in release 730. correct me if I am wrong and request your input on implementing ATC notes in relesae 730 for checked system.

     

    Appreciate your help in this regard.

     

    Regards

    Kasi

    • Hi Kasi,

      7.30 is supported for remote ATC checks. Most notes from the collective SAP Note 2364916 recommended for Checked system also list 7.30 release. Some functionalities are yet not supported like developer scenario. But you should be able to check 7.30 with ATC remotely.#

      Kind Regards,

      Olga.

      • Hi Olga, I went back and checked each and every note. for ex: “2381403 Infrastructure for remote checks.” This note where we define RFC Destination in SCI is Not applicable for 730. and without this, I cannot even create Remote Check variant to central system.   Version 730 is not applicable for any of the OSS notes mentioned in 2364916 except below given 3 notes. I am missing something here.  I have installed ATC in about 20 systems so far and this is the only trouble version. Any plan of adding these notes to 730 in future or any lead that can make callback work would be great help.

        Only three notes that are applicable for 730 are.

        2822593 Remote Analysis (for source system. Releases 7.11 + 7.30)

        2613349 RFC-Stub for CVA/SLIN remote checks (version 3)

        2810046 RFC-Stub for CVA/SLIN remote checks (version 5)

        Regards

        Kasi

        • Hi Kasi,

          the 2822593 and also the 2190065 (which is also available for 730) should be sufficient to check 730 remotely with the central ATC. RFC-Stub for CVA/SLIN remote checks is for CVA security checks (if you use CVA add-on).

          The 2381403 is only for the remote functionality for developers to enable developers to use the remote ATC on their dev systems, you don’t necessarily need it.

          Regards,

          Olga.

  • Hi Olga,

    We are currently working with my team on the ATC implementation. We have a different issue that hasn’t been listed: ATC transaction doesn’t exist on our system. Does it need to have any required software component or product version for this? I wasn’t able to find this information.

    Thanks and regards,

    Rodrigo.