Upgradation

1
2
What is SAP Up-gradation
Upgrading is the process of replacing a product with a newer version of the same product.

Typically, software companies sell upgrades to prevent users from switching to other products. and
providing additional fuctinalities in their product.

In case of SAP, ECC 4.7, ECC 6.0 are the versions of upgrade.

Need Of SAP Upgrade

Why upgrade?

The first and easiest, but maybe not the most correct answer, is to remain in support. 
It's true though, by upgrading, customers will have their strategic business software of choice in
support until December 31st 2020 which by any means provides a great deal of stability and
peace of mind budget holders - this could be a reason enough, however this is not the norm from
my experience.

Secondly, there normally has to be a business case and this is where things get interesting. 
Finding the benefits a customer could employ from an upgrade carries far more weight behind a
business case.  For example what seems to be a current popular customer choice is technical
consolidation where cost reductions are realised or the upgrade was to provide a platform for the
take up of a further SAP module where process improvements could then be employed.  

Thirdly, you have those customers that have seen the future and want, no need, the likes of 
SRM, CRM, Mobile, Cloud, and HANA right now to stay ahead of the competition.  They can't
wait, the impulse is too much.  SAP HANA right now is producing so many lines of enquiry it's
scary  - nearly as scary as the lines of data SAP HANA can process in a second.   
An upgrade becomes 'just a prerequisite' in these cases - an important stepping stone to all those
new toys and a business case may be straight forward.

 
You know your own reason for upgrading and no doubt you sit somewhere in an
innovative/visionary loop where you have an eye on the future tech but not yet committed or you
want the tech now.  Either way it makes no difference, the result is the same - the current SAP
components need to be upgraded to supported versions.

3
Types of SAP Upgrades
SAP has three main types of upgrade.

Technical Upgrade: Considered to be the fastest upgrade which does not disturb any of the existing
business processes.

Functional Upgrade: This upgrade starts with a technical upgrade, mentioned above. A functional
upgrade allows new functionality to be implemented as part of the upgrade project. This upgrade type
also provides you with the ability to convert many of the custom process into standard functionality.

Strategic Upgrade: This is driven by enterprise SOA to provide more flexibility to business process
innovation.

Technical Upgrade vs Functional Upgrade :

As the name implies, technical upgrade only upgrades the software to the latest version and the new
functionalities that come with the new version are
not activated or implemented. Whereas in a functional upgrade, the functionalities offered by the new
SAP version are also implemented in addition
to technically upgrading the software.

4
How to check current kernel Version/ Release in SAP
To check the Kernel version, login to SAP system, click on System pull down menu and
then select Status 

Then click on kernel information as shown in below image, this will result another popup
which will show current kernel release

5
How to check Current SAP Support Package level of each
component
1. Log into your SAP system

2. Click on System > Status in the menu

3. Click on the magnifying glass icon in the pop-up window, below component version 

4. It will show your current SAP Support Package of each component.

6
How to trace / check if an OSS SAP Note is deployed /
implemented in your system or not ( SNOTE )
SAP frequently releases “Online SAP Support” (OSS) Notes which may contain bug
fixes , new program developments or enhancements or other miscellaneous updates.
At times before you begin work , it will be required to check whether a particular note is present
in your SAP system
To ensure that a particular OSS note is present in your SAP system ,execute the following
steps:

a)In SAP command prompt , Enter TCode # SNOTE

b) In the next screen, Click  SAP Note Browser
c) Type in your SAP Note Number in the corresponding text field and click execute
d) Next Screen shows status of the SAP note

For a background, a SAP note could have any of the following seven status -

 Can be implemented
 Cannot be implemented
 Completely implemented
 Incompletely implemented
 Obsolete
 Obsolete version implemented
 Undefined Implementation State

7
How to Determine SAP GUI Version / Patch level / Build
number
In order to determine SAPGui Version installed on your client PC and to know the Patch
Level of your SAP GUI installation, SAP users or ABAP developers can use
SAPLOGON or SAPLOGONPAD application.

