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

Similar Messages

  • 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

  • Change in the source system

    Dear All,
    We have currently BW 3.5 and CRM R/3 server up and running in Production.
    Now CRM server is being upgrade to CRM 7.0 . Now i being the BW consultant needs to find out what is that needs to be done at BW side.
    My idea :-
    1) We first need to create a new Source system and repllicate all the data sources in bw system.
    2) Assign this datasource to the old infosource.
    3) create an infopkg and try loading the data once again to the old cube.
    We can ahieve this in Dev system and then transport the Transfer rules again to BW Production system.
    Can we directly get this done in Production system????
    Kindly add your idea to this list and suggest if we can do this directly in the Productions system without the need to transport the Transfer rule from Deve system.
    Thanks & Regards,
    Anup

    first, temporarily disconnect the source system connection when the upgrade is started...
    after that as you said, please transport the transfer rules from DEV box to production box. it is not advisble to do directly in production box.
    Since the end user is having access to the production box, it is not advisble to open the production box as modifiable and allow to changes.
    Hence we cannot take long down time isnt..? After upgrade is done, please restore the source system connection.
    Better you dont delete the source system of your CRM system in BI.
    Hope this would help you.

  • Problem restoring source system connection post BW system copy

    Hi.
    I am having problems restoring the R/3 connection in our BW system.
    This is the scenario.
    We need to move our BW production system onto a new system, but keep both BW connected to R/3 production for testing etc until cutover to our new BW system.
    Basis performed a system copy and restore of BW production to the new system and ran BDLS.
    When I try to restore the R/3 connection via RSA1 I am getting the following error at the end-
    "A connection already exists there ......." and the message refers to our current/live BW system. The options are to delete the existing or not delete. I have only chosen "do not delete" and therefore the connection is not restored. My concern is that if I choose "delete" this will damage my existing connection between R/3 and the currently live BW system which is we cannot afford to do.
    In our newly copied BW system we are using the existing R/3 SM59 (from system copy), and in R/3 we have created a new SM59 for our new BW system.
    It seems from the error message information that is complains that BW sent R/3 some sort of ID (value = "WS") and that is already taken by the existing BW system. I tried to find where and what this WS value is referring to and the only thing I have found is that in table RSBASISIDOC "WS" is the suffix for transfer structure for that R/3 system. ??? Not sure if this is related for what.
    Thanks for any help

    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

  • 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

  • Source system connection problem in BI

    Hi ,
    While checking source system connection we are getting below error
    " BI IDoc type ZSBP055 is not the same as source system IDoc type ZSBP120"
    could please guide on this .
    Regards
    vamsi

    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

  • 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

  • Error: Infoobject is not defined in the source system

    hi
    (I posted this in other forums as well - but wondering, it it should be here in BCT/Extractors - I could use more help).
    this is my issue:
    I am trying to load master data (attr) for an infoobject.
    But, it fails with the following error message (when I click on the "Error message" button on the "monitor" screen.
    "Infoobject is not defined in the source system"
    "Erros in source system".
    (I did rsa3 and find it has some data + i checked on the base table as well, it has data; the datasource is from an SRM system) Why is it complaining like this.
    any help on what could be wrong here? Pl let me know,
    thanks

    Thanks Ricardo,
    I have tried that b4. and it says the "source system connection is OK".
    any other idea?
    Do I have to install the infoobjects on the source system as well? SRM is my source system.. I am not sure on that, but If I have to, how do I do that?
    thanks
    Message was edited by: Esan

  • Change the source system

    Hello
    In our Quality Box , I need to change the source system connection (from QR1 to QR2). I created the new connection successfully. Now the issue is all the Transfer structure still using OLD connection ( i.e QR1) . I run BDLS and it did not word. How can I re-assign the new source system (QR1)  to all of my Transfer structures in one go. Is there any report ?
    Farooq

    Hello,
    You cant directly convert the existing objects for a source system to the new source system.
    For that you need to do a transport of the objects to the QA box while maintaining the entry in BDLS to convert to the new source system.
    Regards,
    Shashank

  • SQL Server 2005 DB as a source system connection

    Dear all,
    We are planning to connect SQL server 2005 DB as one of the source system connection in RSA1.
    Please let me know how to do and if procedure/steps doc for the same.
    please do the needful. Thanks in advance.
    Regards,
    Mohankumar.G

    Hi Mohan,
    You can use DB connect method...
    Please find following for the same.
    https://wiki.sdn.sap.com/wiki/display/BI/DB+Connect
    Regards,
    Mahesh

  • 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

  • BI Source System connection to ECC

    Hi experts,
    I have a BI 7.0 fresh install and I'm trying to connect ECC 6.0 client dev100 (golden client) to BI so I can activate BI Content. However, the client 100 goes to the BI folder instead of the SAP folder when I create source system in AWB. Is this normal behavior?
    I have another system client dev200 and it goes inside SAP folder when I create source system. I'm just wondering if this has something to do will my error in BI Content activation. Key figures and characteristics are activated but not DataSources, Update rules, and InfoPackage.
    Your comments are greatly appreciated. Thank you

    Hi JD,
    I think the source system connection must have been made in Bi folder. basically even BI folder shall contain BI system but if ECC system connection is made in this folder it shall not make any diffrence. You must be getting the datasources as of ECC only after replication.
    Regards,
    Wrushali
    Request for points deleted. Please do not ask for points in the forum.
    Edited by: Vikram Srivastava on Jun 22, 2010 1:56 PM

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

  • 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

Maybe you are looking for

  • How to Use a report as a filter in another report

    Hi We are presently migrating from microstategy to OBIEE. There is a report with 3 attributes and a single metric(the metric is the count of remedy ticket). The 2nd report has just the 3 attributes(the person who doesn't have a ticket for the given t

  • Strange Oracle---- ORA-00904

    I have below query.. it looks fine but still getting error as shown below ... Breaking my head to identify error but couldn't.. its prompting me as 'ora-00904: "Y"."TRANSACTION_NUMBER": invalid identifier' in short my query is of form... SELECT * FRO

  • View Standard tabs in BP

    Hi Experts, I have a requirement to view standard tabs on BP transaction which are not visible. For Eg: While Creating Business partner with role as (BP General) I could see the following tabs :- Address , Address Overview , Identification , Control

  • I buy a new MacBook pro but i don't want lost any documents...

    I buy a new MacBook Pro  but don't know how i can transfer all my pics and documents

  • Maximum length Title field SSP

    All, We use Service Manager 2012 with the default Microsoft Self Service Portal solution. When users enter a very long title in a request, than is it not possible to create the request because the length is not conform the maximum length requirement.