ODS activation, short dump COMPUTE_INT_PLUS_OVERFLOW. How to solve?

Hello Gurus,
We are on BW 3.1.
We have an issue - ODS activation failed due to a short dump.
Runtime Error COMPUTE_INT_PLUS_OVERFLOW
Exception CX_SY_ARITHMETIC_OVERFLOW
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
In the current program "SAPLRSSM_PROCESS",
using + or 'ADD' to add the values 2137304138 and 12410267 resulted in a
value greater than 2147483647 or samller than -2147483648. This
leads to a whole number overflow.
Could you please guide me to solve this?
Please let me know if you need more details.
Thanks,
raj

This dump is happening because of the overflow of the size assigned for the variable.
This dump can be avoided by changing the declaration of the variable definition.
DATA: variable_name type p decimals 0.
OR
DATA: varibale_name(25) type n decimals 0
Try this. This will resolve your dump.
regards,
brijesh

Similar Messages

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 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
13312

Hi 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

Short Dump in BI 7.0,While Remodelling the Infocube

Hi Experts
I got the below short dump in BI 7.0 while remodelling infocube to add a new time char (0CALMONTH2)
Please update me what is wrong
Runtime Errors GETWA_NOT_ASSIGNED
Date and Time
Short text
Field symbol has not yet been assigned.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_RSCNV_ADD_CHAR=============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.
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:
"GETWA_NOT_ASSIGNED" " "
"CL_RSCNV_ADD_CHAR=============CP" or "CL_RSCNV_ADD_CHAR=============CM002"
"IF_RSCNV_OPERATION~CONVERT"
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 "CL_RSCNV_ADD_CHAR=============CP" -
in "IF_RSCNV_OPERATION~CONVERT".
The main program was "RADGENREP ".
In the source code you have the termination point in line 23
of the (Include) program "CL_RSCNV_ADD_CHAR=============CM002".
The program "CL_RSCNV_ADD_CHAR=============CP" was started as a background job.
Job Name....... "ZC13_32/ZCM_INSERT"
Job Initiator.. "GHANTAK"
Job Number..... 10521300
Source Code Extract
Line
SourceCde
1
METHOD if_rscnv_operation~convert.
2
*CALL METHOD SUPER->IF_RSCNV_OPERATION~CONVERT
3
EXPORTING
4
 I_R_OLD =
5
CHANGING
6
 C_R_NEW =
7
8
FIELD-SYMBOLS: <l_s_oldtable> TYPE ANY.
9
FIELD-SYMBOLS: <l_s_newtable> TYPE ANY.
10
FIELD-SYMBOLS: <l_fillfield> TYPE ANY.
11
FIELD-SYMBOLS: <l_addfield> TYPE ANY.
12
DATA: l_r_fillfield TYPE REF TO data.
13
DATA: l_r_addfield TYPE REF TO data.
14
15
TRY.
16
ASSIGN i_r_old->* TO <l_s_oldtable>.
17
ASSIGN c_r_new->* TO <l_s_newtable>.
18
19
ASSIGN COMPONENT p_fillfieldnm OF STRUCTURE <l_s_oldtable> TO <l_fillfield>.
20
ASSIGN COMPONENT p_addfieldnm OF STRUCTURE <l_s_newtable> TO <l_addfield>.
21
22
GET REFERENCE OF <l_fillfield> INTO l_r_fillfield.
>>>>>
GET REFERENCE OF <l_addfield> INTO l_r_addfield.
24
25
IF NOT p_constval IS INITIAL.
26
fill constant
27
CALL METHOD cl_rscnv_operation=>fill_const
28
EXPORTING
29
i_newiobj = p_add_char
30
i_constval = p_constval
31
i_fieldtype = o_fieldtype
32
CHANGING
33
c_r_newfield = l_r_addfield.
34
35
36
ELSEIF NOT p_attriobj IS INITIAL AND NOT p_ofiobjnm IS INITIAL.
37
fill using attribute of characteristic
38
ASSIGN i_r_old->* TO <l_s_oldtable>.
39
ASSIGN COMPONENT p_fillfieldnm OF STRUCTURE <l_s_oldtable> TO <l_fillfield>.
40
GET REFERENCE OF <l_fillfield> INTO l_r_fillfield.
41
CALL METHOD read_attr
42
EXPORTING

Hi,
i mean to say, just come out the transaction & try again..............
or else u can check the short dump in ST22...........
Regards,
SD

DBIF_REPO_SQL_ERROR short dumps while activating data in ODS

Hi All,
We are using BW3.5 with Oracle 9.2 on AIX 5.3 box, from the past few days we are getting DBIF_REPO_SQL_ERROR short dumps frequently while activating data in ODS.
Runtime Error          DBIF_REPO_SQL_ERROR
Date and Time          08.01.2008 13:01:08
     1. A printout of the problem description (short dump)
        To obtain this, select in the current display "System->List->
        Save->Local File (unconverted)".
     2. A suitable printout of the system log
        To obtain this, call the system log through transaction SM21.
        Limit the time interval to 10 minutes before and 5 minutes
        after the short dump. In the display, then select the function
        "System->List->Save->Local File (unconverted)".
     3. If the programs are your own programs or modified SAP programs,
        supply the source code.
        To do this, select the Editor function "Further Utilities->
        Upload/Download->Download".
     4. Details regarding the conditions under which the error occurred
        or which actions and input led to the error.
     Internal call code.........: "[REPO/*/43/LOAD/CX_SY_OPEN_SQL_DB=============CP
     Please check the entries in the system log (Transaction SM21).
     You may able to find an interim solution to the problem
     in the SAP note system. If you have access to the note system yourself,
     use the following search criteria:
     "DBIF_REPO_SQL_ERROR" C
     "SAPLRSSM_PROCESS" or "LRSSM_PROCESSF04"
     "CHECK_IF_ANALYZE_IS_NESSESSARY"
