SAP_APPL Support Pack Upgradation Directlry to SAPKH60015 from SAPKH60010

Hi Dear Friends,
SAP_APPL need top upgrade upto level SAPKH60015 from 10, can we upgrade directly ? OR in sequintally 11,12,13,14,15 manner
Current version ECC 6.0, Win x64 2003, MSSQL DB
Please guide.
Regards
Nilanchal

SAP_APPL need top upgrade upto level SAPKH60015 from 10, can we upgrade directly ? OR in sequintally 11,12,13,14,15 manner
Note only SAP_APPL all the support pack can be upgrade on a sequential manner only, except SPAM/SAINT update.
Regards,
Subhash

Similar Messages

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

Support pack Upgradation

Hi Gurus
I have couple of doubts on my Transports.We are upgrading support packs on BI 7.0.
They upgraded on Development System and They are planning to upgrade support packs on Testing and Production System.I want to transport from Develoment to Testing System.
What would be the effect on Transport if I transport objects from Dev System to Testing System when they are on different Support packs.Can I migrate the Objetcs or not .If so what would be the effect.Please let me know.
Could any one let meknow how to apply SAP notes once the basis apply Support Pack Upgrade.I need to do this down the road.Any help will be appreciatable and assign points.
Thanks,
Suryam.

Hi,
Usually SAP notes are applied by the BASIS team. Notes are nothing but code changes provided by SAP for the std SAP programs.
Also in case you the transports, I would do thorough checking as patch levels are different on both the systems and the functionality might be different. For ex. if a patch upgrade came with some new features in query designer and those features were used in development, they'll not be available in test system after you transport as the patch levels are different. After patch upgrade to the test system, you might have to retransport.
Cheers,
Kedar

Support Pack Upgrade Strategy

Hi Experts,
I am trying to develop a strategy for testing SP upgrades in development and "okaying" them for migration into production.
What steps do you normally take to ensure your system works as intended and the update is really for production?
I would think to go through and verify all of the changes from the SAP note which contains the SP detail, but what else? It is often the case that implementing a SP has an effect on other functionality.
Please share your thoughts and experiences.
Thanks,
Grace Rae

Hi Grace,
Firstly, this question should be posted in the Basis forums You will have more experts who dealt with these activities there.
Regarding the support pack upgrade strategy, we would normally implement it in the test systems, and closely monitor the system performance in peak and normal hours, background jobs, and any other issues that are highlighted during the monitoring period. If there are no issues reported by the functional testing team, we will go ahead implementing it in production system.
Hope this helps!
Regards,
Raghu

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

Web AS 6.4 Support Pack upgrade from stack 9 to stack 10

