Regarding generic delta numeric pointer

Hello gurus,
I have done changes in RS02 --> vbak table on field VBELN > using numeric pointer>new status of changed records.
I have set changes for Delta pointer too e.g 50000 in ROOSGENDLM .
I have entered sales data in VA02 transaction. Say document 50006 has been created. But records are not updated to delta queue during delta load in BW
For LO, we are scheduling job for updating records from extraction queue to delta queue.
Do we need to schedule any job?? So that new/changed data is updated to delta queue.
Please let me know
Thanks,
Sonu
Edited by: Sonu P on Oct 12, 2009 11:48 AM

Hi
1)It will count numeric pointers and if the changes in R/3 create a new record with a new numeric pointer which is different then the orginal record then it will get pulled as delta.
2)in numeric pointer option you can give the field name of the table which can be a any numeric or char field like document number.
3)If the posting is happening at the same time then depending upon the offset given it will come in the next load.
you will never miss any delta if lower limit is set properly.
4)If lower limit is 10 then the last 10 records get pulled again.Thats why you are asked to load such kind of delta loads to a DSO in overwrite mode.
5)use it only when you have a field like document number or a numeric number which is created when a record is changed or created.You can have a documnet number as numeric pointer if you intrested only in new records and not the changes happening to them.
To capture the changes you may need some other field like changed on date.
Santosh

Similar Messages

Regards Generic Delta

Hi Guys,
I have a small doubt regarding Generic Delta Extraction. In Generic Delta i choose Calday on Posting Date. And am getting data on Daily basis. Here My doubt is can I use this posting date in field selection in Info package. If not?Please give me clarification regarding the same.
Thanks,
Tg.

Hi Tg,
If I have understood correctly, Posting date has been chosen as the delta field in datasource.
I don't think you can use the fiield in infopackage selection because the field is used to extract delta for that generic datasource and the system doesn't allow us to put a filter on the filed which is responsible for delta .
If system wud have allowed us to put a selection on that field then correct delta will not be loaded in BI.
System can not allow us to play with deltas and hence the field is not avaialble for selection .
Hope it helps,
Manish Sharma

Geneic Delta Numeric Pointer

Hi,
I have to creating Generic Data Source based on the SAP CRM Table "CRMD_CUSTOMER_H:Transaction - Customer Extension " in this table doesn't have any time filed and cal day field, so i go for Numeric Pointer for delta loads.
This is the unique number GUID of a CRM Order Object :4D90ECFF75034191E1008000AC100A37.
but how to set the Safety intervals for these info object?
Thanks

hi,
Yes....... you are right......
I have created generic ds with numeric pointer without safety interval..it works fine.
Solve my problem
Thank you.

Regarding generic delta.

does any sap bw gurus know the answer to my doubt.
i have created 3 views from mm tables (EBAN,MSEG,MKPF,GLPCA) AND FROM THESE 3 views i have created 3 generic data sorses in r/3 dev server and transported to r/3 quality server and loaded from r/3 qlty server to ods with full update mode in infopackage.
now i want to load delta records for those geeric data sorses, what is the procedure. i have not selected the delta option while creation of data sorses but loaded into ODS with full update.now i want to get delta records, what is the process?
Suppose i have selected generic delta and given some field to get delta records in r/3 dev server, does it effect in r/3 qualty server or do i need to transport same recquest or new recquest for delta from dev to quality server?
this is very very urgent pls. points assigned.

Hi,
ODS may not let you load deltas if there are Full loads already loaded. So either you have to delete them or make them into Full repair using FM RSSM_SET_REPAIR_FULL_FLAG.
This you can decide after talking to users, if they are ok with the data unavailability during the reload, you can delete these data.
Then perform the changes (delta DS) in the DEV and transport it to QUAL.
Then the usual procedure, replicate in BW, perform init load and start deltas.
Hope this helps.
Thanks,
JituK

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

Numeric Pointer Option on Generic Delta Screen

Hi, I was just wondering if anyone could help with why the option for 'Numeric Pointer' on the 'Generic Delta' screen in datasources is missing. I only have the option for 'timestamp' and 'calendar day'.
Thanks

