How to load a generic delta datasource.

I have created a generic delta datasource based on a table. I want to know how to load and monitor a generic datasource from very first step. That is how should i run and maintain delta transfer .

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-dbb4356cf4bf
http://help.sap.com/saphelp_nw04/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33

Similar Messages

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 900secs. After the init load, i waited for more than 900secs 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 DEC15 field which is also a packed field. When i used F1 at the generic delta screen, it told me that the timestamp field should be a dec15 field. Is it correct?
Thanks, Bill!
Message was edited by: Shunhui Chua

How to modify the Generic Delta in Standard Data Source...?

Hi BW Guru's,
We have one issue like all values are coming from customer master data data source 0CUST_COMPC_ATTR which is delta capable. Recently the functional guys done some modification on customer by remapping the field to sales rep. this will be impact on collector field (this is generic field - ZZ field). Now there will be frequent changes for collector field and the delta is not able to pick up the changed values in to BW system.
I have tried in different ways but not resolved finally i got some clue which as follows:
Data source 0CUST_COMPC_ATTR shows delta process as 'E' Unspecific Delta
Using Extractor (Not ODS-capable) in RSA2.
Now i would like to change the option to delta process to D unspecified delta using delta queue (not ODS-capable).
Can any one give advice me on this. Your help will be appreciated.
Thanks in Advance,
Venkat

Hi Olivier,
Thanks for quick response.
I am sorry for not mentioning the module on which i am working.
I am working on FI-CO extraction. I heard that In FI-CO the delta queue does not support because it won't support V3 Delta mechanism.
But any how i will try with ROOSOURCE and let you know the status of it.
If any advices please revert back with suitable suggestions.
Thanks and Regards,
Venkat

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.

Generic Delta for table MVKE

I need to extract material sales data from table MVKE.
I want to use generic delta datasource but I'm not sure based on which field I need to load delta.
Any suggestions?
Is it possible to use generic delta for MVKE?

Hi,
Yes you can go for generic delta, but you need to decide how your delta should be, whether you want only changed records or after before images or only new records,...
After deciding if you want only new records then you can go for CREATED On field
For changed records ou can go for CHANGED ON field
if you want after before images then choose the correct fields,
after choosing the delta you have to check for when you want to run your delta, daily once or more than ones, if you want yo run more than once go for time stamp.
Regards,
Pavan.

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

Generic delta extraction using function module

Hi.
I have a generic datasource , extraction being performed by a function module. The extraction works fine in full update mode. The extract structure has a timestamp field.
I have enabled generic delta using this field(i.e., marked this field in RSO2). I understand that with this setting, I should be able to get delta data when I do a delta request. But it does not seem to happen.
I checked the ROOSPRMSC table for the last(local) timestamp stored there. Now when I do the delta upload I expect to see only those records which are younger than the stored timestamp of last upload.
But I still get the entire set of records.
Questions are :
1. Do I need to explicitly code for fetching the delta in the extractor ?
2. If not, what could be the reason why generic delta is not working ?
Thanks and regards,
Anuradha

Hi GFV,
I read-up all the forum entries on this topic but could not find anything specifically dealing with my problem. I have browsed through the how-to paper on generic delta as well.
I am quite sure that we don't need any special coding in the extrator for generating delta generically. Even the how-to paper does not mention that.
I have used the FM RSAX_BIW_GET_DATA_SIMPLE as a template
for my extractor(as suggested by F1 help in RSO2). This FM does not even have the i_updmode flag in its interface.
Thus this function module always does full extraction and I expect the system to take care of delta using the timestamp field.
Are these assumptions incorrect ?
Regards,
Anuradha

Query for generic delta

i need to create a extractor x_attr to bring master data attributes from a table y.how can set
the generic delta on this x_attr generic datasource.does a generic delta exists for attr
datasource?

Hi,
For delta to work properly in case of generic extractor.the field on which you want to make delta should be present in
the data source.
We have three delta.
1.Time stamp.
2.Cal day.
3Numeric pointer.
So depending upon your requirement and volume of your data you can choose the delta method.
Thanks,
Saveen Kumar

Generic Delta with Timestamp Field

