<?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: EXIT in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/exit/m-p/2556630#M582730</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ashok,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  According to note: 165635 - Documentation: Enhancement LMR1M001 (MM-IV)&lt;/P&gt;&lt;P&gt;this enhacement is obsolete:&lt;/P&gt;&lt;P&gt;"(...) Functions &lt;/P&gt;&lt;P&gt;In the header screen (screen SAPLMR1M 0400) you can define a customer-specific subscreen.With this customer-specific function module you can determine the default values for the subscreen.&lt;/P&gt;&lt;P&gt;As the basis, the fields of structure RBKPV (header data) are available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Remark&lt;/P&gt;&lt;P&gt;As of Release 4.6C, Transaction MR1M is no longer supported. Thus this customer exit and its functions are also obsolete.(...)"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Additional information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To use screen exit pls refer the below link:&lt;/P&gt;&lt;P&gt;&lt;A href="http://wiki.ittoolbox.com/index.php/Implement_a_screen_exit_to_a_standard_SAP_transaction" target="test_blank"&gt;http://wiki.ittoolbox.com/index.php/Implement_a_screen_exit_to_a_standard_SAP_transaction&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To resolve this issue :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So use Badi Invoice_Update and call FM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not sure if method CHANGE_BEFORE_UPDATE is the right one because it does contain neither an "error flag" parameter nor an exception.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assume that method CHANGE_AT_SAVE will be more useful to you because it has an exception (ERROR_WITH_MESSAGE) that you can raise.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also use the METHOD CHANGE_BEFORE_UPDATE or CHANGE_IN_UPDATE..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Which will be called when saving the invoice..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;like Update the structure MRMRBTX of the paramter TI_MRMRBTX in the method&lt;/P&gt;&lt;P&gt;CHANGE_IN_UPDATE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward pts if found usefull :)&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Sathish &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 09 Jul 2007 11:10:48 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-07-09T11:10:48Z</dc:date>
    <item>
      <title>EXIT</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/exit/m-p/2556629#M582729</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;I AM CREATING A EXIT FOR MIRO . IN Enhancements LMR1M001 I AM CREATING ONE SCREEN 400. IN 400 I AM DISPLAYING SOME SCREEN FIELD . NOW IN 6000 (INITIAL SCREEN IN MIRO ) WHENEVE I AM ENTERING &lt;/P&gt;&lt;P&gt;SOME BLDAT LIKE 09.07.2007 THIS SCREEN MUST TRIGGER . SO IN PBO I WROTE LIKE THIS WAY&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: BLDAT LIKE INVFO-BLDAT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MODULE CHECK_BLDAT OUTPUT.&lt;/P&gt;&lt;P&gt;BREAK-POINT.&lt;/P&gt;&lt;P&gt;IF BLDAT = '09.07.2007'.&lt;/P&gt;&lt;P&gt;CALL SCREEN 400.&lt;/P&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ENDMODULE. " CHECK_BLDAT OUTPUT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IN PAI&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MODULE USER_COMMAND_0400 INPUT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CASE OK_CODE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WHEN 'BACK'.&lt;/P&gt;&lt;P&gt;LEAVE PROGRAM .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ENDCASE.&lt;/P&gt;&lt;P&gt;ENDMODULE. " USER_COMMAND_0400 INPUT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BUT AM NOT GETING ANY THING. PLEASE CORRECT IT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;THANK YOU&lt;/P&gt;&lt;P&gt;ASHOK KUMAR&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jul 2007 07:49:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/exit/m-p/2556629#M582729</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-09T07:49:18Z</dc:date>
    </item>
    <item>
      <title>Re: EXIT</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/exit/m-p/2556630#M582730</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ashok,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  According to note: 165635 - Documentation: Enhancement LMR1M001 (MM-IV)&lt;/P&gt;&lt;P&gt;this enhacement is obsolete:&lt;/P&gt;&lt;P&gt;"(...) Functions &lt;/P&gt;&lt;P&gt;In the header screen (screen SAPLMR1M 0400) you can define a customer-specific subscreen.With this customer-specific function module you can determine the default values for the subscreen.&lt;/P&gt;&lt;P&gt;As the basis, the fields of structure RBKPV (header data) are available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Remark&lt;/P&gt;&lt;P&gt;As of Release 4.6C, Transaction MR1M is no longer supported. Thus this customer exit and its functions are also obsolete.(...)"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Additional information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To use screen exit pls refer the below link:&lt;/P&gt;&lt;P&gt;&lt;A href="http://wiki.ittoolbox.com/index.php/Implement_a_screen_exit_to_a_standard_SAP_transaction" target="test_blank"&gt;http://wiki.ittoolbox.com/index.php/Implement_a_screen_exit_to_a_standard_SAP_transaction&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To resolve this issue :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So use Badi Invoice_Update and call FM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not sure if method CHANGE_BEFORE_UPDATE is the right one because it does contain neither an "error flag" parameter nor an exception.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assume that method CHANGE_AT_SAVE will be more useful to you because it has an exception (ERROR_WITH_MESSAGE) that you can raise.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also use the METHOD CHANGE_BEFORE_UPDATE or CHANGE_IN_UPDATE..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Which will be called when saving the invoice..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;like Update the structure MRMRBTX of the paramter TI_MRMRBTX in the method&lt;/P&gt;&lt;P&gt;CHANGE_IN_UPDATE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward pts if found usefull :)&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Sathish &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jul 2007 11:10:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/exit/m-p/2556630#M582730</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-09T11:10:48Z</dc:date>
    </item>
  </channel>
</rss>

