Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Print Error Log Text in Report

former_member541575
Participant
0 Likes
613

Hi

I am facing a issue.

i have displayed the error requests. i want to add one more functinality in that. once i will click on a error request then the detailed log of that error request should be shown.

but once i click on a error request a ABAP dump come with message.Short text

No more storage space available for extending an internal table.

below is the code.

AT LINE-SELECTION.

WRITE: g_s_dtp-dtp HOTSPOT.

CALL METHOD cl_rsbm_error_handler=>get_log

EXPORTING

i_requid = itab1-e_requid

i_datapakid = itab1-e_datapakid

i_segid = itab1-e_segid

i_step = itab1-e_step

i_record = itab1-e_record

IMPORTING

e_t_messages = l_t_messages

e_t_detail = l_t_detail

EXCEPTIONS

log_not_found = 1

OTHERS = 2.

IF sy-subrc <> 0.

MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno

WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4

RAISING log_not_found.

ELSE.

  • ---- Display ----

CALL METHOD cl_rssm_show_log=>show_messages_write_log

EXPORTING

i_t_messages = l_t_messages

i_t_details = l_t_detail.

ENDIF.

1 ACCEPTED SOLUTION
Read only

JerryWang
Product and Topic Expert
Product and Topic Expert
0 Likes
585

Hello Mishra,

first you have to check whether this issue happens occasionally or not. Sometimes if the program needs a lot of memory and current available memory is low, then this runtime exception occurs. If this issue happens always, then you need to consider to make less data displayed. Thus it will cause less memory accordingly.

CALL METHOD cl_rssm_show_log=>show_messages_write_log
EXPORTING
i_t_messages = l_t_messages
i_t_details = l_t_detail.
ENDIF.

Best Regards,

Jerry

2 REPLIES 2
Read only

Former Member
0 Likes
585

Usually, this error is encountered, when we try to accomodate too many entries to the internal table. A specific amount of memory is allocated by the Basis for each process. If the memory is exhausted by all the memory allocations in a particular session, this error occurs.

Check the dump in ST22 to see the exact internal table or part of the code responsible for this & size of the internal table at the time of short dump.

Read only

JerryWang
Product and Topic Expert
Product and Topic Expert
0 Likes
586

Hello Mishra,

first you have to check whether this issue happens occasionally or not. Sometimes if the program needs a lot of memory and current available memory is low, then this runtime exception occurs. If this issue happens always, then you need to consider to make less data displayed. Thus it will cause less memory accordingly.

CALL METHOD cl_rssm_show_log=>show_messages_write_log
EXPORTING
i_t_messages = l_t_messages
i_t_details = l_t_detail.
ENDIF.

Best Regards,

Jerry