Application Development and Automation Blog Posts
Learn and share on deeper, cross technology development topics such as integration and connectivity, automation, cloud extensibility, developing at scale, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 
OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
141,773

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

See also blogs:

Remote Code Analysis in ATC – One central check system for multiple systems on various releases.
Remote Code Analysis in ATC– Working with Baseline to suppress findings in old legacy code
Remote Code Analysis in ATC for Developers
Remote Code Analysis in ATC – Working with Exemptions
Remote Code Analysis in ATC Scanning customer extensions
Remote Code Analysis in ATC – Working efficiently with ATC Result List
Remote Code Analysis in ATC – How to write an ATC check
Remote Code Analysis in ATC – How to check Smart Forms and Adobe Forms
Remote Code Analysis in ATC – Browse Central ATC Result in Developer Systems
Remote Code Analysis in ATC – Maintain exemptions approvers according to their responsibilities
Remote Code Analysis in ATC – FAQ


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, for data volume on the DB about 400 kB per object.

The systems, which you want to check in your landscape, must be on SAP_BASIS 7.00 (not before SP15), 7.01 (not before SP01), 7.02 (not before SP09), 7.31 (not before SP03), 7.40 (not before SP02) or 7.50 releases. For supported SP levels see also the SAP Note 2385520.

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.



 

181 Comments
Enr112233
Discoverer
0 Kudos

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 bdabhade wrote for same problem, but this functionality doesn't work! Why?

OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Enrico,

this functionality is now available. To enable it please refer to the https://blogs.sap.com/2016/12/22/remote-code-analysis-in-abap-test-cockpit-atc-faq/comment-page-1/#_... and the blog mentioned there.

Kind Regards,

Olga.
former_member188032
Participant
0 Kudos
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.

 

 
OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
0 Kudos
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.

 
Enr112233
Discoverer
0 Kudos
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.

 
OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
0 Kudos

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.

former_member188032
Participant
0 Kudos
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
OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
0 Kudos
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.
Enr112233
Discoverer
0 Kudos
Hi Olga,

SAP is S/4HANA 1909 and ATC run locally.

 

There are some cases where I don't correct che code so the pseudo comments is important.
OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Enrico,

please open a customer message to SAP regarding this issue.

Regards,

Olga.

shruthi_nr
Explorer
0 Kudos
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
OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
0 Kudos
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.
kasithunuguntla
Participant
0 Kudos
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
OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
0 Kudos
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.
0 Kudos
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.
OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Rodrigo,

ATC is part of the ABAP stack and is available since SAP NetWeaver 7.2 support package stack 12.

Regards,

Olga.
kasithunuguntla
Participant
0 Kudos
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
OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
0 Kudos
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.
erikhansen03
Discoverer
0 Kudos
Hi Olga,

After successfully implement ATC in several satellite systems we are facing problems with one in particular. When running the ATC scan from satellite system results are not satisfactory. As the screenshot shows, 'Check Tittle' and 'Check Message' is 'Unavailable'.

Do you know how this could be fixed?


 

Regards,

 

Erik
OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
Hi Erik,

please open a ticket to SAP describing in detail what you have done so far.

Regards,

Olga.
psivapuram
Discoverer
0 Kudos
Hi Olga - Thanks for the post. This is really helpful. We have ATC installed in our central system (NW AS ABAP 7.52) and are trying to utilize it to carry out the tests in different satellite systems. While setting up the variant for "Schedule Runs", we noticed that the variant cannot have non RFC enabled checks. Is this a limitation with ATC tool? Will this impact our S/4HANA readiness check for the custom objects?

Thanks,

Phani
OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Phani,

the check variant must be RFC-enabled and contain only RFC-enabled checks since you check the satelite systems from your central ATC check system and they can be accessed only via RFC. This is the prerequisite for remote ATC. Only if you check your system locally, then you don't need RFC-enabled check variant.

Kind Regards,

Olga.
psivapuram
Discoverer
0 Kudos

Thanks for the quick feedback, Olga.

Regards,

Phani

simone_beghi1
Explorer
0 Kudos
Hi Olga,

i'm installing the remote atc service on a checked system with Sap_basis 7.40.

By following the sapnote 2270689, i should implement the sapnotes 2910608 and 2821033 instead of the 2270689 and 2011106.

The problem was that the sapnote 2485231 required as prerequisites a lot of sapnotes as the 2270689. I'll try to skip that but it's not possible and the procedure installed the 2011106 too.

