Delta Extraction - Generic Datasource

Hello Guys,
I have an issue related with the delta extraction for a generic DS. I have a DS setup with
a generic delta for a calendar day and safety interval upper limit 1. So i think that for some reason no all values are loaded in the
delta load. Please help me to find the best approuch for this.
Regards,
Iván.

Hi,
Hope below links are helpful for you to find the best approuch
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33?quicklink=index&overridelayout=true
Generic delta safty intervals
Regards,
Vinay

Similar Messages

How to catch the delta of generic datasource created on table EBAN?

Hi Guru,
I am facing a problem about the delta of generic datasource i created on table EBAN.
when I convert a PR into PO, this PR was created several month ago, this PR will not be caught into delta package.
how to get this PR again after it was converted into a PO?
many thanks.
brgds/steve

hi,
If you have any fields(calday,timestamp,nemric pointer) in your table , using this fields any one we can enable delta.otherwise one option is there but your table is small valoum of datas.
first data load(full) r3 to bw side cube,then using open hub service download data from cube to any file (excel ,csv) then r3 side create one table using that flat file, then load download file to r3 new table using (LSMW - tcode r3 side).
now compare your genric extroction table and new table using ABAP coding , then you have any new record or changed find update new table first then BW side .
using this type we can enable delta for genric extrocation.
regards,
sundar.

How to deal with delete record in generic delta of generic datasource

Hi,
Anyone can give me suggestion about the delete record in generic delta of generic data. I need extract data with a generic datasource and hope deleted record in datasource also can be "delete" in next delta extraction. I do a test with generic delta. It seem that the delete record can not be updated in ODS. but updated record can be updated in next delta extraction.
How dose BW generic delta deal with the deleted record with generic delta mechanisim? Or how can I use generic delta mechanisim to realize that BW "delete" the deleted record of source system in ODS with delta extraction?
Thanks in advance!
Billy

Delete is not supported in delta mechanism of generic delta extractor. You will need to add a workaround for that.
- Capture the deleted records somewhere (maybe enhance the txn deleting the record so the key is written to a Z table). Take these records to BW and manipulate the recordmode to affect deletion of corresponding record from ODS.
- If your generic delta is based on FM, and if the 'delete' is captured in change document tables, add the logic to check change document tables whether any records are deleted, and if yes, send those to BW with appropriate recordmode to achieve deletion.

Delta enable generic datasource

hellow sir ..
im workin on SAP BW 3.5
i'm creating the generic datasource ,, so my confusion is how to make it Delta enabled because The check box for DElta is Greyed...
so wat;s the diference between delta box checked and unchecked..
how to make that grey area checked..
thanks and regards

u r talkin about Generic Delta Tab.. where 3 option s are there,.. - YES
so wat options i shud go for.. so that it enables Delta upload at BW side. - This will not enable delta loading at BI side it will extract delta records from R/3 only, for activation BW delta you have to create a delta infopackage that will extract the delta records from R/3 to BI.
and there are 2 more options in Radio button
- Filed name : Here u specified based on which field ur delta records wil be picked up, like change date field (field name : ERDAT) then specify the name of field, as its a date field so choose the Radio button CAled day. If it had been a time stamp filed u have choosen then Timestamp radio butoon.
1) New status for change Records
2)Additive Delta..
For above read F1 help (that is very clearly explains this)
and what is the DElta check box which is there in Selection and Hide field Tab,, which comes after Saving the First Screen of RS02 ( DATASOURCE : Customer Version Edit ) - This box will become checked when u maitain any delta field in Generic delta tab. It indicates wether the datasource is delta enabled or not
Hope this is clear now.

Error while doing DELTA Extraction (generic data source)

Hi BW Experts,
In my R/3, I have a generic data source ZBUT_VW.
It receives data from a View which is created based on couple tables.
When I do full load to the corresponding ODS, it is successful.
But after that I delete the ODS and created CUBE with DELTA
I have Initialized delta.
When I do DELTA extraction, it fails.
The error The ALE inbox of the SAP BW is identical to the ALE outbox of the source system
and/or
the maximum wait time for this request has not yet run out
and/or
the batch job in the source system has not yet ended.
I delete the initialization load and trying to do DELTA extraction again and it Fails.
With the same error
Please let me know how can I resolve this problem.
URGENT
gaurav