System environment
    SAP Release.............. "640"
    Application server....... "psapdb"
    Network address.......... "158.58.65.11"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00CD615C4C00"
    Character length......... 16 Bits
    Pointer length........... 64 Bits
    Work process number...... 22
    Short dump setting....... "full"
    Database server.......... "psapdb"
    Database type............ "ORACLE"
    Database name............ "BWP"
    Database owner........... "SAPBWP"
    Character set............ "C"
    SAP kernel............... "640"
    Created on............... "Oct 29 2006 20:49:57"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
    Patch level.............. "155"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
     10.2.0.."
    SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory usage.............
Roll..................... 16192
EM....................... 16759424
Heap..................... 0
Page..................... 24576
MM Used.................. 6604384
MM Free.................. 1772536
SAP Release.............. "640"
User and Transaction
    Client.............. 200
    User................ "R3REMOTE"
    Language key........ "E"
    Transaction......... " "
    Program............. "SAPLRSSM_PROCESS"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
Information on where terminated
    The termination occurred in the ABAP program "SAPLRSSM_PROCESS" in
     "CHECK_IF_ANALYZE_IS_NESSESSARY".
    The main program was "RSPROCESS ".
    The termination occurred in line 1143 of the source code of the (Include)
     program "LRSSM_PROCESSF04"
    of the source code of program "LRSSM_PROCESSF04" (when calling the editor
     11430).
    The program "SAPLRSSM_PROCESS" was started as a background job.
    Job name........ "BI_PROCESS_ODSACTIVAT"
    Job initiator... "RPRIYANKA"
    Job number...... 02010102
Also we have a failed job here. Here is the job log.
Job log overview for job:    BI_PROCESS_ODSACTIVAT / 02010102
Date       Time     Message text
08.01.2008 13:01:00 Job started
08.01.2008 13:01:00 Step 001 started (program RSPROCESS, variant &0000000000188, user ID R3REMOTE)
08.01.2008 13:01:02 Activation is running: Data target HBCS_O25, from 1,758 to 1,767
08.01.2008 13:01:02 Data to be activated successfully checked against archiving objects
08.01.2008 13:01:02 SQL: 01/08/2008 13:01:02 R3REMOTE
08.01.2008 13:01:02 ANALYZE TABLE "/BIC/AHBCS_O2540" DELETE
08.01.2008 13:01:02 STATISTICS
08.01.2008 13:01:02 SQL-END: 01/08/2008 13:01:02 00:00:00
08.01.2008 13:01:02 SQL: 01/08/2008 13:01:02 R3REMOTE
08.01.2008 13:01:02 BEGIN DBMS_STATS.GATHER_TABLE_STATS ( OWNNAME =>
08.01.2008 13:01:02 'SAPBWP', TABNAME => '"/BIC/AHBCS_O2540"',
08.01.2008 13:01:02 ESTIMATE_PERCENT => 1 , METHOD_OPT => 'FOR ALL
08.01.2008 13:01:02 INDEXED COLUMNS SIZE 75', DEGREE => 1 ,
08.01.2008 13:01:02 GRANULARITY => 'ALL', CASCADE => TRUE ); END;
08.01.2008 13:01:05 SQL-END: 01/08/2008 13:01:05 00:00:03
08.01.2008 13:01:05     SQL-ERROR: 603 ORA-00603: ORACLE server session terminated by fat al error
08.01.2008 13:01:05 System error: RSDU_ANALYZE_TABLE_ORA/ ORACLE
08.01.2008 13:01:08 ABAP/4 processor: DBIF_REPO_SQL_ERROR
08.01.2008 13:01:08 Job cancelled
Listener is working fine, Checked the RFC connections, Tried restarting the system, tried adding space to the TEMP tablespace as well as PSAPBWP, but they didn't work.
Please help.

