How to create file type source system connection

Hi All,
I have to load data from Flat files , but when i checked the source system connections File type source system connection is not present. Please guide me how can i create the same.
Apoorva

Hi Apoorva,
Goto RSA1 -> Source System -> Right Click on File Folder .-> Create -> Logical system Name as FLAT FILE -> Source system name is the description for this source -> Enter.
Once it is created you can right click from that file and check whether it has created properly or not.
When u r moving the objects which are created under this source, the same flat file source should have been created in the target system also. And check for the entry in the target system table RSLOGSYSMAP for the flat file when u r moving the flat file objects.
Regards,
Muthu.

Similar Messages

  • How to create a DB Source system in BW

    Hi Guys,
      Can anybody explain me how to create DB Connect  source system in BW.
    Points will be awarded.
    Thanks,
    Chinna

    Hi Chinna,
    Below are the steps to be followed for the SS creation in BW :
    Prerequisites :
    1.System Number
    2.System IP address
    3.ALEOLTP like userid and password – this is the RFC user ID in the R/3 system. Usually set to communication - must be set to dialog in the R/3 Source System for the duration of the create/restore connection process.  Note: the password must be in capital letters.(If all instances are in unicode system)
    1.At the time of making the connection, the R/3 source system will need to be opened for client independent configuration.
    2.If it is a connection create or restore, the personal userid of the person doing the work must have SM59 access.
    Follow the naming convention which is being used in your system.
    1.     Logon to r/3 source system using the r/3 RFC userid to check that the userid has been set to dialog user. It is mandatory that the r/3 source system userid be setup temporarily as dialog to create the connection. If not contact the requester to have this done before continuing with the next step.
    Note: When re-checking to ensure that the r/3 userid is a dialog user, you may get prompted for new password. Change password, and make a note of the new password. Use this new password in the steps that follow for the r/3 RFC userid.
    2.     Logon to BW system using your own userid.
    3.     Enter transaction RSA1, In Source Systems, right-click on Source Systems as shown below to create new connection.
    4.     In the screen select the appropriate Source System connection type. Suppose your  are creating connection for r/3 instance, so in this case we pick the very first option.
    5.     A popup window will get displayed asking for the necessary information. To fill in the appropriate information in the that screen you need the following information concerning the r/3 source system.
    •     IP address (Application Server) &
    •     System Number
    Get this information for the r/3 source system from the SAP Logon Pad.
    6.     If Parameters have been incorrectly entered  then  the following error message will appear : “Check connection parameters for the source system”.
    7.     Re-check and re-enter correctly. If all is good then You will see the following prompt : Please log on as an administrator in the following screen.”Click green check to continue.
    8.     This will bring you to the r/3 logon screen. Logon using the r/3 RFC id. Once logged on click Check in ‘Check RFC destination’ dialog box.
    9. Consider the r/3 RFC destination screen.
    10. Check to make sure that BW system information (Userid, IP address, System Number etc) is correctly showing in the Technical Settings and Logon/Security tabs. Next do the following,
         Step 1: Enter password for the BW RFC userid id.
         Step 2: Save Settings
         Step 3: From Test Menu , click on authorization. Ensure there are no errors
         Step 4: Back out of screen.
    11.     System may ask you to logon as administrator again. Logon as in Step 10. This time click on Use in ‘Check RFC destination’ dialog box.
    Connection related processing will start up at this time, and continue for a little while (can be a couple minutes or more).
    12.     Subsequently, a dialog box will show up on the screen.
    13. Pick option, Replicate As Well.
    Replication and activation of data sources & transfer structures will begin.
    With the completion of this step you will have successfully established this source system connection. To confirm, right-click on the new source system entry and click on check
    14. If the connection is good, the following message with the source system ID will display at bottom left corner of screen : Source system connection is Ok”.
    Hope this will be helpful to you.
    Thanks & Regards,
    suchitra.V

  • How to create R/3 source system in biw

    hi
    i hv define logical system assined cllient to logical sytem creating the
    RFC destination but after remote login and all process complete it is not showing the new R/3 source system in source system. why it happening please help me?

    Hi Vivek,
    Try create like this... i think it will helps u out...
    GO TO SALE DISPLAY IMG, EXPAND ALE, EXPAND SENDING & RCIVINING SYSTEM, LOGICAL SYSTEMS, DEFINE LOGICAL SYSTEM, EXECUTE, ASSIGN  CLIENT TO LS, CONVERT LS NAMES IN APPLICATION TABLES.
    ASSIGN CLIENT TO LS                                       DEFINE LS
    CHANGE VIEW “CLIENTS                                  NEW ENTRIES
    SELECT 800 SHN 800                                             SHN 800, LS FOR 800
    DETAILS
         CLIENT 800
          LS    SHN 800
    SAME
    SAP R/3 CLIENT 800
                   LS SHN 800
    2. LOGON TO BW SERVER.
    SALE, EXPAND ALE SEND &RECIVING SYSTEM, EXPAND LOGICAL SYSTEM, ASSIGN CLIENT TO LS.
    SAP BW CLIENT 800, LS L100
    3. CREATE RFC DESTINATION IN BW
       EXPAND ALE, SYSTEMS IN NET WORKS, DEFINE TARGET SYSTEM FOR RFC
    RFC DESTINATION
    R/3 CONNECTION CREATE
    INTERNAL CONNECTION
    TCP/IP CONNECTION
    RFC DESTIONANTION SHN 800
    CONNECTION TYPE 3 CONNECTION TO R/3 SYSTEM DESP_RFC DEST FROM BW TO R/3.
    LOGON DISIT  YES OR NO SELECT NO.
    TARGET S02                       SYSTEM NO 00
    SAVE AS HOSTNAME    IP ADDRESS
    LOGON TO R/3, LANGUAGE EN, CLIENT 800, USER EX: SAPUSER PASSWORD: INDIA, SAVE.
    TEST CONNECTION SAY ENTER
    REMOTE LOGON SAY ENTER GIVES OUT SAP R/3 NEWS SESSION.
    GO TO SAP R/3
    SALE, EXPAND ALE, SEND & RECIVING SYSTEM, SYSTEM IN NETWORK, DEFINE TARGET SYSTEM FOR RFC.
    RFC DESTINATION, IN R/3 CONNECTION CREATE RFC DESTINATION L100, CONNECTION TYPE 3 DESCRIPATION R/3 TO BW
    LOGON/SECURITY
    TARGET HOST S08 SYS NO 00 SELECT HOST NAME, LOGON DETAILS LANGUAGE EN, CLIENT EX: 800 USER SAPUSER GIVE PASSWORD, TEST CONNECTION SAY ENTER.
    GO TO RSA1 SOURCE SYSTEM
    SAP SYSTEM RELASE &(MANUUALY)
    CREATE SOURCE SYSTEM
    RFC DESTIONATION SHN 800
                 LS OF R/3          SHN 800
    SOURCE SYSTEM NAME SHN 800
    BACK, THEN SYSTEM ITSELF CREATE IMPLICITLY ALL IDO’S.
    Assign points if it helps u....
    Regards,
    Ramesh

  • How to verify the  Source systems connectivity with BWQ System.

    Hi All,
    I have diff source systems. And my requirement is to check the source systems connectivity with BWQ (BW Quality sys). please any body tell me the steps how to check the source system connectivity ?
    Thanks & Regards,
    Manju

    Hi Manjula,
    If you encounter problems when establishing a connection to your target server, check the following:
    A message box appears while performing one of the following actions:
          Setting connection by choosing Apply to local session.
          Testing connection settings by choosing Test settings.
          Creating SAP TSQL objects
    If errors occurred, they are displayed in the respective message box.
       Check developer trace files in ST11.
      Test connection:
         For RFC related errors, check the RFC connection via SM59
         For database multi-connect errors, check if you can connect to the target SQL Server with the SQL Server Query Analyzer. Also check if the DBCON entries are correct.
    Regards,
    RK

  • How to create file system datagrid in flex web application

    how to create file system datagrid in flex web application

    Hi,
    Check this out:
    http://shigeru-nakagaki.com/flex_samples/FileReference/FileUploadExample2/FileUploadExampl e2.html
    Johnny
    Please rate answer.

  • Creating New Source System Connection

    [First post, so go easy on me!]
    I have created a source system connection in BW QA, to an additional R3 QA client, but I am unable to assign any datasources to the new this new connection. [I know that I should have created the connection in DEV and transported through, but I need this connection for a small test, that won't be used again.]
    To get round this, do I need to have my BW & R3 clients 'opened' again, then transfer the 'Application Component Hierarchy' via RSA9, then 'Replicate Datasources' in BW. If not, does anyone have any suggestions?
    Thanks in advance.
    Scott

    Scott,
    You will have to transfer the BC datasources that you want to use from R/3 to BW.
    in BW, right-click your source system in the modeling tab and select replicate datasources, this will take you through to your R/3 system. Select the datasources you want to use and transfer them. Then go back to your BW system and right-click the source system and select "Transfer datasources". This should make them available.
    If when you have got through to R/3 to transfer the datasources you are told that cross-client customising is not available then I think that you will have to get the client opened up.
    Cheers,
    Stuart

  • How to find the UWL work item types source system?

    Hi Gurus,
    How to find the Universal Work List work item types source system?
    Thanks in Advance,
    Dharani

    Hi Dharani,
    You can achieve this by personalizing the view for UWL.
    Click on right side context menu of iView, click on personalize view
    Here you will get list of Available Attributes not Displayed select System ID in that.
    Save your settings and now you can see the task is from which system.
    This will solve your problem.
    Regards
    Kedar Kulkarni
    Reward points if useful

  • 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

  • About creating a new source system on BW pointing to an Oracle database

    hi friends
      i m facing problems when i 
    creating a new source system on BW in AIX pointing to an Oracle database, our bw oracle use 10idatabase ,and we want to connet to 9idatabase(Windows) to get data for BW
    (1.)     in /oracle/P01/102_64/network/admin  tnsnames.ora I hava  add
    SJPT =
      (DESCRIPTION =
        (ADDRESS_LIST =
          (ADDRESS = (PROTOCOL = TCP)(HOST = 68.16.211.177)(PORT = 1521))
        (CONNECT_DATA =
          (SERVICE_NAME = SJPT)
    (2) and in etc/hosts I hava  add
    68.16.211.177 SJPT
    (3) in p01adm> tnsping SJPT it is OK
    (4)but when i
    in  BW RSA1 DATA SOURCE 
    create db connect:
    DBMS: ORA
    USER NAME: SAP
    DB PASSWORD: SAP
    [email protected]
    i t give me the error message :
    ORA-12154: TNS:could not resolve  the connect identifier
    please help me

    HI,my trans.log file is
    4 ETW000 R3trans version 6.13 (release 700 - 20.02.06 - 16:15:00).
    4 ETW000 unicode enabled version
    4 ETW000 ===============================================
    4 ETW000
    4 ETW000 date&time   : 13.11.2007 - 10:16:48
    4 ETW000 control file: <no ctrlfile>
    4 ETW000 R3trans was called as follows: R3trans -d
    4 ETW000  trace at level 2 opened for a given file pointer
    4 ETW000  [dev trc     ,00000]  Tue Nov 13 10:16:48 2007                              81  0.000081
    4 ETW000  [dev trc     ,00000]  db_con_init called                                    29  0.000110
    4 ETW000  [dev trc     ,00000]  create_con (con_name=R/3)                             50  0.000160
    4 ETW000  [dev trc     ,00000]  Loading DB library '/usr/sap/P01/SYS/exe/run/dboraslib.o' ...
    4 ETW000                                                                              43  0.000203
    4 ETW000  [dev trc     ,00000]  load shared library (/usr/sap/P01/SYS/exe/run/dboraslib.o), hdl 0
    4 ETW000                                                                           13346  0.013549
    4 ETW000  [dev trc     ,00000]  Library '/usr/sap/P01/SYS/exe/run/dboraslib.o' loaded
    4 ETW000                                                                              32  0.013581
    4 ETW000  [dev trc     ,00000]  function DbSlExpFuns loaded from library /usr/sap/P01/SYS/exe/run/dboraslib.o
    4 ETW000                                                                              35  0.013616
    4 ETW000  [dev trc     ,00000]  Version of '/usr/sap/P01/SYS/exe/run/dboraslib.o' is "700.08", patchlevel (0.46)
    4 ETW000                                                                              53  0.013669
    4 ETW000  [dev trc     ,00000]  function dsql_db_init loaded from library /usr/sap/P01/SYS/exe/run/dboraslib.o
    4 ETW000                                                                              34  0.013703
    4 ETW000  [dev trc     ,00000]  function dbdd_exp_funs loaded from library /usr/sap/P01/SYS/exe/run/dboraslib.o
    4 ETW000                                                                              53  0.013756
    4 ETW000  [dev trc     ,00000]  New connection 0 created                              23  0.013779
    4 ETW000  [dev trc     ,00000]  0: name = R/3, con_id = -000000001 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
    4 ETW000                                                                              39  0.013818
    4 ETW000  [dev trc     ,00000]  db_con_connect (con_name=R/3)                         45  0.013863
    4 ETW000  [dev trc     ,00000]  find_con_by_name found the following connection for reuse:
    4 ETW000                                                                              32  0.013895
    4 ETW000  [dev trc     ,00000]  0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
    4 ETW000                                                                              37  0.013932
    4 ETW000  [dev trc     ,00000]  Got LIBPATH=/usr/lib:/lib:/usr/sap/P01/SYS/exe/run:/oracle/P01/102_64/lib from environment
    4 ETW000                                                                             325  0.014257
    4 ETW000  [dev trc     ,00000]  -->oci_initialize (con_hdl=0)                         47  0.014304
    4 ETW000  [dev trc     ,00000]  Client NLS settings: AMERICAN_AMERICA.UTF8          3234  0.017538
    4 ETW000  [dev trc     ,00000]  Logon as OPS$-user to get SAPSR3's password           28  0.017566
    4 ETW000  [dev trc     ,00000]  Connecting as /@P01 on connection 0 (nls_hdl 0) ... (dbsl 700 240106)
    4 ETW000                                                                              34  0.017600
    4 ETW000  [dev trc     ,00000]  Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
    4 ETW000                                                                              35  0.017635
    4 ETW000  [dev trc     ,00000]    0 UTF8                                                      1 0x110f8b9c0 0x110fa3e38 0x110fa36e8
    4 ETW000                                                                              36  0.017671
    4 ETW000  [dev trc     ,00000]  Allocating service context handle for con_hdl=0       37  0.017708
    4 ETW000  [dev trc     ,00000]  Allocating server context handle                      24  0.017732
    4 ETW000  [dev trc     ,00000]  Attaching to DB Server P01 (con_hdl=0,svchp=0x110f94398,svrhp=0x110fa6158)
    4 ETW000                                                                              72  0.017804
    4 ETW000  [dev trc     ,00000]  Assigning server context 0x110fa6158 to service context 0x110f94398
    4 ETW000                                                                           36191  0.053995
    4 ETW000  [dev trc     ,00000]  Allocating user session handle                        73  0.054068
    4 ETW000  [dev trc     ,00000]  Starting user session (con_hdl=0,svchp=0x110f94398,srvhp=0x110fa6158,usrhp=0x110f937a0)
    4 ETW000                                                                              43  0.054111
    4 ETW000  [dev trc     ,00000]  Assigning user session 0x110f937a0 to service context 0x110f94398
    4 ETW000                                                                           10613  0.064724
    4 ETW000  [dev trc     ,00000]  Now '/@P01' is connected (con_hdl 0, nls_hdl 0).
    4 ETW000                                                                             964  0.065688
    4 ETW000  [dbsloci.    ,00000]  *** ERROR => ORA-942 when accessing table SAPUSER
    4 ETW000                                                                            1183  0.066871
    4 ETW000  [dev trc     ,00000]  Disconnecting from connection 0 ...                   73  0.066944
    4 ETW000  [dev trc     ,00000]  Rolling back transaction ...                          28  0.066972
    4 ETW000  [dev trc     ,00000]  Closing user session (con_hdl=0,svchp=0x110f94398,usrhp=0x110f937a0)
    4 ETW000                                                                             146  0.067118
    4 ETW000  [dev trc     ,00000]  Now I'm disconnected from ORACLE                     409  0.067527
    4 ETW000  [dev trc     ,00000]  Try to connect with default password                  23  0.067550
    4 ETW000  [dev trc     ,00000]  Connecting as SAPSR3/<pwd>@P01 on connection 0 (nls_hdl 0) ... (dbsl 700 240106)
    4 ETW000                                                                              34  0.067584
    4 ETW000  [dev trc     ,00000]  Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
    4 ETW000                                                                              36  0.067620
    4 ETW000  [dev trc     ,00000]    0 UTF8                                                      1 0x110f8b9c0 0x110fa3e38 0x110fa36e8
    4 ETW000                                                                              36  0.067656
    4 ETW000  [dev trc     ,00000]  Assigning username to user session 0x110f937a0        22  0.067678
    4 ETW000  [dev trc     ,00000]  Assigning password to user session 0x110f937a0        41  0.067719
    4 ETW000  [dev trc     ,00000]  Starting user session (con_hdl=0,svchp=0x110f94398,srvhp=0x110fa6158,usrhp=0x110f937a0)
    4 ETW000                                                                              37  0.067756
    4 ETW000  [dboci.c     ,00000]  *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
    4 ETW000                                                                           33690  0.101446
    4 ETW000  [dbsloci.    ,00000]  *** ERROR => CONNECT failed with sql error '1017'
    4 ETW000                                                                              36  0.101482
    4 ETW000  [dblink      ,00431]  ***LOG BY2=>sql error 1017   performing CON [dblink#3 @ 431]
    4 ETW000                                                                             122  0.101604
    4 ETW000  [dblink      ,00431]  ***LOG BY0=>ORA-01017: invalid username/password; logon denied [dblink#3 @ 431]
    4 ETW000                                                                              34  0.101638
    2EETW169 no connect possible: "DBMS = ORACLE                           --- dbs_ora_tnsname = 'P01'"

  • Source system connection issues

    Hello BI Experts,
    We had issues with the source system connection - from our BI system (NW 04s) to our R/3 system (ECC 6.0) .
    From RSA1, when we right click on the R3 source sytem and do a "Check", it was erroring out: "Error in source system <Logsysname1>". This Logsysname1 was different one from the actual R/3 system's Logsys name (Logsysname2) .
    To Fix this, we restored the connection by selecting the (R/3) Source system and right click and "Restore".
    After providing the passwords for the RFC users, the system again asked "The Connection <XY> is used in the <Logsysname1> Source system as a connection." And we selected the "Delete" option here. Then in the Logon screen to R/3, we provided the administrator user Id and password.
    Once the source system connection is complete, we checked the connection as mentioned above and the "Source Sytem connection is OK" now.
    (1) But now, in the transaction RSA1, the R/3 system is displayed under "BI" instead of "SAP".
    (2) When we asked our BI consultant to check the dataloads, he encountered an error: "No transfer structure is available for InfoSource <X> in the Source system. Errors in Source system".
    How can we bring the R/3 system under "SAP" now?
    If we delete the R/3 system (which is listed under BI) and recreate under "SAP", will the transfer rules will also get deleted?? How to avoid this issue?
    Please advise.
    John
    SAP Basis.

    Hi,
    Please make sure that you have followed the below steps while creating the Source System
    1.     In the initial screen of the source system, choose Tools ® Administration ® User Maintenance ® Users and create a background user with a password and the authorization profile S_BI-WX_RFC.
    2.     Define the RFC destination parameters for the SAP source system in BW. To do this, choose Tools ® Administration ® Administration ® Network ® RFC Destinations in BW.
    Enter the information taken from the source system on the server name.
    u2022     Application server: pswdf090
    u2022     System ID: IDF
    u2022     System number: 90
    The destination name has to correspond to the logical name of the source system that you entered for the process step Define Logical System in the implementation guide for the source system. For user and password, enter the background user that you created in step 1.
    3.     Define the RFC destination parameters for the SAP BW in the source system. To do this, select Tools ® Administration ® Administration ® Network ® RFC Destinations in the source system. Enter the server name information taken from the BW system.
    The destination name has to correspond to the logical name of the BW system that you entered in the process step Define Logical System in the BW Customizing Implementation Guide. ALE communicates using the name of the SAP Business Information Warehouse that you defined. The defined name represents how the SAP Business Information Warehouse is identified. For the user and password, enter the background user that you defined in the BW Customizing Implementation Guide under Business Information Warehouse ® Links to Other Systems ® Link Between SAP Systems and BW.
    4.     Test both RFC destinations with the functions Test ® Connection and Test ® Authorization.
    If an error occurs during the authorization check, the background user is not permitted in this client and with this password. If an error occurs in the connection test, it means there is a network problem.
    5.     In the BW Administrator Workbench choose SOURCESYSTEMTREE ® Root ® Context Menu (right mouse button) ®Create and select the radio button for the manually creating an SAP source system.
    6.     Enter a description for the source system and the logical name of the source system that you entered for the process step Maintain Logical System in the source system implementation guide.
    If you still have any issues, let us know.
    Regards,
    Yogesh.

  • Source System Connection Problem - RSAR 371

    We are attempting to create source system connections in our newly created NW2004s Dev system (sapdvbd1/BD1). We also have an existing NW2004s Dev system (sapsvbd1/BD1) which already contains the same source system connections.  The old Dev system was on a virtual machine but due to performance issues we have built another Dev system on a real server.  Is there any way to create these source system connections on both servers until everything has been moved from the old to the new?  The same source systems need to exist on both.  Thanks.

    Hi ,
    Please check with basis or if you can ,then try to restore the source system in BI/BW.This should correct the  inconsistencies between the two systems which is being caused by different Idoc types
    Also check the table RSBASIDOC in the BI system and compare this to R/3 system ,the "basic type" field should be same.
    A restore should work,it has always worked for me.
    Regards
    Amit

  • Bi content with source system connection

    Hello all,
    I am in BI 7.0 DEV SEVER, I WAS CONNECTED TO TWO SOURCE SYSTEMS X,Y, IN BOTH SOURCE SYSTEMS I WAS REPLICATED DATASOURCES, THEN I AM GOING TO INSTALL BUSINESS CONETENT FOR ONE CUBE WITH DATA FLOW BEFORE AND AFTER, IT WAS CONNECTING TO SOURCE SYTEM X, BUT I WANT TO USE SOURCE SYSTEM Y.
    IS THERE ANY PROBLEM WHEN INSTALLING BUSINESSS CONTENT WITH ONE SOURCE SYSTEM X,EXTRACTION DONE BY OTHER SOURCE SYTEM Y.
    OTHERWISE I WANT TO INSTALL BUSINESS CONTENT FROM SOURCE SYSTEM Y,WITH OUT DELETING SOURCE SYTEM X, HOW CAN I CHANGE TO SOURCE SYSTEM Y.

    Hi,
    you can't install BI content infocube for one source system and do the extraction in another source system.
    when you are installing the BI content you can maintain source system assignment for one or more source system like X, Y for both.
    if you don't have Y source system means create it or change the exiting source system..
    hope this give you an idea
    Regards
    Harikrishna N

  • Unable to create File Type Rules Repository

    Hi Gurus,
    I am trying to create File Type Rules Repository(SOA Suite 10.1.3.4).
    As per the documentation:
    To create and connect to a new file-based repository we need to select a
    Repository Type of File, and specify the full path name of where you want to create
    the repository and then click Create.
    But when i select the repository type: file
    and browse for the location of where I want to create it.It won't let me select a directory, only a file..!It opened the browse a window with name :file upload
    Even I am unable to type the folder path where the new repository need to be created.After lot number of trials i am posting this.Please help me in fixing this.
    Thanks in advance..
    Regards,
    Chandra

    Thanks for your reply lahvenai,
    Could you please tell me How to the rule admistrator role get granted.I am loggiing in with oc4jadmin user.
    Please help me on this.
    Regards,
    ravi

  • RFC destination BW could not be created in the source system R3073

    I'm creating a source system for our BW (version 7.0) dev client.I'm linking it to our R/3 4.7 QA client. From RSA1 I select create source system, I enter the system information and in the next screen I'm prompted to log on as system administrator. I'm in QA now and the system automatically crated the RFC connection. I test the connection and it runs ok. I log on to the BW client from QA and it logs on just fine. When I exit the screen I get the following message:
    RFC destination BW could not be created in the source system message number R3073
    Why is this happening? The connection tests just fine.
    I'm using RFCREMOTE user in BW and ALEREMOTE in QA with the same password
    Any ideas?
    thanks

    Hi,
    I cannot tell you surely the settings for SCC4 now (I can't connect to my sys).
    Nevertheless, create your R3QA RFCDEST manually in your BWDEV with SM59.
    Create your BWDEV RFCDEST manually in your BWQA .
    Perform test and authorization test within SM59 from both sys.
    When creating the source system in BW the system will detect the RFC and ask you if you want to use it; accept an proceed the the rest of the procedure.
    hope this helps...
    Olivier.

  • RSA1 - Source system connection : Change in logical system name

    Dear friends,
    Can you please tell me how can i change the logical system name for a source system connection.
    There is no change in source system & source system connection check works well, just we have decided that from current logical system name SID_100 should be changed to SIDCLNT100.
    Can i do this by running BDLS in BW for RSBASIDOC table from SID_100 to SIDCLNT100 ?
    thanks
    ashish

    HI Sunny,
    This is not the same problem, may be similar though..i am not getting a way.
    let me describe u in a bit more details.
    Currently, we have a working source system connection to a system SID_CLT.  there is no change in source system.
    now, can i change this system connection technical name from SID_CLT to SIDCLNT*** .. 
    thanks
    ashish

Maybe you are looking for