Stop Web Object audio on screen exit - Cap 7

I have a series of slides, each with one Web Object. Each is a link to an HTML page with an MP4/player. If I want to go to the next slide while the movie is playing, the audio does not stop on exit. I can't do an action on Exit as the audio isn't from an Advanced Action but from the Web Object. Am I missing something obvious here?
Thanks in advance...

The JavaScript API for Captivate is different for SWF vs. HTML5 output. Both are a mess and have inconssistencies... and there is no documentation. I'm hoping the Adobe Captivate Dev Team will address this for Cp 8. For SWF output, you can look here:
http://captivatedev.com/2012/07/01/adobe-captivate-6-the-javascript-api/
And here:
http://blogs.adobe.com/captivate/2010/12/captivate-swf-events.html
The HTML5 API is much more versatile where you can subscribe to the events mentioned in the last link. I'd recommend poking around with Chrome's dev tools to see what's available in HTML5 land.

Similar Messages

Streaming audio from my IPAD to my Apple TV from Rhapsody application. when Apple TV go into Screen Saver mode, about 5 minutes after that it stops playing the Audio Stream and goes into Sleep mode.

I am Streaming audio from my IPAD to my Apple TV from Rhapsody application. when Apple TV go into Screen Saver mode, about 5 minutes after that it stops playing the Audio Stream and goes into Sleep mode. I am using the Optical Out from the Apple TV to my receiver, the Apple TV is hard Wired to the Network, the IPAD is Wirelessly attached to the network (it continues to play the Audio Stream). When the Apple TV is turned back on it resumes playing once I manual select it for output from the IPAD. All device are on current releases of software. I have no Video hooked up to the Apple TV. How do I correct this?

Intermittent problems are often a result of interference. Interference can be caused by other networks in the neighbourhood or from household electrical items.
You can download and install iStumbler (NetStumbler for windows users) to help you see which channels are used by neighbouring networks so that you can avoid them, but iStumbler will not see household items.
Refer to your router manual for instructions on changing your wifi channel or adjusting your multicast rate.
There are other types of problems that can affect networks, but this is by far the most common, hence worth mentioning first. Networks that have inherent issues can be seen to work differently with different versions of the same software. You might also try moving the Apple TV away from other electrical equipment.

Problem while transporting Screen exit object from DEV to QAS client

Hello All,
I have developed screen exit for tcode 'ME51N' to add customer field in newly added TAB. To grayout that field in display mode, I have added code on the PBO event of that screen. Code for PBO even has been written inside the include. Exit is working fine on development client.
After transporting the exit on QAS client the field graying out functionality in diplay mode is not working eventhough the include which contains the code for PBO even is exist on QAS. Also in flow logic if i double clock on the PBO module event, it says object does not exist, eventhough the include which contains the PBO event code exist in QAS.
Please, help me to understand why the linkage between flow logic PBO event and the include where the PBO code has been written is not getting transported from DEV to QAS.

Hi,
First check the TR log if there is any errors. If no errors, then check if all the objects were properly transported or not.
You might have missed out in transporting the enhancement activation(CMOD).
Try to Rebuild the object list for updating the navigation index. You can do this from SE80=>Rightclick on function group=>More functions=>Rebuild object list.
Thanks,
Vinod.

I am trying to use a Logitech USB headset to record with screencast o matic. In the sound file of system preferences the headset is recording audio. However it stops working when I use screen cast o matic. Any advice?

I am trying to use a Logitech USB headset to record with screencast o matic. In the sound file of system preferences the headset is recording audio. However it stops working when I use screen cast o matic. Any advice?

See these threads for some possible solutions:
Bluetooth and 10.7
Bluetooth speaker error

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

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

Screen exits/BADIs available for Tcode-QM02/QM03

Hi Everyone,
                   I have to modify a screen for Tcode-QM02( 'Checklist' tab) and add a drop down field to it.I have not worked on screen exits/BADIs prior to this please let me know how to proceed with this.
      Alsoplease tell me how can I manually go and check out whether a exit or BADI is available for this transaction?
