ST22 RUNTIME ERROR
Dear All,
i m getting dump in st22.DBIF_REPO_SQL_ERROR
but i m unable to understand this dump error.plz any1 tell me what is this ???
st22 dump log i have attached with it.
What happened?
The system is no longer linked to an ORACLE instance.
No further operations can be performed on the database.
Error analysis
The system attempted to access an ORACLE instance to which
it is no longer linked.
This situation may arise because the ORACLE instance
has been stopped due to an error or an external operation.
How to correct the error
Database error text........: "ORA-03114: not connected to ORACLE"
Triggering SQL statement...: "CX_SY_OPEN_SQL_DB=============CP "
The current status of the ORACLE instance cannot be determined.
It may be still inactive or the database administrator may have
restarted it.
In any case, all systems that have accessed the ORACLE instance
must be restarted after the ORACLE instance has been restarted.
If you were working on a central system, inform
your system administrator.
If you were working on an external local system, inform
the person responsible for this system.
If you were working on your own local system, restart
the system yourself.
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:
"DBIF_REPO_SQL_ERROR" " "
"RSRZLLG0_ACTUAL" or "RSRZLLG0_ACTUAL"
"START-OF-SELECTION"
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).
2. IS THIS IS RESPONSIBLE TRANSPORT COZ MY TRANSPORT IS NOT WORKING.
Regard's
Dear Bhaskar,
Thanc for ur reply.i check out in services one of my service
ORACLE JOB SCHEDULAR is showing cancelled...i have to restart that.
can u plz tell me what is function of this service...
Regard's
Similar Messages
-
error analysis as in ST22 TRANSACTION:
AN EXCEPTION OCCURED THE EXCEPTION ASSIGNED TO CLASS CX_SY_CONVERSION_NO_NUMBER WAS NOT CAUGHT WHICH LED TO AN ERROR. THE REASON FOR THIS EXCEPTION IS :
THE PROGRAM TRIED TO INTERPRET VALUE ':4' AS NUMBER SINCE THE VALUE CONTRAVENES THE CORRECT NUMBER FORMAT THIS WAS NOT POSSIBLE.
ATTACHED IS MY PROGRAM
REPORT ZVXR0303
LINE-COUNT 60(3)
LINE-SIZE 132
MESSAGE-ID VN.
Tables: VBEP, VBAP, NAST.
DATA: BEGIN OF HEADER,
ORDER(15) VALUE 'ORDER',
LINE(5) VALUE 'LINE',
MATERIAL(14) VALUE 'MATERIAL',
DUE(15) VALUE 'DUE (MAD)',
CREATED(10) VALUE 'CREATED',
QTY(10) VALUE 'QUANTITY',
KEY(5) VALUE 'KEY',
TYPE(5) VALUE 'TYPE',
END OF HEADER.
DATA: Begin of IDAT OCCURS 0,
VBELN LIKE VBAP-VBELN,
POSNR LIKE VBAP-POSNR,
werks LIKE VBAP-WERKS,
cuobj LIKE vbap-CUOBJ,
MBDAT LIKE vbep-mbdat,
ERDAT LIKE VBAP-ERDAT,
MATNR LIKE VBAP-MATNR,
KWMENG LIKE VBAP-KWMENG,
QTY TYPE I,
END of IDAT.
class cl_abap_char_utilities definition load.
constants: tab type c value cl_abap_char_utilities=>HORIZONTAL_TAB.
DATA: t_record(1000) TYPE C.
DATA: C_KWMENG(20) TYPE C.
data: OUTFILE(50) value '/usr/users/ftpsapfi/locks_540318'.
DATA: BEGIN OF TKOMCON OCCURS 50.
INCLUDE STRUCTURE CONF_OUT.
DATA: END OF TKOMCON.
DATA: iKEY TYPE I,
offset TYPE I,
KeyTypeLOC TYPE I,
KeyNumberLOC TYPE I,
type(15) TYPE C.
select-options: sVBELN FOR VBEP-VBELN obligatory,
sMAD FOR VBEP-MBDAT obligatory,
sERDAT FOR VBAP-ERDAT,
sMATNR FOR VBAP-MATNR,
sWERKS FOR VBAP-WERKS,
sKWMENG FOR VBAP-KWMENG.
SELECT
vbap~vbeln
vbap~POSNR
vbap~werks
vbap~cuobj
VBEP~MBDAT
VBAP~ERDAT
VBAP~MATNR
VBAP~KWMENG
INTO CORRESPONDING FIELDS of IDAT
FROM ( VBEP INNER JOIN VBAP ON vbepvbeln = vbapvbeln
AND vbepposnr = vbapposnr )
WHERE BMENG > 0
AND vbep~MBDAT IN sMAD
AND VBEP~VBELN in sVBELN
AND VBAP~werks IN sWERKS
AND VBAP~ERDAT IN sERDAT
AND VBAP~MATNR IN sMATNR
AND VBAP~KWMENG IN sKWMENG
AND VBAP~ABGRU = SPACE.
APPEND IDAT.
ENDSELECT.
PERFORM TOP-OF-PAGE.
if sy-batch = 'x'.
OPEN DATASET OUTFILE FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
TRANSFER t_record TO OUTFILE.
endif.
IF SY-SUBRC = 0.
LOOP at IDAT.
write IDAT-KWMENG DECIMALS 0 TO C_KWMENG.
REFRESH TKOMCON.
CALL FUNCTION 'VC_I_GET_CONFIGURATION'
EXPORTING
INSTANCE = idat-cuobj
LANGUAGE = NAST-SPRAS
TABLES
CONFIGURATION = TKOMCON
EXCEPTIONS
OTHERS = 4.
LOOP AT TKOMCON
WHERE ATNAM = 'S_SK_SPEC_KEY' OR ATNAM = 'S_MK_SPEC_KEY'
OR ATNAM = 'S_SK_CONSC_KEY' OR ATNAM = 'S_MK_CONSC_KEY'.
IF TKOMCON-ATNAM = 'S_SK_CONSC_KEY'
OR TKOMCON-ATNAM = 'S_MK_CONSC_KEY'.
KeyTYPELOC = 0.
keynumberloc = 2.
TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
PERFORM OUT-OF-RANGE-FOUND.
ENDIF.
ENDIF.
Else.
Offset = 0.
DO.
IF offset <= 9.
offset = offset + 1.
If TKOMCON-ATWRT+Offset(1) = ':'.
KeyTypeLOC = Offset + 1.
KeyNumberLOC = Offset + 3.
EXIT.
ENDIF.
ELSE.
EXIT.
ENDIF.
ENDDO.
TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
IDAT-KWMENG = TKOMCON-ATWRT(3).
PERFORM OUT-OF-RANGE-FOUND.
ENDIF.
ENDIF.
ENDIF.
ENDLOOP.
ENDLOOP.
ENDIF.
CLOSE DATASET OUTFILE.
FORM OUT-OF-RANGE-FOUND *
FORM OUT-OF-RANGE-FOUND.
WRITE: / IDAT-VBELN.
WRITE: 10 IDAT-POSNR.
WRITE: 20 IDAT-MATNR.
WRITE: 35 IDAT-MBDAT.
WRITE: 50 IDAT-ERDAT.
WRITE: 65(3) IDAT-KWMENG DECIMALS 0.
WRITE: 75 TKOMCON-ATWRT+KeyTypeLOC(6).
IF TKOMCON-ATNAM = 'S_SK_CONSC_KEY'
OR TKOMCON-ATNAM = 'S_MK_CONSC_KEY'.
WRITE: 85 'Consecutive'.
ELSE.
WRITE: 85 'Specific'.
ENDIF.
IF TKOMCON-ATNAM = 'S_SK_CONSC_KEY'
OR TKOMCON-ATNAM = 'S_MK_CONSC_KEY'.
TYPE = 'Consecutive'.
ELSE.
TYPE = 'Specific'.
ENDIF.
* PREPARING A RECORD TO BE SENT TO FILE
CONCATENATE
IDAT-VBELN
IDAT-POSNR
IDAT-MATNR
IDAT-MBDAT
IDAT-ERDAT
C_KWMENG
TKOMCON-ATWRT+KeyTypeLOC(6)
TYPE
INTO t_record SEPARATED BY tab.
if sy-batch = 'x'.
TRANSFER t_record TO OUTFILE.
endif.
ENDFORM.
FORM TOP-OF-PAGE *
FORM TOP-OF-PAGE.
WRITE: / 'ORDER'.
WRITE: 10 'LINE'.
WRITE: 20 'MATERIAL'.
WRITE: 35 'DUE (MAD)'.
WRITE: 50 'CREATED'.
WRITE: 65 'QTY'.
WRITE: 75 'KEY'.
WRITE: 85 'TYPE'.
PREPARING A RECORD TO BE SENT TO FILE
CONCATENATE
header-ORDER
header-LINE
header-MATERIAL
header-DUE
header-CREATED
header-QTY
header-KEY
header-TYPE
INTO t_record SEPARATED BY tab.
ENDFORM.
THIS IS WORKING FINE WITH DIFFERENT RANGES BUT WHEN I USE RANGE
Sales Order 1250000 TO 2250000
MAD 01/18/2005 TO 03/02/2005
Material LOCK9250FR TO LOCK9250XF
PLANT 4500
IT GIVES THE RUNTIME ERROR I MENTIONED ABOVE
ANY HELP WOULD BE GREATLY APPRECIATED
THANKS.HI ROB YOUR REPLY LOOKS TO BE VERY CLOSE OTHER GUYS SAID IT MIGHT BE PROBLEM WITH VARIABLE C_KWMENG BUT I REMOVED THAT PIECE OF CODE WITH C_KWMENG BUT STILL I WAS GETTING THE ERROR ATTACHED IS THE COMPLETE ERROR DETAILS FROM ST22
Runtime Errors CONVT_NO_NUMBER
Exception CX_SY_CONVERSION_NO_NUMBER
Occurred on 09/29/2005 at 14:33:21
Unable to interpret "04:" as a number.
What happened?
Error in ABAP application program.
The current ABAP program "ZVXR0303" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception will be dealt with in more detail
below. The exception, assigned to the class 'CX_SY_CONVERSION_NO_NUMBER', was
not caught, which
led to a runtime error. The reason for this exception is:
The program attempted to interpret the value "04:" as a number, but
since the value contravenes the rules for correct number formats,
this was not possible.
How to correct the error
Integers are represented in ABAP using a sequence of digits and, in some
cases, a preceding sign.
The system offers the following options for displaying floating point
numbers:
[mantissa]E[sign][exponent]
[whole number part].[fractional part]
e.g. -12E+34, +12E-34, 12E34, 12.34
If the error occurred in one of your own programs or in an SAP program
that you modified, try to correct it yourself.
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:
"CONVT_NO_NUMBER" CX_SY_CONVERSION_NO_NUMBERC
"ZVXR0303" or "ZVXR0303"
"START-OF-SELECTION"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "grrsap54"
Network address.......... "10.80.96.102"
Operating system......... "HP-UX"
Release.................. "B.11.11"
Hardware type............ "9000/800"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 3
Short dump setting....... "full"
Database server.......... "grrsap54"
Database type............ "ORACLE"
Database name............ "D01"
Database owner........... "SAPR3"
Character set............ "en_US.iso88591"
SAP kernel............... "640"
Created on............... "Aug 28 2005 20:25:49"
Created in............... "HP-UX B.11.00 A 9000/800"
Database version......... "OCI_920 "
Patch level.............. "88"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE
10.1.0.."
SAP database version..... "640"
Operating system......... "HP-UX B.11"
User, transaction...
Client.............. 050
User................ "NSHAKER"
Language key........ "E"
Transaction......... "SE38 "
Program............. "ZVXR0303"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "ZVXR0303" in
"START-OF-SELECTION".
The main program was "ZVXR0303 ".
The termination occurred in line 156 of the source code of the (Include)
program "ZVXR0303"
of the source code of program "ZVXR0303" (when calling the editor 1560).
Source code extract
Caution: Program has changed
Caution: At time of termination, Active source code no longer available
001260 ? TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
001270 ? IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
001280 ? iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
001290 ?
001300 ? IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
001310 ? OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
001320 ? PERFORM OUT-OF-RANGE-FOUND.
001330 ? ENDIF.
001340 ? ENDIF.
001350 ? Else.
001360 ? Offset = 0.
001370 ? DO.
001380 ? IF offset <= 9.
001390 ? offset = offset + 1.
001400 ? If TKOMCON-ATWRT+Offset(1) = ':'.
001410 ? KeyTypeLOC = Offset + 1.
001420 ? KeyNumberLOC = Offset + 3.
001430 ? EXIT.
001440 ? ENDIF.
001450 ? ELSE.
001460 ? EXIT.
001470 ? ENDIF.
001480 ? ENDDO.
001490 ?
001500 ? TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
001510 ?
001520 ? IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
001530 ? iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
001540 ? IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
001550 ? OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
? IDAT-KWMENG = TKOMCON-ATWRT(3).
001570 ? PERFORM OUT-OF-RANGE-FOUND.
001580 ? ENDIF.
001590 ? ENDIF.
001600 ? ENDIF.
001610 ? ENDLOOP.
001620 ? ENDLOOP.
001630 ? ENDIF.
001640 ? CLOSE DATASET OUTFILE.
001650 ?
001660 ? *----
001670 ? * FORM OUT-OF-RANGE-FOUND *
001680 ? *----
001690 ? * ........ *
001700 ? *----
001710 ? FORM OUT-OF-RANGE-FOUND.
001720 ?
001730 ? WRITE: / IDAT-VBELN.
001740 ? WRITE: 10 IDAT-POSNR.
001750 ? WRITE: 20 IDAT-MATNR.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 44
SY-TABIX 7 SY-DBCNT 1
SY-FDPOS 4 SY-LSIND 0
SY-PAGNO 2 SY-LINNO 18
SY-COLNO 94 SY-PFKEY
SY-UCOMM SY-TITLE Out of Range Keys
SY-MSGTY I SY-MSGID SF
SY-MSGNO 616 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
1 EVENT START-OF-SELECTION
ZVXR0303
ZVXR0303 156
Chosen variables
1 EVENT START-OF-SELECTION
ZVXR0303
ZVXR0303 156
%_SPACE
2
0
SY-REPID ZVXR0303
5555333322222222222222222222222222222222
A682030300000000000000000000000000000000
TKOMCON-ATWRT 04:XF1260
333543333222222222222222222222
04A861260000000000000000000000
KEYNUMBERLOC 5
0000
0005
SYST-REPID ZVXR0303
5555333322222222222222222222222222222222
A682030300000000000000000000000000000000
SY-LDBPG SAPDB__S
5454455522222222222222222222222222222222
31042FF300000000000000000000000000000000
IKEY 1260
000E
004C
KEYTYPELOC 3
0000
0003
SY ###,####################################
0002000000000001000000000000000000000000
000C00020007000E00000001000A000000000000
... + 40 ###########^###<########################
0000000000050003000100080000000000000009
00010004000E000C000200040000000000000000
... + 80 ########################################
0000000000000000000000000000000000000000
0000000000000000000A00000000000000000000
... + 120 #######################################_
0000000000000000000000000000000000010005
00000000000000000000000000000000000A000F
... + 160 ############ÿÿ¹°XC############# E2 X1
000000000000FFBB540000000000000222432253
0000000A0000FF90830040000C0000C000520081
... + 200 000 ####__S 050
3332222222220000555222222222222222223332
0000000000000000FF3000000000000000000500
... + 240 00
222223322222222
000000000000000
SVBELN IBT00012500000002250000
44533333333333333333333
92400012500000002250000
IDAT-KWMENG ########
00000000
0000000C
TKOMCON-ATWRT+0(3) 04:
333
04A
SYST ###,####################################
0002000000000001000000000000000000000000
000C00020007000E00000001000A000000000000
... + 40 ###########^###<########################
0000000000050003000100080000000000000009
00010004000E000C000200040000000000000000
... + 80 ########################################
0000000000000000000000000000000000000000
0000000000000000000A00000000000000000000
... + 120 #######################################_
0000000000000000000000000000000000010005
00000000000000000000000000000000000A000F
... + 160 ############ÿÿ¹°XC############# E2 X1
000000000000FFBB540000000000000222432253
0000000A0000FF90830040000C0000C000520081
... + 200 000 ####__S 050
3332222222220000555222222222222222223332
0000000000000000FF3000000000000000000500
... + 240 00
222223322222222
000000000000000
OUTFILE /usr/users/ftpsapfi/locks_540318
2777277677267776766266667533333322222222
F532F53523F64031069FCF3B3F54031800000000
... + 40
2222222222
0000000000
Application Calls
No dump information available
Application Information
No dump information available
Internal notes
The termination occurred in the function "ab_Move" of the SAP
Basis System, specifically in line 529 of the module
"//bas/640_REL/src/krn/runt/abmove1.c#6".
The internal operation just processed is "MOVE".
The internal session was started at 20050929142552.
Active calls in SAP kernel
( 0) 0x4000000001751924 CTrcStack2 + 0x2bc dw.sapD01_DVEBMGS00
( 1) 0x4000000001751658 CTrcStack + 0x18 dw.sapD01_DVEBMGS00
( 2) 0x4000000001db7478 rabax_CStackSave__Fv + 0x100 dw.sapD01_DVEBMGS00
( 3) 0x4000000001dc3abc ab_rabax + 0x1e1c dw.sapD01_DVEBMGS00
( 4) 0x4000000001b44cb4 ab_cnverr__FiPcPCvN21T2 + 0x18c dw.sapD01_DVEBMGS00
( 5) 0x40000000016c96f8 ab_Move + 0x1910 dw.sapD01_DVEBMGS00
( 6) 0x40000000016d4434 ab_jmove__Fv + 0x384 dw.sapD01_DVEBMGS00
( 7) 0x4000000001022348 ab_extri__Fv + 0x17a0 dw.sapD01_DVEBMGS00
( 8) 0x4000000001726dc8 ab_xevent__FPCc + 0x38 dw.sapD01_DVEBMGS00
( 9) 0x40000000019f7efc ab_trigg__Fv + 0x94 dw.sapD01_DVEBMGS00
(10) 0x40000000019dc9ec ab_run + 0xc4 dw.sapD01_DVEBMGS00
(11) 0x4000000000f65e0c N_ab_run + 0x14 dw.sapD01_DVEBMGS00
(12) 0x4000000000f5fa88 dynpmcal + 0x198 dw.sapD01_DVEBMGS00
(13) 0x4000000000f5d500 dynppai0 + 0x830 dw.sapD01_DVEBMGS00
(14) 0x4000000000f5b8b4 dynprctl + 0x43c dw.sapD01_DVEBMGS00
(15) 0x4000000000f56728 dynpen00 + 0x2118 dw.sapD01_DVEBMGS00
(16) 0x400000000102f1b4 Thdynpen00 + 0x69c dw.sapD01_DVEBMGS00
(17) 0x400000000102e1e4 TskhLoop + 0x523c dw.sapD01_DVEBMGS00
(18) 0x4000000001022f50 tskhstart + 0x1e0 dw.sapD01_DVEBMGS00
(19) 0x4000000000dce3c4 DpMain + 0x484 dw.sapD01_DVEBMGS00
(20) 0x40000000022784cc nlsui_main + 0x14 dw.sapD01_DVEBMGS00
(21) 0x4000000000a39534 main + 0x14 dw.sapD01_DVEBMGS00
(22) 0xc00000000000a588 $START$ + 0xa0 /usr/lib/pa20_64/dld.sl
List of ABAP programs affected
Type Program Gen. Date Time Load Size
Prg ZVXR0303 09/29/2005 14:25:42 39936
Prg SAPMSSY0 05/01/2005 00:21:19 66560
Prg SAPMSSYD 06/05/2002 17:09:33 16384
Prg SAPFSYSCALLS 02/14/2002 14:22:47 6144
Prg RSDBRUNT 06/13/2004 00:43:20 226304
Typ RSSCR / / : m:15 5120
Prg RSDBSPBL 01/07/2003 18:47:02 59392
Prg SAPDB__S 02/14/2002 14:22:47 15360
Typ VARID 05/12/1997 16:51:30 4096
Prg %_CSYDB0 02/14/2002 14:22:46 28672
Prg RSDBSPVA 09/06/2005 22:54:22 112640
Prg SAPLSVAR 09/06/2005 22:57:28 625664
Typ VARIS 05/12/1997 15:27:21 2048
Typ RSVAMEMKEY 05/07/1997 13:07:49 2048
Prg RSDBSPMC 06/05/2002 17:09:26 66560
Typ DDSHDESCR 09/03/1997 03:05:16 3072
Typ SPPARAMS 05/07/1997 13:10:38 2048
Typ SPPARAMS 05/07/1997 13:10:38 2048
Typ RSSELINT 04/04/1995 16:12:37 2048
Prg SAPLICON 03/12/2004 06:57:52 23552
Prg %_CICON 02/14/2002 14:22:46 65536
Prg SAPLSABE 02/14/2002 14:22:47 11264
Prg SAPLSECU 05/23/2005 14:04:05 64512
Typ RSSUBINFO 10/14/1999 22:01:03 3072
Prg %_CRSDS 02/14/2002 14:22:46 8192
Typ RSDSEXPR 08/20/1998 10:57:18 2048
Prg SAPLDSYA 02/14/2002 14:22:47 39936
Prg SAPFSDS1 01/07/2003 18:32:17 47104
Typ TDCLD 11/02/1998 09:51:35 5120
Prg SAPLSDOD 04/30/2005 22:53:50 39936
Typ DOKIL 05/12/1997 16:46:17 3072
Prg SAPCNVE 02/14/2002 14:22:47 6144
Prg SAPLLANG 02/14/2002 14:22:47 8192
Typ T002 02/14/1998 10:24:58 2048
Typ RSEXFCODE 08/13/1997 12:52:57 1024
Prg SAPFSPOR 03/13/2004 19:20:44 12288
Prg SAPLOMCV 05/01/2005 00:14:10 16384
Prg CL_EXITHANDLER================CP 06/13/2004 00:40:58 26624
Prg SAPLSEXV 09/06/2005 22:55:26 107520
Prg CL_BADI_FLT_DATA_TRANS_AND_DB=CP 05/01/2005 00:21:35 33792
Typ SXS_ATTR 08/20/2001 12:23:27 4096
Typ V_EXT_ACT 11/09/2000 14:27:05 2048
Typ SXC_EXIT 11/09/2000 14:23:43 2048
Prg CL_EX_BADI_MATN1==============CP 05/01/2005 00:14:04 22528
Prg IF_EX_BADI_MATN1==============IP 06/13/2004 00:48:55 4096
Typ TMCNV 02/24/1999 03:33:25 3072
Prg SAPLSCNT 02/14/2002 14:22:47 24576
Typ DYCBOX 08/20/1998 11:16:53 2048
Prg SAPLSVSM 01/07/2003 18:35:45 22528
Prg SAPLSGUI 01/09/2003 17:15:12 31744
Prg SAPLSTTM 05/01/2005 00:24:04 75776
Prg SAPLSBDC 05/23/2005 14:05:19 38912
Prg CL_DATAPROVIDER===============CP 02/14/2002 14:22:46 40960
Prg %_CCNTL 02/14/2002 14:22:46 13312
Typ OBJ_RECORD 02/14/1998 08:30:43 2048
Prg SAPLSTUP 05/23/2005 14:03:46 65536
Prg SAPLCNDP 05/23/2005 14:05:47 167936
Prg SAPFGUICNTL 01/09/2003 17:18:52 20480
Prg SAPLOLEA 05/23/2005 14:03:56 79872
Prg SAPLSFES 09/06/2005 22:53:55 191488
Prg SAPLSPLUGIN 02/14/2002 14:22:48 6144
Typ ARFCRDATA 11/09/2000 14:04:16 6144
Prg SAPLGRFC 02/14/2002 14:22:47 13312
Typ SWCBCONT 11/15/2000 17:55:11 3072
Typ OLE_VERBS 04/04/1995 16:02:20 2048
Typ OLE_PA 04/04/1995 16:02:19 2048
Prg SAPSHDTV 03/12/2004 06:40:27 28672
Typ SSCRTEXTS 09/03/1997 03:12:33 3072
Typ SSCRFIELDS 05/13/1997 12:54:26 4096
Prg CL_GUI_PROPS_CONSUMER=========CP 01/07/2003 18:26:56 26624
Prg SAPLTHFB 09/06/2005 22:52:48 306176
Prg CL_DYNAMIC_GUI_EXTENSIONS=====CP 02/14/2002 14:22:46 33792
Prg CL_GUI_DATAMANAGER============CP 05/01/2005 00:20:36 70656
Prg CL_ABAP_CHAR_UTILITIES========CP 05/01/2005 00:14:49 11264
Prg RSDBSPVD 05/01/2005 00:15:44 73728
Typ RVARI 03/30/1998 09:40:50 4096
Typ RSVARIVDAT 04/04/1995 16:12:54 2048
Typ VBEP 01/27/2003 16:50:17 10240
Typ VBAP 09/15/2005 11:15:36 44032
Prg SAPLCEI0 09/22/2005 14:34:40 936960
Typ API_VALUE 02/20/1998 08:46:47 2048
Prg SAPLCUEV 06/07/2001 18:26:56 10240
Prg SAPLSUNI 06/13/2004 00:42:30 131072
Typ TFDIR 07/29/1998 19:49:08 3072
Prg %_CIBCO2 03/13/2004 14:32:13 12288
Typ IBINCOM 06/01/1999 11:56:27 3072
Typ IBINCONF 06/01/1999 11:56:27 2048
Typ IBSTCONF 06/01/1999 11:56:28 1024
Prg SAPLCUCB 05/23/2005 15:20:17 192512
Typ TCUIBSPECIAL 06/07/2001 17:50:37 1024
Prg %_CIBXX 03/13/2004 14:38:45 49152
Typ BAL_S_MSG 12/04/2000 13:04:01 6144
Prg CX_CBASE_ERROR================CP 01/27/2003 16:58:10 10240
Typ SCX_SRCPOS 11/09/2000 14:12:15 2048
Typ BAL_S_CONT 11/02/1998 09:43:07 2048
Typ BAL_S_PARM 12/04/2000 12:45:14 3072
Typ BAL_S_CLBK 11/02/1998 09:43:07 2048
Prg CX_STATIC_CHECK===============CP 02/14/2002 14:22:47 8192
Prg CX_ROOT=======================CP 02/14/2002 14:22:47 9216
Prg CL_CBASE======================CP 05/23/2005 15:19:44 87040
Typ T371G 04/29/1998 10:42:48 2048
Prg SAPLIBCO 03/13/2004 15:32:40 269312
Prg %_CIBCO 03/13/2004 14:38:45 11264
Prg SAPLIBXX 03/13/2004 14:38:46 11264
Prg SAPLIBIBF 03/13/2004 14:38:46 179200
Prg %_CIBIB 03/13/2004 14:38:45 18432
Prg SAPLIBINF 06/12/2004 22:20:22 415744
Prg %_CIBIN 03/13/2004 15:32:40 48128
Prg CL_IBASE_STRUC================CP 06/07/2001 19:59:10 106496
Prg %_CIBST 03/13/2004 14:38:45 37888
Prg CL_IBASE_STRUC_BUF============CP 06/07/2001 19:59:10 89088
Prg CL_IBASE_STRUC_STAT===========CP 06/07/2001 19:59:10 8192
Prg CL_IBASE_STRUC_BUF_IBSTREF====CP 06/07/2001 19:59:10 35840
Prg %_CIBCO1 03/13/2004 14:38:45 14336
Typ IBINVAL 09/18/2001 10:02:52 2048
Prg SAPLIBCU 03/13/2004 14:38:46 12288
Prg SAPLIBCUT 06/07/2001 18:27:19 12288
Typ T371B 05/14/1998 22:58:43 2048
Typ V_IBINR 03/13/2004 15:32:40 5120
Typ V_IBINR_CM 03/13/2004 15:32:40 5120
Prg CL_IBASE_SERVICE==============CP 06/07/2001 19:59:10 13312
Prg CL_IBASE_T371D_BUF============CP 06/07/2001 19:59:10 12288
Typ T371D 08/27/1999 18:19:44 2048
Prg CL_IBASE_R3_MATERIAL==========CP 05/23/2005 15:08:24 59392
Typ MARA 05/23/2005 15:08:18 22528
Typ MAKT 08/28/1997 08:52:19 2048
Typ ICON 01/03/1996 15:34:02 3072
Prg CL_ABAP_TYPEDESCR=============CP 05/01/2005 00:20:10 21504
Prg CL_ABAP_ELEMDESCR=============CP 05/01/2005 00:20:33 20480
Prg CL_ABAP_DATADESCR=============CP 03/12/2004 07:16:33 14336
Prg CL_ABAP_REFDESCR==============CP 03/12/2004 07:17:23 16384
Prg CL_ABAP_STRUCTDESCR===========CP 05/01/2005 00:20:33 20480
Prg CL_ABAP_COMPLEXDESCR==========CP 03/12/2004 07:16:33 13312
Prg CL_ABAP_TABLEDESCR============CP 03/12/2004 07:17:23 17408
Prg CL_ABAP_CLASSDESCR============CP 03/12/2004 07:17:23 23552
Prg CL_ABAP_OBJECTDESCR===========CP 03/12/2004 07:17:23 25600
Prg CL_ABAP_INTFDESCR=============CP 03/12/2004 07:16:33 19456
Prg CL_ABAP_SOFT_REFERENCE========CP 03/29/2001 16:42:12 7168
Prg CL_ABAP_REFERENCE=============CP 02/14/2002 14:22:46 6144
Prg IF_EX_CM_BADI_VERSION=========IP 01/07/2002 16:09:04 3072
Prg %_CABAP 01/07/2003 18:31:23 23552
Typ SXS_INTER 11/30/1998 15:55:16 2048
Prg CL_EX_CM_BADI_VERSION=========CP 05/01/2005 00:14:04 13312
Prg %_CSXRT 06/13/2004 00:40:55 11264
Prg CL_EXIT_MASTER================CP 06/13/2004 00:40:58 13312
Typ V_EXT_IMP 11/09/2000 14:27:05 2048
Typ V_EXT_IMP 11/09/2000 14:27:05 2048
Typ SXC_IMPSWH 11/09/2000 14:23:44 2048
Prg CL_IM_CM_BADI_VERSION_DEF=====CP 04/17/2002 11:01:00 6144
Prg SAPLASTAT_TRIG 02/14/2002 14:22:47 11264
Typ ASTAT_TYP2 11/10/1998 05:35:18 2048
Prg IF_CM_BASELINE================IP 05/23/2005 15:08:24 9216
Prg IF_IBASE_IBOF_TREE_OBJECT=====IP 05/23/2005 15:08:24 5120
Prg IF_IBASE_INSTALL==============IP 06/07/2001 20:08:54 4096
Prg IF_IBASE_MATERIAL=============IP 06/07/2001 20:08:54 3072
Prg IF_IBASE_OBJECT===============IP 06/07/2001 20:08:54 4096
Prg SAPLBOMA 02/14/2002 14:15:40 10240
Typ IONRA 03/12/2004 02:09:40 23552
Typ IBIBCOM 08/30/2001 17:56:57 4096
Typ IBIB 03/13/2004 14:32:13 5120
Prg CL_IBASE_STRUC_SERVICE========CP 06/07/2001 19:59:10 17408
Prg CL_CU_CBASE_ENQUEUE_CORE======CP 06/07/2001 19:58:59 11264
Prg CL_CU_CBASE_ENQUEUE===========CP 06/07/2001 19:58:59 16384
Typ T371F 06/01/1999 12:00:49 2048
Typ V_IBIN_SYVAL 03/13/2004 15:32:41 4096
Typ IBIN 09/18/2001 10:02:52 6144
Typ IBINOWN 02/01/2000 14:56:07 2048
Prg CL_IBASE_T371F_BUF============CP 06/07/2001 19:59:11 8192
Prg CL_IBASE_STRUC_FILT_02========CP 06/07/2001 19:59:10 11264
Prg CL_IBASE_STRUC_FILT===========CP 06/07/2001 19:59:10 10240
Typ IBST 09/18/2001 10:02:52 4096
Typ IBST 09/18/2001 10:02:52 4096
Typ IBSTREF 04/15/1998 00:20:43 2048
Typ IBSTREF 04/15/1998 00:20:43 2048
Prg IF_CBASE_E====================IP 06/07/2001 20:08:25 3072
Prg %_CCXTAB 02/14/2002 14:22:46 6144
Prg SAPLCUCQ 09/15/2005 11:15:38 79872
Typ CUCO 09/18/2001 10:02:34 18432
Typ CUCO_OBJ 09/18/2001 10:02:34 18432
Prg SAPLCLCA 09/06/2005 23:33:29 68608
Typ TCLA 03/13/2004 14:10:20 5120
Typ TCLAO 08/13/1997 13:57:22 4096
Prg SAPLCUOB 05/23/2005 14:31:35 31744
Typ INOB 09/03/1997 03:20:02 4096
Prg SAPLCLSE 05/23/2005 14:32:26 167936
Prg %_CCC01 05/01/2005 00:34:57 53248
Typ TABLEKEY 07/06/1998 21:01:06 2048
Typ KSSK 09/18/2001 10:02:58 3072
Prg SAPLCLEF -
Runtime Errors BCD_FIELD_OVERFLOW Exception CX_SY_CONVERSION_OVERFLOW
Dear All,
I am getting below error in PRD system. We are using ecc6, oracle 10g and windows 2003. The error coming after we have restarted the server. Please suggest how to solve the issues.
SM21 log
09:30:21 DIA 000 000 DDIC AB 0 Run-time error "BCD_FIELD_OVERFLOW" occurred
09:30:21 DIA 000 000 DDIC AB 1 > Short dump "100913 093034 nodeA " generated
ST22
Runtime Errors BCD_FIELD_OVERFLOW
Exception CX_SY_CONVERSION_OVERFLOW
Date and Time 13.09.2010 00:30:19
Short text
A calculation field is defined too small.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_SWNC_RECORD================CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not
caught in
procedure "DO_TRANSFORMATIONS" "(METHOD)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
A value generated during processing is too large for the
field "ME->MAIN_RECORD_STR+1020(7)" of the program
"CL_SWNC_RECORD================CP".
Regards,
KumarDear Friends,
We even got same dump "BCD_FIELD_OVERFLOW" just after system restart. But error was slightly different. Please find below error details and solution:
Error Details:
The current ABAP program "CL_SWNC_RECORD================CP" had to be terminated because it has come across a statement that unfortunately cannot be executed.
Error Analysis:
An exception occurred that is explained in detail below. This exception cannot be caught in the context of the current statement.
The reason for the exception is: A value generated during processing is too large for the field " " of the program "CL_SWNC_RECORD================CP".
"BCD_FIELD_OVERFLOW" " "
"CL_SWNC_RECORD================CP" or "CL_SWNC_RECORD================CM002"
"CALCULATE_PROCESSING_TIME"
SOLUTION:
An OSS Note:
Note 1103295 - BCD_FIELD_OVERFLOW in CALCULATE_PROCESSING_TIME (It solves the problem) -
Performance Tuning 'Runtime Error' on Select statement
Hi Experts,
Good Day!
I would like to ask some help regarding a custom program that will encounter 'Runtime Error' on the below codes on how to perform performance tunning especially number 1.
1.
SELECT A~VBELN A~ERDAT A~AUART A~VKORG A~VTWEG A~SPART A~VDATU
A~KUNNR B~POSNR B~MATNR B~ARKTX B~ABGRU B~KWMENG B~VRKME
B~WERKS B~VSTEL B~ROUTE
FROM VBAK AS A INNER JOIN VBAP AS B ON A~VBELN EQ B~VBELN
INNER JOIN VBEP AS C ON A~VBELN EQ C~VBELN
AND B~POSNR EQ C~POSNR
INTO CORRESPONDING FIELDS OF TABLE I_DATA_TAB
WHERE A~VBELN IN S_VBELN
AND A~VKORG IN S_VKORG
AND A~AUART IN S_AUART
AND A~VTWEG IN S_VTWEG
AND A~SPART IN S_SPART
AND A~VDATU IN S_VDATU
AND A~KUNNR IN S_KUNNRD
AND B~MATNR IN S_MATNR
AND B~KWMENG IN S_KWMENG
AND B~VRKME IN S_VRKME
AND B~WERKS IN S_WERKS
AND C~EDATU IN S_VDATU.
2.
SELECT VBELN FROM LIKP INTO LIKP-VBELN
WHERE LFDAT IN S_VDATU
AND VKORG IN S_VKORG
AND LFART EQ 'YSTD'
AND KUNNR IN S_KUNNRP
AND KUNAG IN S_KUNNRD
SELECT VBELN POSNR LFIMG MATNR WERKS
FROM LIPS INTO (LIPS-VBELN, LIPS-POSNR, DISPLAY_TAB-DEL_QTY,
LIPS-MATNR, LIPS-WERKS)
WHERE VBELN EQ LIKP-VBELN
AND MATNR IN S_MATNR
AND VTWEG IN S_VTWEG
AND SPART IN S_SPART
AND WERKS IN S_WERKS.
ENDSELECT.
ENDSELECT.
4.
SELECT DELIVERY POSNR MATNR PODLFIMG FROM T9YPODI INTO
(T9YPODI-DELIVERY, T9YPODI-POSNR, T9YPODI-MATNR, T9YPODI-PODLFIMG)
WHERE MATNR IN S_MATNR
AND PODDATE IN S_VDATU.
Answer's will be a great help.
~Thank You,
Lourd
Edited by: Lourd06 on Oct 23, 2009 10:32 AM
Moderator message - Welcome to SCN.
Moderator message - Please see Please Read before Posting in the Performance and Tuning Forum before posting. You're in the driver's seat here. It's up to you to do some analysis before expecting that people can halp you. - post locked
And please use code tags.
Edited by: Rob Burbank on Oct 23, 2009 9:13 AMHi All,
We've checked the transaction ST22 it is TIME OUT. I really need your help on this the program will dump in number 1 Select statement. Can you help me perform a performance tunning.
In transaction ST22
Runtime Errors TIME_OUT
Date and Time 21.10.2009 08:51:33
Short text
Time limit exceeded.
What happened?
The program "ZV0PSR10" has exceeded the maximum permitted runtime without
interruption and has therefore been terminated.
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
After a specific time, the program is terminated to make the work area
available to other users who may be waiting.
This is to prevent a work area being blocked unnecessarily long by, for
example:
- Endless loops (DO, WHILE, ...),
- Database accesses with a large result set
- Database accesses without a suitable index (full table scan)
The maximum runtime of a program is limited by the system profile
parameter "rdisp/max_wprun_time". The current setting is 1200 seconds. If this
time limit is
exceeded, the system attempts to cancel any running SQL statement or
signals the ABAP processor to stop the running program. Then the system
waits another 60 seconds maximum. If the program is then still active,
the work process is restarted.
~Thank you
Lourd
Edited by: Lourd06 on Oct 23, 2009 11:22 AM
Edited by: Lourd06 on Oct 23, 2009 11:33 AM -
How to delete the runtime error in st22
Hi all,
How to delete the runtime error in ST22. I want to clear
the list of short dump in st22
is there any T.code or any table to clear?
thanks in advance
sundar.cHi
you cannot delete the dumps through any tcode.
All the dumps are stored in table called SNAP, If there are more dumps the table gets filled therefore u have to reorganize the table.
Run the report RSSNAPDL in SE38.
or
You have the default SAP background jobs, SAP_REORG_ABAPDUMPS which deletes the past dumps raised in the system.
Scheduling the jobs in regular is very important
For more information
http://help.sap.com/saphelp_nw04/helpdata/en/c4/3a7ede505211d189550000e829fbbd/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/d8/a58b4275160d53e10000000a155106/frameset.htm
Regards
Bhaskar -
IDoc to File, SM58 shows error, ST22 short dump - Runtime error
Hi friends,
I am doing a simple IDoc to file scenario using the EVMSTA01 IDoc. My XI is running on client 100 and I am trying to send the IDoc from the client 200 on the same machine. I have completed the design and configuration steps required and also performed the required steps in Sender client (Sm59, we21 and BD54) and receiver client (Sm59, IDX1 and IDX2).
When I tried sending the IDoc from WE19, status meesage says that, the IDoc has been successfully sent to the receiver but SM58 shows error "IDOC_ERROR_WORKFLOW_START_R". When I looked in to ST22, there was a short dump with the below message -
Runtime Errors MESSAGE_TYPE_X
Date and Time 18.10.2008 23:24:29
ShrtText
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
Error analysis
Short text of error message:
Unable to read RFC destination WORKFLOW_LOCAL_200
Technical information about the message:
Message classe...... "SWF_RUN"
Number.............. 617
Variable 1.......... "WORKFLOW_LOCAL_200"
Variable 2.......... "RFC_READ_DESTINATION_TYPE"
Variable 3.......... "DESTINATION_NOT_EXIST"
Variable 4.......... " "
Variable 3.......... "DESTINATION_NOT_EXIST"
Variable 4.......... " "
Trigger Location of Runtime Error
Program CL_SWF_RUN_WIM_LOCAL==========CP
Include CL_SWF_RUN_WIM_LOCAL==========CM07Z
Row 10
Module type (METHOD)
Module Name IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
rce Code Extract
e SourceCde
1 METHOD if_swf_run_wim_utl_internal~get_system_user .
2 DATA: l_excp TYPE REF TO cx_swf_run_wim.
3
4 TRY.
5 IF me->m_int_state-system_user IS INITIAL.
6 me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destination_us
7 ENDIF.
8 re_user = me->m_int_state-system_user.
9 CATCH cx_swf_run_wim INTO l_excp.
>> MESSAGE ID l_excp->t100_msg-msgid
11 TYPE 'X'
12 NUMBER l_excp->t100_msg-msgno
13 WITH l_excp->t100_msg-msgv1 l_excp->t100_msg-msgv2
14 l_excp->t100_msg-msgv3 l_excp->t100_msg-msgv4.
15 ENDTRY.
16
17 ENDMETHOD. "
Any help would be appreciated..!!
PS: Points would be assigned to all the helpful replys without failHi,
See check for RFC destination and it is working as per your configuration or not , i mean , it is trying to locate remote server.. , so try to check in sm59, remote login and the respective result is going to your required client or not ??
Also see the further errors while doing Idoc related scenarios..
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133 - Idocs not reaching XI . Not posted in the receiver SAP
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
Regards
Chilla -
Runtime Error "TYPELOAD_NEW_VERSION" occuring in ST22
Hi,
We have been reporting a Runtime Error "TYPELOAD_NEW_VERSION" for a few days now. It appears when we check in ST22.
The Error is as below :
Error analysis
The data type "ZBSTC0000WMXKNJ" was loaded from the database during the program
run.
However, a type of a newer version than the one requried was found here.
Please give me some idea about the cause of this error. Any solutions?Check this thread which discuss the same error :
Re: TYPELOAD_NEW_VERSION - Error
Mathews -
Hi Experts,
Please help me to resolve this error @ st22 "PXA_NO_SHARED_MEMORY" , my question is :
What particular memory or parameter I need to adjust?
I always reboot/restart my system in-order to refresh the memory. A huge thanks who will be able
to help me to solve this.Runtime Errors : PXA_NO_SHARED_MEMORY
Date and Time: 01/13/2015 13:50:04
What happened?
When starting the R/3 System, 800000 Kbytes of storage space
was required for the ABAP/4 program buffer (PXA), but this
was not available.
The system was started as an emergency system and is not fully
operational.
It is intended only for display and to eliminate errors.
Under no circumstances should it be used for production
purposes.
What can you do?
The system was started as an emergency system and is not fully
operational. It is intended only for display to eliminate errors.
Under no circumstances should it be used for production
purposes.
used in production.
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP adminis
You can use the ABAP dump analysis transaction ST22 to view and ma
termination messages, in particular for long term reference.
Error analysis
The error probably occurred when installing the
R/3 system.
The return code of the SAP shared memory control was 1.
The error reported by the operating system is:
Error number..... 0
Error text....... "No error"
How to correct the error
Report the error to the group responsible for installing y
R/3 System.
The current size of the PXA was set at 737764 kilobytes.
You can increase or decrease the PXA in the SAP profile. W
doing this, please refer to the relevent instructions in t
installation manual.
You can use the utility program 'ipclimits' to display the
available system resources.
If the error occures in a non-modified SAP program, you ma
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with t
keywords:
"PXA_NO_SHARED_MEMORY" " "
"########################################" or
If you cannot solve the problem yourself and want to send
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Lo
(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 " "
Application server... "SAPRD-PRD-1"
Network address...... " "
Operating system..... "Windows NT"
Release.............. "6.1"
Hardware type........ "16x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 6
Shortdump setting.... "full"
Database server... "SAPRD-PRD-2"
Database type..... "ORACLE"
Database name..... "prd1sap"
Database user ID.. "sapr3"
Char.set.... "C"
SAP kernel....... 720
created (date)... "Jan 16 2013 16:56:16"
create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"
Database version. "OCI_10202_SHARE, 11.2.0.2.0 "
Patch level. 401
Patch text.. " "
Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
SAP database version. 720
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0, Windows NT 6.1, Windows NT 6.2"
Memory consumption
Roll.... 0
EM...... 52356379171412
Heap.... 0
Page.... 0
MM Used. 0
MM Free. 0
User and Transaction
Client.............. "###"
User................ "############"
Language key........ "#"
Transaction......... " "
Transactions ID..... " "
Program............. "########################################"
Screen.............. " "
Screen line......... " "
Information on where terminated
Termination occurred in the ABAP program
"########################################" - in " ".
The main program was " ".
In the source code you have the termination point in line 0
of the (Include) program "########################################".
The error occurred during initialization of the R/3 System.
Internal notes
The termination was triggered in function "ab_pbinit"
of the SAP kernel, in line 2119 of the module
"//bas/720_REL/src/krn/runt/abload3.c#31".
The internal operation just processed is " ".
Internal mode was started at "##############". -
Delete the Runtime Errors List from ST22 t-code
HI all;
Can any one Help on these Issue!
How to delete the list of Runtime Errors, which are available in ST22 T-code .
Thnaks
Upender.Hello,
you could use the report RSSNAPDL .
Regards Wolfgang -
Hello, i would like to understand the meaning of the following runtime error .. could you please explain me what they mean?
TIME_OUT
OPEN_DATASET_NO_AUTHORITY
MESSAGE_TYPE_X
SYNTAX_ERROR
RAISE_EXCEPTION
ITS_TEMPLATE_NOT_FOUND
RFC_NO_AUTHORITY
DYNPRO_FIELD_CONVERSION
COLLECT_OVERFLOW_TYPE_P
LIST_ILLEGAL_PAGE
CONNE_IMPORT_CONVERSION_ERROR
GETWA_NOT_ASSIGNED
TIME_OUT
UNCAUGHT_EXCEPTION
CALL_FUNCTION_SEND_ERROR
Thanks in advance.Open the dumps one by one and read all the content.
It shows you What happend? Erro analysis, how to correct? etc.
Regards,
Nick Loy -
RunTime Error while saving a Sales Order
Hi All,
When i am saving a Sales Order, the system is throwing a Runtime Error.
The ABAP Code in the Runtime Error screen as follows.
select * from (t681-kotab) appending table <cond_tab>
up to 1 rows
where kappl = se_kappl
and kschl = se_kschl
and datbi >= se_date
and datab <= se_date
and (coding_tab).
Till these days, there was no such error while saving a Sales Order.
How to resolve this issue?
Regards
PavanHi,
The below piece of code is trying to get the contents of the table mentioned in T681-KOTAB.
select * from (t681-kotab) appending table <cond_tab>
up to 1 rows
where kappl = se_kappl
and kschl = se_kschl
and datbi >= se_date
and datab <= se_date
and (coding_tab).
The reason could be is someone has screwed up the entries in T681 table. Check that out.
Try to put a break point on this SELECT query and see what the value of T681-KOTAB holds before the SELECT query. Check whether such a table entry exists in DB.
Let me know if you are still stuck up.
If you can send me the ST22 dump of the run time error, i might be able to help you more on this.
Hope this helps.
Thanks,
Balaji -
WHILE DELETING A SALE ORDER GETTING A RUNTIME ERROR " Screen: Illegal message"
Hi Experts,
While deleting a sales order giving run time error. PFB runtime error details.
If you know any OSS message, please let m know. I tried, but there is no luck.
Short text
Screen: Illegal message
What happened?
The current screen processing action was terminated since a situation
occurred where the application could not continue.
This is probably due to an error in the ABAP program or in the current
screen.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator.
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
The program attempted to issue a " " message during "Exit Command" processing.
This is an illegal operation.
The program was terminated.
Screen name.............. "SAPMV45A"
Screen number............ 4001
How to correct the error
The program must be modified to correct the error.
The modification must be made in "Exit Command" processing.
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)".
Source Code Extract
Line SourceCde
1 *---------------------------------------------------------------------*
2 * FORM YVBEP_LESEN *
3 *---------------------------------------------------------------------*
4 * Lesen der Tabelle YVBEP (nicht sortiert) *
5 *---------------------------------------------------------------------*
6 FORM YVBEP_LESEN USING US_POSNR
7 US_ETENR
8 CHANGING CH_TABIX.
9
10 YVBEP = SPACE.
11 YVBEP-MANDT = VBAK-MANDT.
12 YVBEP-VBELN = VBAK-VBELN.
13 YVBEP-POSNR = US_POSNR.
14 YVBEP-ETENR = US_ETENR.
15 READ TABLE YVBEP.
16 IF SY-SUBRC > 0.
17 MESSAGE E506 WITH US_POSNR US_ETENR.
18 ENDIF.
>>>>> CH_TABIX = SY-TABIX.
20
21 ENDFORM.
Could you please help on this issue.
Thanks
SrinuHi Srinu,
it looks like you got the error message Schedule line &1 &2 is missing in table YVBEP while deleting the sales order.
It seems, that there are no SAP notes regarding this issue. Do you have this issue with all orders or with a single order?
If only a single order causes this issue, maybe something was wrong during an update.
If you get this error for many orders, then custom code (modification, enhancement, user exit in MV45AFZZ, ...) may be the reason for it.
If you have no custom code in module pool SAPMV45A, then contact SAP for this issue.
Regards,
Klaus -
Hi ,
We are getting the runtime error " RAISE_EXCEPTION" in production server.
Error analysis
A RAISE statement in the program "SAPLSOI1" raised the exception
condition "USER_NOT_EXIST".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
Specified ID or user name does not exist
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
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:Hi krishna,
Sorry for the late reply.
Short text
Exception condition "USER_NOT_EXIST" 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.
Thanks & Regards
Eldho -
Runtime Error in BW, in RSA1 transaction
Hello Boss,
Iam getting runtime error while activating the info object in RSA1 transaction.
I got OSS notes also from our basis consultant, plz give suggestion how to rectify this one.
Even while executing the program iam getting runtime error.
In this OSS notes they mentioned while u activating DSO u get this runtime error & solutions r given. iam not activating any DSO, activating info object. plz give ur suggestion.Hi,
check in ST22 what exactly is message.. Ask basis to check server space and bg process.
Abhi -
HI all.....
please look at this runtime error...... help me to solve this....
Table name:- ZRDSSTOCK.
Data class:- APPL1.
Size category:- 5.
Buffering not allowed .
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Occurred on 26.11.2007 at 12:38:44
An SQL error occurred when accessing a table.
What happened?
What can you do?
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
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 "SAVE_DATA"
"(FORM)"
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:
How to correct the error
The exception must either be prevented, caught within the procedure "SAVE_DATA"
"(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
SAPPRD.ZRDSSTOCK~0 by 128 in tablespace PSAPPRDUSR"
Internal call code.........: "[RSQL/INSR/ZRDSSTOCK ]"
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_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"YKSD010 " or "YKSD010 "
"SAVE_DATA"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "venus"
Network address.......... "192.168.1.151"
Operating system......... "SunOS"
Release.................. "5.9"
Hardware type............ "sun4u"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "venus"
Database type............ "ORACLE"
Database name............ "PRD"
Database owner........... "SAPPRD"
Character set............ "en_US"
SAP kernel............... "620"
Created on............... "Nov 17 2004 01:43:57"
Created in............... "SunOS 5.8 Generic_108528-07 sun4u"
Database version......... "OCI_817_64 "
Patch level.............. "1732"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.."
SAP database version..... "620"
Operating system......... "SunOS 5.8, SunOS 5.9"
User, transaction...
Client.............. 400
User................ "MMUSER"
Language key........ "E"
Transaction......... "ZRDSEN "
Program............. "YKSD010 "
Screen.............. "YKSD010 0100"
Screen line......... 41
Information on where termination occurred
The termination occurred in the ABAP program "YKSD010 " in "SAVE_DATA".
The main program was "YKSD010 ".
The termination occurred in line 685 of the source code of the (Include)
program "YKSD010 "
of the source code of program "YKSD010 " (when calling the editor 6850).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "SAVE_DATA" "(FORM)" but was not handled locally, not declared in the
RAISING clause of the procedure.
The procedure is in the program "YKSD010 ". Its source code starts in line 662
of the (Include) program "YKSD010 ".
Source code extract
006550
006560
006570 *&----
006580 *& Form save_data
006590 *&----
006600 * text
006610 *----
006620 FORM SAVE_DATA.
006630 data: begin of lv_test occurs 0,
006640 werks type s886-werks,
006650 pkunag type s886-pkunag,
006660 end of lv_test.
006670 LOOP AT INDT1.
006680
006690 INDT1-WERKS = WERKS.
006700 INDT1-DAT1 = VDFRM.
006710 INDT1-DAT2 = VLDTO.
006720 * indt1-kunnr = kunnr.
006730
006740
006750 MODIFY INDT1.
006760
006770 ENDLOOP.
006780 *if indt1 is not initial.
006790 *select pkunag werks from s886 into corresponding fields of table
006800 *lv_test where pkunag = indt1-rdscode and werks = indt1-werks.
006810 *if sy-subrc = 0.
006820
006830 &----
changed by prajwal.k----
006840
INSERT ZRDSSTOCK FROM TABLE INDT1 ACCEPTING DUPLICATE KEYS.
006860 *loop at indt1.
006870 * INSERT ZRDSSTOCK FROM INDT1.
006880 *if sy-subrc <> 0.
006890 *message w013 WITH INDT1-MATNR.
006900 *endif.
006910 *endloop.
006920
006930
006940 &----
end----
006950 * MESSAGE I004.
006960 *else.
006970 *message 'Please chek the RDS Code' type 'W'.
006980 *endif.
006990 *endif.
007000 *endif.
007010 LOOP AT INDT1.
007020
007030 AT LAST.
007040
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 0
SY-TABIX 0 SY-DBCNT 1
SY-FDPOS 40 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY YINDENT
SY-UCOMM OPT1 SY-TITLE RDS Stock Entry Screen
SY-MSGTY SY-MSGID
SY-MSGNO 000 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
3 FORM SAVE_DATA
YKSD010
YKSD010 685
2 MODULE (PAI) YINDENT_IN
YKSD010
YKSD010 233
1 EVENT START-OF-SELECTION
YKSD010
YKSD010 181
Chosen variables
3 FORM SAVE_DATA
YKSD010
YKSD010 685
INDT1[] Table IT_121[1738x121]
FFFF94120000000000020007000C00070000FFFF
FFFE7BD00000000000060009006A00090000FFFF
... + 40
00000005012B0000
40000058004C0000
INDT1 TNV0024 2007090120070930CH01C0100300
5453333222333333333333333344334333333322
4E60024000200709012007093038013010030000
... + 40 CAR####`#################`######
2222222244500006000000000000000006000000
0000000031200000C00000C00000C00000C00000
... + 80 #
0222222222222222222222222222222222222222
C000000000000000000000000000000000000000
... + 120
2
0
SY ###############Ê########################
000000000000000C000000000000000000000000
000000000000006A000000000000000000000000
... + 40 #######(###############################y
0000000200000000000000000000000000000007
0001000800010000000100000000000000000009
... + 80 ########################################
0000000000000000000900000000000000000000
0000000000000000001000000000000000000000
... + 120 ########################################
0000000000000000000000000000000000010009
00000000000000000000000000000000000B0000
... + 160 #######ÿ######MX C############# E0 0
0000000F00000045240000000000000222432223
0000000F000000D8030010000C0000C000500000
... + 200 100 ####__S 400
3332222222220000555222222222222222223332
1000000000000000FF3000000000000000004000
... + 240 00
222223322222222
000000000000000
MODIFY-CX ########MODIFY
0000000044444522222222222222222222222222
00020000DF496900000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120 0101####
222222222222222222223333000022222222
000000000000000000000101000100000000
<%_L005>-SEL ???
OK_CODE SAVE
5454222222222222222222222222222222222222
3165000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
<%_TABLE_ZRDSSTOCK> ???
%_DUMMY$$
2222
0000
VLDTO 20070930
33333333
20070930
SY-REPID YKSD010
5454333222222222222222222222222222222222
9B34010000000000000000000000000000000000
SY-MSGID
22222222222222222222
00000000000000000000
SPACE
2
0
SY-MSGNO 000
333
000
2 MODULE (PAI) YINDENT_IN
YKSD010
YKSD010 233
SY-UCOMM OPT1
4553222222222222222222222222222222222222
F041000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
COUNT ########
00000000
0000000C
%_VLDTO_%_APP_% Valid To
566662562222222222222222222222
61C9404F0000000000000000000000
%_WERKS_%_APP_% Plant
566672222222222222222222222222
0C1E40000000000000000000000000
%_VDFRM_%_APP_% Valid From
566662476622222222222222222222
61C94062FD00000000000000000000
%B001000_BLOCK_1000 Enter Values
4676725667672222222222222222222222222222
5E452061C5530000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
222
000
VALUE
222222222222222222
000000000000000000
SYST-REPID YKSD010
5454333222222222222222222222222222222222
9B34010000000000000000000000000000000000
SY-SUBRC 0
0000
0000
A 1
3
1
SY-MSGV4
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV2
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
VARI
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40 ####00000000000000
2222222222222222222200003333333333333322
0000000000000000000000000000000000000000
... + 80 ####################################
2222000000000000000000000000000000000000
0000000000000000000000000000000000000000
... + 120 ########################################
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
... + 160 ########################################
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
... + 200 ########################################
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
... + 240 ###############
000000000000000
000000000000000
INDT[] Table IT_28[0x121]
FFFF958EFFFF940200010001000000070000FFFF
FFFE7B70FFFE74800007000C000000090000FFFF
... + 40
0000000E012B0000
40000048004C4000
INDT 0000000000000000
2222222222333333333333333322222222222222
0000000000000000000000000000000000000000
... + 40 #############################
2222222222200000000000000000000000000000
0000000000000000C00000C00000C00000C00000
... + 80 #
0222222222222222222222222222222222222222
C000000000000000000000000000000000000000
... + 120
2
0
1 EVENT START-OF-SELECTION
YKSD010
YKSD010 181
No dump information available
Application Calls
No dump information available
Application Information
No dump information available
Internal notes
The termination occurred in the function "HandleRsqlErrors" of the SAP
Basis System, specifically in line 760 of the module
"//bas/620/src/krn/runt/absapsql.c#40".
The internal operation just processed is "SQLS".
The internal session was started at 20071126123440.
Internal call code.........: "[RSQL/INSR/ZRDSSTOCK ]"
Active calls in SAP kernel
DoStack2 ( 0xffffffff7fff6490, 0xffffffff7fff6370, 0x0,0x203ac00, >
> 0x100362d98, 0xffffffff7fff5b71 ), at 0x100362d98
CTrcStack2 ( 0x103519930, 0x0, 0x10008, 0x1018dc400, 0x0, 0x1 ), at 0x10036296c
__1cQrabax_CStackSave6F_v_ ( 0x1, 0x28e8400, 0x100000000, >
> 0x1028e8400, 0x0, 0x1 ), at 0x1007cccac
ab_rabax ( 0x1020c9a88, 0x4, 0x1018db3b6, 0x10355210c, 0x2000000, >
> 0x8550c017 ), at 0x1007c0e68
__1cKab_rsqlerr6Fpkcip0pnLRS_HEADER94_2pv_v_ ( 0x1018c7110, >
> 0x2f8, 0x1020c6a14, 0xffffffff7fff6cd8, 0x1018c7121, 0x0 ), at 0x10071aae8
__1cQHandleRsqlErrors6FnJRsqlError_nJCloseMode__v_ ( 0x8, >
> 0xfffffffe97470708, 0x6c8000, 0x100000000, 0x0, 0x1 ), at 0x1006c8764
__1cPSqlsExecuteCall6FCpnLDynCallInfo__v_ ( 0x100000000, >
> 0x6a, 0x20c6800, 0xe8, 0x1d, 0x1 ), at 0x1006ddd24
__1cIab_jsqls6F_v_ ( 0xfffffffe4a309e58, 0xfffffffe974707b0, >
> 0x1028c4f00, 0xe8, 0x1d, 0x100000000 ), at 0x1006c91e8
__1cIab_extri6F_i_ ( 0x103503ff8, 0xfffffffe4a309e44, 0x8a, >
> 0x0, 0x1, 0x100000000 ), at 0x1005364e8
__1cJab_xevent6Fpkc_i_ ( 0x0, 0x3416000, 0xfffffffe4c17f808, >
> 0x0, 0x1d6f, 0xfffffffe975420d8 ), at 0x10068df84
ab_dstep ( 0xd, 0xd, 0x46, 0x1, 0x103521a74, 0x103521800 ), at 0x1007d619c
dynpmcal ( 0xfffffffe9747e8c8, 0x10203a800, 0x1037d8110, >
> 0x101d2a000, 0x2660, 0x100000000 ), at 0x1003e2274
dynppai0 ( 0xfffffffe9747e8c8, 0x0, 0x0, 0xfffffffe97482c3f, >
> 0x0, 0x5 ), at 0x1003df680
dynprctl ( 0x0, 0xfffffffe9747e8c8, 0x203c400, 0x1024d0cf8, >
> 0x1020291c0, 0x1024d0c58 ), at 0x1003dd258
dynpen00 ( 0x0, 0x203c400, 0x1, 0x100000000, 0x203a800, >
> 0x10203a800 ), at 0x1003d9c24
TskhLoop ( 0x2, 0x2, 0x10203a8c0, 0x8, 0x0, 0x1 ), at 0x1001d2b18
tskhstart ( 0x100000000, 0x2028000, 0x102028000, 0x2028000, >
> 0x1, 0x4 ), at 0x1001c5ae0
DpMain ( 0x249a000, 0x26e3400, 0x10249a000, 0xffffffff7c755f44, >
> 0x0, 0x1 ), at 0x100111e60
List of ABAP programs affected
Type
Program
Gen. Date Time
Load Size
Prg
YKSD010
26.11.2007 09:44:15
55296
Prg
SAPMSSY0
18.12.2004 11:31:22
62464
Prg
SAPMSSYD
05.06.2002 17:09:33
16384
Prg
SAPFSYSCALLS
14.02.2002 14:22:47
6144
Prg
RSDBRUNT
18.12.2004 11:32:05
220160
Typ
RSSCR
. . : m:15
4096
Prg
RSDBSPBL
13.12.2002 12:24:35
58368
Prg
SAPDB__S
14.02.2002 14:22:47
16384
Typ
VARID
12.05.1997 16:51:30
4096
Prg
%_CSYDB0
14.02.2002 14:22:46
28672
Prg
RSDBSPVA
18.12.2004 11:18:02
108544
Typ
RSVAMEMKEY
07.05.1997 13:07:49
2048
Prg
RSDBSPMC
05.06.2002 17:09:26
66560
Typ
DDSHDESCR
03.09.1997 03:05:16
3072
Typ
SPPARAMS
07.05.1997 13:10:38
1024
Prg
SAPLICON
18.12.2004 09:37:13
23552
Prg
%_CICON
14.02.2002 14:22:46
57344
Prg
SAPLSABE
14.02.2002 14:22:47
11264
Prg
SAPLSECU
18.12.2004 11:16:36
63488
Prg
SAPLDSYA
14.02.2002 14:22:47
38912
Prg
SAPFSDS1
13.12.2002 12:14:34
46080
Typ
TDCLD
02.11.1998 09:51:35
4096
Prg
SAPLSDOD
18.12.2004 11:31:31
38912
Typ
DOKIL
12.05.1997 16:46:17
2048
Prg
SAPCNVE
14.02.2002 14:22:47
6144
Prg
SAPLLANG
14.02.2002 14:22:47
8192
Typ
T002
14.02.1998 10:24:58
2048
Typ
RSEXFCODE
13.08.1997 12:52:57
1024
Typ
RSPARINT
10.04.1995 09:58:38
1024
Prg
SAPLSCNT
14.02.2002 14:22:47
22528
Prg
SAPLSVSM
13.12.2002 12:16:46
22528
Prg
SAPLSGUI
13.12.2002 12:27:47
29696
Prg
SAPLSTTM
18.12.2004 11:36:10
73728
Prg
SAPLSBDC
13.12.2002 12:13:58
37888
Prg
CL_DATAPROVIDER===============CP
14.02.2002 14:22:46
38912
Prg
%_CCNTL
14.02.2002 14:22:46
13312
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Prg
SAPLSTUP
18.12.2004 09:34:15
62464
Prg
SAPLCNDP
18.12.2004 11:35:59
153600
Prg
SAPFGUICNTL
13.12.2002 12:30:03
20480
Prg
SAPLOLEA
18.12.2004 11:30:56
76800
Prg
SAPLSFES
18.12.2004 11:35:59
162816
Prg
SAPLSPLUGIN
14.02.2002 14:22:48
6144
Prg
SAPLGRFC
14.02.2002 14:22:47
13312
Prg
SAPSHDTV
19.06.2003 19:25:09
27648
Typ
SHDSTU
14.12.1998 23:15:34
2048
Typ
SHDSTCIU
14.12.1998 23:15:34
1024
Typ
SSCRTEXTS
03.09.1997 03:12:33
2048
Typ
SSCRFIELDS
13.05.1997 12:54:26
3072
Prg
CL_GUI_PROPS_CONSUMER=========CP
13.12.2002 12:11:27
27648
Prg
SAPLTHFB
18.12.2004 11:36:24
293888
Prg
CL_DYNAMIC_GUI_EXTENSIONS=====CP
14.02.2002 14:22:46
33792
Prg
CL_GUI_DATAMANAGER============CP
18.12.2004 09:49:48
69632
Prg
CL_ABAP_CHAR_UTILITIES========CP
13.12.2002 12:13:57
11264
Typ
MARD
15.11.2000 17:38:50
8192
Prg
RSDBSPVD
18.12.2004 09:35:18
73728
Typ
RVARI
30.03.1998 09:40:50
3072
Typ
RSVARIVDAT
04.04.1995 16:12:54
2048
Typ
ZLOCKPGM
11.02.2006 09:28:47
2048
Prg
%_CCXTAB
14.02.2002 14:22:46
6144
Typ
ZRDSSTOCK
26.11.2007 09:44:15
3072
Prg
SAPLGRAP
18.12.2004 11:36:25
350208
Prg
CL_GUI_FRONTEND_SERVICES======CP
18.12.2004 11:36:27
84992
Prg
CL_GUI_OBJECT=================CP
13.12.2002 12:13:57
348160
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Prg
CL_GUI_CFW====================CP
05.06.2002 17:02:46
150528
Typ
TOLE
29.07.1998 19:56:01
2048
Prg
%_COLE2
14.02.2002 14:22:46
8192
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Typ
SWCBCONT
15.11.2000 17:55:11
2048
Prg
SAPLCNTL
14.02.2002 14:22:47
270336
Prg
SAPLCNTH
14.02.2002 14:22:47
22528
Typ
FILE_TABLE
05.01.1999 10:23:11
1024
Prg
SAPLURFC
18.12.2004 10:30:34
16384
Prg
SAPLSRFC
18.12.2004 11:36:45
34816
Prg
SAPLSYST
14.02.2002 14:22:48
29696
Prg
SAPMSSY1
14.02.2002 14:22:48
18432
Typ
ARFCDATA
04.04.1995 15:40:32
3072
Typ
RFC_FIELDS
20.08.1998 10:56:34
2048
Typ
DPPROPS
09.07.1997 23:53:23
1024
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Prg
SAPLCNT0
14.02.2002 14:22:47
30720
Typ
OLE_PA
04.04.1995 16:02:19
2048
Typ
ARFCRDATA
09.11.2000 14:04:16
4096
Typ
OLE_VERBS
04.04.1995 16:02:20
2048
Prg
CL_ABAP_TYPEDESCR=============CP
18.12.2004 10:20:56
22528
Prg
CL_ABAP_ELEMDESCR=============CP
18.12.2004 10:20:34
18432
Prg
CL_ABAP_DATADESCR=============CP
18.12.2004 10:20:34
14336
Prg
CL_ABAP_REFDESCR==============CP
18.12.2004 10:20:56
16384
Prg
CL_ABAP_STRUCTDESCR===========CP
18.12.2004 10:20:56
19456
Prg
CL_ABAP_COMPLEXDESCR==========CP
18.12.2004 10:20:34
13312
Prg
CL_ABAP_TABLEDESCR============CP
18.12.2004 10:20:56
17408
Prg
CL_ABAP_CLASSDESCR============CP
18.12.2004 10:20:56
23552
Prg
CL_ABAP_OBJECTDESCR===========CP
18.12.2004 10:20:56
26624
Prg
CL_ABAP_INTFDESCR=============CP
18.12.2004 10:20:34
19456
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Prg
CL_ABAP_SOFT_REFERENCE========CP
29.03.2001 16:42:12
7168
Prg
CL_ABAP_REFERENCE=============CP
14.02.2002 14:22:46
6144
Prg
CL_IXML=======================CP
13.12.2002 12:12:08
210944
Prg
CL_IXML_UNKNOWN===============CP
13.12.2002 12:12:08
9216
Prg
SAPFGUICNTL_CFW
14.02.2002 14:22:47
12288
Prg
SAPLSPO1
18.12.2004 11:37:25
43008
Prg
SAPLCSTR
18.12.2004 11:21:47
63488
Typ
MAKT
28.08.1997 08:52:19
2048
Typ
KNA1
18.12.2004 14:35:36
22528
Typ
MARA
02.07.2002 16:31:17
19456
Typ
ZRDSSTOCK
26.11.2007 09:44:15
3072
Prg
CX_SY_OPEN_SQL_DB=============CP
14.02.2002 14:22:47
9216
Typ
SCX_SRCPOS
09.11.2000 14:12:15
1024
Prg
CX_SY_OPEN_SQL_ERROR==========CP
14.02.2002 14:22:47
8192
Prg
CX_SY_SQL_ERROR===============CP
14.02.2002 14:22:47
8192
Prg
CX_DYNAMIC_CHECK==============CP
14.02.2002 14:22:47
8192
Prg
CX_ROOT=======================CP
14.02.2002 14:22:47
9216
Prg
CX_NO_CHECK===================CP
14.02.2002 14:22:47
8192
Prg
CX_SY_NO_HANDLER==============CP
14.02.2002 14:22:47
8192
Typ
SYST
04.12.2000 14:54:51
24576
List of internal tables
PROGRAM=YKSD010DATA=INDT1[]
TABH+ 0(20) = FFFFFFFE974B1D20000000000000000000000026
TABH+ 20(20) = 00000079000006CA0000007900000000FFFFFFFF
TABH+ 40(16) = 0400000000000558001024BC00000000
store = 0xFFFFFFFE974B1D20
ext1 = 0x0000000000000000
id = 38 (0x00000026)
label = 121 (0x00000079)
fill = 1738 (0x000006CA)
leng = 121 (0x00000079)
lopc = 0 (0x00000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000015
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 7 (cmpManyEq)
occu0 = 1
collHash = 0
lock = 0
shrd = 0
visited = 0
unShareable = 0
wasShared = 0
iterIsValid = 0
isShareable = 0
>>>>> Shareable Table Header Data <<<<<
tabi = 0xFFFFFFFE974B1468
pghook = 0xFFFFFFFE975BCBF0
idxPtr = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 2480 (0x000009B0)
lineAlloc = 1840 (0x00000730)
store_id = 20 (0x00000014)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
PROGRAM=YKSD010DATA=INDT[]
TABH+ 0(20) = FFFFFFFE975B87E0FFFFFFFE9744082000000017
TABH+ 20(20) = 0000001C000000000000007900000000FFFFFFFF
TABH+ 40(16) = 04000000000004E8001024BC04000000
store = 0xFFFFFFFE975B87E0
ext1 = 0xFFFFFFFE97440820
id = 23 (0x00000017)
label = 28 (0x0000001C)
fill = 0 (0x00000000)
leng = 121 (0x00000079)
lopc = 0 (0x00000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000013
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 7 (cmpManyEq)
occu0 = 1
collHash = 0
lock = 0
shrd = 0
visited = 0
unShareable = 0
wasShared = 0
iterIsValid = 0
isShareable = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xFFFFFFFE975172E8
pghook = 0xFFFFFFFE975BCCB8
idxPtr = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 2480 (0x000009B0)
lineAlloc = 176 (0x000000B0)
store_id = 145 (0x00000091)
>>>>> 1st level extension part <<<<<
regHook = 0x0000000000000000
hsdir = 0x0000000000000000
ext2 = 0xFFFFFFFE974596A8
>>>>> 2nd level extension part <<<<<
tabhBack = 0xFFFFFFFE974A6B68
delta_head = 0000000000000000000000000000000000000000000000000000000000000000
Directory of Application Tables
Program
Name................ Contents....1........2........3........4........5....+....
YKSD010
SYST |00000000000000x06Ê000000000000
VARI |
T006A | |
SSCRFIELDS |
SSCRTEXTS |
RSDBRUNT
VARID |
SAPLICON
ICONT |
SAPFSDS1
TDCLD |RE DOKU 8R XX XXLIMUDOKUX x1E0XR3TRPROGX |
SAPLSDOD
DOKIL |
SAPLLANG
T002 |ES1EN|
SAPLOLEA
TOLE |SAP.DATAPROVIDER.1 {799104C5-04C5-11D0-
SAPSHDTV
SHDSTU | |
SHDSTCIU | |
CL_GUI_PROPS_CONSUMER=========CP
EUDB |%C0009900047492F0EC1BC16DDE1000000C0A80197 0000
CL_GUI_FRONTEND_SERVICES======CP
EUDB |FE0009900047492F0EC1BC16DDE1000000C0A80197 0000
Directory of Application Tables (Administrative Information)
Program
Name.......................... Time.......... Length...
CL_GUI_FRONTEND_SERVICES======CP
SYST 20010612125650 00002404
VARI 00002972
T006A 00000056
SSCRFIELDS 20000323224119 00000854
SSCRTEXTS 00000371
RSDBRUNT
VARID 00000132
SAPLICON
ICONT 00000065
SAPFSDS1
TDCLD 00000050
SAPLSDOD
DOKIL 00000076
SAPLLANG
T002 00000005
SAPLOLEA
TOLE 00000197
SAPSHDTV
SHDSTU 00000053
SHDSTCIU 00000050
CL_GUI_PROPS_CONSUMER=========CP
EUDB 00003940
CL_GUI_FRONTEND_SERVICES======CP
EUDB 00003940
ABAP control blocks CONT
Include Line source code
Index Name F1 Co Par01 Par2. Par3. Par4. Tabl
YKSD010 667 LOOP AT INDT1.
1029 LOOP 05 36 37
1033 BRAN 05 Branch to 1043
YKSD010 669 INDT1-WERKS = WERKS.
1034 mvqk 04 178 946
YKSD010 670 INDT1-DAT1 = VDFRM.
1036 mvqk 08 162 982
YKSD010 671 INDT1-DAT2 = VLDTO.
1038 mvqk 08 170 1022
YKSD010 675 MODIFY INDT1.
1040 TMOD 04 36 37
YKSD010 677 ENDLOOP.
1042 BRAX 01 Branch to 1029
YKSD010 685 INSERT ZRDSSTOCK FROM TABLE IN
1043 SQLS 0B
1044 SQLS 00 107
1045 PAR1 00 131
1046 SQLS 39 1
1047 SQLS 39 37
>>>>> SQLS 1D 36
YKSD010 701 LOOP AT INDT1.
1049 LOOP 03 79 36 37
1053 LOOP 05 36 37
1057 BRAN 05 Branch to 1111
YKSD010 703 AT LAST.
1058 CNTL 04
1062 BRAN 03 Branch to 1080
YKSD010 705 MESSAGE I004.
1063 CATC 08
1064 MOVL 00 2 58 21
End of runtime analysis
Regards
Prajwal.KRefer Amit's reply -
Exception occurred which is assigned to the class 'CX_SY_OPEN_SQL_DB',
Regards,
Amit
Reward all helpful replies.
Maybe you are looking for
-
I have a iphone I do not use as a phone anymore. I use the apps and the music on it though. I downloaded itunes and I am trying to update the phone so I can purchase music and apps for it. When I plug it to the computer it starts syncing and runs a g
-
New FaunOS Live Arch-Based DVD/USB Distro Now Available
Hello fellow archers, We have just released the latest version of FaunOS. Since this version of FaunOS is the answer to the most important question in the universe, we have named it "fortytwo." FaunOS-fortytwo contains many improvements over previous
-
Does Time Machine make Backup obsolete?
I am a relative novice to the world of Macs, but I have been a big fan of Backup. Now that I have Time Machine, I am wondering whether or not I even need Backup anymore. Any advice/guidance would certainly be appreciated. Thanks.
-
Hello all, i am working on EDI X12 over Internet transaction given in user guide.after completing everything in B2B UI tool on both acme and globalchips servers.i ran deq.bat file on both servers giving s*ubscriber=b2berroruser* and wait=1 in ipdeque
-
I am encountering duplicate printing using my MacBook Pro to print to a Kyocera 2550ci Multi-function color printer. This is in an office environment. Irrespective of the application I use, I get 7 copies of each page of each document I print. Thi