Short dump in delta extract using bgRFC in NW 2004s

Short dump in delta extract after Support Pack install, using bgRFC.
InfoSet Query extractor from Z-table residing on BW system into ODS.
Init and Full loads load successfully, delta loads short dump.
"MESSAGE_TYPE_X"
"SAPLARFC" or "LARFCU25"
"TRFC_SET_QUEUE_RECEIVER_LIST"
Problem began after support pack install, from SP 9 to SP 12.   Switched to Classic RFC in SM59, seemed to correct this extractor but caused problems in other extractors.

Hi Kevin,
check out this note: https://websmp205.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1054970&_NLANG=EN
it might help.
regards
Siggi

Similar Messages

Short dump error when extracting delta records from R/3

I am working on BW 3.5 and I am facing some short dump error when extracting delta records from the r/3 to BW.
Below is the error message
Kindly do the needful ASAP.
Job started
Step 001 started (program SBIE0001, variant &0000000024277, user ID BWREMOTE)
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 0ISCM_PAYMENT_01
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 2000000000                              *
abap/heap_area_total.......... 2000000000                              *
abap/heaplimit................ 40000000                                *
zcsa/installed_languages...... DE                                      *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 6500000                                 *
ztta/roll_extension........... 2000000000                              *
2,454 LUWs confirmed and 2,454 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DAT
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelled

Hi,
I look at the transaction ST22 to see which type of error has given you. Take a look at the notes to correct the error.
Another option is to look at OSS notes, because the error is giving you a standard extractor.
Greetings,

Code For Delta Extraction Using Function Module

Dear Experts,
I want a sample code for Delta Extraction using Function Module ( If it is customized already working code very helpful ), I have already created Function Module but Full update is happening. If I give delta update again it is retrieving all records. It is very urgent, if you have please send me to the following mail ID.
[email protected]
Best Regards,
SGK.

Dear KJ,
Thank for your response. I saw the code that you sent, you have used some ztables like ZSC_DELTA_IP, ZSC_SAFETY_DELTA, ZSC_SET_EXT_TIME
What are the fields that you have created in these tables , what is use of these tables, can you send the fields that you have used in these tables.
Thanks & Regards,
SGK

Delta Extraction Using Function Module ( Customization )

Dear Experts,
I want a sample code for Delta Extraction using Function Module ( If it is customized already working code very helpful ), I have already created Function Module but Full update is happening. If I give delta update again it is retrieving all records. It is very urgent, if you have please send me to the following mail ID.
[email protected]
Best Regards,
SGK.

Hi SGK,
I've done this for a delta based on a timestamp and it's actually pretty easy. The basic steps are:
1) Create an extract structure in SE11. Make sure the structure has a date or timestamp field in it that you can use for delta. You'll need to include the field twice if you also want to extract it to BW/BI since once it's chosen as the delta field then it will be hidden in the interface.
2) Create the extractor function module in SE37. You can use RSAX_BIW_GET_DATA_SIMPLE as a template. Make sure your logic restricts the data it retrieves according to the selections that are passed in I_T_SELECT, including restrictions on the delta field.
3) Create a generic DataSource in RSO2. Click Extraction by FM then fill in your extract structure and function module. Click Generic Delta and pick your delta field and the appropriate radio button (time stamp or calendar day). If your delta field is a timestamp field then be sure to set the upper and lower safety limits to -86400 and 86400 respectively. This might not be necessary on your version of SAPI but on mine there is a bug where it doesn't translate between system time and UTC (GMT) correctly so this was necessary.
You don't need to program any special delta handling logic in your function module as long as you restrict the data you retrieve based on the delta field (I_T_SELECT). This is because the SAPI takes care of catching the init, delta and repeat requests, translating them to the appropriate delta field values, and then passing them to your function module as if it was a full extraction for a specific date or timestamp range.
Hope this helps!
Jason

Short dump error when extracting from one of the datasource in R/3 to BW

