Dump error in db02 CONNE_IMPORT_WRONG_COMP_TYPE

Dear All,
When use the t-code db02 and press refresh button for database + history check it give abap runtine error dump.
it gives this error as runtime error:
CONNE_IMPORT_WRONG_COMP_TYPE.
please guide me, it is happening both in Devlopment and well as in production server.
Thanks
Bhaskar

Hi,
check Note 657981 - CONNE_IMPORT_WRONG_COMP_TYPE in DB02 for RSORAUD1
also check Note 997535 - DB02: Problems with History Data.
regards
kaushal

Similar Messages

Dump error while creating a new page in smartforms URGENT pls!!!

while creating a new page it is showing me a dump error , that the superior program execption was not intercepted , i have even given the next page field also correctly, i have attached a mainwindow to that page and a text element to that . .
thanks
sridhar

Hi Deena,
This error:
"[2012-07-10T14:50:30.005+05:30] [wls_ods1] [ERROR] [] [oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000JXkC9dU3FClqwsJb6G1FyhO000003D,0] [APP: odsm#11.1.1.2.0] Server Exception during PPR, #7[[
javax.servlet.ServletException: Could not initialize class com.octetstring.vde.admin.services.client.VDEAdminServiceSoapBindingStub"
is known issue
Go to metalink, article: Unable To Connect To OVD 11g Webinterface Using ODSM. [ID 1282757.1]
You need to apply that patch.
I hope this helps,
Thiago Leoncio.

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

Short Dump Error

Hi Everyone,
I'm loading 690k odd records to cube
I am facing short dump error while data request is processed to cube.
In ST22 i'm getting Timeout Error.
Buffer time is set for 10mins to process
Can anyone guide me in this issue.
Thanks in advance

Hi,
Due to data volume your load took more than 7hrs. in general time out time is 7hrs. so in your case its may exceeded.
Try to increase time out time for your info package.
Go to your info pack--> menu scheduler --> time out time--> increase 7 hrs to 14hrs and trigger your load again. if its full load delete failed load and retrigger.
Thanks

Short dump error when using count(*)

Hi Experts
I am getting a short dump error when selecting the records >= current date - 30 see the coding and comment please correct the coding I want to know the ztable records it is important for command interface.
I have 1402345 records available after deleting the records but as the memory is not enough it is giving short dump error
select count(*) from ZINT_TABLE
select count(*) from ZINT_MSGS
   select * from zint_data
             nto table izint_d2 . "PACKAGE SIZE 20000
   where STATUS = 'OK' AND CREATED_ON >= w_date1.          " VALUE
endselect.**
report z_eslp_command_records.
data: cnt type i.
data: cnt2 type i.
data: cnt3 type i.
data: cnt4 type i.
DATA:
     w_date1 like sy-datum .
DATA:
     w_date2 like sy-datum.
data: izint_msgs type table of zint_msgs.
data: izint_data type table of zint_data.
data: izint_m2 type table of zint_msgs.
data: izint_d2 type table of zint_data.
INITIALIZATION.
w_date1 = sy-datum - 30.
w_date2 = sy-datum - 30.
select * from zint_data
             into table izint_data PACKAGE SIZE 3000
             where STATUS = 'OK' AND CREATED_ON <= w_date1.   " ZERO
endselect.
select * from zint_msgs
             into table izint_msgs PACKAGE SIZE 3000
              where CREATED_ON <= w_date2.              " ZERO
endselect.
select * from zint_data
             into table izint_d2 PACKAGE SIZE 20000
   where STATUS = 'OK' AND CREATED_ON >= w_date1.          " VALUE
endselect.
select * from zint_msgs
             into table izint_m2 PACKAGE SIZE 20000
where CREATED_ON >= w_date2.                            " VALUE
endselect.
select * from zint_data
            into table izint_data2
where STATUS = 'OK' AND CREATED_ON >= CONVERT(CHAR(8), GETDATE() - 30, 112)).
ENDSELECT.
select * from zint_msgs
            into table izint_msgs2
