Source System Activation Error

Hi,
We Upgraded BW3.1 to BI7.0, we did successfully on Development. but when in QA when I was trying to activate RFC by going to RSA1 and right click and activate it is showing errors like
Source system XXX300 is inactive     RSAR     5     
BI unknown in source system     RSAR     8     
BI IDoc type ZSBB025 is not the same as source system IDoc type     RSAR     371     
The following errors occurred in the source system:     RSAR     374     
EDI: Partner profile not available     E0     332     
Entry in inbound table not found     E0     414     
Entry in outbound table not found     E0     400     
Entry in outbound table not found     E0     400     
Am I missing anything ?
Thanks,
Chander

Hi
As a part of sanity check did you perform rituals as below -
Below deletes the BW-specific information in the source system that does not have a connection to the BW System.
1. Log on to the source system in question
2. Call Transaction SE37
3. Enter function module name 'RSAP_BIW_DISCONNECT'
4. Select the 'Sngl. test' function.
5. Enter the name of the BIW system for the import parameter 'I_BIW_LOGSYS' that matches the one prior to the new installation
6. Enter the name of the source system for the import parameter 'I_OLTP_LOGSYS'
7. Choose the function 'Execute'
and then
Transaction SE37 - function module RSAP_BIW_CONNECT - Single Test. Parameter:
                        I_LANGU        <language of the destination to BW>
                        I_SLOGSYS      <OLTP Source system (SLOGSYS from RSBASIDOC in BW)>
                        I_LOGSYS       <BW system (RLOGSYS from RSBASIDOC in BW)>
                        I_STEXT        <name of the OLTP system>
                        I_BASIC_IDOC   <BIDOCTYP from RSBASIDOC in BW>
                        I_SAPRL        <SAPREL from RSBASIDOC in BW>
                        I_RESTORE
                        I_TSPREFIX     <TSPREFIX from RSBASIDOC in BW>
                        I_PREFIXE <35 times second byte of TSPREFIX from RSBASIDOC in BW
                                       (Example TSPREFIX = 'BA', then
                                         I_PREFIXE = 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA')>
Hope it Helps
Chetan
@CP..

Similar Messages

  • Source system activate error

    Hi,
    I have created new source system for R/3 quality , when i am activating then getting following error. Kindly suggest how to resolve this error. Thanks in advance.
    BI unknown in source system     RSAR     8     
    BI IDoc type ZSDB018 is not the same as source system IDoc type     RSAR     371     
    EDI: Partner profile not available
    Entry in inbound table not found
    Entry in outbound table not found
    Rgrds
    Rakesh

    Hi,
    Check the source system RFC connection in SM59, if this is ok then check the tcode  WE20 for EDI partner profiles and inbound and out bound Idocs defined.
    In BW Out boud IDOC type should be same in ECC in bound Idoc type, and in ECC out Bound IDOC type should be same in BW in bound IDOC type then the source system activation is possible in RSA1.

  • Error in codepage mapping for source system. Error

    Hi BW Experts,
    I am facing following error:
    Error message: Error in codepage mapping for source system. Error text:
    Details: Inbound Processing ( 1000  Records ) : Errors occurred
                Error in codepage mapping for source system. Error text:
                Update PSA ( 0 Records posted ) : Missing messages
    I repeated the delta working and everything fine.
    Does anybody know why this error occurs?

    Run rsa13 (for bi 7.0) find your source system which one you are using for data transfer and double  click on it and find special options there select  the optioned i mentioned already.
    Please search SDN you can fin threads related to this thread
    if not let me know.
    Regards.

  • Error in codepage mapping for source system. Error text:

    guyz,
    im facing the below issue in prod.
    Error in codepage mapping for source system. Error text:
    Message no. RSDS_ACCESS013
    Collection in source system ended
    Error message during processing in BI
    Diagnosis
    An error occurred in BI while processing the data. The error is documented in an error message.
    System Response
    A caller 01, 02 or equal to or greater than 20 contains an error meesage.
    Further analysis:
    The error message(s) was (were) sent by:
    Inbound Processing
    Procedure
    Check the error message (pushbutton below the text).
    Select the message in the message dialog box, and look at the long text for further information.
    Follow the instructions in the message.
    need your guidance,
    cheerz,
    raps.
    Edited by: raps on Mar 1, 2012 9:39 AM

    Hi ,
    Kindly go throught the following threads for your issue resolution::
    Error in code page mapping for Source System
    Erroe in source system
    Regards,
    Arpit

  • Source system connection error

    Dear BW Experts,
    Now, i am in a critical situation,that the source system giving error in the quality system.So unable to extract data for testing.we have tried a lot getting any solution.
    But now planning to connect the sand box system to the bw quality system.
    The confusion is that if the sand box is connected to the bw quality system,then can i use all the developed objects(infocubes,ds objects,multi providers etc) which i had created before or design and activate all the objects again for the new source system.
    If any body attended this type of issues earlier,please suggest me how to proceed....
    Thanks & Regardas
    Debasish

    Hi,
    u can connect ur bw quality system to ur sand box.
    but u have to reimport all requests from Bw development to bw qualty.
    Imp. u have to delete Source conversion routine before importing request.
    Steps will be same like
    1. replicate data source.....
    2.....
    etc..
    /Sachinkumar.

  • Error in Source System Activation

    Hi
    When i am activating/restoring CRM Source System, i am getting following <b>Error</b>:
    The following errors occurred in the source system:     RSAR     374     
    Result of the destination check: Timeout     RSAR     375     
    There is also a <b>short dump</b>:
    Runtime Error          CALL_FUNCTION_REMOTE_ERROR                               
    Date and Time          27.09.2007 16:45:22                                                                               
    ShrtText                                                                       
         "Password logon no longer possible - too many failed attempts"                                                                               
    What happened?                                                                 
         Error in ABAP application program.                                                                               
    The current ABAP program "SAPLRSAC" had to be terminated because one of the
         statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                                                               
    The error occurred in an RFC call to another system.                       
         The target system has also written a short dump.                           
         Consult this short dump for more precise information about                 
         the cause of the error.                                                                               
    What could be the problem?
    Your suggestions are welcome....
    Regards
    Prasad

    Hi Srikanth,
    Thanks for the quick reply.
    RFC Connection Test is OK through SM59 in both the systems.
    Short Sump Analysis :
    Error analysis                                                     
        An error occurred when executing a REMOTE FUNCTION CALL.       
        It was logged under the name " "                               
        on the called page.                                            
    Regds
    Prasad

  • Souce system activation error

    Hello BW Experts,
    I am getting this error while trying to activate the source system in rsa1 > source systems > r/3 source system
    error msg:
    BW IDOC type ZSEA305 is not the same as the source system IDOC type ZSEA305 RSAR 371.
    Any suggestion appreciated.
    Thanks,
    BWer

    hi,
    have you try source system right click 'restore' ?
    take a look threads
    When I activate source system in BW, problem with IDoc (ZSBB027) occurs.
    BW idoc type not same as source system idoc type
    Active system source with IDoc type error

  • R/3 source system creation error(Idoc is missing)

    Hi expert's.
    i have created an r/3 source system in BI 7. but it's showing error when i am activating it.
    error as follows.
    1. Basic type ZSMA087 does not exist     EA     447     
    2. Incorrect IDoc type ZSDF085 in the ALE definition of the source system     RSAR     373     
    for the above error 1 i checked in the RSBASIDOC table. it showing the idoc type. when i am checked with the source system that is r/3 system in the partner profile for logical system. it's showing the incorrect idoc type in RSSEND outbound parameters for that logical system
    when i am changed that idoc type it's showing error as follows.
    "entry RSSEND zsma087 does not exit in edimsg.
    after that i checked with this table edimsg. for the rssend outbound option it's won't have the idoc type zsma087. table edit is also not possible on that.
    so please help me to solve the issue.
    regards
    Harikrishna N

    Hi Hari,
                    Are you using ECC6.0 system or Bw(bi7.0) & R/3 source system
    Regards,
    Vijay.

  • Error deleting source system with error message: "incorrect input for....."

    Hi,
    I'm trying to delete the source system using tcode RSA1 => Source systems => select the 'source system' and delete, but I got an error message as follows:
    "incorrect input for activating transported shadow IPacks"
    Fyi, I have opened up the client configuration (SCC4) prior to delete this source system but the source system still cannot be deleted and I receive the above error message.
    Please let me know what is the caused of the error and how to solve the problem.
    Thanks for your kind help.
    Regards,
    Mark

    Hi Mark,
    Which version of BW are you in?
    check this thread and also the note 709581
    Error Deleting Source system connection
    Thanks,
    Raj

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

  • RRI using Tcode in source system giving error

    Hi,
    I am trying to run a report in BW in tcode RSRT using RRI mechanism and the same is throwing an exception - An error occurred with the report to report interface during the jump. The same when run in BExAnalyzer throws an error "A critical error occured".
    The selections I have applied are as under:
    Target system -> Source System(ECC)
    Report Type -> Transaction
    Report Destination -> ME2L
    Assignments as under:
    0DOC_NUM -> EBELN
    Any trace to the cause of the error would be helpful.
    Thanks,
    Amogh

    Try creating a program in source whihc calls t-code ME2L and then from RRI try to call the program., and also check if you have authorization to t-code RSRR_WEB &RSBBS_WEB in you source system,
    If this did not help give us more detial on the error you are faceing.
    Shashi

  • 2LIS_02_HDR : Source System ID error

    Trying to upload from this datasource in 3.5 environment. I keep getting error while extracting, erroneous data in PSA.
    Source System ID not found, how do I fix this?
    Thanks in advance
    Fran

    Fran
    Go To RSA1>Tools>choose assignment of source system to source system ID-->assign ID. assign your source system ID to source system and save it
    You could find source system ID in your source system tab
    Hope this helps
    Thnaks
    Sat

  • Source System RFC Error in BI

    Hello SAP Experts,
    I have installed BI 7.0. And i have created an RFC connection for BI to R3. It was working fine but now the SAP R/3 source system in RSA1 is giving an error "Result of the destination check:Name or password in incorrect(repeat logon)". And also when i am logging in, moving between screens or T-codes, it is taking a long time and the status in the bottom of the screens shows that it is checking all the destinations that is the RFC connection created. Not able to trace the reason behind this. Please help. BL consultants are waiting to work.
    Thanks a lot
    Regards
    Vani

    Hello MLN,
    This is not the first time i am configuring SS. I have done it long back. I created a user manually long back and i used that user while configuring the SS. All these months it worked fine and no issues. As far as i know,ALEREMOTE and BWREMOTE are service users which we get by default after installation. And during configuration, i remember, i gave the passwords for both the users. But my question is, all these days it went fine and now it is giving an error. And why is it checking all the destinations when i execute any transaction. Please clarify. BI consultants practiced SPRO, so is there any chance that they might have changed or ececuted something and the result is this error? If so what can that be. Please suggest
    Thanks a lot
    Regards
    Vanitha

  • Source system Activation in BI

    Hello All
    I'm trying to activate Source System (RSA1) in BI System, I'm keep getting following ERROR.
    BI  unknown in source system
    BI IDoc type ZWAA003 is not the same as source system IDoc type
    The following errors occurred in the source system:
    Incorrect IDoc type ZWAS002 in the ALE definition of the source system
    Result of the destination check: Password logon no longer possible - too many faile d attempts
    when I tried to re-set the password for background user (AEREMOTE), but I'm still getting the SAME error.
    Thanks for your immediate help
    BI

    Hello,
    First try to restore ur source system from the right click option. If it fails....
    Check in WE20 of the source system whether proper idoc type are specified for the BI system.
    You can compare with any other working source system for the idocs name.
    Regards,
    Shashank
    Edited by: Shashank Dighe on Aug 13, 2009 9:13 PM

  • Source System creation error

    Hi..
    I cannot create R/3(productive) source system at BW (development)
    I checked password, cross-client and client specific are all changeble (t-code SCC4) and namespaces, sofeware are also modifiagle (t-code SE06) at R/3.
    At BW, RFC connection is Ok (SM59) and R3 side, RFC also connected w/o problem.
    But the error is still not resolved.
    What I have to do now..

    Hi Ravi..
    Error massage is...
    Massage No. RSAR502
    Diagnosis
    With Remote Function Call to system  error Screen output without connection to user.  ccurred.
    and runtime error massage is (ST22)
    DYNPRO_SEND_IN_BACKGROUND
    Rita

Maybe you are looking for