Need user exit / screen exit for SE38 program variant save

Hi ABAPers,
Need user exit / screen exit for SE38 program variant save action to log addition details of variant changes done and relavent ticket details in z table.
Currently table VARID table stores only latest change and not history.
We need to avoid logging enabling for table VARID and custom field addition in it.
Please advice.
-Nilesh

HI Nilesh,
I don't think any Exits available for this.
Better u go for Implicit Enhancement.
regards
Sreekanth

Similar Messages

User and screen exit for BP transaction

Hi,
We need to add a few z-fields to BP (Business Partner) address tab and save data into database. Please let me know if any user or screen exits are available.
Thank you.

hi
use this program to get all the relevant enhancement and based on that ....use the relevant one and write ur piece of code..
& 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.
    endif.
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.
    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.
    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.
    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.
    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.
    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.
    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.
      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
reward points if it helps
gunjan

DIFF. BETWEEN USER EXIT & SCREEN EXIT .

Dear All ,
Kindly help me to clear the diff between user exit & screen exit , where user exit is required & where screen exit is required . Do there is a need of Abaper in both the cases ?
Regards,
SAP11

Hi,
The basic rule in SAP as far as ABAP workbench developments are concerned is "Do not modify the source code of the program"
Since needs and requirements keep on changing from client to client and for various business scenarios, there is a need to customise the programs as per client requirement.
For this purpose, SAP has provided numerous list of user-exits also known as enhancements, which is nothing but a program which will deal with the client additional requirement, without modifying the source code of the program. These exits are already provided by SAP. You can see the list of user-exits provided by using the transaction code SMOD. If you cannot find an user exit which match with client requirements, then you can tell SAP to create a new user exit.
As far as screen exit is concerned, as per the client requirement if the user wants a separate screen to appear on execution of a particular task, which deviates from the standard sap provided flow of transactions, you write a screen exit. In such case you first prepare the screen using the screen painter and define it as to after which sap screen you want this screen to appear for processing the transaction further.
Regards,
Baskar

User Exit / Functional Exit / Screen Exit /Customer Exit

Dear all,
Can anybody explain me about the User Exit / Functional Exit / Screen Exit /Customer Exit and give me the step by step procedure.I want to know more plese reply me.

Hi,
Exits are basically the hooks whcih SAP has provided to add your own code. There are two types of Exits:
1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.
2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.
BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)
Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.
Please go through the following link which will help you understand the exits in a much better way:
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
http://sap.niraj.tripod.com/id21.html
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.sap-img.com/ab038.htm
User Exits.
http://www.erpgenie.com/sap/abap/code/abap26.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
customer exits
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
Menu Exit.
http://www.sappoint.com/abap/spmp.pdf
http://www.sappoint.com/abap/userexit.pdf
http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm
http://www.sapdevelopment.co.uk/enhance/enhancehome.htm
USER EXIT
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.sap-img.com/ab038.htm
http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm
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://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html
Field Exit
If you are in 4.7 and up follow this
1. Run report RSMODPRF
2. Run on the selection screen
3. In list Field Exit > Create
4. Give your data element
5.System will generate the FM FIELD_EXIT_XXXXX
6. Activate it.
7. Select your field exit and assign to your program and screen
8. Select again .. Field exit > Activate
If you are in version below 4.7
1. CMOD
2. Go to >Text enhancment > Field exit
then follow the same step from 3 onwards as given above.
Menu Exit
Procedure for Creating MENU Exits.
1) To get into Area Menu Maintenance Screen Type SE43 T.Code in Command
Line.
2) In Area Menu Paramenter type 'S000' (S triple Zero)
3) Then Press Change Icon in Application Tool Bar. Then It may ask for
Access Key [or] it may display "Specify Processing mode" window. If it ask
for the Access Key Check for the availability of OSS Note and apply to open
Standard SAP Menu to include MENU Exits. Otherwise, if it display "Specify
Processing mode" window with Three Push Button. In which select "Change" and
proceed further.
4) Then it will display "Information" window with the following information
"Caution : The Original Language of the structure is German (editing lang. :
English) ". Then press "Enter Key to proceed further.
5) Then you will get into "Edit Area Menu S000".
6) for eg:- Expand Tools Menu.
7) Then Press ABAP Workbench <Icon>.
8) Then you will get into ABAP Workbench Menu Tree.
9) Then Expand Utilities Menu.
10) In the last line you will find one MENU EXIT Provision to include your
own menu. "Node Text Not Found" This text can be change by double Clicking
that. There you can find the T.Code. Here for Eg:- "+DW4".
11) for eg: - Here change the Text to "Sample Menu Exit" and then note down
the T.Code "+DW4".
12) Then Save with Change Request Number and come out of Transaction SE43.
13) Then Goto Transaction SE93.
14) Then type T.Code "+DW4" and press Create.
15) Then proceed further to create transaction called "+DW4".
I hope this could help you in Creating Menu Exit...
Creating menu exits
http://help.sap.com/saphelp_nw04/helpdata/en/c8/19762743b111d1896f0000e8322d00/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/83/7a18cbde6e11d195460000e82de14a/frameset.htm
Regards,
Satish

