cancel
Showing results for 
Search instead for 
Did you mean: 

User Exits

Former Member
0 Kudos

Hi,

Can anyone help me in regarding User Exits.

Hw many types of User exits r there?

Wt r the user exits for pricing and sales order , Delivery?

Thanx in advance

Accepted Solutions (0)

Answers (8)

Answers (8)

Former Member
0 Kudos

Standard User exits can be checked out from Path: IMG> Sales and Dist> System Modification--> User exits. Here you have specific user exits for sales also.

We use SAP transactions CMOD and SMOD to manage exits. Before implementing an exit , it is required to create the project by using CMOD

selecting the enhancement and then implement it in SMOD . After the coding is done please activate it with lit stick button.

Please reward points if helpful

Former Member
0 Kudos

Hi Ravi,

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

SMOD is the transaction to view user exits assigned to an object.

CMOD is the transaction to change the user exits according to your requirement.

You can find user exits by looking into the phrase USER_EXIT.

Check this program to find out user exits for a transaction

TABLES: tftit,

e071,

e070.

TYPES: BEGIN OF x_tstc,

tcode TYPE tcode,

pgmna TYPE program_id,

END OF x_tstc.

TYPES: BEGIN OF x_tadir,

obj_name TYPE sobj_name,

devclass TYPE devclass,

END OF x_tadir.

TYPES: BEGIN OF x_slog,

obj_name TYPE sobj_name,

END OF x_slog.

TYPES: BEGIN OF x_final,

name TYPE smodname,

member TYPE modmember,

include(15), "Include name

END OF x_final.

DATA: it_tstc TYPE STANDARD TABLE OF x_tstc WITH HEADER LINE.

DATA: it_tadir TYPE STANDARD TABLE OF x_tadir WITH HEADER LINE.

DATA: it_jtab TYPE STANDARD TABLE OF x_slog WITH HEADER LINE.

DATA: it_final TYPE STANDARD TABLE OF x_final WITH HEADER LINE.

SELECTION-SCREEN: BEGIN OF BLOCK blk01 WITH FRAME TITLE text-t01.

PARAMETERS: p_tcode LIKE tstc-tcode OBLIGATORY.

SELECTION-SCREEN END OF BLOCK blk01.

START-OF-SELECTION.

PERFORM get_tcodes. "Get Tcodes

PERFORM get_objects. "Get Objects

END-OF-SELECTION.

PERFORM display_results. "Display Results

FORM get_tcodes.

SELECT tcode

pgmna

INTO TABLE it_tstc

FROM tstc

WHERE tcode = p_tcode.

IF sy-subrc = 0.

SORT it_tstc BY tcode.

ENDIF.

ENDFORM. " get_tcodes

FORM get_objects.

DATA: l_fname LIKE rs38l-name,

l_group LIKE rs38l-area,

l_include LIKE rs38l-include,

l_namespace LIKE rs38l-namespace,

l_str_area LIKE rs38l-str_area.

DATA: v_include LIKE rodiobj-iobjnm.

DATA: e_t_include TYPE STANDARD TABLE OF abapsource WITH HEADER LINE.

DATA: l_line TYPE string,

l_tabix LIKE sy-tabix.

IF NOT it_tstc[] IS INITIAL.

SELECT obj_name

devclass

INTO TABLE it_tadir

FROM tadir FOR ALL ENTRIES IN it_tstc

WHERE pgmid = 'R3TR' AND

object = 'PROG' AND

obj_name = it_tstc-pgmna.

IF sy-subrc = 0.

SORT it_tadir BY obj_name devclass.

SELECT obj_name

INTO TABLE it_jtab

FROM tadir FOR ALL ENTRIES IN it_tadir

WHERE pgmid = 'R3TR' AND

object = 'SMOD' AND

devclass = it_tadir-devclass.

IF sy-subrc = 0.

SORT it_jtab BY obj_name.

ENDIF.

ENDIF.

ENDIF.

*- Get UserExit names

LOOP AT it_jtab.

SELECT name

member

INTO (it_final-name, it_final-member)

FROM modsap

WHERE name = it_jtab-obj_name AND

typ = 'E'.

APPEND it_final.

CLEAR it_final.

ENDSELECT.

ENDLOOP.

*- Process it_final contents.

LOOP AT it_final.

l_tabix = sy-tabix.

CLEAR: l_fname,

l_group,

l_include,

l_namespace,

l_str_area.

l_fname = it_final-member.

CALL FUNCTION 'FUNCTION_EXISTS'

EXPORTING

funcname = l_fname

IMPORTING

group = l_group

include = l_include

namespace = l_namespace

str_area = l_str_area

EXCEPTIONS

function_not_exist = 1

OTHERS = 2.

IF sy-subrc = 0.

IF NOT l_include IS INITIAL.

*- Get Source code of include.

CLEAR: v_include, e_t_include, e_t_include[].

v_include = l_include.

CALL FUNCTION 'MU_INCLUDE_GET'

EXPORTING

i_include = v_include

TABLES

e_t_include = e_t_include.

IF sy-subrc = 0.

LOOP AT e_t_include.

IF e_t_include-line CS 'INCLUDE'.

