Generic delta issue - INITIALIZATION - Missing some records

Hello all,
We have create a specific table on our SAP system (4.6C) and a specific datasource.
We have customized a generic delta process (DELTA SPECIFIC FIELD = Last Change Date type DATS).
The table contains 38 records.
When we launch a full loading all the records are extracted (that is to say 38 records).
When we launch a INIT loading (with no selection) only 6 records are extracted.
The generic TYPE for delta field is CALENDAR DAY.
Why the init loading doesn't load all the data contain in the table ?
Some of you have already meet such problem ?
The table structure can be the reason of this problem ?
Points will be done
Edited by: Marc Marquez on Jul 24, 2008 10:56 AM

This test is already done, the problem is on ECC system.
On RSA3 side the behaviour is the same than in BW
FULL loading is ok (all records are extracted)
INIT loading is ok but most of the records are not loaded (6 instead of 38)
Christophe
Edited by: Marc Marquez on Jul 28, 2008 3:18 AM

Similar Messages

End routine Works fine but missing some records while updating to cube.

Hi All
I have an issue here... My End routine works fine and I even debugged by putting the breakpoint and It fetches data from dso. strangely when I run my DTP the load is successful but I can see some of the records are missing. but there is data in dso and also when i debug the code it fetches the values for particular fields.
My requirement is I have a cube 'A' and under it DSO1 and I need six more fields from dso2. Now I made a look up for these six fields in End routine. My routine works fine and so the DTP Is Green. My issue is I cant see these six fields updated for some of the records.
PLZ put some light on it!!!!!!!!!!!!!!!!!

Hi Naveen & Jaya
Thanks for your quick response. Below is my code logic in end routine.
METHOD end_routine.
*=== Segments ===
    FIELD-SYMBOLS:
      <RESULT_FIELDS>    TYPE tys_TG_1.
    DATA:
      MONITOR_REC     TYPE rstmonitor.
$$ begin of routine - insert your code only below this line        -
... "insert your code here
data: lv_result_package like line of RESULT_PACKAGE,
      l_tabix type sy-tabix.
loop at RESULT_PACKAGE into lv_RESULT_PACKAGE.
   l_tabix = sy-tabix.
Update lot/decision attributes Lot/Decision ( ZQM_O04 ) DSO
   read table itab_qm_o04 into itab_qm_o04_wa
       with key insp_lot = lv_result_package-insp_lot.
   if sy-subrc = 0.
     lv_result_package-ivaluation = itab_qm_o04_wa-ivaluation.
     lv_result_package-catcode_ud = itab_qm_o04_wa-catcode_ud.
     lv_result_package-catgrp_ud = itab_qm_o04_wa-catgrp_ud.
     lv_result_package-/bic/zcattp_ud = itab_qm_o04_wa-/bic/zcattp_ud.
     lv_result_package-/b41/s_usuddate = itab_qm_o04_wa-/bic/gqmuddat.
     lv_result_package-/b41/s_usudcdate = itab_qm_o04_wa-/bic/gqmudcdt.
   endif.
   modify RESULT_PACKAGE FROM lv_RESULT_PACKAGE INDEX l_tabix.
endloop.
Well based on the insp_lot in ZQM_O03( DSO1) the logic above gets the six fields from ZQM_O04(DSO2) and feeds the cube.
The Insp_lot has multiple records in DSO1 based on specific characteristic and so the cube. This Logic gets all these six fields
from DSO2 which has single record per insp_lot and feeds the cube which has multiple records on insp_lot based on a specific characteristic. For some reason some of the records are not been updated to cube.
waiting for your valuable response.....
Thank You,
Abhishek Yeachni

Generic Delta issue..

