Complete procedure to appy Support Package in ECC

Hi
Could anybody send me a document that describes the complete procedure of applying support packages in ECC systems (Version 5.0)? I would like to specifically know the prerequisites and the checks that are required before patching.
Thanks in Advance

Its always better to do these before applying support packs
1) Update the kernel to latest level. If you cant do that at least update tp and R3trans
2) Update SPAM/SAINT to latest level
3) Read all notes related to your release from OSS , you can see something like Known Problems in support packs in 640/620 etc. That note will give you the recommended queue for support packs
Thanks
Prince Jose

Similar Messages

Installing support package 16, 17 and 18 for Netwever 7.0 (ECC 6 EHP 3 )

Hi I just want to know if we can directly load SP for Netweaver 7.00. I just went through some doc but they said we can upload SP directyl from SPAM tcode. can we install it from SPAM tcode i have component SAP_BASIS SP 16, 17 and 18. i downloaded SP using Solution manager i am at implementation phase in the same. i am bit confused should i proceed with SPAM ( but i tried upload package option is greyed out there).
any suggestion will be appreciated.
Mani

Hi Mani,
Follow this,
http://help.sap.com/saphelp_nw70/helpdata/EN/a7/a7a932845c11d2b421006094b9ea64/frameset.htm
- 000 client
- modifiable status of client.
- don't use DDIC/SAP*, use a user with full authorization
Question on Appying NW Support Package Stack
Please note that both individual Support Packages and SP Stacks are Non-cumulative. This means that, when you import Support Packages, then you import a gap less series of Support Packages and, if
you use SP Stacks, you also import these without a gap. The only exception is the Support Package for SPAM itself. & Java support packages which comes in SCA format.
Uday, Did you try to copy from what I posted?.. the correct procedure would be to direct to the original link.. not CTRLC & CTRLV!
Regards,
Debasis.
Edited by: Debasis Sahoo on Apr 22, 2009 1:04 PM

Support Packages Execution consuming too long time to get complete

Hi,
I installed the SAP Solution Manager 4.0 SR1, I have downloaded the support package stack till june 2007, and applied it. while importing I faced one error XPRA_EXECUTION, Resolved it (by refering sap note:979594) and again click on import. Now it is post 2 and the half day, the execution is still under process. Displaying status as "tp buffer prepared OK". Can anyone tell me how much time it will take to complete.

I have found these errors in tp log can any tell me the solution
WARNING: /usr/sap/trans/tmp/N110531.PRO : cant open
WARNING: : cant open
WARNING: /usr/sap/trans/tmp/N110531.PRO : cant open
WARNING: : cant open
STOP tp_getprots PRO Y 20110531061009
WARNING: /usr/sap/trans/tmp/N110531.PRO : cant open
WARNING: /usr/sap/trans/tmp/N110530.PRO : cant open
WARNING: : cant open
WARNING: : cant open
unable to open the open the files...???

Basis Support package level of ECC 6.0

Dear All,
I use SAP Version ECC 6.0 (700 Kernel, 64bit) Database SQL.
My question is what should be the support package level of ECC 6.0? SAP recommends for the latest support package level always. But, whether the latest support package level will be stable?
We are in the blue print stage now, I haven't received any requirement from the fuctionals for the support package upgrade.
We have modules like, SD, MM, FI, FICO, HR, PS and CS.
Anyone worked with these modules who can provide me, the particular components related to these modules with the stable support pack level.
Thanks in Advance,
Abu Sandeep

Hi,
Yes, for a new installation always go for the last support packages.
After going live, NEVER, NEVER apply support packages without qualifying them for YOUR company in a test system. It takes a lot of time to do non regression tests but it is mandatory IMHO.
Regards,
Olivier

Upgrade from 46c to ECC 6.0 new components support package

