Menu Exit Code
Hello All,
I wanted a Menu Item in the SAP Standard Menu Bar.
i.e the SYSTEM, HELP menu .
So, for the above I went to the Screen Painter SE41--> Program --> MENUSYST --> Status > MEN> Change .
Here under the Help Menu - I added one more item with Text TEST and Function Code as HELP_1.
Now I found out the Enhancements for this by going to the SMOD and the enhancement is : SEUMP002
Now I created a project in CMOD (ZHELP) and I mentioned the enhancement SEUMP002 in it and activated it.
Now when I see the HELP Menu Items I can see the TEST menu item in the active mode.
Now to write the functionality of the TEST with function code HELP_1 i used the enhancements :
EXIT_SAPLSMPE_001
EXIT_SAPMSMPE_001.
In that there is a Z include INCLUDE ZXseuu13.Here I kept a breakpoint to chk whether it is getting triggered or not.
But it's not stopping when I press the TEST MEnu Item.
Can u guys tell me wht to do to trigger the functionality of the TEST Menu Item ?
Regards,
Deepu.K
Hello ,
I did that !
I've written the following code in the Z INclude :
IF sy-uname = 'MY USER NAME'.
BREAK-POINT.
ENDIF.
I also have activated the project.
Any other clues ????
Regards,
Deepu.K
Similar Messages
-
Error ! No field defined for function Code in MENU EXIT
Hello All,
I've created a project in CMOD for the MENU EXIT for handling one menu item in the SAP Standard Menu Bar .
i.e under the HELP MENU Item I've included one more sub menu item.
I've activated the project and I'm able to se the newly added Sub-Menu Item in the activated mode.
But when I press the newly created Sub Menu Item I'm getting a Message in the Status Bar saying :
No field defined for the function code
The Help of it says :
Message no. 00125
Diagnosis
The function code field (OK code field) has not been defined on this screen. If the user selects an application function (not a system function), the system usually provides it in the function code field (OK code field) as well as in SY-UCOMM. This is no longer possible.
System Response
The system is unable to inform the application of the current function code. The application should not use field SY_COMM. This field always contains the code of the last function chosen, which is not always identical to the application-relevant code.
Procedure
You should always define a field for the function code on every screen. The Screen Painter always proposes such a field (OK category), you only need to assign a name and include the definition in the ABAP program.
Please let me know what shud be done ?
Regards,
Deepu.KDon't use this scanrio ! Instead got Access Key and chamged the Std. Program.
-
Need Menu Exit for T-Code ME32K in ECC
Hello,
I need Menu Exit for Transaction ME32K in ECC version, It would be helpful if any one could tell me,
Deserving answer will be rewarded points
Regards
Rajeshhi
use this program to search for the BADIS and enhancements
& 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 -
Problem in writing a code MENU EXIT.. it is asking for access key.
Hi,
I have a problem in creating a menu exit.
while am creating a menu exit i went to CUS to write code but it is asking for Access Key..
could anybody help me regarding this..??
Thank you,
Praveen Dubasi.Is the address on your iTunes account exactly the same (format and spacing etc) as on your credit card bill : http://support.apple.com/kb/TS1646 ? If it is then you could try what it says at the bottom of that page :
If the issue persists, contact your credit card company and verify that they and any company they use to process credit card authorisations have the correct information on file.
And/or try contacting iTunes support : http://www.apple.com/support/itunes/contact/ - click on Express Lane, then iTunes > iTunes Store -
Error while running a OA framework Page Process exited with exit code 1.
Hi all,
I downloaded the Patch 4573517 from Metalink for JDEV with OA extension release 11i.I followed all the instruction of the setup init and installed the Jdev,also mytutorial pages got compiled successfully,but when i trie dto run the page
Run > Run test_fwktutorial.jsp from the main menu.
it gives me error.The error is as follows
[Starting OC4J using the following ports: HTTP=8988, RMI=23891, JMS=9227.]
C:\D drive\OA_2008\jdevbin\jdk\bin\javaw.exe -client -classpath C:\D drive\OA_2008\jdevbin\j2ee\home\oc4j.jar;C:\D drive\OA_2008\jdevbin\jdev\lib\jdev-oc4j.jar -Xbootclasspath/p:C:\D drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip -DFND_JDBC_STMT_CACHE_SIZE=200 -DCACHENODBINIT=true -DRUN_FROM_JDEV=true -mx256m -Doracle.j2ee.dont.use.memory.archive=false -Xverify:none -Doracle.j2ee.dont.use.memory.archive=true -Doracle.j2ee.http.socket.timeout=500 com.evermind.server.OC4JServer -config C:\D drive\OA_2008\jdevhome\jdev\system9.0.3.5.1437\oc4j-config\server.xml
[waiting for the server to complete its initialization...]
java.lang.NoClassDefFoundError: drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14/jar;C:\D
Exception in thread "main"
Process exited with exit code 1.
I am not understanding why it is going in exception.One reason which i doubthere is the line
java.lang.NoClassDefFoundError: drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14/jar;C:\D
here in this line the last word is ojdbc14/jar,i think it should have been ojdbc14.jar.
Can any body please help me out on how to correct this problem.Thanks
ManishManish,
You should ask on the OA Framework Forum.
john -
How to add function key to a menu exit in a standard transaction
Hi all,
I have a requirement to add a function key for a menu item in a standard transaction.
In Menu bar we have an option Extras->Other->Repricing . Now my requirement is if i click a function key (ex. F9) the code under the menu exit (Repricing) should trigger. For that i had a function exit EXIT_SAPLJHPA_011 and in this the menu exit SAPLJHPA +CU7 is defined.could anyone suggest me the procedure in detail to add a function key..
Thanks in advance,
Uday.Hi
for this u have to edit standard PF-status, that particular transaction is using. becarefull as the same pf-status may be used for many programs.
get the PF-status for that program. you can get the pf-status via se80, give the program name and u can get the the list of all the objects of that prigram, there you can edit the standard status and can add the function key to your menu item. -
HELP!! Process exited with exit code 128.
Hi all,
I am using JDeveloper 10G to develop a struts project. I use the struts-tiles.tld to construct the layout.
<tiles:insert page="classicLayout.jsp" flush="true">
<tiles:put name="title" value="User and Assigned Role" />
<tiles:put name="header" value="menuTemplate.jsp" />
<tiles:put name="menu" value="TestPoint.jsp" />
<tiles:put name="body" value="ARM001800.jsp" />
<tiles:put name="footer" value="DebugPage.jsp" />
</tiles:insert>
However, when I run the project, then the OC4J Server terminated with this error code : Process exited with exit code 128.
What happen??
PS: I tried to remove the last 2 tags: body and footer. The Server did not terminate, but with some exceptions which related to tiles library.This type of error may occur because of developers mistake.
This error occurs when any function is called recursively in a loop.
The server calls the same function again and again in a loop and hence the server goes in infinite loop. This gives the error "Process exited with exit code 128".
You need to check your code thoroughly for such mistake.
Nital.
i-engineering.com -
Cannot install Illustrator CS5.5 on Windows 7 64-bit Enterprise - (Exit Code: 7)
I am able to install the rest of the CS5.5 Master collection without any issues, but I receive the following error message when trying to install Illustrator:
Exit Code: 7
-------------------------------------- Summary --------------------------------------
- 1 fatal error(s), 2 error(s), 3 warning(s)
WARNING: DW031: Payload:{2EBE92C3-F9D8-48B5-A32B-04FA5D1709FA} Adobe XMP Panels CS5 3.0.0.0 has been updated and has been selected for repair. The patch {42774483-D33C-46F7-8B20-FD0B1A3DAC25} Adobe XMP Panels CS5_3.1_AdobeXMPPanelsAll 3.1.0.0 will be uninstalled now.
WARNING: DW031: Payload:{3F023875-4A52-4605-9DB6-A88D4A813E8D} Camera Profiles Installer 6.0.0.0 has been updated and has been selected for repair. The patch {A189C479-C7CD-4E08-8CCF-D999B68C0C71} Camera Profiles Installer_6.3_AdobeCameraRawProfile6.0All 6.3.0.0 will be uninstalled now.
WARNING: DW031: Payload:{37AB3C65-E02C-4DCF-B0E0-4C2E253D8FA3} Photoshop Camera Raw 6.0.0.0 has been updated and has been selected for repair. The patch {FD58D99B-9927-4226-8E00-959A4F76BD89} Photoshop Camera Raw_6.3_AdobeCameraRaw6.0All 6.3.0.0 will be uninstalled now.
ERROR: DW020: Found payload conflicts and errors:
ERROR: DW020: - Adobe Flash CS5.5 depends on Adobe Flash Player 10 ActiveX to be installed.
FATAL: DW020: Conflicts were found in the selected payloads. Halting installation.
I have tried uninstalling the entire Master Collection Suite via the control panel and using the CS5InstallerDatabaseUtility.exe (Clean up script) which completed with errors:
[Tue Jun 24 10:29:13 2014] ---------------------------------------------------------
[Tue Jun 24 10:29:13 2014] *=*=*=*=*=*=*=*=* :: Start Session :: *=*=*=*=*=*=*=*=*=*
[Tue Jun 24 10:29:13 2014] ---------------------------------------------------------
[Tue Jun 24 10:29:13 2014] Win OS Version: 6.1
[Tue Jun 24 10:29:13 2014] Cleaner Tool version : 3.0.0.37
[Tue Jun 24 10:29:13 2014] Cleanup source directory : E:\Software\AdobeRemover
[Tue Jun 24 10:29:13 2014] [AdobeProgramFiles] : C:\Program Files (x86)\Adobe
[Tue Jun 24 10:29:13 2014] [AdobeProgramFiles_x64] : C:\Program Files\Adobe
[Tue Jun 24 10:29:13 2014] [AdobeCommon] : C:\Program Files (x86)\Common Files\Adobe
[Tue Jun 24 10:29:13 2014] [AdobeCommon_x64] : C:\Program Files\Common Files\Adobe
[Tue Jun 24 10:29:13 2014] [UserRoamingAppData] : C:\Users\oc-jjust17\AppData\Roaming
[Tue Jun 24 10:29:13 2014] [UserLocalAppData] : C:\Users\oc-jjust17\AppData\Local
[Tue Jun 24 10:29:13 2014] [StartMenu] : C:\ProgramData\Microsoft\Windows\Start Menu\Programs
[Tue Jun 24 10:29:13 2014] [System32Folder] : C:\windows\system32
[Tue Jun 24 10:29:13 2014] [SharedApplicationData] : C:\ProgramData
[Tue Jun 24 10:29:17 2014] Language selected: English
[Tue Jun 24 10:29:17 2014] Displaying the Adobe End User License Agreement
[Tue Jun 24 10:29:17 2014] Please enter (y) for Yes or (n) for No.
[Tue Jun 24 10:29:23 2014] Choose any one from the options below :
[Tue Jun 24 10:29:23 2014] 1. CS3, CS4
[Tue Jun 24 10:29:23 2014] 2. CS5
[Tue Jun 24 10:29:23 2014] 3. Flash Player
[Tue Jun 24 10:29:23 2014] 4. Quit
[Tue Jun 24 10:29:23 2014] Choice :>
[Tue Jun 24 10:29:31 2014] User selected: CS5
[Tue Jun 24 10:29:31 2014] Executed the command : call copy /Y "C:\Program Files (x86)\Common Files\Adobe\caps\pdb.db" "C:\Program Files (x86)\Common Files\Adobe\backup20140624T102931\pdb.db"
[Tue Jun 24 10:29:31 2014] Executed the command : call copy /Y "C:\Program Files (x86)\Common Files\Adobe\caps\Media_db.db" "C:\Program Files (x86)\Common Files\Adobe\backup20140624T102931\Media_db.db"
[Tue Jun 24 10:29:31 2014] Opened PDB database connection with path: C:\Program Files (x86)\Common Files\Adobe\caps\pdb.db
[Tue Jun 24 10:29:31 2014] Opened MediaDB database connection with path: C:\Program Files (x86)\Common Files\Adobe\caps\Media_db.db
[Tue Jun 24 10:29:31 2014] List of products installed on this machine
[Tue Jun 24 10:29:31 2014] Listing products for cleanup:
[Tue Jun 24 10:29:31 2014] Please select a number corresponding to the product that needs to be removed else press Ctrl + C to Quit :>
[Tue Jun 24 10:29:40 2014] User selected: 'Clean All'
[Tue Jun 24 10:29:40 2014] WARNING : All the CS5 products and installer related data will be REMOVED from the machine. Do you want to continue..
[Tue Jun 24 10:29:40 2014] Please enter (y) for Yes or (n) for No. :>
[Tue Jun 24 10:29:46 2014] Please wait for Cleaner tool to finish........
[Tue Jun 24 10:29:46 2014] *-*-*-*-*-*-* Start removing product : ALL *-*-*-*-*-*-*
[Tue Jun 24 10:29:46 2014] :: Cleaning-up left over inventories ::
[Tue Jun 24 10:29:46 2014] Inventory: 'AdobeApplicationManager-1.0' Type: SelfUpdate, Action: NoDelete
[Tue Jun 24 10:29:46 2014] Inventory: 'uninstallts', Type: RIBS, Action: Delete
[Tue Jun 24 10:29:46 2014] Deleting folder: C:\Program Files (x86)\Common Files\Adobe\AAMUpdaterInventory\1.0\uninstallts
[Tue Jun 24 10:29:46 2014] ERROR: Exception while removing folder. Ensure files/folder exists and are not locked; then manually remove: C:\Program Files (x86)\Common Files\Adobe\AAMUpdaterInventory\1.0\uninstallts
[Tue Jun 24 10:29:46 2014] Atleast one Non-RIBS Inventory : False, Atleast one AAMRef: False
[Tue Jun 24 10:29:46 2014] ::Start:: Removing AUM contents
[Tue Jun 24 10:29:46 2014] Deleting registry root:HKLM key:Software\Microsoft\Windows\CurrentVersion\Run value:AdobeAAMUpdater-1.0
[Tue Jun 24 10:29:46 2014] Exception during deleting key : (2, 'RegDeleteValue', 'The system cannot find the file specified.')
[Tue Jun 24 10:29:46 2014] Deleting registry root:HKLM key:Software\Microsoft\Windows\CurrentVersion\Run value:ADOBE_UPDATER_STARTUP_UTILITY
[Tue Jun 24 10:29:46 2014] Exception during deleting key : (2, 'RegDeleteValue', 'The system cannot find the file specified.')
[Tue Jun 24 10:29:46 2014] Deleting scheduled task : AdobeAAMUpdater-1.0-GBN-oc-jjust17
[Tue Jun 24 10:29:46 2014] Executing command: schtasks /delete /TN "AdobeAAMUpdater-1.0-GBN-oc-jjust17" /F
[Tue Jun 24 10:29:47 2014] ERROR: The system cannot find the file specified.
[Tue Jun 24 10:29:47 2014] Deleting scheduled task : AdobeUpdater Task-GBN-oc-jjust17
[Tue Jun 24 10:29:47 2014] Executing command: schtasks /delete /TN "AdobeUpdater Task-GBN-oc-jjust17" /F
[Tue Jun 24 10:29:47 2014] ERROR: The system cannot find the file specified.
[Tue Jun 24 10:29:47 2014] Deleting folder: C:\Users\oc-jjust17\AppData\Local/Adobe/AAMUpdater/1.0
[Tue Jun 24 10:29:47 2014] ::Finish:: Removing AUM contents
[Tue Jun 24 10:29:47 2014] ::Start:: Removing OOBE
[Tue Jun 24 10:29:47 2014] Executing command "taskkill /F /FI "IMAGENAME eq AAM Updates Notifier.exe""
[Tue Jun 24 10:29:47 2014] INFO: No tasks running with the specified criteria.
[Tue Jun 24 10:29:47 2014] Deleting folder: C:\Program Files (x86)\Common Files\Adobe/OOBE
[Tue Jun 24 10:29:47 2014] Deleting folder: C:\Program Files (x86)\Common Files\Adobe/AAMUpdaterInventory/1.0
[Tue Jun 24 10:29:47 2014] Folder does not exist: C:\Program Files (x86)\Common Files\Adobe/AdobeApplicationManager
[Tue Jun 24 10:29:47 2014] ::Finish:: Removing OOBE
[Tue Jun 24 10:29:47 2014] Removing content of Product : CS5Installer, Version : CS5
[Tue Jun 24 10:29:47 2014] Deleting file : C:\Program Files (x86)\Common Files\Adobe\caps\pdb.db
[Tue Jun 24 10:29:47 2014] Deleting file : C:\Program Files (x86)\Common Files\Adobe\caps\Media_db.db
[Tue Jun 24 10:29:47 2014] Folder does not exist: C:\Users\oc-jjust17\AppData\Local\Adobe\OOBE
[Tue Jun 24 10:29:47 2014] Folder does not exist: C:\ProgramData\Adobe\SLStore_v1
[Tue Jun 24 10:29:47 2014] Folder does not exist: C:\Users\oc-jjust17\AppData\Local\Adobe\AAMUpdater\1.0
[Tue Jun 24 10:29:47 2014] *-*-*-*-*-*-* Finished removing product : ALL *-*-*-*-*-*-*
[Tue Jun 24 10:29:47 2014] All the CS5 products and CSInstaller files have been removed.
[Tue Jun 24 10:29:47 2014] Action : Created the C:\Program Files (x86)\Common Files\Adobe\backup20140624T102931 folder as backup of PDB and MediaDB for this session.
[Tue Jun 24 10:29:47 2014] LOG FILE SAVED TO: C:\Users\oc-jjust17\Adobe CS5 Cleaner Tool.log
[Tue Jun 24 10:29:47 2014] Cleanup Script Completed With ERRORS!
[Tue Jun 24 10:29:47 2014] Check the end of the log file for list of errors
[Tue Jun 24 10:29:47 2014]
[Tue Jun 24 10:29:47 2014] *-*-*-*-*-*-* ::START:: - SUMMARY OF ERRORS *-*-*-*-*-*-*
[Tue Jun 24 10:29:46 2014] ERROR: Exception while removing folder. Ensure files/folder exists and are not locked; then manually remove: C:\Program Files (x86)\Common Files\Adobe\AAMUpdaterInventory\1.0\uninstallts
[Tue Jun 24 10:29:47 2014] *-*-*-*-*-*-* :: END :: - SUMMARY OF ERRORS *-*-*-*-*-*-*
[Tue Jun 24 10:29:47 2014] ---------------------------------------------------------
[Tue Jun 24 10:29:47 2014] *=*=*=*=*=*=*=*=* :: End Session :: *=*=*=*=*=*=*=*=*=*=*
[Tue Jun 24 10:29:47 2014] ---------------------------------------------------------
Restarted the computer and re-installed the entire Adobe Suite but received the same error message again. Adobe Flash professional runs fine also, so from what I have read at Installation error DW050, DW020 | CS5.5 | Windows the adobe flash player error is irrelevant.Exit Code: 6, Exit Code: 7
Installation Errors - http://helpx.adobe.com/creative-suite/kb/errors-exit-code-6-exit.html
for information on how to review your installation logs - Troubleshoot with install logs | CS5, CS5.5, CS6 -
http://helpx.adobe.com/creative-suite/kb/troubleshoot-install-logs-cs5-cs5.html -
Installed Adobe CS 5.5 Design Premium on new computer... WIN 8.1... get Exit Code 6
Adobe tech support told me phone support for this version is no longer available. I am at your mercy. I would like to try to re-install by shutting down running apps in the System Configuration. and deactivating my anti-virus software. I am unsure what is safe to shut down in the Sys Config. Any help would be appreciated. If someone does not think this method is the way to go, I am open to suggestions.
Thanks!
P.S.
I also ran the Adobe Cleaner application, the result gave me many more errors.
Use the CC Cleaner Tool to solve installation problems | CC, CS3-CS6
Exit Code: 6
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 5 error(s), 54 warning(s)
WARNING: DW066: OS requirements not met for {0D96CFE6-376D-44B8-808A-16F3BEB73263}
WARNING: DW066: OS requirements not met for {7202D4A7-F7E6-4e7a-B77D-7B1C4E8B5CA6}
WARNING: DW066: OS requirements not met for {43A1C48E-3E50-410e-951C-E17A66BBF824}
WARNING: DW066: OS requirements not met for {CE75F5DB-8CA3-4E84-A30E-AF9160006105}
WARNING: DW066: OS requirements not met for {B55FDCCB-8A45-4943-8D90-585C3490A032}
WARNING: DW066: OS requirements not met for {98DD55B6-C58C-462F-B8A4-F0585BFEBB15}
WARNING: DW066: OS requirements not met for {4603E0C5-6880-4A4F-BCF8-DF1F6AE0E317}
WARNING: DW066: OS requirements not met for {EB186BF2-0A84-40A2-B794-0326D3DF9973}
WARNING: DW066: OS requirements not met for {17C6080E-F475-4B49-A30C-EEB85673E999}
WARNING: DW066: OS requirements not met for {9A8B01C5-78D1-465F-B5F6-BD59B7800EC7}
WARNING: DW066: OS requirements not met for {3450d4c5-a82b-4428-a512-842ee1555a14}
WARNING: DW066: OS requirements not met for {61A3D10A-AA4D-4E4C-B9DB-6A08D318EA41}
WARNING: DW066: OS requirements not met for {32841ECE-EC28-42CD-A4DD-6CE832A7EA8D}
WARNING: DW066: OS requirements not met for {0669F23C-1B69-41B4-A3ED-4F54A5986D66}
WARNING: DW066: OS requirements not met for {00AEBAF2-D950-467B-BD24-449BCA2A4424}
WARNING: DW066: OS requirements not met for {FF5837B9-6F4D-1014-B2FA-C016F4A584FA}
WARNING: DW066: OS requirements not met for {F37EA9EC-638F-4E61-BED4-BDB10461D73B}
WARNING: DW066: OS requirements not met for {7745F18B-FD8A-4011-BE16-588900C503D0}
WARNING: DW066: OS requirements not met for {32C78855-194D-4E66-9EB5-D6DC1C418D79}
WARNING: DW066: OS requirements not met for {89823DB1-05CA-1016-BA4A-BE6A29E42461}
WARNING: DW066: OS requirements not met for {4C08199E-0D93-4227-8325-F024E71CA7A1}
WARNING: DW066: OS requirements not met for {BD3F3C6B-5F98-109B-A0CA-B0FAE4A7D983}
WARNING: DW066: OS requirements not met for {301D39AF-43B1-445B-88CF-D78584200322}
WARNING: DW066: OS requirements not met for {07C64F28-6F4E-1014-A82C-D40EE8D79912}
WARNING: DW066: OS requirements not met for {260BF844-6F4D-1014-A611-DFCB82217C38}
WARNING: DW066: OS requirements not met for {11C0657F-2BD4-4CBC-87F3-9455DC91886E}
WARNING: DW066: OS requirements not met for {7F9C94CD-0BAC-4F8F-8990-6A5886F4D550}
WARNING: DW066: OS requirements not met for {4883A813-2805-4FA8-A91C-073BA7B2667A}
WARNING: DW066: OS requirements not met for {9F16123E-05FC-1016-91BC-C090234C0EE3}
WARNING: DW066: OS requirements not met for {6BC81374-1E33-4495-93E2-DD2B10D358EE}
WARNING: DW066: OS requirements not met for {AC76BA86-1033-F400-7760-000000000005}
WARNING: DW066: OS requirements not met for {60E59A6C-7399-495A-B85C-C829F4E59602}
WARNING: DW066: OS requirements not met for {0215A652-E081-4B09-9333-DC85AAB67FFA}
WARNING: DW066: OS requirements not met for {35ED8892-98E5-488A-A23C-6DB842A46EA5}
WARNING: DW066: OS requirements not met for {D8CCCF4C-C227-427C-B4BE-736657D2AB7E}
WARNING: DW066: OS requirements not met for {8DADF070-FE60-4899-8EF0-4242E7702F7D}
WARNING: DW066: OS requirements not met for {1C9D6B02-8B92-4E40-8B22-37D8C95430F0}
WARNING: DW066: OS requirements not met for {23767F5D-A80C-4264-B8EA-ED4085FC332A}
WARNING: DW066: OS requirements not met for {DDBDE7B0-6FC4-40B1-B673-66EEE8CB60CF}
WARNING: DW066: OS requirements not met for {08EF22BC-43B2-4B4E-BA12-52B18F418F38}
WARNING: DW066: OS requirements not met for {EDE888ED-3BD7-4D8C-AB35-7E4C661A94D9}
WARNING: DW066: OS requirements not met for {10355145-8A4C-47F3-994B-B9B81B4DABF5}
WARNING: DW066: OS requirements not met for {F9F276DA-9EC6-492C-AF58-F27C5EC19D66}
WARNING: DW066: OS requirements not met for {D97AF04B-B70A-4862-BC25-31E6D9C4A529}
WARNING: DW066: OS requirements not met for {970C9F3A-39C5-480B-BE51-7C70AB9F84DB}
WARNING: DW066: OS requirements not met for {E348E466-429A-4FB0-AFCF-8306C16BBFF1}
WARNING: DW066: OS requirements not met for {2EA9B52E-8613-41A0-9EEF-FF54AD4CC810}
WARNING: DW066: OS requirements not met for {857CC5F0-040E-1016-A173-D55ADD80C260}
WARNING: DW066: OS requirements not met for {B98CCEE8-0217-1016-B5BF-F06B878DAC9A}
WARNING: DW066: OS requirements not met for {50509A36-0291-1016-9CCF-FC05E9E55550}
----------- Payload: {CFA46C39-C539-4BE9-9364-495003C714AD} Adobe SwitchBoard 2.0 2.0.0.0 -----------
WARNING: DF029: ARKServiceControl::StartService: Service not started/stopped SwitchBoard. Current State: 0 Exit Code: 0 Service Specific Exit Code: 0(Seq 1)
----------- Payload: {2EE4F060-CEE6-4002-AA8B-91B791541767} Pixel Bender Toolkit 2.6.0.0 -----------
WARNING: DF035: CreateAlias:Icon file does not exist at C:\Program Files (x86)\Adobe\Adobe Utilities - CS5.5\Pixel Bender Toolkit 2.6\windows\pb_app.icofile:\\\C:\PIXELB~1\source\winwood\Staging 0X1.CE3E42P-1022rea\windows\pb_app.ico42178f80493091e8e552c84a2897e9da68fce32_32_f8049309 1e8e552c84a2897e9da68fce for icon C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Adobe Design Premium CS5.5\Adobe Pixel Bender Toolkit 2.6.lnk with target C:\Program Files (x86)\Adobe\Adobe Utilities - CS5.5\Pixel Bender Toolkit 2.6\Pixel Bender Toolkit.exe(Seq 89)
----------- Payload: {7202D4A7-F7E6-4e7a-B77D-7B1C4E8B5CA6} Adobe Flash Player 10 ActiveX 10.0.0.0 -----------
ERROR: Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action NewCustomAction1, location: C:\Users\Sharon\AppData\Local\Temp\InstallAX.exe, command: -install activex -msi
ERROR: Install MSI payload failed with error: 1603 - Fatal error during installation.
MSI Error message: Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action NewCustomAction1, location: C:\Users\Sharon\AppData\Local\Temp\InstallAX.exe, command: -install activex -msi
----------- Payload: {8DADF070-FE60-4899-8EF0-4242E7702F7D} Adobe Fireworks CS5.1 11.1.0.0 -----------
WARNING: DF012: File/Folder does not exist at D:\Adobe CS5_5\payloads\AdobeFireworks11.1.0All\OEM(Seq 1215)
----------- Payload: {1C9D6B02-8B92-4E40-8B22-37D8C95430F0} Adobe Fireworks CS5.1_AdobeFireworks11.1.0en_USLanguagePack 11.1.0.0 -----------
WARNING: DF012: File/Folder does not exist at D:\Adobe CS5_5\payloads\AdobeFireworks11.1.0en_USLanguagePack\OEM(Seq 74)
----------- Payload: {D97AF04B-B70A-4862-BC25-31E6D9C4A529} Adobe Flash CS5.5 11.5.0.0 -----------
ERROR: DR012: Setting Registry Value Failed. Error 5 Access is denied.(Seq 154)
ERROR: DW050: The following payload errors were found during install:
ERROR: DW050: - Adobe Flash Player 10 ActiveX: Install failedThank you Psynikk, I followed the instructions to the link you provided, Solutions 1, same result, exit code 6. I did not follow through with the remaining solutions, as I do not feel confident in messing with the configurations of my computer since the solutions are not for Windows 8.1. It is unfortunate that I won't be able to use this product fully. I am discouraged to invest my dollars in any more Adobe suites.
(This issue also occurred when I had it installed on my Vista system (exit code 7), back then Adobe Support assisted over the phone to fix the problem)
If anyone has any information that pertains to Windows 8.1 to further fix this issue I would welcome the resolution.
Exit Code: 6
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 8 error(s), 53 warning(s)
WARNING: DW066: OS requirements not met for {0D96CFE6-376D-44B8-808A-16F3BEB73263}
WARNING: DW066: OS requirements not met for {7202D4A7-F7E6-4e7a-B77D-7B1C4E8B5CA6}
WARNING: DW066: OS requirements not met for {43A1C48E-3E50-410e-951C-E17A66BBF824}
WARNING: DW066: OS requirements not met for {CE75F5DB-8CA3-4E84-A30E-AF9160006105}
WARNING: DW066: OS requirements not met for {B55FDCCB-8A45-4943-8D90-585C3490A032}
WARNING: DW066: OS requirements not met for {98DD55B6-C58C-462F-B8A4-F0585BFEBB15}
WARNING: DW066: OS requirements not met for {4603E0C5-6880-4A4F-BCF8-DF1F6AE0E317}
WARNING: DW066: OS requirements not met for {EB186BF2-0A84-40A2-B794-0326D3DF9973}
WARNING: DW066: OS requirements not met for {17C6080E-F475-4B49-A30C-EEB85673E999}
WARNING: DW066: OS requirements not met for {9A8B01C5-78D1-465F-B5F6-BD59B7800EC7}
WARNING: DW066: OS requirements not met for {3450d4c5-a82b-4428-a512-842ee1555a14}
WARNING: DW066: OS requirements not met for {61A3D10A-AA4D-4E4C-B9DB-6A08D318EA41}
WARNING: DW066: OS requirements not met for {32841ECE-EC28-42CD-A4DD-6CE832A7EA8D}
WARNING: DW066: OS requirements not met for {0669F23C-1B69-41B4-A3ED-4F54A5986D66}
WARNING: DW066: OS requirements not met for {00AEBAF2-D950-467B-BD24-449BCA2A4424}
WARNING: DW066: OS requirements not met for {FF5837B9-6F4D-1014-B2FA-C016F4A584FA}
WARNING: DW066: OS requirements not met for {F37EA9EC-638F-4E61-BED4-BDB10461D73B}
WARNING: DW066: OS requirements not met for {7745F18B-FD8A-4011-BE16-588900C503D0}
WARNING: DW066: OS requirements not met for {32C78855-194D-4E66-9EB5-D6DC1C418D79}
WARNING: DW066: OS requirements not met for {89823DB1-05CA-1016-BA4A-BE6A29E42461}
WARNING: DW066: OS requirements not met for {4C08199E-0D93-4227-8325-F024E71CA7A1}
WARNING: DW066: OS requirements not met for {BD3F3C6B-5F98-109B-A0CA-B0FAE4A7D983}
WARNING: DW066: OS requirements not met for {301D39AF-43B1-445B-88CF-D78584200322}
WARNING: DW066: OS requirements not met for {07C64F28-6F4E-1014-A82C-D40EE8D79912}
WARNING: DW066: OS requirements not met for {260BF844-6F4D-1014-A611-DFCB82217C38}
WARNING: DW066: OS requirements not met for {11C0657F-2BD4-4CBC-87F3-9455DC91886E}
WARNING: DW066: OS requirements not met for {7F9C94CD-0BAC-4F8F-8990-6A5886F4D550}
WARNING: DW066: OS requirements not met for {4883A813-2805-4FA8-A91C-073BA7B2667A}
WARNING: DW066: OS requirements not met for {9F16123E-05FC-1016-91BC-C090234C0EE3}
WARNING: DW066: OS requirements not met for {AC76BA86-1033-F400-7760-000000000005}
WARNING: DW066: OS requirements not met for {60E59A6C-7399-495A-B85C-C829F4E59602}
WARNING: DW066: OS requirements not met for {0215A652-E081-4B09-9333-DC85AAB67FFA}
WARNING: DW066: OS requirements not met for {35ED8892-98E5-488A-A23C-6DB842A46EA5}
WARNING: DW066: OS requirements not met for {D8CCCF4C-C227-427C-B4BE-736657D2AB7E}
WARNING: DW066: OS requirements not met for {8DADF070-FE60-4899-8EF0-4242E7702F7D}
WARNING: DW066: OS requirements not met for {1C9D6B02-8B92-4E40-8B22-37D8C95430F0}
WARNING: DW066: OS requirements not met for {23767F5D-A80C-4264-B8EA-ED4085FC332A}
WARNING: DW066: OS requirements not met for {DDBDE7B0-6FC4-40B1-B673-66EEE8CB60CF}
WARNING: DW066: OS requirements not met for {08EF22BC-43B2-4B4E-BA12-52B18F418F38}
WARNING: DW066: OS requirements not met for {EDE888ED-3BD7-4D8C-AB35-7E4C661A94D9}
WARNING: DW066: OS requirements not met for {10355145-8A4C-47F3-994B-B9B81B4DABF5}
WARNING: DW066: OS requirements not met for {F9F276DA-9EC6-492C-AF58-F27C5EC19D66}
WARNING: DW066: OS requirements not met for {D97AF04B-B70A-4862-BC25-31E6D9C4A529}
WARNING: DW066: OS requirements not met for {970C9F3A-39C5-480B-BE51-7C70AB9F84DB}
WARNING: DW066: OS requirements not met for {E348E466-429A-4FB0-AFCF-8306C16BBFF1}
WARNING: DW066: OS requirements not met for {2EA9B52E-8613-41A0-9EEF-FF54AD4CC810}
WARNING: DW066: OS requirements not met for {857CC5F0-040E-1016-A173-D55ADD80C260}
WARNING: DW066: OS requirements not met for {B98CCEE8-0217-1016-B5BF-F06B878DAC9A}
WARNING: DW066: OS requirements not met for {50509A36-0291-1016-9CCF-FC05E9E55550}
----------- Payload: {CFA46C39-C539-4BE9-9364-495003C714AD} Adobe SwitchBoard 2.0 2.0.0.0 -----------
WARNING: DF029: ARKServiceControl::StartService: Service not started/stopped SwitchBoard. Current State: 0 Exit Code: 0 Service Specific Exit Code: 0(Seq 1)
----------- Payload: {2EE4F060-CEE6-4002-AA8B-91B791541767} Pixel Bender Toolkit 2.6.0.0 -----------
WARNING: DF035: CreateAlias:Icon file does not exist at C:\Program Files (x86)\Adobe\Adobe Utilities - CS5.5\Pixel Bender Toolkit 2.6\windows\pb_app.icofile:\\\C:\PIXELB~1\source\winwood\Staging 0X1.CE8800P-1008rea\windows\pb_app.ico42178f80493091e8e552c84a2897e9da68fce32_32_f8049309 1e8e552c84a2897e9da68fce for icon C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Adobe Design Premium CS5.5\Adobe Pixel Bender Toolkit 2.6.lnk with target C:\Program Files (x86)\Adobe\Adobe Utilities - CS5.5\Pixel Bender Toolkit 2.6\Pixel Bender Toolkit.exe(Seq 89)
----------- Payload: {7202D4A7-F7E6-4e7a-B77D-7B1C4E8B5CA6} Adobe Flash Player 10 ActiveX 10.0.0.0 -----------
ERROR: Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action NewCustomAction1, location: C:\Users\Sharon\AppData\Local\Temp\InstallAX.exe, command: -install activex -msi
ERROR: Install MSI payload failed with error: 1603 - Fatal error during installation.
MSI Error message: Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action NewCustomAction1, location: C:\Users\Sharon\AppData\Local\Temp\InstallAX.exe, command: -install activex -msi
----------- Payload: {43A1C48E-3E50-410e-951C-E17A66BBF824} Adobe Flash Player 10 Plugin 10.0.0.0 -----------
ERROR: Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action NewCustomAction1, location: C:\Users\Sharon\AppData\Local\Temp\InstallPlugin.exe, command: -install plugin -msi
ERROR: Install MSI payload failed with error: 1603 - Fatal error during installation.
MSI Error message: Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action NewCustomAction1, location: C:\Users\Sharon\AppData\Local\Temp\InstallPlugin.exe, command: -install plugin -msi
----------- Payload: {8DADF070-FE60-4899-8EF0-4242E7702F7D} Adobe Fireworks CS5.1 11.1.0.0 -----------
WARNING: DF012: File/Folder does not exist at D:\Adobe CS5_5\payloads\AdobeFireworks11.1.0All\OEM(Seq 1215)
----------- Payload: {1C9D6B02-8B92-4E40-8B22-37D8C95430F0} Adobe Fireworks CS5.1_AdobeFireworks11.1.0en_USLanguagePack 11.1.0.0 -----------
WARNING: DF012: File/Folder does not exist at D:\Adobe CS5_5\payloads\AdobeFireworks11.1.0en_USLanguagePack\OEM(Seq 74)
----------- Payload: {D97AF04B-B70A-4862-BC25-31E6D9C4A529} Adobe Flash CS5.5 11.5.0.0 -----------
ERROR: DR012: Setting Registry Value Failed. Error 5 Access is denied.(Seq 154)
ERROR: DW050: The following payload errors were found during install:
ERROR: DW050: - Adobe Flash Player 10 Plugin: Install failed
ERROR: DW050: - Adobe Flash Player 10 ActiveX: Install failed -
Query on using Screen exits & Menu Exits
Hi Group,
I was trying to make changes to Screen and also adding Menus to the standard transactions.
I went through some sites like <b>SAP Help and SAP Development</b>. But, they were giving info on how to create the things and not giving any sample example for creating things.
So please kindly provide some <b>useful examples</b> on creating the above <b>Screen & Menu Exits</b>.
thanks in advance.
Regards,
Vishnu.So here is an example to Modifying Standard SAP System and help Menu options.
Use Menu Painter (Transaction SE41), enter program MENUSYST, status MEN and click change.
Modify SAP Standard by adding function codes.
add the 'NEW1' fuction code just for example. u can add any no of fuction keys and lastly.
For each of the function codes click on Extras and choose Active functions in multiple statuses.
Thanks and regards,
Pavan
Thanks and regards,
Pavan -
Exit Code: 6 - 0 fatal error(s), 58 error(s), 58 warning(s) can't install CS5
I can't seem to get CS5 to install on my compute, any idea where I should start?
computer -
Acer Aspire x3300 4 gigs of RAM, lots of free space on the harddrive
Windows Home Premium 64 Bit
Install errors -
Exit Code: 6
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 58 error(s), 58 warning(s)
WARNING: OS requirements not met for {667C8B6C-3EAF-4646-A8EC-D85CCC4D3D84}
WARNING: OS requirements not met for {7DFEBBA4-81E1-425B-BBAA-06E9E5BBD97E}
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
ERROR: The following payload errors were found during install:
ERROR: - Adobe CSXS Infrastructure CS5: Install failed
ERROR: - Microsoft_VC90_ATL_x86: Install failed
ERROR: - Adobe Media Player: Install failed
ERROR: - Adobe Linguistics CS5 x64: Install failed
ERROR: - Adobe Photoshop CS5 Support: Install failed
ERROR: - Adobe Bridge CS5: Install failed
ERROR: - Microsoft_VC80_ATL_x86: Install failed
ERROR: - Recommended Common Fonts Installation x64: Install failed
ERROR: - AdobePDFL x64 CS5: Install failed
ERROR: - DeviceCentral_DeviceCentral3LP-en_US: Install failed
ERROR: - Microsoft_VC80_MFCLOC_x86_x64: Install failed
ERROR: - Adobe XMP Panels CS5: Install failed
ERROR: - Photoshop Camera Raw: Install failed
ERROR: - AdobeColorCommonSetCMYK: Install failed
ERROR: - Adobe Mini Bridge CS5: Install failed
ERROR: - Microsoft_VC80_CRT_x86_x64: Install failed
ERROR: - Adobe Photoshop CS5 English Language Pack_x64_AdobePhotoshop12-en_US_x64: Install failed
ERROR: - AdobeColorJA CS5: Install failed
ERROR: - Adobe ReviewPanel CS5: Install failed
ERROR: - Photoshop Camera Raw (64 bit): Install failed
ERROR: - Microsoft_VC90_MFC_x86: Install failed
ERROR: - Adobe Photoshop CS5 Core_x64: Failed due to Language Pack installation failure
ERROR: - Adobe Photoshop CS5 English Language Pack_AdobePhotoshop12-en_US: Install failed
ERROR: - Suite Shared Configuration CS5: Install failed
ERROR: - Adobe Linguistics CS5: Install failed
ERROR: - PDF Settings CS5: Install failed
ERROR: - DeviceCentral: Failed due to Language Pack installation failure
ERROR: - AdobeColorEU CS5: Install failed
ERROR: - AdobeTypeSupport CS5: Install failed
ERROR: - AdobeColorVideoProfilesCS CS5: Install failed
ERROR: - AdobeColorCommonSetRGB: Install failed
ERROR: - Adobe Player for Embedding x64: Install failed
ERROR: - Adobe Photoshop CS5 Core: Failed due to Language Pack installation failure
ERROR: - Required Common Fonts Installation x64: Install failed
ERROR: - Microsoft_VC90_ATL_x86_x64: Install failed
ERROR: - Adobe CSXS Extensions CS5: Install failed
ERROR: - Microsoft_VC80_ATL_x86_x64: Install failed
ERROR: - AdobeOutputModule: Install failed
ERROR: - Microsoft_VC80_CRT_x86: Install failed
ERROR: - AdobeCMaps x64 CS5: Install failed
ERROR: - AdobeTypeSupport x64 CS5: Install failed
ERROR: - Microsoft_VC90_MFC_x86_x64: Install failed
ERROR: - Adobe WinSoft Linguistics Plugin CS5: Install failed
ERROR: - Adobe WinSoft Linguistics Plugin CS5 x64: Install failed
ERROR: - AdobePDFL CS5: Install failed
ERROR: - AdobeCMaps CS5: Install failed
ERROR: - Microsoft_VC80_MFC_x86_x64: Install failed
ERROR: - Required Common Fonts Installation: Install failed
ERROR: - Adobe SwitchBoard 2.0: Install failed
ERROR: - Microsoft_VC80_MFC_x86: Install failed
ERROR: - AdobeColorNA CS5: Install failed
ERROR: - AdobeColorPhotoshop CS5: Install failed
ERROR: - Microsoft_VC80_MFCLOC_x86: Install failed
ERROR: - Recommended Common Fonts Installation: Install failed
ERROR: - Adobe Extension Manager CS5: Install failed
ERROR: - Adobe ExtendScript Toolkit CS5: Install failed
ERROR: - Adobe AIR: Install failedI had the same problem referenced, and tried a fair number of things simultaneously, and was able to successfully re-install CS5 & then upgrade to 6.2 Adobe Camera Raw.
1. Remove Program (through add/remove programs).
2. Run the CS5 removal script (downloaded from Adobe - be careful to wait until all files are extracted).
3. Run MSCONFIG (type it into "Run" on start menu). Disable every single item in Services and Startup that authored by Adobe. Also disable your anti-virus software and any program that syncs your files).
4. Disable Windows Firewall.
5. Reboot
6. Run the installation program. Be sure to right click, and "run as administrator". Hope for success.
7. Run from Photoshop Updates (click help at the top, then updates). Hope for success.
8. Reverse steps 3 and 4.
9. Reboot. -
Error Message in xcode: Command /usr/bin/codesign failed with exit code 1
I am attempting build my iPad application on my device and I have went though the provisioning and successfully created an App ID, provisioning, etc. and when i 'Build and go' i get this error message:
*Command /usr/bin/codesign failed with exit code 1*
The only thing that I could think of that might be causing this is that when I 'Build and Go' on my device it come up with this pop-up message from xcode twice:
+codesign wants to sign using key "MY NAME" in your keychain.+
+Do you want to allow access to this item?+
Please Help.Hey jamez97,
In Xcode, top left hand corner of the window. Access the drop down menu, make sure that you have;
1) Set to run on the DEVICE
2) Selected DEBUG
3) Connected your device
click build and run...adjusting these sometimes works when i have the same error as you.
You should have also added your device the provisioning profile you made. If you haven't done this, you can do it via the iOS Devcentre --> provisioning portal -->launch assistant.
Hope this helps...if it doesn't, post back and somebody else may be able to give you the solution.
j
Message was edited by: james_coleman01
Message was edited by: james_coleman01 -
Hi,
Please tell me steps for how to create Menu Exit. Please Help meMENU 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.
There are 'only' 177 Menu exits in standard - I couldn't see the right one, too.
But you could search the implemented exits, this should be only a small number. Go to transaction CMOD, enter * and F4, information system (F5), show all selections (Shift+F7) and then you can restrict to search only menu exits.
Of course there is the possibility, that these are added in a different way...
... at least you can be sure, if it's a normal menu exit.
Check this sap help..
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
http://www.sapbrainsonline.com/TUTORIALS/default.html
You can achieve this functionality by configuring in IMG.
Please find the info regarding User-Exit's in the following links:
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/frameset.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
Re: doubt on user exits
user exits and Badis
User exits is the enhancements provided by SAP
You can use them in transactions. Each transaction will have user exits.
If you want to use your own requirements by making your coding while the transaction is run you can use user exits.
For example if you want to run the MRP in MD02 specific to MRP controller you can user exit.
Please also refer the document below.
USEREXIT
Userxits allow us to add our own functionality to SAP standard program
without modifying it . These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.
All Userexits start with the word USEREXIT_...
FORM USEREXIT_..
z..
ENDFORM.
The problem lies in finding the correct userexit and how to find it if one exists for the purpose. Once the correct userexit is found the necessary customer code is inserted in the customer include starting with the z.. in the form routine.
e.g. USEREXIT_SAVE_DOCUMENT_PREPARE
Certain application like SD still provide this form of enhancement using userexit but this practice is no longer being followed for newer extensions instead they are using EXITs which come bundeled in enhancement packages . Neverthiless existing USEREXITS will be supported by SAP an all the newer versions of SAP.
HOW TO FIND USEREXITS
Userexits can be found in number of ways:
1) To find userexits in SD module , goto object navigator(SE80) and select
development class from the list and enter VMOD in it. All of the userexits in SD are contained in the development class VMOD. Press enter and you will find all the includes which contain userexits in SD for different functions like PRICING, ORDER PROCESSING etc. Select the userexit according to the requirement and read the comment inserted in it and start coding .
Some examples of userexits in SD(SALES & DISTRIBUTION ) are:
1)ADDING OF NEW FIELDS IN PRICING
In Pricing in SD the fields on the basis of which pricing is done are derived from the FIELD CATALOG which is a structure KOMG .This structure is used to transfer transaction data to the pricing procedure in SD and is also known as communication structure.This structure KOMG consists of two tables KOMK for Header related fields and KOMP for item related fields. The fields which are not in either of the two tables KOMK and KOMP cannot be used in pricing .Sometimes a need arises when the pricing is to be based on some other criteria which is not present in the form of fields in either of the two tables. This problem can be solved by using USEREXITS which are provided for pricing in SD. Pricing takes place both when the SALES ORDER ( Transaction VA01) is created as well as when INVOICING ( Transaction VF01) is done.Hence SAP provides 2 userexits ,one for sales order processing which is
USEREXIT_PRICING_PREPARE_TKOMP or
USEREXIT_PRICING_PREPARE_TKOMK
Depending upon which table (KOMK or KOMP) the new fields were inserted we use either of the above two userexits.These userexits are found in include MV45AFZZ of the standard SAP sales order creation program SAPMV45A.
In the case of userexit which will be called when invoicing is done ,these
are provided in the include RY60AFZZ which is in the standard SAP program SAPMV45A. The name of the userexits are same. i.e
USEREXIT_PRICING_PREPARE_TKOMP or
USEREXIT_PRICING_PREPARE_TKOMK
These userexits are used for passing the data from the communication structure to the pricing procedure, for this we have to fill the newely created field in the communication structure KOMG for this we fill the code in the above userexit using the MOVE statement after the data that has to be passed is taken from the database table by using the SELECT statement. The actual structure which is visible in these userexits and which is to be filled for that particular field is TKOMP or TKOMK.
Before the coding for these userexits is done ,it is necessary to create a new field in either of the two tables KOMK or KOMP .For this purpose includes are provided in each of them .
To create the field in header data(KOMK) the include provided is KOMKAZ
and to create the field in item data(KOMP) the include provided is KOMPAZ.
One possible example for the need of creating new fields can be e.g. Frieght to be based upon transportation zone ,for this no field is available in field catalog and hence it can be created in KOMK and then above userexits can be used to fill the transportation data to it.
2)The other method of finding userexit is to find the word USEREXIT in the
associated program of the transaction for which we want to determine userexit using SE38.
3)The other method of finding userexits is to find the include in case of SD/MM applications where the userexits are located ,this can be found in the SAP reference IMG generally in the subfolder under SYSTEM MODIFICATION.
Some other examples of userexits in SD are:
USEREXIT_NUMBER_RANGE
This userexit is used to assign a different internal document number to the
sales order(VA01) when it is created depending on some criteria like a different SALES ORGANIZAION(VKORG) .
USEREXIT_SAVE_DOCUMENT_PREPARE
This userexit is used to insert the ABAP code which will be called when
the document (sales order VA01) is just about to be saved.This userexit is used generally for custom checks on different fields , to display some information before the order will be saved or for making changes to certain fields before the sales order will be saved.
Exits & Enhancements
There are mainly six types of EXITs in sap which have been collected in the form of enhancement packages and attached to standard code in SAP.
These are different from USEREXIT in the way that they are implemented
in the form of FUNCTIONs while in USEREXITS we use form routines for their implementation. These are also sometimes known as function exits .
These start from the word EXIT_ followed by the program name and then followed by a three digit number.
e.g. EXIT_SAPMV45A_002
This exit is found in SD in enhancement V45A0002.
TYPES OF EXITS
1)MENU EXITS
2)FUNCTION EXITS
3)TABLE EXITS
4)SCREEN EXITS
5)KEYWORD EXITS
6)FIELD EXITS
We use SAP transactions CMOD and SMOD to manage exits. Before implementing an exit , it is required to create the project by using CMOD
selecting the enhancement e.g. V45A0002 and selecting the component
(one which fulfills our need) i.e the exit which will be implemented in SMOD and after coding has been done the project has to be activated.
An exit can be coded only once.
FUNCTION EXITS
These are used to add functionality through ABAP code . These start from the word EXIT_programname_NNN ending in a 3 digit number. No access code is required to implement any tupe of exit including function exits.
The function exits are called from the standard SAP program in the form
of ABAP statement
CALL CUSTOMER-FUNCTION 'NNN'
This is in contrast to USEREXITs where PERFORM statement is used to call
the required userexit.
To implement the FUNCTION EXITs first of all the project is created and a suitable enhancement package is selected and from its compnents the function exit to be implemented is selected and on double clicking it the exit code will appear in ABAP EDITOR(se38) where a Z include will be found and the customer code should be entered in this include.
e.g.
ADDING A DEFAULT SOLD-TO-PARTY in Sales Order Creation
To show a default sold-to-party in this field when the user creates a sales order (VA01) we can use a function exit .This function exit is located in enhancement no V45A0002 . Before we can choose the exit we have to create a project in CMOD after that enter V45A0002 in the enhancement field and click on the components . In the components you will see the exit EXIT_SAPMV45A_002 . This exit is used for our purpose.
Double clicking on this exit will takes us to function builder (SE37) . This
function exit has one exporting parameters and two importing parameters, we are interested in exporting parameter which is E_KUNNR of type KNA1-KUNNR i.e if we move the desired customer name to this structure(E_KUNNR) it will be shown in the field as the default value when we create the sales order. This function also contains a customer include ZXVVA04 . This include will be used to write our custom code .
Double clicking on this include and it will prompt us that this include does not exists do you want to create this object ,select yes and the include will be created .In this include we can write our own code that will fill the field E_KUNNR.
e.g. E_KUNNR = 301.
Activate the include and Activate the project. Now when ever the SALES ORDER will be created , sold-to-party field will come up with a predefined customer .
FIELD EXITS
The field exits are managed,created,activated through program RSMODPRF. The field exit is associated with a data element existing in ABAP dictionary and hence to the screen field using that data element.
The format of field exit is :
FIELD_EXIT_dataelement_A-Z or 0-9
If a particular screen and program name is not specified than the field exit will effect all the screens containing that data element.
The function module associated with field exit shows two parameters
INPUT and OUTPUT. Input parameter contains the data passed to the field exit when the field exit was invoked by the R/3 , We can write our own code to change the output parameter depending upon our requirements.
Before the field exit can have any effect the system profile parameter
ABAP/FIELDEXIT in all the application servers should be set to YES
ABAP/FIELDEXIT = YES.
Reward points Please ... -
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 -
hi everyone,
can you send me some examples on menu exits and screen exits.
thank you.
preethamHi Preetham,
In older versions MENU Exits approached through Transaction CMOD by creating
PROJECTS and activating the project and assigning Program to that
Transaction Codes. For MENU Exits, Transaction Codes will be starting with
"+" sign and with default text "NODE TEXT NOT FOUND" for which you can
assign your Report or Dialog Program etc., (for Eg:- +DW4 MENU Exits
Transaction available in TOOLS --> ABAP Workbench --> Utilities --> <Node
Text Not found>).
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
For screen exits.
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
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.
the tcode is cmod...
1.From the main screen of the Project management transaction, proceed as follows:
Select Enhancement components and choose Change.
2.Choose Edit component.
3.Choose the screen exit and double click on it
4.Create your subscreen using the Screen Painter.
5.Design your screen to be added to the standard screen and activate the particular screen and return back to the flow logic .
6.Choose the PAI and PBO to write down the logic.
7.Generate your screen and choose Back (the green arrow) to return to the Project management transaction.
8.Go to the transaction ME22 to view the customer defined screen exit.
9.Enter the purchase order number and press Enter.
10.Go to the menu header --> Details.
11.Purchase number is visible on the standard screen
check the foll link,
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
Menu exits allow you to add your own functions to the pulldown menus in standard R/3 transactions. To take advantage of a menu exit, you first need to create a project as described in the section Creating an add-on project. Then, you must include the SAP enhancement package that contains the menu exit you want to use in your project. From the main screen of the Project management transaction, proceed as follows:
Select Enhancement components and choose Change.
The system lists all customer exits contained in the enhancements included in your project.
Place the cursor on the menu exit you want to add your own function to.
Choose Edit component.
The system displays technical information about the menu entry. It also displays two input fields where you can specify a language and the text you want your menu item to have.
Enter the name of your menu function (such as Special order method) in the field New text.
Choose Save text.
Your special menu function will not appear in the pulldown menu of the corresponding standard transaction until you activate your enhancement project.
Specifying a menu text and activating your project are not the only steps you need to take to make your own menu item work. After you carry out these steps, your menu item will appear, but it will not call a corresponding function. To attach your menu entry to its corresponding function, you need to create a function module for the function module exit associated with your menu text. This function module exit is part of the same SAP enhancement that contains the menu exit you used. Creating Customer-Specific Function Modules tells you more about how to use function module exits.
also refer
MEnu Exit
http://www.sap-img.com/abap/what-is-user-exits.htm
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
For screen exits.
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
chech these links for user exists its usefull
http://www.allsaplinks.com/user_exit.html
Re: Screen exit
user exit and customer exit
http://help.sap.com/saphelp_47x200/helpdata/en/dd/561602545a11d1a7020000e829fd11/frameset.htm
http://www.sap-basis-abap.com/sapab013.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
How to implement screen exit for a SAP standard transaction
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 them save. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
Original Source: ittoolbox.com
MENU
refer
MEnu Exit
just refer to the link below for step by step procedure with screen shots
http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g
Check this link:
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975e643b111d1896f0000e8322d00/frameset.htm
Menu exits allow you to add your own functions to the pulldown menus in standard R/3 transactions. To take advantage of a menu exit, you first need to create a project as described in the section Creating an add-on project. Then, you must include the SAP enhancement package that contains the menu exit you want to use in your project. From the main screen of the Project management transaction, proceed as follows:
Select Enhancement components and choose Change.
The system lists all customer exits contained in the enhancements included in your project.
Place the cursor on the menu exit you want to add your own function to.
Choose Edit component.
The system displays technical information about the menu entry. It also displays two input fields where you can specify a language and the text you want your menu item to have.
Enter the name of your menu function (such as Special order method) in the field New text.
Choose Save text.
Your special menu function will not appear in the pulldown menu of the corresponding standard transaction until you activate your enhancement project.
Specifying a menu text and activating your project are not the only steps you need to take to make your own menu item work. After you carry out these steps, your menu item will appear, but it will not call a corresponding function. To attach your menu entry to its corresponding function, you need to create a function module for the function module exit associated with your menu text. This function module exit is part of the same SAP enhancement that contains the menu exit you used. Creating Customer-Specific Function Modules tells you more about how to use function module exits.
User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a function module. The code for the function module is written 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>
To find a Exit.
Goto Transaction -- Find The Package
SMOD >f4>Use the Package here to Find the Exits In the Package.
Else if you Want to search by Application Area wise ,
There is one more tab to find the Exits in the Respective Application Area.
Implementing the Exit-- CMOD Create ProjectsAssgn your Component .
Now Run ur Transaction to Check if it Triggers.
Thats it..
Suppose you need to find out all the user exits related to a tcode.
1. Execute the Tcode.
2. Open the SAP program.
3. Get the Development Class.
4. Execute Tcode SE84.
5. Open the Node 'Envir. -> Exit Techniques -> 'Customer Exits -> Enhancements'
6. Enter the Development class and execute.
Check out this thread..
The specified item was not found.
1. Type the transaction : system->status-> <PROG. NAME>
2 open SE37 , type EXIT<PROG NAME> and press F4 to get the list of function exits available.
3. Open CMOD utilities->SAP enhancements
EDIT->All selections
4.type the function module name obtained in step 2, in fields 'component name' in 'additional selections' block. and execute.
5. The displayed list contains the enhancements names for the transaction You were looking for.
6. Create a project in CMOD and the code in default include->activate.
http://www.erpgenie.com/sap/abap/code/abap26.htm
which gives the list of exits for a tcode
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
For information on Exits, check these links
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.planetsap.com/userexit_main_page.htm
User-Exits
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/ab038.htm
http://www.planetsap.com/userexit_main_page.htm
http://www.sap-basis-abap.com/sapab013.htm
http://sap.ittoolbox.com/documents/popular-q-and-a/user-exits-for-the-transaction-code-migo-3283
These links will help you to learn more on user exits.
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.planetsap.com/userexit_main_page.htm
http://www.allsaplinks.com/user_exit.html
www.sap-img.com/abap/what-is-user-exits.htm
Also please check these threads for more details about user exits.
Re: Screen exit
user exit and customer exit
user exit
1. Document on UserExits in FI/CO
http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
2. Finding User Exits...
http://sap.ionelburlacu.ro/abap/sap2/Other_Useful_Tips.html#Finding_User_Exits
3. List of all User Exits...
http://www.planetsap.com/userexit_main_page.htm
Reward points if helpful.
Thanks
Naveen khan
Message was edited by:
Pattan Naveen
Maybe you are looking for
-
How to get green p in quickproxy?
how to get green p in quickproxy
-
Changing a G/L account code from B/S item to P/L item
Hi Experts, I created a G/L account code as a Profit & Loss item. After that some document transactions were posted in that G/L Account code. Later, I realized that that G/L account should have been a Balance Sheet item. So, when in FS00, I tried to
-
30-pin male to 30-pin male iPod cable?
Looking to purchase a new home audio system (LG's LH-E922PB) which has as cool built-in iPod control system. However the connector on the rear of the unit is a female 30-pin (same as on the iPod). I have not been able to track down a 30-pin (male) to
-
I did not want yahoo as my default search engine. I want to be able to pick and choose as always. When i clicked on a different search engine i lost all functionality of the search bar and it became blank.I,ve gone back to 33 till i can get a fix for
-
Webcast Archive and Test Questions with DVD Pro Studio
Is there a way to put a web archive of a Mediasite (by Sonic Foundry) webcast into a DVD that can be played on a TV through a traditional DVD player? I know you can link a site to pull up in a web browser when you use the DVD in a computer, but I was