The problem got solved as there were DB errors like ORA-01114: IO error writing block to file 256 (block # 126218).
Here the point to be notes is file 256. The number greater than 255 indicates a temp datafile. This indicates an issue with PSAPTEMP tablespace. When checked on PSAPTEMP tablespace, one of the filesystems where one temp data file sitting was full. The filesystem was 100% full. This will prevent the temp datafile to grow and shrink as and when required.
So, adding more space to the filesystem solved the problem.
Thanks to everyone who have shown interest in solving my problem.

Short dump (DBIF_RSQL_INVALID_RSQL) during activating ODS

Hello Experts,
I found short dump during activating ODS.
The error message in short dump:
Runtime Error: DBIF_RSQL_INVALID_RSQL
Except.: CX_SY_OPEN_SQL_DB
The termination occurred in the ABAP program "GP7WIVS2MDWGSTMN3ICFDKNAH65" in "ACTIVATE_SIDS".
The main program was "RSODSACT1 ".
I add one InfoObject in the ODS. After activating related objects, I loaded data into the data target.
Data seemed to be loaded correctly, but couldn't be activated.
Any suggestion on this?
-WJ-

Hi,
Please chekc the following SAP Notes you will find solution
Note 908599 - Runtime error SAPSQL_INVALID_FIELDNAME during activation
Note 612995 - P13:ODS:Data activation in bckgrnd always ends 'successfully
Note 1175860 - P19: DSO: SDL: Automatic update after activation
Note 1113603 - P17:DSO:Postprocessing ODS - activating and updating
Note 378447 - Correction: hierarchies do not become green
Note 1272738 - P21:DSO: Activation and automatic updating
Note 794584 - P26:Timestamp field empty in RS2NDPROCPROT after ODSACTIVATE
Note 800086 - P26: ODS activation: Status field in table RS2NDPROCPROT
Note 856292 - P28: Automatic functions: No lock obtained for ERSICENQ
Thanks
Reddy

RE: Short dump after activation of BADI

Hi all,
We are getting short dumps in all the transactions after activating the BADI 'BADI_LAYER'
We are not able to execute any of the transactions.
The details of runtimeerror
Runtime Errors RAISE_EXCEPTION
Date and Time 30.07.2007 09:58:06
Short text
Exception condition "SINGLE_EXIT_MULTIPLY_ACTIVE" 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 "SINGLE_EXIT_MULTIPLY_ACTIVE".
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" "SINGLE_EXIT_MULTIPLY_ACTIVE"
or
"SAPMF05A " "SINGLE_EXIT_MULTIPLY_ACTIVE"
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... "sapdevp"
Network address...... "192.168.0.205"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x Intel 80686"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "SAPDEVP"
Database type..... "ORACLE"
Database name..... "TDV"
Database user ID.. "SAPSR4"
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...... 6271344
Heap.... 0
Page.... 57344
MM Used. 1728072
MM Free. 360856
User and Transaction
Client.............. 400
User................ "FIUSER01"
Language key........ "E"
Transaction......... "FB50 "
Program............. "CL_EXITHANDLER================CP"
Screen.............. "SAPMF05A 1010"
Screen line......... 7
Information on where terminated
Termination occurred in the ABAP program "CL_EXITHANDLER================CP" -
in "GET_INSTANCE".
The main program was "SAPMF05A ".
In the source code you have the termination point in line 145
of the (Include) program "CL_EXITHANDLER================CM001".
Source Code Extract
Line
SourceCde
115
SELECT SINGLE is_impl FROM badiisimpled INTO is_impl
116
WHERE badi_name = mig_badi_name.
117
IF sy-subrc NE 0.
118
 not yet filled
119
is_impl = cl_enh_badi_tool_utilities=>update_badiisimpled( mig_badi_name ).
120
ENDIF.
121
122
IF is_impl = 'X'.
123
 ok at least one implementation found
124
act_imp_existing = 'X'.
125
ENDIF.
126
127
ENDIF.
128
ENDIF.
129
ELSE.
130
131
check how many implementations exist for an exit
132
CALL METHOD cl_badi_flt_data_trans_and_db=>act_imps_per_flt_val
133
EXPORTING
134
runtime_call = seex_true
135
exit_name = exit_name
136
EXCEPTIONS
137
singular_exit_multiply_active = 1
138
no_active_implementation = 2
139
only_default_implementation = 3
140
OTHERS = 4.
141
CASE sy-subrc.
142
WHEN 0.
143
act_imp_existing = seex_true.
144
WHEN 1.
>>>>>
RAISE single_exit_multiply_active.
146
WHEN 2.
147
act_imp_existing = seex_false.
148
WHEN 3.
149
act_imp_existing = seex_false.
150
def_impl = seex_true.
151
WHEN 4.
152
RAISE data_incons_in_exit_managem.
153
ENDCASE.
154
155
new parameter considered for performance purposes
156
IF act_imp_existing = seex_true OR
157
def_impl = seex_true OR
158
null_instance_accepted = seex_false.
159
160
ok, then do your job
161
CREATE OBJECT exit TYPE (abs_type_classname).
162
CATCH SYSTEM-EXCEPTIONS move_cast_error = 1.
163
instance ?= exit.
164
ENDCATCH.
Contents of system fields
Name
Val.
SY-SUBRC
1
SY-INDEX
0
SY-TABIX
0
SY-DBCNT
2
SY-FDPOS
1
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
FSKB
SY-UCOMM
SY-TITLE
Enter G/L Account Document: Company Code TJ01
SY-MSGTY
S
SY-MSGID
B!
SY-MSGNO
015
SY-MSGV1
00001140
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20070730
SY-UZEIT
095806
SY-XPROG
SY-XFORM
Active Calls/Events
No. Ty. Program Include Line
Name
5 METHOD CL_EXITHANDLER================CP CL_EXITHANDLER================CM001 145
CL_EXITHANDLER=>GET_INSTANCE
4 METHOD CL_EXIT_MASTER================CP CL_EXIT_MASTER================CM004 2
CL_EXIT_MASTER=>CLASS_CONSTRUCTOR
3 METHOD CL_EX_FI_HEADER_SUB_1300======CP CL_EX_FI_HEADER_SUB_1300======CM003 53
CL_EX_FI_HEADER_SUB_1300=>IF_EX_FI_HEADER_SUB_1300~PUT_DATA_TO_SCREEN_PBO
2 FORM SAPMF05A MF05AF00_D0100_PRE_APPL_SUB_2 50
D0100_PRE_APPL_SUB_PBO
1 MODULE (PBO) SAPMF05A MF05AO00_D0100_PRE_APPL_SUB 10
D0100_PRE_APPL_SUB
Chosen variables
Name
Val.
No. 5 Ty. METHOD
Name CL_EXITHANDLER=>GET_INSTANCE
EXIT_NAME
BADI_LAYER
44445445452222222222
2149FC19520000000000
00000000000000000000
00000000000000000000
NULL_INSTANCE_ACCEPTED
2
0
0
0
ACT_IMP_EXISTING
2
0
0
0
INSTANCE
F0000000
F0000000
%_SPACE
2
0
0
0
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
SEEX_TRUE
X
5
8
0
0
SYST-REPID
CL_EXITHANDLER================CP
4454545444444533333333333333334522222222
3CF589481E4C52DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
<%_TABLE_BADIISIMPLED>
SY-REPID
CL_EXITHANDLER================CP
4454545444444533333333333333334522222222
3CF589481E4C52DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY-SUBRC
1
0000
1000
SY-XPROG
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
No. 4 Ty. METHOD
Name CL_EXIT_MASTER=>CLASS_CONSTRUCTOR
%_SPACE
2
0
0
0
SYST-REPID
CL_EXIT_MASTER================CP
4454545544554533333333333333334522222222
3CF5894FD13452DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY-REPID
CL_EXIT_MASTER================CP
4454545544554533333333333333334522222222
3CF5894FD13452DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CL_EXIT_MASTER=>LAYER_EXIT
F0000000
F0000000
%_DUMMY$$
2222
0000
0000
0000
No. 3 Ty. METHOD
Name CL_EX_FI_HEADER_SUB_1300=>IF_EX_FI_HEADER_SUB_1300~PUT_DATA_TO_SCREEN_PBO
IM_BKPF
TJ01 2007SA00000000200707300400000000000000000000000000000000000000
2225433222222222233335433333333333333333333333333333333333333333333333333333333222222222222222
0004A01000000000020073100000000200707300400000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
IM_X_NO_INPUT
2
0
0
0
FLT_VAL
IN
44
9E
00
00
<EXIT_OBJ>-IMP_CLASS
<FLT_CACHE_LINE>-OBJ
|
| F0000000 |
| F0000000 |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| 0000 |
| 0000 |
| ME->INSTANCE_BADI_TABLE |
| Table[initial] |
| <EXIT_OBJ> |
| ??? |
| ?????? |
| ?????? |
| <%_L001> |
| ??? |
| ?????? |
| ?????? |
| RSJOBINFO |
| 00000000000000 ## |
| 2222222222222222222222222222222233333333333333222222222222222222222222222222222200 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| SY-REPID |
| CL_EX_FI_HEADER_SUB_1300======CP |
| 4454554454444455554533333333334522222222 |
| 3CF58F69F851452F352F1300DDDDDD3000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| <%_L001>-METHOD_NAME |
| ??? |
| ?????? |
| ?????? |
| EXIT_OBJ_TAB |
| Table[initial] |
| SY-SUBRC |
| 1 |
| 0000 |
| 1000 |
| ME |
|
F0000000
C0003000
SXRT_TRUE
X
5
8
0
0
No. 2 Ty. FORM
Name D0100_PRE_APPL_SUB_PBO
*BSEG-STBUK
2222
0000
0000
0000
%_DUMMY$$
2222
0000
0000
0000
SY-REPID
SAPMF05A
5454433422222222222222222222222222222222
310D605100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SYST-REPID
SAPMF05A
5454433422222222222222222222222222222222
310D605100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
KDBTAB-DMBTR
0.0.0.0.0.0.1.
0000000
000000C
%_SPACE
2
0
0
0
KDPTAB-BELNR
2222222222
0000000000
0000000000
0000000000
KDPTAB-GJAHR
0000
3333
0000
0000
0000
KDPTAB-BUZEI
000
333
000
000
000
KDBTAB-XRUND
2
0
0
0
SPACE
2
0
0
0
F05ACTRL
2
0
0
0
SYST
######################################ð#######################################~######### C####
00000000000000000000000000000000000000F0000000000000000000000000000000000000107000000050240000
000000200000000000002010100010000000000000000010400000000000000000000000000080E000200080030100
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000040000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000000000D000000C
BSED
0000000# ############## 0000000000000000
2222222222222222233333330200000000000000223333333333333333222222222222222222222222222222222222
00000000000000000000000000000C000000C000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000C0000000C000000C000000000000000000000000000000000000000000000000000000
SY-SUBRC
1
0000
1000
G_APPL_SUB_ACTIVE
X
5
8
0
0
CHAR_X
X
5
8
0
0
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
BKPF-BUKRS
TJ01
5433
4A01
0000
0000
BKPF
TJ01 2007SA00000000200707300400000000000000000000000000000000000000
2225433222222222233335433333333333333333333333333333333333333333333333333333333222222222222222
0004A01000000000020073100000000200707300400000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
G_APPL_SUB_DISABLE
2
0
0
0
T005-INTCA
IN
44
9E
00
00
No. 1 Ty. MODULE (PBO)
Name D0100_PRE_APPL_SUB
C_FIELD_DIALOG_ALL
BUTTON_DIALOG_ALL
4555445444444544422222222222222222222222222222222222222222222222222222222222222222222222222222
2544FEF491CF7F1CC00000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Internal notes
The termination was triggered in function "ab_jfune"
of the SAP kernel, in line 2561 of the module
"//bas/700_REL/src/krn/runt/abfunc.c#10".
The internal operation just processed is "FUNE".
Internal mode was started at 20070730095806.
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=4436)
When : 7/30/2007 9:58:6.359
Threads : 2
Computer Name : SAPDEVP
User Name : SAPServiceTDV
Number of Processors: 4
Processor Type: x86 Family 6 Model 15 Stepping 6
Windows Version : 5.2 Current Build: 3790
State Dump for Thread Id 250c
eax=34d52300 ebx=000003f8 ecx=0001ccc0 edx=34d039e0 esi=000003f8 edi=00000000
eip=7c82ed54 esp=053fceb4 ebp=053fcf24 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:053fceb4=7c822124
7c82ed5c 8d642400 lea esp,[esp] ss:6627b4c7=00002100
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
053fcf24 77e6ba42 000003f8 0001d4c0 00000000 053fcf5c ntdll!KiFastSystemCallRet
053fcf38 0100b3aa 000003f8 0001d4c0 00000001 7c38b5c8 kernel32!WaitForSingleObject
053fcf5c 0055b4ac 0055b4e5 7c38b5c8 7c38b5c8 7c38b5c8 disp+work!NTDebugProcess
053fcf60 0055b4e5 7c38b5c8 7c38b5c8 7c38b5c8 01d35ab0 disp+work!NTStack
053fcf7c 0055b519 7c38b5c8 00000000 008536a8 7c38b5c8 disp+work!CTrcStack2
053fcf88 008536a8 7c38b5c8 00000000 005f0059 00300030 disp+work!CTrcStack
053fcfac 008569fa 6d1d037c 0000001b 00000000 01cfc168 disp+work!rabax_CStackSave [abrabax.c (6871)
053fd084 006aaaf4 0134837c 0134835c 00000a01 235f1640 disp+work!ab_rabax
053fd0c0 0067bb56 00000003 34cf5708 00000000 053fd128 disp+work!ab_jfune
053fd128 007af183 00000000 34cf5708 053fd274 34cf8c26 disp+work!ab_extri
053fd13c 00837a37 00000000 34cf7dd6 00596fa0 34cf68b4 disp+work!ab_xevent
053fd148 00596fa0 34cf68b4 000003db 34cf7dd6 00000000 disp+work!ab_dstep
053fd274 00597fa1 34cf5708 34cf5708 053ffd04 00597b13 disp+work!dynpmcal
053fd284 00597b13 34cf5708 34cf5708 00000003 053ffd04 disp+work!dynppbo0
053fd2a0 0056dcf1 34cf5708 0006e768 00000000 0000000c disp+work!dynprctl
053ffd04 00471848 00000013 07de0048 00000001 00494960 disp+work!dynpen00
053ffd14 00494960 0000000c 00000000 00000003 00000002 disp+work!Thdynpen00
053ffee0 00494ee2 00000001 00000000 00000000 00430000 disp+work!TskhLoop
053fff00 00421150 00000000 00000000 7ffd8000 053fff60 disp+work!ThStart
053fff14 00401080 00000003 003f6850 00000001 00000000 disp+work!DpMain
053fff60 011a94a0 00000003 003f6850 003f78f8 01bd5000 disp+work!nlsui_main
053fffc0 77e523e5 00000000 00000000 7ffd8000 88602680 disp+work!wmainCRTStartup
053ffff0 00000000 011a935d 00000000 00905a4d 00000003 kernel32!IsProcessorFeaturePresent
State Dump for Thread Id 27bc
eax=00000001 ebx=00000103 ecx=fffffffe edx=003f01f8 esi=00000000 edi=00000000
eip=7c82ed54 esp=075dfec0 ebp=075dff04 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:075dfec0=7c821514
7c82ed5c 8d642400 lea esp,[esp] ss:6845e4d3=50004500
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
075dff04 010f7ffc 000006c0 00000000 00000000 003f77d0 ntdll!KiFastSystemCallRet
075dff84 7c349565 00000000 00000000 00000000 0587ff08 disp+work!SigIMsgFunc
075dffb8 77e6608b 0587ff08 00000000 00000000 0587ff08 MSVCR71!endthreadex
075dffec 00000000 7c3494f6 0587ff08 00000000 00000000 kernel32!GetModuleFileNameA
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
SAPMF05A
0
22.05.2007
11:37:49
1563648
E
1
Prg
SAPMSSYD
0
10.01.2007
12:33:28
21504
E
2
Prg
SAPFSYSCALLS
0
09.09.2004
14:18:32
8192
E
3
Typ
TFDIR
0
13.02.2005
17:31:57
3072
4
Prg
SAPLAPAR_EBPP_SERVICES
4
03.01.2007
11:23:55
114688
E
5
Typ
T042ZEBPP
0
08.01.2002
14:42:24
2048
6
Typ
T020
0
24.02.1999
03:17:19
3072
7
Typ
RFOPT2
0
11.12.2003
15:00:17
5120
8
Prg
SAPFF001
0
22.05.2007
11:37:49
195584
E
9
Typ
SWOTOBJID
0
04.05.1995
15:20:52
2048
10
Prg
SAPLSWOR
10
10.01.2007
12:33:34
292864
E
11
Typ
TFBUF
0
30.11.1998
22:08:34
3072
12
Typ
ACC_KONTEXT
0
08.01.2003
17:30:26
3072
13
Typ
BKPF
0
13.03.2006
11:01:29
18432
14
Prg
SAPLFACSCORE
14
01.12.2006
22:00:12
13312
E
15
Typ
T001
0
25.08.2005
22:03:13
13312
16
Prg
SAPLACHD
16
03.01.2007
11:23:55
51200
E
17
Prg
SAPFSPOR
0
09.09.2004
14:18:32
15360
E
18
Prg
SAPLSCNT
18
18.02.2005
14:16:06
30720
E
19
Typ
DYCBOX
0
20.08.1998
11:16:53
3072
20
Prg
SAPLSVSM
20
18.02.2005
14:16:06
27648
E
21
Prg
SAPLSGUI
21
10.01.2007
12:33:33
82944
E
22
Prg
SAPLSTTM
22
05.07.2005
13:10:18
69632
E
23
Prg
SAPLSBDC
23
05.07.2005
13:10:18
44032
E
24
Prg
CL_DATAPROVIDER===============CP
24
28.02.2005
21:00:46
49152
E
25
Prg
%_CCNTL
24
18.02.2005
14:15:08
15360
E
26
Typ
OBJ_RECORD
0
14.02.1998
08:30:43
2048
27
Prg
SAPLSTUP
27
08.03.2005
19:04:31
73728
E
28
Prg
SAPLCNDP
28
01.12.2006
22:04:33
193536
E
29
Prg
SAPSHDTV
18
05.01.2005
16:26:16
33792
E
30
Typ
SHDSTU
0
14.12.1998
23:15:34
2048
31
Typ
SHDSTCIU
0
14.12.1998
23:15:34
2048
32
Prg
SAPFGUICNTL
0
18.02.2005
14:15:08
24576
E
33
Prg
SAPLOLEA
33
05.07.2005
13:10:18
96256
E
34
Prg
SAPLSFES
34
10.01.2007
13:26:20
256000
E
35
Prg
SAPLSPLUGIN
35
09.09.2004
14:18:36
8192
E
36
Typ
ARFCRDATA
0
13.02.2005
18:20:24
7168
37
Prg
SAPLGRFC
37
13.02.2005
18:20:25
16384
E
38
Typ
SWCBCONT
0
15.11.2000
17:55:11
3072
39
Typ
OLE_VERBS
0
04.04.1995
16:02:20
2048
40
Typ
OLE_PA
0
04.04.1995
16:02:19
2048
41
Typ
ACGL_HEAD
0
11.12.2003
14:59:21
8192
42
Typ
RF05A
0
11.04.2005
11:50:21
38912
43
Typ
TCURC
0
01.12.1999
12:14:40
2048
44
Prg
SAPLFAGL_ACTIVATION_SERVICES
44
30.04.2007
17:00:55
45056
E
45
Prg
SAPLSTR9
45
09.05.2006
10:39:47
39936
E
46
Prg
CONTEXT_X_TR_SYS_PARAMS
45
09.05.2006
10:39:47
40960
E
47
Typ
TCONT
0
09.09.2004
14:18:43
2048
48
Typ
CONTEXTB
0
09.09.2004
14:15:52
6144
49
Typ
FAGL_ACTIVEC
0
19.08.2004
16:55:10
5120
50
Typ
FAGL_CHECK_SETUP
0
11.12.2003
15:01:05
2048
51
Prg
SAPLSHD0
51
03.01.2007
06:52:22
232448
E
52
Prg
SAPLBFFM3
52
10.01.2007
13:15:21
169984
E
53
Typ
OFIWA
0
15.04.1998
00:11:05
2048
54
Typ
FTEXTS
0
20.08.2001
12:13:26
3072
55
Prg
SAPLITSR
55
10.01.2007
14:23:52
107520
E
56
Typ
FMRFC
0
13.08.1997
12:32:59
2048
57
Typ
TBE01
0
20.01.2003
16:41:38
2048
58
Typ
TBE31
0
03.09.1997
03:01:11
2048
59
Typ
TBE31
0
03.09.1997
03:01:11
2048
60
Typ
TBE11
0
03.09.1997
03:01:06
2048
61
Prg
CONTEXT_X_SP_INFO
55

Hello Sowmya
The BAdI BADI_LAYER is not defined for Multiple-Use (see checkbox on tabstrip Attributes).
Apparently you have created several implementation of this BAdI and activated several (at least 2) of these implementations.
If you inactivate all except a single implementation the BAdI (and all transactions using this BAdI) should work again.
Regards
Uwe

Dump error when doing ODS activation

Hi,
When doing to the ODS activation, out of 500 data packets 1 data packet is not updated its highlighting Red traffic light. After that i selected that incorrect data packet i given manual update sytem is gives ABAP runtime errror MESSAGE_TYPE_X. i checked in SM21 as well as ST22 also it was MESSAGE_TYPE_X.
Run-time error "MESSAGE_TYPE_X" occurred
> Short dump "090413 143857 ccdbwprd BIADMIN " generated
Run-time error "MESSAGE_TYPE_X" occurred
> Short dump "090413 144123 ccdbwprd BIADMIN " generated
Run-time error "MESSAGE_TYPE_X" occurred
> Short dump "090413 144435 ccdbwprd BIADMIN " generated
Transaction Canceled BT 510 ( )
Run-time error "MESSAGE_TYPE_X" occurred
> Short dump "090413 150322 ccdbwprd BIADMIN " generated
Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20090413150322ccdbwprd BIADMIN 0051 )
Run-time error "MESSAGE_TYPE_X" occurred
> Short dump "090413 150639 ccdbwprd BIADMIN " generated
Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20090413150639ccdbwprd BIADMIN 0051 )
Run-time error "MESSAGE_TYPE_X" occurred
> Short dump "090413 150837 ccdbwprd BIADMIN " generated
please give ur suggestion to solve this issue.
Thanks & Regards
Khamesh

