topic Re: user-exit in Application Development and Automation Discussions

user-exit

Former Member — Mon, 05 Jun 2006 05:02:55 GMT

Hi.

I have few questions about user-exit.

Where to find user-exits?

WHat is CMOD and SMOD.

What are different kind of exits?

What is field exit?

Re: user-exit

Former Member — Mon, 05 Jun 2006 05:09:31 GMT

Hello!!

Check these links.. YOu will get everything you need here!

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

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

http://www.planetsap.com/userexit_main_page.htm

http://www.sapgenie.com/abap/fieldexits.htm

http://www.sap-basis-abap.com/sapab013.htm

http://www.sap-img.com/abap/field-exits-smod-cmod-questions-and-answers.htm

http://www.sap-basis-abap.com/sapab014.htm

Regards,

Susmitha

Re: user-exit

Bema — Mon, 05 Jun 2006 05:11:11 GMT

Hi,

Refer

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

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

http://www.sap-basis-abap.com/sapab014.htm

Re: user-exit

Former Member — Mon, 05 Jun 2006 05:11:43 GMT

hi,

for finding user exit use this program,it'll list u all the enhancement:

*&----

& Report ZPJA_PM002 (V2) &

& &

*&----

& Text Elements: &

& P_DEVC Show user-exits from development class &

& P_LIMIT Limit submit program selection &

& P_FUNC Show function modules &

& P_SUBM Show submit programs &

& S01 Selection data (TCode takes precedence over program name) &

*&----

report zpja_pm002

no standard page heading

line-size 158.

*tables: enlfdir. "Additional Attributes for Function Modules

data: tabix like sy-tabix,

w_linnum type i,

w_off type i,

w_index like sy-tabix,

w_include like trdir-name,

w_prog like trdir-name,

w_incl like trdir-name,

w_area like rs38l-area,

w_level,

w_str(50) type c,

w_funcname like tfdir-funcname.

constants: c_fmod(40) type c value 'Function modules selected: ',

c_subm(40) type c value 'Submit programs selected: ',

c_col1(12) type c value 'Enhanmt Type',

c_col2(40) type c value 'Enhancement',

c_col3(30) type c value 'Program/Include',

c_col4(20) type c value 'Enhancement Name',

c_col5(40) type c value 'Enhancement Description'.

Work Areas: ABAP Workbench

data: begin of wa_d010inc.

data: master type d010inc-master.

data: end of wa_d010inc.

data: begin of wa_tfdir.

data: funcname type tfdir-funcname,

pname type tfdir-pname,

include type tfdir-include.

data: end of wa_tfdir.

data: begin of wa_tadir.

data: devclass type tadir-devclass.

data: end of wa_tadir.

data: begin of wa_tstc.

data: pgmna type tstc-pgmna.

data: end of wa_tstc.

data: begin of wa_tstcp.

data: param type tstcp-param.

data: end of wa_tstcp.

data: begin of wa_enlfdir.

data: area type enlfdir-area.

data: end of wa_enlfdir.

Work Areas: BADIs

data: begin of wa_sxs_attr.

data: exit_name type sxs_attr-exit_name.

data: end of wa_sxs_attr.

data: begin of wa_sxs_attrt.

data: text type sxs_attrt-text.

data: end of wa_sxs_attrt.

Work Areas: Enhancements

data: begin of wa_modsap.

data: member type modsap-member.

data: end of wa_modsap.

data: begin of wa_modsapa.

data: name type modsapa-name.

data: end of wa_modsapa.

data: begin of wa_modsapt.

data: modtext type modsapt-modtext.

data: end of wa_modsapt.

Work Areas: Business Transaction Events

data: begin of wa_tbe01t.

data: text1 type tbe01t-text1.

data: end of wa_tbe01t.

data: begin of wa_tps01t.

data: text1 type tps01t-text1.

data: end of wa_tps01t.

user-exits

types: begin of t_userexit,

type(12) type c,

pname like trdir-name,

txt(300),

level type c,

modname(30) type c,

modtext(40) type c,

