Delta extraction failing.... status still yellow

Hello Experts
I am working in 3.5 system.
I ran a delta IP to load data to cube, source of DS is another BW system.
IP failed and technical status was set to Red but request status in cube is still Yellow.
what could be the reason?
Also when i try to re run IP i get msg "previous delta failed do you weant to re run?"
and then reruns previous load.
Only error message i see in IP is "Error 7 in the update " no more etails anywhere.
Please help.
Regards
Sudeep

Hi
Thanks you both for quick reply.
I left that request yesterday to become red automatically and when i checked today it was red.
Now i deleted request from IC and PSA and then tried to run delp IP again.
I got message saying "previous delta failed no new delta possible. you can try to rerun previous delta or cancel".
I chose to rerun delta but it has failed again.
Everythign till update rules is executed fine but it fails at processing end with message "Error 7 in update" same as it was happenning yest.
Please help.
Regards
Sudeep

Similar Messages

Delta extraction failed

Hello,
I have Special Ledger cube with more than 15M records. A few days ago its update failed with a dump because of basis problems in the source system. Im trying to update the data that failed. I deleted the request that failed and in the infopackage when it asked me if to bring the last request again i answered yes. The update finished without bringing any records with status 8. I checkd RSA7 in the source system and there are records that have to be update.
Please Advice. I really dont want to do initial update...
Thank you!
David

Hi David,
Please ensure that u have made the status of ur failed request to RED in status tab from status 'NOT OK'.
Then please check whether the data has arrived to PSA or not ,if not then schedule the infopackage again , it will bring missed delta which is available in RSA7.
Hope it helps.
Apparao

Delta extraction is not possible at the moment

Hello,
I am trying to run a delta load and am getting the message "Delta extraction is not possible at the moment". This is actually a repeat because i have tried this load multiple times with no success.
The Diagnosis in the error message is:
The delta extraction is not possible at the moment because the status list of the request is locked in the Cube. This can be for a number of reasons:
1. Another extraction is taking place in the target BI.
2. The control parameters of the request in the InfoCube are locked by deletion or compressing processes.
I dont see that any other extraction or a deletion or compression job. I've tried going through each failed job in the monitor and red lighting them but that hasnt helped. Any ideas what to check or how to fix the problem?
Regards,
TMS

Hi,
From what you are describing, there is already some process going on on the infoprovider you are trying to load the data to. Check if a data load is still active/activation is happening, if its a cube then are there aggregates and are they rolling up. You can check the process in SM66 or SM50 and the jobs in SM37.
The process has locked the infoprovider and no delta or for that matter any process can be done until the earlier one finishes. You can take help from the BASIS team to find out what is locking your infoprovider.
Cheers,
Kedar

R/3 extraction failed - recovery procedure?

R/3 extraction is running from past 2 years.
Suddenly it failed since 5 days and again today it is running fine.
But how i do get data loaded to cube for failed loads?
what is the exact process that should be normally followed?

Hi,
In case you are doing full loads, there is no problem since the last request went fine.
In case of delta loads, there is the option to repeat the last delta. Every time a delta request fails, you can do a Repeat delta, which will load again the last delta.
If you have already load another delta request and didn't repeat the failed delta, you may have missing records in BW system. In this case, a full repair extraction is need.
Have a look a below SAP notes which describes in details the options you have:
739863 - Repairing data in BW
873694 - Consulting: Delta repeat and status in monitor/data target
Best regards,
Eduardo

Repeat delta are failing

Hello experts,
I have an imp production issue. We had delta failing in one of LO Cockpit extractor for last 4 days.
Message: Error occurred in the data selection
Job terminated in source system --> Request set to red
Message no. RSM078
I did repeat delta (by changing status to red and deleting requests). But still I get same message.
Please help.
Rita.

