SUPPORT PACKAGES:
Support packages or support stats provides enhanced functionality, changes to the existing data dictionary elements, repository objects like reports programs, transactions etc.,
Support packages of various types, few of them are:
1) Basis support packages -> SAPKB620050
2) ABAP support packages -> SAPKA620050
3) APL support packages -> SAPKH470050
4) HR support packages 2324 -> SAPKE470050
In order to display the current support package level.
Go to system -> status -> click on Magnifier.
Then all the package levels will be displayed.
Pre-requisites for support packages:
There should be 2 Background jobs.
The latest SPAM/SAINT versions should be applied on the system.
There should be enough space to hold the support packages in EPS/in
There should be no aborted packages.
Support packages should be applied on this sequence of nos. of support packages level.
Upgrade the Kernel version if required.
Apply support packages in order of BASIS/ABAP/APPL/HR.
Technical and functional consultants need to be informed while applying support packages because when the system updating DD elements, repository objects functional and technical objects. Functional and Technical team are the right people to advice whether to keep the existing functionality or move on the current functionality which comes in SP.
Scheduled down time and inform users.
Go through composite note thoroughly before applying support packages.
If the support package is more than 10MB, UNCAR the file using
o sapcar –xvf <filename>.sar.
When we uncar two files are generated with extension .ATT or .PAT.
When the support pack is aborted and could not be resolved the final remedy is to delete entries in the 2 tables.
Packages once applied cannot be reverted back.
If we want to revert, then contact SAP technical support.
Applying Support Packages or Patches:
1) Go to SPAM (SAP Patch Manager).
2) Load packages from the Presentation Server/Application Server.
3) Display all the new Support Patches to be applied (Queue).
4) Import the Queue or Display in Define Queue.
5) Support pack starts upgrading the system and it goes into various phases like TP Connect To DB, DDIC import , DDIC activation …(all these 27 steps can be found in PAT01) while applying support package, it stops to run the SPDD/SPAU.
SPAD:
This is the transaction which is used to update the data dictionary tables which applying SP. This is the phase where functional consultant assistance is required.
SPAU:
This is the transaction which is used to update the repository objects like programs, reports, functional modules while applying support packages. This is the phase where technical consultants required.
Note: If the objects are changed earlier with the help of SAP notes, Now these notes are parts of the support package which are modifying the system, during this scenario each and every object which was modified earlier with the help of the note are popped on the screen whether to keep the original or change to version.
Support packages or support stats provides enhanced functionality, changes to the existing data dictionary elements, repository objects like reports programs, transactions etc.,
Support packages of various types, few of them are:
1) Basis support packages -> SAPKB620050
2) ABAP support packages -> SAPKA620050
3) APL support packages -> SAPKH470050
4) HR support packages 2324 -> SAPKE470050
In order to display the current support package level.
Go to system -> status -> click on Magnifier.
Then all the package levels will be displayed.
Pre-requisites for support packages:
There should be 2 Background jobs.
The latest SPAM/SAINT versions should be applied on the system.
There should be enough space to hold the support packages in EPS/in
There should be no aborted packages.
Support packages should be applied on this sequence of nos. of support packages level.
Upgrade the Kernel version if required.
Apply support packages in order of BASIS/ABAP/APPL/HR.
Technical and functional consultants need to be informed while applying support packages because when the system updating DD elements, repository objects functional and technical objects. Functional and Technical team are the right people to advice whether to keep the existing functionality or move on the current functionality which comes in SP.
Scheduled down time and inform users.
Go through composite note thoroughly before applying support packages.
If the support package is more than 10MB, UNCAR the file using
o sapcar –xvf <filename>.sar.
When we uncar two files are generated with extension .ATT or .PAT.
When the support pack is aborted and could not be resolved the final remedy is to delete entries in the 2 tables.
Packages once applied cannot be reverted back.
If we want to revert, then contact SAP technical support.
Applying Support Packages or Patches:
1) Go to SPAM (SAP Patch Manager).
2) Load packages from the Presentation Server/Application Server.
3) Display all the new Support Patches to be applied (Queue).
4) Import the Queue or Display in Define Queue.
5) Support pack starts upgrading the system and it goes into various phases like TP Connect To DB, DDIC import , DDIC activation …(all these 27 steps can be found in PAT01) while applying support package, it stops to run the SPDD/SPAU.
SPAD:
This is the transaction which is used to update the data dictionary tables which applying SP. This is the phase where functional consultant assistance is required.
SPAU:
This is the transaction which is used to update the repository objects like programs, reports, functional modules while applying support packages. This is the phase where technical consultants required.
Note: If the objects are changed earlier with the help of SAP notes, Now these notes are parts of the support package which are modifying the system, during this scenario each and every object which was modified earlier with the help of the note are popped on the screen whether to keep the original or change to version.
No comments:
Post a Comment