​‍​‌‍​‍‌​‍​‌‍​‍‌Connecting SAP Legacy Systems to SAP Support Backbone via HTTPS 2025

Table of Contents

The manner in which SAP systems communicate with SAP Legacy Systems has been completely changed with the update of the SAP Support Backbone. As a matter of fact, all RFC-based connections between customer systems and SAP’s Support Backbone were terminated as of January 8, 2020. What this change implies is that HTTPS is the only protocol that is supported for the connection of SAP systems to backbone services of SAP. 

For those organizations that are still on SAP BASIS 7.00 – 7.31, this manual helps in understanding the reasons behind the change, what services are affected, and the detailed procedures to implement the HTTPS connectivity. 

Connect With Us: WhatsApp

📌 Why Did RFC Shutdown Happen? 

To improve security, scalability, and implementation of modern integration standards, SAP decided to discontinue the use of RFC-based connections. Thus, while you can still use RFC for internal communication within your SAP landscape, support communication with the SAP Support Backbone is to be carried out only through HTTPS. 

🛑 Impacted Services & Timelines 

Around the time of the RFC shutdown, a number of essential SAP services had been deeply affected: 

  • Early Watch Alert (EWA): 

May 29, 2020 – non-HANA systems data via RFC blocked 

July 31, 2020 – All RFC-based EWA data blocked 

  • Service Preparation Check (RTCCTOOL):
    November 30, 2020 – Content loading from services in the legacy BASIS systems (7.00–7.31) via RFC was no longer possible 
  • SAP Notes Download:
    July 31, 2020 – BASIS ≥ 7.40 stopped from RFC downloads
    November 30, 2020 – BASIS 7.00–7.31 stopped from RFC downloads 

👉 To remain capable of downloading SAP Notes, companies need to either activate the HTTP(S) Download Service (SAP Note 2928592) or go for manual downloads (SAP Note 2865380). 

⚙️ Implementation Steps (HTTPS Enablement) 

  1. Ensure HTTPS Service is Active
  • Transaction SMICM → Services View 
  • In case the service is not running, a free port can be set up by RZ10 via parameter configuration: 

 Code: PROT=HTTPS, PORT=<HTTPS_PORT>, TIMEOUT=240, PROCTIMEOUT=<Preferred Value>

  1. Check TLS/SSL Protocol Version
  • Transaction RZ11 → sell/clientciphersuites 
  • Verify that TLS 1.2 is active and is using the values recommended: 
  • 150: PFS: HIGH:EC_P256:EC_HIGH for ABAP systems 
  • 918: HIGH:EC_P256:EC_HIGH for Solution Manager 
  1. Verify SAP CryptolibVersion 
  • Transaction STRUST → Environment → Display SSF Version 
  • The minimum required version is 8.4.48 or above 
  1. Install SSL Certificates
  • Required certificates: 
  • DigiCert Global Root CA 
  • DigiCert Global Root G2 
  • DigiCert High Assurance EV Root CA
     
  • Upload them using STRUST under SSL Client (Standard & Anonymous). 
  1. Create HTTPS Connections (SM59)

Set the destinations for the backbone services as: 

  • SAP-SUPPORT_PARCELBOX (Type G) – Parcel downloads 
  • SAP-SUPPORT_PORTAL (Type H) – Support Portal access 
  • SAP-SUPPORT_NOTE_DOWNLOAD (Type G) – SAP Notes download 

Each of these links has to be tested in order to make sure that the HTTP Response 200 (OK) is received. 

 Key Benefits of HTTPS Connectivity 

  • Security: Encryption will be much stronger if TLS 1.2 is used 
  • Compliance: The connection is in line with the global backbone standards of SAP 
  • Continuity: The users will have uninterrupted access to SAP Notes, EWA, and other backbone services 
  • Futureproofing: It will make legacy systems ready for coming integration with modern SAP landscapes.

SAP Legacy Systems

Connect With Us: WhatsApp

🎯 Final Thoughts 

The changeover from RFC to HTTPS was a big step toward the modernization of SAP. For BASIS administrators, it is very important to enable HTTPS connectivity not only because they are required to do so, but mainly because it is the only way to maintain access to the most essential SAP services such as Early Watch alerts, SAP Notes, and backbone integrations.

By organizations carrying out the steps that have been described turning on HTTPS, allowing TLS 1.2, updating Cryptal, putting in place SSL certificates, and setting up SM59 connections they can be certain that their legacy systems are still able to link up with SAP’s Support Backbone safely. 

At GTR Academy, we provide the means for SAP professionals to acquire the necessary skills with these technical transitions through our practical training sessions, thus enabling them to remain in the forefront of the ever-changing SAP ​‍​‌‍​‍‌​‍​‌‍​‍‌ecosystem. 

Leave a Reply

Your email address will not be published. Required fields are marked *

Contact Now

    All Categories

    Recent Post

    Submit Your Details to
    Get Instant Offer

    Provide your details to receive course information and exclusive

      Download your Brochure

      Fill out the application form and download the brochure for joining our program.


        Graduate































                    https://youtu.be/_KW9ZKQYtNY?si=wrMtMBnFXZk5IJ3c





































































































                                                            UPCOMING BATCHES






                                                              https://youtu.be/IoG1WxAKXwg

                                                              https://www.youtube.com/watch?v=l9XB4Gwt0H4

                                                              https://www.youtube.com/watch?v=71Y_1M0NSoo

                                                              https://www.youtube.com/watch?v=yjGQ1g9S-dU

                                                              https://www.youtube.com/watch?v=Q_BixayJrHk

                                                              https://www.youtube.com/watch?v=LMc1oH5ikpE