ABAP Dump with using FM 'REUSE_ALV_GRID_DISPLAY'

Hi,
I copied a Standard report program(RCOPCA02) to Z-Program for adding two new fields in the report output. I added those two new fields in the field catalog also. Actually the program is using
FM 'REUSE_ALV_GRID_DISPLAY' , when i execute the program it is dumping.
when i use the same program with FM 'REUSE_ALV_LIST_DISPLAY' with same field catalog the fields are displaying in the layout and report but the values are not populating in the report.
Where is the problem i am not understanding.
Thanks,
fractal

I checked in Debug mode, the values are coming in Internal Table correctly...
Here is the Dump.
Runtime Errors              MESSAGE_TYPE_X
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
Error analysis
Short text of error message:
Technical information about the message:
Message classe...... "0K"
Number.............. 000
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
"MESSAGE_TYPE_X" C
"SAPLSLVC " or "LSLVCF01 "
"LINE_OUT_NEW_2"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
Information on where termination occurred
The termination occurred in the ABAP program "SAPLSLVC " in "LINE_OUT_NEW_2".
The main program was "ZRCOPCA02 ".
The termination occurred in line 924 of the source code of the (Include)
program "LSLVCF01 "
of the source code of program "LSLVCF01 " (when calling the editor 9240).
Source code extract
008940                   gs_roid-row_id = rs_row-index * -1.
008950                 endif.
008960                 gs_roid-sub_row_id = rs_row-rowtype+7(10).
008970                 gs_poid-row_id = gs_roid-row_id.
008980                 gs_poid-sub_row_id = gs_roid-sub_row_id.
008990                 gs_poid-rowtype    = rs_row-rowtype.
009000                 gs_poid-index      = rs_row-index.
009010                 insert gs_poid into table rt_poid.
009020               endif.
009030               append gs_roid to rt_roid.
009040
009050               loop at rt_fieldcat assigning <ls_fieldcat> where tech ne 'X' and
009060                                                                 no_out ne 'X'.
009070
009080                 if gflg_invisible = 'X'.
009090                   if <ls_fieldcat>-do_sum is initial.
009100                     clear gflg_invisible.
009110                     continue.
009120                   else.
009130                     clear g_col_counter.
009140                     clear gflg_invisible.
009150                   endif.
009160                 endif.
009170
009180                 clear gs_lvc_data.
009190                 clear g_style.
009200
009210                 assign component
009220                        <ls_fieldcat>-fieldname of structure rt_data to <g_field>.
009230                 if sy-subrc ne 0.
>                   message x000(0k).
009250                 endif.
009260
009270                 g_col_counter = g_col_counter + 1.
009280
009290                 gs_lvc_data-row_pos = r_row_counter.
009300                 gs_lvc_data-col_pos = g_col_counter.
009310                 gs_lvc_data-row_id = gs_roid-row_id.
009320                 gs_lvc_data-sub_row_id = gs_roid-sub_row_id.
009330
009340             *   Endtotal and average
009350                 if rs_row-rowtype(1) ca 'T' and <ls_fieldcat>-do_sum = 'C'.
009360             *     save the actual grouplevel information
009370                   gs_grouplevels = rs_grouplevels.
009380                   clear g_lines.
009390
009400             *     get number of lines of the collect table
009410                   describe table rt_data lines g_lines.
009420             *     if there is only one line or the field has no references so
009430             *     that only the first line has to be considered
SY field contents.....................           SY field contents........
SY-SUBRC           4                                  SY-INDEX           1
SY-TABIX           95                                 SY-DBCNT           0
SY-FDPOS           0                                  SY-LSIND           0
SY-PAGNO           0                                  SY-LINNO           1
SY-COLNO           1                                  SY-PFKEY           STANDARD_GRID
SY-UCOMM           DTC_CONT
SY-TITLE           Profit Center: Actual Line Items
SY-MSGTY           X                                  SY-MSGID           0K
SY-MSGNO           000                                SY-MSGV1
SY-MSGV2                                              SY-MSGV3
SY-MSGV4
No.... Type........ Name..........................
       Program
       Include                                  Line
       Class
    14           FORM                   LINE_OUT_NEW_2
            SAPLSLVC
            LSLVCF01                                             924
    13           FORM                   TOTAL_OUT_NEW
            SAPLSLVC
            LSLVCF01                                            1297
    12           FORM                   DATA_TABLE_PREPARE
            SAPLSLVC
            LSLVCF36                                             833
    11           FORM                   LVC_TABLE_FOR_DISPLAY_PREPARE
            SAPLSLVC
            LSLVCF36                                             259
    10           FUNCTION               LVC_TABLE_FOR_DISPLAY_PREPARE
            SAPLSLVC
            LSLVCU35                                             106
     9           METHOD                 SOFT_REFRESH_TABLE_DISPLAY
            CL_GUI_ALV_GRID===============CP
            CL_GUI_ALV_GRID===============CM01P                  240
            CL_GUI_ALV_GRID
     8           METHOD                 REFRESH_TABLE_DISPLAY
            CL_GUI_ALV_GRID===============CP
            CL_GUI_ALV_GRID===============CM00T                  125
            CL_GUI_ALV_GRID
     7           METHOD                 MAINTAIN_VARIANT
            CL_GUI_ALV_GRID===============CP
        CL_GUI_ALV_GRID===============CP
        CL_GUI_ALV_GRID===============CM00P                  313
        CL_GUI_ALV_GRID
