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

Similar Messages

  • RDA enable option in Generic Delta

    Hi,
    Where do you see RDA enable option in Generic Delta in both the cases R/3 4.7 and ECC6.0?  I didn't find the enabling option.  Could anyone tell me any settings need to be done before it enables.  Whether RDA enables for Generic Delta?  If yes what method SAP recommended to use among table/view, FM, or InfoSet Query?
    Thanks & Regards,

    Hi Lathika
    to enable RDA option go with WEB Service data sources in the data source-Extraction tab you can see the option Realtime where you can find RDA suppoted
    but wen creting the infopackage you need to assign the daemon to that and assign your DTP which loads further targets from that data source also to the same daemon and mention request losing settings in the info package
    for example if you mention the request closing time is 1 hour that particular request will be opened for 1 hour the deltas that are posted in that 1 hour will fall in this request
    after the request automatically will set to closed
    Thank you

  • Generic Delta Extraction

    Hi,
    In Generic delta extraction for function module which generic delta we can use
    1)Time stamp 2)CAL day 3)Numeric pointer?
    What safety upper limit and safety lower milit in time stamp?
    When we use safety upper limit and lower limit in Time stamp and numeric pointer?
    If possible give 1 scenario for this question
    Thanks,

    Hi,
    Delta with data transfer, you do an init with all the data and marke the requests as delta. The next request will bring the new records and modifications as a normal delta.
    Without data transfer, you're only marking the request as delta, the init don't bring any data. Only next deltas will bring new and modified requests.
    Normally you'll use init with data transfer and deltas after it.
    But imagine you already have an init of a datasource to a Dataprovider, but you'll want to connect that datasource to a new one. Since you already have an init to a first dataprovider, connect it to another new dataprovider, you won't be able to start a new init with data trasnfer to the new dataprovier (without deleting the old one). Therefore, you could bring a full of all the data to the new dataprovider, after that, delete the init flag of the old dataprovider, and create a new init without data. Therefore, the old dataprovider, since already had all the data before, you're only deleting the init flag and create it again, the new dataprovider, you already had sent the data with a full load, so marking the init flag, after that sending deltas will bring new and modified requests to the two dataproviders as what you want.
    Please go through the below links,
    Re: Generic extraction
    Re: Generic Extraction-example
    Re: Numeric Pointer Option on Generic Delta Screen
    Hope it helps you,
    Thanks & Regards,
    Ravi.

  • 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

  • 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

  • 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

  • Generic delta - custom table in r3- help needed

    hI ALL
    I am using a ztable in r3 as data source . i wish to extract data from this table
    to my bw ods as a daily delta . i have created a generic data src zds_ztable on the
    basis of this table and in the generic delta section selected ' new and changed records' and 'numeric pointer'
    options .
    however , on the bw side when i try to create an infopackage under the relevant infosrc , it does not give
    me an option for ' initialisation' or 'delta ' , i only have option for FULL loads , I know i can use a date
    field and do a pseudo delta using technical FULL load ...but i want to know why cant i do an init and then
    a delta the way we do for other data srcs....
    pls help

    Hi,
    You may go to RSA2 for your datasource in R/3 & check do the delta settings are correct ? or you might need to re-generate the datasource and replicate in BW.
    Eddo

  • Problem in getting Generic Delta records to BW

    Hi BW Gurus,
    I have got one issues with which I have been struggling a lot for several days . i.e
    I am extracting data from R/3 using Generic Extractor (View) from CATSCO and CATSDB. At the time of delta, I tried using Personal  No with Time Stamp giving Upper limit as 1800 seconds. I executed Infopackage in BW immediately. But it didn't work out. So plz guide me how I can get Delta Records to BW. Or should I do any  necessary factors apart from these in Generic Delta Screen (RSO2).
    It is very urgent.
    I will be thankful for solving this issue.

    Hey I am "Intros" again,,
    I am sorry man for giving the wrong T-code mistakenly in my last reply..
    To solve the proble...the whole process is same what I told u before..
    But... you got to go to T-Code :  BD87   , then execute the IDocs manually to bring them in to BW
    identify your IDocs which are missing in Monitor screen, then goto BD87 and select those IDocs and click execute... )you can search the IDoc's based on selection conditions)
    I hope this will help u...
    cheers man..
    ---Intros

  • How to Create a Generic Delta Datasource

    Hi All,
    I have created a extractor thru RSO2 using a table.
    The table consist of a time field which i set it to the timestamp field. After initlializing the delta upload successfully, when i run delta upload, no data has been uploaded even having made changes to some of the records.
    Why is it so? Kindly advise.
    Does the timestamp field have to be a datetime field or it can be any field of any data type?
    Thanks in advance.

    Hello Bill,
    I have checked RSA7 and my datasource has the status of green. I have set the upper level to <b>900secs</b>. After the init load, i waited for more than <b>900secs</b> before i do another load but it still comes out as 0 records. Is there anything else i need to do?
    I'd like to clarify one thing, is the timestamp field's data type suppose to be a decimal of length 15 field? Mine is currently a <b>DEC15</b> field which is also a packed field. When i used <b>F1</b> at the generic delta screen, it told me that the timestamp field should be a <b>dec15</b> field. Is it correct?
    Thanks, Bill!
    Message was edited by: Shunhui Chua

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

  • Delta Option for Generic Data Source

    Hi ,
    My requirement is Delta Option for Generic Data Source. This Data Source is getting Extracted from Function Module.
    For this requirement I have followed below steps.
    1) Added the Field (On which Delta gets enabled) to the extract structure by using Append Structure
    2) Enabled Delta On this Filed.
    3) If I try to save the Data Source,  I have gone to a screen where I am able to see 4 coloumns
    a) Selection
    b) Hide Field
    c) Inversion
    d) Filed Only known in User Exit.
    By default Hide Field and Filed Only known in User Exit check boxes have been checked.
    Would you please tell what is the use of Filled Only known in User Exit check biox.
    As My data source is getting the data buy using the Function Module, Shall I uncheck this Check Box.
    Thanks and Regards,
    K.Krishna Chaitanya.

    Hi Krishna,
    The "FIELD" should be checked if we write any enhancement in CMOD, so that system can identify that this particular field has enhancement written to it,
    But even in real time systems i usually find that even though we check the "FIELD" or not , there is no effect .
    So Checking "FIELD" or not will not impose any isses .
    Regards,
    Krishna

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

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

Maybe you are looking for