Applying Ocs Patches: Type Area Topic Author

Type Handbook Document
Area SAP Basis

Topic Applying OCS Patches
Author Huseyin Bilgen
APPLYING OCS PATCHES

V 1.1
All Rights Reserved.

Copyright  2001-2002. Page 1 of 16
Area SAP Basis
Contents
BASIC TERMS AND CONCEPTS ....................................................3

A. Hierarchy Of SAP Software Conponents....................................................... 3
B. Support Packages: Types............................................................................... 4
C. SAP Patch Manager ( SPAM ) ......................................................................... 5
D. SPAM Steps ..................................................................................................... 5
IMPORTING SUPPORT PACKAGES USING SPAM ..........................7
A. Preparations..................................................................................................... 7
B. Retrieve Support Packages ............................................................................ 7
C. Load Support Packages.................................................................................. 8
D. Define Queue ................................................................................................. 10
E. Import Queue ................................................................................................. 12
F. Modification Adjustment............................................................................... 14
G. Check Logs .................................................................................................... 14
H. Confirm Queue............................................................................................... 15
I. Delete Unnecessary files after Patch Application.......................................... 15
J. Applying Patches in a 3 – System Landscape ............................................ 15

Area SAP Basis
BASIC TERMS AND CONCEPTS
A. Hierarchy Of SAP Software Conponents

The new Support Package model is based on SAP's new Software Components model.
• The objects of a software component correspond to a number of development classes that are
unique for that component. This enables each software component to be provided with patches.
• The hierarchy in the diagram shows the dependencies between SAP's software components. SAP
tries to minimize these dependencies. The Patch Manager recognizes these dependencies and
determines which patches are required for further components.
• Conflict Resolution Transports (CRTs) supply adapted objects to resolve conflicts between R/3
and SAP add-ons. These dependencies are also recognized by the SAP Patch Manager
automatically. The CRTs are requested to be applied to the system in the same step as the add-
on Support Packages that causes the conflict.
Online Correction Support (OCS) comprises tools and standard advance corrections called Support
Packages. A Support Package eliminates an error in an R/3 System. It is made available before the
next R/3 Release that contains the correction. A Support package replaces the objects affected by the
error, rendering their old versions obsolete. OCS makes Support Packages available to all customers
and enables them to apply them before the errors can affect a system. Thus OCS provides preventive
support. Unlike manual corrections, OCS patches are not recognized as modifications during upgrade
and are overwritten. This is no problem, as each new R/3 Release contains all previous OCS
corrections which were made before the new R/3 Release was built.
With R/3 Release 4.6, SAP introduces a new nomenclature for the OCS based on the new Software
Components concept. The former Hot Packages are replaced by Support Packages. Whereas Hot
Packages covered the area corresponding to the current software component types ABA, APPL and
BASIS, each Support Package covers only one software component type. Support Packages:
Contain full patches, that is, patches for ABAP Dictionary objects and Repository objects
Apply to a single R/3 Release, but are not operating-system specific or database specific

Area SAP Basis
Are named according to the form: "SAPK<Patch type><Release no.><serial no.>". They are
applied in order of serial number. New patch types introduced by SAP will follow a new 20 digit
naming convention.
Technically correspond to an upgrade, that is, require modification adjustments using
Transactions SPDD and SPAU.
B. Support Packages: Types
Definition
A Support Package corrects errors in the SAP System or makes necessary adjustments, for example,
due to legal changes. The objects affected are replaced in your system.
Each Support Package is valid for only one release (but for all databases and operating systems) and
requires an exactly defined number of predecessors. The upgrade of the following release or
correction release contains all the Support Packages of the previous versions that were available up to
the delivery of the upgrade.
SPAM makes sure that Support Packages are imported only in the specified order.
To prevent errors from occurring, you should import every Support Package as soon as it becomes
available. This keeps your system up-to-date.
Types
The following types of Support Packages are available:

• SPAM/SAINT Update
A SPAM/SAINT Update (PAT) contains updates and improvements to the SAP Patch
Manager and the SAP Add-On Installation Tool.
• FCS Support Package
An FCS Support Package (FFD) updates an FCS system to its General Availability release so
that other Support Packages can be imported.
• Component Support Package
This type of Support Package (COP) is valid for one software component (SAP_BASIS,
SAP_HR, SAP_APPL, ...) and contains corrections to errors in the Repository and Dictionary
in this software component only. In addition to these corrections, Support Packages for the
SAP_HR component also contain adjustments due to legal changes.
Naming Convention:
Software Component Name
SAP_APPL R/3 Support Package
SAP_BASIS Basis Support Package
SAP_ABA Application Interface Support Package
SAP_HR R/3 HR Support Package
SAP_APO APO Support Package
• BW Support Package
A BW Support Package (BWP) is a Support Package for the software component SAP
Business Information Warehouse (SAP_BW) and only contains corrections for this
component.
• Add-On Support Package