6           METHOD                 EXECUTE_FCODE
        CL_GUI_ALV_GRID===============CP
        CL_GUI_ALV_GRID===============CM007                  582
        CL_GUI_ALV_GRID
5           METHOD                 SET_FUNCTION_CODE
        CL_GUI_ALV_GRID===============CP
        CL_GUI_ALV_GRID===============CM01E                   53
        CL_GUI_ALV_GRID
4           FORM                   PAI
        SAPLSLVC_FULLSCREEN
        LSLVC_FULLSCREENF01                                 1776
3           MODULE (PAI)           PAI
        SAPLSLVC_FULLSCREEN
        LSLVC_FULLSCREENI01                                    4
2           FUNCTION               REUSE_ALV_GRID_DISPLAY
        SAPLSLVC_FULLSCREEN
        LSLVC_FULLSCREENU01                                   91
1           EVENT                  START-OF-SELECTION
        ZRCOPCA02
        ZRCOPCA02                                            928

Similar Messages

ABAP Dump while using "Upload from clipboard"

Hi,
We are facing ABAP dump when using "upload from clipboard" funciton without any data on the clipboard.
"Upload data" is working fine if some data exists on the clipboard. If in case of no data on the clipboard, it is leading to an ABAP dump.
Appreciate if anyone could point some OSS note or any solution if you've already faced this issue.
This is happening in our BW system with SAP_BASIS "SAPKB62018" and SAP_ABA "SAPKA62018".
Same thing happens in our BW test systems which are upgraded to the latest support pack.
Following is the error analysis
Error analysis
A RAISE statement in the program "CL_GUI_FRONTEND_SERVICES======CP " raised the
exception
condition "CNTL_ERROR".
Since the exception was not intercepted by a superior program
in the hierarchy, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
How to correct the error
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"RAISE_EXCEPTION" C
"CL_GUI_FRONTEND_SERVICES======CP " or "CL_GUI_FRONTEND_SERVICES======CM00T "
"CLIPBOARD_IMPORT"

Hi,
When you say 'We are facing ABAP dump when using "upload from clipboard" funciton without any data on the clipboard.', are you using this in a custom program and are you running your custom program in the background?
From the error you mentioned, to me it looks like you had a control error and controls are for foreground, online process and not suitable for background processing. Same argument holds good for most of the enjoy SAP transactions when you try to do BDC, they will give you a similar error if you hit the piece of code where controls are used.
Controls are created on the desktop of the user and in background this is not possible.
Please let me know if this is the reason.
Srinivas

