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

Similar Messages

  • Upgrading the support package

    Dear All,
    We are going to upgrade the support package in R/3 side.  Our delta records are running everyday.
    Kindly let me know what are the precautions to be taken.
    Points will be rewarded
    Thanks in advance
    Sathiya

    Hi,
    All V3 jobs to be suspended and all the delta records to be fethed into BW side before the SP implementation.
    For this the easier and better approach, if you have so many delta packages for different applications to handle, bette create a Info package group and run it just before the SP implementation twice to bring all the records,
    Hope this helps
    Regards
    Srini

  • SAP HR Support Package Problem with HR_CEE 106_500

    Hi, I am trying to apply support packages of HR_CEE 106_500(SAPK-10601INHRCEE--SAPK-10627INHRCEE), SPAM/SAINT is the lastest version, but I got the following error:
              Error in phase: XPRA_EXECUTION
         -   Reason for error: TP_STEP_FAILURE
         -   Return code: 0008
         -   Error message: OCS Package SAPK-10611INHRCEE, tp step R, return
             code 0008
        TP_STEP_FAILURE: The system was unable to execute the                           XPRA_EXECUTION tp step.
    I applied the current version of R3trans, but it does not work.Any ideas?
    Thank you for your time ,
    Evan

    Hi,
             See the Actionlog, import logs,u will get more info..or post those logs..
    Regards
    Umesh K

  • Support Package Problem

    Hi Experts,
      While applying the support package of BASIS (KB70012) and ABAP (KA70012) in SAP ECC 6.0.we get the following error.
    <i>The import was stopped, since an error occurred during the phase
    DDIC_ACTIVATION, which the Support Package Manager is unable to resolve
    without your input.
    After you have corrected the cause of the error, continue with the
    import by choosing Support Package -> Import queue from the initial
    screen of the Support Package Manager.
    The following details help you to analyze the problem:
        -   Error in phase: DDIC_ACTIVATION
        -   Reason for error: TP_CANNOT_CONNECT_SYSTEM
        -   Return code: 0230
       -   Error message: Cant create any process
    When I go through the command mode and type tp connect <sid> & tp connect <sid> pf=g:\usr\sap\trans\bin\ TP_DOMAIN_S10.PFL
    It’s give the following error.
    G:\usr\sap\trans>tp connect S10
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    This is tp version 372.04.04 (release 700)
    E-TPSETTINGS could not be opened.
    EXIT
    ERROR: System : Parameter SAPEVTPATH not set. Batch jobs cannot be started.
    Error in TPSETTINGS: transdir not set.
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 0
    ERRORS: Highest tp internal error was: 0208
    tp finished with return code: 208
    meaning:
      error in transportprofil (param missing, unknown,...)
    G:\usr\sap\trans>tp connect S10 pf=G:\usr\sap\trans\bin\TP_DOMAIN_S10.PFL
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    This is tp version 372.04.04 (release 700)
    Connection to Database of S10 was successful.
    punesrv02\usr\sap\trans\tmp\C071023.S10 for transport: ALL: No such file or di
    rectory
    punesrv02\usr\sap\trans\tmp\SLOG0743.S10.LOC: No such file or directory
    PANIC --> exiting
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 0
    ERRORS: Highest tp internal error was: 0212
    tp finished with return code: 212
    meaning:
      could not access file as supposed (see dev_tp or SLOG0743.S10 for more details
    Please help me.

    Hi Sateesh,
    It seems like your transport management system is not configured properly, Just check your CTS. is it configured properly.
    Check your transport directory too.
    when you imort a support patch it creates a file in this location. this message are co,img that means you transport directory is not configured properly.
    \punesrv02\usr\sap\trans\tmp\C071023.S10 for transport: ALL: No such file or di
    rectory
    punesrv02\usr\sap\trans\tmp\SLOG0743.S10.LOC: No such file or directory
    Regards
    Subhash

  • Side effects in SAP BW after support package upload

    Hello!
    I would like to ask whether do You know any side effects executed by installing of a support package (18 and 19)  in SAP BW 3.5.  If so, should any preventive steps be taken before, to avoid those errors.
    Many thanks
    RW

    Thank You for Your answer.
    What I was looking for were all the activities, that are necessary before uploading of a new support package to avoid possible system errors afterwords. As I read on the forum, there are some errors following the SP upgrade like:
    - user can not use some program variants any more
    - customer exits show error messages, because some tables from the base are changed
    - descriptions of new activities in IMG customizing are missing
    etc.
    Well it seems, that the only thing the user can do is to upload SP patches in the correct order and with an exeption of the last one released.
    RW

  • Unable to login to sap after importing support package

    Dear consultants,
    I have applied the support package basis 11, but it terminated since then i am not able to login to sap from any client  and any user,
    please give your opinions,
    it gives dumps, and at the bottom of logon screen it says, status 0020 program sapmsyst .
    regards,

    Sameer,
    I hope your problem is resolved right now. If not,
    It would be better if you can give a little more information as to which system and version did you apply support pack to? What was the SPAM support pack level? At what phase did the SAPKBxx11 support pack terminated? What OS are you running on? Also, please check if any transports are still running at the 'OS' level.
    Thank you.

  • Support Package problem in Solution Manager 7 / NW 700

    Hi ,
    Once again I need your help. The scenario is :
    I want to upgrade the SAP_BASIS from SP11 to SP16 but it is stopped at  ADD-ONS_CONFLICT_  phase. Then I note down the CRT required for the SP and uncar it to /usr/sap/trans/EPS/in and uploaded via SPAM but again the SAP_BASIS stuck at same step.
    Next  Resetted SPAM queue --> again uncar SAP_BASIS and ST 400 --> uploaded --> tried to define the queue --> Error message "No Valid Queue for SAP Basis rel 700"
    I also tried to apply ST 400 from SAINT --> start --> continue/back/load ( in this screen no add on to be applied found but all the addon SP is successfully uploaded) --> if i press continue --> error message "no add on package found"
    Please guide me.
    Regards,
    Partha Sarathi Hazra

    Not really a portal question. Maybe you should ask in one of the ABAP forums?

  • Activites after Upgrading with Support Package

    Hi
    This week, we upgraded from 8 to 13 SP level in our SCM 5.0 system. Here i am confused what are all activities we have to do as application support ? My BASIS is not really cooperative/ not fully knowledgeable in this.
    After the implementation of 13, first time I accessed RSA1, it said a background job was scheduled with the job BI_TCO_ACTIVATION. and it has spool for 46 pages, with all errors occurred while activating the BW object. All are SAP objects, which we are not using anyway, but It has 0Recordmode object, which is used in our objects
    1) How do I fix these activation errors ?
    2) Do I need to install the BI content again after the SP upgradation ?
    3) Whats SPAU adjustment ? Do we have to do this ? BASIS tells me to look at it. The list has few Question marks, and others are in white status- what does that mean ?
    Any Help to understand this processes ?
    thanks
    Venkat

    closing this thread.

  • 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

  • Upgrading Support Packages

    How can I upgrade the support package of MDM 7.1?

    It also depends which support pack you are upgrading with.
    say
    From MDM 7.1 SP06 and up, multiple instances of MDM are supported on the same MDM host machine.
    Each instance must be installed separately and requires a different SID and different listening ports.
    From MDM 7.1 SP07 and up, MDM can be installed with SSL. This is configured using one of the following
    modes: Unencrypted, SSL or Both. The installation type is configurable in the MDM server ini files.
    In the Projects preparation phase you must:
    1. Adapt all custom applications that use ABAP API, Java API, or CLIX. These programs can be adapted in
        advance.
    2. Update and test import and syndication maps. This has to be done in the Dev/Test environment.
    3. Delete all pre-7.1 ports and maps from the Productive environment. This must be done before any
    schema imports are allowed in the 7.1 Productive environment
    Please see below link for all your concerns (SMP Login Needed)
    https://websmp201.sap-ag.de/~sapidb/011000358700001668502008E
    hth
    thx
    Deep

  • ???? in Menu Bar after upgrading support packages

    Hi All,
    I have upgraded the support packages from Stack 16 to Stack 20 for my ECC 5.0
    Every functionality is fine after the upgrade. But when our consultant tries to check the material in transaction MB52, in the next screen we see some ?????? in the menu items which is supposed to have some options in letters. The functionality is fine when we click on it knowing the option which is supposed to be there.
    Assuming that it is the issue with the GUI, we have upgraded our GUI to 710 patch level 4 which is the latest available. Still no luck.
    Can anyone help me with this. This is holding our upgrade on quality.
    Points will be rewarded.
    Thanks
    Vijay

    Hi All,
    I resolved this myself. We just need to get to the screen shere the ???? show up and go to SYSTEM >> STATUS
    Under SAP Data, double click on GUI Status > STANDARD
    Select the Application Toolbar and click on Activate.
    This should solve the issue.
    Thanks
    Vijay

  • Error getting in useradmin after support package issue!!

    Hi all ,
    We have just upgraded our support package for Bi_JAVA and other.According to our BASIS guy the package installation is through.
    But when i checked the portal-----user adminnistration , iam getting the below error.
    500   Internal Server Error
      Web Dynpro Container/SAP J2EE Engine/6.40 
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.NoSuchMethodError: com.sap.tc.webdynpro.services.task.IRequestTask.isUsrLogoffRequest()Z
        at com.sap.portal.pb.PageBuilder.wdDoExit(PageBuilder.java:203)
        at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoExit(InternalPageBuilder.java:169)
        at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doExit(DelegatingComponent.java:112)
        at com.sap.tc.webdynpro.progmodel.controller.Component.exitController(Component.java:255)
        at com.sap.tc.webdynpro.progmodel.controller.Controller.exit(Controller.java:154)
        ... 27 more
    See full exception chain for details.
    Correction Hints
    The currently executed application, or one of the components it depends on, has been compiled against class file versions that are different from the ones that are available at runtime.
    If the exception message indicates, that the modified class is part of the Web Dynpro Runtime (package com.sap.tc.webdynpro.*) then the running Web Dynpro Runtime is of a version that is not compatible with the Web Dynpro Designtime (Developer Studio or Component Build Server) which has been used to build + compile the application.

    Hi
    Check SAP Note : 869852
    I think it UME is not correctly installed
    After upgrading your system to a newer SP, you get one of the following
    exceptions when executing the UME WD application:
    o java.lang.NoSuchMethodError:
    com.sap.security.core.wd.umeuifactory.wdp.I
    ExternalUmeUiFactoryCompInterface.hasSimplePermission(Ljava/lang/St
    ring;
    Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/St
    ring;Ljava/lang/String;)Z at
    com.sap.security.core.wd.maintaingroup.MaintainGroupComp.afterModel
    Init(MaintainGroupComp.java:787)
    In order to avoid this error, perform following steps:
    - Open the SDM tool and undeploy all components starting with
    "tc/sec/ume/wd/..."
    - Go to your downloaded SP archives and find the UMEADMIN*.SDA.
    Redeploy it.
    Regards
    Krishna.

  • SCC4 - Protection against SAP upgrade

    Hello guys,
    i have a question regarding to the "Protection against SAP upgrade" flag in SCC4 for the client settings.
    I know that this flag will make a client unusable in case of an upgrade (for example from ERP2004 to ERP2005), but what is about applying support packages?
    Is this flag also valid for support packages?
    The documentation about this parameter does not make a statement to this point:
    > If this flag is set, the client is no longer supplied with data during SAP upgrades. After an SAP upgrade, it is not possible to work actively in the client. The flag can only be set for a test client or an SAP reference client (Early Watch).
    Does SAP understand "applying support packages" as an upgrade?
    Answers will be rewarded.
    Regards
    Stefan

    No.
    Applying SP is not SAP upgrade.
    -Pinkle

  • 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

  • Combination of support packages invalid.

    I am getting the following error in RSPOR_SETUP, but according to note 1013369
    this stack is supported. This system is a fresh SR2 install , then I applied
    SPS12 , then finally applied SAPKW70014.
    Is the error referring to the version 11 of the java classes? How did those even get there?
    The Systeminfo shows all java components correctly at SPS12....
    Status for Step 2 - Create RFC Destination for Portal
       Status 1: Create RFC Destination In J2EE Engine         Okay
       Status 2: Create RFC Destination for Portal             Different ABAP and Java support packages. Combination of support packages invalid.
       Status 3: Maintain Portal Server Settings for Portal    Okay
       Status 4: Maintain Single Sign-On in BI                 Okay
       Status 5: Export BI Certificate into BI                 Okay
       Status 6: Import BI Certificate into Portal             Okay
       Status 7: Create BI Sytem in Portal                     Existence of BI System in Portal cannot be checked automatically.
       Status 8: Configure User Management in Portal           Okay
       Status 9: Export Portal Certificate into Portal         Okay
       Status 10: Import Portal Certificate into BI            Okay
       Status 11: Set Up Repository Manager for BI in Portal   Setup of Repository Manager for BI in Portal cannot be checked automatically.
       Status 12: Maintain User Assignment in Portal           Okay
       Status 13: Import SAP NetWeaver Plug-In into BI         Okay
    Entries for Step 2 - Create RFC Destination for Portal
    BI Transaction Display and Maintenance of RFC Destinations (SM59)
    Create
    Name of RFC destination:             (redacted)
    Connection type:                     T (TCP/IP connection)
    Description of RFC destination:      (redacted)
    Technical settings
    Activation type:                     Registered Server Program
    Program ID:                          (redacted)
    Gateway host:                        (redacted)
    Gateway service:                     (redacted)
    Logon/security
    Send SAP Logon Ticket                active
    Checks for Step 2 - Create RFC Destination for Portal
    1. Check existance of RFC destination
       Check of RFC destination  (redacted)  with RFC_READ_TCPIP_DESTINATION successful
    2. Check RFC destination with RFC Call
       RFC Call RFC_PING, destination  (redacted)  successful
    3. Check Number of registered Processes
       GWY_GET_NO_REG_PROGRAMS
       Number of registered processes:       20
    4. Check existance of com.sap.ip.bi Java classes
       RFC Call RSWR_RFC_SERVICE_TEST, destination  (redacted)  successful
        BI test service for user (redacted) called successfully with parameter RSPOR_SETUP.
    5. Check version information of com.sap.ip.bi Java classes
       RFC Call RSWR_RFC_VERSION_INFO_GET, destination  (redacted) successful
       com.sap.ip.bi.base.application.par           7.0012.20070801085802.0000
       com.sap.ip.bi.base.par                       7.0012.20070801085802.0000
       com.sap.ip.bi.base.portal.par                7.0012.20070801085802.0000
       com.sap.ip.bi.bics.cmi.par                   7.0012.20070426205038.0000
       com.sap.ip.bi.bics.os.impl.par               7.0011.20070131173855.0000
       com.sap.ip.bi.bics.os.par                    7.0011.20070131173855.0000
       com.sap.ip.bi.bics.par                       7.0012.20070801085802.0000
       com.sap.ip.bi.broadcasting.base.par          7.0012.20070801085802.0000
       com.sap.ip.bi.broadcasting.par               7.0011.20070131173855.0000
       com.sap.ip.bi.conv.backendaccess.par         7.0011.20070131173855.0000
       com.sap.ip.bi.conv.dac.res.bi.os.par         7.0011.20070131173855.0000
       com.sap.ip.bi.conv.dac.res.bi.par            7.0012.20070801085802.0000
       com.sap.ip.bi.conv.dac.res.dll.par           7.0011.20070131173855.0000
       com.sap.ip.bi.conv.dac.res.oqqv.par          7.0012.20070801085802.0000
       com.sap.ip.bi.conv.dac.res.trex.par          7.0011.20070131173855.0000
       com.sap.ip.bi.dataaccessservice.par          7.0012.20070426205038.0000
       com.sap.ip.bi.export.lib.par                 7.0012.20070426205038.0000
       com.sap.ip.bi.export.model.par               7.0012.20070801085802.0000
       com.sap.ip.bi.export.office.par              7.0012.20070801085802.0000
       com.sap.ip.bi.export.printformats.par        7.0012.20070801085802.0000
       com.sap.ip.bi.export.xfa.par                 7.0012.20070801085802.0000
       com.sap.ip.bi.folderpickerpcd.par            7.0012.20070426205038.0000
       com.sap.ip.bi.km.base.par                    7.0012.20070801085802.0000
       com.sap.ip.bi.km.documentmigration.par       7.0012.20070426205038.0000
       com.sap.ip.bi.km.integration.par             7.0012.20070801085802.0000
       com.sap.ip.bi.km.propertyrenderer.par        7.0011.20070201072627.0000
       com.sap.ip.bi.km.repositorymanager.par       7.0012.20070801085802.0000
       com.sap.ip.bi.metadata.par                   7.0012.20070426205038.0000
       com.sap.ip.bi.objectservices.oqqv.par        7.0011.20070201072627.0000
       com.sap.ip.bi.objectservices.par             7.0011.20070201072627.0000
       com.sap.ip.bi.offlinenavigation.par          7.0011.20070201072627.0000
       com.sap.ip.bi.portal.rfc.dispatcher.par      7.0012.20070426205038.0000
       com.sap.ip.bi.portalheartbeat.par            7.0010.20061024165340.0000
       com.sap.ip.bi.portallogger.par               7.0010.20061024165340.0000
       com.sap.ip.bi.portalnavigation.par           7.0011.20070131173855.0000
       com.sap.ip.bi.portalrfc.par                  7.0010.20061024165340.0000
       com.sap.ip.bi.portalrfctest.par              7.0010.20061024165340.0000
       com.sap.ip.bi.ranges.par                     7.0012.20070801085802.0000
       com.sap.ip.bi.repositorymanager.par          7.0010.20061024165340.0000
       com.sap.ip.bi.service.bics.par               7.0012.20070426205038.0000
       com.sap.ip.bi.service.generic.par            7.0012.20070801085802.0000
       com.sap.ip.bi.service.km.os.par              7.0012.20070426205038.0000
       com.sap.ip.bi.service.portal.os.par          7.0010.20061024142635.0000
       com.sap.ip.bi.supportdesk.par                7.0013.20070620182001.0000
       com.sap.ip.bi.web.advancedcontrols.par       7.0012.20070801085802.0000
       com.sap.ip.bi.web.broadcasterstart.par       7.0011.20070201072627.0000
       com.sap.ip.bi.web.composites.par             7.0011.20070201072627.0000
       com.sap.ip.bi.web.dataprovider.par           7.0012.20070801085802.0000
       com.sap.ip.bi.web.deploytime.par             7.0012.20070426205038.0000
       com.sap.ip.bi.web.dialogs.conditions.par     7.0012.20070801085802.0000
       com.sap.ip.bi.web.dialogs.exceptions.par     7.0012.20070801085802.0000
       com.sap.ip.bi.web.dialogs.formula.par        7.0011.20070201072627.0000
       com.sap.ip.bi.web.dialogs.generic.par        7.0011.20070201072627.0000
       com.sap.ip.bi.web.dialogs.opensave.par       7.0012.20070801085802.0000
       com.sap.ip.bi.web.dialogs.selector.par       7.0012.20070801085802.0000
       com.sap.ip.bi.web.dialogs.statistic.par      7.0012.20070801085802.0000
       com.sap.ip.bi.web.dialogs.variablescreen     7.0012.20070801085802.0000
       com.sap.ip.bi.web.dialogsframework.par       7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.analysis.par         7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.bodyattributes.p     7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.broadcastindex.p     7.0011.20070201072627.0000
       com.sap.ip.bi.web.items.buttongroup.par      7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.chart.par            7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.command.par          7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.container.par        7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.contextmenu.par      7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.dataproviderinfo     7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.filter.par           7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.filterpane.par       7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.generic.par          7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.group.par            7.0011.20070201072627.0000
       com.sap.ip.bi.web.items.hierarchfilter.p     7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.htmlattributes.p     7.0011.20070201072627.0000
       com.sap.ip.bi.web.items.infofield.par        7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.inputfield.par       7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.km.par               7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.map.par              7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.menu.par             7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.messageslist.par     7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.mime.par             7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.navigation.par       7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.persistency.par      7.0011.20070201072627.0000
       com.sap.ip.bi.web.items.properties.par       7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.report.par           7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.structural.par       7.0011.20070201072627.0000
       com.sap.ip.bi.web.items.text.par             7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.ticker.par           7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.variables.par        7.0011.20070201072627.0000
       com.sap.ip.bi.web.objectservices.par         7.0011.20070201072627.0000
       com.sap.ip.bi.web.pageexport.par             7.0011.20070201072627.0000
       com.sap.ip.bi.web.portal.deployment.par      7.0011.20070201072627.0000
       com.sap.ip.bi.web.portal.integration.par     7.0012.20070801085802.0000
       com.sap.ip.bi.web.portal.mimes.par           7.0012.20070801085802.0000
       com.sap.ip.bi.web.preexecution.par           7.0012.20070426205038.0000
       com.sap.ip.bi.web.runtime.par                7.0012.20070801085802.0000
       com.sap.ip.bi.web.runtime.scripting.par      7.0012.20070801085802.0000
       com.sap.ip.bi.web.runtime.template.par       7.0012.20070426205038.0000
       com.sap.ip.bi.web.scripting.par              7.0012.20070426205038.0000
       com.sap.ip.bi.web.ui.dragdrop.par            7.0012.20070426205038.0000
       com.sap.ip.bi.web.ui.queryviewactions.pa     7.0012.20070426205038.0000
       com.sap.ip.bi.web.uiframework.par            7.0012.20070426205038.0000
       com.sap.ip.bi.web.uiitem.par                 7.0011.20070201072627.0000
       com.sap.ip.bi.web.unifiedrendering.par       7.0012.20070801085802.0000
       com.sap.ip.bi.webdynpro.alv.pdf.par          7.0011.20070201072627.0000
    6. Compare version information of Java support package (com.sap.ip.bi classes) with ABAP support package (SAP BI)
       ABAP Support Package:                  14
       Java Support Package:                  11

    Hi,
    I have the same problem. I´ve installed a fresh netweaver SR3, and the patch level is the next,
    6. Compare version information of Java support package (com.sap.ip.bi classes) with ABAP support package(SAP BI)
    ABAP Support Package:           19
    Java Support Package:              16
    More thanks

