R/3 Source System Check in BW

Hi ,
We had a BW client Copy from Production to QA and DEV system. Last week, When I am trying to restore source system connection to R/3 after client copy by creating PORT and PARTNERPROFILES in BW system. I could restore connection in BW Dev but not in QA.When I tried to check the source system in RSA1 then I am getting an error that USER IS LOCKED. The remote logon test is going sucessful and when I replicate I could replicate every thing successful.  I checked the user(ALEREMOTE) in R/3 and the status of the user is not locked.
Thanks in Advance,
Varma.

Hi,
Did you check the ALEREMOTE in your BW QA?  The best to test out is to go into SM59 of both the system (BW and R3) and try the logon.
Hope this helps,
Cheers,
Gimmo

Similar Messages

  • Source system restore - Source system does not exist

    Hello friends,
    We have a problem. Now we have a new test system QA2. From BW system source system connection was configured for older test source system QA1.
    We needed to route this source system to new system. I tried with changing RFC of QA1 to QA2 details.
    Now, when i check RSA1 source system Check for QA1, i get this error :
    Port 'A000000103 ' of type 'ALE ' does not exist
    No destination exists to source system QA1
    I can see this source system in RSA1 in BW. However, in WE21 port is not available now.
    Please suggest.
    I do not have to lose transfer rules/PSA tables..etc.
    thanks
    ashish

    I get this when i try to restor connection :
    Source system does not exist
    Message no. RSAR175
    Diagnosis
    You have specified that you want to restore source system QA2. This source system is not known in BI.
    System Response
    The source system is not restored.
    Procedure
    Recreate the source system.
    If the source system should be known to BI, the name of source system QA2 may be incorrect. Rename the source system and try the function again.

  • How to change a source system

    Hello,
    we have just copied our BW productive system on the consolidation system. With this copy on the consolidation system now exist the source system to our productive R/3 system.
    I would like to connect the bw consolidation systen with the R/3 consolidation system.
    Does anybody now a possibility to switch the existing source system "R/3 productive" to "R/3 consolidation".
    All source system related objects (infopackages and so on) should be switched to the new source system too.
    Thanks
    Frank

    Hi,
    Roberto's answer is correct but it is making the assumption that all the DataSources in R/3 production are the same in R/3 QA.
    Once you have done the BDLS in BW for the source system technical name, you will have to do a source system check and restore. This will check the idoc and low level communication settings.
    As Roberto states, SAP note 325525 is the best source of information.
    Finally, you will have to deal with the data differences. Your data in R/3 QA will not be the same in R/3 PRD. This is a manual process.
    Cheers,
    Mike.

  • Transfer method 'TRFC with PSA' is not supported by the source system.

    Hi guys
    We are getting the following error when we try to open the transfer rules:
    Transfer method 'TRFC with PSA' is not supported by the source system.
    And when we run the load we are getting this error message:
    An RFC call-up triggered the exception
    Our source system check is ok. RFC test is ok from both sides.
    Please advice what else can be the solution.
    Edited by: sam on Nov 6, 2008 4:51 PM

    Did you do Right click on Source system and 'Check' option in RSA1-> Source Systems?
    Is this problem after upgrade or something like that?
    -Abhijit

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

  • Source systems

    Hi
    I'm a bit confused, I need to load some data from R/3 to bw, using business content. I think my data are in R/3 but why when I call, in bw, show data flow, my cube is linked to other systems (I_EXTERN, My IDES BW system etc.)
    I have to change those links?
    what is I_extern?
    thanks to all
    Michele

    Hi Michele,
    whwn you install the business content, you can push a little button (Shift+F7) called Source System Assignement...here you can check which source system you want to assign by default when you activate business content object (that is the infosources).
    In your situation, your infosource are linked to these source systems (check them in the page Source systems in RSA1 (Modeling), but try to check your default entries in business content installation settings.
    Now, if you want to assign your infosource to the R/3 you have to right click on the infosource and assign the source system you need...If you need more information, write me (and don't forget to assign some star points to the contributors that help you !!!)
    Hope this helps.
    Bye,
    Roberto

  • Source system R33CLNT100 is marked as inactive in BI.

    Dear Experts
    When I do a source system check via RSA1 > Source systems > SAP folder > right-click the R/3 system ID and select Check function,
    the system throws as error as shown :
    "Source system R33CLNT100 is marked as inactive in BI."
    "Procedure
        If you have upgraded to BW 2.0, activate the source system.
        With other errors connected to this source system, choose Restore   the
        source system from the source system tree in the Data Warehousing
        Workbench. This regenerates the source system, merges the relevant
        communication parameters, and replicates the DataSources in BI.
    and
    "BI IDoc type ZZZZ011 is not the same as source system IDoc type ZSSS021     RSAR     371     
    There was a system Refresh from Production R/3 46C to QA system R/3 46C.
    We did the BDLS but the IDOC seems to have got overwritten by R/3 Production's, obviously , due to refresh.
    Any idea how to resolve this?
    It seems like I need to re-create manually the idoc but I am not expert in this area.
    I do know there are standard IDOC aspects for BI 7.
    But how to re-create the relevant IDOC settings or configurations ? Need to do this in both  BI and R/3 ?
    Best regards
    Pascal

    Hi pascal ,
    Seems to be connectivity between the source system and the Bi system it will be restore by basis team only. Couple of tings that you can do at your end will make their work at ease
    i) check the RFC connection between the Source system and the Bi system in Sm59.
    ii)Make sure the user ALERMOTE and SAPCPIC are unlock in ecc side
    Now for configuring the source system by urself follow the below points :
    1. In BW, call TA RSA1.
    2. In the left hand column, choose "Source systems".
    3. In the column Source systems, right click on the respective source system and choose "Restore".
    4. A popup "Create R/3 source system" appears. Enter the passwords for user SAPCPIC. Hit enter.
    5. A popup "Please log on as an administrator in the following screen." appears. Hit enter.
    6. A logon screen of the child system appears. Enter your user and password and hit enter.
    7. A popup "New source system connection" appears. Hit "Continue".
    8. A popup "Check RFC destination" appears. Hit "Check".
    9. The child system jumps into TA59, displaying the RFC destination pointing to the BW system. Check it by pressing "Remote logon" (nothing happens, i.e. no error message appears!) and "Test connection" (the connection test table will be displayed). Hit F3 twice. The system jumps back.
    10. The popup "Check RFC destination" appears again. Now hit "Use".
    11. A popup "Connection can not be used" appears. Hit "Delete".
    12. A popup "Please log on as an administrator in the following screen." appears. Hit enter.
    13. A logon screen of the child system appears. Enter your user and password and hit enter.
    14. A popup "New source system connection" appears. Hit "Continue".
    15. A popup "Check RFC destination" appears. Hit "Check".
    16. The child system jumps into TA59, displaying the RFC destination pointing to the BW system. Check it by pressing "Remote logon" (nothing happens, i.e. no error message appears!) and "Test connection" (the connection test table will be displayed). Hit F3 twice. The system jumps back.
    17. The popup "Check RFC destination" appears again. Now hit "Use".
    18. A popup "Replicate Metadata?" appears. Hit "Only Activate".
    19. If popup "Do you want to reactivate all transfer structures and DataSources?" appears. Hit "No". If "Display activation log" popup appears - press "No" (that message may appear several times).
    20. Press "Back" if "Analyze application logs" screen appears
    Source -->http://forums.sdn.sap.com/thread.jspa?threadID=1892011
    Thanks,
    Deepak

  • Source System Problem after system refresh in RSA1 trx

    Hi,
    We have R/3 4.7 Test source system created in our SCM 2007 Test System. The source system check was OK.
    The R3 Test system was refreshed with Production data few days back and now my source system is not working. When i perform Source System check it says:
    BI unknown in source system
    BI IDoc type ZSSB006 is not the same as source system IDoc type
    I performed following steps in R3 Test system after its system refresh:
    1. Created logcal system and created RFC.
    2. Created port in trx we21.
    3. Created partner profile in trx we20.
    4. For the outbound parameter RSSEND, I had to create idoc type that should be same as in my SCM system i.e. ZSSB006.
    5. Created idoc type using trx we30 as a copy of RSSEND and added entry in table EDIMSG. Now, i could also create outbound parameter RSSEND with idoc type ZSSB006.
    After performing the above steps i also replicated the datasources for the R3 Test source system, but its still showing above error.
    I also checked the RSBASIDOC table in SCM test system. It has correct entry for my source system. But there is no such entry in RSBASIDOC table in the R3 test system.
    Someone pls help me.
    Regards,
    Chintan

    Hi
           Need to restore the All Dalaload connection settings after refresh the system which either R/3 or SCM.
    RSA1 -> select the Source system -> Right click -> Restore , It'll ask the connecon paramters like RFC , method of activations. Then check the connection test of the Source system .
    Check the the note for further  info...
    Note 886102 - System Landscape Copy for SAP BW and NW BI
    Hope halp you...
    Regards,
    Sureshram

  • Source System Problem after System Refresh

    Hi,
    We have R/3 4.7 Test source system created in our SCM 2007 Test System. The source system check was OK.
    The R3 Test system was refreshed with Production data few days back and now my source system is not working. When i perform Source System check it says:
    BI unknown in source system
    BI IDoc type ZSSB006 is not the same as source system IDoc type
    I performed following steps in R3 Test system after its system refresh:
    1. Created logcal system and created RFC.
    2. Created port in trx we21.
    3. Created partner profile in trx we20.
    4. For the outbound parameter RSSEND, I had to create idoc type that should be same as in my SCM system i.e. ZSSB006.
    5. Created idoc type using trx we30 as a copy of RSSEND and added entry in table EDIMSG. Now, i could also create outbound parameter RSSEND with idoc type ZSSB006.
    After performing the above steps i also replicated the datasources for the R3 Test source system, but its still showing above error.
    I also checked the RSBASIDOC table in SCM test system. It has correct entry for my source system. But there is no such entry in RSBASIDOC table in the R3 test system.
    Someone pls help me.
    Regards,
    Chintan

    Hi Chintan,
    Can you please check IDOC in your Target system. It should be the same type. Better you do the Partner profile steps.
    Also please check have correctly created the idoc in Inbound or Outbound.
    Consider the case like if its exist in BW as Out bound then its connected to Inbound IDOC of R/3 and vice a versa.
    Please elaborate your refresh activites. Normally IDOC setting never get changed in you refresh activites.
    Just check your BW system patch level and search for Notes.
    Regards,
    Mahesh

  • Source system conversion doesn't work after transport

    Just transported a query to BW Production and found that the source system is still the same as in DEV.
    The conversion is there (QAS-->PRD). But the conversion doesn't seem working in the transport.
    Can anyone tell me how to troubleshoot this issue?

    Hi,
    Please check the following:----
    1. RSA1->Source Systems --> Select the source system -->Check. It should take you to the correct source system with a Remote logon.
    2. Check the logical system mappings in RSLOGSYSMAP table.
    3. http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/70a7b233-8be5-2c10-4190-aed723af5373
    Regards,
    Suman

  • Generation Log for  Trasfer Structure on Source System

    Hey Folks, I'm reciving a weird message at the moment of activate the transfer rules, something like:
    Error when creating transfer structure /BIC/CCGO0CO_PC_01 in source system XXXX,An error occurred when creating transfer structure /BIC/CCGO0CO_PC_01 as an IDoc segment in source system XXXX  Meesage Number : R3104
    Could someone explain where on the source system Side can I check the generation log for this?
    Thanks a lot

    Hi William,
              The problem may be because of some error in connection with Source System . Check all entries in table  T000. Note them up in field RLOGSYS and  check with RSBASIDOC with fields Rlogsys and Slogsys .
    U can see the Source System assignment and IDoc type is the table RSBASIDOC .
    Check the field RlOGSYS in the table.The possible cause of error is caused because of renaming the Source System
    Check with the assignment in Sourcesystems of BW .
    also Check with Transaction RS_LOGSYS_CHECK in R/3 .
    U can have more information in the OSS Notes : 140276
    Hope it helps.
    Thanks,
    krish
    *Awarding points is a way of saying thanks in SDN
    Message was edited by: krishna V

  • Error in source system T90CLNT090

    HI gurus,
    I am using Bw 3.1c and 4.7 r/3 working with Buss content trying with generic data i have filled the all the parameters , simultaniously i created info source in Bw Cid with Char and size 4, and attribute name and address with char size 15&20  exactly with the same char i craeted in Generic too,
    replicated too
    but the problem is when i want to assign infosouce, to datasource in the transfer rules screen while mapping i am getting this error.
    infact this error is happening with me while doing logistics also
    mail me [email protected]
    points will be assinged for useful
    regards
    john

    Pl Activtated in Soure sytem ..
    Step to follow
    Login to Bw sytem and Enter T-Code RSA13.
    1. Right Click on Soure Sytem and Replicated the soure Sytem (T90CLNT090).
    2. Click Active button
    3.Click the Check button
    4. check in Status  bottom  ( Make Sure the Status should be green ).
    <i>OtherWise</i>
    Please Check sm59 in BW system and Also check in R/3 side also in Soure System T90CLNT090.Plz Make sure you have the proper connection with the source system.
    Check in RSA1-source system- right click on your source system- check ,it should be ok.
    Message was edited by:
            Jayendra kumar DT

  • How to check data records in R/3 (source system)

    Hello,
    I need to check the data records in R/3 (source system). Is Transaction RSA3 the only option or is there another way. When I use RSA3, all I see is the sandbox and cursor. Nothing seems to happen.
    Pls help.
    SD

    Hi Sebastian,
    To some extent this works out i.e Comparision of Tables in R/3 Vs ODS at BIW.
    Tables in R/3 like VBAK(Order),VBRK(Billing),MKPF(inventory Management) and LIKP(Delivery)
    compare them with the respective Datasource/PSA/ODS
    2LIS_11_VAITM
    2LIS_12_VCITM
    2LIS_13_VDHDR      
    2LIS_03_BF
    in the BIW.
    The Total numbers of Document Numbers ,Quantity or Value should match !!!!!!!!
    Hope it helps !!
    Rgds
    SVU123
    Edited by: svu123 on Mar 3, 2009 1:16 PM

  • Error RSAR 371 when checking source system in BI

    This was mentioned in 1 forum but not really answered to my understanding.
    Message - BI IDOC type ZSBB003 not the same as source system IDOC type ZSBC005
    RSAR 371
    This is when checking a source system from BI 7.0 to ECC 6.0 after a refresh and running BDLS with many patches.
    thanks

    Hi Bradley,
    I believe you have to run BDLS using option 1 - Conversion of Client Dependent and Client-Independent Tables. This is to ensure that you have a correct conversion to a new logical system.
    You can refer to these notes too:
    886102, 184754, 325470
    These notes help but rather confusing to read it at first. Hope this helps.
    Regards,
    Andrew

  • Check on source system failing

    My info package is failing
    When i check the connection with my source system it says
    "Result of the destination check:Password logon no longer possible -  too many failed attempts"
    How can this be fixed??

    Hi,
    This problem comes whenever the background user password changes or resets, so contact Ur basis Team for restoring the connection
    The password for ALEREMOTE has been locked
    Try to Schedule Info Package once the password has been reset. It will be successful.
    T.codes : SM59 Source system Connection
                  RSCUSTV*                   * 1,2,3,4,5,6,7  Back ground user ID Setup
    Regards
    Hari

Maybe you are looking for