Then, completed the 2485231 activity, i tried to de-implement the sapnote 2270689 but i got a short dump during de-implementation

Category ABAP Programming Error
Runtime Errors IMPORT_DECOMPRESS_FAILED
Except. CX_SY_COMPRESSION_ERROR
ABAP Program CL_CWB_OBJECT_SINGLE==========CP
Application Component BC-UPG-NA

So, what's the next step?

thank you in advance

Simone
OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Simone,

please open a ticket to SAP regarding this.

Kind Regards,

Olga.
sarath_27
Explorer
0 Kudos
Hello Olga,

Thanks for the informative blog!!!

In our project planning to do upgradation from HANA 1809 to 2020. Sandbox is Upgraded to S/4 HANA 2020. So in the phase of CCM . i have to run ATC remote analysis from SBX(2020) to DEV(1809). All set up of implementation of notes in Central Check System( SBX) and Checked System( DEV) done according to version compatibility following the Note 2364916.

When i ran ATC in central check system( Z* & Y* Packages) . I got 3 failure checks.


 

Could please tell us how can I overcome with this failures?..

 

In checked system (Dev) ran report RS_ABAP_INIT_ANALYSIS as mentioned in SAP Note 2270689?. But when i execute i didn't see any message of tables creation / tables already created. I checked $TMP package if any tables created but no results found. I suspect this manually activity is causing issue or am i missing any other prerequisite.

 

Regards,

Sarath.K
OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Sarath,

please open a ticket to SAP, then development colleagues can look into this issue.

Kind Regards,

Olga.
declan_sweeney89
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Sarath,

I found this note for your issue, which should help:

3053737 - CX_SY_ITAB_LINE_NOT_FOUND in CL_CI_TEST_NO_ORDER_BY

 

Can you apply this in the central check system and retry?

 

Thanks,

Declan
sarath_27
Explorer
0 Kudos
Hi Declan,

 

Thanks for your response.

 

Now I am able to run remote analysis successfully with out check failures.

 

Regards,

Sarath.K
former_member793413
Discoverer
0 Kudos
Hello Olga,

i have this Problem:






SYSTEM_FAILURE: No RFC authorization for function module SCI_REMOTE_SYNTAX_CHECK.

 

Regards,

Adnan U
schneidermic0
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Adnan,

most probably you are using ATC Check "Syntax Check in Remote System". In this case, you have to add the authorization S_RFC for function module SCI_REMOTE_SYNTAX_CHECK to the role of your RFC-user in the checked system.

Regards,
Michael
former_member793413
Discoverer
0 Kudos
Hi Michael,

 

Thank you it worked

 

Regards (Viele Grüße 🙂 )

Adnan
vonglan
Active Participant
0 Kudos
Hi Olga,

I want to avoid opening a ticket, but instead give the feedback here:

the current version of the "collective note" 2364916

mentions the "evergreen" note 2527903 as if it was only required for certain SPs.

This is misleading.

Best regards,

Edo
niba1
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hello Edo,

thanks for the information, we will check the note and bring it up to date.

Best regards,
Nils
0 Kudos
olga.dolinskaja

 

This is really a great article.  I'm just curios, shouldn't you mention note 2695129 to remote enable some of these ATC checks ?

 

  • "Table Attributes Check", technical name: CL_CI_TEST_DDIC_TABLES

  • "Nested Sequential Accesses to Internal Tables", technical name: CL_CI_TEST_SEQ_ACC_ITAB_NESTED

  • "Copy current table row for LOOP AT ...", technical name: CL_CI_TEST_LOOP_AT


Also, the help documentation still incorrectly states that you need to use Code Inspector instead of ATC in the older systems:

ABAP Test Cockpit and Code Inspector in Context of HANA Migration - SAP Help Portal

 

These two tools are available for executing static checks:




  • ABAP Test Cockpit (ATC) - in the case of systems SAP EhP2 and upwards for SAP NetWeaver 7.0 SP 12.

  • Code Inspector - in the case of older systems (< SAP EhP2 for SAP NetWeaver 7.0, SP 12), static checks must be performed using the Code Inspector instead


Can someone correct that?
OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
Hi Panaya,

the note 2695129 is already listed in the collective note 2364916. Regarding the documentation of SAP NetWeaver 7.40: the statements about the usage of ABAP Test Cockpit and Code Inspector are correct, what are you missing there?

Kind Regards,

Olga.
0 Kudos
Hi Olga,

