CHECK_26 is not remote enabled

[fidley]

Check_26 is not remote enabled as it uses DD02L to check if table is standard or not, and this table of course contains different data that on checked system.

My idea is following:

• create a Z- table on central remote system on a basis of DD02L
• create a report to copy data from satellites systems (once a while)
• update the check to use standard DD02L if the system uses local server or to use Z-Table if it uses central system.

What do you think @larshp ?

[larshp]

https://blogs.sap.com/2018/09/06/remote-code-analysis-in-atc-how-to-write-an-atc-check/ describes something that might help solving this.

I think the idea with central ATC breaks when checks get a bit more complicated like above, changes to development objects has to be done in the satellite system anyways, which was the selling point for central ATC? The result is just a more complex landscape with higher TCO?

[fidley]

Central ATC was chosen as we have several systems and few people to handle the ATC story. One config for all of them plus dedicated NW instance for quick updates that doesn't corrupt with the normal business stuff was the key.

I thought about RFC calls using RFC_GET_TABLE_ENTRIES but I'm thinking how this would change the performance.

I'll try with my own created test at first.

[larshp]

Last section "ENSURING REMOTE ABILITY OF YOUR CHECK" of https://www.sap.com/documents/2018/09/905bfdab-1a7d-0010-87a3-c30de2ffd8ff.html is relevant

it seems CL_ABAP_SOURCE_ID=>GET_DESTINATION is not present in 740