FB03 - Short Dump - is not Unicode-compatable
hi gurus,
i have a short dump in PRODUCTION in TCODE : FB03.
the short dump says that syntax error in program : RK2RS001 is not UNICODE-COMPATABLE in program attributes...
how can i resolve this one pls...
thanks in advance,
pasala.
Hi,
Refer to below links:
<<links removed, points unassigned by moderator>>
Regards,
Prasuna.
Edited by: kishan P on Nov 24, 2010 2:03 PM
Similar Messages
-
Short dump on production server
ABAP runtime errors GETWA_NOT_ASSIGNED
Occurred on 28.12.2007 at 11:16:11
>> Short dump has not been completely stored. It is too big.
Field symbol has not yet been assigned.
What happened?
The current ABAP/4 program "SAPLCEI0 " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
You attempted to access an unassigned field symbol
(data segment 2941).
This error occurs:
- if you address a typed field symbol before it has been set with
ASSIGN or
- if you address a field symbol that has been reset with UNASSIGN
or pointed to a local field that no longer exists, or
- if you address a field symbol that pointed to a line of an internal
table that has now been deleted, or
- if you address a global function interface partameter, even
though the relevant function module is not active,
i.e. it is not in the list of active calls. You can get the list
of active calls from the this short dump.
How to correct the error
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:
"GETWA_NOT_ASSIGNED"
"SAPLCEI0 " or "LCEI0U29 "
"CEI0_DDB_HAS_VALUES_INTERNAL"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "46C"
Application server....... "SAPCLUN"
Network address.......... "172.18.112.20"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "16x Intel 80158"
Database server.......... "DBCLUN"
Database type............ "MSSQL"
Database name............ "PRD"
Database owner........... "dbo"
Character set............ "English_United State"
SAP kernel............... "46D"
Created on............... "Apr 9 2006 21:37:58"
Created in............... "NT 4.0 1381 Service Pack 6 x86 MS VC++ 12.00"
Database version......... "SQL_Server_7.00 "
Patch level.............. "2225"
Patch text............... " "
Supported environment....
Database................. "MSSQL 6.5.213 or higher, MSSQL 7.0.1 or higher"
SAP database version..... "46D"
Operating system......... "Windows NT 4.0, Windows NT 5.0, Windows NT 5.1,
Windows NT 5.2, , System build information:,
, LCHN : "
User, transaction...
Client.............. 400
User................ "QPBASIC"
Language key........ "E"
Transaction......... "QA02 "
Program............. "SAPLCEI0 "
Screen.............. "SAPLQPL1 0200"
Screen line......... 34
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPLCEI0 " in
"CEI0_DDB_HAS_VALUES_INTERNAL".
The main program was "SAPLQPL1 ".
The termination occurred in line 49
of the source code of program "LCEI0U29 " (when calling the editor 490).
Source code extract
000190 *" EXCEPTIONS
000200 *" NOT_FOUND
000210 *"----
000220
000230 DATA:
000240 ls_charac TYPE api_char,
000250 lt_charac TYPE STANDARD TABLE OF api_char,
000260 ls_vali TYPE api_vali.
000270
000280 DATA: ls_mi TYPE ts_mi,
000290 ls_wi TYPE ts_wi,
000300 ls_icv TYPE ts_value,
000310 ls_defval TYPE ts_defval,
000320 ls_inco_val TYPE ts_inco_val,
000330 ls_char_list TYPE ts_char_list,
000340 lv_subrc TYPE sy-subrc,
000350 lv_kntype TYPE cukntype.
000360
000370 data: ls_vallist TYPE ddb_c04, "676840
000380 lt_vallist TYPE STANDARD TABLE OF ddb_c04, "676840
000390 ls_restrict type ddb_c03, "699141
000400 lt_restrict type STANDARD TABLE OF ddb_c03, "699141
000410 lv_rflag type c. "676840
000420
000430 *----
000440 REFRESH exp_values.
000450
000460 DESCRIBE TABLE imp_characteristics LINES sy-tfill.
000470 IF sy-tfill EQ 0.
000480 LOOP AT
INTO ls_char_list.
000500 ls_charac-atinn = ls_char_list-atinn.
000510 APPEND ls_charac TO lt_charac.
000520 ENDLOOP.
000530 ELSE.
000540 lt_charac = imp_characteristics[].
000550 ENDIF.
000560
000570 LOOP AT lt_charac
000580 INTO ls_charac.
000590 IF ls_charac-atnam NE space.
000600 * input: name
000610 PERFORM read_mi_with_atnam
000620 USING
000630 ls_charac-atnam
000640 CHANGING
000650 lv_subrc
000660 ls_mi.
000670 ELSE.
000680 * input: atinn
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 0
SY-TABIX 0 SY-DBCNT 1
SY-FDPOS 1 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1
Chosen variables
Name.......................... Contents.1........2........3....+....4
PROP_BITMAP 310
3000
6100
ALLOWED_VALUES
2
0
PROP_WIDTH 300
2000
C100
ASSIGNED_VALUES X
5
8
TOP_WINDOW 33
2000
1000
ASSIGNED_VALUES_API_DI
2
0
PROP_INDEX 350
5000
E100
DEFAULT_VALUES
2
0
DYNPRO_9 19
1000
3000
DEFAULT_VALUES_API_DN
2
0
DYNPRO_8 18
1000
2000
DEFAULT_VALUES_API_ST
2
0
DYNPRO_7 17
1000
1000
DOCUMENT_INFO
2
0
PROP_SOUND 340
5000
4100
FIRST_ASSIGNED_VALUE
2
0
PROP_TEXT 330
4000
A100
INCONSISTENT_VALUES
2
0
LANGUAGE E
4
5
SY-LANGU E
4
5
PROP_BITMAP_STYLE 320
4000
0100
VALID_VALUES
2
0
PROP_FONT_SIZE 380
7000
C100
EXP_VALUES[] #########################À##°###########
0000000000000000000000000C00B00000000000
00000000000000000000000040000A0000000000
... + 40 ################ÿÿÿÿ####################
0000000000000000FFFF00000000000000000000
1000000000001000FFFF81007000430000000000
... + 80 ################################
00000000000000000000000000008000
00000000000000000000000000004100
PROP_ITEM 370
7000
2100
IMP_CHARACTERISTICS[] #########################À##############
0000000000000000000000000C00800000000000
00000000000000000000000040000A0000000000
... + 40 ################ÿÿÿÿI###################
1000000000000000FFFF40000000000000000000
0000000000000000FFFF90002000430000000000
... + 80 ################################
00000000000000000000000000008000
00000000000000000000000000005100
SCREEN-ACTIVE 0
3
0
SY-XPROG SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
TVS_EDITLABELS 6
0000
6000
SY-TFILL 0
0000
0000
INCL_PRICE 0000
3333
0000
LS_CHAR_LIST 00000000000000000000
3333333333333333333322222222222
0000000000000000000000000000000
RSJOBINFO 00000000
2222222222222222222222222222222233333333
0000000000000000000000000000000000000000
... + 40 000000
3333332222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 ####
0000
0000
SYST ########################################
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
... + 40 ####################################I###
0000000000000000000000000000000000004000
1000100010000000100000000000000000009000
... + 80 ########################################
0000000000000000100000000000000000000000
0000000000000000E00000000000000000000000
... + 120 ####################################p###
00000000
0000000
LT_CHARAC Table[initial]
0000FFFD
0000FFFF
LS_CHARAC 0000000000
3333333333222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
222222222222222222222222222222222
000000000000000000000000000000000
SPACE
2
0
Active calls / events
No.... Type........ Name..........................
Programm
Include Line
1 FUNCTION CEI0_DDB_HAS_VALUES_INTERNAL
SAPLCEI0
LCEI0U29 49
2 FUNCTION QMCF_CONFIGURATION_READ
SAPLQMCF
LQMCFU02 61
3 FUNCTION QMCF_SPECIFICATION_CONFIG_READ
SAPLQMCF
LQMCFU01 60
4 FUNCTION QPAP_PLAN_READ
SAPLQPAP
LQPAPU02 297
5 FUNCTION QEEV_TABLES_GENERATE
SAPLQEEV
LQEEVU01 118
6 FORM MERKMALSSAETZE_ANLEGEN
SAPLQPL1
LQPL1F12 85
7 FORM ST_RECHNE_571
SAPLQPL1
LQPL1F1L 26
8 FORM OK_PROBENBERECHNUNG
SAPLQPL1
LQPL1F1W 23
9 FORM FCODE_BEARBEITEN
SAPLV00F
LV00FF0F 97
10 FUNCTION SCREEN_SEQUENCE_CONTROL
SAPLV00F
LV00FU02 46
11 FORM FCODE
SAPLQPL1
LQPL1F2D 61
12 MODULE (PAI) FCODE
SAPLQPL1
LQPL1I0P 11
Internal notes
The termination occurred in the function "getwa_abswa" of the SAP
Basis System, specifically in line 1003 of the module
"//bas/46D/src/krn/runt/abgetwa.c#20".
The internal operation just processed is "LOOP".
The internal session was started at 20071228111310.
Active calls in SAP kernel
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App : disp+work.EXE (pid=500)
When : 12/28/2007 11:16:13.65
Threads : 2
Computer Name : ELEPRDCI
User Name : prdadm
Number of Processors: 16
Processor Type: x86 Family 15 Model 4 Stepping 8
Windows Version : 5.2 Current Build: 3790
Stack Dump for Thread Id a5c
eax=00000000 ebx=000003a8 ecx=00000e58 edx=00000000 esi=000003a8 edi=00000000
eip=7c82ed54 esp=03138cc4 ebp=03138d34 iopl=0 nv up ei ng nz ac po cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000297
function : KiFastSystemCallRet
7c82ed54 c3 ret
7c82ed55 8da42400000000 lea esp,[esp] ss:03138cc4=7c822124
7c82ed5c 8d642400 lea esp,[esp] ss:40cd7cc3=????????
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
03138d34 77e6ba12 000003a8 0001d4c0 00000000 03138d6c ntdll!KiFastSystemCallRet
03138d48 00baaa71 000003a8 0001d4c0 77bf1d88 00000002 kernel32!WaitForSingleObject
03138d6c 004d113b 004d10fc 77bf1d88 77bf1d88 77bf1d88 disp+work!
04b5ffb8 77e66063 00215740 00000000 00000000 00215740 MSVCRT!endthreadex
04b5ffec 00000000 77bcb4bc 00215740 00000000 00000000 kernel32!GetModuleFileNameA
List of ABAP programs affected
Type
Program
Gen. date time
LoadSize
Prg
SAPLQPL1
17.09.2006 09:35:11
479232
Prg
SAPMSSYD
14.08.2000 15:39:21
16384
Prg
SAPFSYSCALLS
21.12.1999 19:32:31
7168
Prg
CL_EXITHANDLER================
18.12.2004 13:14:45
13312
Prg
CL_ABAP_TYPEDESCR=============
04.01.2000 19:06:00
17408
Prg
CL_ABAP_ELEMDESCR=============
04.01.2000 19:06:00
13312
Prg
CL_ABAP_DATADESCR=============
04.01.2000 19:06:00
11264
Prg
CL_ABAP_REFDESCR==============
04.01.2000 19:06:00
14336
Prg
CL_ABAP_STRUCTDESCR===========
04.01.2000 19:06:00
16384
Prg
CL_ABAP_COMPLEXDESCR==========
04.01.2000 19:06:00
11264
Prg
CL_ABAP_TABLEDESCR============
04.01.2000 19:06:00
16384
Prg
CL_ABAP_CLASSDESCR============
04.01.2000 19:06:00
23552
Prg
CL_ABAP_OBJECTDESCR===========
04.01.2000 19:06:00
28672
Prg
CL_ABAP_INTFDESCR=============
04.01.2000 19:06:00
21504
Prg
IF_EX_INSPECTIONLOT_UPDATE====
13.07.2002 00:12:42
5120
Typ
SXS_INTER
30.11.1998 15:55:16
1024
Prg
SAPLSEXV
17.09.2006 08:50:01
155648
Prg
SAPLSXCH
18.12.2004 13:22:27
80896
Typ
V_EXT_ACT
14.10.1999 22:16:55
2048
Prg
CL_EX_INSPECTIONLOT_UPDATE====
13.07.2002 00:12:42
26624
Prg
SAPLV00F
08.03.2001 10:01:57
68608
Typ
T185E
15.07.1997 16:57:08
2048
Typ
T185F
14.08.1997 21:32:52
2048
Typ
T185
16.08.2000 11:43:40
3072
Typ
T185V
10.11.1999 17:45:26
4096
Typ
TQ01
14.02.1998 14:07:17
2048
Prg
SAPLSTXD
17.09.2006 08:53:44
406528
Prg
SAPCNVE
04.01.2000 19:06:37
7168
Prg
SAPLLANG
04.01.2000 19:06:49
9216
Prg
SAPLV01Z
17.09.2006 09:34:42
210944
Prg
SAPLCLFM
17.09.2006 09:34:56
688128
Prg
SAPLCUOB
17.09.2006 09:18:21
34816
Prg
SAPLCLSE
13.02.2005 06:50:14
177152
Prg
SAPLCTMS
17.09.2006 09:34:59
942080
Prg
SAPLCTCV
17.09.2006 09:27:23
192512
Prg
SAPLCTCF
12.02.2005 20:42:31
24576
Prg
SAPLV01P
17.09.2006 09:34:42
166912
Prg
SAPLMFAW
18.12.2004 14:02:28
51200
Typ
TFAWY
29.07.1998 19:48:52
2048
Typ
TFAWL
29.07.1998 19:48:49
2048
Typ
TFAWX
29.07.1998 19:48:51
2048
Typ
TFAW
29.07.1998 19:48:45
2048
Prg
RDDFIE00
04.01.2000 19:06:11
19456
Prg
SAPLQAST
13.02.2005 07:23:55
28672
Prg
SAPLBSVA
17.09.2006 09:02:09
270336
Prg
SAPLQSTA
20.01.2000 10:08:08
26624
Typ
TQ01A
29.07.1998 19:56:34
2048
Prg
SAPLOMCV
04.01.2000 19:06:50
14336
Typ
TMCNV
24.02.1999 03:33:25
2048
Prg
SAPLSCNT
15.11.2001 05:19:20
28672
Prg
SAPLSVSM
15.11.2001 05:19:20
25600
Prg
SAPLSGUI
15.11.2001 05:19:20
33792
Prg
SAPLSTTM
17.09.2006 08:49:52
83968
Prg
SAPLSBDC
17.09.2006 08:46:17
66560
Prg
CL_DATAPROVIDER===============
15.11.2001 05:19:18
50176
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Prg
SAPLSTUP
17.09.2006 08:46:10
96256
Prg
SAPLCNDP
17.09.2006 08:53:21
201728
Prg
SAPFGUICNTL
18.12.2004 11:31:41
20480
Prg
SAPLOLEA
12.07.2002 21:39:11
81920
Prg
SAPLSFES
17.09.2006 08:53:22
164864
Prg
SAPLGRFC
12.07.2002 21:39:11
16384
Prg
SAPSHDTV
18.12.2004 12:16:52
36864
Typ
SHDSTU
14.12.1998 23:15:34
1024
Typ
SHDSTCIU
14.12.1998 23:15:34
1024
Prg
CL_GUI_PROPS_CONSUMER=========
18.12.2004 11:27:30
26624
Prg
CL_DYNAMIC_GUI_EXTENSIONS=====
11.02.2000 14:36:06
55296
Prg
CL_GUI_DATAMANAGER============
18.12.2004 11:34:01
82944
Prg
/1BCDWBEN/SAPLQEN0000
13.07.2002 02:11:40
51200
Prg
SAPLSENA
04.01.2000 19:06:53
28672
Prg
SAPLQELA
17.09.2006 09:27:48
415744
Typ
QALS
13.07.2002 00:12:42
27648
Prg
SAPLQAUT
13.02.2005 01:25:27
177152
Prg
SAPLSWUG
17.09.2006 08:53:33
264192
Typ
SWOTOBJID
04.05.1995 15:20:52
2048
Typ
SWHACTOR
04.04.1995 16:18:07
1024
Prg
CL_GOS_MANAGER================
17.09.2006 08:53:30
24576
Prg
CL_GOS_VIEW_MANAGER===========
21.12.1999 19:23:29
29696
Typ
SGOS_MVOBJ
01.12.1999 08:16:05
2048
Prg
SAPLSUU1
17.09.2006 08:53:37
183296
Typ
USR02
15.11.2001 05:09:06
5120
Typ
USREFUS
18.12.2004 11:18:28
1024
Prg
SAPLTHFB
17.09.2006 08:53:29
270336
Typ
BORIDENT
28.08.1997 08:38:50
1024
Prg
CL_GOS_TOOLBOX_MODEL==========
17.09.2006 08:53:30
39936
Typ
SGOS_MODL
08.02.2000 16:42:30
3072
Prg
SAPLBDLS
14.08.2000 15:20:53
13312
Typ
T000
11.09.1997 10:17:18
3072
Prg
CL_GOS_PUBLICATION============
17.09.2006 08:53:30
24576
Prg
CL_GUI_OBJECT=================
15.11.2001 05:19:18
187392
Prg
CL_GUI_CFW====================
18.12.2004 13:28:20
195584
Typ
TOLE
29.07.1998 19:56:01
2048
Prg
SAPLSGOSHIST
17.09.2006 08:53:33
56320
Prg
SAPFSGOS
08.11.2003 23:57:36
13312
Typ
SGOSHIST
14.10.1999 22:09:01
2048
Prg
SAPLURFC
04.01.2000 19:08:13
14336
Prg
CL_GOS_STARTER================
09.12.1999 13:49:28
21504
Prg
CL_GUI_CONTROL================
08.11.2003 23:57:31
117760
Prg
CL_GUI_TOOLBAR================
15.11.2001 05:19:18
72704
Prg
CL_GUI_GOS_CONTAINER==========
01.02.2000 10:16:37
38912
Typ
CFW_LINK
01.12.1999 12:16:48
2048
Prg
CL_GUI_CONTAINER==============
15.11.2001 05:19:18
58368
Prg
SAPLCNTH
08.11.2003 23:56:48
26624
Prg
SAPLSCONTROLINFO
04.01.2000 19:06:52
13312
Prg
SAPLSCONTROLSTATUSCHECK
04.01.2000 19:06:52
10240
Typ
USR05
09.07.1997 23:46:52
1024
Typ
CNTLWARN
25.01.1999 13:09:44
2048
Prg
SAPLICON
17.09.2006 08:39:01
25600
Prg
%_CICON
14.08.2000 15:39:36
55296
Typ
JSTO
27.08.1994 20:32:55
2048
Typ
JEST
27.08.1994 20:32:50
2048
Prg
SAPLAIEV
15.11.2001 05:18:17
14336
Prg
CL_OS_TRANSACTION_END_NOTIFIER
18.12.2004 13:21:30
8192
Typ
LFA1
13.07.2002 01:08:16
12288
Prg
SAPLCPDB
17.09.2006 09:17:36
113664
Typ
PLKO
15.01.1999 22:26:42
9216
Prg
SAPLCCPR
17.09.2006 09:09:14
231424
Typ
TCC08
17.03.1999 16:30:21
4096
Typ
AEEF
13.02.2005 06:49:14
3072
Typ
TCC10
23.04.1998 14:45:07
2048
Typ
TCCET
28.08.1997 09:33:24
1024
Typ
TCCEP
20.08.1998 11:28:15
2048
Typ
TCCER
10.11.1998 05:49:03
2048
Typ
TCCETT
14.02.1998 12:45:20
1024
Typ
TCCEPT
14.02.1998 12:45:07
1024
Typ
TCCERT
17.03.1999 16:24:38
2048
Typ
TCCS01
27.08.1999 18:28:00
1024
Prg
SAPLCCHO
17.09.2006 09:18:17
55296
Prg
SAPLCPTA
17.09.2006 09:09:03
122880
Prg
SAPLCQTA
17.09.2006 09:34:41
88064
Typ
TQ33
10.07.1997 00:12:25
2048
Typ
TQ30
15.04.1998 00:38:23
3072
Typ
TQ30T
14.02.1998 14:11:06
2048
Prg
SAPLCV141
17.09.2006 09:18:22
86016
Typ
DRAD
01.12.1999 15:17:34
3072
Prg
SAPLBSVT
16.08.2000 11:43:43
18432
Prg
SAPLSMSG
18.12.2004 13:27:29
108544
Typ
TJ05
30.11.1993 16:45:10
1024
Typ
TJ01
01.03.1999 13:50:12
4096
Typ
TJ07
30.11.1993 16:45:13
1024
Typ
TJ06
30.11.1993 16:45:11
1024
Typ
TJ03
16.08.2000 11:43:42
2048
Prg
SAPFGUICNTL_CFW
15.11.2001 05:19:19
17408
Prg
CL_GUI_DOCKING_CONTAINER======
15.11.2001 05:19:18
50176
Prg
SAPLQBCK
17.09.2006 09:27:37
106496
Typ
QINF
09.12.1999 19:04:48
5120
Typ
MTQSS
23.04.1998 14:51:52
4096
Prg
SAPLMAQM
17.09.2006 09:35:30
61440
Typ
T001W
18.11.1998 16:27:15
1024
Typ
T001K
01.02.2000 14:56:09
3072
Prg
SAPLMG21
17.09.2006 09:34:30
159744
Typ
MARA
17.09.2006 09:17:34
15360
Prg
SAPLMG22
17.09.2006 09:17:36
115712
Typ
MARC
04.01.2000 18:04:45
23552
Typ
RMQEA
13.08.1997 12:52:02
9216
Typ
TJ02
27.03.1996 18:28:28
1024
Typ
TJ02T
14.02.1998 13:40:18
2048
Typ
TJ04
30.11.1993 16:45:08
2048
Prg
SAPLKDIC
04.01.2000 19:06:48
17408
Prg
SAPLSDTO
04.01.2000 19:06:52
25600
Typ
DD07T
12.05.1997 16:45:51
2048
Prg
SAPLCSCE
04.01.2000 19:06:44
8192
Typ
T024E
10.12.1998 18:01:35
2048
Prg
SAPLSCVU
17.09.2006 08:50:02
59392
Typ
T006A
28.08.1997 09:04:18
2048
Typ
OLE_PA
04.04.1995 16:02:19
2048
Typ
ARFCRDATA
12.07.2002 21:39:11
3072
Typ
SWCBCONT
14.02.1998 10:14:45
2048
Typ
OLE_VERBS
04.04.1995 16:02:20
1024
Prg
SAPLSDSD
17.09.2006 08:53:36
437248
Typ
DDSHIFACE
20.08.1998 10:51:59
2048
Typ
DFIES
15.01.1999 16:49:52
6144
Typ
DDSHFPROP
20.08.1998 10:51:57
2048
Typ
DDSHSELOPT
20.08.1998 10:52:01
2048
Prg
SAPLSDNT
18.12.2004 12:05:44
188416
Prg
SAPLSDIF
18.12.2004 13:03:59
256000
Typ
T006
29.07.1998 19:25:31
3072
Prg
SAPLSCV0
17.09.2006 08:50:22
99328
Typ
TCA01
10.03.1999 18:31:19
5120
Typ
TCA02
14.02.1998 12:40:44
2048
Typ
TCA35
06.07.1998 20:51:04
2048
Typ
QMAT
27.08.1999 18:14:19
5120
Typ
TQ32
10.07.1997 00:12:23
2048
Prg
SAPLXQPL
17.09.2006 09:30:13
28672
Typ
TCA44
29.07.1998 19:44:06
2048
Prg
SAPLQPAP
17.09.2006 09:30:13
295936
Prg
SAPMSSY0
17.09.2006 08:53:44
69632
Prg
SAPLSNR3
17.09.2006 08:53:36
48128
Typ
TNRO
18.12.2004 13:02:43
4096
Prg
SAPLQEEV
17.09.2006 09:27:48
216064
Typ
QAPP
15.04.1998 00:12:33
7168
Typ
TQSS
20.01.2000 10:08:08
3072
Prg
SAPLQMCF
17.09.2006 09:34:35
46080
Prg
SAPLCEI0
03.12.2006 09:44:54
1121280
Prg
SAPLCUEV
13.07.2002 02:21:41
11264
Typ
IBINCOM
01.06.1999 11:56:27
2048
Typ
IBINCONF
01.06.1999 11:56:27
2048
Typ
IBSTCONF
01.06.1999 11:56:28
1024
Prg
IF_EX_CEI0_INVLD_POSSIBLE=====
12.02.2005 20:53:18
4096
Prg
CL_EX_CEI0_INVLD_POSSIBLE=====
12.02.2005 20:52:40
10240
Prg
CL_EXIT_MASTER================
01.02.2000 09:29:10
10240
Typ
V_EXT_IMP
14.10.1999 22:16:55
2048
Prg
SAPLCUCB
17.09.2006 09:34:59
199680
Typ
TCUIBSPECIAL
15.11.2001 05:31:05
1024
Prg
CL_CBASE======================
13.02.2005 07:14:09
95232
Typ
T371G
29.04.1998 10:42:48
1024
Prg
SAPLIBCO
13.02.2005 05:49:04
305152
Prg
SAPLIBXX
13.07.2002 02:21:41
12288
Prg
SAPLIBIBF
13.02.2005 06:58:29
177152
Prg
SAPLIBINF
13.02.2005 06:58:30
452608
Prg
CL_IBASE_STRUC================
13.07.2002 02:21:39
141312
Prg
CL_IBASE_STRUC_BUF============
13.02.2005 01:44:37
120832
Prg
CL_IBASE_STRUC_STAT===========
13.07.2002 02:21:39
9216
Prg
CL_IBASE_STRUC_BUF_IBSTREF====
13.02.2005 01:44:37
61440
Typ
IBINVAL
14.05.1998 22:39:25
2048
Prg
SAPLIBCU
13.07.2002 02:21:41
14336
Prg
SAPLIBCUT
13.07.2002 02:21:41
14336
Typ
T371B
14.05.1998 22:58:43
1024
Prg
CL_IBASE_SERVICE==============
13.07.2002 02:21:39
17408
Prg
CL_IBASE_T371D_BUF============
13.07.2002 02:21:39
15360
Typ
T371D
27.08.1999 18:19:44
2048
Prg
CL_IBASE_R3_MATERIAL==========
17.09.2006 09:33:39
99328
Typ
MAKT
28.08.1997 08:52:19
2048
Typ
ICON
03.01.1996 15:34:02
3072
Prg
IF_EX_CM_BADI_VERSION=========
12.07.2002 23:55:25
4096
Prg
CL_EX_CM_BADI_VERSION=========
12.07.2002 23:54:25
11264
Prg
CL_DEF_IM_CM_BADI_VERSION=====
12.07.2002 23:54:24
8192
Prg
SAPLASTAT_TRIG
18.12.2004 12:15:52
12288
Typ
ASTAT_TYP2
10.11.1998 05:35:18
1024
Typ
ASTAT_TYP1
30.11.1998 15:54:16
1024
Prg
IF_CM_BASELINE================
13.02.2005 06:50:14
40960
Prg
IF_IBASE_IBOF_TREE_OBJECT=====
13.02.2005 05:59:51
10240
Prg
IF_IBASE_INSTALL==============
13.07.2002 02:21:40
4096
Prg
IF_IBASE_MATERIAL=============
13.07.2002 02:21:40
4096
Prg
IF_IBASE_OBJECT===============
13.07.2002 02:21:40
5120
Prg
SAPLBOMA
01.02.2000 14:54:24
13312Hi Sanjay,
This dump generally occurs when there are inconsistencies between the name of the fields in the fieldcatalog and the names of the fields in the internal table. Please post ur code.(Assuming that this dump has occured in a Z* program)
Edited by: Rajesh on Dec 29, 2007 2:40 PM -
Urgent : short dump while executing prog
Dear Gurus,
While executing a program i am getting following errors :
Runtime Errors PXA_NO_FREE_SPACE
Date and Time 27.01.2008 15:17:34
Short dump has not been completely stored (too big).
Error analysis
Unable to load a program of 763904 bytes.
The PXA ('program execution area') was too small to hold all
currently active programs for all users.
At present, the size of the PXA is set at 144708 Kbytes.
The largest contiguous and unlocked memory chunk has 621568 bytes.
Please do the needful at earliest, coz its very urgent.
Looking forward to your earliest response.
Thanks & Regards,
Gulrez AlamHi Alam,
Contact your Basis team guys ASAP as there seems to be nothing wrong with the prog ....
There is some memory management issue.
Regards,
Raghav -
Short Dump "ITAB_DUPLICATE_KEY" while executing DTP
Hi all,
i am getting a short dump when i try to execute the DTP to Cube, following is the error details.
i could not analyze the reason, need your inputs on this.
Runtime Errors ITAB_DUPLICATE_KEY
Date and Time 02/08/2009 21:33:53
Short dump has not been completely stored (too big)
Short text
A row with the same key already exists.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLRSAODS" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An entry was to be entered into the table
"\FUNCTION=RSAR_ODS_GET\DATA=L_TH_ISOSMAP" (which should have
had a unique table key (UNIQUE KEY)).
However, there already existed a line with an identical key.
The insert-operation could have ocurred as a result of an INSERT- or
MOVE command, or in conjunction with a SELECT ... INTO.
The statement "INSERT INITIAL LINE ..." cannot be used to insert several
initial lines into a table with a unique key.
thanks,
RkHello Rk,
What is the data source??
whats is your SP level??
Seems like the data source is not properly activated or duplicate entries exists in the system tables for the same data source...
If you have recently done a system copy??
Try to activate the data source again...if its from R/3 then replicate and activate it again...also if its a BW object then try to reactivate it as well.
Thanks
Ajeet -
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 -
Short dump with error :TSV_TNEW_INDEX_NO_ROLL_MEMORY
This is the error that i'm getting
ABAP runtime errors TSV_TNEW_INDEX_NO_ROLL_MEMORY
Occurred on 29.01.2007 at 20:27:13
>> Short dump has not been completely stored. It is too big.
No roll storage of length 64094208 available for internal table index.
What happened?
Each transaction requires some main memory space to process
application data. If the operating system cannot provide any more
space, the transaction is terminated.
Please advice.
Points Assured
Regards,
Ravikanth.It is as it says - a problem of not enough (ROLL) memory.
- You can ask basis to look into it - whether ROLL memory on app server can be increased.
- You can run whatever you are running at a time when the load on the system is less.
- You can check the code that runs to see why it should look for so much memory - maybe you can change the code so it uses less memory. -
HELP!
I am trying to install BI Content on a newly installed netweaver Box. We are running BI 7.0 with SP 15 and BI_CONT 703 SP 5. This is the error:
Runtime Errors ASSIGN_LENGTH_0
Date and Time 2008/02/18 12:55:36
Short dump has not been completely stored (too big)
Short text
Program error: ASSIGN with length 0 in program "SAPLSNR3".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSNR3" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Tried to create a field with length 0. This is not
possible.
Error analysis
In an ASSIGN statement in the program "SAPLSNR3" a field symbol with
length 0 should have been created. However, this is not possible.
length 0.
This is not possible.
Trigger Location of Runtime Error
Program SAPLSNR3
Include LSNR3F01
Row 178
Module type (FORM)
Module Name LOCAL_BUFFER
Line SourceCde
148 ID 'NONRSWAP' FIELD TNRO-NONRSWAP.
149 IF SY-SUBRC .
180 * Funktionsbaustein kann beendet werden
181 P_EXIT = YES.
182 EXIT.
183
184 ELSEIF SY-SUBRC = 4.
185 * Das Intervall wurde nicht gefunden
186 MESSAGE E751 RAISING INTERVAL_NOT_FOUND WITH P_OBJECT P_SUBOBJECT
187 P_NR_RANGE_NR TNRO-CODE.
188 ELSEIF SY-SUBRC = 19.
189 * Der Nummernkreis ist nicht intern
190 MESSAGE E752 RAISING NUMBER_RANGE_NOT_INTERN.
191 ELSEIF SY-SUBRC = 15.
192 * Overflow
193 IF NOT TNRO-NONRSWAP IS INITIAL.
194 MESSAGE E028 WITH BNRIV-FROMNUMBER BNRIV-TONUMBER
195 P_OBJECT RAISING INTERVAL_OVERFLOW.
196 ENDIF.
197 ELSEIF SY-SUBRC = 11.Problem:
When trying to collect BI objects prior to installing (activate) for use in BI (TCODE: RSA1) a short dump would be thrown when 'in and out' objects were selected. No short dump was thrown for demo objects when source system was set to local.
Reason:
The objects tracking sequence numbers for incoming BI transports from external systems were not correctly set. The sequences should have been set with a valid range of 1 to 9999999999 however the sequences were either missing or set to 0. This was a problem with the BI server (EPSAND), the CRM server was functioning correctly.
Why this happened:
Unknown. Perhaps a bug in a service pack. This error appears to be very uncommon. The error being thrown was a generic error thus difficult to trace to the actual problem.
How the problem was fixed:
(1) Using TCODE: SNUM set intervals for objects: BI_TS, BI_TSDTEL, BI_TSDOMA and BI_CS. These objects should each be set as follows:
No. From Number To Number Currenct Number
01 0000000001 9999999999 1
(2) Then there was also a second unrelated bug which is fixed in latest SAP_BW support package (SP 0014, released: January 2008). We couldn't risk the support package so a single note: 1102743 was applied. -
Short Dump - GETWA_NOT_ASSIGNED - Flexible upload of RFD
Hi,
SEM 6.0 / BI 7.0
When i try to do a Flexible upload for a sample RFD, i get the following dump:
Runtime Errors GETWA_NOT_ASSIGNED
Date and Time 11/25/2008 16:22:01
Short dump has not been completely stored (too big)
Short text
Field symbol has not yet been assigned.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_UC_TASK_EXECUTION==========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
You attempted to access an unassigned field symbol
(data segment 32776).
This error may occur if
- You address a typed field symbol before it has been set with
ASSIGN
- You address a field symbol that pointed to the line of an
internal table that was deleted
- You address a field symbol that was previously reset using
UNASSIGN or that pointed to a local field that no
longer exists
- You address a global function interface, although the
respective function module is not active - that is, is
not in the list of active calls. The list of active calls
can be taken from this short dump.
Trigger Location of Runtime Error
Program CL_UC_TASK_EXECUTION==========CP
Include CL_UC_TASK_EXECUTION==========CM02V
Row 155
Module type (METHOD)
Module Name COMPARE_OLD_AND_NEW_DOCS
Flexible upload - Delete all / Cumulative
Has anyone encountered this type of dump before?
My Observation
(Data Rows contain the following columns - Item / Company / Trading partner / PV LC)
When i give a trading partner which is not defined in the system, the system is interpreting the header row & data rows. Also, it gives an error message for each row.
But,
When i give a trading partner which is defined in the system, or when i remove the trading partner column in total, it throws the above short dump.
The breakdown category defined in the system are Trading partner & Movement type.
Both, have the breakdown type 1. (optional breakdown, initialized value allowed).
Pls note that after several permutations & combinations - to trace the error, i have removed all the columns & kept the minimum required (Item / Company / Trading partner / PV LC).
Appreciate your comments / inputs.
Thanks!
KumarHi Kumar,
The note refers to FINBASIS 300 release.
In the present system we have, it is FINBASIS 600.
I raised an OSS message.
Anyway, implementation of the note helped me with all releases.
But, first of all, I mentioned another remedy that you may see here:
SPRO: SEM/Business Analytics -> Fin. Basis -> Master Data Framework -> System Settings -> Profile Parameter Setting.
It's about setting parameter for ABAP shared memory on the server. If you do not set this parameter to 200-300 MB, you constantly will have the errors like I mentioned while trying to save master data. Did you read my previous message carefully and look at this hint?
In case of breakdown type 1 - the upload should happen - if we dont specify any values for the breakdown category. Pls confirm.
- Confirmation. The system will accept any value, including null.
Is it true that we cannot load RFD data (with both movement type & trading partner information), in one go? If yes, what is the reason behind it.
- No confirmation. Where is it from? I always do such a load. -
Short dump in Production system !!!
Hi Experts,
We have getting a short dump for all actions in Production system. Suppose if we use se38 and tried to press display it shows a short dump error. Despite when we tried to use tcodes or using LSMW or try to execute a program or like this all type of actions its throws a short dump error. Dont know what is the reason behind that since the short dump is not the defined the reason for the dumb. Have any of you experts got this type of experience?. Pls give your ideas. Thanks in advance.Hello Kavi,
Contact your basis team. SNAP is a table which holds all ABAP dump. It looks like SNAP table is full and cannot accomodate new entries.
In any production enviornment, the SNAP entires will be deleted regularly and only dumps for the last 8 days will be available
Check if any job(SM36 or table tbtcp) is running for this program RSSNAPDL in your production system.
Thanks -
Hi All,
While saving or activating infocube transformations in BI development system getting abap short dump.
Short dump:
Runtime Errors ASSERTION_FAILED
Date and Time 04.08.2009 12:35:44
Short dump has not been completely stored (too big)
Short text
The ASSERT condition was violated.
What happened?
In the running application program, the ASSERT statement recognized a
situation that should not have occurred.
The runtime error was triggered for one of these reasons:
- For the checkpoint group specified with the ASSERT statement, the
activation mode is set to "abort".
- Via a system variant, the activation mode is globally set to "abort"
for checkpoint groups in this system.
- The activation mode is set to "abort" on program level.
- The ASSERT statement is not assigned to any checkpoint group.
Error analysis
The following checkpoint group was used: "No checkpoint group specified"
If in the ASSERT statement the addition FIELDS was used, you can find
the content of the first 8 specified fields in the following overview:
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
Trigger Location of Runtime Error
Program CL_RSTRAN_GEN_STEPGRP=========CP
Include CL_RSTRAN_GEN_STEPGRP=========CM00O
Row 19
Module type (METHOD)
Module Name OPEN_IF
Source Code Extract
Line SourceCde
1 METHOD open_if.
2
3 DATA:
4 ls_step_gen TYPE ty_s_gen_param_step.
5
6 READ TABLE o_t_step_gen INTO ls_step_gen
7 WITH TABLE KEY r_step_ = i_r_step_.
8 ASSERT sy-subrc = 0.
9 IF ls_step_gen-r_step_exe IS BOUND.
10 EXIT.
11 ENDIF.
12
13 IF o_if = if_rstran_gen_root=>c_s_status-open.
14 r_true = rs_c_false.
15 ELSEIF o_if = space.
16 r_true = rs_c_true.
17 o_if = if_rstran_gen_root=>c_s_status-open.
18 ELSE.
>>>>> ASSERT 1 = 2. "Invalid call
20 ENDIF.
21
22 ENDMETHOD.
Can anybody tell me why it is throwing short dump in this case.
Suggest me necessary actions to resolve this issue.
Thanks,Hi Shiva,
Let me explain my problem.
I have one infocube, two transformations. In the infocube I have added few master data objects directly into the corresponding dimensions and mapped to read from master data with current date.
Now I am changing Current date to End date in the transformations. After changing Current date to End date from Calendar Month or Calendar Day activating the transformations. While activating the transformations getting short dump.
Here I am using time dependent master data.
Thanks -
TSV_TNEW_PAGE_ALLOC_FAILED - error -Short Dump - Storage Problems
Dear Gurus,
I am new at SAP Basis, can you please help with the following;
One of our FI System Analyst is running a FI report that gives the followin error:
ABAP runtime errors TSV_TNEW_PAGE_ALLOC_FAILED
Occurred on 30.04.2008 at 11:11:14
>> Short dump has not been completely stored. It is too big.
Please helpIs the report a standart report or a custom one?
If custom, then the report might be using too much memory. You have to look into the report to optmize it. -
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 'Table does not exist in database'
Hello All,
When a report is executing it is going to short dump by saying 'Table does not exist in database'. As per the short dump analysis this issue is happening because of the following Native SQL statement statement :
Program : %_T050N0 (This is a dynamic program generating by SAP )
Form Name : DYN_LIC_SEL_TOT
exec sql performing LOOP_MOVE_WRITE_ISAP.
select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty into :dcat-lplate, :dcat-matnr,
:dcat-werks, :dcat-charg, :dcat-holdflag,
:dcat-qty from ZLICENSE_R2 where itm_num = :p_matnr and
model_lot = :p_charg
endexec.
As per the customer this issue occurring since they migrated the SAP back-end data base from Oralce to DB6. Here I felt that ZLICENSE_R2 is not migrated from the Oracle to DB6. But as per the BASIS Team, even this table was not maintained in Oracle also. If the table was not maintained in the Oracle, this issue should have been there even before migration also.
Following is the short dump details:
Short text
Table does not exist in database.
What happened?
The table or view name used does not
exist in the database.
The error occurred in the current database connection "DEFAULT".
What can you do?
Check the spelling of the table names in your report.
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_NATIVE_SQL_ERROR', was not
caught in
procedure "DYN_LIC_SEL_TOT" "(FORM)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Triggering SQL statement: "select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty from ZLICENSE_R2 where itm_num = ? and model_lot = ? "
Database error code: "-204"
Could you please let me know what might be the reason for this issue.
Many Thanks in Advance.Transaction SE11, input ZLICENSE_R2 for table name, and display the table. Did the table display? If not, that is the main problem.
If the table displays, go to menu item Utilities -> Database Object -> Database Utility
In the resulting screen, under the "Status" fields, you should see text "Exists in the database." If you don't, then the table exists in the dictionary, but doesn't exist in the database system. Click the "Create database table" button and then you should be able to run the program.
You may need basis team's help to carryout some of these actions. -
CX_SY_FILE_OPEN_MODE - short dump on production but not in Dev and Test
Hello,
I'm getting the follwoing short dump in production when I run the program which writes the data to application server. I have open data set and close data set. Same program when I in development and test I do not get any short dump. Can any know what could be cause for this.
CX_SY_FILE_OPEN_MODE
Copy paste of error analysis from ST22 short dump -
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_FILE_OPEN_MODE', was not
caught in
procedure "DATA_UPLOAD_APP_SERVER" "(FORM)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
When accessing the file "/bw/FTPOUT/BPR/OTHER/test.csv", the system recognized
that this file is
not open. Therefore, the file cannot be accessed.The file could not be OPENed in your production system for a variety of reasons - no authorization, file doesn't exist etc. You should have check sy-subrc right after OPEN DATASET and if not zero, yous should not TRANSFER or READ the file and instead you should have given a message with sy-msgid and sy-msgno which would give you the reason. The dump here is simply saying that OPEN is unsuccessful, so any subsequent READ or TRANSFER would throw runtime dump, if done after an unsuccessful OPEN.
-
Buffer Table Not Up To Date Short Dump When Publishing Change Version of Bid Invitation
Hi experts,
We are running SRM 5.5 with Support Level 16.
We have a bid invitation for which a user is trying to publish a Change Version. This bid contains two bid outlines, with one line item in each bid outline:
ITEM 1: HIER (Bid Outline)
ITEM 2: Line Item
ITEM 3: HIER (Bid Outline)
ITEM 4: Line Item
However, upon clicking on the Check or Publish button, the system throws a CX_BBP_PD_ABORT exception short dump. The reason for the exception given in ST22 is "Buffer table not up to date".
Due to organisational system security restrictions, I am unable to copy-paste the dump from ST22, so I will be typing out some of the details here.
Transaction: BBP_BID_INV
Program: SAPLBBP_PDH
Screen: SAPLBBP_BID_INV_1000
Termination occurred in the ABAP program "SAPLBBP_PDH" - in "BBP_PD_ABORT". The main program was "SAPLBBP_BID_INV".
In the source code you have the termination point in line 73.
Active Calls/Events
(formatted below as "No: Type: Name")
24: Function: BBP_PD_ABORT
23: Form: ABORT
22: Form: ITMADM_UPDATE
21: Form: ITMADM_MAINTAIN_SINGLE
20: Form: ITEM_F_CHECK_FROM_WTAB
19: Form: ITEMLIST_F_CHECK
18: Function: BBP_ITEMLIST_CHECK
17: Form: PROCDOC_DB_CHECK
16: Form: PROCDOC_CHECK
15: Function: BBP_PROCDOC_CHECK
14: Form: SSIS_DOCUMENT_CHECK_COMPLETE
13: Form: STATUS_SET_AND_INTERNAL_SAVE
12: Form: PROCDOC_UPDATE
11: Function: BBP_PROCDOC_UPDATE
10: Form: CHANGE_VERSION_UPDATES_ACTIVE
9: Function: BBP_PDCV_UPDATE_ACTIVE
8: Form: PROCDOC_CHECK
7: Function: BBP_PROCDOC_CHECK
6: Function: BBP_PD_BID_CHECK
5: Form: FCODE_DOCUMENT_CHECK
4: Form: FCODE
3: Function: BBP_BID_PROCESS
2: Form: PROCESS
1: Module (PAI): PROCESS
The ABORT subroutine is being called in Step 22 (ITMADM_UPDATE), at the following line:
* parent guids have to be identical ...
if gt_itmadm-parent <> w_itmadm-parent.
perform abort.
endif.
Upon tracing the variable values in the ST22 dump, it appears the program terminates when processing line 3 (i.e. the second Bid Outline). It appears that the first Bid Outline processes fine.
In the iteration for Line 3, the dump provides that gt_itmadm-parent contains the GUID to the Change Version document header, whereas w_itmadm-parent contains the GUID to the original Bid Invitation document header, resulting in a mismatch and subsequently program termination.
We have tried to replicate this bid invitation in our Development environment, but when executing, both gt_itmadm-parent and w_itmadm-parent contain GUIDs to the Change Version document header, hence the program does not abort.
Any suggestions would be greatly appreciated.
Thanks!
Best regards,
Kwong HowHi Janu,
For Note 1561750, I have looked at the Correction Details and observed that it makes changes to an IF-ELSE block, but will result in the same path of code execution as before. I.e., the Note changes the code from "IF a THEN b, ELSE c" to just "c", but according to my code trace, we are already executing the "ELSE c" block in its current state.
We will look further into Note 1877600. The unfortunate situation here is that since we are unable to replicate this issue in our Development/QA environment, and the Note description does not explicitly fit the situation we are facing, we need to be very sure that the Note can address the issue before bringing it into Production.
Otherwise, we will raise a message as suggested.
Thank you so much for your help!
Best regards,
Kwong How
Maybe you are looking for
-
How to determine the last backup time?
On my iPhone 4 I sync it to iTunes on my IMAC. I hit backup and it says "Backing up my iPhone" I then want to see the date and time of the last backup? How do I do that? I right click on the iPhone in Itunes and select "Restore from Backup" and the l
-
What can I do for an Ipod that won't update, won't allow you to eject it, and can't reset either? I can simply unplug it from my pc and after a while it runs down and works fine after a charge. Wanting to clear data and sell but nothing seems to work
-
I have an app that does NOT run properly on my iPad2. My husbnd has the SAME app and his works just fine. I want the app GONE, I don't want to just "hide" it. I'd like to redownload the app. I believe I just got a bad download of the file. After
-
Unable to install java app in 6500c through pc sui...
handset: 6500c upgraded to latest firmware v08.30 pcsuite: on xp upgraded to latest version verson 7.0.8.2 issue: coundn't install java app through pc suite application installer, but wap donwload installation is ok. When connected, I couldn't see in
-
Storyboards via Google sheets + Indesign link
Hello. I'm in Visual Effects, and am used to rigid pipelines, and workflows. One of the most annoying problems I've yet to solve is on the subject of storyboards, and pitches for my presentations. Indesign has always played an integral role in des