Upgrade from ERP 5.0 to ERP 6.0 SR3

Hi,
i got problem, and i can't find any solution in sdn or other internet sources. I downloaded all the DVD's for the upgrade, and when i start from MASTER UPGRADE DVD, command: STARTUP jce_policy_zip=jce_policy_zip=<path to JCE policy archive>
system gives me a message:
Checking if C++ runtime is installed ...
Running MIDBOOT to unpack and startup...
/usr/lib/pa20_64/dld.sl: Unable to find library 'ibnsl.1'.
Killed
I asked OS and Database administrators, should HP-UX system have any libraries that starts not from L character, they told me that there is an error in UPGRADE MASTER DVD
i tried find the solution in SAP notes or just google, but there is nothing for this problem. Can anyone help me please?
OS: HP-UX PARISC
Version: 11.11
Database: Oracle 10.2.0.4

Hi All,
i can't pass the step Initialization in PREPARE, here is the result of CHECKS.LOG:
#=======================================================================
Starting new execution of PREPARE modules
     Initialization
at 20100217115713.
#=======================================================================
   #====================================================#
Requests and information for module Initialization #
   #====================================================#
INFO:    The version check of the R3trans in your active SAP kernel
         determined that it has a sufficient level.
         No update of R3trans is necessary.
INFO:    The version check of the disp+work in your active SAP kernel
         determined that it has a sufficient level.
         No update of disp+work is necessary.
INFO:    The version check of the tp in your active SAP kernel
         determined that it has a sufficient level.
         No update of tp is necessary.
WARNING: The version 2006_1_640 of the Add-on PI_BASIS is too high for this upgrade (> 2005_1_700).
         To avoid loss of data it is necessary to include the latest available version for the Add-on
         in the IS_SELECT phase.
         Please refer to Add-on note 555060 for further information.
WARNING: The version 2008_1_640 of the Add-on ST-PI is too high for this upgrade (> 2005_1_700).
         To avoid loss of data it is necessary to include the latest available version for the Add-on
         in the IS_SELECT phase.
         Please refer to Add-on note 69455 for further information.
INFO:       The upgrade strategy for the addon C-CEE
            is described in note: 520991
INFO:       The upgrade strategy for the addon DMIS
            is described in note: 1000578
INFO:       The upgrade strategy for the addon HR-CEE
            is described in note: 572252
INFO:       The upgrade strategy for the addon HR-CEECBG
            is described in note: 632429
INFO:       The upgrade strategy for the addon HR-CEECCO
            is described in note: 632429
INFO:       The upgrade strategy for the addon HR-CEECCZ
            is described in note: 632429
INFO:       The upgrade strategy for the addon HR-CEECHR
            is described in note: 632429
INFO:       The upgrade strategy for the addon HR-CEECHU
            is described in note: 632429
INFO:       The upgrade strategy for the addon HR-CEECPL
            is described in note: 632429
INFO:       The upgrade strategy for the addon HR-CEECRO
            is described in note: 632429
INFO:       The upgrade strategy for the addon HR-CEECRU
            is described in note: 632429
INFO:       The upgrade strategy for the addon HR-CEECSI
            is described in note: 632429
INFO:       The upgrade strategy for the addon HR-CEECSK
            is described in note: 632429
INFO:       The upgrade strategy for the addon HR-CEECTR
            is described in note: 632429
INFO:       The upgrade strategy for the addon HR-CEECUA
            is described in note: 632429
INFO:       The upgrade strategy for the addon HR-CEEGXX
            is described in note: 632429
INFO:       The upgrade strategy for the addon HR-CEERXX
            is described in note: 632429
INFO:       The upgrade strategy for the addon NMI_CONT
            is described in note: 632429
INFO:       The upgrade strategy for the addon PI
            is described in note: 700779
INFO:       The upgrade strategy for the addon PI_BASIS
            is described in note: 555060
