Re: About user exits

Former Member · ‎2007 Apr 09

Hi to all,

1.) How to find out that a SAP application consits of a user exit or not.

Is there any standard method .

2.) where to use User exits.

3.) User exits are still used as new technology like BAPI arrived.

Also tell me difference b/w customization,modification,Enhancement .

Thanks .

Regards

Anubhav

Former Member · ‎2007 Apr 09

Hi Anubhav,

Check this info.

User exit - A user exit is a three character code that instructs the system to access a program during system processing.

SXX: S is for standard exits that are delivered by SAP. XX represents the 2-digit exit number.

UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number

Customer exit - The R/3 enhancement concept allows you to add your own functionality to SAP’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.

User Exits : -

__________

1. User exits are routines which SAP allows you to add in additional

customized programs process without affecting the standard SAP programs. SAP

user exits are usually declared as a form routine :-

form userexit_xxxxx

........................

endform.

2. No need to create project in CMOD/SMOD.

3. Won't be automatically transported during version upgrade.

Customer Exits :-

_________________

1. Could be either Function Exits or Menu Exits. SAP will provide certain

FMs which will be called during the execution of SAP transactions.

2.Generally require the developer to create a project in CMOD/SMOD.

3. Will be automatically transported during version upgrade.

Types of Exits

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.

Menu Exits

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.

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’s text when activating the item in an add-on project.

Screen Exits

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’s flow logic.

Function Module Exits

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 pull down 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. 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 ‘001’.

Field Exits

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’s international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.

The field exit concept lets you create a special function module that contains this logic.

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.

In 4.6c, you can use "RSMODPRF" program to create field exits.

An example of a user exits :-

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.

User Exits:

-

User exits allow you to add additional functions to the SAP standard.

Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix USEREXIT. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can include any changes (enhancements) that they want to make to the system. These includes are always processed during program flow.

Advantage: In principle, customers can modify anything they want that is found in the include (tables, structures, and so forth).

Disadvantage: SAP cannot check the individual enhancements themselves which often leads to errors in the enhancement process.

User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a functionmodule. The code for the function module is writeen 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.

Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System.

Customer Exit

-

SAP creates customer exits for specific programs, screens, and menus within standard 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.

If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:

• They do not affect standard SAP source code

When you add new functionality to your SAP System using SAP’s exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAP’s standard software package.

• They do not affect software updates

When you add new functionality to your SAP System using SAP’s exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects’ names ensure that they will not be affected by any changes or new additions to the standard software package.

Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits

User Exits

www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

www.sap-img.com/ab038.htm

www.planetsap.com/userexit_main_page.htm

1. Learn user exits :

http://www.sapgenie.com/links/abap.htm

2. finding user exits :

http://www.sapgenie.com/abap/code/abap26.htm

3. A short tutorial on user exits :

http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

4. Introduction to user exits with examples :

http://www.sap-img.com/abap/what-is-user-exits.htm

5. Difference between BADI and user exits :

http://www.sap-img.com/abap/ difference-between-badi-and-user-exits.htm

FOR EXAMPLE CHECK...

www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

SAP delivers a broad range of business functions within its R/3 application suite. The standard applications may not offer some of the functionality needed. The R/3 enhancement concept allows addition of one’s own functionality to SAP’s standard business applications.

SAP creates user exits for specific programs, screens and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the user exits act as hooks. One can hang his own add-on functionality onto these hooks.

The user exit is a point in a SAP program where a customer’s own program can be called. On upgrade, each user exit must be checked to ensure that it conforms to the standard system.

There are two types of user exit:

• User exits that use INCLUDEs.

These are customer enhancements that are called directly in the program.

• User exits that use tables.

These are used and managed using Customizing.

Purpose of the Enhancement Concept

With the ABAP/4 Development Workbench, SAP’s client-server development environment, one can create add-ons or entire applications. Before the enhancement concept existed, customers who wanted to add their own specific functions to SAP software had to modify the standard SAP programs. Modifying SAP’s software holds at least two dangers:

Modifying standard code can lead to errors

When a customer changes the source code of a standard program, these changes can have unwanted results within other parts of the application. Once a customer has begun ‘reconstructing’ a standard program, SAP can no longer guarantee that this customer’s system will run without serious errors.

Modifications mean more work during software upgrades

Customers of standard software packages often want to take advantage of software upgrades or new releases. Customers who have modified the software of their current release must save these modifications and reenter them into the new software after each upgrade or release change. Depending on the number and scope of modifications, this reentry process may make it difficult or even impossible to take advantage of new software releases.

The enhancement concept offers a better alternative to the problem-ridden modification approach.

Reason for Using Exits :

If you want to extend the functionality of your R/3 System, you should take advantage of the user exits available within the standard R/3 applications. There are two main reasons why you should use exits rather than modifying SAP software. Add-ons that are attached to user exits have the advantage that they:

Do not affect standard SAP source code

When you add new functionality to your R/3 System using SAP’s user exits, you do not change the source code of standard SAP programs. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but they exist apart from SAP’s standard software package.