end of t_userexit.

data: i_userexit type standard table of t_userexit with header line.

Function module developmnet classes

types: begin of t_devclass,

clas like trdir-clas,

end of t_devclass.

data: i_devclass type standard table of t_devclass with header line.

Submit programs

types: begin of t_submit,

pname like trdir-name,

level,

done,

end of t_submit.

data: i_submit type standard table of t_submit with header line.

Source code

types: begin of t_sourcetab, "#EC * (SLIN lügt!)

line(200), "#EC * (SLIN lügt!)

end of t_sourcetab. "#EC * (SLIN lügt!)

data: sourcetab type standard table of t_sourcetab with header line.

data c_overflow(30000) type c.

Description of an ABAP/4 source analysis token

data: i_stoken type standard table of stokex with header line.

data wa_stoken like i_stoken.

Description of an ABAP/4 source analysis statement

data: i_sstmnt type standard table of sstmnt with header line."#EC

keywords for searching ABAP code

types: begin of t_keywords,

word(30),

end of t_keywords.

data: keywords type standard table of t_keywords with header line.

function modules within program

types: begin of t_fmodule,

name like rs38l-name,

pname like trdir-name,

pname2 like trdir-name,

level,

bapi,

done,

end of t_fmodule.

data: i_fmodule type standard table of t_fmodule with header line.

*&----

& Selection Options &

*&----

selection-screen begin of block selscr1 with frame title text-s01.

parameter: p_pname like trdir-name memory id rid,

p_tcode like syst-tcode,

p_limit(4) type n default 100,

p_devc like rihea-dy_ofn default ' ',

p_func like rihea-dy_ofn default ' ',

p_subm like rihea-dy_ofn default ' '.

selection-screen end of block selscr1.

*&----

& START-OF-SELECTION &

*&----

start-of-selection.

if p_pname is initial and p_tcode is initial.

message e008(hrfpm). "Make entry on the selection screen

stop.

endif.

ensure P_LIMIT is not zero.

if p_limit = 0.

p_limit = 1.

endif.

perform data_select.

perform get_submit_data.

perform get_fm_data.

perform get_additional_data.

perform data_display.

*&----

& Form DATA_SELECT &

*&----

& &

*&----

form data_select.

data selection message to sap gui

call function 'SAPGUI_PROGRESS_INDICATOR'

destination 'SAPGUI'

keeping logical unit of work

exporting

text = 'Get programs/includes' "#EC NOTEXT

exceptions

system_failure

communication_failure

. "#EC *

determine search words

keywords-word = 'CALL'.

append keywords.

keywords-word = 'FORM'.

append keywords.

keywords-word = 'PERFORM'.

append keywords.

keywords-word = 'SUBMIT'.

append keywords.

keywords-word = 'INCLUDE'.

append keywords.

if not p_tcode is initial.

get program name from TCode

select single pgmna from tstc into wa_tstc-pgmna

where tcode eq p_tcode.

if not wa_tstc-pgmna is initial.

p_pname = wa_tstc-pgmna.

TCode does not include program name, but does have refereve TCode

else.

select single param from tstcp into wa_tstcp-param

where tcode eq p_tcode.

if sy-subrc = 0.

check wa_tstcp-param(1) = '/'.

check wa_tstcp-param+1(1) = '*'.

if wa_tstcp-param ca ' '.

endif.

w_off = sy-fdpos + 1.

subtract 2 from sy-fdpos.

if sy-fdpos gt 0.

p_tcode = wa_tstcp-param+2(sy-fdpos).

endif.

select single pgmna from tstc into wa_tstc-pgmna

where tcode eq p_tcode.

p_pname = wa_tstc-pgmna.

if sy-subrc <> 0.

message e110(/saptrx/asc) with 'No program found for: '

p_tcode."#EC NOTEXT

stop.

endif.

else.

message e110(/saptrx/asc) with 'No program found for: ' p_tcode.

"#EC NOTEXT

stop.

endif.

Call customer-function aus Program coding

read report p_pname into sourcetab.

if sy-subrc > 0.