Hi,
Did any one apply support pack from stack 9 to stack 10 for Web AS 6.4, which installed on windows 2003 and Oracle 9.2?
I got error on step 9 over 19 steps, MUT-02041. In callSdmViaSapinst.log, I found following:
Apr 19, 2005 3:21:39 PM Info: SDM configuration: Do not determine state of J2EE Engine now.
Apr 19, 2005 3:21:39 PM Info: SDM configuration: Do not save/restore state of J2EE Engine now.
Apr 19, 2005 3:21:39 PM Info: Error handling strategy: OnErrorStop
Apr 19, 2005 3:21:39 PM Info: Update strategy: UpdateLowerVersions
Apr 19, 2005 3:21:39 PM Info: Starting: Update: Selected development component 'keystore'/'sap.com'/'SAP AG'/'6.4010.00.0000.20041222145329.0000' updates currently deployed development component 'keystore'/'sap.com'/'SAP AG'/'6.4009.00.0000.20041117092012.0000'.
Apr 19, 2005 3:21:39 PM Info: SDA to be deployed: D:\usr\sap\VDT\JC00\SDM\root\origin\sap.com\keystore\SAP AG\6.4010.00.0000.20041222145329.0000\keystore.sda
Apr 19, 2005 3:21:39 PM Info: Software type of SDA: primary-service
Apr 19, 2005 3:21:39 PM Info: ***** Begin of SAP J2EE Engine Offline Deployment (Service component of SAP J2EE Engine) *****
Apr 19, 2005 3:21:40 PM Info: ***** End of SAP J2EE Engine Offline Deployment (Service component of SAP J2EE Engine) *****
Apr 19, 2005 3:21:40 PM Error: Aborted: development component 'keystore'/'sap.com'/'SAP AG'/'6.4010.00.0000.20041222145329.0000':
Caught exception during deployment from SAP J2EE Engine's offline deploy API:
com.sap.engine.tools.offlinedeploy.rdb.ODeploymentException: WARNING: Can't deploy component with sda D:\usr\sap\VDT\JC00\SDM\root\origin\sap.com\keystore\SAP AG\6.4010.00.0000.20041222145329.0000\keystore.sda
com.sap.engine.lib.io.hash.CorruptedHashException
at com.sap.engine.lib.io.hash.IndexUtils.verifyCRC(IndexUtils.java:73)
at com.sap.engine.lib.io.hash.MultipleHash.decodeFromByteArray(MultipleHash.java:73)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineOfflineDeployerImpl.performAction(DeploymentActionTypes).ODEXC)
Apr 19, 2005 3:21:40 PM Info: -
Deployment was successful -
Apr 19, 2005 3:21:40 PM Info: Summarizing the deployment results:
Apr 19, 2005 3:21:40 PM Error: Admitted: D:\J2EE-RUNT-CD\J2EE-ENG\OFFLINE\SAPJEECOR10_0.SCA
Apr 19, 2005 3:21:40 PM Error: Admitted: D:\J2EE-RUNT-CD\J2EE-ENG\OFFLINE\JRFC.SDA
Apr 19, 2005 3:21:40 PM Error: Processing error. Return code: 4
Anybody has a clue how to solve it? Thanks in advance!!

solved it myself. Re-install J2EE, and re-apply patch again. Everything is good now.

PI System Support Pack Upgraded from 04 to 07

Hi Guys,
In PI system basis people upgraded support pack 04 to 07.
how i will check the PI system functionality after upgrading support package 04 to 07...
first basis people upgrated in PI Development system. after they will do in PI Quality and PI Production.
is there any effect on PI existing interfaces once it comes to live system production..
can any one please help me on this.
Thanks,
Siva.

first basis people upgrated in PI Development system. after they will do in PI Quality and PI Production.
is there any effect on PI existing interfaces once it comes to live system production..
backward compatibility is provided so if you upgrade a SP then your existing interfaces will continue to run without any issue/ modification.
The only thing that you need to take care is that all your environments (DEV, QA, PROD) should be on same level so that transport of objects is not affected.

Support Pack upgrade path

We recently upgraded from ECC 6.0 support pack 9 to support pack 15. At the same time, we installed EHP4 support pack 5. A few questions:
1. Will we upgrade our ECC 6.0 support pack 15 system to the next support pack, for example to support pack16 or 17, OR will our support packs follow the EHP4 support pack update path, for example upgrading our current environment by moving from EHP4 support pack 5 to support pack 6?
2. We have not yet enabled any of the new EHP4 functions in our landscape. Is it recommended that if we upgrade EHP4 support pack 5 to support pack 6 we do a full integration test? If we haven't enabled any EHP4 support pack 5 functions, I wasn't sure if an integration test was needed.
thank you,
Jonathan

Hello Jonathan,
I hope you are aware of SPDD/SPAU.
Point to be notes is support package will not overwrite your own customizing (Z, Y).
and if you modified any Standard object for your purpose and its been overwritten by the Support package then you will definately get a prompt in SPDD and SPAU and you have a chance to take decision how would you like to go. whether you want to keep your customizing to the standard objects or you want the new standard code to overwrite it.
So, you will not need to do integration testing for complete things in your system.
Let me know if you need more clarifications.
Best Regards
Niraj

Support Pack upgrade issue: Request deletion dose not work on CUBE

Hi Gurus,
We recently had a support package upgrade from SAPBW701 SP6 to SAPBW702 SP7.
We have an Info package request stuck in yellow state for DSO Load in HR Data.
We manually made it red and are trying to delete it manually/by creating a variant for Delete target contents in the process chain. It is not getting deleted.
Rather if we use the Delete target contents variant previously created before the support package upgrade, it works fine.
Please help me if any one can suggest any SAP NOTE or some other solution if possible.
Thanks in advance,
Sourabh Deo

