Generic Extraction Delta Loads

Hi Experts,
I am facing problem is I want to extract the data in Generic Extraction in View, Suppose my requirement is I want to delta loads every 1 hour per day, how can i do, Generic Extraction possible are not delta records.
Note:- LO Extraction is possible like we have update mode we can scheduled hours in everyday, But Generice Extraction possible are not.
Please provide me solutions ASAP.
Thanks in Advance......
Regards,
Bharathi.

There are various delta method
1.calday.
2.time stamp.
3.Numeric pointer.
For youe requirement Time stamp will work.
Please check weather you have any field related to time.
Thanks,
Saveen kumar

Similar Messages

BW GENERIC EXTRACTION DELTA PROBLEM

I have a problem for extracting delta from R/3 to BW.
Init data is loaded from R/3 to BW system for ZST_ORDER datasource.
Repair full request and selection parameter is created on date August 1st 2007 to August15th 2007.
During the delta extraction - A lot of records around 500,000 records are getting extracting from R/3 to BW.
R/3 side - There is only 5 entries available in AUFK table.
It should extract delta only less than 35 entries.
ZST_ORDER is generic datasource . Delta captured field is DATUM -New status changed record value 2.
Advance Thx for your help. The code looks like
FUNCTION ZST_ORDER.
""Local Interface:
*" IMPORTING
*" REFERENCE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUNR
*" REFERENCE(I_DSOURCE) TYPE SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
*" REFERENCE(I_MAXSIZE) TYPE SRSC_S_IF_SIMPLE-MAXSIZE DEFAULT 1000
*" REFERENCE(I_INITFLAG) TYPE SRSC_S_IF_SIMPLE-INITFLAG OPTIONAL
*" REFERENCE(I_READ_ONLY) TYPE SRSC_S_IF_SIMPLE-READONLY OPTIONAL
*" TABLES
*" I_T_SELECT TYPE SRSC_S_IF_SIMPLE-T_SELECT OPTIONAL
*" I_T_FIELDS TYPE SRSC_S_IF_SIMPLE-T_FIELDS OPTIONAL
*" E_T_DATA STRUCTURE ZST_ORDEROPTIONAL
*" EXCEPTIONS
*" NO_MORE_DATA
*" ERROR_PASSED_TO_MESS_HANDLER
TABLES: AUFK, "Order master data
TJ02T, "System status texts
TJ30T, "Texts for user status
JSTO. "Status object information
DATA DECLARATION
DATA: L_DATE TYPE DATS,
L_STATUS TYPE J_STATUS,
L_LINES TYPE SY-TABIX,
L_CHANGED(1) TYPE C.
Auxiliary Selection criteria structure
DATA: L_S_SELECT TYPE SRSC_S_SELECT.
Another data objects
Service Order Data
DATA: BEGIN OF LT_AUFK OCCURS 0,
AUFNR LIKE AUFK-AUFNR,
AUART LIKE AUFK-AUART,
ERDAT LIKE AUFK-ERDAT,
AEDAT LIKE AUFK-AEDAT,
STDAT LIKE AUFK-STDAT,
AEZEIT LIKE AUFK-AEZEIT,
ERFZEIT LIKE AUFK-ERFZEIT,
IDAT1 LIKE AUFK-IDAT1,
IDAT2 LIKE AUFK-IDAT2,
IDAT3 LIKE AUFK-IDAT3,
LOEKZ LIKE AUFK-LOEKZ,
OBJNR LIKE AUFK-OBJNR,
END OF LT_AUFK.
Individual Object Status
DATA: BEGIN OF LT_JEST OCCURS 0,
OBJNR LIKE JEST-OBJNR,
STAT LIKE JEST-STAT,
INACT LIKE JEST-INACT,
CHGNR LIKE JEST-CHGNR,
END OF LT_JEST.
***Change Documents for System/User Statuses (Table JEST)
DATA: BEGIN OF LT_JCDS OCCURS 0,
OBJNR LIKE JCDS-OBJNR,
STAT LIKE JCDS-STAT,
CHGNR LIKE JCDS-CHGNR,
USNAM LIKE JCDS-USNAM,
UDATE LIKE JCDS-UDATE,
UTIME LIKE JCDS-UTIME,
INACT LIKE JCDS-INACT,
CHIND LIKE JCDS-CHIND,
END OF LT_JCDS.
DATA: BEGIN OF LT_JSTO OCCURS 0,
OBJNR LIKE JSTO-OBJNR,
STSMA LIKE JSTO-STSMA,
END OF LT_JSTO.
STATIC FIELDS
STATICS: S_S_IF TYPE SRSC_S_IF_SIMPLE,
counter
S_COUNTER_DATAPAKID LIKE SY-TABIX,
cursor
S_CURSOR TYPE CURSOR.
User-defined Ranges
RANGES: L_R_AUFNR FOR AUFK-AUFNR ,
L_R_ERDAT FOR AUFK-ERDAT.
Initialization mode (first call by SAPI) or data transfer mode
(following calls) ?
IF I_INITFLAG = SBIWA_C_FLAG_ON.
Check DataSource validity
CASE I_DSOURCE.
WHEN 'ZST_ORDER '.
WHEN OTHERS.
RAISE ERROR_PASSED_TO_MESS_HANDLER.
ENDCASE.
Copy selection criteria for future extractor calls (fetch-calls)
APPEND LINES OF I_T_SELECT TO S_S_IF-T_SELECT.
Fill parameter buffer for data extraction calls
S_S_IF-REQUNR = I_REQUNR.
S_S_IF-DSOURCE = I_DSOURCE.
S_S_IF-MAXSIZE = I_MAXSIZE.
S_S_IF-INITFLAG = I_INITFLAG.
APPEND LINES OF I_T_FIELDS TO S_S_IF-T_FIELDS.
ELSE.
First data package -> OPEN CURSOR
IF S_COUNTER_DATAPAKID = 0.
LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT
WHERE FIELDNM = 'AUFNR'.
MOVE-CORRESPONDING L_S_SELECT TO L_R_AUFNR.
APPEND L_R_AUFNR.
ENDLOOP.
LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT
WHERE FIELDNM = 'ERDAT'.
MOVE-CORRESPONDING L_S_SELECT TO L_R_ERDAT.
APPEND L_R_ERDAT.
ENDLOOP.
LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT
WHERE FIELDNM = 'DATUM'.
L_DATE = L_S_SELECT-LOW.
ENDLOOP.
OPEN CURSOR WITH HOLD S_CURSOR FOR
SELECT AUFNR AUART ERDAT
AEDAT OBJNR AEZEIT
STDAT ERFZEIT IDAT1
IDAT2 IDAT3 LOEKZ
FROM AUFK
WHERE AUFNR IN L_R_AUFNR AND
ERDAT IN L_R_ERDAT.
ENDIF.
Fetch records into interface table LT_AUFK
FETCH NEXT CURSOR S_CURSOR
APPENDING CORRESPONDING FIELDS OF TABLE LT_AUFK
PACKAGE SIZE S_S_IF-MAXSIZE.
IF SY-SUBRC <> 0.
CLOSE CURSOR S_CURSOR.
RAISE NO_MORE_DATA.
ENDIF.
Determining the number of lines of the table LT_AUFK .
L_LINES = LINES( LT_AUFK ).
IF L_LINES IS NOT INITIAL.
Sort the internal table LT_AUFK
SORT LT_AUFK BY OBJNR ASCENDING.
Selecting the records from JCDS depending upon the entries in LT_AUFK.
SELECT OBJNR STAT CHGNR USNAM
UDATE UTIME INACT CHIND
INTO TABLE LT_JCDS
FROM JCDS
FOR ALL ENTRIES IN LT_AUFK
WHERE OBJNR EQ LT_AUFK-OBJNR
AND ( CHGNR EQ '001'
OR UDATE >= L_DATE ).
Sort the internal table lt_jcds.
SORT LT_JCDS BY OBJNR STAT CHGNR ASCENDING.
Select records from table JEST depending upon the entries in LT_AUFK.
SELECT OBJNR STAT INACT CHGNR
INTO TABLE LT_JEST
FROM JEST
FOR ALL ENTRIES IN LT_AUFK
WHERE OBJNR = LT_AUFK-OBJNR.
SELECT OBJNR STSMA
INTO TABLE LT_JSTO
FROM JSTO
FOR ALL ENTRIES IN LT_AUFK
WHERE OBJNR = LT_AUFK-OBJNR.
SORT LT_JSTO BY OBJNR.
ENDIF.
LOOP AT LT_JEST.
CLEAR: LT_AUFK,
l_changed.
CLEAR L_CHANGED.
CLEAR LT_JSTO.
READ TABLE LT_JSTO WITH KEY OBJNR = LT_JEST-OBJNR BINARY SEARCH.
IF SY-SUBRC EQ 0.
E_T_DATA-STSMA = LT_JSTO-STSMA.
ENDIF.
*End**
Read the data from LT_AUFK.
READ TABLE LT_AUFK WITH KEY OBJNR = LT_JEST-OBJNR BINARY SEARCH.
E_T_DATA-AUFNR = LT_AUFK-AUFNR.
E_T_DATA-AUART = LT_AUFK-AUART.
E_T_DATA-ERDAT = LT_AUFK-ERDAT.
E_T_DATA-AEDAT = LT_AUFK-AEDAT.
E_T_DATA-AEZEIT = LT_AUFK-AEZEIT.
E_T_DATA-ERFZEIT = LT_AUFK-ERFZEIT.
E_T_DATA-IDAT1 = LT_AUFK-IDAT1.
E_T_DATA-IDAT2 = LT_AUFK-IDAT2.
E_T_DATA-IDAT3 = LT_AUFK-IDAT3.
E_T_DATA-LOEKZ = LT_AUFK-LOEKZ.
E_T_DATA-INACT = LT_JEST-INACT.
E_T_DATA-CHGNR = LT_JCDS-CHGNR.
e_t_data-datum = lt_aufk-erdat.
READ TABLE LT_JCDS WITH KEY OBJNR = LT_JEST-OBJNR
STAT = LT_JEST-STAT
CHGNR = '001'
BINARY SEARCH.
IF SY-SUBRC EQ 0.
E_T_DATA-UDATE = LT_JCDS-UDATE.
E_T_DATA-AEDAT = LT_JCDS-UDATE.
E_T_DATA-UTIME = LT_JCDS-UTIME.
E_T_DATA-AEZEIT = LT_JCDS-UTIME.
E_T_DATA-CHIND = LT_JCDS-CHIND.
E_T_DATA-USNAM = LT_JCDS-USNAM.
e_t_data-chgnr = lt_jcds-chgnr.
IF LT_JCDS-UDATE GE L_DATE
AND L_DATE IS NOT INITIAL.
L_CHANGED = 'X'.
ENDIF.
IF LT_JEST-CHGNR NE '001'.
CLEAR LT_JCDS.
READ TABLE LT_JCDS WITH KEY OBJNR = LT_JEST-OBJNR
STAT = LT_JEST-STAT
CHGNR = LT_JEST-CHGNR
BINARY SEARCH.
IF SY-SUBRC EQ 0.
L_CHANGED = 'X'.
E_T_DATA-AEDAT = LT_JCDS-UDATE.
E_T_DATA-AEZEIT = LT_JCDS-UTIME.
E_T_DATA-CHIND = LT_JCDS-CHIND.
E_T_DATA-USNAM = LT_JCDS-USNAM.
e_t_data-chgnr = lt_jcds-chgnr.
ENDIF.
ENDIF.
IF LT_JEST-STAT(1) EQ 'I'.
E_T_DATA-ISTAT = LT_JEST-STAT.
ELSEIF LT_JEST-STAT(1) EQ 'E'.
E_T_DATA-ESTAT = LT_JEST-STAT.
ENDIF.
IF L_CHANGED EQ 'X'
AND L_DATE IS NOT INITIAL.
APPEND E_T_DATA.
ELSEIF L_DATE IS INITIAL.
APPEND E_T_DATA.
ENDIF.
ENDIF.
CLEAR: LT_AUFK,
E_T_DATA.
ENDLOOP.
CLEAR LT_JEST.
REFRESH LT_JEST.
next data package
S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
ENDIF. "Initialization mode or data extraction ?
ENDFUNCTION.

