‎2009 Jan 29 12:15 PM
hai,
i get following dump error when tryign to print a alv list report.
'Illegal interruption of the event LOAD-OF-PROGRAM.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSZA12" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
During the flow of the event LOAD-OF-PROGRAM (event for the
initialization of an ABAP program), a condition occurred under which
the event was to be left early. This is not permitted as it would
result in an inconsistent status in the ABAP program.'
the problem resolves for a particular output(when i restrict the list to lesser rows) by changing FORMAT from
X_65_255 to X_90_120 in the print dialog properties option..
however this restricts the coloumn width..
anycase i will have to print the output for all conditions.
the problem seems to be centred around number of rows in the list output..
‎2009 Jan 30 10:17 AM
Hey
I'm not sure about this but since we've had a similar problem with a report - albeit a classical one - could it be that you might have written LINE SIZE and LINE COUNT in the beginning of your report and these are not large enough ?
Pushpraj
‎2009 Jan 30 10:29 AM
no.
i ddint have any line size line count in the report statement.
‎2009 Jan 30 10:31 AM
Hi Gaurav ,
In alv the concept of line size and line count do not come in picture , they are relevant only in case of classical reports , please try changing the settings when you try to print the ALV:
Regards
Arun
‎2009 Jan 30 10:25 AM
Hi ,
As mentiond in the dump , please change the printer settings and use any one of the options
X_65_255 or X_90_120.
Please revert back in case you still have further queries.
Reagds
Arun
‎2009 Jan 30 10:35 AM
hi arun,
the dump says about printer settings???
any case,when i click on print,i get a dialog where in i can set properties.i have choosen all possible formats from that option.
by default it is X_65_255 (which gives me the dump error)..
as i mentioned choosing X_90_120 was ok for a particular output of report(with lesser rows than int he case when it failed)
does this hint any problems with printer settigns???
anything to do with patches notes etc..?
pls help..
Edited by: kumar gaurav on Jan 30, 2009 11:35 AM
‎2009 Jan 30 12:13 PM
hi arun,
heres the code for your reference.
this report is named 'vendor acc with opening balance' it is similar to fbl5n but it comes with the opening balance on the top of the items for the vendor accoutn.
ok to trigger the problem,one ahs to get a report with a huge lenght(over 3 page lenths) and try to print..
(also i am not great at formalities,mainting comments etc in programs)
‎2009 Jan 31 6:22 AM
can some one pls check and confirm if this problem is specific to our system.
‎2009 Feb 02 6:04 AM
is somethign wrong with the values in this internal table gt_comtypes_tab...
this is where the dump is pointing..at LAOD OF PROGRAM EVENT
1 FUNCTION addr_get_conversion_table.
2 *"----
3 ""Lokale Schnittstelle:
4 *" EXPORTING
5 *" VALUE(COMTYPES_TAB) TYPE ADCOMTYPES_TAB
6 *" EXCEPTIONS
7 *" INTERNAL_ERROR
8 *"----
9
10 comtypes_tab = gt_comtypes_tab.
11
12 ENDFUNCTION.
values of gt_comtypes_tab.
2 TEL ADTEL
3 FAX ADFAX
4 TTX ADTTX
5 TLX ADTLX
6 INT ADSMTP
7 RML ADRML
8 X40 ADX400
9 RFC ADRFC
10 PRT ADPRT
11 SSF ADSSF
12 URI ADURI
13 PAG ADPAG
‎2009 Feb 02 8:29 AM
ok when i comment this line the error changes...
GS_PRINT-reserve_lines = '3'.
now after commentig,the output times out
‎2009 Feb 02 9:39 AM