Delta extractors

Hi,gurus,
I have two BW systems connect to one R/3 system, and both systems will extract data using datasource 2LIS_03_BF, is it possible? and will they have different delta queues which would not interfere with each other?
Thanks a lot.

Hi,
System takes care for that for the data source who use delta queue like LO data source
Since you will be doing two inits from the BW system for the data source...therefore system will push the LUW's to the delta queue by itself.The same job for colletice update will update both the queue in RSA7 at the same time.
Also for the FI-CO data source...if you see my reply I have mentioned that...you cannot schedule the delta at the same time but one after the another...this is applicable to all the FI data sources.So multiple BW connetivity is possible.
See this note 844222 and 775568 and they explain in the best way possible.... instead of me writing everything.They explain the caution you need to take for FI-CO data source and the multiple BW connectivety to the same source system.
Thanks
Ajeet

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.

Delta Extractor Is not picking changed values

Hi All,
When the values or texts in a PO are changed the delta extractor is picking up the changed values as deltas (provided the changes where done in PO Header or Item Overview) but when a PO values or text that are changed in the Item Details the delta mechanism is not picking up the changed values (the fields whose values are changed were initially not in the LO Cockpit Extractor they where added and the values to these fields are populated using an ABAP Program)
Is there a reason that Delta mechanism doesn't work for fields that are not delivered by the SAP Extractor or do we need to modify the code in order to collect these changed values by Delta Mechanism (Direct Delta as the Update Mode).
Please let me know if anybody came across the same problem .
Thank you all in advance.
Regards,
Dhanam

Hi,
this is another story.....
You'll have to
- enhance the PO items table (EKPO) with your fields
- activate the right customer exit for purchase orders (search in SMOD; or in this forum..) and populate your fields during this exit. if the field needs to be maintainable by the R3 user, you'll have find a SAP exit (again SMOD) in order customize one of the screen and populate your fields in R3.
- use another exit to populate the new fields to LO delta queue
- enhance your BW extract structure (done)
- and so on...
As you can imagine, the above get quite more complicated (an expert in MM shall support you) and it needs to be approved by the PM since you'll modify R3.
But that's basically it!
hope this helps...
Olivier.

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.

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.

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

Generic delta Extractors

Hi All,
I have a requirement to develop generic DELTA extractors. have extensively created generic ectractors using function module RSAX_BIW_GET_DATA_SIMPLE.
Can you please let me know how to create generic delta extractors with Steps.
Also How the tabel ROOSGENDLM us used in generic extractors..
Point will be assigned to useful answers..
Regards,
Bill

Hi Bill,
check this out: Generic Extraction via Function Module
You do not have to take care about that table, the service api will do that for your, you only need to take care about the information (delta date, timestamp or pointer) passed to the fm by the api and design your coding related to that information.
regards
Siggi

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.

Upper/Lower limit for delta extractor

Hi Experts,
Where can I see the configuration of the upper/lower safety limit for a delta extractor (tcode)? I would like to determine the configuration of one of our FI extractors.
Regards
Mark

Hi Chandra,
When checking the source system the extractor is extracted using FM RKE_BIW_GET_DATA_API. When we display the datasource and click on generic delta, we are getting an error "Specified table does not exist."
Forgot to mention this is a SAP delivered extractor for CO-PA.
Regards
Mark

Error with Generic delta extractor when checking in RSA3

Hi,
I have created one Test Generic Datasource based on Table MARA.Delta specific field I mentioned is LAEDA(Last changed On). After creating I have generated the datasorce also. But when I check the datasource in RSA3, I am getting error if Update Mode is "D". Error is "An error occurred during extraction". I am not seeing this datasource in RSA7 (Delta Queue).
If I say Update Mode is "F", then extractor is working fine.It is fetching some records.
Your help will be appreciated.
Thanks
Sirineni.

Hi Sirneni,
Is your Init load in BW successfull. Only after
successfull completion of init load in BW the data source appears in delta queue RSA7 in R/3. Also check whether any materials are being changed in R/3 because u r delta is based on last changed date.
Regards,
Prakash B

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.

ABR delta extractor and entries written to the delta queue

Hello Everyone,
We have an ABR extractor and it's behaving like this:
For example fields: PM Order Number, Post Goods Issue Date, Start Date, Work Qty, Projected Qty
Create the PM order the entry is written perfect to the delta queue:
10019987, blank, 04/29/2009, 100 PC, 90 PC
Now, if we perform a confirmation on the PM order we see the following:
10019987, 04/29/2009, blank, 0 PC, 90 PC
Now if we change something on the PM order header we see the following:
10019987, blank, blank, 100 PC, 0 PC
When this comes over to BW we don't get good results in our ODS.
Basically we don't get our Post Goods Issue date and Work Qty gets blanked out. Basically, the last change to the order gets written to the ODS and isn't correct.
Shouldn't it do the following:
10019987, blank, 100 PC, 90 PC
10019987, 04/29/2009, 100 PC, 90 PC
10019987, 04/29/2009, 100 PC, 90 PC
10019987, 04/29/2009, 04/29/2009, 100 PC, 90 PC------this gets sent as last record with all fields updated. We choose all these fields in the extract structure.
Thanks