hi,
for that quantity SALK3 is referring a different table in the reference field for your table fields. check that field and refer the correct table for that field in table view.
table join has a problem in that. i think your joined some other table with that field. replace the field assignment or create a new view.
hope this help you
regards
harikrishna N

Reagrding Generic Extraction Delta

hai
Can anyone explain in detail with example or reak time scenarios about "Generic delta extraction for '0calday'" , "Generic Delta extraction for Numaric Pointer" , "Generic Delta extraction for timestamp" individually ..
Please also send some documents or forums or weblog or screen shots to [email protected] now
Thanks
Bye
mohammed

Dear shylaja,
can you please send the documents related to generic extraction to [email protected] &/ to [email protected] ?
hope you will help.
Waiting for your reply.
Regards
Vinay

Generic Extraction & delta

Hi Experts,
Can anyone tell me regarding the generic extraction and how delta happens in this case.
regards,
MGR

MGR,
Please find the below links for more better understanding about the generic delta and extraction:
Business Content and Extractors
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
****Assign Points*********
Gattu

HI could you pls explaing generic extraction delta mechanism

I know what is delta . but i couldnt differentiate when we go for time stamp and numeric pointer
i have the document for how to generic delta but inthat it is mentioned about how to use . but i want to know when shoudl i use time stamp and numeric pointer
all answers would be rewarde

