<?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 in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/module-pool/m-p/2841648#M665539</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The way to do this is to create your own screen in a Z* program (or SAPMZ* for module pool), build required screen layout to get data, build buttons etc for saving, changing or whatever you need, and then create Sales order by calling BADI in PAI processing (probably BAPI_SALESORDER_CREATEFROMDAT2).  Then need to add error handling and BAPI commit processing. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This could be quite a bit of work.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another option is to persuade user to live with standard screen in VA01 and use customising to hide unused fields where possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could also create the screen /  processing as Web Dynpro or as BSP Page instead of as Dynpro screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andrew&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 23 Sep 2007 02:27:10 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-09-23T02:27:10Z</dc:date>
    <item>
      <title>module pool</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/module-pool/m-p/2841647#M665538</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;how  to create sale order va01 .that end user need all the sale order creation mandatory fields in single page.by using module pool.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 22 Sep 2007 12:34:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/module-pool/m-p/2841647#M665538</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-22T12:34:35Z</dc:date>
    </item>
    <item>
      <title>Re: module pool</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/module-pool/m-p/2841648#M665539</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The way to do this is to create your own screen in a Z* program (or SAPMZ* for module pool), build required screen layout to get data, build buttons etc for saving, changing or whatever you need, and then create Sales order by calling BADI in PAI processing (probably BAPI_SALESORDER_CREATEFROMDAT2).  Then need to add error handling and BAPI commit processing. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This could be quite a bit of work.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another option is to persuade user to live with standard screen in VA01 and use customising to hide unused fields where possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could also create the screen /  processing as Web Dynpro or as BSP Page instead of as Dynpro screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andrew&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 23 Sep 2007 02:27:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/module-pool/m-p/2841648#M665539</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-23T02:27:10Z</dc:date>
    </item>
  </channel>
</rss>

