<?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: Variable naming conventions in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/variable-naming-conventions/m-p/2298319#M502084</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;It is usually done by the project standards. Usually it is defined during the beggining. Ask for that document.&lt;/P&gt;&lt;P&gt;Usually is like this:&lt;/P&gt;&lt;P&gt;TI_X for internal tables.&lt;/P&gt;&lt;P&gt;G_X for globlas&lt;/P&gt;&lt;P&gt;T_X for Types&lt;/P&gt;&lt;P&gt;WA_X for work areas&lt;/P&gt;&lt;P&gt;C_X for constants.&lt;/P&gt;&lt;P&gt;P_X parameters, sometimes PI_X for input and PO_X for output.&lt;/P&gt;&lt;P&gt;FS_x for field symbols&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;etc,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps dont forget to reward&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gabriel P.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 15 May 2007 19:34:14 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-05-15T19:34:14Z</dc:date>
    <item>
      <title>Variable naming conventions</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/variable-naming-conventions/m-p/2298316#M502081</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I come from a mostly JAVA background. Big emphasis in that arena on encapsulation and modularization of code to help facilitate ease of maintenance and reuse...in theory &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt; I sometimes struggle with variable naming conventions within my ABAP code because I'm not all together certain there are any. In C or C++ I might use a derivation of Hungarian notation to name varaibles...and in JAVA I might observe certain object oriented rules regarding varaible naming...I find myself using a combination of those two protocols in my ABAP code. Does anyone have any suggestions for how I might name global and lcoal variables within my code?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mat&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 May 2007 18:34:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/variable-naming-conventions/m-p/2298316#M502081</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-15T18:34:23Z</dc:date>
    </item>
    <item>
      <title>Re: Variable naming conventions</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/variable-naming-conventions/m-p/2298317#M502082</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;For every project there is specific client driven SAP naming convention which needs to be followed for ABAP code.&lt;/P&gt;&lt;P&gt;e.g. say -&lt;/P&gt;&lt;HR originaltext="---" /&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;for types - TYPE_&amp;lt;NAME&amp;gt;&lt;/P&gt;&lt;P&gt;for internal table T_&amp;lt;NAME&amp;gt;&lt;/P&gt;&lt;P&gt;for global variable GV_&amp;lt;NAME&amp;gt;, etc.&lt;/P&gt;&lt;P&gt;So just follow the convention given by the client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Still you can check these threads -&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="3119059"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="3120304"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Amit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 May 2007 18:38:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/variable-naming-conventions/m-p/2298317#M502082</guid>
      <dc:creator>amit_khare</dc:creator>
      <dc:date>2007-05-15T18:38:38Z</dc:date>
    </item>
    <item>
      <title>Re: Variable naming conventions</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/variable-naming-conventions/m-p/2298318#M502083</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;Please check this links perhaps they may help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/92/c2b084bc1d11d2958700a0c94260a5/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/92/c2b084bc1d11d2958700a0c94260a5/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://websmp101.sap-ag.de/~sapdownload/011000358700004455192006E/NameConventions.pdf" target="test_blank"&gt;https://websmp101.sap-ag.de/~sapdownload/011000358700004455192006E/NameConventions.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/2a/6b0b1f547a11d189600000e829fbbd/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/2a/6b0b1f547a11d189600000e829fbbd/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/011ccf90-0201-0010-92a7-b319adf89b73" target="test_blank"&gt;https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/011ccf90-0201-0010-92a7-b319adf89b73&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://web.mit.edu/sapr3/dev/newdevstand.html" target="test_blank"&gt;http://web.mit.edu/sapr3/dev/newdevstand.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ferry Lianto&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 May 2007 18:48:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/variable-naming-conventions/m-p/2298318#M502083</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-15T18:48:36Z</dc:date>
    </item>
    <item>
      <title>Re: Variable naming conventions</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/variable-naming-conventions/m-p/2298319#M502084</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;It is usually done by the project standards. Usually it is defined during the beggining. Ask for that document.&lt;/P&gt;&lt;P&gt;Usually is like this:&lt;/P&gt;&lt;P&gt;TI_X for internal tables.&lt;/P&gt;&lt;P&gt;G_X for globlas&lt;/P&gt;&lt;P&gt;T_X for Types&lt;/P&gt;&lt;P&gt;WA_X for work areas&lt;/P&gt;&lt;P&gt;C_X for constants.&lt;/P&gt;&lt;P&gt;P_X parameters, sometimes PI_X for input and PO_X for output.&lt;/P&gt;&lt;P&gt;FS_x for field symbols&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;etc,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps dont forget to reward&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gabriel P.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 May 2007 19:34:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/variable-naming-conventions/m-p/2298319#M502084</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-15T19:34:14Z</dc:date>
    </item>
  </channel>
</rss>

