Following SAP's Support Backbone Switch-over on 8 January 2020 10:00 MET you are experiencing problems in applications that rely on functioning connectivity between your on-premise SAP systems and SAP's Support Backbone.
Areas typically affected would be
- a number of SAP Solution Manager applications (more details below),
- non-SAP-Solution-Manager ABAP systems directly connected to SAP for the purposes of Notes Download or exchange of EarlyWatch Alert (EWA) and other SAP services (GoingLive etc) data,
- Support Technology Cloud Solution (STCS) applications, for example in the area of EarlyWatch Alert (EWA) Workspace.
One of the main features of SAP's Support Backbone Update is the near-complete decommissioning of legacy RFC connectivity technology in favor of HTTPS connections. Hence, problems related to lost RFC connections between your systems and SAP can also be symptomatic of Support Backbone Switch-over troubles: well-known RFC connections such as SAP-OSS, SAP-OSS-LIST-O01, SAPNET_RTCC, SDCC_OSS etc will no longer work and you will also not be able to repair them; only SAPOSS will continue to function for a few months after January 2020, if and only if you have fitted SAPOSS with a technical communication user, and if the system connecting to SAP through SAPOSS had already been participating in the EWA service before 8 January (this holds for both SAP Solution Manager systems and non-SAP-Solution-Manager ABAP systems sending EWA data directly to SAP).
on-premise SAP Solution Manager 7.1, on-premise SAP Solution Manager 7.2, non-SAP-Solution-Manager ABAP systems directly connected to SAP, Support Technology Cloud Solutions
OSS Shutdown, Support Backbone Update, SAPOSS access denied , KBA , XX-SER-BB-UPD , SAP Backbone Update , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.