2009 Jul 09 2:24 PM
Hello Experts,
I m copying standard Report MB51 to my Z Report.
My Z report is working fine.But MB51 is showing dump .I can clearly make out that (when compare to PRD) in Standard report RM07DOCS_Generated, where there is selection-screen declaration part all that is removed
and internal table ITAB is removed .
Plz suggest.
Aastha
Hello Experts,
I m copying standard Report MB51 to my Z Report.
My Z report is working fine.But MB51 is showing dump .I can clearly make out that (when compare to PRD) in Standard report RM07DOCS_Generated, where there is selection-screen declaration part all that is removed
and internal table ITAB is removed .
Plz suggest.
Aastha
2009 Jul 09 2:25 PM
Hi
Send the dump message please so we can meke some comments.
Edited by: Gungor Ozcelebi on Jul 9, 2009 3:25 PM
2009 Jul 09 2:30 PM
Hello.,
Plz check
Runtime errors SYNTAX_ERROR
Occurred on 09.07.2009 at 17:23:46
-
Syntax error in program "RM07DOCS ".
-
What happened?
-
The following syntax error occurred in the program RM07DOCS :
"The field string "ITAB" contains no fields."
Error in ABAP application program.
The current ABAP program "????????????????????????????????????????" 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?
-
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "RM07DOCS ".
You can also perform the syntax check from the ABAP/4 Editor.
If the problem persists, proceed as follows:
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
-
The following syntax error was found in the program RM07DOCS :
"The field string "ITAB" contains no fields."
-
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, 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....... "sam_dev"
Network address.......... "172.16.1.51"
Operating system......... "AIX"
Release.................. "5.1"
Hardware type............ "0051495A4C00"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "sam_dev"
Database type............ "ORACLE"
Database name............ "DEV"
Database owner........... "SAPDEV"
Character set............ "en_US.ISO8859-1"
SAP kernel............... "640"
Created on............... "Oct 29 2006 20:42:11"
Created in............... "AIX 1 5 00538A4A4C00"
Database version......... "OCI_920 "
Patch level.............. "155"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
-
User, transaction...
-
Client.............. 100
User................ "ABAP04"
Language key........ "E"
Transaction......... "MB51 "
Program............. "????????????????????????????????????????"
Screen.............. "############################################"
Screen line......... 0
-
Information on where terminated
-
-
Contents of system fields
-
SY field contents..................... SY field contents.....................
-
-
-
-
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
-
Active calls / events
-
No dump information available
-
Chosen variables
-
No dump information available
-
Application Calls
-
No dump information available
-
Application Information
-
No dump information available
-
Internal notes
-
The termination occurred in the function "ab_genprog" of the SAP
Basis System, specifically in line 1406 of the module
"//bas/640_REL/src/krn/runt/abgen.c#11".
The internal operation just processed is " ".
The internal session was started at 20090709172345.
Program name.........: "RM07DOCS ".
Error message........: "The field string "ITAB" contains no fields.".
-
Active calls in SAP kernel
-
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit = unlimited
=> Stack limit = 2147483647
=> Core limit = 1073741312
=> File size limit = unlimited
=> Heap address = 0x1154568e0
=> Stack address = 0xfffffffffff0ef0
=> Stack low = 0xfffffffffff0ef0
=> Stack high = 0xffffffffffff780
=> Stack Trace:
AixStack() at 0x10002092c
CTrcStack2() at 0x100020a24
rabax_CStackSave__Fv() at 0x10015357c
ab_rabax() at 0x1001503ac
ab_genprog__FPcPvUii() at 0x100497d6c
newload__FPcP13TmpSubpoolDirUi() at 0x1007df59c
ab_LoadProg__FPcUi() at 0x1007df070
ab_LoadMainProg() at 0x1005b85c0
ab_strep() at 0x10107c708
dystartx() at 0x101078d00
dy_cdiag() at 0x1005b2fa4
ab_ctransaction__Fv() at 0x10132f8c8
ab_retdynp__Fi() at 0x1005b93bc
ab_dstep() at 0x1005b9064
dynpmcal() at 0x1010dd988
dynppai0() at 0x1010dab58
dynprctl() at 0x1010e4704
dynpen00() at 0x100be69e0
Thdynpen00() at 0x1000a26c0
TskhLoop() at 0x1000a6fc0
tskhstart() at 0x1000bc1e8
DpMain() at 0x1015982cc
nlsui_main() at 0x10156b560
-
List of ABAP programs affected
-
-
No dump information available
-
List of internal tables
-
No dump information available
-
Directory of Application Tables
-
No dump information available
-
Directory of Application Tables (Administrative Information)
-
No dump information available
-
ABAP control blocks CONT
-
No dump information available
-
End of runtime analysis
-
2010 Nov 30 5:33 AM
Hi Aastha,
Have you Got The Solution? If Yes I am also Getting Same Problam but My Itab Getting Some Extra Field .
Thanks.
Regards:Hemant GUlati(A1)
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |