topic Re: Regarding user exits in Application Development and Automation Discussions

Regarding user exits

Former Member — Thu, 07 Feb 2008 07:50:26 GMT

What is the difference b/w user exit and customer exit

Re: Regarding user exits

Former Member — Thu, 07 Feb 2008 07:52:51 GMT

USER EXITS

1. Introduction:

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.

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>

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

CUSTOMER EXITS

t-code CMOD.

As of Release 4.6A SAP provides a new enhancement technique, the Business Add-Ins.

Among others, this enhancement technique has the advantage of

being based on a multi-level system landscape (SAP, country versions, IS solutions, partner,

customer, and so on)

instead of a two-level landscape (SAP, customer) as with the customer exits.

You can create definitions and implementations of business add-ins at any level of the system landscape.

To unify enhancements of the SAP Standard you can migrate customer exits to business add-ins.

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

*****************

In order to find out the user exits for any tcode,

1. get the developement class of the tcode from SE93.

2. Now goto transaction SMOD and press F4,

3. give in the Deve class in the dev class and Press ENTER

this will show u the exits for any tcode.

or execute this report

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.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

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

Look at the below link, it will solve your Prblem

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

the following links give u a clear picture abt customer & user exits

This will surely help:

Reward points if useful.

Re: Regarding user exits

Former Member — Thu, 07 Feb 2008 07:55:05 GMT

User exits are dirrectly attached with the standard code. The approach is as normal subroutine. You need accesskey to code in those exits. But when the upgrade happens then these exits are not overwritten. Ex: MV45AFZZ

Customer exits are maintained far from code. You do not need access keys. These are created as functional module and created in CMOD & SMOD. AS they are created far from the source they are easy to manage.

Re: Regarding user exits

Former Member — Thu, 07 Feb 2008 07:55:57 GMT

User Exit:

When you work with global variables, you need to specify a replacement type to determine how the variable should be replace with a value. In most cases, the replacement types provided by the system (automatic, manual, SAP exit, fixed value from table) will be sufficient.

If you need to have a variable replace using a different method, you can program a user exit for global variables to define your own replacement type.

Deriving the current calendar year from the current fiscal year

Deriving a 7-digit period from the current period

You can read about the user exit by choosing Tools ® ABAP Workbench ® Utilities ® Enhancements ® Definition (enhancement KKDR0001) from the initial screen. There you will find the technical information necessary for programming an exit as well as a code example.

See this link

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

Customer Exit:

Use:

If you want to process a variable using a processing type other than Manual Entry/Default Value, Replacement Path, SAP Exit, or Authorization, you can use Customer Exit to set up a customized processing type for variables to suit your specific needs.

The customer exit is designed as an enhancement that you can configure with customer-specific logic. For detailed, general information about customer exits and their use, see the Enhancements to the Standard section of the BC Changes to the SAP Standard documentation.

See this link

http://help.sap.com/saphelp_nw04s/helpdata/en/f1/0a56f5e09411d2acb90000e829fbfe/frameset.htm

Reward Points if useful.

Re: Regarding user exits

Former Member — Thu, 07 Feb 2008 08:00:42 GMT

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. *-- Mani

The following document is about exits in SAP :-

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 user 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 are FORMS and are called by SAP standard programs

using PERFORM.

CUSTOMER EXITS are FUNCTIONS so they are called using CALL

FUNCTION (or more exactly CALL CUSTOMER FUNCTION).

Inside the form (user exit) you can read and change almost

any global data from host program.

Inside a function (customer exit) you can only acces your

import/export/changing/tables parameters.

User exits are more flexible because you have more

information to use in your code but on the other hand , it

is very easy to manipulate erroneously global data and lead

the standard program to a dump or even to make database

inconsistent.

Customer exits are more restrictive but you are sure any

change you can make to any parameters will never lead to

inconsistency

User-exit doesnâ€™t have any classification.