message e017(enhancement) with p_pname raising no_program."#EC *

endif.

scan abap-source sourcetab tokens into i_stoken

statements into i_sstmnt

keywords from keywords

overflow into c_overflow

with includes.

WITH ANALYSIS.

if sy-subrc > 0. "keine/syntakt. falsche Ablauflog./Fehler im Skanner

message e130(enhancement) raising syntax_error. "#EC *

endif.

check I_STOKEN for entries

clear w_linnum.

describe table i_stoken lines w_linnum.

if w_linnum gt 0.

w_level = '0'.

w_prog = ''.

w_incl = ''.

perform data_search tables i_stoken using w_level w_prog w_incl.

endif.

endform. "DATA_SELECT

*&----

& Form GET_FM_DATA &

*&----

& &

*&----

form get_fm_data.

data selection message to sap gui

call function 'SAPGUI_PROGRESS_INDICATOR'

destination 'SAPGUI'

keeping logical unit of work

exporting

text = 'Get function module data' "#EC NOTEXT

exceptions

system_failure

communication_failure

. "#EC *

Function module data

sort i_fmodule by name.

delete adjacent duplicates from i_fmodule comparing name.

loop at i_fmodule where done ne 'X'.

clear: i_stoken, i_sstmnt, sourcetab, wa_tfdir, w_include .

refresh: i_stoken, i_sstmnt, sourcetab.

clear wa_tfdir.

select single funcname pname include from tfdir into wa_tfdir

where funcname = i_fmodule-name.

check sy-subrc = 0.

call function 'FUNCTION_INCLUDE_SPLIT'

exporting

program = wa_tfdir-pname

importing

group = w_area.

concatenate 'L' w_area 'U' wa_tfdir-include into w_include.

i_fmodule-pname = w_include.

i_fmodule-pname2 = wa_tfdir-pname.

modify i_fmodule.

read report i_fmodule-pname into sourcetab.

if sy-subrc = 0.

scan abap-source sourcetab tokens into i_stoken

statements into i_sstmnt

keywords from keywords

with includes.

if sy-subrc > 0.

message e130(enhancement) raising syntax_error.

endif.

check i_stoken for entries

clear w_linnum.

describe table i_stoken lines w_linnum.

if w_linnum gt 0.

w_level = '1'.

w_prog = i_fmodule-pname2.

w_incl = i_fmodule-pname.

perform data_search tables i_stoken using w_level w_prog w_incl.

endif.

endloop.

if p_devc = 'X'.

loop at i_fmodule.

clear: wa_tadir, wa_enlfdir.

select single area from enlfdir into wa_enlfdir-area

where funcname = i_fmodule-name.

check not wa_enlfdir-area is initial.

select single devclass into wa_tadir-devclass

from tadir where pgmid = 'R3TR'

and object = 'FUGR'

and obj_name = wa_enlfdir-area.

check not wa_tadir-devclass is initial.

move wa_tadir-devclass to i_devclass-clas.

append i_devclass.

i_fmodule-done = 'X'.

modify i_fmodule.

endloop.

sort i_devclass.

delete adjacent duplicates from i_devclass.

endif.

endform. "GET_FM_DATA

*&----

& Form GET_SUBMIT_DATA &

*&----

& &

*&----

form get_submit_data.

data selection message to sap gui

call function 'SAPGUI_PROGRESS_INDICATOR'

destination 'SAPGUI'

keeping logical unit of work

exporting

text = 'Get submit data' "#EC NOTEXT

exceptions

system_failure

communication_failure

. "#EC *

sort i_submit.

delete adjacent duplicates from i_submit comparing pname.

w_level = '0'.

loop at i_submit where done ne 'X'.

clear: i_stoken, i_sstmnt, sourcetab.

refresh: i_stoken, i_sstmnt, sourcetab.

read report i_submit-pname into sourcetab.

if sy-subrc = 0.

scan abap-source sourcetab tokens into i_stoken

statements into i_sstmnt

keywords from keywords

with includes.

if sy-subrc > 0.

