<?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: Modification using User Exit... in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/modification-using-user-exit/m-p/3200003#M762664</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 am unsure if this program is active for MM - I have only used it from SD. &lt;/P&gt;&lt;P&gt;You need to use the existing forms to manipulate data - I have used   FORM USEREXIT_XKOMV_BEWERTEN_END to manipulate the xkomv structure.&lt;/P&gt;&lt;P&gt;I am quite sure you can not disable the save button here, but it should be possible to check for SY-UCOMM = 'SICH' to identify that save was pressed and issue a message with E - disallowing saving ( when specific conditions are fulfilled )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Ole&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 07 Dec 2007 12:55:20 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-12-07T12:55:20Z</dc:date>
    <item>
      <title>Modification using User Exit...</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/modification-using-user-exit/m-p/3200001#M762662</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 am using an User exit RV61AFZB in the Transaction ME21N..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now the requirment is , the "SAVE" button should be Disabled at some condition. (For example if the price is Greater than 500) .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So..Please let me know how to Disable the button..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank u.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Dec 2007 11:47:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/modification-using-user-exit/m-p/3200001#M762662</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-07T11:47:16Z</dc:date>
    </item>
    <item>
      <title>Re: Modification using User Exit...</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/modification-using-user-exit/m-p/3200002#M762663</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi!!!!!!!!!!1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;any business transaction, triggers a BADI on clicking some button on the application toolbar. You can read the fcode of that button in the relavant badi, and instead of disabling it, give user an error msg that "this functionality is diabaled". This is the alternate way if your business scenario allows this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;other way u do need a access key, contact ur basis team to obtain an access key, once u r done with that u need to write the condition 4 enabling n disabling.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward if useful...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Dec 2007 12:50:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/modification-using-user-exit/m-p/3200002#M762663</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-07T12:50:19Z</dc:date>
    </item>
    <item>
      <title>Re: Modification using User Exit...</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/modification-using-user-exit/m-p/3200003#M762664</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 am unsure if this program is active for MM - I have only used it from SD. &lt;/P&gt;&lt;P&gt;You need to use the existing forms to manipulate data - I have used   FORM USEREXIT_XKOMV_BEWERTEN_END to manipulate the xkomv structure.&lt;/P&gt;&lt;P&gt;I am quite sure you can not disable the save button here, but it should be possible to check for SY-UCOMM = 'SICH' to identify that save was pressed and issue a message with E - disallowing saving ( when specific conditions are fulfilled )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Ole&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Dec 2007 12:55:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/modification-using-user-exit/m-p/3200003#M762664</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-07T12:55:20Z</dc:date>
    </item>
  </channel>
</rss>

