SAP's support backbone is the central infrastructure located at SAP to provide technical support to our customers. The support backbone consists of several different systems for different purposes - for example, it provides the SAP Support Portal infrastructure, the Maintenance Planner, SAP EarlyWatch Alert Reports, and many more.
SAP's support backbone has been updated. The legacy infrastructure remains in place to allow a safe transition for customers. Customers need to switch to the new infrastructure before January 2020 to ensure continuous connectivity.
This impacts every ABAP-based SAP system which is connected to the support backbone.
On this page you can find information about the impact of the support backbone update on various scenarios.
You need to switch the communication of SAP Solution Manager and Focused Run to the new infrastructure before January 2020 to ensure continuous connectivity.
On the info page linked below, you will find detailed information about the impacted scenarios in SAP Solution Manager and the required steps to ensure the connectivity of SAP Solution Manager and Focused Run.
SAP Note Assistant (transaction SNOTE) needs to be enabled to handle digitally signed downloads. To achieve this, SAP Note Assistant needs to be updated in every system where it is used.
Remark: The download of SAP Notes with SNOTE is no longer possible after January 1st, 2020 if SNOTE is not updated to handle digitally signed SAP Notes before this date.
To find out more about the required activities, please see the page linked below.
All ABAP-based SAP systems which have direct connectivity to SAP (i.e. sending EWA reports directly to SAP) need to be updated with the latest ST-PI AddOn. You can find the required ST-PI and ST-A/PI versions in the FAQ.
Systems which do not have direct connectivity to SAP (because, for example, EWA reports are sent through SAP Solution Manager) do not need to update ST-PI and ST-A/PI. Nevertheless, SAP generally recommends to keep ST-PI and ST-A/PI updated in the managed systems.
For the new connections, a dedicated user needs to be in place. Connections using generic users will not work anymore after January 1st, 2020. For this purpose, customers need to ensure that all connections use a technical communication user in all systems which have connectivity to SAP (this includes all systems directly sending EWA data to SAP and all systems where SAP Note Assistant is being used on).
A technical communication user is an isolated user used for connectivity purposes only. No logon at any SAP portals is possible with this user. The password of a technical communication user does not expire. Technical communication users can be requested via this app.
You can find more information about technical communication users in the FAQ.
For every affected area, various activities have to be performed (as listed on this page).
To ease the configuration process, common configuration steps are provided as an automated task list for the ABAP task manager. This task list provides the automated creation of the necessary connections to the support backbone. To leverage the automation, please implement SAP Note 2738426.