Hi,
i think you have made it to red in request tab and tried deleting. Actually , you have to make the QM status red in Dataload monitor by double clicking the TOTAl technical status.
After the above activity, then try deleting.
I don't think its a Service Pack problem.
Regards,
Suman

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

Support Pack upgrade error in Import Phase

Hello,
Currently I am upgrading SCM system with Support pack level 12 to 20 . When i am applying Basis 12 to 20. I got an error in Import_Proper phase.
Could you please help me on this? I tried and still searching solution for this..But no luck...
Os is : AIX and
Log File:                /usr/sap/trans/log/SAPIB70013.xxx
Main import
Transport request   : SAPKB70013
System              : xxxx
tp path             : tp
Version and release: 372.04.71 700
child process 934006 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function:   db_report_interface
fcode:      CLOSE_LINE_MODE
tabname:    SOURCE
len (char): 40
key:        CL_OBJECT_COLLECTION==========CT
retcode:    1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1212554 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function:   db_report_interface
fcode:      CLOSE_LINE_MODE
tabname:    SOURCE
len (char): 40
key:        CL_WDR_APPLICATION_WINDOW=====CT
retcode:    1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1171520 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function:   db_report_interface
fcode:      CLOSE_LINE_MODE
tabname:    SOURCE
len (char): 40
key:        CL_WDY_MD_EVENT_SOURCE========CI
retcode:    1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1331412 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function:   db_xrtab
fcode:      RT_MI_LOAD
tabname:    ECSCR_DATA
len (char): 106
key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
retcode:    1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
insert / update sequence failed due to an error in DBI.
maybe there's a concurrent process which inserted this table entry at the same time.
insert / update sequence failed due to an error in DBI.
maybe there's a concurrent process which inserted this table entry at the same time.
child process 1310922 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function:   db_xrtab
fcode:      RT_MI_END
tabname:    WDY_APP_PROPERTY
len (char): 64
key:        DEMO_UIEL_DROPDOWN_BY_IDX     DEMO_VIEW
retcode:    1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
import portion 018446 - 999999 not imported because the child processes died for unknown reason
child process 1310924 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function:   db_report_interface
fcode:      CLOSE_LINE_MODE
tabname:    SOURCE
len (char): 40
key:        CL_WDY_MD_OUTGOING_EVENT======CT
retcode:    1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1286192 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function:   db_xrtab
fcode:      RT_MI_LOAD
tabname:    ECSCR_DATA
len (char): 106
key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
retcode:    1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
import portion 009158 - 018411 not imported because the child processes died for unknown reason
import portion 018412 - 018527 not imported because the child processes died for unknown reason
import portion 018528 - 999999 not imported because the child processes died for unknown reason
sap_dext called with msgnr 1:
db call info -
function:   db_xrtab
fcode:      RT_MI_LOAD
tabname:    ECSCR_DATA
len (char): 106
key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
retcode:    1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
Main import
End date and time : 20100909034914
Ended with return code: ===> 12 <===
     |   ######################################
Thanks and Regards,
Sankar
SAP BASIS Consultant

Hi,
Thanks for you reply. I restarted import but no luck still. I activated some object also not working. when i call SPAM it is not going to the SPAM pager. Showing dump...
Runtime Errors         CALL_FUNCTION_NOT_FOUND
Except.                CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time          10.09.2010 09:41:37
Short text
     Function module "POSS_UIREQ_OPT_SUBMIT" not found.
What happened?
     The function module "POSS_UIREQ_OPT_SUBMIT" is called,
     but cannot be found in the library.
     Error in the ABAP Application Program
     The current ABAP program "SAPLSTXC" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
      not caught in
     procedure "OPEN_FORM" "(FUNCTION)", nor was it propagated by a RAISING clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     The program "SAPLSTXC" contains the CALL FUNCTION statement.
     The name of the function module to be called is "POSS_UIREQ_OPT_SUBMIT".
     No function module exists with the name "POSS_UIREQ_OPT_SUBMIT".
     All function modules are listed in the Function Library (SE37).
Possible reasons:
a) Wrong name specified. Pay particular attenti
    upper/lower case and underscores ("_").
    or
b) Transport error
c) In the case of an enqueue/dequeue module,
    the lock object may not have been activated
    (ABAP/4 Dictionary).
