<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Runtime Errors dump  DATA_OFFSET_LENGTH_TOO_LARGE in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-dump-data-offset-length-too-large/m-p/7915927#M1598182</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I did not understand ur purpose with the below code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT matnr&lt;/P&gt;&lt;P&gt;menge&lt;/P&gt;&lt;P&gt;mblnr&lt;/P&gt;&lt;P&gt;ebeln&lt;/P&gt;&lt;P&gt;meins&lt;/P&gt;&lt;P&gt;werks FROM mseg INTO CORRESPONDING FIELDS OF TABLE t_mseg&lt;/P&gt;&lt;P&gt;WHERE mblnr IN mblnr.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;call function 'F4IF_INT_TABLE_VALUE_REQUEST'&lt;/P&gt;&lt;P&gt;exporting&lt;/P&gt;&lt;P&gt;retfield = 'MBLNR'&lt;/P&gt;&lt;P&gt;dynprofield = 'MBLNR'&lt;/P&gt;&lt;P&gt;dynpprog = sy-cprog&lt;/P&gt;&lt;P&gt;dynpnr = sy-dynnr&lt;/P&gt;&lt;P&gt;value_org = 'S'&lt;/P&gt;&lt;P&gt;tables&lt;/P&gt;&lt;P&gt;value_tab = T_MSEG.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL FUNCTION lv_form "'/1BCDWB/SF00000190'&lt;/P&gt;&lt;P&gt;EXPORTING&lt;/P&gt;&lt;P&gt;USER_SETTINGS = 'X'&lt;/P&gt;&lt;P&gt;TABLES&lt;/P&gt;&lt;P&gt;t_mseg = t_mseg&lt;/P&gt;&lt;P&gt;IF sy-subrc 0.&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you explain your requirement I am more thankful to you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: subas  Bose on May 27, 2011 12:39 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 27 May 2011 10:36:58 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2011-05-27T10:36:58Z</dc:date>
    <item>
      <title>Runtime Errors dump  DATA_OFFSET_LENGTH_TOO_LARGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-dump-data-offset-length-too-large/m-p/7915924#M1598179</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm working a executable program for SF and i want apply seach help on field mseg-mblnr .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so i am using CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i got an error when executing a programe.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Runtime Errors         DATA_OFFSET_LENGTH_TOO_LARGE&lt;/P&gt;&lt;P&gt;Exception              CX_SY_RANGE_OUT_OF_BOUNDS&lt;/P&gt;&lt;P&gt;Date and Time          27.05.2011 13:56:43&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What happened?&lt;/P&gt;&lt;P&gt;    Error in the ABAP Application Program&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    The current ABAP program "SAPLSDH4" had to be terminated because it has&lt;/P&gt;&lt;P&gt;    come across a statement that unfortunately cannot be executed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error analysis&lt;/P&gt;&lt;P&gt;    An exception occurred that is explained in detail below.&lt;/P&gt;&lt;P&gt;    The exception, which is assigned to class 'CX_SY_RANGE_OUT_OF_BOUNDS', was not&lt;/P&gt;&lt;P&gt;     caught in&lt;/P&gt;&lt;P&gt;    procedure "CONVERT_RESULT" "(FORM)", nor was it propagated by a RAISING clause.&lt;/P&gt;&lt;P&gt;    Since the caller of the procedure could not have anticipated that the&lt;/P&gt;&lt;P&gt;    exception would occur, the current program is terminated.&lt;/P&gt;&lt;P&gt;    The reason for the exception is:&lt;/P&gt;&lt;P&gt;    In the running program "SAPLSDH4", the field "&amp;lt;RECORD_OLD&amp;gt;", which is of the&lt;/P&gt;&lt;P&gt;     type "X" and&lt;/P&gt;&lt;P&gt;    length 2000, was to be accessed with the offset 1994 and the length 24.&lt;/P&gt;&lt;P&gt;    However, subfield accesses in which the sum of the offset and length&lt;/P&gt;&lt;P&gt;    specifications is greater than the field length are not allowed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;how to solved this problem?&lt;/P&gt;&lt;P&gt;guide me.............&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 May 2011 08:53:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-dump-data-offset-length-too-large/m-p/7915924#M1598179</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-05-27T08:53:03Z</dc:date>
    </item>
    <item>
      <title>Re: Runtime Errors dump  DATA_OFFSET_LENGTH_TOO_LARGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-dump-data-offset-length-too-large/m-p/7915925#M1598180</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please provide the code so that It will be easy for us to identify the issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 May 2011 10:16:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-dump-data-offset-length-too-large/m-p/7915925#M1598180</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-05-27T10:16:36Z</dc:date>
    </item>
    <item>
      <title>Re: Runtime Errors dump  DATA_OFFSET_LENGTH_TOO_LARGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-dump-data-offset-length-too-large/m-p/7915926#M1598181</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;  program Code.......&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECTION-SCREEN : BEGIN OF BLOCK b1 WITH FRAME TITLE text-001 .&lt;/P&gt;&lt;P&gt;*PARAMETERS : MBLNR LIKE mseg-mblnr.&lt;/P&gt;&lt;P&gt;SELECT-OPTIONS:  mblnr for mseg-mblnr.&lt;/P&gt;&lt;P&gt;SELECTION-SCREEN : END OF BLOCK b1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;at selection-screen on value-request for mblnr-LOW .&lt;/P&gt;&lt;P&gt;at selection-screen on value-request for mblnr-HIGH .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data: dynfields type table of dynpread with header line.&lt;/P&gt;&lt;P&gt;dynfields-fieldname = 'MBLNR'.&lt;/P&gt;&lt;P&gt;append dynfields.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; call function 'DYNP_VALUES_READ'&lt;/P&gt;&lt;P&gt;       exporting&lt;/P&gt;&lt;P&gt;            dyname               = sy-cprog&lt;/P&gt;&lt;P&gt;            dynumb               = sy-dynnr&lt;/P&gt;&lt;P&gt;            translate_to_upper   = 'X'&lt;/P&gt;&lt;P&gt;       tables&lt;/P&gt;&lt;P&gt;            dynpfields           = dynfields&lt;/P&gt;&lt;P&gt;       exceptions&lt;/P&gt;&lt;P&gt;            invalid_abapworkarea = 1&lt;/P&gt;&lt;P&gt;            invalid_dynprofield  = 2&lt;/P&gt;&lt;P&gt;            invalid_dynproname   = 3&lt;/P&gt;&lt;P&gt;            invalid_dynpronummer = 4&lt;/P&gt;&lt;P&gt;            invalid_request      = 5&lt;/P&gt;&lt;P&gt;            no_fielddescription  = 6&lt;/P&gt;&lt;P&gt;            invalid_parameter    = 7&lt;/P&gt;&lt;P&gt;            undefind_error       = 8&lt;/P&gt;&lt;P&gt;            double_conversion    = 9&lt;/P&gt;&lt;P&gt;            stepl_not_found      = 10&lt;/P&gt;&lt;P&gt;            others               = 11.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  read table dynfields with key fieldname = 'MBLNR'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  MBLNR = dynfields-fieldvalue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  call function 'CONVERSION_EXIT_ALPHA_INPUT'&lt;/P&gt;&lt;P&gt;       exporting&lt;/P&gt;&lt;P&gt;            input  = MBLNR&lt;/P&gt;&lt;P&gt;       importing&lt;/P&gt;&lt;P&gt;            output = MBLNR.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'&lt;/P&gt;&lt;P&gt;   EXPORTING&lt;/P&gt;&lt;P&gt;     formname                 = lv_name&lt;/P&gt;&lt;P&gt;  IMPORTING&lt;/P&gt;&lt;P&gt;    FM_NAME                  = lv_form&lt;/P&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; IF sy-subrc &amp;lt;&amp;gt; 0.&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt; ENDIF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT matnr&lt;/P&gt;&lt;P&gt;       menge&lt;/P&gt;&lt;P&gt;       mblnr&lt;/P&gt;&lt;P&gt;       ebeln&lt;/P&gt;&lt;P&gt;       meins&lt;/P&gt;&lt;P&gt;       werks FROM mseg INTO CORRESPONDING FIELDS OF TABLE t_mseg&lt;/P&gt;&lt;P&gt;WHERE mblnr IN mblnr.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  call function 'F4IF_INT_TABLE_VALUE_REQUEST'&lt;/P&gt;&lt;P&gt;       exporting&lt;/P&gt;&lt;P&gt;            retfield    = 'MBLNR'&lt;/P&gt;&lt;P&gt;            dynprofield = 'MBLNR'&lt;/P&gt;&lt;P&gt;            dynpprog    = sy-cprog&lt;/P&gt;&lt;P&gt;            dynpnr      = sy-dynnr&lt;/P&gt;&lt;P&gt;            value_org   = 'S'&lt;/P&gt;&lt;P&gt;       tables&lt;/P&gt;&lt;P&gt;            value_tab   = T_MSEG.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL FUNCTION  lv_form    "'/1BCDWB/SF00000190'&lt;/P&gt;&lt;P&gt; EXPORTING&lt;/P&gt;&lt;P&gt;   USER_SETTINGS              = 'X'&lt;/P&gt;&lt;P&gt;  TABLES&lt;/P&gt;&lt;P&gt;     t_mseg                    = t_mseg&lt;/P&gt;&lt;P&gt;IF sy-subrc &amp;lt;&amp;gt; 0.&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;guide me................................&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 May 2011 10:31:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-dump-data-offset-length-too-large/m-p/7915926#M1598181</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-05-27T10:31:36Z</dc:date>
    </item>
    <item>
      <title>Re: Runtime Errors dump  DATA_OFFSET_LENGTH_TOO_LARGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-dump-data-offset-length-too-large/m-p/7915927#M1598182</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I did not understand ur purpose with the below code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT matnr&lt;/P&gt;&lt;P&gt;menge&lt;/P&gt;&lt;P&gt;mblnr&lt;/P&gt;&lt;P&gt;ebeln&lt;/P&gt;&lt;P&gt;meins&lt;/P&gt;&lt;P&gt;werks FROM mseg INTO CORRESPONDING FIELDS OF TABLE t_mseg&lt;/P&gt;&lt;P&gt;WHERE mblnr IN mblnr.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;call function 'F4IF_INT_TABLE_VALUE_REQUEST'&lt;/P&gt;&lt;P&gt;exporting&lt;/P&gt;&lt;P&gt;retfield = 'MBLNR'&lt;/P&gt;&lt;P&gt;dynprofield = 'MBLNR'&lt;/P&gt;&lt;P&gt;dynpprog = sy-cprog&lt;/P&gt;&lt;P&gt;dynpnr = sy-dynnr&lt;/P&gt;&lt;P&gt;value_org = 'S'&lt;/P&gt;&lt;P&gt;tables&lt;/P&gt;&lt;P&gt;value_tab = T_MSEG.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL FUNCTION lv_form "'/1BCDWB/SF00000190'&lt;/P&gt;&lt;P&gt;EXPORTING&lt;/P&gt;&lt;P&gt;USER_SETTINGS = 'X'&lt;/P&gt;&lt;P&gt;TABLES&lt;/P&gt;&lt;P&gt;t_mseg = t_mseg&lt;/P&gt;&lt;P&gt;IF sy-subrc 0.&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you explain your requirement I am more thankful to you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: subas  Bose on May 27, 2011 12:39 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 May 2011 10:36:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-dump-data-offset-length-too-large/m-p/7915927#M1598182</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-05-27T10:36:58Z</dc:date>
    </item>
    <item>
      <title>Re: Runtime Errors dump  DATA_OFFSET_LENGTH_TOO_LARGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-dump-data-offset-length-too-large/m-p/7915928#M1598183</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am working on zprogram for smartform in which i am using select option for range of material Document ( MSEG-MBLNR ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when i can press F4 key in field of material doc. don't show search help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i did also check MSEG table in which MBLNR field  assign without seach help in MSEG table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i also know that when we create a program with select opton then Automatic create seach help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so, &lt;/P&gt;&lt;P&gt;i am using  FM : F4IF_INT_TABLE_VALUE_REQUEST. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;guide me........&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 May 2011 10:49:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-dump-data-offset-length-too-large/m-p/7915928#M1598183</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-05-27T10:49:50Z</dc:date>
    </item>
    <item>
      <title>Re: Runtime Errors dump  DATA_OFFSET_LENGTH_TOO_LARGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-dump-data-offset-length-too-large/m-p/7915929#M1598184</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;call function 'DYNP_VALUES_READ'
