Multiple Usage of a Delta Extractor from R/3

Dear all,
do anybody know if a Delta Extractor from one R/3 system could be used in different SAP BW Systems?
Many thanks
Didi

Hi Dieter,
your comment:
"e.g. 2 BW systems that should get the same data from one Delta Extraktor."
is very much possible.
The Initialize information in the source system (R3 system) is maintained in the Table ROOSPRMSC.
If you check the Key fields in this table , you will find
DataSource
DWH System  
Source system
An R3 system can supply a Number of BW systems via DELTA.
Cheers,
Praveen.

Similar Messages

  • Custom delta extractor: All data deleted in source table in R/3

    Hi everyone,
    I have made a custom delta extractor from R/3 to a BW system. The setup is the following:
    The source table in R/3 holds a timestamp, which is used for the delta. The data is afterwards loaded to a DSO in the BW system. The extractor works as expected with delta capability. Furthermore if I delete a record in the source table, this is not transmitted to the DSO, which is also as expected.
    The issue is this however: If we delete all data in the source table, then on the next load there is a request showing 1 record transfered to the DSO. This request does, however, not show up in the PSA, and afterwards all data fields in the DSO is set to initial.
    Does anyone know why this happens?
    Thank you in advance.
    Philip R. Jarnhus

    Hi Philip,
    As you have used generic extractor I am not sure how the ROCANCEL will work but you can check the below link for more information,
    [0RECORDMODE;
    Regards,
    Durgesh.

  • How to configure Environment Parameter BW_SPEC_USAGE to get multiple Usages

    We are extracting EHS data from R/3 to BW system. The Environment Parameter BW_SPEC_USAGE can allow only ONE Rating and ONE Validity Area. Our EHS is maintained for many different Ratings and Validity Areas. Does any experts know how to configure Environment Parameter BW_SPEC_USAGE to get data from multiple Usages (the combinations of Rating and Validity Areas).
    The default usage is PUBLIC: REG_WORLD (Rating: Validity Area), so we configure the default Usage as sort sequence 0. EHS data maintained for PUBLIC: REG_WORLD is then extracted to BW system successfully. Then, I try to create another sort sequence of  BW_SPEC_USAGE as CUSTOMER: REG_EU, but the data maintained for CUSTOMER: REG_EU has never been extracted to BW. I guess this may be the solution to carry multiple Usages, but not sure it is the correct way to do it. Plus, I don't know what to input to the field "Parameter Value" and don't know if the "Parameter Value" matters. 
    Does any expert have experience to configure Environment Parameter BW_SPEC_USAGE?
    Thank you in advance
    Tina Wu

    Hello Tina
    I have done a small review of this paramater. I believe by using this paramter there is no "further option".  But: to my knowlegde you can define several "extractors" (via customizing etc.) (e.g. Data related to 0EHS_PHRASE_TEXT Extractor.)
    You can define any type of extraktor. EHS does have some "standard extraktors" (please consult corresponding release information). In preparing a "customer specific" extraktor it is clear that you can do there what you would like to get. (retrieve data with several usages). We have done that recently successfully.
    take a look here:
    SAP NetWeaver -> SAP Business Information Warehouse -> BI
    Content -> Product Lifecycle Management -> Environment, Health and Safety (help.sap.com)
    With best regards
    C.B.

  • Short dump error when extracting delta records from R/3

    I am working on BW 3.5 and I am facing some short dump error when extracting delta records from the r/3 to BW.
    Below is the error message
    Kindly do the needful ASAP.
    Job started
    Step 001 started (program SBIE0001, variant &0000000024277, user ID BWREMOTE)
    Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
    DATASOURCE = 0ISCM_PAYMENT_01
             Current Values for Selected Profile Parameters               *
    abap/heap_area_nondia......... 2000000000                              *
    abap/heap_area_total.......... 2000000000                              *
    abap/heaplimit................ 40000000                                *
    zcsa/installed_languages...... DE                                      *
    zcsa/system_language.......... E                                       *
    ztta/max_memreq_MB............ 2047                                    *
    ztta/roll_area................ 6500000                                 *
    ztta/roll_extension........... 2000000000                              *
    2,454 LUWs confirmed and 2,454 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DAT
    ABAP/4 processor: MESSAGE_TYPE_X
    Job cancelled

    Hi,
    I look at the transaction ST22 to see which type of error has given you. Take a look at the notes to correct the error.
    Another option is to look at OSS notes, because the error is giving you a standard extractor.
    Greetings,

  • No records in delta extractor after change

    We have a generic delta extractor that is based on ztable filled by a scheduled load program.
    Last week I changed some records and then ran the transaction to fill the table and the program correctly filled the table and the extractor had the delta data.
    I then extracted a delta init to an ODS in BW where I had to manually change the QM status of the load from yellow to green and got the status messages that the timestamp had changed from 0 to xxxxxx
    Now after this init delta load, I went into R/3 again and changed the records.
    Ran the transaction to fill the ztable but no records come up in there.
    Also the extractor has no delta records.
    In VBAP I see the changed items but in 2lis_11_vaitm, no delta records.
    Any thoughts?
    Edited by: CC on Jul 1, 2008 12:33 AM

    Hi,
    We have a generic delta extractor that is based on ztable filled by a scheduled load program.
    Now after this init delta load, I went into R/3 again and changed the records.
    Ran the transaction to fill the ztable but no records come up in there.
    Also the extractor has no delta records.
    If I understand correctly, the load program did not add any records to  'ztable'.
    If that is the case the extractor running off  'ztable' would not deliver any delta records as there is nothing to deliver.
    If my understanding is right you should revisit the load program of 'ztable' to see why it is not filling 'ztable' table as you expect.
    BR/
    Mathew.

  • BW 7.3 ,can we extract delta data from mutiproviders using OHD

    Hi Gurus,
    My requirement is to extract the delta data from multiple infocube (more than one IC) using open hub destination to third party system. We thought of implementing BW 7.3 so that we can extract delta data from multiproviders instead of cubes to open hub destination...
    My question is:
    1.Is that possible to extract delta data from multiproviders using open hub destination.
    2.Is there any limitations?
    3.list of possible known issues from BW7.3 .
    Please suggest your valuble experience..
    Thanks in advance
    Vaish

    Hi Vaish,
    Yes you are right. In 7.3 we can extract data from MultiProviders using DTP.
    This is the new functionality in 7.3
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/304444f7-e02d-2d10-9c97-d5e3ecf09882?QuickLink=index&overridelayout=true
    check the 18th slide in the above PDF
    Regards,
    Venkatesh

  • Process for Flat file delta load from Application server to transactional??

    I want to do a flat file extraction in delta loads from application server and that should be loaded into a transactional cubes scheduling a process chain.
    Can any one help with ABAP code and step by step process for this?
    Thank you
    Devi

    Hi Devi,
    As per your explaination, you want to load a list of files from application server using process chain.
    You can do this with below steps.
    1) Create a Event and call event to run Process chain multiple times.
    2) Put all filenames in a file say, source-File
    3) Write a rooting to read filename from Source-File and trigger InfoPackage
    4) At the end of the process chain create new customized program which will delete first line from Source-File so that it will take next file in next run as well as delete currently loaded file. Once this is done trigger event again to start process chain again.
    Regards,
    Ganesh

  • Delta Extractors: To Add Timestamp to table

    Hi All,
    We have a requirement to make 0GL_ACCOUNT_ATTR to work in delta mode. 0GL_ACCOUNT_ATTR datasource is based on SKA1 database table .
    But with SKA1 table we dont have any timestamp field or calendar day fields.
    We have another requirement to make YC_CTTR_YCCOMPACC to work in delta mode. YC_CTTR_YCCOMPACC  is based on SKB1 table.
    But with SKB1 table we dont have any timestamp field or calendar day fields.
    Please let me know how to acheive this requirement.
    Thanks,
    Arun

    Hi,
    No need to do anything for the 0GL_ACCOUNT_ATTR datasouce. It is already delta enabled. I guess you are running full loads for some reason. You can do an init from BW and carry on with the delta loads afterwards.
    For the other extractor, from RSO2 change mode of datasource, datasource menu, ALE delta, give the details like extractor, change doc (SACH) etc. Replicate to BW and test the datasouce by doing init. Ask functional folks to make changes and do delta load and check if the changes are captured. I have never done this before. Try it and let us know if it works.

  • How to see deleted records in delta extraction from view

    Hi folks,
    i am currently reflecting about delta extraction from a view:
    The view contains a date field (change date) which is used to identify new or changed records.
    So the delta extraction of new and changed records works without problems.
    But what is happening with records that are deleted in the source system?
    My current understanding is that deleted records will not be shown in the view. Therefore the deletion is not visible in the extraction.
    - Is there a workaround for this problem?
    - How is deletion of records normaly handled in generic extractors? 
    - Is it impossible to extract a deletion when using views?
    any suggestions and help will be appretiated...
    bye

    Hello Florian,
    Generally records will not be deleted (until if you physically delete it from table) but will have a status deleted.
    So it doesn't matter whether you use view or tables the deleted records will be extracted through the view to update the BW data targets.
    Thanks
    Chandran

  • Support Package and Delta/Extractor functionality

    Hello Experts,
    We have been testing the New GL Totals Delta and Extractor functionalities. Previously when Support Packege 13 was installed, the Delta was bringing incorrect results.
    Now we are using Support Pack 15. Now if i post documents in ecc and upload to bi, the Delta is working properly and values match in ecc and bi.
    Could you please suggest if there have been any changes or upgradations in the New GL Totals Delta/Extractor functionality between Support Packages 13 and 15.
    Thanks and Regards,
    Labanya.

    Hi,
    Its always better to drain the delta queues before an upgrade.
    As a standard practice we drain the delta queues by running the IP/ chain multiple times.
    As a prerequiste we cancel/reschedule the V3 jobs to a future date during this activity.
    The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss.
    V3 collector jobs should be suspended for the duration of the upgrade.
    They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
    See SAP Notes 506694 and 658992 for more details.
    Page 17
    Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
    The SAP BW Service SAPI, which is used for internal and ‘BW to BW’ data mart extraction, is
    upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the
    upgrade to avoid any possibility of data loss.
    upgrade preparation and postupgrade checklist
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
    /message/3221895#3221895 [original link is broken]
    OSS notes 328181 and 762951 as a prerequisites.
    Failure to follow the instructions in those notes may probably result in data loss.
    https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
    /thread/804820 [original link is broken]
    thanks,
    JituK

  • Creation of Function Module Delta Extractor

    can anybody Explain me ,
    How  anybody  handle delta in FM extractor . have you codes  .
    Any body provide me Codes of Z  FM Delta Extractor .
    Edited by: skarya2003 on Dec 7, 2009 10:22 PM

    Hi,
    One way of handling delta is to use table ROOSGENDLM. This table stores the information of last load for a data soure.
    In the FM code, we and read this table to get the time stamp to last load and can use that value for loading delta if delta is based on creation or changed date of document.
    Here is one sample code:
    READ TABLE g_t_select INTO l_s_select
                                         WITH KEY fieldnm = 'ZDATE'.
            IF sy-subrc EQ 0.
              CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET'
                IMPORTING
                  OWN_LOGICAL_SYSTEM             = lw_slogsys
                EXCEPTIONS
                  OWN_LOGICAL_SYSTEM_NOT_DEFINED = 1
                  OTHERS                         = 2.
              IF SY-SUBRC EQ 0.
                SELECT SINGLE *
                         FROM roosgendlm
                        WHERE oltpsource EQ <Data Source Name>
                          AND slogsys    EQ lw_slogsys.
                IF sy-subrc EQ 0.
                  lw_date = roosgendlm-DELTAID.
                ENDIF.
              ENDIF.                        
            ENDIF.                       
    Open cursor for Sales Orders
            OPEN CURSOR G_CURSOR FOR
              Select VBELN
                     ERDAT
                     SPART From VBAK
              Where  VBELN IN l_r_vbeln
              AND   ( ( ERDAT GE lw_date ) OR ( AEDAT GE lw_date ) )
              AND    SPART IN l_r_spart.
    I hope this should help you.
    Regards,
    Gaurav

  • Multiple Usage unchecked but shadow table still updated with IUUC_PROCESSED = 0

    Hello,
    We changed several MT_IDs by unchecking the Multiple Usage checkbox:
    The OLI functions have been redesigned correctly and all Run Time Objects also. The IUUC_PROCESSED field is now conditioned to empty in the Abap statements:
    *** get records from logging table
    SELECT * FROM /1CADMC/00001360 CLIENT SPECIFIED
      INTO TABLE _IT_IO_S_/1CADMC/00001360 UP TO I_NUM_OF_RECORDS ROWS
      WHERE (_WC_S_/1CADMC/00001360)
       AND IUUC_PROCESSED = ' '
      ORDER BY
        IUUC_PROCESSED
    TABNAME
    VARKEY
    IUUC_SEQUENCE
    %_HINTS MSSQLNT 'TABLE &TABLE& abindex(IUC), READCOMMITTED,READPAST'.
    However the records in the table are still updated with IUUC_PROCESSED equals to 0:
    We use DB6 09.07.0005 and ECC 6.0 with DMIS 2011_1_731 0004 SAPK-11604INDMIS DMIS 2011_1.
    Any idea?
    Regards,
    Laurent

    I have the "techie" answer for all of you. According to the tier 2 support at Norton Help Desk, the latest live update from Norton "utilizes Visual Studio 2012 which enables SSE2 instructions" and my processor can not handle that.
    He said they are "working on a solution" and offered to reply back on Wednesday / Thursday this week if a solution could be found...

  • What happend to past delta data if we delete Delta INIT from Cube? safe ?

    Hi Friends,
    we have a cube where delta data is loaded daily from ODS.
    So, cube have many delta requests and data is compressed.
    Now have some problem and need to delete Delta INIT from this Cube and run fresh delta INIT again into Cube from ODS. Is that safe ?
    If we do this...is there is any problem with past delta data availble in the Cube?
    Please confirm..
    Thanks
    Tony

    Hi,
    I told you to check this before deleting the init as it very tough to manage it after that.
    Now those delta request are missed and I dont think can be retrieved without doing a full repair with proper selection.
    If you do a new init then there should be no request without a check for data mart status??
    So you found it before deleting the init??Then you should not have deleted the init as I told earlier.
    The only option is too reload the whole histroy again if you are not able to load it through selections in infopackage.
    First do a selective deletion from the cube for the same selections and then schedule the full load for those selections from DSO.make sure these selections cover the whole scenario.
    You cannot do anything else now to correct it.
    If you data is not huge in cube then delete the whole data and reload it.
    Schedule multiple loads from the DSO at the same time through different infopackages.
    this will save time as weill will do the loads in quick time.
    Thanks
    Ajeet

  • Why isnt there a delta extractor for CCA Commitments

    Can someone explain why there is not a delta extractor for CCA Commitments; whereas there is one for CCA Actual - Line Items?  
    Both CCA commitments and Actuals are stored in table COSP; which has no date/time stamp.  Somehow the CCA Actuals can be delta enabled, however.

    The actuals are actually taken from COVP - this is a view across COBK and COEP (from memory - I could be wrong)
    COBK has the timestamp that is used - there is no requirement to take changes to CO documents as you cannot change any important information in CO relevant for BW
    If you do - then the change is not reflected in BW
    Regarding why no delta for commitments - I can not comment - I avoid this like the plague
    Have you see Note 721519 - Delta update for FI-FM DataSources

  • Problem with 0FI_GL_4 Delta extractor

    hi everyone,
    I have encountered a problem when using 0FI_GL_4 delta extractor.
    As I had changed the settings in table BWOM_SETTINGS according to note 485958, the datasource should be able to extract FI lines up to the day I run the extractor.
    Here is the problem:
    At 1st March, 01:18 am, I ran the extractor and get some records.
    I found that FI lines with createdon date later than 29th Feb 16:00 were not extracted to BW. According to that note, shouldn't I get all FI lines created on 29th Feb?
    After 30 minutes, I ran the extractor again. These records came to BW this time. That's strange.
    My settings in table BWOM_SETTINGS:
         EXTLOG     
         ORGSYSONLY     
         NOTSSELECT     
         OBJSELSIZE     X
         FLAG_AL     
         OBJCURTYPE     10
         BWFILOWLIM     19910101
         BWFISAFETY     1
         BUFFERREF     
         OBJSELSICO     X
         BWFITIMBOR     020000
         BWFIOVERLA     X
         DELTIMEST     60
         PRICECOMP     X
    Thanks for your help!

    Hi,
    I agree with Murali as your are extracting data before 02.00 AM the data till yesterday will be extracted.
    Check the below link for more information,
    [http://help.sap.com/saphelp_bw33/helpdata/en/af/16533bbb15b762e10000000a114084/content.htm]
    but as per your another post the second extraction happened before 0200, just cross check one thing that the time noted was not from local machine but was from app server.
    Rgards,
    Durgesh.

Maybe you are looking for