dear experts,
we have upgraded our test system from 46C to ECC 6.0
before upgrade in 46C we have support packages components
SAP_BASIS 46C
SAP_ABAP 46C
SAP_APPL 46C
SAP_HR
PI 2003_1_46C
SAP_NOTES 46C
ST-A/PI 01B_R3_46C
ST-PI 2005_1_46C
after upgrade to ECC 6.0 we found
SAP_ABA 700 0006
SAP_BASIS 700 0006
ST-PI 2005_1_700 0001
PI_BASIS 2005_1_700 0006
SAP_BW 700 0006
SAP_AP 700 0003
SAP_HR 600 0003
SAP_APPL 600 0003
EA-IPPE 400 0003
EA-HR 600 0003
EA-GLTRADE 600 0003
EA-PS 600 0003
EA-RETAIL 600 0003
EA-FINSERV 600 0003
EA-DFPS 600 0003
EA-APPL 600 0003
FINBASIS 600 0003
ECC-DIMP 600 0003
ERECRUIT 600 0003
FI-CA 600 0003
FI-CAX 600 0003
INSURANCE 600 0003
IS-CWM 600 0003
IS-H 600 0003
IS-M 600 0003
IS-OIL 600 0003
IS-PS-CA 600 0003
IS-UT 600 0003
LSOFE 600 0003
SEM-BW 600 0003
we are planning to apply SPS 06. Is it mandatory we have to apply
all the support packages in SPS 06.
we are confused as we dont use IS-OIL,EA-,ERECUIT,INSURANCE,FI-
please suggest which support packages we have apply relating to the
functionality we have in 46C
regards
Raghu

Hi,
you have to apply the same type of packages as before.
All other are included in ECC, but if you don't use the special services and applications (for example IS Oil or stuff like this), there is no need to apply all these packages.
SAP_ABA 700 0006
SAP_BASIS 700 0006
ST-PI 2005_1_700 0001
PI_BASIS 2005_1_700 0006
SAP_AP 700 0003
SAP_HR 600 0003
SAP_APPL 600 0003
should be enough
Regards
Timm

ECC 6.0 IDES - SUPPORT PACKAGES

Hi Friends.
I' SAP PP Consultant. I installed sap 46c ides, support packages and all of this stuff for long time. I just download the SP 54 in my 46c ides some weeks ago, but no new functionality i found in r/3.. so i fed up of r/3 46c
Now, I want to learn the new func of ECC6 (like xSOP, xSTEPS, SCM), so I just install the ECC 6 IDES (w2003 server, SQL5, Athlon X2 4200, 4gb ram, raid). My instalation is OK, about 9 hours.
I didnt install the Solution Manager (i found one solman ID in the SDN, thks BOB!!!).
My problem is the IDES 6 has Support Package 002, so i need to install the SP 3 to 10 (pr the last stack). When i try to download SP from Marketplace (as i did with 46c), i didnt.
I want to know if I can download this stuff or is a must to download via SolMan (as i read on the help).
PS, if there any "trick" pls explain me.

You need to configure "Maintenance Optimizer" in the Solution Manager (check the IMG for steps to do that).
You need an official S-User number to confirm your download basket, then you can download the SPs.
Markus

SAP Upgrade Assitant Support Package Problem 4.7 to ECC 6

Hi all,
Doing an upgrade from 4.7E to ECC 6. Does anyone know what should be the minimum patch level to start upgrade. Basis and Abap Supp. pack is on level 60. HR is on 61. But after starting prepare, it is giving error in version check phase. It is saying Upgrade Assitant the start release configuration is not supported. SAP_ABA : 620
SAP_APPL : 470
SAP_BASIS : 620
SAP_HR : 470
Infact all the support packages are at this level however the kernel is upgraded to 640 patch level 43.
If anyone has the info please help.. If ignored the upgrade assistant ask VALCHK_INI password which searched is nowhere found.
Kindly help.
Regards,
Valvan