Dear SDN Team,
We changed one of our HR datasource from FULL to DELTA with Timestamp(TMSTMP)-Time Stamp(UTC).
Which Delta we need to take Timestamp(Local) or Timestamp(UTC)
Our Generic Datasource is based on Function Module.This data source contains HR Hours Data i.e Direct Hours & Indirect Hours.
With interval settings has
Safety Interval Upper Limit - 'Blank' .
Safety Interval Lower Limit - 1800
New status for Changed Records (Selected)
It is a HR Generic Data Source.
We are creating the records in PA30,PA40 and going to take the records from PA0000,PA0001
Delta type for this DS is "AIE" as our delta type process for our DS.
I am trying to load the INIT to Cube,but its not allowing to load,saying with 'AIE' delta type its not possible to load to cube.
I changed the delta type to 'ADD' then the safety interval limits changed to
Safety Interval Upper Limit - 1800 .
Safety Interval Lower Limit - Blank.
Additive Delta (selected)
Is it possible to load the Generic Delta Time stamp to Cube?
Please let us know what are the settings & delta type needs to be there to load the Generic Delta Timestamp to Cube.
Your suggestions are really appreciated.
Thanks and Kind Regards,
Lakshman Kumar G

Hi,
We used TMSTMP filed with Data element TZNTSTMPS with data type DEC Length 15 in Function Module & Extract Structure.
Default filed name is TIMESTAMP_UTC,Domain is TZNTSTMPS.
Generic Delta -
Filed name - TMSTMP
Timestamp (UTC) selected
With interval limits
Safety Interval Upper Limit 1800
Safety Interval Lower Limit
New Status or Changed Records selected.
Thanks and Kind Regards,
lakshman

How to create generic text datasource to load text data?

met issue in generic master data load
Hi,
please see above link for detail infomation regarding the attribute data load. now the language and description column of the infoobject s_saled is empty. i need to create a generic text datasource to load data from R3 to BW. the table which i use to extract attribute data is VBAK, but i don't find any filed relate to language and description.
met issue in generic master data load
can anyone tell me how to load the text data?
thanks very much.
Eileen

hi eileen,
go to transactio rso2 in your source system ie r/3.
there u have three three fields for transaction data
attributes.
text.
choose text and proceed as u did for trancsaction data load.
thank u,
reward if helpful.

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.

How to load 0customer_text by ALE delta

Hi,
I would like to load customers name of one account group by delta.
The ocustomer_text DataSource has no selection of account group, so it extracts all the customers text.
I tried to create a new datasource which is a view that have the table kna1, and added the field "account group" as selection.
It seems well, but the problem is, that when I try to load data by delta I get nothing.
So,Can anybody explain how can I load text by delta from the table kna1 ?
Thankfully,

hi Mohamad,
try if generic delta helps.
RSO2, give your datasource master text name in 'texts', and create. click generic delta button, and choose 'calendar day', and field nm 'UPDAT'.
safety upper limit interval = 1, leave lower limit blank.
click save, in next screen mark field KTOKD for selection. and save. replicate to bw, and map NAME1 to TXTMD or TXTSH or TXTLG.
another way is try without click 'generic delta' but mark ERDAT UPDAT as selection, later in bw create 2 infopackage, one with ERDAT as selection and the other with UPDAT as selection in infopackage, and can choose type 0 (get yesterday), or 6 (abap routine) and put routine for both
ERDAT
data: l_idx like sy-tabix.
          read table l_t_range with key
               fieldname = 'ERDAT'.
          l_idx = sy-tabix.
          l_t_range-low = sy-datum.
          append l_t_range.
          modify l_t_range index l_idx.
          p_subrc = 0.
UPDAT
data: l_idx like sy-tabix.
          read table l_t_range with key
               fieldname = 'UPDAT'.
          l_idx = sy-tabix.
          l_t_range-low = sy-datum.
          append l_t_range.
          modify l_t_range index l_idx.
          p_subrc = 0.
hope this helps.

Delta loading of generic data source.

Hi,
please tell me the procedure for How to load Delta data For generic data source?

