<?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: Mandatory Fields in Module pool in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/mandatory-fields-in-module-pool/m-p/11081087#M1901873</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Amit,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As Raymond said, it will be impossible to do if you don't remove the obligatory tick.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only way to implement your requirement, is to remove the obligatory ticks, and use code to validate the field in PAI.&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;In your screen flow PAI:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;PROCESS AFTER &lt;/STRONG&gt;&lt;SPAN class="L0S52"&gt;&lt;STRONG&gt;INPUT&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN class="L0S52"&gt;FIELD &lt;/SPAN&gt;INPUT_FIELD &lt;SPAN class="L0S52"&gt;MODULE &lt;/SPAN&gt;validate_initial&lt;/STRONG&gt;&lt;SPAN class="L0S55"&gt;&lt;STRONG&gt;.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;And inside the module validate_initial:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;SPAN class="L0S52"&gt;&lt;STRONG&gt;IF sy&lt;SPAN class="L0S70"&gt;-&lt;/SPAN&gt;ucomm &lt;SPAN class="L0S52"&gt;EQ &lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;'BUTTON1' &lt;/SPAN&gt;&lt;SPAN class="L0S52"&gt;AND &lt;/SPAN&gt;input_field &lt;SPAN class="L0S52"&gt;IS &lt;/SPAN&gt;&lt;SPAN class="L0S52"&gt;INITIAL&lt;/SPAN&gt;&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN class="L0S52"&gt;MESSAGE &lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;'Fill all required entries' &lt;/SPAN&gt;&lt;SPAN class="L0S52"&gt;TYPE &lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;'E'&lt;/SPAN&gt;&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;SPAN class="L0S52"&gt;ENDIF&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN class="L0S55"&gt;&lt;STRONG&gt;.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;Depending on how your screen is built, you might need to use:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;STRONG&gt;CHAIN.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt; FIELDS: field1 MODULE validate,&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; field2 MODULE validate2....&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;....&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;STRONG&gt;ENDCHAIN.&lt;/STRONG&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;Regards,&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;Thales Schmidt&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 13 May 2015 14:02:21 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2015-05-13T14:02:21Z</dc:date>
    <item>
      <title>Mandatory Fields in Module pool</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/mandatory-fields-in-module-pool/m-p/11081082#M1901868</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;I have created a module pool program in which there are around 30 input/output fields on screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;out of which i have kept 3 fields are mandatory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LIFNR - Vendor ID&lt;/P&gt;&lt;P&gt;BELNR - Acc. Dc. No.&lt;/P&gt;&lt;P&gt;Invoice date.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;User update all the fields and and it gets saves into database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now i have placed one more command button on screen for display of data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IF user enter the BELNR no. and click on display all others details should be auto populated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But after entering BELNR and clicking in display it gives error "Fill all the required entries".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I do not want remove the mandatory tick of LIFNR and invoice date while entering data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas to overcome this problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Amit Diwvedi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 May 2015 11:40:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/mandatory-fields-in-module-pool/m-p/11081082#M1901868</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-05-13T11:40:52Z</dc:date>
    </item>
    <item>
      <title>Re: Mandatory Fields in Module pool</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/mandatory-fields-in-module-pool/m-p/11081083#M1901869</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;use chain endchain concept &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 May 2015 11:55:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/mandatory-fields-in-module-pool/m-p/11081083#M1901869</guid>
      <dc:creator>former_member218424</dc:creator>
      <dc:date>2015-05-13T11:55:11Z</dc:date>
    </item>
    <item>
      <title>Re: Mandatory Fields in Module pool</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/mandatory-fields-in-module-pool/m-p/11081084#M1901870</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had this problem before and I prefered to control everything in P.A.I event. I did it:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;----------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;PROCESS BEFORE &lt;SPAN class="L0S52"&gt;OUTPUT&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &lt;SPAN class="L0S52"&gt;MODULE &lt;/SPAN&gt;status_1000&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &lt;SPAN class="L0S52"&gt;MODULE &lt;/SPAN&gt;bloquear_campos&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;BR /&gt; &lt;BR /&gt; PROCESS AFTER &lt;SPAN class="L0S52"&gt;INPUT&lt;/SPAN&gt;&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &lt;SPAN class="L0S52"&gt;FIELD&lt;/SPAN&gt;&lt;SPAN class="L0S55"&gt;: &lt;/SPAN&gt;w_xxx&lt;SPAN class="L0S70"&gt;-&lt;/SPAN&gt;belnr&amp;nbsp; &lt;SPAN class="L0S52"&gt;MODULE &lt;/SPAN&gt;check_field.&lt;SPAN class="L0S55"&gt;&lt;/SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;&amp;nbsp;&amp;nbsp; &lt;SPAN class="L0S52"&gt;MODULE &lt;/SPAN&gt;user_command_1000&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;----------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S52"&gt;MODULE &lt;/SPAN&gt;check_field.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; if belnr is initial&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MESSAGE 'xxxxxxxxx' TYPE 'E'.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; endif.&lt;/P&gt;&lt;P&gt;ENDMODULE.&lt;/P&gt;&lt;P&gt;----------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You also can do that with loop at screen, setting group property for each field in your screen painter, and after:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;----------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;LOOP &lt;SPAN class="L0S52"&gt;AT &lt;/SPAN&gt;&lt;SPAN class="L0S52"&gt;SCREEN&lt;/SPAN&gt;&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN class="L0S52"&gt;IF &lt;/SPAN&gt;&lt;SPAN class="L0S52"&gt;screen&lt;/SPAN&gt;&lt;SPAN class="L0S70"&gt;-&lt;/SPAN&gt;group1 &lt;SPAN class="L0S55"&gt;= &lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;'GR1'&lt;/SPAN&gt;&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN class="L0S52"&gt;screen&lt;/SPAN&gt;&lt;SPAN class="L0S70"&gt;-&lt;/SPAN&gt;&lt;SPAN class="L0S52"&gt;input &lt;/SPAN&gt;&lt;SPAN class="L0S55"&gt;= &lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;'0'&lt;/SPAN&gt;&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN class="L0S52"&gt;MODIFY &lt;/SPAN&gt;&lt;SPAN class="L0S52"&gt;SCREEN&lt;/SPAN&gt;&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN class="L0S52"&gt;ENDIF&lt;/SPAN&gt;&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &lt;SPAN class="L0S52"&gt;ENDLOOP&lt;/SPAN&gt;&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;----------------------------------------------------------------------------&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 May 2015 12:16:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/mandatory-fields-in-module-pool/m-p/11081084#M1901870</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-05-13T12:16:55Z</dc:date>
    </item>
    <item>
      <title>Re: Mandatory Fields in Module pool</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/mandatory-fields-in-module-pool/m-p/11081085#M1901871</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE&gt;&lt;CODE&gt;
