NAME field in FBL5N transaction

Hello everybody,
I am trying to add the field NAME1 within the structure RFPOS agree to the settlement informed by SAP on the Notes 112312 and 208807, also by the indications that we have in this forum. But after creating the basis for the event 1650 (BTE) and the time to execute the transaction FBL5N there is a DUMP problems of the structure RFPOS. This happens because the function that creates works with the new structure modified, RFPOSXEXT which contains the field NAME1 added by customizing (Tx. OBVU).
Please tell me the solution.
Thank you.
Regards.
Daniel Montes Zarza

Hi,
Go to FIBF environment >> info system P/S >> then execute .. you will find 1650
Create BTE 1650 (Business Transaction Event). For this purpose, copy the
sample function module SAMPLE_INTERFACE_00001650 into the customer
namespace.
Then activate the module in transaction FIBF.
Go to 'Settings -> Products -> ... of a customer' and create a product.
You can choose the name of the product and the description.
Set the 'Active' indicator and save.
Go to 'Settings -> P/S Modules -> ... of a customer' and include this
entry:
Event:              00001650
Product:            'Product name'
Lnd/Appl:           empty
Function module:    'Your module'
Save the entry.
Regards
Ravinaghh Boni
Please rewards me if it usefull

Similar Messages

CITY NAME field on BP transaction

Hi Gurus,
I have two requirements on city name field in BP transaction for every address:
The first requirement is that the field city name was not ready for input. I have achieved it implementing a zfunction module for field group 65 which I have set on field grouping customizing. I have given a status '*' (only for display) to field group 65.
The problem is that the search help doesn't work now. The hit list is displayed but when I do double-click on a result entry the city name value is not mapped to dynpro field. How can I achieve both things, not ready for input field but with efective search help, I mean the result value will be mapped on dynpro field too.
The second requierement is that the search help on ADDR2_DATA-CITY_NAME, besides city name and region dynpro field also fill up the regiogroup dynpro field. Is there anyway to achieve it without standard modification?
Best Regards,
Rosa

Hi Rohit,
You can right click on the corresponding column( Bank Account number) and choose the
option 'Delete Current Column'. This will remove the column data and then you can take
the print. It will not remove the column permanently. If you close this popup and open again,
the field will reappear. So just for your printing purpose, you can do this.
Regards
Leon

User Name field in fbl3n, fbl1n, fbl5n

Hello,
How should i add user name field in fbl5n / fbl3n / fbl1n?
Thanks

hi,
215798 FBL*N: Special fields are not displayed
Have you done the following :
In the Line item Display list in FBL3N follow this menu path: Settings
-> Special fields, and add field BKPF-USNAM from table BKPF.
The field is later available for display,and you can choose it from
the Line item Display list following this menu: Settings -> Display
variant -> Current. From the hidden list you can now choose the field.
If the technical name is shown for the fields, the special fields are
are all starting with '1-U_'. It's important, that you add the Special
field, if the field also exist as Standard field. The Special fields
are shown in the buttom of the Hiddden list.
Please still remember step 2 and 3 from note 215798.
reg
Madhu M

Table Name For 'Picked Quantity' Field in VL03 Transaction

Dear All,
I am not able to find out 'Picked Quantity' Field in VL03 Transaction.Can anybody provide me Table name and field name for the same.
Regards,
Mayank

Hi Mayank / Masha.
Your requirement is to find out the picked quantity for the delivery document.
Please note that this value can never be found from any table & what you will find are only structures.
For this you need to use / run a function module to fetch the Picked Quantity
Functional Module: WB2_GET_PICK_QUANTITY
Goto Tcode SE37 & enter the function module.
Further enter the delivery details in the screen
I_VBELN - Delivery Number
I_POSNR - Item Number
And Execute.
E_PIKMG - the picked quantity.
If you require to find picked quantity for any report you can very well ask your ABAPer to include this function module in your program
Hope this solves your requirement
Regards,
Dhananjay

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 kumar

Hi,
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

Replication of bp name field from ERP to CRM

Hi experts,
We have a problem in ERP to CRM master data replication.
We have already connected our ERP (ECC 5.0) system to CRM 7.0.
We have made initial master business partners (bp) data load from ERP to CRM without problems.
All bp fields, including NAME (but000-name_org1) are transfered correct from ERP (KNA1-NAME1) to CRM.
We have a z program in ERP that is used by users to change the customers names (KNA1-name1).
When we use our custom program in ERP to change the kna1-name1 field in ERP, the bp name field is not changes in CRM.
Using XD02 or FD02 in ERP to change the name (kna1-name1) field in ERP the replication of this field to CRM is correct.
KNA1 table is updated correctly in ERP using our custom program .
What does transactions XD02 and FD02 has that make name filed replicated in CRM?
Thanks in advanced.