Hi
You can use the following procedue
Enabling Delta Load
Use
You must first configure and modify the DataSource to be used for delta loading in CAF and SAP BW integration and define delta-relevant attribute fields.
Prerequisites
You have launched the Maintain Generic DataSources tool of SAP BW.
Procedure
1. Configuring Generic DataSources
     1.      In the DataSource pane, choose next to the Transaction data field to select the DataSource to use for CAF and SAP BW integration and choose Change.
     2.      In the Change DataSource maintenance screen:
           a.      Set Applic. Component to BW.
            b.      Choose Save.
    3.      In the Create Object Directory Entry dialog box:
            a.      Choose Local Object to see the DataSource information.
             b.      Choose Save to return to the Change DataSource maintenance screen.
4.      Choose Generic Delta. In the Generic Delta dialog box:
            a.      Browse Field Nm. to select the delta-relevant field.
           b.      Mark the Time stamp radio button.
            c.      Mark New Status for Changed Records.
5.      In the Selection of field determining delta dialog box, select the following delta-relevant fields:
○       For the entity service DataSource, select the field corresponding to LASTCHANGEDAT.
○       For the application service DataSource, select the field corresponding to delta-relevant field specified by BW extractor method developer.
6.      In the DataSource: Customer version Edit screen, save all data.
2. Activating DataSources
       1.      Launch the SAP BW Administrator Workbench and go to Modeling.
      2.      Open the list of InfoSources and select the DataSource assignment you want.
      3.      With the secondary mouse button, choose Replicate DataSources.
      4.      Select the same object from step 3 and choose Change Transfer Rules with the secondary mouse button.
      5.      In the InfoSource Change screen, choose with the quick info text Activate.
Initializing Delta Load
Prerequisites
You have configured the DataSource for the delta loading process. For more information, see Enabling Delta Load.
Procedure
1. Starting Delta Initialization
     1.      Launch the SAP BW Administrator Workbench and go to Modeling.
     2.      From the Modeling pane, click InfoSource to populate the InfoSource pane and select the InfoPackage you created for the InfoSource in, for example, Example of Data Extraction.
      3.      From the Update tab page, activate the Initialize Delta Process indicator.
      4.      To define parameters to be used for the delta load process, go to the Data Selection tab page and define relevant parameters.
      5.      In the Schedule tab page, choose Start to begin delta initialization.
If you defined parameters to be used in delta load (step 4 above), use PSA in the modeling component of Administrator Workbench to view the request results.
     6.      To check when delta initialization is finished, go to the Maintain InfoPackage screen of the Monitor u2013 Administrator Workbench and press F6.
2. Monitoring Delta Initialization
     1.      Launch the BW Delta Queue Maintenance and select the DataSource in question.
     2.      Use the secondary mouse button to see the current pointer value in Generic Delta Current Status.
     3.      You can delete the delta initialization (if you want, and subsequently create a new delta initialization) in Scheduler (Maintain InfoPackage) by choosing the delta request from Initialization Options For Source System and choosing Remove.
In this screen, you can also check the status of the delta initialization request.
To see the content and results of the delta initialization request, go to PSA in the modeling component of Administrator Workbench to view the request results.
3. Running Delta Load
You can run the delta load process only after delta initialization has been completed.
     1.      Open the InfoPackage and in the Update tab page activate the Delta Update indicator.
      2.      Go to the Schedule tab page and choose Start.
*Enabling Delta Load *
Use
You must first configure and modify the DataSource to be used for delta loading in CAF and SAP BW integration and define delta-relevant attribute fields.
Prerequisites
You have launched the Maintain Generic DataSources tool of SAP BW.
Procedure
1. Configuring Generic DataSources
      1.      In the DataSource pane, choose next to the Transaction data field to select the DataSource to use for CAF and SAP BW integration and choose Change.
     2.      In the Change DataSource maintenance screen:
        a.      Set Applic. Component to BW.
        b.      Choose Save.
    3.      In the Create Object Directory Entry dialog box:
           a.      Choose Local Object to see the DataSource information.
            b.      Choose Save to return to the Change DataSource maintenance screen.
   4.      Choose Generic Delta. In the Generic Delta dialog box:
       a.      Browse Field Nm. to select the delta-relevant field.
       b.      Mark the Time stamp radio button.
       c.      Mark New Status for Changed Records.
