SAP 4.6C to ECC 6.0 Upgrade.Issues in Workflows

Hi Gurus
Can anyone please enumerate the list of issues likely to arise
when sap is upgraded from 4.6C to ECC 6.0.

There is  a wonderfule document in SDN related to upgrade from 4.6 to ECC 6.0. Please check that it is self explanatory and is of great help.
Check this link
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/103b1a61-294f-2a10-6491-9827479d0bf1
Thanks
Arghadip
Edited by: Arghadip Kar on Jul 23, 2008 12:53 PM

Similar Messages

  • 4.6C to ECC 6.0 upgrade - Issue with Virsa Compliance Calibrator

    The issue is that phase IS_SELECT during the PREPARE is not detecting VIRSA as an add-on. This of course will result in VIRSA not being upgraded and the system will be unstable ( note 989368 ). Also, I can't choose to delete the add-on either.
    We installed the compliance calibrator before SAP purchased VIRSA. So, the tool was installed through transports, not SAINT. I assume this is why phase IS_SELECT is not seeing the tool.
    Any ideas?
    -Scott

    Received a reply from SAP. Since VIRSA was installed through STMS the IS_SELECT phase will not see the add-on. I had to do the ECC 6 upgrade as normal and then install VIRSA 4.0 for SAP 700 systems through SAINT.
    I had to clear SPDD and SPAU as much as possible for /VIRSA/* objects. However, there were six objects I could not clear. This did not cause any issues.
    Notes 1006083 and 985617 are needed for this procedure.
    Thanks for all the suggestions.
    -Scott

  • ECC 6.0 Upgrade Issue !!

    Dear All,
    I have come across a FM MSQ_READ_TABLE_STATISTICS_HIST which exist in SAP 4.6 , but not in ECC6.0.
    Secondly I am not able to get the replacement of FM TZ_SYSTEM_TO_LOCAL.
    Can anyone tell me what are the replacments for the above Function Modules.
    Thanks and Regards,
    Rachit Khanna

    Hi Khanna,
    i dont' have system for 4.6C in ECC u can try like readstastics* then search for the function modules which is relacement of u r FM.
    For the FM TZ_SYSTEM_TO_LOCAL in this Fm documentation the replacement for this use the 'CONVERT' statement.This function functionality i is the system time is also in locaal time zone.
    Hope this may help you.
    Thanks,

  • SAP R/3 4.6C Cable Solutions upgrade to ECC 6.0 DIMP

    Hi all.
    We are planning to upgrade SAP R/3 4.6C system (Cable solutions) to an SAP ECC 6.0 (EHP4 - DIMP). We have few questions related to this upgrade.
    1. Since Cable solutions add-on is no more available in ECC 6.0 and its getting replaced with DIMP, what kind of data conversion/migration we need to perform before or after upgrade?
    2. Is there a data migration document available in SDN or SMP? We could not find such document though the note  664712 says there is a document ""Migration from Cable Solution V4.6C/1A to DIMP""
    3. Does the data conversion/migration will happen from SAP 4.6C to ECC 6.0 or it needs an SCM system?
    Thanks & Regards
    Senthil

    Thank you for your reply Gerald & Sunny.
    Still I am not clear on the following
    1. Where do we get the CS-to-DIMP-Migration-Guide.pdf document?
    2. Is SCM a mandatory? or all CS data can be migrated to ECC 6.0 DIMP system?
    would appreciate, if someone can throw some insight
    Regards
    Senthil

  • Upgradation Minimum sp level & kernel level for SAP 4.7 to ECC 6.0

    Hi,
    We recently created a test box , copy of devolopment.
    We are running on SAP 4.7 with sap_basis and sap_abap with sp level 46.
    SAP 4.7 with kernel release 640 and kernel patch version 155.
    Oracle 9i.
    What is minimum support pack level  and kernel patch level required to upgrade from sap 4.7 to ecc 6.0.
    As per threads it looks like kernel patch version should be 175.
    Can any one guide me with sap note which provides the info of minimum sp level and kerenl patch level.

    The source system requires a certain support package level (that is described in the upgrade guides) because the tools that to the import require them.
    So the easiest way is to check the upgrade guides and the mentioned notes which is the minimum support package level for the source system to start the upgrade.
    The target level must be at least equivalent or higher.
    Markus

  • Does anybody know benefices of upgrading SAP ERP from version ECC 6.0 EHP 7 to ECC 6.06 EHP 10?

    An upgrade of ERP SAP from version  ECC 6.0 EHP 7 to ECC 6.06 EHP 10 is being planned in the company I work for. However, I don´t know what the benefices are to   implement this upgrade so I wonder if someone knows benefices of upgrading SAP ERP from version ECC 6.0 EHP 7 to ECC 6.06 EHP 10?
    Regards, Alejandro

    Hi _Miguel
    I am going from ECC 6.0 to ECC 6.06. However, I don´t know what the benefices are to   implement this upgrade so I wonder if someone knows benefices of upgrading SAP ERP from version 6.0 to 6.06
    regards, Alejandro

  • SAP R/3 4.6 C to ECC 6.0 Upgrade using CU &UC method- Unicode conversion

    Basis Gurus
       I am working on upgrade from R/3 4.6C to ECC 6.0.
    ECC 6.0 upgrade completed( still in non Unicode).  Now I am in the process of Unicode conversion.
    I have used following methods for the upgrade.
    1. Combined Upgrade & Unicode conversion(CU & UC)
    2. Resource minimized( as I am doing it in Sandbox).
      As I understand I need to perform the DB export and Import now for the unicode conversion.
      According to the Upgrade document, First I need to run Export using R3load in ECC6.0(Non unicode)
      and then install Unicode system and import the same data file.
      My understanding was, when I choose, Resource minimized, I need to run Export and import
      in the same system.
      Can you please help me , whether I need another Unicode system for import ??
    Graham

    Hi,
    Dont get confused with upg strategy and unicode conversion.
    In general Upgrade strategy (either downtime-minimized/resource minimized)
    In unicode conversion you have export/import(exp/imp) of data concept
    In CU&UC approach you have to do in a streach to complete migrate from old release to new realease ECC 6.00.
    Using database independent (sapinst only) or Using database dependent (migration monitor or Distribution monitor)
    It can be done in 2 ways.
    If you dont have addtional server for unicode conversion
           1)you can either do exp on same hardware and take bakup and do import using the exp dump.
           2)Do exp on one server and prepare your target empty database on another server and complete imp of data.
    Hope this is clear.
    Regards,
    Vamshi.

  • ECC-600 EHP4 upgrade with VIRSAHR 520 700 - PREP_EXTENSION/ADDON_QCALC

    Hi
    We are getting following error at phase PREP_EXTENSION/ADDON_QCALC in the ECC 6.0 upgrade:
    3 ETN256 You want to install the following add-on components:
    3 ETN248 Component: "VIRSAHR" rel. "520_700", Support Package
    level: "0" (component type "A")
    3 ETN248 Component: "VIRSANH" rel. "520_700", Support Package
    level: "0" (component type "A")
    2 ETN085X"2. Adding Add-on Installation Queue" " " " " " "
    3 ETN262 Calculating queue part for add-on "VIRSAHR" rel. "520_700"
    3 ETN490 Use the Add-On installation package "SAPK-523EXINVIRSAHR"
    (type &4"AOX") for Add-On &2"VIRSAHR" rel.&3"520_700"
    3 ETN245 The following import prerequisites of OCS Package "SAPK-
    523EXINVIRSAHR" have not been met:
    3 ETN264 In the (alternatively) Requirement set "01":
    3WETN491 Required software component "SAP_HR" rel."600" is not installed2WETN543 OCS package "SAPK-523EXINVIRSAHR" does not match the current
    software component vector
    1 ETN214X."**************************************************"
    We have alreacy checked note 1002147, which clearly states that we have to include SAPK-523EXINVIRSAHR in the upgrade. SAP_HR is part of the upgrade.
    We have included SAP_HR and other Support Package as per the queue generated by Solution Manager, but we did not include VIRSAHR & VIRSANH Packages until we got to this phase. We then included these support packages in eps\in directory, but we are now getting this error now.
    Any ideas?
    Regards
    Chandu

    Hi
    This is what the solution provided by SAP Support:
    Quote:
    we have finally found the problem, it's a bug in the package upload
    functionality used by the upgrade. The consequence of this bug is that
    Support Packages whose EPS files (.PAT files) have a certain string in
    the name, namely the string 0000000 after the _ and before .PAT
    extension, are not properly uploaded to the ABAP system and hence are
    not visible or known to the upgrade.
    This bug will be fixed in the next upgrade tool fix, but in the meantimeyou can use the following workaround:
    Check your EPS/in directory after the CAR/SAR Archives of the SPs are
    extracted and rename all .PAT and .ATT files, which have a name like
    *_0000000.PAT (or *_0000000.ATT), by changing the string 0000000 to
    9000000. For example, for the VIRSANH SP SAPK-52302INVIRSANH rename the
    file VS30020106486_0000000.PAT to VS30020106486_9000000.PAT
    Afterwards, the upgrade will upload the informations about the SP
    properly and the SP can be included into the upgrade.
    Files:
    31/01/2007 07:32 329 VS30020106486_0000000.ATT
    31/01/2007 07:32 554,073 VS30020106486_0000000.PAT
    If these two files are renamed to e.g.
    VS30020106486_9000000.ATT
    VS30020106486_9000000.PAT
    the affected VIRSANH SP2 is uploaded correctly by the upgrade
    functionality and the SP inclusion of the VIRSANH SPs works.
    Sorry, as of now I cannot promise you a date when the tool fix will be
    available. I have found this bug only today in the evening (german time)and will discuss this with the responsible colleagues tomorrow.
    Afterwards, I will know more...
    Unquote:
    Hope this helps. We have decided against upgrading to 530_700 as it will involve upgrading GRC system and also new version has lot of new functionalities, which we like explore it after the ECC upgrade.
    Also, I would not suggest deleting VIRSAHR as all the config and customising done for VIRSAHR will be lost.
    Regards
    Chandu
    Edited by: Chandu Cheeti on Jan 17, 2010 11:19 AM

  • Problem with ECC 6.0 upgrade iseries

    Hello,
    We are upgradering our SAP 4.6c to ECC.6.0 on OS/400. This are the steps which i used to start the upgrade as shown in the Upgrade guide - SAP ERP Central Component 6.0 ABAP Support Release 3
    Operating System and Database IBM i5/OS/IBM DB2 for i5/OS
    *1. Login with QSECOFR.*
    *2 .MKDIR u2019/usr/sap/putu2019*
    *3. CHGPGP OBJ(u2019/usr/sap/putu2019) NEWPGP(R3GROUP) DTAAUT(RWX) OBJAUT(ALL)*
    *4. LODRUN DEV(OPT) DIR(u2019UMN_OS400_PPC64/UPGRADEu2019)**
    *5. Login with the <SID>OFR*
    *6. ADDLIBLE SAPUP*
    *7. GO SAPUP
    8. Here i choose PREPARE but received the following error message: Function check. CEE9901 unmonitored by PREPAREOS4 at statement 0000046300..
    When i checked the /usr/sap/put/bin content, i don't see the PREPARE file and also many files are missing. Maybe the LODRUN....didn't worked properly. We used the same CD for the our sandbox and it worked well.
    Regards
    Niclas
    Edited by: Niclas Glenneholm on Dec 15, 2008 12:54 PM

    Hi,
    Firstly, please ensure you are using the latest SAPup version. You can download it at  http://service.sap.com/patches.
    Any errors when you call qp2term:
      call qp2term
    Cheers.

  • 4.6 C to ECC 6.0 Upgrade Project Timeline Sheet in MPP format

    Dear all,
    We are now proposing our customer for the 4.6c to ECC 6.0 Upgrade.
    Our customer is currently in 4.6c/oracle 9i/HPUX 11 i. He wants to move to ECC 6.0.
    If you have the project timeline for the above Technical Upgrade, can you pl send it to me.
    If you don't have in MPP format atleast send me the Work Breakdown structure with timelines.
    I shall modity the same to our customer and submit
    Thanks & Regards
    Senthil
    [email protected]

    Preparation Phase* 6 days
    Kick Off Meeting 1 day
    Upgrade Project Procedures Preparation 1 day
    Prepare Upgrade Project Plan 1 day
    Technical Requirements Assessment 3 days
    Assess Training needs of Key-users & End-users 1 day
    Prepare Detailed Basis Activity List for DEV, QA & PRD 1 day
    Business Blueprint Phase 6 days
    Develop System Landscape Upgrade Plan 1 day
    Functional Requirement Checklist 1 day
    ABAP Development check list 1 day
    Develop detailed Training Procedures & Documentation for Key Users & End Users 1 day
    Identify Testing Scope & Scenarios 1 day
    Identify Authorizations Conversion to Roles for SAP ECC 6.0 2 days
    Develop Documents as per Basis Activity List 1 day
    Develop Authorization Matrix for Activity Groups to Roles Conversion 2 days
    Prepare Upgrade Deliverables Checklist 1 day
    Realization Phase 28 days
    Installation of Solution Manager 3.2 System 1 day
    Creation of New Development System for Upgrade Project (Homogenous System Copy - PRD) 2 days
    Upgrade to AIX & Oracle 10g, SAP ECC 6.0 on New Development Server 3 days
    Upgrade Frontend Software 4 days
    Perform SPAU & SPDD Corrections 5 days
    Perform ABAP Development & Corrections 10 days Perform Authorizations Conversions and corrections after upgrade 8 days
    Perform Upgrade Testing for each Application Module 7 days
    Perform Unit & Integration Testing 6 days
    Perform Training to Key Users & End Users (Generic & Specific) 3 days
    Upgrade to AIX, Oracle 10g, SAP ECC 6.0 on Quality System 1 day
    Homogenous System Copy of PRD to New Quality & Upgrade to AIX, Oracle 10g & SAP ECC 6.0 2 days Perform Testing in Quality System 3 days
    Testing by end users on Quality System 1 day
    Production Realization & Go-Live Phase 6 days
    Upgrade to Production System Operating System to AIX (after close of business hours - 23:00) 1 day
    Oracle Upgrade to 10g (after close of business hours - 23:00) 1 day
    SAP Release Upgrade to ECC 6.0(Downtime Minimized - Downtime occurs in non-business hours) 2 days
    User Acceptance Testing 1 day
    Production System Go-Live 1 day
    Post Go-Live Support 14 days
    Post Go-Live Support 14 days Note: This is high level plan subject to change during Business Blue Print Phase 0 days
    This is taken from a post in Ittoolbox, May be this is generic. Hope you can tailor this to meet your requirements.

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

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

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

  • Issues in ECC 6.0 upgrade

    Hello,
    We are doing an upgrade from SAP 4.7 to ECC 6.0. In step 2C of SU25 we get a large number of roles in "RED". How do we identify if any additions or changes have happened to these roles. Please help
    Many thanks
    Vijaya

    Hello Vijayalakshmi,
    pls use the search function in this forum (for instance <SU25> returns 11 hits, for instance this one: https://forums.sdn.sap.com/click.jspa?searchID=13818484&messageID=5409652
    > How do we identify if any additions or changes have happened to these roles. Please help
    >
    Well, if the roles are listed in SU25/2c, then there have been changes to that roles. In normal cases the SU24 values for the contained transactions have been changed or the transactions themeselves got changed/removed/replaced.
    The documentation for SU25 is quite good and gives some valuable information too.
    I hope this gives you a starting point for your upgrade project.
    Last tipp: it is not a good ideay, to skip SU25 after the upgrade. Sooner or later you will have to perform this task to avoid losts of reclamations regarding missing authorizations from your users.
    b.rgds, Bernhard

  • Load balancing after ECC 6.0 upgrade

    Hi
    I we this configuration on ECC 6.0 upgrade:
    SAPGUI 7.10
    SAP_BASIS  700  Patch level 15
    SAPportal ESS
    Webdispatcher Installed
    Internal ITS
    Single sign-on
    Can somebody assist as with identifying the problem with load balancing (PUBLIC) E.g. When running ESS remuneration package via the Sapportal. we have configured ITS-Based GUI Services on transaction SICF for customised ZESS_PZ11PDF service.
    When we have load balancing group on the load balancing does not work, because  I  see somebodyu2019s payslip
    but when using one app server I see my own payslip. Please help.

    Hi PR,
    Please take a look at the following link:-
    http://help.sap.com/SAPHELP_NWPI71/helpdata/EN/28/75153a1a5b4c2de10000000a114084/frameset.htm
    "You can only use the SAP message server for HTTP load distribution if 
    the browser is the direct client of the message server. If another     
    component lies between the client (browser) and the message server, (for
    example, the portal), you cannot use the message server to distribute  
    the load."                                                             
    When using the External ITS you could balance the load using the message server and logon groups. In 700 this functionality is not present if there is not a direct connection to the client (Firefox or IE). So you will have to install the webdispatcher to balance the load.
    Hope this helps
    Michael

  • Hardware requariment for ECC 6.0 upgrade from ECC 5.0

    Hello
    I am on ECC 5.0 with oracle 9.2.0.7.I need to upgrade this to ECC 6.0.
    I have already implemented MM,PP,FICO,QM and HCM.My current data base size is 900GB.This has 30GB monthly growth.
    With this ECC 6.0 upgrade i am planing to implement PM,EP.
    I know converting none Unicode system to unicode system is required some more hardware resources than the none Unicode.
    Some document says 40-60% more disk space and 35% more processing speed from current system.
    Can any one give me the correct information about the hardware requirement for ECC 5.0 to ECC 6.0 upgrade.
    Thanks
    Roshantha

    Check with the Links
    https://websmp102.sap-ag.de/sizing
    https://websmp208.sap-ag.de/quicksizer
    http://www.4soi.de/
    http://www.easymarketplace.de/
    Kanagaraja L

  • OM and PA data transfer from SAP 4.7 to ECC 6.0

    Dear Experts,
    hi
    i am working on one project where i will need to design the data transfer from SAP 4.7 to ECC 6.0. this is not a upgrade project.
    the data of PA and OM are in 4.7 which is existing system. i need to transfer entire data into ECC 6.0 so i can use that data for my E-Recruitment module ( we are doing E-rec fresh implementation.)
    we will keep both the systems (4.7 and ECC 6.0). ECC 6.0 will be used for E-Rec and OM only. for PA and Payroll we will use 4.7.
    can some one tell me,
    1. what are the key points to keep in consideration from OM point of view ?
    2. which is the best method to transfer the OM structure and data from 4.7 to ECC?
    3. what are the risks?
    4. which system we should make master system and which will be the slave system? why ?
    your input will be much appreciated.
    thanks and regards
    chandra

    Hi Chandra,
    I was under the impression that you are planning to use PA & OM from 4.7, now I read it again.
    Now its advisable to keep ECC 6 as a master system, becoz OM is the stating point of the HR processes where all Orgnization unit, job, position exists. Later the same data can flow to the slave system for PA use. As OM is the starting point, this system should be the master system.
    Abou the IDoc interface.
    Check the basic type HRMS_A05, whether it has all the data you need to transmit. T-Code WE30
    If you need to add something you can create a Z version in WE31. I selected HRMS_A05 as it is present in both the SAP version.
    Next there are series of transaction you need to process. Check with technical person who hands IDoc interafcing.
    Steps are:
    Assigning Message type to IDOC Type with extension. T-Code WE82
    Create Logical System:
    T-Code SALE-> Basic Settings-> Logical Systems-> Define Logical System
    It is required to configure in the sending system as well as in the receiving system
    Assign Logical System to Client:
    T-Code SALE-> Basic Settings-> Logical Systems-> Assign Logical System to Client
    Create RFC Destinations:
    T-Code SM59, select ABAP connection of type 3.
    Create Distribution Model: T-Code BD64
    Generate Partner Profile: T-Code BD82
    Maintain sending system partner profile: T-Code WE20
    Link Message Type to Function Module T-Code WE57 in receiving system only
    Hope this will help.
    Let me know if you need anything else.
    BR/Manas

Maybe you are looking for