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

Similar Messages

  • 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

  • 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]

  • Need to study the relevance & do an impact analysis for Support Pack 19

    Dear Experts ,
    I need to study the SP 19 released by SAP wrt IS Retail & specific logistics modules .
    Where can i find the details of notes & enhancements associated with the SP 19 released?
    Regards
    Anis

    Hello Anis,
    there are 3 links that came to my mind for your inquiry:
    http://solutionbrowser.erp.sap.fmpmedia.com/
    https://service.sap.com/sp-stacks
    https://service.sap.com/side-effects
    On the SP-Stacks particularly you can set your source release and targer (sp19), then there'll be a link with the side-effects report which I believe contain the information you're looking for.
    I hope this helps.
    Best regards,
    Tomas Black

  • 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

  • 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

  • Reg: Support Pack supports Windows 7 , ie8 and Adobe reader X

    Hi Team,
    Could anyone advise me what is the SAP Support pack that support Windows 7, IE8  and  Adobe reader X?
    Thanks in advance.
    Regards,
    SDKumar

    The installers for all Windows versions are the same.

  • SAP R/3  4.6 B Support pack level for AIX 5.2

    Hi,
    We have upgraded O.S version from AIX 4.3 to AIX 5.2. Here our environment is SAP R/3 4.6B and DB oracle 8.1.7.
    My question: Do we apply any support pack to the system after support pack upgrade. Please find the below support pack level for our current system.
    SAP_BASIS      46B           0054    SAPKB46B54
    SAP_ABA         46B           0054    SAPKA46B54
    SAP_APPL       46B           0054    SAPKH46B54
    SAP_HR           46B           0000        -
    ST-PI            2005_1_46B    0003    SAPKITLQC3
    Please request the feedback.
    Thanks & Regards,
    Narayana Murthy.

    Do we apply any support pack to the system after O.S upgrade ?
    ( Correction for the below posted mail)

  • Support Pack level for R/3 4.7 and BW 3.5 with SAP CRM2007

    What should be the Support Pack level for R/3 4.7 and BW 3.5 with SAP CRM2007?
    Regards,
    Rajesh Banka

    >
    Rajesh Banka wrote:
    > What should be the Support Pack level for R/3 4.7 and BW 3.5 with SAP CRM2007?
    >
    > Regards,
    > Rajesh Banka
    Hi Rajesh,
    Please see the note '833438', it explains which pack is required in this scenario.
    "You cannont connect ERP (R/3) releases lower than 4.6C to CRM 5.0.
    All subsequent CRM releases (5.0 or higher) cannot be connected to ERP lower
    than (R/3) 4.6C.
    These types of system landscapes are not supported by SAP.
    If you are using CRM 5.0, you must have implemented Plug-in PI 2004.1
    Support Package 10 and, provided you have Basis Release 620 or higher, you
    must import PI_BASIS 2005.1 in R/3. --> After you have imported these
    plug-ins"
    Thanks,
    Nitin Sharma

  • Latest Support Packs for integration of SAP XI 7.0 and SAP ECC 6.0 Retail

    Hi,
    We are integrating SAP ECC 6.0 for IS-Retail System with SAP XI 7.0. I would like to know what lastest Support Packs should present in both the Systems for proper integration, without any technical errors in future.
    Regards,
    Balaji

    Hi,
    The latest Support Pack for PI 7.0 is now SP 14
    You can confirm this from SAP service market.
    https://service.sap.com/swdc
    Thanks
    Swarup

  • How to flush Delta queue for future SAP upgrades/support pack !

    Guys,
    I'm making documentation regards to " How to flush Delta Queues" in case SAP wanted to upgrade the system or any support pack. Please anyone let me know the effective way to flush out the delta queue in step by step methods. I really appreciate your help.

    1.  Run V3 for associated application(s), this will load any potential delta data to the delta queues.
    2.  Run the delta load for each datasource twice.  The second load will clear the delta repeat data so that there should not be any more data in the delta queues defined with the format of the current datasources.
    Does this help?

  • Latest support pack for sap srm 5.0(server 5.5)

    Hi,
    Pls let me know the latest support pack for sap srm 5.0(server 5.5).
    Thanks,
    Manu

    Hi Muthu,
    if we take e.g. note 1302207. This was created a short while ago after SP14 was delivered. It has to be included in the next support package.
    So the entry with SP15 here means that it is included in SP15 if it is released.
    Hope that i could help.
    Best regards,
    Georg

  • SAP BW Support pack

    BW Experts,
    Can anyone tell me what is the recent most SAP BW Support pack? My client is on support pack 19, and they want to upgrade it with the version previous to the most recent one.
    Thanks
    Ashwin

    hi Ashwin,
    yes, the note mention the impact.
    for steps please find here
    http://help.sap.com/saphelp_nw2004s/helpdata/en/29/ff9036e1e4b603e10000009b38f889/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/a7/a7a932845c11d2b421006094b9ea64/frameset.htm
    normally this task is done by basis.
    hope this helps.
    783253
    Symptom
    Support Package 23 for BW Release 3.1 Content
    Other terms
    SAPBWNEWS, Support Packages for 3.1 Content, BW 3.10, BW Patches
    Solution
    This note contains the SAPBWNews for Support Package 23 for BW Release 3.1 Content. It contains a list of all notes that describe the corrections and enhancements in Support Package 23 (SAPKW31023). This note will be updated as soon as further notes are added.
    The information is divided into the following areas:
    Manual actions that may be required:
    Factors you must take into account when you import the Support Package.
    Errors that may occur after you import the Support Package
    General information:
    This Support Package corrects the following errors.
    Enhancements delivered with this Support Package
    Note 539867 contains further important and necessary information about importing Support Packages for BW 3.1 Content, and this information does not refer to any particular Support Package.
    For example, Note 539867 contains the necessary patch level for the basis system and other essential information about importing the Support Packages, as well as information about problems that originate in other systems but may also appear in BW.
    Note 539867 also contains the planned Support Package release dates. The note is regularly updated to include the most current information (the last update was on NOV/08/2004).
    Therefore, we strongly recommend that you refer to this note before you import the Support Package. To subscribe to the note, refer to the instructions contained in Note 487366.
    Support Package 23 for BW 3.1 Content corresponds to the technological level of Support Package 29 for BW 3.0B (SAPBWNews 783251).
    Factors you must take into account when you import the Support Package:
    After you import the Support Package, remember to restart the application or to use $sync to clear the temporary storage.
    If filter value selection takes a long time, refer to Note 912773.
    Errors that may occur after you import the Support Package:
    Querys on MultiCubes in read mode A. For more information, see Note 896066.
    The query shows more rows. For more information, see Note 901097.
    The update from the PSA using the 'Update' indicator in the scheduler no longer works for normal master data that is not flexible and text DataSources that were updated using 'PSA only' - Reason: The problem is caused by the correction that is contained in Note 889160, Note 905105 corrects the problem.
    A syntax error occurs in class CL_RSMD_CONVERSION, method DROP_TMPTABLES. For more information, see Note 905168.
    F4 and authorization: SQL error in SAPLRSDM_F4. For more information, see Note 907337.
    This Support Package corrects the following errors:
    Enhancements that are delivered with this Support Package:
    Refer also to the Documentation Enhancements on the SAP Service Marketplace (http://service.sap.com/bi --> Documentation --> SAP BW 3.x Documentation Enhancements), which describe the enhancements that are delivered with this Support Package.
    Enhancements in the area of OLAP technology:
    General performance improvements for OLAP. For more information, see Note 825396.
    The runtime in the REMOVE_SELDR_0INFOPROV_NEW form is very long. For more information, see Note 887801.
    Unnecessary reading of partprovider. For more information, see Note 885733.
    The performance in from SAPLRRK0; loc_rechnen has been improved. For more information, see Note 884482.
    Problems occur with hierarchy selections in MultiProviders. For more information, see Note 879290.
    Query runtime if there are several nested formulas. For more information, see Note 872904.
    Information regarding the system component validation:
    The Support Package was validated at a specific level of the system components that are available at this time. We therefore recommend that, in parallel to the BW Support Package upgrade, you adjust the system environment to the version of the individual components.
    You can find more information in the SAP Support Portal at http://service.sap.com/swdc:
    -> Additional Download Information -> SAP Support Package Stacks -> SP Stack Information and Download -> SP Stack SAP BW 3.1 Content

Maybe you are looking for