Re-connect sorce system in RSA1

Dear BW experts
re-connect sorce system that existent in bw and don't existent in the
sorce system.
I try to re-connect ECC system to BW by the function RSAP_BIW_CONNECT
and when I try to execute the function I get NO_TSPREFIX_DEFIEND
Entry TSPREFIX for table RSBASIDOC could not be created.
I look at the table RSBASIDOC and I see that the TSPREFIX is already in
the table to another system.
If I do restore connection to the system
I get a message that said:
The connection BC is used in the LOGTST400 source system as a connection LOGDEV100 USED.
do you want to delete this connecrion in the source system?
the connection is restored after it has been deleted successfully
and I don't want to delete the LOGDEV100 connection.
there is a way to change the TSPREFIX in RSBASIDOC table?
Thanks
Royi Denis

solution found:
config needs to be opened on source system ,if not, a popup tries to tell you that config needs to be opened, but it cannot because the frontend is not active on this connection.

Similar Messages

  • How to Check source systems in RSA1 and verify that connections are working

    How to Check source systems in RSA1 and verify that connections are working ok and how to Check Planning Area have green status.................

    Hi,
    In rsa1, go to 'Tools' and option 'Manage Source System' - the screens are self explanatory there after. To check the planning areas, go to transaction /SAPAPO/MSDP_ADMIN anc check the status of the relevant planning areas.
    Regards
    Vinod

  • RSA1 - Source system connection : No connection to system  possible

    Hello friends,
    I am creating a Source system connection from our BW system. I have already established the working RFC connection to source system which works fine, both side client is open & system is modifiable.
    Bit i am getting error : No connection to system  possible
    No connection to system  possible
    Message no. RSAR501
    Diagnosis
    Logical system  cannot be accessed.
    System Response
    Error during the retrieval of the logon data store d in secure storage
    Procedure
    Use transaction SM59 (for BAPI and SAP source systems) or DBCO (for database source systems) to check the RFC parameters of source system . Also check whether the system can be accessed in the network and whether the necessary application and system programs have been started.
    I have already implemented SAP note 1276270 - RSAR 501 for source system restore due to router string /H/ without success.
    thanks
    ashish

    Error during the retrieval of the logon data store d in secure storage
    Have you tested the remote login also ?
    Regards,
    Subhash

  • SAP Source System showing up as BI Source System in RSA1

    I have 2 BW systems and 2 CRM Systems.  In one BW system, when I create a SAP Source system in RSA1, It gets listed as a SAP Sources system along with ECC and all the rest.
    The Logicial Systems and RFC Connections all appear to be the same between each pair.
    In the other system, using identical procedure, it the source system gets listed as a BI Source System.  The 2 CRM systems have identical components and version levels as do the 2 BW systems.
    Any idea why and if this would make any difference and how to correct.

    Hi,
    To fix this, you need to do a restore (& not a delete) of the source system in BW, having deleted the RSBASIDOC entry in the source OLTP system.
    This will force the BW system to interrogate the RSBASIDOC table entry in the source system again and it should then realise that it is an R/3 system (not a BW system) and move the entry to the SAP folder.
    Rgds,
    Colum

  • Unable to Create Source system in RSA1

    I have installed a BI Server(Netweaver 2004s). When i try to add source system in RSA1, it gives an error "No entry for BW_USER in table RSADMIN available"
    Let me tell what all i tried.
    1) i clicked on settings>global settings- it gives a blank page. when i switch it to change mode, there is a button called "Position" and then "Entry1 of 2". I cant enter any value there and when i click on "Position" button, it says "Table RSADMINAV has no relevant fields"
    2) In se16 tried to maintain RSADMINA table and for BW User field, i gave BW_USER, but there is no "execute" Button. all i see is "Reset" button. i tried pressing F8 key, it wont do anything. I clicked on save but it says "the entry is already exist"
    Regarding RFC - i created a user BW_USER in ERP Sytem and ERP_USER in BI server and both the user type are System user.
    From both the server i tried to do Connection test and i am not getting any error. but if i try clicking Remote Connection, it wont connect and wont do anything and no Errors.
    Please help me Resolving this Issue, Since it became a very critical issue.

    Hi,
    Can you check  if there is any other user ID specified in "BW user for ALE".
    To check, Go to transaction RSA1 --> Settings --> Global Settings.
    If you find a different user id there, then specify the correct BW user id there.
    Please refer to OSS Note 410952 for details.
    Hope this solves your problem!!
    Regards,
    Raj.
    Edited by: Raj on Aug 14, 2009 8:15 PM
    Edited by: Raj on Aug 14, 2009 8:16 PM

  • DB connect source system creation in BI

    Hi,
    I would like to create a DB connect source system to an external MSSQL 2005 database in RSA1.
    The external MSSQL 2005 database is setup using Windows Authentication mode.
    Question: Which user actually should I specify when creating the source system in RSA1? or which user should I assign the db_ddladmin role in the external MSSQL database?
    Many thanks,
    YJ.

    Hi,
    Please note the following with regard to the user:
    To avoid problems loading data, proceed as follows:                   
    1. Create a special login for the extraction. You should add this login to the db_ddladmin database role in the 
    corresponding database. This generates a similar DB user at database level. The user you use must have the 'CREATE VIEW'
    authorization at least.  This is contained in the role mentioned above.
    2. For the extraction, you should only use DB views that were  created under this DB user. (refer also to type conversion, naming       
    convention and so on)                                                    
    3. Assign the necessary authorizations (SELECT at least) to the  selected user in the source tables, or the columns of these tables.      
    4. Use the specially created login in the logon information when you set up the DB source system in BW.   
    You will find much more detailed information on how to setup the connection and known problems and issues in the
    attached note 512739.
    Best Regards,
    Des.

  • Issue in while connecting Source system

    Hi All,
    I mistakenly Ran the function module RSAP_BIW_DISCONNECT in BIW, I suppose to run this FM in Source system side,
    We observed that Source system in RSA1 (BI) has been deleted), and also one record from the table RSBASIDOC (which is from source connection) has been deleted .
    When I try to create he source system in BI, after entering logical system and ALEREMOTE and BWUSER logins, it was asking me to login to source system, after entering the details,
    A pop-up message:
    RFC destination already exists in source system
    Do you want to use this destination, check, or
    cancel source system connection?
    options: USE, CHECK and Cancel, -> We pressed USE
    Then it came back to RSA1 screen and a pop-up message
    Connection BA is used in the ERQXXXX
    source system as a connection BWQXXXX to BW.
    Do you want to delete this connection in the source system?
    Connection Is Restored After It Has Been Deleted Successfully
    Options: Delete, Do not delete.
    When we go for Delete : It is saying that "Error in source system ERQXXXXX"
    Thanks in Advance,
    Teena

    Hi,
    Please find the link which might help you:
    http://help.sap.com/saphelp_nw70/helpdata/EN/00/dc54384ac9a81be10000009b38f8cf/frameset.htm
    Best Regards,
    rajani

  • Db Connect source systems

    Are DB connect source systems also created in SM59 or just directly in RSA1? Thanks

    Check out the following Links
    http://help.sap.com/saphelp_nw04/helpdata/en/58/54f9c1562d104c9465dabd816f3f24/content.htm
    Step by step guide.
    http://www.slideshare.net/blackwhites/sap-bw-connect-db

  • Authorization for user in ECC while creating source system in RSA1 in BW

    Hello All..
    We are trying to create source system from BW(7.0) system using transaction code rsa1 to R/3 Production server.
    After providing details in RSA1->Source system ; Remote logon screen of Production server pops up ...and ask to login thru admistrator Id..
    To achieve the above task,, what authorization user should have in R/3 system..
    Thanks

    Hi,
    Hope you are using the RFCUSER with these profile SAP_ALL , SAP_NEW , S_BI-WX_RFC in SAP ECC. Please create the RFCUSER with above profiles in ECC and BW (SAP_ALL , SAP_NEW and S_BI-WHM_RFC).
    Pls follow the below steps for source system connection
    In ECC side
    1.) Client administration SCC4 ( select your client and allow changes to repository and cross client customizing)
    2.) Define a logical system in ECC
    3.) Assign a logical system in ECC
    4.) Creating RFC user with system user type and give these profiles SAP_ALL, SAP_NEW, S_BI-WX_RFC
    In SAP BI Side
    1.) Client administration SCC4 ( select your client and allow changes to repository and cross client customizing)
    2.) Define a logical system
    3.) Assign a logical system
    4.) Creating RFC user with system user type and give these profiles SAP_ALL, SAP_NEW, S_BI-WHM_RFC)
    5.) Define RFC user as default (Click RSA1> Global Settings/Customizing dialog box> Glob. Settings)
    Connection of SAP BI with ECC
    RSA1> Source System>SAP>create>Enter the below entries
    Target computer (server)                        Server of the SAP ECC
    System ID System ID of the SAP ECC
    System number System number of the SAP ECC
    Background user in source system RFCUSER
    Password for source system Password
    Background user in BW RFCUSER (can not be changed in this activity)
    Password for BW user Password
    Select unicode in RFC destination and don't select the checkbox in logic screen.
    On the dialog box Please log on as an basis administrator in the following screen choose Continue.
    Log on to the Source System with your administrator user. Choose the correct client.
    On the Replicate Metadata dialog box, choose Only Activate.
    Make sure ECC client will allow changes in cross customizing client. It is one time activity once success then deselect the entry.
    Hope this will help you to connect the system.
    Rgs,
    Ambuj Kathuria

  • Connecting source system

    Hi,
    I am working on BI 7.0 ... I have connected my BI dev client with QA client 630 and have loaded the target. Now the user wants to connect BI dev to another QA client 650 and load the data. Is there any way by which i will have to not create the IP, DTP and Transformation again when connecting to 650. These IP,DTP and Transformation are alread created for source system 630.??? Plz let me know its urgent and imp.
    Thanks
    Prashant

    Dear
    Kindly see the following link
    Steps on R/3 Side (Client :230,Dev) :
    1.     Create user BWALEUSER with usertype as communication and profile : SAP_ALL & SAP_NEW
    2.     Create Admin ( here we used :Basis) with user type as dialog and profile : SAP_ALL & SAP_NEW
    3.     Create logical system ZSENDER230 and assign the same to client 230
    Steps on BW side ( Client 220,Dev)
    4.     Create logical system and assign to client  ( In our case it was already done by basis during client copy , hence new logical system not created., even though we create and replace in assign client screen, it will throw error in RSA1 screen. Hence not created.)
    5.     Create BWREMOTE user in spro ( system creates on its own with usertype : system) > BIW>Automated process>create user for b/g processes
    6.     Also in spro Maintain proposal for R/3 ALE user i.e BWALEUSER
    7.     Goto SM59 , create RFC connection under R/3 connection with R/3 connecting user as BWALEUSER with RFC destination as ZSENDER230
    8.     Create source system in RSA1, with Basis as Admin user
    Steps on R/3 Side ( Client :230,Dev) :
    9.     While creating  sourcesytem in RSA1 , u will be connected to R/3 and it will take u to SM59 screen on R/3 side
    10.     RFC destination will be here BW logical system  ( step 4) and user for BW login is BWREMOTE
    11.     Check connection.
    shailesh

  • Deleting a system in RSA1

    Hello,
    We have completed a system refresh of our BI prod to a test system.  Upon running bdls, I noticed that we have a foren system listed under "RSA1".  This system however is a production system that we do not need listed as a source. 
    I would like to delete/remove this system from the source tree, however, is there any chance removing this system may affect the production system?  i.e.  is it safe to delete systems in rsa1 in our test environment w/out having to ever worry about an rfc call in the background that could cause issues with the production system, etc?
    Thank you very much everyone for any info on this matter.
    Kind Regards
    Richard Rog

    Hi,
    You can just delete the Source System in BW. All changes in configuration will be done ONLY in BW.
    If you want to feel even better just go to SM59 and delete the RFC to that Production System from there and go to WE20 and delete the Partner Profile at once. You can also delete the entry for the system in table "RSBASIDOC" or even run the function
    "RSAP_BIW_DISCONNECT" on SE37...
    But, again, you'll be fine just deleting the Source System.
    Regards,
    Luis
    I think you need an active RFC connection to the Source System to be able to delete. I think that happen to me once. But, anyways, no impact in your Source System.
    Edited by: Luis Sales on Jan 25, 2010 8:41 PM

  • Dúvida -  NF-e: Maintain Connected Authority Systems - layout 3.10

    Boa noite!
    Estou realizando o customize da SPRO, porém notei que só posso inserir a seguinte entrada para um mesmo CNPJ:
    Ou seja, quando tento colocar os demais estados o erro de chave duplicada é retornado devido aos campos logical system e Company's Own CNPJ. Dessa maneira, quando executo o novo programa de status de serviço (/XNFE/NFE_CHECK_SRV_STATUS) relalizando o debug noto que existe uma verificação durante a execução da função (/XNFE/SRVSTA_READ_CUST) na qual, por mais que eu tenha cadastro todos os cUF na spro que ficam registrados na tabela (/xnfe/tcuf) o status de serviço acaba sendo executado apenas para o que existe na tabela (/xnfe/govpar) alimentada pela configuração da NF-e: Maintain Connected Authority Systems da imagem que enviei posteriormente. Sendo assim só é executado o status de serviço para SP e não para todas as cUF que estão na atividade NF-e: Define Service Status Request for Authority (SEFAZ). Abaixo segue trecho do código que verifiquei que realiza esse controle no debug:
    SELECT * FROM /xnfe/govpar INTO TABLE lt_govpar
                                  WHERE doctype = iv_doctype.
    *--- 2. Version determination
      IF lt_govpar IS NOT INITIAL.
        SELECT * FROM /xnfe/xmlversdet INTO TABLE lt_xmlversdet
                           FOR ALL ENTRIES IN lt_govpar
                                 WHERE doctype  = iv_doctype
                                   AND logsys   = lt_govpar-logsys
                                   AND ( cnpj     = lt_govpar-cnpj
                                    OR   cnpj     = ' ' )
                                   AND messtype = iv_messtype.
    *--- 3. Service status check parameter
        SELECT * FROM /xnfe/tcuf INTO TABLE lt_tcuf.
        LOOP AT lt_govpar ASSIGNING <ls_govpar>.
    *--- Get corresponding entry from version determination
          READ TABLE lt_xmlversdet WITH KEY doctype = <ls_govpar>-doctype
                                            logsys  = <ls_govpar>-logsys
                                            cnpj    = <ls_govpar>-cnpj
                                  ASSIGNING <ls_xmlversdet>.
          IF sy-subrc <> 0.
    *--- If nothing is found try with blank CNPJ
            READ TABLE lt_xmlversdet WITH KEY doctype = <ls_govpar>-doctype
                                              logsys  = <ls_govpar>-logsys
                                              cnpj    = ' '
                                    ASSIGNING <ls_xmlversdet>.
          ENDIF.
          IF sy-subrc IS INITIAL.
    *--- Get corresponding entry for service status check parameter
            READ TABLE lt_tcuf WITH KEY doctype = <ls_govpar>-doctype
                                        cuf     = <ls_govpar>-cuf
                                      ASSIGNING <ls_tcuf>.
            IF sy-subrc IS INITIAL.
              ls_stacheck-cuf       = <ls_govpar>-cuf.
              ls_stacheck-tpamb     = <ls_govpar>-tpamb.
              ls_stacheck-xmlvers   = <ls_xmlversdet>-xmlvers.
              ls_stacheck-sscperiod = <ls_tcuf>-sscperiod.
              ls_stacheck-tzone     = <ls_tcuf>-tzone.
              ls_stacheck-respcont  = <ls_tcuf>-respcont.
              ls_stacheck-checkcont = <ls_tcuf>-checkcont.
              APPEND ls_stacheck TO et_stacheck.
            ENDIF.
          ENDIF.
          CLEAR: ls_stacheck.
        ENDLOOP.
      ENDIF.
    Sendo assim, como faço para que na atividade NF-e: Maintain Connected Authority Systems eu possa inserir todos os cUF com para os quais executarei o status de serviço e posteriormente enviarei notas?
    Obrigado.,

    Bom dia Luís,
    Exatamente! De fato o que ocorreu foi uma confusão, pois na versão anterior era possível enviar o status de serviço mesmo se você não possuísse uma filial para o estado em questão. Quando fui fazer a migração do cliente todos os estados estavam configurados para emitir status de serviço, porém não há necessidade de enviar o status de serviço para um estado visto que você não possui uma filial para emissão de Nota no mesmo.
    Abs.,

  • NF-e: Maintain Connected Authority Systems - Já existe uma entrada com a mesma chave

    Bom dia!
    Estou tendo um problema para adicionar novas entradas na SPRO - OUTBOUND -NF-e: Maintain Connected Authority Systems para configuração do layout 3.10:
    Sendo assim, como devo configurar todos os estados para a SEFAZ se o sistema lógico e CNPJ são chaves da tabela /xnfe/govpar?
    Com isso, não consigo executar todos os status de serviço no layout novo através do report (/XNFE/NFE_CHECK_SRV_STATUS) depois de cadastrálos na atividade NF-e: Define Service Status Request for Authority (SEFAZ,) pois durante a execução do report  (/XNFE/NFE_CHECK_SRV_STATUS) além da tabela  /xnfe/tcuf a tabela /xnfe/govpar também é verificada.
    Grato.,

    Bom dia Luís,
    Exatamente! De fato o que ocorreu foi uma confusão, pois na versão anterior era possível enviar o status de serviço mesmo se você não possuísse uma filial para o estado em questão. Quando fui fazer a migração do cliente todos os estados estavam configurados para emitir status de serviço, porém não há necessidade de enviar o status de serviço para um estado visto que você não possui uma filial para emissão de Nota no mesmo.
    Abs.,

  • Error when creating SAP source-system in RSA1

    hi,
    we have a new bi-installation. the bi-system is running in the SAME system as our erp 2005-system is running.
    the bi-client is 700, our source-system (FI/CO) client is 101. I want to create a source-system in RSA1. at the end i get the following error message:
    <b>Name D01MAND700 of client 700 is not the same as the name D01MAND101 of the Warehouse
    Message no. R3225
    Diagnosis
    In order to guarantee error-free communication between the source system and the SAP Business Information Warehouse, the logical system names must be known to both.
    The system has established that the selected source system name D01MAND101 in the SAP Business Information Warehouse is not the same as the logical system name D01MAND700.
    System Response
    Processing has been terminated and all changes undone.
    Procedure
    Create the source system under the name D01MAND700 in the SAP Business Information Warehouse or change the logical system name for client 700 to D01MAND101 in the ALE customizing screen of the source system.
    Note that the logical system name for client 700 may already be being used for other ALE scenarios. If this is the case you are not able to change the name.</b>
    i don't understand this error ? is it because the BI-system and the erp-system is the SAME system ?
    reg, Martin

    mr. kapadia,
    there is one entry in table rsbasidoc, and it looks like that:
    SLOGSYS     D01MAND700                            
    RLOGSYS     D01MAND700                                                                               
    OBJSTAT     ACT                                   
    BIDOCTYP    ZSCA017                               
    TSIDOC3X    0                                     
    TSPREFIX    CA                                    
    SRCTYPE     M                                     
    SAPREL      700                                   
    TSTPNM      D78358                                
    TIMESTMP    20.070.622.093.042                    
    SBWBCRL     700                                   
    RBWBCRL     700                                   
    looks strange, right ? what should i do ? delete this entry ? how can i do this, it is a customizing table, i cant delete it via SE16 ?!?
    reg, Martin

  • Source system in RSA1 is diiferent to the datasource in infoprovider

    Dear Guru's
    I have created a quality source system in RSA1 tcode for client 210 but in my infoprovider it shows me of diiferent datasource ie for client 200 and i need this client to be 210 so kindly help me to resolve this issue
    Regards
    Mohammed

    HI,
    Do you want to change all the assignments from client 200 to 210. Or is it for this particular Infoprovider (you have mentioned) and the relevant transformations.
    Does
    1) both clients exists as your source systems or
    2) client 200 is to be replaced by client 210.
    In the second scenario, you can refer this article. Contact your BASIS team for guidance.
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/805eefcd-5428-2d10-c0ab-dc27a95b2c81
    For scenario 1, if you want to load data from 210 client to this particular Infoprovider , replicate the datasource for client 210 in BI side and create new transformation, Infopackage and DTP from the datasource to the target.
    Hope this helps.
    Regards,
    hari.

Maybe you are looking for