Hi Dolly,
Here the changed records can be isentified by :
1. Based on the date of creation or last change ( Delta based on 0Calday)
2. Based on the record number ( Numeric Pointer )
3. Based on time of change ( Timestamp)
real time examples would be
1. Master Record creation like customer ID creation
2. Timesheets in SAP PS
3. Invoive details / Sales Order Details.
Here is a weblog from Siggi for Generic Delta Extraction with Function Module.
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
Check previous posts as well.
Generic delta
Data Warehousing
regards
@jay

GENERIC EXTRACTION DELTA SETTINGS

HI Everyone,
                    I need to know how we set up Generic Delta in the following scenarios.
1) When we have a Generic Extractor based on a View and this View has multiple table(For Example 2 Tables to start with).
Then how wil you have the Generic Delta based on which field from which table? FOr example Table 1 has Header Data and Table2 has Item Data.Our Functional Consultant says Header can change or Item data can change.So we need to pick up the record based on the change in each of the tables. For Example , there is a field called CHANGED DATE(AENDT) which is present in both the tables. Now , in the view if I add AENDT from Table1, then Table1's chnages will only be updated i guess. What if the change occurs in TABLE2 (ITEM).
I dont know how to go about this. The solution is I created two Generic Extractors with two views (The only difference between the views is AENDT field coming from TABLE1 in the first extractor and AENDT field coming from TABEL2 in the second Extractor).But I think this is not the best way and there must be an alternative for this
2) The other issue is If I have a Function Module which Brings data from Multiple Tables, then how to select the field on which Delta is set.Do we need to write some Logic. After writing the logic, can we directly set the Generic Delta in RSO2 or is there any other way to do it.
Regards,
Samir