message e130(enhancement) raising syntax_error.

continue.

endif.

check i_stoken for entries

clear w_linnum.

describe table i_stoken lines w_linnum.

if w_linnum gt 0.

w_prog = i_submit-pname.

w_incl = ''.

perform data_search tables i_stoken using w_level w_prog w_incl.

endif.

restrict number of submit program selected for processing

describe table i_submit lines w_linnum.

if w_linnum ge p_limit.

w_level = '1'.

endif.

i_submit-done = 'X'.

modify i_submit.

endloop.

endform. "GET_SUBMIT_DATA

*&----

& Form DATA_SEARCH &

*&----

& &

*&----

form data_search tables p_stoken structure stoken

using p_level p_prog p_incl.

loop at p_stoken.

clear i_userexit.

tabix = sy-tabix + 1.

i_userexit-level = p_level.

if i_userexit-level = '0'.

if p_incl is initial.

i_userexit-pname = p_pname.

else.

concatenate p_pname '/' p_incl into i_userexit-pname.

endif.

else.

if p_incl is initial.

i_userexit-pname = p_prog.

else.

concatenate p_prog '/' p_incl into i_userexit-pname.

endif.

Include

if p_stoken-str eq 'INCLUDE'.

check p_level eq '0'. " do not perform for function modules

*(2nd pass)

w_index = sy-tabix + 1.

read table p_stoken index w_index into wa_stoken.

check not wa_stoken-str cs 'STRUCTURE'.

check not wa_stoken-str cs 'SYMBOL'.

read table i_submit with key pname = wa_stoken-str.

if sy-subrc <> 0.

i_submit-pname = wa_stoken-str.

i_submit-level = p_level.

append i_submit.

endif.

Enhancements

if p_stoken-str eq 'CUSTOMER-FUNCTION'.

clear w_funcname.

read table p_stoken index tabix.

translate p_stoken-str using ''' '.

condense p_stoken-str.

if p_prog is initial.

concatenate 'EXIT' p_pname p_stoken-str into w_funcname

separated by '_'.

else.

concatenate 'EXIT' p_prog p_stoken-str into w_funcname

separated by '_'.

endif.

select single member from modsap into wa_modsap-member

where member = w_funcname.

if sy-subrc = 0. " check for valid enhancement

i_userexit-type = 'Enhancement'.

i_userexit-txt = w_funcname.

append i_userexit.

else.

clear wa_d010inc.

select single master into wa_d010inc-master

from d010inc

where include = p_prog.

concatenate 'EXIT' wa_d010inc-master p_stoken-str into

w_funcname

separated by '_'.

i_userexit-type = 'Enhancement'.

i_userexit-txt = w_funcname.

endif.

BADIs

if p_stoken-str cs 'cl_exithandler='.

w_index = sy-tabix + 4.

read table p_stoken index w_index into wa_stoken.

i_userexit-txt = wa_stoken-str.

replace all occurrences of '''' in i_userexit-txt with space.

i_userexit-type = 'BADI'.

append i_userexit.

endif.

Business transaction events

if p_stoken-str cs 'OPEN_FI_PERFORM'.

i_userexit-type = 'BusTrEvent'.

i_userexit-txt = p_stoken-str.

replace all occurrences of '''' in i_userexit-txt with space.

i_userexit-modname = i_userexit-txt+16(8).

case i_userexit-txt+25(1).

when 'E'.

clear wa_tbe01t.

select single text1 into wa_tbe01t-text1 from tbe01t

where event = i_userexit-txt+16(8)

and spras = sy-langu.

if wa_tbe01t-text1 is initial.

i_userexit-modtext = ''. "#EC NOTEXT

else.

i_userexit-modtext = wa_tbe01t-text1.

endif.

i_userexit-modname+8 = '/P&S'. "#EC NOTEXT

when 'P'.

clear wa_tps01t.

select single text1 into wa_tps01t-text1 from tps01t

where procs = i_userexit-txt+16(8)

and spras = sy-langu.

i_userexit-modtext = wa_tps01t-text1.

i_userexit-modname+8 = '/Process'.

endcase.

append i_userexit.

endif.

Program exits

if p_stoken-str cs 'USEREXIT_'.

i_userexit-type = 'Program Exit'.

i_userexit-txt = p_stoken-str.

replace all occurrences of '''' in i_userexit-txt with space.