When extracting from one of the datasource I am getting the short dump. below is the source code of the same.
Source code extract
Get boundaries of next TID block
L_FROM_INDEX = L_TO_INDEX + 1.
IF L_FROM_INDEX GT NFILL. EXIT. ENDIF.
L_TO_INDEX   = L_TO_INDEX + L_BLOCK_SIZE.
IF L_TO_INDEX GT NFILL.
L_TO_INDEX = NFILL.
L_BLOCK_SIZE = L_TO_INDEX - L_FROM_INDEX + 1.
ENDIF.
Create hashed index on TID of TID table
CLEAR L_TH_TID_IDX.
LOOP AT TIDTAB FROM L_FROM_INDEX TO L_TO_INDEX.
L_S_TID_IDX-TIDIX = SY-TABIX.
L_S_TID_IDX-TID   = TIDTAB-TID.
COLLECT L_S_TID_IDX INTO L_TH_TID_IDX.
ENDLOOP.
Select TID block from STATE table
SELECT * INTO TABLE L_T_STATE
       FROM ARFCSSTATE FOR ALL ENTRIES IN L_TH_TID_IDX
       WHERE ARFCIPID   EQ L_TH_TID_IDX-TID-ARFCIPID
         AND ARFCPID    EQ L_TH_TID_IDX-TID-ARFCPID
         AND ARFCTIME   EQ L_TH_TID_IDX-TID-ARFCTIME
         AND ARFCTIDCNT EQ L_TH_TID_IDX-TID-ARFCTIDCNT
       ORDER BY PRIMARY KEY.
Consistence check
DESCRIBE TABLE L_T_STATE LINES L_LINES.
IF L_LINES NE L_BLOCK_SIZE OR
   L_LINES EQ 0.
MESSAGE X097(SY).
ENDIF.
PERFORM DELETE_BATCH_JOB
        USING    L_T_STATE
        CHANGING L_S_TID1.
Update LUW-Status und Zeit
CLEAR L_T_STATE_IDX.
CLEAR L_TH_TID2_IDX.
CLEAR L_T_TID.
LOOP AT L_T_STATE INTO L_S_STATE.
L_S_STATE_IDX-TABIX = SY-TABIX.

Hi Pavan,
                 This is a table space error.
Regards,
rahul

Regarding Short dump while data extraction

Hi All,
We are trying to extract data from DB Connect. When we try to pull the data by giving selections, we are getting short dump.
Name of Run time error.
PERFORM_CONFLICT_TAB_TYPE
Exception Name
CX_SY_DYN_CALL_ILLEGAL_TYPE
What could be the reason for this error.

Hi Jayanth,
Check these ...
Perform_conflict_tab_type error
Oracle to BW Load Runtime error CX_SY_DYN_CALL_ILLEGAL_TYPE
Raja

Generic delta extraction using function module

Hi.
I have a generic datasource , extraction being performed by a function module. The extraction works fine in full update mode. The extract structure has a timestamp field.
I have enabled generic delta using this field(i.e., marked this field in RSO2). I understand that with this setting, I should be able to get delta data when I do a delta request. But it does not seem to happen.
I checked the ROOSPRMSC table for the last(local) timestamp stored there. Now when I do the delta upload I expect to see only those records which are younger than the stored timestamp of last upload.
But I still get the entire set of records.
Questions are :
1. Do I need to explicitly code for fetching the delta in the extractor ?
2. If not, what could be the reason why generic delta is not working ?
Thanks and regards,
Anuradha

Hi GFV,
I read-up all the forum entries on this topic but could not find anything specifically dealing with my problem. I have browsed through the how-to paper on generic delta as well.
I am quite sure that we don't need any special coding in the extrator for generating delta generically. Even the how-to paper does not mention that.
I have used the FM RSAX_BIW_GET_DATA_SIMPLE as a template
for my extractor(as suggested by F1 help in RSO2). This FM does not even have the i_updmode flag in its interface.
Thus this function module always does full extraction and I expect the system to take care of delta using the timestamp field.
Are these assumptions incorrect ?
Regards,
Anuradha

