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

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

  • 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

  • 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

  • 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

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

  • Import Support pack in Portal system with ESS & NWDI.

    Hi ,
    NW Portal system has the current support pack level of JAVA stack 11 which includes ESS business backages SAP_ESS 603 SP1, BP_ERP5***,BP_ERP5COM,BP_ERP5ESS, BP_ERP5HRA, BP_ERP5PSS 1.0 SP12. We are using NWDS for doing some customizing the ESS portal iViews configuration and transporting through NWDI tracks.
    If we are upgrading the support pack for netweaver and portal, whether the business packages and the java stack needs to be go through JSPM or through NWDI transport?
    At the same time we like to upgrade the SLD system which has only JAVA stack installed separately. What are the thing that we need to do in SLD before & after updating the support packages like CIM model, etc.
    As we are having the JAVA stack NETWEAVER 7.0,Eventhough SOLMAN mopz decides the level of SP level, but is it good to go to EHP1 or stay in the current Netweaver 7.0 Java stack and our current ECC are going to be in the Netweaver 7.0 Java.
    Thanks
    John

    John,
    If we are upgrading the support pack for netweaver and portal, whether the business packages and the java stack needs to be go through JSPM or through NWDI transport?
    JSPM only
    At the same time we like to upgrade the SLD system which has only JAVA stack installed separately. What are the thing that we need to do in SLD before & after updating the support packages like CIM model, etc.
    May be you want to trigger data push manually once from all system to make sure if everything is working fine , other than this nothing
    As we are having the JAVA stack NETWEAVER 7.0,Eventhough SOLMAN mopz decides the level of SP level, but is it good to go to EHP1 or stay in the current Netweaver 7.0 Java stack and our current ECC are going to be in the Netweaver 7.0 Java.
    Its good to go with latest , but to be in sync with ECC you can continue with 7.0.
    Regards,

  • Inits/Deltas during Uprgrades and support packs

    How are people handling the deltas and initializations when upgrades and support packs are applied to the source system. We had to delete our delta queues and reload everything!!! I know that's not right. ( At least I hope that's not right!!!). Please advise...

    Ye s- you should not have to reload targets a a result of an SP/Upgrade.
    When there are changes to the PI_BASIS plugin (extraction from ERP), you need to clear your V3 and Delta queues.
    When SAP Service API (internal and BI Data mart extraction) is changed, you need to clear the BW delta queues.  This can require two complete extraction and laod processes.
    As a matter of practice, we always clear all queues prior to an SP/upgrade.
    See the How to... Checklist: Rapid SAP Netweaver 7.0 BI Technical Upgrade document which is where you can fins this info page 11or 12.

  • 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 Level Upgrade in BI 7.0

    Hi all,
    Can anyone let me know what are the possible issues that would occur after upgrading support pack level in BI 7.0.
    As far as I know a BI consultant would participate in the upgrade activities like BI objects check, SPAU, query check, etc. Can anyone let me know if there are are any other activities to be performed.
    I would appreciate your help.
    Thanks,
    Sunny.

    Hi
    There is any customer specific development done by SAP in the previous system. If so, the time to act is just after the pre upgrade study only. The customer would only want to retain the customer specific module developed by SAP. We need to get SAPu2019s intervention in the project before we start the upgrade. SAP would develop certain patches to be run on the previous system  to capture all the customer specific development and then they would run some patches on ECC system u2013 this would release the customer specific development in the new system (ECC./BI). This is a very crucial and important check of the step. If not taken care of at the proper time, it might hamper the Customer Specific development on the new system.
    It is to be assured that the new system is at the latest stack level for ABAP, XI, BI etc before we start the SPDD and SPAU phase
    Only one request is to be made for SPDD. For SPAU too, only one request should be made.
    Previous system sandbox  should be available for reference during the entire upgrade project and should not be scrapped before the Go Live.
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0c9c8be-346f-2a10-2081-cd99177c1fb9
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/304b9de6-f84f-2b10-94af-e5ff7461c18c
    http://www.thespot4sap.com/upgrade_guide_v2.pdf
    Hope it helps.

  • Suggested Support Pack Level for ECC 6.0 Upgrade - Target

    Hi ,
    Can someone give us the suggested support pack level for the ECC 6.0 system after the upgrade.
    Our current patch level is:
    SAP_ABA     700     0012     SAPKA70012
    SAP_BASIS     700     0012     SAPKB70012
    PI_BASIS     2005_1_700     0012     SAPKIPYJ7C
    ST-PI     2005_1_700     0003     SAPKITLQI3
    SAP_BW     700     0014     SAPKW70014
    SAP_AP     700     0009     SAPKNA7009
    SAP_APPL     600     0010     SAPKH60010
    SAP_HR     600     0013     SAPKE60013
    EA-IPPE     400     0008     SAPKGPID08
    EA-APPL     600     0008     SAPKGPAD08
    EA-DFPS     600     0008     SAPKGPDD08
    EA-FINSERV     600     0008     SAPKGPFD08
    EA-GLTRADE     600     0008     SAPKGPGD08
    EA-HR     600     0013     SAPKGPHD13
    EA-PS     600     0008     SAPKGPPD08
    EA-RETAIL     600     0008     SAPKGPRD08
    FINBASIS     600     0008     SAPK-60008INFINBASIS
    ECC-DIMP     600     0008     SAPK-60008INECCDIMP
    ERECRUIT     600     0008     SAPK-60008INERECRUIT
    FI-CA     600     0008     SAPK-60008INFICA
    FI-CAX     600     0008     SAPK-60008INFICAX
    INSURANCE     600     0008     SAPK-60008ININSURANC
    IS-CWM     600     0008     SAPK-60008INISCWM
    IS-H     600     0008     SAPK-60008INISH
    IS-M     600     0008     SAPK-60008INISM
    SEM-BW     600     0008     SAPKGS6008
    IS-OIL     600     0008     SAPK-60008INISOIL
    IS-PS-CA     600     0008     SAPK-60008INISPSCA
    IS-UT     600     0008     SAPK-60008INISUT
    LSOFE     600     0008     SAPK-60008INLSOFE
    IRMIPM     30B     0005     SAPK-30BI7INIRM
    IRMGLB     30B     0005     SAPK-30BG7INIRM
    ST-A/PI     01K_ECC600     0000     -
    GSCDMC     600     0001     SAPK-60001INGSCDMC
    RCMGT     601     0001     SAPK-60101INRCMGT
    Thanks
    Senthil

    Hi Senthil,
    of course it is always recommended to use the newest Support Package Stack,
    but if your system (your business processes) are working fine, I would recommend you to
    import support package only then when you have an error or you want to have a special fiunctionality.
    Some customers play support packages into the system only twice a year, because the business processes
    should be tested after the sp import.
    Kind regards
    Imre Takácsi-Nagy
    Senior Support Consultant II.
    SAP Global Support Center Austria
    Netweaver WEB Application Server ABAP / JAVA

Maybe you are looking for