please verify the note 852443

Short Dump when clicking on Reconstruction tab in ODS.

Hi,
I get a short dump with 'MESSAGE_TYPE_X' error when I click on the reconstruction tab in ODS
Error analysis
"MESSAGE_TYPE_X" " "
"SAPLRSS2" or "LRSS2U13"
"RSS2_PSA_NEW_OLD_DS"
Information on where terminated
    Termination occurred in the ABAP program "SAPLRSS2" - in "RSS2_PSA_NEW_OLD_DS".
    The main program was "RSAWBN_START ".
    In the source code you have the termination point in line 277
    of the (Include) program "LRSS2U13".
Code
274             if i_only_active is initial.
275               clear: l_s_psa_out-psa_tech, l_s_psa_out-psa_version.
276             else.
>>>>>               message x000.
278             endif.
279           endif.
280           case l_s_isosmap-issrctype.
Please let me know how to solve this issue.

Try checking note 948189.

How to keep short dumps for a longer time

Hi All,
I need to write a program to fetch all the below mentioned fields from the system dump tables and insert into a user defind table. Please help me with the code. Thanks in advance....
PROBLEM DESCRIPTION
ABAP runtime errors (also known as short-dumps) are kept in the system only for two days, mainly because every short-dump can use a lot of disk space depending on short-dump type. Problem is that this reduced time frame (two days) is not allowing us to focus in solve the more frequent ones and we do not have any statistic about:
    how many are we getting
    how often
    repetitive ones