Hi Samir,
We too had a simliar requirement. In your case you can create a FM generic datasource on top of the view. The view in your case will get the intersection of the Header and Item level data. the main challenge was to get the delta records as we can have both Orders created and changed , and in Delta can be maintained on only one field.
To overcome this issue in the FM coding, Steps:
create Generic datasource, with Delta on changed on date (AENDT)
So during extraction you get the date on which the last Load was succesfully completed using the (AENDT).
So in the selection part use the statement similar to this:
      select * from vbap into table it_order where
                             ( erdat in l_r_erdat or aedat in l_r_zaedat ) and
                             ( erdat in l_r_aedat or aedat in l_r_aedat )
Sample generic datasource for your reference:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/403b299b-94e5-2c10-a3b4-e2cecb8ee869?quicklink=index&overridelayout=true
Hope this helps.
Regards,
Umesh.

Generic extraction - Delta Update

I am creating a generic extractor to extract PM confirmations data from AFRU table. I need to make it delta enable. how do I decide which field to use for delta relevant check? any ideas?

Hi,
Take a look at the blog below.It is telling very well delta concept in BW.Also check how to guide.
/people/swapna.gollakota/blog/2007/12/27/how-does-a-datasource-communicates-delta-with-bw
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-dbb4356cf4bf
Regards.

Delta load from planning area to third party system

Hi All,
Generally we sent full data load from DP planning area to back up cube in BW system..But suppose we are to send delta load from DP planning area to third party BW system, then what changes we need to do on the DP planning area side so that we send all the changed data from livecache. Can this be done in a standard way?
Thanks

Hi Tarun,
It's not possible to extract delta loads from the APO planning areas. The delta loads are only possible with standard BW objects, and planning area is not a BW object.
SAP doesn't provide the functionality to have delta loads when you use export data source based on the planning area.
PS: From backup point of view, anyway having delta load would not make much sense. We take the backup as a snapshot of a particular time, and if restoration is required, based on the request numer or the date of extraction, we restore the relevant data from cube to the planning area.
Thanks - Pawan

Delta loading in Generic extraction

Hi Everybody,
Can anybody explain the procedure of delta loading in generic extraction.
With Regards
Raju

Raju,
Just goto RSO2->Enter your datasource name->Click Generic Delta
Select one in Delta Specfied field.
Either Time stamp or Calender day or numeric Pointer.
If you select Numeric Pointer then enter the filed name on which you want to creat delta in Field name.
Or just browse in Field name , it will display you all valid fields for delta.
Check new status for changed records.
Now save.You know the next steps.
If you need any thing else.Buzz me.
Thanks
Ram
"BW is Everywhere"
Then make necessary setting in setting.
Safety interval upperlimit-1
Safety interval lowetlimit-1

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

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