Hi,
First variant:
You have to retry load business partners by request:
Tcode R3AR4, R3AR2, R3AR3
So, system retrive new data from tables and transfer to CRM.
Second variant:
You have to add to your z-program part, there you fill data in the CRM system also (via RFC).
Denis.

E-Recruiting 6.0: Name Field

Hi Experts,
I have the following questions as regards to 'name' field and would appreciate your help:
1) I understand the name fields (first name and last name) cannot be customised. But does E-Recruiting support the addition of middle name? I can configure under Business Partner to add in the Middle name, but it did not display on the E-Recruiting screen or R/3 BP transaction. I am not sure whether standard E-Recruiting does not support it or I have not configure correctly.
2) What is the table name which stores the name of a candidate and the applicant objecet number? I can see the name of the candidate in transaction BP, but i do not know where to find the applicant number. I need the information to for tracing and troubleshooting purposes.
Many thanks,
William

Hello William,
with e-recruiting 600 support package 10 or 11 e-recruiting supports middle name, 2nd academic title and name prefixes in the web dynpro frontend as standard fields for candidates. Unfortunately it seems SAP is no longer adding such stuff to the BSP frontend. In transaction BP you should be able to see these fields if noone changed BP. But the fields are only visible when filled so you might have to change to edit mode to click this small button with the plus.
Personal data of candidates name, birthdate, gender, titles are stored in the standard business partner tables BUT000 and following. Address is saved in the tables of the central address service but needs an entry in IT5110. That's why adding an address in BP won't work while changing is possible.
To get the differnt keys which are used for the candidate I usually start from BP as I have a name. I simply use the sear help of BP to get the BP number. Then it's all about HRP1001 which stores all object relations. As BP is an external object from HR view (as is the User) you put the BP into SCLAS and number into SOBID field (dont forget leading zeros here) and you can get the CP number. With the CP number you can get the User and the candidate (NA) number. From the candidate you can get applications (ND) and candidacies (NE) and so on.
Best Regards
Roman Weise

Table Names & Field Names in FS for ABAP

What is the easiest option to find out Table & Field Names normally asked by ABAP Consultant through Functional Specs?
Any specific tips to find specific table names & field names?

