RESB Extraction with Delta

Hi All,
I have a requirement to extract data from RESB(Reservation) table. There is no create Date or Date field in the table.
My Question is:
1. How to extract data from RESB table with Delta option.
2. Is there any standard data source to extract data from RESB table.
Your earliest response will be highly appreciated.
Thanks,
Bsreddy

Hi,
well I'm not sure if there is a standard extractor but anyway, you can goto table aufk. There you have a creation as well as a change date. This might help.
regards
Siggi
PS: Additionally you might look here: http://help.sap.com/saphelp_nw04/helpdata/en/28/500b3c56488e6be10000000a114084/frameset.htm

Similar Messages

Generic Extraction with delta

Hi Every one,
I use an extractor based on a function module which is copy of the RSAX_BIW_GET_DATA_SIMPLE and gets delta records.
I have a doubt of how the communication happens between BW and R/3 when delta info package is ran inorder to get delta records.
Can any one explain how this FM RSAX_BIW_GET_DATA_SIMPLE works ie., the input parameters,usage of static var, Cursors etc?
FUNCTION RSAX_BIW_GET_DATA_SIMPLE.
""Lokale Schnittstelle:
*" IMPORTING
*"     VALUE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUNR
*"     VALUE(I_DSOURCE) TYPE SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
*"     VALUE(I_MAXSIZE) TYPE SRSC_S_IF_SIMPLE-MAXSIZE OPTIONAL
*"     VALUE(I_INITFLAG) TYPE SRSC_S_IF_SIMPLE-INITFLAG OPTIONAL
*"     VALUE(I_READ_ONLY) TYPE SRSC_S_IF_SIMPLE-READONLY OPTIONAL
*"     VALUE(I_REMOTE_CALL) TYPE SBIWA_FLAG DEFAULT SBIWA_C_FLAG_OFF
*" 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 SFLIGHT OPTIONAL
*" EXCEPTIONS
*"      NO_MORE_DATA
*"      ERROR_PASSED_TO_MESS_HANDLER
Example: DataSource for table SFLIGHT
TABLES: SFLIGHT.
Auxiliary Selection criteria structure
DATA: L_S_SELECT TYPE SRSC_S_SELECT.
Maximum number of lines for DB table
STATICS: S_S_IF TYPE SRSC_S_IF_SIMPLE,
counter
          S_COUNTER_DATAPAKID LIKE SY-TABIX,
cursor
          S_CURSOR TYPE CURSOR.
Select ranges
RANGES: L_R_CARRID FOR SFLIGHT-CARRID,
          L_R_CONNID FOR SFLIGHT-CONNID.
Initialization mode (first call by SAPI) or data transfer mode
(following calls) ?
IF I_INITFLAG = SBIWA_C_FLAG_ON.
Initialization: check input parameters
                buffer input parameters
                prepare data selection
Check DataSource validity
    CASE I_DSOURCE.
      WHEN '0SAPI_SFLIGHT_SIMPLE'.
      WHEN OTHERS.
        IF 1 = 2. MESSAGE E009(R3). ENDIF.
this is a typical log call. Please write every error message like this
        LOG_WRITE 'E'                  "message type
                  'R3'                 "message class
                  '009'                "message number
                  I_DSOURCE   "message variable 1
                  ' '.                 "message variable 2
        RAISE ERROR_PASSED_TO_MESS_HANDLER.
    ENDCASE.
    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.
Fill field list table for an optimized select statement
(in case that there is no 1:1 relation between InfoSource fields
and database table fields this may be far from beeing trivial)
    APPEND LINES OF I_T_FIELDS TO S_S_IF-T_FIELDS.
ELSE.                 "Initialization mode or data extraction ?
Data transfer: First Call      OPEN CURSOR + FETCH
               Following Calls FETCH only
First data package -> OPEN CURSOR
    IF S_COUNTER_DATAPAKID = 0.
Fill range tables BW will only pass down simple selection criteria
of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
      LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'CARRID'.
        MOVE-CORRESPONDING L_S_SELECT TO L_R_CARRID.
        APPEND L_R_CARRID.
      ENDLOOP.
      LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'CONNID'.
        MOVE-CORRESPONDING L_S_SELECT TO L_R_CONNID.
        APPEND L_R_CONNID.
      ENDLOOP.