Delta loading through Generic extractor - function module not found

Hi,
I'm working on a BW3.5 system and we have some generic delta FM extractors. One of these is called ZBW_CONF_DELTA and the FM is also called ZBW_CONF_DELTA. It is a delta-enabled extractor. Whenever an extraction is done in the init delta mode, the data gets picked up from SAP.
However, whenever we load subsequent deltas, the extractor brings zero records. When I look in the SM37 logs in R/3, it says "Function module /BIC/QIZBW_CONF_DELTA0001 does not exist"
I'm not sure where the "/BIC/QIZBW_CONF_DELTA0001" function module name came from, because I haven't given it like that (if I did, the init load would also have failed).
Due to this problem, I'm unable to perform any delta loads. Is there anything I could be doing to fix this?
Regards

Hi,
First check how extractor works in R/3 side using RSA3
Make a full load.
Now check the generic delta field of your generic extractor, lets say changed on date.
Do the SAP transaction ( take help from some Functional COnsultant ) to update that delta field. Note that record.
Now if u do the delta load with same extractor, you are suppose to get that record.
If not then there is some problem with FM or extracor.
Let me know what happens.
Thank-You.
Regards,
Vinod

Difference between Generic extraction and Generic Delta

Hi Experts,
Pleasee give of some information below query:
1) Difference between Generic extraction and Generic Delta.
2) How to achieve Generic delta.
3) When we go for Generic delta instead of generic extraction.
Advance ThankU. Points vl be assigned.
Thanks,
Ragu.R

Hi,
Generic delta is the delta load done using Generic DS.
Generic extraction
Usage:
1. When the standard extractors are not supporting the extraction what you need. If SAP does not have a standard extractor for your need to get data from R3, you would have to go for generic extractor.
2. If you create a custom object say by combining certain base tables in R3 say custom tables ZTAB1 and ZTAB2. These two tables are not SAP provided tables and there will not be any standard extractors. So cases like this you will have to go for generic extractors.
How:
You have to use RSO2 transaction and you can also set delta based on, one of the three characteristics such as timestamp, calday or pointer (a sequence no).
once you create it and activate it. The extractor will be available in ROOSOURCE - (table in R3 where all the data sources are available).
Refer:
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
http://help.sap.com/saphelp_nw04/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
Generic Extraction via Function Module
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
thanks,
JituK

Deltas in generic extraction

how can we set delta updates in generic extraction?can any one help in this

Hi Praveen,
Please do check the link for step by step for generic extraction
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
check the following
http://help.sap.com/bp_biv235/BI_EN/html/bw.htm
business content
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/g-i/how%20to%20co-pa%20extraction%203.0x
https://websmp203.sap-ag.de/co
http://help.sap.com/saphelp_nw04/helpdata/en/37/5fb13cd0500255e10000000a114084/frameset.htm
(navigate with expand left nodes)
Check these links:
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
<b>For Generic:</b>
>Go to Tcode : RSO2,
>There give the name of data source which you want to create like transaction data source or master data attribue or Text data source.
>enter
>again in the next screen you need to give application like SD or MM etc
>in the same screen need to select table/view or infosetquery or function module. these are different ways of creating data sources.
>Give the name for the same like if u r creating data source on table give the name of table.
>click on Generic delta which will there in application tool bar and fill the required columns in that screen like type of delta and all
>continue and save
>it will give all the fieds
>enable the check boxes based on your requirement like selection or hide or field only..
>save
Hope This Helps.
Regards,
Ravikanth

Generic extraction loading and performances issues

hi,
any one can give the details about the generic extraction loading as well as performance issues.
advance thanks
regards
praveen

Hi,
when there is no suitable business content datasource we go for creating generic data source.
by using generic data source we can extract data present in single or multiple tables.
If the data is present in the single table we go for generic data source extracting from table.
If the data that is to be extracted is present in multiple tables and the relation between the tables is one to one and if there is a common field in both the tables we create a view on these tables and create a generic data source extracting from view.
if you want to extract data from different tables and there is no common field we create a info set on these tables and create a generic datasource extracting from query.
if you want to extarc the data from different tables and the relation is one to many or many to many we create a generic data source from function module.
If we extarct from function module ,at run time it has to execute the code and brings the data to BW.so it degrades the loading performance.
regards,

Generic Extraction Delta Loads

Similar Messages

Maybe you are looking for