Delta in Generic

Hi SAP Gurus
We are using generic extraction to extract sales orders data.
We are sending data to the ODS then into the Info cube.
Frequency of upload to BI is daily.
Every night job will run to upload the data into the Info cube. Everyday Sales transaction will be stored in the respective data targets.
What delta settings need to be maintained to get changed records to BI?where need to maintain these settings?
Please provide me the information with regard to this.
regards
Vicky

Tips:
1. If delta field is Date (Record Create Date or change date), then use Upper Limit of 1 day.
This will load Delta in BW as of yesterday. Leave Lower limit blank.
2. If delta field is Time Stamp, then use Upper Limit of equal to 1800 Seconds (30 minutes).
This will load Delta in BW as of 30 minutes old. Leave Lower limit blank.
3. If delta field is a Numeric Pointer i.e. generated record # like in GLPCA table, then use
Lower Limit. Use count 10-100. Leave upper limit blank. If value 10 is used then last 10
records will be loaded again. If a record is created when load was running, those records
may get lost. To prevent this situation, lower limit can be used to backup the starting
sequence number. This may result in some records being processed more than once;
therefore, be sure this DataSources is only feeding an ODS Object
(Goto RSO2 give the Datasource Name and dispaly Click on Generic Delta and assign)

Similar Messages

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.

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 for Generic Extraction

Hi all,
Can anyone tell about delta for generic extraction i.e 3 options in detail and when do we use it.
thanks in advance,
chandra sekhar

When you want to customize existing datasources at R/3 sides then you can do that with customer exits.
Suppose if you want to add a column to the existing datasource then you will use append structures (Transaction SBIW-> Edit Data sources - Enhance Datasource) then to fill the column you will write the code in these Exits.
There are 4 types of Exits available.Function Group (XRSA)
EXIT_SAPLRSAP_001 Customer Function Call for Supplying Transaction Data
EXIT_SAPLRSAP_002 Customer Function Call for Supplying Master Data (Attributes)
EXIT_SAPLRSAP_003 Customer Function Call for Supplying Text
EXIT_SAPLRSAP_004 Customer Function Call for Supplying Hierarchies
As you are aware there 4 types since the datasources in R/3 are predefined to fill the data of BW viz, attributes,Text,Hierarchy and Transaction.
Check the below forum discussion for more information..
DataSource Enhancement
Regs
Gopi
Assign point if it helps ...

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 using generic data source

Hi experts !
How can i create a delta using generic data source ? i am using BW 7.0.
Thanks.

Dear FABRICIO VAZ DE SOUZA ,
Generic extraction
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
step by step procedure for generic extraction delta
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
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
Hope it helps you,Revert me back if you have any queries
Assign points if helpful
Regards
Bala

Delta Enabled Generic Data Source

Hi All,
I have created one Delta Enabled Generic Data Source with
Function Module. The Delta field is Date Field. The Data source picks data from R3 to BW.
In RSA3, I executed the Extractor with the Delta Type "C" i.e Delta Initialization ... but it is throwing the error "Errors occured during the extraction". I also checked the Display Log and the error message is "Could not determine BW release of logical system".
Moreover I am not able to see the Delta Attributes in
RSA7. I checked with the other delta enabled generic extractors which uses Views .. is found to be working fine ... and I also able to see the Delta Attributes in RSA7.
Any suggestions?
Bye
Dinesh

Dinesh,
Once you have generated transfer rules in BW for the datasource, delta init can be tried out in RSA3. It iwll not create the delta queue though. Only test the initialization.
To do this, once you have created the transfer rules in BW, specify the logical system name of the BW system in the target system field. After that the extractor can be run in RSA3. It is flagged as read only so delta queue will not get created.
Cheers
Aneesh

Delta in Generic data extraction

Hi all,
I have a doubt here,
What is the delta in Generic Data extraction?
What are the types?
and what are their significances?
Please give reply.
Thanks
Surya.

Hi Surya,
If a field (date, progressive document number, timestamp) 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 (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).
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.
Hope now is clearer...
Bye,
Roberto

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.

Delta fo Generic extractor using function module

