Solution

This outlines and then details out the solution approach. For a note that can be
applied, this is a list of codes that need to be updated followed by the code that has
to be added/deleted/changed.
Valid Releases
This is very critical. SAP clearly mentions the component version for which the note
is applicable. The reason – SAP will fix known issues in future release and hence the
issue described will only be observed in specified versions or earlier versions. More
often, consultants end up digging up notes that are irrelevant because the notes are
for older versions. This takes the issue off the focus as we tend to assume it is SAP
Code issue than to look for real cause. Hence this has to be carefully checked before
working on the note details.
a. e.g.:

Implementing Notes
In simple terms, SAP notes are correction instructions from SAP for known issues in
SAP system. The corrections can be mainly categorized into two categories –
Implementable and Non-Implementable. A note’s header section clearly mentions
out if the note can be implemented or not.

If it is an implementable note, first, go to transaction SNOTE.

A. To download a note, go to menu option Go To à Download SAP Note.

Enter the note number and execute to download.

It is easy to notice various icons next to note numbers. They visually indicate
implementation status for each note. The grey diamond indicates that note cannot
be implemented. A play button indicates note can be implemented.
Notes that can be implemented, the best way to implement is thru SNOTE.

Thru SNOTE, we can check the implementation status of each SAP note. If the note
says ‘Can be implemented’, then after ensuring that the note is required and can fix
the issue, click execute button on top. System applies the note and updates the
status whether the note was successfully implemented or not.
The code correction technical details can be obtained from the info tree on left.
Select folder ‘Corrections’ and expand it. It lists the code corrections that will be
done to fix the issue. Each correction mentions a code section from system followed
by code changes in terms of insertion of code, commenting (deleting) the code or
both.
Some notes need manual intervention and the note mentions how it has to be done
– step by step. For e.g. if system requires to add a new data element or some entry
in data dictionary followed by code changes then the note explains the same.
Note: When code changes are to be done manually, an access key is required to
make changes to SAP code. This needs help from BASIS team as the object ID for
the code being altered (e.g. include name) needs to be updated in SAP service place
and then the key is generated. This key has to be entered in order to edit SAP code.
The purpose of doing this – each SAP installation is registered with SAP and
hence SAP keeps track of which SAP code was altered and this comes handy during
an upgrade or during a support request to SAP.
IMPORTANT: Since these are SAP code corrections, Transport Request will
be requested while system applies the code changes. Be prepared to
create/provide TRs – mostly workbench requests.
Uninstalling a Note
When a note is applied thru SNOTE by clicking execute, system allows to uninstall it
as well. Technically it revert the code to original state. To uninstall a note, select
‘Reset SAP Implementation Note’ from menu as shown below.
This doesn’t apply if codes are changed manually by a developer and hence it is
advised to keep a copy of code being altered either in system or as document in a
safe place. Reverting note changes in this case is to again edit the code and put
back old version, preferable from a system where the code is not altered or from a
backup system.
Troubleshooting
Things can go wrong when implementing SAP Note. There are many ways to trouble
shoot. Please note that the best way is to uninstall, if allowed, and apply again.
Other way is to perform a code comparison and see which sections of the code were
changed. Now pull up the advised code changes from SAP Note – corrections folder
and see what’s gone wrong and apply the changes manually.
Best practices while implementing an SAP Note
As we all know SAP clearly identifies SAP’s own code and customer’s code and
treats them totally different. The SAP code was developed by SAP AG and is hence
maintained by only SAP. When a code correction is applied per a note, the code that
is affected is considered as altered.
Applying is SAP note is an easy task but there are certain best practices that can
keep you safe and revert system in case the note doesn’t work or issues occur.
 Ensure note applies to the current version of system
 Prefer SNOTE application than manual application
 Create a backup copy of the code before applying note
 When applying manual note changes, clearly document the code changes so
that it can be reverted if issues occur
 Never attempt to add any code other than what is in note when applying note
manually.
 Never attempt to alter code / write code in own naming convention etc. than
what is mentioned in note.
 When applying note automatically, ensure that the TRs (Transport Requests)
are ready or the ID thru which note is being applied has sufficient rights to
create TRs.
Notes are to fix issues but are still CODE CHANGES. Hence the functionalities need
to be thoroughly tested after note application no matter how trivial the change is.
End of Document