on 08-20-2008 5:11 PM
we recently upgraded our development test sandbox from 46C to ECC6.0 using downtime minimized strategy for practice purposes.After a sucessful completion of the upgrade we applied all the support packages successfully upto the latest available. Upon testing we found that everything else works fine except code inspector. Everytime we go to transaction sci we get syntax error
Runtime Errors SYNTAX_ERROR
Date and Time 08/20/2008 08:26:29
Short text
Syntax error in program "SAPLS_CODE_INSPECTOR ".
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 "SAPLS_CODE_INSPECTOR " in
include "LS_CODE_INSPECTORTOP " in
line 11:
""SCI_DYNP" must be a flat structure. You cannot use internal tables, s"
"trings, references, or structures as components. ."
" "
" "
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "CRENSHAWDP "
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 "SAPLS_CODE_INSPECTOR ".
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.
r analysis
The following syntax error was found in the program SAPLS_CODE_INSPECTO
""SCI_DYNP" must be a flat structure. You cannot use internal tables, s
"trings, references, or structures as components. ."
" "
" "
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
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.
tem environment
SAP-Release 700
Application server... "kiel"
Network address...... "138.254.140.161"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "000B7B2ED600"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "kiel"
Database type..... "ORACLE"
Database name..... "UPD"
Database user ID.. "SAPR3"
Terminal................. "D800204486"
Char.set.... "en_US.ISO8859-1"
SAP kernel....... 700
created (date)... "Jun 22 2008 20:58:25"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 166
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 16128
EM...... 8379840
Heap.... 0
Page.... 40960
MM Used. 705904
MM Free. 3481488
r and Transaction
Client.............. 070
User................ "CRENSHAWDP"
Language key........ "E"
Transaction......... "SCI "
Transactions ID..... "48AB59A7D7E00112E10080008AFE8CA1"
Program............. "????????????????????????????????????????"
Screen.............. " "
Screen line......... 0
Information on where terminated
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 0
SY-DBCNT 0
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE
SY-MSGTY
SY-MSGID
SY-MSGNO 000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20080820
SY-UZEIT 082629
SY-XPROG
SY-XFORM
Internal notes
The termination was triggered in function "ab_genprog"
of the SAP kernel, in line 1551 of the module
"//bas/700_REL/src/krn/runt/abgen.c#10".
The internal operation just processed is " ".
Internal mode was started at 20080820082629.
Program name.........: "SAPLS_CODE_INSPECTOR ".
Error message........: ""SCI_DYNP" must be a flat structure. You cannot use
internal tables, s".
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit = 2684354560
=> Stack limit = unlimited
=> Core limit = unlimited
=> File size limit = unlimited
=> Heap address = 0x11716f260
=> Stack address = 0xfffffffffff2a20
=> Stack low = 0xfffffffffff2a20
=> Stack high = 0xffffffffffff710
=> Stack Trace:
#AixStack() at 0x1000a2474
#CTrcStack2() at 0x1000a256c
#rabax_CStackSave__Fv() at 0x1000d0e04
#ab_rabax() at 0x1000cd7e4
#ab_genprog() at 0x100b3d5f8
#newload__FPCcP13TmpSubpoolDirUiPUi() at 0x1002194ac
#ab_LoadProgOrTrfo__FPCcUiPUi() at 0x10021905c
#ab_load() at 0x100218e2c
#ab_LoadMainProg() at 0x100820d6c
#dystartx() at 0x100ade944
#dy_cdiag() at 0x100833174
#ab_ctransaction__Fv() at 0x100ae1ef0
#ab_retdynp__Fi() at 0x100821c98
#ab_dstep() at 0x100821924
#dynpmcal() at 0x100e932e0
#dynppai0() at 0x100e905ec
#dynprctl() at 0x100e99d48
#dynpen00() at 0x100e8cc18
#Thdynpen00() at 0x1000f9ed4
#TskhLoop() at 0x1000fec7c
#ThStart() at 0x100115890
#DpMain() at 0x1017f4b14
#nlsui_main() at 0x1018e2b6c
We contacted SAP OSS about this problem and they suggested that we check our LS_CODE_INSPECTORTOP include in program SAPLS_CODE_INSPECTOR and revert it to the original version. We did that and still are getting this error. Any suggestions how to fix this issue. All advices are welcome.
Thanks.
Kamran
Nope... this is SAP standard code so I will reply to the OSS and wait for them to come back to you.
Regards
Juan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.