Hi,
I am using the following function module for generic extractor but its always showing me extraction error.Could anyone please suggest to resolve the issue.
Thanks in advance fo rsuggestion.
FUNCTION Z_BW_SALESDATA_EXTRACT_CHNG2.
""Local interface:
*" IMPORTING
*"     VALUE(I_REQUNR) TYPE SBIWA_S_INTERFACE-REQUNR
*"     VALUE(I_ISOURCE) TYPE SBIWA_S_INTERFACE-ISOURCE OPTIONAL
*"     VALUE(I_MAXSIZE) TYPE SBIWA_S_INTERFACE-MAXSIZE OPTIONAL
*"     VALUE(I_INITFLAG) TYPE SBIWA_S_INTERFACE-INITFLAG OPTIONAL
*"     VALUE(I_UPDMODE) TYPE SBIWA_S_INTERFACE-UPDMODE OPTIONAL
*"     VALUE(I_DATAPAKID) TYPE SBIWA_S_INTERFACE-DATAPAKID OPTIONAL
*"     VALUE(I_PRIVATE_MODE) OPTIONAL
*"     VALUE(I_CALLMODE) LIKE ROARCHD200-CALLMODE OPTIONAL
*"     VALUE(I_REMOTE_CALL) TYPE SBIWA_FLAG DEFAULT SBIWA_C_FLAG_OFF
*" TABLES
*"      I_T_SELECT TYPE SBIWA_T_SELECT OPTIONAL
*"      I_T_FIELDS TYPE SBIWA_T_FIELDS OPTIONAL
*"      E_T_DATA OPTIONAL
*"      E_T_SOURCE_STRUCTURE_NAME OPTIONAL
*" EXCEPTIONS
*"      NO_MORE_DATA
*"      ERROR_PASSED_TO_MESS_HANDLER
The input parameter I_DATAPAKID is not supported yet !
Example: InfoSource containing TADIR objects
TABLES: VBFA,VBRK,tadir.
Auxiliary Selection criteria structure
DATA: l_s_select TYPE sbiwa_s_select.
Maximum number of lines for DB table
STATICS: l_maxsize TYPE sbiwa_s_interface-maxsize.
user defined variables.
DATA : X_UPDMODE(1) Type c,        " Update Type
        X_LastUpdate Like Sy-Datum. " Last Update Date
         X_LastUpdate TYPE RODELTAID. " Last Update Date   "TCS_KAP
Select ranges
RANGES: L_R_VBELN   FOR VBAK-VBELN,
          L_R_AUDAT   FOR VBAK-AUDAT.
Parameter I_PRIVATE_MODE:
Some applications might want to use this function module for other
purposes as well (e.g. data supply for OLTP reporting tools). If the
processing logic has to be different in this case, use the optional
parameter I_PRIVATE_MODE (not supplied by BIW !) to distinguish
between BIW calls (I_PRIVATE_MODE = SPACE) and other calls
(I_PRIVATE_MODE = X).
If the message handling has to be different as well, define Your own
messaging macro which interprets parameter I_PRIVATE_MODE. When
called by BIW, it should use the LOG_WRITE macro, otherwise do what
You want.
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
The input parameter I_DATAPAKID is not supported yet !
Invalid second initialization call -> error exit
    IF NOT g_flag_interface_initialized IS INITIAL.
      IF 1 = 2. MESSAGE e008(r3). ENDIF.
      log_write 'E'                    "message type
                'R3'                   "message class
                '008'                  "message number
                ' '                    "message variable 1
                ' '.                   "message variable 2
      RAISE error_passed_to_mess_handler.
      ENDIF.
Check InfoSource validity
    CASE i_isource.
      WHEN 'Z_BW_SDDATA_CREATEON'.
      WHEN 'Y'.
      WHEN 'Z'.
      WHEN OTHERS.
        IF 1 = 2. MESSAGE e009(r3). ENDIF.
        log_write 'E'                  "message type
                  'R3'                 "message class
                  '009'                "message number
                  i_isource            "message variable 1
                  ' '.                 "message variable 2
        RAISE error_passed_to_mess_handler.
    ENDCASE.
Check for supported update mode
   CASE i_updmode.
     WHEN 'F'.
     WHEN OTHERS.
       IF 1 = 2. MESSAGE e011(r3). ENDIF.
       log_write 'E'                  "message type
                 'R3'                 "message class
                 '011'                "message number
                 i_updmode            "message variable 1
                 ' '.                 "message variable 2
       RAISE error_passed_to_mess_handler.
   ENDCASE.
Check for obligatory selection criteria
   READ TABLE i_t_select INTO l_s_select WITH KEY fieldnm = 'VBELN'.
   IF sy-subrc <> 0.
     IF 1 = 2. MESSAGE e010(r3). ENDIF.
     log_write 'E'                    "message type
               'R3'                   "message class
               '010'                  "message number
               'PGMID'                "message variable 1
               ' '.                   "message variable 2
     RAISE error_passed_to_mess_handler.
   ENDIF.
   APPEND LINES OF i_t_select TO g_t_select.
Fill parameter buffer for data extraction calls
    g_s_interface-requnr    = i_requnr.
    g_s_interface-isource   = i_isource.
    g_s_interface-maxsize   = i_maxsize.
    g_s_interface-initflag = i_initflag.
    g_s_interface-updmode   = i_updmode.
    g_s_interface-datapakid = i_datapakid.
    g_flag_interface_initialized = sbiwa_c_flag_on.
