user exit

[Former Member]

whats the mean of user exit? could u plzz tell?

[Former Member]

Hi Sonyia,

look here: http://help.sap.com/

Regards, Dieter

Reward points if usefull

[Former Member]

User Exit is the SAP provided enhancements to the standard version of the system. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery.

Consider SAP standard functionality of increamenting the counter is by 1.

but by your requirement it need to be incremented by 2. SAP would have provided a space for writing your own code to accomdate your requirement.

Pls note of CMOD & SMOD transaction

[Former Member]

Hi Soniya,

Looks like u wanna learn the whole subject at a single go. It is good but do try to analyse all the doubts practically.

I will provide u the answer surely. Do remember to reward with healthy poinrs.

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.

The naming standard of function modules for functionmodule exits is:

EXIT_<program name><3 digit suffix>

The call to a functionmodule exit is implemented as:

CALL CUSTOMER.-FUNCTION ❤️ digit suffix>

Example:

The program for transaction VA01 Create salesorder is SAPMV45A

If you search for CALL CUSTOMER-FUNCTION i program

SAPMV45A you will find ( Among other user exits):

CALL CUSTOMER-FUNCTION '003'

exporting

xvbak = vbak

xvbuk = vbuk

xkomk = tkomk

importing

lvf_subrc = lvf_subrc

tables

xvbfa = xvbfa

xvbap = xvbap

xvbup = xvbup.

The exit calls function module EXIT_SAPMV45A_003

Hope this will surely help you.

Reward all the helpful answers.

Regards.

[Former Member]

Hi Soniya,

User exits are used when the flow for a aprticular transaction has to take some other route other then the normal flow. this can be the case when you have to attach some additional functionality lik u need a customised screen, or new functionality (using a functional module). based on these things user exits can be classified as screen exits, function module exits, field exits( not used anymore). hope this gives some help on userexits.

regards,

Chaitanya

[Former Member]

Hi Soniya,

Do u think the info provided is not helpful.

If required revert back soon.

Regards

[Former Member]

Hi...

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.

Customer exits are implemented in Z-includes and are ENHANCEMENTS to the system.

User-exits were firstly intended to be developed for the SD module. You make your coding in includes in SAP namespace (e.g MV*). That's why, user exits are MODIFICATIONS to the system. In includes for user exits there are empty subroutines ( generally with the name convention "userexit_...") and you code using global variables of the main program.

But, generally developers use these terms without this distinction. So, someone may mean a "customer exit" when (s)he says "user exit" or vice-versa.

Regards,

Vivekananda Varma Dandu