ALE inbox of BI is identical to the ALE outbox of the source system

Hi experts
We have BW 7 on ERP (ECC) 6. We have BW and ERP TOGETHER on the same developing system. BW is designed on developing client 100 (it is future productive client on the future productive system). It is of course default "myBI" source system. Upload is correct.
But because data is only inside clinet 200 (in the same system) I must create SAP source system client 200. It is correct, RFC destination is corect, source system clnt200 is correct and active.  But data I cannot upload from this source system clnt200 - IDOCs are not correct, BW monitor is yellow and message:
ALE inbox of BI is identical to the ALE outbox of the source system
Is mistake in situation "the same system - various clients and sourcesystems"? Do you have any experiences with BW on the same system with ERP 6 and client enviroment?
Thanks
Ales

Hi Ales,
The problem can often be caused due to missing authorizations with the background user used to receive the data in BW or
the background user in the source system that sends the data to BW. Please check the authorizations as per the note
150315 , sometimes SAP_ALL profile does not have the required authorizations so please check that the background users
have the profiles mentioned in the note 150315:
As per the note:
Reason and Prerequisites                                             
a) In the BW there exist two user:                                   
   i)  a human administrator, using S_RS_ALL                         
   ii) a user called BWREMOTE (or similar), used to receive the data 
       from the OLTP, using S_BI-WHM_RFC                             
b) In the OLTP there exist also two user:                            
   i)  a human administrator, needing authorizations to create users 
       and RFC-destinations.                                         
   ii) a user called ALEREMOTE (or similar), used to ...             
       1) ... connect the OLTP to the BW                             
       2) ... extract the data                                       
       3) ... send the data to the BW                                
       4) ... show monitoring dialogs                                
       for tasks 1 to 4, the profile S_BI-WX_RFC is used (however does
       not suffice on some points since some authorizations are      
       missing in the delivered profile)                             
       5) ... make customizing of OLTP extractors                    
       for this, additionally the authorizations to execute          
       IMG-functionality, to execute Transaction SBIW and            
       to maintain the applications, which shall be customized, must 
       be given during the customizing functionality is used.        
I hope that this helps.
Regards,
Des.