Store Update mode in static variable...
   X_UPDMODE = I_UPDMODE.
    Select Single DELTAID
           Into   X_LastUpdate
           From   ROOSGENDLM
           Where OLTPSOURCE = 'Z_BW_SDDATA_CREATEON'.
    If X_LastUpdate Is Initial.
      X_LastUpdate = '19800101'. " The oldest..., this should not happen
    Endif.
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 g_t_segfields.
ELSE.                 "Initialization mode or data extraction ?
Data transfer: First Call      OPEN CURSOR + FETCH
               Following Calls FETCH only
X_UPDMODE = I_UPDMODE.
First data package -> OPEN CURSOR
    IF g_counter_datapakid = 0.
Fill range tables for fixed InfoSources. In the case of generated
InfoSources, the usage of a dynamical SELECT statement might be
more reasonable. BIW will only pass down simple selection criteria
of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
      LOOP AT g_t_select INTO l_s_select WHERE fieldnm = 'VBELN'.
        MOVE-CORRESPONDING l_s_select TO L_R_VBELN.
        APPEND L_R_VBELN.
      ENDLOOP.
      LOOP AT g_t_select INTO l_s_select WHERE fieldnm = 'AUDAT'.
        MOVE-CORRESPONDING l_s_select TO L_R_AUDAT.
        APPEND L_R_AUDAT.
      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 InfoSource table lines and database entries, this is trivial.
In other cases, it may be impossible and some estimated value has to
be determined.
*added by Yogesh
      DELETE FROM ZBWSALEDATA.
*ended by Yogesh
      l_maxsize = g_s_interface-maxsize.
Check for supported update mode
      CASE X_UPDMODE.
        WHEN 'F' Or 'I'. " Full or Init
**get sales orders
          SELECT *
                       INTO CORRESPONDING FIELDS OF TABLE I_SALESDATA
                       FROM VBAK AS K
                       INNER JOIN VBAP AS P
                             ON PVBELN = KVBELN
                       WHERE K~VBELN IN L_R_VBELN
                       AND   K~AUDAT IN L_R_AUDAT
                       AND   K~VBTYP = 'C'.
          IF I_SALESDATA[] IS NOT INITIAL.
            PERFORM F_GET_DATA.                   "get data
            PERFORM F_DEL_VATCOND.                "delete vat conditions
            PERFORM F_GET_TAR_COSTUNIT.           "get tariff cost unit
            PERFORM F_GET_NETVAL TABLES IT_VBDPA1. "get net val of the item
            PERFORM F_GET_SALESDATA.
*write perform with name F_INSERT_DB_ZBWSALEDATA.
            PERFORM F_INSERT_DB_ZBWSALEDATA.      "insert into table ZBWSALESDATA
           LOOP AT I_SALESDATA WHERE NETPR = 0.
             MOVE-CORRESPONDING I_SALESDATA TO I_SALESDATA_FIN.
             APPEND I_SALESDATA_FIN.
           ENDLOOP.
           SORT I_SALESDATA_FIN BY VBELN POSNR KSCHL.
           DELETE ADJACENT DUPLICATES FROM I_SALESDATA_FIN
                                           COMPARING VBELN POSNR
                                                     KSCHL.
           INSERT ZBWSALEDATA FROM TABLE I_SALESDATA_FIN.
          ENDIF.
        WHEN 'D'. " Delta
          SELECT *
                         INTO CORRESPONDING FIELDS OF TABLE I_SALESDATA
                         FROM VBAK AS K
                         INNER JOIN VBAP AS P
                               ON PVBELN = KVBELN
                        WHERE K~ERDAT >= X_LastUpdate
                         WHERE K~ERDAT >= X_LastUpdate+0(8)          "TCS_KAP
                         AND   K~VBTYP = 'C'.
          IF I_SALESDATA[] IS NOT INITIAL.
            PERFORM F_GET_DATA.                   "get data
            PERFORM F_DEL_VATCOND.                "delete vat conditions
            PERFORM F_GET_TAR_COSTUNIT.           "get tariff cost unit
            PERFORM F_GET_NETVAL TABLES IT_VBDPA1. "get net val of the item
            PERFORM F_GET_SALESDATA.
*write perform with name F_INSERT_DB_ZBWSALEDATA.
            PERFORM F_INSERT_DB_ZBWSALEDATA.      "insert into table ZBWSALESDATA
           LOOP AT I_SALESDATA WHERE NETPR = 0.
             MOVE-CORRESPONDING I_SALESDATA TO I_SALESDATA_FIN.
             APPEND I_SALESDATA_FIN.
           ENDLOOP.
           SORT I_SALESDATA_FIN BY VBELN POSNR KSCHL.
           DELETE ADJACENT DUPLICATES FROM I_SALESDATA_FIN
                                           COMPARING VBELN POSNR
                                                     KSCHL.
           INSERT ZBWSALEDATA FROM TABLE I_SALESDATA_FIN.
          ENDIF.
        WHEN OTHERS.
          IF 1 = 2. MESSAGE E011(R3). ENDIF.
          LOG_WRITE 'E' "message type
          'R3' "message class
          '011' "message number
          I_UPDMODE "message variable 1
          ' '. "message variable 2
          RAISE ERROR_PASSED_TO_MESS_HANDLER.
      ENDCASE.
