<?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: module pool programming in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/module-pool-programming/m-p/3887646#M933878</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;Module Pool programing or dynpro programing is concerned with the UI designing of the ABAP . It is concerned with the creation of the screens and all the UI elements. There are two types of events in it. The PBO and PAI Modules handles the bulk of the task including the processing of logic and validations. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Below is a list of the links that will help you to start with the Module pool programing. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP Help &lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_47x200/helpdata/en/d1/802cfc454211d189710000e8322d00/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_47x200/helpdata/en/d1/802cfc454211d189710000e8322d00/frameset.htm&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/9f/dbab2935c111d1829f0000e829fbfe/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/9f/dbab2935c111d1829f0000e829fbfe/content.htm&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is a very good link: &lt;/P&gt;&lt;P&gt;&lt;A href="http://abapprogramming.blogspot.com/2007/08/lesson-38-introduction-for-screen.html" target="test_blank"&gt;http://abapprogramming.blogspot.com/2007/08/lesson-38-introduction-for-screen.html&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just try to do some sample programs. &lt;/P&gt;&lt;P&gt;You will find a lot of examples in SE38. Just type *DYNPRO ** &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this will help you. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;setscreen - you are calling anotehr screen from the sam screen area. aftr callin another screen , the previous screen wil not be available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;call screen - callin another screen, if you go back the previous screen wil be available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;Sandeep REddy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 31 May 2008 09:43:45 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-05-31T09:43:45Z</dc:date>
    <item>
      <title>module pool programming</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/module-pool-programming/m-p/3887645#M933877</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;1.what is module pool program?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.what is the difference between reports and module pool?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3.what r the events are involved in module pool program?what is the use of those events?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4.howmany screens we can make?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5.how can we move from module pool to reports and viceversa?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;6.what is the differnce between set screen and call screen and leave screen and exit?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 31 May 2008 07:49:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/module-pool-programming/m-p/3887645#M933877</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-31T07:49:29Z</dc:date>
    </item>
    <item>
      <title>Re: module pool programming</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/module-pool-programming/m-p/3887646#M933878</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;Module Pool programing or dynpro programing is concerned with the UI designing of the ABAP . It is concerned with the creation of the screens and all the UI elements. There are two types of events in it. The PBO and PAI Modules handles the bulk of the task including the processing of logic and validations. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Below is a list of the links that will help you to start with the Module pool programing. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP Help &lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_47x200/helpdata/en/d1/802cfc454211d189710000e8322d00/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_47x200/helpdata/en/d1/802cfc454211d189710000e8322d00/frameset.htm&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/9f/dbab2935c111d1829f0000e829fbfe/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/9f/dbab2935c111d1829f0000e829fbfe/content.htm&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is a very good link: &lt;/P&gt;&lt;P&gt;&lt;A href="http://abapprogramming.blogspot.com/2007/08/lesson-38-introduction-for-screen.html" target="test_blank"&gt;http://abapprogramming.blogspot.com/2007/08/lesson-38-introduction-for-screen.html&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just try to do some sample programs. &lt;/P&gt;&lt;P&gt;You will find a lot of examples in SE38. Just type *DYNPRO ** &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this will help you. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;setscreen - you are calling anotehr screen from the sam screen area. aftr callin another screen , the previous screen wil not be available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;call screen - callin another screen, if you go back the previous screen wil be available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;Sandeep REddy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 31 May 2008 09:43:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/module-pool-programming/m-p/3887646#M933878</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-31T09:43:45Z</dc:date>
    </item>
    <item>
      <title>Re: module pool programming</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/module-pool-programming/m-p/3887647#M933879</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Durga,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Module pool programs are also called dialog programs ,used to get input from the user in an interactive manner.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Diiference between Reports and Module pool programs&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;1. Reports are used to display data from the SAP database.&lt;/P&gt;&lt;P&gt;    Mostly they use the SAP standard screen 1000.&lt;/P&gt;&lt;P&gt;    Module pool are used to get data from the user and store   in   the SAP database as well as to display them from the database. They contain user defined screens designed using screen painter.&lt;/P&gt;&lt;P&gt;2. Tcode for Reports - se38&lt;/P&gt;&lt;P&gt;    Tcode for module pool programs -se80, or se38 and se41,se51,&lt;/P&gt;&lt;P&gt;3. Reports are of type 1 Executable program&lt;/P&gt;&lt;P&gt;    Module pool pgm are of type M and can be executed only via a tcode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Events in module pool programming&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;PBO - Proccess Before Output&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;The event PROCESS BEFORE OUTPUT (PBO) is triggered by the runtime environment before the screen of a dynpro is sent to the presentation layer. After processing the related event block, the contents of the global fields of the ABAP program are transported into screen fields of the same name and then the screen is displayed in the window. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;PAI   - Process After Input&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;The event PROCESS AFTER INPUT (PAI) is triggered by a user action on the user interface, which is associated with a function code&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;POV - Process on Value request&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;POH - Process on Help request&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The events PROCESS ON HELP-REQUEST (POH) and PROCESS ON VALUE-REQUEST (POV) are triggered by the request for the field help (F1) or the input help (F4) for a screen element of the screen&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Moving from module pool to reports is possible by using &lt;STRONG&gt;submit&lt;/STRONG&gt; statement.&lt;/P&gt;&lt;P&gt;Moving from report to module pool is by using &lt;STRONG&gt;Call transaction&lt;/STRONG&gt; statement&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Difference between set screen and call screen&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&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;&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;Regards,&lt;/P&gt;&lt;P&gt;Charumathi.B&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Jun 2008 06:54:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/module-pool-programming/m-p/3887647#M933879</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-02T06:54:08Z</dc:date>
    </item>
  </channel>
</rss>