Hello,
Thanks Eric I had already checked and they are above what is the minimum support pack level for eg SAP_BASIS requires minimum 41 support pack level and i have installed 61. Everything is according or more than the prerequisite requirement. Is this is a database version problem. Shall i go to upgrade oracle first as of now i am on 9.2.0.6.
Regards,
Shekhar Kulkarni

Customer exit is not functioning after ECC upgrade/support package

It seems our customer exit is not functioning after ECC upgrade/support package. I tried to activate the project again, no use. please help. Thanks! (see below for the enhancement info)
COZF0002 Change purchase req. for externally procured component
EXIT_SAPLCOZF_002
INCLUDE ZXCOZU02
*& Include           ZXCOZU02
CONSTANTS: lcc_eban(25)   TYPE c VALUE '(SAPLCOBC)EBAN'.
FIELD-SYMBOLS: <fs_eban>   TYPE eban.
DATA: l_fkstl TYPE prps-fkstl.
Move values from the LUW to the Internal Table
ASSIGN (lcc_eban) TO <fs_eban>.
If the field symbol is "NOT' empty then proceed
IF ( <fs_eban> IS ASSIGNED ).
if WBS work order, get cost center from PRPS
IF ( caufvd_imp-auart = 'ZM05' ).
    SELECT SINGLE fkstl INTO l_fkstl FROM prps
      WHERE pspnr = caufvd_imp-pspel.
    IF ( sy-subrc = 0 ).
      WRITE l_fkstl TO <fs_eban>-zzfistl.
    ENDIF.
if not WBS WO, move cost center minus leading zeros to funds center
ELSE.
    WRITE caufvd_imp-kostl TO <fs_eban>-zzfistl.
ENDIF.
ENDIF.

Did you mean set a break point in the follow code?(Include ZXCOZU02), I tried set a break point in this code, but It didn't stop .
*& Include ZXCOZU02
CONSTANTS: lcc_eban(25) TYPE c VALUE '(SAPLCOBC)EBAN'.
FIELD-SYMBOLS: <fs_eban> TYPE eban.
DATA: l_fkstl TYPE prps-fkstl.
Move values from the LUW to the Internal Table
ASSIGN (lcc_eban) TO <fs_eban>.
If the field symbol is "NOT' empty then proceed
IF ( <fs_eban> IS ASSIGNED ).
if WBS work order, get cost center from PRPS
IF ( caufvd_imp-auart = 'ZM05' ).
SELECT SINGLE fkstl INTO l_fkstl FROM prps
WHERE pspnr = caufvd_imp-pspel.
IF ( sy-subrc = 0 ).
WRITE l_fkstl TO <fs_eban>-zzfistl.
ENDIF.
if not WBS WO, move cost center minus leading zeros to funds center
ELSE.
WRITE caufvd_imp-kostl TO <fs_eban>-zzfistl.
ENDIF.
ENDIF.

Error in the phase IMPORT_PROPER while applying support packages

Dear All,
I am on ECC 6.0(ABAP+JAVA) SR2, SUSE Linux 10 SP1, DB2.
I have successfully applied the kernel patch and started applying the support packages, i have successfully completed applying the ABAP, Basis, BW, HR and other related patches, but i am not sure why i am stuck at the import_proper phase when applying the SAP_APPL patches (SAPKH60008 and SAPKH60009 both in the same queue) and my tp log is as follows
========================================================================================================
START imp all              SCD        20081229080538              DDIC         sealcpro 20081229080537
INFO: event SAP_IMPORT_START triggered successfully
INFO TBATG CONVERSION OF SCD N      not needed                  DDIC         sealcpro 20081229080537
START tp_getprots          SCD P      20081229080539              DDIC         sealcpro 20081229080537
2EETP000 sap_dext called with msgnr "1":
2EETP000      db call info
2EETP000 function:   db_setget
2EETP000 fcode:      RT_SETB (65535)
2EETP000 tabname:    TRBAT
2EETP000 len (char): 0
2EETP000 key:
2EETP000 retcode:    1
1AETP000 exit in function texitnow
ERROR: EXIT(16) -> process ID is: 5319
STOP imp all              SCD   0016 20081229080602              DDIC         sealcpro 20081229080537
=========================================================================================================
And also when i look at the Support package import logs they show that
TEST IMPORT
Import ABAP Dictionary Objects and
ABAP Dictionary Activation phases ended with return code 4
But i dont think this can give any problem.
I have tried to import from the phase where it stopped, but all of a sudden i get disconnected from SAP and get an error message saying that NO CONNECTION TO THE DATABASE, then when i check for the processes for dw and db2 there are process already running.
I had to start SAP and only then i was able to connect to the SERVER again.
Can you please help me on this..
For any more information plz let me know
Thanks and regards
Hunky