Customized Table is giving Short Dump .Want to extract data in Production S

Hi ,
I have a problem in customized table .Table is giving a data after trying to access 185th record.There is some problem in the table.But I want to pull out all the data from the table..Is it possible to download it .Pls suggest..
Even If I put one select query also it is givning dump..
Pls suggest some other technique to download it..
Regards
Arun.P

Hi Arun,
Where there you are using WHERE condition in select statement while fetching the records?
if yes means check for the fields are primary key, available in WHERE condition, or else create secondary index for those
non Primary key Fields in WHERE condition.
This may help you.
Thanks and Regards,
Prakash.K

Delta Extraction using Infospoke

We are currently on BW 3.1C with 3.3 business Content. I have created an infospoke to get data from ODS object into db table. I am trying to get delta and also turned on the techinical Key on the infospoke but when I run the infospoke I get before and after images. Is there any way that I can get just the changed record if not how can I identify the changes do I have to build my own logic to capture changes?? I dont understand how the delta works on Infospoke for an ODS object and I am not sure whether I am creating it correctly. Please help.
Thank you,
Neelu

Roberto,
I have created an infospoke off of an ODS which contains MARA table. My question with respect to infospoke
1. if you are looking to send only changed records to the different target like db table would you check the technical key
2. if an existing record is changed with the technical key on it would add another record so when reporting off of the db table i will see multiple records where as our requirement is to see the most updated record.
Thank you
Neelu

Error in Delta extraction of Material using MDM_CLNT_EXTR

Hi All ,
I am facing the following error while doing the delta extraction for material by using MDM_CLNT_EXTR.
ABAP/4 processor: MESSAGE_TYPE_UNKNOWN
I used MATERIAL_EXTRACT stucture, and successfully run the intial load.
Any help will be appriciated
BR
Syam

Hi Syam,
Just check whether the target system defined in XI and the extraction object that you are selecting are in sync.
Such error is possible when there is a conflict in the same.
You can also refer to the below link.
Delta Extraction Using MDM_CLNT_EXTR (Urgent)
Hope it helps.
Thanks,
Minaz
Edited by: Minaz Kathawala on Sep 30, 2008 4:14 PM

Short dump error report

What is the purpose of short dump error report generated by the system? What r the major parts/section of this report?

hi please look through this:
Whenever any transaction or any process is executed it hits an ABAP code.
If there is any issue in executing the code the situation is called "ABAP DUMP" or 'Short Dump'
Transaction ST22 is used to check any ABAP Dump within a given duration.
U can also fix the issue with the help of ABAP editor (Transaction Code SE38) if u r good with ABAP.
you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
sap-basis sap-basisAll Groups Ignore this text box. It is used to detect spammers.If you enter anything into this text box, no search results will be displayed.
SAP Groups > Technical-functional > sap-basis > Message
About This Group | Invite peers to join this group
<< Prev thread < Prev msg Next msg > Next thread >>
short dump----urgent
Reply from Keith Lewis on 5/2/2003 3:22:00 AM
Good explanation Joy, but it is not only limited to the current day and
yesterday. If you click on the Selection button you can select previous
days as well. In fact you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
Cheers
Keith
SAP R/3 Support Specialist
Information Services International
Tel +44 1664 41 6178 Mobile +44 7887 627818
E-mail email@removed
Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp
Dear sreenivas
If you receive an error message in the R/3 System log (SM21), or if you
see
a terminated update in the update service analysis transaction (SM13), or
DB
realated error ,check for dumps using the dump analysis transaction
(transaction ST22), or choose Tools -> Administration -> Monitoring ->
Dump
analysis.
Transaction ST22 enables you to analyze short dumps from the current and
previous day.
The dump analysis function shows you:
What happened
What you can do
How to correct the error
The dump analysis function also provides an error ID and keywords that you
can use to search in SAPNet, as well as information about:
The system environment
Users and transactions
Transaction ST22 enables you to analyze the following data:
Date, time, user, client
Contents of system and data fields
Contents of internal tables and application tables
ST22 is a very nice feature in SAP. This is where all the system errors
and users mistakes showed up. If there is a problem that you cannot
solve and you contact SAP support, they look at this area to analyze it.
This gives us lead where to handle the problems.
Error analysis
How to correct the error
System environment
User, transaction...
Information on where termination occurred
Contents of system fields
Chosen variables
Active calls / events
Internal notes
Active calls in SAP kernel
List of ABAP programs affected
List of internal tables
Directory of application tables (contents)
Directory of data areas (administration information)
Directory of data areas (contents)
ABAP control blocks CONT
End of runtime analysis
i think this would be helpful
regards
sravani