hi experts,
i have created Datasource based on view which is based on EKPO and EKBE tables.
i have date fields BUDAT, CPUDT and CPUTM.
I have selected CPUDT as Delta Field.
select Calendar Day and Safety Interval Upper Limit as 1.
I have initialized yesterday, though the records are created and i can see the new records with today's date, in RSA7 i cannot see any records.
what is the issue in it, do i need to change delta field as CPUTM as it is time.
if yes then how can i set the Delta to capture the Delta Records?
regards
venuscm

Hi,
All three fields are from EKBE table, so kindly check whether there is any change in source system table EKBE, for these fileds for the new records created.
New record created will be updated in table EKPO and EKKO only.
Also make sure that delta field should be one of the extracted field in your generic extractor.
wish u all the best
Regards,
Vinod

Missing some records after Loading Data in Oracle 11g Release 1

Hi All,
I wrote a script to load one million records into the database using all insert commands.
I know there is a faster way using SQL Loader- but i am in the process of learning but ran out of time.
Anyhow, 1 million data was injected into the database but only 999998 records are there....does anyone know why?
Is there a way I can find out which data was rejected?
thanks

Hello,
It could be nice that your script spool a log.
By that way, you could more easily catch the error and the detail of the rows rejected.
Best regards,
Jean-Valentin

Some records are missing in the mail, when scheduled a background job.

There is a Z report, which will display some details from SD, MM , WM every day , and the same thing need to be mailed to the user through background Job.
Issue is that spool is correct and it is missing some records ( Billing due list ), even internal table have records and displayed in the spool , in the mail it says
No Entries Found.
Is there any chance of debugging background job.
Good thing is that when executed in foreground it is working fine. Both mail and report display.

EM_BODY = '4) VF04 -- Processing Billing document due list.'.
APPEND EM_BODY.
EM_BODY = ' '.
APPEND EM_BODY.
IF IT_FINAL3[] IS INITIAL.
    EM_BODY = '        No Entry Found'.
    APPEND EM_BODY.
    EM_BODY = ' '.
    APPEND EM_BODY.
ELSE.
    CONCATENATE 'Delivery No' 'Created By' 'Created On'
                 'Reason' INTO HEAD SEPARATED BY '     '.
    EM_BODY = HEAD.
    APPEND EM_BODY.
    EM_BODY = ' '.
    APPEND EM_BODY.
    CLEAR V_TEXT.
    CLEAR ITEM.
    LOOP AT IT_FINAL3.
      CONCATENATE IT_FINAL3-VBELN IT_FINAL3-ERNAM IT_final3-ERDAT
                  IT_FINAL3-RESO INTO ITEM SEPARATED BY '     '.
      V_TEXT = ITEM.
      EM_BODY = V_TEXT.
      APPEND EM_BODY.
    ENDLOOP.
    EM_BODY = ' '.
    APPEND EM_BODY.
ENDIF.
This is the part where it is failing, where it_final3[] is initial.
but whereas in the spool i can view those records.

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 extraction by Function module issue

Hello Experts,
Please help !!!
I have problem for delta extraction by Function module. For the full load, I wrote function module based on RSAX_BIW_GET_DATA_SIMPLE. It works fine.
But I would like to have the delta load enabled. Therefore, I modified the datasource, add a delta specific field u2018ztimestampu2019, which type is calendar day.
Then I create a function module based on template u2018RSAX_BIW_GET_DATAu2019, as this support the upload mode. But when I test this datasource in RSA3, no matter itu2019s full load or initial delta load, it always send me an error, u201CErrors occurred during the extractionu201D.
I had some debug, and found that there is no value for i_isource when my function module is called. Therefore it raised the exception.
But I do not have the chance to debug my code for the delta logic, can somebody help to check?
I also check the entries in ROOSOURCE,
For my datasource ZTRNREC_FM_DELTA, The DELTA value is u2018AIEu2019, and extraction method is u2018F2u2019, should I change them to DELTA= u2018Du2019 and extraction method to u2018F1u2019? Where to change?
FUNCTION ZRSAX_TRAININGREC_DELTA.
""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 STRUCTURE ZTRN_REC_TIME 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
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,
          S_S_IF TYPE SRSC_S_IF_SIMPLE,
          S_COUNTER_DATAPAKID LIKE SY-TABIX.
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 'ZTRNREC_FM_DELTA'.
      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 'D'.
      WHEN 'R'.
      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
    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.
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
LOOP AT G_T_SELECT INTO L_S_SELECT
        WHERE FIELDNM = 'ZTIMESTAMP'.
