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

Similar Messages

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

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.

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..

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...

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

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?

Numeric Pointer not available

Dear all,
I am trying to configure my generic data source for delta update through a numeric pointer but there's only timestamp and calendar day available.
Anybody out there who knows this case?
Many thanks in advance.
Regards
Tobias

A numeric data pointer is a field in your table that contains sequential numbers. The pointer works by noting down the last pointer value transferred. The next delta takes the values appended to the table since the last pointer value.
If you have timestamp and/or date field, that would be better because the are already there (you don't have to change the table). If you have a timestamp field (not a time field but a time and date field), then I would use that since it is the most accurate.
Brian

Generic Queue not necessarily for delta only

Hi,
I am using the R3 transparent table to store the data extracted, and I am using it to create the datasource from RSO2 => 'Extraction from DB view'. Is there a way to write the data from this table to a queue on the R3 side every time the data is extracted?
Thank you

Dear Crysral Smith,
As Sat was explaining:
1) If your datasource setup (in RSO2) had the suitable
   delta handling mechanism....the R3 system will write
   the delta records to the suitable queue
   "automatically".
2) You would have chosen a suitable timestamp or date
   or a numeric pointer type field for the sytem to base
   the delta mechanism.
Check the link:
   Need "Generic Data source using Function module" to handle Delta
Good luck, BB

Numeric Value for Radio Buttons

This should be easy for the experts:
I got a bunch of 10 exclusion groups containing 3 radio buttons each. Every radio button got a numeric value associated, meaning the user is picking a numeric value by selecting a given radio button pretty much like the tests on the magazines in which the people pick options like "single= 10 points, married=5 points, engaged=1 point)
In the bottom part of the same form I got a table of one one column and 10 raws sumarizing the 10 already mentioned above.
The aim: to place the value coming from the radio button in the specific cell of the table.... in short, I want a script that allows me to palce the value of the selected radio button somewhere else in the same form, a numeric field for example.
Thanks,