INFO:       The upgrade strategy for the addon SAP_BW
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCAR
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCAT
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCAU
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCBE
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCBR
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCCA
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCCH
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCCN
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCDE
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCDK
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCES
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCFI
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCFR
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCGB
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCHK
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCID
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCIE
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCIN
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCIT
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCJP
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCKR
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCMX
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCMY
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCNL
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCNO
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCNZ
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCPH
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCPT
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCSE
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCSG
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCTH
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCTW
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCUS
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCVE
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRCZA
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRGXX
            is described in note: 632429
INFO:       The upgrade strategy for the addon SAP_HRRXX
            is described in note: 632429
INFO:       The upgrade strategy for the addon ST-A/PI
            is described in note: 69455
INFO:       The upgrade strategy for the addon ST-PI
            is described in note: 539977
INFO:       You have installed the add-on CEEFISI in your system
INFO:       Please read note 574102 and 584396 carefully before continuing
INFO:       You have installed the add-on C-CEE in your system
INFO:       Please read note 574102 and 584396 carefully before continuing
INFO:       You have installed the add-on CEEFIHR in your system
INFO:       Please read note 574102 and 585119 carefully before continuing
INFO:       You have installed the add-on C-CEE in your system
INFO:       Please read note 574102 and 585119 carefully before continuing
INFO:       You have installed the add-on C-CEE in your system
INFO:       Please read note 574102 and 585195 carefully before continuing
INFO:       You have installed the add-on CEEFIRO in your system
INFO:       Please read note 585804 and 574102 carefully before continuing
INFO:       You have installed the add-on C-CEE in your system
INFO:       Please read note 585804 and 574102 carefully before continuing
   #===========================================================#
PREPARE module Initialization finished with status failed #
   #===========================================================#
#====================================================
Execution of all selected PREPARE modules finished.
#====================================================
==================================================================================================
i readed all the notes, and all required addons are installed, what can i do to pass normally step Initialization in PREPARE?