T000 Clients
T001 Company Codes
T001E Company code-dependent address data
T001P Personnel Areas/Subareas
T500L Personnel Country Grouping
T500P Personnel Areas
T500T Personnel Country Groupings
T501 Employee Group
T501T Employee Group Names
T502T Marital Status Designators
T503 Employee Groups / Subgroups
T503K Employee subgroup
T503T Employee Subgroup Names
T504A Benefits - Default Values (NA)
T504B Benefit Option Texts (North America)
T504C Benefit Type (NA)
T504D Benefit Credit Group Amount
T504E Benefit Amount
T504F Benefit Costs
T508A Work Schedule Rules
T508T Texts for Employee Subgroup Groupings for Work Schedules
T510 Pay Scale Groups
T510A Pay Scale Types
T510F Assign Pay Scale > Time Unit, Currency
T510G Pay Scale Areas
T510H Payroll Constants with Regard to Time Unit
T510I Standard Working Hours
T510J Constant Valuations
T510L Levels
T510M Valuation of pay scale groups acc. to hiring date
T510N Pay Scales for Annual Salaries (NA)
T510S Time Wage Type Selection Rule
T510U Pay Scale Groups
T510Y Special Rules for Wage Type Generation
T511 Wage Types
T512R Cumulation Wage Types in Forms
T512S Texts for Cumulation Wage Types in Forms
T512T Wage Type Texts
T512W Wage Type Valuation
T512Z Permissibility of Wage Types per Infotype
T513 Jobs
T514S Table Name Texts
T514T Field Name Texts
T51D2 Wage Type Classes
T51D3 Reduction Rules
T51D4 Cumulation Rules
T527X Organizational Units
T528B Positions - Work Centers
T528C Wage Type Catalog
T528T Position Texts
T529A Personnel Event
T529F Fast Data Entry for Events
T529T Personnel Event Texts
T52BT Texts For HR Objects
T52C0 Payroll Schemas
T52C1 Payroll Schemas
T52C2 Texts for Personnel Calculation Schemas
T52C3 Texts for Personnel Calculation Schemas
T52C5 Personnel Calculation Rules
T52CC Schema Directory
T52CD Schema Directory
T52CE Directory of Personnel Calculation Rules
T52CT Text Elements
T52CX Cross References via Generated Schemas
T52D1 Valid Processing Classes
T52D2 Valid Values for Processing Classes
T52D3 Valid Evaluation Classes
T52D4 Permitted Values for Evaluation Classes
T52D5 Wage Type Groups
T52D6 Wage Type Group Texts
T52D7 Assign Wage Types to Wage Type Groups
T52D8 Valid Processing Classes - Texts
T52D9 Valid Values for Processing Classes - Texts
T530 Reasons for Events
T530E Reasons for Changes
T530F Reasons for Changes
T530L Wage Types for Special Payments
T530T Event Reason Texts
T531 Deadline Types
T531S Deadline Type Texts
T533 Leave Types
T533T Leave Type Texts
T539A Default Wage Types for Basic Pay
T539J Base Wage Type Valuation
T539R Events for Standard Wage Maintenance
T539S Wage Types for Standard Wage Maintenance
T548 Date Types
T548S Date Conversion
T548T Date Types
T548Y Date Types
T549A Payroll Areas
T549B Company Features
T549C Decision Trees for Features (Customers)
T549D Feature Directory
T549L Date modifiers
T549M Monthly Assignment: Payroll Period
T549N Period Modifiers
T549O Text for date modifier
T549P Valid Time Units for Payroll Accounting
T549Q Payroll Periods
T549R Period Parameters
T549S Payroll date types
T549T Payroll Areas
T549M Monthly Assignment: Payroll Period
T549N Period Modifiers
T549O Text for date modifier
T549P Valid Time Units for Payroll Accounting
T549Q Payroll Periods
T549R Period Parameters
T549S Payroll date types
T549T Payroll Areas
T554S Absence and Attendance Types
T554T Absence and Attendance Texts
T554V Defaults for Absence Types
T554Y Time Constraints in HR TIME
T555A Time Types
T555B Time Type Designations
T559A Working Weeks
T559B Name of Working Week
T572F Event Texts
T572G Allowed Values for Events
T572H Event Value Texts
T582A Infotypes
T582B Infotypes Which Are Created Automatically
T582S Infotype Texts
T582V Assignment of Infotypes to Views
T582W Assigns Infotype View to Primary Infotype
T582Z Control Table for PA Time Management
T584A Checking Procedures - Infotype Assignment
T588A Transaction Codes
T588B Infotype Menus
T588C Infotype Menus/Info Groups
T588D Infogroups for Events
T588J Screen Header Definition
T588M Infotype Screen Control
T588N Screen Modification for Account Assignment Block
T588O Screen Modification for Assignment Data
T588Q Screen types for fast entry
T588R Selection Reports for Fast Data Entry
T588S Screen Types for Fast Entry
T588T Menu and Infogroup Designations
T588V Business object type
T588W Event types for infotype operations
T588X Cust. composite definition of event types for IT operations
T588Z Dynamic Events
T591A Subtype Characteristics
T591B Time Constraints for Wage Types
T591S Subtype Texts
T596F HR Subroutines
T596G Cumulation wage types
T596H _Cumulation wage type texts
T596I Calculation rule for cumulation wage types
T596U Conversion Table
T599B Report Classes
T599C Report Classes
T599D Report Categories
T599F Report Classes - Select Options
T777A Building Addresses
T777T Infotypes
T777Z Infotype Time Constraints
T778T Infotypes
T778U Subtypes
CATSCO Cross-Application Time Sheet (CATS)- Transfer to CO
CATSDB CATS- Database Table for Time Sheet
CATSHR Cross-Application Time Sheet (CATS)- Transfer to HR
CATSMM Cross-Application Time Sheet (CATS)- Transfer to MM
CATSPM Cross-Application Time Sheet (CATS)- Transfer to PM/CS
CATSPS Cross-Application Time Sheet (CATS)- Transfer to PS

Adding one header text field in FBL5N output

Hi Experts,
I hava a requirment to show one extra field of length 200 character in the FBL5N transaction output. When I analyzed the program I found its using "FI_ITEMS_DISPLAY" Fm to display the output. The table passed to this FM is of type structure "RFPOSXEXT", which dont have any field of 200 length.
can anybody suggest me a better way to do the change rather then going for a 'Z' FM and 'Z' program.
Regards,
Puja Patil.

Hi,
a. Add the news fields in structure RFPOS and RFPOSX by APPEND structure
b. Run the report RFPOSXEXTEND in order to update the structure RFPOSXEXT from RFPOSX
(this report has to be run in every enviroment, dev, test and prod)
c. Active the BTE 00001650 in order to create a fm as copy of SAMPLE_INTERFACE_00001650:
d. here insert the code you need to fill your new field.
e. Use trx FIBF to active the BTE, trx SE37 to create the new fm
Just now I have incorporated a requirement of adding additional customer field in FBLN5 using BTE enhancement. It works fine.
Please reward points if helpful.
Regrads
Mohamed Aboobacker Siddique.

Find obligatory fields in the transaction MM01

Hi,
My requirement is to create a Z table which will store all mandatory fields from the transaction MM01.
Is there a way to know which fields are mandatory without being in the transaction MM01 or OMS9? In which system table is this information saved?
Regards,
Roberto