exporting
dyname = sy-cprog
dynumb = sy-dynnr
translate_to_upper = 'X'
tables
dynpfields = dynfields " You added a field MBLNR to dynfields 
exceptions

read table dynfields with key fieldname = 'MBLNR'.
" And you are trying to pass the value back here so you r passing the Value to a structure with fields sing option low and high
"as you said below which is giving the Error since the fisrt field SIGN accepts only I or E only
MBLNR = dynfields-fieldvalue.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The Issue is with in the following code as your MBLNR is of Select-option type which means&lt;/STRONG&gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;with SIGN OPTION LOW and HIGH where as after conversion or before conversion you are passing MBLNR_SIGN MBLNR-OPTIN etc to Function module which is resulting in dump

"Or Optionally you might need to loop this Select Options and modify the Low and HIgh Values explicitly 
" Or Just Dont proivide the option of Intervals and Extension 

"Explore other Options in this way , To the best of my knowledge this is causing you the DUMP
 
call function 'CONVERSION_EXIT_ALPHA_INPUT'
exporting  " Or take it as PARAMETER if you want a single Material Document number
input = MBLNR "Change it to MBLNR-LOW or HIG 
importing
output = MBLNR. "Change it to MBLNR-LOW or HIGH&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheerz&lt;/P&gt;&lt;P&gt;Ramchander Rao.K&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 May 2011 10:50:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-dump-data-offset-length-too-large/m-p/7915929#M1598184</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-05-27T10:50:25Z</dc:date>
    </item>
    <item>
      <title>Re: Runtime Errors dump  DATA_OFFSET_LENGTH_TOO_LARGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-dump-data-offset-length-too-large/m-p/7915930#M1598185</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;check the below link...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.erpgenie.com/sap-technical/abap/call-f4-help-from-selection-screen" target="test_blank"&gt;http://www.erpgenie.com/sap-technical/abap/call-f4-help-from-selection-screen&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it will help you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ram.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 May 2011 11:02:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-dump-data-offset-length-too-large/m-p/7915930#M1598185</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-05-27T11:02:14Z</dc:date>
    </item>
    <item>
      <title>Re: Runtime Errors dump  DATA_OFFSET_LENGTH_TOO_LARGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-dump-data-offset-length-too-large/m-p/7915931#M1598186</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey, this issue occurs when the structur of VALUE_TAB is too big or you have to many fields in there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try to reduce the fields in VALUE_TAB to the necessary ones and then it should work. I think the field length of all fields combined should not exceed 1000 characters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;Stefan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Sep 2015 11:03:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-dump-data-offset-length-too-large/m-p/7915931#M1598186</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-09-25T11:03:10Z</dc:date>
    </item>
  </channel>
</rss>

