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

Similar Messages

SMQ1 - outbound queue with destination NONE

Dear all,
I did the setup for LIS application 13 two days back. I have scheduled the V3 job in LBWE but the job fails with ABAP Dump. I checked in SMQ1 and see that the destination in NONE for this datasource. Please help me.
Thanks and Regards
Adhira Anand

Hi Mti,
I did a init with data transfer and DSO is my first data target.
Please check the below ABAP dump.
What happened?
    The current application program detected a situation wh
    should not occur. Therefore, a termination with a short
    triggered on purpose by the key word MESSAGE (type X).
Error analysis
    Short text of error message:
    Structures have changed (sy-subrc=2)
    Long text of error message:
    Technical information about the message:
    Message class....... "MCEX"
    Number.............. 194
    Variable 1.......... 2
    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" " "
    "SAPLMCEX" or "LMCEXU22"
    "MCEX_UPDATE_18"
    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.
Information on where terminated
    Termination occurred in the ABAP program "SAPLMCEX" - in "MCEX_UPDATE_18".
    The main program was "RMCEXUP1 ".
    In the source code you have the termination point in line 156
    of the (Include) program "LMCEXU22".
    The program "SAPLMCEX" was started as a background job.
    Job Name....... "LIS-BW-VB_APPLICATION_18_635"
    Job Initiator.. "SDSDISP"
    Job Number..... 07003800
Thanks and Regards
Adhira Anand

Short dump using CS_BOM_EXPL_MAT_V2 with different user ids

Hi
We are getting a short dump in our program when using FM'CS_BOM_EXPL_MAT_V2' and this is happening only for super user roles but not with regular user ids in production. We are not able to identify the solution yet, and it needs to be resolved as quickly as possible. Anyhelp, really appreciated.
Thanks
Anil
Here is our code:
CALL FUNCTION 'CS_BOM_EXPL_MAT_V2'
    EXPORTING
      aumgb                 = 'X'
      capid                 = 'PP01'
      datuv                 = p_valfrm
      ehndl                 = '1'
      emeng                 = 1
      mbwls                 = ' '
      mehrs                 = 'X'
      mmory                 = '1'
      mtnrv                 = p_matnr
      stlal                 = p_stlal
      stlan                 = p_stlan
      werks                 = p_werks
    TABLES
      stb                   = i_stb
      matcat                = i_matcat
    EXCEPTIONS
      alt_not_found         = 1
      call_invalid          = 2
      material_not_found    = 3
      missing_authorization = 4
      no_bom_found          = 5
      no_plant_data         = 6
      no_suitable_bom_found = 7
      conversion_error      = 8
      OTHERS                = 9.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.

Hi senthil,
1. I suppose u want to explode the BOM.
2. CS_BOM_EXPLOSION
   use the above FM
   in the below mentioned fashion.
3.
CALL FUNCTION 'CS_BOM_EXPLOSION'
   EXPORTING
   capid                       = 'PP01'
   emeng                       = bmeng
   datuv                       = sy-datum
   mtnrv                       = matnr
   stlan                       = '1'
     werks                       = werks
     mehrs = 'X'
IMPORTING
TOPEQUI                     =
TOPMAT                      =
TOPTPL                      =
DSTST                       =
    TABLES
      stbd                        = stbd
      stbe                        = stbe
      stbk                        = stbk
      stbm                        = stbm
      stbp                        = stbp
      stbt                        = stbt
EXCEPTIONS
   alt_not_found               = 1
   call_invalid                = 2
   missing_authorization       = 3
   no_bom_found                = 4
   no_plant_data               = 5
   no_suitable_bom_found       = 6
   object_not_found            = 7
   conversion_error            = 8
   OTHERS                      = 9
regards,
amit m.

Short Dump in RDDEXECL with OBJECTS_OBJREF_NOT_ASSIGNED on import

Hello,
I am currently having problems importing a transport to our production environment as I get the above error on import. It successfully imported to the text environment though, both systems are BI 7 SP14.
The error analysis in the short dump is as follows:-
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "CHECK_ME" "(METHOD)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component (variable: "L_R_RULE").
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
The transport contains Transformations and DTP's which I think may be the cause of the problem, but since I have a large number of transports ready to import after this one, it is difficult to go back and retry the transport without certain objects.
I can find nothing relating to this on SAP notes.
Any advice would be much appreciated...
Regards,
Mark.

Hi Mark,
you should implement the note 1094978.
This note is a collection note with notes which correct most errors concerning Transformation.
This should solve the issue.
Regards,
Srikanth

