Reg upgrading SAP Support packs

Hi,
We have solution amnager 7.0 with release 700
For upgrading SPS to 18, we have to do SAP_BASIS 701 and other packages
As per my understanding, we just download the following installation component and upload in SAINT. Please confirm
SAPK-701DHINSAPBASIS--- SAP_BASIS 701 Upgrade

Hi,
Refer to below links,
Upgrade to SAP Solution Manager 7.0 EHP1
http://www.scribd.com/doc/26198618/Release-Notes-SAP-Solution-Manager-7-0-EHP-1
Regards,
Ravi

Similar Messages

BSI Tax Factory Upgrade:HR Support packs

Hi All,
We are starting with upgrade of BSI tax Factory from 8.0 to 9.0. And as per SAP main note '1469858' for upgrade, the support
pack required is 'HRSP61' but we currently have 'HRSP59'. Also, CLC 61 was applied for 2010 year end activities.
So, with CLC 61 present, would it be possible to upgrade to 9.0 without upgrading to HRSP 61 ?
In other words I want to confirm if CLC 61 includes the Tax Factory 9.0 updates.
Thanks,
Avinash

Hi Avinash,
I just updated relevant information for your query in the following thread:
[*BSI 8.0 becomes obsolete August 31st 2011, 9.0 troubleshooting guide here*;
Kind regards,
Felipe

SAP Support pack upgrade help!!!

Dear Experts ,
Am new into basis . My environment is ECC6 ehp4 with solman 7.0 ehp1 .
Right now my existing support pack stack is 19.
When i check in solman using MOPZ it shows the target stack as 20. when i checked the components in target stack it shows only few application component patches. No Basis & abap patches.
But i checked individually in service market place patches list . all components including application & technical components 4 more patches has been released.
1.My doubt is did support pack upgrade should be done using support pack stack only ?.
2.Abap & basis patches should be implemented separately based on the dependency of patches in Support pack stack ?
Kindly help me!!!!

Hello,
First of all you need to make sure your ECC6.0 system product type as ECC6.0 ERP4 under Product Systems --> SAP ERP Enhancement in SMSY. Once it's done, you need to click on "Read System Data Remote" to refresh ECC system component detail. Then after check MOPZ and you should be able to see the target stack level with all components.
Thanks,
Siva Kumar

SAP support pack upgrade

Dear Experts,
There has been a discussion with my colleagues to discontinue support pack upgrade. But we are not able to reach to any consensus. We would require your opinion on the same.
Background of the discussion:
Since we are using SAP-EH&S in highly customized manner, support pack causes more issues rather than improvements. Each time we have to invest lot of efforts while testing the system after support pack is applied. We have to stop all the development work for 2 months.
I need to know:
- What are the implications of discontinuing support pack upgrades?
- SAP will no longer provide support for current SAP-EH&S module after 2020. What possible issues can we face if no support pack upgrade is done? I believe after 2020 other module would be used, so we are looking for only next 5 years or so.
- Have there been any other module (highly customized) facing similar issues?
- Do we lose support from SAP if we don’t upgrade the system?
I tried to approach SAP as well but couldn't get a straight answer.
Thanks,
Apoorv Bhargava

Dear Apoorv
in regards of:
What are the implications of discontinuing support pack upgrades?
=> you will never get "legal updates". A support package is not only a "fix"; but sometimes SAP is delivering new solutions based on legal topics. Good example is "SVT". This is shipped with a Support Package only; you should not never ever try to implement the more than 100 OSS notes manually
=> you will never get "error" fixes; yes you can implement one OSS after the other (if neededI but this is the wrong approach
=> if you would like to do "major upgrade" (e.g. SAP 6.0 EnhPack7) you need to go through the whole process; and only by high level SAP releases you will get the "newest" functions
On the top only by installing SP or Upgrade you will get updates in property tree (only if you buy legal content from SAP the story would be different)
In regards of:
Background of the discussion:
Since we are using SAP-EH&S in highly customized manner, support pack causes more issues rather than improvements. Each time we have to invest lot of efforts while testing the system after support pack is applied. We have to stop all the development work for 2 months.
Be happy that you only need 2 months; in most cases more than that is needed,
In regards of:
SAP will no longer provide support for current SAP-EH&S module after 2020. What possible issues can we face if no support pack upgrade is done? I believe after 2020 other module would be used, so we are looking for only next 5 years or so.
Anybody has the same situation here. After 2020 clearly SAP must deliver a solution (alternative etc.); (and you can extend maintenance period as well)
- Have there been any other module (highly customized) facing similar issues? => I am pretty sure that SAP SD, SAP Mm etc. is the same story
- Do we lose support from SAP if we don’t upgrade the system? = in my opinion no. But if you need to strat OSS the story is always the same: they will come back and ask you to implement SP etc.
A lot of SAP services exists to help you in your situation. But you can help yourself. One option is;
a.) create first a "sandbox" with current SAP ERP release and prepare EHS
b.) then compare your set up to standard set up and list" differencies"
c.) start of analyzing: what can be done to get "closer" to standard
d.) start with "quick win" standardization and the generate a list of "subprojects" to take care the other differences so that may be after a short time (may be only one year) you are much closer to SAP standard
In regards of:
Since we are using SAP-EH&S in highly customized manner => as long as you are using only customizing you are in "Standard". There should be less problems in update/upgrade; only if you have adpated SAP codings etc. you have a problem.
C.B.
PS: may be check as well:Overview: SAP EHS Management in context of Enhancement Package / Support Package

