<?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: Difference in structure declaration in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-in-structure-declaration/m-p/6511568#M1423575</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1) Typing using &lt;EM&gt;data element&lt;/EM&gt; . This means that the field "inherits" all semantics and functionality this data element provides i.e field label (short, medium, long text) - they are used i.e. in ALV, input/search help which was attached to that data element, once you change its definition all fields in all the reports which refer to it will get change too&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) Typing using &lt;EM&gt;table field&lt;/EM&gt; . This means that field "inherits" all semantics of data element which used for that field (namely the above metioned) + can provide check if field is set in table as so called &lt;EM&gt;check field&lt;/EM&gt; (input is available based on &lt;EM&gt;check table&lt;/EM&gt; entires).&lt;/P&gt;&lt;P&gt;This is just one level higher that the first one. All i all table field also uses data element to describe its sematics.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So there is no really significant difference b/w those two. Only input help may act differently.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Marcin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Jan 2010 10:31:41 GMT</pubDate>
    <dc:creator>MarcinPciak</dc:creator>
    <dc:date>2010-01-19T10:31:41Z</dc:date>
    <item>
      <title>Difference in structure declaration</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-in-structure-declaration/m-p/6511565#M1423572</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;Can anyone tell me the difference between the declaration of structure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Referring to the domain level.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ex :Types : Begin of St,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    matnr type matnr,&lt;/P&gt;&lt;P&gt;    posnr type posnr,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    Types: end of st.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Referring to the table field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ex. Types: Begin of St,&lt;/P&gt;&lt;P&gt;     &lt;/P&gt;&lt;P&gt;    matnr type Mara - matnr,&lt;/P&gt;&lt;P&gt;    posnr type Vbeln - posnr,&lt;/P&gt;&lt;P&gt;   &lt;/P&gt;&lt;P&gt;   Types: end of St.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please let me know about the difference between the above mentioned delcarations.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jan 2010 09:19:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-in-structure-declaration/m-p/6511565#M1423572</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-01-19T09:19:19Z</dc:date>
    </item>
    <item>
      <title>Re: Difference in structure declaration</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-in-structure-declaration/m-p/6511566#M1423573</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;While declaring the structure:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;using table fields - You get the field labels &amp;amp; search help for that partcular field&lt;/P&gt;&lt;P&gt;using domains - You do not get field labels&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jan 2010 10:23:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-in-structure-declaration/m-p/6511566#M1423573</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-01-19T10:23:26Z</dc:date>
    </item>
    <item>
      <title>Re: Difference in structure declaration</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-in-structure-declaration/m-p/6511567#M1423574</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MARA-MATNR refers to the table-field name. The data element assigned to MARA-MATNR is assigned to the variable declared in the structure. If MARA-MATNR is of type MATNR1 for example, then the structure field will have data type MATNR1. It is similar to creating a structure field name of type MATNR1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Janani&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jan 2010 10:27:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-in-structure-declaration/m-p/6511567#M1423574</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-01-19T10:27:31Z</dc:date>
    </item>
    <item>
      <title>Re: Difference in structure declaration</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-in-structure-declaration/m-p/6511568#M1423575</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1) Typing using &lt;EM&gt;data element&lt;/EM&gt; . This means that the field "inherits" all semantics and functionality this data element provides i.e field label (short, medium, long text) - they are used i.e. in ALV, input/search help which was attached to that data element, once you change its definition all fields in all the reports which refer to it will get change too&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) Typing using &lt;EM&gt;table field&lt;/EM&gt; . This means that field "inherits" all semantics of data element which used for that field (namely the above metioned) + can provide check if field is set in table as so called &lt;EM&gt;check field&lt;/EM&gt; (input is available based on &lt;EM&gt;check table&lt;/EM&gt; entires).&lt;/P&gt;&lt;P&gt;This is just one level higher that the first one. All i all table field also uses data element to describe its sematics.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So there is no really significant difference b/w those two. Only input help may act differently.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Marcin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jan 2010 10:31:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-in-structure-declaration/m-p/6511568#M1423575</guid>
      <dc:creator>MarcinPciak</dc:creator>
      <dc:date>2010-01-19T10:31:41Z</dc:date>
    </item>
  </channel>
</rss>