Open your SAP Logon Pad by a double-clicking to the icon on your desktop.

Click on the top-left corner of the SAP Logon Pad window.

Select the "About SAP Logon..." option which is displayed as the last option, as shown in the
image below.

An info screen which is similar to the one shown below will appear.
Check the lines with label "Release" and "Patch Level".

8
Here in this example, the SAP GUI version number is 7100.4.17.1046.
 
The first part 7100 of the SAP Gui version gives us the release information.
This SAP GUI is the Final Release 710 (means 7.10).

You can also see that the patch level is displayed as 17 (look at line Patch Level 17).
  1046 which is the last portion of the version number is showing us the internal build
number of the GUI 
  
It is also possible to take the version information from the file properties of the SAPGUI.EXE
executable file.
SAPGUI application executable can be found in file folder "C:\Program Files\SAP\FrontEnd\
SAPgui\SAPgui.exe" with a default SAP GUI installation.

9
Difference between support packages, kernels & SAP Note

Difference between support packages, kernels & SAP Note

Snote :-

By implementing an SAP Note an error in a single program or 

Transaction is removed.
You can apply these using SNOTE

Support Package:-

Applying an SAP Support Package, all errors are corrected that

Were known, SAP Support Package is nothing but bunch of corrections.
(Collection of corrections of serious errors in the ABAP/4 Repository)
You can apply this using transaction SPAM
 Kernel :-