SM 37 LOG:
Job started
Step 001 started (program SBIE0001, variant &0000000017045, user ID ALEREMO
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 2LIS_18_I0NOTIF
RLOGSYS    = PRODCLNT200
REQUNR     = REQU_D4VWYY4JTTY9ODFHL16WPLR5M
UPDMODE    = R
LANGUAGES = *
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 0                                       *
abap/heap_area_total.......... 8588886016                              *
abap/heaplimit................ 40000000                                *
zcsa/installed_languages...... 123ACEFIJKLMNOPSUVc                     *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 6500000                                 *
ztta/roll_extension........... 2000000000                              *
Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 1,491 records
Result of customer enhancement: 1,491 records
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 1,491 records
ABAP/4 processor: COMPUTE_INT_TIMES_OVERFLOW
Job cancelled

Extracting User Status for Sales Orders

I am trying to extract user status transactional data for sales orders (at both the header and item level). I have been following SAP note 300300 to configure the status extractors and map the BW objects to sales order status data sources (2LIS_11_VASTH & 2LIS_11_VASTI). I think I have set up both R/3 and BW correctly according to note 300300 and the IMG documentation, but I am not getting any values in the info source for the new user status info objects, when I run the extract.
Has anyone successfully done this? If so, do you have any documentation or pointers on how I can get this to work? Or, am I better off creating a generic extractor? Thanks for your consideration.
Sincerely, Hashi Chakravarty

Hello Ravi,
well yes, I can derive the status for that order in the update rules if i show the status as an attribute of the 0pm_order; but basically there will be only the last status shown.
My problem:
a. i report on day 1, the status of the order is REL
b. on day 2 i load the master data for the orders, new status is TECO
c. on day three i want to report in the past and see the status of day 1; that's not possible in this scenario because i'll see the current status (TECO).
So that's why I want to have the statuses in the cube...
The 2lis_17_i3hdr extractor is only sensitive to CRT and TECO statuses, but not to the others (like REL / BLC and so on... :_(( )
I could read the statuses from the JEST and TJ02T tables...but still, if a document status is changed, no delta record is written in the queue...
Thanks,
Tudor

Request still yellow in manage screen after successful load

Hi ,
I have loaded the data into the cube .The load is init .Even thought the load is successfully load the manage screen shows request still yellow in color. I checked everywhere but did not find relevant setting.
Any help please.
Thanks

Hi,
Chk for any active job in SM37 still going on which is related to this load...
And then under details tab chk under extraction--->is the data selection ended or not?
And chk in the manage screen->Environment(in the menu bar)>Autoimatic request proceessing>set quality status to OK is checked or not?-> Chk this box and refresh....
If u chk all the things are in green and successfull u can manually turn the status into green in the manage screen....then auotmatically the reporting symbol comes if there are no aggregates...
rgds,

DSO reporting icon was displayed although load status was "Yellow"/"Red"

Hi,
Whilst loading a DSO, I observed that the reporting icon was displayed even when the load was in status "Yellow" and in one instance, the reporting icon displayed even when the status of the load to the DSO was "Red" i.e it had failed. I would reckon that the DSO reporting icon would be displayed only after the load was successful including the activation step. Why then was the reporting icon displaying when the load was not successful.? Is this an SAP bug.
Any thoughts, gurus!
Thanks
Kevin

Hi,
I don't understand this. In a Standard DSO if the Quality Status is set to Automatic then the report shows as Green in the Quality Status Icon. However, data is still in the "New Data Table" and is not yet updated in the Active data table/change log unless the activation is done. If the Activation is done, only the will the data be available in the Active Data table/Change log.
It is only afther this data is available that the reporting icon is displayed.
If the Qualilty status is Yellow/Red the activation cannot be done. In whcih case there is no question of data being available in Active Table/Change log and hence the reporting icon should not be displayed.
Therefore, I am not able to understand the anomalous behavior of the display of the reporting icon even when the Qualtiy Status is Yellow/Green
@Experts: Is there something that I am missing
Thanks
Kevin

How to get the records of the particluar day when delta laod failed (Urgent

Hello BW Gurus,
We are facing one serious issue. Here is the scenario.
1st time the Delta was init and for next consective two loads delta ran sucessfully... then next time delta got failed and the status is in red..... even though system started next delta loading and it has fetched the records and status is in green but not activated ,,,,,its happening still past one month so almost there are 20 requests which are to be get activatetd.
How to resolve this issue.
<b>And how to get the records of the partilcular day when the delta got failed.
</b>
Anyone have come across with this strange issue then help me out and i will rewarrd the points.
Urs,
Raki.

Hi
Can you provide more details about your extractor and data targets.
Are you loading delta to an ODS ??
If you are loading to an ODS, The only solution i can see is to get the missing delta records via FULL UPDATE. Because if you delete the error request from ODS it will also delete the 20 successful requests above it.
Cheers
Praveen
null

Error while doing DELTA Extraction

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.

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.

"Extraction Failed: Cannot Open Output File" error message when installing new drivers

Hello, I'm trying to install new drivers for my HP Photosmart C4385 Printer. I downloaded the full feature drivers for Windows XP 32-bit, and when I start to install (extract), I get the error message:
Extraction Failed
Cannot Open Output File
And the process closes. It happens at about 85% extraction every time.
Any idea why? I called HP but since it is out of warranty they wanted money, which I think as absolutely ridiculous - won't even give me basic support?? Poor, poor customer service.
This question was solved.
View Solution.

Hi,
If you haven't still got the Full Feature software installer, download it from the link below and save it to your Desktop. If you already have it, place it on your Desktop.
ftp://ftp.hp.com/pub/softlib/software10/COL20274/mp-53147-4/100_228_PS_AIO_02_Full_USW_enu_NB.exe
Make sure the Printer is disconnected from your PC.
Download and install 7-ZIP. Once installed, right click on the software installer for your printer, select 7-Zip and choose extract files, then click Ok.
Open the newly extracted folder and double click the setup application to start the installation ( the setup application will probably have the same icon as the original software installer you downloaded ). Connect the printer to your PC when the software asks.
Hope this helps.
Best wishes,
DP-K
****Click the White thumb to say thanks****
****Please mark Accept As Solution if it solves your problem****
****I don't work for HP****
Microsoft MVP - Windows Experience

R/3 table to BW via Delta Extraction (Urgent plz)

Hello Experts,
How to load a data from one of the R/3 tables to BW when the table doenst contains either a time stamp, Date field or numeric pointer.
I have PS Table in R/3 (RPSCO) with over 7 hundered thousand records in it. I would like to populate the data to a ODS via delta extraction.
The table doesnt contain either a timestamp, numeric pointer or date. How would I extract a data now to BW via delta. Would it be possible to use Generic extraction.
Thanks and Regards,
Harish

Hi Harish,
If you need ODS to make delta DataMart you can not delete data before every upload.
For spee-up the upload you can follow these solution:
1)Take off from parameters of your ODS Reporting BEx flag. Without this flag the system does not spent time for reporting activation of data.
2)If upload is too slow you can try to make delta in R/3 via a program that compare previous upload and new status of your table, introducing in the tableforthe upload only modified records. It can be very slow, but it is all R/3 time.
Ciao.
Riccardo.

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 !

Short dump in r/3 in delta extraction

Hi all,
Today we got short dump in R/3 for delta extraction of data source
2LIS_13_VDITM.We want these data to do month end analysis.
I have tried to run extraction checker (rsa3) still it gives me short
dump for the same.
SAP r/3 4.6c
and bw 3.5
Regards,
Viren.

Hi,
please paste some more info about the dump...
Olivier.

Delta extraction failing.... status still yellow

Similar Messages

Maybe you are looking for