<?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: Valid types in DATA inline declarations in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/valid-types-in-data-inline-declarations/m-p/12659892#M2015587</link>
    <description>&lt;P&gt;It's what I do too...&lt;/P&gt;&lt;P&gt;Why would it be forbidden?&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jan 2023 12:46:23 GMT</pubDate>
    <dc:creator>Sandra_Rossi</dc:creator>
    <dc:date>2023-01-04T12:46:23Z</dc:date>
    <item>
      <title>Valid types in DATA inline declarations</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/valid-types-in-data-inline-declarations/m-p/12659891#M2015586</link>
      <description>&lt;P&gt;Sometimes names of data elements look rather cryptic. So i prefer inline declarations like&lt;/P&gt;
  &lt;PRE&gt;&lt;CODE&gt;DATA(lv_sap_object) = CONV toav0-sap_object( 'PRINTDOC' ).&lt;BR /&gt;&lt;/CODE&gt;&lt;/PRE&gt;
  &lt;P&gt;instead of&lt;/P&gt;
  &lt;PRE&gt;&lt;CODE&gt;DATA(lv_sap_object) = CONV saeanwdid( 'PRINTDOC' ).&lt;BR /&gt;&lt;/CODE&gt;&lt;/PRE&gt;
  &lt;P&gt;It works. But I never seen declarations like that in the official reference or demos. Is it allowed?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jan 2023 11:29:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/valid-types-in-data-inline-declarations/m-p/12659891#M2015586</guid>
      <dc:creator>touzik_itc</dc:creator>
      <dc:date>2023-01-04T11:29:27Z</dc:date>
    </item>
    <item>
      <title>Re: Valid types in DATA inline declarations</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/valid-types-in-data-inline-declarations/m-p/12659892#M2015587</link>
      <description>&lt;P&gt;It's what I do too...&lt;/P&gt;&lt;P&gt;Why would it be forbidden?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jan 2023 12:46:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/valid-types-in-data-inline-declarations/m-p/12659892#M2015587</guid>
      <dc:creator>Sandra_Rossi</dc:creator>
      <dc:date>2023-01-04T12:46:23Z</dc:date>
    </item>
    <item>
      <title>Re: Valid types in DATA inline declarations</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/valid-types-in-data-inline-declarations/m-p/12659893#M2015588</link>
      <description>&lt;P&gt;In my view, yes. Sometimes I'd says it's good practice. For example, I think&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;DATA: g_matnr TYPE marc-matnr,
      g_werks TYPE marc-werks.
SELECT-OPTIONS: s_matnr FOR g_matnr,
                s_werks FOR g_werks.&lt;BR /&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;is better than&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;DATA: g_matnr TYPE matnr,
      g_werks TYPE werks_d.
SELECT-OPTIONS: s_matnr FOR g_matnr,
                s_werks FOR g_werks.&lt;BR /&gt;&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 04 Jan 2023 12:47:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/valid-types-in-data-inline-declarations/m-p/12659893#M2015588</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2023-01-04T12:47:30Z</dc:date>
    </item>
  </channel>
</rss>

