<?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: recursive structure: compiler error in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/recursive-structure-compiler-error/m-p/638414#M27097</link>
    <description>&lt;P&gt;Sorry, bad phrasing. I meant dynamic processing or referencing. You will need some kind of looping or nested access methods. &lt;/P&gt;
  &lt;P&gt;I don't see OO as being significant overhead. Clarity / ease of use is a good tradeoff for a really minor performance hit. To me this screams out for OO &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 18 Apr 2018 07:38:24 GMT</pubDate>
    <dc:creator>pokrakam</dc:creator>
    <dc:date>2018-04-18T07:38:24Z</dc:date>
    <item>
      <title>recursive structure: compiler error</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/recursive-structure-compiler-error/m-p/638410#M27093</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;I'd like to define a recursive structure like&lt;/P&gt;
  &lt;PRE&gt;&lt;CODE&gt;TYPES:
  BEGIN OF st_assembly_element,
    matnr TYPE                   matnr,
    brkup TYPE                   c,
    state TYPE                   icon_d,
    " ...
    pords TYPE STANDARD TABLE OF ebeln               WITH DEFAULT KEY,
    elems TYPE STANDARD TABLE OF st_assembly_element WITH DEFAULT KEY,
  END OF st_assembly_element
.
&lt;/CODE&gt;&lt;/PRE&gt;
  &lt;P&gt;Compiling this code leads to an "unknown type: st_assembly_element"-error.&lt;/P&gt;
  &lt;P&gt;Is there a way of forward declaration in ABAP (syntax required)?&lt;/P&gt;
  &lt;P&gt;How can I avoid this error (without using TYPE REF TO data)?&lt;/P&gt;
  &lt;P&gt;Regards,&lt;/P&gt;
  &lt;P&gt;Hubert&lt;/P&gt;</description>
      <pubDate>Tue, 17 Apr 2018 12:34:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/recursive-structure-compiler-error/m-p/638410#M27093</guid>
      <dc:creator>hubert_heitzer</dc:creator>
      <dc:date>2018-04-17T12:34:35Z</dc:date>
    </item>
    <item>
      <title>Re: recursive structure: compiler error</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/recursive-structure-compiler-error/m-p/638411#M27094</link>
      <description>&lt;P&gt;Even if the compiler allowed it, I would not do it. &lt;/P&gt;
  &lt;P&gt;You couldn't read it properly without some kind of dynamic referencing. And if we're going to do that then a hierarchical list is much easier to code, understand, and debug. If you want recursion, use objects; much neater.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Apr 2018 14:52:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/recursive-structure-compiler-error/m-p/638411#M27094</guid>
      <dc:creator>pokrakam</dc:creator>
      <dc:date>2018-04-17T14:52:27Z</dc:date>
    </item>
    <item>
      <title>Re: recursive structure: compiler error</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/recursive-structure-compiler-error/m-p/638412#M27095</link>
      <description>&lt;P&gt;The "elems" should be just STANDARD TABLE of matnr in my opinion because this i the key for the next layer.&lt;/P&gt;
  &lt;P&gt;(standard in Bill of Materials [BOM])&lt;/P&gt;</description>
      <pubDate>Tue, 17 Apr 2018 15:05:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/recursive-structure-compiler-error/m-p/638412#M27095</guid>
      <dc:creator>UweFetzer_se38</dc:creator>
      <dc:date>2018-04-17T15:05:00Z</dc:date>
    </item>
    <item>
      <title>Re: recursive structure: compiler error</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/recursive-structure-compiler-error/m-p/638413#M27096</link>
      <description>&lt;P&gt;Of course can I read it properly without some kind of dynamic referencing.&lt;/P&gt;
  &lt;P&gt;I need this data structure only in this special case, so I try to avoid the overhead of OO.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Apr 2018 07:29:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/recursive-structure-compiler-error/m-p/638413#M27096</guid>
      <dc:creator>hubert_heitzer</dc:creator>
      <dc:date>2018-04-18T07:29:33Z</dc:date>
    </item>
    <item>
      <title>Re: recursive structure: compiler error</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/recursive-structure-compiler-error/m-p/638414#M27097</link>
      <description>&lt;P&gt;Sorry, bad phrasing. I meant dynamic processing or referencing. You will need some kind of looping or nested access methods. &lt;/P&gt;
  &lt;P&gt;I don't see OO as being significant overhead. Clarity / ease of use is a good tradeoff for a really minor performance hit. To me this screams out for OO &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Apr 2018 07:38:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/recursive-structure-compiler-error/m-p/638414#M27097</guid>
      <dc:creator>pokrakam</dc:creator>
      <dc:date>2018-04-18T07:38:24Z</dc:date>
    </item>
  </channel>
</rss>