append i_userexit.

endif.

Submit programs

if p_stoken-str cs 'SUBMIT'.

check p_level eq '0'. " do not perform for function modules

*(2nd pass)

check not p_stoken-str cs '_'. " ensure not SUBMIT_XXX

w_index = sy-tabix + 1.

read table p_stoken index w_index into wa_stoken.

check not wa_stoken-str cs '_'. " ensure not SUBMIT_XXX

replace all occurrences of '''' in wa_stoken-str with space.

read table i_submit with key pname = wa_stoken-str.

if sy-subrc <> 0.

i_submit-pname = wa_stoken-str.

i_submit-level = p_level.

append i_submit.

endif.

Perform routines (which reference external programs)

if p_stoken-str cs 'PERFORM'.

check p_level eq '0'. " do not perform for function modules

*(2nd pass)

w_index = sy-tabix + 1.

read table p_stoken index w_index into wa_stoken.

if not wa_stoken-ovfl is initial.

w_off = wa_stoken-off1 + 10.

w_str = c_overflow+w_off(30).

find ')' in w_str match offset w_off.

w_off = w_off + 1.

wa_stoken-str = w_str(w_off).

endif.

check wa_stoken-str cs '('.

w_off = 0.

while sy-subrc = 0.

if wa_stoken-str+w_off(1) eq '('.

replace section offset w_off length 1 of wa_stoken-str with ''

replace all occurrences of ')' in wa_stoken-str with space.

read table i_submit with key pname = wa_stoken-str.

if sy-subrc <> 0.

i_submit-pname = wa_stoken-str.

append i_submit.

endif.

exit.

else.

replace section offset w_off length 1 of wa_stoken-str with ''

shift wa_stoken-str left deleting leading space.

endif.

endwhile.

endif.

Function modules

if p_stoken-str cs 'FUNCTION'.

clear i_fmodule.

check p_level eq '0'. " do not perform for function modules

*(2nd pass)

w_index = sy-tabix + 1.

read table p_stoken index w_index into wa_stoken.

if wa_stoken-str cs 'WF_'.

if wa_stoken-str cs 'IF_'.
break-point.
endif.

if wa_stoken-str cs 'BAPI'.

i_fmodule-bapi = 'X'.

endif.

replace first occurrence of '''' in wa_stoken-str with space.

if sy-subrc = 4. " didn't find 2nd quote (ie name truncated)

clear wa_tfdir.

concatenate wa_stoken-str '%' into wa_stoken-str.

select single funcname into wa_tfdir-funcname from tfdir

where funcname like wa_stoken-str.

if sy-subrc = 0.

i_fmodule-name = wa_tfdir-funcname.

else.

continue.

endif.

else.

i_fmodule-name = wa_stoken-str.

endif.

i_fmodule-level = p_level.

append i_fmodule.

endif.

endloop.

endform. "DATA_SEARCH

*&----

& Form GET_ADDITIONAL_DATA &

*&----

& &

*&----

form get_additional_data.

data selection message to sap gui

call function 'SAPGUI_PROGRESS_INDICATOR'

destination 'SAPGUI'

keeping logical unit of work

exporting

text = 'Get additional data' "#EC NOTEXT

exceptions

system_failure

communication_failure

. "#EC *

loop at i_userexit.

Enhancement data

if i_userexit-type cs 'Enh'.

clear: wa_modsapa.

select single name into wa_modsapa-name from modsap

where member = i_userexit-txt.

check sy-subrc = 0.

i_userexit-modname = wa_modsapa-name.

clear wa_modsapt.

select single modtext into wa_modsapt-modtext from modsapt

where name = wa_modsapa-name

and sprsl = sy-langu.

i_userexit-modtext = wa_modsapt-modtext.

endif.

