Connect ABAP On-Premise to a Central Check System for Custom Code Migration Using ABAP Test Cockpit (ATC)

In your browser, log on to SAP Cloud Connector for your on-premise system. If your on-premise system is SAP AS ABAP Developer Edition, 7.5x, open the browser inside your virtual machine, e.g. VMWare

• Address = e.g. https://localhost:<port> (Default = 8443)

• User = Administrator

• Password = Your password. (Initial password = manage)

  

Your Cloud Connector dashboard should look like this, with:

• At least one Cloud Foundry subaccount connected (1)
• At least one mapping from Cloud to on-premise (2)

Note the Location ID (3) - here, XXX. You will need it later.

Now you will add the resources you need for the CCM app. Resources are, for example, RFCs or BAPIs that the app check needs to call.

1. Download the attachment in SAP Note 2861842, CustomCodeMigration(1).zip. If using to the Linux system where your ABAP server is located.

   

2. Choose Cloud to On-Premise on the left, then choose Import System Mappings….

   

3. Navigate to the .zip file you downloaded, then choose Import.

   

4. The resources are downloaded:

1. Import the following SAP Notes (download, then upload):

   • 2599695 Custom Code Migration Fiori App: Remote Stubs for the Checked System
   • 2888880 Remote analysis: Bulk determination of method names
   • 2820446 Remote Analysis for source system, Release 7.52, i.e. run the report RS_ABAP_INIT_ANALYSIS

2. Implement SAP Notes.

Also, see SAP Note 2270689 Remote Analysis for source system for reference but do not implement it.

1. In the SAP BTP Cockpit of your Cloud Foundry subaccount, choose Cloud Connectors.

   

   The location ID points to the correct SAP Cloud Connector (located in the on-Premise system); The virtual host points to the on-Premise connection mapped in SAP Cloud Connector.

2. Still in the Cockpit, choose Destinations, then choose the destination you created previously, such as NPL_###.

   

3. Check the following:

   • Destination Name = here, NPL_###

   • jco.client.ashost = here, nplhost

   • Location ID = here, XXX

     

4. Check the connection by choosing Check Connection. You should get a message like this:

   

1. In our browser, open the SAP Fiori launchpad (“or dashboard”) for your SAP BTP, ABAP Environment instance. To find the URL for this, from the subaccount overview, choose the relevant space, e.g. Dev, then choose Service Instances > ABAP System > Your System > View Dashboard. Log on.

   

   .

   

2. Choose Communication Management > Communication Systems, then choose New.

   

3. Enter a System ID, e.g. NPL_ATC_###. The application automatically provides an identically-named system name. Accept this.

4. Switch Destination Service to ON.

   

5. Choose Use Default Instance, then choose the name of your destination service, NPL_###, from the drop-down list.

   

6. Save your changes.

1. In SAP Fiori launchpad, open the Fiori app Communication Arrangement and choose New.

2. Enter the following, then choose Create:

   • Communication Scenario SAP_COM_0464 - Choose from the dropdown list. If this communication scenario does not appear, then you are missing the correct authorizations and cannot complete this tutorial

   • Arrangement Name - Overwrite the default (identically-named), e.g. with SAP_COM_0464_### or SAP_COM_0464_SID.

     

3. Choose your communication system from the dropdown list, SAP_COM_0464_###.

4. Save your changes.

   

1. Choose Identity and Access Management > Maintain Business Roles.
2. Choose BR_IT_PROJECT_MANAGER > Edit.
3. In Assigned Business Catalogs, choose Add > SAP_CORE_BC_CCM > Apply > OK. The tile should appear in the Launchpad:

1. Choose Go.
2. Choose Create to create new project.
   • Target release = SAP BTP, ABAP Environment
   • Destination = SAP_COM_0464_NPL_###
   • Transition Scenario = New implementation

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