Dear Balaji,
Thank you very much for the reply...
I deleted the import request in the STMS and wi ran the RDDIMPDP and RDDMNTAB reports and restart the SPAM, but this time the SPAM immediately stopped, but i am still connected to the system and the error which i got earlier (database connection error ) is now not occuring.
But otherwise also i noticed that i get the following ABAP Dump while this error is triggering
===================================================================
DBIF_REPO_INTERNAL_ERROR
Internal error when accessing program "CX_SY_OPEN_SQL_DB=============CP ".
An unspecified internal error occurred in the SAP-internal
database interface.
For further analysis the SAP system log should be examined
(transaction SM21).
Check the entries in the developer trace of the relevant work process
(transaction ST11).
Attempted to access component "LOAD" of program
"CX_SY_OPEN_SQL_DB=============CP ".
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_REPO_INTERNAL_ERROR" " "
"SAPLSTPA" or " "
==========================================================================
Based on this error i searched few notes and got the below results 309583 and 132383 but these are not for my release.
So i request you to kindly help me on this as i am running out of time in delivering my server.
Waiting for all the valuble replies
Thank you in advance
Regards
Hunky

Solution Manager - Support Packages

Dear All,
       We are applying patch for our SAP Solution Manager 4.0. We are using SAP ECC 6.0, We already applied patch for our development and production servers.
     The following are the patch level in Solution manager
     BBPCRM             500          0007     SAPKU50007
     CPRXRPM     400          0007     SAPK-40007INCPRXRPM
     BI_CONT             703          0003     SAPKIBIIP3
     ST                     400          0010     SAPKITL420
     ST-A/PI     01I_CRM500     0000
     ST-ICO             150_700     0006     SAPK-15076INSTPL
     ST-SER             700_2006_2     0000
We downloaded all the above package, but struck in applying the patch. I want to know the hierarchy of the packages to apply, i confused in this level.
Could anybody let me know the order of above support packages to import.
Regards,
Sridhar S

As already mentioned, the best is to apply a complete Stack by the way you should do the complete job and update to EHP1 because your system will be still low in some SP's.
If you have done SP's installations per components and not per stacks then you could face problems after or during SP's installations so it will be way better to use the Stack Strategy.
But if you think you should go this way then in SPAM you can review New Packages and once there, every package will show up there prerequisites or level of the components (ex: SAPBASIS, ST_SER, ETC) that are necesary to be able to install any component SP's.
It is extremely important to read the Notes regarding the SP's, their dependencies and possible problems with some of them, for example, some SAPBASIS SP's cannot be applied alone or up to certain level because there are known problems and you should go one level up or down to avoid this problems.
Either way I have applied Stacks since they come out and it is better to use this strategy in our Solman with no problems at all.
Have a nice day,

Support package requierement for unicode conversion

We are currently planning a unicode conversion for a SAP 4.7enterprise 1.1 extension version, running under Aix and Oracle, Basis/ABAP SP 35, HR SP20.
According to the conversion guide, we must implement at least Support Pachage 60 for Abap and Basis, no explicit requierement for HR SP level.
I believed that we must applied SAP procedure and exclusively HR Support Package Stack up to 27, which include SP 60 for Basis and Abap and HR 61.
Our HR guys argue there is no indication from SAP that the SUPPORT PACKAGE STACK policy is mandatory and that SAP will provide us with normal support if we run the unicode conversion with SP Basis/ABAP 60, in other word even if we do not respect the support package stack combinaison. Need help on this issue before starting the project

