Apply service pack SAP

8/11/2019 Apply service pack SAP

http://slidepdf.com/reader/full/apply-service-pack-sap 1/16

Type Handbook Document

Area SAP Basis

Topic Applying OCS Patches

Author Huseyin Bilgen

All Rights Reserved.

Copyright 2001-2002. Page 1 of 16

V 1.1

APPLYING OCS PATCHES




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





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 usingTransactions 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) andrequires an exactly defined number of predecessors. The upgrade of the following release orcorrection release contains all the Support Packages of the previous versions that were available up tothe 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 becomesavailable. 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 PatchManager 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 Dictionaryin this software component only. In addition to these corrections, Support Packages for theSAP_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 thiscomponent.

• Add-On Support Package




Area SAP Basis





An Add-On Support Package (AOP) is valid for an add-on with a particular release andcontains 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 fromthis add-on. A CRT can also contain other corrections for the relevant add-on. A CRT can also be aspecial 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 yoursystem.

Depending on the system used or the configuration of your system, you must apply different Types ofSupport Packages. You can get the Support Packages in the SAPNet R/3 Frontend, the SAPNet Webfrontend, or on Collection CDs.

SPAM runs at the SAP transaction level, so that a knowledge of the operating system is not requiredfor 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 SAPNetR/3 Frontend, or from Collection CDs into your system.

• Importing Support Packageso Restart capability

When you import a Support Package into your system, SPAM follows a predefinedsequence 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 statusbar. 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_REQUIREMENTSIn this step, various requirements are checked for importing a Support Package, for example, thetransport control program tp logging on to your system.

3. DISASSEMBLEIn this step, files from the corresponding EPS parcels are disassembled, or unpacked, and stored inthe directory.

4. ADD_TO_BUFFERIn this step, the queue is put into the transport buffer of your system.

5. TEST_IMPORTIn this step, the system checks if there are still objects in tasks that have not yet been released andare overwritten when the Support Package is imported.

6. IMPORT_OBJECT_LISTIn 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 andare overwritten when the Support Package is imported.

8. SCHEDULE_RDDIMPDPIn 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_CHECKIn this step, the system checks if a modification adjustment is necessary (Transactions SPDD/SPAU).

11. DDIC_IMPORTIn this step, all the ABAP Dictionary objects of the queue are imported.

12. AUTO_MOD_SPDDIn this step, the system checks if modifications to the ABAP Dictionary objects can be adjustedautomatically.

13. RUN_SPDD_?In this step, you are asked to adjust your modifications to the ABAP Dictionary objects by callingTransaction SPDD.

14. IMPORT_PROPERIn this step, all the Repository objects and table entries are imported. Then actions such asdistribution, conversion, activation and generation occur.

15. AUTO_MOD_SPAUIn 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 TransactionSPAU .

17. EPILOGUE

In this step, the import of the Support Package is ended. The system checks if the queue has beencompletely 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 transportdirectory.For example: SAPKA46C07 ( 7. ABAP SP )

FILE NAME DEFINITION DIRECTORY SIZE

KA46C07.CARPacked Support PackageFile.

Any place on filesystem

3,86 MB

CSN0120061532_0006849.PATUnpacked Ready-to-importFile.

/usr/sap/trans/EPS/in 3,86 MB

RA46C07.<SID>Backup of Changed Datain SAP System.

/usr/sap/trans/data 3,86 MB

tmp filesTemporary files usedduring Import process.

/usr/sap/trans/tmp 3,86 MB

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 inDatafiles 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 namingconvention:

KXVVVNN.CAR

X = Application Component Type ( A: ABAP, APO, B:BASIS, BW, H: APPL, … )VVV = Application Version ( 40B, 46C, 46D, 610, … )






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 3System 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 inqueues for Import.

D. Define Queue

The queue specifies which Support Packages are imported into your system by the SAP PatchManager and in which order.If the queue is not completely defined, you must define the queue from the Support Packagesavailable.If the queue is already completely defined, this is then displayed; you cannot change the selectionanymore. 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 thequeue. 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 Packagesavailable for the selected components in your system, and, if necessary, the ConflictResolution 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.60097629 - 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 ifconflicts or problems arise (for example, repairs that have not been released), or if amodification adjustment is necessary.

The scenario enables you to estimate and perhaps minimize the time and energy needed toimport Support Packages. In this scenario, no data is imported into the system and if an erroroccurs, 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 erroroccurs, 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 SAPPatch Manager ( Figure 11 ). You may be taken to modification adjustment (TransactionsSPDD, 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. (TransactionSPDD adjusts Dictionary objects, Transaction SPAU adjusts Repository objects.).

After finishing Main import of Support Request, SPAM Prompts you to adjust Modifications. In thiscase, your Developers have to check validity of modifications. If applied support packages alreadyincludes modification corrections, then you or your developers can return modificated objects to SAPStandart.But if modifications still needed, and future support packages will solve the problems, then you mustkeep 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 informationfile

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 warningsWarnings are generally not critical for the system. Check them however, sincesequence errors may occur in exceptional cases.

Greater than 4 Serious errors that must be corrected before you can successfully import theSupport Package.

H. Confirm Queue

Confirm the successful application of the queue in your system. This ensures that other SupportPackages can be imported in the future. Another Support Package cannot be imported without aconfirmation.

If you have not yet confirmed Support Packages that were imported successfully, you will be asked toconfirm these Support Packages when the system is upgraded.

Confirm the successful import of the Support Package in your system by choosing SupportPackage Confirm.

I. Delete Unnecessary files after Patch Application

After you’ve finished applying Support Packages, certain files can be deleted from Operating Systemof 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 SPDDand 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 thatare 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

Documents

Apply service pack SAP