ABAP Dump when using Shift Related Confirmations in CO11N

Dear SAP Gurus,
We have activated business function LOG_PP_SRN_CONF for doing shift
related confirmations using T Code CO11N.
On entering the production order and operation number in CO11N, the
system proposes the actual data. Then we select the shift number.
If we try to change the selected shift again, the system gives an ABAP
dump - "OBJECTS_OBJREF_NOT_ASSIGNED" and exits the program.
Please suggest some SAP Note or other solution for the problem.
Thanks!
With Regards,
Nitin

Dear Prasobh,
Thanks for the quick reply.
I have checked the OSS Note - 1359966 as mentioned by you.
However, there are 2 things which make me feel that the note is not relevant to my scenario -
1. The note says that the confirmation profile for CO11N includes the detail area "0240-Quantities: Subdivided Quantities". I'm not using this detail area in my confirmation profile. Instead, I'm using the detail area "0200-Quantities: yield/scrap/rework/reason".
2. System may issue termination message COCF 000 when single-screen entry for the confirmation (CO11N) is called by another application such as the order information system (COOIS). However, I'm getting this dump when i run the T Code CO11N directly. Further, I don't get the termination message at all.
Please suggest.
With Regards,
Nitin

HR ABAP: Issue with using 'nocommit' parameter on FM HR_INFOTYPE_OPERATION

Issue with using nocommit parameter on FM HR_INFOTYPE_OPERATION:
My client has a requirement to create the following 4 infotypes in sequence in a LUW, i.e either all are created or none is created.
9045 (custom infotype)
0045
0078
0015
I tried to use the nocommit parameter on FM HR_INFOTYPE_OPERATION to insert the 4 infotypes
in a nocoomit mode and then at the end I have issued
'Commit Work', but to my surprise only I/T 0015 is created in the database and the first three (9045, 0045 and 0078) did not make it to database.
I searched many threads on SDN but could not find a solution.
Please let me know if there could be any solution to implement the LUW.
YOur inputs will be appreciated.

Hi ,
i think u can also try with this FM HR_MAINTAIN_MASTERDATA , see its documentations.
no commit works like a simulation mode , what u can do is ,
call FM for all Infotypes and collect all error msgs if any , then finally call FM for all infotypes again without passing nocommit work ( i.e space).
regards
prabhu

CONVT_CODEPAGE : Abap Dump while using Transfer statment

Hi,
I am getting an abap dumb CONVT_CODEPAGE when the program is executed.
It is encountered at the Transfer statement.
The file is opened in legacy text mode.
So i assume come characters in the file are not being interpretated using the existing system codepage,thus the dump.
Pls let me know if my analysis is incorrect.
Can anyone provide me with a workaround ?
Answers will be rewarded.
- Rohan

Hi Rohan
Check these notes :
Note 547308 - Shortdump CONVT_CODEPAGE when displaying measure
Note 752835 - Usage of the file interfaces in Unicode systems
Note 1057289 - Reasons for CX_SY_CONVERSION_CODEPAGE / CONVT_CODEPAGE
Note 853665 - LSMW: Dump occurs when file imported from application server

Urgent: ABAP Dump when using ME9F

Hi All,
I am using ME9F transaction to re-print POs. I get a short dump stating error "MOVE_TO_LIT_NOTALLOWED_NODATA". This just started happend after we applied the support packs. We are using custom SAP Script form.
Did anyone ever experience this problem before with ME9F or anywhere else.
Any ideas/suggestions will be greatly appreciated.
Thanks in advance.

Check out oSS # 354101
FYI
ME9E: short dump for releases with web releases
Symptom
If messages of JIT delivery schedules and forecast delivery schedules are issued with web release functions in Transactions ME9E, a short dump is generated, if print-dependent data is updated.
Additional key words
ME9E, short dump, MOVE_TO_LIT_NOTALLOWED_NODATA, ME_PRINT_PO, print-dependent data
Cause and prerequisites
For function module ME_PRINT_PO, the transfer of parameter DOC is carried out as a reference. As a result, you cannot change internal tables which are transferred with this parameter.
Solution
Set indicator 'Call by value' for parameter DOC of function module ME_PRINT_PO. As a result, the parameter is copied and can be changed.
Source code corrections
Hope thisll give you idea!!
<b>P.S award the points.</b>
Good luck
Thanks
Saquib Khan
"Some are wise and some are otherwise"

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.