SAP Kernel is the core of the application. Like all other applications the Kernel contains the executable
files (.EXE files for stating various processes in SAP.
That’s the reason when a Kernel upgrade is done it means new versions of the various EXE files replace
the older versions.
 With regards to advantages, it is an appropriate question in this context since the Kernel is a must (.EXE)

10
SAP Support Pack Errors Troubleshooting (SPAM / SAINT )
1. SYNTAX_ERROR- This might come if you are trying  to access the t-codes when the update is running
 
Solution-  You have 2 options. 

1. Open a customer message with SAP Support. They will give you some 
OS level commands that will fix the problem. 
DO NOT attempt to do this yourself. Or SAP can refuse to support your system 
until you pay Consulting services to fix the problem. 

2. Restore your system to the state it was before you started the 
import of support package queue and start from scratch. 

2. PATCH_FILE_READ_ERROR- Error in phase: DISASSEMBLE, Return code: 12,OCS Package:

SAPKB70008

Solution-  Space constrained; you are running out of space.

3.  TP_STEP_FAILURE- Error in phase: IMPORT_PROPER, Return code: 0008, Error message: OCS

Package ALL, tp step "N", return code 0008

Solution- you can fix it by creating a index in database DB02OLD

If an error is
recognized during a phase, Support Package Manager stops the import process
until the error is corrected. You can get information about the reason the SPAM
transaction was stopped and in which phase by choosing Queue ® Status.

Error Types
Support Package
Manager displays the following types of error messages:
…

11
1. 1.
Support Package
Manager Security Checks
A typical
example is the OBJECTS_LOCKED_? phase. Support Package Manager stops the import
process if objects that need to be overwritten by the queue are still locked in
requests.
1. 2.
Error messages from
programs tp and R3trans
You can always
find the cause of the error in the relevant transport log. A typical example is
the TEST_IMPORT phase. This step checks whether there are unconfirmed repairs to
objects that need to be overwritten by the queue. The objects in question are
listed in the test import log.
1. 3.
Incorrect
configuration of the Change and Transport System
Errors here
often include not having the relevant authorizations for accessing files in the
Change and Transport System, or using old versions of the tp or R3transprograms. Check the
configuration of the
transport tools by choosing Utilities ® Check transport tool.
A typical
example is the DISASSEMBLE phase. If <sid>adm does not have write authorization for
directory /usr/sap/trans/data (UNIX), Support Package Manager stops at the
DISASSEMBLE phase with CANNOT_DISASSEMBLE_R_DATA_FILE.
Support Package
Manager requires the Change and Transport
System to be configured correctly.
For more information
on known problems, see the OCS Notes referred to in SAP Note 97620.

Known Errors
PROLOGUE
In this phase, a
dialog box prompts you to confirm the import of the Support Package. If you are
not authorized to use Support Package Manager, or if the current queue has not
yet been confirmed, Support Package Manager stops with a message to this
effect.
CHECK_REQUIREMENTS
This phase
checks various requirements for importing a Support Package. It may terminate
for the following reasons:
○
TP_CANNOT_CONNECT_TO_SYSTEM: tp
cannot log on to the
database of the system.

12
○
QUEUE_NOT_EMPTY: The tp buffer contains incompletely processed OCS
requests. Use the following tp command to display these requests:
tp SHOWBUFFER <SID> -D SOURCESYSTEMS=
TAG=SPAM
You can only
continue to import the queue after these requests have been completely
processed, or deleted from the tp buffer.
DISASSEMBLE
In this phase,
files from the corresponding EPS parcels are unpacked and stored in the
directory /usr/sap/trans/data (UNIX). It generates the command files
(cofiles) from the accompanying files and saves them to directory /usr/sap/trans/cofiles (UNIX). It may
terminate for the following
reasons:
○
CANNOT_SKIP_ATTRIBUTE_RECORD: The attributes could not be read in the EPS
parcel. The reason that the file cannot be read is either because it has been
deleted or because your authorizations at operating system level do not allow
this.
○
CANNOT_DETERMINE_EPS_PARCEL: The EPS parcel is not in the EPS Inbox, because
it may have been deleted. You need to download the relevant Support Package
again.
○
CANNOT_DETERMINE_DATA_FILES: The name of a data file could not be
determined, because a profile parameter was not correctly configured. Use report RSPARAM to check
the
settings.

○
CANNOT_DISASSEMBLE_R_DATA_FILE: An R3trans data file could not be unpacked.Possible errors
include a missing EPS parcel or
a data file that could not be written to. An error occurred while transmitting a
20K block from the EPS Inbox to directory /usr/sap/trans/data(UNIX).
○
CANNOT_DISASSEMBLE_D_DATA_FILE: An ADO data file could not be
unpacked. The reasons are the same as for CANNOT_DISASSEMBLE_R_DATA_FILE.
○
CANNOT_CREATE_COFILE: The cofile could not be created from the
corresponding data file. One possible error source is that <sid>adm does not have write authorization for
the
directory /usr/sap/trans/cofiles (UNIX). Check whether the data file has been
created. If it has not been created, check that the option Create new data
file is activated in the settings.
ADD_TO_BUFFER
This phase adds
the queue to your system’s transport buffer. It may terminate for the following
reasons:

13
○
TP_INTERFACE_FAILURE: The tp interface could not be called. An RFC error has occurred.
○
CANNOT_ADD_PATCH_TO_BUFFER: A Support Package could not be added to the
transport buffer. For more information, see the SLOG log file in the directory
/usr/sap/trans/log (UNIX).
MODIFY_BUFFER
This phase
prepares the transport buffer so that the subsequent import phases can be
processed correctly. It may terminate for the following reasons:
○
TP_INTERFACE_FAILURE: The tp interface could not be called. An RFC error has occurred.
○
CANNOT_MODIFY_BUFFER: An unsuccessful attempt was made to modify the
transport buffer.
IMPORT_OBJECT_LIST
This phase
imports the object lists for the Support Packages in the queue into the system.
It may terminate for the following reasons:

○
TP_INTERFACE_FAILURE: The tp interface could not be called.
○
TP_FAILURE: The tp program could not be executed. For more
information, see the SLOG or ALOG log files.
○
COMMAND_FILE_IMPORT_FAILURE: The object list for one or more Support
Packages could not be imported. You can find the source of error in the command
file import log.
TEST_IMPORT
This phase
checks whether any objects overwritten by the import are still in unreleased
tasks. You can find the source of error in the log of the test import.
You can skip
test import errors and continue the import by choosing Extras ® Ignore
Test Import Errors. However, depending on the type of error, this
may cause the error to reappear with very serious consequences during the real
import. You therefore always need to check test import errors first, and correct
them wherever possible.
OBJECTS_LOCKED_?
This phase
checks whether any objects overwritten by the import are still in unreleased
requests. It may terminate for the following reasons:
○
CANNOT_GET_OBJECT_LIST: The object list for a Support Package could not
be found, since the Support Package does not exist.
○
CANNOT_CHECK_LOCKS: An error occurred when checking the locks for
an object in the queue.

14
○
OBJECTS_LOCKED_IN_REQUESTS: Objects were found that are still in requests
that have not yet been released. Release these requests before continuing
importing the Support Packages.
ADDON_CONFLICTS_?
This phase
checks for conflicts between objects in the queue and installed add-ons. If it
finds any, Support Package Manager stops and prompts you to import the relevant
Conflict Resolution Transports (CRTs). It may terminate for the following
reasons:
○
CANNOT_GET_OBJECT_LIST: The object list for a Support Package could not
be found, because the Support Package does not exist.
○
CANNOT_GET_LAST_UPGRADE_INFO: The information about the component upgrade
could not be determined.
○
UNRESOLVED_ADDON_CONFLICTS: Conflicts with add-ons could not be resolved,
because the relevant CRTs are missing from the queue.
SCHEDULE_RDDIMPDP
This phase
schedules the transport daemon (program RDDIMPDP). It may terminate for the
following reasons:
○
CANNOT_SCHEDULE_RDDIMPDP: Job RDDIMPDP could not be scheduled. Call
Transaction SM37 (job selection), enter the following
parameters and choose Continue:

Job name RDDIMPDP

User name <User

name>

Trigger event SAP_TRIGGER_RDDIMPDP

○       Parameter ein und wählen Sie Weiter:

Wählen Sie den abgebrochenen Job aus und
zeigen Sie das Jobprotokoll an.

Select the job

that was terminated and display the job log.
○
Problems with the
SAP lock mechanism: Call transaction SM12 and make sure that there are no
programs listed with the name RDDIMPDP.
CREATE_VERS_BEFORE
This phase
creates versions in the version database of the objects that you want to import
and for which versions can be created (ABAP coding, screens, and DDIC objects).

15
It may terminate for the following reasons:
○
TP_INTERFACE_FAILURE: The tp interface could not be called.
○
TP_FAILURE: The tp program could not be executed. For more
information, read the SLOG or ALOG log files.
If the return
code is 0152 (nothing done), check in the configuration of the transport tools
in the Transport Management System (transaction STMS) whether the VERS_AT_IMP parameter is set
as ALWAYS. If it is not, set this value and continue
importing the queue.
○
TP_STEP_FAILURE: tp step CREATE_VERS_BEFORE could not be performed
successfully. To find the exact cause of the error, choose Goto ®
Log
® Queue, and look at the version log.
SPDD_SPAU_CHECK
In this phase,
the system checks if a modification adjustment is necessary (transactions
SPDD/SPAU).
DDIC_IMPORT
This phase
imports the ABAP Dictionary. It may terminate for the following
reasons:
○
TP_INTERFACE_FAILURE: The tp interface could not be called.
○
TP_FAILURE: The tp program could not be executed. For more
information, read the SLOG or ALOG log files.
○
CANNOT_IMPORT_DDIC: The ABAP Dictionary could not be imported. You
can find the source of the error in the Dictionary import log.
AUTO_MOD_SPDD
This phase
checks whether all modifications to ABAP Dictionary objects can be adjusted
automatically.
RUN_SPDD_?
In this phase,
you are prompted to adjust your modifications to the ABAP Dictionary objects by
calling transaction SPDD.
LOCK_EU (only
for import mode downtime-minimized)
This phase locks
the development environment. It may terminate for the following reasons:
○
TP_INTERFACE_FAILURE: The tp interface could not be called.
○
TP_FAILURE: The tp program could not be executed. For more
information, read the SLOG or ALOG log files.

16
INACTIVE_IMPORT
(only for import mode downtime-minimized)
This phase
imports program code and program texts in an inactive state. It may terminate
for the following reasons:
○
TP_INTERFACE_FAILURE: The tp interface could not be called.
○
TP_FAILURE: The tp program could not be executed. For more
information, read the SLOG or ALOG log files.
○
TP_STEP_FAILURE: The tp step INACTIVE_IMPORT could not be executed
successfully. The cause of the error is in the relevant log (SAPBxxxxxx.<SID>). This log is in subdirectory
log in the transport directory. To display this
file, run report RSPUTPRT, or call transaction AL11.
DDIC_ACTIVATION
This phase
activates the imported ABAP Dictionary objects. It may terminate for the
following reasons:
○
TP_INTERFACE_FAILURE: The tp interface could not be called.
○
TP_FAILURE: The tp program could not be executed. For more
information, read the SLOG or ALOG log files.
○
TP_STEP_FAILURE: tp step DDIC_ACTIVATION could not be executed
successfully. To view the cause of the error in the activation log, choose
Goto
® Log ® Queue.
If you import two or more Support Packages
in a queue, activation errors can result from an incorrect activation sequence
for Dictionary objects. If this is the case, the activation errors disappear if
the objects are activated again. To do this, choose Support Package
® Import queue.
IMPORT_PROPER
This phase
imports all Repository objects and table entries. It may terminate for the
following reasons:
○
TP_INTERFACE_FAILURE: The tp interface could not be called.
○
TP_FAILURE: The tp program could not be executed. For more
information, read the SLOG or ALOG log files.
○
TP_STEP_FAILURE: A tp step could not be performed successfully. You
can find the source of error in the relevant log, for example, in the import
log.
If a
tp step 6, N or S is in the termination message,

17
it is a step independent of the transport request. The corresponding logs are
contained in the log overview under the node Import steps not specific to the transport
request.
You can also
find these logs in the following files in the log subdirectory of your transport directory
(usually /usr/sap/trans/log):
tp step 6: P<YY><MM><DD>.<SID>
tp step N: N<YY><MM><DD>.<SID>
tp step S: DS<YY><MM><DD>.<SID>
To display
these files, run report RSPUTPRT or call transaction AL11.
PREPARE_XPRA
This phase
prepares the execution of the XPRAs and after-import methods. It may terminate
for the following reasons:
○
TP_INTERFACE_FAILURE: The tp interface could not be called.
○
CANNOT_MODIFY_BUFFER: The tp program could not change the corresponding
buffer file. For more information, read the SLOG log file.
UNLOCK_EU (only
for import mode downtime-minimized)
This phase
unlocks the development environment. It may terminate for the following reasons:
○
TP_INTERFACE_FAILURE: The tp interface could not be called.
○
TP_FAILURE: The tp program could not be executed. For more
information, read the SLOG or ALOG log files.
AUTO_MOD_SPAU
This phase
checks whether modifications can be adjusted automatically.

XPRA_EXECUTION
This phase
executes the XPRAs and after-import methods. It may terminate for the following
reasons:
○
TP_INTERFACE_FAILURE: The tp interface could not be called.
○
TP_FAILURE: The tp program could not be executed. For more
information, read the SLOG or ALOG log files.
○
TP_STEP_FAILURE: tp
step XPRA_EXECUTION could
not be performed successfully. To find the cause of the error, read the method
execution log. To view the cause of the error in the log, choose Goto ® Log ® Queue.
○
CANNOT_READ_BUFFER: The tp program could not open the corresponding buffer

18
file. For more information, read the SLOG log file.
○
CANNOT_MODIFY_BUFFER: The tp program could not change the corresponding
buffer file. For more information, read the SLOG log file.
ABAP_GENERATION
This phase
generates the runtime objects for the imported Repository objects (ABAP source
code and screens). It may terminate for the following reasons:
○
TP_INTERFACE_FAILURE: The tp interface could not be called.
○
TP_FAILURE: The tp program could not be executed. For more
information, read the SLOG or ALOG log files.
○
TP_STEP_FAILURE: The tp step could not be executed successfully. To
view the cause of the error in the generation log, choose Goto ® Log ® Queue.
Remember that
objects delivered in Support Packages have already been imported completely. If
the return code is 0008, all objects without syntax errors have been generated.
The persistence
of syntax errors can be due to one of the following reasons:
■
Systems that have
been developed over a long period of time often contain many objects that are
not longer used or maintained. These objects are still active in the Repository
and can reference or use other objects (such as includes). If these includes are
modified, syntax errors might occur in the obsolete objects. However, these
errors have no effect on the SAP System, and can be ignored.
■
Generated includes
or programs can contain syntax errors after an import. You can usually ignore
these errors, since the source code of the generated objects is generated again
when the corresponding transactions are started (a special generation
transaction might exist).
■
If SAP objects have
been modified, or if customer objects use SAP objects, there are may also be
syntax errors in the modified SAP objects and the customer objects. If this is
the case, you must adjust the modifications or customer developments.
■
Buffer
synchronization problems can also cause generation errors.
Generation
errors do not necessarily indicate inconsistencies in the system. However, you
should investigate them using the criteria above. If the errors are
non-critical, or temporary, ignore them by choosing Extras ® Ignore generation errors, and continue
the import of the queue. Choose Support Package ® Import queue.
○
CANNOT_READ_BUFFER: The tp program could not open the corresponding buffer

19
file. For more information, read the SLOG log file.
○
CANNOT_MODIFY_BUFFER: The tp program could not change the corresponding
buffer file. For more information, read the SLOG log file.
RUN_SPAU_?
This phase
prompts you to adjust your modifications to Repository objects by calling
transaction SPAU.
CLEAR_OLD_REPORTS (only for import mode
downtime-minimized)
This phase
deletes obsolete versions of program code and program texts from the system. It
may terminate for the following reasons:
○
TP_INTERFACE_FAILURE: The tp interface could not be called.
○
TP_FAILURE: The tp program could not be executed. For more
information, read the SLOG or ALOG log files.
○
TP_STEP_FAILURE: The tp step CLEARREPORTS could not be performed
successfully. The cause of the error is in the corresponding log (PZ<yy><mm><dd>.<SID>). This log is in
subdirectory log in the transport directory. To display this
file, run report RSPUTPRT, or call transaction AL11.
EPILOGUE
This phase
completes the import process. The system checks if the queue has been completely
processed. If it has, there should be no more transport buffer entries for the
queue. It may terminate for the following reasons:
○
TP_INTERFACE_FAILURE: The tp interface could not be called.
○
TP_FAILURE: The tp program could not be executed. For more
information, read the SLOG or ALOG log files.
○
QUEUE_STILL_IN_BUFFER: The queue has not been processed completely,
since there are still incomplete Support Packages from the queue in the
transport buffer.

20
How to compress or extract a SAR file in SAP

What is a SAR file

SAR files are  delivered by SAP for releasing supportpackages of Kernel and other OS level binaries.

How to extract a SAR file in SAP in Unix based operating systems(AIX / HP-UX )

Login to the Unix system with sidadm user

Navigate to the path where the SAR file is located and use following command

to extract a SAR file.

SAPCAR -xvf <filename.SAR>

Please find below example of extracting PIS_COFINS_604_20110311.SAR file extraction. 6 files got
extracted from this  process

21
How to compress some files to generate a SAR file in SAP in Unix based operating
systems(AIX / HP-UX ) ?

Login to the Unix system with sidadm user

Navigate to the path where the files that are to be compressed are located and  use the following
command to compress a single SAR file.

SAPCAR -cvf <filename.SAR>

To compress multiple files, we can use the following command:

SAPCAR -cvf <compressed_filename.SAR> <file1> <file2> <file n>

Please find below screenshot where three files UMODPROT.T01, IMODPROT.T01 and CMODACT.T01
are compressed to form  king.SAR file.

What is SAPCAR ?

SAPCAR is an utility provided by SAP to compress or extract files (similar to winzip, tar etc)

22
Kernel Upgrade Interview Questions
1)What is your present patch level?
A: 710