PROPOSED SOLUTION
We need a program to be executed in a daily job right after midnight which will take the basic information of all todays short-dumps and store it in a custom table.
Information to be kept:
      DATE
      TIME
      HOST
      USER
      SYSTEM
      CLIENT
      ERROR ID
      TRANSACTION
      PROGRAM NAME
      PROGRAM NAME VERSION (TRANSPORT REQUEST NUMBER)
      PROGRAM NAME VERSION TIMESTAMP (transported to PPx)
      SCREEN
      SCREEN LINE
      MAIN PROGRAM NAME
      MAIN PROGRAM NAME VERSION (TRANSPORT REQUEST NUMBER)
      MAIN PROGRAM NAME VERSION TIMESTAMP (transported to PPx)
      PROGRAM LINE NUMBER AT TERMINATION
      SAP RELEASE
      SAP KERNEL
      PATCH LEVEL
      DATABASE VERSION
The program must have archiving capabilities implemented. In the month end run it will also perform the table house-keeping accordingly with a parameter like this:
     ERROR-ID
     MONTHS TO KEEP
We need to have the possibility of defining different retention periods for different kind of errors, for example our friend GETWA_TOO_MANY_SEGMENT could be stored for a year and a simple CONVT_NO_NUMBER only for a month. One of the parameters should be the default one, something like
        ERROR-ID **************
        MONTHS TO KEEP 01.

