Custom code analysis for SAP S/4HANA with SAP Fiori App Custom Code Migration

[OlgaDolinskaja]

Maybe you already know, that ABAP Test Cockpit offers the option of executing the checks remotely on any ABAP system (SAP_BASIS >= 7.00). Using remote ABAP Test Cockpit infrastructure SAP customers and partners can analyze custom code in older systems using the latest ABAP Test Cockpit checks and only one central system for ABAP Test Cockpit (see blog series about Remote Code Analysis in ATC).

With SAP S/4HANA 1809, we offer the SAP Fiori Custom Code Migration App based on this remote ABAP Test Cockpit infrastructure. The App should be used for custom code analysis for SAP S/4HANA in the context of  SAP S/4HANA conversion (see also  SAP S/4HANA System Conversion – Custom code adaptation process).

NEW: Starting with the SAP Cloud Platform ABAP Environment 1908 (now named SAP Business Technology Platform (BTP) ABAP Environment) you can use SAP Fiori App Custom Code Migration in the Cloud to analyze custom code in your on-premise SAP system for SAP S/4HANA readiness. See also the blog ABAP custom code analysis using SAP Business Technology Platform.

The App performs SAP S/4HANA checks on your custom code, which needs to be migrated from your SAP Business Suite System to SAP S/4HANA and provides the analytical presentation of the ABAP Test Cockpit check results with comprehensive filtering and navigation capabilities. Beyond this the App identifies the unused custom code based on your collected usage data, and this enables you to remove it automatically during a system conversion to SAP S/4HANA.

Technical Setup

There are two options to setup the custom code analysis with SAP Fiori App Custom Code Migration:

1) Use SAP Fiori App Custom Code Migration in SAP Business Technology Platform

For technical setup instructions for using the SAP Fiori App Custom Code Migration in SAP Business Technology Platform please refer to the blog ABAP custom code analysis using SAP Business Technology Platform.

The SAP Fiori App Custom Code Migration will run in SAP SAP Business Technology Platform (BTP) ABAP Environment - formerly known as SAP Cloud Platform ABAP Environment - and will check custom code in your on-premise SAP system using the remote ATC infrastructure with RFC through SAP Cloud Connector:

The SAP Discovery Center Mission Use SAP Fiori Custom Code Migration App to Analyze Your ABAP Custom Code for SAP S/4HANA Readiness enables you to setup Custom Code Migration app in SAP BTP ABAP Environment easily using automated capabilities with CIAS (Cloud Integration Automation Service) guided workflow and execute step-by-step guided custom code analysis in your on-premise SAP ERP system.

2) Use SAP Fiori App Custom Code Migration on-premise

You need an SAP S/4HANA >=1809 system set up as a central ATC check system. Our recommendation is to use your SAP S/4HANA sandbox system. See also Remote Code Analysis in ATC – Technical Setup step by step for setup guidance.

You need also to setup and configure the SAP Fiori App Custom Code Migration on this SAP S/4HANA 1809 system. Use SAP documentation on SAP Help Portal for specific implementation and configuration information on SAP Fiori App Custom Code Migration. The SAP Note 2436688 provides all required SAP Notes for the SAP Fiori App Custom Code Migration.

The SAP Fiori App Custom Code Migration will check custom code in your SAP backend system using the remote ATC infrastructure:

Create your Custom Code Migration Project

Start Custom Code Migration App on your SAP Fiori Launchpad. You can maintain multiple custom code migration projects in the App:

  => 

Create your Custom Code Migration Project by pressing “+” (Create Object) button and entering your project data: Project Description, Target Release for your SAP S/4HANA System and RFC Destination to your SAP ERP system:

Add usage data to your Custom Code Migration Project

Now you can add usage data collected either by the ABAP Call Monitor (SCMON) and aggregated by the SUSG transaction or add usage data collected in your SAP Solution Manager system (SAP Solution Manager 7.2 SP8 is the prerequisite).

NOTE: You should collect usage data of your business processes at least for one year in order to get really reliable results for not productively used code.

For information about how to collect usage data and aggregate it in your ERP production system see the blogs: ABAP Call Monitor (SCMON) – Analyze usage of your code and Aggregate usage data in your production system with SUSG transaction.

If you collected usage data in your ERP production system, use there the SUSG transaction to create a snapshot of the usage data. Afterwards download the snapshot and upload it using the SUSG in your checked system. The App will access your checked system (and snapshot with usage data) via RFC:


