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.

Similar Messages

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

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

How to get generic delta using timestamp field

Hi All,
i have created a generic datasource using tables vbrp,vbrk.mara,marc,knvv.. to get the sales data for planning.Here i have document created date and time.So i'm concatinating these 2 date and time fields into timestamp which is of format yyyymmddhhmmss.Finally i'm using this timestamp to extract data .
So is it the right way to pull the data using timestamp and what is the timezone i need to specify as the servers are in india only.
or any other way to proceed.
Thanks
Rao.

Hi Rao,
Delta based on timestamp based on generic datasource only works if any one of the tables contains timestamp field(not time and date fields separately).
I dont think by combining date & time fields will give you correct results.
Regarding time zone: Use SAP system time zone.
Srini

Generic delta creation with Extractor Starter Kit - BW Datasource option

Hi Rajesh, Rohit,
As per the wiki, http://wiki.sdn.sap.com/wiki/display/CPM/FAQ-DataExtractionforSpendPerformance+Management, the question:-
Do these starter kits have any support for delta (periodic data updates) after the initial load is completed?
A. Yes. Deltas are available (for all source objects that support delta mechanism) in both of the extraction options. You don't need to reload the full set of data, when you perform the periodic data updates.
I understand you can use the date range but this in my view is still a full load. We understand that you can create your own generic datasource based on the generated function module generated by generating the object, for e.g PO.
We have tried to do this for the object PO, thus the following:-
rso2 > create a new transaction datasource > base on generated datasource (Z_SADSERPPO) and use it's fm and extract strucutre :- Z_SAERPPO_DS fm , ZEXTR_ERPPO extr structure
When we goto to create a generic delta based on DATE_RANGE we get the error message ::-
Z_PDPOTEST: TABLES-paramter E_T_DATA for extractor Z_SAERPPO_DS is missing
Can you create a blog around this as we understand other customers have managed to create these deltas?
Best regards,
Pom

Hi Claudia,
That's fine, please continue to use the Z_SA_DEPD to generate the datasource. If you then do a rsa2 on this datasource, you can see the underlying function module and the extract structure for this which is also fine.
The bizarre thing is that through rso2 for this generated extractor, you cannot see the fm associated for this, hence why the generic delta is not working.
What we thought of doing and in line with the sap recommendation was to create a new transaction datasource from tcode rso2 and base it on the above function module and extract structure, but when we goto choose the date_range as the generic delta, it doesn't work and gives the error.
Am still waiting an answer.
Will keep you posted.
Thanks,
Pom

Handling Init/Full/Delta-Loading for a generic DS based on function-module

Hi Experts,
we need to build a generic datasource based on a function-module; and we would like to
implement a slightly different logic in the function-module depending on the data-staging-mode that was selected in the InfoPackage.
What we're missing is a possibility to distinguish (in the ds-function-module) if an init/delta/full-load was requested.
Could you please provide some information/hints about that topic?
Thanks in advance,
Marco

Hi Anjum,
we found an alternative that seems to be closer to SAPs idea of how it should work:
We check the status of the Init-Table (RSA7) - depending on the result
a) Init exists ---> Delta or Full
b) Init does not exist --> Init or Full
we check if the system itself passes a timestamp together with the data-request.
1) If it does so --> Delta/Init
2) If it doesn't provide a timestamp --> Full.
Summary:
a1 --> Delta
a2 --> Full
b1 --> Init
b2 --> Full

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

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.

Generic data source. Delta based on the changes in the CDHDR & CDPOS

Hello all,
I need to create a generic data source using fun module. This fun module has to execute delta based on changes in table CDHDR & CDPOS for purchase order info records.
can I use RSAX_BIW_GET_DTA_SIMPLE?
Is there any other way to implement this requirement?
waiting for ur suggestions ...........
Thanks,
zak.

hi
check the below extractor... it will extract status from both table.. u may not be required to build a generic one..
0TE_OBJ_STATUS_HIST

Generic delta

Hi experts
i have problem in loading generic delta , Generic delta have three parameters
1.Time Stamp
2.Numeric pointer
3.Calender day
and also upperlimit and lower limit
can any one explain me about this parameters and how it works in generic delta
Thanks in in advance