**end get sales orders
      OPEN CURSOR WITH HOLD g_cursor FOR
      SELECT (g_t_fields) FROM ZBWSALEDATA.
     WHERE pgmid IN l_r_pgmid AND
                                    object IN l_r_object.
    ENDIF.                             "First data package ?
Fetch records into interface table. There are two different options:
- fixed interface table structure for fixed InfoSources have to be
named E_T_'Name of assigned source structure in table ROIS'.
- for generating applications like LIS and CO-PA, the generic table
E_T_DATA has to be used.
Only one of these interface types should be implemented in one API !
    FETCH NEXT CURSOR g_cursor
               APPENDING CORRESPONDING FIELDS
               OF TABLE E_T_DATA
               PACKAGE SIZE l_maxsize.
    IF sy-subrc <> 0.
      CLOSE CURSOR g_cursor.
      RAISE no_more_data.
    ENDIF.
    g_counter_datapakid = g_counter_datapakid + 1.
ENDIF.              "Initialization mode or data extraction ?
Best regards,
Yogesh

Dear Yogesh,
Try to debug the code by putting a break point at select statement...is the FM Syntactically correct ??
Check the Select statements..if all fields are not required avoid using Select * , and use always for all entries rather than JOINS..
Note : For Joins you have to specify the Fields in the Select...Dont use Select * ....
Hope it helps..
Thanks,
Krish

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.

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

Deltas in generic extractor

I am trying to have more then one field in my generic extractor as a delta and so far i can only set one field as delta in my generic extractor....can someone help me in setting more than one field as a delta in my custom generic extractor ????

The last delta performed will be stored in the ROOSGENDLM table....
Use this value and then fetch the delta pointers you need..
Here is how I would do it...
In the FM :
Look up value of DELTAID from table ROOSGENDLM for your datasource - this will give details of the last delta performed..
Then use this value and search for the actual delta pointers in your custom table - then perform your delta logic within the FM...
P.S The entry in ROOSGENDLM will come only after you init the datasource...

To enable delta in generic data source

Hi,
There is a generic datasource created on top of PRPS & RPSCO tables. Currently the extraction mode is 'full update'.
There is no time stamp field available in RPSCO, Please suggest how can I enable delta?

Hi
Make sure at least you have Numeric pointer or time stamp field in your table to make the data source enable.
If you created view on these two tables, then in RSA6 --> open the data source --> goto edit mode.
here you will delta enable check box --> select this check and you can give the field which has to be used for delta.
If you using FM, then you have to write to code in functional module.
Regards,
Venkatesh

Deltas for generic extraction.

Hi,
if i want use time stamp & calday for my generic extraction , i can use uppercase and lower case, wher can i give timings suppose want run deltas for 10am-10.30am.
regards
anitha

Hi,
Security 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 security interval for the upper limit is 120 seconds. The selection interval for the delta request is: 12:00:00 to 12:28:00. When the extraction is finished, the pointer is set to 12:28:00. Security interval lower limit The delta-relevant field is a timestamp. After images are transferred. In BI the record is overwritten with the post-change status, for example, for master data. Any duplicate data records do not affect BI. The last read timestamp is 12:28:00. Delta extraction begins at 13:00. The security interval for the lower limit is 180 seconds. The selection interval for the delta request is: 12:25:00 to 13:00:00. When the extraction is finished, the pointer is set to 13:00:00.

Delta for Generic data source.

Hi,
I have created a generic data source for which I have taken the change data as generic delta in CRM4.0. But the problem is delta is not getting initiated. like we are not getting any records in delta. Kindly guide me what else i have to do to get this delta
Thanks
Naveen

Hello Naveen,
What is the delta method you have used, is it Time stamp or ALE Pointer?
See this SAP Note 539547 Generic delta with date does not work
Please see these docs as well
[How to Create Generic Delta|How to Create Generic Delta]
[How to Create Generic Data Sources which use the Delta Queue (NW7.0)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10b68b99-022e-2a10-999d-c4dc9ec24a59]How to Create [Generic DataSources Which Use the Delta Queue (NW2004)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-dbb4356cf4bf]
Thanks
[Chandran|http://chandranonline.blogspot.com/]

Delta in Generic

Similar Messages

Maybe you are looking for