You can add usage data to your Custom Code Migration Project by pressing “+” (Add) button and using F4 Help in the Usage Description field. Save your project by pressing the "Save" button.



NOTE: If you collected usage data in the SAP Solution Manager, then the App detects whether it is a SAP Solution Manager system behind the RFC destination for the usage data. Then the existing SAP Solution Manager usage data records are displayed in the selection dialog. See the blog How to upload usage data from the SAP Solution Manager to the SAP Fiori App Custom Code Migration.

Define the scope of your Custom Code Migration Project

Now you can define (based on usage data) which ABAP custom code needs to be taken over to your SAP S/4HANA system. The App will create a deletion transport in order to enable deletion of unused ABAP custom code during the system conversion to SAP S/4HANA.

Navigate to the Scope overview. You will see the graphical presentation of the detailed scope information. When you add usage data to your custom code migration project, a default scope is calculated. The default scope includes all used objects, all objects which are statically referenced by the used objects, and objects for which no usage data is available such as database tables or data elements.

Generally the following scope information categories are possible:

In scope (by object) – objects, for which usage data do not exist, for example DDIC objects like Data Elements. Such objects are always automatically in the scope.
In scope (by usage) – objects, for which usage data exist. These objects are used and therefore they are in the scope.
In scope (by reference) – objects, which are statically referenced by the objects in the scope. Such objects cannot be removed from the scope as this would lead to syntax errors.
In scope (by user selection) – objects, which were added to the scope by the user.
In scope (by package) - objects which were added to the scope by adding the corresponding package to the scope.
Not in scope – objects , which are not used (not listed in the usage data) and not statically referenced by the objects in the scope.
Not in scope (by user selection) – objects, which were removed from the scope by the user.


If you included usage data into your Custom Code Migration Project, you can click on the Scope Request Entry Points. There you will get (based on the usage data) a list of the executed request entry points (such as a specific transaction, RFC call, URL request, or ABAP report) along with all ABAP procedures that have been executed under these entry points, and you can decide, which objects you want to remove (Remove from scope) (for example based on the last usage date).



In case you want to adjust the scope manually, the App offers the possibility to add/remove packages or single objects to/from the scope (click “Scope Packages” button). This can be useful to include new developments that are not yet productively used or exclude some developments that you will not need in your new SAP S/4HANA system.

When defining the scope, you can also display the complexity of your custom code in a graphic (click Scope Packages and then go to the Packages tab):

It summarizes the number of relevant changes in accordance with the complexity of the custom code on package level (or request entry point level of the ABAP Call Monitor (SCMON) if you go to the Entry Points tab).The upper right part of the diagram represents the most complex and most frequently changed development packages. They should be removed from the scope for SAP S/4HANA migration, since they cause high TCO. SAP recommends to review these custom code developments to reconfirm the need of this functionality with the business, and reevaluate if meanwhile the same can be achieved by using SAP standard, or with in-app extensibility, or if it qualifies for a side-by-side extension on SAP BTP. 

After you defined the scope of your Custom Code Migration Project, you can create a transport request in your ERP system, which contains all information about your unused custom code (all objects that are not in scope). To do so go to the Project tab and click Save Scope as Transport Request:


NOTE: in the newer versions of the Custom Code Migration App the button is called "Create Deletion Transport".

The transport request gets created and appears under Request/Task of your Custom Code Migration Project:


This transport request can be added to the Software Update Manager (SUM) during the SAP S/4HANA conversion, the unused objects (not in scope) will be deleted by SUM.

NOTE: In case you want to keep a backup of the unused objects we recommend to use gCTS after SAP S/4HANA system conversion to store the objects in the Git repository, see the blog How to backup custom code with gCTS for details. You can also use abapGit (see the Steps 1-3 in the tutorial Use abapGit to Transform ABAP Source Code to the Cloud on sap.com).

Analyze your custom code with SAP S/4HANA checks

As soon as you create your Custom Code Migration Project the SAP S/4HANA custom code checks are executed automatically by ATC, and the App offers you the analytical presentation of SAP S/4HANA custom code check findings.

Go to the Analysis tab and click on the “Analyze Findings” button:



Using the visual filters above you can group your ATC findings to get information on for example:

• What are the most important (urgent) findings (-> filter Findings by Priority)