Exterprise 4.7 is Unicode-Compliant,meaning that you can have unicode in 4.7.
If that the case, you should convert to 4.7 Enterprise Ext 2.00 Unicode First.
later only upgrade to ECC 6.0 after 2 years, as you said.
My answer is yes, to your question.
You can download the installation kits at:
http://service.sap.com/swdc
anyway, it is recommended to have the latest SP in your system.
cheers,
Vincent

Support Package and Delta/Extractor functionality

Hello Experts,
We have been testing the New GL Totals Delta and Extractor functionalities. Previously when Support Packege 13 was installed, the Delta was bringing incorrect results.
Now we are using Support Pack 15. Now if i post documents in ecc and upload to bi, the Delta is working properly and values match in ecc and bi.
Could you please suggest if there have been any changes or upgradations in the New GL Totals Delta/Extractor functionality between Support Packages 13 and 15.
Thanks and Regards,
Labanya.

Hi,
Its always better to drain the delta queues before an upgrade.
As a standard practice we drain the delta queues by running the IP/ chain multiple times.
As a prerequiste we cancel/reschedule the V3 jobs to a future date during this activity.
The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss.
V3 collector jobs should be suspended for the duration of the upgrade.
They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
See SAP Notes 506694 and 658992 for more details.
Page 17
Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
The SAP BW Service SAPI, which is used for internal and BW to BW data mart extraction, is
upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the
upgrade to avoid any possibility of data loss.
upgrade preparation and postupgrade checklist
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
/message/3221895#3221895 [original link is broken]
OSS notes 328181 and 762951 as a prerequisites.
Failure to follow the instructions in those notes may probably result in data loss.
https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
/thread/804820 [original link is broken]
thanks,
JituK

Support package upgrade / SPAU with multiple queues

Hello, We are upgrading our support package level on our ECC 6.0 system. I divided up the support packages into 4 different queues:
SAP_BASIS
SAP_ABA
PI_BASIS
ST-PI
SAP_BW
SAP_AP
SAP-HR
After importing each queue, I had a few things to do in SPDD and SPAU. I created a new SPDD or SPAU transport request for each queue. My question is now what is the recommended procedure to handle these SPAU/SPDD transport requests when you have multiple queues? I plan to define the same queues when doing QA and PRD. Do I mark all of the requests and then when I do each queue, I only specify that particular request? Thank you in advance for your help.
Best regards,
Russ Cook

Hi Russ,
when did you export the different SPAU requests or didn't you export them at all?
If the export happens only after all queues are already imported, this final system state (component version + SP level) is stored in the requests.You are then not able to include e.g. the request for the SAP_BASIS SPs into the SAP_BASIS queue, because the other components are still on the old version, while according to the request they should be on the newer state.
So, the right procedure would be; import the SP queue, do the modification adjustment for this queue, mark the workbench request as modification adjustment transport request and export this request. Then you can import the next SP queue.
Best regards,
Dirk

EHP and Support packages

Hello,
Im going through this document;
Master Guide ; SAP Enhancement Package 5 for SAP ERP 6.0 Powered by SAP NetWeaver
Using SAP Enhancement Package 5 for SAP ERP 6.0 and SAP NetWeaver 7 including Enhancement Package 2
Im having a point to clarify;
SAP enhancement packages have Support Packages of their own that are equivalent to the Support Package versions of the underlying SAP system.
We highly recommend installing the enhancement package in combination with the latest available Support Package stack. This approach reduces installation, modification adjustment, and testing effort. Using this strategy, you can install SAP enhancement packages as a normal maintenance activity together with Support Package stacks.
Whats meant by ;
SAP enhancement packages have Support Packages of their own that are equivalent to the Support Package versions of the underlying SAP system.
We highly recommend installing the enhancement package in combination with the latest available Support Package stack.
Can you help me to clarify this with an example
regards,
Zerandib