Hi,
If you are trining to create a Generic delta with FM, you can't find the option "Numaric pointer".
Please check this link.
[Generic Extraction via Function Module|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=%28J2EE3417500%29ID1674507050DB11515805598662912203End?blog=/pub/wlg/2415]
Regards,
Madhu

Generic Delta with Numeric pointer.

Hi Experts,
We are using a generic delta for a Standard Master Data Attribute Data Source. Since it is standard by default it has the Numeric Pointer and the Additive Delta in the settings.
When a delta extraction is done with this option it does not bring any changed records it just brings the newly added records.
We are not able to change to the other Delta options available in that screen.
Could you guys help us with this issue.
Thanks
Sandhya

Hi Harvinder,
The answer you gave was very helpful.Thanks for all your help so far.
Due to some restrictions from our BASIS team, We are not able to Check the 'Change Document' for (AEDAT) Changed on field. There are other fields in the same Data Source which are Delta Enabled and they also have the 'Change Document' Checked. Could we use one of those fields in our Delta. If yes what changes do we have to make. If you can, Can you give a brief step by step how to make the changes.
Also we are not able to change anything in the Generic Delta tab. At times it is giving an error, other times it does not get saved when we go back it is unchaged. May be we are doing something wrong.
Regards,
Sandhya

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?

How can we get changed records in delta in case of numeric pointer

Deall All,
Thanks to all of you gurus i have been able to Get delta update for my query.
There is one last issue how can i include changes records in my delta update when i am using numeric pointer for data selection.
or
It can only be doen by time stamp.
can you explain me details of using time stamp.
Thanks & regards,
Gaurav Sood

Dear Gaurav,
Here we have three options for delta updation:
Time Stamp:   If we want to update change in the records with respect to the time interval then this option is selected.
Calend. Day:   If we want to update change in the records with respect to day to day basis then this option is selected.
Numeric Pointer: If we want to update in case of record which is completely new with respect to Field name then we use this option.
And we have got some settings like:
Safety Interval upper limit:
This field is used by Data Sources that determine their delta generically using a repetitively-increasing field in the extract structure.
The field contains the discrepancy between the current maximum when the delta or delta init extraction took place and the data that has actually been read.
Leaving the value blank increases the risk that the system could not extract records arising during extraction.
Example: A time stamp is used to determine the delta. The time stamp that was last read is 12:00:00. The next delta extraction begins at 12:30:00. In this case, the selection interval is 12:00:00 to 12:30:00. At the end of extraction, the pointer is set to 12:30:00.
A record - for example, a document- is created at 12:25 but not saved until 12:35. It is not contained in the extracted data but, because of its time stamp, is not extracted the next time either.
For this reason, the safety margin between read and transferred data must always be larger than the maximum length of time that it takes to create a record for this DataSource (with a time stamp delta), or it must display an interval that is sufficiently large (for determining delta using a serial number).
Safety Interval Lower Limit
This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction.
For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems.
Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable.
Data Source Is Real-Time Enabled
The 'real time enabled' indicator determines whether a delta-enabled Data Source can be used as a supplier of data for a real-time daemon.
And there are two options provided like
1)     New Status for changed records:
If you select this option each record to be loaded delivers the new status for the key figures          and characteristics. DataSources with this delta type can write to ODS objects or master data tables.
2)     Additive Delta:
The key figures for extracted data are added up in BW. Data Sources with this delta type can supply data to ODS objects and Info Cubes.
Hope this helps u..
Best Regards,
VVenkat..

Generic delta has problem with delts pointer time stamp

Hi All,
We have generic delta data source with Delte pointer as Time stamp. We have not used any safety limits. We are loading the data to DSO and using Additive delta. But the problem is when delta flag is set, there might be a case where some records still being inserted to table with lower time stamp. These records are not being fetched in next delta.
We are planning to keep a safety upper limit of 5 min so that those records can not be missed. But we have a doubt as it is a Additive delta duplicate records will be loaded. If we make the delta to 'new status to changed records', it is going to work?? Any other things we have to check when we make this changes??
Thanks
Haaris

