Sei sulla pagina 1di 7

Category

ABAP Programming Error


Runtime Errors
SYNTAX_ERROR
ABAP Program
SAPLSPFL
Application Component BC-CCM-CNF-PFL
Date and Time
24.04.2013 13:28:32

Short text
Syntax error in program "SAPLSPFL ".

What happened?
Error in the ABAP Application Program
The current ABAP program "????????????????????????????????????????" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLSPFL " in include "LSPFLF07
" in
line 558:
"The data object "EASY_VAL_START" does not have a component called "RSL"
"GSEND"."
""
""
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "????????????????????????????????????????" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.

What can you do?


Please eliminate the error by performing a syntax check
(or an extended program check) on the program "SAPLSPFL ".
You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
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
The following syntax error was found in the program SAPLSPFL :
"The data object "EASY_VAL_START" does not have a component called "RSL"
"GSEND"."
""
""

How to correct the error


Probably the only way to eliminate the error is to correct the program.
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..... 702
SAP Basis Level. 0010
Application server... "AEOM1SAP08"
Network address...... "172.16.1.87"
Operating system..... "Windows NT"
Release.............. "6.0"
Hardware type........ "4x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 6
Shortdump setting.... "full"

Database
Database
Database
Database

server... "AEOM1SAP04\AED"
type..... "MSSQL"
name..... "AED"
user ID.. "aed"

Terminal.......... "GSC-DT-024"
Char.set.... "C"
SAP kernel....... 720
created (date)... "Apr 15 2013 00:07:23"
create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"
Database version. "SQL_Server_9.00 "
Patch level. 424
Patch text.. " "
Database............. "MSSQL 9.00.2047 or higher"
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...... 8379584
Heap.... 0
Page.... 40960
MM Used. 1123216
MM Free. 3063904

User and Transaction


Client.............. 200
User................ "AEOMBASIS"
Language key........ "E"
Transaction......... "RZ10 "
Transaction ID...... "B2C9ACE26D18F1ABB23D000C2993DDA5"
EPP Whole Context ID.... "000C2993DDA51EE2AB9934E790A9F23D"
EPP Connection ID....... 00000000000000000000000000000000
EPP Caller Counter...... 0
Program............. "????????????????????????????????????????"
Screen.............. " "
Screen Line......... 0
Debugger Active..... "none"

Information on where terminated

Contents of system fields


Name

Val.

SYSUBR
C
SYINDE
X
SYTABI
X
SYDBCN
T
SYFDPO
S
SYLSIN
D
SYPAGN
O
SYLINN
O
SYCOLN
O
SYPFKE
Y
SYUCO
MM
SYTITLE
SYMSGT
Y
SYMSGI
D
SYMSG
NO
SYMSG
V1
SYMSG
V2
SY-

0
0
0
0
0
0
0
1
1

000

MSG
V3
SYMSG
V4
SYMOD
NO
SYDATU
M
SYUZEI
T
SYXPRO
G
SYXFOR
M

0
20130424
132832

Internal notes
The termination was triggered in function "ab_genprog"
of the SAP kernel, in line 1843 of the module
"//bas/720_REL/src/krn/runt/abgen.c#11".
The internal operation just processed is " ".
Internal mode was started at 20130424132832.
Program name.........: "SAPLSPFL ".
Error message........: "The data object "EASY_VAL_START" does not have a
component called "RSL".

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=2932)
When
: 4/24/2013 13:28:30.822
Threads : 2
Computer Name
: AEOM1SAP08
User Name
: SAPServiceAED
Number of Processors: 4
Processor Type: Intel64 Family 6 Model 26 Stepping 5
Windows Version
: 6.0 Current Build: 6001
State Dump for Thread Id 2ac
000000000201C4E0 00000001418B3686 000000000215D9E0 disp+work!DumpStacks
[ntstcdbg.c (548)]
000000000201C5E0 000000014027DC24 00000000754EA000 disp+work!
NTDebugProcess [ntstcdbg.c (383)]

