Additional fields in MIGO transaction
Hi Everybody,
We have a requirement where we need to have additional fields in MIGO transaction when the user chooses 'distribute qty' option to split the quantity, the normal screen shows the following fields,
1. Qty in UnE
2. Stock type
3. Movement type
4.Stor location, we need Serial number, Drum number in Screen number 1000 of SAPLMIGO program, Can any one tell me how do I achieve this functionality,
Rgds,
The only option I see is design your own custom screen with the required fields and call it as popup ( Modal Dialog Box ) from user exit ZXMBCU02 .
This user exit will be triggered when you click on "CHECK" or "SAVE" button.
There is no way to modify MIGO screen itself , so maybe you will have to pass the item number etc from MIGO and have a table control on your custom screen for data entry.
For saving data into database donot use this exit as a user may just check and go out and you will unnecssarily push the data into z table . In this exit do an export to memory for your custom fields.
In another exit ZXMBCU01 , do an import from memory and update the required Z table . This exit is called while updating material document in update task.
However to goto popup screen for displaying chnaging custom fields you will have to press "CHECK" button , maybe a user training issue.
Cheers
Similar Messages
-
Regarding - add a new field in migo transaction
Hai guys,
i need to add one field in MIGO transaction, can u pls tell me the step by step procedure for adding the new field in migo transaction.
Regards,
N.selvamuthukumar.Hi Selvamuthu,
It is possible using the BADI MB_MIGO_BADI to add Additional tabs in header and/or item as required
MB_MIGO_BADI -> BAdI in MIGO for External Detail Subscreens
See the documentation below...........
With the Business Add-In (BAdI) MB_MIGO_BADI, you can extend the interface of the goods movements transaction ( MIGO) with additional tabstrip controls for the detailed information (detail tabstrips) and header information (header tabstrips). It is possible for an external application
to display an additional detail tabstrip with own subscreen (max. 10 lines) in MIGO
to display an additional header tabstrip with own subscreen (max. 3 lines) in MIGO
The program name, screen number and tab page text can be determined dynamically. Different screens can therefore be controlled according to the mode (for example, change mode, display mode, goods receipt, goods issue).
To read the complete documentation --go to se18 --click on BADI -- enter -- MB_MIGO_BADI----Display
inside click on "DOCUMENTATION" button and there is a complete documentation step by step
in addition to it ...--go to se18 --click on BADI -- enter -- MB_MIGO_BADI----Display ->
on the top menu -> "GOTO" -> sample code -> "Display"
in will get the "methods" tab..see the description
Initialization and Registration of Ext. Detail Screens
PBO of Detail Screen
PAI of Detail Screen
Add / Change a Line (GOITEM)
Delete a Line (GOITEM)
MIGO Reset (Delete All Internal Data)
Post Goods Movement
Check Item Data of Goods Movement
Mode of Transaction MIGO (Action / Reference Document)
Status Information and Header Data
Save Held Data
Load Held Data
Delete Held Data
PBO of Header Screen
PAI of Header Screen
Check Header Data of Goods Movement
Publish Item Data After Processing
sample code is given in these methods..so when we create a custom badi implementation of our own go to the sample code and copy the required code in the corresponding methods as required
double click on the method..for eg:IF_EX_MB_MIGO_BADI~PBO_HEADER in the sample code to see code....in this particular method we can see how method calls an external program and screen to create a new tab in MIGO...use code from mainly the following to get a new header/item tab
PBO of Header Screen
PAI of Header Screen
PBO of Detail Screen
PAI of Detail Screen
Pls take some time to analyse the code or flow but we can have the tabs in the header/item level
Hope it helps
Regards
Byju -
How to add a new field in migo transaction (header level)
hi guru's
can you please tell me how to add a field in migo transaction?
i want to add a field in header data and that too under "general" tab. i dont have data regarding that field.
and when we enter a value for that field in migo, it has to take .
thank you.Hi, My problem is allmost like the one you are discussing here....
I have appended MKPF for my Z-fields and created a sub-screen (Design the screen). I am calling this screen in PBO_HEADER. Now i can see my newly created tab along with fields.
Now the problem is:-
1. How I can transfer that data entered in screen fields back to my BADI.
2. How to update my z-fields in MKPF table along with standard fields. I have tried using FM - 'J_1IEXGM_BADI_POST_DOCUMENT' in Method - POST_DOCUMENT, but its not updating table record in MKPF for Z-Fields.
Please advice.....
Thanks -
Possibility of adding new fields to migo transaction
Is there a possiblity of adding new fields in migo transaction so that we can enter the base price of items in po.
Also Can we send mail to relevant authorization if there is difference in price entered in the po and the value entered in GRHi, You can use BADI 'MB_MIGO_BADI' for adding custom fields at item as well as header level .
or Check SAP Note 339448 - MIGO: settings of table control
2-You can not do any thing related to price in MIGO, since you cannot enter any manual values in MIGO, it will always pull from PO or MIRO (in case of Imports). -
Saving custom fields to MSEG added in additional TAB in MIGO transaction
Hi Experts,
I am facing an issue with an enhancement in MIGO transaction for which i need help. I have gone through several threads with similar issues but none of them have solved my issue. I have worked around with all BADIs of MIGO and user exits available but to no avail so I am posting a new thread.
The requirement is pretty straight forward of adding a custom TAB in item details section of MIGO transaction. I have done that using BADI: MB_MIGO_BADI, method PBO_DETAIL. I created a screen with my custom fields and passed them in this method. The TAB appears as expected with all the fields. The custom fields are in MSEG table which has been enhanced and it needs to be updated with the user values on the screen.
The issue creeps in when there are multiple materials in the purchasing document and user works around with them. Say he clicks on the second material and in the custom TAB changes its details in custom fields. Now he clicks on the fourth material and changes its details. Continues this for all the materials in random order. How do i identify in my custom screen [developed separately and called in PBO_DETAIL of the BADI] which details belong to which material or line number. The only way to do it is by using the purchasing order number and line item number. These are not available in my custom screen and needs to be exported from somewhere and imported there. I have not been able to identify the point where export can be done.
Can anyone help me out with this problem? Either the point where export can be done or any other way of identifying the link between the line number / material number and the custom field details entered by the user.
Thanks,
RitvikHi Ritvik,
you will not need it.
The item methods will process exactly the item what the addional item data are related to. In PBO_DETAIL and PAI_DETAIL, use parameter I_LINE_ID for the item reference.
Note: Not only read SCN etc, also the parameters desciption of the methods used.
Regards,
Clemens -
Addition of Dept ans Section input fields in MIGO transaction.
Hi experts,
im very new to customer exits. I got requirement to add two input fields in 'OWN DATA' in MIGO transaction. These fields should be for selected movement types.
Can any one please help me in solving this. Please kindly tell me in detail as im new to enhancements.
advance
thanks
vijay.SEARCH in SCN for these badi you will get lot of posts.
MB_MIGO_ITEM_BADI,MB_MIGO_BADI -
How to add a new additional field in MIGO
Dear Sir,
As a business requirement , we are required to capture some additional information related to Material packing /sizes at the time of MIGO . This information need to be captured /input at the Item level during the MIGO .
We request sap gurus , to kindly guide as what steps need to be followed for adding a new field and also will it require a Z-table also to save the data pertaining to new added field .
Regards
B MittalHi ,
Create a BADI implementation for MB_MIGO_BADI .
Create a program with the screen type sub-screen in SE80 and design the layout for the custom fields.
Declare the custom fields in a Z**TOP include.
Under the PBO method declare the program name and screen number as shown below:
gf_class_id = 'MIGO_BADI_IMPLEMENTATION_CIN'
e_cprog = <program name>
e_dynnr = <screen number>.
e_heading = <heading>
Under PAI method declare the field to u2018Xu2019.
e_force_change = 'X'.
Under the line modify method declare a flag and set to u2018Xu2019 checking for material document number by which we can set the fields to be in display mode when we open MIGO for display of material document created after doing goods receipt.
Under the POST_DOCUMENT method write the code for appending the value to Z table along with the values of the line item .For these values to be available here in this method use the memory concept u201CExport to memory idu201D in the method LINE_MODIFY.
In order to do any validations to the custom fields, go to transaction SE80 and mention the program Name created and in PROCESS ON VALUE_REQUEST create a module and provide the validations required for those custom Fields.
order to make the fields to be in display mode during the display of material document, create a module under PBO and import the flag value in the method LINE_MODIFY and if that flag = u2018Xu2019, use
LOOP AT SCREEN.
IF SCREEN-NAME = <NAME>.
SCREEN-INPUT = '0'.
MODIFY SCREEN.
ENDIF.
ENDLOOP.
Retrieve the values from the Z table matching the key field (production order number) and pass the value of the custom field on to the screen.
Thanks,
Shailaja Ainala. -
EXIT NAME OR BADI FOR FIELD IN MIGO TRANSACTION (full poins will be given)
Hai all,
VERY URGENT REQ.
In MIGO transaction, I want to know the BADI or EXIT NAME in which the following fields are avilable .
Fields name: exgrp, EXCISE_ACTION
exact screen field name is : J_1IEXHEAD-EXGRP
J_1IEXHEAD-EXCISE_ACTION
Full Points will be given for correct answer.
Thanks in advance.
s.senthil kumarHi,
Try this code .We can get the User exits and Badis for the Tcode.
Code:
& Report ZPJA_PM002 (Ver4) &
& PJA Consultancy Services (www.pjas.com) &
& This report attmpts to find Enhancements, Program-Exits, BADIs &
& and Business Transaction Events in a particular program/tcode. &
& Other search options: &
& Program: RPR_ABAP_SOURCE_SCAN &
& FModule: &
& 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 221.
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_fsel like sy-ucomm, " Determination of screen field
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',
c_col6(8) type c value 'Project',
c_col7(1) type c value 'S',
c_col8(12) type c value 'ChangeName',
c_col9(10) type c value 'ChangeDate'.
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 ty_mod,
member like modact-member,
name like modact-name,
status like modattr-status,
anam like modattr-anam,
adat like modattr-adat,
end of ty_mod.
data: w_mod type ty_mod.
types: begin of t_userexit,
type(12) type c,
pname like trdir-name,
txt(300),
level type c,
modname(30) type c,
modtext(60) type c,
modattr type ty_mod,
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.
types: begin of t_enlfdir,
area type enlfdir-area,
end of t_enlfdir.
data: i_enlfdir type standard table of t_enlfdir 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 NEEDED
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
endif.
else.
message e110(/saptrx/asc) with 'No program found for: ' p_tcode."#EC NOTEXT
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.
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.
store function groups
select single area from enlfdir into wa_enlfdir-area
where funcname = i_fmodule-name.
i_enlfdir-area = wa_enlfdir-area.
append i_enlfdir.
Store development classes
if 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.
endif.
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.
sort funtion groups
sort i_devclass.
delete adjacent duplicates from i_devclass.
sort i_enlfdir.
delete adjacent duplicates from i_enlfdir.
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'.
check i_submit-pname ne p_pname. " ensure not the same as origianl program
clear: i_stoken, i_sstmnt, sourcetab.
refresh: i_stoken, i_sstmnt, sourcetab.
read report i_submit-pname into sourcetab.
if sy-subrc 0.
delete i_submit.
continue.
else.
scan abap-source sourcetab tokens into i_stoken
statements into i_sstmnt
keywords from keywords
with includes.
if sy-subrc > 0.
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.
sort i_submit.
delete adjacent duplicates from i_submit comparing pname.
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 'IDOC'.
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.
read table i_fmodule with key name = i_fmodule-name.
if sy-subrc 0.
i_fmodule-level = p_level.
append i_fmodule.
endif.
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.
MOH - enhancement to get the project name
clear w_mod.
select single modactmember modactname modattr~status
modattranam modattradat
into w_mod
from modact
inner join modattr
on modattrname = modactname
where modact~member = wa_modsapa-name
and modact~typ = space.
i_userexit-modattr = w_mod.
MOH - eoe
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.
Get IDOCs
loop at i_devclass.
endloop.
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,
(60) c_col5, "Enhancement description
sy-vline,
(8) c_col6, "Project
sy-vline,
(1) c_col7, "S
sy-vline,
(12) c_col8, "ChangeName
sy-vline,
(10) c_col9, "ChangeDate
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(60),
sy-vline,
i_userexit-modattr-name,
sy-vline,
i_userexit-modattr-status,
sy-vline,
i_userexit-modattr-anam,
sy-vline,
i_userexit-modattr-adat no-zero,
sy-vline.
hide: i_userexit-type,
i_userexit-txt,
i_userexit-pname,
i_userexit-modname,
i_userexit-modtext.
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).
write: 157''.
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
& User Selection Processing &
at line-selection.
get cursor field w_fsel.
case w_fsel.
when 'I_USEREXIT-MODNAME'.
case i_userexit-type.
when 'Enhancement'.
set parameter id 'MON' field i_userexit-modname.
call transaction 'SMOD' and skip first screen.
when 'BADI'.
check i_userexit-modname ne 'Dynamic call'.
set parameter id 'EXN' field i_userexit-modname.
call transaction 'SE18' and skip first screen.
when 'BusTrEvent'.
submit rfopfi00 with attr_typey_selm = 'A'
with event = i_userexit-modname(8)
via selection-screen
and return.
when others.
endcase.
when 'I_USEREXIT-PNAME'.
check i_userexit-modname ne 'Unknown'.
w_off = 0.
find '/' in i_userexit-pname match offset w_off.
if w_off = 0.
set parameter id 'RID' field i_userexit-pname.
call transaction 'SE38' and skip first screen.
else.
w_off = w_off + 1.
w_prog = i_userexit-pname+w_off.
set parameter id 'RID' field w_prog.
call transaction 'SE38' and skip first screen.
endif.
when others.
endcase.
Thank You,
Saritha -
Table used in goitem fields in MIGO transaction.
Hello experts,
I was given to write BDC for MIGO transaction.
Please any one suggest me how to get the following fields (from which table) .
material text - maktx,
Quantity in Une - ERFMG
batch number - CHARG
external entered posting amt in local currency - EXBWR
please do me the requested favor,
advanced thanks,
vijayHi,
Better way i`ll tell you how to find the database tables.
Goto the transaction CV03.
Get the program name.
SYSTEM ---> STATUS ---> PROGRAM(GUI)
The program name for this transaction SAPLCV00.
Copy this program name.
Goto SE38. Open this program.
Get the package name.
GOTO ---> ATTRIBUTES ---> PACKAGE
The package for this program is CV.
Copy the package name.
Goto to SE80 or Click on Display Object List(CtrlShiftF5) button which is on the toolbar.
Select package and open the package name.
You will get the list of business engeneering, dict.objs, class library, programs etc.
Goto Dict.objects ---> Database tables.
All the tables related to this transaction are given here.
Use these steps to find the tables, programs, function grps etc
whenever required.
Hope this solves your problem.
Thanks,
Darpana. -
EXIT NAME OR BADI FOR FIELD IN MIGO TRANSACTION
Hai all,
In MIGO transaction, I want to know the BADI or EXIT NAME in which the following fields are avilable .
Fields name: exgrp, EXCISE_ACTION
exact screen field name is : J_1IEXHEAD-EXGRP
J_1IEXHEAD-EXCISE_ACTION
Full Points will be given for correct answer
Thanks in advance.
s.senthil kumarHai all,
In MIGO transaction, I want to know the BADI or EXIT NAME in which the following fields are avilable .
Fields name: exgrp, EXCISE_ACTION
exact screen field name is : J_1IEXHEAD-EXGRP
J_1IEXHEAD-EXCISE_ACTION
Full Points will be given for correct answer
Thanks in advance.
s.senthil kumar -
Disabling G/L Account field in MIGO transaction
HIiya Gurus,
I have got a requirement to disable the GL Account field in Accounting tab in the MIGO transaction. since i am an abaper i am not sure how to disable this field. i have gone through the transaction SPRO , but unfortunately for the filed G/L Account field KONTO there are only 2 options :--
either to make it optional or mandatory.
But my requirement is to make it disabled (greyed out), IS it possible to Grey out that field.
In my customization this field is set as Option.
Kindly provide me with your valuable suggestions.
Cheers,
ZIaHi,
Use this BADI 'MB_MIGO_BADI'
Do write the code in PBO of the screen.......which you have created ....
In order to make the fields to be in display mode during the display of material document, create a module under PBO and import the flag value and the production order number details in the method LINE_MODIFY and if that flag = u2018Xu2019, use
LOOP AT SCREEN.
IF SCREEN-NAME = 'ZZGBAGS'.
SCREEN-INPUT = '0'.
MODIFY SCREEN.
ENDIF.
ENDLOOP.
Regards
krishna
Edited by: Krishna Gowrneni on May 1, 2009 12:25 AM
Edited by: Krishna Gowrneni on May 1, 2009 12:39 AM -
Hiding G/L Account field in MIGO transaction (Goods Issue)
Dear Gurus,
Anyone knows how I can hide the G/L account in the MIGO transaction (Goods Issue).
Thanks,
John.Hi
Try it in Tcode OMBW
In that select the particular field and change it to suppress..
It will work
Regards,
raman -
How to use OMJX transaction? Need to add an additional field on MIGO item
hi guys
we need to add a new field on the MIGO screen at the item level. We are trying to explore OMJX to add custom fields.
We have used append structutre to enhance the GOITEM structure but are not clear on how to use OMJX.
ANy idea how to use the transaction OMJX.
Thanks in advanceWith the Business Add-In (BAdI) MB_MIGO_BADI, you can extend the
interface of the goods movements transaction (MIGO) with additional
tabstrip controls for the detailed information (detail tabstrips) and
header information (header tabstrips). It is possible for an external
application
o to display an additional detail tabstrip with own subscreen (max. 10
lines) in MIGO
o to display an additional header tabstrip with own subscreen (max. 3
lines) in MIGO
The program name, screen number and tab page text can be determined
dynamically. Different screens can therefore be controlled according to
the mode (for example, change mode, display mode, goods receipt, goods
issue).
Pushbuttons
It is not possible to implement pushbuttons in the MIGO menu, but you
can, however, implement pushbuttons directly on the external subscreen.
The OK code from MIGO is forwarded to the external application so it can
react.
Cursor Control
So that the cursor stays on the same subscreen after you press Continue,
if it was positioned there before, the external application in the own
PAI must hold the cursor positioning (on the same screen 'yes'/'no'; if
'yes', on which field), to set the cursor in PBO again.
Requirements
If you use the BAdI MB_MIGO_BADI in MIGO to update customer-own data, in
addition to the material document, to the database, you should note the
following:
o The BAdI MB_MIGO_BADI is only active in transaction MIGO.
o If you post goods movements with other transactions (for example, with
MB01, MB1C, VL02N), you must ensure that customer data is also
updated, if necessary.
You can do this by using the BAdI MB_DOCUMENT_BADI (Creating a
material document) to post the goods movements with the transactions
mentioned above.
o Note that otherwise, posting the goods movements will lead to
inconsistencies between SAP system data (for example, in stocks,
material documents, FI documents) and customer data. -
Flagging of Item OK field in MIGO transaction
Hi all,
Is there any option to flag the Item OK field for multiple line items in MIGO (select all option) as the User is ticking the item OK field for line items individually.
thanks in advance.
regards,
KumarDear all,
Thanks, through default values i can attain this,, my issue is solved,, awarded points to all.
this thread is closed.
regards,
Kumar -
HI all,
Is it possible to add one more date field in MIGO transaction? If yes, how?
Thanks in advance,
MadhuHi,
With MB_MIGO_BADI , you can add additional tabstrip controls for the detailed information (detail tabstrips) and header information (header tabstrips) controls.
This badi comes with sample code implement this sample code as a reference I hope it will help you a lot.
For sample code goto tcode se18 enter badi name
From file menu choose goto->sample code->display.
Cheers
Ahsan
Maybe you are looking for
-
How to process a sales project in SD module?
Dear all, I have a sales business scenario, but I don't know how to implement in SAP. The business scenario is as follows: - Company A will sell a batch goods to its customer B. But, this is a large sales project. So, A should create a series of sale
-
I need help with my Iphone 4 reset cause I will activate it in other country
I need help with my Iphone 4 reset cause I will activate it in other country Thanks
-
Urgent: smartform tutorials
hi, i am new to the smart frms i want to have tutorials which are easy to understand and can be practised. points will be definately rewarded.
-
Fdisk ignores arguments?
Hello! I have ben using Arch for a while now, and everything works great, except of 1 little thing. I can't get fdisk working... Look at this: root@MobileCommand: /home/emil #> fdisk -l Usage: fdisk [options] <disk> change partition table fdisk [opti
-
Unable to stay connected to my iTunes library. After a short period of time I get a message to turn on home sharing. Home sharing is on?