Internal table size - short dump
Hi all,
I am getting following error:
'Following a SELECT statement, the data read could not be placed in AN
the output area.
A conversion may have been intended that is not supported by the
system, or the output area may be too small.'
Actually I am extracting data into an internal table. I have implemented my own logic to fetch data in packets. And after each packet, I am freeing the internal table using FREE command. After fetching 16 data packets, it gives me this error.
Please help me with this.
Thanks and regards,
Ridhima
It gives short dump in selecting data from ETXDCJ
*-- Local Data
DATA: t_etxdch TYPE STANDARD TABLE OF tp_etxdch,
t_etxdci TYPE STANDARD TABLE OF tp_etxdci,
t_etxdcj TYPE STANDARD TABLE OF tp_etxdcj,
t_docnr TYPE STANDARD TABLE OF tp_docnr,
wa_etxdch TYPE tp_etxdch,
wa_etxdci TYPE tp_etxdci,
wa_etxdcj TYPE tp_etxdcj,
wa_docnr TYPE tp_docnr,
wa_data TYPE zoxdev0388,
l_lines TYPE sy-tabix,
l_line1 TYPE sy-tabix,
l_times TYPE sy-index,
l_div TYPE sy-index,
l_cnt1 TYPE sy-tabix,
l_cnt2 TYPE sy-tabix.
*-- Clean Up
CLEAR: t_etxdch[],
t_etxdci[],
t_etxdcj[],
t_docnr[].
*-- Get the document numbers selected in extraction
LOOP AT c_t_data.
CLEAR wa_docnr.
wa_docnr = c_t_data-docnr.
APPEND wa_docnr TO t_docnr.
ENDLOOP.
DATA: t_doc TYPE STANDARD TABLE OF tp_docnr,
wa_doc TYPE tp_docnr.
DESCRIBE TABLE t_docnr LINES l_lines.
CHECK l_lines IS NOT INITIAL.
WHILE l_cnt2 LE l_lines.
l_cnt1 = l_cnt2 + 1.
l_cnt2 = l_cnt1 + 200.
APPEND LINES OF t_docnr FROM l_cnt1 TO l_cnt2 TO t_doc.
SORT t_doc BY docnr.
DELETE ADJACENT DUPLICATES FROM t_doc COMPARING docnr.
*-- Get Header data
SELECT docnr
client
currency
gl_currency
FROM etxdch
INTO TABLE t_etxdch
FOR ALL ENTRIES IN t_doc
WHERE docnr = t_doc-docnr.
*-- Success
IF sy-subrc IS INITIAL.
SORT t_etxdch BY docnr.
ENDIF.
*-- Get Item data
SELECT docnr
itemnr
quantity
unit
amount
gross_amount
freight_am
exempt_amt
taxpcov
taxamov
gl_taxpcov
gl_taxamov
FROM etxdci
INTO TABLE t_etxdci
FOR ALL ENTRIES IN t_doc
WHERE docnr = t_doc-docnr.
*-- Success
IF sy-subrc IS INITIAL.
SORT t_etxdci BY docnr
itemnr.
ENDIF.
*-- Get Jurisdiction data
SELECT docnr
itemnr
txjlv
taxpct
taxamt
taxbas
examt
gl_taxpct
gl_taxamt
gl_taxbas
FROM etxdcj
INTO TABLE t_etxdcj
FOR ALL ENTRIES IN t_doc
WHERE docnr = t_doc-docnr.
*-- Success
IF sy-subrc IS INITIAL.
SORT t_etxdcj BY docnr
itemnr
txjlv.
ENDIF.
*-- Populate the enhanced fields
CLEAR wa_data.
LOOP AT c_t_data INTO wa_data FROM l_cnt1 TO l_cnt2.
*-- Populate Header fields
CLEAR wa_etxdch.
READ TABLE t_etxdch INTO wa_etxdch WITH KEY docnr = wa_data-docnr
BINARY SEARCH.
IF sy-subrc IS INITIAL.
wa_data-yyclient = wa_etxdch-client.
wa_data-yycurrency = wa_etxdch-currency.
wa_data-yygl_currency = wa_etxdch-gl_currency.
ENDIF.
*-- Populate Item fields
CLEAR wa_etxdci.
READ TABLE t_etxdci INTO wa_etxdci WITH KEY docnr = wa_data-docnr
itemnr = wa_data-itemnr
BINARY SEARCH.
IF sy-subrc IS INITIAL.
wa_data-yyquantity = wa_etxdci-quantity.
wa_data-yyunit = wa_etxdci-unit.
wa_data-yyamount = wa_etxdci-amount.
wa_data-yygross_amount = wa_etxdci-gross_amount.
wa_data-yyfreight_am = wa_etxdci-freight_am.
wa_data-yyexempt_amt = wa_etxdci-exempt_amt.
wa_data-yytaxpcov = wa_etxdci-taxpcov.
wa_data-yytaxamov = wa_etxdci-taxamov.
wa_data-yygl_taxpcov = wa_etxdci-gl_taxpcov.
wa_data-yygl_taxamov = wa_etxdci-gl_taxamov.
ENDIF.
*-- Populate Jurisdiction fields
CLEAR wa_etxdcj.
READ TABLE t_etxdcj INTO wa_etxdcj WITH KEY docnr = wa_data-docnr
itemnr = wa_data-itemnr
txjlv = wa_data-txjlv
BINARY SEARCH.
IF sy-subrc IS INITIAL.
wa_data-yytaxpct = wa_etxdcj-taxpct.
wa_data-yytaxamt = wa_etxdcj-taxamt.
wa_data-yytaxbas = wa_etxdcj-taxbas.
wa_data-yyexamt = wa_etxdcj-examt.
wa_data-yygl_taxpct = wa_etxdcj-gl_taxpct.
wa_data-yygl_taxamt = wa_etxdcj-gl_taxamt.
wa_data-yygl_taxbas = wa_etxdcj-gl_taxbas.
ENDIF.
*-- Update values in Extract structure
MODIFY c_t_data FROM wa_data.
CLEAR wa_data.
ENDLOOP.
CLEAR: t_doc[].
FREE : t_etxdch,
t_etxdci,
t_etxdcj.
ENDWHILE.
Similar Messages
-
Short dump-internal table size issue
Hi,
I get the following message in the short dump analysis for a report.
No storage space available for extending table "IT_920".
You attempted to extend an internal table, but the required space was not available.
Error Analysis:
The internal table "IT_920" could not be enlarged further.
To extend the internal table, 9696 bytes of storage space was
needed, but none was available. At this point, the table "IT_920" has
1008240 entries.
Its an old report and I saw the internal table declaration using the "OCCURS" clause in the internal table declaration.
begin of itab occurs 100.
end of itab.
I tried the option of changing to "OCCURS 0", still issue persists.
Any help would be highly appretiated
CMHello CMV,
This is basic problem with SAP internal tables. For every internal table memory is alocated ( Max..256K)...once you cross the memory size/limit of the internal table it resuls in short dump.
Only way to overcome this problem is handle limited number of records at a time..
Please refer following sample code which will help you to avoid short dump while processing large number of records....
SORT TAB_RESULT.
DESCRIBE TABLE TAB_RESULT LINES W_RECORDS.
W_LOW = 1.
W_UP = 1000.
*Spliting the records from tab_result1 by pakage of 1000 at a time
*to avoid short dump in case of more records
WHILE W_LOW <= W_RECORDS.
R_PKUNWE-SIGN = 'I'.
R_PKUNWE-OPTION = 'EQ'.
R_WERKS-SIGN = 'I'.
R_WERKS-OPTION = 'EQ'.
LOOP AT TAB_RESULT FROM W_LOW TO W_UP.
MOVE TAB_RESULT-PKUNWE TO R_PKUNWE-LOW.
MOVE TAB_RESULT-WERKS TO R_WERKS-LOW.
APPEND R_PKUNWE.
APPEND R_WERKS.
ENDLOOP.
*fetch sold to party
SELECT KUNNR NAME1
FROM KNA1
APPENDING CORRESPONDING FIELDS OF TABLE TAB_KNA1
WHERE KUNNR IN R_PKUNWE.
*fetch plant
SELECT WERKS NAME1
FROM T001W
APPENDING CORRESPONDING FIELDS OF TABLE TAB_T001W
WHERE WERKS IN R_WERKS.
REFRESH: R_PKUNWE,
R_WERKS.
W_LOW = W_LOW + 1000.
W_UP = W_UP + 1000.
ENDWHILE.
Hope this will help you to solve problem.
Cheers,
Nilesh -
Short Dump to extending internal table memory
Hi All,
I have an internal table with 10 million records . While appending records to this internal table iam getting dump as "No storage space available for extending the internal table." .I declared internal table with "OCCURS 0 "How can i avoid this dump ?Hi,
The problem seems to be related to overflow of the internal table allocation size which will be set by BASIS people. Like if the internal table size restricted to say 1024KB and if we are trying to push data more than this it will throw such error.
Please try to split them into more smaller but several internal tables. Also try to restrict the number of records selected, if they are not really required to be selected.
Regards,
Ferry Lianto -
Query related to Internal Table
Hi ,
I have a small query related to internal table , can we dump millions of records to an internal .
The actual requirment is like i need to develop a report in BI side where i have to dump records into an internal table from PSA tables without filtering .
Can we do so ....
or do we have any other option to dump the data to an internal tables .
need some tips on the same .
Thanks ,
VInay.Hello Vinay,
I believe the following extract will give you a brief idea on the size limitations for an internal table.......
Internal tables are dynamic data objects, since they can contain any number of lines of a particular type. The only restriction on the number of lines an internal table may contain are the limits of your system installation. <u><i>The maximum memory that can be occupied by an internal table (including its internal administration) is 2 gigabytes. A more realistic figure is up to 500 megabytes. An additional restriction for hashed tables is that they may not contain more than 2 million entries.</i></u>
Hope it proved useful
Reward if helpful
Regards
Byju -
Internal table data 1E2 automatically convert to scientific format
Dear all,
I have been searched for solution moths from the forums and tried all possible methods, but still no way to solve my above problem. I found a way to solve it partially for us, but may be very helpful for others who meet similly case like mine, so I posted here.
my problem is when I export my internal table data to Excel, the Cell data with 1E2 auto becomes 1.00E02, and 1E8 becomes 1.00E08, we need it to be 1E2 and 1E8 in excel.
you can recreate my problem by
1, input 1E2 into your Microsoft Excel, then Enter, it will auto change into scientific format. which is we do not want.
2, use any of your SAP system open any table as long as there is a Char (>3) field in that table. add some
data entry in that field in the form "any amount (<15) of numeric 1 to 9"E"any one or two numeric 1 to 9". such as, 123E2, 1234E12 etc. then save this table's data to local file spread sheet, or use any FM to download it to a Excel file, when you open this
file by Excel, the cell with above form will display as scientific. but
if you put three or more numeric after the "E", such as 123E123 it will
display correctly.
what I have done:
I searched in SCN for similar thread:
Export to Excel 2007 - item number problem
Exceding the limit of numbers in Excel at target side
Excel download cell format problem
Formating as Text in excel through SAP
Converting of amount field into excel file through GUI DOWNLOAD
Data downloaded to excel gets converted to exponential format.
Problem with Excel download and scientific number
Re: Issue in displaying numbers in Excel?
CSV Flat File Data Problem (Number converting to Scientific Notation)
Tested accordingly, But none of these works in our case. because our
ultimate receiver of email attachment will be external third party, we cannot ask
them to change anything in their Excel.
Search Microsoft help about Excel, http://support.microsoft.com/kb/214233,
and it says this "Automatic Number Formatting" is a normal behaviour of excel.
no way to turn it off, the "work-around" way that Microsoft provides is not suitable for our
case.
We test CL_iXML recently arrording to weblog http://wiki.sdn.sap.com/wiki/display/Snippets/FormattedExcelasEmailAttachment
it successful controled the format. so this could be a solution for others whose internal table size is small. but our 2MB internal table bocome 6MB when converted to xml file attachment, which cannot be received by our end user's mail box. too big.
So please advise your ideas.
Many thanks in advance!
Peter Ding
Thank you very much for your time!Hi,
You can achieve this by describing the spreadsheet in XML with the help of the DOM classes.
The later releases of Excel can read and save spreadsheets as XML, providing your release supports this you can achieve it.
Check out the following Wiki
[Excel - XML|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/abap/exporting%2bdata%2bto%2bexcel%2b-%2bxml%2bto%2bthe%2brescue]
Regards,
Darren -
Hello abap-gurus,
I have a small problem when doing a select into an internal table. As i select and append into an internal table, the program dumps as there is not enough memory for the internal table. The SAP-table i'm selecting from is simply too big. So I'm wondering if there is a way to stop or set the max lines in the internal table to say 10000 rows? I would appreciate any example.. the statement looks like this:
SELECT * INTO l_bdcpv
FROM bdcpv
WHERE not process = 'X'
AND mestype = 'ISM_MATMAS'.
APPEND l_bdcpv TO i_bdcpv.
ENDSELECT.
Best regards BalloHI,
DATA: I_BDPCV LIKE BDPCV OCCURS 0 WITH HEADER LINE.
SELECT * FROM BDPCV INTO I_BDPCV UP TO 100 ROWS WHERE PROCESS NE 'X' AND MESTYPE = 'ISM_MATMAS'.
APPEND I_BDPCV.
ENDSELECT.
Regards
CNU -
Need help regarding short dumps in BW
hi all,
We have a problem in our production.Thousands of short dumps have been created in a day stating
"Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB"
=====================
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 "INSERT_ODS"
"(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The exception must either be prevented, caught within the procedure
"INSERT_ODS"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-14400: inserted partition key does not map to
any partition"
===================
The RSRV check shows "Inconsistency: High value for table /BIC/B0000xxx000: 0002 ; PARTNO value in RSTSODS: 010."
When a repair was run on this table the short dumps stopped.Is there any other steps that should be taken to avoid such dumps in future/is there something that we have missed to maintainin in BW.
Please explain in detail, it will be of great help.
ThanksHi All,
Thanks a lot for the valuable messages.
So when all these stated notes are followed, and if in future if a simillar problem comes, the recovery step would be running the RSRV test and repair on the particular object?
Thanks once again.
Shailaja -
Short dump while reading a currency field from Flat file into internal tabl
Hi,
I am getting a short dump........saying number conversion dump (while reading a currency value into field in internal table from a fixed lenght flat file).........
Do I need to use a string variable to get the value from flat file or how ??
Please suggest.Santosh,
Thanks for your inputs,
But my internal table type is of DEC (5,2) , I am getting that... it needs to be of type 'C'. Can you suggest.
Ex :
MOVE wa_temp-infile_string+106(8) TO wa_item-QT_PERCENT
This didnt work
so i tried moving into a seperate variable
MOVE wa_temp-infile_string+106(8) TO v_percent.
and then write to
WRITE v_percent to wa_item-QT_PERCENT. -
Short dump - No more storage space available for extending an internal tabl
Hi All,
I have requirement in which my program generates a text file on my presentation server. Here my problem is, this requirement can not be executed in back ground, it should be done in foreground only. When I execute in foreground, if the data records comes to some 38 lacks then I am getting a short dump saying 'No more storage space available for extending an internal table'.
And in dump analysis under WHAT HAPPENED section it is giving as
' What happened? |
| You attempted to extend an internal table, but the required space was |
| not available.
Please suggest me, what I have to do in this case?
Thanks in advance.
Thanks,
Sudha MettuHi SuDash,
Allocation of the memory spaces will be done by BASIS people.
you can contact them..
Regards! -
Short dump -No more storage space available for extending an internal table
Hi All,
While running one program I get the short dump saying
"No more storage space available for extending an internal table "IT_862".
Error Analysis given in the dump log :
The internal table "IT_862" could not be enlarged further.
To extend the internal table, 14656 bytes of storage space was
needed, but none was available. At this point, the table "IT_862" has
8528862 entries.
Source Code Extract :
003360 loop at t_line.
003370 clear t_output.
003380
003390 * Increment Line counter
003400 add 1 to l_line_cnt.
003410
003420 t_output-object = t_stxh-tdobject.
003430 t_output-id = t_stxh-tdid.
003440 t_output-spras = t_stxh-tdspras.
003450 t_output-name = t_stxh-tdname.
003460 t_output-line = l_line_cnt.
003470 t_output-format = t_line-tdformat.
003480 t_output-text = t_line-tdline.
*> append toutput. " ERROR POINT*
Can you please suggest what can be the possible solution for the above error.
Thanks in advance.
SanjeetHi
Check out this thread:
Re: No storage space available for extending the internal table
Make sure you are not having an infinite loop.
Hope this helps
Regards,
Jayanthi.K -
Short Dump while INSERTING to a DB Z table
There is one report that we are running in production. Earlier it was taking about 2hrs to run and now it's taking about 14-15 hours to run after we applied the Support Pack. I must agree that the report is not well written by the previous developers and I have been asked to rewrite it but in the meanwhile, they want to continue running the old one.
This report deletes all the existing records first and then updates a Z table. Last week when they tried to run the report as batch job it got cancelled after running 22000 secounds and my basis team told me that logs are getting saturated and we need to use Truncate Statement instead of DELETE from table statement and that is what I did but again when they tried running the report in production it got cancelled again and this time after 55000 secs and this time it's getting cancelled in the last step when we are inserting the records back to the table from the internal table.
So can you please tell me how can I take care of this.
My Findings:
1. Report updates a Z table for 700K records which is really not a very big size.
2. Z table size category is customized for upto 48K to 93K . Does this matter when I try to update 700K records at a time.
3. There is no foreign key relations in the Z table
4. I feel that, it could be a basis problem like, memory related. Any light on this?
5. The program currently uses INSERT statement.Can I try for a success using MODIFY statement. All validations are handled before inserting to remove the duplicates.So I dont see any issues using INSERT statement
6. Can we use a commit statement after INSERT or MODIFY?
7. From SAP help, I see that there is a limitation on the number of records can be inserted or modified. Any idea on the number?
Thanks & Best Regards,
Kiran Babu DasariDump:
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Date and Time 01/01/2009 10:17:22
Short text
SQL error in the database when accessing a table.
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.
How to correct the error
Database error text........: "SQL0964C The transaction log for the database is
full. SQLSTATE=57011 row=1"
Internal call code.........: "[RSQL/INSR/ZTMM_PU_FOR_BW ]"
Please check the entries in the system log (Transaction SM21).
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_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"ZPMM_BWLOAD_R_V2" or "ZPMM_BWLOAD_INC02"
"FILL_ZTMM_PU_FOR_BW"
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.
The exception must either be prevented, caught within proedure
"FILL_ZTMM_PU_FOR_BW" "(FORM)", or its possible occurrence must be declared in
the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "ucerp13"
Network address...... "192.168.254.23"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "00C4B5BE4C00"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 34
Shortdump setting.... "full"
Database server... "ucerp10"
Database type..... "DB6"
Database name..... "RP1"
Database user ID.. "SAPRP1"
Terminal................. " "
Char.set.... "C"
SAP kernel....... 700
created (date)... "Oct 26 2008 20:51:39"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "DB6_81 "
Patch level. 183
Patch text.. " "
Database............. "DB6 08.02., DB6 09."
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 16192
EM...... 234631488
Heap.... 0
Page.... 24576
MM Used. 28706288
MM Free. 197532304
User and Transaction
Client.............. 400
User................ "BATCHUC"
Language key........ "E"
Transaction......... " "
Transactions ID..... "49597E9619C40076E1008000C0A8FE17"
Program............. "ZPMM_BWLOAD_R_V2"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "ZPMM_BWLOAD_R_V2" - in
"FILL_ZTMM_PU_FOR_BW".
The main program was "ZPMM_BWLOAD_R_V2 ".
In the source code you have the termination point in line 2886
of the (Include) program "ZPMM_BWLOAD_INC02".
The program "ZPMM_BWLOAD_R_V2" was started as a background job.
Job Name....... "ZPMM_BWLOAD_R_V2"
Job Initiator.. "BATCHSCHED"
Job Number..... 10261500
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "FILL_ZTMM_PU_FOR_BW" "(FORM)", but it was neither handled locally
nor declared
in the RAISING clause of its signature.
The procedure is in program "ZPMM_BWLOAD_R_V2 "; its source code begins in line
2751 of the (Include program "ZPMM_BWLOAD_INC02 ".
Source Code Extract
Line
SourceCde
2856
itab_result-rec_no = recnum.
2857
ENDIF.
2858
2859
11/30/05 - Change it back after sorting
2860
IF linetype = 'AAA'.
2861
itab_result-linetype = 'INI'.
2862
ENDIF.
2863
itab_result-extractdate = e_sdate.
2864
itab_result-mandant = sy-mandt.
2865
MODIFY itab_result INDEX indx.
2866
2867
SELECT SINGLE
2868
rec_no
2869
ponumber
2870
FROM ztmm_pu_for_bw
2871
INTO CORRESPONDING FIELDS OF itab_duprec
2872
WHERE rec_no = recnum
2873
AND ponumber = pono
2874
AND linetype = linetype
2875
AND line_no = lineno
2876
AND changenr = chgno
2877
AND chgind_h = indh
2878
AND chgind_p = indp
2879
AND tblname = tbl
2880
AND fldname = fld.
2881
IF sy-subrc <> 0.
2882
MOVE-CORRESPONDING itab_result TO itab_result_bw.
2883
APPEND itab_result_bw.
2884
nrecs_results = nrecs_results + 1.
2885
>>>>>
INSERT ztmm_pu_for_bw FROM TABLE itab_result_bw.
2887
INSERT zztmm_pu_for_bw FROM TABLE itab_result_bw.
2888
2889
CLEAR itab_result_bw.
2890
REFRESH itab_result_bw.
2891
ENDIF.
2892
ENDLOOP.
2893
*change to array insert for performance
2894
INSERT ZZTMM_PU_FOR_BW FROM TABLE itab_result_bw.
2895
2896
ENDFORM. " fill_ztmm_pu_for_bw
Contents of system fields
Name
Val.
SY-SUBRC
4
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Load Purchasing Info. for BW Reporting
SY-MSGTY
E
SY-MSGID
TD
SY-MSGNO
600
SY-MSGV1
T710-08L04
SY-MSGV2
K01
SY-MSGV3
EN
SY-MSGV4
SY-MODNO
0
SY-DATUM
20081231
SY-UZEIT
190013
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
2 FORM ZPMM_BWLOAD_R_V2 ZPMM_BWLOAD_INC02 2886
FILL_ZTMM_PU_FOR_BW
1 EVENT ZPMM_BWLOAD_R_V2 ZPMM_BWLOAD_R_V2 192
START-OF-SELECTION
Chosen variables
Name
Val.
No. 2 Ty. FORM
Name FILL_ZTMM_PU_FOR_BW
SY
#######ৡ###################A###P#################ż#############################T#######린 u#̀##
00000000000000000000000000000000000000010000000000000000000000000000000000000000000000FB000000
000000090000000000000000000000000000000A0000000001000000000000000000000000000000000000F9000300
0000000E0000000000000000000400050000000B0000000007000000000000000000000000000105000000FB270000
0000010100000000000000000101010000000000000000040C000000000000000000000000000604000000F005000C
ITAB_RESULT_BW-WAERS
USD
00000
00000
55422
53400
ITAB_RESULT-WAERS
USD
00000
00000
55422
53400
ITAB_RESULT_BW+5358(10)
#U#C# #
0205040202
0005030000
ITAB_RESULT+4160(10)
#U#C# #
0205040202
0005030000
AMTCRCHGPOSREGUA2
00000000000
0000000000C
ITAB_RESULT_BW+5378(572)
#S#h#i#p#p#i#n#g# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
0205060607070606060202020202020202020202020202020202020202020202020202020202020202020202020202
000308090000090E070000000000000000000000000000000000000000000000000000000000000000000000000000
ITAB_RESULT+4170(572)
#S#h#i#p#p#i#n#g# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
0205060607070606060202020202020202020202020202020202020202020202020202020202020202020202020202
000308090000090E070000000000000000000000000000000000000000000000000000000000000000000000000000
C_INITIAL
@0E@
000000
000000
434422
005000
ITAB_RESULT_BW-ORT01
Cincinnati
00000000000000000000000000000000000
00000000000000000000000000000000000
46666666762222222222222222222222222
39E39EE1490000000000000000000000000
ITAB_RESULT-ORT01
Cincinnati
00000000000000000000000000000000000
00000000000000000000000000000000000
46666666762222222222222222222222222
39E39EE1490000000000000000000000000
ITAB_RESULT_BW-PSTLZ
45206
0000000000
0000000000
3333322222
4520600000
ITAB_RESULT-PSTLZ
45206
0000000000
0000000000
3333322222
4520600000
ITAB_RESULT_BW-REGIO
OH
000
000
442
F80
ITAB_RESULT-REGIO
OH
000
000
442
F80
ITAB_RESULT_BW-STRAS
2709 Woodburn Ave.
00000000000000000000000000000000000
00000000000000000000000000000000000
33332566667762476222222222222222222
270907FF4252E0165E00000000000000000
ITAB_RESULT-STRAS
2709 Woodburn Ave.
00000000000000000000000000000000000
00000000000000000000000000000000000
33332566667762476222222222222222222
270907FF4252E0165E00000000000000000
%_SPACE
0
0
2
0
ITAB_RESULT_BW+6154(4)
0202
0000
ITAB_RESULT+4908(4)
0202
0000
LW_LINES
164
000A
0004
ITAB_RESULT_BW-TELF1
961-1122
0000000000000000
0000000000000000
3332333322222222
961D112200000000
ITAB_RESULT-TELF1
961-1122
0000000000000000
0000000000000000
3332333322222222
961D112200000000
ITAB_RESULT_BW-LAND1
US
000
000
552
530
ITAB_RESULT-LAND1
US
000
000
552
530
COUNTROCHGNEGCONOVER1K2
0
0000
0000
ITAB_RESULT_BW+6158(337)
#0#3#6#0#-#0#0# # # # # # # # # # # # # #M#R#O# #&# #C#o#n#s#t#r#u#c#t#i#o#n#A#t#h#l#e#t#i#c
0203030303020303020202020202020202020202020405040202020406060707070706070606060407060606070606
00000306000D0000000000000000000000000000000D020F000600030F0E030402050304090F0E0104080C05040903
ITAB_RESULT+4950(337)
#0#3#6#0#-#0#0# # # # # # # # # # # # # #M#R#O# #&# #C#o#n#s#t#r#u#c#t#i#o#n#A#t#h#l#e#t#i#c
0203030303020303020202020202020202020202020405040202020406060707070706070606060407060606070606
00000306000D0000000000000000000000000000000D020F000600030F0E030402050304090F0E0104080C05040903
ITAB_CHGLOG[]
Table IT_33[587x1576]
\PROGRAM=ZPMM_BWLOAD_R_V2\DATA=ITAB_CHGLOG[]
Table reference: 25
TABH+ 0(20) = 070000009070DB38000000000000000000000000
TABH+ 20(20) = 00000019000000210000024B00000628FFFFFFFF
TABH+ 40(16) = 040000000000149000082C9401800000
store = 0x070000009070DB38
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 25 (0x00000019)
label = 33 (0x00000021)
fill = 587 (0x0000024B)
leng = 1576 (0x00000628)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000095
occu = 8 (0x00000008)
access = 1 (ItAccessStandard)
idxKind = 1 (ItIndexLinear)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x07000000A0E13E70
pgHook = 0x07000000B2EBC728
idxPtr = 0x07000000906BA5E0
shmTabhSet = 0x0000000000000000
id = 32 (0x00000020)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 1024 (0x00000400)
lineAlloc = 592 (0x00000250)
shmVersId = 0 (0x00000000)
shmRefCount = 469 (0x000001D5)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
ITAB_RESULT_BW+3592(1026)
0202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ITAB_RESULT+5798(1026)
0202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ITAB_RESULT_BW-MANDANT
400
000
000
333
400
ITAB_RESULT-MANDANT
400
000
000
333
400
AMTTCCHGPOSREGST2
00000000000
0000000000C
ITAB_RESULT_BW[]
Table IT_132[1x6760]
\PROGRAM=ZPMM_BWLOAD_R_V2\DATA=ITAB_RESULT_BW[]
Table reference: 51
TABH+ 0(20) = 07000000A9A1FEA8000000000000000000000000
TABH+ 20(20) = 00000033000000840000000100001A68FFFFFFFF
TABH+ 40(16) = 0400000000003140000224C401800000
store = 0x07000000A9A1FEA8
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 51 (0x00000033)
label = 132 (0x00000084)
fill = 1 (0x00000001)
leng = 6760 (0x00001A68)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000248
occu = 2 (0x00000002)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x07000000A283E980
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 141 (0x0000008D)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 2 (0x00000002)
lineAlloc = 2 (0x00000002)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x00000001)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
ITAB_RESULT_BW
400##͒4500034945
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000030000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3330053333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
4000024500034945000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
COUNTTCCHGNEGCONST3
0
0000
0000
<%_TABLE_ZTMM_PU_FOR_BW>
AMTTOTAL3
00000000000
0000000000C
No. 1 Ty. EVENT
Name START-OF-SELECTION
T023T
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T024
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T161
00000 00000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222223333322222222222222222222222222222222222333332222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
TWLAD
000000000000000000000000
000000000000000000000000
222222222222222222222222
000000000000000000000000
ZTMM_BOA
0000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222223333333333333333222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ZTMM_PU_FOR_BW
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2220002222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ZTPU_DOCTYPE
0000000000000000000000000000000000
0000000000000000000000000000000000
2222222222222222222222222222222222
0000000000000000000000000000000000
USR02
####0000000000000000 # 000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222220000333333333333333322222222222220222222222222222222222222333333333333333333333
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SSCRFIELDS
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_BLUESQUAREX
@3X@
000000
000000
435422
038000
Internal notes
The termination was triggered in function "HandleRsqlErrors"
of the SAP kernel, in line 786 of the module
"//bas/700_REL/src/krn/runt/absapsql.c#11".
The internal operation just processed is "SQLS".
Internal mode was started at 20081231190002.
Internal call code.........: "[RSQL/INSR/ZTMM_PU_FOR_BW ]"
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 = unlimited
=> Stack limit = 4294967296
=> Core limit = 1073741312
=> File size limit = unlimited
=> Heap address = 0x0x11c0f5d60
=> Stack address = 0xfffffffffff8040
=> Stack low = 0xfffffffffff8040
=> Stack high = 0xffffffffffff800
=> Stack Trace:
AixStack() at 0x1000c945c
CTrcStack2() at 0x1000c9554
rabax_CStackSave__Fv() at 0x1000b3ee0
ab_rabax() at 0x1000b0628
ab_rsqlerr__FPCUsiT1P11RS_HEADER94T1Pv() at 0x10058c010
HandleRsqlErrors__F9RsqlError9CloseMode() at 0x1017f1e94
SqlsExecuteCall__FUcP11DynCallInfo() at 0x1017efc68
ab_jsqls__Fv() at 0x1017ea82c
ab_extri__Fv() at 0x100419ca0
ab_xevent__FPCUs() at 0x10094e47c
ab_trigg__Fv() at 0x10094e168
ab_run() at 0x1011aabb8
N_ab_run() at 0x100f6edc0
dynpmcal() at 0x100f6d9c4
dynppai0() at 0x100f6b2c8
dynprctl() at 0x100f7375c
dynpen00() at 0x100f6761c
Thdynpen00() at 0x1000e3c6c
TskhLoop() at 0x1000e5b64
ThStart() at 0x1001000c0
DpMain() at 0x101301d34
nlsui_main() at 0x101abea68
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
ZPMM_BWLOAD_R_V2
0
12/31/2008
10:10:08
409600
E
1
Prg
SAPMSSY0
1
05/30/2008
12:59:05
92160
E
2
Prg
SAPMSSYD
1
08/16/2006
12:06:37
21504
E
3
Prg
SAPFSYSCALLS
1
09/09/2004
14:18:32
7168
E
4
Prg
RSDBRUNT
0
12/13/2008
02:15:03
254976
E
5
Prg
SAPLSPRI
5
12/13/2008
02:14:06
342016
E
6
Typ
PRI_PARAMS
0
11/02/1998
09:46:12
5120
7
Typ
ARC_PARAMS
0
08/28/1997
08:36:28
6144
8
Typ
PRI_LAYOUT
0
11/06/2003
20:30:04
2048
9
Typ
PRIPAR_EXT
0
05/18/2004
14:07:03
3072
10
Typ
PRIPAR_EX2
0
11/09/2000
14:10:39
2048
11
Typ
PRIPAR_EX3
0
05/18/2004
14:07:03
5120
12
Typ
TPRI_DEF
0
11/09/2000
14:24:28
5120
13
Typ
USR01
0
05/30/2008
19:06:47
4096
14
Typ
TSP1D
0
11/15/2000
17:58:02
5120
15
Prg
SAPLSPOO
15
12/13/2008
02:14:06
160768
E
16
Prg
SAPLRSPOLSTDRV
16
12/13/2008
02:13:54
58368
E
17
Typ
TSPOPTIONS
0
01/29/1997
19:13:56
2048
18
Typ
TSP03
0
11/02/1998
09:57:05
5120
19
Typ
TSP0A
0
11/15/2000
17:58:02
6144
20
Typ
TSP03C
0
11/21/2003
11:41:10
7168
21
Typ
TSP03T
0
03/23/1998
18:21:38
6144
22
Typ
TSP06A
0
11/15/2000
17:58:02
7168
23
Prg
SAPCNVE
23
09/09/2004
14:36:10
8192
E
24
Prg
SAPLSPOC
24
12/13/2008
02:15:07
137216
E
25
Typ
TSP03L
0
07/10/1997
00:46:18
2048
26
Typ
RSPOCHECK
0
08/13/1997
12:53:10
4096
27
Typ
TSP03A
0
07/10/1997
00:46:15
3072
28
Prg
SAPLSPOR
28
12/13/2008
02:15:07
39936
E
29
Prg
SAPLSPOB
29
05/30/2008
09:36:14
67584
E
30
Prg
SAPLSDEX
30
09/09/2004
14:20:42
22528
E
31
Typ
DD07T
0
05/30/2008
00:38:18
3072
32
Typ
DEVPAR
0
12/04/2000
12:46:11
3072
33
Typ
RSPOATTR
0
11/10/1999
17:44:19
2048
34
Typ
RSSCR
0
03/30/2005
10:21:45
5120
35
Prg
RSDBSPBL
0
03/30/2005
10:21:58
72704
E
36
Prg
SAPDB__S
0
03/30/2005
10:22:01
19456
E
37
Typ
VARID
0
05/12/1997
16:51:30
4096
38
Typ
SSCRFIELDS
0
05/13/1997
12:54:26
5120
39
Prg
%_CSYDB0
0
03/30/2005
10:21:45
35840
E
40
Prg
RSDBSPVA
0
12/13/2008
02:15:03
133120
E
41
Typ
RSVAMEMKEY
0
05/07/1997
13:07:49
5120
42
Prg
RSDBSPMC
0
08/16/2006
11:55:58
79872
E
43
Typ
DDSHDESCR
0
09/03/1997
03:05:16
4096
44
Typ
SPPARAMS
0
05/07/1997
13:10:38
2048
45
Prg
SAPLICON
45
05/30/2008
13:22:44
27648
E
46
Prg
%_CICON
45
05/30/2008
13:22:44
107520
E
47
Typ
ICONT
0
08/16/2006
11:55:57
2048
48
Prg
SAPLSABE
48
09/09/2004
14:18:36
12288
E
49
Prg
SAPLSECU
49
05/30/2008
11:07:13
87040
E
50
Typ
RSSUBINFO
0
10/14/1999
22:01:03
2048
51
Typ
RSEXFCODE
0
08/13/1997
12:52:57
2048
52
Prg
SAPLDSYA
52
05/30/2008
12:53:05
45056
E
53
Prg
SAPFSDS1
52
03/30/2005
10:22:01
52224
E
54
Typ
TDCLD
0
11/02/1998
09:51:35
6144
55
Prg
SAPLSDOD
55
01/25/2006
10:59:45
45056
E
56
Typ
DOKIL
0
05/12/1997
16:46:17
3072
57
Prg
SAPLLANG
57
09/09/2004
14:18:35
10240
E
58
Typ
T002
0
05/30/2008
00:53:58
2048
59
Prg
SAPFSPOR
0 -
Timeout Short Dump on a Data Query to a blank table.
Hi,
My program gives a short dump on quering a blank table. The dump says timeout.
what could the possible problem be.
regards,Runtime Error TIME_OUT
Occurred on 02/19/2009 at 10:35:35
Time limit exceeded.
What happened?
The program "SAPLE31C" has exceeded the maximum permitted runtime without
interruption, and has therefore been terminated.
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
After a certain length of time, the program is terminated. In the case
of a work area, this means that
- endless loops (DO, WHILE, ...),
- database accesses producing an excessively large result set,
- database accesses without a suitable index (full table scan)
do not block the processing for too long.
The system profile "rdisp/max_wprun_time" contains the maximum runtime of a
program. The
current setting is 5400 seconds. Once this time limit has been exceeded,
the system tries to terminate any SQL statements that are currently
being executed and tells the ABAP processor to terminate the current
program. Then it waits for a maximum of 60 seconds. If the program is
still active, the work process is restarted.
successfully processed, the system gives it another 5400 seconds.
Hence the maximum runtime of a program is at least twice the value of
the system profile parameter "rdisp/max_wprun_time".
How to correct the error
You should usually execute long-running programs as batch jobs.
If this is not possible, increase the system profile parameter
"rdisp/max_wprun_time".
Depending on the cause of the error, you may have to take one of the
following measures:
- Endless loop: Correct program;
- Dataset resulting from database access is too large:
Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
(for example);
- Database has an unsuitable index: Check index generation.
You may able to find an interim solution to the problem
~~~~~~~
The line to which it points is a select query on a table that has not records. -
Dump in include LSKBHF06 of SAPLSKBH program while creating dynamic internal table.
Hello Guys,
We are facing a issue and expecting a support to resolve it.
Brief Info about the issue:
We have developed a code which downloads some specific information from database tables from client's system in excel file.
For that we have used below mentioned method to create the dynamic table.
cl_alv_table_create=>create_dynamic_table.
Now this code is successfully executing in our system and giving us the required output. But when client is running this code in their system they are getting a dump.
Dump Details:
Runtime Errors LOAD_PROGRAM_NOT_FOUND
Exception CX_SY_PROGRAM_NOT_FOUND
Occurred on 12.03.2014 at 11:01:51
Program " " not found.
What happened?
There are several possible reasons for the error:
or
The current ABAP program had to be terminated because the
ABAP processor detected an internal system error.
The current ABAP program "SAPLSKBH" had to be terminated because the ABAP
processor discovered an invalid system state.
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 is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_PROGRAM_NOT_FOUND', was
neither
caught nor passed along using a RAISING clause, in the procedure
"FB_TABLE_CREATE_STRING" "(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:
On account of a branch in the program
(CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
or a transaction call, another ABAP/4 program
is to be loaded, namely " ".
However, program " " does not exist in the library.
System environment
SAP Release.............. "620"
Application server....... "gs-sh110"
Network address.......... "10.2.95.17"
Operating system......... "Linux"
Release.................. "2.6.16.60-0.39.3-smp"
Hardware type............ "x86_64"
Character length......... 16 Bits
Pointer length........... 64 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "gs-sh110"
Database type............ "ORACLE"
Database name............ "H15"
Database owner........... "SAPORA"
As per the dump we have tried to find the root cause of the issue and found in debug mode that in 'SAPLSKBH' program in SE38 in include 'INCLUDE LSKBHF06' program name SAPLSKBH is converted in some random generated program by sap ex. '%_T008F0' which is passed in the perform 'TABLE_CREATE' of the program generated dynamically.
If this program name does not exists in the system then system will generate the dump
Program " " not found as show in the dump received.
Please find the short dump attached.
Please help to solve the issue.
Regards.
Abhinav Goel.Hi Abhinav,
I tried it myself in our system in debug mode. If SY_REPID is empty, l_name is set to %_T0000L (in our system) by GENERATE SUBROUTINE POOL and code line
perform (l_form) in program (l_name).
is a
perform TABLE_CREATE in program %_T0000L.
This works fine.
But in your dump field l_name is still empty. This shouldn't be after a successfully processed GENERATE SUBROUTINE POOL.
But SY-SUBRC seems to be 0 and l_message seems to be empty.
In Your client's system, please try to check it
- on a DEV system with open system settings (system client should allow changes)
- with an user, who has developer's authorities and a registered developer key in table DEVACCESS
Please tell us, if the issue remains after that.
Regards,
Klaus -
Internal Order status issue Error - Message Class X short dump
Hi All Experts,
I am creating internal order with CRTD status. However when I am trying to post transaction through MIRO , I am getting ABAP short dump mseeage class X. So I changed the CRTD to REL manually and able to solve the error.
But could any expert help me what is the logic behind this CRTD , REL, LKD etc ?
Since I am reading help.sap.com also as well but simple word help will be appreciable !
One more can we,
1 ) Create Internal Order with the REL status directly ?
2 ) If YES where configuration needs to be done
3 ) Will it hamper any business process ?
Exprts guidance will be appreciable.
Regards,
Sharvari Joshi.Hi,
All Masters,
Eli - Thank you for your answers.
Lawrence - Thank you for simple word that is what I was looking for.
Can anybody tell me how can we create IO directly in LKD status ? Or it is manual acitivity by clicking on Set / Rest button and then check LKD and save. I tried in KOT2_OPA but not no any option found. If any experts can guide for the following configuration would be great.
1 ) Is it possible to create IO with LKD status directly ?
2 ) Where that configuration needs to be done ?
3 ) What is significance of JEST Table relating to Internal Order ?
Exprerts help would be great !
Regards,
Sharvari Joshi.
Edited by: Sharvari Joshi on Dec 3, 2010 11:52 AM -
Short Dump in table maintenance events
Dear Experts,
I am getting a short dump when i am trying to maintain my Z table. the error is "The statement "MOVE src TO dst" requires that the operands "dst" and "src" are convertible. Since this statement is in a Unicode program, the special conversion rules for Unicode programs apply. In this case, these rules were violated.
the actual short dump is appearing at Move total to fs_zsdslsbud.
ZSDSLSBUD table has a NUMC, 4 char field but in total internal table it is appearing as 0000####. I guess this is the error. I tried to replicate the same code where there are only char type fields and i dont have any issues with below code.
My Z table also have a currency field. How to handle the unicode conversion in this case? can i use Try and Catch statements. A piece of code would be appriciated.
Thanks in advance.
FORM f_trigger_before_save.
DATA: wf_index TYPE sy-tabix. "Index to note the lines found
DATA: BEGIN OF fs_zsdslsbud.
INCLUDE STRUCTURE zsdslsbud.
INCLUDE STRUCTURE vimtbflags.
DATA: END OF fs_zsdslsbud.
LOOP AT total.
IF <action> = neuer_eintrag .
READ TABLE extract WITH KEY <vim_xtotal_key>.
IF sy-subrc EQ 0.
wf_index = sy-tabix.
ELSE.
CLEAR wf_index.
ENDIF.
* (make desired changes to the line total)
MOVE total TO fs_zsdslsbud.
fs_zsdslsbud-ernam = sy-uname.
fs_zsdslsbud-erdat = sy-datum.
fs_zsdslsbud-erzet = sy-uzeit.
total = fs_zsdslsbud.
MODIFY total.
CHECK wf_index GT 0.
extract = total.
MODIFY extract INDEX wf_index.
ELSEIF <action> = aendern.
READ TABLE extract WITH KEY <vim_xtotal_key>.
IF sy-subrc EQ 0.
wf_index = sy-tabix.
ELSE.
CLEAR wf_index.
ENDIF.
* (make desired changes to the line total)
MOVE total TO fs_zsdslsbud.
fs_zsdslsbud-aenam = sy-uname.
fs_zsdslsbud-aedat = sy-datum.
fs_zsdslsbud-aezet = sy-uzeit.
total = fs_zsdslsbud.
MODIFY total.
CHECK wf_index GT 0.
extract = total.
MODIFY extract INDEX wf_index.
ENDIF.
ENDLOOP.
sy-subrc = 0.
ENDFORM. "f_trigger_before_save
Thanks,
Rajesh.Hi,
Use this FM instead of Move statement.. In Unicode environments the left and right operands should be of same data type. to over come this you can use the below FM
CALL FUNCTION 'HR_99S_COPY_STRUC1_STRUC2'
EXPORTING
P_STRUCT1 = total
IMPORTING
P_STRUCT2 = fs_zsdslsbud.
Maybe you are looking for
-
How to delete from Nokia C5-03?
How to do delete music and other unnessary things from Nokia C5-03? I have not found delete or remove area. Help me.
-
*** Can't connect a d-link DL-524 router...
I've been using my iBook and my airport express base station to connect to the 'net no problem, but I would like to incorporate a DL-524 as my router because I'd like to move my airport express near my stereo to have it there to receive streamed musi
-
Downloaded MUSE trial then got Cloud subscription. MUSE still thinks it is a trial
SITUATION: 1. I downloaded MUSE as a trial last night and started using it. 2. Today I bought a Creative Cloud subscription and downloaded MUSE so I wouldn't be using it as a trial anymore. 3. MUSE still thinks it is on a 30 day trial. I can't find a
-
i have a iphone that my daughter gave me and its locked how do i unlock it with no minutes on it
-
I can see a picture in iPhoto thumbnail view, but when I click on the picture for a closer view or editing I get a dash outline of a picture with and ! in the middle. I know the picture still exists in my iPhoto b/c I can find it in Finder. Also I be