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

Similar Messages

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

Generic delta extractor on view with ALE

Hello.
Extractor 0RT_WRF1_ATTR has type V and generic delta setting Numeric Pointer. Generic delta field is empty. Delta Process = A (ALE Update Pointer (Master Data)). ALE delta setting includes all fields of extractor structure. But changing one of these fields doesn't push new records into datasource.
Can you please explain, how generic delta works with ALE pointers аnd why no data is delivered?

CC,
Check on deletion data available in table(with any indicator updated) or not available in table.
If not available, you can not get delta through generic datasouce.
Hope it Helps
Srini

Generic delta extractor for BW

Hello people!
I'm developing an extractor for BW with Generic delta with the field AEDAT.
In function module for the extractor, how can I identify this delta?
I have to select the table ESSR with this field and I don't know how to identify this field.
Thanks in advance!
See ya!

Define a range field like
ranges : l_r_aedat for <tabname>-aedat.
In your FM
LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'AEDAT'.
MOVE-CORRESPONDING L_S_SELECT TO L_R_AEDAT.
append l_r_aedat.
Then when you do selections :-
Select * from <tabname> where
and aedat in l_r_aedat.

Generic Delta based off TimeStamp field is extracting full load

I have a generic delta in place which is extracting a full load every time instead of only extracting the changes.
I have created a generic delta based off a timestamp using a "Last Changed by" field of type Dec15, format YYYYMMDDHHMMSS.
This datasource is populated via a FM which is only used to update two fields, all other fields (including last changed by field) are taken straight from the source table. Entries to the last changed by field are entered like this:
20080310021530, then show up like this: 20,080,310,021,530.
All relevent entries are showing in the tables ROOSOURCE, ROOSGENDLM, and ROOSPRMSC. There is also an entry in RSA7, status Green, Total = 1, and Status is showing the correct Delta relevent field as well as the correct timestamp of the last extraction.
The entry in ROOSGENDLM contains:
Current Pointer Repeat Pointer
20080320091503 20080320091653
Yet every time I extract a "delta" from BI, it pulls a full load.
Does anyone have an idea of how I can get the generic delta to work properly? I'm using 7.0 transformation/DTP. This field in BI uses a routine to convert the timestamp to a date field. Any help is greatly appreciated.
Thanks!

I think I found the issue. This timestamp is UTC timestamp, and until we implement SP13 (which is being onboarded in a week), this type of timestamp is not delta-relevent. Only timestamps on the local application server are delta-relevent pre-SP13, which can cause issues if the time is updated in a different timesone (to the east) of the application server.
The following note corrects this issue:
1073871
Edited by: Cote Adams on Mar 20, 2008 4:59 PM

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

Generic delta based on timestamp ?

Hello BW Experts,
For a generic datasource involving the sales order data what is the best option for the delta type timestamp / calender day / numeric pointer. I am in the opinion of the timestamp as the records are based on timestamp. let me know if I correct.
Thanks,
BWer

hi,
yes, it's depend on the extract structure (your table/view/fm), F1 info :
1. Time stamp - The field is a DEC15 field which always contains the time stamp of the last change to a record in the local time format.
2. Calendar day - The field is a DATS8 field which always contains the day of the last change.
3. Numerical pointer - The field contains another numerical pointer that appears with each new record.
hope this helps.

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.

Incorrect TimeStamp in Generic Delta (UTC Issue)

Hi,
I have a problem regarding a generic delta extractor. The pointer stored in rsa7 (ROOSGENDLM table) is not UTC but system time. As standard tables store the timestamp using UTC format the delta extractor is not picking up the correct data.
Do you know a solution for this?

Hi,
Thanks for your reply. However I think that unfortunately this solution is not enough
For example:
I execute a delta. My TimeStamp is registered as UTC +2: 20080612160000. (Here I have the error, it should be in UTC)
Now I modify a record in R3 and it is registered with timestamp UTC: 20080612140000.
If I execute a delta it will take all the records higher than 20080612160000. Therefore my modification will never be uploaded.

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.

Generic delta with function module