CN41N ABAP Dump

Hi,
When I am tryin to change object type in CN41N it is giving ABAP dump with funtion "AC_system_flush" and this function is calling another function "AC_FLUSH_CALL",
Moreover when I checked "AC_FLUSH_CALL" got introduction statement
"NO DIRECT CALLS TO CONTROL FRAMEWORK FROM THIS FUNCTION MODULE".
Anyone has any ideas or come across this situation,,,Or any OSS notes ??
Any help will be appreciated.
Thanks
Abhinay

hi
check this Note 1245875 - CN41N: Blank screen displayed and termination without dump.

Regarding ABAP dump

Hi all,
When i execute the tcode co02 for the order number 10015447 (only) and when i change the technical information and when i press save button the system leads to ABAP dump
with parameters_not_valid message.
I tried to find out SAP notes for the problem all notes
saying that support package not required for version 4.6c.
Can anybody help me regarding this matter
with regards
chandu.

Hi Max,
The termination occurred in the ABAP/4 program "SAPLCXOT " in
"CX_SCHED_VIA_OPERATING_TIME".
The main program was "SAPLCOKO1 ".
The termination occurred in line 244
of the source code of program "LCXOTU01 " (when calling the editor 2440).
002260         if not i_date_end is initial.
002270           call function 'DATE_TIME_CONVERT'
002280                exporting
002290                     date                 = i_date_end
002300                     time                 = i_time_end
002310                importing
002320                     point_in_time        = i_point_in_time_end
002330                exceptions
002340                     date_before_rel_date = 01
002350                     date_to_big          = 02.
002360           if sy-subrc <> 0.
002370             e_message_code = mc-date_out_of_pit_range.
002380           endif.
002390         endif.
002400       endif.
002410   *   Eingabeparameter prüfen
002420       if i_point_in_time_start = 0 and
002430          i_point_in_time_end = 0.
     >         raise parameters_not_valid.
002450       elseif i_duration_sec <> 0 and
002460              i_point_in_time_start <> 0 and
002470              i_point_in_time_end <> 0.
002480         raise parameters_not_valid.
002490       endif.

Abap error with exception CX_SY_IMPORT_MISMATCH_ERROR.

Hello Everyone,
I got the abap dump with exception CX_SY_IMPORT_MISMATCH_ERROR.
The reason for the exception is:
When importing the object "AUS_S000", the component no. 13 in the dataset has a different type from the corresponding component
of the target object in the program "SAPLZTEST".
The data type is "P" in the dataset, but "C" in the program.
In How to correct Error:
Try to find out why the data type is 32.
I dont know what was the issue. When i check in ST22 i saw this message which i mentioned above Error Analysis and How to correct Error.
Please help me out, Your inputs will be helpufl

Hi All,
For the first time:
Try to import the data to the IT with old structure (say 32 fields)
         IMPORT ty_data = it_temp_old FROM DATABASE indx(sp) TO wa_indx ID obj.
   2. Append the data it_temp_old to new structure it_temp_new.
         EXPORT ty_data = it_temp_new TO DATABASE indx(sp) TO wa_indx ID obj.
For the next time:
Edit the IMPORT statement.
         Import the data to IT with new structure (40)
         IMPORT ty_data = it_temp_new FROM DATABASE indx(sp) TO wa_indx ID obj.
   2. Perform the required Operations and export the same data with new structure(40).
         EXPORT ty_data = it_temp_new TO DATABASE indx(sp) TO wa_indx ID obj.
Thanks,
Shameer.

ABAP DUMP - CX_SY_IMPORT_MISMATCH_ERROR