Please reply as its a bit urgent.
Thanks and Regards
Abhishek

hi,
check these exits n badi's.
Transaction Code - QM02                     Change quality notification
Enhancement/ Business Add-in            Description
Enhancement
IWOC0004                                Change single-level list editing PM/QM/SM ALV settings
IWOC0003                                PM/SM authorization check of ref. object and planner group
IWOC0002                                PM/SM notification: Check whether status change is allowed
IWOC0001                                Create PM/SM notification: Determine reference object
IWO10027                                User exit: Generate user-defined settlement rule
IWO10026                                User check on setting status 'Do not perform'
Business Add-in
IQS0_STATUS_MAINTAIN                    Control of Changeability of User Status
IWO1_SUBSCREEN_0170                     Display Additional Data on Object Screen 0170 PhysicalSample
IWOC_LIST_TUNING                        Performance Tuning for Lists in PM/CS
IWOC_OBJECTINFO_CHNG                    Changes to Data of Object Info Screen
WOC_FL_DETERMINE                        Determine Date for Determining Installation Loc. Equi.
NOTIF_AUTHORITY_01                      Additional Authorization Checks for the Notification
goto system - status of ur transaction and find porogram name
then goto attributes of program n find package.
now goto smod or se18 click f4 click information system u will get all exits or badis available.

Screen exits in XK01

Hi,
How to find out the screen exits in Xk01?
Also,plz let me know how to find the screen exits for any given transaction...and if we can find the screen exits on any screen.
Thanks
Sahitya

Hi Sahitya.
May be this program will be of some help to you.
REPORT z_find_userexit NO STANDARD PAGE HEADING.
*& Enter the transaction code that you want to search through in order
*& to find which Standard SAP User Exits exists.
*& Tables
TABLES : tstc,    "SAP Transaction Codes
         tadir,    "Directory of Repository Objects
         modsapt, "SAP Enhancements - Short Texts
         modact,   "Modifications
         trdir,    "System table TRDIR
         tfdir,    "Function Module
         enlfdir, "Additional Attributes for Function Modules
         tstct.    "Transaction Code Texts
*& Variables
DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
DATA : field1(30).
DATA : v_devclass LIKE tadir-devclass.
*& Selection Screen Parameters
SELECTION-SCREEN BEGIN OF BLOCK a01 WITH FRAME TITLE text-001.
SELECTION-SCREEN SKIP.
PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN END OF BLOCK a01.
*& Start of main program
START-OF-SELECTION.
Validate Transaction Code
SELECT SINGLE * FROM tstc
    WHERE tcode EQ p_tcode.
Find Repository Objects for transaction code
IF sy-subrc EQ 0.
    SELECT SINGLE * FROM tadir
       WHERE pgmid    = 'R3TR'
         AND object   = 'PROG'
         AND obj_name = tstc-pgmna.
    MOVE : tadir-devclass TO v_devclass.
    IF sy-subrc NE 0.
      SELECT SINGLE * FROM trdir
         WHERE name = tstc-pgmna.
      IF trdir-subc EQ 'F'.
        SELECT SINGLE * FROM tfdir
          WHERE pname = tstc-pgmna.
        SELECT SINGLE * FROM enlfdir
          WHERE funcname = tfdir-funcname.
        SELECT SINGLE * FROM tadir
          WHERE pgmid    = 'R3TR'
            AND object   = 'FUGR'
            AND obj_name = enlfdir-area.
        MOVE : tadir-devclass TO v_devclass.
      ENDIF.
    ENDIF.