Do not affect software upgrades

When you add new functions using SAP’s user exits, the objects you develop are customer objects. Customer objects adhere to strict naming conventions. When the time comes to upgrade a software release, the special names of customer objects ensure that they will not be affected by either changes or additions within the standard software package. As a result, you do not need to save and then reenter add-ons attached to user exits.

User exits are not available for all programs and screens within the R/3 standard applications. One can only use exits if they already exist within the SAP R/3 System. Locating Applications that Have Exits explains how to find applications with predefined exits.

If no user exit is available in an area to add a particular functionality, a request can be made to SAP to develop an exit. This request can be made via the Online Service System (OSS).

Navigation

To take advantage of user exits they have to be added to a standard application by SAP. For this reason, it is necessary to know how to locate the exits available within the R/3 System. SAP organizes its user exits in packages that are called SAP enhancements. Each SAP enhancement can contain many individual exits.

From within the ABAP/4 Development Workbench menu choose Utilities ® Enhancements ® Project management. To call up a selection screen that lets one look for the exits available in standard applications, choose Utilities ® SAP enhancements. If no information about the name of specific enhancement packages is available, one can search for all enhancements belonging to a particular development class or to a set of development classes. To list all enhancements in the entire system, the Execute function without specifying any selection criteria is chosen.

LINKS :

http://www.erpgenie.com/sap/abap/code/abap26.htm

http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

http://www.sapgenie.com/abap/code/abap26.htm

http://www.sap-img.com/abap/what-is-user-exits.htm

http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction

http://www.easymarketplace.de/userexit.php

http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

http://www.sappoint.com/abap/userexit.pdfUser-Exit

http://www.sapdevelopment.co.uk/enhance/enhancehome.htm

http://www.sap-img.com/abap/what-is-user-exits.htm

http://www.planetsap.com/userexit_main_page.htm

http://www.erpgenie.com/sap/abap/code/abap26.htm

which gives the list of exits for a tcode

http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm

For information on Exits, check these links

http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

http://www.sapgenie.com/abap/code/abap26.htm

http://www.sap-img.com/abap/what-is-user-exits.htm

http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction

http://www.easymarketplace.de/userexit.php

http://www.sappoint.com/abap/userexit.pdfUser-Exit

http://www.planetsap.com/userexit_main_page.htm

User Exits

http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

http://www.sapgenie.com/abap/code/abap26.htm

http://www.sap-img.com/abap/what-is-user-exits.htm

http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction

http://www.easymarketplace.de/userexit.php

http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

Hope this resolves your query.

Reward all the helpful answers.

Regards

Former Member · ‎2007 Apr 09

Hi Anubhav,

Userxits allow us to add our own functionality to SAP standard program

without modifying it . These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.

All Userexits start with the word USEREXIT_...

FORM USEREXIT_..

z..

ENDFORM.

The problem lies in finding the correct userexit and how to find it if one exists for the purpose. Once the correct userexit is found the necessary

customer code is inserted in the customer include starting with the z..

in the form routine.

e.g. USEREXIT_SAVE_DOCUMENT_PREPARE

Certain application like SD still provide this form of enhancement using userexit but this practice is no longer being followed for newer extensions

instead they are using EXITs which come bundeled in enhancement packages . Neverthiless existing USEREXITS will be supported by SAP an all the newer versions of SAP.

Need to find user exits module-wise? Suppose we want to see the

available sales module user exits. Go to transaction SE81.

Click on SD, then click "edit" on the menu bar and choose select subtree.

Click on "information system," Open Environment node, customer exits, and enhancements.

Press F8 to get all the user exits for that module.

In brief:

SE81->SD->Select subtree->Information System->Envir->Exit Techniques->

Customers exits->enhancements->Execute(F8)

regards,

keerthi

Former Member · ‎2007 Apr 10

hi keerthi,

Thanks for your reply.

You solved my query to some extent.

- I am enhancing the appliction XK01 having enhancement code SAPMF02K.

There is a function Exit available.While double clicking a function module opens and it contains a Include program which starts from Z.....

In that include's change mode we can write our code.

Tell me this is the UserExit or other thing.

- Other query for

FORM USER_Exit

Endform.

Requires Access key.

How to write code there.

Thanks & Regards

Anubhav Gupta

Former Member · ‎2007 Apr 11

hi keerthi,

Thanks for your reply.

You solved my query to some extent.

- I am enhancing the appliction XK01 having enhancement code SAPMF02K.

There is a function Exit available.While double clicking a function module opens and it contains a Include program which starts from Z.....

In that include's change mode we can write our code.

Tell me this is the UserExit or other thing.

- Other query for

FORM USER_Exit

Endform.

Requires Access key.

How to write code there.

Thanks & Regards

Anubhav Gupta

By Category

Related Content

Activity Groups

Industry Groups

Influence and Feedback Groups

Interest Groups

Location Groups

Customer Only Groups

Forums

Related Resources

Products

Learning and Support

About

My SAP Profile

My SAP Profile

About user exits