Aruna,
Following may be the action points for your requirements.
1. Create Custom table with all fields you required.
2. Create ABAP program to extract the data from SAP standard table where runtime error information is stored.
Like: select * from snap_beg into wa_snap_beg
          where seqno = '000'
          and   datum in s_datum
          and   uzeit in s_uzeit
          and   ahost in s_ahost
          and   uname in s_uname
          and   mandt in s_mandt.......
So SNAP_BEG is a table where you can find dump information.
After extracting the data from this table insert it into a Custom table which you have created in Step 1.
Use INSERT statement for this.
3. Create transaction for this report.
4. Schedule this program every day so that you will get all data into custom table.
I hope this will help you.
Regards,
Amey

Getting short dump at the time of loading data from R/3 to ODS

Hi BW Grurus,
I am trying to load data from R/3 to ODS, but after running for a few minutes it is getting into the short dump and displays the following run time error. So please give me solution how I can load data without getting short dump. I tried thrice but it is giving the same and failed.
Run time error : TSV_TNEW_PAGE_ALLOC_FAILED

Hi,
Check, is start routine or individual routine in present in update/transfer rule?
May be read large amount data (select * from) another ODS and put into internal table cause these type of error.
Regards,
Saran

Short Dump error while loading data from R/3 to ODS

Hello,
while trying to load data into the ODS from R/3 I get the following short dump error message. How do I carry out step 1 in the below procedure. Where do i find the Activate Function. And idea?
Thanks,
SD
                                                                                Diagnosis
