Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

User Exits

Former Member
0 Kudos

Could anyone help me What is this exactly...Plz...Need to know on a very urgent basis...

1 ACCEPTED SOLUTION
5 REPLIES 5

Former Member
0 Kudos

Hi,

Userexits are system modifications. The requirements of the client which can be met with Standard SAP are done with help of routines or userexits.

Userexits are nothing but a provision given by sap to write your own code/logic in the standard program.

Refer

https://forums.sdn.sap.com/click.jspa?searchID=11074347&messageID=1635471

https://forums.sdn.sap.com/click.jspa?searchID=11074347&messageID=2400871

https://forums.sdn.sap.com/click.jspa?searchID=11074464&messageID=2847356

Regards

Kiran

Former Member
0 Kudos

Hi,

User Exits:

The original purpose of user exits was to allow the user to avoid modification adjustment.

 A user exit is considered a modification, since technically objects in the SAP namespace are being modified.

The SAP developer creates a special include in a module pool. These includes contain one or more subroutines routines that satisfy the naming convention userexit_<name>.

&#61656; The calls for these subroutines have already been implemented in the R/3 program.

&#61656; Usually global variables are used.

After delivering them, SAP never alters includes created in this manner; if new user exits must be delivered in a new release, they are placed in a new include program.

User exits are actually empty subroutines that SAP developers provide for you. You can fill them with your own source code.

&#61656; The purpose behind this type of system is to keep all changes well away from program source code and store them in include programs instead.

&#61656; To this end, SAP developers create various includes that fulfill the naming conventions for programs and function groups.

&#61656; The last two letters in the name of the include refer to the include that the customer should use: "Z" is usually found here.

Example: Program SAPM45A

Include M45AFZB

This naming convention guarantees that SAP developers will not touch this include in the future. For this reason, includes of this nature are not adjusted during modification upgrade.

&#61656; The subroutine call is already implemented in the program. The interface is already defined.

&#61656; Normally, subroutines of this type only work with global data.

If any new user exits are delivered by SAP with a new release, then they are bundled into new includes that adhere to the same naming convention.

enhancements

it is used to enhance a sap object without actually modifying the object

customer exits The 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 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. That is already SAP provided some space to write our own functionality that space is nothing but hooks.

If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications.

advantages are

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.

Check out this article.

http://abapprogramming.blogspot.com/2008/03/sap-user-exits.html

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

Regards,

Satish

Former Member
0 Kudos

hi,

User exits : The orginal purpose of userexits was to allow the user to avoid modificationadjustment.

Userexits actually are empty subroutines that SAP developers provide us, you can fill them with our own source code.

User exits are defined that SAP developers creates a special include in a module pool .Includes contain one or more subroutines that satisfy the naming convention userexit _<name>.

Usually global variables are used.

Limitations of userexits :

1. cannot be reusable.

2.can be written only through acesskey.

3.Read and change almostany global data from host program.

Disadvantage :

Very easy to Manipulate erroneously global data.

pls reward if helpful.

Former Member
0 Kudos

Hi

To find User Exits in SAP please follow the steps given below.

1) Run Transaction SE81

2) Select SD

3) From the Menu Click on Edit

4) Select the option ‘Select Subtreee +/-‘

5) From the Menu bar click on Information system

6) From the R/3 Repository information System open the Envir option

7) Select Exit Techniques

😎 Select Customer Exits

9) Double click on Enhancements

10) Press F8

Reward If Helpfull,

Naresh.