I dont think it is possible to have to additive delta with creation date.
Try a full load to cube to check if the extractor is working.

Delta in Generic datasources.

For the generic datasource. I have to run Delta multiple times per day. In this case I hope that, TIMESTAMP is the suitable option to run delta. Here, to set up TIMESTAMP, I have to select the field name for Delta, based on that field name the delta will work and pick the records into BW side.I have 2 fields DATE and TIME to set up delta. I have given field DATE for delta.
For example.The data in the source system is
      IC            DATE                    TIME
      XX           22/03/2009           09:30:41
I will run delta on 22/03/2009, 10 AM , then the above record will go to BW successfully.
At 11 AM one more record will be added into the source sytem on the same date 22/03/2009. Now the data in the source system is
IC            DATE                    TIME
XX           22/03/2009           09:30:41
YY           22/03/2009           11:00:00
Again, at 11:30, I will run delta to pick the 2nd record. Here my doubt is, will that 2nd record be picked into the BW?. I doubt that, as we have set up delta based on the field DATE, Will the 2nd record will be picked into the BW side or not?. If the 2nd record will not be picked into the BW side.
How can I achieve this. But, I need to run multiple times per day and need all records.
Please let me know if you dont understand.

Hi,
I understand your requirement, as you are using date as delta specific field you would not get another record created on the same day. To solve it you have two options,
1) Field with date and time combination. - e.g 20090317164909.
2) Or can you use time field as delta field.
Any of above can solve your problem.
Hope this helps.
Regards,
Viren
Edited by: Viren Devi on Mar 22, 2009 9:11 PM

Delta in generic datasource

Hi all,
In case of standard datasource, the document posted in R/3 is written to BW delta queue. Generic datasources don't support delta update directly but support generic delta. Can you pleasce clarify what exactly happend in case of generic datasoure.
Thanks in advnce,
Zak.

based on timestamp or values of certain field generic datasource shall manage delta. Check this please - Generic Delta-
http://help.sap.com/saphelp_nw70/helpdata/en/37/4f3ca8b672a34082ab3085d3c22145/content.htm

"Delta" Extraction with Datasource 0FI_TV_01

Hi,
Because the Datasource 0FI_TV_01 doesn't allow delta extraction I would like to know what is the estrategy to get data from ECC without have to always extract full data. Does anybody have some experience with this DS ?
Thanks in advance.
Denny.

Hi
Check in
http://help.sap.com/bp_biv235/BI_EN/BBLibrary/documentation/D17_BB_ConfigGuide_EN_DE.doc
Re: Standard extractor
Thanks

Errors occurred during the extraction - Generic datasource

Hi,
We had created a Generic datasource based on Infoset. While executing RSA3 for that datasource, 'Errors occurred during the extraction' message is getting displayed.
In the Error log, it says, "Field catalog does not agree with the fields of the functional area".
Please let us know on how to resolve this error asap.
Thanks in advance!!!!

hi haripriya,
just go to RSO2.
Enter the name of your datsource.
then Click on Delete.
Then Again Recreate your data source with correct structure and definition.
then activate it and replicate it in BW.
hope this will help u.
thanks

How to set Generic Delta for Generic Datasource

Hi to all,
please can any one explain me the generic Delta option for Generic datasource
after creating generic datasource, i need to set the generic delta .
can any one explain me all generic delta option in simple language with example.
Field Nm
Time samp
calend. Day
Numeric Pointer
Safety Interval Upper Limit
Safety Interval Lower Limit
New status for changed Records
Additive Delta
i shall be thankful to you for this.
Regards
Pavneet Rana

this question has been answered a million times.
search the forum.
M.

Processing overdue error during delta extraction from datasource 0CO_OM_CCA