where CREATED_ON >= CONVERT(CHAR(8), GETDATE() - 30, 112)).
ENDSELECT.
sort izint_data by created_on ascending.
sort izint_msgs by created_on ascending.
sort izint_d2 by created_on ascending.
sort izint_m2 by created_on ascending.
describe table izint_data lines cnt.
describe table izint_msgs lines cnt2.
describe table izint_d2 lines cnt3.
describe table izint_m2 lines cnt4.
write:/ ' Note: THE RECORDS COUNTED SHOULD SHOW ZERO ELSE THE SCRIPT FAILED TO RUN' color 3.
skip.
write:/ '1. Records counted in ZINT_DATA   <=current date - 30                   :' color 2,                        cnt color 4.
write:/ '2. Records available in ZINT_DATA >=current date - 30                   'color 4,                   cnt3 color 4 .
skip.
write:/ '2. Records counted in ZINT_MSGS   <=current date - 30                   :' color 2                 ,                      cnt2 color 4.
write:/ '4. Records available in ZINT_MSGS >=current date - 30                   'color 4 ,            cnt4 color 4 .
TOP-OF-PAGE.
WRITE:/55(60) ' WAGNERS INVESTMENT LIMITED '.
WRITE:/50(40) ' Command Interface Data' CENTERED .
WRITE:/50(40) '----
' CENTERED .
FORMAT INTENSIFIED ON.
SKIP.
"FORMAT COLOR COL_HEADING.
ULINE.
FORMAT COLOR 1.
END-OF-PAGE.

Answer

Getting a program Dump Error in Herarchial ALV

Hello All,
I am getting a dump error when I am executing the below program. Kindly help as I am not getting the output. However all the subroutines are getting properly populated with data. Getting a dump error while calling the function : REUSE_ALV_HIERSEQ_LIST_DISPLAY
Pasted below are both the question and solution. Copy the solution in SE38 and execute it to check out the dump error.
Kindly help.
Thanks,
Vinod.
QUESTION :-
Objective
     Hierarchical ALV for displaying Sales documents per customer
Design
     Create a program that will allow the user to display all customers that have placed Sales Orders in the given date range. The user will have an ability to drill-down to see the sales order items per customer.
     Selection screen fields
          Sales order creation date (range)
          Customer number (range)
     Output
          Header
               Customer Number
               Customer Name
               Total Order value (sum of order values from items below)
          Details
Sales order number
Material number
Order quantity
Order value
Reference
     Tables: KNA1, VBAK, VBAP
     Transaction VA03 (Sales order)
SOLUTION :-
*& Report Z_HALV_32722                                                *
REPORT Z_HALV_32722                            .
TYPE-POOLS: slis.
TABLES : kna1,
         vbak.
SELECT-OPTIONS: s_cst_no FOR kna1-kunnr.
SELECT-OPTIONS: s_cr_dt FOR vbak-erdat.
DATA : BEGIN of ty_hdr,
        kunnr TYPE vbak-kunnr,
        name1 TYPE kna1-name1,
        netwr TYPE vbak-netwr,
        END of ty_hdr,
        gt_hdr LIKE TABLE OF ty_hdr,
        gs_hdr LIKE LINE OF gt_hdr.
DATA : BEGIN of ty_ln,
        kunnr TYPE vbak-kunnr,
        vbeln TYPE vbap-vbeln,
        matnr TYPE vbap-matnr,
        kwmeng TYPE vbap-kwmeng,
        netwr TYPE vbap-netwr,
        END of ty_ln,
        gt_ln LIKE TABLE OF ty_ln,
        gs_ln LIKE LINE OF gt_ln.
DATA : BEGIN of ty_hdr1,
        kunnr TYPE vbak-kunnr,
        END of ty_hdr1,
        gt_hdr1 LIKE TABLE OF ty_hdr1,
        gs_hdr1 LIKE LINE OF gt_hdr1.
DATA : gt_fc TYPE slis_t_fieldcat_alv,
       gs_fc LIKE LINE OF gt_fc,
       gs_k_fld TYPE slis_keyinfo_alv,
       gt_layout TYPE slis_layout_alv,
       gv_repid TYPE sy-repid.
START-OF-SELECTION.
gv_repid = sy-repid.
perform fetch_data.
perform prepare_fc.
perform prepare_layout.
perform show_output.
*&      Form fetch_data
      text
