ECC6.0 patch

Hi,
When a patch is applied in ECC6.0, what are the steps to be done in ECC6.0 and BI7.0 before and after?
Thanks.

Hi,
When a patch is applied in ECC6.0, what are the steps to be done in ECC6.0 and BI7.0 before and after?
Thanks.

Similar Messages

  • DDIC_FIELDS_NO_ACCESS Error messages after ECC6 patches

    Dear All,
    we have just completed the support package update process of our productive system.
    Our system is an ECC 6 installation on HP-UX, using an Oracle 10 database.
    After the successful patching process of the ABAP stack and the kernel,
    we procceeded with the use of the SAP Load Generator (sgen) to re-generate all objects of the software components that we use.
    While the job RSPARAGENER8 was running, there were error messages in the system log.
    The error messages in sm21 and st22 were the following:
    DDIC_FIELDS_NO_ACCESS
    Short text               
         Error when accessing Dictionary table "HRDEPBSVASENS_LOG_P14N91_QOTB".          
    What happened?               
         Processing had to be terminated because an internal error     
    occurred when generating the ABAP/4 program "CL_HRDEPBSVASEN_P14N91_TOOLS==CP".          
    Error analysis               
         When accessing the attributes of Dictionary table          
    "HRDEPBSVASENS_LOG_P14N91_QOTB",meaningless values were found.          
    Since this is a Productive System it is very crucial that we solve this
    issue immediately.
    We have not been able to find any relevant SAP notes on this issue and this is why your help will be valuable.
    Please advice for necessary steps.
    Regards,
    Kontogianni Eleni

    Hello!
    I am seem to be having these issue with many tables in my upgraded system (I am upgrading from 4.6c to ECC 6.0).
    I have been able to resolve the problem by activating the tables again.
    Is there note or fix to solve this problem for all tables?
    Would Mass activating all tables be a good idea?
    Has anyone else encountered this?
    So far I have the problem with the following tables:
    T496D, TZPA, TZK01, TZK02, TZC37, TZB0A
    T399X,  T156S
    TVAKZ
    TVLP
    TCORU  
    CAUFV
    AUFK
    AFKO
    Thank you for your help!
    Sean Shea-Schrier
    Edited by: Sean Shea-Schrier on Mar 23, 2010 8:09 PM

  • Patch strategy for ECC6 in SAP NW2004s environment

    Hi Experts,
    Our SAPNW04s landscape consists of ECC6, BI 7.0, EP7.0 , SRM, XI, Solution Manager systems.  We are drafting patch upgrade strategy for the ECC6 system & have 2 options:
    Option 1: Apply patches only in ECC6 & not in other components.
    Option 2: Patch ECC6 together with other components like SRM, BI, EP etc.
    Option 2 will make things complicated but for Option 1 below are the 2 concerns/questions raised:
    1. Option 1 will lead to doing UAT twice for Business Processes which have a tight integration with ECC6, for ex. UAT for data extraction needs to be done after applying patches both in the ECC6 & the BI systems. This will lead to arrange for more user resources.
    2. Due to the tight integration between ECC6 & other components applying patches alone in the ECC6 might lead to other systems like BI, EP,SRM, XI etc at a lower level & they might not be able to connect to ECC6 or work properly with ECC6.
    Can somebody share how they are managing the ECC6 patches upgrade in a big NW2004s environment with other components present, are the ECC6 patches done standalone & other systems like EP, BI follow their own different time schedules for patching or ECC6, BI, EP are recommended to be done together.
    Are there any best practices recommendations from SAP on the same?.  Can somebody share the blueprint or any strategy document they are using.
    Thanks,
    Abhishek

    Hi Abhishek,
    For the reasons you outline in 2, it is recommended to patch entire business scenarios (i.e. business processess that are coupled integrated across systems) together.  Rather than go into a full discussin here, I recommend you see my paper [How To Design a SAP NetWeaver - Based System Landscape |https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50a9952d-15cc-2a10-84a9-fd9184f35366].
    Best Regards,
    Matt

  • Java problem - J2EE status info unavailable

    Hi
    ( Environment: ECC6 patched to NW SP16 / Unicode / 700 Kernel patch 173 / Dbserver=DB2/400 )
    When I start the Application server instance (Windows) with J2EE after applying SP16 of JSPM support package patches, the disp+work.exe on the System Management console has a yellow light and status of :
    Running, message server connection ok; dialog queue time 0.00sec; J2EE status info unavailable.
    The dev_jcontrol trace file has the error messages:
    trc file: "U:\usr\sap\WFD\D00\work\dev_jcontrol", trc level: 1, release: "700"
    node name   : jcontrol
    pid         : 2308
    system name : WFD
    system nr.  : 00
    started at  : Thu Sep 25 15:46:00 2008
    arguments       :
           arg[00] : U:\usr\sap\WFD\D00\exe\jcontrol.EXE
           arg[01] : pf=
    sapdev\sapmnt\WFD\SYS\profile\WFD_D00_dfbhl6
           arg[02] : -DSAPSTART=1
           arg[03] : -DCONNECT_PORT=64990
           arg[04] : -DSAPSYSTEM=00
           arg[05] : -DSAPSYSTEMNAME=WFD
           arg[06] : -DSAPMYNAME=dfbhl6_WFD_00
           arg[07] : -DSAPPROFILE=
    sapdev\sapmnt\WFD\SYS\profile\WFD_D00_dfbhl6
           arg[08] : -DFRFC_FALLBACK=ON
           arg[09] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 2040] Thu Sep 25 15:46:00 2008
    [Thr 2040] *** WARNING => INFO: Unknown property [instance.box.number=WFDD00dfbhl6] [jstartxx.c   841]
    [Thr 2040] *** WARNING => INFO: Unknown property [instance.en.host=sapdev] [jstartxx.c   841]
    [Thr 2040] *** WARNING => INFO: Unknown property [instance.en.port=3241] [jstartxx.c   841]
    [Thr 2040] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    [Thr 2040] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
    [Thr 3504] JControlDPMessageProxy: Thread 3504 started as handler thread for R/3 dispatcher messages.
    [Thr 2040] [Node: bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_13
    [Thr 2040] JStartupICheckFrameworkPackage: can't find framework package U:\usr\sap\WFD\D00\exe\jvmx.jar
    [Thr 2040] JControlCheckRunMode: run mode of the instance = safe
    [Thr 2040] Instance is disabled -> terminate.
    [Thr 2040] JControlCloseProgram: started (exitcode = -11113)
    [Thr 2040] JControlCloseProgram: good bye... (exitcode = -11113)
    Any ideas what is wrong? Have tried restarting the Application server.
    regards
    Michael.

    Hi,
    *I am too getting the following error "Running, message server connection ok; dialog queue time 0.00sec; J2EE status info unavailable."*
    the trace is as follows. Kindly help
    thanks
    Denis.
    trc file: "dev_disp", trc level: 1, release: "700"
    sysno      01
    sid        DM0
    systemid   560 (PC with Windows NT)
    relno      7000
    patchlevel 0
    patchno    52
    intno      20050900
    make:      multithreaded, Unicode, optimized
    pid        2228
    Fri Nov 20 15:43:45 2009
    kernel runs with dp version 210000(ext=109000) (@(#) DPLIB-INT-VERSION-210000-UC)
    length of sys_adm_ext is 572 bytes
    SWITCH TRC-HIDE on ***
    ***LOG Q00=> DpSapEnvInit, DPStart (01 2228) [dpxxdisp.c   1231]
         shared lib "dw_xml.dll" version 52 successfully loaded
         shared lib "dw_xtc.dll" version 52 successfully loaded
         shared lib "dw_stl.dll" version 52 successfully loaded
         shared lib "dw_gui.dll" version 52 successfully loaded
    rdisp/softcancel_sequence :  -> 0,5,-1
    use internal message server connection to port 3901
    Fri Nov 20 15:43:50 2009
    WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds
    ***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  5233]
    MtxInit: 30000 0 0
    DpSysAdmExtInit: ABAP is active
    DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
    DpIPCInit2: start server >sapserver_DM0_01                        <
    DpShMCreate: sizeof(wp_adm)          14080     (1408)
    DpShMCreate: sizeof(tm_adm)          3954072     (19672)
    DpShMCreate: sizeof(wp_ca_adm)          24000     (80)
    DpShMCreate: sizeof(appc_ca_adm)     8000     (80)
    DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064
    DpShMCreate: sizeof(comm_adm)          528064     (1048)
    DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    DpShMCreate: sizeof(file_adm)          0     (72)
    DpShMCreate: sizeof(vmc_adm)          0     (1452)
    DpShMCreate: sizeof(wall_adm)          (38456/34360/64/184)
    DpShMCreate: sizeof(gw_adm)     48
    DpShMCreate: SHM_DP_ADM_KEY          (addr: 05DC0040, size: 4608920)
    DpShMCreate: allocated sys_adm at 05DC0040
    DpShMCreate: allocated wp_adm at 05DC1E28
    DpShMCreate: allocated tm_adm_list at 05DC5528
    DpShMCreate: allocated tm_adm at 05DC5558
    DpShMCreate: allocated wp_ca_adm at 0618AAF0
    DpShMCreate: allocated appc_ca_adm at 061908B0
    DpShMCreate: allocated comm_adm at 061927F0
    DpShMCreate: system runs without file table
    DpShMCreate: allocated vmc_adm_list at 062136B0
    DpShMCreate: allocated gw_adm at 062136F0
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated ca_info at 06213720
    DpShMCreate: allocated wall_adm at 06213728
    Fri Nov 20 15:43:51 2009
    MBUF state OFF
    Fri Nov 20 15:43:53 2009
    EmInit: MmSetImplementation( 2 ).
    MM diagnostic options set: 0
    <ES> client 0 initializing ....
    <ES> InitFreeList
    <ES> block size is 4096 kByte.
    Using implementation flat
    <EsNT> Memory Reset disabled as NT default
    <ES> 1022 blocks reserved for free list.
    ES initialized.
    Fri Nov 20 15:43:54 2009
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 2724
      argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=1044
      argv[5] = -DSAPSYSTEM=01
      argv[6] = -DSAPSYSTEMNAME=DM0
      argv[7] = -DSAPMYNAME=sapserver_DM0_01
      argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    rdisp/http_min_wait_dia_wp : 1 -> 1
    ***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c   1617]
    Fri Nov 20 15:43:55 2009
    ***LOG Q0K=> DpMsAttach, mscon ( sapserver) [dpxxdisp.c   11414]
    Fri Nov 20 15:43:56 2009
    DpStartStopMsg: send start message (myname is >sapserver_DM0_01                        <)
    DpStartStopMsg: start msg sent
    Fri Nov 20 15:43:57 2009
    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    CCMS: Initalizing shared memory of size 60000000 for monitoring segment.
    Fri Nov 20 15:44:00 2009
    CCMS: start to initalize 3.X shared alert area (first segment).
    DpMsgAdmin: Set release to 7000, patchlevel 0
    Fri Nov 20 15:44:01 2009
    MBUF state PREPARED
    MBUF component UP
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]
    DpMsgAdmin: Set patchno for this platform to 52
    Release check o.K.
    Fri Nov 20 15:44:37 2009
    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
    Fri Nov 20 15:44:57 2009
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 1064
      argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=1081
      argv[5] = -DSAPSYSTEM=01
      argv[6] = -DSAPSYSTEMNAME=DM0
      argv[7] = -DSAPMYNAME=sapserver_DM0_01
      argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    Fri Nov 20 15:45:17 2009
    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
    Fri Nov 20 15:45:37 2009
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 2656
      argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=1107
      argv[5] = -DSAPSYSTEM=01
      argv[6] = -DSAPSYSTEMNAME=DM0
      argv[7] = -DSAPMYNAME=sapserver_DM0_01
      argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    Fri Nov 20 15:45:57 2009
    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
    Fri Nov 20 15:46:19 2009
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 1428
      argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=1113
      argv[5] = -DSAPSYSTEM=01
      argv[6] = -DSAPSYSTEMNAME=DM0
      argv[7] = -DSAPMYNAME=sapserver_DM0_01
      argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    Fri Nov 20 15:46:37 2009
    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
    Fri Nov 20 15:46:46 2009
    MBUF state ACTIVE
    Fri Nov 20 15:46:53 2009
    DpModState: change server state from STARTING to ACTIVE
    Fri Nov 20 15:46:57 2009
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 3192
      argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=1131
      argv[5] = -DSAPSYSTEM=01
      argv[6] = -DSAPSYSTEMNAME=DM0
      argv[7] = -DSAPMYNAME=sapserver_DM0_01
      argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    Fri Nov 20 15:47:17 2009
    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
    Fri Nov 20 15:47:37 2009
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 3180
      argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=1141
      argv[5] = -DSAPSYSTEM=01
      argv[6] = -DSAPSYSTEMNAME=DM0
      argv[7] = -DSAPMYNAME=sapserver_DM0_01
      argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    Fri Nov 20 15:47:57 2009
    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
    Fri Nov 20 15:48:08 2009
    WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
    Fri Nov 20 15:48:17 2009
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 952
      argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=1147
      argv[5] = -DSAPSYSTEM=01
      argv[6] = -DSAPSYSTEMNAME=DM0
      argv[7] = -DSAPMYNAME=sapserver_DM0_01
      argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    Fri Nov 20 15:48:37 2009
    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
    Fri Nov 20 15:48:58 2009
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 3192
      argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=1156
      argv[5] = -DSAPSYSTEM=01
      argv[6] = -DSAPSYSTEMNAME=DM0
      argv[7] = -DSAPMYNAME=sapserver_DM0_01
      argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    Fri Nov 20 15:49:17 2009
    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
    Fri Nov 20 15:49:37 2009
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 3660
      argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=1164
      argv[5] = -DSAPSYSTEM=01
      argv[6] = -DSAPSYSTEMNAME=DM0
      argv[7] = -DSAPMYNAME=sapserver_DM0_01
      argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    Fri Nov 20 15:50:01 2009
    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
    Fri Nov 20 15:50:21 2009
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 2208
      argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE
      argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=1171
      argv[5] = -DSAPSYSTEM=01
      argv[6] = -DSAPSYSTEMNAME=DM0
      argv[7] = -DSAPMYNAME=sapserver_DM0_01
      argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    Fri Nov 20 15:50:41 2009
    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
    Fri Nov 20 15:51:01 2009
    DpEnvCheckJ2ee: switch off j2ee start flag
    Fri Nov 20 15:59:24 2009
    WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
    Fri Nov 20 15:59:25 2009
    WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
    Fri Nov 20 15:59:45 2009
    WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
    Fri Nov 20 15:59:46 2009
    WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
    SoftCancel request for T16 U19 M0 received from IC_MAN
    Fri Nov 20 15:59:51 2009
    SoftCancel request for T15 U18 M0 received from IC_MAN
    Fri Nov 20 15:59:52 2009
    ERROR => DpRqCheck: mode 0 in status CANCEL [dpxxdisp.c   6815]
    Fri Nov 20 15:59:56 2009
    SoftCancel request for T14 U17 M0 received from IC_MAN
    Fri Nov 20 16:01:09 2009
    WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
    Fri Nov 20 16:01:10 2009
    WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
    Fri Nov 20 16:01:15 2009
    WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
    Fri Nov 20 16:01:16 2009
    WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
    Fri Nov 20 16:01:17 2009
    WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
    WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
    Fri Nov 20 16:01:18 2009
    SoftCancel request for T16 U22 M0 received from IC_MAN
    Fri Nov 20 16:01:23 2009
    SoftCancel request for T15 U21 M0 received from IC_MAN
    Fri Nov 20 16:01:28 2009
    SoftCancel request for T14 U20 M0 received from IC_MAN
    Fri Nov 20 16:01:29 2009
    ERROR => DpRqCheck: T14 in state TM_SLOT_FREE [dpxxdisp.c   6753]
    ***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c   5104]
    Fri Nov 20 16:01:30 2009
    ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 5901): [dpxxdisp.c   5106]
    -IN-- sender_id DISPATCHER        tid  14    wp_ca_blk   50      wp_id 1
    -IN-- action    SEND_TO_WP        uid  20    appc_ca_blk -1      type  DIA 
    -IN-- new_stat  WP_WAIT           mode 0     len         672     rq_id 527
    -IN-- req_info  MSG_WITH_REQ_BUF MSG_WITH_OH

  • Multiple account assignment switching between distribution indicators not working for service

    Hi Gurus,
    Account assignment distribution function not working post ECC6 patching activity
    we have recently completed ECC6 patching actvity and we are facing issues on processing multiple account assignment in service.
    we create Purhcase order with single account assignment and will process service with Multiple account assignment selecting distribution on qty or percentage basis till patching functionality works fine post patching we are facing issue when we are selecting distribution indicator system provides an error message switching between distribution indicator is not allowed when we continue system ask to enter in case of multiple account assignment select the distribution indicator. could you please suggest me on the issue.
    Thanks in advance.

    we have found a SAP note
    1915000 - SE685 - Switching between distribution indicators is not allowed
    This is now standard behavior.

  • ECC6 SR3 on fighting the problem of system patches

    ECC6 SR3 on fighting the problem of system patches
    My system is ECC6 SR3, and the installation of the system, PI-BASIS patch version number is the first 2005_1_70C months SAPKIPYJ7E How do I upgrade to the PI-BASIS this patch 2006_1_70C how the patch SAPKIPYM01 play ah?
    thanks

    You will need a delta package for this component to upgrade it to 2006_1_700
    Go to -> service.sap.com/swdc
             -> Installations and Upgrades
             -> Plug-Ins
             -> SAP Plug-In
             -> PI_BASIS
             -> PI_BASIS 2006_1_700
    The patches for 2006_1_700 you will find at similar path to above just replace "SAP Installations and Upgrades" with "SAP Support Packages". See [Note 1007796 - Installation/Upgrade Basis Plug-In (PI_BASIS) 2006.1|https://websmp106.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1007796&_NLANG=E] for further information.
    Regards,
    Nelis

  • Which will benefit more: Upgrade 16 patches in 46C or upgrade to ECC6?

    Hi All,
    My company supports a client who has got a SAY system with 4.6C version. The current level of patch is 16 levels less that what SAP prescribes. We need to take a decision on whether we would upgrade the current version with those 16 patches and still remain in 4.6C OR we should upgrade the system to ECC6.0?
    The comparison has to be based on the following parameters:
    1) Cost involved
    2) Time taken
    3) SAP Support
    Any help at the earliest in this regard would be very much appreciated.
    Thanks in advance,
    PP

    This is a question not too easy to answer:
    1.- Cost involved: this depends if you have the hardware for Upgrade or not, if don´t have enough hardware then move on lattest support packages will not cost so much as Upgrade. How standard is the system and complexity of the business processes also makes a difference here
    2.- Time Taken: Is the instalation using lots of customer developments? if not, time taken in both scenarios won´t be that much.
    3.- SAP Support: Here you have one of the main points to upgrade but not the only one, to be able to get support on 4.6C will be higher than using newer versions.
    Now, to be able to upgrade to ECC 6.0 from 4.6C you will need a certain SP level already so the most probable scenario before an upgrade is to move up the SP and kernel Level and then do the upgrade.
    Of course you could include the 4.6C SP instalations as part of the upgrade project so developers and functional people will just fix one time the developments and configurations.
    Hope this helps

  • Java Patches download for ECC6.0

    Hi
    Currently i have ecc 6.0 with ABAP+JAVA Stack. My java stack is on SP18 and need to upgrade. On the same server we have ESS Portal and ADS.
    Kindly suggest me where to download patches in SMP.  Im bit confused with path.
    Thanks
    Regards
    Prateesh K

    Hi Prateesh,
    You can download, from http://service.sap.com/swdc > SAP Support package stacks (left frame) > SAP ERP 6.0 (SAP ERP 2005) (in the right frame).
    Select the appropriate components based on, the usage.
    Or the best way is, if you a Solution manager in your landscape, log in to that, and use DSWP > Operations > Change Management > Maintenance Optimizer > Create New Maintenance Transaction > Select the appropriate system, and continue.
    If will show the current level and you need to select the target level, then it will automatically give the components that you can add to your download basket and approve them.
    Also, download the stack.xml file, which will make the component target SPS level calculated, in JSPM.
    Hope this info helps,
    with regards,
    Rajesh

  • SAP HR patch Ecc6.0 Ehp4 not found after installation

    Hi,
    I have installed Ecc 6.0 Ehp7 but after installation i found SAPHR Patches on SAPHR6.0 .(SAPKE600)
    WAnt SAPHR patches on Ehp4.
    Is there any way which i can do at time of installtion only?
    Now i have to create xml stack file from Solman for upgradation to SAPKE604?
    Kindly suggest
    Regards
    Adil

    Hi Adil,
    After the installation ECC 6.0 EHP 7 , the base component will be at 600.since ECC 6.0 EHP7 is coming as a ready phase installation.
    You need to upgrade all the base coponenet 607 , with the help of SUM.
    So you need to generate the stack and upgrade it.
    With Regards
    Ashutosh Chaturvedi

  • HR - PA upgrade issue (4.6C to ECC6.0)

    dear all,
    we are currently in the process of upgrade from 4.6C to ECC6.0
    and we found this minor issue in the submodule PA:
    using tcode pa20/pa30 we can not see any record of IT0000 Actions using 'overview'
    but the all the detail actions can be displayed..
    the overview (mountain icon) can't show all the records- only happen when we want to overview the infotype IT0000 Actions.
    but all the details that we have recorded in IT0000 Actions, can still be displayed (using spectacle icon)
    this is only happen in IT0000 Actions
    all other infotypes can be overviewed using 'mountain icon' and can be displayed using 'spectacle icon' as normal condition.
    anyone ever gone through the same issue?
    we have updated patch for SAP HR : SP 32 and EA 7.
    the authorization is SAP ALL.
    looking forward to hearing from you.
    best regards,
    dhenny muliawaty (pei pei)

    Hi Abhishek,
    thanks for your reply and your guidance..
    we need more information from you..
    1. how to back up the table, is it right that we need to contact basis and ask our basis guy to back up the tables?
    2. after we do the backup of HR table T512W, before upgrading your HR support package, then we upgrade the support package and after that..
    is it right that we need to restore the table? or that the back up is use to do cross check on the content of the T512W after upgrade?
    V_512W_B                       Valuation Bases                                         
    V_512W_C                       Averages                                                
    V_512W_D                       Processing Classes, Cumulations, and Evaluation Classes 
    V_512W_O                       Complete View T512W                                     
    V_512W_T                       Wage Type Texts                                         
    thanks for informing us that it's a standard practice to backup this table before applying the HR patch to system. how do you know this is a standard practice?
    do you know any other additional standard practices for HR in upgrade project from 4.6C to ECC6.0?? do you have the link of this complete information?
    thank you for your kind attention and support.
    looking forward to hearing from you.
    thanks and best regards,
    dhenny muliawaty (pei pei)

  • Plug in compatability between BW plugin in R/3 and BI - R/3 upgrade to ECC6

    Hello,
    we are running SAP NetWeaver BI 7.0  Release 700 Patch 19.
    Our underlying R/3 system is still 4.6C with plugin 2004_1_46C ( yes, I know it is time )
    We are upgrading R/3 to ECC6 with plug in P701 Patch 3.
    Questions:
    1.) I would like to know where exactly I can see which ECC6 plugin is copmpatible with our BI Version.
    2.) Did anyone who has upgraded to ECC6 experience any particular issues when upgrading the plugin?
    3.) Sense check of approach - so far the simplistic idea from a BW perspective is:
    New R/3 system has been created and connected to BW :
    1.)     In BW ACTIVATE SOURCE SYSTEM
    2.)     In source system connection option : Replicate datasources and activate
    3.)     Transfer global settings u2013 first simulate then update tables u2013 no rebuild should be necessary
    Before the Plugin P 701 in the R/3 ( ECC6 ) system can be upgraded the BW delta queues need to be cleared in the source system ( R/3.)
    4.)     Clear out V3 queue either via BW as part of the jobplan ( or manually via RSA7 but would mean loss of data )
    5.)     After run of batch schedule during posting free period check in RSA7 for entries in delta queue - should be empty    
                         now.
    6.)     Does the clearing of the delta might need to be run twice to clear the queue completely ?????
    8.)                 Deactivate logistics cockpit via SBIW ...LEBW ( is this mandatory ? )
    9.)                 If delta queues are empty and the logistics cockpit is deactivated then upgrade the plug ins in R/3
    10.)               Then repeat step 1-3 and reactivate the logistics cockpit again
    Is this it?
    Many thanks for advise on this.
    Regards
    ChrisAC

    SAP Note : 153967 and
    https://service.sap.com/r3-plug-in should give some information on plug in compatibility...
    8.) Deactivate logistics cockpit via SBIW ...LEBW ( is this mandatory ? )  - I think you just need to desachedule the collection jobs alone and not deactivate the LO Extractors and activate them once again...
    Edited by: Arun Varadarajan on Oct 9, 2009 11:43 PM

  • Report Output is not same as R/3 4.7 and ECC6 ( sort issue)

    Dear Experts,
    I have a problem with external sort used in the program. due to that report output records are not in the same order.
    For example, i am extracting data from BSEG with fields company code, fiscal year, document no, item no, amount and GL Respectively.
    in both the systems (R/3 4.7 and ECC6), data in internal tables are in same order by default.
    but after the external sort using filelds company code, fiscal year and document no.
    output records are sorted exactly with respect to the external sort order in both systems, but for certain line items are not in same order.
    Please check below example.
    For example in R/3:
    684
    2012
    5000000532
    5
    H
    2662.51
    411100
    684
    2012
    5000000532
    4
    H
    13
    555200
    684
    2012
    5000000532
    3
    S
    0.5
    635400
    684
    2012
    5000000532
    2
    S
    12.5
    627800
    684
    2012
    5000000532
    1
    S
    2662.51
    555209
    In ECC6,
    684
    2012
    5000000532
    1
    S
    2662.51
    555209
    684
    2012
    5000000532
    2
    S
    12.5
    627800
    684
    2012
    5000000532
    3
    S
    0.5
    635400
    684
    2012
    5000000532
    4
    H
    13
    555200
    684
    2012
    5000000532
    5
    H
    2662.51
    411100

    The order of extracted records can no be assumed to be constant, any SQL optimizer can change behavior, even without any wide upgrade, but a single database or kernel patch as well as many operation of database administrator can change the order, as well as a change of user behavior, if they fill now another field in selection. So it is good practices to always sort (or use sorted type) internal table extracted or use a ORDER BY clause (provided there is an index in database, else do not)
    Read online documentation of SELECT statement clause ORDER BY
    The order of the rows in the result set refers to all columns that are not listed after ORDER BY, is undefined, and can be different in repeated executions of the same SELECT statement.
    There are also some [MANY > 1000] OSS notes on the subject (look for your database, e.g.  1858427 - Incorrect Sorting of SQL-Select Statement, 1859655 - The result set of an SQL-Select Statement may not be sorted, 1858479 - Result set of select statement is not sorted, 1858569 - Incorrect access to result set of SELECT statement, etc.)
    Also if you sort an internal table and require records with same key values to keep their respective order, use the STABLE clause.
    Regards,
    Raymond

  • SAP GUI 7.10 Compatibility with ECC6 EHP4

    Hello,
    My company is on SAP GUI 7.10 Patch 8 and we are looking to install EHP 4 on our ECC6 system. Can someone tell me if we need to apply the latest patch to SAP GUI for EHP 4 support?
    Does anyone know if there are known issues with SAP GUI 7.10 Patch 8 and EHP 4 if we do not patch?
    Thanks,
    Pete

    Hello,
    We did not find any issue with this, hope all goes well with you.
    Thanks,
    Prasant K Paichha

  • Upgrade 4.6C to ECC6.0 IT0000 can't be overviewed, can only be displayed..

    dear all,
    we are currently in the process of upgrade from 4.6C to ECC6.0
    and we found this minor issue in the submodule PA:
    using tcode pa20/pa30 we can not see any record of IT0000 Actions using 'overview'
    but the all the detail actions can be displayed..
    this is only happen in IT0000
    other infotypes can be overviewed and can be displayed as normal.
    anyone ever gone through the same issue?
    we have updated patch for SAP HR : SP 32 and EA 7.
    the authorization is SAP ALL.
    looking forward to hearing from you.
    best regards,
    dhenny muliawaty (pei pei)

    dear JLJ
    we're still on the upgrade process. i can only share with you our current condition and the lesson learnt.
    we have copy production, upgraded from 4.6C to ECC6.0
    and we did not face authorization issue or any other main issues in HR cause we have not yet implemented the submodules e-recruitment/ESS/other sub modules that are being enhanced in ECC6.0
    our technical team did the oracle database upgrade + 4.6C upgrade to ECC6.0 right away directly after the oracle database upgrade. TST production is considered ok. we only have some minor configurations to be done.
    next when our tech team upgrade the oracle database to ver. 10 in R/3 4.6C production system, and there's a time lag (interval) where our 4.6C production system not directly upgraded to ECC6.0 after the oracle database upgrade done.
    and current condition - production database oracle upgraded, the R/3 4.6C Prod has not yet being upgrade to ECC6.0,
    R/3 4.6C production face the authorization issue (not HR module, but other modules)
    we need to check and apply sap notes/release to solve some errors in 4.6C production system and related modules settle the authorization issue. current progress is still on the technical abap preparation and functional testing.
    it's been scheduled the next step - tech team will upgrade the production system from to ECC6.0 within next week. we hope all will be ok.
    from this experience, my suggestion is that you need to make sure basis team have implemented sap support packages module related/ enhancement packages- latest updated one in your 4.6C system, then you also needs to check sap release notes implemented related with your module.
    would you share the steps have been done in upgrading your production system in detail?
    thanks and best regards,
    dhenny muliawaty (pei pei)

  • TP version problem during upgrade from 4.7 sr2 to ECC6

    Hello All,
    i am doing an upgrade from 4.7 to ECC6 (ultimately i have to upgrade to EHP4). I am stuck in phase PREPARE module Initialization finished with status failed #. Below is the error i am getting. before pasting log file i tried my best to uprade TP level by upgrading the Patch level. but its not taking effact in to SAP system. If i check TP version in STMS >> system >> Check TP tool it shows me old version.
    below is the error log excerpt from file CHECKS.LOG
       #====================================================#
    Requests and information for module Initialization #
       #====================================================#
    ERROR:   The upgrade needs a patched version of R3trans which is
             build on 21.06.06 or later.
             The R3trans in your active SAP kernel is either older or
             the version could not be determined. Call it without
             any option to determine the build date.
             If the build date is too old, you have to replace it
             before you can continue the upgrade.
             Download the latest executable available from the SAP service
             market place and update it before you continue.
             Otherwise, the upgrade tools will be corrupted.
    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.
    ERROR:   The upgrade needs a patched version of tp with version
             number 340.16.05 or higher.
             The tp in your active SAP kernel is either older or the
             version could not be determined. Call it without any option
             to determine the version.
             If the version is too old, you have to replace it before
             you can continue the upgrade.
             Download the latest executable available from the SAP service
             market place and update it before you continue.
             Otherwise, the upgrade tools will be corrupted.
    ERROR: To be able to use ASU Toolbox, your system requires
           the ST-PI software component with at least Support Package Level 8
          After the update is done, the module must be repeated!
           For more information, see the upgrade documentation
    INFO:       The upgrade strategy for the addon ABA_PLUS
                is described in note: 632429
    INFO:       The upgrade strategy for the addon APPINT
                is described in note: 632429
    INFO:       The upgrade strategy for the addon BP-R3PF
                is described in note: 632429
    INFO:       The upgrade strategy for the addon FINBASIS
                is described in note: 438521
    INFO:       The upgrade strategy for the addon LSO
                is described in note: 503468
    INFO:       The upgrade strategy for the addon LSOFE
                is described in note: 503907
    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 SLL_PI
                is described in note: 1306751
    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:       The upgrade strategy for the addon WP-PI
                is described in note: 632429
       #===========================================================#
    PREPARE module Initialization finished with status failed #
       #===========================================================#
    i downloaded the 47 kernel files SAPEXEDB_304-20001172.SAR and SAPEXE_304-20001172.SAR and installed the kernel file. if i check TP version from command level it shows me 340.16.62, but in SAP STMS it shows me 340.16.03. Can somebody explain what shoulkd i do?
    Can i know also if i can update SAP Kernel from 4.7 sr2 to NW7.0 without upgrading even started?
    If somebody can tell me the exact number of CDs to use to upgrade from 4.7 SR2 to ECC6 EHp4, that would be very
    nice.
    Mani

    Hi Mani,
    ERROR: The upgrade needs a patched version of R3trans which is
    build on 21.06.06 or later.
    ERROR: The upgrade needs a patched version of tp with version
    number 340.16.05 or higher.
    show that the tp and R3trans used by the source 470 system are old.
    You should download the latest tp and R3trans for kernel 470, and
    replace the old tp and R3trans with the downloaded ones under the 470 kernel directory. The 470 kernel directory is specified by parameter DIR_EXECUTABLE which is usually /usr/sap/<SID>/SYS/exe/run.
    Please note that there is also a kernel directory under /<DIR_PUT>/<SID>/SYS/exe which is for the the target system 700. Please do not replace tp and R3trans under this directory with the ones downloaded for kernel 470.
    NO, you cannot update SAP Kernel from 4.7 sr2 to NW7.0 without upgrading even started. Kernel upgrade will be done by SAPup automatically.
    With Best Regards
    Julia

Maybe you are looking for