--- parser: v2 auto_validation: true time: 60 tags: [ tutorial>intermediate, software-product>sap-btp--abap-environment, software-product>sap-business-technology-platform, tutorial>license] primary_tag: programming-tool>abap-development author_name: Julie Plummer author_profile: https://github.com/julieplummer20 slug: abap-environment-atc-run canonical_url: https://developers.sap.com/tutorials/abap-environment-atc-run --- # Connect ABAP On-Premise to a Central Check System for Custom Code Migration Using ABAP Test Cockpit (ATC) Connect an ABAP On-Premise System to a SAP Business Technology Platform (BTP), ABAP Environment containing the Custom Code Migration (CCM) App, ABAP Test Cockpit (ATC) ## Prerequisites - **IMPORTANT**: This tutorial cannot be completed on a trial account (due to connectivity requirements) - **Tutorial**: [Call a Remote Function Module From SAP Business Technology Platform, ABAP Environment](abap-env-rfc), prerequisites plus steps 1-2, then steps 4-5. (You can test connectivity by performing steps 6-12) - In SAP Cloud Platform, ABAP environment, you have been assigned the role **`SAP_CORE_BC_CCM`**. This role allows you to connect your SAP Cloud and on-premise instances using communication objects For more information, see Tutorial [Create Communication System to Connect to SAP BTP, ABAP Environment](abap-environment-s4hanacloud), step 2 - In your on-premise system, you have installed the following: - SAP Cloud Connector with Administrator rights. (In the systems listed in the above tutorial, this is pre-installed) - Java 8. Uninstall other versions of Java, e.g. Java 11 ## You will learn - How to connect your on-premise AS ABAP to a service in SAP BTP, ABAP Environment - specifically, the Custom Code Migration App. This app allows you to see whether your custom ABAP development objects are cloud-ready, or ready for SAP S/4HANA, and what exact changes you have to make ## Intro After you set up the connections, your landscape will look roughly like this: ![overview-atc-2024](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/overview-atc-2024.png) Throughout this tutorial, replace the suffix `_000` or `_###` with your initials or group number. --- ### Open SAP Cloud Connector 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:` (Default = 8443) - User = Administrator - Password = Your password. (Initial password = manage) ![step1a-cloud-conn-login](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/step1a-cloud-conn-login.png) 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. ![step1b-scc-cloud-onp](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/step1b-scc-cloud-onp.png) ### Add resources for Custom Code Migration (CCM) App 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](https://launchpad.support.sap.com/#/notes/2861842), `CustomCodeMigration(1).zip`. If using to the Linux system where your ABAP server is located. ![step2b-download-attachment](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/step2b-download-attachment.png) 2. Choose **Cloud to On-Premise** on the left, then choose **Import System Mappings...**. ![step2a-import-system-mappings](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/step2a-import-system-mappings.png) 3. Navigate to the `.zip` file you downloaded, then choose **Import**. ![step2c-browse-for-resource-file](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/step2c-browse-for-resource-file.png) 4. The resources are downloaded: ![step2c-resources-downloaded](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/step2c-resources-downloaded.png) ### Import SAP Notes 1. Import the following SAP Notes (download, then upload): - [2599695 Custom Code Migration Fiori App: Remote Stubs for the Checked System](https://launchpad.support.sap.com/#/notes/2599695) - [2888880 Remote analysis: Bulk determination of method names](https://launchpad.support.sap.com/#/notes/2888880) - [2820446 Remote Analysis for source system, Release 7.52](https://launchpad.support.sap.com/#/notes/2820446), i.e. run the report **`RS_ABAP_INIT_ANALYSIS`** 2. Implement SAP Notes. Also, see SAP Note [2270689 Remote Analysis for source system](https://launchpad.support.sap.com/#/notes/2270689) for reference but do not implement it. ### Check connectivity in SAP BTP cockpit 1. In the SAP BTP Cockpit of your Cloud Foundry subaccount, choose **Cloud Connectors**. ![step4a-cf-cloud-connectors-in-sap-cloud-cockpit](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/step4a-cf-cloud-connectors-in-sap-cloud-cockpit.png) > 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_###`**. ![step4b-cf-destinations-in-sap-cloud-cockpit](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/step4b-cf-destinations-in-sap-cloud-cockpit.png) 3. Check the following: - Destination Name = here, **`NPL_###`** - `jco.client.ashost` = here, **`nplhost`** - Location ID = here, **`XXX`** ![step5b-cf-destination-created](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/step5b-cf-destination-created.png) 4. Check the connection by choosing **Check Connection**. You should get a message like this: ![step4b-cf-connection-successful](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/step4b-cf-connection-successful.png) ### Create communication system for Custom Code Migration 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. ![step5b-choose-dev-space](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/step5b-choose-dev-space.png) . ![step5a-view-dashboard](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/step5a-view-dashboard.png) 2. Choose **Communication Management > Communication Systems**, then choose **New**. ![step5c-comm-system-new](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/step5c-comm-system-new.png) 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**. ![step5d-destination-service-on](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/step5d-destination-service-on.png) 5. Choose **Use Default Instance**, then choose the name of your destination service, **`NPL_###`**, from the drop-down list. ![step5e-destination-dropdown](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/step5e-destination-dropdown.png) 6. Save your changes. ### Create communication arrangement for Custom Code Migration 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`**. ![step6a-choose-comm-scen-0464](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/step6a-choose-comm-scen-0464.png) 3. Choose your communication system from the dropdown list, **`SAP_COM_0464_###`**. 4. Save your changes. ![step6a-comm-arr-0464](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/step6a-comm-arr-0464.png) ### Assign business role for Custom Code Migration App 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: ![step7d-atc-tile](https://raw.githubusercontent.com/sap-tutorials/abap-core-development/main/tutorials/abap-environment-atc-run/step7d-atc-tile.png) ### Run Custom Code Migration App 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 ### Test yourself ### More Information [Custom code analysis for SAP S/4HANA with SAP Fiori App Custom Code Migration](https://blogs.sap.com/2019/02/27/custom-code-analysis-for-sap-s4hana-with-sap-fiori-app-custom-code-migration/) ---