2)From which patch level did you upgrade it?

A: 720

3) Why do you go for kernel patch upgrade?

A: we usually do it when there is a problem with the existing kernel files &
When we go for latest functionality like support packs implementation or add-ons or plug-in
implementation.
When sap recommends in early watch alerts we go for the kernel patch upgrade.

4)What are the files do you downloaded from service market place?
A: 1) sapexe file (db independent) & sapexedb file (db dependent)……

5)How many ways do you know the current patch level?

A: At os level -> login with sidadm and use the command disp+work
At sap level -> system -> status.

6)What are the problems do you faced while kernel patch upgrade?
PROBLEM 1:we generally forgot about file permissions
PROBLEM2: we should stop saposcol & listener otherwise it give problems.

7)What are the prerequisites for kernel patch upgrade?

A: we should take the backup of old kernel & check for the existing patch version to download
latest version.

8)how do you uncar the downloaded car files?

A: By using command SAPCAR -xvf 

9)Why do you overwrite the old kernel instead of replace?

A: Because latest kernel consist only updated kernel files only so to use the remaining files we
use to overwrite the kernel.

10)What are the post requisites for kernel patch upgrade and why?
A: run the scripts saproot.sh for the permissions in non windows environment & check for the
kernel patch version whether it is updated or not?

11)What is default kernel location

