Lo que sigue a continuacin es un pequeño DUMP ocurriedo en la mala ejecucin de un programa, vamos a intentar averiguar por que ha petado. En rojo veremos las lineas que analizamos, mientras que en <font color=#00FF00>verde, sern mis comentarios.
Errores tiempo ejecucin RAISE_EXCEPTION
ocurrido el 09.07.2001 a 14:56:15
------------------------------------------------------------------------------------------
>> Dump breve ABAP/4 no grabado completamente (muy grande)
------------------------------------------------------------------------------------------
Exception condition "NOT_FOUND" raised.
Este es el verdadero Error--------------- Qu sucedi ? --------------- The current ABAP/4 program encountered an unexpected situation. ---------------------- Qu se puede hacer ? ----------------------
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the error. Esto es lo tpico que pasa, viene el usuario, con doscientas pginas impresas... jurjur To resolve the problem, contact your SAP system administrator. Y esto es lo que deberiamos hacer nosotros, pasarle el brown a otro.-------------- Anlisis error -------------- A RAISE statement in the program "SAPLCDIC " raised the exception condition "NOT_FOUND". Since the exception was not intercepted by a superior program in the hierarchy, processing was terminated. Short description of exception condition: Entry not found 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. - --------------------------- Notas para corregir errores --------------------------- You may able to find an interim solution to the problem in the SAP note system. If you have access to the SAP note system yourself, please use the following search criteria: ----------------------------------------------------------------------- "RAISE_EXCEPTION" "SAPLCDIC " or "LCDICU01 " "C_DIC_DOMAIN_VALUE_TEXT_READ" ----------------------------------------------------------------------- or "SAPLCDIC " "NOT_FOUND" or "SAPMSVMA " "NOT_FOUND" 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. --------------- Entorno sistema
Aqu est la configuracin bsica de la mquina
--------------- SAP Release.............. "40B" Application server....... "PLUTON" Network address.......... "192.25.2.23" Operating system......... "OS/400" Release.................. "V4R4" Hardware type............ " 730" Database server.......... "PLUTON" Database type............ "DB400" Database name............ "GBF" Database owner........... "R3GBFDATA" Character set............ "ES_ES_ISO1" SAP kernel............... "40B" Created on............... "Jan 30 2001 04:14:29" Created in............... "5769SS1 V4R4 M0 720" Database version......... "DB4 V4R4" Patch level.............. "802" Patch text............... " " Supported environment.... Database................. "V4R4, V4R3, V4R2" SAP database version..... "40B" Operating system......... "OS/400 V4R2 M0, OS/400 V4R3 M0, OS/400 V4R4 M0, OS/400 V4R5 M0" ------------------------ Usuario, transaccin.... ------------------------ Client.............. 004 User................ "USU006" Language key........ "S" Transaction......... "SM30 " Program............. "SAPLCDIC " Screen.............. "SAPLZ450 9100" Screen line......... 6 ------------------------------- Informaciones lugar terminacin ------------------------------- The termination occurred in the ABAP/4 program "SAPLCDIC " in "C_DIC_DOMAIN_VALUE_TEXT_READ". The main program was "SAPMSVMA ". The termination occurred in line 48 of the source code of program "LCDICU01 " (when calling the editor 480). --------------------- Detalle cdigo source
Aqui tenemos el cdigo fuente que ha dado error
--------------------- 000180 * AND DOMVALUE_L = VALUE. 000190 * MOVE BUF_DD07V-DDTEXT TO TEXT. 000200 * EXIT. 000210 * ENDLOOP. 000220 * IF NOT SY-SUBRC IS INITIAL. 000230 * SELECT * FROM DD07V 000240 * WHERE 000250 * DOMNAME = NAME AND 000260 * DDLANGUAGE = SPRAS AND 000270 * DOMVALUE_L = VALUE. 000280 * MOVE DD07V-DDTEXT TO TEXT. 000290 * MOVE-CORRESPONDING DD07V TO BUF_DD07V. 000300 * APPEND BUF_DD07V. 000310 * EXIT. 000320 * ENDSELECT. 000330 * ENDIF. 000340 000350 CALL FUNCTION 'DD_DOMVALUE_TEXT_GET' 000360 EXPORTING 000370 DOMNAME = NAME 000380 VALUE = VALUE 000390 LANGU = SPRAS 000400 IMPORTING 000410 DD07V_WA = DD07V 000420 RC = SY-SUBRC 000430 EXCEPTIONS 000440 OTHERS = 1. 000450 000460 IF SY-SUBRC > 0. 000470 CLEAR TEXT.
-----> RAISE NOT_FOUND.
Y esta es la linea donde realmente ha petado, SAP nos ayuda a encontrarla señalandola con una flecha.000490 ELSE. 000500 MOVE DD07V-DDTEXT TO TEXT. 000510 ENDIF. 000520 000530 ENDFUNCTION. ------------------------
Contenido campos sistema
A partir de aqu podemos ver las variables que tiene y con que las ha llenado
------------------------
Campo SY Contenido.................... Campo SY Contenido....................
-------- ----------------------------- -------- -----------------------------
SY-SUBRC 4 SY-INDEX 1
SY-TABIX 1 SY-DBCNT 0
SY-FDPOS 5 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1
-----------------------
Variables seleccionadas
-----------------------
Nombre........................ Cont. ...1....+....2....+....3....+....4
------------------------------ ----------------------------------------
SY-SUBRC 4
0000
0004
%_?NOT_ASSIGNED?
4444
0000
TEXT
4444444444444444444444444444444444444444
0000000000000000000000000000000000000000
... + 40
44444444444444444444
00000000000000000000
DD07V-DDTEXT
4444444444444444444444444444444444444444
0000000000000000000000000000000000000000
... + 40
44444444444444444444
00000000000000000000
--------------------------
Llamadas / Eventos activos
--------------------------
Nº.... Tipo........ Nombre........................
Programa
Include Lnea
-----------------------------------------------------
1 FUNCTION C_DIC_DOMAIN_VALUE_TEXT_READ
SAPLCDIC
LCDICU01 48
2 FORM BUSCAR_TEXTO
SAPLZ450
ZM450INC 135
3 MODULE (PBO) CARGAR_NOMBRE
SAPLZ450
ZM450INC 26
4 FORM CALL_DYNPRO
SAPLZ450
LSVIMFXX 5034
5 FORM TABLEPROC
SAPLZ450
LSVIMFTX 1164
6 FUNCTION TABLEPROC_Z450
SAPLZ450
LZ450U02 9
7 FORM TABLE_CALL_FUNCTION
SAPLZ450
LSVIMFTX 138
8 FORM TABLEFRAME
SAPLZ450
LSVIMFTX 1012
9 FUNCTION TABLEFRAME_Z450
SAPLZ450
LZ450U01 11
10 FUNCTION VIEW_MAINTENANCE
SAPLSVIM
LSVIMU01 127
11 FUNCTION VIEW_MAINTENANCE_CALL
SAPLSVIM
LSVIMU03 321
12 MODULE (PAI) D0101_PAI
SAPMSVMA
SAPMSVMA 310
-------------
Notas interna
-------------
The termination occurred in the function "ab_jfune" of the SAP
Basis System, specifically in line 1123 of the module "abfunc".
The internal operation just processed is "FUNE".
---------------------------
Llamadas activas kernel SAP
---------------------------
Mon Jul 9 14:56:15 2001
DpMain statement 41 (R3GBF40B/DPDWLIB.DPXXDISP)
tskhstart statement 19 (R3GBF40B/THLIB.THXXHEAD)
TskhLoop statement 363 (R3GBF40B/THLIB.THXXHEAD)
Thdynpen00 statement 40 (R3GBF40B/THLIB.THXXHEAD)
dynpen00 statement 357 (R3GBF40B/DYNPLIB.DYNPMAIN)
dynprctl statement 71 (R3GBF40B/DYNPLIB.DYNPMSTP)
dynppbo0 statement 17 (R3GBF40B/DYNPLIB.DYNPMSTP)
dynpmcal statement 49 (R3GBF40B/DYNPLIB.DYNPMSTP)
ab_dstep statement 36 (R3GBF40B/ABAP4LIB.ABDYNPRO)
ab_xevent statement 2 (R3GBF40B/ABAP2LIB.ABRUNT1)
ab_extri statement 16 (R3GBF40B/ABAP1LIB.ABEXTRI)
ab_jfune statement 29 (R3GBF40B/ABAP1LIB.ABFUNC)
ab_rabax statement 56 (R3GBF40B/ABAP4LIB.ABRABAXR)
CTrcStack statement 7 (R3GBF40B/DPTRCLIB.DPTSTACK)
As4Stack statement 3 (R3GBF40B/DPTRCLIB.DPTSTACK)
---------------------------------
Lista programas ABAP involucrados
---------------------------------
------------------------------------------------------------------------------------------
| Programa | Fecha hora gen. | LoadSize | RollSize |
------------------------------------------------------------------------------------------
| SAPMSVMA | 29.03.2001 17:44:58 | 60 147 | 92 loade |
| SAPLSCNT | 29.03.2001 17:44:58 | 72 1 | 16 loade |
| SAPSHDTV | 29.03.2001 17:44:58 | 80 5 | 68 loade |
| SAPLSVIM | 04.07.2001 14:32:00 | 76 64 | 47 loade |
| SAPLSVIX | 10.05.2001 11:01:01 | 96 103 | 94 loade |
| RDD02DAT | 29.03.2001 17:44:58 | 80 12 | 87 loade |
| SAPLSDD3 | 29.03.2001 17:44:58 | 12 34 | 72 loade |
| SAPLSEQ0 | 29.03.2001 17:45:56 | 64 4 | 00 loade |
| SAPLSUNI | 29.03.2001 17:44:58 | 64 211 | 32 loade |
| SAPLSLDB | 29.03.2001 17:44:58 | 96 7 | 40 loade |
| /1BCDWBEN/SAPLSENQ | 29.03.2001 17:45:56 | 08 | 05 loade |
| SAPLSENA | 29.03.2001 17:44:58 | 60 1 | 72 loade |
| SAPLZ450 | 04.07.2001 14:32:00 | 744 17 | 472 load |
| SAPLSDCO | 29.03.2001 17:44:58 | 88 | 76 loade |
| SAPLBD30 | 09.05.2001 14:49:13 | 52 18 | 40 loade |
| SAPLBDMO | 09.05.2001 14:49:13 | 48 6 | 72 loade |
| SAPLBD22 | 29.03.2001 17:44:58 | 52 11 | 68 loade |
| SAPLSTRD | 09.05.2001 14:52:11 | 04 22 | 50 loade |
| SAPLSTR9 | 29.03.2001 17:44:58 | 76 4 | 26 loade |
| SAPLCDIC | 29.03.2001 17:44:58 | 88 | 91 activ |
| SAPLSDEX | 29.03.2001 17:44:58 | 72 1 | 65 loade |
------------------------------------------------------------------------------------------
---------------------
Lista tablas internas
---------------------
No existe ninguna informacin en el dump.
-----------------------------------
Fin anlisis error tiempo ejecucin
-----------------------------------