<?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: about dialog programming in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/about-dialog-programming/m-p/2818452#M659155</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;events in dialog programming&lt;/P&gt;&lt;P&gt;process before output&lt;/P&gt;&lt;P&gt;used for declaring variables and assigning pf satus for screens&lt;/P&gt;&lt;P&gt;process after in put&lt;/P&gt;&lt;P&gt;used for screen validations and allow user to interact with screens&lt;/P&gt;&lt;P&gt;means screen sequences&lt;/P&gt;&lt;P&gt;call screen&lt;/P&gt;&lt;P&gt;set screen&lt;/P&gt;&lt;P&gt;leave screen&lt;/P&gt;&lt;P&gt;leave to screen &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;process on value request provides F4 functionality&lt;/P&gt;&lt;P&gt;process on help provides F1 functionality&lt;/P&gt;&lt;P&gt;reward for use ful points&lt;/P&gt;&lt;P&gt;REgards&lt;/P&gt;&lt;P&gt;Nagesh.Paruchuri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 26 Sep 2007 12:05:35 GMT</pubDate>
    <dc:creator>paruchuri_nagesh</dc:creator>
    <dc:date>2007-09-26T12:05:35Z</dc:date>
    <item>
      <title>about dialog programming</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/about-dialog-programming/m-p/2818451#M659154</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Plz explain what r the events in dialog programming.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks . points sure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anshu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Sep 2007 11:46:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/about-dialog-programming/m-p/2818451#M659154</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-26T11:46:11Z</dc:date>
    </item>
    <item>
      <title>Re: about dialog programming</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/about-dialog-programming/m-p/2818452#M659155</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;events in dialog programming&lt;/P&gt;&lt;P&gt;process before output&lt;/P&gt;&lt;P&gt;used for declaring variables and assigning pf satus for screens&lt;/P&gt;&lt;P&gt;process after in put&lt;/P&gt;&lt;P&gt;used for screen validations and allow user to interact with screens&lt;/P&gt;&lt;P&gt;means screen sequences&lt;/P&gt;&lt;P&gt;call screen&lt;/P&gt;&lt;P&gt;set screen&lt;/P&gt;&lt;P&gt;leave screen&lt;/P&gt;&lt;P&gt;leave to screen &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;process on value request provides F4 functionality&lt;/P&gt;&lt;P&gt;process on help provides F1 functionality&lt;/P&gt;&lt;P&gt;reward for use ful points&lt;/P&gt;&lt;P&gt;REgards&lt;/P&gt;&lt;P&gt;Nagesh.Paruchuri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Sep 2007 12:05:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/about-dialog-programming/m-p/2818452#M659155</guid>
      <dc:creator>paruchuri_nagesh</dc:creator>
      <dc:date>2007-09-26T12:05:35Z</dc:date>
    </item>
    <item>
      <title>Re: about dialog programming</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/about-dialog-programming/m-p/2818453#M659156</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Anshu,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check these links,&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://sap.niraj.tripod.com/id25.html" target="test_blank"&gt;http://sap.niraj.tripod.com/id25.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapbrainsonline.com/FAQs/TECHNICAL/SAP_ABAP_Transactions_FAQ.html" target="test_blank"&gt;http://www.sapbrainsonline.com/FAQs/TECHNICAL/SAP_ABAP_Transactions_FAQ.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb2d67358411d1829f0000e829fbfe/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb2d67358411d1829f0000e829fbfe/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Pritha.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if helpful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Sep 2007 14:19:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/about-dialog-programming/m-p/2818453#M659156</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-26T14:19:41Z</dc:date>
    </item>
    <item>
      <title>Re: about dialog programming</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/about-dialog-programming/m-p/2818454#M659157</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Anshu,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;PROCESS BEFORE OUTPUT (PBO)&amp;lt;/b&amp;gt; is automatically triggered after the PAI processing of the previous screen and before the current screen is displayed. You can program the PBO processing of the screen in this block. At the end of the PBO processing, the screen is displayed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;PROCESS AFTER INPUT (PAI)&amp;lt;/b&amp;gt; is triggered when the user chooses a function on the screen. You can program the PAI processing of the screen in this block. At the end of the PAI.&lt;/P&gt;&lt;P&gt;processing, the system either calls the next screen or carries on processing at the point from which the screen was called. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;PROCESS ON HELP-REQUEST (POH) and PROCESS ON VALUE-REQUEST (POV)&amp;lt;/b&amp;gt; are triggered when the user requests field help (F1) or possible values help (F4) respectively. You can program the appropriate coding in the corresponding event blocks. At the end of processing, the system carries on processing the current screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;few more info on the same in FAQ format.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are &amp;#147;field&amp;#148; and &amp;#147;chain&amp;#148; statements ?&lt;/P&gt;&lt;P&gt;The FIELD and CHAIN flow logic statements let you program your own field checks. FIELD and CHAIN tell the system which fields you are checking,and whether the system should perform checks in the flow logic or call an ABAP/4 module. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is an on &amp;#147;*-input field&amp;#148; statement ?&lt;/P&gt;&lt;P&gt;-	ON *-INPUT&lt;/P&gt;&lt;P&gt;The ABAP/4 module is called if the user has entered a "*" in the first character of the field, and the field has the attribute *-entry in the Screen Painter. You can use this option in exceptional cases where you want to check only fields with certain kinds of input.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are conditional chain statements ?&lt;/P&gt;&lt;P&gt;-	ON CHAIN-INPUT similar to ON INPUT. &lt;/P&gt;&lt;P&gt;The ABAP/4 module is called if any one of the fields in the chain contains a value other than its initial value (blanks or nulls).&lt;/P&gt;&lt;P&gt;           ON CHAIN-REQUEST&lt;/P&gt;&lt;P&gt;This condition functions just like ON REQUEST, but the ABAP/4 module is called if any one of the fields in the chain changes value. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is &amp;#147;at exit-command&amp;#148; ?&lt;/P&gt;&lt;P&gt;-	The flow logic keyword AT EXIT-COMMAND is a special addition to the MODULE statement in the flow logic. AT EXIT-COMMAND lets you call a module before the system executes the automatic field checks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Which function type has to be used for using &amp;#147;at exit-command&amp;#148; ?&lt;/P&gt;&lt;P&gt;-	To use AT EXIT-COMMAND, we must assign a function type &amp;#145;E&amp;#146; to the relevant function in the Menu Painter or Screen Painter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the difference between SET SCREEN and CALL SCREEN ?&lt;/P&gt;&lt;P&gt;With SET SCREEN, the current screen simply specifies the next screen in the chain. control branches to this next screen as soon as the current screen has been processed. Return from next screen to current screen is not automatic. It does not      interrupt processing of the current screen.  If we want to branch to the next screen without finishing the current one, use LEAVE SCREEN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With CALL SCREEN, the current (calling) chain is suspended, and a next screen (or screen chain) is called in. The called screen can then return to the suspended chain with the statement LEAVE   SCREEN TO SCREEN 0. Sometimes we might want to let an user call a popup screen from the main application screen to let them enter secondary information. After they have completed their entries, the users should be able to close the popup and return directly to the place where they left off in the main screen. Here comes CALL SCREEN into picture. This statement lets us insert such a sequence into the current one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward points if this helps.&lt;/P&gt;&lt;P&gt;Manish&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Sep 2007 14:30:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/about-dialog-programming/m-p/2818454#M659157</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-26T14:30:24Z</dc:date>
    </item>
  </channel>
</rss>

