ECC 6.0 EHP-4 upgrade Issue in phase MAIN SHDRUN/ALTNTAB FILL were negative

Hi Basis Expert,
while doing ECC 6.0 EHP-4 Upgrade in MAIN_SHDRUN/ALTNTAB_FILL phase we are getting the following issue please help us.
Checks after phase MAIN_SHDRUN/ALTNTAB_FILL were negative!
Last error code set: BATCH JOB RDDNT2MT FAILED: Error(s) found in the log(s), accumulated in "ALTNTFI.ELG".
We check the shadow instance is up and we can log in to the system. Check ST22 and SM21 notice no error.
Check the JOB RDDNT2MT (SM37) successfully running and all the job finish without any error.
Hope anybody can share a bit your experience on this issue. we try search the note and  find the forum but no luck.
Thanks

Hi,
> 2EETG011 "No shadow system""(environment parameter)""auth_shadow_upgrade"
> 2EETG011 "No shadow system""DB-connect not against shadow tables !"
>
It looks from your log that shadow system is not able to connect to database. Please check your shadow system. Check below link as well:
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/ecc-6-upgrade-issue-in-phase-altntab_fill-1556272
Thanks
Sunny
Edited by: Sunny Pahuja on Oct 15, 2010 1:27 PM

Similar Messages

  • CRM 7.0 EHP-1 Upgrade Issue In phase MAIN_SHDIMP/SUBMOD_CP2SHD

    Hello All,
    Im in the process of upgrading SAP CRM 5.0 to SAP CRM 7.0 EHP-1,By using SAPUP Tool in phase  MAIN_SHDIMP/SUBMOD_CP2SHD/SUBMOD_DIFFCP2SHD/DIFFEXPADDI
    Single errors found in log file DIFFEXPAI.ELG..
    The  DIFFEXPAI.ELG Log Says
    2EETW000 sap_dext called with msgnr "4":
    2EETW000 -
    db call info -
    2EETW000 function:   db_dynpro_interface_ext
    2EETW000 fcode:      DI_MODIFY
    2EETW000 tabname:    SFIELDS
    2EETW000 len (char): 44
    2EETW000 key:        /SSA/ABS                                1000
    2EETW000 retcode:    4
    2EETP200 Export with errors, request will not be imported
    Cause
    The export was finished with errors or terminated (return code >= 8).
    System Response
    The request is not imported. Instead it is set back to "can be changed"
    in the source system.
    What to do
    The export log contains remarks concerning the reason for the incorrect export. Correct the error and repeat the export.
    Immediate response appriciated..
    Thanks,
    Syed

    Hello All,
    Im in the process of upgrading SAP CRM 5.0 to SAP CRM 7.0 EHP-1,By using SAPUP Tool in phase  MAIN_SHDIMP/SUBMOD_CP2SHD/SUBMOD_DIFFCP2SHD/DIFFEXPADDI
    Single errors found in log file DIFFEXPAI.ELG..
    The  DIFFEXPAI.ELG Log Says
    2EETW000 sap_dext called with msgnr "4":
    2EETW000 -
    db call info -
    2EETW000 function:   db_dynpro_interface_ext
    2EETW000 fcode:      DI_MODIFY
    2EETW000 tabname:    SFIELDS
    2EETW000 len (char): 44
    2EETW000 key:        /SSA/ABS                                1000
    2EETW000 retcode:    4
    2EETP200 Export with errors, request will not be imported
    Cause
    The export was finished with errors or terminated (return code >= 8).
    System Response
    The request is not imported. Instead it is set back to "can be changed"
    in the source system.
    What to do
    The export log contains remarks concerning the reason for the incorrect export. Correct the error and repeat the export.
    Immediate response appriciated..
    Thanks,
    Syed

  • Upgrade issue in phase PREP_IMPORT/TOOLIMP_TOOLDEL_PRE were negative

    Hello Team,
    Got hanged at the phase PREP_IMPORT/TOOLIMP_TOOLDEL_PRE were negative,.
    Error:
    Checks after phase PREP_IMPORT/TOOLIMP_TOOLDEL_PRE were negative!
    Last error code set: Detected 1 aborted activities in 'PHASES.ELG'<br/> Calling 'D:\usr\sap\XXX\DVEBMGS00\exe/tp' failed with return code 13, check D:\Software\SUM\abap\log\SAPup.ECO for details
    Log file says:
    EXECUTING D:\usr\sap\XXX\DVEBMGS00\exe\tp.EXE "pf=D:\Software\SUM\abap\var\DEFAULT.TPP" import all XXX
    This is D:\usr\sap\XXX\DVEBMGS00\exe\tp.EXE version 380.03.95 (release 738, unicode enabled)
    Could not open the ICU common library.
    The following files must be in the path described by
    the environment variable "PATH":
    icuuc50.dll, icudt50.dll, icuin50.dll [D:/depot/bas/741_REL/src/flat/nlsui0.c 1535] pid = 12148
    PATH is currently set to D:\usr\sap\XXX\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\j2sdk1.4.2_24-x64\bin;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;D:\usr\sap\XXX\SYS\exe\uc\NTAMD64  [D:/depot/bas/741_REL/src/flat/nlsui0.c 1538] pid = 12148
    stopping on error 13 during MAIN IMPORT
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 13
    WARNS: Highest tp internal warning was: 0118
    tp finished with return code: 13
    meaning:A tool used by tp got a signal from operating system
    tp=>sapparam(1c): No Profile used.
    tp=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: stopping on error 13 during MAIN IMPORT
    SAPup> Process with PID 12212 terminated with status 13 at 20140515155156!
    ### Phase PREP_IMPORT/TOOLIMP_TOOLDEL_PRE:
    Please help me out,..
    Thank you,
    Mohan Karamala.

    I have cancelled the upgrade and tried again,..but got hanged with the same problem,..
    Please help me,. or can i raise a ticket with SAP.???
    Log details:
    ### Phase PREP_IMPORT/TOOLIMP_TOOLDEL_PRE:
    SAPup> Starting subprocess in phase 'TOOLIMP_TOOLDEL_PRE' at 20140519045354
        ENV: DBMS_TYPE=mss
        ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
        ENV: PATH=D:\usr\sap\PS1\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\j2sdk1.4.2_24-x64\bin;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;D:\usr\sap\PS1\SYS\exe\uc\NTAMD64
        ENV: SAPSYSTEMNAME=PS1
        ENV: dbs_mss_schema=ps1
        ENV: rsdb_ssfs_connect=0
    EXECUTING D:\usr\sap\PS1\DVEBMGS00\exe\tp.EXE "pf=D:\Software\SUM\abap\var\DEFAULT.TPP" import all PS1
    This is D:\usr\sap\PS1\DVEBMGS00\exe\tp.EXE version 380.03.95 (release 738, unicode enabled)
    Could not open the ICU common library.
       The following files must be in the path described by
       the environment variable "PATH":
       icuuc50.dll, icudt50.dll, icuin50.dll [D:/depot/bas/741_REL/src/flat/nlsui0.c 1535] pid = 2560
    PATH is currently set to D:\usr\sap\PS1\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\j2sdk1.4.2_24-x64\bin;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;D:\usr\sap\PS1\SYS\exe\uc\NTAMD64  [D:/depot/bas/741_REL/src/flat/nlsui0.c 1538] pid = 2560
    stopping on error 13 during MAIN IMPORT
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 13
    WARNS: Highest tp internal warning was: 0118
    tp finished with return code: 13
    meaning:
      A tool used by tp got a signal from operating system
    tp=>sapparam(1c): No Profile used.
    tp=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: stopping on error 13 during MAIN IMPORT
    SAPup> Process with PID 7332 terminated with status 13 at 20140519045404!
    Thank you,
    Mohan Karamala.

  • Upgrade from ECC 6.0 EHP 4 to EHP 7.0 influence on SRM Add-On

    Hi everyone,
    We want to upgrade our ECC 6.0 EHP 4 to ECC 6.0 EHP 7. We are currently running SRM 7 EHP1 as ERP Add-On in the one-client scenario.
    I have read the EHP7 Upgrade/restriction note also as the SAP Note 963000 - Usage and release of SRM as AddOn to ECC in ERP 6.0
    But i did not find the information if we have to upgrade our SRM 7 EHP 1 to EHP3.
    Please make this clear for me.
    Best regards,
    David

    Yes, you will need to upgrade the SRM system to EHP3.
    1951805 - Adjusted Version Interoperability for Business Suite 7i2013
    1388258 - Version Interoperability within the SAP Business Suite
    You can make use of the UDA tool to confirm this.
    http://service.sap.com/uda
    As you are upgrading the ERP system to EHP 7 which is based on NetWeaver 7.4 you will need to upgrade the other systems like SRM, BW to a supported release.
    Regards
    RB

  • Upgrade issues in moving Exits and BADI Enhancements to ECC 6.0

    Hi All,
    I want to know when moving customer enhnacements including badis and exits etc.,  while upgrading from R/3 to may be ECC 6.0 what kind of issues will be  encountered .
    Will there be manual efforts required to import all of the ones migrated to this new framework.
    To my understanding the ones which exits in the same way can be imported in the new system however what about the ones migrated like conventional badis being included in enhancement-spot.
    I belive there would be issues because of the new enhancement framework and not all enhancements rather a good number of them would report issues as they might have got incorporated in this new technique.
    Please suggest with some logical explanation.
    To be precise let me add here, for example we have a badi implementation in old release. now when we import it to ECC 6 where badi implementation exits only in a container Enhacement implementation. Now my question is whether we have to create an enhacement implementaion for the badi implementation or not? i.e manual efforts will be required or not?
    thanks and regards,
    Vikas.
    Message was edited by:
            Vikas Taneja

    Hi Nikunj ,
              Thanks , I have one problem . I now installing AFS 6.3 ADDON in our server , While installing i got the message box given below .
    REPEAT      SKIP     CUST.COCKPIT
    PHASE CHECK_REQUIREMENTS :EXPLANATION OF ERRORS
    "THE SYSTEM HAS FOUND THE NUMBER OF OPEN DATA  REQUESTS "
    Kindly tell me , what i have to do .
    Regards
    Selvan

  • 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

  • EHP Upgrade Issue - Java Stack

    Hi,
    Our Source System at NW 7.0 SP13 and we are upgrading the system to EHP1 SP03.
    Upgrade failed at Downtime > DEPLOY_ONLINE_DEPL phase.
    Error log:
    Sep 9, 2009 10:11:51 PM [Error]:                       com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
    Sep 9, 2009 10:11:51 PM [Error]:             com.sap.sdt.jspm.unattended.RequestController.addContextInfo(RequestController.java:178) [Thread[main,5,main]]: Deployment of queue sapjup-queue completed with error
    JSPM version is 7.01.3.0.15. Current JSPM log directory is /usr/sap/XPD/JC00/j2ee/JSPM/log/log_2009_09_09_16_09_42.
    Sep 9, 2009 10:11:51 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:698) [Thread[main,5,main]]: The deployment of the queue failed.
    Sep 9, 2009 10:11:51 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.deploy.SAPJupJSPMDeployer.deployList(SAPJupJSPMDeployer.java:68) [Thread[main,5,main]]: Could not execute deployment of stack file /usr/sap/trans/EPS/in/XPD.xml.
    Sep 9, 2009 10:11:51 PM [Error]:      com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.execute(PhaseTypeDeploymentManager.java:519) [Thread[main,5,main]]: Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action.
    Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase UPGRADE/DEPLOYMENT_BASED_UPGRADE/DEPLOY_ONLINE_DEPL has been completed.
    Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2009/09/09 22:09:42.
    Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2009/09/09 22:11:51.
    Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:02:08.248.
    Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
    I went through the following link , proceeded with option 2, But still getting same error.  
    Portal Upgrade Issue
    Please advise the resolution for the issue I have.
    Thanks in advance
    Regards
    Srinivas
    Edited by: Srinivas Dasari on Sep 10, 2009 5:48 AM
    Edited by: Srinivas Dasari on Sep 10, 2009 5:48 AM

    Issue resolved

  • Potential Conflict? - ECC 6.0 EHP 4 vs. SAP PI 7.0 SP12

    Hi Experts - We are currently upgrading our ERP system to ECC 6.0 EHP 4.
    Our middleware layer is a SAP PI 7.0 in SP12.
    Are there potential conflicts between these two? Maybe around Proxies?
    My current understanding is that SAP PI isn't closely coupled with the ECC system (we mainly use IDocs, some Proxies),
    so there shouldne be any issues.
    Do you have a different view or experiences? Thanks for your help.
    Best Regards, Mathias.

    Mathias,
    I would suggest to go through the upgrade document to get the exact issues if any are there:
    http://service.sap.com/instguides -> SAP Business Suite Applications -> SAP ERP -> SAP ERP 6.0 -> Upgrade. Then select the OS and Database.
    Regards,
    ---Satish

  • EHP 7 upgrade & Mopz in Solman 7.1 SP 8

    Hi Everyone,
    I am currently working on EHP 7 upgrade for my ECC 6 EHP 6 system. I began my work in ECC with SLD data push and SMSY, LMDB config, in Solman now moved on with MOPZ config to download EHP SPS. I have a query here, is it important to have the entire system data updated with SMSY and LMDB in Solman? i understand that MOPZ checks the current system Patch level from SMSY/LMDB and based on our target selection it calculates and recommends. just wondering how exactly it happens!. Bacause we have our BO system and few other non SAP systems in the landscape that are not updated with the SMSY/LMDB but they also should be considerd for the upgrade to check if there are dependencies.
    so my question is, do we have to push data from non sap also and maintaine in SMSY and LMDB before we perform EHP SPS download from MOPZ?
    other question is, if we perform upgrade in a ECC Sandbox environment (usually a copy of Production), it is not necessary to have sandbox for Portal, PI and other systems. so what is the recommended approach here? do we have to select the Developement  ECC system from MOPZ so that we will have other Dev systems (PI, Portal.,..etc) present in the SMSY & LMDB and MOPZ recommendation will be perfect?
    please help me understand this
    Thanks,
    Shiv

    Instead of reviewing SMSY, you should switch over to the LMDB as it is the future for system data in SolMan.
    The reason its telling you ERP 6.0 SPS25 is because it is not taking into account your Ehp, SAP still has to support customers who haven't taken the Ehp (perhaps unicode issues, 32 bit to 64 bit, etc) so this is a way to compare.  I found a bar graph that explained this in a very simple picture, however I can't find it online and leads me to believe I read/saw it in a book.  Also think of this my company is currently updating ECC from Ehp 5 SPS 4 to Ehp7 SPS 4, the SPS are the same due to the Ehp change and resetting the SPS counter back to 0, but in mopz I believe it shows SPS 28 or 29 for ECC 6.0; so essentially there is nothing you can or need to fix for the system data.  If this is still confusing I will try to track down the bar graph example I saw.
    As for logical components you can create your own (and is advised to do so as SAP could remove entries on you during a SolMan upgrade) so you could list it as z_ERP or zEhpERP or z_ECC; however it makes sens to you and your co-workers/customer, when you manage the system and the button that allows you to configure the system, the first section in the new window stays red until you assign a logical component to the system.  So you might already have something assigned to the system(s).
    SAP doesn't list it as BO, and I'm not sure if you can run a successful mopz on BO systems; if you leverage the PAM at SAP you can track down dependencies.  I also believe Process Orchestration is only 7.3/7.31/7.4 which is compatible with Ehp 7.
    SAP PAM:  http://service.sap.com/pam
    As for BO, do you have the following under the SWDC?
    Installations and Upgrades - B" SBOP BI platform (former SBOP Enterprise)" SBOP BI PLATFORM (ENTERPRISE)" SBOP BI PLATFORM 4.1

  • About to put EHP4 onto ECC 6 - are EHP's for other SAP systems required?

    Hi All,
    In our landscape we have ECC 6, Solution Manager, SRM, BI and Portal. we are about to start a project to put EHP4 onto the ECC 6 system, as a pre-requisite to this we are also putting  EHP1 onto our Solution Manager system.
    I have been told that we may also need to put EHP's onto all the other systems in our environment, does anyone else know if this is necessary as I assumed that the systems would still be compatable without the EHP's on SRM, BI and the Portal.
    Thanks
    Simon

    It is not required, but I would recommend it.
    I just upgraded to EHP4 in ECC and also applied EHP1 to Solution Manager, XI, BI, and the Portal.  This client is still using SRM 5.5 so we just applied Support Packages to it. The systems will still be compatible if you leave them alone, though there may be a few notes that have to be applied for some functionality.  But since you are already going to have a maintenance window for ECC, you may as well upgrade the auxiliary systems while you are at it.  If it is anything lik ethis environment, the other systems can be upgraded during wait times for the larger ECC system.
    We also encountered very few issues related to applying the enhancement packages, so testing was very smooth.

  • SRM 7.0 PO not replicated to Backend ECC 6.0 Ehp 4

    Hi SRM Gurus,
    SRM 7.0  SP 8 - ECC 6.04 SAPKH60406 ECS
    RFx Response to PO -
    SRM Local PO is created and is in held status.  Purchaser gives the source of supply and Acc Assignment and order it.
    PO now is in Ordered status.
    Issue: this PO is not replicated to Backend ECC 6.04.
    Did the Debugging as follows:
    1.  BP at B46B_DPO_TRANSFER.
    2.  Got the PO GUID from the BBP_PD transaction.
    3.  FM BBP_PD_PO_TRANSFER_EXEC, execute it and it  stopped in the breakpoint.
    4.  On 'FUNCTION 'BBP_PO_INBOUND' DESTINATION lv_destination',  hit F6.
    5. Checked  lt_bapi_return details.
    Here there should be information regarding some error during the PO copy to backend.
    With this error message you can check why the PO was not created in backend.
    ERRORS from Backend are as follows:
    1.   No instance of object type PurchaseOrder has been created. External reference:   E  BAPI 001
    2.   Document contains no items       E    ID 06   Number 010
    3.   Please enter items first.              W   ID 05                 005
    No XML messages in SXMB_moni both in SRM side and ECC side.
    What am i doing wrong here?  Any help is highly appreciated.
    with regards,
    Freemind

    RZ20 errors:
    Local Errors:   Business to Business Procurement(600)
    Error reading export data for EXEC transfer of purchase order
    Error in local purchase order; no update of references in EXEC system
    Backend Errors:
    PO 3000000051: No instance of object type PurchaseOrder has been created. External reference:
    Purchase order 3000000051: Document contains no items
    Purchase order 3000000051: Transfer Failed; Resubmit
    Since we are in SRM 7.0 ECC 6.04 Ehp 4,  with PI 7.11 + ROS and no SUS.
    doent the system uses ESOA Service for PO replication.
    We did CCTR / CPPR scenarios too. Both are sucessful.
    Do we need to impl BADI PUR_SE_PO_INTERFACE_OUT_SELECT
    But thats for Service hierarchy and Service POs -  We dont have Service hierarchy or SUS in our SLD.
    IF PO replication also uses PI, what configuration do i need to do?

  • Problem with ECC 5.0 Upgrade in JOB_RASUVAR1 phase of PREPARE

    I am upgrading 4.6B system (copy of production to build QA system) on Tru64 with 3TB Oracle DB. The JOB_RASUVAR1 phase of PREPARE in running for about 115 hours. This phase saves existing variants for future conversion. There is a job running at the SAP level which using a lot of CPU, but no active Oracle session for this job. The same job took less than an hour on development system (200GB DB). So far the response from SAP has been like "Unfortunatly there is no possibility to improve the performance of the reports RASUVAR1 and RASUVAR2 during the upgrade" because this phase does not happen during production downtime.
    Did anyone else face similar problem?

    Hi Kausik,
                  we recently upgrade our client systems from 4.6c to ECC 5.0, on unix environment. we too faced similar kind of problem, our job_rasuvar1 in prepare phase took almost 70hrs. after raising a msg with SAP, we were asked some correction in function module.."FASU_RS_VARIANT_CONTENTS"..check whether the following changes are already available..or not
    <b>the necessary change:</b>
    replace the line
    PERFORM fill_tables_ps TABLES objects
    with the line
    PERFORM fill_tables_ps(saplsvar) TABLES objects "CHANGE
    in function module FASU_RS_VARIANT_CONTENTS
    2) To fix this issue I would recomment, that you stop the JOB_RASUVAR1.
    Then please implement the corrections of note 712297. After this please
    clear out all the entries in DB tables TASUVCAT, TASUVSVO and TASUVSVD.
    You can do thie for example via transaction SE14.
    Then implement the following modification to ABAP RASUVAR1:
    FORM return_content USING taskname.
    RECEIVE RESULTS FROM FUNCTION 'FASU_V_VARIANT_CONTENTS'
    TABLES
    valutab = gt_params
    OBJECTS = gt_objects
    EXCEPTIONS
    syst_except = 1
    communication_failure = 2
    system_failure = 3
    variant_non_existent = 4
    variant_obsolete = 5
    error = 6.
    g_error = sy-subrc.
    g_returned = 'X'.
    data: l_count type i. "INSERT MOD
    describe table gt_params lines l_count. "INSERT MOD
    if l_count gt 20000. "INSERT MOD
    g_error = 7. "INSERT MOD
    endif. "INSERT MOD
    ENDFORM. " return_content
    After this you can restart the JOB_RASUVAR1 by just call report
    please try with this & let me know. and 1 more thing, this phase again depends on database size (in our case, for 1.8TB it took 6hrs).
    with regards,
    Raj

  • SRM 7.01 with ECC 6.0 EHP 7.0

    Hi Guys,
    Does anyone have an idea on SRM 7.01 compatibility with ECC 6.0 EHP 7.0. Any things needs to be taken care from SRM side after an upgrade to EHP 7 in ECC side.
    Please share your experience.
    Thanks for your reply in advance.

    Hi Imran,
    It is compatible, But still for confirmation please see the product availability matrix.
    https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/support/pam/pam.html?smpsrv=https%3A%2F%2Fwebsmp203.sap-ag.de#pvnr=01200615320900003495&ts=4&pt=t%7Co
    Best regards,
    Rohit

  • Upgrade issues OBIEE 10g to 11g along with OBIA upgrade

    Hi,
    I have to upgrade OBIEE 10.1.3.4.1 to OBIEE 11.1.1.5 along with OBIA 7.9.6.1 to 7.9.6.5(Informatica 8.6.1 to 9.0.1) at my client location and I have very little knowledge on it. and want to know/have help documents for upgrade.
    And if anyone in the forums involved in upgrade please list the errors/issues occured during upgrade and after upgrade.
    1. OBIEE 10g to 11g upgrade issues??
    2. OBIA OBIA 7.9.6.1 to 7.9.6.5 upgrade issues along with 10g to 11g??
    3. Informatica 8.6.1 to 9.0.1 upgrade issues??
    4. DAC upgrade issues??
    any response for my questions is appreciated.
    Thanks
    Jay.
    Edited by: Jay on Apr 11, 2012 9:11 AM

    HI Jay,
    We cannot explained thread list here, If you get any errors plz post me,will try to help out.
    This is oracle document link - This document has given step by step with screen shots upgration for 10g to 11g ,Please refer the below link.
    http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm
    http://obieemanu.blogspot.in/2011/05/rpd-upgration-from-10g-to-11g.html
    http://docs.oracle.com/cd/E21764_01/upgrade.1111/e10125/ua_command_line.htm#ASMAS149
    Award points it is useful.
    Thanks,
    satya

  • Report generation toolkit upgrade issues

    I have created multiple vi's in that utilize the previous report generation toolkits specifically using the Generate Report Get Data to Modify.vi and the Generate Report Set Modified Data.vi.  Obviously the report reference has now changed in 8.6's version of the report generation toolkit and these vi's do not exist in the 8.6 library anymore.  What vi's do I need to replace these functions with to make this code work.  Can anyone tell me what the work around is to solving this problem.  This is a picture of the code.
    BJD1613
    Lead Test Tools Development Engineer
    Philips Respironics
    Certified LV Architect / Instructor
    Attachments:
    code.JPG ‏92 KB

    Hi BJD1613,
    The Report Generation VIs on the LabVIEW Palettes mutate properly. However, you may run into upgrade issues if VIs distributed with LabVIEW, but not available in the Palettes are used in the code. Hence, I would caution against using them for the same reason.
    In this case, the specific references do exist in the report generation classes; however, since they are private, they cannot be accessed by VIs outside the respective classes. A temporary workaround for now is mentioned in the following KB 4OOCSJ4M Getting References in Report Generation Toolkit 1.1.3 with LabVIEW 8.6.  
    This was reported to R&D (CAR# 123064) for further investigation

Maybe you are looking for