Hello Everyone,
I got the abap dump with exception CX_SY_IMPORT_MISMATCH_ERROR.
In Error Analasys:
I got the message. When importing the object "15" , the component 3 in the dataset had the different length from the corresponding component of the target object in the program.
The length is 32 in the dataset, but 20 in the program.
In How to correct Error:
Try to find out why the length of the object is 32.
I tried to load the data from one SRM ODS to another SRM ODS. all the data load went fine. I was trying to logout then i got this abap dump. I dont know what was the issue. When i check in ST22 i saw this message which i mentioned above Error Analysis and How to correct Error.
Please help me out, Your inputs will be helpufl
Thanks,
Lasya.

Hi,
Can you give solution to this problem.
Thank You,
SB.

How to avoid ABAP dump

Hi,
How to avoid ABAP dump
With Warm Regards
Khaja

Hi,
One of the most common short dumps is while entering the values in selection-screen.
So Before processing the selection-screen, the values entered by user need to be
examined and make sure program handle any kind of input through test cases.
And also Its good practice to catch exceptions raised in between the process of the
program.
Regards and Best wishes.

NW04 Testdrive Dump when using ABAP Webservice whizard

Hello,
I have NW4 running on FC5.
When I try to create a webservice in SE80 the whizard dumps:
Runtime Errors         GEN_NO_GENINFO_FOR_DATID
       Occurred on     21.02.2008 at   10:08:16