ABAP short dump with "CNTL_ERROR"

Hi,
I am getting an ABAP short dump with "CNTL_ERROR" while using an input script. What do I do?
Thanks,
Sreekar.

Hi,
Newer versions of SAP GUI and R/3 include external controls called as ActiveX (OCXs). ABAP code internally issues some commands to flush and refresh these controls. Since, when using GuiXT and input scripting, these controls are not created, and ABAP dumps. Use keyword "Enable controls" (without quotes on a separate line) in a screen block that has an ActiveX control.
Example:
Screen SAPLCOIH.3000
Enter "/Menu=4,1,5"
Screen SAPLSP01.0100
Enter "=No"
Screen RIPLKO10.1000
Enable controls
Set F[Group] "UG"
Enter "/8"
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.

Delta extraction for a generic datasource

Hi BWers,
I want put in Delta the extraction of a generic datasource.
Currently this generic datasource is based on the table VBPA (Sales Document: Partner). Any time field exists.
We need a time field in order to converse to a Delta extraction. This time field exists in the table VBAP (Sales Document: Item data). In fact two time fields exist: one which is filled at the creation of the sales order (ERDAT), another at the change of the sales order (AEDAT).
The fields VBELN, POSNR and MANDT are keys in the tables VBAP and VBPA.
The table VBAP changes when partner functions is created or changed in a sales order (VBELN) :
- When it is a creation of a new sales order (with new partner functions), a new record is created in VBAP and the field ERDAT (Created on) is filled. The field AEDAT (Changed on) is empty.
- When is a change of an existing sales order, the corresponding record in VBAP changed, and the field AEDAT is filled. ERDAT stays unchanged.
In order to converse to the Delta extraction, i need a only one time-field (calendar day) in RSO2 / Generic Delta.
But there is 2 time-fields ERDAT and AEDAT. So i just need to get AEDAT if it is filled, else if AEDAT is empty I will get ERDAT.
I would base my datasource on a view between VBPA and VBAP with one field which will be filled by AEDAT or ERDAT (with the conditions below). But it seems it is not possible.
Can you give me other ideas ?
Thanks a lot.
Cheers,
Vince.

In order to create a generic delta from two source fields, ERDAT and AEDAT in this case, you're going to have to create your generic extractor from a Function Module. Otherwise you'll only have the standard functionality available to you for creating the generic delta, which allows you to base it on only one column.
Here's a sample you can use, that was created for VBFA, and change for your DataSource.
FUNCTION y_docu_flow.
*"*"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 YSDS_DOCU_FLOW OPTIONAL
*" EXCEPTIONS
*"      NO_MORE_DATA
*"      ERROR_PASSED_TO_MESS_HANDLER
*& Global Data Declarations
* Type for VBFA Data
TYPES : BEGIN OF ty_vbfa            ,
            mandt   TYPE vbfa-mandt   ,
            vbelv   TYPE vbfa-vbelv   ,
            posnv   TYPE vbfa-posnv   ,
            vbeln   TYPE vbfa-vbeln   ,
            posnn   TYPE vbfa-posnn   ,
            vbtyp_n TYPE vbfa-vbtyp_n ,
            rfmng   TYPE vbfa-rfmng   ,
            meins   TYPE vbfa-meins   ,
            rfwrt   TYPE vbfa-rfwrt   ,
            waers   TYPE vbfa-waers   ,
            vbtyp_v TYPE vbfa-vbtyp_v ,
            plmin   TYPE vbfa-plmin   ,
            erdat   TYPE vbfa-erdat   ,
            aedat   TYPE vbfa-aedat   ,
          END   OF ty_vbfa            .
