<?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 SY-UCOMM and OK_CODE in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/sy-ucomm-and-ok-code/m-p/5530378#M1263522</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;&lt;/P&gt;&lt;P&gt;I have got a simple question that I would like to clarify. In report program, the function code will be assigned to both SY-UCOMM and OK_CODE field defined in the screen. I would like to know what's the purpose of making two different versions of the same value? Why shouldn't I access the sy-ucomm directly instead? If so, I can skip saving the OK_CODE to a temporary variable and clearing it up.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Alex&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 24 Apr 2009 08:36:24 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-04-24T08:36:24Z</dc:date>
    <item>
      <title>SY-UCOMM and OK_CODE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sy-ucomm-and-ok-code/m-p/5530378#M1263522</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;&lt;/P&gt;&lt;P&gt;I have got a simple question that I would like to clarify. In report program, the function code will be assigned to both SY-UCOMM and OK_CODE field defined in the screen. I would like to know what's the purpose of making two different versions of the same value? Why shouldn't I access the sy-ucomm directly instead? If so, I can skip saving the OK_CODE to a temporary variable and clearing it up.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Alex&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Apr 2009 08:36:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sy-ucomm-and-ok-code/m-p/5530378#M1263522</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-04-24T08:36:24Z</dc:date>
    </item>
    <item>
      <title>Re: SY-UCOMM and OK_CODE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sy-ucomm-and-ok-code/m-p/5530379#M1263523</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Reason found in &lt;A href="http://help.sap.com/saphelp_nw2004s/helpdata/en/9f/dbaa1335c111d1829f0000e829fbfe/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw2004s/helpdata/en/9f/dbaa1335c111d1829f0000e829fbfe/content.htm&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"In your ABAP programs, you should work with the OK_CODE field instead of sy-ucomm. There are two reasons for this: Firstly, the ABAP program has full control over fields declared within it, and secondly, you should never change the value of an ABAP system field."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Alex Lau on Apr 24, 2009 10:38 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Apr 2009 08:37:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sy-ucomm-and-ok-code/m-p/5530379#M1263523</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-04-24T08:37:51Z</dc:date>
    </item>
  </channel>
</rss>