No generation information for DATID "%_#D18404".
What happened?
Processing had to be terminated because an internal error
occurred when generating the ABAP/4 program "CL_SWF_CNT_FACTORY============CP".
What can you do?
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
There is no generation information for the internal ID "%_#D18404".
This is most probably due to an
invalid DATID or an object type for which there is usually
no generation information.
Possible causes for the error are:
- an RSYN programming error
- the following internal constants were used
%_ENDIAN, %_CHARSIZE, %_MINCHAR, %_MAXCHAR, %_HORIZONTAL_TAB,
%_VERTICAL_TAB, %_NEWLINE, %_CR_LF, %_FORMFEED, or %_BACKSPACE
For optimization reasons, no generation information is created for these
constants. Therefore these constants can generally only be used with
the VALUE specification of DATA, CONSTANTS etc.
How to correct the error
Use the Transaction SYNT to search for the error.
System environment
SAP Release.............. "640"
Application server....... "BLN787"
Network address.......... "192.168.100.2"
Operating system......... "Linux"
Release.................. "2.4.22-1.2129.nptlsm"
Hardware type............ "i686"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "BLN787"
Database type............ "ADABAS D"
Database name............ "NW4"
Database owner........... "SAPNW4"
Character set............ "en_US.ISO-8859-1"
SAP kernel............... "640"
Created on............... "Jan 13 2004 20:13:34"
Created in............... "Linux 2.4.18-64GB-SMP
#1_SMP_Wed_May_15_13:27:16_GMT_2002 i686"
Database version......... "SAPDB 7.4.3.029 "
Patch level.............. "1"
Patch text............... " "
Supported environment....
Database................. "SAP DB 7.4.3, MySQL MaxDB 7.5.0"
SAP database version..... "640"
Operating system......... "Linux 2.2, Linux 2.4"
Memory usage.............
Roll..................... 8112
EM....................... 15679560
Heap..................... 0
Page..................... 49152
MM Used.................. 6768560
MM Free.................. 546564
SAP Release.............. "640"
User, transaction...
Client.............. 000
User................ "DEVELOPER"
Language key........ "E"
Transaction......... " "
Program............. "CL_SWF_CNT_FACTORY============CP"
Screen.............. " "
Screen line......... " "
Information on where terminated
The termination occurred during generation of the ABAP program
"CL_SWF_CNT_FACTORY============CP".
The point of termination was in line 64 of the ABAP source code of the
(Include) program "CL_SWF_CNT_FACTORY============CCIMP".
of the program "CL_SWF_CNT_FACTORY============CCIMP" (when calling the editor
640).
Source code extract
000340
000350   **** Test methods. Use TA SE80 or RS_AU_LIGHT for complete test.
000360
000370
000380   **** Test METHOD test_instance_manager_state
000390     METHOD test_instance_manager_state.
000400       DATA:
000410         l_abap_rh1      TYPE swfrcntref, "cont IF reference
000420         l_abap_rh2      LIKE l_abap_rh1,
000430
000440         l_inst_manager_state    TYPE xfeld,
000450         l_num_requests          TYPE i,
000460         l_num_hits              TYPE i,
000470         l_num_misses            TYPE i,
000480         l_cache_size            TYPE i,
000490         l_last_reset            TYPE timestamp,
000500         l_non_expected_ifs_cx TYPE REF TO cx_swf_ifs_exception.
000510   **** container manager is expected to be active
000520       CONSTANTS l_expected_inst_manager_state TYPE xflag VALUE 'X'.
000530   **** is the container instance manager currently active ?
000540       TRY.
000550           CALL METHOD cl_swf_cnt_factory=>create_method_container
000560             EXPORTING
000570               im_objtype          = 'CL_SWF_CNT_FACTORY'
000580               im_catid            = 'CL'
000590               im_method           = 'CREATE'
000600             IMPORTING
000610               ex_method_container = l_abap_rh1.
000620         CATCH cx_swf_ifs_exception INTO l_non_expected_ifs_cx.
000630       ENDTRY.
>       cl_aunit_assert=>assert_not_bound( l_non_expected_ifs_cx ).
000650
000660       TRY.
000670           CALL METHOD cl_swf_cnt_factory=>query_create_buffer
000680             IMPORTING
000690               ex_inst_manager_state = l_inst_manager_state
000700               ex_num_requests       = l_num_requests
000710               ex_num_hits           = l_num_hits
000720               ex_num_misses         = l_num_misses
000730               ex_last_reset         = l_last_reset
000740               ex_num_cache_entries = l_cache_size.
000750         CATCH cx_swf_ifs_exception INTO l_non_expected_ifs_cx.
000760       ENDTRY.
000770       cl_aunit_assert=>assert_not_bound( l_non_expected_ifs_cx ).
000780
000790   **** check status of instance manager
000800       cl_aunit_assert=>assert_equals( act = l_inst_manager_state
000810                                        exp = l_expected_inst_manager_state
000820                                  msg = 'METHOD' &             "#EC NOTEXT
000830      'test_instance_manager_state:' & 'check instance manager state' ).
Contents of system fields
SY field contents..................... SY field contents.....................
Active calls / events
No dump information available
Chosen variables
No dump information available
Application Calls
No dump information available
Application Information
No dump information available
Internal notes
The termination occurred in the function "cg_GetSdatPtr" of the SAP
Basis System, specifically in line 2918 of the module
"//bas/640_REL/src/krn/gen/cgen.c#6".
The internal operation just processed is " ".
The internal session was started at 20080221100749.
Active calls in SAP kernel
(LinStack+0x3e)[0x81ed7ce]
(CTrcStack2+0x59)[0x81ed439]
(CTrcStack+0x21)[0x81ed3d1]
(rabax_CStackSave__Fv+0x9f)[0x857ac4f]
(ab_rabax+0x400)[0x8571db0]
(cg_GetSdatPtr__FPc+0x7e)[0x87523de]
(cg_cbindex__FPc+0x18)[0x8752408]
(sc_scont_short+0x86)[0x874d996]
(rs_expan_abap+0x51cff)[0x886210f]
(sc_expan__FUi+0xcf)[0x872e23f]
(parse__FUiPi+0x479)[0x8726fc9]
(sc_check+0x1bd)[0x872573d]
(ProcessText__FUi+0x6a)[0x872556a]
(sc_check+0x15c)[0x87256dc]
(sc_inclu+0x6e2)[0x871f142]
(rs_oper_abap2129+0x8e)[0x894d79e]
(rs_expan_abap+0x8f618)[0x889fa28]
(sc_expan__FUi+0xcf)[0x872e23f]
(parse__FUiPi+0x479)[0x8726fc9]
(sc_check+0x1bd)[0x872573d]
(cg_generate+0x9df)[0x8757c2f]
(ab_gabap+0x9f)[0x850c85f]
(dy_gen+0x45c)[0x82473ac]
(ab_genprog__FPcPvUii+0x487)[0x850c187]
(newload__FPcP13TmpSubpoolDirUi+0x29e)[0x8355b2e]
(ab_LoadProg__FPcUi+0x152)[0x8355752]
(LoadGlobalClass__FPCcUiUiUi9ClasState+0xcd)[0x83a06dd]
(FillCfixInt__FPC4CREFP4CFIXUiUi9ClasState+0x19f)[0x83a1bff]
(ab_FillCfix__FUsUi+0x23c)[0x83a263c]
(ab_CrefToCladId_ActivateOK__FUsPUc+0x4c)[0x83a26fc]
(ab_jclcc__Fv+0x26)[0x84190c6]
(ab_extri__Fv+0x9c9)[0x831e9b9]
(ab_xevent__FPCc+0x20)[0x8457f10]
(ab_dstep+0x775)[0x8582d55]
(dynpmcal+0x89b)[0x823e83b]
(dynppbo0+0x2a8)[0x823bb88]
(dynprctl+0x62e)[0x823b5fe]
(dynpen00+0x2db0)[0x8239160]
(Thdynpen00+0x6f6)[0x80d1916]
(TskhLoop+0x3bdf)[0x80d0c6f]
(tskhstart+0x27b)[0x80c964b]
(DpMain+0x26c)[0x805af9c]
(main+0x16)[0x80595a6]
/lib/libc.so.6(__libc_start_main+0xbf)[0x41dbbbaf]
List of ABAP programs affected
No dump information available
List of internal tables
No dump information available
Directory of Application Tables
No dump information available
Directory of Application Tables (Administrative Information)
No dump information available
ABAP control blocks CONT
No dump information available
End of runtime analysis
Has anyone come across this and knows how to fix it?
Thanks
Matthias