hi,
Yes we have these 3 delta types.
timestamp is used when the requiement of data load is depends on time ie hourly based.
0calday is is used when the requiement of data load is depends on date ie daily based.
Numeric pointer is uesed if u want to load delta based on some fields like sales order,material order.
Lower limit and upper limit used for not to miss the records.
regards,
kundan

What are the disadvantages of generic delta extraction

Hi all,
what are the disadvantages of generic delta extraction.
how function module generic extraction works.
Thanks,
Madhu.

hi madhu,
Pls refer ths,To learn more about Generic Extraction pls read BW350 book.
Gereric Extraction can be done in 3 ways.
If you go to transaction RSO2 in R/3 side, provide tech name for data source and click create.
you will get the 3 options.
1)From a DB Table
2)From a DB View
3)From Functional module/ Infoset Query
in first option you can directly give a standard or custom build talbe name. in second option you can select the necessary fields from more than one talbe(eiter standard or custom). In third option you will create a function module or Query to extract data. When creating function modules you can use standard function modules as a template e.g. RSAX_BIW_GET_DATA_SIMPLE.
see weblog : /people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
If you want to enable delta for generic extractor you choose the option delta and provide necessary settings.
Generic extraction is when your extraction is not satisfied by either BC or LIS/LO. It can be using a view / query/table/FM
Here the changed records can be isentified by :
1. Based on the date of creation or last change ( Delta based on 0Calday)
2. Based on the record number ( Numeric Pointer )
3. Based on time of change ( Timestamp)
real time examples would be
1. Master Record creation like customer ID creation
2. Timesheets in SAP PS
3. Invoive details / Sales Order Details.
Pls check this web logs for clear Idea.
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
Have a look at these threads too.
Tables
Transfer Structure
The steps for creating extractor using Function Module.
1. Create new Function group (if you have already not done so) in Se80
2. Copy Function module "RSAX_BIW_GET_DATA_SIMPLE" with suitable name.
3. Change the code that populate data.
Following table may give you the guideline for parameters.
Parameter Description
I_REQUNR (import) BW provides this request identifier. It is a system-generated identifier in the form REQU_XXXXXX. BW uses this same identifier in all function module calls that relate to a single load.
I_DSOURCE (import) The name of the generic extractor
I_MAXSIZE (import) The maximum number of records that BW expects to be in each data packet
I_INITFLAG (import) A Boolean flag that indicates if this is the initialization (first) call to the function module
I_READ_ONLY (import) A test flag not needed in most extraction scenarios
I_T_SELECT (table) This table holds any selections from the BW InfoPackage. The function module should examine these selections and only return data that matches the selections.
I_T_FIELD (table) This table holds the fields that BW requests
E_T_DATA (table) The function module fills this table with data records. These records then return to BW as data packets. This table has the same structure as the extract structure defined in the generic DataSource.
NO_MORE_DATA (exception) The function module raises this exception when no more data is available
ERROR_PASSED_TO_MESS_HANDLER (exception) The function module raises this exception if an error occurred during the extraction. It alerts BW to check for error logs.
Change following code to put the selection fields
Select ranges
RANGES: L_R_CARRID FOR SFLIGHT-CARRID,
L_R_CONNID FOR SFLIGHT-CONNID.
Change following to populate data
OPEN CURSOR WITH HOLD S_CURSOR FOR
SELECT (S_S_IF-T_FIELDS) FROM SFLIGHT
WHERE CARRID IN L_R_CARRID AND
CONNID IN L_R_CONNID.
ENDIF. "First data package ?
Fetch records into interface table.
named E_T_'Name of extract structure'.
FETCH NEXT CURSOR S_CURSOR
APPENDING CORRESPONDING FIELDS
OF TABLE E_T_DATA
PACKAGE SIZE S_S_IF-MAXSIZE.
Some more links:
Re: functionmodule
Re: FM for G. extractor
with hopes
Raja Singh

RSO2 - Generic Delta

Hello Guys,
I have created a generic datasource using the rso2 transaction and I defined the aedat field (calendar day) as generic delta
my doubt as follow. When a new record is created it is transfered to bw, but if the same record is updated
I mean a numeric field like atnum. Is it transfered to bw as delta?
Regards,
Renato.

