Differnce Between Customer & User Exits

[former_member191391]

Pls tell me

What are various types of exits?

with Regards,

Manmeet singh

[Former Member]

Hi,

There are FUNCTION exits, Screen Exits, Menu Exits and field exits.

Function exits are mostly used . for every application SAP has defined enhancements with some fun modules in it. You have to find the correct related exit for a particular APPLICATION AND TO USE.

Use CMOD for the Project Creation and SMOD Tcodes for Enhancements

In some program there will be user exits with CUSTOMER-FUNCTION defined. you can double click on it and use it.

Regards,

Anji

Message was edited by:

Anji Reddy Vangala

[Former Member]

Hi Manmeet,

Differnce Between Customer & User Exits

In contrast to customer exits, user exits allow developers to access and modify program components and data objects in the standard SAP System. On upgrade, each user exit must be checked to ensure that it conforms to the standard system.

There are the following 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.

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:

-

-

---

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.

Types of Exits.

1)MENU EXITS

2)FUNCTION EXITS

3)TABLE EXITS

4)SCREEN EXITS

5)KEYWORD EXITS

6)FIELD EXITS

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.

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’.

screen exits:

http://help.sap.com/saphelp_erp2005/helpdata/en/94/bef83770798b76e10000009b38f842/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/13/1f2d1a831a43be8a43ecd14170bf1c/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm

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.

Screen exits:

http://help.sap.com/saphelp_erp2005/helpdata/en/94/bef83770798b76e10000009b38f842/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/13/1f2d1a831a43be8a43ecd14170bf1c/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm

Regards,

Priyanka.

[former_member191391]

Tusi Great ho !!!

[former_member194669]

One more Conversion exits.

Conversion exits are triggered between the ABAP and screen. Which means that when value is passed to/from the screen the conversion exit is triggered

aRs