ENDLOOP.
      IF G_COUNTER_DATAPAKID = 0.
        IF L_S_SELECT-LOW = '' AND L_S_SELECT-HIGH = ''.
        OPEN CURSOR WITH HOLD G_CURSOR FOR
            SELECT (g_t_fields)
            FROM ZTRN_REC_TIME.
        ELSE.
          OPEN CURSOR WITH HOLD G_CURSOR FOR
            SELECT (g_t_fields)
            FROM ZTRN_REC_TIME
            WHERE ZTIMESTAMP >= L_S_SELECT-LOW
              AND ZTIMESTAMP <= L_S_SELECT-HIGH.
        ENDIF.
      ENDIF.
FETCH NEXT CURSOR G_CURSOR
               APPENDING CORRESPONDING FIELDS
               OF TABLE E_T_DATA
               PACKAGE SIZE S_S_IF-MAXSIZE.
    IF SY-SUBRC <> 0.
      CLOSE CURSOR G_CURSOR.
      RAISE NO_MORE_DATA.
    ENDIF.
    S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
ENDIF.
ENDFUNCTION.
I found some similar issue in this forum by link
Generic Extractor Delta Function Module code, but still I could not get clear answer.
Can you please help me:
1)     why there is no value for i_source , how to fix it?
2)     For the delta logic for ztimestemp, is it correct?
3)     Need I modify the entries in ROOSOURCE ?
Thanks a lot !!!

Hello Andre,
        Thanks a lot for your help. I did some change , but still does not work. Could you please help check.
Now the source code are the following, It's based on the RSAX_BIW_GET_DATA_SIMPLE, as you confirm that this also supply the update mode (full, initial delta, delta).
FUNCTION RSAX_BIW_GET_DATA_TRAININGREC1.
""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
*"     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 ZTRN_REC_TIME OPTIONAL
*" EXCEPTIONS
*"      NO_MORE_DATA
*"      ERROR_PASSED_TO_MESS_HANDLER
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_ZTIMESTAMP FOR ZTRN_REC_TIME-ZTIMESTAMP.
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 'ZTRNREC_FM'.
      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.
      LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'ZTIMESTAMP'.
      MOVE-CORRESPONDING L_S_SELECT TO L_R_ZTIMESTAMP.
      APPEND L_R_ZTIMESTAMP.
      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.
     IF L_S_SELECT-LOW = '' AND L_S_SELECT-HIGH = ''.
        OPEN CURSOR WITH HOLD S_CURSOR FOR
        SELECT (S_S_IF-T_FIELDS)
        FROM ZTRN_REC_TIME.
        ELSE.
        OPEN CURSOR WITH HOLD G_CURSOR FOR
        SELECT (S_S_IF-T_FIELDS)
        FROM ZTRN_REC_TIME
        WHERE ZTIMESTAMP >= L_S_SELECT-LOW
        AND ZTIMESTAMP <= L_S_SELECT-HIGH.
     ENDIF.
    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.
I think it already includes the important statements you suggested.
I test this FM in RSA3, for the Full load mode, it works fine. Also if I checked the debug mode in execution , it will stop in the code and let me debug.
But when I choose other mode, like 'initializion of the delta transfer' or simulation of initial delta, I always get error 'error occurs during the extraction' .. even I choose debug mode, but it could not enter the code for debug..
Till now I did not see any parameter or value for the upload mode..
Another questions is that, in RSO2, I define Ztimestamp as my delta field.. But , can I add other field as selection condition in the datasource definition, and has its range table in this function module ?
Should I change the entries in ROOSOURCE for this datasource ??
Please let me know your feedback, do you have some concret example for generic delta extraction ?
Thanks a lot !