A: Usually it is located in: </usr/sap/SID/SYS/exe/<uc or nuc>/<system>. it might also be
located in /usr/sap/SID/SYS/exe/run 

Ex.

23
How to Implement SAP Note SNOTE
 Go to Transaction SNOTE

 Read the note carefully and check for validity, Pre-Implementation steps , Post-
Implementation steps and Pre-requisite Notes.

 Download / Upload the desired Note

 Do the manual pre-implementation steps in case the Note suggests.

 Implement the pre-requisite Note if needed

 Implement the Note , Navigate to menu Goto -> SAP Note Browser

24
 Make sure the Note is in “Can be Implemented” or “Obsolete version Implemented”
Implementation status.

 Select the note and proceed with Implementation (F8) , SNOTE also allows to implement set
of Notes together.

 Select the request from the pop-window or create a new request.

25
SNOTE lists out objects

26
Make sure to see the final status and log of note implementation (ctrl+F5).

Check for Post-Implementation steps from the Note , if mentioned proceed with the steps
accordingly.

27
SAP SPAM / SAINT UPDATE

SAP recommends to update SPAM /SAINT to latest  version  before applying

any Support packs or Add-on in SAP system

Please note :For  SPAM and SAINT update, you do not have to follow
increment approach like other SAP ABAP components.
For example if your current SPAM/SAINT version is 7.00/0034 ,you can
directly update this component to the latest . You do not have to apply version
35,36,37..and son on to reach to target level.

