Difference between User Exit and Routine

1 .Routines are the Piece of code which we write to get some xtra functionality for the
Std business transactions See the Tcode VOFM, we write different types of routines here,
check them.

Subroutines are the piece of code which we write for the Reusability of code shape of the
code is PERFORM..<name> Using/changing/tables.... FORM...<code> ENDFORM.
Function modules are the flobal programs which are provided by SAP for the Reusability.

see the doc

Function Modules;

Check this matter.

Function Modules are Global ABAP programs created by SAP for reusable purpose.they
have IMPORT,EXPORT and TABLE parameters, and EXCEPTIONS to through when error
occurs You can create them from TCode SE37.

Go through the following doc:

Function modules are cross-program, reusable procedures that are organized into
function groups, and whose functions are implemented between the statements
FUNCTION and ENDFUNCTION. Function modules and their interfaces are created in the
Function Builder.

Function Module Interfaces

The parameter interface of a function module is defined in the Function Builder. It

includes the definition of interface parameters and the specification of exceptions that
can be triggered by a function module. The Function Builder automatically generates
comment lines below the FUNCTION statement in the source code of the function module

Routines are the Piece of code which we write to get some xtra functionality for the Std
business transactions See the Tcode VOFM, we write different types of routines here,
check them.

Subroutines are the piece of code which we write for the Resusability of code

shape of the code is PERFORM..<name> Using/changing/tables....

FORM...<code> ENDFORM.

Function modules are the flobal programs which are provided by SAP for the Reusability.

see the doc

Function Modules;

Check this matter.

Function Modules are Global ABAP programs created by SAP for reusable purpose.they
have IMPORT,EXPORT and TABLE parameters, and EXCEPTIONS to through when error
occurs

2 .User exit is a place where we can write our own logic inside SAP programs. Instead of
modification of SAP code, we can place our custom logic in User Exit.

There are three types of User exits:

1. Function Exits

2. Menu Exits

3. User Exits

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.

u can use the exits for enhancement of sap functionalities.

there are also screen exits and customer exits

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

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 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 sub screen
from the standard screen 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
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.

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

User exits are used in an extraction if the standard SAP extractors do not provide the
expected data or the required functionality, for instance in authorizations or time
checks. User exits are commonly used in Sales and Distribution (SD) modules. There
are many exits provided by SAP in the areas of sales, transportation, shipping and
billing. A user exit is designed to make some changes when standard SAP is not capable
of fulfilling all the requirements.
To be able to access what exits are available in each area of sales, go to IMG using this
path: IMG → Sales and Distribution → System Modifications → User Exits. The
documentation for each exit in the areas of SD is explained thoroughly.