Maybe you are looking for

  • Can we use BLOB fields (that store images) in Crystal Report ?

    I'm developing with ASP.NET, VS.NET 2003. Using Crystal Report for VS.NET DataBase: Oracle 10g I store a BLOB field in a table. This field store images, like jpg files. The Stored Procedure that I use to fill the report is: OPEN MyCursor FOR SELECT M

  • Lumia Camera/4K not working after Denim Update

    Hi, Received the Lumia denim update this morning but after installation, the Lumia Camera app is not open (displaying a megbox that says "Lumia camera requires Lumia denim software update") and the extra+info still shows "cyan". The rest of denim upd

  • URL in email to a report on a specific record

    Hi - I have setup an email notification process that will send a URL to bring the user back to a report for a specific record. The link is bringing me back to the right page, but there are no results for the report. How do I go to the page AND run th

  • Picture Book Customization

    This is my first time putting together a picture book, so far the IPHoto application is great, however I was wondering, is there a reason why the customizations or restricted? I seen a couple of layouts in different themes of picture books, why must

  • I am facing "Please re-login to renew your session" error in Blackberry Z30 smartphone

    After updating my OS y2 days ago, when I am logging in to Facebook using my Blackberry Z30 smartphone, I am facing "Please re-login to renew your session" error. Please help me resolve this problem.