User exits

[Former Member]

Name atleast 10 user exits you have developed in your project?

[Former Member · Accepted solution]

Hi Gopala,

User exits in the SD orders. These are program names (SE38):

MV45ATZZ

For entering metadata for sales document processing. User-specific

metadata must start with "ZZ".

MV45AOZZ

For entering additional installation-specific modules for sales

document processing which are called up by the screen and run under

PBO (Process Before Output) prior to output of the screen. The

modules must start with "ZZ".

MV45AIZZ

For entering additional installation-specific modules for sales

document processing. These are called up by the screen and run under

PAI (Process after Input) after data input (for example, data

validation). The User exits in the SD orders. These are program names (SE38):

MV45ATZZ

For entering metadata for sales document processing. User-specific

metadata must start with "ZZ".

MV45AOZZ

For entering additional installation-specific modules for sales

document processing which are called up by the screen and run under

PBO (Process before Output) prior to output of the screen. The

modules must start with "ZZ".

MV45AIZZ

For entering additional installation-specific modules for sales

document processing. These are called up by the screen and run under

PAI (Process after Input) after data input (for example, data

validation). The modules must start with "ZZ".

MV45AFZZ and MV45EFZ1

for entering installation-specific FORM routines and for using user

exits, which may be required and can be used if necessary. These

program components are called up by the modules in MV45AOZZ or

MV45AIZZ. e modules must start with "ZZ".

MV45AFZZ and MV45EFZ1

for entering installation-specific FORM routines and for using user

exits, which may be required and can be used if necessary. These

program components are called up by the modules in MV45AOZZ or

MV45AIZZ.

Please Reward If Really Helpful,

Thanks and Regards,

Sateesh.Kandula

[Former Member]

Hi Gopala,

User exits in the SD orders. These are program names (SE38):

MV45ATZZ

For entering metadata for sales document processing. User-specific

metadata must start with "ZZ".

MV45AOZZ

For entering additional installation-specific modules for sales

document processing which are called up by the screen and run under

PBO (Process Before Output) prior to output of the screen. The

modules must start with "ZZ".

MV45AIZZ

For entering additional installation-specific modules for sales

document processing. These are called up by the screen and run under

PAI (Process after Input) after data input (for example, data

validation). The User exits in the SD orders. These are program names (SE38):

MV45ATZZ

For entering metadata for sales document processing. User-specific

metadata must start with "ZZ".

MV45AOZZ

For entering additional installation-specific modules for sales

document processing which are called up by the screen and run under

PBO (Process before Output) prior to output of the screen. The

modules must start with "ZZ".

MV45AIZZ

For entering additional installation-specific modules for sales

document processing. These are called up by the screen and run under

PAI (Process after Input) after data input (for example, data

validation). The modules must start with "ZZ".

MV45AFZZ and MV45EFZ1

for entering installation-specific FORM routines and for using user

exits, which may be required and can be used if necessary. These

program components are called up by the modules in MV45AOZZ or

MV45AIZZ. e modules must start with "ZZ".

MV45AFZZ and MV45EFZ1

for entering installation-specific FORM routines and for using user

exits, which may be required and can be used if necessary. These

program components are called up by the modules in MV45AOZZ or

MV45AIZZ.

Please Reward If Really Helpful,

Thanks and Regards,

Sateesh.Kandula

[Former Member]

Hi,

USEREXIT_FIELD_MODIFICATION

USEREXIT_PRICING_CHECK

USEREXIT_FILL_XKOMK3

USEREXIT_PRICING_PREPARE_TKOMK

USEREXIT_PRICING_PREPARE_TKOMP

USEREXIT_SAVE_DOCUMENT

USEREXIT_SAVE_DOCUMENT_PREPARE

Reward points if useful

Regards,

Amrish Purohit

[Former Member]

hI,

And if you want only the userexits

http://www.easymarketplace.de/userexit.php

just click on the link adn you can get the All SAP User Exits on one view

<b>**REWARD IF THIS HELPS***</b>

Regards

Ak

[Former Member]

user exits are basically 4 types,

Field exit, Menu Exit, Function module and screen exit.

these exits we can use according to a situation...

Regards

Ramki

[Former Member]

Hello,

**PLEASE REWARD IF THIS HELPS**