In customer-exit we have function-module exit , screen exit

, menu exit.

User exits are Basically designed For SD module.

Costomer exits Are available for MM,SD,FI,HRâ€¦..Basically

designed for all modules.

USER EXITS

In computer software, a user exit is a place in a software program where a customer can arrange for their own tailor-made program to be called.

In the R/3 system from SAP, a user exit is contrasted with a customer exit and allows a customer's developer to access program components and data objects within the R/3 system. In R/3, some user exits use Include statements to include customer program enhancements that are called from the program.

Other user exits use tables that are accessed through customization.

Overview

Extension of SAP functionality

SAP makes different possibilities available to extend SAP functionality in the R/3 without modifying the delivered R/3-Standard. Thus these extensions are further present also after a R/3-Release-Wechsel.

• User exit

• Field exit

• Text extensions

• Customer exit

• Table extensions

1. User exit

User exits are original one in the selling module (SD) developed expandability.

They consist of empty subroutines (FORM) in special Includes, which can be filled by a ABAP Use developer.

In special places in the SA P-CODE such subroutine references were inserted by SAP. An extension is thus only possible, where SAP planned it.

They usually offer a rather rudimentary expandability, since purely technically objects in the SAP name area are modified.

2. Field exit

Field exits are bypasses of a Dynprofield with data element purchase into a functional module. These will go through when leaving the Dynpros. There are global and local field exits.

Global field exits

are not limited to a Dynpro. If a data element is used on several Dynpros, after activation of the field exit with all this Dynpros to a functional module one branches out.

Local one field exit

work only on a Dynpro limited. There is the possibility of putting on bus to 36 local field exits to a data element.

3. Text extensions

With text extensions it acts around user keywords and user documentation (F1-Hilfe) to data elements. The new keywords can refer to SAP documentation and to user documentation. Thus one has also the possibility of overwriting the keywords delivered by SAP.

With text extensions the changes are global effective for all SAP applications concerned contrary to application extensions after activation.

4. Customer exit

An application function can be extended by application extensions by the customer. Customer exits must be intended by SAP. They consist generally of several components. The interface SAP/Kunde is clearly defined.

With a R/3-Release-Wechsel and/or. Upgrade remain the customer extensions without effort.

• Function exit

• Menu exit

• Dynpro exit

A) Function exit

By functional module exits the customer can implement additional logic in an application function.

SAP built such exits in different places into many application functions. Thus are the interfaces are already given, and/or which data handed over.

These functional modules can be filled now by the customer. It can insert also user Dynpros with associated processing logic and GUI surface and put on user text elements.

B) Menu exit

Menu exits make it for the customer possible to build and occupy with a function code in an SAP application new menu entries.

SAP determined, where in the program additional function codes are queried and like to it is being reacted, either by a functional module exit or by an already firmly given functionality.

C) Dynpro exit

Dynpro exits permit the customer to arrange ranges of a dynpros reserved by SAP. Within these ranges large information can be indicated or data be seized. Those for this force fields by the customer on a user Dynpro are arranged.

In Details

What is User Exits?

The following document is about exits in SAP: -

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

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

Reward Points if found helpfull..

Cheers,

Chandra Sekhar.

Re: Regarding user exits

soumya_jose3 — Thu, 07 Feb 2008 08:24:11 GMT

Hi,

customer exits are provided to the customer in the form of function module which holds the include in the customer namespace. the user can add own source code in it. this is an enhancement. This doesnot affect sap std source code.

user exits are empty sub routines that the sap provides . you can fill it with your own source code. this is a modification. this affect the source code.

user exits means there is need of access key, as we are going to modify the sap std. code. whereas customer exits don't need access keys.

Eg: go to any sap std. pgm.Go to edit menu->find next->find for call cutomer-function. you can see different call customer-functions ...these are customer exits.

in some pgms u can see perform userexit_.....these are user exits.

Regards,

Soumya.