Delta issue on a Generic Datasource

Hi
   I had a Generic Datasource on a Z table.
   The Z table had a Date field on which Delta is based.The Postings are performed manually.
How to solve the delta issue in the below scenario.
Ex; A user made a manual posting with a date 09AUG2010 today and delta is extracted to BW.
    But tommorow a used made another posting with a date 14JULY2010....
Currently that record is not being extracted....how can i resolve this
Thanks

Hi,
Once the data source is created you will extract the data till that date and as the delta is set it will fetch the newly updated records .But i dont think one can post with the back dates in R/3 side.
If i'm not wrong if you are asking regarding record got missed out them wht need to be done?
Then do the repair full request and pull the missed delta records and it wont effect the delta settings.
Regards
KP

Problem in getting Generic Delta records to BW

Hi BW Gurus,
I have got one issues with which I have been struggling a lot for several days . i.e
I am extracting data from R/3 using Generic Extractor (View) from CATSCO and CATSDB. At the time of delta, I tried using Personal No with Time Stamp giving Upper limit as 1800 seconds. I executed Infopackage in BW immediately. But it didn't work out. So plz guide me how I can get Delta Records to BW. Or should I do any necessary factors apart from these in Generic Delta Screen (RSO2).
It is very urgent.
I will be thankful for solving this issue.

Hey I am "Intros" again,,
I am sorry man for giving the wrong T-code mistakenly in my last reply..
To solve the proble...the whole process is same what I told u before..
But... you got to go to T-Code : BD87 , then execute the IDocs manually to bring them in to BW
identify your IDocs which are missing in Monitor screen, then goto BD87 and select those IDocs and click execute... )you can search the IDoc's based on selection conditions)
I hope this will help u...
cheers man..
---Intros

Loading issue..missing records .. randomly

HI ALL,
Thanks for ur replies.
We found on 11/09 some records are missing from last 6 months ( 3 to 4 records for each group with diff dates) in daily delta loads 1pm.
It is very difficult to load each group as full loads on that dates.
We did repeat delta with no selections on 12.09.2005 at 9 am (loads 8 million rec) and on the same day daily delta also run at 1pm( it also loads 8 million rec) . Finally we seen on 13/09 we get duplicate records. We forcibly removed these request which we had run on 12th (i.e Repeat Delta & Delta). Those were now in reconstruct tab.
How to get my missed records from 6 months? How to handle this with out effecting cube data?
Can we do selections in repeat delta / delta cases?
Initialization was done on 04/04/2004.
What is the reason for missing these recors?/
pls tell the step wise.
Please guide me.
Regards,
Srilakshmi

Hi Roberteo:
It is 2.X , I think so, its not possible Full repir request here.
You Mean 1)re-init with transfer/without transfer ? selection?( before this we should remove previous init load) 2) then daily delta.
I am thinking :to do like this , please guide me:
My suggestion would be since we have the option of transfered date in the selection conditions of infopackage , what we have do is we can do selective deletion of the contents of last and current month based on the closing date of the HR system and load only that data .
For ex: if you want to delete the contents of MAY 2005 and June 2005 , and the delta failed lies in the month of May 2005. so delete the two months and load only May 2005 in a separate infopackage. After that you can continue your normal loads with the month June 2005. By this way we wont miss any data as you are loading to cube no problem of duplication.
Is it advisable??
cheers,
sri

Problem in extracting Generic Delta Records

