ECC 6.0 UPGRADE WITH AFS 6.0

Hi ,
   We try to upgrade our R/3 Server to ECC 6.0 , The Upgrade was successfully completed . But iam not able to install the IS ADDON AFS 6.0 after the upgrade . The error shows the ECC DIMP has not to be installed .
Kindly tell me solution for this problem , It is possible to include AFS 6.0 during the upgrade phase , if it is possible , kindly tell me the steps .
Or tell me the solution for this problem .
Regards
PalaniSelvan

As I replied in your other three or four threads with almost the same question:
It's not enough to just try to import AFS, you have to import the corresponding CRTs as mentioned in
Note 1029517 - SAP AFS V600 : CRTs and Support Packages
Markus

Similar Messages

  • 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

  • 4.6C to ECC 6.0 Upgrade with EP 6.0

    HI
    We are planning to upgrade from 4.6C to ECC 6.0 . We have the Following as of now
    SAP ITS 6.2 standalone.
    ESS/MSS Business Packages for 4.6C
    SAP EP 6.0
    I understand that
    a) Migrating to Integrated ITS is a must
    b) EP 6.0 works with SAP ECC 6.0 as a product
    Now my question is
    a) It is required to Upgrade EP 6.0 to EP 7.0 . Is this Mandotary?
    b) What happens to ESS/MSS Business packages in the Upgraded ECC 6.0 System, Does this need any adjustments and can still work with SAP EP 6.0?
    Regards
    Deepak

    Hello there,
    I assume you mean Enterprise Portal. The general recommendation is that the portal must be based upon an equivalent or newer Netweaver version than the backend system. As the backend is going to be upgraded to a Netweaver 7  based released, EP 7 would be preferrable to staying with EP 6.
    EP 6 would work, but the colleagues from EP support told me EP 7 would be recommended.
    Best regards,
    Miguel Ariñ

  • ECC 6.0 UPGRADE - BW 3.10

    We are planning to upgrade our source system from 4.6C to ECC 6.0.  We are on BW 3.10 ( But planning to upgrade to BI 7.0 once after ECC 6.0 upgrade)
    Would like to know,
    1. Do we need apply any plug-in requirements to accommodate the ECC 6.0 compatibility?
    2. Will the existing BW 3.10 work without any issue with ECC 6.0?
    ( We are not going to do any change with new Business content available with ECC 6.0)
    3. What are the other precautions, we need to take in order to work BW 3.10 with ECC 6.0?
    Advance Thanks.

    refer replies here:
    Re: ECC 6.0 Upgrade with BW 3.5

  • UPGRADE ECC 6.0 with AFS 6.3 from R/3 4.7

    We are now preparing the upgrade of our R/3 server to ECC 6.0 with
    AFS . As per the plan and SAP guide for upgrade we started the prepare
    phase with upgrade master for ERP 6.0 . But in the initial stage i saw
    the page of prepare it showing all the induatry specific components
    like ECC DIMP ,IS_OIL etc . But we want to use AFS 6.3 . So if i
    continue the installation all the industry specific addon installed .
    So why because of the conflict iam should not apply AFS into our
    server .
    So kindly tell me how can i remove ECC DIMP like industry components
    from the prepare phase .

    good

  • Upgrade from ERP 6.0 with AFS 6.0 to ERP EHP4 - AFS 6.4

    Dear all,
    I've upgraded our Solution Manager to latest maintenance (all latest release/all latest Sp/all Oss notes)
    I 'm unable to have a queue with EHP4 - Afs 6.4 from Solution Manager
    If I define a system as SAP ERP 6 with Afs, the sol. man. give me the option to upgrade to EHP4 but 'forget' AFS 6.4.
    If I define a system as Afs Server 6, the sol. man doesn't show me the option to upgrade to EHP4.
    Any Idea to exit from this stall condition ?
    If I choose the option SAP ERP 6.0 to upgrade to EHP4, SAPHEPI will ask me the AFS upgrade CD and all AFS Sp ?
    My target is:
    - ERP 6.0 SPS 16 with AFS SP8 + ERP 6 EHP4 SPS 4 with AFS 6.4 SP 2, the max possibile now.
    Thanks tho who will try to help me.
    Regards

    Hi Reena
    Yes, you can upgrade the system to ECC 6 EHP 6 or 7,
    before that is any other SAP system are connected to ECC6 ?
    If it is yes, Kindly refer the SAP Note, & you require to check those SAP version are supported to ECC 6 EHP 7 ?
    1388258 - Version Interoperability within the SAP Business Suite
    BR
    SS

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

  • Error in WBS Element Hierarchy load after ECC 6.0 Upgrade

    Hi All,
    After ECC 6.0 Upgrade in R/3, we are doing test load in a Test server. While doing, we have encountered an issue with 0WBS_ELEMENT Hierarchy load. The message in the monitor is like below.
    "Node ID 00014240 has not been included in the hierarchy
    Message no. RH207"
    When I run the same hierarchy in another system which is not upgraded , it works fine.
    Anybody has faced similar kind of issues and can throw some light on this issue?
    Thanks,
    Mohan

    Try activating the Heirarchy in R/3 and re-trigger the load, error is very specific to structure of the hierarchy. there is a possibility that this Hierarcy could have got inconsistent after the upgrade.
    Thanks,
    Amit

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

  • 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

  • ECC 6.0 Upgrade - Problem in phase PARDIST_SHD

    Upgrading from 4.6C to ECC 6.0 on Windows/SQL Server.
    Phase PARDIST_SHD failed with the following error:
    "Table change not possible.  There is a DB trigger on the table." 
    This problem is documented in the note 825146 (Add Info on upgrading to NW04s) in section IV item number 7.  The note points to note number 956198 for the fix, which is to delete the trigger defined on table MSSDEADLCK manually in the SQL Server query analyzer.
    I have performed the steps outlined in note 956198 to delete the trigger, but when restarting the upgrade it keeps coming back with the same error.  It seems that, even if I restart the upgrade with INIT option, the upgrade is not re-setting to the beginning of the phase, but continues to error out immediately upon restart.  Originally the phase took about 45 minutes to complete before it aborted with the error.  Each time I have restarted the phase it ends after only a few seconds.
    Anyone have any thoughts?  I'm real close to just starting the whole thing over, I've never run into anything like this before.  I am using the latest SAPup.

    SAP gave me the answer.
    ATAB needed to be renamed the Operation library.

  • DB Migration and ECC 6.0 Upgrade

    I have a number of questions, we have a SAP R/3 4.7x200 landscape that is currently Windows 2003 and SQL2000 both 32 bit, we want to do the following, move to Windows 2003 and SQL2005 64bit, perform a Unicode and ECC6.0 Upgrade.
    here are the steps I am planning on new hardware
    1. Migrate to 64bit
    -install 64bit OS and SQL2006 64bit on new hardware
    -export db from current 32 bit and import into 64 bit system
         a. I am confused, I have seen threads where it appears this was done in house, do we need an SAP certified      person to complete this task, this is a hetergenous copy? Note 82478
         b. can we do this inhouse if we follow the SAP documentation and checklists provided and have their signoff      with checks
    - Run tests and then confirm process before real migration
    2. Perform Unicode Upgrade
    - run this on sandbox, test and verify
    3. Perform ECC 6.0 upgrade
    - run this on sandbox a no. of times confirm
    - freezing development and starting with DEV (this is a small landscape, we can do this)
    p.s can steps 2 and 3 be combined in one step, I have broken that out, to in my mind make it simpler to fix if anything breaks.

    Hi,
    DB Migration
    1. MS SQL Server 2000 is based on BIN collation and MS SQL Server 2005 is BIN2 collation. SO you need to first convert BIN to BIN2 collation.
    Note 960769  Windows Migration from 32bit to 64bit x8664
    Note 799058 - Setting Up Microsoft SQL Server 2005
    2. can steps 2 and 3 be combined in one step?
    Yes. check with link http://service.sap.com/erp-upgrade
    Regards,
    Srini Nookala

  • CRM2007 upgrade with BI 7.0 and SEM 6.0

    Scenario: We currently use Opportunity Planning on CRM 4.0, (with BI 3.5 and SEM 4.0). We are upgrading to CRM2007 using only the Sales "Account and Contact Management" and Sales "Lead and Opportunity Management" scenarios in this phase.
    We know that upgrade to BI 7.0 is required to support Lead and Opportunity Management and that BI 7.0 will only work with the SEM 6.0 version.  We are on ECC 5.0 and do not plan an upgrade to ECC 6.0 at this time.
    Question: Can someone confirm 1) that SEM 6.0 is required with BI 7.0 and, 2) If required, can we upgrade to SEM 6.0 in conjunction with our BI upgrade versus as part of a larger upgrade to ECC 6.0 (which now includes the SEM 6.0 component)?
    Thanks
    Edited by: Rick Moore on Apr 10, 2008 1:17 AM

    Hai,
    2) We do have the SEM 4.0 addon in existing BI 3.5. Where can we get the media for the SEM 6.0 upgrade so we can upgrade with BI 7.0? We have only been able to locate it packaged with ECC 6.0 media. Can we obtain it separately?---> The media can be obtained from SAP itself or else you can download the same from SAP ServiceMarketplace.
    The Upgrade CDs for BI 7.0 are Netweavers2004s CDs only,it contains all the required media for upgrade of both BI and SEM simultaneously.
    3) Our ECC 5.0 does not contain any SEM component. I don't believe it is packaged with ECC until 6.0. Is that correct? Our BCS consolidation uses the SEM 4.0 component in our BI 3.5.------> We can get the SEM compoenet for ECC 5.0 also. The SEM can be more customized with BI or WAS700.
    Thanks and Regards,

  • ECC 6.0 Upgrade from 4.7 - EDI Interfaces

    Hi Gurus,
    Need your inputs on what are the precautions to be taken during ECC 6.0 Upgrade related to EDI Interfaces.  with SAP upgrading from 4.7 to ECC 6.0, do you see any precautions need to be taken considering the middle ware involvement.  Also, is there any changes in IDOC Structures in ECC 6.0 which my cause issues related mapping with middleware.
    Please suggest.
    Thanks & Regards,
    C.L. Narasimhan "CLN"

    Hi,
    generally, a release upgrade, delivers new idoc/message types or new releases of existing idoc/message types.
    So, taking this in mind, you shouldn't have problems for the mapping of the messages, because the versions of the basic idoc, once released, cannot be changed.
    You might have some application problems related to the inbound interfaces, but this is part of the game...the testing phase will highlight whether the problem exists.
    A known problem is that the upgrade removes all the customer specific entries in the system table EDIFCT.
    Further details are provided in the OSS note [https://service.sap.com/sap/support/notes/865142]
    Regards,
    Andrea

Maybe you are looking for