Hi
If you had selected additive delta then you can load data to DSo with addition mode only. No overwrite possible.
If you want to select new or changed status then you can load to DSO with overwrite mode only.
Additive or changed delta depends on your requirement because if you want to add data to the DSO then you can go ahead with additive otherwise you have to use DSO with overwrite mode only.
You can either give safety upper limit or lower limit but if you give safety lower limit then you can only load data to DSO with overwrite mode because there could be some duplicate records.
Hope it clarifies.
Regards
Sadeesh

How to identify which key figure will the numeric pointer for deltas?

Hi All,
I have created a numeric pointer for generic extraction ? but how to identify which key figure will the numeric pointer will use for deltas ?
how to identify the key figures which is suitable for numeric pointer. And the generic extraction is based upon the copa table?
Can anyone suggest me how the numeric pointer works and how to identify deltas are carried out at numeric pointer?
Thanks
Pooja

Pooja,
If you are using a generic extractor which is based on COPA table, then numeric pointer may not be the suggested delta extraction mechanism.
A time stamp would be the better one to use. In a time stamp, you can give a lower limit value of 300 seconds.. so that it will try to fetch the missed records.
Moreover, a delta would be based on a character, preferably a time char.
In your requirement, try to figure out the character on whichdeltas will be based.
Sasi

Numeric Pointer for delta

Hi guys,
can any key field be a numeric pointer will that be missing any deltas for the extractor and also what should be the safety lower limit for this.
Thanks,
Your help will be rightly appreciated

HI,
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.
So you can use any time related filed in this column.
Using timestamp we can run delta multiple times per day but we need to use the safety lower limit and safety upper limit with minimum of 5 minutes.
Thanks and Regards
Rajesh

0FI_AR_4-Delta Time Settings based on Numeric Pointer Time Stamps

Hi All,
For Numeric Pointersettings for 0FI_AR_4, I checked the table of DELTA settings, the time stamps are different and it says GMT IN BWOM2_SETTINGS.
So I am confused here whether for FI based on GMT timestamps or numeric pointer BAED on documents entered..
say user entered a DOCUMENT clearing ON mONDAY AFTERNOON, WE HAVE BATCH UPDATE on TUESDAY MIDNIGHT, WHEREAS the document not picked up on TUESDAY batch and so the document is still not cleared in OUR report whereas cleared in SAP..
whereas the same document CLEARED in wednesday midnight batch job...so it means there is a delay in picking up the document which is running every MIDNIGHT...
Does anyone clearly explain how its picking and why? hope it is not based on GMT TIMING...
Also I check another table, it has set the time limit of 2AM and whereas our TUESDAY batch runs before 2AM..whereas Wednesday batch runs after 2am, i am not sure whether it could be because of the above issue...

Hi Durgesh,
I checked this link..That's why raised it whether it really works based on the last part in the link based GLOBAL SETTING OF FI...
If it considers 2AM and check the same settings in my system too, it could be the reason, why my data doesn't pupulate on TUESDAY ..I AM THINKING... is my assumption right???
i am still waiting from our HQ team..will see whether that works or not..
then will let you know...

Generic delta not working with '0calday' change pointer

I have created a generic datasource based on a database view and extracted data with afull load infopackage into BI. Then, I configured the generic delta with a date field and 0calday type. Set the safety interval of 1 day as a lower limit. Saved the datasource in R/3 and Replicated and activated the datasource in BI. Done some changes to a record in R/3.
After that, I created an Init delta infopackage (with data) and extracted the data with the same number of records as extracted in the full load. Note that all these were done on the same day.
If I have done something wrong by doing it on a same day, I should get 0 records.
Why did I get the same data with a delta init package? I wonder the generic delta is configured correctly or not? Please tell me where I have gone wrong. Thanks..

Hi Shiva,
While running the delta init, you have option of without data transfer and, with data transfer.
I am sure, you used with data transfer and thats why got all those records same as full load.
U can use different options like.
1. DO the init without data transfer and then do the full load, and then run delta everyday for delta records
2. Do the init with data transfer then no need to do the full load and the subsequent delta will take care day onwards,
I guess your are good to do the delta load by tomorrow.
Thank-You.
Regards,
Vinod

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

Regarding generic delta numeric pointer

Similar Messages

Maybe you are looking for