depending on the table, but aedat is normally the changed on date.
this date is only filled when the doc is changed. a newly created doc will have 00.00.0000 as changed on date.
so according to me you will only get changed doc not new ones.
options :
you can create a delta based on erdat. but this will not detect changed docs only new ones.
--> so you can create both and load to a dso (with overwrite). this way you'll have all new and changed records.
another option is to create a full datasource and use two infopackages:
a first one with aedat in eg last 7 days and another one with erdat in last 7 days. again load to a dso.
last (complicated) option : use a extractor based on a function module. in this case you need to handle the timestamp yourself in the code. you can search on the net for examples, as this has been discussed many times.
M.

What type of generic delta to use and what field?

Dear BW Gurus,
I am creating a generic datasource based on a view BSAK and BSIK (Accounts Payable tables). I am not able to determine what type of generic delta (numeric pointer, calender day or timestamp) should i use and what field in the table should it that be based on? All or any help is greatly appreciated.
Thanks
Raj

CALDAY on field BLDAT (in both tables) seem an obvious candidate.
Added - You will need help from functional people (or you can try it in ABAP forum) to determine which date field is updated with the system date when these tables are updated with SAP txns (some hint can be had by looking at the data)- the fields of interest would be -
BUDAT
BLDAT
CPUDT
It is almost certain that CALDAY is the only option you have for delta type, and one of these three fields will have to be chosen.
Message was edited by: Ajay Das

Generic Deltas vs. LO Deltas

Dear All,
I am learner of SAP BI/BW I have one query mentioned below
1) I would like to know the difference between Generic Deltas vs. LO Deltas u2013 when we used to prefer both the Deltas.
2) When did you go for Function module and let me know the real time scenario which you faced.
Regards,
Divyesh

Hi..
1) I would like to know the difference between Generic Deltas vs. LO Deltas u2013 when we used to prefer both the Deltas.
Generaic datasource is something which you create when the standard ones doesn't fulfill your requirement.....
To make it delta enable you should select some delta specific field.......which will work as a timestamp.......which will record the changes based on which the new or changed records (delta records) will get fetched......
You have to do the init......and then you can execute the delta.......
Here you are directly fetching data from some Application table, view, Infoset........
Or if the logic is complex..........means you have fetch data from multiple table you can go for a Function Module......
Now...LO deltas are different........here Set up table is mandatory..........because it cannot access data directly from the Application table......
First, you have to fill the set up table..........then run the init.........once the init is done..........after that changes will automatically get recorded in the Delta queue........but here also once catch is there........
Different Update modes are there...........if it is a Queued delta or Unserialized V3 update ..........then the changes and new records will get stored in the Extraction Queue(LBWQ) and Update table (SM13) respectively............then you have to schedule the Collective run in LBWQ to pull the records in RSA7..............only in case of Direct delta changes will directly get recorded in RSA7........
2) When did you go for Function module and let me know the real time scenario which you faced.
if the logic is complex..........means you have fetch data from multiple table you can go for a Function Module......
For an example..........for FI logic is quite complicated.........business specific.......if you just create a view it will not fulfill the requirement.........you will have some business specific logic..........
So in this case you have to go for a FM......
Regards,
Debjani....

Difference between Generic extraction and Generic Delta

Hi Experts,
Pleasee give of some information below query:
1) Difference between Generic extraction and Generic Delta.
2) How to achieve Generic delta.
3) When we go for Generic delta instead of generic extraction.
Advance ThankU. Points vl be assigned.
Thanks,
Ragu.R

Hi,
Generic delta is the delta load done using Generic DS.
Generic extraction
Usage:
1. When the standard extractors are not supporting the extraction what you need. If SAP does not have a standard extractor for your need to get data from R3, you would have to go for generic extractor.
2. If you create a custom object say by combining certain base tables in R3 say custom tables ZTAB1 and ZTAB2. These two tables are not SAP provided tables and there will not be any standard extractors. So cases like this you will have to go for generic extractors.
How:
You have to use RSO2 transaction and you can also set delta based on, one of the three characteristics such as timestamp, calday or pointer (a sequence no).
once you create it and activate it. The extractor will be available in ROOSOURCE - (table in R3 where all the data sources are available).
Refer:
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
http://help.sap.com/saphelp_nw04/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
Generic Extraction via Function Module
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
thanks,
JituK

Generic delta based on timestamp ?

Similar Messages

Maybe you are looking for