Short dump in WF with DYNPRO_SEND_IN_BACKGROUND

Hi,
I am getting a short dump with the error DYNPRO_SEND_IN_BACKGROUND for the work flow id WF_BATCH in ST22 during a material creation process that we have. This is happening in the background processing for one of the steps and the WF hangs up. That step is never completed. Any ideas about what is going wrong?
Thanks,
Bala.

Have you tried to switch that special task to dialogue processing, make yourself an agent for this task, and than see, which dynpro is displayed.
That ought to be the easiest way, once you know what´s going wrong you can search for alternative processes.
Hth
Ute

Short dump creating variant with RS_CREATE_VARIANT

I'm getting the attached short dump while creating a variant with ABAP. The problem only occurs when the variants for both RPTIME00 and HDKCALC0 are created in the same program. I've tried adding a COMMIT between them to avoid any buffering problems, but to no avail. I've also tried searching SAP Notes for any hints.
So any input would be appreciated..
Regards,
Jan
Short text
    The length of COMMON PART "INFTY_TIME_EVAL" in program "RPTIME00" is incorrect.
Error analysis
    The structure of the COMMON PART "INFTY_TIME_EVAL" in program "RPTIME00" is
    different from the corresponding area in the calling program
    "HDKCALC0".
Length of the COMMON PART in program RPTIME00: 11784 bytes.
    Length of the COMMON PART in program HDKCALC0: 10752 bytes.
There is probably an error in the program
    "SAPLSLDB".
Edited by: Jan Petersen on Sep 18, 2009 1:17 PM
Edited by: Rob Burbank on Sep 18, 2009 9:16 AM

Hi,
Try to use the below way.
    REPORT ZTEST_PROGRAM.
DATA:
       G_REPORT      LIKE RSVAR-REPORT VALUE SY-REPID,
       G_VARIANT     LIKE RSVAR-VARIANT VALUE 'TEST_VAR1',
       G_VARI_DESC   LIKE VARID.
DATA:
       IT_RSPARAMS   TYPE STANDARD TABLE OF RSPARAMS,
       WA_RSPARAMS   LIKE LINE OF IT_RSPARAMS,
       IT_VARI_TEXT TYPE STANDARD TABLE OF VARIT,
       WA_VARI_TEXT LIKE LINE OF IT_VARI_TEXT.
PARAMETERS :P_NAME   TYPE CHAR15.
AT SELECTION-SCREEN.
    IF SY-UCOMM = 'ONLI'."Variant is created when you press EXECUTE button on selection-screen.
      WA_VARI_TEXT-LANGU     = 'EN'.
      WA_VARI_TEXT-REPORT    = G_REPORT.
      WA_VARI_TEXT-VARIANT   = G_VARIANT.
      WA_VARI_TEXT-VTEXT     = 'Test variant'.
      APPEND WA_VARI_TEXT TO IT_VARI_TEXT.
      CLEAR WA_VARI_TEXT.
      G_VARI_DESC-REPORT     = G_REPORT.
      G_VARI_DESC-VARIANT    = G_VARIANT.
      G_VARI_DESC-ENVIRONMNT = 'A'.
      G_VARI_DESC-AEDAT      = SY-DATUM.
      G_VARI_DESC-AETIME     = SY-UZEIT.
      WA_RSPARAMS-SELNAME    = 'P_NAME'.
      WA_RSPARAMS-KIND       = 'P'.
      WA_RSPARAMS-LOW        = P_NAME.
      APPEND WA_RSPARAMS TO IT_RSPARAMS.
      CLEAR WA_RSPARAMS.
      CALL FUNCTION 'RS_CREATE_VARIANT'
        EXPORTING
          CURR_REPORT   = G_REPORT
          CURR_VARIANT = G_VARIANT
          VARI_DESC     = G_VARI_DESC
        TABLES
          VARI_CONTENTS = IT_RSPARAMS
          VARI_TEXT     = IT_VARI_TEXT.
    ENDIF.
START-OF-SELECTION.
    WRITE 'Variant created'.
Thanks
Venkat.O

WFM_CORE2PUBLISH Queue in SMQ1 of CRM with destination NONE

Hi,
In the Outbound queue of CRM, I can see the queue "WFM_CORE2PUBLISH" with destination as "NONE" & status as "READY".
Queue Name Destination Entries Status
WFM_CORE2PUBLISH NONE 33,611 READY
Why this queue is created? &
is this required ? or
if v delete this any impact ?
tnx in adv.
rgds,
balu

