Dump error when clicked on text elements in SAP Script window

[rekha_manjunath2]

Hi All,

There is an inclusion in SAP Script. I have written the code in driver program. I need to pass the value to SAP Script in the requested position. But when I go to SE71 > Form Name > Change or Display > MAIN Window > Text Elements > I get a dump error.

Category               ABAP Programming Error
Runtime Errors         DATA_LENGTH_TOO_LARGE
Except.                CX_SY_RANGE_OUT_OF_BOUNDS
ABAP Program           SAPLSTXK
Application Component  BC-SRV-SCR
Date and Time          30.04.2014 20:00:08

Short text
     Invalid partial field access: Length is too large

What happened?
     Error in the ABAP Application Program

     The current ABAP program "SAPLSTXK" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.

What can you do?
     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.

Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_RANGE_OUT_OF_BOUNDS', was not
      caught in
     procedure "TOKEN_COMMENT" "(FORM)", nor was it propagated by a RAISING clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.

    The reason for the exception is:
    In the executed program "SAPLSTXK", the system attempted to access the field
    "ITF_TOKEN" of the type "C" and with the length 255 using the length 272.
    However, a partial field access with a length specification that is
    larger than the field length is not allowed.

How to correct the error
    Reduce the length used to access the field.

    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:

    "DATA_LENGTH_TOO_LARGE" "CX_SY_RANGE_OUT_OF_BOUNDS"
    "SAPLSTXK" or "LSTXKFRN"
    "TOKEN_COMMENT"

    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

2937 * todo empty comment ???

2938       if g_tm_open    eq true or     " Section

2939          g_tm_b_close eq true.

2940         l_token = '\chcbpat0'.

2941         l_len = strlen( l_token ).

2942         token_control = true.

2943         assign l_token to <itf1>.

2944         perform put_itf1_new using l_len.

2945         perform token_line_begin changing l_next_token.

2946       else.                          " without section

2947         concatenate '\chcbpat0\line' g_cf_string l_cbpat_token into l_token.

2948         l_len = strlen( l_token ).

2949         token_control = true.

2950         assign l_token to <itf1>.

2951         perform put_itf1_new using l_len.

2952       endif.

2953     elseif l_next_token-code eq ')L'.         " \par

2954       l_token = '\par'.

2955       l_len = strlen( l_token ).

2956       token_control = true.

2957       assign l_token to <itf1>.

2958       perform put_itf1_new using l_len.

2959     elseif l_next_token-code eq '(C' or       " \par + format

2960            l_next_token-code eq ')C' or

2961            l_next_token-code eq '(&' or

2962            l_next_token-code eq 'TA' or

2963            l_next_token-code eq 'SC' or

2964            l_next_token-code eq 'ST'.

2965       concatenate '\chcbpat0\par' g_pf_string g_cf_string l_cbpat_token into l_token.

2966       l_len = strlen( l_token ).

>>>>>       itf_token(l_len) = l_token.

2968       token_control = true.

2969       assign l_token to <itf1>.

2970       perform put_itf1_new using l_len.

2971     endif.

2972

2973 * Step 7: (L to disarm

2974   if g_compose eq true and

2975      l_next_token-code eq '(L'.

2976     perform read_next_itf_token(rstxscan) using p_token.

2977   endif.

2978

2979 ENDFORM.                    " token_comment

2980 *&---------------------------------------------------------------------*

2981 *&      Form  create_lang_info

2982 *&---------------------------------------------------------------------*

2983 *       add default language to rtf

2984 *----------------------------------------------------------------------*

2985 *      -->P_HEADER  text

2986 *      <--P_RESULT  text

How do I open the text elements? I need to pass the variable inside SAP Script.

Please Help. The requirement is pending from very long. Not able to rectify this issue.

Regards,

Rekha

[Former Member]

Hi,

There is a SAP Note about this problem

566794 - Runtime error: STRING_OFFSET_TOO_LARGE during conversion

Correction Instructions

Correction Instructions
Software Component Valid from Valid to Number SAP_BASIS 46B 46D 473267 SAP_BASIS 610 620 473185

Support Packages & Patches

Support Packages
Software Component Release Support Package SAP_BASIS 46B SAPKB46B48 46C SAPKB46C39 46D SAPKB46D28 610 SAPKB61027 620 SAPKB62014

Regards

Miguel

[rekha_manjunath2]

Hi Miguel,

The release for SAP_BASIS in our SAP is 731. So it is a higher version than the one specified in the note. Kindly let me know what can be done?

Regards,

Rekha

[Private_Member_7726]

Hi,

The only action I can think of besides reporting this to OSS would be trying to bypass dump via debugger, by manually restricting l_len to 255 (maximum length of itf_token). It may get tricky and/or tedious getting to the state just prior to error via debugger, but try setting breakpoint on itf_token(l_len) = l_token... The offending token seems to be a comment line, so no form logic should get destroyed if it will be truncated.

chers

Janis

[rekha_manjunath2]

Hi Jānis,

Trying the same option. Still no luck..

Regards,

Rekha

[rekha_manjunath2]

Hi Jānis,

Thank you very much. This option did work!!!! I changed the offset length in debugging mode.

I am able to enter the text elements and pass the value.!!

Regards,

Rekha

[Private_Member_7726]

Debugger FTW!