Delta Extraction using Infospoke

We are currently on BW 3.1C with 3.3 business Content. I have created an infospoke to get data from ODS object into db table. I am trying to get delta and also turned on the techinical Key on the infospoke but when I run the infospoke I get before and after images. Is there any way that I can get just the changed record if not how can I identify the changes do I have to build my own logic to capture changes?? I dont understand how the delta works on Infospoke for an ODS object and I am not sure whether I am creating it correctly. Please help.
Thank you,
Neelu

Roberto,
I have created an infospoke off of an ODS which contains MARA table. My question with respect to infospoke
1. if you are looking to send only changed records to the different target like db table would you check the technical key
2. if an existing record is changed with the technical key on it would add another record so when reporting off of the db table i will see multiple records where as our requirement is to see the most updated record.
Thank you
Neelu

Similar Messages

  • Code For Delta Extraction Using Function Module

    Dear Experts,
    I want a sample code for Delta Extraction using Function Module ( If it is customized already working code very helpful ), I have already created Function Module but Full update is happening. If I give delta update again it is retrieving all records. It is very urgent, if you have please send me to the following mail ID.
    [email protected]
    Best Regards,
    SGK.

    Dear KJ,
    Thank for your response. I saw the code that you sent, you have used some ztables like ZSC_DELTA_IP, ZSC_SAFETY_DELTA, ZSC_SET_EXT_TIME
    What are the fields that you have created in these tables , what is use of these tables, can you send the fields that you have used in these tables.
    Thanks & Regards,
    SGK

  • Delta Extraction Using Function Module ( Customization )

    Dear Experts,
    I want a sample code for Delta Extraction using Function Module ( If it is customized already working code very helpful ), I have already created Function Module but Full update is happening. If I give delta update again it is retrieving all records. It is very urgent, if you have please send me to the following mail ID.
    [email protected]
    Best Regards,
    SGK.

    Hi SGK,
    I've done this for a delta based on a timestamp and it's actually pretty easy.  The basic steps are:
    1) Create an extract structure in SE11.  Make sure the structure has a date or timestamp field in it that you can use for delta.  You'll need to include the field twice if you also want to extract it to BW/BI since once it's chosen as the delta field then it will be hidden in the interface.
    2) Create the extractor function module in SE37.  You can use RSAX_BIW_GET_DATA_SIMPLE as a template.  Make sure your logic restricts the data it retrieves according to the selections that are passed in I_T_SELECT, including restrictions on the delta field.
    3) Create a generic DataSource in RSO2.  Click Extraction by FM then fill in your extract structure and function module.  Click Generic Delta and pick your delta field and the appropriate radio button (time stamp or calendar day).  If your delta field is a timestamp field then be sure to set the upper and lower safety limits to -86400 and 86400 respectively.  This might not be necessary on your version of SAPI but on mine there is a bug where it doesn't translate between system time and UTC (GMT) correctly so this was necessary.
    You don't need to program any special delta handling logic in your function module as long as you restrict the data you retrieve based on the delta field (I_T_SELECT).  This is because the SAPI takes care of catching the init, delta and repeat requests, translating them to the appropriate delta field values, and then passing them to your function module as if it was a full extraction for a specific date or timestamp range.
    Hope this helps!
    Jason

  • Short dump in delta extract  using bgRFC in NW 2004s

    Short dump in delta extract after Support Pack install, using bgRFC. 
    InfoSet Query extractor from Z-table residing on BW system into ODS. 
    Init and Full loads load successfully, delta loads short dump.
    "MESSAGE_TYPE_X"        
    "SAPLARFC" or "LARFCU25"     
    "TRFC_SET_QUEUE_RECEIVER_LIST"
    Problem began after support pack install, from SP 9 to SP 12.   Switched to Classic RFC in SM59,  seemed to correct this extractor but caused problems in  other extractors.

    Hi Kevin,
    check out this note: https://websmp205.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1054970&_NLANG=EN
    it might help.
    regards
    Siggi

  • Generic delta extraction using function module

    Hi.
    I have a generic datasource , extraction being performed by a function module. The extraction works fine in full update mode. The extract structure has a timestamp field.
    I have enabled generic delta using this field(i.e., marked this field in RSO2). I understand that with this setting, I should be able to get delta data when I do a delta request. But it does not seem to happen.
    I checked the ROOSPRMSC table for the last(local) timestamp stored there. Now when I do the delta upload I expect to see only those records which are younger than the stored timestamp of last upload.
    But I still get the entire set of records.
    Questions are :
    1. Do I need to explicitly code for fetching the delta in the extractor ?
    2. If not, what could be the reason why generic delta is not working ?
    Thanks and regards,
    Anuradha

    Hi GFV,
    I read-up all the forum entries on this topic but could not find anything specifically dealing with my problem. I have browsed through the how-to paper on generic delta as well.
    I am quite sure that we don't need any special coding in the extrator for generating delta generically. Even the how-to paper does not mention that.
    I have used the FM RSAX_BIW_GET_DATA_SIMPLE as a template
    for my extractor(as suggested by F1 help in RSO2). This FM does not even have the i_updmode flag in its interface. 
    Thus this function module always does full extraction and I expect the system to take care of delta using the timestamp field.
    Are these assumptions incorrect ?
    Regards,
    Anuradha

  • Error in Delta extraction of Material using MDM_CLNT_EXTR

    Hi All ,
    I am facing  the following error while doing the delta extraction for material by using MDM_CLNT_EXTR.
    ABAP/4 processor: MESSAGE_TYPE_UNKNOWN 
    I used MATERIAL_EXTRACT stucture, and successfully run the intial load.
    Any help will be appriciated
    BR
    Syam

    Hi Syam,
    Just check whether the target system defined in XI and the extraction object that you are selecting are in sync.
    Such error is possible when there is a conflict in the same.
    You can also refer to the below link.
    Delta Extraction Using MDM_CLNT_EXTR (Urgent)
    Hope it helps.
    Thanks,
    Minaz
    Edited by: Minaz Kathawala on Sep 30, 2008 4:14 PM

  • Delta extraction for a generic datasource

    Hi BWers,
    I want put in Delta the extraction of a generic datasource.
    Currently this generic datasource is based on the table VBPA (Sales Document: Partner). Any time field exists.
    We need a time field in order to converse to a Delta extraction. This time field exists in the table VBAP (Sales Document: Item data). In fact two time fields exist: one which is filled at the creation of the sales order (ERDAT), another at the change of the sales order (AEDAT).
    The fields VBELN, POSNR and MANDT are keys in the tables VBAP and VBPA.
    The table VBAP changes when partner functions is created or changed in a sales order (VBELN) :
    - When it is a creation of a new sales order (with new partner functions), a new record is created in VBAP and the field ERDAT (Created on) is filled. The field AEDAT (Changed on) is empty.
    - When is a change of an existing sales order, the corresponding record in VBAP changed, and the field AEDAT is filled. ERDAT stays unchanged.
    In order to converse to the Delta extraction, i need a only one time-field (calendar day) in RSO2 / Generic Delta.
    But there is 2 time-fields ERDAT and AEDAT. So i just need to get AEDAT if it is filled, else if AEDAT is empty I will get ERDAT.
    I would base my datasource on a view between VBPA and VBAP with one field which will be filled by AEDAT or ERDAT (with the conditions below). But it seems it is not possible.
    Can you give me other ideas ?
    Thanks a lot.
    Cheers,
    Vince.

    In order to create a generic delta from two source fields, ERDAT and AEDAT in this case, you're going to have to create your generic extractor from a Function Module. Otherwise you'll only have the standard functionality available to you for creating the generic delta, which allows you to base it on only one column.
    Here's a sample you can use, that was created for VBFA, and change for your DataSource.
    FUNCTION y_docu_flow.
    *"*"Local interface:
    *"  IMPORTING
    *"     VALUE(I_REQUNR) TYPE  SRSC_S_IF_SIMPLE-REQUNR
    *"     VALUE(I_DSOURCE) TYPE  SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
    *"     VALUE(I_MAXSIZE) TYPE  SRSC_S_IF_SIMPLE-MAXSIZE OPTIONAL
    *"     VALUE(I_INITFLAG) TYPE  SRSC_S_IF_SIMPLE-INITFLAG OPTIONAL
    *"     VALUE(I_READ_ONLY) TYPE  SRSC_S_IF_SIMPLE-READONLY OPTIONAL
    *"     VALUE(I_REMOTE_CALL) TYPE  SBIWA_FLAG DEFAULT SBIWA_C_FLAG_OFF
    *"  TABLES
    *"      I_T_SELECT TYPE  SRSC_S_IF_SIMPLE-T_SELECT OPTIONAL
    *"      I_T_FIELDS TYPE  SRSC_S_IF_SIMPLE-T_FIELDS OPTIONAL
    *"      E_T_DATA STRUCTURE  YSDS_DOCU_FLOW OPTIONAL
    *"  EXCEPTIONS
    *"      NO_MORE_DATA
    *"      ERROR_PASSED_TO_MESS_HANDLER
    *& Global Data Declarations
    * Type for VBFA Data
      TYPES : BEGIN OF ty_vbfa            ,
                mandt   TYPE vbfa-mandt   ,
                vbelv   TYPE vbfa-vbelv   ,
                posnv   TYPE vbfa-posnv   ,
                vbeln   TYPE vbfa-vbeln   ,
                posnn   TYPE vbfa-posnn   ,
                vbtyp_n TYPE vbfa-vbtyp_n ,
                rfmng   TYPE vbfa-rfmng   ,
                meins   TYPE vbfa-meins   ,
                rfwrt   TYPE vbfa-rfwrt   ,
                waers   TYPE vbfa-waers   ,
                vbtyp_v TYPE vbfa-vbtyp_v ,
                plmin   TYPE vbfa-plmin   ,
                erdat   TYPE vbfa-erdat   ,
                aedat   TYPE vbfa-aedat   ,
              END   OF ty_vbfa            .
    * Internal Tables and Selection Criteria Structure
      DATA : t_vbfa     TYPE STANDARD TABLE OF ty_vbfa ,
             l_s_select TYPE srsc_s_select             .
    * Field Symbols
      FIELD-SYMBOLS : <fs_fields> TYPE rsfieldsel.
    * Constants
      CONSTANTS : c_error_msgty TYPE rslogparms-msgty VALUE 'E'            ,
                  c_error_msgid TYPE rslogparms-msgid VALUE 'YAERO_WTY_VSR',
                  c_error_msgv1 TYPE rslogparms-msgv1 VALUE ' MESSAGE_V1 ' ,
                  c_error_msgv2 TYPE rslogparms-msgv1 VALUE ' MESSAGE_V2 ' ,
                  c_error_msgv3 TYPE rslogparms-msgv1 VALUE ' MESSAGE_V3 ' ,
                  c_error_msgv4 TYPE rslogparms-msgv1 VALUE ' MESSAGE_V4 ' ,
                  c_error_msgno TYPE rslogparms-msgno VALUE 999            ,
                  c_alias(2)    TYPE c                VALUE 'A~'           ,
                  c_vbfa        TYPE dntab-tabname    VALUE 'VBFA'         .
    * Maximum Database Lines, Data Package Counter and Cursor
      STATICS : s_s_if              TYPE srsc_s_if_simple ,
                s_counter_datapakid TYPE sy-tabix         ,
                s_cursor            TYPE cursor           .
    * Select Ranges
      RANGES : r_erdat FOR vbfa-erdat ,
               r_aedat FOR vbfa-aedat ,
               r_vbelv FOR vbfa-vbelv ,
               r_posnv FOR vbfa-posnv ,
               r_vbeln FOR vbfa-vbeln ,
               r_posnn FOR vbfa-posnn .
    *& Processing Logic
    * Refresh Internal Table and Clear work area
      REFRESH: t_vbfa   ,
               e_t_data .
    * Check the Extraction Mode (Delta Initialization Or Delta)
      IF i_initflag EQ sbiwa_c_flag_on.
    *   Determine DataSource Validity
        IF i_dsource NE 'YSDDS_DOCU_FLOW'.
    *     Call Function to Write Log
          CALL FUNCTION 'RSAL_LOG_WRITE'
            EXPORTING
              i_msgty = c_error_msgty
              i_msgid = c_error_msgid
              i_msgno = c_error_msgno
              i_msgv1 = c_error_msgv1
              i_msgv2 = c_error_msgv2
              i_msgv3 = c_error_msgv3
              i_msgv4 = c_error_msgv4.
    *     Raise Exception
          RAISE error_passed_to_mess_handler.
        ENDIF.                  " IF i_dsource NE 'YSDDS_DOCU_FLOW'.
    *   Append the Selection Criteria
        APPEND LINES OF i_t_select TO s_s_if-t_select.
    *   Fill parameter buffer for data extraction calls
        MOVE : i_requnr  TO s_s_if-requnr  ,
               i_dsource TO s_s_if-dsource ,
               i_maxsize TO s_s_if-maxsize .
    *   Append Fields to be Selected
        APPEND LINES OF i_t_fields TO s_s_if-t_fields.
    *   Add the Alias to Fields
        LOOP AT s_s_if-t_fields
          ASSIGNING <fs_fields>.
          CONCATENATE c_alias
                      <fs_fields>-fieldnm
                 INTO <fs_fields>-fieldnm.
          CONDENSE <fs_fields>-fieldnm NO-GAPS.
        ENDLOOP.                " LOOP AT s_s_if-t_fields..
      ELSE.                     " IF i_initflag EQ sbiwa_c_flag_on
    *   For First Data Package, Open Cursor
        IF s_counter_datapakid EQ 0.
    *     Clear Ranges
          CLEAR : r_erdat ,
                  r_aedat ,
                  r_vbelv ,
                  r_posnv ,
                  r_vbeln ,
                  r_posnn .
    *     Fill Selection Ranges
          LOOP AT s_s_if-t_select
            INTO l_s_select.
    *       Determine Selection Range Field Name
            CASE l_s_select-fieldnm.
    *         Created On Date
              WHEN 'ERDAT'.
                MOVE : l_s_select-sign   TO r_erdat-sign   ,
                       l_s_select-option TO r_erdat-option ,
                       l_s_select-low    TO r_erdat-low    ,
                       l_s_select-high   TO r_erdat-high   .
                APPEND r_erdat.
    *           Fill the change date too
                MOVE r_erdat[] TO r_aedat[].
    *         Predecessor Document Number
              WHEN 'VBELV'.
                MOVE : l_s_select-sign   TO r_vbelv-sign   ,
                       l_s_select-option TO r_vbelv-option ,
                       l_s_select-low    TO r_vbelv-low    ,
                       l_s_select-high   TO r_vbelv-high   .
                APPEND r_vbelv.
    *         Predecessor Document Line Item
              WHEN 'POSNV'.
                MOVE : l_s_select-sign   TO r_posnv-sign   ,
                       l_s_select-option TO r_posnv-option ,
                       l_s_select-low    TO r_posnv-low    ,
                       l_s_select-high   TO r_posnv-high   .
                APPEND r_posnv.
    *         Successor Document Number
              WHEN 'VBELN'.
                MOVE : l_s_select-sign   TO r_vbeln-sign   ,
                       l_s_select-option TO r_vbeln-option ,
                       l_s_select-low    TO r_vbeln-low    ,
                       l_s_select-high   TO r_vbeln-high   .
                APPEND r_vbeln.
    *         Successor Document Line Item
              WHEN 'POSNN'.
                MOVE : l_s_select-sign   TO r_posnn-sign   ,
                       l_s_select-option TO r_posnn-option ,
                       l_s_select-low    TO r_posnn-low    ,
                       l_s_select-high   TO r_posnn-high   .
                APPEND r_posnn.
            ENDCASE.            " CASE l_s_select-fieldnm.
          ENDLOOP.              " LOOP AT s_s_if-t_select..
    *     Open Cursor on View to Fetch data
    *     If full load with Selection on Fiscal Year
          IF r_aedat[] IS INITIAL.
    *       Full Extraction
            OPEN CURSOR
            WITH HOLD s_cursor FOR
          SELECT (s_s_if-t_fields)
            FROM vbfa      AS a
            JOIN pnwtyv    AS b
              ON a~vbelv   EQ b~sdvbeln
           WHERE a~vbelv   IN r_vbelv
             AND a~posnv   IN r_posnv
             AND a~vbeln   IN r_vbeln
             AND a~posnn   IN r_posnn
             AND a~rfmng   NE 0
             AND a~erdat   IN r_erdat
             AND b~sdvbeln NE space.
          ELSE.
    *       Delta Extraction Using ERDAT and AEDAT
            OPEN   CURSOR
            WITH   HOLD s_cursor FOR
          SELECT   (s_s_if-t_fields)
            FROM   vbfa      AS a
            JOIN   pnwtyv    AS b
              ON   a~vbelv   EQ b~sdvbeln
           WHERE   a~vbelv   IN r_vbelv
             AND   a~posnv   IN r_posnv
             AND   a~vbeln   IN r_vbeln
             AND   a~posnn   IN r_posnn
             AND   a~rfmng   NE 0
             AND ( a~erdat   IN r_erdat
              OR   a~aedat   IN r_aedat )
             AND   b~sdvbeln NE space.
          ENDIF.                " IF r_aedat[] IS INITIAL
        ENDIF.                  " IF s_counter_datapakid..
    *   Fetch Records into Interface Table
        FETCH NEXT CURSOR s_cursor
             APPENDING CORRESPONDING FIELDS
              OF TABLE t_vbfa
          PACKAGE SIZE s_s_if-maxsize.
    *   No More Data, Raise Exception
        IF sy-subrc NE 0.
    *     Close the Cursor
          CLOSE CURSOR s_cursor.
    *     Raise Exception
          RAISE no_more_data.
        ELSE.
    *     Move Extracted Data to Output Structure
          MOVE t_vbfa[] TO e_t_data[].
    *     Release Memory
          FREE t_vbfa.
    *     Sort Output Structure
          SORT e_t_data BY vbelv
                           posnv
                           vbeln
                           posnn
                           vbtyp_n.
    *     Delete Duplicate Records from Output Structure
          DELETE ADJACENT DUPLICATES
            FROM e_t_data
       COMPARING vbelv
                 posnv
                 vbeln
                 posnn
                 vbtyp_n.
    *     Increment Data Package Number
          s_counter_datapakid = s_counter_datapakid + 1.
        ENDIF.                  " IF sy-subrc NE 0
      ENDIF.                    " IF i_initflag EQ sbiwa_c_flag_on
    ENDFUNCTION.              
    Edited by: Dennis Scoville on Jul 16, 2009 8:29 AM
    Edited by: Dennis Scoville on Jul 16, 2009 8:29 AM

  • Error while extracting data from ODS using Infospokes - URGENT

    Hi all,
    I am extracting data from an ODS using infospokes and nothing fancy, no selection criteria but I am getting an error message saying
    Syntax error in row3(-> long text) Msg id = "RG" and msgno is 102
    Any ideas on how I can see what is the exact error and how to debug this?
    thanks
    Sabrina.

    Hi Sabrina
    service.sap.com can help you getting the details of your mesg.
    I found one OSS note suitable to your mesg. So just check out OSS note # 671097. I hope this note will be some help to you. If not go and chk in the OSS you can find some more.
    Here is the note details also
    <i>Symptom
    Error message RG102: 'Syntax error in &1, row &2 (-> long text)' appears in the request log of an InfoSpoke.
    Reason and Prerequisites
    The data source is an ODS object and the extraction mode is 'delta'. The cause of the error message is that the ODS extractor is unable to select the request ID (InfoObject 0REQUID) from the change log of the ODS object. However, the request ID is mistakenly provided in the field list of the ODS object on the InfoSpoke maintenance screen. --
    Solution
    Delete the 0REQUID InfoObject from the field list of the InfoSpoke and activate the InfoSpoke. As of the patch mentioned below, the request ID in the template tab is no longer provided.
    BW 3.0B
               Import Support Package 16 for 3.0B (BW3.0B Patch 17 or SAPKW30B16) into your BW system. The Support Package will be available once note 571699 with the short text "SAPBWNews BW 3.0B Support Package 16", which describes this Support Package in more detail, has been released for customers.
    BW 3.1 Content
               Import Support Package 10 for 3.1 Content (BW3.10 Patch 11 or SAPKW31010) into your BW system. The Support Package will be available once note 571747 with the short text "SAPBWNews BW 3.1 Content Support Package 10" has been released for customers.
    To provide information in advance, the notes mentioned above may already be available before the Support Package is released. In this case, however, the short text still contains the words "preliminary version".
    Refer to note 110934, which contains information about BW Support Packages.</i>
    Regards,
    Rohini

  • How to use Delta Update in InfoSpoke

    How to use Delta Update in InfoSpoke & to include in Process Chain

    Initialization / delta updates are what we do every day, and it is usually the update method of choice for most data targets. The delta mechanism ensures the consistency of transactional data. So if some data is wrong in the early stage of data flow, we have to not only correct the data itself but also the related records in subsequent data targets.
    Unfortunately, such data can't be avoided in daily extractions. In some situations, the data to ODS is correct but reports errors while loading from ODS to Cubes.
    Here is one example:
    Some FI documents transferred in R/3 with LSMW's background mode and one of the line items 'Negative posting signal' was inserted with 'x' while the right one should be 'X'.
    This line time stays cool in my ODS Z1CCWO01, but encounters errors while loaded into several Cubes when the process chain's running.

  • Error while extracting ODS data using Infospoke

    Hello Gurus,
    I am not able to extract any ODS data using Infospoke. Let me describe the step by step process:
    I have created one infospoke for ODS data and i am selecting a 'File' option in the destination tab of infospoke. We are trying to land this file over to BW Server (on the default directory DIR_HOME). When I start executing the Infospoke in a dialog mode, I am getting the following error in the monitor screen:
    - Editing or Reading of data packet cancelled
    - System Error: RSDRC/FORM AUTHORITY_CHECK
    - Extraction Cube: Error in DataManager API
    - Cancelled.
    I can see two files created on BW Server in the Transaction screen AL 11. But the data file is empty.
    Does anyone know, why is doing this?
    Is there any authorization restriction, for extracting this transaction data? (I checked my profile and I have all the authorization granted)
    Is there any directory size related restriction, which prevents to extract and land this data over to default DIR?
    I am able to extract the Master Data files but not ODS data. Why is that?
    any idea or step by step procedure will be highly appreciated.
    Points will be assign to helpful answer(s).
    thanks in advance.
    Maulesh

    check this link
    https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/ee14e25d-0501-0010-11ad-8eb2861a7ec0 [original link is broken]
    for the
    How to Extract Data with OPEN HUB to a Logical Filename

  • Use of Update Table in Delta Extraction ....

    Hi all ,
           I have a small doubt regarding why there is an update table introduced between statistical table and delta queue in delta extraction process ... why not directly extract data from the statastical table and put it in to the delta queue .....
    Kindly help me regarding this ...
    Regards ,
    Santosh ....

    Hi Santosh,
    I think it is related to resource, batch and memory, problem. Infact you can use only delta queue if you select direct update, but you use this kind of update only for huge amount of data produced in a short period of time.
    The two queue let you divide transaction moment to batch collection moment.
    Hope this help.
    Ciao.
    Riccardo.

  • Delta (Extraction mode) for Infospoke on Multi provider

    Hello SAP-BW gurus,
    I want to develope a Infospoke on Multiprovider to implement the delta extration mode. Right now it is working for Cube but not for Multi provider. If anybody implemented this for Multiprovider, Please help me.
    Thanks in advance.
    Regards
    Prabhu

    Manga,
    Yes you are right, we can extract data from Multiprovider.
    I am doing that from past one month but it will work for only full update (Extraction mode). I want delta extraction mode on multiprovider.
    Regards
    Prabhu

  • InfoSpoke Delta Extraction

    I have two InfoSpokes in Production (NW 2004) with Delta as update mode.
    Source – ODS
    Target     - DB table
    The Business is asking for a 2years of historical data. I was testing this scenario in QA (the order in which the steps were performed)
    1.     Changed the update mode from Delta to full (applied filters in selection tab so as to restrict data to only two years)
    2.     Data was successfully loaded and now the update mode is restored to Delta
    3.     For the First InfoSpoke, Delta extract was 0 records (success),
    4.     For the 2nd InfoSpoke, Kicked off extraction, this terminated with the following Dump
    Dump with Message type X
    Message classe...... "BRAIN"
    Number.............. 299
    Variable 1.......... "RSBLOGSTATE"
    Variable 2.......... "STATE_CHECK"
    Can anyone throw some light here, full points assured.

    Hi Sandy,
    OSS 971386 might give you some lead.
    Rgs,
    Amol

  • When do we use Infospoke?????????????

    Hi Experts,
    Can anyone please tell me the exact client reqirement when we use Infospoke to extract the data from the data targets.. Iam expecting a real time example.. please help me out...
    Immediate resopnse will be very helpfull..
    Thanks in advance,
    Chintu..

    Hi,
    Infospokes are used when you want to transfer data in BW cubes, objects or ODS to another BW object or to an external system.
    ex. Say I've another instance of the Prod system and I've a Sales cube that has data for all Sales orgs. In the new instance, I only want data for certain Sales orgs. So instead of loading all the data all over again, I only use infospokes with the filter for those sales orgs to extract data to the new BW cube. In this case the data would be downloaded to a file and then uploaded. But in the same BW system, you can directly download this data to a table.
    Another ex would be, if I want to extract the BW data every quarter to a local datamart. Then I would extract the data using infospokes to a flat file and then transfer the flat file through some interface to the local datamart.
    Infospokes give you flexibility in data extraction as they allow you to do a full or delta extract. Also you have the option of writing logic using BADIs in the infospoke while data extraction.
    Cheers,
    Kedar

  • Hierarchy Extraction using Open hub Destination

    Hi,
    I need to extract hierarchy data for Application code(YAPPLCD) using OHD. In the Hierarchy there are 4 components(Industry, Market, Application Group and Application Code). i need to get all the 3 details for the Application Code(i.e to which Indusrty does it belong, Market and Application Group).But HIerarchy table is having one record for each apllication code, Market, Application Group, Application code.
    How to get relevant data for the application code?
    My file format should be:
    Appl.Code | Appl.Group | Market | Industry.

    Hi Suma...
    The SAP Open Hub service enables you to distribute data from an SAP BI/BW system into external data marts, analytical applications, and other applications. With this, you can ensure controlled distribution using several systems. The central object for the export of data is the InfoSpoke. Using this, you can define the object from which the data comes and into which target it is transferred, leveraging SQL Server Integration Services (SSIS) as the transfer/transform mechanism. 
    SAP BI objects such as InfoCubes, ODS objects, or InfoObjects can act as open hub data sources. You can select database tables or flat files as open hub destinations, and then use those destinations as actual sources within SSIS.  To automate the extraction using SAPu2019s Open Hub Service, youu2019ll need to setup a process chain. Note that both a full and delta modes are also available as the extraction mode.
    As stated already with direct extraction from SAP R/3, once data is extracted out of SAP NetWeaver® BI (SAP BW), the destination of that data could be any relational database (such as SQL Server), and then reports (from SSRS) and multi-dimensional cubes (from SSAS) can be created from that database data.  The resulting SQL Server reports/cubes could then be used within the Microsoft Business Intelligence delivery mechanisms, such as through Excel, SharePoint, PerformancePoint, etc.
    Hope this below link may helpful
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c08b1f70-6fb1-2b10-97a5-df4c503e03cb
    Regards
    Sudheer

Maybe you are looking for