Proper Plan for SAP Support Pack Upload

Hi Experts,
We are going for Support pack upload of SAP at your firm.
Like to get your suggestions on the Plan we have done for going with the update.
The Present Level of SAP in our server is very low 8 stacks low approx in both the Development Server and Production Server.
What is the best way to apply them from the below mentioned plan.
1. shall we go for 1 stack in Development for the required components then test it for 3-4 days then go for the same stack in Production. So that both the server go sync with each other. This way going till the target stack one by one.
2. shall we go and upload all 8 stacks for the components required in development first one by one and then test the system for all the errors available and then start with the Production. Will there be a transport problem if the system are not in sync for the so many days.
Please suggest which one shall be best suited if any other plan can be used for safe and proper update of Support pack.
Jitesh

Hi,
1. shall we go for 1 stack in Development for the required components then test it for 3-4 days
then go for the same stack in Production. So that both the server go sync with each other.
This way going till the target stack one by one.
If Large Support Stack gape is there, then
1. I would perform system copy of Existing Development System into another separate New Test Server.
2. Then , I will generate Side Effect Reports based on the Source-to-Target Support Stack gape. You can request such side effect from SMP at https://service.sap.com/side-effects by selecting the solution and by providing source to target SP level per component.
3.Refer The required SAP Notes regarding OCS Know problems for the support patches. Apply latest SPAM/SAINT Updates. Apply Latest SAP Kernel patches.
4. Apply the Required Support Package stack after taking successful offline backup of Database.
5. Perform SPDD - SPAU adjustment and record it in single/Multiple Change requests.
6. Ask the function team to check the Functionality in new Upgraded TEST system
7. After Confirmation from the Functional & Technical Team, Apply the same support package stack in existing real DEVELOPMENT system and move that SPAU-SPDD adjustment request.
2. shall we go and upload all 8 stacks for the components required in development first one by one
and then test the system for all the errors available and then start with the Production.
Will there be a transport problem if the system are not in sync for the so many days.
The same above steps will be applicable here also. Change Requests Transports are not recommended between the systems which are on different Support Patch Stacks. With the above mentioned steps your downtime as well as Development Holiday will be minimized.
Regards,
Bhavik G. Shroff

Upgradation of SUPPORT PACK in BI 7.0

Hi All,
We are using BI 7.0. and need to upgrade the Service pack from SP 14 to SP 16.
Can anyone please let me know
1. The Impact on the system we would be facing with this upgrade.
2. The things that need to be taken care - pre or post upgradation. Any check list or Test
Plan to take care after the upgrade.
Thanks in advance.
-- Maddy

Hi Kavitha,
Check these links:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10564d5c-cf00-2a10-7b87-c94e38267742
Bi7 upgradation.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10564d5c-cf00-2a10-7b87-c94e38267742
http://wiki.ittoolbox.com/index.php/Upgrade_BW_to_Netweaver_2004s_from_v3.0B
Up grade 3.5 to BI 7.0
Upgrading BW 3.X to SAP NetWeaver 2004s BI
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
/people/prakash.darji/blog
/people/prakash.darji/blog/2006/09/22/rolling-out-the-new-sap-netweaver-2004s-bi-frontend-tools
/people/prakash.darji/blog/2006/07/26/troubleshoot-the-sap-netweaver-2004s-bi-frontend-installation
/people/prakash.darji/blog
https://forums.sdn.sap.com/click.jspa?searchID=5046269&messageID=3148221
https://websmp103.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000586052&
https://forums.sdn.sap.com/click.jspa?searchID=5046269&messageID=3980419
3.x to 7.0 Upgrade
https://websmp208.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000586052&
https://wiki.sdn.sap.com/wiki/x/JYk
Hope this helps...................
Thanks=Points in SDN
Rgs,
I.R.K

