Note implementation is really helpful to fix issues without having to carry out big system updates and avoid hassles.
However, sometimes we don’t actually need a code solution, but rather only the manual Solution steps provided by a note. A note can deliver the code correction and in the solution section. A configurable parameter, or delivers a report and instructions on how to run it, etc.
To easily identify if the code correction of a note is valid or not for a system
Each code correction note will have one or more Correction Instructions sections with a “Valid for” list. For example note 2068862:
- Check the line “Software component” to know what component the code change belongs to.
In this case, it is SAP_APPL. The system you want to apply the note must have that component.
- Check the Release of the software component on the lines bellow. In this case, releases 600,602,603 etc. If the system you want to apply the note doesn’t match any of the releases listed, then the code correction is not valid for that system.
- Check the text on the right of the release. It will have the id of the support package, in this case, for example “SAPKH60001”. Where:
- “SAPKH” means SAP_APPL
- “600” means the version of the component
- “01” means the support package level.
*Please note: the Support package ID “SAPKH60001” will change according to each component, it could have extra characters on it.
In the “Valid for” region, the text should be interpreted as following:
- “SAPKH60001 – SAPKH60026”: the code correction of that module is valid to be implemented in a system with SAP_APPL version 600 from Support Package 01 to SP 26.
- “To SAPKH60216”: the code correction of that module is valid to be implemented in a system with SAP_APPL version 602 from SP 00 to SP 16.(That means the code correction is included in SP17, so a system in SP17 already have that correction and does not need to implement the code correction)
- “All Support Package Levels”: This means the code correction is valid to be implemented on all Support Packages of a release version. This is usually used in pilot notes.
- “Fm SAPKH60001”: This is the same behavior as “All Support Package Levels”, but from a starting point. In this case, from SAP_APPL version 600 SP01. If the system has any version higher than it, the note should be valid.
Each note can carry several Correction instructions. Each “Correction Inst.” will have the list mentioned above. In some cases, a correction instruction might not be valid for a support package version, but another correction instruction, in the same note, could be. If just one correction instruction is valid, then the note should be valid to be implemented on that system.
Support pacakges that deliver notes
You can also check the “Support Packages & Patches” section of the note. Example of note 2068862:
This section demonstrates on what Support Package the code correction and note implementation is delivered. So if the system is on the version listed or above, then the code correction has already been delivered.
That doesn’t always means the Solution section of the note has been implemented, for example a parameter set up. Therefore you always have to carefully read the Solution section to make sure the solution has been correctly implemented.
Please consider this post just as a quick reference. If you are not sure if the note is valid or not, use transaction SNOTE to download the note and validate if it can or not be implemented on that system.
Please also consider SAP Notes can have versions, it is important to check if the version you have downloaded is the last version of the note.
Thank you for reading my post.
If you have any comments or other tips, please let me know on the comment section bellow.