Empowering Solution

Title Support Packages

Version 1.0

Author Kapil Bhati

Date 01.01.2014

Support Packages

BASIS Service

W

AD

DA

YA

S

OL

UT

IO

NS

P

ag

e

No

2

Table of Contents

1 Symptoms .......................................................................................................................... 3

2 Prerequisites ...................................................................................................................... 3

3 Solutions ............................................................................................................................ 4

4 References ........................................................................................................................11

Support Packages

BASIS Service

W

AD

DA

YA

S

OL

UT

IO

NS

P

ag

e

No

3

1 Symptoms: SAP Support package's are used to enhance the functionality or bug fixing in the program, it

contains a collection of error corrections. You can only import complete Support Packages

and in a specified sequence. Each correction in a Support Package is documented in an SAP

Note.

2 Prerequisites: Support package applied once cannot be reverted back, always apply support packages to

the level n-1, since developments still goes on with the latest patch level

Ex:- If the latest patch release are 54 better to have the patch 54-1=53

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.

i. SPAM and SAINT version should be latest.

ii. Maintenance Certificate should be valid.

iii. Go through the OCS (online correction support) note before doing support package.

iv. There should not be any aborted packages which were applied earlier.

v. Login to 000 client with user like DDIC.

vi. Suspend all background jobs using report BTCTRNS1 except background jobs like RDD*

jobs.

vii. There should be at least two background work process reserved for this process.

viii. Check for enough space in eps/in directory (os level) \\usr\sap\trans\eps\in take successful

backup.

ix. Functional and technical consultants should be around for applying changes to data

dictionary and repository objects

x. Take the database backup before going to apply support packages

xi. There should be enough space in tablespace (DB02) (If any tablespace is > 90% add data

file )

xii. Apply patches in the sequence defined in the composite note. Patches can be applied

individually or bundled together.

xiii. Patches can not be revert by consultant, only SAP can revert the patches by developing a

negative patches if required.

xiv. Schedule downtime before going to apply support packages. Notify user through email or by

creating a message SM02 transaction.

xv. Lock all user’s, except BASIS Admin users, DDIC and SAP* for Make sure no user should

be logged on while performing support package.

Support Packages

BASIS Service

W

AD

DA

YA

S

OL

UT

IO

NS

P

ag

e

No

4

xvi. In order to avoid network congestion the files which are more than 10MB has to be applied

through “Application sever”. Patches which are less than 10MB can be applied through

“Front end”.

xvii. “tp” version should be latest and also upgrade the Kernel version.

xviii. Support package should be applied in the sequence of landscape, First in Dev system and

next apply in QAS for the consistency test and finally in PRD system.

xix. Note: You require the authorizations S_TRANSPRT and S_CTS_ADMIN to be able to run

transaction SPAM. These authorizations are part of authorization profile S_A.SYSTEM.

3 Solutions:

1. Click on Package level to know the existing level of the support packs and the add-ons.

Support Packages

BASIS Service

W

AD

DA

YA

S

OL

UT

IO

NS

P

ag

e

No

5

2. Go to transaction SPAM and Load the support packages from frontend if it is < 10 MB. The

support packages which are in the form of .car will be decompressed into eps/in directory.

Support Packages

BASIS Service

W

AD

DA

YA

S

OL

UT

IO

NS

P

ag

e

No

6

If the size is > 10mb, copy the support packages to /trans directory and uncar the support packages

using the below command

cmd>cd usr\sap\trans

> sapcar –xvf <filename>.car

The command SAPCAR will decompress the CAR file and put two files (with extensions .ATT and

.PAT in the /usr/sap/trans/EPS/in directory.

3. Click on "Display/define"

Support Packages

BASIS Service

W

AD

DA

YA

S

OL

UT

IO

NS

P

ag

e

No

7

4. A box will appear with the Support Package categories, Click on the category for the support

packages that you uploaded and it will list them in order. You can apply them individually or the

whole list at one time.

5. Go to support package click import queue (or) Click on truck icon.

6. Click on continue after importing in to the Queue.

Support Packages

BASIS Service

W

AD

DA

YA

S

OL

UT

IO

NS

P

ag

e

No

8

7. Click Continue..

8. Note :- While applying support packages it triggers two phases SPAU and SPDD

SPDD

When the support packages contains any changes in the data dictionary then this phase is invoked.

SPAU

When the support packages contains the changes related to repository objects SPAU phase is

invoked. it prompts whether to keep to existing changes modified by notes or adapt to changes.

Modification Adjustment During Import of Support Packages

Use : - If SAP modified objects that have also been modified by the customer, a modification

adjustment is executed in the transactions SPDD and SPAU during import of Support packages.

Procedure

As far as the modification adjustment is concerned, you use the common procedure described below

to import Support Packages:

Support Packages

BASIS Service

W

AD

DA

YA

S

OL

UT

IO

NS

P

ag

e

No

9

Create two change requests in the Workbench Organizer (transaction SE09), one for the

modification adjustment with transaction SPDD and the other one for the modification

adjustment in transaction SPAU.

Create a task for each developer who is involved in the modification adjustment.

The developers must use transactions SPDD and SPAU to determine whether to retain or

delete the modifications.

After modification adjustment is finished, the developers must release their tasks.

Use transaction SPAM to access the SAP Patch Manager.

Choose Patch -> Import Patch Queue. A confirmation dialog window appears.

Choose Enter to finish the import process of the Support Package.

Release the change requests that result from the modification adjustment using transactions

SPAU and SPDD. At a later time, you can use the change request of transaction SPAU to

import the modification adjustment after this patch queue has been imported into other SAP

Systems within the system landscape. You cannot use the change request of transaction

SPDD to avoid the required SPDD adjustment during import into other systems. You must

always re-adjust the Dictionary manually. However, you should still transport the change

request to ensure that identical modifications are made in all SAP systems. Before importing

the change request resulting from the modification adjustment with transaction SPAU or with

transaction SPDD during import of a patch queue into the subsequent systems, import the

patch queue itself.

9. It prompt you the Queue is imported successfully and ask to confirm the queue.

Support Packages

BASIS Service

W

AD

DA

YA

S

OL

UT

IO

NS

P

ag

e

No

1

0

10. Go to -> SPAM -> Support Package -> Confirm the Queue

This shows the support package has implemented for the one of the queue and you need to do the

same as for the other queue (software components).

Post processing for support package

1. Check if any alerts or error messages in SICK and SM21.

2. Release all the background jobs (BTCTRNS2).

3. Unlock all the users.

4. Run SGEN ( SGEN compiles all programs.SGEN reduces abap load on the system).

5. Take a successful backup.

Problems While Applying Support Packages

Tablespace overflow.

Max extents reached.

Archive struck.

Kernel outdated.

SPAM/SAINT outdated.

No enough space in eps/in directory.

Support Packages

BASIS Service

W

AD

DA

YA

S

OL

UT

IO

NS

P

ag

e

No

1

1

"tp" could not connect to database (Execute R3trans –d which will generate trans.log)

STMS configuration should be consistent.

"tp" and "R3trans" is outdated or obsolete or corrupted which needs to be updated.

Check environmental variables.

RDDIMPDP job not scheduled

Objects conflict b/w the packages

Inconsistent in TMS

Background jobs is terminated with memory related issue.

4 References: [1] http://help.sap.com