ABAP Code Changes During Upgrade from 4.7C to ECC6

Hi all,
I'm in process of collecting information for our next upgrade.
We are on 4.7C and are planning to upgrade to ECC6. We wanted to know what changes shall be required on ABAP side during this upgrade. e.g. certain ABAP commands which are obselete, few tables , few fucntional modules being obselete.
Any specific functional areas/transcation codes being obselete which in turn would make Uer Exit redudant etc.....
Could somebody please help me out with some info regarding this upgrade? Some links or any hint you can give would help me a lot. (Whether technical or functional..all very welcome!).
Thanks in advance
Moderator message: topic too broad to be answered in a forum thread, many people had to go through this, please search for available information/documentation.
Edited by: Thomas Zloch on Jun 14, 2011 9:31 AM

Hi ,
I too got an error of this type .
The resolution is as follows :
login as user SAP<SID> in the oracle database .
SQL> drop tabel <tablename>;
Restart the upgrade from PARMVNT_SHD phase.
Regards
Ratnajit

Similar Messages

  • Report writer issue during upgrade from 4.6 to ecc6

    Hi all,
    On generating report of report writer through GR5G (we are regenerating because we were getting dump for this report after up gradation from 4.6c to ecc6)we found one syntax error. The error is in auto generated program we can see that error but cant fix it as it needs a key and maybe that might not also be the right method to resolve is as auto generated codes should not be touched . So what would I like to ask  is how can error come in auto generated program and how do I fix it (error is in data declaration QUOTDATE_MAX(08)                       TYPE C VALUE '). Here u can see that instead of ‘’ only ‘ is used there is no closing inverted comma.

    Hi,
    You  need to make sure that all your delta queues are empty before the upgrade.
    In case of logistics make sure all v3 jobs are stopped and extract queues are empty.
    After the upgrade make sure that the source systems are mapped and working correctly. Check that your delta queues are conneted to the correct BW system.
    You need to test all your extractors as they might have changed (check release notes). Test delta loads to make sure they are working properly.
    Cheers,
    Kedar

  • Report Layout Changed After Upgrade from 4.6C to ECC6

    Dear Gurus,
    I do functional test of every process in ECC6 after upgrade from 4.6C. I found all report layout changed without variant (it's happen to all Query/SQ01 reports ). So I've to assign manually the fields for the reports, and create a default variant then.
    Why it happen ? Is there configuration or setting missed or this is standard while we do upgrade ?
    Thx in advance.
    Tri Wicaksono

    We do re arrange for all ALV report ...

  • Can we activate Classic General Ledger in ECC6.0 during upgrade from 4.6C

    Dear SAP Gurus,
    Greetings
    My Client's technical team had upgraded their system from 4.6C to ECC6.0 and they had activated classic GL instead of New GL. And they had also activated classic withholding tax in place of Extended Withholding tax.
    They are facing some error during posting of transactions (like generation of excise invoices, posting of WHT transactions, etc.) I told that it can be a reason of not activating New GL.
    Is my understanding correct...?? Can we activate classic GL during upgrade from 4.6C to ECC6.0...??
    In case of a new client built (with ECC6.0), can we activate the classic GL instead of the New GL..??
    Does the system will work correctly in the long run if they had activated classic GL and classic WHT...??
    Please clarify. Thanks in advance for your time and efforts
    Regards,
    Chaps
    P.S. Points will be awarded for answers !!

    Hi,
    I think that you should read long text of OSS note 999614 carfully and you are
    aware of the fact that you will have additional migration efforts in
    case you need to migrate to new G/L later on.
    In case you are convinced that  this is the best way please feel free
    to deactivate new G/L as described in note 999614.
    Please make sure that you deactivate new G/L in all clients of your
    new system in case there were already client copies done.
    Yes this is possible and I would not automatically assume that
    error during posting of transactions are due to New GL not being activated.
    Note 756146 documents the issue and possible repercussions
    of using Classic GL.
    In the case of a new installation the new G/L accounting
    is active by default in ERP. In principle, the use
    of the classic GL is also possible for new customers, however,
    SAP does not recommend it since this requires an additional
    migration expense in later years.
    Regards,
    Aidan

  • 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

  • ABAP Query in Upgradation from 4.7 to ECC6.0

    Hi there,
    We are upgrading SAP system from 4.7 to ECC6.0. We have s/w component SAP_BASIS = 700.
    It would be of great help if anybody share their thought on handling ABAP queries after upgradation from 4.7 to ECC6.0.
    We have refered SAP notes 132813 and 672784 where in we need to change the default query area.
    Also, do we need to re-genarate the queries? If yes then how can we achive the same.
    Thanks in advance.

    Hi,
    It may happen that some times, the queries are not generated after the upgrade.
    Hence call the FM: RSAQ_GENERATE_PROGRAM
    Pass the Query name and user group.
    For all global queries: refer table AQGQCAT and local/client specific queries: Refer to AQLQCAT.
    This can help to regenerate the queries.
    You can also write a small program to generate using the above FM(one time program) that runs after upgrade
    Hope this helps
    Regards
    Shiva

  • Functional upgrade from 4.6C to ECC6, changes in Controlling

    Hi
    We will be doing a functional upgrade from 4.6C to ECC6. I need to know what are the changes in Controlling on ECC6, with specific reference to the Aerospace and Defence Industry Solution. We have completed the technical upgrade.
    Thanks
    Henry Bekker
    [email protected]

    Hi
    We will be doing a functional upgrade from 4.6C to ECC6. I need to know what are the changes in Controlling on ECC6, with specific reference to the Aerospace and Defence Industry Solution. We have completed the technical upgrade.
    Thanks
    Henry Bekker
    [email protected]

  • How to adopt the index changes during upgrade

    Hi All,
    Please let me know how to adopt the standard index changes during upgrade. We are not able to change using SPDD.
    Regards
    Anil Kumar K

    Hi Micheal,
           I have posted one query can you answer for that also.
    Actually we are facing a problem  in activating the table COEP. It is saying duplicate field name exist for GEBER. But we have checked all the tables and structures.But no duplicates.
    Please help us..
    Regards
    Anil Kumar K

  • Changes in PM Module while Upgrading from 4.6C to ECC6

    Hiii
    Can any body tell me where can i get the detailed infromation about Techincal upgradation from 4.6C to ECC6 & Technical as well as functional chnages Changes due to the upgrade??
    Thanks in advance.
    Makarand Gurjar

    Dear All
    We are closing the issue. Thanks for your all replies.

  • Abap issues when upgrading from 4.7 to ecc6.0

    hello All,
    I am posting this question with intention of general issues we face that are abap related when upgrade from 4.7 to ECC6.0,
    do the programs ahve to be adjusted, if sumone cud also throw some light on what is unicode and wat role does it play in the upgrade,
    some specific examples wud be appreciated
    thanks,
    RS

    hi,
    Go through this
    Unicode is an international standard that assigns characters from virtually every
    language and script a unique Unicode Scalar Value, which is a number written in
    hexadecimal notation.
         Character     Unicode Scalar Value     Unicode Character Name
         A      U+0041          LATIN CAPITAL LETTER A
         Ä     U+00C4          LATIN CAPITAL LETTER A WITH DIAERESIS
         α     U+03B1          GREEK SMALL LATTER ALPHA
    Implementing the Unicode standard enables a single software product or a single
    web site to be accessed across multiple platforms, languages, and countries without
    the need for re-engineering. It allows data to be transferred across many different
    SAP and non-SAP systems without corruption. To meet these requirements, the SAP
    Unicode team continues to promote Unicode-enabled SAP systems, aid their
    installation, and provide tools and full technical support for the smooth
    conversion of existing SAP non-Unicode systems to Unicode.

  • Upgrade from 4.7C to ECC6.0 fields missing in t code FBL5N

    Few fields are missing while upgrading from 4.7C to ecc6.0 in SAP STD Transaction FBL5N.  Will pl clarify me.

    Hi,
    Can you clear whether you are in the process of upgrading to ECC6 or you have already completed the Upgrade to ECC6 ?
    Regards
    Suhas

  • 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

  • Upgrade from 4.6C to ECC6.0 - development quality and production

    Upgrade from 4.6C to ECC6.0
    I have got three systems right now...
    Development(D1)     Quality(Q1)    Production(P1).
    These three systems need to be upgraded to ECC6.0
    The recommended process is to copy D1 to a new temporary server(D2) and
    then upgrade it. At the time of the copy we will have to run the transactions
    SPDD and SPAU for which the one one transport requests will be created.
    Now after the complete upgradation we will be running the UCCCHECK and SCUV.
    The problem is after running this process we are going to copy the Quality(Q1)
    to a new quality system Q2. Now the code in the D2 system is unicode complaint with all the
    same functionalities as in D1.
    How to get all the change and customizing objects which is updated in the D2 system
    to the Q2 system (only the relevant ones - this will also ensure for PRD as the same process could be followed)?
    Or else do we have to repeat the process for both the new quality(Q2) and new production(P2)
    systems?
    Useful answers will be rewarded accordingly....

    Hi,
    If you do SPDD and SPAU changes to create unique transports (as per upgrade guide) so the Q2 upgrade will have it embeded during the upgrade process then you should not have any problem because after the D2 combined upgrade (unicode and Technical Upgrade) the system will be in Unicode, UCCHECK is to check unicode compatibility as long as I know. You won´t need to use SPDD and SPAU again in Q2.
    Also you could do Upgrade to D2, run UCCHECK and SCOV and then create all changes to objects that needs to be changed to create requests. Then do Q2 upgrade and when is finished then you move every transport you need from D2 to Q2 to do the necesary tests, it should not take much time. In the upgrades I know and done this is the way the changes were moved up to PRD, we have never used the unique transport request mentioned in the Guide. During Quality tests developers and funtional consultants will need to keep doing changes until everything is OK so even if you create unique requests, you will also have to transport after PRD upgrade.
    Either way you won't need to run SPDD and SPAU after D2 upgrade.
    Good luck
    Edited by: AC on Nov 18, 2008 1:26 PM

  • BAdi & user-exits while upgrade from 4.6c to ECC6

    Hello all,
    Can anybody put light on how User-exits and BAdi will be effected while upgrade from lower version to ECC6.
    Many Thnanks.....
    Apps.

    Hi,
    The main concept of enhancements is to keep the code unaffected during version upgrades
    Hence all the BADI implementations and User Exit/Customer exits implementations will be in place and no effect due to upgrade...I hope in case of badi, some new BADI(as part of enhancement framework-GET BADI/CALL BADI) will be added up and the old BADI(Those in 4.6c or below) will not get affected.
    Regards
    Shiva

  • Invoice Receipt Warning Message Appear After Upgrade from 4.6C to ECC6

    Hi Gurus,
    We do upgrade from 4.6C to ECC6. And we do Invoice Verification base on Delivery (Vendor delivery number), in our business process there more than one Purchase Order has same Vendor Delivery Number while GR executed. But only one Purchase order related to Invoice verification, others PO are Free PO (no need Invoice Verification).
    The problem is:
    In SAP 4.6C, while execute Invoice base on Delivery (Vendor delivery), system automatic select only PO with Delivery (vendor) which related/allow invoice receipt.
    In SAP ECC6, while execute Invoice base on Delivery (vendor delivery), all PO selected. So than there are warning messages appear (warning pop screen) for those PO not allow invoice Receipt (message M8035: PO item XXXXX does not allow invoice receipt), and at the end PO which allow Invoice receipt then appear for further Invoice Receipt process.
    At overall, the final result SAP 4.6C and SAP ECC6 is same (only PO which allowed Invoice Receipt will processed further).
    The Question are:
    1. Why in ECC6 appear warning message, while in 4.6C no warning message ? Is there config to ignoring the warning message. I've try to maintain system message for M8035 (t-code: OMRM) to ignoring the pop screen, but can not created.
    2. How do we make warning message dissapear (no need warning message), because if the PO's has hundred items so user need to click enter hundred times.
    Thanks in advance.
    Regards,
    Tri Wicaksono

    Hi,
    could you please check whether the flag "GR-based IV" is set in the purchase orders?
    If GR based-IV is ticked, then this pop-up cannot be suppressed.
    If you would like to post the invoice first then GR-based IV should not be checked, otherwise this pop-up will always appear.  I am afraid that this behaviour is standard. 
    Please, be aware that this feature is only available if you set  in the Purchase Order item the 'GR-based IV' indicator:
       If the GR-IV flag is not set in the PO, then the system does not                     
       differentiate individual goods receipts. Please see the <f1> help                    
       for the field "GR-IV" in the PO item detail. Since the individual                    
       receipts are not differentiated, an invoice is not tied per se to                    
       an individual receipt and a goods receipt can be reversed despite                    
       an invoice receipt.                                                                               
    With the GR-IV flag set on in a PO, you can specify which goods                      
       receipt is being invoiced in an IR and which goods receipt is being                  
       reversed in a return. It is this correlation between goods receipts                  
       and invoices that enables you to specify for GR-IV PO's whether an                   
       item can be returned despite an invoice. 
    Please refer to the note :457511 Question 10.          
    Best regards
    Erika

Maybe you are looking for