Find SAP Modifactions
    SELECT * FROM tadir
      INTO TABLE jtab
      WHERE pgmid    = 'R3TR'
        AND object   = 'SMOD'
        AND devclass = v_devclass.
    SELECT SINGLE * FROM tstct
      WHERE sprsl EQ sy-langu
        AND tcode EQ p_tcode.
    FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
    WRITE:/(19) 'Transaction Code - ',
    20(20) p_tcode,
    45(50) tstct-ttext.
    SKIP.
    IF NOT jtab[] IS INITIAL.
      WRITE:/(95) sy-uline.
      FORMAT COLOR COL_HEADING INTENSIFIED ON.
      WRITE:/1 sy-vline,
      2 'Exit Name',
      21 sy-vline ,
      22 'Description',
      95 sy-vline.
      WRITE:/(95) sy-uline.
      LOOP AT jtab.
        SELECT SINGLE * FROM modsapt
        WHERE sprsl = sy-langu AND
        name = jtab-obj_name.
        FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
        WRITE:/1 sy-vline,
        2 jtab-obj_name HOTSPOT ON,
        21 sy-vline ,
        22 modsapt-modtext,
        95 sy-vline.
      ENDLOOP.
      WRITE:/(95) sy-uline.
      DESCRIBE TABLE jtab.
      SKIP.
      FORMAT COLOR COL_TOTAL INTENSIFIED ON.
      WRITE:/ 'No of Exits:' , sy-tfill.
    ELSE.
      FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
      WRITE:/(95) 'No User Exit exists'.
    ENDIF.
ELSE.
    FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
    WRITE:/(95) 'Transaction Code Does Not Exist'.
ENDIF.
Take the user to SMOD for the Exit that was selected.
AT LINE-SELECTION.
GET CURSOR FIELD field1.
CHECK field1(4) EQ 'JTAB'.
SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).
CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.
Thanks and regards.

Screen exits - Urgent.

Hi,
I am working on screen exits for VA01.
Can someone tell me how to add table control in a sub screeen at item level in additional data B ?