USEREXIT

Userxits allow us to add our own functionality to SAP standard program

without modifying it . These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.

All Userexits start with the word USEREXIT_...

FORM USEREXIT_

z..

ENDFORM.

The problem lies in finding the correct userexit and how to find it if one exists for the purpose. Once the correct userexit is found the necessary

customer code is inserted in the customer include starting with the z..

in the form routine.

e.g. USEREXIT_SAVE_DOCUMENT_PREPARE

Certain application like SD still provide this form of enhancement using userexit but this practice is no longer being followed for newer extensions

instead they are using EXITs which come bundeled in enhancement packages . Neverthiless existing USEREXITS will be supported by SAP an all the newer versions of SAP.

1)ADDING OF NEW FIELDS IN PRICING

In Pricing in SD the fields on the basis of which pricing is done are derived from the FIELD CATALOG which is a structure KOMG .This structure is used to transfer transaction data to the pricing procedure in SD and is also known as communication structure.This structure KOMG consists of two tables KOMK for Header related fields and KOMP for item related fields.

The fields which are not in either of the two tables KOMK and KOMP

cannot be used in pricing .Sometimes a need arises when the pricing

is to be based on some other criteria which is not present in the form of fields in either of the two tables.

This problem can be solved by using USEREXITS which are provided for pricing in SD.

Pricing takes place both when the SALES ORDER ( Transaction VA01) is created as well as when INVOICING ( Transaction VF01) is done.Hence SAP provides 2 userexits ,one for sales order processing which is

USEREXIT_PRICING_PREPARE_TKOMP or

USEREXIT_PRICING_PREPARE_TKOMK

Depending upon which table (KOMK or KOMP) the new fields were inserted we use either of the above two userexits.These userexits are found in include MV45AFZZ of the standard SAP sales order creation program SAPMV45A.

In the case of userexit which will be called when invoicing is done ,these

are provided in the include RY60AFZZ which is in the standard SAP

program SAPMV45A. The name of the userexits are same. i.e

USEREXIT_PRICING_PREPARE_TKOMP or

USEREXIT_PRICING_PREPARE_TKOMK

These userexits are used for passing the data from the communication structure to the pricing procedure, for this we have to fill the newely

created field in the communication structure KOMG for this we fill the code in the above userexit using the MOVE statement after the data that

has to be passed is taken from the database table by using the SELECT statement. The actual structure which is visible in these userexits and which is to be filled for that particular field is TKOMP or TKOMK.

Before the coding for these userexits is done ,it is necessary to create a new field in either of the two tables KOMK or KOMP .For this purpose

includes are provided in each of them .

To create the field in header data(KOMK) the include provided is KOMKAZ

and to create the field in item data(KOMP) the include provided is KOMPAZ.

One possible example for the need of creating new fields can be e.g. Frieght to be based upon transportation zone ,for this no field is available in field catalog and hence it can be created in KOMK and then above userexits can be used to fill the transportation data to it.

2)The other method of finding userexit is to find the word USEREXIT in the

associated program of the transaction for which we want to determine userexit using SE38.

3)The other method of finding userexits is to find the include in case of SD/MM applications where the userexits are located ,this can be found in the SAP reference IMG generally in the subfolder under SYSTEM MODIFICATION.

Some other examples of userexits in SD are:

USEREXIT_NUMBER_RANGE

This userexit is used to assign a different internal document number to the

sales order(VA01) when it is created depending on some criteria like a different SALES ORGANIZAION(VKORG) .

USEREXIT_SAVE_DOCUMENT_PREPARE

This userexit is used to insert the ABAP code which will be called when

the document (sales order VA01) is just about to be saved.This userexit is used generally for custom checks on different fields , to display some information before the order will be saved or for making changes to certain fields before the sales order will be saved.

Exits & Enhancements

There are mainly six types of EXITs in sap which have been collected in the form of enhancement packages and attached to standard code in SAP.

These are different from USEREXIT in the way that they are implemented

in the form of FUNCTIONs while in USEREXITS we use form routines for their implementation. These are also sometimes known as function exits .

These start from the word EXIT_ followed by the program name and then followed by a three digit number.

e.g. EXIT_SAPMV45A_002

This exit is found in SD in enhancement V45A0002.