<?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: customer exits in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/customer-exits/m-p/1347950#M175040</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi swaminathan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EXITS : they are for the purpose&lt;/P&gt;&lt;P&gt;of calling customer abap code,&lt;/P&gt;&lt;P&gt;from standard transaction,&lt;/P&gt;&lt;P&gt;at specific points (eg. while showing &lt;/P&gt;&lt;P&gt;default values on screen, while saving,&lt;/P&gt;&lt;P&gt;while validations, etc)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Previously there were only user-exits.&lt;/P&gt;&lt;P&gt;2. Then came the concept of customer-exits.&lt;/P&gt;&lt;P&gt;3.&lt;/P&gt;&lt;P&gt;user exits were nothing but&lt;/P&gt;&lt;P&gt;subroutines&lt;/P&gt;&lt;P&gt;FORM/PERFORM&lt;/P&gt;&lt;P&gt;called from standard programs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. The FORM defintion was placed inside&lt;/P&gt;&lt;P&gt;an empty include file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5. So It was called EVERYTIME.&lt;/P&gt;&lt;P&gt;and we need to MODIFY/REPAIR the&lt;/P&gt;&lt;P&gt;standard include .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;6. Then it came with concept of customer-exit&lt;/P&gt;&lt;P&gt;7. It consists of calling a FUNCTION MODULE,&lt;/P&gt;&lt;P&gt;which is called only if &lt;/P&gt;&lt;P&gt;the user-exit is ACTIVATED (other wise not called)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this case, the code in put inside&lt;/P&gt;&lt;P&gt;a pre-defined Z include.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*----&lt;/P&gt;&lt;HR originaltext="----------------------------" /&gt;&lt;P&gt;8. Functionality of both is same, howerver&lt;/P&gt;&lt;P&gt;we can note the following important differences&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a) Customer exit is called only if activated.&lt;/P&gt;&lt;P&gt;(hence, it does not waste resources)&lt;/P&gt;&lt;P&gt;b) in customer exit, REPAIR does not happen&lt;/P&gt;&lt;P&gt;to the standard include.&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;amit m.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 29 May 2006 06:55:58 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-05-29T06:55:58Z</dc:date>
    <item>
      <title>customer exits</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/customer-exits/m-p/1347948#M175038</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what are customer exits ?&lt;/P&gt;&lt;P&gt;thanks in advance...&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;b.s&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 May 2006 06:52:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/customer-exits/m-p/1347948#M175038</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-05-29T06:52:24Z</dc:date>
    </item>
    <item>
      <title>Re: customer exits</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/customer-exits/m-p/1347949#M175039</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;Check this....&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Vijay&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 May 2006 06:55:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/customer-exits/m-p/1347949#M175039</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-05-29T06:55:49Z</dc:date>
    </item>
    <item>
      <title>Re: customer exits</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/customer-exits/m-p/1347950#M175040</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi swaminathan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EXITS : they are for the purpose&lt;/P&gt;&lt;P&gt;of calling customer abap code,&lt;/P&gt;&lt;P&gt;from standard transaction,&lt;/P&gt;&lt;P&gt;at specific points (eg. while showing &lt;/P&gt;&lt;P&gt;default values on screen, while saving,&lt;/P&gt;&lt;P&gt;while validations, etc)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Previously there were only user-exits.&lt;/P&gt;&lt;P&gt;2. Then came the concept of customer-exits.&lt;/P&gt;&lt;P&gt;3.&lt;/P&gt;&lt;P&gt;user exits were nothing but&lt;/P&gt;&lt;P&gt;subroutines&lt;/P&gt;&lt;P&gt;FORM/PERFORM&lt;/P&gt;&lt;P&gt;called from standard programs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. The FORM defintion was placed inside&lt;/P&gt;&lt;P&gt;an empty include file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5. So It was called EVERYTIME.&lt;/P&gt;&lt;P&gt;and we need to MODIFY/REPAIR the&lt;/P&gt;&lt;P&gt;standard include .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;6. Then it came with concept of customer-exit&lt;/P&gt;&lt;P&gt;7. It consists of calling a FUNCTION MODULE,&lt;/P&gt;&lt;P&gt;which is called only if &lt;/P&gt;&lt;P&gt;the user-exit is ACTIVATED (other wise not called)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this case, the code in put inside&lt;/P&gt;&lt;P&gt;a pre-defined Z include.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*----&lt;/P&gt;&lt;HR originaltext="----------------------------" /&gt;&lt;P&gt;8. Functionality of both is same, howerver&lt;/P&gt;&lt;P&gt;we can note the following important differences&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a) Customer exit is called only if activated.&lt;/P&gt;&lt;P&gt;(hence, it does not waste resources)&lt;/P&gt;&lt;P&gt;b) in customer exit, REPAIR does not happen&lt;/P&gt;&lt;P&gt;to the standard include.&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;amit m.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 May 2006 06:55:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/customer-exits/m-p/1347950#M175040</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-05-29T06:55:58Z</dc:date>
    </item>
    <item>
      <title>Re: customer exits</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/customer-exits/m-p/1347951#M175041</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Customer exits are provided to the customer in the form of Function Module which holds the include in the customer namespace.The user can add his/her own source code in it.This is technically an enhancement.Eg for customer exits are Function module exits,Menu Exits,Screen Exits.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rgds,&lt;/P&gt;&lt;P&gt;latheesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 May 2006 07:10:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/customer-exits/m-p/1347951#M175041</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-05-29T07:10:32Z</dc:date>
    </item>
    <item>
      <title>Re: customer exits</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/customer-exits/m-p/1347952#M175042</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Swaminathan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.CUSTOMER EXITS are FUNCTIONS so they are called using CALL FUNCTION (or more exactly CALL CUSTOMER FUNCTION).&lt;/P&gt;&lt;P&gt;Inside a function (customer exit) you can only acces your import/export/changing/tables parameters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.There are more restrictions on customer exits  but you are sure it will never lead to inconsistency even if  you  make changes to any parameters &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3.In customer-exit we have function-module exit , screen exit , menu exit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4.Are available for MM,SD,FI,HR&amp;#133;..i.e  designed for all modules.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5.Here in case of customer exits there is no need of access key.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;6.During any upgradation Customer-exits are not wiped out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;Pawan P. Khilari&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;*Mark Useful Answers&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 May 2006 07:32:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/customer-exits/m-p/1347952#M175042</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-05-29T07:32:38Z</dc:date>
    </item>
  </channel>
</rss>