Area SAP Basis
An Add-On Support Package (AOP) is valid for an add-on with a particular release and
contains corrections for this add-on.
• Conflict Resolution Transport ( CRT )
A Conflict Resolution Transport CRT is exclusively used for add-ons, for example, IS-IS or IS-
OIL. It resolves conflicts that can occur between Support Packages and an add-on.
Note that a CRT that is valid for an add-on release also resolves all conflicts with earlier releases from
this add-on. A CRT can also contain other corrections for the relevant add-on. A CRT can also be a
special Add-On Support Package.
C. SAP Patch Manager ( SPAM )
Definition
The SAP Patch Manager (SPAM) is the customer side of the Online Correction Support (OCS).
Transaction SPAM lets you efficiently and easily import SAP-provided Support Packages into your
system.
Depending on the system used or the configuration of your system, you must apply different Types of
Support Packages. You can get the Support Packages in the SAPNet R/3 Frontend, the SAPNet Web
frontend, or on Collection CDs.
SPAM runs at the SAP transaction level, so that a knowledge of the operating system is not required
for handling the tool.
SAP now uses the term Support Package instead of patch.

Note that you can only use this transaction with SAP GUI for Java and SAP GUI for Windows.
Functions
The SAP Patch Manager offers you the following functions:
• Loading Support Packages:

You can load the Support Packages you need from the SAPNet Web Frontend, the SAPNet
R/3 Frontend, or from Collection CDs into your system.
• Importing Support Packages

o Restart capability
When you import a Support Package into your system, SPAM follows a predefined
sequence of steps.
If the Support Package process terminates, it can be resumed at a later point in time.
Processing restarts at the step that failed.
o Displaying the import status in your system
You can find the import status in your system at any time using Transaction SPAM.
Transaction SPAM is integrated into the SAP upgrade procedure.
D. SPAM Steps
The SAP Patch Manager informs you of the status of the step currently being executed in the status
bar. If you want to know which steps are executed for which scenario, run the program RSSPAM10.
The following list explains the steps executed by SPAM in the order in which they are performed.
1. PROLOGUE
In this step, the system checks if you are authorized to import Support Packages.

Area SAP Basis
2. CHECK_REQUIREMENTS
In this step, various requirements are checked for importing a Support Package, for example, the
transport control program tp logging on to your system.
3. DISASSEMBLE
In this step, files from the corresponding EPS parcels are disassembled, or unpacked, and stored in
the directory.
4. ADD_TO_BUFFER
In this step, the queue is put into the transport buffer of your system.
5. TEST_IMPORT
In this step, the system checks if there are still objects in tasks that have not yet been released and
are overwritten when the Support Package is imported.
6. IMPORT_OBJECT_LIST
In this step, the object lists for the Support Packages in the queue are imported into the system.
7. OBJECTS_LOCKED_?
In this step, the system checks if there are still objects in tasks that have not yet been released and
are overwritten when the Support Package is imported.
8. SCHEDULE_RDDIMPDP
In this step, the transport daemon (program RDDIMPDP) is scheduled.
9. ADDON_CONFLICTS_?
In this step, the system checks if there are conflicts between objects in the queue and installed add-
ons.
10. SPDD_SPAU_CHECK
In this step, the system checks if a modification adjustment is necessary (Transactions SPDD/SPAU).
11. DDIC_IMPORT
In this step, all the ABAP Dictionary objects of the queue are imported.
12. AUTO_MOD_SPDD
In this step, the system checks if modifications to the ABAP Dictionary objects can be adjusted
automatically.
13. RUN_SPDD_?
In this step, you are asked to adjust your modifications to the ABAP Dictionary objects by calling
Transaction SPDD.
14. IMPORT_PROPER
In this step, all the Repository objects and table entries are imported. Then actions such as
distribution, conversion, activation and generation occur.
15. AUTO_MOD_SPAU
In this step, the system checks if modifications can be adjusted automatically.
16. RUN_SPAU_?
In this step, you are asked to adjust your modifications to the Repository objects by calling Transaction
SPAU.
17. EPILOGUE
In this step, the import of the Support Package is ended. The system checks if the queue has been
completely processed.