Hi Balu,
WFM_CORE2PUBLISH queue is required to publish WFM server data (like
assignments, requirements, resources, time specifications) to groupware.
Settings for this can be maintained at below customizing path:
"SPRO => SAP Customizing Implementation Guide => Customer Relationship
Management => Workforce Deployment => WFD Server => WFM Event Handler =>
Specify Event Handling for WFD Objects"
If you do not have groupware integration then remove the groupware
relevant settings from this customizing.
If you do need these queues, then please register the queue name in SMQR; htne it will process automatically rather than remaning in status Ready.
Best regards,
Brian.

How to delete the short dump list in st22

Hi all,
i want to clear the runtime error list in ST22.
How to clear the list of short dump in ST22.
is there any T.code kindly suggest
thanks in advance
Sundar.c

Dear Sundar,
By default, short dumps are stored in the system for 14 days. The transaction for managing short dumps is ST22. You can delete short dumps in accordance with a time specification using the Reorganize function, which you can call by choosing
Goto u2192 Reorganize in ST22. You can save a short dump without a time limit using the Keep function, which you can choose under Short Dump u2192 Keep/Release in ST22.
The short dumps are stored in table SNAP. If there are too many entries in table SNAP, problems can occur during the reorganization (see SAP Note 11838). There are different options for deleting short dumps from table SNAP:
1. Call transaction ST22. Choose Goto u2192 Reorganize. You can now specify that all short dumps older than n days old (default 7) are to be deleted. If a very large number of records are deleted at once during the reorganization,
ORACLE error ora1562, failed to extend rollback segment ..., can occur. In this case, see SAP Note 6328.
2. Dropping and recreating table SNAP with the database utility (transaction SE14): you can use this transaction to drop and recreate the table SNAP. This means that all short dumps are deleted.
3. The reorganization program RSSNAPDL deletes old short dumps in pieces (to avoid database problems) from table SNAP. It deletes short dumps that are not flagged for retention and are older than seven days old. Schedule this program at a time of low workload, as large changes in the database are to be expected. The program RSNAPJOB performs a standard scheduling: it starts the program RSSNAPDL every day at 1:00 a.m.
4. TableSNAP is also automatically reorganized. At every short dump that occurs in dialog (the dump is displayed immediately after it is created), a maximum of 20 short dumps that are older than 7 days old are deleted from SNAP. This reorganization should be sufficient in normal production operation.
Hope this information resolves your error and also more useful in the feature.
Thanks
Kishore

Short dump while loading data in ODS

Hi,
When i scheduled data load for ODS, a short dump was generated with following error:
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"RULE_BASED_MODIFY_RSMONMESS" "(FORM)"
How to correct the error
The exception must either be prevented, caught within the procedure
"RULE_BASED_MODIFY_RSMONMESS"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-01654: unable to extend index
SAPBD2.RSMONMESS~AXY by 128 in tablespace PSAPBD2"
Internal call code.........: "[RSQL/INSR/RSMONMESS ]"
Please check the entries in the system log (Transaction SM21).
Please suggest what needs to be done.

Hi Sneh,
This is table space issue.
You need to contact basis guys to get it resolved.
Take a screen shot of this error and send the information to basis guys.
Once they clear the problem. repeat the step.
Hope this helps,
Sri.....

Short Dump Error DYNPRO_SEND_IN_BACKGROUND

hello Experts
I am facing one problem while query execution as a short dump is coming with run time error DYNPRO_SEND_IN_BACKGROUND.
On the same time, the other query based on same Info provider is running perfectly without giving any error.
Plz help on this , I checked the forums but does not get any output.
Thanks in advance
Neha

Hi Neha,
Check the below SAP Note.
Note 1010525 - ABAP dump in precalculation server with system messages
Veerendra.

Locking problem when calling FM in background OR destination NONE....

Hi,
I've made a RF transaction to handle some movements from one Storage Unit to another one by creating a TO using standard FM L_TO_CREATE_SINGLE - so far, so good.
My problem is that this FM makes a lot of standard checks (which is fine!) and if any of them fails - it issues a message, although I certainly don't want any message to be issued in this RF screen other than the ones that can be displayed on another screen.
In order to avoid those annoying on-line messages I've tried to call the function in background, and even with DESTINATION 'NONE' - and here it is doing fine regarding the message handling (it is handled by the sy-subrc handler after the FM call) BUT now I'm having an even more annoying problem -> a lock is created (on tables LQUAX and VEKP) which I can't get rid of!!! (unless deleting manually the lock in SM12.......)
Anyone experienced this by performing L_TO_CREATE_SINGLE in background mode or DESTINATION 'NONE' ?
A check whether the TO is succesfully created or not is important, as after the TO creation I'm creating an Idoc (via L_SUB_INITIATION_FOR_PICK_HU) for that TO.
Any ideas?
Message was edited by:
        Branko Jovanovic