* Internal Tables and Selection Criteria Structure
DATA : t_vbfa     TYPE STANDARD TABLE OF ty_vbfa ,
         l_s_select TYPE srsc_s_select             .
* Field Symbols
FIELD-SYMBOLS : <fs_fields> TYPE rsfieldsel.
* Constants
CONSTANTS : c_error_msgty TYPE rslogparms-msgty VALUE 'E'            ,
              c_error_msgid TYPE rslogparms-msgid VALUE 'YAERO_WTY_VSR',
              c_error_msgv1 TYPE rslogparms-msgv1 VALUE ' MESSAGE_V1 ' ,
              c_error_msgv2 TYPE rslogparms-msgv1 VALUE ' MESSAGE_V2 ' ,
              c_error_msgv3 TYPE rslogparms-msgv1 VALUE ' MESSAGE_V3 ' ,
              c_error_msgv4 TYPE rslogparms-msgv1 VALUE ' MESSAGE_V4 ' ,
              c_error_msgno TYPE rslogparms-msgno VALUE 999            ,
              c_alias(2)    TYPE c                VALUE 'A~'           ,
              c_vbfa        TYPE dntab-tabname    VALUE 'VBFA'         .
* Maximum Database Lines, Data Package Counter and Cursor
STATICS : s_s_if              TYPE srsc_s_if_simple ,
            s_counter_datapakid TYPE sy-tabix         ,
            s_cursor            TYPE cursor           .
* Select Ranges
RANGES : r_erdat FOR vbfa-erdat ,
           r_aedat FOR vbfa-aedat ,
           r_vbelv FOR vbfa-vbelv ,
           r_posnv FOR vbfa-posnv ,
           r_vbeln FOR vbfa-vbeln ,
           r_posnn FOR vbfa-posnn .
*& Processing Logic
* Refresh Internal Table and Clear work area
REFRESH: t_vbfa   ,
           e_t_data .
* Check the Extraction Mode (Delta Initialization Or Delta)
IF i_initflag EQ sbiwa_c_flag_on.
*   Determine DataSource Validity
    IF i_dsource NE 'YSDDS_DOCU_FLOW'.
*     Call Function to Write Log
      CALL FUNCTION 'RSAL_LOG_WRITE'
        EXPORTING
          i_msgty = c_error_msgty
          i_msgid = c_error_msgid
          i_msgno = c_error_msgno
          i_msgv1 = c_error_msgv1
          i_msgv2 = c_error_msgv2
          i_msgv3 = c_error_msgv3
          i_msgv4 = c_error_msgv4.
*     Raise Exception
      RAISE error_passed_to_mess_handler.
    ENDIF.                  " IF i_dsource NE 'YSDDS_DOCU_FLOW'.
*   Append the Selection Criteria
    APPEND LINES OF i_t_select TO s_s_if-t_select.
*   Fill parameter buffer for data extraction calls
    MOVE : i_requnr TO s_s_if-requnr ,
           i_dsource TO s_s_if-dsource ,
           i_maxsize TO s_s_if-maxsize .
*   Append Fields to be Selected
    APPEND LINES OF i_t_fields TO s_s_if-t_fields.
*   Add the Alias to Fields
    LOOP AT s_s_if-t_fields
      ASSIGNING <fs_fields>.
      CONCATENATE c_alias
                  <fs_fields>-fieldnm
             INTO <fs_fields>-fieldnm.
      CONDENSE <fs_fields>-fieldnm NO-GAPS.
    ENDLOOP.                " LOOP AT s_s_if-t_fields..
ELSE.                     " IF i_initflag EQ sbiwa_c_flag_on
*   For First Data Package, Open Cursor
    IF s_counter_datapakid EQ 0.