Thank you for pointing out the note, you are correct.

In the context of "Hana migration" for inspections specifically related to functional_db_addition and performance_db, using remote static checks on the older NW systems, as described here:

https://help.sap.com/viewer/a24970c68fcf4770a64bf9a78e3719e2/7.4.23/en-US/550a16acb2de445a85e96b5406...

Couldn't we essentially just use the ATC (instead of the SCI) to run the above mentioned inspections using remote checks?
OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
Hi Panaya,

yes you can use remote ATC to execute functional_db_addition and performance_db check variants, they are remote-enabled. But you would need then the ATC central check system based on SAP_BASIS >=7.52 release.

Kind Regards,

Olga.
chanchaitomas
Explorer
0 Kudos
Hello Olga,

First of all thank you for your time, excellent articles and blogs. We have an issue with when we try to implement de SAP Note 2822096 (referenced by SAP note 2270689 - Remote Analysis (for source system)).

Based on our version of SAP (on source system) we need to implement this instructions:

Release 7.31: 2910608 , 2822096 Remote Analysis (for source system, Release 7.31). If Note 2011106 or Note 2270689 are implemented, please de-implement these notes in the order: 2270689, 2011106.

After successfully implementation of note 2910608, we try to implement note 2822096 and the following errors appears:

 

Program CL_ABAP_COMP_PROCS_E==========CP, Include CL_ABAP_COMP_PROCS_E==========CCIMP: Syntax error in line 000007

Ya existe una clase con el nombre 'LCX_EXCEPTION''LCX_EXCEPTION'.


class_already_exist


 

In tx. SE80 we searching the Class CL_ABAP_COMP_PROCS_E to confirm the duplication:

 


LCX_EXCEPTION_duplicated


 

We compare the same Class in our Central Check System (S/4HANA) and as we can see, no duplicate found


LCX_EXCEPTION_S4HANA_central_Check_System


How solve this error?

As this is ABAP code from a SAP note 2822096, we don't dare to touch this code...

Could your please help us?

 
chanchaitomas
Explorer
0 Kudos
Hello again,

 

Can you help me with this problem? It seems to be an error in the note code itself.

 

Best Regards.
OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
Hi Chanchai,

please open a ticket to SAP regarding this issue.

Kind Regards,

Olga.
percy_686
Explorer
0 Kudos

Hello Experts,




Could you please help to understand difference between, Performance Checks-> Search problematic SELECT * statements and Intern. Tests-> Search problematic SELECT * statements (Diagnosis) ?


How to decide which should be active or both are recommended in ATC ?

OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Prasanna,

please don't use Intern. Tests->.. checks, they are for SAP internal test purposes.

Kind Regards,

Olga.
percy_686
Explorer
0 Kudos
Hello Olga,

Thank you for quick reply. 🙂

Regards,
Prasanna
KavitaMane
Participant
0 Kudos
Hi Olga,

We have successfully setup Central ATC system and able to schedule ATC runs for the Development system. We are having one challenge while we baseline the legacy code, the central result does not show what code has been changed recently and who has changed it. It shows everything with one ID who originally created the Object.

Is there any way we can work this out ? Would you be able to assist.

 

Thanks and Regards

Kavita
OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Kavita,

under the "Change Layout" button of the table with the ATC result you can choose the columns, which you want to display.

Kind Regards,

Olga.
KavitaMane
Participant
0 Kudos
Hello Olga,

Thanks for your response. The change Layout show us who has created the series and all the below details. I was checking if we could know contact person who last made changes on the program. Now when we are running ATC, its giving the results with contact person as who has intially created the program and recent changes are not getting mapped to new developer.

Central
Is in Baseline
Run Series
Check Run Title
Priority 1
Priority 2
Priority 3
Failures Occurred During Check Run
Created By
Created On
SAP System ID
Expires On
Object Provider
Active

 
OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Kavita,

you need to display the ATC findings of the ATC result which is in baseline, then you can select also other columns in the layout like "Last Changed By".

Kind Regards,

Olga.
KavitaMane
Participant
0 Kudos

Hi Olga,

In the baselined code as well, Objects are tagged to old ids who has created the Object. We are not able to see who has recently changed the code.

 

OlgaDolinskaja
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Kavita,

I proposed you to change display layout. Just choose "Change Layout menu"


 

 

 

 

 

 

 

and add "Last Changed By" column (or other columns, which you need) to the displayed column set:


Kind Regards,

Olga.
Labels in this area