BADI data

if i_userexit-type eq 'BADI'.

clear wa_sxs_attr.

select single exit_name into wa_sxs_attr-exit_name from sxs_attr

where exit_name = i_userexit-txt.

if sy-subrc = 0.

i_userexit-modname = i_userexit-txt.

else.

i_userexit-modname = 'Dynamic call'. "#EC NOTEXT

endif.

clear wa_sxs_attrt.

select single text into wa_sxs_attrt-text from sxs_attrt

where exit_name =

wa_sxs_attr-exit_name

and sprsl = sy-langu.

i_userexit-modtext = wa_sxs_attrt-text.

endif.

modify i_userexit.

endloop.

get enhancements via program package

clear wa_tadir.

select single devclass into wa_tadir-devclass from tadir

where pgmid = 'R3TR'

and object = 'PROG'

and obj_name = p_pname.

if sy-subrc = 0.

clear: wa_modsapa, wa_modsapt.

select name from modsapa into wa_modsapa-name

where devclass = wa_tadir-devclass.

select single modtext from modsapt into wa_modsapt-modtext

where name = wa_modsapa-name

and sprsl = sy-langu.

read table i_userexit with key modname = wa_modsapa-name.

if sy-subrc <> 0.

i_userexit-modtext = wa_modsapt-modtext.

i_userexit-type = 'Enhancement'. "#EC NOTEXT

i_userexit-modname = wa_modsapa-name.

i_userexit-txt = 'Determined from program DevClass'."#EC NOTEXT

i_userexit-pname = 'Unknown'. "#EC NOTEXT

append i_userexit.

endif.

endselect.

endif.

endform. "GET_ADDITIONAL_DATA

*&----

& Form DATA_DISPLAY &

*&----

& &

*&----

form data_display.

data selection message to sap gui

call function 'SAPGUI_PROGRESS_INDICATOR'

destination 'SAPGUI'

keeping logical unit of work

exporting

text = 'Prepare screen for display' "#EC NOTEXT

exceptions

system_failure

communication_failure

. "#EC *

sort i_userexit by type txt modname.

delete adjacent duplicates from i_userexit comparing txt modname.

format headings

write: 'Enhancements from main program'. "#EC NOTEXT

write: /.

uline.

format color col_heading.

write: / sy-vline,

(12) c_col1, "Enhanmt Type

sy-vline,

(40) c_col2, "Enhancement

sy-vline,

(30) c_col3, "Program/Include

sy-vline,

(20) c_col4, "Enhancement name

sy-vline,

(40) c_col5, "Enhancement description

sy-vline.

format reset.

uline.

format lines

loop at i_userexit.

set line colour

case i_userexit-type.

when 'Enhancement'.

format color 3 intensified off.

when 'BADI'.

format color 4 intensified off.

when 'BusTrEvent'.

format color 5 intensified off.

when 'Program Exit'.

format color 6 intensified off.

when others.

format reset.

endcase.

write: / sy-vline,

i_userexit-type,

sy-vline,

i_userexit-txt(40),

sy-vline,

i_userexit-pname(30),

sy-vline,

i_userexit-modname(20),

sy-vline,

i_userexit-modtext(40),

sy-vline.

endloop.

format reset.

uline.

user-exits from development class of function modules

if p_devc = 'X'.

write: /.

write: / 'User-exits from function module development class'."#EC

*NOTEXT

write: 157''.

uline (90).

write: 157''.

loop at i_devclass.

clear wa_modsapa.

select name from modsapa into wa_modsapa

where devclass = i_devclass-clas.

select single name modtext into corresponding fields of wa_modsapt

from modsapt

where name = wa_modsapa-name

and sprsl = sy-langu.

format color 3 intensified off.

write: / sy-vline,

(12) 'Enhancement',

sy-vline,

wa_modsapa-name,

sy-vline,

wa_modsapt-modtext,

sy-vline.

endselect.

endloop.

uline (90).

format reset.

endif.

describe table i_fmodule lines w_linnum.

write: / c_fmod , at 35 w_linnum. "#EC NOTEXT

