ERP 5.0 to ERP 6.0 upgrade: Activities in advance

ERP 5.0 to ERP 6.0 upgrade: What activities can advance in the upgrade project, for missing three months for the server. ?
Thanks

Get a Solution Manager up and running, and run the configuration for Maintenance Optimizer mentioned in
https://websmp106.sap-ag.de/~sapdownload/011000358700000639422012E/MaintPlan_Guide_71_SP05.pdf .
Best regards,
Miguel Ariño

Similar Messages

  • ERP 2005 and SAP ERP 6.0 are same

    Hi friends,
    First of all why i have asked ERP 2005 and SAP ERP 6.0 are same or not because i am creating a new system under transaction solution_manager in the solman system for the installation of the EHP4 packs.
    The problem here is when i create a new system for SAP ERP, the product version that is displayed is SAP ERP 2005, my system doesn't show SAP ERP 6.0, will that make much difference.
    IsSAPERP 2005 and SAP ERP 6.0 are same.
    thanks.
    anurop

    > I am not getting the option SAP ERP 6.0 but i am getting only SAP ERP 2005 , is there  any other way i can get SAP ERP 6.0 or can i leave it as it as SAP ERP 2005 and start downloading the EHP4 packs thorugh the Solution manager.
    The given note contains a step-by-step configuration how to change that - including a PDF as attachment with screenshots.
    You need at least SolMan SP17 to get EHP4.
    Markus

  • Show ERP Sales order adn ERP Quotes in Interaction History

    Hi ,
    I have a requirement to be able to search for the ERP sales orders and ERP quotes created via CRM 70 IC.
    When I create ERP Sales order and ERP quote they do tie up to the Interaction record, but when I try search for the same using the Sales order and Quotes search category in the Interaction history, I donu2019t see any results.
    Has anyone done this before in any assignments before? If yes can please throw some light on how you handled it.
    Is development required compulsory for this requirement to be fulfilled?
    Thanks,
    Ravi

    There are some limitations using ERP sales orders (there is a decent OSS note that i don't recall the number)
    Do your ECC orders replicate back to CRM????
    IN IMG t-code CRMC_IC_AUI_MAINCAT for the inbox search yuo can set the search to be ERPORDER (means inbox will search in ECC for the document type)  where ONEORDER is searching CRM for the document.

  • 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

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

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

  • Moving transport from Lower ERP Version to Higher ERP Version?

    Hi All,
    I got a quick question regrads to Transporting object frpm ERP 6.0 SP 13 and ERP Ehp 4.0 SP 3.
    Currently, We went Go-live with ERP 6.0 with SP13, as part of Release 1 Landsape.
    ECD ---> ECQ --> ECP
    For release 2, which is starting in few months, we are planning to Build a Project Landscape seprate from Support landsacpe.
    ECD --> ECQ
       |                  -
    >     ECP
    E2D --> E2Q
    2 = Release 2 SID name
    Our Support landscape will be on ERP 6.0 with SP 13
    and Project landscape we wanted upgrade to ERP 6.0 ehp 4.0 with SP 03. To keep the landscape consistent, whatever work we do on ECD (R1 lanscape), we would like to import to R2 E2D as well, so when we Go-Live with R2 implementation, then our DEV and QA systems will be consitent.
    My Question would, can I move/transport object from R1 (lower ERP version) to R2 (higher ERP version)?
    My answer is BIG-NO, since version and objects are differenent, all transport will fail.
    I want to hear what you Experts say about this?
    Thanks in Advance
    Kumar
    Can you
    Edited by: Kumar Subramaniam on Jun 5, 2009 7:25 AM

    Hi,
    As per your query it can be moved but you will face some issue in this, there are two type of trandport 1. workbench 2. customizing. If you want to move customizing then your abaper will check this will be transport, but workbench will have some issue due to variotion of verion. But you transport this in your new dev server and do the configuration again in new dev serve then test in your qac. The job is very tipical but its posible.
    Anil

  • Creation of an ERP Sales Order or ERP Quotation from CRM Opportunity

    Hello Experts,
    The scenario is as follows:
    I have done the cross-system copy control of transaction types and item categories to enable ERP Quotation and ERP Sales Order creation from CRM Opportunity.  However, after saving the CRM Opportunity, when I click on the follow-up transaction and select ERP Quotation or ERP Sales Order from the list, the screen doesnt change and instead I got the following error:
    "Diagnosis
    An exception occurred during request processing. This was handled centrally. It changed the program flow and the result of the request probably contains errors.
    Procedure
    Contact your system administrator.
    Procedure for System Administration
    Activate checkpoint group BSP_WD_EXCEPTION_DISPLAY. To do this, use transaction SAAB. If the error recurs, further details are displayed.
    Exception Details
    CX_BSP_WD_INCORRECT_IMPLEMENT - Define component usage 'CUERPFollowUp'
    Method: CL_BSP_WD_REPOSITORY=>GET_CMP_USAGE_DEF
    Source Text Row: 20"
    Experts, kindly help me understand what the error is about and pointers to resolve it.
    Points would be awarded.
    Thanks,
    VSK.
    Edited by: venkatskumar on Feb 21, 2011 8:37 PM

    Hello Robert,
    Thanks for the quick reply.
    I have followed your instructions and I wanted to confirm one more thing with you.
    When I enter the component usage it gave a pop-up which said:
    "Enter either a reference or an interface view"
    Any information on what should be entered in the reference or the interface view? What should be the used component name and interface view name in this scenario?
    Kindly confirm.
    Points awarded
    VSK.
    Edited by: venkatskumar on Feb 22, 2011 12:37 PM

  • How to attach ERP smartform to a ERP Quotation generated from CRM 7.0

    Hi,
    I have this requirement of calling the ERP smartforms in CRM 7.0 where ever applicable.
    I don't want to use Transaction Launcher and also creating the same smartform in CRM would be double work.
    1. Can we attach a smartform of ERP to LEAD/OPPORTUNITY when we click on the MORE button on toolbar and choose PREVIEW OUTPUT/ TRIGGER OUTPUT. I think in ACTION we can just assign a smartform which is created in CRM system.
    Actually this is my client requirement and since my first CRM implementation do't know whether this is a valid point and how to go on.
    2. Also on ERP Quotation view page (toolbar) there is no button called MORE to PREVIEW OUTPUT. Can we assign a smartform to ERP Quotation?
    If any body can direct me on this issue would be of great help and full points will be given.
    Thanks,
    Jaya

    Hi,
    as far as I know there is no standard way of doing this in CRM 7.0.
    I imaging it would be possible to call an ERP smartform from CRM by :
    - writing an RFC capable function module in ERP that wraps the call of the smartform and returns the generated PDF data.
    - writing a function or method in CRM that calls the ERP function module and displays the returned data.
    In the lead and opportunity the print preview is done by having a print relevant action in the action profile assigned to the transaction type and I guess for these it should be possible to call a function module by creating an own smart forms method.
    But I think this is not possible for an ERP quotation, so you would have to create an own button. In the event handler for this button, one could call the ERP function module and display the result.
    Paul

  • ERP PR -- SRM SC -- ERP PO ?

    Hi Gurus,
    Is this possible:
    Transfer ERP PR to SRM as shopping cart (no sourcing required) and get approved based on the workflow definition, then create PO in ERP system?
    Best regards,
    jack

    Hi Masa,
    Yes, that's what we expected.
    Best regards,
    jack

  • SMD Post upgrade activities after EHP1

    Hi,
    We have recently upgraded our solution manager from SP15 to SP20(EHP1). We have upgraded our kernel to 7.01
    I found that in the directory /usr/sap/SMD/exe, the kernel files are still in version 700.
    So what is the exaxt post processing steps related to SMD and wily introscope in Solman and satellite system after EHP 1 upgrade
    PS: We are upgrading our satellite systems ie ECC 6.0 to ECC 6.0 EHP4 and Netweaver 2007 systems to  Netweaver 2007 EHP1.
    Best Regards,
    Sriram.S

    Any updates...
    Sriram.S

  • RV082 upgrade backup firmware - advanced

    Good morning to everyone, I have a question for the RV082 (Primary firmware ver 2.0.0.19-tm - backup firmware ver 1.3.98-tm) and i would like to ask whether could i upgrade the backup firmware without restarting to it.In other words, how can i upgrade the backup firmware when the primary firmware is active? Thank you in advance.......

    Update... I found the original firmware under the updated firmware on Linksys' website.  Downloaded the new firmware even though I'm running Win 2K. I'll post my other problem in another post.

  • ES Bundle upgrade for Utilities - Advanced Metering Infrastructure

    Hi Expert,
    One of my utility client upgrading the ECC system from IS-UT 605 to IS-UT 607.
    In SAP PI, the ES bundle for AMI that we are using comes under software component IS-UT 605 and software component version IS-UT 605.
    I need your expert advice on few queries I have as a part of upgrade:
    1. Whether it is necessary to upgrade the ES Bundle as well from IS-UT 605 to IS-UT 607?
    2. If so, whether old services will get affected?
    3. What all new services get added?
    If you have any documentation or any link related to ES Bundle upgrade in SAP ECC and SAP PI, please provide me the details.
    Your help is highly appreciated.
    Thanks,
    Vicky

    Andrew Hodgson ,
                                   Those are not available . Only the definitions are available as of now.
    Thanks,
    Greetson

  • Upgrading ISA 4.0 to "SAP E-Commerce for mySAP ERP"

    We currently have a Internet Sales (R/3 edition) environment connected to a R/3 4.6C backend. We are upgrading the backend to mySAP ERP 2005. This has necessitated an upgrade of the Internet Sales environmet, too.
    Has anyone does this or had any experience with the ISA side of this upgrade?
    Currently the ISA 4.0 environment is running on a NW2004 SR1 framework with a SAP Web AS JAVA 6.40 (J2EE 6.40, too).
    I know after this upgrade is completed, my environment will change to the following...(I think)
    Internet Sales (R/3 Edition) will become "SAP E-Commerce for mySAP ERP"
    NW2004 will become NW2004s SR1
    J2EE 6.40 will become J2EE 7.00
    I guess I'm looking for anyone who has been through this type of upgrade and how best to tackle it (aside from looking at the upgrade guides).
    What to watch for? What to double-check? Anything noteworthy would be of value to me.
    Should I even bother running through the upgrade process or should I just flatten the environment and start over with installation media?? Is that path easier and less of a pain?
    I'm open for any feedback or thoughts.....
    Thank you,
    Bryan

    Find this one
    http://help.sap.com/bp_bblibrary/600/HTML/C20_EN_DE.htm

  • Is EHP4 on ERP 6 EHP2  an Install or Upgrade??

    Hello Sandeep,
    #2 means Upgrade from a lower release to ERP 6.0 with EHP4 included.
    for example version upgrade from ERP 5.0 to ERP 6.0 including EHP4.
    3 means Installation of EHP4 when you are on ERP 6.0 already.
    for example ERP 6.0 SPS16 to EHP4 or ERP 6.0 EHP1 to EHP4 etc.
    I Hope it makes clear now.
    Best Regards
    Niraj

    Hello!
    Old thread, but same question. The EHPI-Guide says at the end of the postinstallation tasks:
    6.13Updating Dialog Instances
    After the enhancement package installation on the central instance,
    you need to update the dialog instance accordingly. To do this, you
    install the new dialog instance on top of the old dialog instance using
    the SAPinst tool.
    NOTE
    The following applies to high-availability systems only: After the enhancement
    package installation, you additionally need to update your Enqueue Replication
    Server (ERS) instance to the enhancement package level. To do this,...
    Our environment is Windows x64. We have 2 HA-Systems and one of them has also 5 Dialog Instances. Do we really need to update the Dialog Instances? Which would mean to uninstall the old ones and do a new installation, because an Update doesn't work, it always that there is already an DI on the host. They are all copying  the kernel from 
    server\usr\sap\<sid>\sys\exe\nuc\amd64 and the EHPI installed there the right kernel (7.01). So when we start the DIs, they will get the right kernel.
    Regarding to the Guide, we would also have to update the ERS. But they are also getting the kernel from 
    server\usr\sap\<sid>\sys\exe\nuc\amd64 and as they were started after the Downtime, they took the new kernel and are running well. We followed the note 1050343 in the ehpi-phase MODPROF_TRANS and installed the MS-DLLs with vcredist.msi and the MMC.msi. We think that doing this (installing both MSIs) and the kernelupdate on the DIs should be sufficient.
    Cheers,
    Kai
    Edited by: Kai Gebhardt on Oct 15, 2011 8:30 PM

Maybe you are looking for