0FI_GL_12 delta safety interval

Hi
I am using 0FI_GL_12.
Requirement is to run the delta every 2 hours.
I want to know if there is any time limit contraint between 2 delta loads.
can be there any issue if I start loading delta every 2 hours for this datasource.
Thanks
Navneet

Hi Revanth
0FI_GL_12 is replacement of 0FI_GL_10
your SAP should be ECC 6.0
There are certain modifications you need to do in R/3 side then only you can see 0FI_GL_12 in business content datasources.
Changes are mentioned in SAP notes.
Also you need to write start routine for calculation of key figure 0BALANCE as this datasource does not contain 0BALANCE values
and they are always calculated in BI in start routine which is also provided in SAP Note:
Please refer to the following SAP notes and the link :
1153944 -> R/3 settings
1233941 -> start routine for 0BALANCE
1392817-> 0FI_GL_12 delta concept and compariosn with 0FI_GL_10
link: [0FI_GL_12 FI new datasource;

Similar Messages

Doubt Reg Generic Delta "Safety Interval" Setting

Hi Experts,
I have a doubt regarding Setting "Safety Interval Upper Limit" and Lower limit in RSO2 for generic delta.
What does this setting imply?
If I do setting for calender day say both 1 then wht will be difference between delta before setting amd after setting?
Plz explain in terms other tham help provided...
Points will be awarded to say thanks..
Thanks in advance,
Sorabh

Hi Sorabh,
Here some SAP informations:
Safety Interval Upper Limit of Delta Selection
This field is used by DataSources 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.
Extracted Data Delta Type
The system uses the delta type to determine how extracted data is to be interpreted in BW, and into which data targets it can be posted.
A distinction is made between the following:
1. Additive delta
The key figures for extracted data are added up in BW. DataSources with this delta type can supply data to ODS objects and InfoCubes.
2. New status for changed records
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.
Check also examples in "How to... Create Generic Delta" under www.service.sap.com/bi.
Ciao.
Riccardo.

Regd Safety Interval Lower Limit for Generic Delta

Hi All,
Safety Interval Upper Limit =1 for a Generic Delta would get Delta based on yesterday's BW data.
What would Safety Interval Lower Limit would do for a Generic Delta .
Your inputs please
Sree

Hi,
just a short example:
you run a init today --> 20070525 (internal date format).
for the next delta tomorrow the system takes the last extraction date - 1 day so 20070524 for data selection and will store 20070526 as last extraction date and so on.
This is to make sure that you will get all additional records extracted which were changed or created on each extraction date, but after last extraction. OK, you will get some records twice, but therefore you normally post the data to a ods via overwrite mode and this will take care about the 'real' delta while doing the further posting to the cube.
Hope this helps
kind regards
Siggi

What is safty delta and safety interval

Hello,
PLease tell me What is mean by Safety Delta and Safety Interval?

Hi,
Safety interval should be set so that no document is missed even if it was not stored in the DB table when the extraction took place.
Example for Determining Selection Intervals with a Generic Delta:
1. If delta field is Date (Record Create Date or change date), then use Upper Limit of 1 day.
This will load Delta in BW as of yesterday. Leave Lower limit blank.
2. If delta field is Time Stamp, then use Upper Limit of equal to 1800 Seconds (30 minutes).
This will load Delta in BW as of 30 minutes old. Leave Lower limit blank.
3. If delta field is a Numeric Pointer i.e. generated record # like in GLPCA table, then use Lower Limit. Use count 10-100. Leave upper limit blank. If value 10 is used then last 10 records will be loaded again. If a record is created when load was running, those records may get lost.
To prevent this situation, lower limit can be used to backup the starting sequence number. This may result in some records being processed more than once; therefore, be sure this DataSources is only feeding an ODS Object
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
Assign points if this is needful.
Rgs,
I.R.K

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?

What type of Data target is used when the safety interval is used?

Hi ,
what type of Data target is used when the safety interval is used in generic delta in datasource?DSO or cube or cube?
Pls explain me ?
Thanks,
Nimai

It's up to your reporting requirement to go for dso or cube..
I prefer to having staging with DSO and then further reporting on Cube ..
It's always easier to manage when you have any changes to the cube .. you need not to extract data from R/3 .. if you have dso you can extract directly to cube
Another thing is -for any reason some of your records got corrupted so you can have full loads to dso which has the overwrite functionality... and sends delta records to cube. even in cube you can do selective deletion but we have to very careful to avoid double records in next loads
Edited by: Srinivas on Jul 29, 2010 8:23 PM

How to change safety interval in COPA extractor

Hi, guys!
I had a problem with changing safety interval in COPA extractor. I created COPA datasource using keb0. In RSA2 it can only view security interval. It is 1800 sec by default. I cannot change it.
How can I change it? I cant do it in RSO2, because it is not true generic delta.
Note 808663 is not implemented (we have higher patch on R/3). Delta extraction is correct, but safety interval is very annoying
Please help.
Message was edited by: Emerald

Thanks. I'll try to.
I thought I should edit ROOSOURCE, but it's maintainable in productive system.
Should I reInit delta after corrections implementation?

Safety interval

hi -
is there a way to find out what is the saftey interval assigned for a datasource. lets say for fi_ap_4 what is the safety interval. where is it mentioned? is there a way to change this and if so how?
thanks
ravi

Hi Ravi,
In case of FI extraction you can find this information from the table BWOM_SETTINGS .
For further information , take a look on the following site ( especially 'Global settings' paragraph).
http://help.sap.com/saphelp_bw33/helpdata/en/af/16533bbb15b762e10000000a114084/frameset.htm
With rgds,
Anil Kumar Sharma .P

How to change the safety interval for 0FG_DO01- Special ledger data source

Gurus,
Is there a way to change the safety interval for SAP Standard Data source 0FG_DO01(safety Inteval).
I am only able to display it in RSA2 and not change.
Appreciate your immediate assistance.
Thanks,
Ravi Aananthuni

You can view it in RSA2. However you may need to update table ROOSOURCE to change the value of safety interval upper and lower limits.
Thanks,
Ravi ananthuni

Where to find deltas in generic extraction

hi experts,
could you please explain me tcodes which are used to find the delta data while we go for generic extraction. Also can anyone explain me the full process of extracting the data using
infoset query and function module.
Cheers,
Pragya.

Hi
You can define delta's in generic using " calendr day, numeric pointer, time stamp."
Generic Delta
If a field exists in the extract structure of a DataSource that contains values which increase monotonously over time, you can define delta capability for this DataSource. If such a delta-relevant field exists in the extract structure, such as a timestamp, the system determines the data volume transferred in the delta method by comparing the maximum value transferred with the last load with the amount of data that has since entered the system. Only the data that has newly arrived is transferred.
To get the delta, generic delta management translates the update mode into a selection criterion. The selection of the request is enhanced with an interval for the delta-relevant field. The lower limit of the interval is known from the previous extraction. The upper limit is taken from the current value, such as the timestamp or the time of extraction. You can use security intervals to ensure that all data is taken into consideration in the extractions. After the data request was transferred to the extractor, and the data was extracted, the extractor then informs generic delta management that the pointer can be set to the upper limit of the previously returned interval.
The delta for generic DataSources cannot be used with a BW system release prior to 3.0. In older SAP BW releases, the system does not replicate DataSources for master data and texts that were made delta-enabled using the delta for generic DataSources.
Determining the Generic Delta for a DataSource
       1.      Choose Generic Delta.
       2.      In the subsequent dialog box, specify the delta-determining field and the type for this field.
       3.      Maintain the settings for the generic delta:
                            a.      Specify a security interval.
The purpose of a security interval is to make the system take into consideration records that appear during the extraction process but which remain unextracted (since they have yet to be saved) during the next extraction.
You have the option of adding a security interval to the upper limit/lower limit of the interval.
A security interval should only be specified for the lower limit when the delta method results in a new status for changed records, in other words, when the status is overwritten in BW. In this case, duplicate data records that could arise in such a safety interval have no affect on BW.
                            b.      Choose the delta type for the data to be extracted.
The delta type is used to determine how extracted data is interpreted in BW and which data targets in which it can be posted.
With the delta type additive delta, the record to be loaded for summarizable key figures only returns the change to the key figure. The extracted data is added in BW. DataSources with this delta type can supply both ODS objects and InfoCubes with data.
With the delta type New Status for Changed Records, every record to be loaded returns the new status for all key figures and characteristics. The values are overwritten in BW. DataSources with this delta type can write the data into ODS objects and master data tables.
       4.      Save your entries.
Delta transfer is now possible for this DataSource.
After generating the DataSource, you can see this from the marking for the field Delta Update on the DataSource: Customer Version screen.
In systems from release 4.0B, you can display the current value of the delta-relevant field in the delta queue.
Example for Determining the Selection Interval for a Generic Delta
Safety Interval Upper Limit
The delta-relevant field is a timestamp.
The timestamp that was read last is 12:00:00. Delta extraction begins at 12:30:00. The safety interval for the upper limit is 120 seconds. The safety interval for the delta request is: 12:00:00 to 12:28:00. Upon completion of the extraction, the pointer is set to 12:28:00.
Safety Interval Lower Limit
The delta-relevant field is a timestamp. After images are transferred. In other words, the record is overwritten with the status after the change in BW, for example for master data. Any duplicate records that appear have no effect upon the BW system.
The last changed timestamp is 12:28:00. Delta extraction begins at 13:00. The safety interval for the lower limit is 180secs. The safety interval for the delta request is: 12:25:00 to 13:00:00. Upon completion of the extraction, the pointer is set to 13:00:00.
source: help.sap.com
Hope it helps
kalyan

Genric extractor on logical database

Hi
I have a requirement to create a generic datsource.
the requirement is to pull the data from logical database
the logical data base consists of tables and structures.
could pls let me know how would i create a generic datasource to pull the data from logical database.
Thanks,
D

Hi
Determining the Generic Delta for a DataSource
       1.      Choose Generic Delta.
       2.      In the subsequent dialog box, specify the delta-determining field and the type for this field.
       3.      Maintain the settings for the generic delta:
                            a.      Specify a security interval.
The purpose of a security interval is to make the system take into consideration records that appear during the extraction process but which remain unextracted (since they have yet to be saved) during the next extraction.
You have the option of adding a security interval to the upper limit/lower limit of the interval.
b.      Choose the delta type for the data to be extracted.
The delta type is used to determine how extracted data is interpreted in BW and which data targets in which it can be posted.
With the delta type additive delta, the record to be loaded for summarizable key figures only returns the change to the key figure. The extracted data is added in BW. DataSources with this delta type can supply both ODS objects and InfoCubes with data.
With the delta type New Status for Changed Records, every record to be loaded returns the new status for all key figures and characteristics. The values are overwritten in BW. DataSources with this delta type can write the data into ODS objects and master data tables.
       4.      Save your entries.
Delta transfer is now possible for this DataSource.
After generating the DataSource, you can see this from the marking for the field Delta Update on the DataSource: Customer Version screen.
Example for Determining the Selection Interval for a Generic Delta
Safety Interval Upper Limit
The delta-relevant field is a timestamp.
The timestamp that was read last is 12:00:00. Delta extraction begins at 12:30:00. The safety interval for the upper limit is 120 seconds. The safety interval for the delta request is: 12:00:00 to 12:28:00. Upon completion of the extraction, the pointer is set to 12:28:00.
Safety Interval Lower Limit
The delta-relevant field is a timestamp. After images are transferred. In other words, the record is overwritten with the status after the change in BW, for example for master data. Any duplicate records that appear have no effect upon the BW system.
The last changed timestamp is 12:28:00. Delta extraction begins at 13:00. The safety interval for the lower limit is 180secs. The safety interval for the delta request is: 12:25:00 to 13:00:00. Upon completion of the extraction, the pointer is set to 13:00:00.

0FI_AR_4 safety delta

Hi all,
We have a query on datasource: 0FI_AR_4,and every night i runs a delta load to BW. But the users are telling me that the changes they make aren't shown in the query the next day. But if they wait for 2 days the changes will show. Therefor I started to look for a setting for 0FI_AR_4 delta .
I found a document for "data extracton FI/CO" and here it says i should look in BWOM2_TIME, but here I can't find my datasource. DELTIMEST has setting : 60 ,but i dont know if this means that the delta should wait 60 hours before it should transfer to BW
Any ideas on way my delta is delayed?
Best regards
Anette

Hi there,
Please take a look to this OSS note:
485958
This will explain you that it has a safety interval ina a particular table refering just that.
By default, the data is extracted with the safety interval of 1 day. If the changes are done from 00:00 til 02:00, that safety interval will be 2 days.
Hope this helps,
Diogo.

What is safety delta time

Hi Experts
Can any one please explain me
What is safety delta time in terms of delta data source
Thanks

Hi,
Safety Interval Upper Limit of Delta Selection
This field is used by DataSources 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:40:00. In this case, the selection interval is 12:00:00 to 12:40:00. At the end of extraction, the pointer is set to 12:40:00.
A record - for example, a document- is created at 12:40 but not saved until 12:40. 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.
these are used to determining the delta in a datasource:
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
check the thread:
safety intervels in genric delta extraction.?
Sriram

Safety intervals for delta for different datasources

Hi, Please help me to find the Safety intervals for delta for different datasources in RSA7 or in table ROOSPRMSC. Like for FI_GL_10 I know it is 60 mins but where do I see this. I checked Note 380078, Please let me know this specific answer to the question asap.
Thanks
Soniya Kapoor

Hi
Go to RSA2->give your datasource name ->setting up GEN delta
It shows you whts the safety interval setting.
Hope it helps
Thanks for points assigned

Safety intervels in genric delta extraction.?

can anyone expliain me with an example how to set safety intervel limit?how to set upper limit and lower limit?

Hello Shilpa !
Guess this doc will clear ur issues:-
Safety Interval Upper Limit of Delta Selection
This field is used by DataSources 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:40:00. In this case, the selection interval is 12:00:00 to 12:40:00. At the end of extraction, the pointer is set to 12:40:00.
A record - for example, a document- is created at 12:40 but not saved until 12:40. 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.
these are used to determining the delta in a datasource:
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 .
also download Generic Delta doc
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
Regards
Tom.

0FI_GL_12 delta safety interval

Similar Messages

Maybe you are looking for