DIfference Between User Exits, Screen Exits, Menu Exits And BADI

Could any one let me know the exact/practical dIfference Between User Exits, Screen Exits, Menu Exits And BADI. ? And why BADIs are more proned to use?

Hi,
User Exits:
A user exit is a three character code that instructs the system to access a program during system processing.
SXX: S is for standard exits that are delivered by SAP. XX represents the 2-digit exit number.
UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number
Menu Exits:
Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu items text when activating the item in an add-on project.
Screen Exits:
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screens flow logic.
BADIs:
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
And why BADIs are more proned to use?
In contrast to above customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
Regards,
Ferry Lianto

Version Change in User Exit , Customer Exit, Screen Exit

Hi All,
If Version change then whether the user exit, customer exit & screen exit will remain same? or what needs to be done for that?.
Regards,
Abhijit

Hi,
as per my knowledge there is no effect in the user exit ,in generally when version change the screens are chenges for particular transaction not the user exit .
Regards,
Madhu

User Exit or BADI for F-28 on Save Event

Dear Expert,
Please tell me User Exit or BADI for F-28 on Save Event for T.Code F-28.

Dear Expert,
Please tell me User Exit or BADI for F-28 on Save Event for T.Code F-28.

Menu-exits, Function-exits & Screen-exits

What is Menu-exits, Function-exits & Screen-exits ? explain

Hi,
Why do you need enhancements ?
The standard applications do not offer some of the functionality you need. The R/3 enchancement concept allows you to add your own functionality to SAP's standard business applications.
What are the different types of enhancements ?
Enhancements using customer exits
Customers' potential requirements which are not included in the standard software are incorporated in the standard as empty modification 'shells'. Customers can then fill these with their own coding. Enhancements can relate to programs, menus and screens. Upward compatibility is assured. In other words, SAP guarantees that the jump from the standard software to the exit and the interface which call the exit will remain valid in future releases.
Enhancements to ABAP/4 Dictionary elements
These are ABAP/4 Dictionary enhancements (creation of table appends), text enhancements (customer-specific key words and documentation for data elements) and field exits (creation of additional coding for data elements).
What is customer development ?
Creating customer-specific objects within the customer name range.
What is SSCR ?
SSCR (SAP Software Change Registration) is a procedure, for registering all manual changes to SAP source coding and SAP Dictionary objects.
What is the difference between modifications and enhancements ?
Modifications mean making changes to the SAP standard functionality.
Enhancements mean adding some functionality to SAP standard functionality.
What are the disadvantages of modification ?
Modifying standard code can lead to errors
Modifications mean more work during software upgrades
What are the advantages of enhancements ?
Do not affect standard SAP source code
Do not affect software upgrades
when do you opt for modification ?
Customer exits are not available for all programs and screens within the R/3 standard applications. You can only use exits if they already exist within the SAP R/3 System . Otherwise you have to opt for modifications .
What are the various types of customer exits ?
Menu exits
Screen exits
Function module exits
Keyword exits
What is a menu exit ?
Adding items to the pulldown menus in standard R/3 applications .
13.What is a screen exit ?
Adding fields to the screens within R/3 applications. SAP creates screen exits by placing special subscreen areas within a standard R/3 screen and calling a customer subscreen from within the standard dynpro's flow logic.
What is a function module exit ?
Adding functionality to R/3 applications. Function module exits play a role in both menu and screen exits.
What is a keyword exit ?
Add documentation to the data elements of key words defined in the ABAP/4 Dictionary. The system displays this documentation whenever a user presses F1 to get online help for a screen field.
How do SAP organizes its exits ?
SAP organizes its exits in packages that are called SAP enhancements. Each SAP enhancement can contain many individual exits
Regards