write: 157''.

if p_func = 'X'.

display fuction modules used in program

uline (38).

write: 157''.

loop at i_fmodule.

write: sy-vline,

i_fmodule-name,

sy-vline,

i_fmodule-bapi,

sy-vline.

write: 157''.

endloop.

uline (38).

endif.

describe table i_submit lines w_linnum.

write: / c_subm , at 35 w_linnum. "#EC NOTEXT

write: 157''.

if p_subm = 'X'.

display submit programs used in program

uline (44).

write: 157''.

loop at i_submit.

write: sy-vline,

i_submit-pname,

sy-vline.

write: 157''.

endloop.

uline (44).

endif.

issue message with number of user-exits displayed

describe table i_userexit lines w_linnum.

message s697(56) with w_linnum.

endform. "DATA_DISPLAY

cmod is the place where u create and attach the enhancement provided by SAP.

and SMOD is where u find these std enhancement

diff kind of exit:

field exit,customer exit,menu exit,user exit

4> if u want to provide some check at the field level, attach some more functionality to some field when user exters u can do that using program RSMODPRF--Field Exits for Data Elements

reward points if it helps

gunjan

Re: user-exit

Former Member — Mon, 05 Jun 2006 05:13:20 GMT

Hi,

User Exits are a method whereby the end user can add extra functionality or

change to a certain degree the way that SAP performs certain functions.

There are four types of exits:1.menu exit.

2.screen exit.

3.function module exits.

4.field exits.

How are they implemented ?

User Exits are implemented in such a way that unlike changes to SAP

standard code, they will survive across upgrades and hot pack applications.

They are also User Objects and can therefore be implemented without the

need of requesting an SSCR from SAP.

Within the standard SAP programs at key points are calls to function

modules starting with 'EXIT_'. These function modules generally accept as

input parameters structures containing for example the entire Order Header

(VBAK) of the sales order just entered, or perhaps a table of the Order

Items. These function calls are placed at points such as just before the

Order is saved or just before it is printed and so on.

These function modules contain a single include statement. The name of this

include is in the User domain and starts with Z. This enables it to be

edited without the need for an SSCR and also prevents it being overwritten

during upgrades.

Once this include has been created and activated, and the user exit is

activated the User exit becomes functional.

Implementing a User Exit.

User Exits are implemented using the transaction code 'SMOD'. Enter this in

the command line and press the Enter key. This will then show the SMOD

parameter screen:

User Exits are assigned a project name which begins with Z. Having entered

the relevant name in the 'Project' field, click the Create (or Change)

button as applicable.

When you are creating a new project, the projects attribute screen will be

displayed. This allows you to enter a title for the project and allows

access to the Enhancements (User Exits) that you want to assign to the

project and the components that you wish to use within those enhancements.

This screen allows you to enter a description of the project. Once you have

done this, click the save button. You will be asked as usual to assign a

development class and create a transport.

Once the transport has been created you can then go on to assign the

enhancements that you wish to use to the project.

Locating The Enhancements For A Project.

Unfortunately I have access to a 4.6C system only so therefore this

description is based around that.

To find enhancements for a particular program locate the Development Class

for the relevant program. Run the transaction and on the first input screen

click on the Status button. This provides the program name. Another method

of finding the program name is to use transaction SE93 which is the

Create/Modify Transaction transaction. Enter the transaction code and click

display.

In either case, cut the program name and then enter it into transaction

SE38 ? the ABAP program editor. Select the 'Attributes' radio button and

click display. Note the Development Class.

In 46C, go back to the SMOD main screen, enter the project name and select

the 'Enhancement Assignment' radio button.

Click the change button. This will display the enhancement assignment

screen. Position the cursor in the first field and press the <F4> key. This

will display the Input Help personal list window, a standard window that

you should be familiar with. Click the 'Information System' button and

enter the development class located above into the development class field.

Click the green tick.

This will display a list of enhancements for that particular development

category with a short description of what they do.

Select relevant description which will be transferred back to the

Enhancement Assignment screen.

