MESSAGE_TYPE_X Short dump in CAT2

Hi,
We are receiving a dump in CAT2 while maintaining 'long text'. The dump is at the following source code. Can someone help me understand what is causing this? I see that this is happening in the update mode. Message X030 reads "internal program error'.
Main program SAPLCATS (screen 2200)
In LCATSF4A
001020           IF <LONGTEXT> IS INITIAL.
001030             <LONGTEXT> = YX.
001040           ENDIF.
001050           IF UNEW_TEXT_WITHOUT_NUMBER = YX.
001060             IF <LONGTEXT> = '0'.
001070               INSERT INT_TEXT INDEX UCOUNT.
001080               IF SY-SUBRC NE 0.
001090                 MESSAGE X030.
001100               ENDIF.
001110             ELSE.
001120               INSERT INT_TEXT INDEX UCOUNT.
001130               IF SY-SUBRC NE 0.
001140                 MESSAGE X030.
001150               ENDIF.
001160             ENDIF.
001170             IF SY-SUBRC NE 0.
001180               MESSAGE X030.
001190             ENDIF.
001200           ENDIF.
001210           <LTXA1> = USHORT_TEXT.
001220         WHEN TFUNCTION-UPDATE.
001230           UMODIF = YX.
001240           IF <LONGTEXT> NE YX.
001250   * change due to behaviour of EDIT_TEXT: when an existing text is deleted
001260   * and created again with the same name, the FUNCTION is U and not I
001270   * this can only happen for texts that have been on the database, i.e
001280   * the counter exists, hence <LONGTEXT> = YX
001290             READ TABLE TEXT_DELETE WITH KEY NAME = TEXT_DELETE-NAME
001300                                             BINARY SEARCH.
001310             IF SY-SUBRC NE 0.
     >               MESSAGE X030.
001330             ELSE.
001340               <LONGTEXT> = YX.
001350             ENDIF.
001360           ENDIF.
001370           <LTXA1> = USHORT_TEXT.
001380       ENDCASE.
001390     ENDIF.
001400   ENDFORM.                               " LONGTEXT
Thanks in advance.

Hi,
if you have SAP rel. 4.6C you should take a look on SAP note (see also related notes)
Note 304418 - CATS: Short dump in CATS due to inconsistencies
For other releases you can have a look at the related notes of
Note 1246420 - Composite SAP Note : Cross Application Time Sheet Docum.
Also
Note 1128987 - Dump while entering long text in CAT2
might be an idea!
Regards,
Klaus
Edited by: Klaus Babl on Jun 24, 2011 6:51 AM

Similar Messages

Message_type_x short dump while deleting request from infocube

Hi,
While deleting one of the erroneous requests from some infocubes,
system is resulting in short dump "MESSAGE_TYPE_X".
This is happening only with respect to some infocubes.
Description of short dump:
Short text of error message:
System error in program RSMDATASTATE and form RSM_DATASTATE_CHECK-5- (see long text)
Can any one of you please help with this?
Regards,
Nilima Rodrigues

Hi NILIMA,
I got same problem with my InfoPackage last month with same error msg.
that error come due to data inconstancy in data base table.
in my case i am unable to open my InfoPackage and after double clicking it was giving dump with same error.
If u know abap then just change the sy-subrc value from 4 to 0 before dump line code it will resolve your problem.
for this on dump screen click on debugger button then it opens your code and shows line on which u getting dump with table name check your entry in table ok
if u unable u find table then do one thing just put break point before dump line and open fresh rsa1 and go to same cube and double click it will stop on your debugger point just press f5 button it shos sy-subrc 4 convert it to 0 and press edit button and press f8 .
Regards
Ankit

Infospoke short dumps with MESSAGE_TYPE_X

Whenever one of our many infospokes are invoked and there is no data to pull from BW, the process short dumps with MESSAGE_TYPE_X in module RSB_API_OHS_DEST_READ_DATA.
Is anyone else experiencing this problem?

Hi,
Please take a look in note 1370227.
I hope this note help you.
Thanks,
Rafael

Short dump MESSAGE_TYPE_X in displaying data from BPC Virtualcube

Hi Experts,
I am experiencing an error when try to display data from a BPC VirtualProvider Infocube (both from Workbench and with LISTCUBE transaction).
This kind of virtualcube is auto generated by BPC.
When I do some kind of selection I obtain this error: MESSAGE_TYPE_X
Short text of error message:
System error in program SAPLRRK0 and form CHECK_KHANDLE (see long text)
Technical information about the message:
Message class....... "BRAIN"
Number.............. 299
Variable 1.......... "SAPLRRK0"
Variable 2.......... "CHECK_KHANDLE"
I have another BPC vitualprovider and this doesnu2019t happen.
I would use this cube inside a multiprovider, that has a BI cube too, and get the data through a BEx query. But the query throws the error and stopped.
I know that there could be problems with BPC structures (i.e. changes in tech name when transporting it), but at the moment I donu2019t see other solution to compare BI to BPC data.
I went through other posts in sdn forum for this issue, but I am not able to get the exact solution,
please help
Thanks,
Marco
System version:
BW: 701 level 0007
BPC: 750 level 0005

Hi Lokesh,
I read the note you have indicated.
For the first note 1479393: I donu2019t have hierarchies and the error appears in a different program to what is indicated in the note. This is where terminated:
Termination occurred in the ABAP program "SAPLRRK0" - in "CHECK_KHANDLE".
The main program was "GP4LQ7N6RS4RUB6HA69UREYGPKB ".
In the source code you have the termination point in line 34
of the (Include) program "LRRK0F05".
Furthermore, there are no calculated measures nor members in the MDX statement, because I just try to display the data from the virtualcube.
For the second 1448691: yes, it could be a performance related problem. Indeed, when I apply stronger filters, the error doesnu2019t occur and I got the data. But the system is already patched to SAPKW70107.
So, do you have any other ideas?
Thanks,
Marco

SHORT DUMP WHILE EXECUTING DTP.

Hi Gurus,
I have got a short dump while executing DTP the Error is as Follows.
Runtime Error: MESSAGE_TYPE_X.
Reasons for Error: 1.The installation of the SAP GUI on the present server is faulty or obselete
2.There is a error in the application program
And i have sent the sreen shot of the Short Dump to BASIS TEAM and they have replied me that they have to install some patches and it will take some time.
But i have no much time and i have to someway or the other execute the DTP and load the data.
Is there any shortcuts for this i mean to say without the involvement of Basis team that i can do in th BI System
Regards
Amar.