Hi try67,
Thank you so much for your help. Your code has brought me one step closer, I would never have gotten even this far without it!
Initially, it was giving me and error, so I added a ")" and now it does display "Mastery", but I cannot get it to display the other two ("Acquiring" and "Practicing"), it just displays a blank space but does not give me an error. I tried to fix it on my own by searching for some help, so I found and started playing around with jsbeautifier.org and JSLint. However, since I really don't know much about coding or syntax I hope these were not harmful. So now the code looks like this:
// name for the text box field;
var cTextBox = "Firm-Wide Talent Strategy Knowledge - Totals";
// get the value of the field with the name in cTextBox;
var sTextBox = +this.getField(cTextBox).value;
if (sTextBox >= 1 && sTextBox <= 2) {
    event.value = "Acquiring";
if (sTextBox >= 3 && sTextBox <= 4) {
    event.value = "Practicing";
if (sTextBox >= 5 && sTextBox <= 6) {
    event.value = "Mastery";
} else {
    event.value = "";
Do you know what I might be missing that prevents "Acquiring" and "Practicing" from displaying?
Thank you so much again for your help,
Chris

Need for locking system for delta initialization (BW-R3-LO)

Hello all,
Could someone please help me with the following,
Please be kind, don't get impatient for the lengthy post
1. Do we need to lock the system (or posting-free the system) to do early delta initialization or not? If yes, please explain me how that work?
2. Someone somewhere mentioned that early delta initialization is not preferable compared to normal delta initialization, even though early delta initialization is advantageous. Why is that so?
3. Imagine, while scheduling Queued Delta Init or un-serialized V3 delta Init, if I choose certain end date and time (say, 10pm, 12-31-2007) for the records, then all the records till that point would be loaded to setup tables and all the records after that point of time will be moved to extraction queue or update tables. My question is, if this is true why would we ever need to lock the system during setup tables filling?
    If you say the records after that particular time and date (10pm, 12-31-2007) will not be collected in extraction queue and update tables, why don't we do the following
             a). say, I do full load with end date and time (10pm 12-31-2007)
             b). Next, I do delta init with start date and time (10pm 12-31-2007) (this time I lock the postings)
         If we do this way, we can actually reduce the down time of the system. Is my conclusion right?
         If you say it's not practicable as some transactions' saving time differs from time stamp and some transactions' delta is even measured by pointer.......if this is the case we can use Delta offset. What do you say about this?
4. How this scenario differs to early delta initialization?
Your responses would be greatly appreciated
Thank you

Hello,
1
>
curious maven wrote:
> Do we need to lock the system (or posting-free the system) to do early delta initialization or not? If yes, please explain me how that work?
No,you don't need to lock the Source System which is the advantage of Early Delta Init.
With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the posting of data in the source system. The option of executing an early delta initialization is only available if the DataSource extractor called in the source system with this data request supports this.
[Business Information Warehouse 3.0 Overview Presentation|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9a0e9990-0201-0010-629b-dc2735cb9c81]
2
>
curious maven wrote:
> 2. Someone somewhere mentioned that early delta initialization is not preferable compared to normal delta initialization, even though early delta initialization is advantageous. Why is that so?
Early delta is not supported by all the extractors. See Lo Extraction
3
>
curious maven wrote:
Imagine, while scheduling Queued Delta Init or un-serialized V3 delta Init, if I choose certain end date and time (say, 10pm, 12-31-2007) for the records, then all the records till that point would be loaded to setup tables and all the records after that point of time will be moved to extraction queue or update tables. My question is, if this is true why would we ever need to lock the system during setup tables filling?
>
>     If you say the records after that particular time and date (10pm, 12-31-2007) will not be collected in extraction queue and update tables, why don't we do the following
>
>              a). say, I do full load with end date and time (10pm 12-31-2007)
>              b). Next, I do delta init with start date and time (10pm 12-31-2007) (this time I lock the postings)
>
>          If we do this way, we can actually reduce the down time of the system. Is my conclusion right?
>
>          If you say it's not practicable as some transactions' saving time differs from time stamp and some transactions' delta is even measured by pointer.......if this is the case we can use Delta offset. What do you say about this?
This is applicable to Generic Delta where you can set the Safety Interval (Upper Limit and lower Limit) for the extractor based on ALE Pointer, or Time Stamp or Calendar day.
If you excute a extractor with early delta init, during the setup table fill, the delta records will be directly written to the delta queue. The delta management handles these functionality.
[How to Create Generic Delta|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33]
[SAP BI Generic Extraction Using a Function Module|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33]
4
>
curious maven wrote:
How this scenario differs to early delta initialization?
If you do a Init without Early Delta init, then the user cannot post new documents and you have to either schedule in the weekend or request for a Source System downtime.
But if you use Early delta , then you don't need the source system down time and the user can post new records during the init, which will be written to the delta queue directly.
[How to Minimize Effects of Planned Downtime (NW7.0)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/901c5703-f197-2910-e290-a2851d1bf3bb]
[How to Minimize Downtime for Delta Initialization (NW2004)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5d51aa90-0201-0010-749e-d6b993c7a0d6]
Thanks
Chandran

Is Downtime necessary for delta methods?

Hi all,
When we do initialization for full updates or delta initialization, downtime is necessary.
Is downtime necessary for delta updates also? Whenever a document is posted to an application tables, will it come directly to extraction queue, update table or delta queue(depending on delta method we chose)? Or do we need any downtimes?
Please explain me in detail...
Thanks.

Hi Komal,
You require Downtime only during a SETUP run, after the Successful Setup run and initialization in BW, you need to schedule JOBs to run DAILY/HOURLY along with the TYPE of DELTA that is required...Downtime is NOT required after this point.
The jobs scheduled will pick up any deltas and post it to for the BW Delta Queue. The Delta load in BW will then pick the Delta records.
Cheers,
Praveen.

ALE change Pointers for delta load

The master data datasource is 0CRM_BPSALESCL_ATTR, which is in my source system use change pointers for delta loading. When I use delta loading, the error is "ALE change pointers are not set up correctly". I went to the source system, and use BD61 to activate change pointers. But it does not work. Then I created new Business partners to make changes. I can find these new records in table CDHDR and CDPOS, but there is no records found in table BDCP. And my delta loading still got the error as "ALE change pointers are not set up correctly."
Can anybody give me advice?
Thanks,
Wenjie

Hi, Ron,
Thanks for your reply. I already assign points to you.
I relicated the datasource, and re-active the transfer structure, but it still doesn't work. My one more question is that do I run BD61 on BI system or on source system? I did on source system only. And is there any more setting need to be done on source system? Because my error message said setting on source system is wrong.
Thank you very much.
wenjie

Numeric Pointer for delta

Similar Messages

Maybe you are looking for