&lt;P&gt;I do not want remove the mandatory tick of LIFNR and invoice date while entering data.&lt;/P&gt;

&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Don't seem possible:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Mandatory fields in dynpro definition&lt;/LI&gt;&lt;/UL&gt;&lt;P style="padding-left: 30px;"&gt;As soon as there are initial mandatory fields on screen, only exit function code will be executed, other function code will trigger the Fill all the required entries message. So you cannot do that, as exit function-code will not transfer any data from screen to program and you won't be able to read data with the required database key...&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Mandatory fields in code (FIELD/MODULE)&lt;/LI&gt;&lt;/UL&gt;&lt;P style="padding-left: 30px;"&gt;If you manage the mandatory field in some FIELD/MODULE statement, even after execution of a USER_COMMAND module that would fill the data. As soon as the error message for required entries is raised, no data is sent back from program to screen and you lose previous action...&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;Raymond&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 May 2015 13:12:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/mandatory-fields-in-module-pool/m-p/11081085#M1901871</guid>
      <dc:creator>RaymondGiuseppi</dc:creator>
      <dc:date>2015-05-13T13:12:53Z</dc:date>
    </item>
    <item>
      <title>Re: Mandatory Fields in Module pool</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/mandatory-fields-in-module-pool/m-p/11081086#M1901872</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Amit,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; In my opinion It is not possible without removing Mandatory fields for your requirement.&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;Surya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 May 2015 13:59:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/mandatory-fields-in-module-pool/m-p/11081086#M1901872</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-05-13T13:59:53Z</dc:date>
    </item>
    <item>
      <title>Re: Mandatory Fields in Module pool</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/mandatory-fields-in-module-pool/m-p/11081087#M1901873</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Amit,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As Raymond said, it will be impossible to do if you don't remove the obligatory tick.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only way to implement your requirement, is to remove the obligatory ticks, and use code to validate the field in PAI.&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;In your screen flow PAI:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;PROCESS AFTER &lt;/STRONG&gt;&lt;SPAN class="L0S52"&gt;&lt;STRONG&gt;INPUT&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN class="L0S52"&gt;FIELD &lt;/SPAN&gt;INPUT_FIELD &lt;SPAN class="L0S52"&gt;MODULE &lt;/SPAN&gt;validate_initial&lt;/STRONG&gt;&lt;SPAN class="L0S55"&gt;&lt;STRONG&gt;.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;And inside the module validate_initial:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;SPAN class="L0S52"&gt;&lt;STRONG&gt;IF sy&lt;SPAN class="L0S70"&gt;-&lt;/SPAN&gt;ucomm &lt;SPAN class="L0S52"&gt;EQ &lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;'BUTTON1' &lt;/SPAN&gt;&lt;SPAN class="L0S52"&gt;AND &lt;/SPAN&gt;input_field &lt;SPAN class="L0S52"&gt;IS &lt;/SPAN&gt;&lt;SPAN class="L0S52"&gt;INITIAL&lt;/SPAN&gt;&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN class="L0S52"&gt;MESSAGE &lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;'Fill all required entries' &lt;/SPAN&gt;&lt;SPAN class="L0S52"&gt;TYPE &lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;'E'&lt;/SPAN&gt;&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;SPAN class="L0S52"&gt;ENDIF&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN class="L0S55"&gt;&lt;STRONG&gt;.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;Depending on how your screen is built, you might need to use:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;STRONG&gt;CHAIN.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt; FIELDS: field1 MODULE validate,&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; field2 MODULE validate2....&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;....&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;STRONG&gt;ENDCHAIN.&lt;/STRONG&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;Regards,&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;Thales Schmidt&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 May 2015 14:02:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/mandatory-fields-in-module-pool/m-p/11081087#M1901873</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-05-13T14:02:21Z</dc:date>
    </item>
    <item>
      <title>Re: Mandatory Fields in Module pool</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/mandatory-fields-in-module-pool/m-p/11081088#M1901874</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Amit,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you make user click a button to enter data entry mode then you could do it:&amp;nbsp; Define a variable GV_ENTRY_MODE that you set to X in the PAI when that button is pressed, and set to blank when the button to display an entry is clicked.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Do not set mandatory attribute in screen painter&lt;/LI&gt;&lt;LI&gt;In PBO, set SCREEN-REQUIRED = '1' if GV_ENTRY_MODE = 'X'&lt;UL&gt;&lt;LI&gt;Probably also want to change SCREEN-INPUT depending on GV_ENTRY_MODE so they cannot change fields when in display mode&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Jim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 May 2015 17:35:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/mandatory-fields-in-module-pool/m-p/11081088#M1901874</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-05-13T17:35:52Z</dc:date>
    </item>
  </channel>
</rss>