Indeed, this solved my problem:
CALL FUNCTION 'L_TO_CREATE_SINGLE'
    EXPORTING
      i_lgnum               = whs_id
      i_bwlvs               = ltak-bwlvs
      i_matnr               = wa_lqua-matnr
      i_werks               = wa_lqua-werks
      i_lgort               = wa_lqua-lgort
      i_charg               = wa_lqua-charg
      i_anfme               = rl03t-anfme
      i_altme               = ltap-altme
      i_vltyp               = ltap-vltyp
      i_vlpla               = l_vlpla
      i_vlenr               = ltap-vlenr
      i_nltyp               = ltap-nltyp
      i_nlpla               = l_nlpla
      i_nlenr               = ltap-nlenr
      i_update_task         = c_true
      i_commit_work         = c_true
    IMPORTING
      e_tanum               = g_tanum
      e_ltap                = itab_ltap
    TABLES
      t_ltak                = itab_ltak_vb
      t_ltap_vb             = itab_ltap_vb
    EXCEPTIONS
<b>      error_message         = 01       "Shows errors if this is commented</b>
      no_to_created         = 1
      bwlvs_wrong           = 2
      betyp_wrong           = 3
      benum_missing         = 4
      betyp_missing         = 5
      foreign_lock          = 6
      vltyp_wrong           = 7
      vlpla_wrong           = 8
      vltyp_missing         = 9
      nltyp_wrong           = 10
      nlpla_wrong           = 11
      nltyp_missing         = 12
      rltyp_wrong           = 13
      rlpla_wrong           = 14
      rltyp_missing         = 15
      squit_forbidden       = 16
      manual_to_forbidden   = 17
      letyp_wrong           = 18
      vlpla_missing         = 19
      nlpla_missing         = 20
      sobkz_wrong           = 21
      sobkz_missing         = 22
      sonum_missing         = 23
      bestq_wrong           = 24
      lgber_wrong           = 25
      xfeld_wrong           = 26
      date_wrong            = 27
      drukz_wrong           = 28
      ldest_wrong           = 29
      update_without_commit = 30
      no_authority          = 31
      material_not_found    = 32
      lenum_wrong           = 33
      OTHERS                = 34.
IF sy-subrc NE 0.
    MOVE sy-subrc TO g_rc.
    message_id     = sy-msgid.
    message_number = sy-msgno.
    message_var1   = sy-msgv1.
    message_var2   = sy-msgv2.
    message_var3   = sy-msgv3.
    message_var4   = sy-msgv4.
    PERFORM error_message.
ENDIF.
So I'll reward Arnold eventhough I got the answer earlier .....
Cheers!

Short Dump While Changing Non-KeyField of Sorted Table

Hello,
A short dump occurs while trying to change a field of a sorted table item passed as CHANGING parameter. Are non-key fields in a sorted structure protected? The error message does not explicitely say so. Can anyone link to documentation explaining this behavior?
best regards,
JNN

You are passing by reference with CHANGING.
It looks like read-only stuff can't be passed to method CHANGING.
When I pass a literal or constant, there is a syntax error.
System could have given you a syntax error instead of dump.
Have a look at this snippet. Both method calls throw syntax error.
CLASS mainclass DEFINITION.
PUBLIC SECTION.
    CLASS-METHODS main.
PRIVATE SECTION.
    CLASS-METHODS passref CHANGING cv_test TYPE i.