--> p1        text
<-- p2        text
form fetch_data .
SELECT kunnr
INTO CORRESPONDING FIELDS OF TABLE gt_hdr1
FROM vbak
WHERE vbak~kunnr IN s_cst_no
AND vbak~erdat IN s_cr_dt.
DELETE ADJACENT DUPLICATES FROM gt_hdr1 COMPARING kunnr.
LOOP AT gt_hdr1 INTO gs_hdr1.
SELECT SINGLE vbakkunnr kna1name1 SUM( vbak~netwr )
INTO (gs_hdr-kunnr, gs_hdr-name1, gs_hdr-netwr)
FROM vbak INNER JOIN kna1
ON vbakkunnr = kna1kunnr
WHERE vbak~kunnr = gs_hdr1-kunnr
GROUP BY vbakkunnr kna1name1.
APPEND gs_hdr TO gt_hdr.
SELECT vbakkunnr vbapvbeln vbapmatnr vbapkwmeng vbap~netwr
INTO CORRESPONDING FIELDS OF TABLE gt_ln
FROM vbap INNER JOIN vbak
ON vbapvbeln = vbakvbeln
WHERE vbak~kunnr = gs_hdr1-kunnr.
ENDLOOP.
endform.                    " fetch_data
*&      Form prepare_fc
      text
--> p1        text
<-- p2        text
form prepare_fc .
CLEAR gs_k_fld.
gs_k_fld-header01 = 'KUNNR'.
gs_k_fld-item01   = 'KUNNR'.
CLEAR gs_fc.
gs_fc-fieldname = 'KUNNR'.
gs_fc-tabname   = 'GT_HDR'.
gs_fc-seltext_l = text-001.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'NAME1'.
gs_fc-tabname   = 'GT_HDR'.
gs_fc-seltext_l = text-002.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'NETWR'.
gs_fc-tabname   = 'GT_HDR'.
gs_fc-seltext_l = text-003.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'VBELN'.
gs_fc-tabname   = 'GT_LN'.
gs_fc-seltext_l = text-004.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'MATNR'.
gs_fc-tabname   = 'GT_LN'.
gs_fc-seltext_l = text-005.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'KWMENG'.
gs_fc-tabname   = 'GT_LN'.
gs_fc-seltext_l = text-006.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'NETWR'.
gs_fc-tabname   = 'GT_LN'.
gs_fc-seltext_l = text-007.
APPEND gs_fc TO gt_fc.
endform.                    " prepare_fc
*&      Form prepare_layout
      text
--> p1        text
<-- p2        text
form prepare_layout .
gt_layout-colwidth_optimize = 'X'.
gt_layout-expand_fieldname = 'TST'.
endform.                    " prepare_layout
*&      Form show_output
      text
--> p1        text
<-- p2        text
form show_output .
CALL FUNCTION 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'
EXPORTING
I_INTERFACE_CHECK              = ' '
    I_CALLBACK_PROGRAM             = gv_repid
I_CALLBACK_PF_STATUS_SET       = ' '
I_CALLBACK_USER_COMMAND        = ' '
    IS_LAYOUT                      = gt_layout
    IT_FIELDCAT                    = gt_fc
IT_EXCLUDING                   =
IT_SPECIAL_GROUPS              =
IT_SORT                        =
IT_FILTER                      =
IS_SEL_HIDE                    =
I_SCREEN_START_COLUMN          = 0
I_SCREEN_START_LINE            = 0
I_SCREEN_END_COLUMN            = 0
I_SCREEN_END_LINE              = 0
I_DEFAULT                      = 'X'
I_SAVE                         = ' '
IS_VARIANT                     =
IT_EVENTS                      =
IT_EVENT_EXIT                  =
    i_tabname_header               = 'GT_HDR'
    i_tabname_item                 = 'GT_LN'
I_STRUCTURE_NAME_HEADER        =
I_STRUCTURE_NAME_ITEM          =
    is_keyinfo                     = gs_k_fld