• How many findings relate to the custom code objects you take over to SAP S/4HANA (-> filter Findings by Scope Information)

• How many findings relate to your custom package XYZ (-> filter Findings by Package)

• In which simplification areas do you get the most findings (->filter Findings by SAP Note Number)

• For which findings there are Quick Fixes available and which findings you need to fix manually (->filter Findings by Quick Fix Availability, currently available with SAP S/4HANA 1809 FPS02)

Download SAP S/4HANA analysis results

Use the Export to Spreadsheet  button in the Findings table to download the analysis results:

Integration with SAP Readiness Check 2.0

You can download the check results with purpose to upload them later on to SAP Readiness Check 2.0.
To do so press Export to Spreadsheet button and select Export for SAP Readiness Check:


See the latest information about SAP Readiness Check 2.0 in the blog SAP Readiness Check for SAP S/4HANA – What’s New in November 2020.

Further information

See Documentation on SAP Fiori App Custom Code Migration on SAP Help Portal.

[OlgaDolinskaja]

Hello Bernhard,

yes it is possible. On the tab "Scope" in the app there is a button "Scope Packages". If you click it, you get a list of the packages and will see from "Scope Information" if the package (or some its objects are in/not in scope. By clicking ">" on the package row you will see the list of objects which in/not int scope. You can add objects to scope or remove them from scope in the app.

Best Regards,

Olga.

[striezl]

Thank you Olga, that is very helpful

[satinder_singh]

Olga,

 

I have one more question. I was finally able to setup the CCM App and use it for myself. But when I asked my development lead to check the same, the analysis project that I created does not appear for his login but it appears perfectly for my login. I even tried sharing the link via email from the CCM App, but even that link results in "No Data found". So is there a restriction that the analysis project will be displayed for the owner only ?

[OlgaDolinskaja]

Hi Satinder,

have you assigned the user roles SAP_BASIS_TCR_T and SAP_BC_YCM_APS to your development lead?

You need to assign the respective roles to all users of the app.

Regards,

Olga.

[satinder_singh]

Thanks Olga for the reply. The role was assigned but apparently there was some issue with auth profile generation and after regeneration it started working (auth object S_YCM_APS was assigned to me and him visa different roles). Thanks

[João_Paixão_Sil]

Hello Olga.

Thank you for the blog post, but I'm having some issues with the remote checks.

The project state stays has corrupt:

 

With the error: "Modifications cannot be checked in S4H (see long text) 2":

 

I've found that this is the message SATC_CI_CFG006 and the procedure for the solution is: "Verify the used stub version in the target system (see note )"

 

Is the a way to know what stub should I verify? Which note?

Is the a more detail log I can analyse?

 

Thanks in advance.

 

Regards,

João Paixão Silva

[OlgaDolinskaja]

Hi João,

to be able to get modifications checked your remotely checked system must implement the SAP Notes 2485231, 2270689 and 2451683. See also the blog https://blogs.sap.com/2017/09/18/remote-code-analysis-in-atc-scanning-customer-extensions/

Best regards,

Olga.

[João_Paixão_Sil]

Hello, Olga.

My problem was with the 2270689 note. The system had an obsolete version installed.

The note update solved my problem.

Thank you for your help.

 

Regards,

João Paixão Silva

[ansul_chandra3]

Hello Expert, Anyone can help me to understand if I can use Solution Manager 7.2 SP04 for ATC work before I convert my ECC 6.0 EHP5/Oracle12 to S/4HANA 1909 FP01. Thank in advance!

[OlgaDolinskaja]

Hi Ansul,

you cannot use your SAP Solution Manager 7.2 SP04 system as an ATC central check system because SAP Solution Manager is on SAP NetWeaver 7.4 and a central ATC check system requires at least SAP NetWeaver AS ABAP 7.51-7.52.

Regards,

Olga.

[oscar_zeng88]

Hi Olga,

 

Thanks for your blog,it's helpful.

Now I have a question about remote analysis note.

My ECC system version is ECC6.0 Netweaver 7.00.

Which note below should I use？

2270689 - Remote Analysis (for source system)

2829419 - Remote Analysis (for source system. Release 7.00)

In manual step, it told me to create function group SABP_COMP_PROCS_E in different package.

 

br,

Chen

 

[OlgaDolinskaja]

Hi Chen,

as stated in the collective note 2364916 please implement the 2270689 for the 7.00 release and the 2905901  (see the entry for the 7.00 in the 2270689).

Best regards,

Olga.

[artiushyna]

Hi Olga,

is there any possibility to download the Scope result from Custom Code Migration Application?

I could download result for Analyze findings but I wanted to analyze all objects which are out of scope and are not having issues, but should be excluded from the migration scope (in excel, as not all colleagues can have access to the application).

Thank You!

[OlgaDolinskaja]

Hi Natalia,

unfortunately it is not yet possible. This feature is in our development backlog but it is not yet clear when it will be developed.

Regards,

Olga.

[artiushyna]

Thank you, Olga, for your quick response! We'll wait for the feature! 🙂

[neelsap2]

Hello Olga,

We are on Solution Manager 7.2 SP11. Can we use the SCMON and UPL data from Solman and port it into the App ? Or does it need to be collected from backend system..?

Thanks & Regards,

Neel

[OlgaDolinskaja]

Hi Neel,

yes, you can upload SCMON or UPL data from Solman to the Custom Code Migration app.

Regards,

Olga.

[Muadib]

Good Morning Olga,

 

We are planning a S/4HANA release upgrade from S/4HANA1809 to S/4HANA2020 (NetWeaver 7.55).

SAP recommends to perform a custom code migration for S/4HANA 2020, and I am unclear about the minimum release version of the central ATC system.

According to the guide, the minimum version for ATC check system is S/4HANA1809 : https://help.sap.com/doc/9dcbc5e47ba54a5cbb509afaa49dd5a1/202009.000/en-US/CustomCodeMigration_EndTo...

But then there is a a whole chapter about Using SAP S/4HANA 2020 as Central Check System ?

Do you know which one is it ?

 

Thanks and Regards

 

[OlgaDolinskaja]

Hi Raoul,

S/4HANA 1809 release is the minimum release, where you can use Custom Code Migration app (see page 7 of the guide). Of course any release > 1809 (like 2020 for example) is better, because of more (and improved) features of the Custom Code Migration app. If you have already set up an SAP S/4HANA 2020 sandbox system, this system can also be used for the
custom code analysis. This is what the chapter Using SAP S/4HANA 2020 as Central Check System is about.

Kind Regards,

Olga.

[Private_Member_7726]

Hi, and thanks for writing all the great articles for us!

There might be a small bug in CL_YCM_FULLNAME_PROCESSOR\LCL_FULLNAME_MAPPER->TADIR_ID_FUGR_IC( ) (SAP_BASIS 754 SP 01, with all kinds of relevant Notes implemented), whereby “ordinary” customer includes with namespace are wrongly identified as belonging to nonexistent FUGR and as a result are excluded from scope, even though their main program is in scope:

This specific program looks like this; it’s an ‘Executable program’, but Module Pool includes are affected as well:

*&---------------------------------------------------------------------*

*& Report  /FWW/UI_AKT_INDEX_VALUES

*&---------------------------------------------------------------------*

REPORT /fww/ui_akt_index_values MESSAGE-ID /fww/zidx.

TABLES: sscrfields .

DATA: s_zidxbez     TYPE /fww/zidxbez.



INCLUDE /fww/ui_akt_index_values_cls.

INCLUDE /fww/ui_akt_index_values_sel.



START-OF-SELECTION.

  lcl_main=>get_instance( )->execute(

    EXPORTING

      it_r_bukrs       = s_bukrs[]

      it_r_index       = s_index[]

  ).

I didn’t find anything in OSS yet and fixed it like this:

Also, it would be nice, if:

• the generated SM30 view Maintenance Dialog FUGRs were ‘in scope’ by default, regardless of productive use (used mostly for customizing tables, so will hardly be used productively), ditto for the ‘funky’ 4 per object Change Document Object Includes (CDT, CDV, CDF, CDC), even if they are not referenced in  code;
• one could pick and choose the namespaces to be analysed at the UI… (mainly to exclude /0LOCAL/, but I guess it can also be easily deleted from the table, if one knows where)

Other than that – great stuff

Thank you and best regards,
Jānis

[Private_Member_7726]

Hi Olga,

The deletion Transport Requests, is it possible to get rid of them in a clean way, please..?

It’s  thoroughly distressing seeing it having been automatically ‘exported’ after creation… – not at all what I expected pressing something that says [Save Scope as Transport Request]

Thank you and best regards,
Jānis

[OlgaDolinskaja]

Hi Jānis,

we already renamed the button to "Create deletion transport" in the newer versions of the app (e.g. in SAP S/4HANA 2020 and in the SAP Cloud Platform ABAP Environment).

Thanks & Regards,

Olga.

[Balu483]

hi Olga,

now for an example all this Checking process is happen in central system( assume SandBox system).we are identified the source code scope and created a deletion TR. so now do we need to transport Deletion TR from SandBox system to DEV? and include the same TR in SUM during DEV S/4 HANA Conversion?

Other than Deletion TR any thing else we need to transfer from SandBox system to DEV?

 

Regards,

Balu.

[OlgaDolinskaja]

Hi Balu,

an deletion TR will be created on the ERP system, which you check with the central check system (e.g. sandbox) and not on the sandbox. During conversion of the ERP system to S/4HANA as the SUM asks for custom transports you can add it.

Regards,

Olga.

[former_member691009]

Hello Olga,

great post, thank you an a great feature set regarding the app! I have some questions left, regarding the usage of the app.

For context: We are on S/4HANA 1909 now and unfortunately didn't use the custom code app for scoping and migrating our custom code. We also didn't use similar features like the SOLMAN decomissioning cockpit. We did a Brownfield approach. This obviously resulted in every custom object being ported to the new S4 system.

In the meantime we have now setup a S/4HANA 2020 central ATC hub system and are planing to update it as often as possible to leverage it's features in the future. Can we now still make use of the custom code app features during our next S4 major release upgrade? Especially regarding the scoping feature to reduce our custom code objects during this upgrade?

E. g. if we upgrade from S4 1909 to S4 2020 in the future on the same machine, can we then still phase out unsued code with the app during this process? Is it only possible if the new S4 2020 system is a completly new one with data migration and everything like with the ECC -> S4 conversion and not an "inplace" upgrade? Has the chance to use the apps features indeed passed for us now because the initial S4 conversion is done?

Which options are left for us regarding the usage of the app?

Regarding upgrading the ATC hub system: will baselines and configurations of ATC be kept, if we upgrade the hub from S4 2020 to S4 2021 later this year or do we have to save them manually beforehand?

Thank you very much and best regards

Patrick

[OlgaDolinskaja]

Hi Patrick,

you can also (and it is even recommended to) do custom code scoping (incl. elimination of unused custom code) and analysis between SAP S/4HANA upgrades (e.g. check an SAP S/4HANA 1909 system for S/4HANA 2020 readiness). The baselines and configurations of the central ATC check system will remain after upgrading this hub system.

Best Regards,

Olga.

[pc22]

Hello Olga,

In CCM App under Scope, the ECC Data Dictionary objects such as TABL is considered as 'In Scope (by object)'. If we review and identify some Database Tables are not needed in our new S/4HANA system, can we add such Tables as 'Out of Scope' and capture them under the Deletion Transport option? That I assume will help to avoid the migration and conversion of such Tables that are not needed in S/4HANA system.

In addition to that when we manually tag such Tables as 'Out of Scope', will CCM also add the other dependent objects on the Table (such as Programs/ Classes using the Table) as Out of Scope?

Regards,

Prathap

[former_member691009]

HI Olga,

thanks for your response. This is great news!

I have a folllow-up question one one topic. We have an internal debatte now whether the SOLMAN decomissioning cockpit fulfills the same purpose and provides similarly sufficient features of the app anyway. But in my understanding they are not mutual exclusive or redundant to each other and provide a set of features which can be combined over the system's lifecycle.

As I understand it, the custom code app is best suited for scoping and possibly deleting code via SUM while performing an S4 upgrade and decomissioning cockpit is for deactivating and deleting objects between two upgrades.

Is that correct? Can you please clarify if these two tools are inclusive/exclusive in some way to each other?

Thanks again and best regards

Patrick

[OlgaDolinskaja]

Hi Prathap,

yes, you can take the DDIC tables out of scope and capture them in the deletion transport request. But: the other objects, which access these tables, will not be removed from the scope, since they may be used in other custom code.

Regards,

Olga,

[OlgaDolinskaja]

Hi Patrick,

it depends on the use case.

The SolMan decomissioning cockpit should be used for elimination of unused custom code during normal operation (not at upgrades).

For the SAP S/4HANA conversion or during SAP S/4HANA upgardes use cases the CCM app captures the unused code in the separate transport request, which will be added to the SUM and deleted automatically (you cannot do so with SolMan decomissioning cockpit).

But you are right: the use cases are to some extent identical, meaning, if prior to upgrade you used SolMan decomissioning cockpit and eliminated the unused code from the system beforehand, you wouldn't probably need to capture it in CCM app during upgrade anymore.

Best regards,

Olga.

[acibanik]

Hi Olga,

 

Thank you for the info shared.

We have just executed the ATC run and right now we are analyzing the results provided.

Strangely, on this occasion, the button to download the findings to a spreadsheet is missing:

CCM app

Any hint on what could be wrong?

Thank you!

Alejandro

[OlgaDolinskaja]

Hi Alejandro,

this button is actually the SAP Fiori-feature, meaning independent of the Custom Code Migration app, is should be there. Please open a ticket to SAP if you want to get it investigated.

Kind Regards,

Olga.

[member123]

 

Hi Olga,

Thanks for the wonderful blog and your responses

I wanted to ask you a few questions

1. Can we use our Solman SOLMAN 7.2 SP  12 as a ATC Check system. If not which version of solman can be used as a ATC check central system


2. Is ATC Check central system free of cost as part of SAP Netweaver.(Custom code analysis for SAP S/4HANA with SAP Fiori App Custom Code Migration). We are going to use this central system only for custom code analysis.

Awaiting your response.

Thank you,

Amar

[OlgaDolinskaja]

Hi Amar,

1. You cannot use an SAP Solution Manager system, since it is on SAP NetWeaver 7.4 release and the minimum for an ATC central check system is SAP NetWeaver 7.51


2. You need a valid SAP S/4HANA licence to use Custom Code Migration app. See for more details also the SAP note 2912919 - SAP S/4HANA FOUNDATION 2020: Release Information Note.

Best Regards,

Olga.

[member123]

 

Thanks Olga,

 

Currently we are having an additional sandbox system( ECC 6.0) in our environment. So, Would it be fine if we just convert our POC(Sandbox system into 1909) & then configure it as a ATC Check System. We will not worry about open checks during conversion. We will only use it as a ATC Central Check system and work from there. Cost wise , this looks like a cost effective solution rather than going ahead with a new box for ATC check.

Let me know your opinion on this approach. Appreciate your response.

 

Thanks,

Amar

 

[OlgaDolinskaja]

Hi Amar,

yes, exactly, the newly converted SAP S/4HANA 1909 sandbox is ideal for the central ATC analysis with Custom Code Migration app.

Best Regards,

Olga.

[member123]

Thanks Olga,

 

We will be going ahead with this approach.

1. We can ignore the open checks during migration as we are only going to perform ATC Remote checks & not data checks in this sandbox system once it is converted it to s4 1909 ATC Central system. I guess we can always do a data check as a bonus. Am I right?


2. Since we have already got the s4hana licensing done and we are moving ahead with s4 hana migration, do you think there will be additional costs for a new box( In case we do not pursue sandbox conversion approach). I am quite confused as some say if it is just ATC Central check system, then there will be no additional costs to build a new box. Just wanted some clarity on this front. It will be great if you have some inputs.

[former_member702797]

Hello All,

Can you please let us know if obsolete objects are deleted from system using custom code  migration fiori app.

Another question, If we have a smartform (SSFO)/Function group, then fiori app is capable to provide driver program for smartforms/Function Group.

 

Thanks,

Sampat

[OlgaDolinskaja]

Hello Sampat,

if you create for your not-used (not scoped) objects in the Custom Code Migration app the transport request ("Create deletion transport" button in the Custom Code Migration app) and add later this transport as a custom transport to the SUM during conversion process, then SUM will delete these objects from the system.

Custom Code Migration app also analyzes Smart Forms for SAP S/4HANA. Was it your question?

Regards,

Olga.

[chanchaitomas]

Hello Olga,

 

Firts of all, I want to congrats to you for this incredible post about ATC, for me it has been a great help for understanding the concepts and guide to me for the technical preparation to deploy the ATC.

Unfortunately we are stuck in manually activity required by note 2587593 - ATC: Checkability of Modifications and Enhancements in Remote Checks - Developer Scenario.

The required manual activity says to create the following objects manually:

# Messages:
# MESS SATC_CI_CFG006

We don't quite understand what mean by the manual creation of this MESS object... Do you mean to add directly into a Transport Order? or access to some transaction like SE91 (this is for MASG message class object...)

Could you shed some light on this?

Best Regards,

Chanchai.

[OlgaDolinskaja]

Hello Chanchai,

my understanding is, that you should use the transaction SE91 to create the message object.

Kind Regards,

Olga.

[chanchaitomas]

Hello Olga,

Thanks for your quicky answer. We try to create the message object through transaction SE91 but but as far as I can see, it only allows you to create message class of type MSAG and no MESS object type...

 

Object creation tx. SE91

 

As we can see this is the specification for MESS object.

 

MESS object type

 

Is there a way to add this object manually? I have not seen that since the tx. SE91 can modify this type of object.

Thanks,

Chanchai.

 

[ThFiedler]

Hi,

MSAG is a message class that contains several single message of type MESS.

That means when you add a new message to a message group a transport entry of type MESS is written to the transport task. In your case you have to edit the SAP message class and add the single message as modification.

Regards,

Thomas.

[chanchaitomas]

Hello Thomas,

 

Thanks for the clarification. We have been able to implement the amendment correctly. We would only like to suggest, that if in these manual steps that are required, it's indicated that all this is done from the transaction SE91 and it's necessary to look for the message class SATC_CI_CFG and add in line 006 the required text, it would be very useful and save a lot of headaches for future users.

 

Regards,

Chanchai.

 

[Gilmour213]

Hello Olga,

we are using a Central ATC System with NW AS ABAP 7.52 SP0004. In the past we have connected several other NW Systems to this Central ATC and 1 S/4 HANA System.
Now we want to connect the next S/4 HANA System with S4CORE 105(0002) and SAP_BASIS 7.55(0002). On trying to connect this System we got an Error which says that the Release of the Central ATC System is to low to connect to the S/4 System.
Does this mean that we have to go with our Central ATC System to S/4 HANA too ?

And if so, is there an option for a System Conversion of the existing Central ATC System to S/4 ? We have written a lot of own ATC Checks, which we will surely use again in the new System.
Or do we have to set up the new Central ATC for S/4 HANA manually and what then abou the existing Findings, Baselines etc., ? How do we get those Artefacts into the new System ?

Best regards

Mario

[ThFiedler]

Hi Mario,

yes, you need at least the same release on the ATC system as the release of the checked system. You can do an upgrade of your central ATC system to S/4HANA Foundation. We tested this a few weeks back in our own landscape and it worked perfectly without data lost.

Please keep us posted when you go that step.

Regards,

Thomas.

[BaerbelWinkler]

thomasfiedler

Hi Thomas,

now I'm getting confused! Your statement "You can do an upgrade of your central ATC system to S/4HANA Foundation." seems to contradict with Olga's reply upthread to my question way back in 2019 where she stated that "there is no system conversion path from NW AS ABAP 7.52 to S/4HANA 1809. So you need to setup a new S/4HANA 1809 system as a central ATC check system and migrate your baseline and exemptions data in there."

Has something changed since then and an upgrade from NW AS ABAP 7.52 to an S/4HANA system is now possible? We'd be very interested in such an option as well!

Thanks much and Cheers

Bärbel

[ThFiedler]

Hi Bärbel,

the usage of S/4HANA foundation for ATC is available since 1909. See the remarks in the following note https://launchpad.support.sap.com/#/notes/2750164 .

"SAP S/4HANA customers can use a S/4HANA foundation test system to setup an ABAP Test Cockpit hub for remote checks."

So you can upgrade your NW system to S/4HANA foundation. All ATC settings and all ATC data incl. exemptions survives the upgrade.

Regards,

Thomas.

[christian_takeda]

Hi Olga,

We have a central ATC system to check customers' systems, and we have downloaded the excel sheet with customer's findings, and filtered by object name. We have noticed that several lines are duplicated, some cases even more.

We have also check in the app, doing the same filter and it looks the same. Any thoughts?

 

Thanks

 

Christian

[schneidermic0]

Hi Christian,

It is possible to get the same finding several times per object. In this case, each finding should refer to a different location in the source code.

Did you check whether the findings refer to different source code locations? You can navigate to the source code location of a finding in the app.

Regards,
Michael