Determine number of database records to be read per FETCH statement
from input parameter I_MAXSIZE. If there is a one to one relation
between DataSource table lines and database entries, this is trivial.
In other cases, it may be impossible and some estimated value has to
be determined.
      OPEN CURSOR WITH HOLD S_CURSOR FOR
      SELECT (S_S_IF-T_FIELDS) FROM SFLIGHT
                               WHERE CARRID IN L_R_CARRID AND
                                     CONNID IN L_R_CONNID.
    ENDIF.                             "First data package ?
Fetch records into interface table.
named E_T_'Name of extract structure'.
    FETCH NEXT CURSOR S_CURSOR
               APPENDING CORRESPONDING FIELDS
               OF TABLE E_T_DATA
               PACKAGE SIZE S_S_IF-MAXSIZE.
    IF SY-SUBRC <> 0.
      CLOSE CURSOR S_CURSOR.
      RAISE NO_MORE_DATA.
    ENDIF.
    S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
ENDIF.              "Initialization mode or data extraction ?
ENDFUNCTION.
Also how the delta queue is loaded in rsa7 when the delta records made?
When the delta info package is ran, the delta queue in rsa7 is changed to '0'.How is that communication made in between them?
Please clear my doubts?
Regards,
Pra

Hi Suneel,
You can load delta to write optimized DSO. Your Data source will have delta load (through infopackage) and then with DTP (with Extraction Mehtod --> Delta) you can load delta records to this write optimized DSO. So only the new requests, which are not loaded yet will be loaded to WO-DSO. I tried it in system and it works.
They can be used in the following scenarios:
●      You use a write-optimized DataStore object as a temporary storage area for large sets of data if you are executing complex transformations for this data before it is written to the DataStore object. The data can then be updated to further (smaller) InfoProviders. You only have to create the complex transformations once for all data.
●      You use write-optimized DataStore objects as the EDW layer for saving data. Business rules are only applied when the data is updated to additional InfoProviders.
it is used when you don't want to wait for DSO activation and error troubleshooting. It will make raportable data available instantly.
Hope it helps...
Regards,
Ashish
Edited by: Ashish Tewari on May 6, 2009 1:33 PM

Issue with delta queue initialization

Hello
I am having a problem with an initialization of the delta queue for a certain extractor. The initialization was successfull, and I can see the extractor in the delta queue maintenance (RSA7) in ECC, but when users are posting transactions in ECC, they are not coming into RSA7.
The extractor is 0CO_OM_WBS_6, so its not standard LO cockpit where we have V3 (background) jobs which have to be triggered.
One more thing, the record which was posted was backdated, ie the date is sometime in the past. But I think the delta queue still picks the records. Can i know how the delta queue funtions based on the time stamp?
Please advise.

Here is the OOS note fro FI Datasources.
OSS 485958:
Symptom
The FI line item delta DataSources can identify new and changed data only to the day because the source tables only contain the CPU date and not the time as time characteristic for the change.
This results in a safety interval of at least one day.
This can cause problems if the batch processing of the period-end closing is still running on the day following the period-end closing and all data of the closed period is to be extracted into BW on this day.
Example:
The fiscal year of the company ends on December 31, 2002.
On January 01, 2003, all data of the closed fiscal year is to be extracted into BW.In this case, the FI line item delta DataSources only extract the data with a safety interval of at least one day.
This is the data that was posted with a CPU date up to December 31, 2002.
However, the batch programs for closing the 2002 fiscal year are still running on January 01, 2003.
The postings created by these programs with a January 01 date for the 2002 fiscal year can therefore only be extracted with delta extraction on January 02, 2003. However, extraction should already be possible on January 01, 2003.
Other terms
FI line item delta DataSources
0FI_AP_4; 0FI_AR_4; 0FI_GL_4
Reason and Prerequisites
This problem is caused by the program design.
Solution
The functions are enhanced as of PI 2002.1, standard version.
Due to a customized setting, it is now possible for the FI line item extractors to read the data up to the current date during the delta runs.
During the next delta run, the data is then read again from the day when the previous extraction was called, up to the current day of the call for the new extraction.This means that the delta extraction of the data always occurs with time intervals overlapping by one day.
The delta calculation by the ODS objects ensures that the repeatedly extracted data does not cause duplicate values in the InfoCube.
Activate the new functions as follows:
1. PI 2001.1 or PI 2001.2:
Implement the new functions with the correction instructions in this note.As of PI 2002.1, these changes are already implemented in the standard version.
1. Start a test run for an FI line item DataSource via transaction RSA3.
2. Two new parameters are now available in the BWOM_SETTINGS table.
3. Parameter BWFIOVERLA (Default _)
Set this parameter to "X" using transaction SE16, to activate the new function of overlapping time intervals.
Caution
The new function also uses a safety interval of one day to determine the To value of the selection, if the time limit set by BWFITIMBOR is not reached.This means that only data up to the day before the extraction was called is selected, if the extraction starts before 02:00:00 (default for BWFITIMBOR).
Correction: Parameter BWFITIMBOR (Format HH:MM:SS, default 020000)
The default value for this parameter is 02:00:00.Do not change this value.
If this time limit is not reached, only data up to the previous day (with BWFIOVERLA = 'X') or the day before this day (with BWFIOVERLA = ' ') is selected.
This logic prevents records with a CPU date of the previous day being contained in the posting when the extraction is executed.
Check any OSS notes for your data source.