Area SAP Basis
IMPORTING SUPPORT PACKAGES USING SPAM
Importing Support Packages takes place with the following phases:
Preparations
Retrieve Support Packages
Load Support Packages
Define Queue
Import Queue
If necessary: Adjust Modifications
Checks Logs
Confirm the Queue
Delete Unnecessary Files
A. Preparations
Before starting to apply Support Packages, check the following cases:
1. Logon the SAP System in Client 000.

Check the correct function of transport tools by choosing Utilities Check Transport
Tool.
2. Make sure that there is enough space under /usr/sap/trans File System.
For every Support Package, there must be ‘ 3 x Unpackes File Size ‘ space under transport
directory.
For example: SAPKA46C07 ( 7. ABAP SP )
FILE NAME DEFINITION DIRECTORY SIZE

Packed Support Package Any place on file
KA46C07.CAR 3,86 MB
File. system
Unpacked Ready-to-import
CSN0120061532_0006849.PAT /usr/sap/trans/EPS/in 3,86 MB
File.
Backup of Changed Data
RA46C07.<SID> /usr/sap/trans/data 3,86 MB
in SAP System.
Temporary files used
tmp files /usr/sap/trans/tmp 3,86 MB
during Import process.
Total 3 x 3.86 MB Space needed under /usr/sap/trans file system during import process.
3. Make sure there is enough space in Tablespaces and Tables for ORACLE and DB2 and in
Datafiles in MSSQL.
4. You have the newest SPAM update.
B. Retrieve Support Packages

Every Support Package is delivered in compressed file format ( *.CAR ) with the following naming
convention:
KXVVVNN.CAR
X = Application Component Type ( A: ABAP, APO, B:BASIS, BW, H: APPL, … )

VVV = Application Version ( 40B, 46C, 46D, 610, … )

Area SAP Basis
NN = Patch Number
Example: ABAP Support Package 7 has a file name KA46C07.CAR
SAP is delivering Support Packages with several ways:
1. Via Support Package Collection CDs.

You can order Collection CDs, via SAPNET ( alias SWCAT )
2. Via Online Correction Support System. Now named SAP Software Center.
Use HTTP Address http://service.sap.com/swcenter or http://service.sap.com/swcenter-main to

download support packages.
3. Via Online Support System ( OSS ).
C. Load Support Packages

You must load Support Packages before you can import them. SAP provides Support Packages in the
following locations.
Support Packages from SAPNet or from Collection CDs are in a compressed format. You have to
unpack these Support Packages before you can process them further.
PROCEDURE
1. Load the Support Packages from SAPNet - Web Frontend or mount the right CD.
If you have downloaded Packages from SAPNET, then you have to put them in a directory on
Central Instance Server. ( use FTP, TFTP programs or programs such as CuteFTP ).
Figure 1

Area SAP Basis
You have to give access to <sid>adm user for those files.
# chmod 777 KB46C07.CAR

# chown hitadm:sapsys KB46C07.CAR
2. Log on using the following user
UNIX : <sid>adm
Windows NT : <sid>adm
3. Switch to the following subdirectory in your system:
UNIX : /usr/sap/trans
Windows NT : <Drive>:\usr\sap\trans
4. Unpack the archive containing the Support Packages using the following command:
UNIX : CAR -xvf /<CD_DIR>/<PATH>/<ARCHIVE>.CAR

Windows NT : CAR -xvf <CD_DRIVE>:\<PATH>\<ARCHIVE>.CAR
Figure 2
5. Now load the Support Packages into your system via SPAM menu path Support Package
Upload.

Area SAP Basis
Figure 3
System will ask you to upload Packages from /usr/sap/trans/EPS/in with the following pop-up screen (
Figure 4 ). You have to agree by pressing ENTER key.
Figure 4
Upload Log screen will be seen after process completed ( Figure 5 )
Figure 5
Now you have uploaded all the packages that are unpacked. Packages are ready to be included in
queues for Import.
D. Define Queue
The queue specifies which Support Packages are imported into your system by the SAP Patch
Manager and in which order.
If the queue is not completely defined, you must define the queue from the Support Packages
available.
If the queue is already completely defined, this is then displayed; you cannot change the selection
anymore. However, you can delete the queue completely by choosing Delete queue.