Hi,
For writing a substitution exit code you will need the help of your ABAPer.
Use T Code GGB1 to create a substitution. In the application Area select Financial Accounting --> Line item.
Create a substitution for your company code. Under Substitution Create Step. When you click on step it will give you a list of fields in BSEG table. Select field name XREF1 or XREF2 or XREF3 any one. In the next screen select "Exit". In the Prerequisites give conditions as BKPF-BUKRS = 1000 (your company code).
In the Substitution select your exit code against your XREF1 or XREF2 or XREF3 field.
While writing the exit code you can give the logic as select BSEG-KUNNR and pass to table KNA1. Then populate BSEG-XREF1 with KNA1-NAME1
Save this substitution and activate it in T Code "OBBH"
While writing Substitution exit copy the standard program "RGGBS000" and create your Z program. Write your new code in the Z program. This step should be done before you create a substitution. Use T Code GCX2 and maintain your Z program against Application Area "GBLS".
Also see to it that the Reference Key1 / 2 / 3 field is made optional in all the Posting Keys and Field Status Groups.
Please let me know whether this helps.
Regards,
Swapnil

Adding a screen field in FB60 transaction

Hi all,
I just want to add a screen field in FB60 transaction. In that transaction there is a table control. I want to add a coloumn there. Can anyone help me how to do that? I am working in ECC 5.0
Thanks in advance
Pranav

Hi Pranav,
If you want to add a new column under the table control in FB60, there is a way to do it through config.
This is how it can be done:-
1) Go to T-Code SPRO
2) Financial Accounting New>Financial Global Settings New>Ledgers>Fields>Customer Fields>Edit Coding Block
3) Define your new field under "Customer defined account assignments" . Make sure the name starts with either 'ZZ' or "YY". This creates a standard structure with your custom field and also appends this new custom field in many FI related tables including BSEG so make sure to check the impact with your functional consultant.
4) Once it is defined, you might need to change the characteristics of your field under
Financial Accounting New>Financial Global Settings New>Document>Define Posting Keys
(This changes your fields status from suppresed to either Optional or Required depending on your requirement)
Hope this link also helps
http://help.sap.com/erp2005_ehp_03/helpdata/EN/65/ec4bd7fb0f44f6814fa790dde9a172/frameset.htm
Reward points if helpful
Cheers
Sanjiv

Add fields in FBL5N output

Hi
     I have to add some fields in output list in FBL5N transaction code.
How to add the fields?
     Is it possible to copy the standard program and again shall i add the new fields in output list.
    Please tell me how to do it?
Thanks.

There is a Business Transaction Event (BTE) for that, its number [00001650|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=00001650+bte&adv=false&sortby=cm_rnd_rankvalue]. Look at OSS [Note 112312 - Line item: Display of offsetting a/c information|https://service.sap.com/sap/support/notes/112312] and [Note 373268 - Line item: new display field|https://service.sap.com/sap/support/notes/373268] for an implementation sample and guidance.
- Append a structure to structure [RFPOS|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=rfpos&adv=false&sortby=cm_rnd_rankvalue] with your fields (SE11)
- Run report [RFPOSXEXTEND|https://www.sdn.sap.com/irj/sdn/advancedsearch?query=rfposxextend&cat=sdn_all]
- Create a FM (copy of [SAMPLE_INTERFACE_00001650|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=sample_interface_00001650&adv=false&sortby=cm_rnd_rankvalue]) to fill these fields (SE37)
- Optimize and bufferize your FM (accountants love when there are many lines) (SE37)
- Link the FM to the BTE ([FIBF|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=fibf&adv=false&sortby=cm_rnd_rankvalue])
- Run [BALVBUFDEL|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=balvbufdel&adv=false&sortby=cm_rnd_rankvalue] to correct the ALV buffer inconsistency
- Adapt your layout variants
In more recent versions take also a look at BADI like [BADI FI_ITEMS*|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=badi+fi_items&adv=false&sortby=cm_rnd_rankvalue]
Regards

Is it possible to add new screen fields to the transaction /dsd/sl_cockpit

HI experts,
Would like to know if it is possible to add new screen fields to the cloned version of /dsd/sl_cockpit.
I cloned the original transaction /dsd/sl_cockpit into a diff. name, now I want to know how I can include/ add those new fields to this transaction. It looks like the screen is dynamically built using Standard ABAP classes. Need help.
Thanks in advance

it is not possible to add new fields via badi on /dsd/sl_cockpit.

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

Dynamic Selections - FBL5n transaction

Hi all,
How can we add a new field on the "Dynamic Selections" in FBL5n transaction?
Thanks

HI,
pls. see SAPNET 310886. This describes how to add additional dynamic selections to FBL*N T-codes.
Next time, pls. make a SAPNET search on your own before post in this forum.
BR Christian

NAME field in FBL5N transaction

Similar Messages

Maybe you are looking for