<?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 reports in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/reports/m-p/2065587#M427388</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is the main difference between AT PF &amp;amp; AT USER-COMMAND ?&lt;/P&gt;&lt;P&gt;please give reply.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Mar 2007 14:45:03 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-03-08T14:45:03Z</dc:date>
    <item>
      <title>reports</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/reports/m-p/2065587#M427388</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is the main difference between AT PF &amp;amp; AT USER-COMMAND ?&lt;/P&gt;&lt;P&gt;please give reply.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Mar 2007 14:45:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/reports/m-p/2065587#M427388</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-08T14:45:03Z</dc:date>
    </item>
    <item>
      <title>Re: reports</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/reports/m-p/2065588#M427389</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;AT USER-COMMAND event is for handling user defined function.Say for eg when the user clicks the Pushbutton in the list you can do further processing for this action in AT USER-COMMAND event.&lt;/P&gt;&lt;P&gt;AT PF-STATUS is outdated/obsolete so dont think/worry about it.But it is used for handling function keys in the list.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Mar 2007 14:48:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/reports/m-p/2065588#M427389</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-08T14:48:04Z</dc:date>
    </item>
    <item>
      <title>Re: reports</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/reports/m-p/2065589#M427390</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;AT PFnn&lt;/P&gt;&lt;P&gt;  statements.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These event blocks are executed when the user chooses the corresponding function key. The position of the cursor in the list is irrelevant. &lt;/P&gt;&lt;P&gt;If you use these event blocks at all, it should only be for temporary test versions. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In production programs, you should only use AT USER-COMMAND with a dialog status of your own to assign function codes to function keys. When you use your own interfaces, the system displays a function text explaining what the function does. This does not happen when you use AT PFnn event blocks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;madhu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Mar 2007 14:51:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/reports/m-p/2065589#M427390</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-08T14:51:07Z</dc:date>
    </item>
    <item>
      <title>Re: reports</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/reports/m-p/2065590#M427391</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you might want to use F1 help in SAP. they explain it in very short terms, probably better than i can but still i try.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;at PF is an event which is beeing thrown just on LISTS while the ok_code is like PF## where ## stands for a number between 01 and 24.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;at user command is a more generic event which is beeing thrown on every dynpro (be aware that selection screens and lists are technically dynpros as well).&lt;/P&gt;&lt;P&gt;SAP help says that even on lists you better use at user-command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Probably thats why i didnt hear from at PF till today, i just dont need it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Mar 2007 14:51:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/reports/m-p/2065590#M427391</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-08T14:51:28Z</dc:date>
    </item>
    <item>
      <title>Re: reports</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/reports/m-p/2065591#M427392</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;AT USER-COMMAND - Event in interactive reporting &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This event is executed whenever the user presses a function key in the list or makes an entry in the command field . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some functions are executed directly by the system and thus cannot be processed by programs. These include: &lt;/P&gt;&lt;P&gt;PICK See variant AT LINE-SELECTION PFn See variant AT PFn /... System command %... System command PRI Print BACK Back RW Cancel P... Scroll function (e.g.: P+ , P- , PP+3 , PS-- etc.) &lt;/P&gt;&lt;P&gt;Instead of this functions, you can use the SCROLL statement in programs. &lt;/P&gt;&lt;P&gt;Since many of these system functions begin with "P", you should avoid using this letter to start your own function codes. &lt;/P&gt;&lt;P&gt;Otherwise, the effect is as for AT LINE-SELECTION ; also, the current function code is stored in the system field SY-UCOMM . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: NUMBER1 TYPE I VALUE 20,&lt;/P&gt;&lt;P&gt;NUMBER2 TYPE I VALUE 5,&lt;/P&gt;&lt;P&gt;RESULT TYPE I.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;START-OF-SELECTION.&lt;/P&gt;&lt;P&gt;WRITE: / NUMBER1, '?', NUMBER2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AT USER-COMMAND.&lt;/P&gt;&lt;P&gt;CASE SY-UCOMM.&lt;/P&gt;&lt;P&gt;WHEN 'ADD'.&lt;/P&gt;&lt;P&gt;RESULT = NUMBER1 + NUMBER2.&lt;/P&gt;&lt;P&gt;WHEN 'SUBT'.&lt;/P&gt;&lt;P&gt;RESULT = NUMBER1 - NUMBER2.&lt;/P&gt;&lt;P&gt;WHEN 'MULT'.&lt;/P&gt;&lt;P&gt;RESULT = NUMBER1 * NUMBER2.&lt;/P&gt;&lt;P&gt;WHEN 'DIVI'.&lt;/P&gt;&lt;P&gt;RESULT = NUMBER1 / NUMBER2.&lt;/P&gt;&lt;P&gt;WHEN OTHERS.&lt;/P&gt;&lt;P&gt;WRITE 'Unknown function code'.&lt;/P&gt;&lt;P&gt;EXIT.&lt;/P&gt;&lt;P&gt;ENDCASE.&lt;/P&gt;&lt;P&gt;WRITE: / 'Result:', RESULT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After entry of a function code, the appropriate processing is performed under the event AT USER-COMMAND and the result is displayed in the details list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AT PFn - Event in interactive reporting &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here, n stands for a numeric value between 0 and 99. &lt;/P&gt;&lt;P&gt;This event is executed whenever the user presses a function key that contains the function code PFn in the interface definition. The default status for lists contains some of these functions. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Otherwise, the effect is as for the variant AT LINE-SELECTION . The cursor can be on any line. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To ensure that the chosen function is executed only for valid lines, you can check the current HIDE information. This variant should be used only for test or prototyping purposes, since the default status is not normally used. Instead, you should set a program-specific status with SET PF-STATUS . This should not contain any function codes beginning with " PF ". &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA NUMBER LIKE SY-INDEX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;START-OF-SELECTION.&lt;/P&gt;&lt;P&gt;DO 9 TIMES.&lt;/P&gt;&lt;P&gt;WRITE: / 'Row', (2) SY-INDEX.&lt;/P&gt;&lt;P&gt;NUMBER = SY-INDEX.&lt;/P&gt;&lt;P&gt;HIDE NUMBER.&lt;/P&gt;&lt;P&gt;ENDDO.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AT PF8.&lt;/P&gt;&lt;P&gt;CHECK NOT NUMBER IS INITIAL.&lt;/P&gt;&lt;P&gt;WRITE: / 'Cursor was in row', (2) NUMBER.&lt;/P&gt;&lt;P&gt;CLEAR NUMBER.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Mar 2007 14:52:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/reports/m-p/2065591#M427392</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-08T14:52:19Z</dc:date>
    </item>
    <item>
      <title>Re: reports</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/reports/m-p/2065592#M427393</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;check these...&lt;/P&gt;&lt;P&gt;&lt;A href="https://forums.sdn.sap.com/click.jspa?searchID=1518159&amp;amp;messageID=2983379" target="test_blank"&gt;https://forums.sdn.sap.com/click.jspa?searchID=1518159&amp;amp;messageID=2983379&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://forums.sdn.sap.com/click.jspa?searchID=1518159&amp;amp;messageID=3119476" target="test_blank"&gt;https://forums.sdn.sap.com/click.jspa?searchID=1518159&amp;amp;messageID=3119476&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;priya.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Mar 2007 14:52:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/reports/m-p/2065592#M427393</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-08T14:52:47Z</dc:date>
    </item>
  </channel>
</rss>