Area SAP Basis
If you delete the queue after objects have already been transported (for example, after an
error in step DDIC_IMPORT), your system will be inconsistent. Only delete in these SPAM
steps to correct errors and import the Support Packages again as soon as you can.
Transaction SPAM ensures that only the Support Packages appropriate for your system appear in the
queue. Support Packages that are meant for another release or add-on do not appear in the queue,
even if they were loaded into your SAP System. For more information, see Rules for the Queue.
PROCEDURE
1. To define a queue, call Transaction SPAM and choose Display/define. The Component
selection dialog box appears ( Figure 6 ).
Figure 6
2. The list of installed software components (for example, SAP_BASIS, SAP_HR, SAP_BW,
Add-On) appears. Select the relevant components.
3. The available queue appears ( Figure 7 ). This queue contains the Support Packages
available for the selected components in your system, and, if necessary, the Conflict
Resolution Transports (CRTs) and other Add-On Support Packages.
Figure 7

Area SAP Basis
You have to choose Support Packages one-by-one or in group according to OSS Notes
about related Patches.
Example Notes:
0173814 - OCS: Known problems with Support Packages Rel. 4.6
0097629 - OCS: Known problems with patches Rel. 4.5
4. Press F5 to Recalculate Queue, in order to avoid problems caused by Package files.
5. Now Queue for selected Support Packages is defined and Ready-to-Import ( Figure 8 ).
Figure 8
E. Import Queue
The SAP Patch Manager offers you 2 scenarios for importing Support Packages or a queue:
i. Test scenario
Use the Test scenario before actually importing the Support Package or queue to determine if
conflicts or problems arise (for example, repairs that have not been released), or if a
modification adjustment is necessary.
The scenario enables you to estimate and perhaps minimize the time and energy needed to
import Support Packages. In this scenario, no data is imported into the system and if an error
occurs, you can also continue the process without correcting the error.
You must choose the Test scenario explicitly.
ii. Standard scenario

Area SAP Basis
In this scenario, the Support Packages in the queue are completely imported. If an error
occurs, you can only continue and end the application successfully if the error is corrected.
PROCEDURE
1. Choose the scenario.
To choose the scenario you want, choose Extras Settings ( Figure 9 ).
Figure 9
2. Choose Support Package Import Queue ( Figure 10 ).
Figure 10
This function is also used to resume an aborted Support Package import.
The status line informs you of the progress of the application and the current steps of the SAP
Patch Manager ( Figure 11 ). You may be taken to modification adjustment (Transactions
SPDD, SPAU) during the import.

Area SAP Basis
Figure 11
If you import with the standard scenario, you must adjust Dictionary objects immediately
(Transaction SPDD). You can choose to skip the adjustment of Repository objects
(Transaction SPAU) and do it later.
F. Modification Adjustment
If you have modified SAP objects, you must adjust these objects when importing them. (Transaction
SPDD adjusts Dictionary objects, Transaction SPAU adjusts Repository objects.).
After finishing Main import of Support Request, SPAM Prompts you to adjust Modifications. In this
case, your Developers have to check validity of modifications. If applied support packages already
includes modification corrections, then you or your developers can return modificated objects to SAP
Standart.
But if modifications still needed, and future support packages will solve the problems, then you must
keep those modifications.
G. Check Logs
The function Queue logs displays logs for SPAM steps that the transport control program tp uses.
After successfully importing the queue, check these logs each time ( Figure 12 ). Following Log
Phases produced during import of a support package.
PHASE NAME LOG STEP

DISASSEMBLE_PATCH Generate transport information
file
TEST_IMPORT Test import
IMPORT_OBJECT_LIST Import request piece list
DDIC-IMPORT Import Dictionary objects
IMPORT_PROPER Dictionary activation
Import
Method execution
To display logs Goto Logs Queue in the initial screen of SPAM.

Area SAP Basis
Figure 12
Return Codes:
RETURN CODE MEANING

0 or 4 System information and warnings
Warnings are generally not critical for the system. Check them however, since
sequence errors may occur in exceptional cases.
Greater than 4 Serious errors that must be corrected before you can successfully import the
Support Package.
H. Confirm Queue
Confirm the successful application of the queue in your system. This ensures that other Support
Packages can be imported in the future. Another Support Package cannot be imported without a
confirmation.
If you have not yet confirmed Support Packages that were imported successfully, you will be asked to
confirm these Support Packages when the system is upgraded.
Confirm the successful import of the Support Package in your system by choosing Support
Package Confirm.
I. Delete Unnecessary files after Patch Application