Hi,
without service.sap.com access you can not download kernel patch.
any way what is you current kernel version.?
you can get this by login into sap system, system -> status -> other kernel info. (shift + F5)
regards,
kaushal

RDDGENOL job getting cancelled with huge number of ABAP dumps

Hi,
In our Production system, we had applied Kernel upto patch level 263 and while
applying SPAM 30 for release 640 it failed. We tried applying Basis patch 15 still
it did not went through.
Since then we are getting around 1500-2500 dumps daily. The job RDDGENOLis getting cancelled and the dumps RAISE_EXCEPTION and SYNTAX_ERROR is displayed in ST22. Today, there were around 2500 dumps in the system.
When I now run the Database <-> ABAP Dictionary consistency check in
DB02, I see number of errors for missing objects in the database. There
are around of dozens of Primary Indexes, secondary Indexes, Tables,
Views listed in the result:
Objects Missing in database No.
=========================== ===
Primary indexes 6
Secondary indexes 14
Tables 37
Views 26
When I try to create each of them using SE16 or using SQL utility on OS
level, it gives an SQL system error. We are also getting thousands of
dumps each day (attached alongwith this message). Also I see the CPF327E error
in the OS Level Joblog.
Also we cannot transport any requests. There is some problem with or
due to the conversions. Is it a problem with Kernel, ABAP dictionary or
database.
Following is the extract of the dumps due to DDIC in 000:
============================================================
Runtime Error          SYNTAX_ERROR
Date and Time
ShrtText
Syntax error in program "CL_WB_CROSSREFERENCE==========CP ".
What happened?
Error in ABAP application program.
The current ABAP program "SAPLSEWB" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
In program "CL_WB_CROSSREFERENCE==========CP ", the following syntax error
occurred
in the Include "CL_WB_CROSSREFERENCE==========CM00D " in line 8:
|    "The type "KEYWORD_TAB" is unknown."
============================================================
============================================================
Runtime Error          RAISE_EXCEPTION
Date and Time
ShrtText
Exception condition "DESTINATION_NOT_OPEN" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
A RAISE statement in the program "SAPLCRFC" raised the exception
condition "DESTINATION_NOT_OPEN".
Since the exception was not intercepted by a superior program
in the hierarchy, processing was terminated.
Short description of exception condition:
Specified destination is not open.
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
How to correct the error
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"RAISE_EXCEPTION" C
"SAPLCRFC" or "LCRFCU20"
"RFC_CONNECTION_CLOSE"
or
"SAPLCRFC" "DESTINATION_NOT_OPEN"
or
"RADBAT01 " "DESTINATION_NOT_OPEN"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "640"
Application server....... "TXTPDSAP"
Network address.......... "172.16.0.140"
Operating system......... "OS400"
Release.................. "5.3"
Hardware type............ "0065000655EC"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 35
Short dump setting....... "full"
Database server.......... "TXTPDSAP"
Database type............ "DB400"
Database name............ "TXT"
Database owner........... "R3TXTDATA"
Character set............ "en_US.ISO8859-1"
SAP kernel............... "640"
Created on............... "Dec 11 2008 23:06:45"
Created in............... "AIX 1 5 00538A4A4C00 (IBM iSeries with OS400)"
Database version......... "DB4_52"
Patch level.............. "263"
Patch text............... " "
Supported environment....
Database................. "V5R2, V5R3, V5R4, V6R1"
SAP database version..... "640"
Operating system......... "OS400 2 5, OS400 3 5, OS400 4 5, OS400 1 6"
Memory usage.............
Roll..................... 696832
EM....................... 16759712
Heap..................... 0
Page..................... 32768
MM Used.................. 1383120
MM Free.................. 3483600
SAP Release.............. "640"
User and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Program............. "SAPLCRFC"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "SAPLCRFC" in
"RFC_CONNECTION_CLOSE".
The main program was "RADBAT01 ".
The termination occurred in line 22 of the source code of the (Include)
program "LCRFCU20"
of the source code of program "LCRFCU20" (when calling the editor 220).
The program "SAPLCRFC" was started as a background job.
Job name........ "RDDGEN0L"
Job initiator... "DDIC"
|    Job number...... 00032101
============================================================
Kindly let me know the immediate fix. Thanks!
Regards,
Nick