Hi,
I'm getting "Processing overdue error" in BW while extracting delta from datasource 0CO_OM_CCA_9. all other extraction jobs from R3 -> BW are successful. Even Delta init on this datasource is successful & problem is only with delta package.
I appreciate if someone could provide information based on the following error details on this issue.
here are the extraction steps we followed.
Full load of fiscal years 2006 & 2007 Into transactional cube.
load budget data into transactional cube.
compression of the cube with "0 elimination"
Delta Initialization with fiscal period selections 1/2008 to 12/9999
all the above steps were successful.
and when delta package is scheduled, we are getting following errors.
BW system log
BW Monitoring job is turning red with following message.
Technical : Processing is overdue
Processing Step : Call to BW
Sending packages from OLTP to BW lead to errors
Diagnosis
No IDocs could be sent to the SAP BW using RFC.
System response
There are IDocs in the source system ALE outbox that did not arrive in
the ALE inbox of the SAP BW.
Further analysis:
Check the TRFC log.
You can get to this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Removing errors:
If the TRFC is incorrect, check whether the source system is completely
connected to the SAP BW. Check especially the authorizations of the
background user in the source system.
R3 Job Log
Even after BW job turns to red, R3 job continues to run for 2 hours and
eventually gets cancelled with an ABAP dump & here is the log.
Job
started
Step 001 started (program SBIE0001, variant &0000000110473, user ID
BWREMOTE) DATASOURCE = 0CO_OM_CCA_9
Current Values for Selected Profile Parameters
abap/heap_area_nondia.........2000000000 *
abap/heap_area_total..........2000000000 *
abap/heaplimit................20000000 *
zcsa/installed_languages......EDJIM13 *
zcsa/system_language..........E *
ztta/max_memreq_MB...........2047 *
ztta/roll_area................6500000 *
ztta/roll_extension...........2000000000 *
ABAP/4 processor: SYSTEM_CANCELED
Job cancelled
Thanks,
Hari Immadi
http://immadi.com
SEM BW Analyst

Hi Hari,
We were recently having similar problems with the delta for CCA_9. And activating index 4 on COEP resolved our issues.
Yes, by default there is a 2 hour safety interval for the CCA_9 DataSource. You could run this extractor hourly but at the time of extraction you will only be pulling postings through 2 hours prior to extraction time. This can be changed for testing purposes but SAP strongly discourages changing this interval in a production environment. SAP does provide an alternative described in OSS note 553561. You may check out this note to see if it would work for your scenario.
Regards,
Todd

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

I am using generic datasource first time init sucessful, next time deltas

Hai ALL,
I am using Generic Datasource first time i run init next time i want to run the delta, delta is sucessful but 0 records. i am taken date field and new status fileds(DSO) for DSO. R/3 side table values chaging but not replicate to BI. Can any suggest how to run the delta for Generic Datasource.
Thanks & Regards,
Suresh

Hi
Have you set delta pointers in your Generic datasource? if yes then what it is ? try to see if its logically related with your changes in records or you need to use any other type of delta pointer.

Delta enabled generic data source not updating delta

HI,
   Created one Delta enabled generic datasource with the help of ztable .Fill the content of table by manual entries.
   While executin init,records are extracted from R/3 system. After made a change in table entries , it is not captured in RSA3.
   Data source is avaialble in RSA7 after execueting init.
   Delta type== TIME STAMP
   fIELD NAME=zTIME
SAFETY LIMIT=30 SEC
ITS FROM 'NEW STATUS FOR CHANGE RECORDS'
Please help me on this issue..
Regards,
MohammeD

how did you create your data source? - based on view, table for Function Module?
If it is based on a View or table, ideally delta should have worked. If it is not working, please chedk the data type of the field. Make sure that delta field (i.e. ZTIME) is getting updated evertyime you change any record in ztable. While extracting data in RSA3 in delta (D) mode, make sure you also give the target system ID. Also try runnign the delta infopackage in BW if it fetches data.
If nothing works, try creating your data source again.
If it is based on Fuction Module, you will have to include the delta functionality in your code.
Regards,
Gaurav

Delta in Genric datasource

Hi Experts,
How to test delta for generic datasource.
will the delta goto lbwq for generic datasource or straight away rsa7?
Regards,
Anand

Hi,
For generic data source, delta will be seen in RSA7 not LBWQ.
Generic datasource to have a delta capability, your table or view should have either time or date field.
Thanks
Srikanth

Delta Extraction - Generic Datasource

Similar Messages

Maybe you are looking for