topic Re: user exits in Application Development and Automation Discussions

user exits

Former Member — Wed, 09 Jan 2008 14:47:00 GMT

what is user exit and can any one provide me a user exit for mm and how to assign them to user profile

please give the steps

Re: user exits

Former Member — Wed, 09 Jan 2008 14:53:18 GMT

Hi,

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>

2. How to find user exits?

Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT

If you know the Exit name, go to transaction CMOD.

Choose menu Utillities->SAP Enhancements. Enter the exit name and press enter.

You will now come to a screen that shows the function module exits for the exit.

What is the use of user-exit and all?

Is it about modifying SAP program?

Suppose that you need some functionality which is not provided in sap what do you do. Sap has provided you with three options.

1) Customizing.

2) Modifications.

3) User Exits.

So what are these three in the first case when you take Customization is nothing but you are customizing SAP according to your need and requirement for example you want the Purchase Order Numbers to start with <Co_Name><seq_no>(sequential no) this kind of stuff is done in customization.

Modification is nothing but you are modifying SAP std code which is written during developing your SAP std programms or screens.

Thirdly to avoid modifications SAP has provide you with some exit points like for example after the PBO event in module pool programming comes the PAI. so in between these two events you wanted the change something so SAP has provided with an exit point. that exit point is called user exits. for example user exits for me21 PO Create is MM06005 if I am not wrong. they are nothing but simple function module within which you write your code which functions just like normal program and executes between the PAI and PBO events.

thanks and regards

suma sailaja

Re: user exits

Former Member — Wed, 09 Jan 2008 14:54:48 GMT

A user exit is a way of modifyinf standard SAP code. It is simply a piece of code inserted into a SAP program by the original author. This code takes the format of a function module CALL CUSTOMER-FUNCTION 'nnn'. Parameters are passed and returned. You can program changes in this function module and they will not be lost when upgrades/patches etc are applied becaue the call will always be present.

What do you want to achieve in MM? You would need to find a suitable customer exit for whatever it is.

Re: user exits

Former Member — Wed, 09 Jan 2008 14:56:47 GMT

Hi,

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

TO FIND USER EXITS:

Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT

If you know the Exit name, go to transaction CMOD.

Choose menu Utillities->SAP Enhancements. Enter the exit name and press enter.

You will now come to a screen that shows the function module exits for the exit.

Hope it will be helpful

Reward points if helpful

thanks,

swaroop

Re: user exits

Former Member — Wed, 09 Jan 2008 14:58:50 GMT

hi Jas,

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>

The following link might be useful..

[http://sapmmforum.blogspot.com/2007/10/user-exits-in-mm-area.html]

Reward if useful.

THankyou,

Regards.

Re: user exits

Former Member — Wed, 09 Jan 2008 14:59:55 GMT

hi,

To find a Exit.

Goto Transaction -- Find The Package

SMOD ~~>f4~~>Use the Package here to Find the Exits In the Package.

Suppose you need to find out all the user exits related to a tcode.

1. Execute the Tcode.

2. Open the SAP program.

3. Get the Development Class.

4. Execute Tcode SE84.

5. Open the Node 'Envir. -> Exit Techniques -> 'Customer Exits -> Enhancements'

6. Enter the Development class and execute.

The following SAP enhancements are available for the Purchasing area:

AMPL0001 - User subscreen for additional AMPL data (manufacturer part number)

LMELA002 - Adoption of batch number from shipping notification at time of posting of a goods receipt

LMELA010 - Incoming shipping notification: adoption of item data from IDoc

LMEQR001 - User exit for source determination

M06B0001 - Role determination for release of requisitions

M06B0001 - Changes to communication structure for release of requisitions

M06B0003 - Number range and document number

M06B0004 - Number range and document number

M06B0005 - Changes to communication structure for overall release of purchase requisitions

M06E0004 - Changes to communication structure for release of purchasing document

M06E0005 - Role determination for release of purchasing documents

ME590001 - Grouping of requisitions for PO split in transaction ME59

MEETA001 - Determination of schedule line type (backlog, immediate requirement, forecast)

MEFLD004 - Determination of earliest delivery date for checking at time of goods receipt (PO only)

MELAB001 - Generation of forecast delivery schedule: realization via creation profile

MEQUERY1 - Enhancement for document overview ME21N / ME51N

MEVME001 - Calculation of default GR quantity and over/underdelivery tolerances

MM06E001 - User exits for inbound EDI messages and outbound purchasing documents

MM06E003 - Number range and document number

MM06E004 - Control of import data screens in purchase orders

MM06E005 - Customer fields in purchasing documents

MEREQ001 - Customer's own data in purchase requisitions

MM06E007 - Change document for requisitions when converting into POs

MM06E008 - Monitoring of contract target value in case of release orders

MM06E009 - Relevant texts for "Texts exist" indicator

MM06E010 - Field selection for vendor address

MM06E011 - Activation of requisition block

MM06L001 - Exits for determination of ratings in vendor evaluation

MMAL0001 - ALE source list distribution: outbound processing

MMAL0002 - ALE source list distribution: inbound processing

MMAL0003 - ALE purchasing info record distribution: outbound processing

MMAL0004 - ALE purchasing info record distribution: inbound processing

MMDA0001 - Default values for delivery addresses

MMFAB001 - User exit for generation of releases

MRFLB001 - Control items during release creation

LWBON001 - Enhancement of LIS update through extension of the communication structure MCKONA (business volumes and rebate income)

LWBON003 - Change settlement data for end-of-period rebate settlement before creation of settlement documents

LWSUS001 - Customer-specific source determination in Retail

LMEXF001 - Conditions in purchasing documents without invoice receipt

LMEKO002 - Enhance communication structure KOMP for price determination

REWARD IF USEFUL

thanks and regards

suma sailaja