Form routine CONVERT_ITAB_RFC is incorrect in transfer program
     GP4C0LOLZ6OQ70V8JR365GWNW3K .
System Response
The IDoc processing was terminated and indicated as incorrect. The IDoc
     can be reimported at any time.
Procedure
1. Go to the transfer rule maintenance for your InfoSource
         ZFIN_TR_FLQITEM_FI and the source system DA_M_10 and regenerate the
         transfer program using the function Activate. Remove possible syntax
         errors on the basis of your conversion routines.
2. Restart the processing of this IDoc.
3. If the error occurs again search for SAPNet R/3 notes, and create a
        problem message if necessary.
Edited by: Sebastian D'Souza on Jan 13, 2009 3:22 PM

Hi.......
Goto RSA1>> then to source system tab (on left side) >> double click on the desired source system...........Then on the right side you have the Datasource tree..........there search the datasource and activate.......Also u can Replicate the datasource again.......and activate the Transfer rules using the program : RS_TRANSTRU_ACTIVATE_ALL
After this operation when come back to source system (R/3).........I think the error log line will be disappeared from SM58......... Then repeat the load.........
Also u can try to Activate the infosource once...........in RSA1.........before repeating the load....
Hope this helps......
Regards,
Debjani....

How to deal with Short dump that restarts the index server?

Hi ,
I have been experiencing this problem whenever any exception occurs in my SQL SCRIPT procedure. For instance when there is a situation when I try to insert a value of 50 characters in length to a column with max size of 40 it throws a short dump and restarts the index server. I tried to insert the exception handling code as well but still the problem persists. Is there a way to solve this issue?