5.      In the Selection of field determining delta dialog box, select the following delta-relevant fields:
○       For the entity service DataSource, select the field corresponding to LASTCHANGEDAT.
○       For the application service DataSource, select the field corresponding to delta-relevant field specified by BW extractor method developer.
   6.      In the DataSource: Customer version Edit screen, save all data.
2. Activating DataSources
   1.      Launch the SAP BW Administrator Workbench and go to Modeling.
   2.      Open the list of InfoSources and select the DataSource assignment you want.
3.      With the secondary mouse button, choose Replicate DataSources.
    4.      Select the same object from step 3 and choose Change Transfer Rules with the secondary mouse button.
5.      In the InfoSource Change screen, choose with the quick info text Activate.
Hope this helps
Regards
Shilpa

Full to delta load in generic extration

Hi All,
I am loading the data form R/3 to BW with full load by using the generic data sources.
Now I need to change the full load to delta. But I get the data 2 views and one FM.
Some what I have got the solution, that is going RSO2 there generic delta will be available
If I click I will get the one wind there 3 deltas form there I took time stamp. Then I need
Select the field name.
1) Now only my problem started in that field name there is no creation
Date and last changed data, based on this we need to get the data from R/3 to BW.
2) In that 3 datasorce I used the one DS function module in this also that field name is not
available .
3) In safety interval what I need to give.
Please help on above 3 issues.
Thanks
kumar.

Hi,
plz check with this most proberly it works.
Go to RSO2 >> Now select the right option(Transaction data,Master data attributes or texts) >> Now in the next screen enter the Application Component >> enter the descriptions >> Now select how you want to populate data in your data source .....following options are there :
View/table >> Choose the extraction from view button if you want to want to extract the data from a transpatrent table or database view,and enter the name of the table or view...the extraction structure of the generated datasource is then identical to that of view or table.......
SAP Query/Infoset>> Choose the extraction from query button if you want to use SAP query infoset as datasource..then select the required infoset from the infoset catalog...you can go to the screen for maintaining an existing infoset by double click on its name...
Function Module
To make your datasource delta enable >> Click on Generic Delta on the top >> Here first give the field name .This field from the extract structure of a DataSource meets one of the following criteria:
1. The field has type: time stamp. New records to be loaded into the BW using a delta upload have a higher entry in this field that those which have already been loaded.
2. The field has type: calendar day. The same criteria applies to new records as in the time stamp field.
3. The field has another type. This case is only supported for SAP Content DataSources. In this case, the maximum value to be read must be displayed using a DataSource-specific exit when beginning data extraction.
Now choose one of the three options :
Time Stamp
Calender day
Numeric pointer...
Safety Interval Upper Limit >>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.
DataSource Is Real-Time Enabled
The "Real-time enabled" indicator determines whether a delta-enabled DataSource can supply data for a real-time demon.
If the DataSource finds the delta generically using a delta-relevant field, observe the following with regard to the safety intervals:
The safety interval at the lower limit may cause redundant data to arrive in BW. This data is not suitable for InfoCubes and ODS objects with key figures that are updated in appended order. With real-time updates, the redundancy of the data is increased by the short time spans between the individual runs of a real-time demon. With a lower safety interval of 2 minutes and a demon frequency of one per minute, all data may potentially arrive in the PSA three times. This can lead to database and runtime problems.
The safety interval at the upper limit makes the data less up to date. How up to date the data is with real-time is always the sum of the upper safety interval and the time span between two runs of the demon.
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.

How does the Generic Delta Works

Hi All,
Please let me know how the different types of Generic Delta works i.e. Numeric Pointer, 0Calday and Timestamp with one simple example for each.
Thanks & Regards,
Sunny

Hi........
There are three options for the type of the field 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.
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 this link :
http://help.sap.com/saphelp_nw2004s/helpdata/en/37/4f3ca8b672a34082ab3085d3c22145/content.htm
generic delta
Hope this helps you..........
Regards,
Debjani.............

How to load a generic delta datasource.

Similar Messages

Maybe you are looking for