Similar Messages

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

  • R/3 connection to BIW - No Idocs arrived from the source system

    Question,
    Hi Team,
    I have issues during loading attribute data from R/3 source system to BI,
    I go to the path
    Data Warehousing Workbench - Modeling window. In the DataSources view, my application component Group ##. On my DataSource i Create Info Package and save it,
    Later I select the following options
    Full Update = select
    On the Processing tab page, select only PSA.
    On the Schedule tab page, choose Start Data Load Immediately and start the data load.
    Till here everything is in active version and saved, and connection to the source system is active and working fine.
    However when I do loading I received following messages, what I observed in Monitor window,
    Data was requested OK
    Request still running
    Diagnosis
    No errors found. The current process has probably not finished yet.
    System Response
    The ALE inbox of BI is identical to the ALE outbox of the source system
    or
    the maximum wait time for this request has not yet been exceeded
    or
    the background job has not yet finished in the source system.
    Current status
    No Idocs arrived from the source system.
    When I go to detail tab, under transfer section, I receive the following message
    Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n
    But when I actually go to PSA maintain section and select data and no of records, I can see the that data is loaded into PSA section,
    But when I chose to run the transformation I donu2019t get data here,
    Kindly help me to resolve this issue,
    Regards,
    BluSKy

    Hi,
    the BIW i am using , its compact BIW, which is in EXI, and i execute transaction /nrsa1 to go biw development workbench,
    i am not sure about transactions settings about r/3 side,
    could you plz throw some light on this issue,
    regards
    blusky

  • Restoring the source system connection in BW

    Hi all,
    I’ve been trying to upload data for 2 of my infocubes, and the extractions are bouncing. The message in R/3 is told me to check the connection. The RFC are fine.  But when I tried to restore the source system connection (RSA1 in BW), it sent me the following error messages:
    1.-  Basic type ZS 118 does not exist.
    2.-  The following error in the source system:
    3.-  Incorrect IDoc type ZSAB023 in the ALE definition of the source system.
    The description in each error is:
    Error #1:
    Diagnosis                                  
        IDoc type ZS 118 could not be found.   
    System response                            
    Procedure                                  
       Please enter an IDoc type that exists. 
    Error #3:
    Diagnosis                                                                  
        Incorrect IDoc type ZSAB023 in the ALE definition of the source system.                                                                               
    System response                                                            
        Error when sending data to BW.                                                                               
    Procedure                                                                  
        Enter IDoc type ZS 118 .                                               
    They told me this IDocs are created automatically by the connection. Is that true?
    How can I fix this, so that I can restore my connection and do the data extraction?
    Thanks a lot
    Regards,
    Vic

    Hi Victor Tostado
    1.- Basic type ZS 118 does not exist.
    Type Transaction WE30. Check iDoc types Obj. Name :  RSSEND -> press F7
    a.) Enter 'RSSEND' in the Obj. Name field.  You will see an entry similar to the one below:
              RSSEND                          Data transfer from the source system (template)
                    [-]  E1RSSH               Data transfer IDoc: Header information
                             [+]  E1RSHIE    Data transfer Idoc: Hierarchy header information
                                    E1RSTXT   Data transfer IDoc: Texts
         b.) Enter RSREQUST in the Obj. Name field.  You will see an entry similar to the one below:
                RSREQUST                    Data request to the source system
                     [-]  E1RSRH               Data request IDoc: Header segment
                             [+]  E1RSRHI     Data request IDoc: Hierarchy
                             [+]  E1RSRTX    Data request IDoc: Texts
                             [+]  E1RSRMD   Data request IDoc: Master data
                             [+]  E1RSRIS      Data request IDoc: InfoSource
         c.) Enter RSINFO in the Obj. Name field.  You will see an entry similar to the one below:
                RSINFO                         Info IDoc
                    [-]  E1RSHIN             InfoIDoc: Status segment
                            E1RSPIN            InfoIDoc: Data packet segment
                            E1RSEIN            InfoIDoc: Error segment
    d.) If any of the above do not exist, contact your BASIS Team.
    2.- The following error in the source system:
    Type Transaction SM59. Maintain RFC destinations
    a.)     Open the RFC Destinations. b.) Find your Source System and double click on it. c.) Technical setting should contain information regarding your source system d.) Logon Information should contain source system client and name & password for you remote logon.
    3.- Incorrect IDoc type ZSAB023 in the ALE definition of the source system
    Type Transaction WE21. iDoc Processing Ports.
    receivers port is not available go to WE21 -> create port
    a.) Select 'Ports' and then 'Transactional RFC'. b.) Click on the Port # for you source system. c.) Verify description & SAP R/3 versiond. RFC Destination should be one created in SM59. If non-existent then create one.
    I) Type Transaction SE16. Data browser (for R/3 -> BW Connections)
    Enter RSBASIDOC Print out copy of all entries in table.
    II) Type Transaction SM30. Msg Types & Assignment to iDocs
    Enter 'EDIMSG' in the Table/View field. Click on the 'Enter Conditions' option for Restrict Data Range. Click 'Maintain'. Select Message Type. Then enter 'RSSEND' in "From' field. Verify that the Basic Type matches what is in your RSBASIDOC table for each of your connections. If any are missing any entries you must create them as follows: Create another session and type Transaction WE30. Enter IDoc Type (ZSBAXXX) in Obj. Name field (Suggestion: Start new type with 'ZS' + Transfer Structure Prefix + (3)#'s) Select Create. Select "Create from Copy'. Enter 'RSSEND" in 'Copy From' field Enter Description (i.e. IDoc Type for BW Development) Execute (Green Check). Repeat for other missing entries.
    Regards
    Sangram Sutar

  • Error occured in the source system

    hi experts,
    can you plz how to resolve this error
    incorrect doc type ZSBB003 in the ALE defination of the source system.
    system response
    error when sending data to bi.

    Is the partner system profile incorrect? Please reconcile with table entries in RSBASIDOC. You can ask BASIS for assitance. Case A : Check RFCs via SM59. Configure IDoc settings via WE20 and WE21. If there's an issue with source system, restore & reactivate in RSA1 > Source System. SAP Note 325470 can also assit you for this method. Reference : http://goo.gl/t33d0

  • ALE Change Pointers in source system not active

    Hi All,
    I am trying to load 0COSTELMNT using deltas. The initial load is OK and then i use a delta and it fails and i get the error:
    "ALE Change Pointers in source system not active"
    I have carried out the following steps in an attempt to resolve the problem - but it didnt. Anyone have any advice??
    (1) Checked BD61 – to confirm whether the change pointers are active
    (2) Checked BDCP to confirm the number range is maintained
    (3) Checked SALE (Activate change pointers for message types)  to confirm whether the change pointer has been activated for the type we need:
    COCOKA     Control segment CO object/cost element
    COELEM     Cost element master data
    (4) In transaction snum, Selected number ranges and confirmed the intervals are setup
    No. 01
    FROM: 0000000001
    TO: 0000009999
    (5) Activate transfer structure
    (6) Replicate Datasources
    Thanks,

    If you are transferring master data from source system, the BD61 setting on the source system should be checked.
    Why it has been unchecked - not sure (likely someone did it by mistake).
    It shouldn't have any effect on txnl delta. What will be effected though is that you will have lost delta of the ALE based data sources for the period this setting was unchecked.

  • We would like to test old deltas from the source system( copied to new)

    Hi Gurus,
    The scenario is
    They will make a DB copy of the Prod system onto a QA system, the Copied system will have
    its system ID changed(SID) to a new one.
    There will be deltas available in the RSA7, as this is a copy of the  3 weeks old prod
    system. Now the delta's will be available on the Copied system pointing to the BW Prod system.
    We would like to test these delta's to BW Dev. why we would like to do the delta's to the
    BW dev system is to check whether we can do system copies without clearing the delta's on
    the source system.
    After the system copy we will do all the activities necessary to reflect the system changes
    a. Like BDLS, We20, we21,ALE checks, RFCDES, RSLOGSYSDEST, RSBASIDOC, etc on the source system to
    reflect the changes of the BW Prod system to BW Dev system.
    b. Likewise, we will perform all the above activities on the BW dev system by changing the
    existing source system to the new source system( performing BDLS,we0, we21, etc)to reflect
    the new Source system with the new (SID).
    c. We will check the source system connection
    d. Replicate the datasources on the new source system
    e. Activate the Transfer rules for the new source system.
    Now for us to do delta's from the new source system to the Bw dev system we need to change
    underlying tables in source system to point the delta's, arfc TID's etc to the BW dev system.
    We can change the entries in the TRFCQOUT, ARFCCSTATE, ARFCDATA tables to point the LUW's and
    destination to the BW dev system.
    What I presume is if we run the BDLS on the Copied system to change the BW prod system to BW
    and also  the underlying Tables for the LUW's and etc will still be pointing to BW Dev. I would
    like to know if this is the case .
    Lastly, appreciate if anyone can say if this is possible to do without having to clear the
    BW delta queue on the source system.

    Hi Ramesh,
    Appreciate a lot for your response, but i would like to know if we can reflect the entries in table RSSDLINIT(Last Valid Initializations to an OLTP Source) and RSSDLINITSEL(Last Valid Initializations to an OLTP Source)  in the BW system on the copied source system
    tables ROOSPRMSC(Control Parameter Per DataSource Channel), ROOSPRMSF(Control Parameter Per DataSource Channel) by executing the ABAP program RSSM_OLTP_INIT_DELTA_UPDATE after we do the BDLS conversion on the new copied source system.
    After the BDLS conversion I reckon the entries in the RSA7 queue, ARFCCSTATE, TRFCQOUT tables willl reflect the BW Development system instead of the BW Production system isnt it.
    response much appreciated.
    Kalyan

  • Changing the source system in QA

    Hello All,
    I just wanted a quick opinion from your experience on the following issue:
    We  have a ECC Dev client 20 connected to BI Dev client 20
    Similarly we have ECC QA 120 connected to BI QA 120
    But due to some reason we now want to connect a new ECC QA client 150 to BI QA 120 and take out ECC QA 120 totally(120 is wiped off).
    I already have a lot of development transported to BI QA where the source system is ECC 120. Now if 120 dies and we pull the data from 150, what are the pitfalls to watch for?
    Like all my Master data objects , DSO and Cubes still point to ECC QA client 120 but now the "actual" source system is going to be ECC QA 150.
    Points,
    Gaurav

    You need to replicate all the data sources in BI from QA 150 and change the source system assignment to 150 instead of 120.
    Also, you need to reinitilase delta for delta enabled extractors.
    Two  things to watch out:
    1.  If you dont have source system identifier,  then if you happen to get records with same key, then it will overwrite. This applies to both master and transaction data.
    2. For transaction data that is not delta enables, there may be a possibiltiy with which the records will get duplicated. So, better to delete the old requests before reload the data from QA150.
    Ravi Thothadri

  • Data Source Z*** is not defined in the source system

    Hello All,
    I am facing a well known problem extracting data from R3 to the BI side. On both sides I've got SAP ALL.
    I created data source on R3 DEV side, tested it and it extracts data. I've replicated metadata on BI side and activated the data source. The problem starts once I create the info package as no data is availble in PSA.
    I went to extractor checker and tried to start the extraction and I could see the message: data source Z**** not defined in the source system.
    I tried to locate the data source through RSA5 and I cannot see that it is availble there.
    Can you please help and advise where the problem is?

    Hi Neb,
    It can be related to many issues, one of them can be RFC connection issue. Please check the link below :-
    Datasource xxx is not defined in the source system
    It might give you some of ideas. Also if possible can you tell what Datasource are you having problem with.
    Regards
    Sunny

  • Error message from the source system

    Hi,
    I'm trying to load 0SD_O03 & 0SD_C03 using fullupload.
    I have data in source system which I checked in RSA3.
    I deleted the init request from the Infopackage.
    Diagnosis
    An error occurred in the source system.
    System response
    Caller 09 contains an error message.
    Further analysis:
    The error occurred in Service API .
    Refer to the error message.
    Procedure
    How you remove the error depends on the error message.
    Note
    If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
    Please help!
    Thanks,
    Vish

    I see a shortdump in BW system with runtime error
    MESSAGE_TYPE_X
    The current application program detected a situation which
    should not occur. Therefore, a termination with a short du
    triggered on purpose by the key word MESSAGE (type X).   
    Hi A.H.P,
    It didn't happen to other extractions. I just started with this one. I set up the table in SAP R/3 system and when I tried to do the initial full load in SAP BW, it comes up with the above error.
    Thanks,
    Vish

  • Error message from the source system, Caller 09 contains an error message.

    Hi,
        Guru's, i got an error massage when my process chain is running(Daily) in BIW 7.0, the error got in Data Loading from source to PSA or data targets. The errors having the below details
    Error message from the source system
    Diagnosis
    An error occurred in the source system.
    System Response
    Caller 09 contains an error message.
    Further analysis:
    The error occurred in Extractor .
    Refer to the error message.
    Procedure
    How you remove the error depends on the error message.
    Note
    If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.   "
    Can any body help me out of this situation what to do and how to resolv ethe problem.
    Thanks and Regards,.
    Taps....

    Caller 09 is a very common issue - please search the forums before posting....
    Arun

  • Error occurred in the source system

    Hi,
    I am receiving the below error while loading data from APO system
    Error message from the source system
    Diagnosis
    An error occurred in the source system.
    System response
    Caller 09 contains an error message.
    Further analysis:
    The error occurred in Extractor .
    Refer to the error message.
    Procedure
    How you remove the error depends on the error message.
    Note
    If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
    ******On further investigating the error message I get the following Diagnosis and Resolution details.*****
    Diagnosis
        The sequence for creating time series in LiveCache is:
        1.  Characteristic value combinations are created which in turn create
            planning object in the system
        2.  The combination of version, planning area, and planning object is
            initialized, creating time series  in LiveCache. This combination is
            so to speak the LiveCache anchor.
        This error occurs if
        o   New characteristic value combinatons have been created for the
            master palnning object structure that is assigned to the planning
            area, but the time series objects were not created.
    System response
         Processing cannot continue.
    Procedure
         There are two methods of creating time series objects for individual
         characteristic value combinations:
             a)  Re-initialize the version without deleting the time series
                 objects beforehand.
             b)  Execute the report program /SAPAPO/TS_LCM_PLOB_DELTA_SYNC.
         In general SAP recommend that when you generate new characteristic value
         combinations, you set the Create time series objects indicator.  This
         prevents this error from occurring.
    Please let me know what I need to do to rectify this error. Please send me the steps to overcome this error.
    Regards,
    Tyson

    Hi tyson,
    Has it run good before? if yes, try to restore the source system.
    by right click on the source system then choose restore.
    It will require you to fill in some information about RFC destination. contact with your basis to have the information about: Target host, Sys no, and Sys ID of your APO system.
    hope it help. Give point if you see its helpful.
    Chuong Hoang

Maybe you are looking for