Hi Sudarshan
crashes are rather generic reactions of the system to virtually any kind of problem that may occur.
Memory shortage is one of the more common issues in current SAP HANA setups and SAP HANA development is heavily working on handling memory shortage situations more gracefully.
Massive over allocation of memory, for example by very large intermediate result sets or join result sets typically can be addressed by correcting the query or model that leads to the issue.
Anyhow, the initial post was not about a memory shortage but about a crash that seemed to have occurred with wrong data type handling.
These are two very different kinds of problems, so I am not really sure how your comment relates here.
- Lars

Reg : Short Dump While Activating Workflow

Hi All,
This morning I added a condition step in my workflow and created two custom methods in the corresponding BO and used them in the task. Initially when i made the changes in the workflow and tested it, it was working fine. But after sometime, when I did the necessary binding and tried to activate the workflow, the workflow started resulting in short dump.
Below is the dump analysis.
SAPSQL_ARRAY_INSERT_DUPREC
The ABAP/4 Open SQL array insert results in duplicate database records.
000310        L_OTYPE EQ ORG_OBJTYPE_WORKFLOW.
000320       LOOP AT ACT_LINES.
000330         MOVE-CORRESPONDING ACT_WFDKEY TO ACT_LINES.
000340         MOVE ACT_CLIENT TO ACT_LINES-CLIENT.
000350         MODIFY ACT_LINES.
000360       ENDLOOP.
000370     ELSE.
000380       MESSAGE E280 WITH L_OTYPE RAISING INVALID_OBJECT_TYPE.
000390     ENDIF.
000400
000410   *- insert lines table
------>     INSERT SWD_LINES CLIENT SPECIFIED FROM TABLE ACT_LINES.
000430     IF SY-SUBRC NE 0.
000440       MESSAGE E281 WITH SY-SUBRC 'SWD_LINES'
000450                    RAISING INTERNAL_DATABASE_ERROR.
000460     ENDIF.
000470
000480   *- commit
000490     IF DO_COMMIT NE ' '.
000500       COMMIT WORK.
000510     ENDIF.
000520
000530   ENDFUNCTION.
I tried searching sdn. But all other posts were related to passing entries from internal table to DB. Also I'm not even sure if i can raise a OSS, because a few minutes back the system was working fine and all of sudden this started happening.
So can you please guide me what I am missing and how can i fix this?
Thanks & Regards,
Raj

Hi Rick,
When I get acitvate the workflow, the workflow template is gettign active & saved and after that the system results into short dump. And also when i try creating a PR and test this workflow, in SWEL, i can see the below message in RFC status field.
The ABAP/4 Open SQL array insert results in duplicate database records..
I haven't done any duplicate binding. Also I checked what you suggested. Didn't work. Also checked my newly added code. But I'm not accessing database directly anywhere. All is done via SAP standard function module.
Even if i try to display this workflow in PFTC, the system is resulting in the same short dump.
What could be the reason?
Regards,
Raj
Edited by: Raj Karunanidhi on Feb 23, 2010 5:30 AM

How to find which Badi Implementation is causing Short Dump

Hi Experts,
We are getting short dump on IW32 transaction when the users hit SAVE button.
The Dump Details:
Runtime Errors SYNTAX_ERROR
Short text
Syntax error in program "WORKORDER_UPDATE==============CP ".
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_EX_WORKORDER_UPDATE========CP" had
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"WORKORDER_UPDATE==============CP " in include
"WORKORDER_UPDATE==============CM000 " in
line 12:
"The specified type cannot be converted into the target variable
The current ABAP program "CL_EX_WORKORDER_UPDATE========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
The following syntax error was found in the program
WORKORDER_UPDATE==============CP :
"The specified type cannot be converted into the target variables."
Information on where terminated
Termination occurred in the ABAP program "CL_EX_WORKORDER_UPDATE========CP" -
in "IF_EX_WORKORDER_UPDATE~AT_SAVE".
The main program was "SAPLCOIH ".
After going through the dump analysis, I found that there are around 25 BADI Implementations got created on Enhancement Spot "WORKORDER_UPDATE".
How to find out which BADI Implementations is causing this dump?
Please let me know.
Thanks.
Edited by: ravi kumar on Feb 22, 2011 1:12 PM

Yes, I tried the Active Calls Stack also. The Short Dump is occuring exactly at the line :-
method IF_EX_WORKORDER_UPDATE~AT_SAVE.
in Class:-
CL_EX_WORKORDER_UPDATE
I was informedby the user that this is working perfectly fine in DEV System. The Short Dump is occuring in SBX System.
When I executed the Class "CL_EX_WORKORDER_UPDATE" and Method "IF_EX_WORKORDER_UPDATE~AT_SAVE" via SE24 in SBX, I got the same dump. However it worked fine in DEV System.
I am wondering if the issue is with the Standard Program itself?
Any ideas?
Thanks a lot again.
Another thing is: It is short dumping even before calling any of the BADI Implementations.
Wanted to give some more info on this: I put a break point in Function "CO_ZV_ORDER_POST" after the CALL FUNCTION 'CO_BADI_GET_BUSINESS_ADD_IN'.
And the program dumps right after that when it calls the: CALL METHOD lp_badi_if->at_save.
Thanks.
Edited by: ravi kumar on Feb 22, 2011 1:51 PM
Edited by: ravi kumar on Feb 22, 2011 2:11 PM

ODS activation, short dump COMPUTE_INT_PLUS_OVERFLOW. How to solve?

Similar Messages

Maybe you are looking for