<?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: ALV in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv/m-p/3317820#M794766</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It is not possible to set some fields as mandatory using fieldcatalog or by layout setting. But we can write some logic to check the whether required fields are filled or not and then give an error message.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Before updating the values, check the internal table whether all the required fields have been filled or not, other wise give an error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOOP AT lt_output INTO lwa_output.&lt;/P&gt;&lt;P&gt;IF lwa_output-req_field IS INITIAL.&lt;/P&gt;&lt;P&gt;MESSAGE e000(z1). "Field is mandatory&lt;/P&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;ENDLOOP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 Jan 2008 07:19:43 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-01-30T07:19:43Z</dc:date>
    <item>
      <title>ALV</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv/m-p/3317819#M794765</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 ALV grid using ABAP OO.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need to make some of the fields as mandatory ones.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pls help me on this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried using DATA_CHANGED. But for the first time it brings up all the fields(even if teh fields are not modified) in the MT_GOOD_CELLS .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pls help&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2008 07:16:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv/m-p/3317819#M794765</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-30T07:16:56Z</dc:date>
    </item>
    <item>
      <title>Re: ALV</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv/m-p/3317820#M794766</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It is not possible to set some fields as mandatory using fieldcatalog or by layout setting. But we can write some logic to check the whether required fields are filled or not and then give an error message.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Before updating the values, check the internal table whether all the required fields have been filled or not, other wise give an error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOOP AT lt_output INTO lwa_output.&lt;/P&gt;&lt;P&gt;IF lwa_output-req_field IS INITIAL.&lt;/P&gt;&lt;P&gt;MESSAGE e000(z1). "Field is mandatory&lt;/P&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;ENDLOOP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2008 07:19:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv/m-p/3317820#M794766</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-30T07:19:43Z</dc:date>
    </item>
    <item>
      <title>Re: ALV</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv/m-p/3317821#M794767</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;Which ever field you want as mandatory,in the fieldcatalog place the component VALEXI as 'X'. It would make that field mandatory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN __default_attr="red" __jive_macro_name="color"&gt;&lt;STRONG&gt;&amp;lt;REMOVED BY MODERATOR - REQUEST OR OFFER POINTS ARE FORBIDDEN&amp;gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Dishant&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Alvaro Tejada Galindo on Aug 25, 2008 5:21 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2008 07:24:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv/m-p/3317821#M794767</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-30T07:24:07Z</dc:date>
    </item>
    <item>
      <title>Re: ALV</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv/m-p/3317822#M794768</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dishant,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thats not right, sorry...valexi works only, if in the dictionary is a foreignkey or valuetable defined...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Greetz&lt;/P&gt;&lt;P&gt;Sabrina&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Aug 2008 15:51:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv/m-p/3317822#M794768</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-08-25T15:51:37Z</dc:date>
    </item>
  </channel>
</rss>

