System Maintenance

The SAP software is largely maintained using support packages, a support package is a
set of corrections for errors in ABAP programs, these corrections are usually ready
available as SAP Notes Support package bundles the corrections that have been provided
over a period of time in a consolidated package!unctional enhancements give SAP
additional functional features and are less common
Support packages are specific for products, releases and components, because
components are tied with each other it is important to make sure to apply all packages
and the correct ones, to resolve these conflicts SAP uses support package stacks, which
contain compatible kernel and support package versions for all components in a system,
make sure you use this the support package stacks instead of individually applying
support packages in isolation
"hen should you apply these packages, most companies will have a patch procedure and
the SAP system should be part of this process, basically you should install the patches
when they come out #most companies may only apply packages every $ or %& months or
even only when they get a problem that the packages will fi'( but they should be applied
in order in your environment #)*+ first then ,A then Production(, and with at least a
week between environments this means that by the time you get to Production the
packages have been fully test
SAP Maintenance -ertificate
.f when using transaction code SPAM or SA.NT you get the below message, this means
that you need to obtain a SAP maintenance certificate, this proves that you are supported,
you simply login to the portal and in the license section re/uest for a maintenance
certificate, if you have Solution Manager implemented this can be done automatically
0nce you have obtained a maintenance certificate you use transaction code S1.-*NS* to
enter the license into the system
To
obtain
more
infromation on how to get a maintenance certificate see this link
)ownloading Support Packages
Support packages, support package stacks and functional enhancements can be
downloaded directly from SAP, with the newer releases of SAP you can only download
them via Solution Manager, you can download support packages from the SAP portal
directly but you need Solution Manager to confirm the downloads The Maintenance
0ptimi2er in Solution Manager simplifies the selection of support packages and helps
avoid errors, it is recommended to use this method
3ernel updates and updates for the SPAM #Support PAckage Manager( 4SA.NT #SAP
Add5on .Nstallation Tool( versions can be downloaded with Solution Manager
!irst how do we determine the current support package level within our SAP system, we
can use status from the main menu
The status
dialog bo'
#left5hand
screenshot(
give us lots of
information
about the SAP
system, client,
operating
system,
database used
license details,
etc The
component
version gives
us the version and support level of our SAP system To get more details on the packages
select the spyglass #red bo'( then you will see the dialog bo' in the right5hand screenshot,
here you can see the software component, release and the level #you can print this list(
Technical support packages comprise of the following elements
SAP6component76release76level7
So for e'ample SAP3B89%9: can be broken down as SAP434B489%49: which means this
is the third support package of the SAP Basis component for release 89%
.f you select the other kernel info button at the bottom of the status dialog bo', you can
obtain your kernel release and current patch level, in my case the kernel is 8&9 and . am
at patch level %9;
<ou can
also use
transaction code SPAM which gives you more detailed information regarding which
support packages have been imported, here you can see the imported support packages
#left5hand red bo'( and the package levels #right5hand red bo'(
The below lists
the imported
support
packages #left5
hand
screenshot(,
and the support
package levels
#right5hand
screenshot(
Now that we know what kernel and patch levels we are at we can start to download the
latest packages, you login into the SAP support portal, for this you will need a =ser .),
the main screen has various categories, from license details, knowledge transfer and
software downloads
There are many software downloads that you can select from, if performing a upgrade or
updating to the latest packages you must find the appropriate documentation and read it
carefully, this will help you select the correct packages that you need to download This is
probably the most time consuming part but you should spend some time on this as you
don>t want to get half way through the install to find you are missing packages
There is also a support package stack schedule so that you know when the ne't releases
will be available
0nce you have your list you can then use one of the many options to search for the
packages that you re/uire, if you look at the left5hand side of the screenshot you can see
many different ways to search
0nce you have find the re/uired package you drill down until you come to the download
screen, you can either download them directly or add them to a download basket in which
we can download the basket using SAP>s )ownload Manager which we will look in a
moment
<ou can view you download basket at any time and items will remain in the basket until
you either delete them or download them
The SAP )ownload Manager is a ?=. tool that is installed on your P- #or various other
options( to download the basket that you have your packages in, there are many various
options as you can see below
The P- version is a simple standard installation, @ust follow the on screen prompts, you
will be re/uired to enter your SAP =ser .) this allows the download manager to login to
SAP support portal and communicate with your download basket
0nce
you
connect to the download basket you should be able to view all your downloads that you
selected, you can either select specific packages to download or download them all at
once, you can even schedule to perform the download at a specific time, so overnight
while your P- is doing nothing
"hen the package has been download it turns green, also you have a progress bar at the
bottom of the ?=. which display the progress made thus far 0nce you have your
download packages then get them on the SAP server #if not already( and you are ready to
install4import, remember once you have downloaded your packages they will be removed
from the SAP support portal download basket
Aere is a list of important notes4points regarding maintenance
% Make sure you have secured a full backup before performing any maintenance to
a SAP system
& Make sure you lock out all users while perform any maintenance
: Bead all SAP notes and documentation relating to the maintenance that you are
performing
C )ownload the necessary packages once and use the same packages on all SAP
systems
; Always perform the first maintenance on a test or development system before
moving onto Production
$ Always leave sometime time between moving on to the ne't system, this will
hopefully will provide time to test most features
8 Start with a kernel update first unless the documentation tells you otherwise
D Then perform SA.NT4SPAM updates ne't
E !inally import the ABAP support packages, import in test mode then import in
standard mode
Performing a 3ernel =pdate
The operating system files are updated in a kernel update, there are used to eliminate
bugs and other errors in the kernel The kernel depends on the operating system and the
database of the SAP server, the same kernel version must be installed on all SAP servers
in a system #the central instance and other application servers(
A kernel update comprises the following
%9 Save the old 3ernel
%% -opy the new kernel to the SAP server and unpack it
%& Stop the SAP system and services
%: Beplace the kernel files
%C Start the SAP system and check the logs
<ou should have sufficient privileges on the operating system to perform a kernel update
and you should be familiar with the operating commands, you must make a backup of the
old kernel, this is your rollback option if things do not go to plan, if the SAP systems after
a kernel update it is save to say that it is successfully, most problems will be highlighted
when trying to start the SAP system
To backup the current kernel, you need to copy the entire 4usr4sap46S.)746instance74e'e
directory for save keeping, on my current .)*S system it is about %%?B in si2e
0nce you have downloaded
the kernel from the SAP portal
you need to unpack it using
the SAP-AB program #you
can download this from the
SAP support portal(, if you
have ever used tar in the =ni'
world before then it is similar
to this,
using SAP-AB "hen you have download the kernel update you unpack the kernel files using the below
F "indows
SAP-AB 5'vf SAP*G*H6patchHlevel756identifier7SAB 5B 6drive7IJsaptempJkernelH89%H$EJnew
F =ni'
SAP-AB 5'vf SAP*G*H6patchHlevel756identifier7SAB 5B 4usr4sap46S.)746instance74temp4kernelH89%H$E4new
Make sure that you do not receive any errors when unpacking the file may have been
corrupted during the download
Ne't you need to stop the SAP system, and this depends on the type of operating system
you are using, . have a starting and stopping section on the windows version, you must
also stop the database, saposcol and saprouter
Now replacing the kernel is simply copying the unpack kernel update files in the
4usr4sap46S.)746instance74e'e directory #make sure you have backed up this directory(,
overwrite any e'isting files if the operating system prompts you to do so, remember you
are overwriting the directory not replacing it .f you get errors stating that you cannot
overwrite a file because it is in use then you have forgotten to stop a service, make sure
that all services are stopped Also check that permissions have not change on the
directories and files you can compare this with your backup
0nce you have copied the new kernel update simply start SAP and then check the logs for
any errors, it may take a bit longer to start with a new kernel so don>t be too alarmed, @ust
keep an eye on the log files for any errors 0nce running try and login to the SAP system
via the ?=., and then check system 57 status to confirm the kernel has been updated
0nce a few weeks have pasted and you have had no errors then you can delete the old
kernel to claw back disk space
Applying SPAM4SA.NT updates
ABAP components are maintained in the two below SAP tools
Support PAckage Manager #SPAM(
SAP Add5on .Nstallation Tool #SA.NT(
The difference between them is SPAM is used to upgrade e'isting components #support
packages( to the latest versions and SA.NT is used to install new components #plug5ins
and add5ons(, you should also perform the update in client 999
These tool are updated on an ongoing basis, so you should download from the SAP
support portal the latest version and import them to avoid any errors or problems, some
support packages re/uire a minimum SPAM4SA.NT version To get the SPAM4SA.NT
version simply run the transaction codes SPAM4SA.NT and the version number will be at
the top
0nce you have
downloaded a
package you
simply select
support
package 57
load packages 57 from front end then point to the downloaded package #top left5hand
screenshot(, then you simply import the package support package 57 import
SPAM4SA.NT update #left5hand screenshot bottom(, you will then receive a confirmation
message that the package has been imported, restart the transaction code SPAM so that it
can reread the configuration
.mporting ABAP Support Packages
1astly we come to importing ABAP support packages, which we use the transaction code
SPAM, the steps to importing ABAP support packages are
%; )ownload the ABAP support packages
%$ Transfer the files to the server
%8 =npack the archives
%D 1ock users and deallocate @obs
%E .mport the support packages in test mode
&9 import the support packages in production mode
&% Perform modification ad@ustments
&& Begenerate ob@ects
&: *'ecute a regression test
<ou import the updated using client 999 as we did in SPAM4SA.NT updates, you need at
least SHAS<ST*M authori2ation, once you have downloaded the support packages
#using download manager( onto your P- you need to get them onto the server, you can
use load the packages from your P- using the from front end as we did in the above
SPAM4SA.NT, the other option is to copy the files to the SAP server into a temporary
directory and unpack them using SAP-AB
The SAP-AB unpacks the archives into two files
-SB6name7ATT
-SB6name7PAT
These files belong to the *PS inbo' that is in the location 4usr4sap4trans4*PS4in as per
below, if you are already in the *PS directory when you unpack the files will
automatically go into the in directory, if not then a directory will be created *PS4in and
the files will go there and then you need to move the files there
0nce you have put the support
packages you can then load the
packages using the from
application server in transaction
code SPAM
<ou
can
then
view
the
new
support packages from the initial screenshot #left5hand screenshot(, now that the systems
has access to the files #right5hand screenshot( you can import them into your system
<ou must make sure of the following before importing
All users are locked and logged off #transaction code SM9C(
No @obs are running or scheduled #transaction code SM:8(
=sing transaction code SPAM we can now import the support packages, select the
display4define button, then select the components you want to import Support packages
for various components must be imported in a specific se/uence known as a /ueue, the
system calculates the /ueue itself which is important if you skip one or more support
package levels, @ust make sure you receive no errors <ou may be asked if you want to
transport the modification ad@ustment, you can transport this ad@ustment to other systems
in your environment which means you don>t have to perform it on each systems 0nce all
the ad@ustments have finished you can then import, select from the menu e'tras 57
settings and then select the import /ueue tab select the test radio button, then from the
main screen select the import button #lorry icon(
After the import has
completed you can
check the log for
any errors as per the
below screenshot>s
Now repeat the same
process but using
standard mode
#production(, and
then import the
support packages
#lorry button(
Performing a
Modification
Ad@ustment
.f a support package
contains SAP ob@ects
#such as programs or
tables( that you have changed in your system and a conflict occurs the support package
manager provides you with information about these ob@ect conflicts and prompts you to
perform a modification ad@ustment, as part of this ad@ustment you must choose between
retaining your modifications and accepting the newly delivered SAP versions of the
ob@ects <ou can use the below transactions code depending on the type of ob@ect
Program ob@ects #programs( 5 transaction code SPA=
)ata )ictionary ob@ects #tables(5 transaction code SP))
<ou may need help from a development team member as you may not have permissions
as you did not make the change yourself, check with the development for any
modification ad@ustment is re/uired when importing support packages
Begenerating 0b@ects
.mporting support packages results in many SAP ob@ects being replaced with new
version, these ob@ects need to be compiled or regenerated for the first time they are called,
this will probably cause a temporary performance degradation, is this a one time
operation <ou can only compile or regenerate ob@ects that were already in use before the
support package import, using the transaction code S?*N, this will help with
performance Bemember you will need additional disk space to regenerate ob@ect the
amount of space depending of the number of ob@ect to regenerate
There are a number of choices when using the transaction code S?*N, each option try>s
to limit the amount of performance impact, lets use regenerate e'isting loads
The ne't screen
again allows you
to limit the
performance
impact to the
system #left5
hand
screenshot(, if
you have several
application
servers you can
select one or
more servers
among which
generation load
is distributed
#right5hand
screenshot(
At this point the system will now search for invalidated ABAP ob@ects, this may take
some time to complete
<ou can
e'ecute the generation in the background and using either using transaction code S?*N
or SM:8 you can monitor the progress

Because many ob@ects may have changed it is best to perform a regression test to check
that all functions are still available and work without any errors after the imports, to
perform regression tests you can use tools like SAP e-ATT #*'tended -omputer Aided
Test Tool(
.nstalling Add50ns
Add5ons enhance the functional scope of standard SAP systems, for e'ample add5ons
include industry solutions and plug5ins, add5ons can be download from the SAP portal the
same way as support packages 0nce downloaded you use transaction code SA.NT to
install, the tool is very similar to using transaction codeSPAM as above,
"hen
you
click
on the
start
button
you
can
upload
the
downloaded add5ons from you P- #using the front end server as we did above(, you can
also download them into the *PS inbo' directory, again which we covered above
Again
the
add5
ons
are
added
to a
/ueue, you can also add them to a transport, you view the add5ons from system 57 status
and then selecting the component information button <ou will have to perform a
modification ad@ustment, select the generate all ob@ects of selected software components
in the transaction codeS?*N, only select the add5on you>ve @ust installed for generation
.mplementing SAP Notes
SAP provides program corrections that have caused problems within the SAP system,
SAP Notes both describe the problem and the solution, the correction itself is attached to
the SAP Note which you download Not all SAP Notes can be implemented many @ust
describe customi2ing settings or system configurations that have to be performed
manually to eliminate the error <ou need to pat particular attention to the following
)ocument all SAP Notes that have been implemented into your SAP systems
)ocument all SAP Notes that only re/uired a manual change to the systems
SAP Notes can be part of an upgrade, so check all upgrade documentation
Make sure you read the SAP Note as other SAP Notes may be re/uired
SAP Notes are usually relevant for specific SAP versions #releases(, support packages
versions or kernel patch levels )etails of a SAP Notes validity are provided in the SAP
Note itself under K+alid BeleasesK and 1inks to Support PackagesK
<ou can check the system patch level using system 57 status, the value in the release
column shows your SAP system version #left5hand screenshot(, the highest support
package column indicates the most recent implemented support package for each
software component <ou can also get the kernel information using the status menu
#right5hand screenshot(
0nce you have determined that a SAP Note needs to be implemented you can use the
transaction code SN0T* #Note Assistant( to install the Note /uickly, it downloads the
SAP Note automatically from the SAP support portal, it also checks for any
dependencies The Note Assistant may also help you to avoid errors because it applies
automatic code changes to SAP Notes Note Assistant also logs all changes that were
previously implemented in your system
Select
the
download button and then enter the SAP Note number
0nce
downloaded the
SAP Note will
appear in the
new worklist
#left5hand
screenshot(, the
SAP Note can or cannot be implemented as indicated by the gray or blue icons, simply
the select the SAP Note you wish to implement and then select implement SAP Note
button, if for whatever reason a SAP Note cannot be implemented double5click on the
SAP Note and the documentation of the SAP Note will appear #right5hand screenshot(
A security dialog bo' will appear to confirm that you have actually read the SAP Note,
you can read it for this screen
Another
informational
screen appears
#left5hand
screenshot(, a
transport
re/uest will
appear #right5
hand
screenshot(,
you can add it
to another
re/uest or
create a new
one
Ne't a dialog bo'es appears lists the ob@ects that are going to be changed or corrected
<ou will be returned back to the worklist after a period of time, the SAP Note will have a
status of processing, you can now test the SAP Note, once tested you highlight the SAP
Note and select the set processing status button #in red bo'(
Set
the
SAP
Note
as
completed to finish off the installation
<ou can search for
SAP Note>s using
the browser #left5
hand screenshot(,
the SAP Note will
appear in the
results screen
#right5hand
screenshot(, as you can see here is the one we @ust installed
As a note you should use transaction code S*%9 #transport organi2er( to release any
transports related to SAP Notes, Support packages and Add50ns