Migrating BADI defn  during Upgrade to ECC 6

Hi All,
         During Upgrade from 4.6C to ECC 6 , we are encountering a BADI Definition in SPAU list.Please let me know the procedure to handle this. Is it the same way as we migrate Classic BADI to ECC 6.0 New BAdI->Enhancement Implementation?
Thanks
Vasuki

Can you specify which BADI is giving you a problem.
Regards,
Suhas

Similar Messages

  • Migrating BADI from 4.7 to ECC 6.0

    Dear Gurus,
    We r migrating from SAP 4.7 to ECC 6.0
    We have one BADI - ME_PROCESS_PO_CUST where we have made changes according to the requirement
    After upgrading to ECC 6.0. This BADI is not working even though it is in active mode.
    Any specific procedure for BADIs during upgrade
    Please let me know how to make it work ?
    Rgds,
    Saurabh

    hi Saurabh,
    did you got solution
    pls let me know that, we have same problem...
    thanks in advance.

  • Migrated BADI Implementation not triggering in ECC 6.0

    Hi Experts,
    Need your urgent assistance how to deal with migrated BADI implementation which is not triggering in ECC 6.0. This is for PO (ME_PROCESS_PO_CUST). In the original version (4.6) it was working fine. But when this is migrated to ECC 6.0, it's not firing. Please help to trigger this one in ECC 6.0.
    Points will be awarded and thanks in advance,
    LM

    Hi LM,
    Can you just paste the code in the BADI.(The method in which code is there)
    Is this BADI implemented and in the Active status.
    Check in SE19 if the implementation exist or not?
    There may be chances that some condition is not met which can trigger this BADI. Have you read the documentation of the BADI?
    Regards,
    Atish

  • Impacts on MRS and MAM during upgradation from ECC 5.0 to 6.0

    Hi Gurus,
    I would like to know the impacts on MRS and MAM during the upgradation from ECC 5.0 to 6.0. The version of MRS we are using is MRSS 500, and the version of MAM is 3.0. please let me know your valuable comments.
    Thanks in advance.
    Regards
    Satish

    HELLO,
    Search the form you will get few links.
    Also many companies have gone technical upgradation , but not functional upgradation.
    Thanks
    RK

  • Integration Repository during upgrade to ECC

    Hi all,
    Do you know of sap documentation regarding the SLD configuration and especially the "Integration Repository", When upgrading SAP system to ECC.
    Thanks,
    Naama

    Upgrading to ECC system wont affect XI much, So I don't think you have to do anything in Integration Repository.
    In SLD configuration you have to reconfigure Business System if the host name changes during upgrade.
    And accordingly you have to change host name/ip address, user and password in RFC maintained in XI system which will point to ECC system.
    In Integration Directory you have to change the business System name for ECC.
    Regards,
    Sarvesh

  • Error during Upgrade of ECC 6.0 to EHP5

    Hi,
    I'm upgrading our ECC 6.0 system to EHP5 (on SLES 11) using SAPup.
    The system check is blaming the os version (please see italic text):
    Result of system check:
    Window "SDTExecution Intervervention required":
    Determined system information:
    Type of operating system: Linux X86_64
    Version of operating system: 2.11.1
    Type of database: SAPDB
    Version of database: 7.7.07.034
    ERROR: OS version 2.11.1 out of range (too low) Upgrade the operating system at least to version 2.3. before you continue.
    WARNING: OS version 2.11.1 out of range (too high) If this version is released for the downward compatible kernel you are using, please ignore this warning. If not, ask SAP for an individual release of your configuration. Do not continue before SAP supports your configuration.
    So the ERROR message is wrong, the WARNING is correct. It seems the upgrade tool is expecting a version between 2.3 and 2.9. How can I handle this "wrong" error message?
    Best regards,
    Christian
    Edited by: Christian Janson on Jul 11, 2011 8:24 AM

    Hello,
    under the link:
    [http://service.sap.com/instguides]
    in the left tree select:
    --> SAP Business Suite Applications
    --> SAP ERP
    --> SAP ERP 6.0
    --> SAP enhancement packages for SAP ERP 6.0
    --> SAP enhancement package 5 for SAP ERP 6.0
    i found the following text:
    SAP Enhancement Package Installation on top of SAP ERP 6.0
    The standard tool to install SAP ERP Enhancement Package 5 on top of SAP ERP 6.0 is the SAP Enhancement Package Installer.
    Download the latest versions of the SAP enhancement package installer (SAPehpi) guide and the SAP enhancement package installer tool.
    But in the download directory the tool SAPup is mentioned.
    So I'm not sure, which tool to use. Sorry.
    Regards, Michael

  • Problem with JOB_RSINDCHK during upgrade to ECC 6.0

    Hi,
    We upgrade from 4.6b to ECC 6.0 SR1.
    During phase JOB_RSINDCHK the upgrade fails.
    The file RSINDCHK.ELG says:
    INDEX PRE-CREATION CHECK Errors and RETURN CODE in RSINDCHK.DE2
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    2EETG011 "Distribution ended with return code:4"
    In the file RSINDCHK_DSxxxx.SID says:
    3WEDA451 Inactive nametab contains no fields for table "M_VMVA"
    4 EDA507 -> "M_VMVA"            - - - "hostname_10"  "08:20:44"  "2007-03-01" - - - - - - - - - - - - - - - - - - - -
    4 EDA471    Result   "M_VMVA":    Action: "ACT"      Mode flag: " "    Return code: "0"
    Can someone give me a hint about how to solve the problem??
    Regards
    Magnus Jansson

    Dear,
    it looks that an inative nametab is available with no fields.
    Could you please check how it is defined in se11 ?
    you may perform the checks there as a first step for analysing this issue.
    best regards,
    Lucio Rodrigues
    SAP Activel Global Support

  • Using UCCHECK during upgrade to ECC 6.0.

    We are upgrading from 4.6B to ECC 6.0.   I am running UCCHECK to flag unicode errors.  We are in the process of correcting these.   We are assuming the warning can be ignored and are not mandatory to address.     Is his a valid assumption.
    thx,, J

    Hi Markus,
    Thanks for your interest.
    The main problem I have is (I think) because this is an upgrade and all phase logs are under /usr/sap/put/log. Each phase has its own log file name that is known because the Upgrade Server web page has a phase list where it specifies those names so the problem should be explained there.
    The only error I found in the logs for this phase is:
    2 ETQ092 Package queue calculation failed, rc = "4", reason = "Calculate the queue part for EA-FINSERV rel.600 with target SP SAPKGPFD12 (level"
    no other logs at that date and time mentions anything about support packages.
    I looked at the logs under source release 4.6C but there is nothing on that date so I guess that it is doing all process with the upgrade executables.
    What we did was to keep going using stack 11 that worked just fine as before but this problem is a black box in this process. Same happened before in a test upgrade and now we don´t get any clue either (in the logs).
    Prepare only said that there was a calculation problem and that was it, no help, no clue, so we are blind here.
    I don´t really want to create an OSS because in this enterprise the support service is Max Attention but notes takes the same time as in any other company with SAP licenses. About 3 weeks ago we had a problem and created an OSS note as High and we only got answers (and what kind of answers) every 24 hours and the problem was solved (4 days later) here doing all kind of tricks known by abap developers.
    We are going to install stack 12 as a post upgrade process that is not exactly the best for us but we are in a tight schedule and are already upgrading Quality system only have one more chance to do upgrade tests in a production test system.

  • How to deal with BDLS during 4.6C -- ECC 6.0 upgrade?

    Hi,
    I am currently performing an upgrade from 4.6C to ECC 6.0 and before which, I am also performing a data migration from x86 (Intel) servers to x64 (AMD) servers. So, we have three fresh AMD servers (DEV, QAS, PRD). While the current landscape (x86) is live, I migrated the data from PRD (x86) to DEV (x64) and performing the upgrade. I used the same data to perform upgrade on QAS (x64) also.
    Now, performing the data migration and upgrade on the PRD (x64) would involve more downtime. So, in order to avoid that, have decided to split the whole process over two consecutive weekends. The plan is as follows:
    Weekend 1:
    Bring down the PRD (x86), do a complete backup and restore the same on PRD (x64), then perform the data migration activities on PRD (x64). Once this is done, we want to go live with the PRD (x64) running R/3 4.6C on MS SQL 2005 and Windows 2003, for one week (5 days - Monday through Friday).
    And during these five days, I would perform the PREPARE phase.
    Weekend 2:
    I will start the upgrade on PRD (x64) on this weekend so that, we will get sufficient time to test and do post upgrade activities and decide to go live or not.
    I hope the above procedure would work. What do you guys say?
    Anyways, my question is, normally with the DEV and QAS, I perform the migration, PREPARE, upgrade and finally do the BDLS to convert the logical system to point to the new SID. But, with PRD, I cannot do so because, the system will go live with the new SID for one week. So, I may want to perform the BDLS on R/3 4.6C running on PRD (x64) and then perform the upgrade the following weekend. My question is, is it ok to do so?
    NOTE: The SID in the x86 and x64 are not the same. I have mentioned above the same SID just for ease of reading and typing.
    Thank you.

    Hi Markus,
    Sorry, it took a while to respond to your reply to my question. Yes, I understand that we don't have to convert the logical system. But, in our case, we use the production system database copy to upgrade the new development  box. So, we have to convert the logical system in the newly upgraded Development system from the one that currently belongs to the 32 bit production system to a new logical system that is unique to the landscape. We cannot even use the logical system name that belongs to the 32 bit Development System because, that box is currently being used until we go live with the 64 bit production box. So, we will have to create a new logical system. In this case, as we want to maintain consistency in the logical system naming format across the new 64 bit landscape, we are probably forced to convert the logical system name on the 64 bit production box also.
    So, now can you please advise, is it wise to convert to the new logical system after migrating the production server from 32 bit to 64 bit but, before the upgrade to ECC 6.0? As I had mentioned in my previous question, we will be live with the 4.6C on the 64 bit box for one week after migration to 64 bit but, before upgrade. In this case, I will have to connect to APO 64 bit and BI 7.0 64 bit (RFC) for one week before upgrade which, would need the logical system.
    Or do you feel, we still can use the old logical system for the one week and after completing the upgrade, we can do the logical system conversion on the PRD to maintain naming consistency across the landscape?
    Thank you.

  • Error during Upgrade from 4.6c to ECC 6.0

    Hi All,
      We are facing an error when upgrading from 4.6c to ECC 6.0. We are facing this error on the table COEP - runtime object inconsistancy. What we found is there is ERP upgrade has created new extra fields in the table. In log file the error is specified as : Duplicate Field name, But we not able to find the duplicate field name in the table.  Please kindly help as early as possible. The upgrade process is stuck.
    Regards
    Anil Kumar K

    Hi Anil,
    Is this issue fixed? Can i know how you fixed it?
    replied to your message Re: How to adopt the index changes during upgrade.
    Thanks,
    Somar

  • BW Related Jobs in ECC during upgrade

    Hi,
    we are upgrading from ECC 5 to ECC6.
    During upgrade, how should we handle the BW related jobs in ECC.
    How do we get the list of BW related jobs that are running in ECC
    How are these Jobs created in ECC ?
    Thanks
    Rekha

    Hi Rekha,
    You can check the job in SM37. check with options scheduled and released checked.
    Usually we will find jobs related to V3 scheduled in LBWE in SM37.
    take immediate run for that job and cancel it.
    now run your delta IP's to load the records from delta queue to BI system.
    Regards,
    Venkatesh

  • ERROR MESSAGE IN PPOME TCODE AFTER UPGRADE TO ECC 6.0

    Hi Experts,
    I have a question.
    Recently our system went for upgrade and during testing phase we have found one issue.
    Error message is appearing in PPOME transactio code after upgrade to ECC 6.0
    The screen is getting defaulted to Budget section and unable to find the subtype as there are no subtypes available there and showing error message as "Fill in all required fields".
    Please let me know your solution on this.
    Regards,
    Sekhar.

    Hi,
    - you can deactivate the budget tab in the IMG-activity 'Hide/Show Tab Page'
    (SIMG_CFMENUOHP1HFW20 alternatively use SM30 on view 'T77OCTABUS')
    1. Create new entries for the following KEY:
    a) Scenario OME0
    b) Object type 'P', 'O', 'S'
    c) Tab Page 'PBC_ORIG'
    2. for each of this entries, set the 'Exclude Tab Page'-Flag.
    - in case you do not want to deactivate the Budget tab:
    The error occurs due to missing entries for subtypes in table T778U
    for infotype 1516.
    Please maintain the according subtyes you want to use if you create a
    budget.
    Regards,
    Ana

  • Smart form Addon after Upgrade to ECC 6 EHP4

    Hi,
    I have succesfully upgraded my system from R/3 4.7 EXT 1 to ECC 6 EHP4.
    During upgrade i had to delete Pre configured smart forms Addon ( According to note 572392 ) .
    Since we are on EHP4 and no smart forms configured we are not able to print.
    The latest pre configured smart form addon ( Best Practice all in one)  available is for EHP3.
    Please let me how to proceed with this situation as there may be other compaines who are on EHP4 and use pre configured smart forms.
    Appreciate your help.
    Thanks,
    FBK

    If you have old system copy try to copy forms into the new.
    Kind regards,
    Mirek

  • Error in transaction KEA0 during upgrade

    Dear All,
    During upgrading the custmer system from 4.7 to ECC 6.0 we found some error in the transaction KEA0 while trying to activate the cross client for an operating concern.
    The activation logs says that there are the syntax errors in the gereted subroutine pool: RK2O0100.
    I however corrected the error and activated the code but again when I am trying to execute the same it gave me the same error and when I go to the sub routine pool I found that the changes are again undone and the previos version is activated. This happens repeatedly that the code is corrected and activated by me and says no error and ones I log off and login again it says the same error.
    Help will be appriciated.
    Thanks iin advance....
    Abhi...

    Dear Raymond,
    Thankds for your help..........
    I tring to run RKEAGENV it shows the error message with STOP button saying that the field WTGBTR not contained in the nametab for table CE1E_B1 and when Io run RKEAGENF it gives a short dump saying that entry for CE10100 is not allowed for TTABS.....
    Please help.

  • How to track changes made to the standard objects by SAP during upgrade ?

    Hi All,
    Can any one of you please let me know if there is any straight forward method to find any change made to the standard objects by SAP in different versions ?
    Like for eg, during upgrade from 4.6c to ECC 6.0.
    Thanks in advance.

    > For eg , if SAP has made any change in the standard  transaction IE02,  in ECC 6.0 how will we come to know those changes?
    There are two sources for that:
    The "Solution Browser" (http://solutionbrowser.erp.sap.fmpmedia.com/) which lists the differences between source and destination release and the release notes (http://service.sap.com/releasenotes). You'd need to read here all those from 4.6 to ERP 6.0 (so 4.7, ECC 5.0 and ERP 6.0) to find out the behaviour changes.
    Markus

Maybe you are looking for