For versions other than 46C, use transaction SE37 which is the Function

Module editor, in the function module name field press the <F4> key and

select further options. One of these will be the development class.

Clicking the enhancement button provides information on the enhancement.

The information displayed in this report includes whether the enhancement

has been implemented, and is active. (Green things scattered throughout the

report). Clicking the Exit name (In this case 'EXIT_SAPLV60A_002' will

display the relevant function module:

To create the enhancement, double click the Include name. This then takes

you into SE38 where you can edit the include to your hearts content.

Step by step procedure for creating Field Exits

There are eight steps to creating a field exit:

Step 1: Determine Data Element

Step 2: Go To Field Exit Transaction

Step 3: Create Field Exit

Step 4: Create Function Module

Step 5: Code Function Module

Step 6: Activate Function Module

Step 7: Assign Program/Screen

Step 8: Activate Field Exit

Step 1: Determine Data Element

- Before you can begin adding the functionality for a field exit, you must know the corresponding data element.

- An easy way to determine the data element associated to a particular screen field is to:

Go the appropriate screen.

Position the cursor in the appropriate field.

Press ‘F1’ for field-level help.

Click on the ‘Technical info’ pushbutton (or press ‘F9’) on the help dialog box.

On this Technical Information dialog box, the data element will be specified if the field is 'painted' from the ABAP/4 Dictionary.

Step 2: Go To Field Exit Transaction

- The transaction to create field exits is CMOD.

- You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.

- From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.

- After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.

NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.

Step 3: Create Field Exit

- From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.

- After choosing this menu path, a dialog box will prompt you for the appropriate data element .

- Enter the data element name and click the ‘Continue’ pushbutton.

- Now, you will be able to create the function module associated to the data element’s field exit.

Step 4: Create Function Module

- You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the ‘Continue’ pushbutton.

- In the ‘Function module’ field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:

FIELD_EXIT_<data element>

- You can add an identifier (an underscore followed by a single character ).

- The first function module for a data element’s field exit must be created without an identifier.

- To create the function module, click on the ‘Create’ pushbutton, choose menu path Function module -> Create, or press ‘F5’.

- After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing ‘Enter’, you will be able to go ahead and create the function module.

- Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.

Step 5: Code Function Module

- From the function module’s attributes screen, click on the ‘Source code’ pushbutton or choose the Goto -> Function module menu path to the code of the function module.

- Here you will add your desired functionality for the field exit.

- Remember that field exit’s function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.

- You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.

Step 6: Activate Function Module

- After coding the function module, you must remember to activate it.

- Use the Function module -> Activate menu path to activate the function module.

- At this point, you can return to the field exit transaction.

- You should be able to 'green arrow' back to this transaction.

- When you return to the field exit transaction, you will see an entry for the newly created field exit.

- At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.

- Also, the field exit will not be triggered yet because it is inactive.

Step 7: Assign Program/Screen

- This step is only needed if you want to make a field exit local.

- To make a field exit local, select the field exit and click on the ‘Assign prog./screen’ pushbutton.

- In the dialog box , indicate the appropriate program name and screen number.

This information indicates that the field exit is local to the specified screen in the specified program.

- In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the ‘Fld. Exit’ field.

- If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.

- If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.

Step 8: Activate Field Exit

- The field exit must be active for it to be triggered by the system.

- Activate the field exit by choosing the Field exit -> Activate menu path.

- After assigning the field exit to a change request, its status will change to ‘Active’ and it will be triggered automatically on the appropriate screen(s).

NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers

send me ur email id .I will send u some good docs on this.]

send u the docs.pls chk ur mail

rgds,

latheesh

Message was edited by: Latheesh Kaduthara

Re: user-exit

Former Member — Mon, 05 Jun 2006 05:13:51 GMT

Hello.

Check this too..

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

Regards,

Susmitha

Re: user-exit

Former Member — Mon, 05 Jun 2006 05:32:43 GMT

Hi Latheesh

My email id is onkar1409@hotmail.com.

Please send me the document.Thanks a lot for your help