IS_PRINT                       =
IS_REPREP_ID                   =
I_BYPASSING_BUFFER             =
I_BUFFER_ACTIVE                =
IMPORTING
E_EXIT_CAUSED_BY_CALLER        =
ES_EXIT_CAUSED_BY_USER         =
tables
    t_outtab_header                = GT_HDR[]
    t_outtab_item                  = GT_LN[]
EXCEPTIONS
PROGRAM_ERROR                  = 1
OTHERS                         = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endform.                    " show_output

Everything looks fine with the gt_layout, it is not an internal table, so no need to append to it, it is simply a structure, but you do tell it that TST is the expand field, but there is no field of this name in your internal for the header, so add it like this.
DATA : BEGIN of ty_hdr,
kunnr TYPE vbak-kunnr,
name1 TYPE kna1-name1,
netwr TYPE vbak-netwr,
<b>TST type c,</b>
END of ty_hdr,
Doing so should make you program work correctly.
Regards,
Rich Heilman
Message was edited by:
        Rich Heilman

Dump error when clicked on text elements in SAP Script window

Hi All,
There is an inclusion in SAP Script. I have written the code in driver program. I need to pass the value to SAP Script in the requested position. But when I go to SE71 > Form Name > Change or Display > MAIN Window > Text Elements > I get a dump error.
Category               ABAP Programming Error
Runtime Errors         DATA_LENGTH_TOO_LARGE
Except.                CX_SY_RANGE_OUT_OF_BOUNDS
ABAP Program           SAPLSTXK
Application Component BC-SRV-SCR
Date and Time          30.04.2014 20:00:08
Short text
     Invalid partial field access: Length is too large
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLSTXK" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_RANGE_OUT_OF_BOUNDS', was not
      caught in
     procedure "TOKEN_COMMENT" "(FORM)", nor was it propagated by a RAISING clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
    The reason for the exception is:
    In the executed program "SAPLSTXK", the system attempted to access the field
    "ITF_TOKEN" of the type "C" and with the length 255 using the length 272.
    However, a partial field access with a length specification that is
    larger than the field length is not allowed.
How to correct the error
    Reduce the length used to access the field.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DATA_LENGTH_TOO_LARGE" "CX_SY_RANGE_OUT_OF_BOUNDS"
    "SAPLSTXK" or "LSTXKFRN"
    "TOKEN_COMMENT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