Generice extracttion with delta

if we do generic extraction with delta in which table luws will be stored

LUW's for generic delta can be monitored in RSA7.
BW Delta queue is based on queue functions in the RFC technology for SAP Web Application servers (qRFC). The data is stored in the following 3 tables:
1. TRFCQOUT (Client Dependent pointer table per queue name and destination.
2. ARFCSSTATE: Likn between TRFCQOUT and ARFCSDARA
3. ARFCSDATA: Compressed data for tRFC/qRFC
refer following: http://help.sap.com/saphelp_nw04/helpdata/en/6f/66bca6ae43744283d74f1e456ff6c0/content.htm for delta queue maintenance.

BI 7.3 delta extraction with SQL Server 2008

Hi experts,
I'm trying to extract data with delta update from a SQL Server with UD Connect, i test this ways:
Field DateTime in SQL Server: The problem is I only can delta within a day, no changes detected in the same day because SAP detects two fields here date and time, and can only can reference date field as a delta field.
Field TimesTamp in SQL Server: The problem seems the same, SAP recognize this as a date and time field.
Can any explain here the correct way for a delta implementation with SQL Server 2008? I would be very grateful.
Regards,

Hi Fernando
That is what I need to do.
Create a Model from an existing SQL Server database with the Import data Dictionary option , be able to modify tables structures, extended properties in the model, and then sync those changes with the database.
So far I can't import the extended properties with DM 3.1.1. If you find a way , please let me know.
Thanks,
Jorge

Error in delta extraction with SAP DataSource 2LIS_11_VAHDR ...

Hi all
I used the old data load process(3.5) in 2004s system.
There are errors in detla extraction with SAP data source
2LIS_11_VAHDR
2LIS_11_VAITM
2LIS_12_VCHDR
2LIS_12_VCITM
The delta data(before/after image) aren't right.
Has anyone experices with this problem?
thanks in advance

No Problems yet,explain the error message with error number in details here for some one to help you.
Hope it Helps
Chetan
@CP..

Data with delta extraction.

Hi Gurus
I want a small clarification regarding data with delta extraction.
If today the data is extracted from r/3 system with delta to ODS object and the data is activated and datamarted to another ODS and Cube.
Now if tomorrow the same records had changes how will the old data will be changed i.e in cube if we compress the old data what is the scnerio.
Can anyone explain in detail starting from Delta queue to change taking place at cube.
Regards
Raju

Raju,
Don't worry about compression of Cube... Even if you do delta after compression, nothing to worry about Data. Next time you compress it, it will Make 1 record.
Assume...
Initially... in ODS Document 45000001 Item 0001 qty 10 Amount 20
in Cube Document 45000001 Item 0001 qty 10 Amount 20 (After compression)
Qty changed to 5...
In ODS Document 45000001 Item 0001 qty 5 Amount 10. This record will create 2 delta records to Cube.
that is looks like this...
Document 45000001 Item 0001 qty -10 Amount -20 Record mode ' X' (Before Image)
in ODS Document 45000001 Item 0001 qty 5 Amount 10 Recordmode ' " (After Image)
Finally cube contains...
Document 45000001 Item 0001 qty 10 Amount 20
Document 45000001 Item 0001 qty 10 Amount -20
ODS Document 45000001 Item 0001 qty 5 Amount 10
If you compress cube... you will endup with last record.
all the best.
Nagesh Ganisetti.

3FI_SL_C1_TT - Procedure of extracting data with delta

Dear experts,
I try to load FI-SL data with delta.
We use extractor 3FI_SL_C1_TT and have implemented the start routine from note 577644 to create 0balance within the transformation.
Delta is only available for actuals so we select data only for valuetype 10 as recommended.
I read that I have to do a full update of the closed periods.
To load the carryforward from 2014 I have to select 000.2015 and load it with a full load.
Till now every thing is clear.
But what are the next steps?
What do I have to select within the infopackage for the init load of the open periods (current year)?
After executing the init load: how do I have to define the delta load?
Thanks for your help.
Best regards
Mirjam

Hi Leszek,
we use cube for each year.
So when the periods of the previous year (2014) is not closed, too, I have to work with them
the same as with cube for current year and do at first an init for the whole year and after that a Delta for whole year.
For current year cube I try do init/Delta with 001.2015 - 016.9999. But what do I do with the carryforward -
I can´t do only once a full, case with every new data record for 2014 it will Change.
What is the best practise with carryforward in this case?
Regards,
Mirjam

Problem with delta update on customised export data source.

Hi all BW gurus,
I have created several customised export data sources in the R/3 system. And I have made use of the utility program <Z_CHANGE_DELTA_PROCESS> to update the ROOSOURCE table.
While this can result in being able to do initial update (instead of full update), the subsuquent delta update is not working.
In RSA7, the datasource is with green light and in RSA3, the extractor can extractor data out of it.
Does anybody have some idea on this?
I heard that there is a way to change the Business Transaction Event (BTE), but I don't quite understand how this is performed. And wonder if this is the only way out. To me, the triggering point would be the same, meaning the InfoPackage would be executed, then call the extractors in R/3 to extract the delta update in order to load into the InfoCube.
And how do others do for executing delta update of the customised data source?
Thanks a lot!!
The utility program of <Z_CHANGE_DELTA_PROCESS>:
=================================================
report z_change_delta_process .
*P_DATAS DataSource
*P_DELTAP Delta Process for DataSource
parameters:
p_datas type roosource-oltpsource,
p_deltap type roosource-delta.
tables:
roosource.
data:
ls_roosource type roosource.
if p_datas(2) ne 'Z_'.
   message 'The DataSource needs to begin with ''Z_''.' type 'E'.
endif.
select single * from roosource into ls_roosource
       where oltpsource = p_datas
       and objvers = 'A'.
if sy-subrc eq 0.
   ls_roosource-delta = p_deltap.
   update roosource from ls_roosource.
message 'The DataSource has been updated successfully.' type 'I'.
else.
   message 'The DataSource entered is not valid, try again.' type 'E'.
endif.

Doesn't anyone have any idea on this topic?
Appreciate for all the help. Thanks.

Issue with Delta in Function Module

Hi Team,
I have an issue with delta in Genric extraction using function module.Full load is working fine and i have taken post_date as delta field.plz chk the code if any delta related statements are missing.
FUNCTION ZRSAX_BIW_MANGEMENT_RAT .
""Local interface:
*" IMPORTING
*"     VALUE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUNR
*"     VALUE(I_DSOURCE) TYPE SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
*"     VALUE(I_MAXSIZE) TYPE SRSC_S_IF_SIMPLE-MAXSIZE OPTIONAL
*"     VALUE(I_INITFLAG) TYPE SRSC_S_IF_SIMPLE-INITFLAG OPTIONAL
*"     VALUE(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 ZQMBW_FUJ_MANAGEMENT OPTIONAL
*" EXCEPTIONS
*"      NO_MORE_DATA
*"      ERROR_PASSED_TO_MESS_HANDLER
Example: DataSource for table MANAGEMENT RATING
TABLES: ZQMBW_MANAGEMENT.
Auxiliary Selection criteria structure
DATA: L_S_SELECT TYPE SRSC_S_SELECT.
Maximum number of lines for DB table
STATICS: S_S_IF TYPE SRSC_S_IF_SIMPLE,
counter
          S_COUNTER_DATAPAKID LIKE SY-TABIX,
cursor
          S_CURSOR TYPE CURSOR.
RANGES: POST_DATE FOR ZMMTVEND_RATING-POST_DATE,
          VENDOR FOR ZMMTVEND_RATING-VENDOR.
Initialization mode (first call by SAPI) or data transfer mode
(following calls) ?
IF I_INITFLAG = SBIWA_C_FLAG_ON.
Initialization: check input parameters
                buffer input parameters
                prepare data selection
Check DataSource validity
    CASE I_DSOURCE.
      WHEN 'ZQMMANAGEMENT_DS'.
      WHEN OTHERS.
        IF 1 = 2. MESSAGE E009(R3). ENDIF.
this is a typical log call. Please write every error message like this
        LOG_WRITE 'E'                  "message type
                  'R3'                 "message class
                  '009'                "message number
                  I_DSOURCE   "message variable 1
                  ' '.                 "message variable 2
        RAISE ERROR_PASSED_TO_MESS_HANDLER.
    ENDCASE.
    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.
Fill field list table for an optimized select statement
(in case that there is no 1:1 relation between InfoSource fields
and database table fields this may be far from beeing trivial)
    APPEND LINES OF I_T_FIELDS TO S_S_IF-T_FIELDS.
ELSE.                 "Initialization mode or data extraction ?
    IF S_COUNTER_DATAPAKID = 0.
Fill range tables BW will only pass down simple selection criteria
of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
      LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'VENDOR'.
        MOVE-CORRESPONDING L_S_SELECT TO VENDOR.
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
          EXPORTING
            INPUT = VENDOR-LOW
          IMPORTING
            OUTPUT = VENDOR-LOW.
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
          EXPORTING
            INPUT = VENDOR-HIGH
          IMPORTING
            OUTPUT = VENDOR-HIGH.
        APPEND VENDOR.
      ENDLOOP.
      LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'POST_DATE'.
        MOVE-CORRESPONDING L_S_SELECT TO POST_DATE.
        CONCATENATE L_S_SELECT-LOW6(4) L_S_SELECT-LOW3(2) L_S_SELECT-LOW+0(2) INTO POST_DATE-LOW.
        CONCATENATE L_S_SELECT-HIGH6(4) L_S_SELECT-HIGH3(2) L_S_SELECT-HIGH+0(2) INTO POST_DATE-HIGH.
        APPEND POST_DATE.
      ENDLOOP.
**Get Management rating details
      OPEN CURSOR WITH HOLD S_CURSOR FOR
      SELECT VENDOR POST_DATE OVERALL_MNGT_RAT OVERALL_DEV_RAT FROM ZMMTVEND_RATING WHERE VENDOR IN VENDOR AND POST_DATE IN POST_DATE .
    ENDIF.
Fetch records into interface table.
    FETCH NEXT CURSOR S_CURSOR
               APPENDING CORRESPONDING FIELDS
               OF TABLE E_T_DATA
               PACKAGE SIZE S_S_IF-MAXSIZE.
    S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
    IF SY-SUBRC <> 0.
      CLOSE CURSOR S_CURSOR.
      RAISE NO_MORE_DATA.
    ENDIF.
ENDIF.              "Initialization mode or data extraction ?
ENDFUNCTION.

Hi
Check URLs:
How to populate the ranges using FM for the SELECTs
Re: Generic Delta Function Module

Issue with Delta Load in BI 7.0... Need resolution

Hi
I am having difficulty in Delta load which uses a Generic Extractor. The generic extractor is based on a view of two Tables. I use the system date to perform the delta load. If the system date increaes by a day, the load is expected to pick up the extra records. One of the tables used in the view for master data does not have the system date in it.
the data does not even come up to PSA. It keeps saying there are no records.... Is it because I loaded the data for yesterday and manually adding today's data...?
Not sure what is the cuase of delta failing....
Appreciate any suggestions to take care of the issue.
Thanks.... SMaa

Hi
The Generic DataSource supports following delta types:
1. Calender day
2. Numeric Pointer
3. Time stamp
Calday u2013 it is based on a calday, we can run delta only once per day that to at the end of the clock to minimize the missing of delta records.
Numeric pointer u2013 This type of delta is suitable only when we are extracting data from a table which supports only creation of new records / change of existing records.
It supports
Additive Delta: With delta type additive delta, the record to be loaded only returns the respective changes to key figures for key figures that can be aggregated. The extracted data is added in BI (Targets: DSO and InfoCube)
New status for changed records: With delta type new status for changed records, each of the records to be
loaded returns the new status for all key figures and characteristics. The values in BI are overwritten (Targets: DSO and Master Data)
Time stamp u2013 Using timestamp we can run delta multiple times per day but we need to use the safety lower limit and safety upper limit with minimum of 5 minutes.
As you specified, the DS is based on VIEW (of two tables, with one containing date and other does not).
Kindly check the above lines and verify, if the view (primary key) could be used to determine the Delta for your DS.
Also let us the if any standard SAP tables used in creating VIEW and if so, what is the size of the DS load every day?
Thanks.
Nazeer

Issue with delta load from R/3 to BW

Hi frnds,
There is a standarded D.S 2LIS_05_ITEM in R/3. Evereday We extraceted data from R/3 to BW based on this standard Data Source with delta load.There are two fields ZX and ZY in BW ,some times the data haven't extracted for this 2 fields in BW with the delta update.But some times this 2 fields properly extracted in to BW with the same delta update.
Why is it happen like this ? Please give some inputs on this.
Regards,
Satya.

Hello,
if its a standard field then its getting populated in correct way.
if its custom field then you need to analyze the records for which its getting populated and for one which its not.
Quite possible that some cutomization in CMOD results in this behaviour.
Also,check underlying tables to see the correct values.
Regards
Ajeet

Function Module Extractor with Delta Functionality

Hi Friends,
I have to extract the entire data of CDPOS table in R/3 , as its a cluster table I am unable to build a view, I am planning to go for FM extraction, Could someone help me as how to build it with Delta Functionality.
I think I need to develop the Datasource, with Extract Structure,( Do I need to create a Structure in SE11) Please help me out .
Thanks,
Krish

Hi,
you can either use an existing structure or else create one on your own. (SE11).
The DeltaHandlig fairly easy.
When having finished the extractor (FunctionModule, Structur and DatasSource), go to the "generic Delta" button and select the relevant field.
The Generic Delta and its DeltaPointer is managed within the DeltaQueue (RSA7) and works more or less like a selection. Don't think too hard about it in your function module except taht you need to select by this field in your FM.
Did that come clear?
hth
Cheers
Sven

Custom Extractor FM with Delta mode

I have looked a few blogs that dont seem to address the whole picture.
the online help looks to be wrong?
http://help.sap.com/saphelp_nw70/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/frameset.htm
Im trying to set up an FM to do generic extraction.
Declare Datasource in RSo2. With Generic delta... all looks BUT
RSa3 can call th FM.
Seems the ROOSOURCE entry was with type F2.
If I copied a "proper" generic delta with complex interface and not the simple interface,
the entry in roosurce looks wrong to me.
What is the normal way to maintain the data source so that generic extraction works and can be tested in RSa3.
I also found this blog:
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
again the issue of deltas is over looked.
The demo function is RSA3_GEN_GET_DATA
BUT when create a dat source with rso2, the function interface used to call teh function
matches function RSAX_BIW_GET_DATA_SIMPLE
and not RSA3_GEN_GET_DATA.
The helpd refers to delta mode, but the interfae does NOT have the upmode flag.
Am i missing something or is this a whole in the RSo2 process.
Custom FM based extractors CAN NOT be called with delta mode.
surely someone knows what the trick is here ?
Cheers
Phil.
Edited by: Phil Soady on Aug 25, 2009 7:00 AM

https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/67efb9bb-0601-0010-f7a2-b582e94bcf8a
No reference here either.
my conclusion that without using pseudo deltas, ie adding a field called delta mode, to the structure
and programming over the simple interface with a extra field
or
build a full F1 complex datasource definition tool,
there is no good standard solution.
Im still interested if anyone has a good approach to this.
regards
phil

Error in LO Extraction with BI7 .

Hi All,
Can anyone suggest me as to how to proceed with LO extraction with Queued Delta method. do we need to activate the Queue manually to work with Delta in LBWQ , I am unable to get the Init load running. I have filled up the setup tables aswell..
Thanks,
Krish..
Points are awarded for a solution.

Hi,
1) Stop all your R/3 users to stop the creation or changing the records in case your R/3 system is PROD
2) set the update mode is Queue delta in LBWE
3) Fill the setup table
4) Create and execute the info package with delta init
5) Schedule the collective run from Tcode LBWE
6) Create and execute the info package with delta load.
With rgds,
Anil Kumar Sharma .P

RESB Extraction with Delta

Similar Messages

Maybe you are looking for