Hi,
Let me give you some basic example to make this statement clear.
We should first of all distinguish between the terms upgrade and update.
UPGRADE means from one Major release level to Another Major Release. Eg: R/3 46C to ECC 6.0
UPDATE means it can be either support package for installed components or Enhancement Packages for existing component.
Instead of upgrading the the entire RELEASE SAP has come up with EHP updates. This give you all major new changes without
doing a complete release upgrade. Also Downtime is reduced.
Consider this component
SAP_HR     470     0010     SAPKE47010      R/3 Enterprise 4.7 system
If this is upgraded to EHP 5 then the naming convention becomes
SAP_HR     605     0043     SAPKE60543      ECC 6.0 with EHP 5
Just like how we have support packages for each component. WE have support packs for the enhancement packages too.
More information can be pbtained in the below link
http://service.sap.com/erp-ehp
Refer to this SAP notes for further understanding.
1484460 EHP5 for SAP ERP 6.0 SP Stacks - Release & Information Note
1064635 SAP ERP Enhancement Packages: SP Stacks Release Info Note
1298878 Installation of SAP Enhancement Package 5 on SAP ERP 6.0
774615    Support Package levels of ERP/ECC installations/upgrades
I hope I was able to clarify your questions.
Regards,
Naveen.
Edited by: Naveen Kumar on Feb 29, 2012 10:41 AM

Why isn't bootcamp allowing me to partition my disk or allow me to download the windows support package?

When i go into bootcamp assistant it immediatly tells me
The disk cannot be partitioned because some files cannot be moved.
Back up the disk and use Disk Utility to format it as a single Mac OS Extended (Journaled) volume. Restore your information to the disk and try using Boot Camp Assistant again.
I have tried removing up to 10 gigabytes worth of imformation which doesnt seem to show up on the About this mac tab, but it says i have over 30 gigabytes open.
Also the windows support package gets stuck at the beginning and freezes half the time.
I have checked the disk utility and it says my hard drive is a Mac OS Extended (journaled) which is what it is telling me to change! i have no idea what to do. HELP

You will have to backup your OS X partition to an external drive, boot from the external drive, use Disk Utility to repartition and reformat your hard drive back to a single volume, then restore your backup to the internal hard drive.
Get an empty external hard drive and clone your internal drive to the external one.
Boot from the external hard drive.
Erase the internal hard drive.
Restore the external clone to the internal hard drive.
Clone the internal drive to the external drive
Open Disk Utility from the Utilities folder.
Select the destination volume from the left side list.
Click on the Restore tab in the DU main window.
Check the box labeled Erase destination.
Select the destination volume from the left side list and drag it to the Destination entry field.
Select the source volume from the left side list and drag it to the Source entry field.
Double-check you got it right, then click on the Restore button.
Destination means the external backup drive. Source means the internal startup drive.
Restart the computer and after the chime press and hold down the OPTION key until the boot manager appears. Select the icon for the external drive and click on the downward pointing arrow button.
After startup do the following:
Erase internal hard drive
Open Disk Utility in your Utilities folder.
After DU loads select your internal hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed. Do not quit Disk Utility.
Restore the clone to the internal hard drive
Select the destination volume from the left side list.
Click on the Restore tab in the DU main window.
Check the box labeled Erase destination.
Select the destination volume from the left side list and drag it to the Destination entry field.
Select the source volume from the left side list and drag it to the Source entry field.
Double-check you got it right, then click on the Restore button.
Destination means the internal hard drive. Source means the external startup drive.
Note that the Source and Destination drives are swapped for this last procedure.

Complete procedure to appy Support Package in ECC

Similar Messages

Maybe you are looking for