When i tried to check function module it is not there..
Could you please help on this?
Regards,
Sankar Basis Consultant

Support Pack Upgrade 5.3

We are currently at GRC 5.3 SP8 and we are upgrading to EHP5. According to SAP Note 1382385, we need to upgrade to at least SP13. We plan on upgrading to the latest version of 5.3 which is SP17.
In the ABAP systems, we are required to install each support pack before we can install the latest support pack.
On the Java side, are we required to install each support pack leading up to the latest? Or can we simply install the latest Java version?

Hi
Always JAVA and ABAP stack both should have same support packs with respective to GRC.
but when you apply support packs java side you can st right away load the recent only, but ABAP side one by one each should apply.
Regards
Hari

Support Pack Upgrade Undo

Hello Experts,
I am new to this fascinating world of SAP BASIS professionals and here I am again with my fourth issue. Please give your valuable advise.
The Scenario:
I have an ECC 6.0 ABAP+JAVA system installed. Recently I have upgraded 3 of it's software components, which are follows:
PI_BASIS 2005_1_700     Level 0009----to-----Level 0010.
SAP_BASIS 700               Level 0009----to-----Level 0010.
SAP_ ABA 700                 Level 0009----to-----Level 0010.
My Question/Issue:
I have upgraded the above to Level 0010, but now I want to revert them back to Level 0009 (initial level), that is, I want to UNDO the SUPPORT PACK application. Is this possible? If this is possible, then how?
Please Note: I have not taken any database backup before applying this patches, furthermore, my database is in NO ARCHIVE LOG mode.
Help me....

Hello,
Since you have no backup available, the only solution is re-installing the system.
"Fooling" the system by changing some of the PAT* tables is not a good proposition.
There remain a lot of open questions with this approach.
How are you going to revert your repository to the previous level ?
Support packages not only import source code corrections but also modifications to the repository (new fields in tables, extend data elements, ...) resulting in conversions of your repository.
By fooling the system you risk serious conflicts weeks or even months later, are you going to take that risk ?
I hope this can help you.
Wim

Support Pack Upgrade to 10 to 23

Hi Experts,
Currently I am wokring on the BW3.5 versiowith support pack 10n. Recently our basis team upgrade the support pack 23(BW component) in source system which is a SRM system.I would like to know that will that be any mismatch issue occur between BW & SRM system. Details furnished below. Advance Thanks.
BW system Current Support Pack Level::
SAP_BW 350 Support pack level: 0010 Highest pack level : SAPKW35010
SRM System Current Support Pack Level::(BW software component):
SAP_BW 350 Support pack level: 0023 Highest pack level : SAPKW35023
Thanks,
RR

Hello Ragu,
This kind of scenario is exists in practice.
Normally I dont see that you will have lot of issue other than the support pack related.
In my practive, I have BI 7.0 system which is connected to 4.6 system as well as EHP1 system. EHP1 system is recently updagrade but still we can use out BW system normally.
For all the issues - your regression tests will give more clarity of the kind of issue that you can face.
For me You need to check whether the RFC is properly maintain and then relicated all the data sources once again followed by activation of transfer structures.
For more information on this you can also check the forum on the known issues of the respective stack.
Hope this helps.
Murali

Support Pack Upgrade to 18 or 19?

Hi all,
We are on Support Pack 13 and we are planning to do an upgrade to SP 18 or 19 next month. Can you please suggest which is a stable one between 18 and 19.
Thanks,
Ram.

SPS18 is fairly stable. It's definitely much more stable than SPS14, by a long shot, and somewhat better stability than SPS16.
Since SPS19 is planned for general release just this week (Week 25), I wouldn't go there yet. It's usually not advisable to go to the latest SP version. We typically stay 6 months behind in order to ensure that a sufficient number of corrections have been created as OSS Note to apply post upgrade. We're in the process of upgrading to EHP1 SPS3 right now (somewhat the equivalent of SPS18), but won't upgrade to EHP1 SPS4 until November/December timeframe because EHP1 SPS4 went on general release a couple of weeks ago (Week 23).

SAP_APPL Support Pack Upgradation Directlry to SAPKH60015 from SAPKH60010

Similar Messages

Maybe you are looking for