Short dump whenever BP is updated or created.
Hi Experts,
I have a new CRM system here, everytime I try to create or change a BP and save it, everything is OK. BUT when I run transaction "BP" again, there's a popup saying "Express document "Update was terminated" received from author ***". And there's a short dump in st22 saying SYSTEM_CORE_DUMPED.
In sm13 there's an entry, the error occured in module SMW3_MFLOW_UPDATETASKBDOC, "Work process restarted; session terminated".
I also checked BDoc, there's one with state I04 - "BDoc stored before update task (intermediate state".
I checked the forums and the notes and also debugged into it. As the short dump happened when calling a kernal module "RFCControl", destination is "NONE", our system is not connected with any ERP system yet.
I wonder if you guys can give me some advice.
Thanks in advance.
Shane
Raja Shekar,
Check if the PSA is full... check the Database space available for PSA and then if required extend the PSA space and see if it goes through...
Arun
Message was edited by:
Arun Varadarajan
Similar Messages
-
Short dump while creating a plant.
Dear experts,
Iam getting a short dump whenever I try to create a plant and save it. Iam posting the contents of the dump ... Iam using Ecc 6.0 with Oracle as database. Kindly help me to resolve this ...
Runtime Errors RAISE_EXCEPTION
Date and Time 27.10.2007 17:10:59
Short text
Exception condition "DATA_INCONS_IN_EXIT_MANAGEM" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
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
A RAISE statement in the program "CL_EXITHANDLER================CP" raised the
exception
condition "DATA_INCONS_IN_EXIT_MANAGEM".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
How to correct the error
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:
"RAISE_EXCEPTION" " "
"CL_EXITHANDLER================CP" or "CL_EXITHANDLER================CM001"
"GET_INSTANCE"
or
"CL_EXITHANDLER================CP" "DATA_INCONS_IN_EXIT_MANAGEM"
or
"SAPLS_IMG_TOOL_5 " "DATA_INCONS_IN_EXIT_MANAGEM"
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.
System environment
SAP-Release 700
Application server... "BSLERP"
Network address...... "10.60.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
Shortdump setting.... "full"
Database server... "BSLERP"
Database type..... "ORACLE"
Database name..... "BTS"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 2 2006 23:08:16"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10103_SHARE "
Patch level. 52
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"
Memory consumption
Roll.... 8176
EM...... 17768808
Heap.... 0
Page.... 65536
MM Used. 12293456
MM Free. 1291704
User and Transaction
Client.............. 800
User................ "MURTHYTSN"
Language key........ "E"
Transaction......... "SPRO "
Program............. "CL_EXITHANDLER================CP"
Screen.............. "SAPLSZA1 0201"
Screen line......... 70
Information on where terminated
Termination occurred in the ABAP program "CL_EXITHANDLER================CP" -
in "GET_INSTANCE".
The main program was "SAPLS_IMG_TOOL_5 ".
In the source code you have the termination point in line 36
of the (Include) program "CL_EXITHANDLER================CM001".
Source Code Extract
Line
SourceCde
6
type_ref TYPE REF TO cl_abap_typedescr,
7
class_name TYPE seoclsname,
8
abs_type_classname TYPE string,
9
def_impl TYPE seex_boolean VALUE seex_false,
10
mig_enhspotname TYPE enhspotname,
11
is_impl TYPE enhboolean,
12
mig_badi_name TYPE enhbadiid.
13
14
CALL METHOD cl_exithandler=>get_class_name_by_interface
15
EXPORTING
16
instance = instance
17
IMPORTING
18
class_name = class_name
19
CHANGING
20
exit_name = exit_name
21
EXCEPTIONS
22
no_reference = 1
23
no_interface_reference = 2
24
no_exit_interface = 3
25
data_incons_in_exit_managem = 4
26
class_not_implement_interface = 5
27
OTHERS = 6.
28
CASE sy-subrc.
29
WHEN 1.
30
RAISE no_reference.
31
WHEN 2.
32
RAISE no_interface_reference.
33
WHEN 3.
34
RAISE no_exit_interface.
35
WHEN 4.
>>>>>
RAISE data_incons_in_exit_managem.
37
WHEN 5.
38
RAISE class_not_implement_interface.
39
ENDCASE.
40
41
CONCATENATE '\CLASS=' class_name INTO abs_type_classname.
42
43
Is the given instance initial?
44
IF NOT instance IS INITIAL.
45
CALL METHOD cl_abap_typedescr=>describe_by_object_ref
46
EXPORTING
47
p_object_ref = instance
48
RECEIVING
49
p_descr_ref = type_ref.
50
CHECK type_ref->absolute_name NE abs_type_classname.
51
ENDIF.
52
53
SELECT SINGLE mig_enhspotname mig_badi_name FROM sxs_attr INTO (mig_enhspotname,mig_badi_n
54
WHERE exit_name = exit_name.
55
Contents of system fields
Name
Val.
SY-SUBRC
4
SY-INDEX
1
SY-TABIX
0
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
ADDR0200
SY-UCOMM
CHCK
SY-TITLE
Edit address: 5002
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20071024
SY-UZEIT
171059
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
43 METHOD CL_EXITHANDLER================CP CL_EXITHANDLER================CM001 36
CL_EXITHANDLER=>GET_INSTANCE
42 FUNCTION SAPLXSZAR ZXSZARU01 25
EXIT_SAPLSZAR_001
41 FUNCTION SAPLSZAR LSZARU01 108
ADDR_REGIONAL_DATA_CHECK
40 FORM SAPLSZA2 LSZA2F20 382
CHECK_ADDR1_DATA
39 FUNCTION SAPLSZA2 LSZA2U02 42
ADDR_CHECK
38 FUNCTION SAPLSZA0 LSZA0U01 79
ADDR_INSERT
37 FORM SAPLSZA1 LSZA1F22 1886
INSERT_ADDRESS_INTO_MEMORY
36 FORM SAPLSZA1 LSZA1F22 2234
PUT_ADDRESS_TO_MEMORY
35 FORM SAPLSZA1 LSZA1I02 409
D0100_OK_CODE
34 FORM SAPLSZA1 LSZA1F03 17
D0100_OK_CODE_WRAPPER
33 MODULE (PAI) SAPLSZA1 LSZA1I02 13
D0100_OK_CODE
32 FUNCTION SAPLSZA1 LSZA1U01 200
ADDR_DIALOG_INTERN
31 FUNCTION SAPLSZA1 LSZA1U05 177
ADDR_DIALOG
30 FORM SAPL0ORG LSVIMF24 292
ADDRESS_MAINTAIN
29 FORM SAPL0ORG LSVIMFX2 577
DETAIL_PAI
28 MODULE (PAI) SAPL0ORG LSVIMIXX 354
DETAIL_PAI
27 FORM SAPL0ORG LSVIMF2L 337
CALL_DYNPRO
26 FUNCTION SAPL0ORG L0ORGU34 35
VIEWPROC_V_T001W
25 FUNCTION SAPL0ORG L0ORGU33 49
VIEWFRAME_V_T001W
24 FUNCTION SAPLSVIM LSVIMU01 138
VIEW_MAINTENANCE
23 FUNCTION SAPLSVIM LSVIMU03 427
VIEW_MAINTENANCE_CALL
22 FORM SAPLS_CUS_ACTIVITY LS_CUS_ACTIVITYF01 358
START_SELECTED_TRANSACTION
21 MODULE (PAI) SAPLDSYH LDSYHI12 56
D1200_PAI_MODULE
20 FUNCTION SAPLDSYH LDSYHU11 70
OUTLINE_LIST_TCODES
19 FUNCTION SAPLS_CUS_ACTIVITY LS_CUS_ACTIVITYU07 103
S_CUS_ACTIVITY_EXECUTE
18 FUNCTION SAPLS_CUS_IMG_ACTIVITY LS_CUS_IMG_ACTIVITYU04 35
S_CUS_IMG_ACTIVITY_EXECUTE
17 FUNCTION SAPLS_IMG_TOOL_1 LS_IMG_TOOL_1U02 63
STREE_EXIT_TO_OBJECT_COBJ
16 FUNCTION SAPLSHI1 LSHI1U16 120
STREE_EXIT_TO_OBJECT
15 FORM SAPLSHI01 LSHI01F0Y 185
EXIT_TO_OBJECT_HC
14 FORM SAPLSHI01 LSHI01F05 70
HANDLE_LINK_CLICK
13 METHOD SAPLSHI01 LSHI01CI1 25
LCL_APPLICATION=>HANDLE_LINK_CLICK
12 METHOD CL_ITEM_TREE_CONTROL==========CP CL_ITEM_TREE_CONTROL==========CM013 53
CL_ITEM_TREE_CONTROL=>HANDLE_NODE_KEY_ITEM_NAME_EVT
11 METHOD CL_ITEM_TREE_CONTROL==========CP CL_ITEM_TREE_CONTROL==========CM00S 60
CL_ITEM_TREE_CONTROL=>HANDLE_EVENT
10 METHOD CL_GUI_COLUMN_TREE============CP CL_GUI_COLUMN_TREE============CM01O 15
CL_GUI_COLUMN_TREE=>HANDLE_EVENT
9 METHOD CL_TREE_CONTROL_BASE==========CP CL_TREE_CONTROL_BASE==========CM017 32
CL_TREE_CONTROL_BASE=>DISPATCH
8 METHOD CL_GUI_CFW====================CP CL_GUI_CFW====================CM001 138
CL_GUI_CFW=>DISPATCH
7 FORM SAPLSHI01 LSHI01F1M 17
EXECUTE_USER_COMMAND_W_EXITS
6 FUNCTION SAPLSHI01 LSHI01U12 30
STREE_BROWSER_PAI
5 MODULE (PAI) SAPLSHI01 LSHI01I01 55
PAI_200
4 FUNCTION SAPLSHI01 LSHI01U07 165
STREE_BROWSER_DYNP_HC
3 FUNCTION SAPLSHI21 LSHI21U03 144
STREE_EXTERNAL_DISPLAY
2 FORM SAPLS_IMG_TOOL_5 LS_IMG_TOOL_5F01 20
DISPLAY_REFERENCE_IMG
1 MODULE (PAI) SAPLS_IMG_TOOL_5 LS_IMG_TOOL_5I01 39
USER_COMMAND_0100
Chosen variables
Name
Val.
No. 43 Ty. METHOD
Name CL_EXITHANDLER=>GET_INSTANCE
EXIT_NAME
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
NULL_INSTANCE_ACCEPTED
2
0
0
0
ACT_IMP_EXISTING
2
0
0
0
INSTANCE
F0000000
F0000000
SY-REPID
CL_EXITHANDLER================CP
4454545444444533333333333333334522222222
3CF589481E4C52DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
%_SPACE
2
0
0
0
CL_DRAGDROP=>COPY
1
0000
1000
CL_WB_REQUEST=>TO_IMMEDIATE_START
SY-SUBRC
4
0000
4000
CL_DRAGDROP=>USEDEFAULTEFFECT
4
0000
4000
SYST-REPID
CL_EXITHANDLER================CP
4454545444444533333333333333334522222222
3CF589481E4C52DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CL_GUI_CONTROL=>LIFETIME_DEFAULT
0
0000
0000
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ABS_TYPE_CLASSNAME
No. 42 Ty. FUNCTION
Name EXIT_SAPLSZAR_001
IV_NATION
2
0
0
0
X_ACCEPT_ERROR
2
0
0
0
X_ADRC_STRUC
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
X_DIALOG_ALLOWED
X
5
8
0
0
Y_ADRC_STRUC
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Y_RETCODE
2
0
0
0
ERROR_TABLE[]
Table IT_2299[0x572]
\FUNCTION-POOL=SZA1\FORM=INSERT_ADDRESS_INTO_MEMORY\DATA=ERROR_TABLE[]
Table reference: 208
TABH+ 0(20) = 00000000F8EB2E3D00000000D0000000FB080000
TABH+ 20(20) = 000000003C020000FFFFFFFF04A90100303E0000
TABH+ 40( 8) = 10000000C1248001
store = 0x00000000
ext1 = 0xF8EB2E3D
shmId = 0 (0x00000000)
id = 208 (0xD0000000)
label = 2299 (0xFB080000)
fill = 0 (0x00000000)
leng = 572 (0x3C020000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000317
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
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 = Not allocated
pghook = Not allocated
idxPtr = Not allocated
shmTabhSet = Not allocated
id = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
shmVersId = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
collHook = 0x00000000
ext2 = 0xD09AD03C
>>>>> 2nd level extension part <<<<<
tabhBack = 0x30F18E3D
delta_head = 000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
000000000000000000000000000000
000000000000000000000000000000
%_VIASELSCR
0
4
%_SPACE
2
0
0
0
SY-REPID
SAPLXSZAR
5454555452222222222222222222222222222222
310C83A120000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LR_EXIT
F0000000
F0000000
%_DUMMY$$
2222
0000
0000
0000
Y_ERROR_TABLE
Table[initial]
No. 41 Ty. FUNCTION
Name ADDR_REGIONAL_DATA_CHECK
IV_NATION
2
0
0
0
X_ACCEPT_ERROR
2
0
0
0
X_ADRC_STRUC
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
X_DIALOG_ALLOWED
X
5
8
0
0
X_T005
800IN IND064 ININD000 00 15500 4111 0000 00 436 664000INDIEN 000 1
3334424443332222222222224444433322233233333223333223333233233322222233333344444423332322222222
8009E09E40640000000000009E9E40000000001550000411100000000004360000006640009E495E00000100000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Y_ADRC_REGIO
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Y_ADRC_STRUC
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Y_RETCODE
2
0
0
0
ERROR_TABLE[]
Table IT_2299[0x572]
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LV_MAND
C
422
300
000
000
SY-REPID
SAPLSZAR
5454554522222222222222222222222222222222
310C3A1200000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
%_SPACE
2
0
0
0
%_CX_GRID_ID
1
0000
1000
SYST-REPID
SAPLSZAR
5454554522222222222222222222222222222222
310C3A1200000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SV_THERE_IS_CUST_EXIT
X
5
8
0
0
T005S
22222222222222
00000000000000
00000000000000
00000000000000
T005
00 000 00 00 00 00 0000 00 000 000
2222222223322222222222222222233322233233233222332223333233222222222222233322222223332222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
CO_ERROR
E
4
5
0
0
No. 40 Ty. FORM
Name CHECK_ADDR1_DATA
SY-MSGV3
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
FIELDNAME
222222222222222222222222222222
000000000000000000000000000000
000000000000000000000000000000
000000000000000000000000000000
C_NULL
0
0000
0000
RETURNCODE_ERRORS
2
0
0
0
C_ERROR_OCCURRED
E
4
5
0
0
H_ADRC_STRUC+0(1800)
2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ADDR1_DATA+460(1800)
2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
H_ADRC_STRUC
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_COMM_TTX
TTX
555
448
000
000
NATION
2
0
0
0
G_ACCEPT_ERROR
2
0
0
0
G_DIALOG_ALLOWED
X
5
8
0
0
T005
800IN IND064 ININD000 00 15500 4111 0000 00 436 664000INDIEN 000 1
3334424443332222222222224444433322233233333223333223333233233322222233333344444423332322222222
8009E09E40640000000000009E9E40000000001550000411100000000004360000006640009E495E00000100000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
TSAD6T
222222222222222222222222222222222222222222222222
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
ERROR_TABLE[]
Table IT_2299[0x572]
%_SPACE
2
0
0
0
No. 39 Ty. FUNCTION
Name ADDR_CHECK
ADDRESS_HANDLE
8005002
3333333222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
8005002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ADDRESS_NUMBER
2222222222
0000000000
0000000000
0000000000
ADDRESS_OBJECT_TYPE
1
3
1
0
0
NATION
2
0
0
0
RETURNCODE
2
0
0
0
ERROR_TABLE[]
Table IT_2299[0x572]
ADDRESS_DATA_1
00000000000000000003XYZ SOLUTIONS LIMITED
3333333333333333333355525445544452444454422222222222222222222222222222222222222222222222222222
0000000000000000000389A03FC549FE30C9D945400000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ADDRESS_DATA_2
0000000000000000
3333333333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ADDRESS_DATA_3
0000000000000000
3333333333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
LV_ADRC_STRUC+0(1800)
2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ADDRESS_DATA_1+460(1800)
2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_DEFAULT_HANDLE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
SAPLSZA2
5454554322222222222222222222222222222222
310C3A1200000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ERROR_TABLE
000
2222222222222222222223332222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
LV_ADRC_STRUC
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_DEFAULT_NATION
2
0
0
0
C_SHOW_ALL
2
0
0
0
C_PERSONAL_ADDRESS
2
3
2
0
0
SY-REPID
SAPLSZA2
5454554322222222222222222222222222222222
310C3A1200000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ADDRESS_DATA_2+32(1800)
2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 38 Ty. FUNCTION
Name ADDR_INSERTDear Sunil,
Thanks a lot for your reply. I did search in service market place for notes regarding this problem. However, i could not find possible solutions to resolve this. I will once again search the notes in case if i have missed something. in case, if you come across any solutions to resolve this problem, Kindly post that here and that would be a great help for me.
Regards,
Chaitanya -
Short Dump with VA22 transaction in ECC 6
Hi All,
We are on ECC 6 and facing a short dump whenever we are trying to save some quotation. We are getting the following error.
There is probably an error in the program "SAPLSYDB". The program is triggered in the update task. There, the following ABAP/4 statements are not allowed:
CALL SCREEN
CALL DIALOG
CALL TRANSACTION
SUBMIT
"POSTING_ILLEGAL_STATEMENT" " "
"SAPLSYDB" or "LSYDBU27"
"DB_COMMIT".
Is there a sap note for this. Any link or pointer to this will be highly appreciated.
Regards,
JayantHello,
This looks like a problem for SAP. I assume that you have not modified the
program SAPLSYDB. I also assume that you have searched the Service Marketplasce
for any OSS notes. My next step would be to create a message to SAP to get them to
have a look.
Regards
Greg Kern -
What is Short Dump Analysis and secendry index ?
Dear Experts .
1.) What is purpose of T-codes SE30 and ST22 ?
What is Short Dump Analysis ?
2.) What is secendry index , How to use it ? How it effects the Performance of a report ?
Please it is urgent ...
Regards : RajneeshHi
A dump analysis is a comprehensive list that should enable you to identify the causes and possible solutions of program errors. The ABAP Workbench generates a short dump whenever a report or transaction terminates due to a serious error. The system enters the error in the system log and writes a snapshot of the program at the moment when it terminated into a special database table called SNAP.
Dump analyses give the user or programmer information about the causes of the error that has caused the program to terminate. Experienced users can use them to identify very quickly where and why this occurred. He or she can them solve the problem.
The snapshot contains the following information:
Why the program has terminated
What caused the program termination
Where in the program code the termination occurred
What you can do to correct the error
The values of the relevant system fields when the program terminated
The calls or events that were active when the program terminated
Any other programs that are affected.
http://help.sap.com/saphelp_nw70/helpdata/en/c6/617d0ce68c11d2b2ab080009b43351/content.htm
Index: Technical key of a database table.
Primary index: The primary index contains the key fields of the table and a pointer to the non-key fields of the table. The primary index is created automatically when the table is created in the database.
Secondary index: Additional indexes could be created considering the most frequently accessed dimensions of the table.
Structure of an Index
An index can be used to speed up the selection of data records from a table.
An index can be considered to be a copy of a database table reduced to certain fields. The data is stored in sorted form in this copy. This sorting permits fast access to the records of the table (for example using a binary search). Not all of the fields of the table are contained in the index. The index also contains a pointer from the index entry to the corresponding table entry to permit all the field contents to be read.
When creating indexes, please note that:
An index can only be used up to the last specified field in the selection! The fields which are specified in the WHERE clause for a large number of selections should be in the first position.
Only those fields whose values significantly restrict the amount of data are meaningful in an index.
When you change a data record of a table, you must adjust the index sorting. Tables whose contents are frequently changed therefore should not have too many indexes.
Make sure that the indexes on a table are as disjunctive as possible.
(That is they should contain as few fields in common as possible. If two indexes on a table have a large number of common fields, this could make it more difficult for the optimizer to choose the most selective index.)
Accessing tables using Indexes
The database optimizer decides which index on the table should be used by the database to access data records.
You must distinguish between the primary index and secondary indexes of a table. The primary index contains the key fields of the table. The primary index is automatically created in the database when the table is activated. If a large table is frequently accessed such that it is not possible to apply primary index sorting, you should create secondary indexes for the table.
The indexes on a table have a three-character index ID. '0' is reserved for the primary index. Customers can create their own indexes on SAP tables; their IDs must begin with Y or Z.
If the index fields have key function, i.e. they already uniquely identify each record of the table, an index can be called a unique index. This ensures that there are no duplicate index fields in the database.
When you define a secondary index in the ABAP Dictionary, you can specify whether it should be created on the database when it is activated. Some indexes only result in a gain in performance for certain database systems. You can therefore specify a list of database systems when you define an index. The index is then only created on the specified database systems when activated -
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
AmanHi 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 -
We get a short dump whenever we try to start t-code MEREP_SBUILDER.
The entire dump is as follows. This is for MI7.1SP03. Please help. Thanks a lot!
Runtime Errors MESSAGE_TYPE_X
Date and Time 22.04.2008 11:01:01
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).
Error analysis
Short text of error message:
Obsolete object being used. See long text
Long text of error message:
This object is obsolete.
If you require this object, create a customer message on component
BC-MOB-DOE.
Technical information about the message:
Message class....... "MEREP_00"
Number.............. 800
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Trigger Location of Runtime Error
Program MEREP_SBUILDER
Include MEREP_SBUILDER_PBO01
Row 10
Module type (MODULE PBO)
Module Name STATUS
Source Code Extract (Source code has changed)
Line
SourceCde
1
This code is no longer being used.If you need more clarification, then please raise a csn
2
3
4
****INCLUDE MEREP_SCENBLDR_PBO1 .
5
6
7
**& Module STATUS OUTPUT
8
9
module status output.
>>>>>
MESSAGE x800(MEREP_00).
11
perform set_status .
12
endmodule. " STATUS OUTPUT
13
14
15
MODULE pbo_0100_01 OUTPUT
16
17
18
19
*module pbo_0100_01 output.
20
perform pbo_0100_01 .
21
*endmodule. "pbo_0100_01 OUTPUT
22
23
24
MODULE pbo_0110_01 OUTPUT
25
26
27
28
*module pbo_0110_01 output.
29
perform pbo_0110_01 .Hi,
check this:
SDOE_WB
Well, to get some more informations on 7.1 have look here:
http://help.sap.com/saphelp_nwmobile71/helpdata/en/8F/0B674240449C60E10000000A1550B0/frameset.htm
>Developers guide>developing mobile applications>developing mobile applications for laptops>Tutorial--creating a service order application.
Hope that helps you!
Regards,
Oliver -
What are techniques used for tuning query performance? Please explain in detail?
What are short dumps how can we check?
What methodologies we follow for the PSA cleansing? Where exactly is the PSA change log where we can delete the request based on timestamp details am using BW 3.1c?
plz help points assured....Hi,
For query performance please check the following link
http://help.sap.com/saphelp_nw2004s/helpdata/en/41/b987eb1443534ba78a793f4beed9d5/frameset.htm
Short dumps:
A short dump is an program error because of which the process terminates. It is notified and can be viewed in t-code ST22 on a particular usernaem where you can analyze the reason for short dump.
and refer these links
http://publib.boulder.ibm.com/tividd/td/ITMAN/SC32-9195-00/en_US/HTML/sap_add06.htm
short dump
Short dump while loading data?
Update rules activation gives short dump?
Delete of Master Data creates short dump?
PSA:
check the following link
http://help.sap.com/saphelp_nw70/helpdata/EN/bd/c627c88f9e11d4b2c90050da4c74dc/frameset.htm
Hope it help u.
Assign Points if it helps.
Regards,
RKC
Edited by: RKC on Mar 7, 2008 11:29 AM -
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
ShammiHi Shammi,
Have you checked in OSS if you find any note.
Regards,
Atish -
Short Dump by creating Transformation
Hi every Body,
I have installed NW2004S ABAP Sneak Preview system(BI 7.0) on my PC at home, and I have the following problem: when I try to create Transformation, the system say proposal generated with (n) rules., and when I click on OK I get a Short Dump as shown below.
The short dump says: Make sure that the OCXs ICDataFlow.ocx and wdbdadpt.ocx are
installed on your computer, but these two OCX data are already installed and I think the front end is installed correctly but the error still occurs.
Please . did any body get such a problem .. I appreciate any help.
short dump----
Error analysis
Short text of error message:
Network could not be launched due to control error
Long text of error message:
Diagnosis
Network control cannot be started either because is is not
installed on the front-end computer, or because the control
framework is inconsistent when the function is called up.
To be able to start the network graphic, you need two OCX files
that are delivered with the BW Frontend.
System Response
Processing has been terminated.
Procedure
Make sure that the OCXs ICDataFlow.ocx and wdbdadpt.ocx auf are
installed on your computer. You can find notes on installing and
checking the BW Frontend by searching for SAP Notes with the
following key words:
Version, sapservX, Setup, Patch, Installation, Frontend, BW,
sapbexc.xla, checktool, wdtaocx, wdtaocx.ocx
If the front end is installed correctly but the error still occurs,
contact SAP.
Procedure for System Administration
Technical information about the message:
Message class....... "RSNG"
Number.............. 001
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
short dump -Check out the note 946481. This should resolve your issue.
Please update the output
Regards
Pankaj -
We are encounter Short dump in BAPI_INCOMINGINVOICE_PARK when creating inte
Hi experts,
We are encounter Short dump in BAPI_INCOMINGINVOICE_PARK when creating inter-company billing.
Itu2019s working fine when executing from foreground and calling from executable program. Through outbound output type calling from the transaction (VF02 or VF01), encounter short dump. Program terminates in the update task. (Call screen 300) program.
Triggering flow:
VF02 -> output type -> msg type -> zfun..module -> Bapi_incominginvoice_park ->
-> calculate_tax_document(fun.module) u2013> call screen 300 (short dump)
Please let me know if any solution for this issue.
Kind Regards,
ThambieProblem solved :
Trigger flow:
VF02 -> output type -> msg type -> zfun..module -> zfun.module(RFC) start new task-> Bapi_incominginvoice_park -> bapi comit.
Thanks.
Edited by: Thambie on Sep 1, 2010 9:45 AM -
Short Dump while creating Configuration (Application or Component)
Hi All,
I m facing a short dump, while creating a Component or Applcation Configuration
in the standard FPM_GAF_COMPONENT.
Short dump states the Runtine error as MESSAGE_TYPE_UNKNOWN
Short text
Message type " " is unknown.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_WDR_MESSAGE_MANAGER========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
Information on where terminated
Termination occurred in the ABAP program "CL_WDR_MESSAGE_MANAGER========CP" -
in "IF_WD_MESSAGE_MANAGER~REPORT_T100_MESSAGE".
The main program was "SAPMHTTP ".
In the source code you have the termination point in line 16
of the (Include) program "CL_WDR_MESSAGE_MANAGER========CM00R".
12 exporting
13 textid = cx_wdr_rt_exception=>invalid_
14 endif.
15
>>>> message id msgid type msgty number msgno
17 with p1 p2 p3 p4
18 into msg.
19
20 if p1 is not initial.Hello Srikanth,
I have no issues in trying to help someone as polite as you! It is very nice to have questions answered in an intelligible manner - not unfortunately always the case.
Without being able to debug on your system it is quite difficult to say what might be causing this error - especially as you say this was working in a different system.
I'm sure you've already tried eliminating differences in your authorisations between the two systems? Are you registered as a developer in the new system?
Sorry I'm now just guessing as I've not come across the error myself - hopefully now that we have clearly documented the issue, someone else might be able to shed some light on what might cause it!
Chris -
Short dump while creating transparent container dynamically
Hi experts!
I want to create a transparent container dynamically, but I get a Short Dump (
Note
The following error text was processed in the system NSP : Access via 'NULL' object reference not possible.
The error occurred on the application server Datatrain_NSP_00 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: CREATE_BY_VIEW_ELEMENT of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP)
while doing so. Below my code...
Can somebody please advise I don't know what I did wrong....
Thanks in advance!
Points will be rewarded
METHOD wddomodifyview .
DATA: lr_container TYPE REF TO cl_wd_uielement_container,
lr_matrix_head TYPE REF TO cl_wd_matrix_data,
lv_hlp_str TYPE string VALUE 'DYNCONT_1',
lr_trans_cont TYPE REF TO cl_wd_transparent_container.
lr_container ?= view->get_element( 'ROOTUIELEMENTCONTAINER' ).
CALL METHOD cl_wd_transparent_container=>new_transparent_container
EXPORTING
enabled = ABAP_TRUE
id = lv_hlp_str
is_layout_container = ABAP_TRUE
receiving
control = lr_trans_cont
lr_matrix_head = cl_wd_matrix_head_data=>new_matrix_head_data(
element = lr_trans_cont ).
lr_trans_cont->set_layout_data( lr_matrix_head ).
lr_container->add_child( lr_trans_cont ).Hi Felix,
You need to set the layout first and then set the layout data. Use the method cl_wd_matrix_layout=>new_matrix_layout. Do a set_layout on the container and then do set_layout_data. That should solve your problem.
Regards
Nithya -
Short Dump While creating a Value Driver Tree
Hi all,
I am trying to create a value driver tree in CPM. i am on SEM verion 3.1b. I am able to create the value driver tree but when i goto the graphical view it generates a ABAP short dump. does anybody have any idea on thishi srini,
Elaborate it clearly .
Regards ,
Muneeh Gitta. -
Short dump while executing few queries , which has got created on Infoset.
Hi,
We went to BI7.0 upgrade from BW3.x now.
We are getting short dump short dump while executing few queries and work book, which has got created on Infoset.
When i was executing work book where i was geting popup message saying that "Erro ZSD_XST_F00121 is invalid".When i click that message it went to dump.
I was getting this error while executing query on infoset.
We are currently SP Stack 13(Patch level 15).
I found some note 1067918 as per the shortdum,where it is saying that you need to apply SP Stack14(patch level16).
Please some one who had earlier this kind of issue.
I appreciate your answer.Dear Krish,
Yes, It is the patch problem.
We too faced the same issue on Infosets.
Apply SP 15.
Regards,
Ram. -
Short Dump created while modifying a process chain
Hi guys ,
Iam getting a short dump while trying to modify a process chain and it is taking me too short dump where the message is PROCESS HAS NO PREDECESSOR but even when Iam trying to DETAILED VIEW it is taking me too short dump
Can anyone help me out of this issueHi ,
I have removed the existing start process and I have checked but there is no Use the same short dump is created again
Please suggest me some usefull solution .
Maybe you are looking for
-
After joining a company to receive products, my icloud mail changed and I can't change it back
I joined 'itworks'.com and went on the site to edit our information for purchasing product etc. my email in icloud changed. it now says 'itworks' in the "To;" section of receiving mail. very confused. I went into the mail preferences and could no
-
Liveconnect bug, in 1.4.2_04 ?
It seems to me that there is a bug in the wery newest version of Java in download on www.java.com . When using liveconnect (javascript - java communication) the browser sometimes freezes. If you are using j2re Version 1.4.2_04 (build b05), with Micro
-
Why don't I see a photo tab (camera roll) in icloud
I am switching computers. Going from XP to 7. I am told everything is in icloud but everytime I try to sync in Itunes a message pops up asking to erase and sync--- will erase the contents of this ipod and replace it with the content of this Itunes l
-
While creating budget through CJ30 for a project , the following Error message comes "Assign plan/ budget profile to the object" Although in the config. Budget profile is already assigned to that Project profile. But through CJ02 ,in the control
-
Hi Folks, I have a concern here below, if you have any idea, could you please throw here. what is the module for ATG control center and how the components get executes. for example: If we click on the 'People and Organizations' under 'Control center