Installation of ECC-DIMP 604 on ERP 6.0 already in EHP4

Hello,
I have a problem regarding the installation of ADD-ON ECC_DIMP 604. My sistem is ALREADY a ECC 6.0 with EHP4 installed. I used the techinical usage FINANCIALS during the queue calculation on SOLMAN.
Now I want to implement this add-on with transaction SAINT . The transactrion asks for an XML file that I'm unable to generate thru SOLMAN MOPZ.
It give me an error like
OCS PACKAGE SAPK-603DHINSAPAPPL DOES NOT MATCH CURRENT SOFTWARE VECTOR
ABAP QUEUE CHECK FAILED
I'm really stuck. Please advise
Kir

Hi,
To implement any add-on in EHP4 system, you need stack xml file. As per your logs it looks like that stack xml file is wrong. Please check stack xml file again.
Also, while downloading stack xml file from MOPZ, please select technical usage related to ECC-DIMP only.
Thanks
Sunny

Similar Messages

  • ECC-DIMP 604 upgrade

    Hi exports,
    I had alredy upgraded my ECC 6.0 Ready to EHP4, know i am trying to upgrade the component ECC-DIMP using SAINT.
    My OS platform is HP-UX IA and DB is Oracle.
    In the SAINT queue i had put both ECC-DIMP 603 and 604, along with stack.xml
    While import during DDIC_ACTIVATION phase it failed and the log file shows "tp ended with return code 12 ".
    I had checked the file system and data base tables, it seems ok.
    Recently i had upgrated my kernel to 117, which is the latest one.
    Also i had alredy gone through all the below mention notes, and taken action as necessary
    Note 822380 - Problems w/ add-on inst/upgrade to SAP NW 7.0 AS ABAP
    Note 874473 - Release strategy for ECC-DIMP as of ECC 6.0
    Note 874471 - Additions for installing or activating ECC-DIMP on ECC 6.0
    Note 1083533 - Installation of Enhancement Package 3 on SAP ERP 6.0
    Note 822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP
    Note 822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP
    Note 1118803 - ECC 600 Support Packages and ERP enhancement packages
    Note 1119856 - Description, tips and tricks for Attribute Change Packages
    Note 1258938 - DDIC_ACTIVATION error during EhP4 installation
    Please provide your valuable suggestion
    Thanks & Regards
    Dusmanta

    Hi,
    The problem is solved after applying SAP Note 1476315 - Error in activation protocol for switch framework.
    You need to implement the coding corrections of the note to your system and restart import . If the note cannot be
    implemented via SNOTE, as most likely the note assistant may be locked . Please ask one of your developers to perform the changes manually via SE80/SE24
    Regards
    Dusmanta.

  • Error in installation of ECC 6 Import ABAP

    I have got error during installation of ECC 6 on win 2003 and oracle.
    "Not all objects are succefully processed. DIAGNOSIS: For detail  see output file with invalid objects invalid_objects.txt and log file object_checker.log SOLUTION: Normally it indicates the data load error but in some special case (for example if some objects were created or loaded externally) you can press OK to continue.
    Here is invalid_objects.txt
    checkObjects=
    dbType=ORA
    strDirs=E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_1\EXP1\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_2\EXP2\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_3\EXP3\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_4\EXP4\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_5\EXP5\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP6\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP7\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP8\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP9\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP10\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP11\DATA
    trace=all
    tskDir=C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS
    package   object  type  action  status
    SAPDFACT  ?N      pkey  create
    and object_checker.log
    INFO: 2020-12-31 10:12:55
    Object Checker is started.
    CONFIG: 2020-12-31 10:12:55
    Application options:
    checkObjects=
    dbType=ORA
    strDirs=E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_1\EXP1\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_2\EXP2\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_3\EXP3\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_4\EXP4\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_5\EXP5\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP6\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP7\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP8\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP9\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP10\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP11\DATA
    trace=all
    tskDir=C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS
    CONFIG: 2020-12-31 10:12:55
    List of packages with table structure: 'SAP0000'.
    INFO: 2020-12-31 10:12:55
    19 packages found in 'E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_1\EXP1\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_2\EXP2\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_3\EXP3\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_4\EXP4\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_5\EXP5\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP6\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP7\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP8\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP9\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP10\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP11\DATA' directories.
    TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'MAPR~ADQ' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (!MSS) index 'MLST~1' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'MLST~1AD' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (!MSS) index 'MLST~2' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'MLST~2AD' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (!MSS) index 'MLST~4' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'MLST~4AD' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'PLMK~ADQ' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'SEMPLOYES~ARE' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'SEMPLOYES_APP~ARE' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'SEMPLOYES_RB~ARE' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'SEMPLOYES_TI~ARE' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'SEMPLOY_CSH~ARE' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'SEMPLOY_SEARCH~ARE' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'STXH~TDN' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:58 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'BBSID~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:58 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'BSID~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:58 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (DB6) index 'DB6CSTRACE~1' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'KBED~3' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'KBED~4' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'NAST~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S003~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S003BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S003BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S004~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S004BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S004BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S006~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S006BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S006BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S011~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S011BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S011BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S012~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S012BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S012BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S013~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S013BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S013BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S031~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S032~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:13:02 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (DB6) index 'VARIS~DB6' found in STR file for 'SAPAPPL2' package.
    TRACE: 2020-12-31 10:13:04 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Data load must be skipped for table 'DBPROPERTIES' from STR file for 'SAPSDIC' package.
    TRACE: 2020-12-31 10:13:04 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Data load must be skipped for table 'DDLOG' from STR file for 'SAPSPROT' package.
    ERROR: 2020-12-31 10:13:05
    1 objects have error/ignore/execute or unknown status in the task lines.
    Invalid objects are saved in 'invalid_objects.txt' file.
    INFO: 2020-12-31 10:13:05
    Object Checker is stopped.
    I have not installed any object manually. Also not sure which object did not installed properly? Any idea or suggestion for this?
    Thanks
    Edited by: Prinesh Patel on Jan 7, 2008 7:35 PM

    Hi Patel,
                         Thanks for your update.
    Regards,
    Hari.

  • Installation of ECC 6.0 on Windows Vista

    HI,
    I am not able to install ECC 6.0 on windows vista OS even I tried to install windows server 2003 but it shown incomitablity error becuse of newer version of OS(windows Vista).Could you let me know how can i remove the vista and get win server 2003 installed at my system.If I run the set up file of windows server 2003 it gives error "setup cannot run in program compatibility mode".Please let me know what else i can do.
    Thanks & Kind Regards
    Sanjay Rai

    Hi Sanjay,
    Few things you have to check before installation of ECC 6.0 on any OS :-
    1. From where have you got the dump for ECC 6.0? Have you downloaded it from Service Marketplace. If Yes then you have to check whether your OS is also of the same configuration as the dump you are using like if you are using 32-bit then your OS also needs to be 32-bit only. As far as ECC 6.0 SR3 is concerned it can be installed on 64-bit machine only. For 32-bit machine you have to go for SR2.
    2. Also the supported JDK for the ERP 6.0 is JDK 1.4.2_17 as per SAP Note 716604. Please uninstall the current JDK and install the required one. The 64 bit JDK as per the SAP Note 941595 is available on the new IDES server.
    3.Although there is cheat code to install the SAP ERP6.0 in 32 bit mode as well. But in that case NO Java system will be installed. I will advise for 64 bit method with Java system. Only use 32 bit mode if 64 bit is not possible. Follow SAP Note 1244548.
    4. The DB Size system will need around 190 -200 GB to install.
    Thanks,
    NItesh Jain

  • SRM "one-client" installation on ECC 6.0 EhP: Own client needed for SRM?

    Hello experts,
    i've a question concerning the SRM "one-client" installation on ECC 6.0 EhP4 as Add-On.
    Is it possible to use SRM and ERP funtionality in a single client e.g. 001?
    Or do we have to use different clients on the system like for SUS?
    I haven't found any information regarding this topic in SAP ressources. I'm currently using CG "SAP SRM on One Client in
    SAP ERP" Release date 2008 (found on marketplace/srm-inst --> srm7.0); SRM - Technical Basis Configuration (BuildingBlock S00/S03). I'm facing problems while going through the following customizing steps:
    Assign logical System to Client [both logicall systems are on the same client (001)] ==> error while trying to reference the second logical sys. because client (001) cannot be used again (own presumption: error message differs)
    I've seen that some of you have successfully installed and customized this szenario. If someone could provide me any helpful information or guideline how to proceed in general... would be great...
    Best regards,
    PATRICK

    Thanks for your reply. I've checked the offline documentation because i've no access to solman.
    There is a document which describes the steps for configuring one-client customizing on marketplace.
    Link: [SAP SRM 7.0: SAP SRM on One Client with SAP ERP|https://websmp203.sap-ag.de/~sapidb/011000358700001201562009E]
    The problem is that its impossible to cofigure the system like it's described in the document.
    Let me explain why...
    SRM Addon is installed and customizing is done in client 001 (same client as erp)
    overview about defined logical systems:
    -ONECLNTERP (for ERP is defined)
    -ONECLNTEBP (for SRM is defined)
    When I try to assign the logical system to client 001 it works for the first entry
    for the second log. system it shows up an error message.
    -->I assume because client 001 has been already assigned. I cant use client 001 again.
    But One-Client szenario schould be possible in a single client or is SAPs One-Client more like One-System with differnet clients for SRM and ERP on the same machine?
    Because of the above mentioned problem I assume that it's impossible to run ERP and SRM in the same Client number.
    Am I right? Do I have to use two Clients on One System for proper Customizing?
    Or if it's possible to use a single client on one machine for both ERP and SRM how is it possible to assign two log. systems to one client number?
    I'm totally confused. Any help would be appreciated  - any tips/hints/experiences from someone who has customized One-Client?
    BR, Patrick

  • ECC 6.0 or ERP 6.0???

    Experts,
    What's ERP 6.0?
    Is it different from ECC 6.0? HowSay during an upgrade we perform SPDD & SPAU on ECC 6.0 and ERP 6.0 comes up, what are the next steps?
    NW
    Edited by: NW on Aug 11, 2008 4:15 PM

    Hi
    for those with the same question:
    SAP ERP 6.0 (formerly known as mySAP ERP 2005) is the name/ release of the complete SAP ERP application. The predessor is mySAP ERP 2004.
    The large SAP ERP application consist of > 30 (?) installable units. One of these installable units is SAP ECC (6.0). Others are SAP NW - EP Core, SAP FSCM - Server ABAP, SAP SEM, etc.
    [=> SAP ECC is a part of SAP ERP 6.0, and not only an alternative name].
    SAP ECC is as well a special case, because it is the successor component of the former SAP R/3 (46c, Enterprise...)
    [=> SAP R/3 is part of the very much larger SAP ERP (6.0)]
    regards,
    Andreas R

  • Missing Customizing settings for software component ECC-DIMP

    Hi all,
    While running the T-code IE4n I am getting this error:
    Missing Customizing settings for software component ECC-DIMP
    This is working fine in IDES ECC 6.0 ,Could u please tell me how to resolve it for my othersystems.
    Thanks
    Yinyan Lu

    Dear Yinyan Lu,
    Please, have a look into the SAP note 767108 (IE4N: Problems due to missing notification Customizing)
    Solution                                                                  
    To correct this error, implement the correction instructions contained    
    in this note or import the relevant Support Package.                                                                               
    In packages                                                                               
    o  DI in Release 4.6C2                                                                               
    o  DIMP in Release 4.71 and higher                                                                               
    o  EA-APPL as of Release 4.7 Extension Set 2 and higher                                                                               
    notifications are created when installing and dismantling. In this case,  
    Customizing must be complete, otherwise errors will occur.                                                                               
    In DI Release 4.6C2 and DIMP Release 4.71 (and higher),                   
    follow the following Customizing path:                                    
      Plant Maintenance and Customer Service                                  
        -> Maintenance and Service Processing                                 
          -> Maintenance and Service Notifications                            
            -> Determine Properties of Notifications for Installing and                                                                               
    Dismantling Parts                                                                               
    Always maintain the notification type for installation and for            
    dismantling.                                                                               
    Follow the following Customizing path on EA-APPL as of Release 4.7        
    Extension Set 2 (and higher):                                             
    follow the following Customizing path:                                    
      Plant Maintenance and Customer Service                                  
        -> Maintenance and Service Processing                                 
          -> Configuration Control                                            
            - > Determine Properties of Notifications for Installing and      
               Dismantling Parts.                                             
    Always maintain the notification type for installation and for            
    dismantling.                                                                               
    What must you do if you do not want to use notifications in IE4N?                                                                               
    1.  You must always maintain the notification type in accordance with     
        Customizing described above.                                                                               
    2.  Create an individual, empty implementation for the BADI               
        BADI_CCM_NOTIF_GENER. To do this, proceed as follows:                                                                               
    a) Execute transaction SE18.                                                                               
    b) Specify BADI_CCM_NOTIF_GENER as the BADI name.                                                                               
    c) Use the menu <Implementation><create> to create an individual      
           implementation with a corresponding name in the Z namespace.                                                                               
    d) You enter the BADI Builder. Name the implementation, and then      
           save and activate your implementation. It is important that the    
           methods CREATE, FILL_CUST_DATA, MODIFY, SET_HEADER_MESSAGE, and    
           PRINT_NOTIF are empty.                                                                               
    Note that these steps are required, since the BADI                    
        BADI_CCM_NOTIF_GENER is equipped with a default source code that      
        includes the use of the notification.                                                                               
    As of ECC600, Note 1368876 replaces error message IEN 126 with error      
      message IEN 026, which is more precise.                                                                               
    Caution:                                                                               
    o  The error message mentioned above indicates that Customizing is    
             missing. To correct the problem, you must perform the relevant     
             Customizing settings for transaction IE4N.                                                                               
    o  As of ECC600, you do not have to activate the DIMP switch (this    
             may not be useful).                                                                               
    o  For more information, see Note 1368876.                                                                               
    I hope, it helps.
    Best regards,
    Roland

  • SAPEHPI ECC-DIMP missing addon - XML error ?

    Hello.
    I'm trying to instal EHP3 using sapehpi, at the configuration step after the stack XML file is loaded I have this error.
    ERROR: Unable to generate addon queue due to missing addons or support packages.
    Missing Support Package(s):
          (ECC-DIMP)
    The Enhancement Package Stack does not fit to the current system.
    The XML was created in a similiar system that we have in our landscape then changed the SID, hostname and installation number. But the stack XML created in MOpz of solution manager manually edited doesn't have anything of ECC-DIMP.
    The XML had to be manually edited because the download stack wasn't for this SID. That had to be done since this error Maintenance Optimizer don't detect EHP3 files, only EHP4
    And we require EHP3 (not ehp4) for a Baseline install.
    Any idea why ECC-DIMP says missing when the stack xml validates the previous ehp3 and stacks, in the earlier screen?
    System is running sap ehp1 netweaver 7.0, and has Ecc-dimp 600, level 16 installed.

    Hi Ruben,
    Your target system has ECC-DIMP installed, while the stack xml has no details about this. This could be one reason why you are getting this error.
    Try to retrieve the stack xml from the solman using RFC. This way you don't need to manually transfer or edit the stack config file. To get this to work, log on to the target system and check table BCOS_CUST using transaction SM30, and make sure that you see the name of the RFC connection OSS_MSG to SAP Solution Manager. Please take a look at this doc for more details: https://websmp208.sap-ag.de/~sapidb/011000358700000293582009E.PDF
    Another reason why this could happen is explained in SAP note 1387523.
    Let me know if you are still stuck.
    Cheers
    Rishi

  • DIMP 471 to ERP Upgrade requires MRP regen

    With our trial upgrade from Enterprise 470 with DIMP 471 industry to ERP 60 (basis 13, app 11, ECC - DIMP 11, we are finding it necessary to delete all mrp lists and run regenerative mrp for all plants to prevent an abap dump with collective mrp lists.
    mdtc is the table involved. We have been unicode for a year now so it is the change to erp60 with DIMP that has required this rather tedious post upgrade process. There are no notes about this. Has anyone encountered this?

    The dump is :
    Runtime Errors         CONNE_IMPORT_WRONG_STRUCTURE
    Exception              CX_SY_IMPORT_MISMATCH_ERROR
    Short text
        Error when importing object "MDTBX".
    55 *   Einlesen komp. Dispoliste
    >>     IMPORT MDTBX FROM DATABASE MDTC(AR) ID DTNUM_OLD.
    57   ELSE.
    Solution is to follow advice in note 1009454 that was about a Unicode error with DIMP but is also relevant to this situation.
    After the release upgrade, delete the old MRP lists using transaction MD08. Afterwards, you can create the MRP lists again using an MRP with the NEUPL processing key.

  • Installation of Business Suite 7 for ERP

    Hi Friends,
    I need ur suggestions and support for installation of  Business Suite 7 for ERP
    My client requirement is,
    They need  installing  Bussiness Suite 7 components (CRM,SRM,SCM,PLM) in single server.
    Is its possible,
    i waiting for  valuable reply.,
    regards,
    R.Selva kumar

    HI,
    Each SAP Component is having its own resource requirements. Please read their corresponding Installation Guides to get information about H/w and S/w requirements.
    Nowadays use of Virtualization technology is in more demand.
    Please read [ Note 1122387 - Linux: SAP Support in virtualized environments|https://service.sap.com/sap/support/notes/1122387] and [Note 171356 - SAP software on Linux: Essential information|https://service.sap.com/sap/support/notes/171356] to get more information.
    Regards,
    Bhavik G. Shroff

  • Installation Of ECC error in step create temp licence:

    We are in process of installation of ECC 6.0 on our server with OS: RHEL5 and DB:MaxDB
    We are getting an error in step Create Temp Licence. The error reads as follow.
    INFO 2008-02-21 04:56:12
    Execute step createTempLicense of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_ADA|ind|ind|ind|ind|1|0.
    INFO 2008-02-21 04:56:12
    Working directory changed to /tmp/sapinst_exe.8005.1203531194.
    ERROR 2008-02-21 04:56:12
    FRY-00001  Cannot load library iamodapp.so: iamodapp.so: cannot open shared object file: No such file or directory.
    INFO 2008-02-21 04:56:12
    Working directory changed to /sapinstd11n.
    ERROR 2008-02-21 04:56:12
    MUT-03025  Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
    ERROR 2008-02-21 04:56:12
    FCO-00011  The step createTempLicense with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_ADA|ind|ind|ind|ind|1|0|createTempLicense was executed with status ERROR .
    Please suggest.

    Hi,
    the installation process aborts in "Create sap license" with error message "library iamodora missing", some libraries needed are missing to work around this, either after it aborts or event before staritng the installation unpack the libraries into the installation directory using:
    SAPCAR -xvf /<sapinst-CD>/SAPINST/UNIX/LINUX_32/SAPPROD.SAR
    1. Copy the installation media dvd to a directory on a files system
    2. change directories into the sub-directory which contains the executable (sapinst)
    3. run the command sapinst -extract
    4. It will unpack the missing libraries into the same directory where you executed the command..
    5. copied these libraries to lib folder
    6. Stop and restart the installation
    regards,
    kaushal

  • IS O&G - is it possible to use MPL without activating the ECC- DIMP?

    Hi
    We are an Oil and Gas industry and activated IS oil and gas in ECC6.0, our requirement is to use functionality such as Master Parts list which is there in ECC-DIMP under configuration control, as some companies within same group where MPL is required .
    The question is it possible to use MPL without activating the ECC- DIMP
    Request you to please help us to understand.
    Regards

    Hi Venkat,
    If a report is created over a DSO, it pulls data from the active table of a DSO. So as suggested in all the posts above it is not possiable to report on the DSO without activating it.
    Activation of DSO only allows to generate SID's to link transaction data and master data, SID's could also be generated at the time of reporting (When the report fetches data from BI server, but for the SID generation data is needed in active table). Also activation checks the correctness of data etc.
    Could you please let know why you want to report on the unactive request, is it having some problem with activation?
    Regards,
    Pankaj

  • Quicktime wont load because the installer thinks I have a newer level quicktime installed already.

    quicktime wont load because the installer thinks I have a newer level quicktime installed already.  Thus the newest level of iTunes and quicktime will not install, help... Thanks.

    Unfortunately, this sort of trouble has gotten more complicated to deal with ever since Microsoft pulled the Windows Installer CleanUp utility from their Download Center on June 25. First we have to find a copy of the utility.
    Let's try Googling. (Best not to use Bing, I think.) Look for a working download site for at least version 3.0 of the Windows Installer CleanUp utility. (The results from mydigitallife and Major Geeks are worth checking.)
    After downloading the utility installer file (msicuu2.exe), scan the file for malware, just in case. (I use the free version of Malwarebytes AntiMalware to do single-file scans for that.)
    If the file is clean, to install the utility, doubleclick the msicuu2.exe file you've downloaded.
    Now run the utility ("Start > All Programs > Windows Install Clean Up"). In the list of programs that appears in CleanUp, select any QuickTime entries and click "Remove".
    Restart the PC, and try another install. Does it go through properly this time?

  • After the OS X Lion installation, my USB modem doesn't work. I already updated the USB drivers, but nothing happened. Any suggestion?

    After the OS X Lion installation, my USB modem doesn't work. I already updated the USB drivers, but nothing happened. Any suggestion?

    You might want to do a search here on the forums re. usb modems - I've seen several threads and the opinion appears to be that faxing is no longer supported (especially since the "Fax" is now missing from the Print Preference Pane in System Preferences). I am faxing with an all-in-one printer which is connected to a landline, but I have to use the printer's control panel - can't use it from the iMac.

  • Error During installation of ECC 6.0 EHP5 on windows and Oracle

    Dear All,
    I am facing an error at the Phase 1 of installation i.e creating users.
    Creating account Domain
    \SAP_SID_GlobalAdmin for system SID,
    Please provide your sugegstions on this ASAP.
    OS: Windows Server 2008
    Database: Oracle 11g
    SAP: ECC 6.0 EHP5
    Error details :
    An error occurred while processing option SAP Business Suite 7i 2010 > Enhancement Package 5 for SAP ERP 6.0 > SAP Application Server ABAP > Oracle > Central System > Central System( Last error reported by the step: System call failed. Error -2147024891 (Access is denied. ) in execution of system call 'IADsGroup::SetInfo' with parameter (), line (976) in file (d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\syslib\synxcgroup.cpp), stack trace: d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\ejs\ejscontroller.cpp: 181: EJSControllerImpl::executeScript() d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\ejs\jsextension.hpp: 891: CallFunctionBase::call() d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\osmod\iaxxbaccount.cpp: 85: CIaOsAccount::createGroup_impl() d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\syslib\synxcaccmg.cpp: 190: PSyGroupInt CSyAccountMgtImpl::createGroup(iastring sName, iastring sSID, ISyProgressObserver*) const d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\syslib\syxxccache.cpp: 244: CSyAccountCache::getGroupImpl(name="NMCORP\SAP_BRT_GlobalAdmin", sid="", create=true, ISyAccountMgt::eAccountType, ISyProgressObserver* ) d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\syslib\synxcgroup.cpp: 54: CSyGroupImpl::CSyGroupImpl(NMCORP\SAP_BRT_GlobalAdmin, , bool bCreate) d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\syslib\synxcgroup.cpp: 828: CSyGroupImpl::addToOS(ISyProgressObserver* pObserver) .). You can now:
    Choose Retry to repeat the current step.
    Choose Log Files to get more information about the error.
    Stop the option and continue with it later.
    Log file:
    TRACE      2014-08-08 14:17:59.293 [iaxxclib.cpp:174]
               CLib::load()
    Opened C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864\\sylib722.dll
    TRACE      2014-08-08 14:17:59.293
    exe dir is C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864
    TRACE      2014-08-08 14:17:59.512
    MessageLib initialized successfully.
    INFO       2014-08-08 14:17:59.527 [synxcpath.cpp:798]
               CSyPath::createFile() lib=syslib module=syslib
    Creating file C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864\dev_sap_kernel_test_08_Aug_2014_14_17_59.
    INFO       2014-08-08 14:17:59.527 [synxcfile.cpp:368]
               CSyFileImpl::removeEx(ISyFSErrorHandler * pErrorHandler)
               lib=syslib module=syslib
    Removed file C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864\dev_sap_kernel_test_08_Aug_2014_14_17_59.
    TRACE      2014-08-08 14:17:59.543 [syxxclogbook.cpp:211]
               PSyLogBook::initSAPKernelTracing(int traceLevel, const CSyPath & filePath)
               lib=syslib module=syslib
    Initialized SAP kernel tracing to file C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864\dev_sap_kernel
    TRACE      2014-08-08 14:17:59.543 [csicomponentsetmanager.cpp:111]
               CSiComponentSetManager::readFrameworkJslib()
    Reading framework jslib.
    TRACE      2014-08-08 14:18:00.981 [iaxxclib.cpp:174]
               CLib::load()
    Opened C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864\iaguieng722.dll
    TRACE      2014-08-08 14:18:00.981 [syxxclogbook.cpp:211]
               PSyLogBook::initSAPKernelTracing(int traceLevel, const CSyPath & filePath)
               lib=syslib module=syslib
    Initialized SAP kernel tracing to file dev_sap_kernel
    TRACE      2014-08-08 14:18:00.996
    Waiting for client connection (1)
    TRACE      2014-08-08 14:18:06.684 [synxcuser.cpp:2083]
               CSyUserImpl::isExistingOnOS() lib=syslib module=syslib
    existence check for user brtadm returned true.
    TRACE      2014-08-08 14:18:06.684 [syxxccache.cpp:419]
               CSyAccountCache::addToCache(const IaPtr<CSyAccountImpl> account)
               lib=syslib module=syslib
    inserted account (brtadm, S-1-5-21-575922271-569720141-4272231626-387102, USER) into the accountcache.
    TRACE      2014-08-08 14:18:06.684 [synxccuren.cpp:901]
               CSyCurrentProcessEnvironmentImpl::setEnvironmentVariable(const iastring & 'SAPINST_JRE_HOME', const iastring & 'C:/Users/brtadm/AppData/Local/Temp/2/sapinst_exe.3932.1407503864/jre')
               lib=syslib module=syslib
    Environment variable SAPINST_JRE_HOME set to value 'C:/Users/brtadm/AppData/Local/Temp/2/sapinst_exe.3932.1407503864/jre'.
    INFO       2014-08-08 14:18:07.716 [synxcpath.cpp:798]
               CSyPath::createFile() lib=syslib module=syslib
    Creating file C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864\dev_sap_kernel_test_08_Aug_2014_14_18_07.
    INFO       2014-08-08 14:18:07.716 [synxcfile.cpp:368]
               CSyFileImpl::removeEx(ISyFSErrorHandler * pErrorHandler)
               lib=syslib module=syslib
    Removed file C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864\dev_sap_kernel_test_08_Aug_2014_14_18_07.
    TRACE      2014-08-08 14:18:08.216
    exe dir is C:/Users/brtadm/AppData/Local/Temp/2/sapinst_exe.3932.1407503864
    INFO       2014-08-08 14:18:08.247 [synxcpath.cpp:798]
               CSyPath::createFile() lib=syslib module=syslib
    Creating file C:\Program Files\sapinst_instdir\x.
    INFO       2014-08-08 14:18:08.247 [synxcfile.cpp:368]
               CSyFileImpl::removeEx(ISyFSErrorHandler * pErrorHandler)
               lib=syslib module=syslib
    Removed file C:\Program Files\sapinst_instdir\x.
    TRACE      2014-08-08 14:18:08.247 [iaxxclib.cpp:174]
               CLib::load()
    Opened C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864\iakdblib722.dll
    TRACE      2014-08-08 14:18:08.247
    SAPinst build information:
    abi version:   722
    make variant:  720_REL
    build:         1453085
    compile time:  Nov 28 2013 17:52:45
    make type:     optU
    codeline:      720-2_REL
    platform:      NTAMD64
    Exe directory: C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864
    regards
    Rakesh

    Dear Divya,
    please find the log details.
    TRACE      2014-08-08 14:17:59.293 [iaxxclib.cpp:174]
               CLib::load()
    Opened C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864\\sylib722.dll
    TRACE      2014-08-08 14:17:59.293
    exe dir is C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864
    TRACE      2014-08-08 14:17:59.512
    MessageLib initialized successfully.
    INFO       2014-08-08 14:17:59.527 [synxcpath.cpp:798]
               CSyPath::createFile() lib=syslib module=syslib
    Creating file C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864\dev_sap_kernel_test_08_Aug_2014_14_17_59.
    INFO       2014-08-08 14:17:59.527 [synxcfile.cpp:368]
               CSyFileImpl::removeEx(ISyFSErrorHandler * pErrorHandler)
               lib=syslib module=syslib
    Removed file C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864\dev_sap_kernel_test_08_Aug_2014_14_17_59.
    TRACE      2014-08-08 14:17:59.543 [syxxclogbook.cpp:211]
               PSyLogBook::initSAPKernelTracing(int traceLevel, const CSyPath & filePath)
               lib=syslib module=syslib
    Initialized SAP kernel tracing to file C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864\dev_sap_kernel
    TRACE      2014-08-08 14:17:59.543 [csicomponentsetmanager.cpp:111]
               CSiComponentSetManager::readFrameworkJslib()
    Reading framework jslib.
    TRACE      2014-08-08 14:18:00.981 [iaxxclib.cpp:174]
               CLib::load()
    Opened C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864\iaguieng722.dll
    TRACE      2014-08-08 14:18:00.981 [syxxclogbook.cpp:211]
               PSyLogBook::initSAPKernelTracing(int traceLevel, const CSyPath & filePath)
               lib=syslib module=syslib
    Initialized SAP kernel tracing to file dev_sap_kernel
    TRACE      2014-08-08 14:18:00.996
    Waiting for client connection (1)
    TRACE      2014-08-08 14:18:06.684 [synxcuser.cpp:2083]
               CSyUserImpl::isExistingOnOS() lib=syslib module=syslib
    existence check for user brtadm returned true.
    TRACE      2014-08-08 14:18:06.684 [syxxccache.cpp:419]
               CSyAccountCache::addToCache(const IaPtr<CSyAccountImpl> account)
               lib=syslib module=syslib
    inserted account (brtadm, S-1-5-21-575922271-569720141-4272231626-387102, USER) into the accountcache.
    TRACE      2014-08-08 14:18:06.684 [synxccuren.cpp:901]
               CSyCurrentProcessEnvironmentImpl::setEnvironmentVariable(const iastring & 'SAPINST_JRE_HOME', const iastring & 'C:/Users/brtadm/AppData/Local/Temp/2/sapinst_exe.3932.1407503864/jre')
               lib=syslib module=syslib
    Environment variable SAPINST_JRE_HOME set to value 'C:/Users/brtadm/AppData/Local/Temp/2/sapinst_exe.3932.1407503864/jre'.
    INFO       2014-08-08 14:18:07.716 [synxcpath.cpp:798]
               CSyPath::createFile() lib=syslib module=syslib
    Creating file C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864\dev_sap_kernel_test_08_Aug_2014_14_18_07.
    INFO       2014-08-08 14:18:07.716 [synxcfile.cpp:368]
               CSyFileImpl::removeEx(ISyFSErrorHandler * pErrorHandler)
               lib=syslib module=syslib
    Removed file C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864\dev_sap_kernel_test_08_Aug_2014_14_18_07.
    TRACE      2014-08-08 14:18:08.216
    exe dir is C:/Users/brtadm/AppData/Local/Temp/2/sapinst_exe.3932.1407503864
    INFO       2014-08-08 14:18:08.247 [synxcpath.cpp:798]
               CSyPath::createFile() lib=syslib module=syslib
    Creating file C:\Program Files\sapinst_instdir\x.
    INFO       2014-08-08 14:18:08.247 [synxcfile.cpp:368]
               CSyFileImpl::removeEx(ISyFSErrorHandler * pErrorHandler)
               lib=syslib module=syslib
    Removed file C:\Program Files\sapinst_instdir\x.
    TRACE      2014-08-08 14:18:08.247 [iaxxclib.cpp:174]
               CLib::load()
    Opened C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864\iakdblib722.dll
    TRACE      2014-08-08 14:18:08.247
    SAPinst build information:
    abi version:   722
    make variant:  720_REL
    build:         1453085
    compile time:  Nov 28 2013 17:52:45
    make type:     optU
    codeline:      720-2_REL
    platform:      NTAMD64
    Exe directory: C:\Users\brtadm\AppData\Local\Temp\2\sapinst_exe.3932.1407503864
    regards
    Rakesh

Maybe you are looking for