2937 * todo empty comment ???
2938       if g_tm_open    eq true or     " Section
2939          g_tm_b_close eq true.
2940         l_token = '\chcbpat0'.
2941         l_len = strlen( l_token ).
2942         token_control = true.
2943         assign l_token to <itf1>.
2944         perform put_itf1_new using l_len.
2945         perform token_line_begin changing l_next_token.
2946       else.                          " without section
2947         concatenate '\chcbpat0\line' g_cf_string l_cbpat_token into l_token.
2948         l_len = strlen( l_token ).
2949         token_control = true.
2950         assign l_token to <itf1>.
2951         perform put_itf1_new using l_len.
2952       endif.
2953     elseif l_next_token-code eq ')L'.         " \par
2954       l_token = '\par'.
2955       l_len = strlen( l_token ).
2956       token_control = true.
2957       assign l_token to <itf1>.
2958       perform put_itf1_new using l_len.
2959     elseif l_next_token-code eq '(C' or       " \par + format
2960            l_next_token-code eq ')C' or
2961            l_next_token-code eq '(&' or
2962            l_next_token-code eq 'TA' or
2963            l_next_token-code eq 'SC' or
2964            l_next_token-code eq 'ST'.
2965       concatenate '\chcbpat0\par' g_pf_string g_cf_string l_cbpat_token into l_token.
2966       l_len = strlen( l_token ).
>>>>>       itf_token(l_len) = l_token.
2968       token_control = true.
2969       assign l_token to <itf1>.
2970       perform put_itf1_new using l_len.
2971     endif.
2972
2973 * Step 7: (L to disarm
2974   if g_compose eq true and
2975      l_next_token-code eq '(L'.
2976     perform read_next_itf_token(rstxscan) using p_token.
2977   endif.
2978
2979 ENDFORM.                    " token_comment
2980 *&---------------------------------------------------------------------*
2981 *&      Form create_lang_info
2982 *&---------------------------------------------------------------------*
2983 *       add default language to rtf
2984 *----------------------------------------------------------------------*
2985 *      -->P_HEADER text
2986 *      <--P_RESULT text
How do I open the text elements? I need to pass the variable inside SAP Script.
Please Help. The requirement is pending from very long. Not able to rectify this issue.
Regards,
Rekha

Hi,
There is a SAP Note about this problem
566794 - Runtime error: STRING_OFFSET_TOO_LARGE during conversion
Correction Instructions
Correction Instructions
Software Component
Valid from
Valid to
Number
SAP_BASIS
46B
46D
473267
SAP_BASIS
610
620
473185
Support Packages & Patches
Support Packages
Software Component
Release
Support Package
SAP_BASIS
46B
SAPKB46B48
46C
SAPKB46C39
46D
SAPKB46D28
610
SAPKB61027
620
SAPKB62014
Regards
Miguel

Dump error while creating Invoicing document

Moderator note - this is the same problem as identified in thread Error is generated in Print workbench function ISU_INV_BILL_PREPARE. Thread locked and poster notified of rules violation.
Hi Experts,
I am new to ISU application.Please provide solution for below mentioned dump error.
The error is generated in Print workbench function ISU_INV_BILL_PREPARE which is called from application form IS_U_BILL (/1PWB/SAPL20020100218092657) when I'm trying to generate invoice for the bill in EASIBI.
Error analysis
Short text of error message:
Unexpected ELSE case: field sy-subrc with value 0 (/1PWB/200201002180926
57 )
Long text of error message:
Something has occurred in a CASE or IF construct which the
developer did not expect, or which is not permissible here.
System Response
Procedure
Note the field name and field value from the message as well as the
data pattern which lead to the error. Create a problem message.
Technical information about the message:
Message class....... "E9"
Number.............. 898
Variable 1.......... "sy-subrc"
Variable 2.......... 0
Variable 3.......... "/1PWB/20020100218092657"
| Variable 4.......... " "
Thanks in Advance.
Vaseem
Edited by: William Eastman on Mar 9, 2010 2:34 PM
Edited by: William Eastman on Mar 9, 2010 2:36 PM

Hi Experts,
Please reply..... It's very important.
Thanks
Vaseem
Moderator note: DO NOT beg for answers, or suggest that you need an immediate reply. Read the rules of engagement here Research Resources and Rules of Engagement
Edited by: William Eastman on Mar 9, 2010 2:24 PM

I am getting dump error while running one report in one select query

Hi,
While running a report program, I am getting a dump error in one select query. So could you please correct the select query so that I can't face the dump error.
SELECT vbeln parvw kunnr INTO CORRESPONDING FIELDS OF TABLE l_t_vbpa
FROM vbpa
FOR ALL ENTRIES IN l_t_backorder_item
WHERE vbeln = l_t_backorder_item-vbeln AND
( ( parvw = c_we AND kunnr IN rng_shipto ) OR ( parvw = c_ag AND
kunnr IN rng_soldto ) ) .
<removed by moderator>
Best Regards,
BDP
Edited by: Thomas Zloch on Apr 30, 2010 12:31 PM

Hi Bansidhar,
It would be helpful if you could tell what type of dump it is.
If it is a timeout you should check whether l_t_backorder_item is empty - in this case ALL document numbers are selected. f you get the timeout with a populated table consider converting the l_t_backorder_item table into one ore more ranges tables - the select with ranges tables is way quicker than 'for all entries'. But take care the ranges table has not to many entries - the SAP SQL converter puts this into one huge SQL statement and this might become too big to be handled by the database (depends on the actual underlying database).
I would also consider splitting the SELECT into two (2nd one with 'appending into table') to make the code easier to understand It also helps the database system determining a strategy for the select.
Regards,
Gerd Rother

Dump error while creating or double click the info package

Hello experts,
I have actived infocube 0FIAR_C03 in BI content. Ago, The creation infopackage have been deleted in the past , today, I created a infopackage, while I update mode selected u2018initialize delta processu2019, then click save button , the system prompt u2018Deltas already loaded for request REQU_D64R47LDUSZHY9CBIB86WMLFJ init.selection; no 2. initu2019, I canoti save it for my setting. Why is this?
Then I have search cause in SDN, and I have reference OSS Note 852443 to do .
Note 852443 have mention some table: RSSELDONE、RSSDLINIT、RSSDLINITSEL、ROOSPRMSC、ROOSPRMSF.
I have to delete that request of record using se16 in these tables: RSSELDONE、RSSDLINIT、RSSDLINITSEL.
in my BI 7.0 system, ROOSPRMSC、ROOSPRMSF is no any data.
I was no found delta queue in RSA7.
Now . Dump error while creating or double click the info package, how can I change this?
Please let me know the solution.
Thanks for your help.
Best Regards
Steve

Here are some links which deals with same issue.
Re: Dump In Infopackage
Re: Getting into Short dump at the time of selecting InfoPackage to execute for
Short dump while performing init in infopackage
Re: Infopackage going into short dump
Thanks.

Dump error after calling a global class from se24

this is the small code i did so far.
parameters: X type i,
                  Y type i.
data: Z type i.
data: con1 type ref to ZTEST1.
CALL METHOD con1->zm1
EXPORTING
    a      = x
    b      = y
IMPORTING
    c      = z.
write:/ z.
after executing iam getting a dump error-
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught and
therefore caused a runtime error.
The reason for the exception is:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component (variable: "CON1").
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.

Hi, Could you please tell me how to solve this issue?

Short Dump error while loading data from R/3 to ODS

Hello,
while trying to load data into the ODS from R/3 I get the following short dump error message. How do I carry out step 1 in the below procedure. Where do i find the Activate Function. And idea?
Thanks,
SD
                                                                                Diagnosis
Form routine CONVERT_ITAB_RFC is incorrect in transfer program
     GP4C0LOLZ6OQ70V8JR365GWNW3K .
System Response
The IDoc processing was terminated and indicated as incorrect. The IDoc
     can be reimported at any time.
Procedure
1. Go to the transfer rule maintenance for your InfoSource
         ZFIN_TR_FLQITEM_FI and the source system DA_M_10 and regenerate the
         transfer program using the function Activate. Remove possible syntax
         errors on the basis of your conversion routines.
2. Restart the processing of this IDoc.
3. If the error occurs again search for SAPNet R/3 notes, and create a
        problem message if necessary.
Edited by: Sebastian D'Souza on Jan 13, 2009 3:22 PM

Hi.......
Goto RSA1>> then to source system tab (on left side) >> double click on the desired source system...........Then on the right side you have the Datasource tree..........there search the datasource and activate.......Also u can Replicate the datasource again.......and activate the Transfer rules using the program : RS_TRANSTRU_ACTIVATE_ALL
After this operation when come back to source system (R/3).........I think the error log line will be disappeared from SM58......... Then repeat the load.........
Also u can try to Activate the infosource once...........in RSA1.........before repeating the load....
Hope this helps......
Regards,
Debjani....

ABAP dump error while updating product master in APO

Hi All,
Greetings from Vijay!
I need to your help to resolve below issue ;
I am getting error '
No simulation parameters could be set for the
active version'
While i am updating and trying to assign active version to my product master in APO which are created in APO for regression testing
and also sometimes system throwing dump error'
Error in the ABAP Application Program
The current ABAP program "/SAPAPO/SAPLDM_LC_SQL" had to be terminated because
it has
come across a statement that unfortunately cannot be executed.;
I appreciate your help
Thanks
Vijay Job

Hi Vijay,
Can you check note 1465462 ?
The same problem is mentioned in the note with correction .
Regards,
Mukesh pandey

Dump error while filling the Setup table

Hi All,
I am trying to fill the setup table.While filling the stup table for 2lis_03_BF datasource, i got the Dump error after some time. I have checked the data in Setup table and found 9000 records.
Shall i proceed further by pulling the data from R/3 to BW.I have checked the data in RSA3 and got some data.
Shall i schedule the data from BW side.
Pls help on this issue.
Thanks,
Siva.

Thanks Reddy and JS.
I have checked the TCODE SM37 and found no jobs are available. I have checked the TCODE : NPRT and found some logs.In this, it is not showing any errors.
I have checked in SM21 and found some errors.
Time_______________Text
17:08:10____________Transaction Canceled M2 630 ( )
17:23:47____________Run-time error "TIME_OUT" occurred
17:23:47____________> Short dump "090302 172347 sand1_W2 2_00 " generated
17:30:08____________Status: 80% of IL00.DAT is in use
17:30:17____________Status: 90% of IL00.DAT is in use
17:30:18____________Overflow of Paging File (032768 Blocks)
17:30:18____________Run-time error "MEMORY_NO_MORE_PAGING" occurred
17:30:19____________> Short dump "090302 173018 sand1_W2 2_00 " generated
Shall i execute filling the setup table again. Do i need to give termination time More ( 2 Hrs difference)
Any issue on refilling the setup table again.
Pls suggest.
Thanks,
Siva.

Short dump error while filling setup tables for 2LIS_06_INV

Hi All,
I am trying to fill the setup table.While filling the stup table for 2lis_06_inv datasource, i got the Dump error after some time.
Error
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Short text
    SQL error in the database when accessing a table.
plz can anyone help me out...

Dear friends,
I tried it by giving the selection on fiscal year,but again same problem.If i give 1 0r 2 document numbers in selection then extractor works fine.
error:in detail.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Short text
    SQL error in the database when accessing a table.
Information on where terminated
    Termination occurred in the ABAP program "SAPLMRMBW" - in "BW_RETRIEVE_DB_CO".
    The main program was "RMCENEUR ".
    In the source code you have the termination point in line 827
    of the (Include) program "LMRMBWF01".
    The program "SAPLMRMBW" was started as a background job.
    Job Name....... "RMCENEUR"
    Job Number..... 10524100
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "BW_RETRIEVE_DB_CO" "(FORM)", but it was neither handled locally nor
     declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLMRMBW "; its source code begins in line
    806 of the (Include program "LMRMBWF01 ".
806 FORM bw_retrieve_db_co USING    t_mcrbkey_bv    TYPE mcrbkey_t
807                                  t_mcrbkey_nbv   TYPE mcrbkey_t
808                                  t_ekbe_acc      TYPE t_ekbe
809                         CHANGING t_mcrbco        TYPE mcrbco_t.
810
811   TYPES: BEGIN OF s_target.
812   TYPES: table_left LIKE rbco.
813   TYPES: table_right TYPE rbex.
814   TYPES: END OF s_target.
815   TYPES: t_target TYPE TABLE OF s_target.
816
817
818   DATA: t_rbco_nbv TYPE t_target,
819         t_rbco_bv   TYPE t_target,
820         s_rbco      TYPE s_target,
821         s_ekbe      LIKE ekbe,
822         s_mcrbco    TYPE mcrbco,
823         l_index     LIKE sy-tabix.
824
   825 * Data source: invoice item non-background
826   IF NOT t_mcrbkey_nbv[] IS INITIAL.
*>>>>>     SELECT * FROM rbco AS r LEFT OUTER JOIN rbex AS i*
828        ON   ( rmandt = imandt AND
829               rbelnr = ibelnr AND
830               rbuzei = ibuzei AND
831               rcobl_nr = icobl_nr )
832        INTO TABLE t_rbco_nbv
833        FOR ALL ENTRIES IN t_mcrbkey_nbv
834        WHERE r~gjahr = t_mcrbkey_nbv-gjahr AND
835              r~belnr = t_mcrbkey_nbv-belnr.
836   ENDIF.
837 * Data source: invoice item background
838   IF NOT t_mcrbkey_bv[] IS INITIAL.
839     SELECT * FROM rbco AS r LEFT OUTER JOIN rbex AS i
840        ON   ( rmandt = imandt AND
841               rbelnr = ibelnr AND
842               rbuzei = ibuzei AND
843               rcobl_nr = icobl_nr )
844        INTO TABLE t_rbco_bv
845        FOR ALL ENTRIES IN t_mcrbkey_bv
846        WHERE r~gjahr = t_mcrbkey_bv-gjahr AND
Thnks in advance

Dump error in db02 CONNE_IMPORT_WRONG_COMP_TYPE

Similar Messages

Maybe you are looking for