CLEAR l_line.

l_line = e_t_include-line.

CONDENSE l_line NO-GAPS.

TRANSLATE l_line USING '. '.

l_line = l_line+7(9).

it_final-include = l_line.

MODIFY it_final INDEX l_tabix TRANSPORTING include.

ENDIF.

ENDLOOP.

ENDIF.

ENDIF.

ENDIF.

ENDLOOP.

ENDFORM. " get_objects

FORM display_results.

FORMAT COLOR COL_HEADING.

WRITE:/1(150) sy-uline.

WRITE:/ sy-vline,

2(23) 'Extension Name',

24 sy-vline,

25(39) 'Exit Name',

64 sy-vline,

65(74) 'Description',

140 sy-vline,

141(9) 'Include',

150 sy-vline.

WRITE:/1(150) sy-uline.

FORMAT RESET.

SORT it_final BY name member.

LOOP AT it_final.

CLEAR tftit.

SELECT SINGLE stext

INTO tftit-stext

FROM tftit

WHERE spras = 'EN' AND

funcname = it_final-member.

WRITE:/ sy-vline,

it_final-name COLOR COL_KEY, 24 sy-vline,

25 it_final-member, 64 sy-vline,

65 tftit-stext, 140 sy-vline,

141 it_final-include, 150 sy-vline.

WRITE:/1(150) sy-uline.

ENDLOOP.

ENDFORM. " display_results

Please Reward If really Helpful,

Thanks and Regards,

Sateesh.Kandula

Former Member
0 Kudos

hi, Can u pls share the notes on rohit_rathi@rediffmail.com

Former Member
0 Kudos

Hi Ravi,

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.

Types of User exits

1. Menu Exits

2.Function exits

3.Table exits

4.Screen exits

5.Keyword exits

6.Field exits.

User exits for Pricing.

1.•USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ

2.•USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ)

3.•USEREXIT_FIELD_MODIFICATION

4.•USEREXIT_FIELD_MODIFIC_KZWI

5.•USEREXIT_FIELD_MODIFIC_KOPF

User exits for Sales order

1•USEREXIT_DELETE_DOCUMENT

2•USEREXIT_FIELD_MODIFICATION

3.•USEREXIT_MOVE_FIELD_TO_VBAK

4.•USEREXIT_NUMBER_RANGE

5.•USEREXIT_SAVE_DOCUMENT

User exits for billing

1.•USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)

2.•USEREXIT_ACCOUNT_PREP_KOMPCV

3•USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)

4•USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB

5.USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)

Reward points if u helpful

Thanks&Regards

Govind.

Former Member
0 Kudos

Hi Ravi,

Give your mail ID. i will send sme notes.

Regards

Srini

Former Member
0 Kudos

Hi Srini,

can you please send me the notes on user exits

my id is srikrishj@gmail.com

Thanks in Advance

Sivaram

Former Member
0 Kudos

HI,

Can you please mail me the user exit docuent on this mail id: chandresh4u@yahoo.co.in

rdgs,

Former Member
0 Kudos

hai srini

pls forward the notes on user exits to my mail id also

kdhanekula@gmail.com

thanks & regards

Former Member
0 Kudos

Hi Srini,

Can I get your notes on user-exits? email me at nehasharma.sap@gmail.com

Thanks

Former Member
0 Kudos

hi dittakavi srinivas,

please send me the notes on user exits, my mail id is ravikiran_sd@yahoo.com. thanks in advance.

regards,

ravikiran.m

Former Member
0 Kudos

Hi srini can you please fwd me the user exits notes or pls upload

my id is srikrishj@gmail.com

Thanks in advance

Sivaram

Former Member
0 Kudos

Hi Kishore / Neha Sharma / Ravi Kiran / Rohit Rathi / Chandresh / Sivaram K ,

Sent mail.

Regards

Srini

Former Member
0 Kudos

Hi Srini,

received u r mail ,thanks a lot

Regards,

Sivaram

Former Member
0 Kudos

Hi,

Please send me documents on user exits to my id karthiksiggu@gmail.com

Regards,

Karthik

Former Member
0 Kudos

There are many ways to find the user-exits.

There are these CMOD and SMOD transactions.

Apart from these the one i really like is se80. Give the Program name and then look in the includes for that program, generally in the end, you will find the user exits for that program.

Regards,

Gaurav.

rmazzali
Active Contributor
0 Kudos

There are many kind of user exits:

1) old-fashioned exits (as I call them), some piece of code in the standard programs that you can modify using an access key released by SAP in the service workplace

2) enhancements: function modules that are called form the standard programs

3) BADI (Business Add-in), object oriented user exits, they are methods and interfaces call by the standard programs.

have a look to this customizing path to have information on the most important user exits in SD:

SPRO: Sales&Distribution -> System Modifications->User Exits

read the help to understand how they work.

Then have a look to this OSS note to understad how to use them:

0381348 Using user exit, customer exit, VOFM in SD

reward points if helpful

regards

Roberto Mazzali

Former Member
0 Kudos

Hi,

The best place to get 100% answer for this would be: ABAP forum in SDN.

Better post one query there, too!

Thanks,

Siva