ENDCLASS.                    "mainclass DEFINITION
CLASS mainclass IMPLEMENTATION.
METHOD main.
    "pass literal by ref
    passref(
      CHANGING
        cv_test = '2'
    "pass constant by ref
    CONSTANTS lc_test TYPE i VALUE 1.
    passref(
      CHANGING
        cv_test = lc_test
ENDMETHOD.                    "main
METHOD passref.
    "nothing
ENDMETHOD.                    "passref
ENDCLASS.                    "mainclass IMPLEMENTATION
START-OF-SELECTION.
mainclass=>main( ).

Short dump with the transaction CJ02

Hello, this is my first thread in the forum. I hope to solve my problem.
It is necesary to say you that my english is very poor, is not so good. Sorry for that.
When i use the transaction CJ02 to finish or close a project, appears an error when i save it. The steps are the followings:
1- Run the transaction CJ02 with a WBS element
2- Mark the line of the WBS element
3- Select then button Settlement rule
4- Fill 4 items in the next screen to distribution rules (the % is 100)
5- Back with green arrow
6- Fill the field Cost Center Req
7- Save
After a few seconds appears the dump:
<b>ABAP runtime errors    MESSAGE_TYPE_X
       Occurred on     20.11.2006 at 11:07:09
>> Short dump has not been completely stored. It is too big.
The current application triggered a termination with a short dump.
Error analysis
Short text of error message:
Nested call of PERFORM ON COMMIT:
Long text of error message:
Diagnosis
     During processing of a routine called using PERFORM ... ON COMMIT,
     the system attempted to call PERFORM ... ON COMMIT again. Nesting
     of this is not allowed.
System Response
Procedure
     The program indicated after "Caller:" must be changed. This is the
     program that calls the routine indicated after "Form:" during
     COMMIT processing. This routine is part of the program indicated
     after
     "Program:".
Procedure for System Administration
Technical information about the message:
Message classe...... 00
Number.............. 081
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
If the error is in one of your own ABAP programs or an SAP program that
you have modified, try to correct it.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"MESSAGE_TYPE_X"
"SAPMSSY0 " or "SAPMSSY0 "
"%_ORDER_FORM_FOR_ROLLBACK"</b>
There are several notes that apparently solve the problem with support packages that are applied in our system (for example 397011 or 614553). Inthis case our system is updated.
Can you help me please.
Thanks
Gabriel.-

Hi
Are you really sure https://websmp101.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=397011&_NLANG=E
is applied correctly ?
Try downloading with snote and see if it gets marked 'not relevant',
( are you on release 4.6 ? )
Given the nature of the problem ( and the fact that this issue is known ) , the best seems log an OSS support request
rgds
Dirk

SAP CRM middleware problem (sysfail ) The current application has triggered a termination with short dump

i'm having a proplem during starting initial load although i'm using the best practice documents C71 and B09 and all the configration was done by them .... could any one help ??

this is the first dump error for my RFCUSER on the ECC server
Category               ABAP Programming Error
Runtime Errors         MESSAGE_TYPE_X
ABAP Program           SAPLCRMC
Application Component CA
Date and Time          05.03.2014 17:50:47
Short Text
     The current application has triggered a termination with a short dump.
What happened?
     The current application program has detected a situation that should
     not occur. A termination with short dump has therefore been triggered
     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
Error analysis
    Short text of the error message:
    See SAP Note 1498111
    Long text of the error message:
     Diagnosis
     System Response
     Procedure
         Refer to the SAP Note that was mentioned.
     Procedure for System Administration
    Technical information about the message:
    Message class....... C_
    Number.............. 330
    Variable 1.......... 1498111
    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 occurs in a non-modfied SAP program, you might be able to
    find a solution in the SAP Notes system. If you have access to the SAP
    Notes system, check there first using the following keywords:
    "MESSAGE_TYPE_X"
    "SAPLCRMC" bzw. LCRMCF0C
    "CHECK_CRMATAB"
    If you cannot solve the problem yourself, please send the following
    information to SAP:
    1. This description of the problem (short dump)
    To do this, choose System -> List -> Save -> Local File (unconverted)
    on the screen you are in now.
    2. A suitable system log
    To do this, call the system log in transaction SM21. Restrict the time
    interval to ten minutes before the short dump and five minutes after
    it. In the display, choose System -> List -> Save -> Local File
    (unconverted).
3. If these are programs of your own, or modified SAP programs: Source
code of these programs
To do this, choose More Utilities -> Upload/Download -> Download in
the Editor.
4. Details regarding the conditions under which the error occurred or
which actions and input caused the error.
thanks

KNA1 short dump with Unicode conversion

Hello,
We did Unicode conversion in our dev box. every thing looks okay except one issue.
when we are trying to create customer using XD01. it gives a short dump DBIF_RSQL_INVALID_REQUEST in the update program at command INSERT KNA1.
we looked at data, structure of KNA1 with non unoicode system and not found any differnece. if i execute the same data in non-unicode system it works.
any idea what must be the issue?
regards
Shammi

Hi Shammi,
Have you checked in OSS if you find any note.
Regards,
Atish

Short Dump on BAPI_TRANSACTION_COMMIT with destination NONE

Similar Messages

Maybe you are looking for