Hi Nick,
I would say, you are having a slight missperception of this forum ... it should not replace your basis ressources in your company.
What you are doing is pretty complex (and the mixtrure of SPAM Update AND Basis SP seems to be wrong to me) and therefore, it will not be possible, to help you, just based on such a short dump.
Sorry,
Volker Gueldenpfennig, consolut international ag
http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

ME21n terminates with Abap dump

Dear user,
when i update the patch level for Logistics from SAPKH47027 to SAPKH47030. system is terminating with dump when i rub ME21N , ME22n, ME23N, and ME29N -transaction
Kindly suggest the solution ... thanks in advance..
Details of the dump are as below..
Runtime errors         SYNTAX_ERROR
       Occurred on     02.05.2011 at   19:24:43
Syntax error in program "SAPLMEPO ".
What happened?
The following syntax error occurred in the program SAPLMEPO :
"Different number of parameters in FORM and PERFORM (routine: MEPO_ITEM"
Error in ABAP application program.
The current ABAP program "SAPLMEGUI" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "SAPLMEPO ".
You can also perform the syntax check from the ABAP/4 Editor.
If the problem persists, proceed as follows:
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
The following syntax error was found in the program SAPLMEPO :
"Different number of parameters in FORM and PERFORM (routine: MEPO_ITEM"
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.

Hi,
As per my understanding check your print program and smartform,i hope its failing there.
Put a break point there and check.
Regards,
Prashant

ABAP Dump with using FM 'REUSE_ALV_GRID_DISPLAY'

Similar Messages

Maybe you are looking for