*     Clear Ranges
      CLEAR : r_erdat ,
              r_aedat ,
              r_vbelv ,
              r_posnv ,
              r_vbeln ,
              r_posnn .
*     Fill Selection Ranges
      LOOP AT s_s_if-t_select
        INTO l_s_select.
*       Determine Selection Range Field Name
        CASE l_s_select-fieldnm.
*         Created On Date
          WHEN 'ERDAT'.
            MOVE : l_s_select-sign   TO r_erdat-sign   ,
                   l_s_select-option TO r_erdat-option ,
                   l_s_select-low    TO r_erdat-low    ,
                   l_s_select-high   TO r_erdat-high   .
            APPEND r_erdat.
*           Fill the change date too
            MOVE r_erdat[] TO r_aedat[].
*         Predecessor Document Number
          WHEN 'VBELV'.
            MOVE : l_s_select-sign   TO r_vbelv-sign   ,
                   l_s_select-option TO r_vbelv-option ,
                   l_s_select-low    TO r_vbelv-low    ,
                   l_s_select-high   TO r_vbelv-high   .
            APPEND r_vbelv.
*         Predecessor Document Line Item
          WHEN 'POSNV'.
            MOVE : l_s_select-sign   TO r_posnv-sign   ,
                   l_s_select-option TO r_posnv-option ,
                   l_s_select-low    TO r_posnv-low    ,
                   l_s_select-high   TO r_posnv-high   .
            APPEND r_posnv.
*         Successor Document Number
          WHEN 'VBELN'.
            MOVE : l_s_select-sign   TO r_vbeln-sign   ,
                   l_s_select-option TO r_vbeln-option ,
                   l_s_select-low    TO r_vbeln-low    ,
                   l_s_select-high   TO r_vbeln-high   .
            APPEND r_vbeln.
*         Successor Document Line Item
          WHEN 'POSNN'.
            MOVE : l_s_select-sign   TO r_posnn-sign   ,
                   l_s_select-option TO r_posnn-option ,
                   l_s_select-low    TO r_posnn-low    ,
                   l_s_select-high   TO r_posnn-high   .
            APPEND r_posnn.
        ENDCASE.            " CASE l_s_select-fieldnm.
      ENDLOOP.              " LOOP AT s_s_if-t_select..
*     Open Cursor on View to Fetch data
*     If full load with Selection on Fiscal Year
      IF r_aedat[] IS INITIAL.
*       Full Extraction
        OPEN CURSOR
        WITH HOLD s_cursor FOR
      SELECT (s_s_if-t_fields)
        FROM vbfa      AS a
        JOIN pnwtyv    AS b
          ON a~vbelv   EQ b~sdvbeln
       WHERE a~vbelv   IN r_vbelv
         AND a~posnv   IN r_posnv
         AND a~vbeln   IN r_vbeln
         AND a~posnn   IN r_posnn
         AND a~rfmng   NE 0
         AND a~erdat   IN r_erdat
         AND b~sdvbeln NE space.
      ELSE.
*       Delta Extraction Using ERDAT and AEDAT
        OPEN   CURSOR
        WITH   HOLD s_cursor FOR
      SELECT   (s_s_if-t_fields)
        FROM   vbfa      AS a
        JOIN   pnwtyv    AS b
          ON   a~vbelv   EQ b~sdvbeln
       WHERE   a~vbelv   IN r_vbelv
         AND   a~posnv   IN r_posnv
         AND   a~vbeln   IN r_vbeln
         AND   a~posnn   IN r_posnn
         AND   a~rfmng   NE 0
         AND ( a~erdat   IN r_erdat
          OR   a~aedat   IN r_aedat )
         AND   b~sdvbeln NE space.
      ENDIF.                " IF r_aedat[] IS INITIAL
    ENDIF.                  " IF s_counter_datapakid..
*   Fetch Records into Interface Table
    FETCH NEXT CURSOR s_cursor
         APPENDING CORRESPONDING FIELDS
          OF TABLE t_vbfa
      PACKAGE SIZE s_s_if-maxsize.