Hi Amar,
If the problem is with with System itself, how can we all have a short cut in that case. You may give it another trial, but you have to wait for the patches to be applied. Ask your basis team to get it done ASAP.
Thanks..
Shambhu

Short Dump on BAPI_TRANSACTION_COMMIT with destination NONE

Hi All
I am using SAP-PM with Compatible Unit(CU) functionality in ECC6 environment.
After we release the CU design to Generate order we get SHORT DUMP.
Any help will be of great help.
I am pasting the details from the dump file here.
Please let me know.
Appretaite your help.
Thanks
Meghana
Runtime Errors         CALL_FUNCTION_REMOTE_ERROR
Date and Time          27.08.2007 18:01:10
Short text
"The current application triggered a termination with a short dump."
What happened?
Error in the ABAP Application Program
The current ABAP program "/***/SAPLCUORDER_N" had to be terminated because it
has
come across a statement that unfortunately cannot be executed.
The error occurred during an RFC call to another system.
In the target system, a short dump has been written as well.
More detailed information on the error cause can be found there.
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 error occurred when executing a REMOTE FUNCTION CALL.
It was logged under the name "MESSAGE_TYPE_X"
on the called page.
How to correct the error
Please refer to the notes described in the
short dump.
System environment
SAP-Release 700
Application server... "MB1ES1005"
Network address...... "10.191.97.206"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 3
Shortdump setting.... "full"
Database server... "MB1ES1005"
Database type..... "ORACLE"
Database name..... "EC6"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Jul 25 2007 00:57:05"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.1.0) "
Patch level. 121
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 8176
EM...... 14633136
Heap.... 0
Page.... 131072
MM Used. 5005432
MM Free. 1263944
User and Transaction
Client.............. 200
User................ 10086330
Language key........ "E"
Transaction......... "/***/DESIGN "
Transactions ID..... "409954DC5D77F1C58E2D0013725D3B3B"
Program............. "/***/SAPLCUORDER_N"
Screen.............. "/***/SAPLCUORDER_N 2000"
Screen line......... 34
Information on where terminated
Termination occurred in the ABAP program "/***/SAPLCUORDER_N" - in
"SAVE_DESIGN".
The main program was "/***/SAPLCUORDER_N ".
In the source code you have the termination point in line 594
of the (Include) program "/***/LCUORDER_NF07".
Source Code Extract
Line
SourceCde
564
ENDIF .
565
ENDLOOP .
566
IF l_ret-type = 'E' OR
567
l_ret-type = 'A' .
568
CLEAR: save_okcode .
569
570
Show Messages
571
CALL FUNCTION '/***/N_LOG_ADD_MSG'
572
EXPORTING
573
i_log_type = 'G'
574
TABLES
575
t_ret      = t_ret.
576
PERFORM log_order_create_show .
577
Show first Message
578
     MESSAGE ID l_ret-id TYPE l_ret-type NUMBER l_ret-number
579
     WITH
580
       l_ret-message_v1 l_ret-message_v2
581
       l_ret-message_v3 l_ret-message_v4.
582
CALL FUNCTION '/***/N_DESIGN_INIT' .
583
ELSE .
584
IF g_design_mode = con_mode_crea.
585
Need to update DMS documents with real design number
586
PERFORM document_prepare_002 USING con_desnum_tmp_1
587
lv_desnum.
588
ENDIF.
589
Commit design BAPI's
590
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' .
591
592
IF save_okcode = con_order.
593
Commit order BAPI's
>>>>>
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
595
DESTINATION 'NONE'.
596
597
call of fct. RFC_CONNECTION_CLOSE is important to get a new
598
initial roll area with initial internal tables next time
599
CALL FUNCTION 'RFC_CONNECTION_CLOSE'
600
EXPORTING
601
destination          = 'NONE'
602
EXCEPTIONS
603
destination_not_open = 1
604
OTHERS               = 2.
605
ENDIF.
606
607
IF lv_desnum IS INITIAL .
608
lv_desnum = /***/cudesign-desnum .
609
ENDIF .
610
SET PARAMETER ID '/***/DESNUM' FIELD lv_desnum .
611
    Changes saved
