cancel
Showing results for 
Search instead for 
Did you mean: 

SAP SD top 10 User exits

Former Member
0 Kudos

Hi,

Can any one tell sap SD top 10 user exites with description

thanks.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

HAi

Use the following Programs to find all UserExits.

For Sales Document - MV45AFZZ

For Delivery - MV50AFZZ

If it is useful for u give me points

Edited by: Subramanian Ramasamy on Sep 5, 2008 5:32 AM

Answers (3)

Answers (3)

claudia_neudeck
Active Contributor
0 Kudos

I close this tread because the last action was before two months

Shiva_Ram
Active Contributor
0 Kudos

Hi,

There is not really any top user exits in the system.

Depending on your business requirements, you need to select them.

For example below are some;

USEREXIT_DELETE_DOCUMENT

This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.

For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.

The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.

USEREXIT_FIELD_MODIFICATION

This user exit can be used to modify the attributes of the screen fields.

To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.

The usage of the field groups (modification group 1-4) is as follows:

Modification group 1: Automatic modification with transaction MFAW

Modification group 2: It contains 'LOO' for step loop fields

Modification group 3: For modifications which depend on check tables or on other fixed information

Modification group 4: is not used

The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.

This FORM routine is called up by the module FELDAUSWAHL.

See the Screen Painter manual for further information on structuring the interface.

USEREXIT_MOVE_FIELD_TO_VBAK

Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".

The user exit is called up at the end of the FORM routine VBAK_FUELLEN.

USEREXIT_MOVE_FIELD_TO_VBAP

Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".

The user exit is called up at the end of the FORM routine VBAP_FUELLEN.

USEREXIT_MOVE_FIELD_TO_VBEP

Use this user exit to assign values to new fields at the level of the sales document schedule lines.

The user exit is called up at the end of the FORM routine VBEP_FUELLEN.

USEREXIT_MOVE_FIELD_TO_VBKD

Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".

The user exit is called up at the end of the FORM routine VBKD_FUELLEN.

USEREXIT_NUMBER_RANGE

Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.

The user exit is called up in the FORM routine BELEG_SICHERN.

USEREXIT_PRICING_PREPARE_TKOMK

Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.

USEREXIT_PRICING_PREPARE_TKOMP

Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.

USEREXIT_READ_DOCUMENT

You use this user exit if further additional tables are to be read when importing TA01 or TA02.

The user exit is called up at the end of the FORM routine BELEG_LESEN.

USEREXIT_SAVE_DOCUMENT

Use this user exit to fill user-specific statistics update tables.

The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.

Note

If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.

USEREXIT_SAVE_DOCUMENT_PREPARE

Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.

The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.

These user exits are available under programs 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).

Regards,

former_member204513
Active Contributor
0 Kudos

Dear Nishanth,

I didn't get the intention of Top 10 User Exits from you ,

You can find the SD related User Exits through this IMG path

SPRO>IMG>Sales and Distribution >System modifications>User Exits, here you can find which are the areas having the User Exits .If you want to find the user exit click on the Documentation opposite to the function.

These will be used based on the business requirement.

I hope it will help you,

Regards,

Murali.