000000000201C610 00000001404C840A 00000000754EA000 disp+work!CTrcStack


[dptstack.c (183)]
000000000201C660 00000001404CE05B 0000000000000000 disp+work!
rabax_CStackSave [abrabax.c (8695)]
000000000201CF70 00000001404A72D6 0000000000000000 disp+work!ab_rabax
[abrabax.c (1442)]
000000000201FDD0 00000001407A4032 0000000002021928 disp+work!ab_genprog
[abgen.c (1847)]
000000000201FEB0 00000001407A4914 000000000000BABA disp+work!newload
[abload1.c (353)]
000000000201FEE0 00000001407A4B10 0000000002021928 disp+work!
ab_LoadProgOrTrfo [abload1.c (159)]
000000000201FF10 0000000140471457 0041004E0041004D disp+work!ab_load
[abload1.c (68)]
000000000201FFA0 00000001402DB417 00000000020219C0 disp+work!
ab_LoadMainProg [abdynpro.c (307)]
0000000002021890 00000001402BFDE0 0000000000000032 disp+work!dystartx
[dytransact.c (1059)]
0000000002026C10 00000001404EFCE3 0000000000000000 disp+work!dy_cdiag
[dynpabsv.c (1973)]
0000000002028480 00000001404794CA 0000000000000000 disp+work!
ab_ctransaction [abtcod.c (704)]
0000000002028D10 000000014047B39F 0000000000000011 disp+work!ab_retdynp
[abdynpro.c (822)]
0000000002028DA0 00000001402F3E46 0000000000000011 disp+work!ab_dstep
[abdynpro.c (637)]
0000000002028F50 00000001402F865A 000007DF000CA0E0 disp+work!dynpmcal
[dymainstp.c (2903)]
0000000002028FE0 00000001402F7BC3 0000000000000000 disp+work!dynppai0
[dymainstp.c (1229)]
00000000020290B0 00000001402AB367 0020002000200020 disp+work!dynprctl
[dymainstp.c (473)]
000000000202F320 00000001401173BB 0000000000000000 disp+work!dynpen00
[dymain.c (2070)]
000000000202FDF0 0000000140117BBC FFFFFFFFFFFFFF00 disp+work!TskhLoop
[thxxhead.c (4896)]
000000000202FE50 0000000140031459 000000000215B1F8 disp+work!ThStart
[thxxhead.c (1190)]
000000000202FEF0 00000001400010B1 FFFFFFFF00000001 disp+work!DpMain
[dpxxdisp.c (1201)]
000000000202FF20 0000000141BE7EE0 0000000002030000 disp+work!nlsui_main
[thxxanf.c (80)]
000000000202FF50 00000000773C43BD 0000000000000000 disp+work!
__tmainCRTStartup [crtexe.c (594)]
000000000202FF80 00000000774F81D1 0000000000000000 kernel32!
BaseThreadInitThunk
000000000202FFD0 0000000000000000 0000000000000000 ntdll!
RtlUserThreadStart
State Dump for Thread Id c60
000000000BA9FDE0 00000000773AB310 0000000000000000 ntdll!ZwFsControlFile
000000000BA9FE50 0000000141ABAACF FFFFFFFFFFFFFFFE kernel32!
ConnectNamedPipe
000000000BA9FEF0 00000000754337D7 00000000039886E0 disp+work!SigIMsgFunc
[signt.c (717)]
000000000BA9FF20 0000000075433894 00000000754E95C0 MSVCR80!endthreadex

000000000BA9FF50 00000000773C43BD 0000000000000000 MSVCR80!endthreadex


000000000BA9FF80 00000000774F81D1 0000000000000000 kernel32!
BaseThreadInitThunk
000000000BA9FFD0 0000000000000000 0000000000000000 ntdll!
RtlUserThreadStart

Potrebbero piacerti anche