Hello Martin,
Below is a snapshot of the delta queue (you can see the Cancel). Question: How do you control what record is updated and what others are not? We thought the cancel won't update and the others will in order they were updated to the delta queue (and that appears how it's behaving):
Scenerio #1 (sorry, can't remember sequence of steps done in system, but thought I'd mention)
Cancel, Order Number, Release Date, Posting Date, Material, Plan Qty, Confirmed Qty
blank, 10019987, 04/29/2009, blank, , 4415, 100, 0
blank, 10019987, 04/29/2009, 04/30/2009, 4415, 0, 100
blank, 10019987, 04/29/2009, blank, 4415, 100, 100
X, 10019987, 04/29/2009, blank, 4415, 100, 100
Scenerio #2
cancel, order, release date, posting date, material, plan qty, confirm qty
blank, 100019989, 04/29/2009, blank, 4415, 50, 0
then we perform a confirmation for 50 pieces and this is how the delta queue looks like
cancel, order, release date, posting date, material, plan qty, confirm qty
blank, 100019989, 04/29/2009, blank, 4415, 50, 0
blank, 100019989, 04/29/2009, 04/30/2009, 4415, 0, 50 <----
second line
Notice the second line now has plan qty at 0 and confirm at 50. Plan should always show 50 (or whatever the plan amount is. Something doesn't seem correct here??
Now, if we change something on the order header, we get the correct plan qty of 50 (and confirmed still 50), but then the posting date is blank. So when this comes over to BW we get correct plan and confirmed qty, but posting date is blank. This really makes no sense because if you have confirmed qty populated with a quantity then you have a posting date.
Thanks!

Standard Generic Delta Extractor 0CRM_SRV_COSTS - Delta stop working

Hello all,
Has anyone experienced an issue with the standard generic extractor 0CRM_SRV_COSTS (reside in SAP R/3 system) where its delta suddenly just stop working? The issue is that the datasource keeps extracting the same delta records and from RSA7 and SMQ1, only have the olda data records and no new data coming through (ie. from RSA7 data are only in the Delta Repetition).
The extractor uses Function Module and Numeric Pointer for the delta and I tried to investigate (via RSA2 and ROOSOURCE ) if there is a way to see what field is being used for the Numeric Pointer and how to trace it - but no luck so far.
Has anyone experienced the similar/same issue on other extractor which can provide some inputs?
Any ideas/suggestions will be very much appreciated.
Thanks,
Andy

Maybe someone knows if records in tables SMOXRELP_S and SMOXRELP should match perfectly? I see that table SMOXRELP lacks one record that I have in table SMOXRELP_S.

Generic delta extractors without timestamp!

Hi,
For a certain requirement, I have to develop generic extractors which should be delta capable. But unfortunately the source tables donu2019t have a timestamp; hence I canu2019t create delta enabled generic extractors using timestamp. Moreover most of the tables are standard SAP tables, which are used across different modules so it is not possible to introduce timestamp in these tables.
I am working on extractors for Business Partners in SAP Transaction Banking.
I have got couple of options:
1) To use the change pointers by activating CNS service in source system. It is possible to activate the service and set up the segments for standard and custom tables, from where I need to extract the data.
2) To develop the function module and create the generic extractors using delta queue functionality.
Issues: In the first approach, I have created an extractor and it is possible to recognize the changed records. But the issue is I need some kind of flag which tracks the information regarding last successful delta extraction for an extractor based on change pointers and standard SAP table. I am not sure how does standard extractors maintains this status and picks up new/changed records in delta functionality. Not sure how to achieve this.
In second approach I am not sure if it is possible to create generic extractors using delta queue and what are the complexities involved.
If someone has already worked on these areas, any inputs are most welcome.
Thanks and Regards,
Amit

Hi Amit,
I haven't worked on SAP Transaction Banking but I hope you can get most of Business Partner data in standard extractors. Try to look for some.
If you have to go for Generic extractor. there are 2 options:
1. Use BTE
[How To Create GDS which uses Delta Queue|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b68b99-022e-2a10-999d-c4dc9ec24a59]
2.Use FM based GDS
[How to Create Generic Delta|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33]
[Generic Delta Using Funtion Module |Re: Generic Delta Using Funtion Module]
You can also look for some numeric pointer from RSO2.
Hope it will help you...
Regards,
Ashish

Delta extractors

Similar Messages

Maybe you are looking for