Analysing SAP Support Packs

Hi,
This is a very general question. My company is currently on support pack 15 and we are going to apply 16-22 prior to a WM implementation. I have been tasked at looking at 16-22 to see what changes will apply to us in MM and PP.
I am unsure where to start! How do I access the information relating to these support packs please
Thanks

Hi
U can refer this limk.It will be helpful.
http://help.sap.com/saphelp_40b/helpdata/es/dc/1939516e36d1118b3f0060b03ca329/content.htm
Regards,
Raman

Test plan for upgrading the support packs

Dear friends,
We are going to upgrade the BI system with SP18.
Please let me know the impact system will be facing with this upgrade and the test plan to take care after the upgrade.
With Regards
Neetu
Edited by: Siegfried Szameitat on Oct 29, 2008 8:48 AM

Hi,
it will helps hopeful,
Upgradation steps:
1) Convert Data Classes of InfoCubes. Set up a new data class as described in SAP OSS Note 46272.
2) Pay attention to the naming convention. Execute the RSDG_DATCLS_ASSIGN report.
3) Run the report RSUPGRCHECK to activate objects.
4) Upgrading ABAP and JAVA in parallel may cause issues. If there is no custom development on J2EE instance, it is recommended to drop the J2EE instance and re-install the latest J2EE instance after the upgrade.
5) Apply SAP OSS Note 917999 if you include the Support Patch 6 with the upgrade or you will get the error at PARCONV_UPG phase. When you upgrade to a product containing Basis 700, the phase PARCONV_UPG terminates. You included Basis Support Packages up to package level 6 (SAPKB70006) in the upgrade. The job RDDGENBB_n terminates with the error RAISE_EXCEPTION. In addition to this, the syslog contains the short dump TSV_TNEW_PAGE_ALLOC_FAILED. The program SDB2FORA terminates in the statement "LOOP AT stmt_tab". An endless loop occurs when the system creates the database table QCM8TATOPGA.
6) Apply the OSS note 917999 if you get the following error during PARCONV_UPG phase: PARCONV_UPG terminates with TSV_TNEW_PAGE_ALLOG_FAILED
Critical OSS Notes:
819655 u2013 Add. Info: Upgrade to SAP NW 2004s ABAP Oracle
820062 - Oracle Database 10g: Patchsets/Patches for 10.1.0
839574 u2013 Oracle database 10g: Stopping the CSS services ocssd.bin
830576 u2013 Parameter recommendations for Oracle 10g
868681 u2013 Oracle Database 10g: Database Release Check
836517 u2013 Oracle Database 10g: Environment for SAP Upgrade
853507 u2013 Usage Type BI for SAP Netwaevers 2004s
847019 - BI_CONT 7.02: Installation and Upgrade Information
818322 u2013 Add. Info: Upgrade to SAP NW 2004s ABAP
813658 - Repairs for upgrades to products based on SAP NW 2004s AS
855382 u2013 Upgrade to SAP SEM 6.0
852008 u2013 Release restrictions for SAP Netweaver 2004s
884678 - System info shows older release than the deployed one
558197 u2013 Upgrade hangs in PARCONV_UPG
632429 u2013 The upgrade strategy for the add-on BI_CONT
632429 - The upgrade strategy for the add-on FINBASIS
570810 - The upgrade strategy for the add-on PI_BASIS
632429 - The upgrade strategy for the add-on SEM-BW
069455 - The upgrade strategy for the add-on ST-A/PI
606041 - The upgrade strategy for the add-on ST-PI
632429 - The upgrade strategy for the add-on WP-PI
Post upgrade Steps :-
1. Read the Post Installation Steps documented in BW Component Upgrade Guide
2. Apply the following SAP OSS Notes 47019 - BI_CONT 7.02: Installation and Upgrade 558197 - upgrade hangs in PARCONV_UPG, XPRAS_UPG, SHADOW_IMPORT_UPG2 836517 u2013 Oracle Database 10g: Environment for SAP Upgrade
3. Install the J2EE instance as Add-in to ABAP for BI 7.0 and apply the Support Patch that equivalent to ABAP Support Patch.
4. Run SGEN to recompile programs.
5. Install the Kernel Patch.
6. Missing Variants - (also part of test script) look at the RSRVARIANT table in SE16. If it is empty, then you will definitely need to run RSR_VARIANT_XPRA program - RSR_VARINT_XPRA OSS -953346 and 960206 1003481
7. Trouble Shootauthorizations 820183 - New authorization concept in BI
Regards,
Deva Reddy

