SAP has announced an update on its support backbone to go live per 1.1.2020. If you did not prepare your systems for it, you might loose support functions.
Even recently you might see this big warning on SAP support site:
Questions that will be answered in this blog are:
- Where can I find more background information on the SAP support backbone update?
- Do I need to upgrade SAP solution manager?
- How to switch to digitally signed OSS notes?
- Do I need to change my OSS RFC’s?
- What else do I need to do?
- How to check the correct setup in the SAP EWA report?
- Where can I find a checklist to see if I am completely done?
Background information on SAP support backbone update
The landing page for SAP support backbone update can be found by following this link.
The webinar recording explaining all the highlights can be found by following this link.
What will change per 1.1.2020?
Basically the connection from SAP solution manager and the on premise SAP systems connection to the SAP backbone will change. This will impact many areas like OSS notes, EWA’s, landscape planning etc.
What do you need to do if you don’t want to loose any functionality?
If you don’t want to loose any functionality in SAP solution manager you will need to upgrade to Solution manager 7.2 to support package 7 or 8. If you are on 8 you have to do less manual work than on 7. On solution manager support packs 5 and 6 some functions will work, but with manual work and limitations. On solution manager 7.1 and solution manager 7.2 up to support pack 3, the connection to SAP support backbone will be lost on 1.1.2020. You can already upgrade to SP8 now and prepare solution manager.
For the automatic configuration of the connectivity follow the instructions in OSS note 2738426 – Automated Configuration of new Support Backbone Communication.
For OSS notes there are 2 changes: the RFC to SAP and digitally signed OSS notes.
OSS notes via SNOTE must be switched to digitally signed OSS notes. How to do this: see blog.
Next to this, you will need to change the OSS note RFC destination. The generic user will no longer work. You will need to change it to named technical user, or change to the connection from RFC to https connectivity.
If you setup digitally signed OSS notes there is an option for fallback to insecure.
Attention: this fallback will no longer work after 1.1.2020.
ANST is a great function to help you find OSS notes relevant for your issue. For more explanation on ANST look at this blog. The ANST reaches out to the SAP support backbone to check for recent notes. To keep the function working you need to setup a new webservice in SOAMANAGER (if the SOAP runtime is not active follow instructions in this blog). To setup the specific webservice follow the instructions in oss note 2730525 – Consuming the Note Search Webservice. Then apply OSS note 2732094 – ANST- Implementing SOAP Based ANST Note Search.
While switching to new SAP support backbone you might get a connection error. Follow the instructions from OSS note 2781045 – ANST / ST22 note search “Connection cannot be established” to solve it.
SAP has now published online checklists, based on your solution manager version. You can find the checklists on this link.
Support backbone configuration check in EWA report
If you install ST-A/PI 01T sp02 or higher in your system (see OSS note 2827332 – Service Data not Complete due to ST-A/PI not Up-to-date), the EWA report of that system will give information about the correct connection to SAP support backbone and correct use of technical user for the communication.
In the process OSS note 2802999 - SDCCN activation fails without errors or red icons in Migrate tab might need to be applied as well to solve an SDCCN error.