There are multiple ways to download & install SAP notes in the SAP systems.
- Download using Note Assistant (SNOTE) using note browser.
- Download notes from SAP ONE Support Launchpad & upload them manually using SNOTE.
However SAP has made mandatory to enable SNOTE for TCI & Digitally Signed SAP Notes.
Why It is necessary?
These digitally signed SNOTES have high security features due to increased authenticity.
This feature is available for both uploading & downloading SNOTES in ABAP based systems.
As per the latest information published by SAP, customers need to enable their ABAP systems to work with digital NOTES by 8 January 2020.
Post this date, download and upload process will stop working.
Steps to enable SNOTE for TCI & digitally signed SAP notes in ABAP based systems
SAP recommends implementing note:
2836302 – Automated guided steps for enabling Note Assistant for TCI and Digitally Signed SAP Notes instead of opting for individual approach.
In case we prefer individual approach, below are the steps:
- Implement notes 2408073, 2546220 and 2508268.
- If Note assistant of system is enabled for TCI , implement 2576306 instead of applying above 3 notes.
- Based upon your SAP_BASIS release, there are certain prerequisites:
| SAP_BASIS release | Actions |
| Below 700 | SAPOSS/SAPNOTE will not work, manually need to install notes as .txt |
| 700 to 731 | SAPOSS/SAPNOTE will work only with Recommended S-user, also called as Technical Communication user |
| 740 & above | Enable HTTP protocol or use download service. |
We will prefer automated approach in this article considering our system is on SAP_BASIS: 740
As per the note, execute report RCWB_TCI_DIGITSIGN_AUTOMATION.
T-code: SE38–>RCWB_TCI_DIGITSIGN_AUTOMATION –> execute.
We need to complete all the automated tasks:
We need to select HTTP protocol for SAP_BASIS: 740 and above.
After completing all the steps, we’ll get below screen:
Install the certificates using STRUST
Execute the task: SAP_BASIS_CONFIG_OSS_COMM via STC01
If all tasks are completed successfully, check the RFC connection test:
NOTE:
Kindly consider the manual pre-steps before implementing the notes or else the functionality won’t be activated successfully.
In case you need any assistance, you may connect with the ABAP team.
For e.g. We missed below manual actions. As a result functionality didn’t activated properly.
The following manual activities are required before implementing the note:
Create the structure SCWB_S_NO_PATCHLEVEL in SCWN package
o Go to transaction SE11 and select the radio button data type enter the name
structure name as SCWB_S_NO_PATCHLEVEL and click on create.
o Select the radio button “structure” from the pop up “Create Type” and click on Ok button.
o Enter the short description Non-ABAP Patch Level by Note
o Enter the below component (fields of structure) and save.
Component Typing Method Component Type Data Type Length
NUMM TYPE CWBNTNUMM
CVNR TYPE CHAR 20
PATNAME TYPE CHAR 30
PATLEVEL TYPE NUMC 6
PAKKTXT TYPE CHAR 30
ALETXT TYPE CHAR 20
RTENVSC TYPE CHAR 10
PATLEV TYPE CHAR 6
SOURCE TYPE CHAR 20
o Go to Extras and choose enhancement category as can be enhanced.
o Activate the structure.
o
o Create the table type SCWB_T_NO_PATCHLEVEL in SCWN package as below.
o Go to SE11 select data type radio button, enter the name as
SCWB_T_NO_PATCHLEVEL and click on create. Select the table type from the popup
o Select line type tab enter the line type as “SCWB_S_NO_PATCHLEVEL” then save and activate.
*Always refer Latest SAP Notes as SAP update them periodically.