Can any one give step by step screen shots for dialog programming

can any one give step by step screen shots for dialog programming ..
thanks
venki...

Hi
see the following links and example programs and practice the same dialog pool program
Check the below link:
http://wiki.ittoolbox.com/index.php/FAQ:What_is_module_pool_program_in_abap%3F
http://help.sap.com/saphelp_46c/helpdata/en/35/26b1aaafab52b9e10000009b38f974/content.htm
http://sap.mis.cmich.edu/sap-abap/abap09/sld011.htm
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
http://www.geocities.com/ZSAPcHAT
http://www.allsaplinks.com/files/using_table_in_screen.pdf
http://help.sap.com/saphelp_webas630/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://www.sap-img.com/
http://help.sap.com/saphelp_46c/helpdata/en/08/bef2dadb5311d1ad10080009b0fb56/content.htm
http://www.sapgenie.com/links/abap.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c9/5472fc787f11d194c90000e8353423/frameset.htm
You can also check the transaction ABAPDOCU which gives you lot of sample programs.
Also you can see the below examples...
<b>Go to se38 and give demodynpro and press F4.
YOu will get a list of demo module pool programs.
One more T-Code is ABAPDOCU.
YOu can find more examples there.
See the prgrams:
DEMO_DYNPRO_TABLE_CONTROL_1 Table Control with LOOP Statement
DEMO_DYNPRO_TABLE_CONTROL_2 Table Control with LOOP AT ITAB</b>
http://www.geocities.com/ZSAPcHAT
http://www.allsaplinks.com/files/using_table_in_screen.pdf
<b>Reward points for useful Answers</b>
Regards
Anji

Menu Exit & Screen Exit Implementation Step by Step Implementation Needed:

Hi Experts,
I am in need of how to implement Menu Exit and Screen Exit using a simple
example.If any step by step implementation through snapshots were it will be
helpful instead just some links that doesn't work after some steps due to version
changes or not proper steply explanations.Points will be rewarded accordingly.
Thanks for your help in Advance.

Hi Sudha,
Screen exits are exits that allow you to use a reserved part of the screen (A subscreen) to display or input data.
It is determined be SAP where the sub screen will be displayed.
The syntax is: CALL CUSTOMER-SUBSCREEN
The screen exit is not processed untill the corresponding subscreen has been created in an enhancement project, and the project has been activated.
Note:
Function codes are only processed in the main screens flow logic
You are not allowed to enter a name for the subscreens command field
You are not allowed to define GUI stauses
You are not allowed to enter a value for Next screen
The global data of the program is not available for the subscreen. Data for the subscreen is provided by function modules. These function modules belongs to the same function group as the subscreen
Subscreens are edited with transaction CMOD. When you activate a project containg subscreens, the calling screen is regenerated and the subscreen is displayed next time you display the calling screen
The developer must create the subscreen and the corresponding PBO and PAI modules
How to identify screen exits
Look after CALL CUSTOMER-SUBSCREEN in the screenprogram of the screen you want to modify.
Use transaction CMOD menu Utillities -> SAP enhancements to search for screen exits
MENU EXITS
Menu exits allow you to add your own functionallity to menus. Menu exits are implemented by SAP, and are reserved menu entries in the GUI interface. The developer can add his/her own text and logic for the menu.
Function codes for menu exits all start with "+"
Example
We want to create a new menu item in the Office menu. The text for the menu should be "Run ZTEST", and the menu will
run report ZTEST.
Goto transaction SE43 Area Menu Maintenance
In Area Menu Paramenter type 'S000' (S triple Zero)
Select Change and ignore all the warning screens
Expand the office menu. In the buttom of the office tree you will find a menu named "Customer function"
Double click on the text. In the pop-up screen change the text to "Run ZTEST". Note that the trsnaction code is +C01
Goto transaction SE93 and create transaction +C01 that calls report ZTEST.
Now you will se the menu displayed in the office tree. If you delete transaction +C01 again, the new menu will dissapear.
USER EXITS
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 <3 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
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.
3. Using Project management of SAP Enhancements
We want to create a project to enahance trasnaction VA01
Go to transaction CMOD
Create a project called ZVA01
Choose the Enhancement assign radio button and press the Change button
In the first column enter V45A0002 Predefine sold-to party in sales document . Note that an enhancement can only be used i 1 project. If the enhancement is allready in use, and error message will be displayed
Press Save
Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit.
Now the function module is displayed. Double click on include ZXVVAU04 in the function module
Insert the following code into the include: E_KUNNR = '2155'.
Activate the include program. Go back to CMOD and activate the project.
Goto transaction VA01 and craete a salesorder. Note that Sold-to-party now automatically is "2155"
Please check if the thread given below would be of any help.
http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/menu-exits-72696#
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
Regards
KK