612
MESSAGE ID '/***/MSG' TYPE 'S' NUMBER '529' WITH lv_desnum .
613
ENDIF .
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
2000
SY-UCOMM
CU01
SY-TITLE
Change Design: 50000109
SY-MSGTY
X
SY-MSGID
00
SY-MSGNO
341
SY-MSGV1
MESSAGE_TYPE_X
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20070827
SY-UZEIT
180110
SY-XPROG
SAPMSSY1
SY-XFORM
XAB_READ
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
4 FORM         /***/SAPLCUORDER_N                  /***/LCUORDER_NF07                    594
SAVE_DESIGN
3 FORM         /***/SAPLCUORDER_N                  /***/LCUORDER_NF07                   2616
CHECK_AND_SAVE_F07
2 FORM         /***/SAPLCUORDER_N                  /***/LCUORDER_NF04                    311
USER_COMMAND_D2000
1 MODULE (PAI) /***/SAPLCUORDER_N                  /***/LCUORDER_NI05                     28
USER_COMMAND_2000
Chosen variables
Name
Val.
No.       4 Ty.          FORM
Name SAVE_DESIGN
%_DUMMY$$
2222
0000
0000
0000
CL_GUI_RESOURCES=>COL_TEXTAREA
31
1000
F000
G_DESIGN_MODE
R
5
2
0
0
CON_MODE_CREA
I
4
9
0
0
GT_NODE_CUI
Table[initial]
SY-REPID
/***/SAPLCUORDER_N
2454254544545445542222222222222222222222
F35DF310C35F2452FE0000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CON_DESNUM_TMP_1
TM00000001CY
543333333345
4D0000000139
000000000000
000000000000
LV_DESNUM
222222222222
000000000000
000000000000
000000000000
SAVE_OKCODE
CU01
4533222222222222222222222222222222222222222222222222222222222222222222
3501000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
CON_ORDER
CU01
4533222222222222222222222222222222222222222222222222222222222222222222
3501000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
SY-XPROG
SAPMSSY1
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CON_DELETE
LVMS
4545222222222222222222222222222222222222222222222222222222222222222222
C6D3000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
No.       3 Ty.          FORM
Name CHECK_AND_SAVE_F07
CL_GUI_ALV_GRID=>MC_MB_VIEW
&MB_VIEW
2445544522222222222222222222222222222222222222222222222222222222222222
6D2F695700000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
GT_OP
Table IT_303[2x1320]
PROGRAM=/***/SAPLCUORDER_NDATA=GT_OP
Table reference: 118
TABH+ 0(20) = 7039FC3C5824DB3C00000000760000002F010000
TABH+ 20(20) = 0200000028050000FFFFFFFF0400000030140000
TABH+ 40( 8) = 08000000C1308001
store        = 0x7039FC3C
ext1         = 0x5824DB3C
shmId        = 0     (0x00000000)
id           = 118   (0x76000000)
label        = 303   (0x2F010000)
fill         = 2     (0x02000000)
leng         = 1320 (0x28050000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000093
occu         = 8     (0x08000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x2010FC3C
pgHook       = 0x00000000
idxPtr       = 0x00000000
shmTabhSet   = 0x00000000
id           = 234   (0xEA000000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 8     (0x08000000)
lineAlloc    = 8     (0x08000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x60B7153D
collHook     = 0x00000000
ext2         = 0x1024DB3C
>>>>> 2nd level extension part <<<<<
tabhBack     = 0xE00FFC3C
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x00000000
pb_handle    = 0x00000000
G_BADI_PROGRAM
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LOG_ERROR
2
0
0
0
CON_BUTT_DELETED
@11QDelete@
43355466676422222222222222222222222222222222
011C145C545000000000000000000000000000000000
00000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000
G_CU_EXIT_CU_EXPLODE
F0000000
F0000000
/***/CUDESIGN-OBJNR
CY00000000000000008835
4533333333333333333333
3900000000000000008835
0000000000000000000000
0000000000000000000000
CL_GUI_RESOURCES=>COL_TEXTAREA
31
1000
F000
G_SEC_COUNT
0
0000
0000
LV_UPD
X
5
8
0
0
%_SPACE
2
0
0
0
GS_ROW_NO
0.0.0.1.
0000
1000
0000
0000
SCREEN
/***/CUDESIGN-GLTRP
2454245445444244555222222222222222222222222222222222222222222222222222222222222222222222222222
F35DF3545397ED7C420000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-MSGID
00
33222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
SWO_%CONTAINER
000000000
2222222222222222222222222222222233333333322222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SPACE
2
0
0
0
SY-MSGNO
341
333
341
000
000
/***/CVCUI-CUTYP
2
0
0
0
SY-MSGV1
MESSAGE_TYPE_X
44554445555455222222222222222222222222222222222222
D533175F4905F8000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV3
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
No.       2 Ty.          FORM
Name USER_COMMAND_D2000
/***/CVCUI
0.0.0.0.0.0.0.1.                                                                         000000
2220000000022222222222222222222222222222222222222222222222222222222222222222222222223333332222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
/***/SAPLCUORDER_N
2454254544545445542222222222222222222222
F35DF310C35F2452FE0000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CON_MODE_COPY
C
4
3
0
0
LT_BAPI_RETURN
Table IT_1778[2x1088]
PROGRAM=/***/SAPLCUORDER_NFORM=USER_COMMAND_D2000DATA=LT_BAPI_RETURN
Table reference: 310
TABH+ 0(20) = 8837083D407E1C3D0000000036010000F2060000
TABH+ 20(20) = 0200000040040000FFFFFFFF04000000F0170000
TABH+ 40( 8) = 08000000C1308101
store        = 0x8837083D
ext1         = 0x407E1C3D
shmId        = 0     (0x00000000)
id           = 310   (0x36010000)
label        = 1778 (0xF2060000)
fill         = 2     (0x02000000)
leng         = 1088 (0x40040000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000113
occu         = 8     (0x08000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
groupCntl    = 0
rfc          = 1
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x50C6073D
pgHook       = 0x00000000
idxPtr       = 0x00000000
shmTabhSet   = 0x00000000
id           = 1534 (0xFE050000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 8     (0x08000000)
lineAlloc    = 8     (0x08000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x00000000
collHook     = 0x00000000
ext2         = 0x6067033D
>>>>> 2nd level extension part <<<<<
tabhBack     = 0xE82F063D
delta_head   = 0000000000000000CF000000000000000400000020180000000000004D00430055004F000000000
pb_func      = 0x00000000
pb_handle    = 0x00000000
CON_MODE_ORDE
O
4
F
0
0
TGSBT
22222222222222222222222222222222222222
00000000000000000000000000000000000000
00000000000000000000000000000000000000
00000000000000000000000000000000000000
CL_GUI_RESOURCES=>COL_TEXTAREA
31
1000
F000
LS_NUMBERS-AUFNR_NEW
000001000677
333333333333
000001000677
000000000000
000000000000
T024I
200UT10100PG for Term & Comp
33355333335426672567622246672222222222222222
20054101000706F20452D0603FD00000000000000000
00000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000
LS_T399X
200UT10UM01                  X    INST 30UT01UT01
3335533543322222222222222222252222445522335533553322222222222222222222222222222222222222222222
20054105D01000000000000000000800009E3400305401540100000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
CON_VBKZ_U
U
5
5
0
0
/***/CU_ORDER_IO-DISP_FACTOR
2097152
0
0
LS_DESIGN
200########000050000109DDCY00000000000000008835PROFILE1 0001UT10UM0100220100MWH001
333D5FC807333333333333344453333333333333333333355444443223333553354333333333345433322222222222
200CDB1E02B00005000010944390000000000000000883502F69C5100000154105D0100220100D7800100000000000
000599F215300000000000000000000000000000000000000000000000000000000000000000000000000000000000
0004C91D3DB00000000000000000000000000000000000000000000000000000000000000000000000000000000000
/***/CUDESIGN
200########000050000109DDCY00000000000000008835PROFILE1 0001UT10UM0100220100MWH001
333D5FC807333333333333344453333333333333333333355444443223333553354333333333345433322222222222
200CDB1E02B00005000010944390000000000000000883502F69C5100000154105D0100220100D7800100000000000
000599F215300000000000000000000000000000000000000000000000000000000000000000000000000000000000
0004C91D3DB00000000000000000000000000000000000000000000000000000000000000000000000000000000000
G_DROP_COUNT
0
0000
0000
LS_DESIGN-DESNUM
000050000109
333333333333
000050000109
000000000000
000000000000
No.       1 Ty.          MODULE (PAI)
Name USER_COMMAND_2000
GT_SELTAB_INIT
Table[initial]
Internal notes
The termination was triggered in function "RfcExtendedReceive"
of the SAP kernel, in line 422 of the module
"//bas/700_REL/src/krn/rfc/abrfcrcv.c#4".
The internal operation just processed is "FUNC".
Internal mode was started at 20070827180011.
Status of connection:
RFC state: " "
RFC error text: "RFC_ERROR_SYSTEM_FAILURE"
CPI-C error text: "The current application triggered a termination with a short
dump."
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App       : disp+work.EXE (pid=26488)
When      : 8/27/2007 18:1:10.942
Threads   : 2
Computer Name       : MB1ES1005
User Name           : ec6adm
Number of Processors: 2
Processor Type: x86 Family 15 Model 4 Stepping 10
Windows Version     : 5.2 Current Build: 3790
State Dump for Thread Id 5e10
eax=000f93c0 ebx=0000042c ecx=00003118 edx=00000000 esi=0000042c edi=00000000
eip=7c82ed54 esp=056d71f0 ebp=056d7260 iopl=0         nv up ei ng nz ac po cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000             efl=00200297
function : KiFastSystemCallRet
7c82ed54 c3               ret
7c82ed55 8da42400000000   lea     esp,[esp]              ss:056d71f0=7c822124
7c82ed5c 8d642400         lea     esp,[esp]              ss:62bd5803=00000000
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
056d7260 77e6ba42 0000042c 0001d4c0 00000000 056d7298 ntdll!KiFastSystemCallRet
056d7274 0109504d 0000042c 0001d4c0 00000001 7c38b5c8 kernel32!WaitForSingleObject
056d7298 00582118 00582151 7c38b5c8 7c38b5c8 7c38b5c8 disp+work!NTDebugProcess (ntstcdbg.c (501))
056d729c 00582151 7c38b5c8 7c38b5c8 7c38b5c8 01e9b1b8 disp+work!NTStack (dptstack.c (1367))
056d72b8 00582185 7c38b5c8 00000000 008b7ec8 7c38b5c8 disp+work!CTrcStack2 (dptstack.c (352))
056d72c4 008b7ec8 7c38b5c8 00000000 005f0059 00330030 disp+work!CTrcStack (dptstack.c (182))
056d72e8 008bb39f 00711076 056d8018 056d7be8 00200020 disp+work!rabax_CStackSave [abrabax.c (7063)
056d7b90 009eca8b 020b9e4c 020b9e14 000001a6 5d88acf0 disp+work!ab_rabax (abrabax.c (1243))
056d7bcc 009ed19e 00000003 00711076 00000020 00000000 disp+work!rcv_message (abrfcrcv.c (422))
056d8068 009ed29d 00000003 00000000 00710c47 056d80c0 disp+work!RfcExtendedReceive [abrfcrcv.c (14
056d808c 00714873 00000003 00710c47 056d80c0 00711076 disp+work!ab_rfcreceive (abrfcrcv.c (59))
056d80e4 0071886b 2694a7c8 2694a7cc 2694a7cc 2694a7cc disp+work!jfunc_get (abfunc.c (5103))
056d89f4 007191d0 00000003 000000b4 00000000 05e8b7c0 disp+work!jfunc_nonstandard [abfunc.c (1655)
056dcfb0 006e3e2d 00000003 3ced8f90 00000000 056dd018 disp+work!ab_jfunc (abfunc.c (554))
056dd018 0081cb5e 00000000 3ced8f90 056dd164 3cedb514 disp+work!ab_extri (abextri.c (552))
056dd02c 00897dbd 00000000 3cedae46 005bf4cd 3ceda13c disp+work!ab_xevent (abrunt1.c (281))
056dd038 005bf4cd 3ceda13c 000000ea 3cedae46 00000000 disp+work!ab_dstep (abdynpro.c (492))
056dd164 005c25be 3ced8f90 3ced8f90 056dfc78 00000000 disp+work!dynpmcal (dymainstp.c (2398))
056dd178 005c1def 00000001 3ced8f90 00000003 056dfc78 disp+work!dynppai0 (dymainstp.c (1004))
056dd194 00595e69 3ced8f90 00000001 00000001 00000001 disp+work!dynprctl (dymainstp.c (360))
056dfcec 00490e06 00000004 0049d15f 00000004 01dadd00 disp+work!dynpen00 (dymain.c (1628))
056dfcf4 0049d15f 00000004 01dadd00 00000003 00000002 disp+work!Thdynpen00 (thxxhead.c (4773))
056dfee0 0049d6d6 00000001 00000000 00000000 00430000 disp+work!TskhLoop (thxxhead.c (4455))
056dff00 00421c36 00000000 00000000 7ffde000 056dff60 disp+work!ThStart (thxxhead.c (1173))
056dff14 00401080 00000003 05876980 00000001 00000000 disp+work!DpMain (dpxxdisp.c (1121))
056dff60 01242970 00000003 05876980 05877a10 01cce000 disp+work!nlsui_main (thxxanf.c (82))
056dffc0 77e523e5 00000000 00000000 7ffde000 8967f020 disp+work!wmainCRTStartup (crtexe.c (395))
056dfff0 00000000 0124282d 00000000 00905a4d 00000003 kernel32!IsProcessorFeaturePresent
State Dump for Thread Id 61fc
eax=00000000 ebx=00000103 ecx=0587a700 edx=02714360 esi=00000000 edi=00000000
eip=7c82ed54 esp=0799fec0 ebp=0799ff04 iopl=0         nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000             efl=00000246
function : KiFastSystemCallRet
7c82ed54 c3               ret
7c82ed55 8da42400000000   lea     esp,[esp]              ss:0799fec0=7c821514
7c82ed5c 8d642400         lea     esp,[esp]              ss:64e9e4d3=00000000
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0799ff04 0119030a 000006e0 00000000 00000000 0587a798 ntdll!KiFastSystemCallRet
0799ff84 7c349565 00000000 00000000 00000000 0587a700 disp+work!SigIMsgFunc (signt.c (610))
0799ffb8 77e6608b 0587a700 00000000 00000000 0587a700 MSVCR71!endthreadex
0799ffec 00000000 7c3494f6 0587a700 00000000 00000000 kernel32!GetModuleFileNameA
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
/***/SAPLCUORDER_N
0
10.08.2007
10:12:44
541696
E
1
Typ
/***/CUDESIGN
0
10.08.2007
10:05:19
7168
2
Typ
/***/CU_ORDER_IO
0
10.08.2007
09:53:38
4096
3
Typ
/***/DESTYPE
0
10.08.2007
10:05:21
2048
4
Typ
/***/PRF_ORD
0
10.08.2007
10:05:21
4096
5
Prg
SAPMSSYD
0
04.04.2007
10:28:36
21504
E
6
Prg
SAPFSYSCALLS
0
09.09.2004
14:18:32
8192
E
7
Typ
/***/G_CUST
0
10.08.2007
09:53:39
3072
8
Prg
/***/SAPLTABLES
8
10.08.2007
10:13:00
19456
E
9
Typ
/***/G_CHAR
0
10.08.2007
10:05:21
3072
10
Prg
SAPLCTCE
10
09.09.2004
14:18:34
9216
E
11
Typ
CABN
0
18.09.2001
10:02:26
12288
12
Prg
SAPLICON
12
04.04.2007
10:10:28
27648
E
13
Prg
%_CICON
12
07.02.2006
10:40:00
104448
E
14
Typ
ICONT
0
04.04.2007
10:10:08
2048
15
Typ
NRIV
0
02.04.1998
08:14:54
3072
16
Prg
SAPLBSVA
16
04.04.2007
14:47:00
296960
E
17
Typ
/***/CU_ORDER_S_OP_N
0
10.08.2007
09:53:39
14336
18
Prg
CL_GUI_CONTROL================CP
18
28.02.2005
21:03:09
112640
E
19
Prg
%_CCNTL
18
18.02.2005
14:15:08
15360
E
20
Typ
OBJ_RECORD
0
14.02.1998
08:30:43
2048
21
Prg
CL_GUI_OBJECT=================CP
21
05.07.2005
13:10:15
375808
E
22
Prg
CL_GUI_CFW====================CP
22
28.02.2005
21:03:09
172032
E
23
Prg
CL_GUI_PROPS_CONSUMER=========CP
23
18.02.2005
14:15:08
30720
E
24
Prg
SAPLTHFB
24
04.04.2007
13:24:38
390144
E
25
Typ
EUDB
0
06.11.2003
20:28:08
8192
26
Prg
SAPLSFES
26
08.08.2007
16:46:17
259072
E
27
Prg
SAPLSPLUGIN
27
09.09.2004
14:18:36
8192
E
28
Prg
SAPLSTTM

Yes even i find it strange. But there is no syntax error and the fact is that it was working 2 days back. Suddenly it has started giving us this dump.
The code is as follows.
Commit design BAPI's
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' .
      IF save_okcode = con_order.
Commit order BAPI's
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          DESTINATION 'NONE'.
Here con_order is CU01.
Please let me know if anybody has faced this problem earlier.
Thanks in Advance
Meghana

Display Data Flow - Short Dump

Hi all,
When i select display data flow of any cube...it is going for a short dump.
I have searched for the answer in previous Forum questions. I could find only for previous BW versions but not for for BI7.
Could you please let me know the solution for this issue.
Thanks & Regards,
Eswari

Hi All,
Thank you very much for all of your responces.....
I am working on Support Package 10.
Here is the detailed description of the short dump.
Short text
    The current application triggered a termination with a short dump.
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).
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
    Short text of error message:
    GP: Control Framework returned an error; contact system administrator
    Long text of error message:
     Diagnosis
         The Graphical Framework is based on the basis technology known as
         the Control Framework. A method in the Control Framework returned
         an error.
     Procedure
         It probably involves a programming error. You should contact your
         system administrator.
     Procedure for System Administration
         Check the programming of the graphics proxy especially for the
         parameters that were sent and, if necessary, correct your program.
    Technical information about the message:
    Message class....... "APPLG"
    Number.............. 229
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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:
    "MESSAGE_TYPE_X" " "
    "CL_AWB_OBJECT_NET_SAPGUI======CP" or "CL_AWB_OBJECT_NET_SAPGUI======CM005"
    "PBO"
    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
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
   4. Details about the conditions under which the error occurred or which
   actions and input led to the error.
Thanks,
Eswari.

Short dump when exporting to Excel

After installing SAP Gui 7.20, I get a short dump (Message_Type_x) whenever exporting a report to Excel (XXL).
SAP Gui 7.20
Patch level 5
Windows 7
Office 2010
has anybody run into this issue or know how to resolve it? Thank you.

Hy,
I've the same problem, have you resolve it?
By,
Ale.

Short Dump generating reports of EWA

Hi Experts,
I get the short dump MESSAGE_TYPE_X when I tried to see the Ewa report?
Any Idea?
Thanks in advance.

Hi,
Mi ST 400 level is 17.
Here is mi dump:
Err.tmpo.ejec.         MESSAGE_TYPE_X
Fecha y hora           10.08.2009 09:37:50
Texto breve
The current application triggered a termination with a short dump.
¿Qué ha sucedido?
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).
Anál.errores
Short text of error message:
    La creación de evento para la sesión EA0000000000881 ha fallado
Long text of error message:
     Diagnóstico
La creación de un evento ha fallado.
     Actividades en el sistema
         La transacción actual se cancela.
     Procedimiento
Procedimiento para la gestión del sistema
         El problema puede estar en el rango de números DSVASEVENT.
         Verifique si el intervalo "01" está creado y si tiene números
         libres. Notifique los resultados de esta exploración a SAP.
Technical information about the message:
    Message class....... "DSVAS"
    Number.............. 093
    Variable 1.......... "EA0000000000881"
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
Posición desencadenante de error tiempo ejecución
    Programa                                SAPLDSVAS_RPGEN
    Include                                 LDSVAS_RPGENU03
    Línea                                   672
    Tp.módulo                               (FUNCTION)
    Nombre módulo                           DSVAS_RPGEN_REPORT_GET_DATA
Detalle código fuente
Lín.      Txt.fte.
642        lf_chapno_old = 0.
643      * Fehlende Kapitelnummern verdichten
644        LOOP AT report_structure.
645          AT NEW chapter.
646            IF lf_chapno_old <> report_structure-chapter.
647              lf_chapno_old = report_structure-chapter.
648              ADD 1 TO lf_chapno.
649            ENDIF.
650          ENDAT.
651          report_structure-chapter = lf_chapno.
652          MODIFY report_structure.
653        ENDLOOP.
654
655
656      * Ereignis "Reportgeneriert" vermerken
657        DATA: ls_dsvassessinstid TYPE dsvassessinstid,
658              lf_event_parameter TYPE dsvasevent-event_parameter.
659      * AH 'SL' wird durch Aufrufer erst spaeter ausgeloest
660        if lf_iCount = 0 or sy-batch is initial.
661          ls_dsvassessinstid-sessitype = sessitype.
662        ls_dsvassessinstid-sessno    = sessno.
663        lf_event_parameter           = ls_dsvassessinstid.
664        CALL FUNCTION 'DSVAS_EVENT_RAISE'
665             EXPORTING
666                  pf_event_type      = 'SL'
667                  pf_event_parameter = lf_event_parameter
668             EXCEPTIONS
669                  failed             = 1
670                  OTHERS             = 2.
671        IF sy-subrc <> 0.
>>>>>          MESSAGE x093(dsvas) WITH ls_dsvassessinstid.
673      *     Ereigniserzeugung für Sitzung &1 fehlgeschlagen
674          ENDIF.
675        endif.
676      * AH
677
678        CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
679             EXPORTING
680                  TEXT = space.
681      ENDFUNCTION.
Thanks in advance!

Short dump while doing subtotal in the ALV report

Hi All,
I am getting run time error while doing the sub total and total in the ALV .
error is "MESSAGE_TYPE_X" and
discription is "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)."
Can anyone help me regarding this.
My alv field catog is like below
DATA: ls_fieldcat TYPE slis_fieldcat_alv,
        ls_sort     TYPE SLIS_SORTINFO_ALV.
CLEAR:ls_fieldcat,
        ls_sort.
REFRESH ot_fieldcat.
ls_fieldcat-FIELDNAME   = 'LEASE_NUMBER'.
ls_fieldcat-SELTEXT_M   = 'Lease Number'(001).
ls_fieldcat-COL_POS     = 0.
ls_fieldcat-OUTPUTLEN   = 10.
ls_fieldcat-DO_SUM      = 'X'.
ls_fieldcat-KEY         = 'X'.
APPEND ls_fieldcat TO ot_fieldcat.
CLEAR ls_fieldcat.
ls_fieldcat-FIELDNAME   = 'LEASE_TYPE'.
ls_fieldcat-SELTEXT_M   = 'Lease Type'(002).
ls_fieldcat-COL_POS     = 1.
ls_fieldcat-OUTPUTLEN   = 5.
APPEND ls_fieldcat TO ot_fieldcat.
CLEAR ls_fieldcat.
ls_fieldcat-FIELDNAME   = 'LEGACY_NUM'.
ls_fieldcat-SELTEXT_M   = 'Legacy Contract No'(003).
ls_fieldcat-COL_POS     = 2.
ls_fieldcat-OUTPUTLEN   = 10.
APPEND ls_fieldcat TO ot_fieldcat.
CLEAR ls_fieldcat.
ls_fieldcat-FIELDNAME   = 'CUSTOMER'.
ls_fieldcat-SELTEXT_M   = 'Customer'(004).
ls_fieldcat-COL_POS     = 3.
APPEND ls_fieldcat TO ot_fieldcat.
CLEAR ls_fieldcat.
ls_fieldcat-FIELDNAME   = 'STATUS'.
ls_fieldcat-SELTEXT_M   = 'Status'(017).
ls_fieldcat-COL_POS     = 16.
ls_fieldcat-OUTPUTLEN   = 10.
APPEND ls_fieldcat TO ot_fieldcat.
CLEAR ls_fieldcat.
ls_fieldcat-FIELDNAME   = 'GATEIN_DT'.
ls_fieldcat-SELTEXT_M   = 'Gate In Date'(018).
ls_fieldcat-COL_POS     = 17.
ls_fieldcat-OUTPUTLEN   = 10.
APPEND ls_fieldcat TO ot_fieldcat.
CLEAR ls_fieldcat.
ls_fieldcat-FIELDNAME   = 'SVALUE'.
ls_fieldcat-COL_POS     = 18.
ls_fieldcat-DO_SUM      = 'X'.
ls_fieldcat-OUTPUTLEN   = 12.
APPEND ls_fieldcat TO ot_fieldcat.
CLEAR ls_fieldcat.
DATA SORTING AND SUBTOTAL
CLEAR ls_sort.
ls_sort-FIELDNAME = 'LEASE_NUMBER'.
ls_sort-SPOS      = 0.
ls_sort-UP        = 'X'.
ls_sort-SUBTOT    = 'X'.
APPEND ls_sort TO GT_SORT.
If i coment the code relate dto 'SVALUE' i am getting output without sub total and total.
if i uncomment the same then I am getting short dump.

Hi,
Try this coding,
TYPE-POOLS: SLIS.                      " ALV GLOBAL TYPES
*      FORM F_READ_DATA
FORM F_READ_DATA.
SELECT * INTO CORRESPONDING FIELDS OF TABLE GT_VBAK
           FROM VBAK
             UP TO P_MAX ROWS
          WHERE KUNNR IN S_KUNNR
            AND VBELN IN S_VBELN
            AND VKORG IN S_VKORG.
ENDFORM.                               " F_READ_DATA
*      FORM F_DISPLAY_DATA
FORM F_DISPLAY_DATA.
DEFINE M_FIELDCAT.
    ADD 1 TO LS_FIELDCAT-COL_POS.
    LS_FIELDCAT-FIELDNAME   = &1.
    LS_FIELDCAT-REF_TABNAME = 'VBAK'.
    LS_FIELDCAT-DO_SUM      = &2.
    LS_FIELDCAT-CFIELDNAME = &3.
    APPEND LS_FIELDCAT TO LT_FIELDCAT.
END-OF-DEFINITION.
DEFINE M_SORT.
    ADD 1 TO LS_SORT-SPOS.
    LS_SORT-FIELDNAME = &1.
    LS_SORT-UP        = 'X'.
    LS_SORT-SUBTOT    = &2.
    APPEND LS_SORT TO LT_SORT.
END-OF-DEFINITION.
DATA:
    LS_FIELDCAT TYPE SLIS_FIELDCAT_ALV,
    LT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
    LT_SORT     TYPE SLIS_T_SORTINFO_ALV,
    LS_SORT     TYPE SLIS_SORTINFO_ALV,
    LS_LAYOUT   TYPE SLIS_LAYOUT_ALV.
M_FIELDCAT 'VKORG' '' ''.
M_FIELDCAT 'KUNNR' '' ''.
M_FIELDCAT 'VBELN' '' ''.
M_FIELDCAT 'NETWR' 'X' 'WAERK'.
M_FIELDCAT 'WAERK' '' ''.
M_SORT 'VKORG' 'X'.                  " SORT BY VKORG AND SUBTOTAL
M_SORT 'KUNNR' 'X'.                  " SORT BY KUNNR AND SUBTOTAL
M_SORT 'VBELN' ''.                   " SORT BY VBELN
LS_LAYOUT-CELL_MERGE = 'X'.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
            IS_LAYOUT   = LS_LAYOUT
            IT_FIELDCAT = LT_FIELDCAT
            IT_SORT     = LT_SORT
       TABLES
            T_OUTTAB    = GT_VBAK.
ENDFORM.                               " F_DISPLAY_DATA
Regards,
Nikhil.

Short dump in standard program

Hi Friends,
below description is short dump for standard program.
Please see the below and help me how to correct the program.
The current application triggered a termination with a short dump.
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:
Internal error: Program   , include   , form   .
Technical information about the message:
Diagnosis
     An unexpected error has occurred.
Procedure
     If you can reproduce the error, contact the SAP Hotline quoting the
     error number.
Message classe...... "GR"
Number.............. 214
How to correct the error
Probably the only way to eliminate the error is to correct the program.
                                                                                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:
"MESSAGE_TYPE_X" C
"SAPFGRWE" or "FGRWEF80_F80_FILL_COL_TAB"
"F80_FILL_COL_TAB"
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.
Thanks & Regards,
Sree
Edited by: adepus on Oct 7, 2009 12:39 PM
Edited by: adepus on Oct 7, 2009 12:39 PM

Hi Clemens,
I am getting a dump error as shown below. Could you please find some resolution for this issue. we just made some changes to the transaction GS02(Just added a GL account to one of the sets).
Runtime Error MESSAGE_TYPE_X
ShrtText
The current application triggered a termination with a short dump.
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).
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
Short text of error message:
Internal error: Program , include , form .
Technical information about the message:
Diagnosis
An unexpected error has occurred.
Procedure
If you can reproduce the error, contact the SAP Hotline quoting the
error number.
Message classe...... "GR"
Number.............. 214
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
to correct the error
Probably the only way to eliminate the error is to correct the program.
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:
"MESSAGE_TYPE_X" C
"SAPFGRWE" or "FGRWEF80_F80_FILL_COL_TAB"
"F80_FILL_COL_TAB"
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.
Source Code
79 MESSAGE x214.
80 ENDIF.
81 PERFORM e08_read_object_index(sapfgsb0)
82 USING fcolumns-dim_index.
83 IF c-subrc 0. MESSAGE x214. ENDIF.
84 c_dsentry = c-tval-from.
85 IF c_dsentry '='.
86 READ TABLE data_fields BINARY SEARCH
87 WITH KEY tab = rep_table
88 dsentry = c_dsentry.
>>>> IF sy-subrc 0. MESSAGE x214. ENDIF.
90 ENDIF.
91 WHEN OTHERS.
92 c_dsentry = '*'.
93 ENDCASE.
94 ENDIF.
Regards,
Pavan

Getting short dumps while reading bulky data from excel sheet

Hi all,
We have converted our non-unicode based sap system (R/3 4.7, Windows 2003,
SQL 2000) into a unicode based system recently. We are facing two peculiar
problems for last few days.
*Problem 1 - *Whenever we want to upload the data from excel sheet, the
system throws a dump after reading about 400 entries, while last week the
same system used to read about 8000 entries in a single go.
*Problem 2 - *Also, whenever we realease a transport requst from development
containing a lot of changes, the request will reach the quality system but
without the changes. but if i ll try to import the changes into quality
system after generating more than one request containing small small
changes, they get reflected in QAS immediately. Is there any size
constraint in transporting a request fro DEV->QAS->PRD.
Please suggest some ways.
I am pasting the dump (that I am getting while data uploading from Excel).
~~~~~~~~~~~~~~~~~~
Runtime errors
MESSAGE_TYPE_X*
Occurred on
22.02.2008 at
13:21:02*
The current application triggered a termination with a short dump.
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).
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.
Error analysis
Short text of error message:
Control Framework : Error processing control
Technical information about the message:
Diagnosis
An error occurred when the system tried to process the commands
from the Automation Queue on the presentation server.
There are several possible reasons for this:
- The installation of the SAP GUI on the presentation server is
faulty or obsolete.
- There is an error in the application program
- There is an error in the SAPGUI or an integrated control
Procedure
1. Make sure that you have imported the appropriate Support
Package, the current kernel, and GUI patch for the release of your
System
2. Check whether the error occurs locally on one or a few PCs, or
generally on all PCs. Note whether the error only occurs for some
users, for example because of a specific Customizing setting.
If it only occurs locally, this suggests an installation problem
with the PC. Check the installation; if necessary, reinstall the
software. In the dump, search for the SY-MSGLI field, since it may
point to the cause of the error.
3. Activate the Automation Trace (in accordance with SAP Note
158985).
4.Start the transaction and continue until the screen immediately
before the dump.
5. From the System -> Utilities menu, choose Autom. Queue,
Synchronous Processing.
The status bar of the GUI displays the text:
"Automation synchron flush mode on"
6. If you now proceed with the application, the short dump will
display the ABAP call that caused the error; the Automation Trace
will contain the error on the presentation server.
7. If necessary, load the short dump and trace files on to
sapservX, so that SAP can analyze them.
Message classe...... "CNDP"
Number.............. 006
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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:
"MESSAGE_TYPE_X" C
"SAPLOLEA" or "LOLEAU02"
"AC_SYSTEM_FLUSH"
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.
System environment
SAP Release.............. "620"
Application server....... "nhbho930"
Network address.......... "192.168.0.30"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 801586"
Character length......... 16 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "NHBHO930"
Database type............ "MSSQL"
Database name............ "DEV"
Database owner........... "dev"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Aug 17 2007 00:18:58"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "196"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
User, transaction...
Client.............. 300
User................ "NHBABAP"
Language key........ "E"
Transaction......... "SE38 "
Program............. "SAPLOLEA"
Screen.............. "SAPMSDYP 0010"
Screen line......... 0
Information on where terminated
The termination occurred in the ABAP program "SAPLOLEA" in
"AC_SYSTEM_FLUSH".
The main program was "ZBDC_CONTRACT ".
The termination occurred in line 29 of the source code of the (Include)
program "LOLEAU02"
of the source code of program "LOLEAU02" (when calling the editor 290).
~~~~~~~~~~~~~~~~~~~~~
Thank you all.
Cheers.
Mitra __.____._

for the 50 millionth time: Excel spreadsheets are NOT databases, you should NOT try to use them as such and NEVER access them using JDBC.
You should also under NO condition use the JDBC-ODBC bridge driver (that was actually the 78 millionth time that was told someone).

Report Painter GR214 generation error - Short dump 4.6C

While generating a report with more than twenty sections, the system short dumps with the error message GR214 pointing to "MESSAGE_TYPE_X"
"%_T01JR0 " or "########################################"
"INSERT_ROW_FORMULA_NEW"
Any leads to fix this?
The generation error happens only when I include a last line formula in the last section, Till then it is working fine.

Hi,
The error you are receiving could be caused by a large number of row blocks in your report definition, (you can check the report definition with report RGRRDC00). A report should not contain too many row and column blocks. It is not possible to give an upper bound for the number of row blocks (since the length of the coding depends on other parts of the report as well). However, even a complicated Report Writer or Report Painter report should not contain more than 50 row blocks, and reports with more than 100 row blocks should not be defined.
In this case the report(s) have to be redefined. Please also refer to the note 387916 for further information regarding this issue.
When there are more than 30 variables in a report, please have a look at the note 332091.
Please reduce the number of row blocks in the report by using the function 'Edit' -> 'Rows' -> 'Explode' in the Report Painter
definition. This function enables several rows to be created for one row block (in the Report Painter definition one row block is just one row). Report Painter (and Report Writer) are designed to display hierarchical reports where the rows in the few row blocks are built up using the 'Explode' function.
regards
Waman

Short Dump while including custom text

Hi Guru's
            I am new to workflow and i have a requirement to include a custom text by replacing the standard one.
            I selected the user decision and navigated to control tab there i got the task number, i just copied the task
           number by using the transaction pftc_cop and reassigned the custom task number.Now i can view the
           custom text in the preview but while doing the check it shows "1 warnings and 0 errors" and while
           activation it goes to short dump can you please resolve my issue as soon as possible.

Hi Suresh,
               I checked in SWU3. While performing automatic workflow customizing
               it shows an information message as "Customizing already carried out".
Below i had given the short dump description.Please have a look and make me clear
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).
How to correct the error.
    Probably the only way to eliminate the error is to correct the program.
    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:
    "MESSAGE_TYPE_X" " "
    "SAPLOLEA" or "LOLEAU02"
    "AC_SYSTEM_FLUSH"
    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
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
Regards,
Manoj

Short Dump while Complete deletion of data Contents from a Cube.

Hello Experts,
I am facing a runtime Short dump whenever i attempt to delete data from a Cube. Shown Below:-
Runtime Errors         MESSAGE_TYPE_X
Error analysis
    Short text of error message:
Data request to the OLTP
    Long text of error message:
    Technical information about t
    Message class....... "RSM"
    Number.............. 000
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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:
    "MESSAGE_TYPE_X" " "
    "SAPLRSM1" or "LRSM1U43"
    "RSSM_UPDATE_RSBKREQUEST"
Information on where terminated
    Termination occurred in the ABAP program "SAPLRSM1" - in
     "RSSM_UPDATE_RSBKREQUEST".
    The main program was "RSAWBN_START ".
    In the source code you have the termination point in line 117
    of the (Include) program "LRSM1U43".
Line SourceCde
   87   call function 'RSSTATMAN_GET_TYPE_FOR_DTA'
   88     exporting
   89       i_dta = l_dta
   90     importing
   91       e_type = l_dta_type
   92     exceptions
   93       error = 1
   94       others = 2.
   95   if sy-subrc <> 0.
   96     message id sy-msgid type sy-msgty number sy-msgno
   97             with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
   98   endif.
   99   call function 'RSSTATMAN_DELETE_STATUS'
100     exporting
101       i_dta      = l_dta
102       i_dta_type = l_dta_type
103       i_process = 'ALL'.
104
105   sort l_t_iccont by rnsidlast ascending.
106   loop at l_t_iccont.
107     data: l_s_reqdone like rsreqdone.
108     select single * from rsreqdone into l_s_reqdone where
109            rnr = l_t_iccont-rnr.
110     if sy-subrc <> 0.
111       read table l_h_dtpreq with key
112            requid = l_t_iccont-rnsidlast.
113       if sy-subrc = 0 and
114          ( l_h_dtpreq-ustate = '0' or l_h_dtpreq-tstate = '0' ).
115         clear l_s_reqdone-archived.
116       else.
>>>>>         message x000.
   118       endif.
119     endif.
120     if l_s_reqdone-archived <> rs_c_false.
121       call function 'RSREQARCH_RELOAD_REQUEST'
122         exporting
123           i_rnr         = l_t_iccont-rnr.
124     endif.
125     select single * from rsbkrequest into l_s_req where
126            requid = l_t_iccont-rnsidlast.
127     if sy-subrc <> 0.
128       continue.
129     endif.
130
131     read table l_h_rsbkdtp with table key
132          dtp = l_s_req-dtp.
133     if sy-subrc <> 0.
134       l_h_rsbkdtp-dtp = l_s_req-dtp.
135       insert table l_h_rsbkdtp.
136     endif.
This issue only exists in Production system not QTY or development thr Cube deletion is working fine.
So far I have tried Deleting Index's and then deleting the Cube Contents & Run Elementary Checks from RSRV but not find any lead yet.Also unable to find appropriate notes for this issue aswell I am using SAP_Bw comp 700 with SP26.
Any suggestion would be of great help .
Thanks & Regards
Aman

Hi Ap_SAP & Arvind,
Any recent upgrades or system refresh done?
In recent update just from SP24 to SP26 was updated and a DB stats Referesh was carried on.But this proublem existed before these activities.
Except deleting can you able to perform all other operations like loading data..etc?
Other than deletion I am able to do load data into cube extract from R3 and also i can delete data from PSA.Only deletion giving dump.
You are trying to delete transactional or master data.
I am tring for transaction data.
WHen I try to delete request by request it also lead to the same short dump.
@ arvind : I checked Sm12 there i see not table which has been locked.
Thanks
Aman

MESSAGE_TYPE_X Short dump in CAT2

Similar Messages

Maybe you are looking for