Hi
How to implement screen exit for a SAP standard transaction HOT
Introduction
SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
An append structure in the database table with the new fields.
A subscreen area into the standard screen where the programmer can attach his subscreen of his own program with the new fields.
A function group under which the new subscreen has to be created with the new fields.
Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
Pre-Requisites
The developer to work on screen exit should have essential knowledge on the following:
DDIC concepts, including the knowledge of append structure.
Concept of SAP Enhancements and implementing them using Projects.
Concept of function exits.
Knowledge on Module Pool including subscreens, Tabstrip controls etc.
Steps
Guidelines
So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
Find out the Required Enhancements
Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton SAP Applications. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest for e.g., Purchasing, Asset Accounting, etc.
Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
Utilize the Enhancement in a Project
After you have found one, do as directed in the documentation. Generally, the steps are as follows:
Create a project using CMOD including your enhancement.
Create the append structure with new fields.
Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
Activate the project.
Test to ensure that required functionality are met.
Case Study 1
Add three new custom fields for Asset master and maintain information for them
Requirement
Three fields in the legacy system have to be maintained in Asset master. These fields are:
Original Asset number 20 characters
Location 2 15 Characters.
Model no 20 characters
Location 2 should start with L.
Pre-Analysis
Finding out the Enhancement
As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
Studying the Function Exits
The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
EXIT_SAPLAIST_002
Function module Level Documentation
This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
Import Parameters
Understanding
This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
EXIT_SAPLAIST_003
Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
Understanding
This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
Studying the Documentation of the Enhancement
The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
Deciding the Final course of Action
After making all the investigations, the final course of action was determined.
SrlNo Step Justification
A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be CUST (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
In the PAI of the subscreen, validation for Location to start with L will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
In the custom include of the function exit module EXIT_SAPLAIST_002, the following code will be written:-
ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
In the custom include of the function exit module EXIT_SAPLAIST_003, the following code will be written:-
E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done otherwise, the new custom subscreen will not be displayed in the Asset master screens.
Development
Creating a Project to include the enhancement
Go to transaction CMOD and create a project.
Enter a description for the project. Then, click on the pushbutton Enhancement Assignments in the Application Toolbar.
Enter the name of the enhancement and Save.
Go to Components.
Creating Custom Include for ANLU
The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
Create the include structure with three new fields, as required. Then, save and activate it.
Develop the subscreen and the program
Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
Create it as subscreen.
Then, go to the Layout of the screen and create three new fields from Database table ANLU.
Drag the fields in the screen body and place them.
Then, save and activate the screen and come back to screen flow editor.
Create the PAI module to add validation for field Location 2, as required .
Activate the whole function group and come out.
Write code in the Function Exits to synchronize the programs
Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
Then, activate everything the whole project and come out.
Complete the configuration to link the subscreen
The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
Here, the requirement is to create these three custom fields in the tab page General of asset master screen ( AS01/AS02/AS03/AS91).
Determine the Layout
To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class 1000 and click on folder General Assignment of Layout.
Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout SAP cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
Create new tab layout
Go to transaction AOLA. Copy the tab layout SAP to create another layout, say, YSUB.
System will copy all the settings and will inform you about that.
Select your newly created layout and double-click on the folder Tab page titles.
You want to put your custom fields in the tab page General. So, select this tab page entry and double-click on the folder "Position of Groups".
Here, all the field groups currently residing in the tab-page General are shown. Add an entry for your newly created fields.
Select the group box from the list. An entry will come with U padded with the custom subscreen prepared by you.
Then, save and come out.
Assign the new Layout to Asset Class
Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
Save and come out.
Test the Exit
Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to themsave. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
Original Source: ittoolbox.com
Screen Exit is nothing but enhancing the screen like creating some more fields, subscreen and so on.
1. Go to the screen>System>Status-->Program (Double
click this program. It will take you to the program.
2. Now, Goto-->Object Directory Entry.
3. Make a note the package name.
4. Now run the transactions SMOD, press F4 and enter the
above noted package, press enter.
5. It will display list of Exits.
6. Now go back to the initial screen SMOD.
7. Specify the exit name here and select the radio button
Components.
8. It will display four group boxes one for FM, second
for Fcodes, thrid for Screen areas and last for
includes.
9. Goto transaction CMOD, create a new project, and
click the button "Enhancement assignments" and
specify your enhancements that you got in SMOD.
10. Now bouble clikc the enhancement, it will take you to editor with some includes starting with Z, double clikc the include you want to edit and proceed.
and you just go through these links also
Screen exit
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
screen-exits
Check the following link.
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=how%20to%20find%20screen%20exits&cat=sdn_all
Reward points if useful
Regards
Anji

Screen exits on Notification level

Can any one let me know the screen exits at notification level....
kindly refer my Enhancements ... points will be given for valid or
useful reply....

Hi,
Screen Exit is nothing but enhancing the screen like creating some more fields, subscreen and so on.
1. Go to the screen>System>Status-->Program (Double
click this program. It will take you to the program.
2. Now, Goto-->Object Directory Entry.
3. Make a note the package name.
4. Now run the transactions SMOD, press F4 and enter the
above noted package, press enter.
5. It will display list of Exits.
6. Now go back to the initial screen SMOD.
7. Specify the exit name here and select the radio button
Components.
8. It will display four group boxes one for FM, second
for Fcodes, thrid for Screen areas and last for
includes.
9. Goto transaction CMOD, create a new project, and
click the button "Enhancement assignments" and
specify your enhancements that you got in SMOD.
10. Now bouble clikc the enhancement, it will take you to editor with some includes starting with Z, double clikc the include you want to edit and proceed.
and you just go through these links also
Screen exit
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
screen-exits
check this Link
http://www.sapbrain.com/TUTORIALS/TECHNICAL/user_exits_tutorial.html
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
check this http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
Regards,
Deepu.K

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

Which category screen exits and function exit come

Hi ,
I have created an enhancement in ECC 6.0 system on screen exit and function exit for LM00 tcode. now i want to update my developed object in Solution manager.
Anyone pls help me under which category this enhancement project falls.

Thanks everyone for the prompt response.
The scenario is thet I have 190 CMOD projects and I needa quick way to find out which of the function exits in the CMOD projects have been implemented and which are the Z includes in these implemented function exits.
Doing it one-by-one would take too much time. TADIR does not give the function exits and the includes in them.
Need a quick way of identifying the implemented function exits, and the includes in the function exits, from the CMOD project name.
Peter

Screen exits in va01

as this is a urgent req. pls can any one suggest what r the diff. screen exits in va01 tcode and how ton find them.
thanx and regards

hi
you can check the same with this report program. execute it, enter your transaction for which you require enhancement then press f8. It would display all the available exits...
*& Report ZFINDUSEREXIT
REPORT ZFINDUSEREXIT.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
select single * from tadir where pgmid = 'R3TR'
and object = 'PROG'
and obj_name = tstc-pgmna.
move : tadir-devclass to v_devclass.
if sy-subrc ne 0.
select single * from trdir where name = tstc-pgmna.
if trdir-subc eq 'F'.
select single * from tfdir where pname = tstc-pgmna.
select single * from enlfdir where funcname =
tfdir-funcname.
select single * from tadir where pgmid = 'R3TR'
and object = 'FUGR'
and obj_name eq enlfdir-area.
move : tadir-devclass to v_devclass.
endif.
endif.
select * from tadir into table jtab
where pgmid = 'R3TR'
and object = 'SMOD'
and devclass = v_devclass.
select single * from tstct where sprsl eq sy-langu and
tcode eq p_tcode.
format color col_positive intensified off.
write:/(19) 'Transaction Code - ',
20(20) p_tcode,
45(50) tstct-ttext.
skip.
if not jtab[] is initial.
write:/(95) sy-uline.
format color col_heading intensified on.
write:/1 sy-vline,
2 'Exit Name',
21 sy-vline ,
22 'Description',
95 sy-vline.
write:/(95) sy-uline.
loop at jtab.
select single * from modsapt
where sprsl = sy-langu and
name = jtab-obj_name.
format color col_normal intensified off.
write:/1 sy-vline,
2 jtab-obj_name hotspot on,
21 sy-vline ,
22 modsapt-modtext,
95 sy-vline.
endloop.
write:/(95) sy-uline.
describe table jtab.
skip.
format color col_total intensified on.
write:/ 'No of Exits:' , sy-tfill.
else.
format color col_negative intensified on.
write:/(95) 'No User Exit exists'.
endif.
else.
format color col_negative intensified on.
write:/(95) 'Transaction Code Does Not Exist'.
endif.
at line-selection.
get cursor field field1.
check field1(4) eq 'JTAB'.
set parameter id 'MON' field sy-lisel+1(10).
please reward if useful...
regards
dinesh

Screen Exit for LT12

Hi Folks,
I need a help regarding Screen Exit for LT12 Tcod.My requirement is to add a screen for Serial Number Keyin for a material and confirm the TO.I try to find an Exit and a Badi where i can put my Custom logic which updats the Serial Number in a Custom 'Z' Table but iam unable to stop at none of the exits .Please help me if any one had worked on this sort of an requirement. I want an Exit/Badi which stops at the time of Save or Confirm TO Ok_code

hi vamsi,
check the below link may be helpful for you
User-Exit in transaction LT12
if u find it useful plz reward the points
Regards,
Naveen

P.O change if i change only screen exit field the data is not saving

Hi ,
In the purchase order header custom tab i am added a screen exit field .In the purchase order creation mode the screen exit field is saving.But in the change mode if i am changing only the screen exit field then it is showing as 'no data to save' and not saving .But at the same time if i am changing some standard field with the screen exit field then both the field is saving.
I have to activate any field to save the screen exit field.Please let me know any exit to be activated for saving the data.
With Regards,
Ambrose

Hi
Pls keep a break-point in the PAI of Screen exit and check, whether it stops in change mode
Regards
Madhan D

Stop Web Object audio on screen exit - Cap 7

Similar Messages

Maybe you are looking for