Hi Gurus,
Is it possible to create a generic DataSource with delta support using function module following the queue delta mechanism (u can get some function moduel in MCEX function group, and check the outbound delta queue before and after update in transaction smq1.
I can store the delta data using qRFC and collective update mechanism. but I don't know how to create a generic data with delta and how to attach a rfc destination (& logical system) to the data source. The Source system information is stored in the table "ROOSGEN". Is there any configuration setting required to do the same.
Regards,
Jugal

Jugal,
What I understand you to be asking is if it is possible to create a generic delta extractor which uses the delta queue. If this indeed is your question the answer is yes.
First you need to create your data source so it is visible via tx RSA5 and need to make sure that the delta type (ie ABR, AIM)is set appropriately for the datasource.
The issue however is determining from where you will associate your delta hook (when will you write to the queue)? I have in the past utilized BTE's, Business Transaction Events to write information out to the delta queue, you can see a list of available BTE's in your system via tx FINF.
Once you find a place to write your deltas from you call the below FM with the appropriate datasource.
RSC1_TRFC_QUEUE_WRITE.
Once you have done this the standard BW extractor for deltas will pull the information from the delta queue. But from what I understand you just want to know how to associate the data with the delta and that is the FM listed above.
Hope this helps,
Cheers,
Scott
> Hi Gurus,
>
> Is it possible to create a generic DataSource with
> delta support using function module following the
> queue delta mechanism (u can get some function moduel
> in MCEX function group, and check the outbound delta
> queue before and after update in transaction smq1.
> I can store the delta data using qRFC and collective
> update mechanism. but I don't know how to create a
> generic data with delta and how to attach a rfc
> destination (& logical system) to the data source.
> The Source system information is stored in the table
> "ROOSGEN". Is there any configuration setting
> required to do the same.
>
> Regards,
> Jugal

How to deal with delete record in generic delta of generic datasource

Hi,
Anyone can give me suggestion about the delete record in generic delta of generic data. I need extract data with a generic datasource and hope deleted record in datasource also can be "delete" in next delta extraction. I do a test with generic delta. It seem that the delete record can not be updated in ODS. but updated record can be updated in next delta extraction.
How dose BW generic delta deal with the deleted record with generic delta mechanisim? Or how can I use generic delta mechanisim to realize that BW "delete" the deleted record of source system in ODS with delta extraction?
Thanks in advance!
Billy

Delete is not supported in delta mechanism of generic delta extractor. You will need to add a workaround for that.
- Capture the deleted records somewhere (maybe enhance the txn deleting the record so the key is written to a Z table). Take these records to BW and manipulate the recordmode to affect deletion of corresponding record from ODS.
- If your generic delta is based on FM, and if the 'delete' is captured in change document tables, add the logic to check change document tables whether any records are deleted, and if yes, send those to BW with appropriate recordmode to achieve deletion.

Generic Delta Extraction via Function Module

Hello,
i need a help for a generic delta extraction based on a Function Module. As an example i take the function module RSVD_BW_GET_DELTA_DATA.
My generic delta extractor based on the field AEDAT - Change Date and i will extract purchase service orders and entry sheets.
In the sample function module the select for the extraction worked with the table ROBWQTSTAT, but this table ist empty after the initialization.
OPEN CURSOR WITH HOLD G_CURSOR FOR
      SELECT * FROM ROVERCUBE1
               WHERE COUNTRY IN L_R_COUNTRY AND
                     REGION IN L_R_REGION AND
                     KUNNR   IN L_R_KUNNR AND
                     TYPE    IN L_R_TYPE AND
                     GJAHR   IN L_R_GJAHR AND
Here the timerange calculated in form GET_TIME_INTERVAL is evaluated.
                     TSTMP   IN S_R_TSTMP AND
                     OBJVERS = 'A'.
I found the table ROOSGENDLM. In this table i found the field DELTAID with the last date of the extraction and the field REPEATID with the date for the repead-Update.
My Questions:
Is this the right way to build an generic delta extraction with an function module or must i install a coding in my function module for an update of the table ROBWQTSTAT?
Which settings are needed in the table ROOSOURCE for a generic delta extraction via function module?
Best regards
Uwe

Hi Uwe,
please have a look at https://weblogs.sdn.sap.com/pub/wlg/2415. [original link is broken] [original link is broken] [original link is broken] It might help
kind regards
Siggi
PS: We already had almost the same question here today.

Generic Delta with numeric pointer (Without safety interval and no field)

Hi
We have problems with Generic Delta extraction. Our previous Dev has created the data source with numeric pointer as the data source without any safety interval and without any field for numeric pointer selection even we have the date field (creation and change dates in view)....
He created the generic delta with numeric pointer and Additive delta selection on top of view (EKKO,EKPO and EKKN). So we are missing lot of records. Now I need to fix this asap, I have done generic delta with timestamp and cal day with change/creation date.
Now in order to fix our delta loads should I use the cal day as the delta pointer with change or creation date already available or is it ok to use numeric pointer with additive delta and safety lower limit as 10 or 20 with upper limit blank?
Also Should I use any field in the field nm section or is it ok to leave it blank ? Please advice...
Note: I checked the missing delta records in ECC and the change timing is in the afternoon and our load time is only night...We also have several other data sources with same settings (numeric with no safety and no field) but it is not giving any issues.
Thanks
Edited by: ganesh uttitti on Jan 26, 2011 10:33 PM

Hi Ganesh ,
I'm a little confuse,Why are you not use LO Delata for it?

Generic Delta with Timestamp Field

Dear SDN Team,
We changed one of our HR datasource from FULL to DELTA with Timestamp(TMSTMP)-Time Stamp(UTC).
Which Delta we need to take Timestamp(Local) or Timestamp(UTC)
Our Generic Datasource is based on Function Module.This data source contains HR Hours Data i.e Direct Hours & Indirect Hours.
With interval settings has
Safety Interval Upper Limit - 'Blank' .
Safety Interval Lower Limit - 1800
New status for Changed Records (Selected)
It is a HR Generic Data Source.
We are creating the records in PA30,PA40 and going to take the records from PA0000,PA0001
Delta type for this DS is "AIE" as our delta type process for our DS.
I am trying to load the INIT to Cube,but its not allowing to load,saying with 'AIE' delta type its not possible to load to cube.
I changed the delta type to 'ADD' then the safety interval limits changed to
Safety Interval Upper Limit - 1800 .
Safety Interval Lower Limit - Blank.
Additive Delta (selected)
Is it possible to load the Generic Delta Time stamp to Cube?
Please let us know what are the settings & delta type needs to be there to load the Generic Delta Timestamp to Cube.
Your suggestions are really appreciated.
Thanks and Kind Regards,
Lakshman Kumar G

Hi,
We used TMSTMP filed with Data element TZNTSTMPS with data type DEC Length 15 in Function Module & Extract Structure.
Default filed name is TIMESTAMP_UTC,Domain is TZNTSTMPS.
Generic Delta -
Filed name - TMSTMP
Timestamp (UTC) selected
With interval limits
Safety Interval Upper Limit 1800
Safety Interval Lower Limit
New Status or Changed Records selected.
Thanks and Kind Regards,
lakshman

Generic delta extractors without timestamp!

Similar Messages

Maybe you are looking for