Tips / Lesson Learn: Upgrading from ECC 5.0 to ECC 6.0 w/ Unicode

Hi
We are looking into moving from ECC 5.0 to ECC 6.0 w/ EP7 and doing the unicode path on as well.
What are some lesson learn you guys could share in potential issue may occur in the HCM realm?
We don't currently have inhouse payroll, using PU12 to interface that information out.
If you could share some past experiences on what could occur during this upgarde caused by going to ECC 6 or even by the unicode patch would greatly be appreciated.
Thanks,

THe guru of ECM on SDN
nice to see you around. came across your tips and tricks regarding SAP HCM.and also for ECM.
you have dne a good job . i am new in this field but soon would have skills like you
Regards
Waqas Anwar

Similar Messages

  • BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0

    Background:
    I am relatively new to BW team and will be going through my 1st source system upgrade.
    We currently have BI 7.0 SPS 17 connected to source system R/3 Enterprise EP1.
    We are upgrading to the source system to ECC 6.0.
    In Development and QA Environments:
    we will have access to both old (R/3 Enterpirse) and the new (ECC 6.0) source systems.
    We have a opportunity to compare the BW Objects, data flow and data loading from
    both source systems.
    In Production, however, we will just upgrade over 3 days downtime.
    One Question that comes to mind in this regard...
    What sort of things, we should be checking for before and after upgrade in Dev/QA and in Prod environments and what tools are available that can help the analysis and validation process ?
    Some of the suggestions that were given to me include following points.
    Before Upgrade:
    1 Check data, taking pre images of it for testing with post upgrade.
    2. Perform proper analysis of Source system related BW objects.
      - A complete listing of actively used Datasources,.. etc.
    3. Make delta queues empty,
    Make sure that all existing deltas are loaded into BW.The last request delta must not deliver any data and must be green in the monitor.
    4. Stop Process chains from BI (remove from schedule) and collection runs from R/3 side
    After Upgrade:
    1 After the OLTP upgrade, refer to note 458305 and other notes that are relevant to the actual upgrade
    (depending on the R/3 system release / R/3 plug-in to BI plug-in compatibility).
    2. Check logical system connections. Transactions SMQS, RSMO and SM59, If no access, then we can use Program RSRFCPIN_NEW for RFC Test.
    3. Check and/or Activate control parameters for data transfer. SBIW ---> General Settings --->
    Maintain Control Parameters for Data Transfer
    http://help.sap.com/saphelp_nw70/helpdata/EN/51/85d6cf842825469a51b9a666442339/frameset.htm
    4. Check for Changes to extract structures in LBWE Customizing Cockpit 
        - OSS Notes 328181, 396647, 380078 and 762951
    5. Check if all the required transfer structures are active. See OSS Note 324520 for mass activation.
    7. Check if all Source system related BW Objects are active - Transfer rules, Communication rules, update rules,DTPs,..etc. 
    Below is a link for some useful programs in this regard.
    https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=35458
    6. Test all important datasources using RSA3 and check for OLTP Datasources changes .
    As soon as BW notices that the time stamp at the DataSource in the OLTP is newer than the one in the transfer structure, it requests replication of the DataSource and activation of the transfer structure. Transfer the relevant DataSources only if required, and transfer only the ones that have changed (RSA5 -> Delta).
    7. Create Data flow objects (trnasfer rules, infopackages, trnasformations, DTPs) for the Replicate
    new/changed datasources,if needed. 
    8. Check all CMOD enhancements.
    If we are using a customer exit with the extractor in the OLTP, see Note 393492.
    7. Check for unicode (all custom programs or Function Modules for DataSources)
    5.  Check all the queues in RSA7, start delta runs and test data consistency.
    For delta problems:In the BW system, start the 'RSSM_OLTP_INIT_DELTA_UPDATE' program for the DataSource and the source (OLTP) system for which the init selections are then transferred from BW into the ROOSPRMSC and ROOSPRMSF tables in the source system so that the delta can continue.
    9. Take back up of data posted during upgrade for contingency planing.
    10. Run the entire set of process chains once if possible and let it pick up no data or the usual master data.
    Since we have lot of experts in this forum, who have probably gone through such scenario many times, i wanted to request you to Please Please advise if i have stated anything incorrectly or if i am missing additional steps, OSS Notes, important details...

    Thanks Rav for your detailed post and very helpful contribution by posting all the information you had regarding the upgrade.
    We have similar scenario -
    We are upgrading our source system from 4.7 to ECC 6.0. We have our BI system with BI 7.0 at support pack 19 (SAPKW70019).
    Our strategy in ECC deployment  ->
    In development we copied our old DEV 4.7 system DXX to new ECC system DXY (new system ID).
    In production we are going to use same system PRXX upgraded from 4.7 to ECC.
    Now we are in testing phase of ECC with all interfaces like BI in Dev.
    My questions are below ->
    How can we change/transfer mapping of all our datasources in Dev BW system BID to new ECC dev system DXY (Eg. Logical system LOGDXY0040) from Old dev system DXX (Eg. Logical system LOGDXX0040). We donot want to create new datasources or change all transfer rules/Infosources for old BW3.x solutions on our BI.
    Also in new ECC sourcesystem copy  we see all datasources in Red in RSA7 transaction. Do we need to initialize again all the datasources from our BW BID system.
    Is there any easy way for above scenario ?
    Please let me know if you have any further helpful information during your ECC 6.0 upgrade connecting to BI 7.0 system.
    I have found some other links which have some pieces of information regarding the topic -
    Upgrade R/3 4.6C to ECC 6.0 already in BI 7.0
    http://sap.ittoolbox.com/groups/technical-functional/sap-bw/sap-r3-migration-and-sap-bw-version-1744205
    BI 7.0: Source System upgrade  from R/3 Enterprise to ECC 6.0
    Re: ECC 6.0 Upgrade
    Re: Impact of ECC 6.0 upgrade on BI/BW Environment.
    ECC 5.0 to ECC 6.0 upgrade
    Thanks
    Prasanth

  • Issues during technical upgrade from  version 4.6C to ECC 6.0

    Dear All,
    We have done a technical upgrade from version 4.6C to ECC 6.0 and encountered following issues -
    In the t-code ABZE (acquisition with in house production) there is a check-box for reversal posting on screen with version 4.6C. However, this field is missing in ECC 6.0. Why so?
    In the report s_alr_87012327, there is a field "only with creation block" in version 4.6C. However, this field is missing in ECC 6.0. Why so?
    Request to kindly suggest the alternative to carry out the same in ECC 6.0.
    Thanks in advance.
    Regards,
    Dhawal

    Hi Akshya,
    Please find answers below.
    1) 4.6c is NON-UNICODE system, Can I upgrade it into ECC 6.0 UNICODE system?
    Yes you can.
    If you are on a single code page system then you can give a gap between your uprade and unicode conversion. There is no problem with the singlecode upgrade and conversion.
    But if your system is MDMP then you will have to do the CUUC method that is both upgrade and unicode conversion together. Though you can give a gap and sign an disclaimer with SAP it is still not recomended way.
    2) 4.6c does not have any ITS system installed. If we upgrade it to ECC6.0 ABAP only, then Can I activate WAS internal ITS?
    Yes you can activate it.
    3) 4.6c does not have any JAVA stack. When I upgrade it to ECC 6.0, can I upgrade it to dual stack (ABAP+JAVA)? If yes, then how?
    After the upgrade and unicode conversion you can install the java stack.
    Regards,
    Ravi.

  • Upgrade from 4.6 B to ECC 6.0

    Hi Gurus,
    Well and I would like to inform to our gurus that currently we are in the Phase of upgrading form 4.6 B to ECC 6.0
    I this regarding, can any one of our Guru's guide me regarding the following doubts.
    1. How to do Upgrade from 4.6 B to ECC 6.0?
    2. If you have any documents in this regard?
    3. Do you have any documentation for ECC 6.0?
    I request you to kindly forward the information to mail id: [email protected]
    Thanks with regards,
    Bala

    Hi,
    Please visit the following links:
    http://service.sap.com/erp
    http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
    http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
    For Functionality Differences pls refer to the below site -
    http://solutionbrowser.erp.sap.fmpmedia.com/
    After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
    Select the Solution Area like Financials, Human Capital Management, Sales....
    Select module like MM, PP, SD, QM.....
    Click on Search
    Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
    and also check the release notes of ECC 6.0 in service.sap.com.
    Hope this helps you.
    Please assign points if it useful.
    Regards
    Ravinah Boni

  • Regarding Upgradation From 4.6 C To ECC 6.0-Urgent

    Hi all
    can anybody let me know what is procedure to upgrade the SAP From 4.6 C To ECC 6.0 from MM and CIN point of view
    --is Up gradation is just like an implementation or Enhancement process
    any help would be appreciable
    thanks in Advance
    Edited by: JAM SAP on Feb 27, 2008 8:47 AM

    Upgrading project mostly involves testing with the existing system with the new system.SAP already released the release notes for this Upgrading ECC 6.0.
    (1). YOu have to do unit test/Integration test/Regression test in your new system based on the business process documents prepared for your present system.
    (2). You mostly encounter Interface issues(If exist)/Authorization issues/Enhanced naming issues/Usage issues.
    (3). In 46C you have to do external configuration for CIN.However In ERP 2005, It is already in built.Hence Knowledge of CIN will be more than sufficient to manage the CIN issues.
    (4). More over you must be very confident in the business process.Unless you will receive many UAT issues.
    (5). I strongly advice you based on my experience, Whenever you do unit test and Integration test, use your user id to.When you do regression testing, get the user id from user copy all the roles from the user id and create new id.Using this new id you do the Regression testing.This will avoid many problems.
    (6). Another Imprtant big issue is patch work infomation.After release of 46C, SAP released many patches for 46C.However these patches are all not updated in to your present 46C system.These patches are already in in built in ECC 6.0, hence you will get diff.result when you do testing.If such a case, advice the user about the patch work, and proceed. In most of my cases , SAP enjoyed with 46C without patch scenario, but in ECC6.0 they started to complain, b'cas the new patches.
    (7).Give me your mail id ,I will send you the release notes.
    (8).Note down my forum discussion to know about the some of the issues.
    Hopefully it will be helpful, Let me know, If you need more Information.Thanks
    Reward If useful!

  • MB_DOCUMENT_BADI - SAP R/3 release upgrade from 4.7.1 to ECC 6

    Once finished upgrading from SAP R/3 4.7.1 to SAP ECC 6, from SPAU I see that there was no problem on the implementations of this BAdI. But when I tried the transaction, where this BAdi was implemented in, I realized that my implementations were not working. In addition, from SE19, I see that these implementations are active, so why they aren't working?
    I think that there are some problem in BAdI implementations when upgrading SAP release, but I don't know how to solve my problem and turn on my implementations.
    Thanks,
    Luca

    Hi Sunny,
    i continued with the option - without ADD ON.
    So, this mount point and ADD ON dvd issues are over.
    In the next screen, i have to specify the xml file and place the packages under EPS/in. I have done that accordingly and now i get a new error - No matching SAINT package for 'SAP_APPL' found.
    Any ideas where i have done wrong?
    Thanks,
    Mohan.

  • Tehnical upgrade from 4.6C MDMP to ECC 6.0 using CU &UC approach

    Hi SAP Experts,
    We are embarking on a project for Technical upgrade from SAP R/3 4.6C MDMP system to ECC 6.0 using the CU & UC approach for our Asian operations (comprising of India, Japan, Taiwan & Singapore).
    Please share with me the Best Practices you followed in your projects, checklists, DOs, DONTs, typical problems you encountered and the possible safeguards, any other useful information, etc.
    Since very little information is available from Organizations who have used this upgrade successfully, I am raising this in SDN to share your experiences during the Technical upgrade.
    All useful information will be surely awarded with suitable points.
    Looking for your invaluable inputs which will be a BIG help for our project.
    Best regards,
    R.Rajaraman

    Pls go thru the below mentioned notes and its related notes
    Note 928729 - Combined Upgrade & Unicode Conversion (CU&UC) FAQ
    Note 73606 - Supported Languages and Code Pages
    Note 79991 - Multi-Language and Unicode support of SAP applications
    Note 959698 - Twin Upgrade & Unicode Conversion FAQ

  • Lessons Learned Migrating from BOXI R1 to BOXI R2

    Post Author: tmiller
    CA Forum: Deployment
    Some notes from our upgrade from Release 1 to Release 2 to, hopefully, prevent headaches in other users:
    Make sure you have your Release 2 license keys, Release 1 keys won't work (check with your vendor if you are an OEM purchaser)
    Make sure you have notes on all your server configurations, including which Destinations are enabled (and their configurations) for the Job Server.  Screen shots are a big help here.
    If you are an OEM user, you have to install at least SP2 (which requires SP1 be installed first) or your licensing will be, uh, how to put it delicately, invalid
    During upgrade, add your license keys in the console BEFORE doing the datasource upgrade.
    If you are upgrading in-place, what worked best for us was to restore our pre-upgrade backup of the CMS database (we use SQL Server) to a new database and import from there to the bobjecms database.  You also need to have a different ODBC DSN setup for each of these databases.
    Once your datasource import is done, make sure you run the UPDATE OBJECTS process from the Central Configuration Manager, otherwise, you'll get an error if you use Windows AD authentication: Error retrieving info for Windows AD authentication: Unable to get SI_SSO_VENDOR property value.  (Windows AD authentication won't work, you'll get this error when trying to configure it through CMS).
    Enable servers that you noted in step 2
    You'll need to update Crystal Reports for your report developers to Release 2, also - especially if you use Windows AD authentication.  Do a COMPLETE UNINSTALL of Crystal Reports release 1, reboot, and then install a fresh Release 2.  If you don't uninstall R1, you will most likely have an annoying "Please wait while Windows configures Crystal Reports XI Release 2" window every time you load Crystal or any VB developed app or Visual Studio 2005.  This might be limited to only clients with VS 2005 installed, but might notu2026
    Those were the major (and minor) hurdles we had to clear to get this upgrade done correctly u2013 and this is also an excellent example of why we have a test and a production server.
    Hope this helps someone else out there.
    - Tom

    Post Author: TAZ
    CA Forum: Deployment
    Hi Tom,
    Great notes, I'd like to add a few details that many people don't know as well.
    1) Many times an upgrade from XIR1 to XIR2 will not be possible. This due to complexities in the DB structure that just don't migrate properly. In these cases there will be many errors during the CMS DB copy stage and the update objetcs stage. If this is the case then you must "migrate" via import wizard instead of "upgrading".
    2) I know you mentioned that you were working off a backup of the original XIR1 CMS DB, but I'd like to add in NO circumstances should this be attempted against a live CMS production DB. If it is most likely your production server will go down and the upgrade will fail. This is due to tables being locked while the CMS copy utiltiy is trying to migrate them.
    3) Regarding Crystal XIR1: You can still keep CRR1 but if you have AD or LDAP auth you will need to patch the client with the Server's SP3 or later.
    4) Also to note CRX1 should NEVER be installed on an existing XIR2 server. CRXIR2 is available for download for free via ESD and will use existing CRXI keycodes.
    Regards,
    Tim

  • IDOC extensions during Upgrade from Ver 4.6 to ECC 6.0

    We are working on an Upgrade project wherein we are going from Ver. 4.6 to ECC 6.0. Can you guide us what all we need to do with the IDOC extensions alerady implimented in ver 4.6 in order to confirm them good with ECC 6. Also to be noted, we are making the new system and all the customer developments Unicode compatible.
    Thank you!!

    Hi Satish,
    Now i am sending some URL for Functional upgrade
    May be those are all useful toyou
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/erp6/transactionsChangedinECC6.0
    http://solutionbrowser.erp.sap.fmpmedia.com/Default.aspx
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/erp6/
    Regards
    Surya

  • Upgrade from 4.6 c to Ecc 6.0

    Hi all,
    We have  R/3 on 4.6c with windows 2000 on 32 bit with Sqlserver 2000, we are planning to upgrade to Ecc6.0 and windows to windows 2003 with 64bit and sqlserver 2000 to sqlserver 2005
    Can you plz guide  me the  the process of doing  things like
    which one i have to do like 32bit to 64  bit or windows to 2003 then bit upgrade then DB .
    I have  done upgrade on 4.7 to Ecc 6.0 does 4.6c upgrade to Ecc 6.0  is the same process...
    Plz suggest...
    Thanks,
    Subhash.G

    Hi all,
    We have 4.6c and windows 2000 32 bit and sql server 2000 32 bit on 64 bit hardware.
    On the same if we want to upgrade windows 2003 to 64 bit then sql server 2005 64 bit and 4.6c to ECC 6.0  what is the approach.
      I have one approch please  guide if i am wrong.
    For OS Upgrade:
    There is no approach to upgrade 32 bit windows 2000 to 64 bit windows 2003, we have  Install the 2003 from scrath.
    For Sqlserver:
      We can use attach/detach methods, we have to  install sqlserver 2005 64 bit with correct collation Bin2  and attach the DB .
    For SAP upgrade:
      Install the 4.6c  or restore the file system , since we have the DB , replace the kernel with 4.6D 64 bit then do the upgrade.
    Please correct  the approach if it's wrong.
    Thanks,
    Subhash.G

  • Upgrade from 4.6C to ERP ECC 6.0

    Hi,
    Help!!! I'm running the prepare the first time and encountered this problem during the Kernel extract.  I received this message from '/usr/sap/put/EXTRKRN.LOG'
    1 ETQ201XEntering upgrade-phase "EXTRACTKRN_PRE" ("20061016131342")       
    2 ETQ367 Connect variables are set for standard instance access           
    4 ETQ399 System-nr = '', GwService = ''
    4 ETQ399 Environment variables:
    4 ETQ399   =<null>
    4 ETQ399   auth_shadow_upgrade=0
    1EETQ204 Upgrade phase "EXTRACTKRN_PRE" aborted with severe errors
    Ramon

    Hi Ramon,
    The major source of information should be the joblog of the job running APYSAP. During the upgrade this should be the joblog of the SAPup job.
    When trying to reproduce by hand make sure you have
    - SAPUP *LIB in your library list and an
    - empty target directory '/usr/sap/put/exe'.
    If you want you can frame your APYSAP call with STRO4TRC and ENDO4TRC from the 700 kernel library (add SAP700DEV to your libl only for the call of xxxO4TRC and remove it afterwards). Specify a trace id as a name, your job and qinter as the subsystem.
    HTH,
    Thomas

  • Old workflow behaving differently in upgrade from 4.6 C to ECC 6.0

    We are facing an issue in the workflow . Old and existing workflows before the upgrade have  different paths then the new workflow in the ECC6.
    Means , the same workflow when started from scratch is working fine , but when the old workflows are copied and run (the way which client is testing or you can say this way they do their work), then the workflow takes a different path. All the forks ,events,if clause are appearing as the last steps in the workflow grapic.
    Now my point is, that in upgrade there should not be any major change happened in SAP, seems that we may be missing some step to be performed after upgrade or during upgrade forits  standrad as well as custom worflows.

    Hello,
    I've never done the upgrade myself, but judging from what I've read it's very very important that you try to complete as many workflow instances before the upgrade. That doesn't help you much, but maybe others will take note.
    All you can do is search for your particular problem. Are there any error messages in the workflows?
    regards
    Rick Bakker
    Hanabi Technology

  • Upgrade from R/3 46C to ECC 6.0 (ERP 2005)

    Hello,
            We want to know the version of the kernel that has to be installed to begin with the upgrade. We have the 46D version already installed, do we have to update the kernel to 46D_EXT (is it the latest?) ?
    Thanks in advance,
    Pablo

    Hello,
    if you install the latest Oracle Client you can use 4.6D with Oracle 10g. Our configs work well with this client-kernel pair.
    You can find the documentation at http://service.sap.com/instguides "/other documentation/Database upgrades/Oracle: Upgrade to Oracle Database 10g Release 2 (10.2): UNIX"
    Best regards
    Tamá

  • Security: Lessons learned from Analysis Authorization Upgrade

    Hi,
    is there any lessons learned summarization from successfully migrated projects available!
    <b>How many old self developed auth. objects were migrated?
    Was the hierachy migration successfully?
    Was the old cponcept role based?
    Any timeline proposals for the migration?</b>
    thanks in advance
    Oliver

    If there are some documents available please send to
    [email protected]
    thanks in advance again
    Oliver

  • Short dump in MIGO and VL02N when upgrading from 46C to ECC 6.0

    Hello,
    We are doing an upgrade from R/3 46C to ECC 6.0 and we face a shortdump in trx MIGO (upon saving the document).
    DBIF_RSQL_INVALID_REQUEST
    a BKPF_INSERT in program SAPLF005
    The same shortdump happens when doing a Goods Issue on the SD side.
    Looking at the program, this is not modyfied so I guess it is a standard SAP error.
    OSS however, up to know did not respond to my message and there does not seem to be a SAP Note on this issue!
    Anyone had this problem before. How did they solve it.
    Thanks for any reply,
    Aart

    Posted in another forum

Maybe you are looking for