Menu Exit, Screen Exit

Hi, Friends,
How to find out Menu and Screen Exits for a particular transaction in version 4.7.

Hi,
These threads explains how to find the menu exits and screen Exit.have a look at it.
How to find Field Exit, Menu Exit and Screen Exit in a given TCode
How to find Menu Exits?
Reward points if helpful.
Manoj.

Need to change screen colours for each system in the landscape

hi ,
we are in need of having different themes for different systems in the landscape .
that is
if i click development system , the screen with 'theme1'
if i click quality system system , the screen with 'theme2'
if i click production system system , the screen with 'theme3'
how to configure this colour setting in accord to the system for all the users

Hi Susin,
You would do this by changing the parameter sapgui/theme for each system. It uses the Tradeshow theme by default as of Web AS 6.40. As long as the SAPgui itself is set to "System Dependant" then it should work fine.
Regards,
Nelis

Need user's manuals document for my Satellite L645

Hi
I need users manuals for my notebook.
I bought it in Asia but unfortunately I dont have manuals for it.
Ive already searched it on toshiba page but I cannot find it.
Who can help me?
My notebook model is Satellite L645.
Thanks in advance
+Message was edited: posting has been translated+

Dont know what *Satellite L645-xxx* you have exactly but such series was released for USA market too: for example +Satellite L645-S4102+
Therefore the manual could be downloaded also from Toshiba US support page; of course it depends on model you have.

Need to create screen exit for Sales Order Transaction

Hi all,
I need to show some additional data on 'ADDITIONAL DATA B' tab of the sales order transaction... I have created a project but not able to get the enhancements that are to be used...
Will be really very heplful if you let me know, which one to use also why to use it...and how to determine which enhancement is to be used.... As i am new to User Exits...

Hi ,
       Check out this exits.
SDTRM001            Reschedule schedule lines without a new ATP check
V45A0001            Determine alternative materials for product selection
V45A0002            Predefine sold-to party in sales document
V45A0003            Collector for customer function modulpool MV45A
V45A0004            Copy packing proposal
V45E0001            Update the purchase order from the sales order
V45E0002            Data transfer in procurement elements (PRreq., assembly)
V45L0001            SD component supplier processing (customer enhancements)
V45P0001            SD customer function for cross-company code sales
V45S0001            Update sales document from configuration
V45S0003            MRP-relevance for incomplete configuration
V45S0004            Effectivity type in sales order
V45W0001            SD Service Management: Forward Contract Data to Item
V46H0001            SD Customer functions for resource-related billing
V60F0001            SD Billing plan (customer enhancement) diff. to billing plan
SDAPO001            Activating Sourcing Subitem Quantity Propagation
Check some of badi .
Please reward if useful.

Need help in screen capturing for flash CS4 AS3

Hi, i need help!!!!!!!!!!!!!!!!!!!!!! URGENT!
I am currently doing Augmented Reality.
I got my marker to detect my model but my problem now is how to screen capture the content that is in swf.
(As in capture the dae model shown in the comp not from webcam.)
& also i just want to capture the swf window not the whole desktop.
I read online, they say its impossible?
Or is it possible to call screen capture function in javascript to flash CS4? (LIke external data)
(Moreover, does anyone know how to detect multiple dae models with different markers?)
Anyone can help??? Thanks in adv!!

My current program (Flash CS4, AS3) only can capture what the webcam sees.
How do i change it to screen capture (something like print screen) with my .DAE models?
In the case, when i click on the capture button, it print screen.
Here's part of the code that capture what the webcam sees.
private function captureImage(e:MouseEvent):void
   bmd.draw(stage);
   bmp = new Bitmap(bmd);
   bmp.x = 140;
   bmp.y = 40;
   addChild(bmp);
   capture.visible = false;
   saveButton.visible = true;
   discardButton.visible = true;
Really really need help! URGENT!
Thanks!

Need user exit / screen exit for SE38 program variant save

Similar Messages

Maybe you are looking for