Hi BW Experts,
I have an issue. I am using Generic Extractor using View from Tables CATSCO and CATSDB. At the time of Generic Delta, I am using the field PERNR(Personal Number) to use Generic Delta. I am using Time Stamp. For this I have selected Safety Interval Upper Limit 100 seconds.But now I am testing whether we get delta records or not. But I am not getting records to BW. They are changed in R/3. So please guide me whether I should use Calday or Time Stamp . How can I get delta records to BW.For testing , I am executing InfoPackage immediately after changes in R/3 like for two or three minutes. Once I will be sure on getting records to BW, then I can move to Production where we execute process chain at 1:00 a.m
there I can use Calday giving Safety Interval Upper Limit as 1 day. Considering the above factors please guide me .
I will be thankful for solving my issue.

PERNR doesn't contain a date right? so timestamp tells the system PERNR is a date field... That will never work.
What kind of value does PERNR contain, is it an incremental value that adds up at every new entry?
Generic delta needs a field that changes in a way that can be predicted.

Issue with generic extraction (Generic Delta)

I have one more issue with Generic Delta Extraction. Here I selected the field related to my requirement but when I am trying to save I am getting error Still OLTP have errors.
I need some help when we select generic delta wht are the settings. Like now I am working on Inventory Management.
Please Some one help me as soon as possible.
Thanks In advance.....
Regds
SDR.

Hi ,
I think there are some of the Keyfigure fields which needs 0Unit or 0Currency field to be present in the Extract Structure but they are not present . Check All unit of measure and Currency unit fields are not hidden .
Regards,
Vijay.

Some fields are missing while recording through shdb

Dear Abapers,
I am doing bdc for F-27 t.code.Some fields,cobl-gsber(business area),cobl-kostl(Cost center) are missing while recording through SHDB.But when do it manualy the fields are displaying.Also i have ddded those fields manualy in the program,stll the fields are not getting captured.May anyone pls help me,why this problem is happening?What is the solution for this.
Thanks in Advance.

hi
i can tell u that few transactions wont suffice us with BDC,so for such transactions we do bdc with similar kind of transactions.
ie., The transactions FB60 and f-63 both are meant for Parking.
But we cant do bdc for FB60 Parking. So we do bdc for f-63.
similarly when we do bdc for vendor few fields wont appear...in that case, we use bapi for it....
So try to find an appropriate bapi or similar tcode which will suffice ur need
hope its clear.
Regards
Sajid

Incorrect TimeStamp in Generic Delta (UTC Issue)

Hi,
I have a problem regarding a generic delta extractor. The pointer stored in rsa7 (ROOSGENDLM table) is not UTC but system time. As standard tables store the timestamp using UTC format the delta extractor is not picking up the correct data.
Do you know a solution for this?

Hi,
Thanks for your reply. However I think that unfortunately this solution is not enough
For example:
I execute a delta. My TimeStamp is registered as UTC +2: 20080612160000. (Here I have the error, it should be in UTC)
Now I modify a record in R3 and it is registered with timestamp UTC: 20080612140000.
If I execute a delta it will take all the records higher than 20080612160000. Therefore my modification will never be uploaded.

Generic delta; When R/3 record deleted.

Hi all
Please tell me What will happen to the BW record when the record in R/3 add-on table is deleted and the data is retrieved by generic delta.
(1)At the beginning.
R/3                         BW
20051124000001   100$   -> 20051124000001   100$
(2)Then, R/3 record deleted.Does the record on BW will be deleted or remain in same?
R/3 record deleted      -> BW record also deleted
                        or
R/3 record deleted      -> 20051124000001   100$
                            remain in same
Now, I cannot access to BW; I couldn't test by myself. So, I wish someone help me.
Ken'ichi

Hi Ken'ichi,
Refer these posts on RECORDMODE:
Re: ods- 0 Record mode
Re: 0RECORDMODE Question
A generic datasource can be based on:
1. View/Table
2. Function module extractor
3. Infoset query.
You would find many links on the same topic in these forums. Kindly use the search option.
Bye
Dinesh

Generic delta issue - INITIALIZATION - Missing some records

Similar Messages

Maybe you are looking for