After you’ve finished applying Support Packages, certain files can be deleted from Operating System
of Central Instance to increase free space under /usr/sap/trans file System.
Those are :
File System Files that can be deleted

/usr/sap/trans/EPS/in All files
/usr/sap/trans/data Files whose extension is SAP ( *.SAP )
/usr/sap/trans/cofiles Files whose extension is SAP ( *.SAP )
/usr/sap/trans/log Files which have name starts with SAP (
SAP*.<SID> files )
J. Applying Patches in a 3 – System Landscape
When applying patches, you may need to perform modification adjustments using Transactions SPDD
and SPAU. Modifications to ABAP Dictionary objects that are adjusted with SPDD can currently be
included in a change request but cannot be used for automatic adjustment during SPDD in the

Area SAP Basis
subsequent systems. Thus, the SPDD adjustment has to be repeated manually on each system in the
system landscape ( Figure 13 ).
Note that the enhancement concept covers also append structures for ABAP Dictionary objects that
are not recognized as modifications. Modification adjustment to Repository objects performed with
SPAU can be included in appropriate change requests.
To determine in advance whether a modification adjustment is necessary, perform a test import using
the test scenario ‘T’ in the SAP Patch Manager.
After the patches have been applied to the development system, they can be applied to the quality
assurance system and subsequently to the production system. After patch application (not before),
import the SPAU adjustments created in the development system using the change requests.
Figure 13


Applying Ocs Patches: Type Area Topic Author

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Applying Ocs Patches: Type Area Topic Author

Загружено:

Авторское право:

Доступные форматы

Type Handbook Document

Area SAP Basis

APPLYING OCS PATCHES

All Rights Reserved.

BASIC TERMS AND CONCEPTS ....................................................3

All Rights Reserved.

BASIC TERMS AND CONCEPTS

A. Hierarchy Of SAP Software Conponents

All Rights Reserved.

B. Support Packages: Types

The following types of Support Packages are available:

Software Component Name

SAP_APPL R/3 Support Package

SAP_BASIS Basis Support Package

SAP_ABA Application Interface Support Package

SAP_HR R/3 HR Support Package

SAP_APO APO Support Package

All Rights Reserved.

C. SAP Patch Manager ( SPAM )

SAP now uses the term Support Package instead of patch.

The SAP Patch Manager offers you the following functions:

• Loading Support Packages:

• Importing Support Packages

All Rights Reserved.

All Rights Reserved.

IMPORTING SUPPORT PACKAGES USING SPAM

Importing Support Packages takes place with the following phases:

Before starting to apply Support Packages, check the following cases:

1. Logon the SAP System in Client 000.

FILE NAME DEFINITION DIRECTORY SIZE

4. You have the newest SPAM update.

B. Retrieve Support Packages

X = Application Component Type ( A: ABAP, APO, B:BASIS, BW, H: APPL, … )

All Rights Reserved.

Example: ABAP Support Package 7 has a file name KA46C07.CAR

SAP is delivering Support Packages with several ways:

1. Via Support Package Collection CDs.

Use HTTP Address http://service.sap.com/swcenter or http://service.sap.com/swcenter-main to

3. Via Online Support System ( OSS ).

C. Load Support Packages

All Rights Reserved.

You have to give access to <sid>adm user for those files.

# chmod 777 KB46C07.CAR

2. Log on using the following user

3. Switch to the following subdirectory in your system:

UNIX : CAR -xvf /<CD_DIR>/<PATH>/<ARCHIVE>.CAR

All Rights Reserved.

Upload Log screen will be seen after process completed ( Figure 5 )

All Rights Reserved.

All Rights Reserved.

4. Press F5 to Recalculate Queue, in order to avoid problems caused by Package files.

You must choose the Test scenario explicitly.

ii. Standard scenario

All Rights Reserved.

2. Choose Support Package Import Queue ( Figure 10 ).

This function is also used to resume an aborted Support Package import.

All Rights Reserved.

PHASE NAME LOG STEP

To display logs Goto Logs Queue in the initial screen of SPAM.

All Rights Reserved.

RETURN CODE MEANING

I. Delete Unnecessary files after Patch Application

File System Files that can be deleted