Following screen-cast will show you how to update your SPAM /SAINT .

1.To check the current Support Package manager version ,Log into SAP and
execute transaction SPAM.

In the above screen you can see that our Support package manager
version is 7.00/0034 . 

2. Now we will go to SAP market place to check the latest  version of SPAM
available for our release.Go to https://service.sap.com/swdc > Support
Packages and Patches > Browse Our Download Catalog > Additional
Components
2.1 Select SAP SPAM/SAINT Update  > Select appropriate version for your
system.
In our example we are trying to update SPAM from version 7.00/0034 to latest
available. So we will select SPAM/SAINT Update 700.

28
2.2 Now click on "Support Packages" and select the latest version.

Download the selected file and copy it to /usr/sap/trans/EPS/in , you can

deploy this file without copying at OS level also,but its recommended to keep
it at mentioned directory, so that it can be reused for all the systems that
landscape.

The gadget spec URL could not be found

29
3. Go to transaction SPAM - client 000 (do not use DDIC) and go to Support
Package > From Application Server > and press Yes.

4.This will upload the file from /usr/sap/trans/EPS/in and you will get below
screen.

30
5.Now go to menu and select Support Package >import SPAM /Saint
Update and press green check mark to start deploying the update.

Known Error : If SPAM updates through an error , go out and

