Idoc Type Mismatch in Source & BW Systems

Hi Friends
My problem goes as follows
I have BW development system and R/3 Development systems.Both this comination was working fine.Suddenly we had system copy of R/3 Production on R/3 Development for some testing.Now BW source system turns inactive.When i try to activate its gives following message.
'BW Idoc Type A is not equal to source system Idoc Type B'.
So using transaction WE30 i mainatined Idoc Type A in source system.But still it gives same error on activation of source system.I am stuck up here
Would u people plz help me with this urgently.Waiting for ur response.
Raghu

See the below link
BW idoc type not same as source system idoc type
After this try to restore the connection
Regs
Gopi
Assign points if it helps ...

Similar Messages

  • Copy IDOC Type to another SAP System

    Hi Team,
    We want to copy a basic IDOC type WGSREQ02 from our ECC system to the BI system. The intent is to use this IDOC as an outbound from the BI system and then recieve it in the ECC system. Since we want to use it only as an outbound, we don't really need any application logic in BI. We just need the IDOC structure and the outbound capabilities so that we can use the application logic provided by default in ECC.
    Please let me know if there is a way to copy the IDOC Definition from ECC to BI system.
    Thanks
    Sanjay

    Hello Sanjay
    I would use the following approach:
    (1) Generate XML structure (XSD schema) from the IDoc type (on the ERP or via SAP-XI)
    (2) On the BI system fill the empty XML with the data and make the transformation
        back to IDoc structure (EDIDC and EDIDD)
    But how to send these IDoc data via ALE? You need to define the IDoc type (which does not exist on your BI system) as outbound parameter of the partner profile (e.g. ERP as logical system).
    Perhaps you can send the IDoc data using fm MASTER_IDOC_DISTRIBUTE.
    Regards
      Uwe

  • How to garantee IDOC types are the same on two communicating sap systems.

    Hi all:
        how to garantee IDOC types are the same on two communicating sap systems,  including segments and versions, using bd64?
        what's more, what bd64 using for besides generating parter profiles,  must we use bd64 for outbound idocs?
        Thank you very much
    best regards ?

    Hi jingying Sony 
    You can compare the Idoc type and Version between Sender System and Reciver System.
    Use TCode SCMP and Compare the Table EDIMSG in Both System.
    This will solve your issue.
    Thanks
    Ramesh

  • IDOC type not in EDIMSG

    Hi all,
    I want to configure the IDOC type BLAORD in our SRM system. The problem is it's not in the table EDIMSG. There is a message type BLAORD but its IDOC type is bot BLAORD03, instead the name of the IDOC type is XEUST01. How can I add the IDOC type so I can use it for my change pointers, RBDMIDOC? I'm trying to transfer RFQ details from SRM to XI.

    not an XI problem. Ask a business process expert.

  • Error Number 13 Type Mismatch VBScript runtime error

    I am getting the following error when administering web forms in HFM v 11.1.2.1.600.07
    Error Number:13
    Error Description:Type mismatch
    Error Source:Microsoft VBScript runtime error
    Page On which Error Occurred:/hfm/data/WebFormBuilder.asp
    Google searches led me to suggestions that this might be a problem with errors in my Member Lists, but I have checked and re-checked this.  The Member list loads without errors and does not resolve the issue.
    Fortunately the problem is only present in my DEV environment.  The error specifically occurs when you click the Rows or Columns tab in the web form editor.  All other tabs work fine.
    At the same time all web forms are also returning the following error on submit:
    An unknown error has occurred in the HsvWebFormGeneratorACM object.
    Error Reference Number: {FE2DBEB4-89E2-4177-A585-474BDAF18CB7};User Name: vincent@Native Directory
    Num: 0x80040d40;Type: 1;DTime: 23/03/2015 14:09:20;Svr: HYPAPPDEV;File: CHsvWebFormGeneratorACM.cpp;Line: 1122;Ver: 11.1.2.1.000.3082;
    Num: 0x80040d40;Type: 0;DTime: 23/03/2015 14:09:20;Svr: HYPAPPDEV;File: CHsvWebFormGeneratorACM.cpp;Line: 914;Ver: 11.1.2.1.000.3082;
    Num: 0x80040d40;Type: 0;DTime: 23/03/2015 14:09:16;Svr: HYPFNDDEV;File: CHsvWebFormsACV.cpp;Line: 711;Ver: 11.1.2.1.600.3779;
    My normal support options have been voided because I recently installed Microsoft Web Platform 5.0 on the server not knowing it might affect HFM and I am unable to verify whether this issue arose before or after this installation as I hadn't used the DEV environment in a while.
    Uninstalling MS Web Platform and rolling back the IIS settings has failed to resolve the  problem.
    I have the option to restore the environment, but the SQL box hosts 2 DBs used in our PROD environment so I am trying to avoid this.
    Can anyone suggest anything, be it an HFM-oriented or related to undoing changes caused by the installation of the Web Platform?
    Thanks!

    The root cause of the above error is a faulty Data form/Data Grid design which anyone try to run with particular POV. This issue can come up when you have row with Scalc or with NoSuppress option and you have also selected in the data form design the option to Suppress the row with Nodata/Invalid/Zero. This can be conflicting/ambiguous when user selects a POV for which the data form comes up with Nodata/Zero/Invalid rows and hence throws the above error.

  • Idoc type extension

    Hi Experts ,
    I have created an extesnion for standrad message type DEBMAS  and Idoc type DEBMAS05 . In devlopment system it is working fine . when transported to other system  it is not working and after analsys it is found that EDISYN table has differnt values for differnt systems .Please let me know how can solve this , is any customization need to be mainatined or how it can be done .
    Regards
    Arun .

    Hi,
    You have to transport the idoc Extension object to fix this issue. It is not related to customization and it is more of IDOC development related. Try to find out the request under which the idoc extn is saved and retransport the request or include the extn related objects into new request and move it to target system. This should solve your problem.
    Cheers,
    Prasanna

  • RSAR2318 : IDoc type for source system T90CLNT090 is not available

    Hi all,
    I am working on BI + ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
    1. Error:
    R7I028
    Object could not be activated
    2. Error:
    RSAR238
    IDoc type for source system T90CLNT090 is not available
    Error when creating the export datasource and dependent objects
    Error RSAR238 : IDoc type for source system T90CLNT090 is not available
    I have already checked trx & dtps, but could not find resolution.
    Kindly help me with this error.
    Thanks and regards,
    MS

    M Sharma wrote:
    But how exactly can I create when T90CLNT is not active? Help please.
    Yes, you would need to check with BASIS team how they have created an alternate source system (for debugging) & prepare a RFC b/n these systems. Can you just check the settings in the source system and BI source system...and check the source system for the same BI system. Right click > Check and then do a restore or take the help of basis to fix it. What I think is a possible solution is : RSA1 > Source system > Search System > Right Click > Activate

  • RSAR238 : IDoc type for source system T90CLNT090 is not available

    Hi all,
    I am working on ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
    1. Error:
    R7I028
    Object could not be activated
    2. Error:
    RSAR238
    IDoc type for source system T90CLNT090 is not available
    Error when creating the export datasource and dependent objects
    Kindly help me with this error.
    Thanks and regards,
    Dhanapal

    Hi,
    Check the same in SDN..
    Object ZDUMMY could not be activatedMessage no. R7I028
    Re: DSO Activation problem
    http://sap.ittoolbox.com/groups/technical-functional/sap-bw/test-cases-for-module-human-capital-management-1425016
    http://sap.ittoolbox.com/groups/technical-functional/sap-bw/idoc-type-for-source-system-t90clnt090-is-not-available-message-no-rsar238-1431565
    Thanks
    Reddy

  • Source System Activation - IDOC Type does not exist

    I'm doing a new installation of BI7 and when I want to activate the source system on  replicate Metadata Box and select "Only Activate" it comes up with error stating :Basic Type ZSxxxxx does not exist
    When I look in SE16 on table RSBASIDOC I can see the IDOC Type exist on both BW and R/3 Systems
    Any solution?

    Check my reply
    Re: "Basic Type Does Not Exist"

  • BI Idoc Type IS NOT THE SAME AS SOURCE SYSTEM IDOC TYPE

    Hi all,
    how can we solve the IDoc miss match in source system (ECC6).
    Error :
    BI Idoc Type ZSTC029 IS NOT THE SAME AS SOURCE SYSTEM IDOC TYPE ZSTC031
    please provide me solutions..
    Thanks in advance,
    Venkatesh

    Hi Venkatesh,
    Check here.........
    BW idoc type not same as source system idoc type
    Thanks,
    Vijay.

  • Incorrect IDoc type ZSWA003 in the ALE defintion of the source system.

    Hi !
    When I triggering the load from BW it is giving me an error Incorrect IDoc type ZSWA003 in the ALE defintion of the source system.
    When I am checking the connection in source system with R3 system , it is giving me this error and asked me to Enter IDoc type ZSWA011 .
    Please tell me how to do this.

    Hi,
    I assume that the source system has been copied fom production onto quality-system (or somothin likely).
    To solve that, plase refer to the oss-note 886102.
    https://websmp130.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=886102
    https://service.sap.com/sap/support/notes/886102
    Hope that helps.
    cheers
    Sven
    Edited by: Sven Muntermann on Mar 26, 2009 6:21 PM

  • Incorrect IDoc type ZSBB010 in the ALE defintion of the source system.

    Hi,
    We have done client copy of BW production system into BW test system.
    I am getting following error while checking Test R/3 system in BW Administrator workbench.
    Diagnosis
    Incorrect IDoc type ZSBB010 in the ALE defintion of the source system.
    System response
    Error when sending data to BW.
    Procedure
    Enter IDoc type ZSBB017 .
    Ring any bell.. Thank you for Ur time..
    Cheers
    Senthil

    Hello Senthil,
    Please check WE20 transaction and look for idoc type there.Most likely you need to make some corrections in there.  Also check BD64.
    Regards.
    Ruchit.

  • Incorrect Idoc type ZSPA065 in the ALE definition of the source system RSAR

    Hi Experts,
    Incorrect Idoc type ZSPA065 in the ALE definition of the source system RSAR 373 error is coming .
    Some one suggested note no 886102  but i went inside i did not find correction or code for implementing please any body suggeste for rectifying this error.
    Please tell correct aproach for solving the issue.

    Hi,
    there is some problem with your RFC connection
    just go to WE20 T code and expand partner type LS
    here search your r/3 system and click on that here you can find the details of idoc
    if you are not able to correct yourself you can contact basis team for that.
    just go to RSA1--> using the conxt menu doa check of Source system you will get the error message
    just send the screen shot of the same to Basis team they will take care of the same.
    Br
    santosh

  • Incorrect IDoc type ZSBC052 in the ALE definition of the source system

    hi guyz,
    i am getting the following error while checking the source system in bi.
    Incorrect IDoc type ZSBC052 in the ALE definition of the source system     RSAR     373     
    please guide through your expertise.
    regards,
    raps.

    Hi,
    Check the below given thread,
    [Source System Check Problem;
    [Incorrect Idoc type ZSPA065 in the ALE definition of the source system RSAR;
    Regards,
    Durgesh.

  • Incorrect Idoc Type in ALE Definition of Source System

    hi,
    I have defined a R/3 Source System in BW client. This source system points to another R/3 Server in our system landscape. When I right click on the source system and click on the "check" option, getting the following error - "Incorrect Idoc type ZSKB013 in the ALE definition of the source system".
    Where can I change this setting and will this be done on BW side or R/3?
    regards,
    SK

    Hi,
    there is some problem with your RFC connection
    just go to WE20 T code and expand partner type LS
    here search your r/3 system and click on that here you can find the details of idoc
    if you are not able to correct yourself you can contact basis team for that.
    just go to RSA1--> using the conxt menu doa check of Source system you will get the error message
    just send the screen shot of the same to Basis team they will take care of the same.
    Br
    santosh

Maybe you are looking for