Online Tutorials & Training Materials |
Register Login

SAP Support Package implementation activities and Processing

19 Jul 2012 10:27 am || 1

SAP Support Package Implementation

Prepared By: Manjunath Basappa 

Please contact me, in case of need my help: Official Number: 98455 13071 (Personal Number: 99022 54554) (Morning : 8am to 9pm)


As per request from Business and Application team Basis will be implementing SAP support packages.

SAP account to be used for application:

- Adminmxb is equivalent to SAP* or DDIC account) in client 000 (do not use SAP* or DDIC)


  1. Discuss with Business Data owner / Information owner, if you are in upper management position, else discuss with immediate supervisor
  2. List out the activities and call for meeting and invite team members, team leaders & supervisor
  3. Initiate ITIL process and minor change management ticket
  4. Call for Cab meeting and share the activities
  5. Document the back out plans, Quality Test, Communication Plan, implementation plan, Testing plan etc.,
  6. Get the approval from business management
  7. Send communication to service desk team for circulation of downtime activities communication (Only for Production Server)
  8. Schedule activities and keep in loop of all team members and supervisors

 Pre-Processing 1 

1.     Get support package numbers to apply

2.     Check OSS notes for known problem/conflict with support packages

1)     Check if any known problem/conflict with the given support packages is reported

OSS 672651 (OCS: Known problems with Support Packages in Basis Rel.6.40) at least, and some more related OSS notes.

2)     Find solution for the reported issue and have a discussion how to solve it before/after support package application.

Pre-Processing 2

1.     Check free space of /usr/sap/trans filesystem and upload all the *.CAR (Support Package) files to this directory

2.     Execute SAPCAR –xvf to move all packages from to /usr/sap/trans/EPS/in

usmsapd1:dvladm 5> SAPCAR -xvf KD64036.CAR

processing archive KD64036.CAR...

x EPS/in/CSR0120031469_0039468.ATT

x EPS/in/CSR0120031469_0039468.PAT

3.     Check status of Service Centre change ticket

4.     Confirm SAP account and password

- Client 000:  

- Client 100:

1)     Confirm that SAPSUPER accounts in client 000 are available and password is known.

5.     Check status of ‘TCC Service tools Update’ (RTCCTOOL)

SE38 > RTCCTOOL, Note the reported errors if any

6.     Decide queues of support package and sequence of them

7.     Read through ‘SAP_Kernel_Update_Procedure.doc’

Pre-Processing 3 (two days in advance)

1.     Set System Message

2.     Confirm that Online DB Backup job is scheduled for one day before SUPPORT PACKAGE application

3.     Request Application team to have all modified objects released

* This applies only to development system

SAP kernel upgrade (on the implementation day)

1.     Refer to ‘SAP Kernel Update Procedure.doc’ and upgrade SAP kernel to 640_274 using kernel bundle

SAPEXE_274-20000196.SAR (non-Unicode).

SAPEXEDB_274-20000198.SAR (non-Unicode).

2.     No SGEN is required

Support Package application (on the implementation day)

1.     Confirm that online DB backup is successfully completed

If not, decide whether you schedule another DB backup or proceed and use previous successful DB backup and REDO log files in case of backout.

2.     Wait for the BW synchronization

3.     Stop SAP instance in all servers (in both DB and APP servers)

To terminate all user sessions and running batch jobs in the system

4.     Switch log file to have a check-point in case of back-out

1)     Switch log file

select sequence#,group#,thread#,bytes,members,archived,status from v$log;

alter system switch logfile;

2)     Note down the REDO log file number

3)     Run backup_logs.ksh

5.     Lock all users except application and basis users from database level.

6.     Start up SAP instance in DB server

7.     Check V3 updates

SE38 -> RSM13005 -> Execute -> Check 'Outstanding Collective Runs' -> Execute

8.     Take a snapshot of all the released, ready & active jobs within the outage window and set all released jobs to scheduled


SM37 -> Check if there is any job with status released. If any, run BTCTRNS1 again.

9.     Upgrade SPAM

10.  Apply support Packages

1)     Choose No-Downtime operation

2)     SPDD

* Modification/adjustment must not be done.

- Click ‘Call SPDD’ -> Save displayed SPDD list in text format (System > List > Save > Local file > unconverted) -> Click back space button (DO NOT click any other button) -> Click ‘Yes’ on pop-up window ‘ABAP Dictionary is being activated. Do you want to continue?’

3)     SPAU

* Modification/adjustment must not be done.

- Click ‘Call SPAU’ -> Click ‘Execute’ button -> Expand displayed tree and save SPAU list in text format (System > List > Save > Local file > unconverted) -> Click back space button (DO NOT click ‘Confirm Adjustment’ button)

4)     Inform Application team for any SAP application-related issue if any

- Send an e-mail with findings, such as error message, object name, update date of the object etc


1.     Run RTCCTOOL

- Click ‘Save’ on pop-up window ‘Setting for RTCCTOOL’ -> Click ‘Addon & Upgr.’ Button if there is any red signal -> Click ‘Procedure after addon implementation’

- Fix the reported issue.

2.     Run SGEN

* For  Non-Production systems

Option: Generate all objects of selected software components

(Always select all components regardless of which support packages you applied)

 * For Production system

Option: Regenerate Existing Load -> Only Generate objects with invalidated loads

Re-run SGEN if it fails until successfully completed

3.     Restart SAP instance in DB server

4.     Start up SAP instance in all application servers

* No system has application server.

Confirm that SAP instance is running on all DB/AP servers

5.     Release jobs SE38 -> BTCTRNS2

SM37 -> Check if there is any job with status released/susp.

If any, run BTCTRNS2 again.

6.     unlock users

7.     Run Online Backup and Monitor

8.     Handover system.



1.     Support package queues and their sequence


1)     SAP_BASIS   : SAPKB64022 to 24                        :  11:40 – 13:07 min

2)     SAP_ABA      : SAPKA64022 to 24                        :  13:08 – 13:22 min

3)     PI_BASIS       : SAPKIPYJ6D to 6I                        :  13:24 – 13:30 min

4)     PI_BASIS       : SAPKINBC8A (SAINT)                   :  13:35 – 14:15 min

5)     PI_BASIS       : SAPKIPYL01 to 08                        :   13:35 – 14:15 min

6)     SAP_BW       : SAPKW35022 to 24                       :   14:15 – 14:20 min

7)     SAP_APPL    :  SAPKH50019 to 21                        :   14:25 – 15:15 min

8)     PI                  : SAPKIPZI6H to 6I                          :   15:15 – 15:20 min



  • 27 Aug 2012 6:30 am
    Hello Mr Manjunath,
    This is Arul discussed with you last week regarding SAP,
    I have gone through your report & found lot of useful datas.
    You refered book ADM100 by amit butola & i have refered the book contains data about SAP admin software.
    I am exp in manufacturing with enduser exp & planning to do PP functional module.

    As discussuion had with you said,refer ADM100 book & your learnabapin21days & regular practice.
    How this will help my needs especially in SAP PP functional.
    Is it posted learnabapin21days in SAP techies?

    I hope your response will do the valuable time in my career plan.

    Thanks & regards,
    Arul N