execute SPAM and execute step 5 again.

6.Once the update is finished , go out and execute SPAM again. Now you can see the
new version deployed.

31
Support Package & Stack Upgrade
Steps to Upgrade the Support Package:

Step 1: Download Support Packs

Support Packages are available in SAP Support Portal,

under service.sap.com/patches.

Step 2: Loading Support Packages:

To load support packages we have two options:-

1. From Application Server

2. From Front End
From Application Server
1. Download the support packages from service marketplace and save them at
OS level in directory /usr/sap/trans.
2. Uncompress these files using sapcar executable
sapcar –xvf <support package name>

32
  
After uncompressing the support packages at OS level the .PAT and .ATT files
are stored in /usr/sap/trans/EPS/in directory.

Next, load the Support Packages into SAP system by choosing  Support Package --
>Load Package  --> From Application Server

From Front End 

Choose Support Package --> Load Packages --> From Front End

33
  

Step 3: Defining Queue 

Queue contains the Support Packages available for the different SAP Components
installed in your system. This Queue information is derived from the support pack
uploaded in Step 2.

1.On the initial screen in Support Package Manager, choose Display/Define.

2.A list of installed software components (for example, SAP_BASIS, SAP_HR,
SAP_BW) is displayed.

34
  

3.Once you select the required component, the current queue appears. This queue
contains the Support Packages available for the selected component in your system.
If you want to define the queue for another software component, choose Other
Component. If the displayed queue meets your requirements, you can confirm it by
choosing Confirm Queue
 