*   No More Data, Raise Exception
    IF sy-subrc NE 0.
*     Close the Cursor
      CLOSE CURSOR s_cursor.
*     Raise Exception
      RAISE no_more_data.
    ELSE.
*     Move Extracted Data to Output Structure
      MOVE t_vbfa[] TO e_t_data[].
*     Release Memory
      FREE t_vbfa.
*     Sort Output Structure
      SORT e_t_data BY vbelv
                       posnv
                       vbeln
                       posnn
                       vbtyp_n.
*     Delete Duplicate Records from Output Structure
      DELETE ADJACENT DUPLICATES
        FROM e_t_data
   COMPARING vbelv
             posnv
             vbeln
             posnn
             vbtyp_n.
*     Increment Data Package Number
      s_counter_datapakid = s_counter_datapakid + 1.
    ENDIF.                  " IF sy-subrc NE 0
ENDIF.                    " IF i_initflag EQ sbiwa_c_flag_on
ENDFUNCTION.
Edited by: Dennis Scoville on Jul 16, 2009 8:29 AM
Edited by: Dennis Scoville on Jul 16, 2009 8:29 AM

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.

Short dump while extracting data

Hi,
When i extract the data from the datasource 2lis_05_item in rsa3 i m getting the following short dump. Can anyone tell what to do in this case?
Runtime Errors         CONNE_IMPORT_WRONG_STRUCTURE
Exceptn                CX_SY_IMPORT_MISMATCH_ERROR
Date and Time          06.12.2006 09:42:15
ShrtText
     Error when importing object "MC05Q00ITM_TAB".
What happened?
     Error in ABAP application program.
     The current ABAP program "SAPLMCEX" had to be terminated because one of t
     statements could not be executed.
     This is probably due to an error in the ABAP program.
     When attempting to import data, the
     structure of the complex object "MC05Q00ITM_TAB" was not compatible with
     target object.
Error analysis
     An exception occurred. This exception is dealt with in more detail below
     . The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_ER
      was neither
     caught nor passed along using a RAISING clause, in the procedure
      "MCEX_BW_LO_API" "(FUNCTION)"
     Since the caller of the procedure could not have expected this exception
      to occur, the running program was terminated.
     The reason for the exception is:
     When attempting to import data, the structure of the complex object
      "MC05Q00ITM_TAB"
     was not compatible with the target object. The error occurred with
component no. 32.
sing RAISING Clause in Interface
Program                                 SAP
Include                                 LMC
Row                                     5
Module type                             (FU
Module Name                             MCE
gger Location of Exception
Program                                 SAP
Include                                 LMC
Row                                     241
Module type                             (FU
Module Name                             MCE
rce Code Extract
e SourceCde
11         endif.
12       enddo.
13     END-OF-DEFINITION.
14 ***** end macro *****

I suppose that you are doing enhancement to your datasource 2LIS_02_ITM
Have you done the following steps in the extractor:
1. Append the new field in MC02M_0ITM structure
2. Append the new field in MCEKPO structure
3. Use Tcode LBWE and expand the Purchsing to get 2LIS_02_ITM and click on the Datasource to uncheck the 'hide' and 'fields only'
4. Activate the data source, by using Tcode RSA5
3. After that I have make changes to the user-exit to add logic for the new field
Do remember to carry out the following steps before you modify the Extraction structure:
1. Make sure that the following steps are carried out at a time when no updates are performed so that no data is lost.
2. Start the update collective run directly from within the Customizing Cockpit. Up to PI(-A) 2001.2 , this collective run exclusively concerns the V3 update. As of PI(-A) 2002.1, depending on the update mode setting of the application, the collective run concerns either the V3 update or the update from the extraction queue ("Delta Queued", see Note 505700).
3. Load all data of the respective DataSource into the BW System.
Hope it helps.
regards
Vinod

Short dump in delta extract using bgRFC in NW 2004s

Similar Messages

Maybe you are looking for