How can upgrade the support pack?

hi all
I was download some file as *.SAR
but I don;t know how can I upgrade it?
and how can I check the version in my SAP and what impact info after upgrade the new support package? (e.g. in web..etc.)
thanks very much
Regards
Kevin

Hi Kevin,
This will help.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCUPGOCSSPAM/BCUPGOCSSPAM.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/83/7a18ecde6e11d195460000e82de14a/frameset.htm
http://www.saptechies.com/sap-patch-manager-spam-bcupgocs/
Regards
Ashok Dalai

ABAP Runtime error on FB50 or FB60 after supplying SAP Support Packs

After applying the latest SAP Financial support stacks and OSS Notes we get the following:
Too many parameters specified with PERFORM.
In a subroutine call, there were more parameters than in the routine definition.
Error in ABAP application program.
The current ABAP program "SAPLGLIN" had to be terminated because one of the statements could not be executed.
This is probably due to an error in the ABAP program.
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
'CX_SY_DYN_CALL_PARAM_NOT_FOUND', was neither
caught nor passed along using a RAISING clause, in the procedure "G_RWIN_CHECK"
"(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
A PERFORM was used to call the routine "G_RWIN_CHECK" of the program
"SAPLGLIN".
This routine contains exactly 3 formal parameters, but the current
call contains 4 actual parameters.
parameters.
We have suspended testing for this reason. Please help.
Thanks,
Barbara

hi barbara
not sure if this is the right forum for this post and you may not get replies
you could try the financials forum
SAP ERP Financials
or the ABAP and Basis forums which you can find from the list in /community [original link is broken]

Reg UPgrading SAP Kernel for ECC 6.0

Hi,
We have a ECC 6.0 SAP System.
The current kernel in our system is 133.
We wanted to upgrade the Kernel
We have the following kernel versions
146
159
175
179
185
We wanted to know the stable kernel versions among the above and general issues encountered in the kernels
Please advice

Just go to the latest kernel.... no point in going from an old kernel to another old kernel. Usually kernels are released every quarter so just get the latest available.
Regards
Juan

Upgradation of Support Pack 21 - Solman

Dear All,
We are using solution manager from last few days, and as suggested by our senior we are planning to upgrade it upto SP21, and we have done few changes in process flow of charm, by adding new actions & user statuses. Now if we did upgradation from SP19 to SP21, is it going to affect anything from solman ?
Looking for your suggestions.
Regds,
Channabasappa

Hi,
No. You won't loose any customized setting becuase of your SP upgrade. If you have made any changes to SAP standard codes, while implementing the SPs, modification adjustment will pop up and will inform you about the changes. But as you haven't done any code changes, there wont be any issue for you. You can go ahead with your new SP.
Rajeev

Download SAP Support Packs

Hello all,
I need to download SAPKB70014 from SAP Marketplace.What is the process??Do I have to do it through Solution Manager??

Theres lots of information about this.
No research done
Read the "Rules of Engagament"
Regards
Juan

Upgrading to Support Pack 1 Interim Release 4 HP5

Will we have to change the Zenworks clients on the Desktop or will the latest release work with our existing client, version 7.01.0 ?

On 1/11/2011 2:06 PM, dcampisi wrote:
>
> Will we have to change the Zenworks clients on the Desktop or will the
> latest release work with our existing client, version 7.01.0 ?
>
>
It will work fine with the older clients however you may not get the
benefit of the fixes if the fixes are done in the client as opposed to
the server. Ultimately the goal should be to do both, but they don't
have to be done at the same time.

Support Pack Upgrade for APO 5.0

Hi Guys,
Can anyone update me on what needs to be done from the functional side if we upgrade the Support pack level.
We are upgrading from Support Pack 11 to 16 and are currently in APO 5.0. What precautions and updates we need to do for the same. I would appreciate if some step wise process can be defined, for this. Also would like to know the difference between SPK 16 and 17.
Thanks,
Harsh

Hello Harsh,
Have you checked the Release & Upgrade Info section in the SAP Service portal (service.sap.com). This containa ample information on this.
Thanks,
Mahesh

Reg upgrading SAP Support packs

Similar Messages

Maybe you are looking for