35
  

Step 4: Importing Queue. 

Once you a define a Queue (Step 4) while selecting a particular component (for
which we want to upgrade support pack), we need to do 'Import queue' to start
importing/applying that particular selected support pack (as per the standard SAP
process).

Choose Support Package --> Import Queue

 

36
To become familiar with known problems and issues, always read the note
mentioned in above screenshot. 

The support package import has been started

 

Step 5: Confirming Queue: 

Confirm that the queue has been imported successfully into your system. This
allows you to import Support Packages in the future. You will not be able to import
Support Packages further, if you do not confirm the queue.
 

37
Once Queue has been imported, SPAM status becomes YELLOW

Confirm successful import of the Support Packages into your system by

choosing Support Package à Confirm.
 

Checking Logs

 IMPORT LOG: It displays logs for Support Package Manager Phases that are

used by transport control program tp(transport control program).
Go to-->Import log-->Queue

38
 ACTION LOG: It contains information about the actions that take place during
the individual phases (while importing the current queue).

It also includes information about the point at which a phase was stopped, as
well as detailed error information.

To display the logs for the current queue Go to-->Action log

 While the support packages are being imported, logs are made into the tmp
directory (path: usr/sap/trans/tmp)
 Once the import process is completed logs can be viewed from the log
directory (path: usr/sap/trans/log)

39