Similar Messages

  • Limitations of upgrading from ERP 2004 to 2005

    We are evaluation completing an upgrade from ERP 2004 to 2005. However, we found a limitation in note 879335 regarding upgrading the portal.
    We have an Enterprise Portal instance that is separate from the SAP ECC J2EE add-in. The ESS components including XSS run on the J2EE add-in.
    According to this note, we cannot upgrade the XSS component on the J2EE add-in because it
    is not running on EP. Does this mean we need to undeploy the XSS components and then upgrade the J2EE and then install the XSS component? or Do we need to import the XSS component on EP and then
    upgrade?
    Why is this a limitation?

    I have isolated the issue further. In the following code fragment the event is being fired twice the first time and never again:
              If pVal.FormType = 133 And pVal.EventType = SAPbouiCOM.BoEventTypes.et_FORM_LOAD Then
                   '// get the event sending form
                   'SBO_Application.MessageBox("Hello world")
                   oForm = SBO_Application.Forms.GetFormByTypeAndCount(pVal.FormType, pVal.FormTypeCount)
                   oNewItem = oForm.Items.Add("Button1", SAPbouiCOM.BoFormItemTypes.it_BUTTON)
                   oNewItem.Left = 285
                   oNewItem.Top = 382
                   oNewItem.Width = 100
                   oNewItem.Height = 19
                   oNewItem.FromPane = 0
                   oNewItem.ToPane = 1
                   oButton = oNewItem.Specific
                   oButton.Caption = "New Button"
              End If
    End Sub
    The code is an adaptation of the SDK VB.NET sample ('11.SystemFormManipulation'), which is supplied with the latest version of the SDK installation.
    The big question is why is the event being fired twice.

  • Upgrade from ERP 5.0 to ERP 6.0 EHP 4 SP5 - phase START_SHDI_FIRST

    operating system: iSeries V6R1
    (this one is probably for Volker Güldenpfennig...a Happy New Year from Germany!)
    SID: AP4
    instance number normal: 00
    instance number shadow: 08
    hostname: ap400c
    error in phase MAIN_SHADOW/START_SHDI_FIRST:
    shadow instance does not start
    effect: The subsystem R3_08 ist started immediately but no process at all appears in WRKACTJOB.
    The upgrade program hangs for about 5 minutes and then shows the error message below.
    SAP note 525677 is already known but does not help.
    error message:
    To analyse the errors during start of shadow instance,
           view files 'STARTSFI.LOG' and 'DEVTRACE.LOG'
           in directory '/usr/sap/AP4/upg/abap/log'
           Repeat phase until shadow instance is started
           and you can log on instance number '08'.
    STARTSFI.LOG:
    BUT: The file DEVTRACE does not exist at all !!!
    From previous upgrades I knew that this phase brings quite some trouble so I already did this:
    - giving special right *ALLOBJ to user AP408 and AP4ADM (with WRKUSRPRF)
    - SAP note 1168235, page 9: file /usr/sap//upg/abap/SYS/global/ms_acl_info
        1.) deleted
        2.) qualified hostname (HOST=ap400c.apetito.de) used
        3.) (HOST=*) used
    Before restarting the phase I always ended the subsystem as QSECOFR with ENDSBS SBS(R3_08) OPTION(*IMMED).
    showipc 08 shows no entries.
    THIS IS THE INTERESTING PART!!!
    After some deeper investigation I found this:
    In /usr/sap/AP4/upg/abap/bin/SHADOW.TPP there are these lines:
    AP4/startsap    = /usr/sap/AP4/upg/abap/AP4/homeshd/ap4adm/startsap  SID(AP4) INSTANCE(08) PROFILE
    ('/usr/sap/AP4/upg/abap/AP4/SYS/profile/START_DVEBMGS08_ap400c') DVEBMGS08
    AP4/stopsap     = /usr/sap/AP4/upg/abap/AP4/homeshd/ap4adm/stopsap  SID(AP4) INSTANCE(08) WAIT(*YES) WAITTIME(600) DVEBMGS08
    but the directory .../homeshd/ap4adm does not exist all (sounds very UNIX-like to me).
    I changed the SHADOW.TPP file and used "/usr/sap/AP4/upg/abap/exe/startsap" and "/usr/sap/AP4/upg/abap/exe/stopsap"
    but this file seems to be created every time this phase starts.
    So I copied the two programs "startsap" and "stopsap" from /usr/sap/AP4/upg/abap/exe to the manually created directory
    /usr/sap/AP4/upg/abap/AP4/homeshd/ap4adm
    Any ideas? (Maybe the R3INLPGM sucks...?)
    Kind regards
    Rüdiger Höckel
    Edited by: Rüdiger Höckel on Jan 8, 2010 5:39 PM

    Rudiger,
    Hello from cold Minnesota, USA!  We are also upgrading from ERP2004 to ERP 6.0 EHP 4 SP4 on IBM i V6R1 and had a similar START_SHDI_FIRST issue that may be relevant to your problem.
    As in your post no shadow system jobs appeared in WRKACTJOB and no DEVTRACE file was created.  After after some time an RFC category message was shown in the upgrade GUI but turned out not relevent for us.
    A QZSHSH control job launches two (2) SBMJOB commands calling R3INLPGM with parameters to start the shadow instance.  In our case these SBMJOB commands were failing because the SAPINLPGM program invoked by this process wasn't found in library SAP<SID>70UP.  I copied the missing SAPINLPGM program from library SAP<SID>70U to SAP<SID>70UP and restarted the upgrade GUI and the shadow instance then started as expected without further issue.
    If this doesn't solve the problem try temporarily changing your shadow instance ("R3_08") job description (*JOBD) in R3<SID>400 to better trace the failing SBMJOB commands--> CHGJOBD JOBD(R3_08) .... LOG(4 00 SECLVL) LOGCLPGM(YES).  Then rerun the upgrade GUI and after the "start failure" message appears check the QEZJOBLOG (or your default) outqueue for the SBMJOB process SAPSTART and SAPSTRSRV joblogs and see why these are not launching correctly.
    Also should you run into the "Symbol o4_getpwnam (number xxx) not exported..." obscure error updating tp and retrans to current patch levels in the ECC5 (640) system took care of that issue for us.
    HTH and best of luck with your upgrade(s) :>
    Scott

  • Failed to upgrade from ERP 6.0 EHP4 to EHP5

    Dear SAP Gurus,
    we are running ERP 6.00 with EHP4 (HCM-component) based on Windows 2003
    SP2 X64 and SQL Server 2005 SP4 (64-bit).
    We are using SAP Kernel Unicode 7.01 PL 133 (64-bit).
    We intend to upgrade from EHP4 to EHP5.
    Upon running SAPehpi, we encountered issue which stopped us from
    proceeding with the upgrade.
    Case 1: Direct upgrade to 605
    The upgrade failed on PREP_INPUT/VERSCHK_INI with error message: The
    following combination is not supported (SAP_APPL 600, SAP_BASIS 701,
    SAP_ABA 701).
    Case 2: Upgrade SAP_APPL component from 600 to 604 (due to the above
    error message)
    The upgrade failed on PREP_INPUT/VERSCHK_INI with error message:
    Release '701' of component SAP_BASIS is too new.
    Case 3: upgrade via SAINT is not supported by SAP. When uploading the
    Stack XML file, we got error saying that the stack is not supported.
    Attached is the complete list of the current SP Level of Installed
    components.
    Please advise on how we can perform the upgrade to EHP5.
    Many thanks in advance.
    regards,
    Denny

    The thing is Solution Manager was able to produce the XML file during the previous upgrade to 604 (the one without SAP_APPL 604).
    So how can it not be supported by SAP?
    If it is not supported by SAP, how can I proceed from here?
    Component Software C SP-Level Support Package Short description of the component
    SAP_ABA 701 0007 SAPKA70107 Cross-Application Component
    SAP_BASIS 701 0007 SAPKB70107 SAP Basis Component
    PI_BASIS 701 0007 SAPK-70107INPIBASIS Basis Plug-In
    ST-PI 2008_1_700 0003 SAPKITLRD3 SAP Solution Tools Plug-In
    SAP_BS_FND 701 0008 SAPK-70108INSAPBSFND SAP Business Suite Foundation
    SAP_BW 701 0007 SAPKW70107 SAP Business Warehouse
    SAP_AP 700 0021 SAPKNA7021 SAP Application Platform
    WEBCUIF 700 0008 SAPK-70008INWEBCUIF SAP WEBCUIF 700
    SAP_APPL 600 0018 SAPKH60018 Logistics and Accounting
    SAP_HR 604 0035 SAPKE60435 Human Resources
    EA-IPPE 400 0018 SAPKGPID18 SAP iPPE
    EA-APPL 600 0018 SAPKGPAD18 SAP Enterprise Extension PLM, SCM, Financials
    EA-DFPS 600 0018 SAPKGPDD18 SAP Enterprise Extension Defense Forces & Public Security
    EA-FINSERV 600 0018 SAPKGPFD18 SAP Enterprise Extension Financial Services
    EA-GLTRADE 600 0018 SAPKGPGD18 SAP Enterprise Extension Global Trade
    EA-HR 604 0035 SAPK-60435INEAHR SAP Enterprise Extension HR
    EA-PS 600 0018 SAPKGPPD18 SAP Enterprise Extension Public Services
    EA-RETAIL 600 0018 SAPKGPRD18 SAP Enterprise Extension Retail
    FINBASIS 600 0018 SAPK-60018INFINBASIS Fin. Basis
    ECC-DIMP 600 0018 SAPK-60018INECCDIMP DIMP
    ERECRUIT 600 0018 SAPK-60018INERECRUIT E-Recruiting
    FI-CA 600 0018 SAPK-60018INFICA FI-CA
    FI-CAX 600 0018 SAPK-60018INFICAX FI-CA Extended
    INSURANCE 600 0018 SAPK-60018ININSURANC SAP Insurance
    IS-CWM 600 0018 SAPK-60018INISCWM Industry Solution Catch Weight Management
    IS-H 600 0023 SAPK-60023INISH SAP Healthcare
    IS-M 600 0018 SAPK-60018INISM SAP MEDIA
    IS-OIL 600 0018 SAPK-60018INISOIL IS-OIL
    IS-PS-CA 600 0018 SAPK-60018INISPSCA IS-PUBLIC SECTOR CONTRACT ACCOUNTING
    IS-UT 600 0018 SAPK-60018INISUT SAP Utilities/Telecommunication
    LSOFE 600 0018 SAPK-60018INLSOFE SAP Learning Solution Front-End
    SEM-BW 600 0018 SAPKGS6018 SEM-BW: Strategic Enterprise Management
    ST-A/PI 01M_ECC600 0001 SAPKITAR7F Application Servicetools for ECC 600-605
    VIRSAHR 530_700 0012 SAPK-53312INVIRSAHR SAP GRC Access Controls 5.3 for 700 HR S
    VIRSANH 530_700 0014 SAPK-53314INVIRSANH SAP GRC Access Controls 5.3 for 700 HR a

  • Upgrade from ERP 6.0 with AFS 6.0 to ERP EHP4 - AFS 6.4

    Dear all,
    I've upgraded our Solution Manager to latest maintenance (all latest release/all latest Sp/all Oss notes)
    I 'm unable to have a queue with EHP4 - Afs 6.4 from Solution Manager
    If I define a system as SAP ERP 6 with Afs, the sol. man. give me the option to upgrade to EHP4 but 'forget' AFS 6.4.
    If I define a system as Afs Server 6, the sol. man doesn't show me the option to upgrade to EHP4.
    Any Idea to exit from this stall condition ?
    If I choose the option SAP ERP 6.0 to upgrade to EHP4, SAPHEPI will ask me the AFS upgrade CD and all AFS Sp ?
    My target is:
    - ERP 6.0 SPS 16 with AFS SP8 + ERP 6 EHP4 SPS 4 with AFS 6.4 SP 2, the max possibile now.
    Thanks tho who will try to help me.
    Regards

    Hi Reena
    Yes, you can upgrade the system to ECC 6 EHP 6 or 7,
    before that is any other SAP system are connected to ECC6 ?
    If it is yes, Kindly refer the SAP Note, & you require to check those SAP version are supported to ECC 6 EHP 7 ?
    1388258 - Version Interoperability within the SAP Business Suite
    BR
    SS

  • Upgrade from ERP 5.0 to ERP 6.0 EHP 4 SP5 phase KX_SWITCH_1

    operating system: iSeries V6R1
    SID: AP4
    instance number normal: 00
    instance number shadow: 08
    hostname: ap400c
    non-unicode system
    kernel 6.40 non-unicode -> 7.01 non-unicode
    error in phase MAIN_SHADOW/KX_SWITCH_1:
    Last error code set:
    Error message CPF0006 running 'LODSAPKRN DEV(STMF) MNTPNT(UPG '/usr/sap/AP4/SYS/exe/run') KRNLIB(SAPAP470U) APYR3KRN(NO) USERDEF(NO) ONESTEP(*NO) STATFILE('/usr/sap/AP4/upg/abap/log/APYSAPKRN.LOG')'
    note: The mentioned log file is NOT created.
    I have uploaded the relevant logs here:
    http://www.mediafire.com/?knzmiwgkmzn
    Log file KX_SW1.LOG doesn't say that much,
    more interesting is file KX_SW1.SAV in which you can see
    that the kernel library has been filled with lots of files.
    The detail error message can only be seen directly on the iSeries
    when looking at the detailed job log of the SAPUP process:
    BuildO4affileFromDir: Could not process PASE.SAR successfully. 
    BuildLibFromDir: Error creating IFS file container in targetlib.
    LodSapKit: PANIC: Could not finish library SAPAP470U.          
    Failed to load first part of SAP kernel.                       
    and before...
    a STOPSAPCL                                           
    SAPCAR: file 'STOPSAPCL' is inaccessible (broken link)
    Then I tried to run the LODSAPKRN command manually as user AP4OFR
    but now this user cannot log on anymore:
    R3AP4400/R3INLPGM: Cannot determine kernel library for SID AP4  (A.....dd) .                                                 
    As listed in my previous message (error in START_SHDI_FIRST)
    I copied the program SAPINLPGM from library SAP70UP.
    After the new error occured I tried the following steps without success:
    copied the program R3INLPGM from library SAP<SID>70U to SAP<SID>70UP
    on the kernel DVD (that I copied to hard disc) I replaced the files SAPEXEDB.SAR and SAPEXE.SAR (old patch from 2009-04-01)
      with SAPnet patch #66
    because of SAP note 1178421 I also exchanged ILE.SAR with SAPnet patch #74 at these locations:
       /usr/sap/trans/media/51036769/DATA_UNITS/K_701_N_OS400_PPC64/DBINDEP
      and the extracted files ILE_TOOLS (130.492 KB) and iletools (33 KB) at these locations:
       /usr/sap/AP4/upg/abap/exe and /usr/sap/AP4/upg/abap/exenew
    Kind regards from Germany,
       Rüdiger Höckel
    Edited by: Rüdiger Höckel on Jan 14, 2010 11:05 AM

    REMINDER: SID = AP4
    in /tmp are two files: SAPEXE.SAR and SAPEXEDB.SAR (SAPnet kernel 701 64bit non-unicode patch #66)
    Manually building the kernel library SAPAP470U from scratch is successfull:
    as user QSECOFR:
    CLRLIB SAPAP470U
    CLRLIB QTEMP
    ADDLIBLE SAPUP
    LODSAPKRN DEV(STMF) MNTPNT('/tmp') KRNLIB(SAPAP470U) USERDEF(YES) LIST('/tmp/parts')
    EDTLIBL   (-> remove SAPUP from list, only kernel library in list is SAPAP470U)
    FIXR3OWNS LIB(SAPAP470U) OBJ(*ALL)
    APYSAP TYPE(*KERNEL) SID(AP4) DSTLIB(SAPAP470U)
    NOW the user AP4OFR is able to log on again!
    repeating the phase KX_SWITCH_1 leads to this error in process SAPup (iSeries joblog):
    (maybe there is a way to ignore the phase???)
    Objekt TS000065D7 in R3400 Art *OUTQ wurde gelöscht.             
    BuildO4affileFromDir: SAPCAR error message processing            
      /usr/sap/AP4/SYS/exe/run/PASE.SAR:
    spooled file: QPRINT -
    a KERNELLIB                                                      
    SAPCAR: error creating file object for XDNXDAAPI (error 100).    
    Eigentumsrecht für Objekt TS000065D7 in R3400 Art *OUTQ geändert.
    Objekt TS000065D7 der Art *OUTQ in Bibliothek R3400 erstellt.    
    Eigentumsrecht für Objekt GETOBJINF in QTEMP Art *USRSPC geändert.
    Verbindung hinzugefügt.                                          
    Eigentumsrecht für Objekt GETOBJINF in QTEMP Art *USRSPC geändert.
    Eigentumsrecht für Objekt TS000000 in QTEMP Art *USRSPC geändert.
    2 Sätze in Datei X26071 in QTEMP kopiert.                        
    Eigentumsrecht für Objekt GETOBJINF in QTEMP Art *USRSPC geändert.
    1 Einträge gelöscht. 0 Einträge nicht gelöscht.                  
    Objekt TS000065D7 in R3400 Art *OUTQ wurde gelöscht.             
    BuildO4affileFromDir: SAPCAR error message processing            
      /usr/sap/AP4/SYS/exe/run/PASE.SAR:                             
    spooled file: QPRINT -
    a KERNELLIB                                                      
    SAPCAR: error creating file object for XDNXDAAPI (error 100).    
    Aktuelles Verzeichnis geändert.                                  
    BuildO4affileFromDir: Could not process PASE.SAR successfully.   
    BuildLibFromDir: Error creating IFS file container in targetlib. 
    LodSapKit: PANIC: Could not finish library SAPAP470U.            
    Failed to load first part of SAP kernel.                         
    Im Befehl ist ein Fehler aufgetreten.

  • RE: Help required regarding to upgrade from R/3 4.6c to mySAp ERP 2005

    Hi there
    I need help as we are planning to upgrade from R/3 4.6C to my SAP ERP 2005, I need the help in the context that
    . How much it will effect the prevoius functionalities, business processes user exits, reports, transactions and etc which thing one should have to keep in mind I need an general overview on this.
    2. What is the SAP best practice for Upgrade.
    3. Which things should be consider before upgrade.
    Thanks and Kind Regards
    Sohail

    Hi Sohail,
    For functional improvement between the releases you can find information in the release notes for example http://service.sap.com/releasenotes
    Also you can find http://service.sap.com/upgrade for very useful entrypoint for any information regarding upgrade.
    For more information, please check this links.
    http://www.sap.com/solutions/business-suite/erp/pdf/BWP_ERP2006_Upgrade.pdf
    http://www.sap.com/solutions/business-suite/erp/index.epx
    https://websmp103.sap-ag.de/~form/handler?_APP=00200682500000001266&_EVENT=DISPLAY
    Hope this will help.
    Regards,
    Ferry Lianto
    Please reward points if helpful.

  • Effect on IDOC while upgrading from 4.0B to ERP 6

    Hi all,
    We are upgrading from 4.0B to ERP 6.0.
    Are there any changes or modifications that has to be done for the IDOCs(which are developed in 4.0B).
    Any pointers will be very helpful.
    Thanks
    Sreekanth P Krishnan

    Hello,
    We have upgraded from 4.6C to ECC6.0 and did not have any port config issues.
    Things to look for:
      - RFC destinations, do they still work
      - directories used in File type ports, are they still there (they should be)
    Hope this helps a bit
    Regards
    Greg Kern

  • Problems of Port Configuration while upgrading from 4.0B to ERP 6

    Hi all,
        We are upgrading a system from 4.0B to ERP 6. Will there will be any problems from port configuration side? If any please tell what they might be.
    thankyou.

    Hello,
    We have upgraded from 4.6C to ECC6.0 and did not have any port config issues.
    Things to look for:
      - RFC destinations, do they still work
      - directories used in File type ports, are they still there (they should be)
    Hope this helps a bit
    Regards
    Greg Kern

  • SAP HR upgrade from 4.7 to ERP 6.00

    Can someone share some documents like presentations, Functional Upgrade Testing, Data backup, recovery or strategy for HCM functional upgrade related to a Functional Upgrade from 4.7 to ERP 6.00..
    Thanks in advance..
    Offline sharing is discouraged.
    Please use the HCM Wiki instead.
    Thread is locked to stop email train!
    Edited by: Suresh Datti on Aug 15, 2009 3:31 PM

    Hi John,
    You can reach basis people for documents...
    But a few things to keep in mind...
    After upgrade do all the integration testing, features updated or not.. and also suggest your client for Regression Testing..
    kind regards rafi

  • Does anybody know benefices of upgrading SAP ERP from version ECC 6.0 EHP 7 to ECC 6.06 EHP 10?

    An upgrade of ERP SAP from version  ECC 6.0 EHP 7 to ECC 6.06 EHP 10 is being planned in the company I work for. However, I don´t know what the benefices are to   implement this upgrade so I wonder if someone knows benefices of upgrading SAP ERP from version ECC 6.0 EHP 7 to ECC 6.06 EHP 10?
    Regards, Alejandro

    Hi _Miguel
    I am going from ECC 6.0 to ECC 6.06. However, I don´t know what the benefices are to   implement this upgrade so I wonder if someone knows benefices of upgrading SAP ERP from version 6.0 to 6.06
    regards, Alejandro

  • Impact of ERP Upgrade from 4.6C to ECC

    Hi All,
    What is the impact and variations/additons with Impact of ERP Upgrade from 4.6C to ECC from Varinat configuration side.
    BR,
    Krishna

    hi krishna,
    You may loose some of the variants becasue of changes happened during upg for ECC600.I have faced certain problems.
    I know in the upgrade there is a phase(RSUVAINT(2) not sure)  which does a backup of all variants and restores in the end.
    regards,
    vamshi.

  • Upgrade from 46C to ERP 2005

    Can you help me with some questions?
    We are going to upgrade from 46C to 6.0 and we have questions.
    1. How much do we expect the database to grow when we 
       change the format?.
    2. What are the minimum requirements of the workstations
       with the new version?
    3. How the change of EBCDIC to ASCII can affect of Disck
       load?.
    4. What percentage grow the data, when this is changed to
       ASCII?
    5. How the changed to ASCII affect the server.?
    6. Is necessary grow in memory and CPU?
    7. Is possible install several application server Intel
       with the AS/400 Data base, once the changed to ASCII?
    8. Is affected the performance of the system is we
       installing hard disk of 30GB with hard disk of 70GB?
    9. What is the impact if we made the upgrade with Unicode
       or No Unicode?

    Hi,
    Detailed info can be found at
    https://service.sap.com//upgrade
    and
    https://service.sap.com/instguides
    Eddy
    PS.
    Put yourself on the SDN world map (http://sdn.idizaai.be/sdn_world/sdn_world.html) and earn 25 points.
    Spread the wor(l)d!

  • Upgrade from 4.6B to mySAP ERP 2004 ( i.e. ECC 5.0)

    Hi
    We are upgrading from 4.6B to ECC 5.0 without unicode conversion.
    I came to know the from service/sap.com/upgrade website which shares the delta functionality added by SAP during upgrade.
    However, I am still looking around for typical technical hurdles which one faces during the upgrade. As SAP says the upgrade is purely Technical in nature.
    Any feedback/documents you have is welcome.
    Pls share  to my mail id [email protected]
    thanks

    Hi Satish,
    Some of the things which we will do at Upgrades.
    1) <b>Identifing additional warings/erros</b> using EPC(Exteneded Program Check) and correcting them.
    2) <b>Identifying the obselette statements/function modules</b> and correcting them using proper replacement of function modules or adding additional clauses to statements.
    Eg: Replacing oboselette FMs like WS_DOWNLOAD with GUI_DOWNLOAD, UPLOAD with conjuction of CL_GUI_FRONTEND_SERVCIES=>FILE_OPEN_DIALOG with GUI_UPLOAD.
    3) <b>BDC Corrections:</b> This has both technical as well as functional scope of changes.
    Mainly BDC Corrections related to
    a) Addition of new field in upgrade version
    b) Screen number change to parcular filed in upgrade version
    Thanks,
    Vinay

  • Problems with office after upgrade to ERP 6.0

    After upgrade from R3 46c to ERP 6.0 , we installed sap gui 710 with patch 14 and in many frontends a new version of Microsoft Office 2003 SP3.
    In many PCs now we have a problem with macros and templates from PA20 transacction with Documents Management.
    We try to execute a Wor for a personnel number with infotype 910 and I have the nex messages when Windows open the Word 2003.
    "Al abrir este domento, se ejecutará el comando SQL siguiente:
    SELECT * FROM C:/DOCUMEN1andreaCONFIG1TempDatasource_tab.SAP
    Los datos de la base de datos se colocarán en el documento. ¿Desea continuar?"
    If you select "Si", appear another message ~SAP(BA6580C1-BE84.... es un documento principal de combinación. Word no puede encontrar el origen de datos"
    When, word document is dsplayed, we only see name of variable and they are not reeplaced by its value.

    Sorry, but the note is in Spain (I guess), can you please translate?
    We have the same issue on our productive HR system - but not on the development system, what makes it curious.
    When we try to start contracts in word we get the same message
    "Opening this will run the following SQL command
    SELECT * FROM C:\.....Datasource_tab.SAP
    How can we avoid this message?
    Thanks in advance!

Maybe you are looking for