<?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: USEREXIT in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/userexit/m-p/2525263#M572036</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi sivananda&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are four types User Exits.&lt;/P&gt;&lt;P&gt;1.Menu Exits&lt;/P&gt;&lt;P&gt;2.Screen Exits&lt;/P&gt;&lt;P&gt;3.Function module Exits&lt;/P&gt;&lt;P&gt;4.Field Exits.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;User exits &amp;#150; Simple Example &lt;/P&gt;&lt;P&gt;1. Introduction &lt;/P&gt;&lt;P&gt;User exits (Function module exits) are exits developed by SAP. The exit is implemented as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module. &lt;/P&gt;&lt;P&gt;The naming standard of function modules for function module exits is:  &lt;/P&gt;&lt;P&gt;EXIT_&amp;lt;program name&amp;gt;&amp;lt;3 digit suffix&amp;gt;  &lt;/P&gt;&lt;P&gt;The call to a function module exit is implemented as: &lt;/P&gt;&lt;P&gt;CALL CUSTOMER.-FUNCTION &lt;span class="lia-unicode-emoji" title=":red_heart:"&gt;❤️&lt;/span&gt; digit suffix&amp;gt; &lt;/P&gt;&lt;P&gt;Example: &lt;/P&gt;&lt;P&gt;The program for transaction VA01 Create sales order is SAPMV45A &lt;/P&gt;&lt;P&gt;If you search for CALL CUSTOMER-FUNCTION in program &lt;/P&gt;&lt;P&gt;SAPMV45A you will find (Among other user exits): &lt;/P&gt;&lt;P&gt;CALL CUSTOMER-FUNCTION '003' &lt;/P&gt;&lt;P&gt; exporting &lt;/P&gt;&lt;P&gt;    xvbak   = vbak &lt;/P&gt;&lt;P&gt;    xvbuk   = vbuk &lt;/P&gt;&lt;P&gt;    xkomk   = tkomk &lt;/P&gt;&lt;P&gt; importing &lt;/P&gt;&lt;P&gt;    lvf_subrc = lvf_subrc &lt;/P&gt;&lt;P&gt;  tables &lt;/P&gt;&lt;P&gt;    xvbfa = xvbfa &lt;/P&gt;&lt;P&gt;    xvbap = xvbap &lt;/P&gt;&lt;P&gt;    xvbup = xvbup. &lt;/P&gt;&lt;P&gt;The exit calls function module EXIT_SAPMV45A_003 &lt;/P&gt;&lt;P&gt;2. How to find user exits &lt;/P&gt;&lt;P&gt;Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT &lt;/P&gt;&lt;P&gt;If you know the Exit name, go to transaction CMOD. &lt;/P&gt;&lt;P&gt;Choose menu Utillities-&amp;gt;SAP Enhancements. Enter the exit name and press enter. &lt;/P&gt;&lt;P&gt;You will now come to a screen that shows the function module exits for the exit. &lt;/P&gt;&lt;P&gt;3. Using Project management of SAP Enhancements &lt;/P&gt;&lt;P&gt;We want to create a project to enhance transaction VA01 &lt;/P&gt;&lt;P&gt;- Go to transaction CMOD &lt;/P&gt;&lt;P&gt;- Create a project called ZVA01 &lt;/P&gt;&lt;P&gt;- Choose the Enhancement assign radio button and press the Change button &lt;/P&gt;&lt;P&gt;In the first column enter V45A0002 Predefine sold-to party in sales document. Note that an enhancement can only be used in 1 project. If the enhancement is already in use, and error message will be displayed &lt;/P&gt;&lt;P&gt;Press Save &lt;/P&gt;&lt;P&gt;Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit. &lt;/P&gt;&lt;P&gt;Now the function module is displayed. Double click on include ZXVVAU04 in the function module &lt;/P&gt;&lt;P&gt;Insert the following code into the include: E_KUNNR = '2155'. &lt;/P&gt;&lt;P&gt;Activate the include program. Go back to CMOD and activate the project.  &lt;/P&gt;&lt;P&gt;Go to transaction VA01 and create a sales order.  &lt;/P&gt;&lt;P&gt;Note that Sold-to-party now automatically is "2155"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if its useful reward points&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;senthil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 07 Jul 2007 11:25:48 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-07-07T11:25:48Z</dc:date>
    <item>
      <title>USEREXIT</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/userexit/m-p/2525262#M572035</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;&lt;/P&gt;&lt;P&gt;             How many types of Exits are there? what r they?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;             How to add customer required fields in both Purchase Order header data and in item data? Give me the complete procedure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bye...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 07 Jul 2007 11:18:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/userexit/m-p/2525262#M572035</guid>
      <dc:creator>former_member778253</dc:creator>
      <dc:date>2007-07-07T11:18:55Z</dc:date>
    </item>
    <item>
      <title>Re: USEREXIT</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/userexit/m-p/2525263#M572036</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi sivananda&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are four types User Exits.&lt;/P&gt;&lt;P&gt;1.Menu Exits&lt;/P&gt;&lt;P&gt;2.Screen Exits&lt;/P&gt;&lt;P&gt;3.Function module Exits&lt;/P&gt;&lt;P&gt;4.Field Exits.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;User exits &amp;#150; Simple Example &lt;/P&gt;&lt;P&gt;1. Introduction &lt;/P&gt;&lt;P&gt;User exits (Function module exits) are exits developed by SAP. The exit is implemented as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module. &lt;/P&gt;&lt;P&gt;The naming standard of function modules for function module exits is:  &lt;/P&gt;&lt;P&gt;EXIT_&amp;lt;program name&amp;gt;&amp;lt;3 digit suffix&amp;gt;  &lt;/P&gt;&lt;P&gt;The call to a function module exit is implemented as: &lt;/P&gt;&lt;P&gt;CALL CUSTOMER.-FUNCTION &lt;span class="lia-unicode-emoji" title=":red_heart:"&gt;❤️&lt;/span&gt; digit suffix&amp;gt; &lt;/P&gt;&lt;P&gt;Example: &lt;/P&gt;&lt;P&gt;The program for transaction VA01 Create sales order is SAPMV45A &lt;/P&gt;&lt;P&gt;If you search for CALL CUSTOMER-FUNCTION in program &lt;/P&gt;&lt;P&gt;SAPMV45A you will find (Among other user exits): &lt;/P&gt;&lt;P&gt;CALL CUSTOMER-FUNCTION '003' &lt;/P&gt;&lt;P&gt; exporting &lt;/P&gt;&lt;P&gt;    xvbak   = vbak &lt;/P&gt;&lt;P&gt;    xvbuk   = vbuk &lt;/P&gt;&lt;P&gt;    xkomk   = tkomk &lt;/P&gt;&lt;P&gt; importing &lt;/P&gt;&lt;P&gt;    lvf_subrc = lvf_subrc &lt;/P&gt;&lt;P&gt;  tables &lt;/P&gt;&lt;P&gt;    xvbfa = xvbfa &lt;/P&gt;&lt;P&gt;    xvbap = xvbap &lt;/P&gt;&lt;P&gt;    xvbup = xvbup. &lt;/P&gt;&lt;P&gt;The exit calls function module EXIT_SAPMV45A_003 &lt;/P&gt;&lt;P&gt;2. How to find user exits &lt;/P&gt;&lt;P&gt;Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT &lt;/P&gt;&lt;P&gt;If you know the Exit name, go to transaction CMOD. &lt;/P&gt;&lt;P&gt;Choose menu Utillities-&amp;gt;SAP Enhancements. Enter the exit name and press enter. &lt;/P&gt;&lt;P&gt;You will now come to a screen that shows the function module exits for the exit. &lt;/P&gt;&lt;P&gt;3. Using Project management of SAP Enhancements &lt;/P&gt;&lt;P&gt;We want to create a project to enhance transaction VA01 &lt;/P&gt;&lt;P&gt;- Go to transaction CMOD &lt;/P&gt;&lt;P&gt;- Create a project called ZVA01 &lt;/P&gt;&lt;P&gt;- Choose the Enhancement assign radio button and press the Change button &lt;/P&gt;&lt;P&gt;In the first column enter V45A0002 Predefine sold-to party in sales document. Note that an enhancement can only be used in 1 project. If the enhancement is already in use, and error message will be displayed &lt;/P&gt;&lt;P&gt;Press Save &lt;/P&gt;&lt;P&gt;Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit. &lt;/P&gt;&lt;P&gt;Now the function module is displayed. Double click on include ZXVVAU04 in the function module &lt;/P&gt;&lt;P&gt;Insert the following code into the include: E_KUNNR = '2155'. &lt;/P&gt;&lt;P&gt;Activate the include program. Go back to CMOD and activate the project.  &lt;/P&gt;&lt;P&gt;Go to transaction VA01 and create a sales order.  &lt;/P&gt;&lt;P&gt;Note that Sold-to-party now automatically is "2155"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if its useful reward points&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;senthil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 07 Jul 2007 11:25:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/userexit/m-p/2525263#M572036</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-07T11:25:48Z</dc:date>
    </item>
    <item>
      <title>Re: USEREXIT</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/userexit/m-p/2525264#M572037</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;There are several different types of customer exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Menu Exits&lt;/P&gt;&lt;P&gt;Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu item&amp;#146;s text when activating the item in an add-on project.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Screen Exits&lt;/P&gt;&lt;P&gt;Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screen&amp;#146;s flow logic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Function Module Exits&lt;/P&gt;&lt;P&gt;Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits. When you add a new menu item to a standard pulldown menu, you use a function module exit to define the actions that should take place once your menu is activated. Function module exits also control the data flow between standard programs and screen exit fields.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs. These calls have the following syntax: CALL CUSTOMER-FUNCTION &amp;#145;001&amp;#146;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Difference between user exits &amp;amp; customer exits: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;User exit - A user exit is a three character code that instructs the system to access a program during system processing. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SXX: S is for standard exits that are delivered by SAP.   XX represents the 2-digit exit number. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;UXX: U is for user exits that are defined by the user.  XX represents the 2-digit exit number &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Customer exit - The R/3 enhancement concept allows you to add your own functionality to SAP&amp;#146;s standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.     *-- Mani &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following document is about exits in SAP :- &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The R/3 enhancement concept allows you to add your own functionality to SAP&amp;#146;s standard business applications without having to modify the original applications.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP creates user exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Types of Exits  &lt;/P&gt;&lt;P&gt;There are several different types of user exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Menu Exits &lt;/P&gt;&lt;P&gt;Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu item&amp;#146;s text when activating the item in an add-on project. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Screen Exits &lt;/P&gt;&lt;P&gt;Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screen&amp;#146;s flow logic. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Function Module Exits  &lt;/P&gt;&lt;P&gt;Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These calls have the following syntax:  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL CUSTOMER-FUNCTION &amp;#145;001&amp;#146;. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Field Exits &lt;/P&gt;&lt;P&gt;Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field.  Example: The data element BBBNR identifies a company&amp;#146;s international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The field exit concept lets you create a special function module that contains this logic.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In 4.6c, you can use "RSMODPRF" program to create field exits. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An example of a user exits :- &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;MODULE user_exit_0001 INPUT  
    CASE okcode. 
        WHEN 'BACK OR EXIT'. 
            CASE sy-dynnr. 
                    WHEN '100'. 
                         SET SCREEN 0. 
                         LEAVE SCREEN. 
                    WHEN '200'. 
****************************************************************************** 
**** Note that you can write any code that satisfy your needs.                                                     **** 
**** But in this case, this was wrote as a sample code for reference sake.                                    **** 
**** And you can test it.                                                                                **** 
******************************************************************************  
                         SET SCREEN 100. 
                         LEAVE SCREEN. 
             ENDCASE. 
      ENDCASE.  &lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward all helpfull answers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pavan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 07 Jul 2007 11:27:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/userexit/m-p/2525264#M572037</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-07T11:27:21Z</dc:date>
    </item>
  </channel>
</rss>

