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 on!
Implementable. A note"s header section clearly mentions out if the
note can be implemented or not.

If it is an implementable note, #rst, go to transaction S$T%.

&lick search button
on top and enter the
note number. If the
note is already
downloaded, system
will point to it. %lse,
there is one additional step to download it.

If note is already a'ailable, ensure it is latest by clicking on ()ownload
*atest 'ersion" from menu as shown below.

1 To download a note, go to menu option +o To , )ownload SAP
ote.

%nter the note number and e-ecute to download.

$nce downloaded, search for note again and then double click note
number to na'igate to note details screen.

It is easy
to notice
'arious
icons
ne-t to
note numbers. They 'isually indicate implementation status for each
note. The grey diamond indicates that note cannot be implemented. A
play button indicates note can be implemented.

otes that can be implemented, the best way to implement is thru
S$T%.

Thru S$T%, we can check the implementation status of each SAP
note. If the note says (&an be implemented", then after ensuring that
the note is re.uired and can #- the issue, click e-ecute 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 (&orrections" and e-pand it. It lists the code
corrections that will be done to #- the issue. %ach correction mentions
a code section from system followed by code changes in terms of
insertion of code, commenting /deleting0 the code or both.

Some notes need manual inter'ention and the note mentions how it
has to be done step by step. 1or e.g. if system re.uires to add a new
data element or some entry in data dictionary followed by code
changes then the note e-plains the same.

ote2 3hen code changes are to be done manually, an access key is
re.uired to make changes to SAP code. This needs help from 4ASIS
team as the ob5ect I) for the code being altered /e.g. include name0
needs to be updated in SAP ser'ice 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 re.uest to SAP.

IMPORTANT: Since these are SAP code corrections, Transport
Request will e requested while s!stem applies the code
changes" #e prepared to create$pro%ide TRs & mostl!
wor'ench requests"

(ninstalling a Note
3hen a note is applied thru S$T% by clicking e-ecute, system allows
to uninstall it as well. Technically it re'ert the code to original state. To
uninstall a note, select (6eset SAP Implementation ote" from menu as
shown below.

This doesn"t apply if codes are changed manually by a de'eloper and
hence it is ad'ised to keep a copy of code being altered either in
system or as document in a safe place. 6e'erting note changes in this
case is to again edit the code and put back old 'ersion, preferable from
a system where the code is not altered or from a backup system.

Trouleshooting
Things can go wrong when implementing SAP ote. There are many
ways to trouble shoot. Please note that the best way is to uninstall, if
allowed, and apply again.

$ther way is to perform a code comparison and see which sections of
the code were changed. ow pull up the ad'ised code changes from
SAP ote corrections folder and see what"s gone wrong and apply the
changes manually.

#est practices while implementing an SAP Note
As we all know SAP clearly identi#es SAP"s own code and customer"s
code and treats them totally di7erent. The SAP code was de'eloped by
SAP A+ and is hence maintained by only SAP. 3hen a code correction
is applied per a note, the code that is a7ected is considered as altered.
Applying is SAP note is an easy task but there are certain best
practices that can keep you safe and re'ert system in case the note
doesn"t work or issues occur.

%nsure note applies to the current 'ersion of system
Prefer S$T% application than manual application
&reate a backup copy of the code before applying note
3hen applying manual note changes, clearly document the code
changes so that it can be re'erted if issues occur
e'er attempt to add any code other than what is in note when
applying note manually.
e'er attempt to alter code 8 write code in own naming
con'ention etc. than what is mentioned in note.
3hen applying note automatically, ensure that the T6s
/Transport 6e.uests0 are ready or the I) thru which note is being
applied has su9cient rights to create T6s.

otes are to #- issues but are still &$)% &:A+%S. :ence the
functionalities need to be thoroughly tested after note application no
matter how tri'ial the change is.