Method for dble-click and table control

I'm a beginner in object. I build, with screen painter, a table control with x rows and x cols. and give the possibilty to use 'double click'.
But how to handle this event by a method and importing the number of the row and col where the action of the event has been.
which class and method can i use. thanks for your help
Moderator message: sorry, these forums are not a replacement for ABAP training, please search for available information and documentation, there is plenty available.
Edited by: Thomas Zloch on Dec 7, 2010 4:21 PM

hi,
You can do this by estimating maximum no of records of that internal table used for table control to some number and then assign that number lines field of table control.
try this.
Regds
Sivaparvathi
Please reward points if helpful...

Similar Messages

Hi All, Pls send me the recording for va01 by handling table control

Hi All, Pls send me the recording for va01 by handling table control with 3 or more materials. Pls send me a flat file and code ASAP.
Thanks&regards.
Bharat

Here is a example of similar kind ..plz go through this doc..it will be help hul 4 u
How to deal with table control / step loop in BDC?
Steploop and table contol is inevitable in certain transactions. When we run BDC for such transactions, we will face the situation: how many visible lines of steploop/tablecontrol are on the screen? Although we can always find certain method to deal with it, such as function code 'NP', 'POPO', considering some extreme situation: there is only one line visible one the screen,
our BDC program should display an error message. (See transaction 'ME21', we you resize your screen to let only one row visible, you can not enter mutiple lines on this screen even you use 'NP')
Now, I find a method with which we can determine the number of visible lines on Transaction Screen from our Calling BDC program. Maybe it is useless to you, but I think it will give your some idea.
Demo ABAP code has two purposes:
1. how to determine number of visible lines and how to calculte page number; (the 'calpage' routine has been modify to meet general purpose usage)
2. using field symbol in BDC program, please pay special attention to the difference in Static
ASSIGN and Dynamic ASSIGN.
Now I begin to describe the step to implement my method:
(I use transaction 'ME21', screen 121 for sample, the method using is Call Transation Using..)
Step1: go to screen painter to display the screen 121, then we can count the fixed line on this screen, there is 7 lines above the steploop and 2 lines below the steploop, so there are total 9 fixed lines on this screen. This means except these 9 lines, all the other line is for step loop.
Then have a look at steploop itselp, one entry of it will occupy two lines.
(Be careful, for table control, the head and the bottom scroll bar will possess another two fixed lines, and there is a maximum number for table line)
Now we have : FixedLine = 9
LoopLine = 2(for table control, LoopLine is always equal to 1)
Step2: go to transaction itself(ME21) to see how it roll page, in ME21, the first line of new page is always occupied by the last line of last page, so it begin with index '02', but in some other case, fisrt line is empty and ready for input.
Now we have: FirstLine = 0
or FirstLine = 1 ( in our case, FirstLine is 1 because the first line of new page is fulfilled)
Step3: write a subroutine calcalculating number of pages
(here, the name of actual parameter is the same as formal parameter)
global data: FixedLine type i, " number of fixed line on a certain screen
LoopLine type i, " the number of lines occupied by one steploop item
FirstLine type i, " possbile value 0 or 1, 0 stand for the first line of new
" scrolling screen is empty, otherwise is 1
Dataline type i, " number of items you will use in BDC, using DESCRIBE to get
pageno type i, " you need to scroll screen how many times.
line type i, " number of lines appears on the screen.
index(2) type N, " the screen index for certain item
begin type i, " from parameter of loop
end type i. " to parameter of loop
*in code sample, the DataTable-linindex stands for the table index number of this line
form calpage using FixedLine type i (see step 1)
LoopLine type i (see step 1)
FirstLine type i (see step 2)
DataLine type i ( this is the item number you will enter in transaction)
changing pageno type i (return the number of page, depends on run-time visible line in table control/ Step Loop)
changing line type i.(visible lines one the screen)
data: midd type i,
vline type i, "visible lines
if DataLine eq 0.
Message eXXX.
endif.
vline = ( sy-srows - FixedLine ) div LoopLine.
*for table control, you should compare vline with maximum line of
*table control, then take the small one that is min(vline, maximum)
*here only illustrate step loop
if FirstLine eq 0.
pageno = DataLine div vline.
if pageno eq 0.
pageno = pageno + 1.
endif.
elseif FirstLine eq 1.
pageno = ( DataLine - 1 ) div ( vline - 1 ) + 1.
midd = ( DataLine - 1 ) mod ( vline - 1).
if midd = 0 and DataLine gt 1.
pageno = pageno - 1.
endif.
endif.
line = vline.
endform.
Step4 write a subroutine to calculate the line index for each item.
form calindex using Line type i (visible lines on the screen)
FirstLine type i(see step 2)
LineIndex type i(item index)
changing Index type n. (index on the screen)
if FirstLine = 0.
index = LineIndex mod Line.
if index = '00'.
index = Line.
endif.
elseif FirstLine = 1.
index = LineIndex mod ( Line - 1 ).
if ( index between 1 and 0 ) and LineIndex gt 1.
index = index + Line - 1.
endif.
if Line = 2.
index = index + Line - 1.
endif.
endif.
endform.
Step5 write a subroutine to calculate the loop range.
form calrange using Line type i ( visible lines on the screen)
DataLine type i
FirstLine type i
loopindex like sy-index
changing begin type i
end type i.
If FirstLine = 0.
if loopindex = 1.
begin = 1.
if DataLine <= Line.
end = DataLine.
else.
end = Line.
endif.
elseif loopindex gt 1.
begin = Line * ( loopindex - 1 ) + 1.
end = Line * loopindex.
if end gt DataLine.
end = DataLine.
endif.
endif.
elseif FirstLine = 1.
if loopindex = 1.
begin = 1.
if DataLine <= Line.
end = DataLine.
else.
end = Line.
endif.
elseif loop index gt 1.
begin = ( Line - 1 ) * ( loopindex - 1 ) + 2.
end = ( Line - 1 ) * ( loopindex - 1 ) + Line.
if end gt DataLine.
end = DataLine.
endif.
endif.
endif.
endform.
Step6 using field sysbol in your BDC, for example: in ME21, but you should calculate each item will correponding to which index
form creat_bdc.
field-symbols: <material>, <quan>, <indicator>.
data: name1(14) value 'EKPO-EMATN(XX)',
name2(14) value 'EKPO-MENGE(XX)',
name3(15) value 'RM06E-SELKZ(XX)'.
assign: name1 to <material>,
name2 to <quan>,
name3 to <indicator>.
do pageno times.
if sy-index gt 1
*insert scroll page ok_code"
endif.
perform calrange using Line DataLine FirstLine sy-index
changing begin end.
loop at DataTable from begin to end.
perform calindex using Line FirstLine DataTable-LineIndex changing Index.
name1+11(2) = Index.
name2+11(2) = Index.
name3+12(2) = Index.
perform bdcfield using <material> DataTable-matnr.
perform bdcfield using <quan> DataTable-menge.
perform bdcfield using <indicator> DataTable-indicator.
endloop.
enddo.
Sample code
Following is a sample code of handling table control in BDC.
REPORT Y730_BDC5 .
*HANDLING TABLE CONTROL IN BDC
DATA : BEGIN OF IT_DUMMY OCCURS 0,
DUMMY(100) TYPE C,
END OF IT_DUMMY.
DATA : BEGIN OF IT_XK01 OCCURS 0,
LIFNR(10) TYPE C,
BUKRS(4) TYPE C,
EKORG(4) TYPE C,
KTOKK(4) TYPE C,
NAME1(30) TYPE C,
SORTL(10) TYPE C,
LAND1(3) TYPE C,
SPRAS(2) TYPE C,
AKONT(6) TYPE C,
FDGRV(2) TYPE C,
WAERS(3) TYPE C,
END OF IT_XK01,
BEGIN OF IT_BANK OCCURS 0,
BANKS(3) TYPE C,
BANKL(10) TYPE C,
BANKN(10) TYPE C,
KOINH(30) TYPE C,
LIFNR(10) TYPE C,
END OF IT_BANK.
DATA : IT_BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE,
IT_BDCMSGCOLL LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
CALL FUNCTION 'WS_UPLOAD'
EXPORTING
FILENAME = 'C:\VENDOR.TXT'
FILETYPE = 'ASC'
TABLES
DATA_TAB = IT_DUMMY.
LOOP AT IT_DUMMY.
IF IT_DUMMY-DUMMY+0(2) = '11'.
IT_XK01-LIFNR = IT_DUMMY-DUMMY+2(10).
IT_XK01-BUKRS = IT_DUMMY-DUMMY+12(4).
IT_XK01-EKORG = IT_DUMMY-DUMMY+16(4).
IT_XK01-KTOKK = IT_DUMMY-DUMMY+20(4).
IT_XK01-NAME1 = IT_DUMMY-DUMMY+24(30).
IT_XK01-SORTL = IT_DUMMY-DUMMY+54(10).
IT_XK01-LAND1 = IT_DUMMY-DUMMY+64(3).
IT_XK01-SPRAS = IT_DUMMY-DUMMY+67(2).
IT_XK01-AKONT = IT_DUMMY-DUMMY+69(6).
IT_XK01-FDGRV = IT_DUMMY-DUMMY+75(2).
IT_XK01-WAERS = IT_DUMMY-DUMMY+77(3).
APPEND IT_XK01.
ELSE.
IT_BANK-BANKS = IT_DUMMY-DUMMY+2(3).
IT_BANK-BANKL = IT_DUMMY-DUMMY+5(10).
IT_BANK-BANKN = IT_DUMMY-DUMMY+15(10).
IT_BANK-KOINH = IT_DUMMY-DUMMY+25(30).
IT_BANK-LIFNR = IT_DUMMY-DUMMY+55(10).
APPEND IT_BANK.
ENDIF.
ENDLOOP.
LOOP AT IT_XK01.
REFRESH IT_BDCDATA.
perform bdc_dynpro using 'SAPMF02K' '0100'.
perform bdc_field using 'BDC_CURSOR'
'RF02K-REF_LIFNR'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'RF02K-LIFNR'
IT_XK01-LIFNR.
perform bdc_field using 'RF02K-BUKRS'
IT_XK01-BUKRS.
perform bdc_field using 'RF02K-EKORG'
IT_XK01-EKORG.
perform bdc_field using 'RF02K-KTOKK'
IT_XK01-KTOKK.
perform bdc_dynpro using 'SAPMF02K' '0110'.
perform bdc_field using 'BDC_CURSOR'
'LFA1-TELX1'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'LFA1-NAME1'
IT_XK01-NAME1.
perform bdc_field using 'LFA1-SORTL'
IT_XK01-SORTL.
perform bdc_field using 'LFA1-LAND1'
IT_XK01-LAND1.
perform bdc_field using 'LFA1-SPRAS'
IT_XK01-SPRAS.
perform bdc_dynpro using 'SAPMF02K' '0120'.
perform bdc_field using 'BDC_CURSOR'
'LFA1-KUNNR'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_dynpro using 'SAPMF02K' '0130'.
perform bdc_field using 'BDC_CURSOR'
'LFBK-KOINH(02)'.
perform bdc_field using 'BDC_OKCODE'
'=ENTR'.
DATA : FNAM(20) TYPE C,
IDX TYPE C.
MOVE 1 TO IDX.
LOOP AT IT_BANK WHERE LIFNR = IT_XK01-LIFNR.
CONCATENATE 'LFBK-BANKS(' IDX ')' INTO FNAM.
perform bdc_field using FNAM
IT_BANK-BANKS.
CONCATENATE 'LFBK-BANKL(' IDX ')' INTO FNAM.
perform bdc_field using FNAM
IT_BANK-BANKL.
CONCATENATE 'LFBK-BANKN(' IDX ')' INTO FNAM.
perform bdc_field using FNAM
IT_BANK-BANKN.
CONCATENATE 'LFBK-KOINH(' IDX ')' INTO FNAM.
perform bdc_field using FNAM
IT_BANK-KOINH.
IDX = IDX + 1.
ENDLOOP.
perform bdc_dynpro using 'SAPMF02K' '0130'.
perform bdc_field using 'BDC_CURSOR'
'LFBK-BANKS(01)'.
perform bdc_field using 'BDC_OKCODE'
'=ENTR'.
perform bdc_dynpro using 'SAPMF02K' '0210'.
perform bdc_field using 'BDC_CURSOR'
'LFB1-FDGRV'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'LFB1-AKONT'
IT_XK01-AKONT.
perform bdc_field using 'LFB1-FDGRV'
IT_XK01-FDGRV.
perform bdc_dynpro using 'SAPMF02K' '0215'.
perform bdc_field using 'BDC_CURSOR'
'LFB1-ZTERM'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_dynpro using 'SAPMF02K' '0220'.
perform bdc_field using 'BDC_CURSOR'
'LFB5-MAHNA'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_dynpro using 'SAPMF02K' '0310'.
perform bdc_field using 'BDC_CURSOR'
'LFM1-WAERS'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'LFM1-WAERS'
IT_XK01-WAERS.
perform bdc_dynpro using 'SAPMF02K' '0320'.
perform bdc_field using 'BDC_CURSOR'
'WYT3-PARVW(01)'.
perform bdc_field using 'BDC_OKCODE'
'=ENTR'.
perform bdc_dynpro using 'SAPLSPO1' '0300'.
perform bdc_field using 'BDC_OKCODE'
'=YES'.
CALL TRANSACTION 'XK01' USING IT_BDCDATA
MODE 'A'
UPDATE 'S'
MESSAGES INTO IT_BDCMSGCOLL.
ENDLOOP.
FORM BDC_DYNPRO USING PROG SCR.
CLEAR IT_BDCDATA.
IT_BDCDATA-PROGRAM = PROG.
IT_BDCDATA-DYNPRO = SCR.
IT_BDCDATA-DYNBEGIN = 'X'.
APPEND IT_BDCDATA.
ENDFORM.
FORM BDC_FIELD USING FNAM FVAL.
CLEAR IT_BDCDATA.
IT_BDCDATA-FNAM = FNAM.
IT_BDCDATA-FVAL = FVAL.
APPEND IT_BDCDATA.
ENDFORM.
Reward if helpful

How to create Search Help for a field in Table control !!

Hello Friends,
 I like to know - How to create Search Help for a field in Table control. Is it possible, if it is please share ur knowledge, I wud be happy if U provide some source code example for this.
Thanks,
Senthil

Check the sample code:
*& Include ZSRO_MPRN_SEARCH *
MODULE PSTLZ_F4 INPUT
MODULE pstlz_f4 INPUT.
reading post code
DATA: stepl TYPE systepl,
 stepl_index TYPE systepl.
CLEAR: stepl, stepl_index.
CLEAR: lt_returntab,lt_dynpfields,i_mprn1.
REFRESH: lt_returntab,lt_dynpfields,i_mprn1.
lt_dynpfields-fieldname = 'I_MPRN-POST_CODE'.
lt_dynpfields-stepl = stepl.
APPEND lt_dynpfields. CLEAR lt_dynpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
 EXPORTING
 dyname = sy-repid
 dynumb = sy-dynnr
 translate_to_upper = c_x
 determine_loop_index = c_x
 TABLES
 dynpfields = lt_dynpfields
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 invalid_parameter = 7
 undefind_error = 8
 double_conversion = 9
 stepl_not_found = 10
 OTHERS = 11.
IF sy-subrc EQ 0.
 READ TABLE lt_dynpfields INDEX 1.
ENDIF.
ws_outcode = lt_dynpfields-fieldvalue.
stepl_index = lt_dynpfields-stepl.
REPLACE '*' WITH ' ' INTO lt_dynpfields-fieldvalue.
IF NOT lt_dynpfields-fieldvalue IS INITIAL.
 MOVE lt_dynpfields-fieldvalue TO ws_outcode.
 ws_len = STRLEN( lt_dynpfields-fieldvalue ).
 IF ws_len GE 7.
 ws_len = ws_len - 3.
 ws_icode = ws_code+ws_len(3).
 lt_dynpfields-fieldvalue = lt_dynpfields-fieldvalue+0(ws_len).
 CONCATENATE lt_dynpfields-fieldvalue '%'
 INTO ws_outcode.
 CONDENSE lt_dynpfields-fieldvalue.
 REPLACE ws_icode WITH ' ' INTO lt_dynpfields-fieldvalue.
 ELSE.
 CONCATENATE lt_dynpfields-fieldvalue+0(4) '%'
 INTO ws_outcode.
 ENDIF.
 ws_ocode = ws_code+0(3).
ENDIF.
reading MPRN
CLEAR: lt_returntab,lt_dnpfields,i_mprn1.
REFRESH: lt_returntab,lt_dnpfields,i_mprn1.
lt_dnpfields-fieldname = 'I_MPRN-MPRN'.
lt_dnpfields-stepl = stepl_index.
APPEND lt_dnpfields. CLEAR lt_dnpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
 EXPORTING
 dyname = sy-repid
 dynumb = sy-dynnr
 translate_to_upper = 'X'
 TABLES
 dynpfields = lt_dnpfields
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 invalid_parameter = 7
 undefind_error = 8
 double_conversion = 9
 stepl_not_found = 10
 OTHERS = 11.
IF sy-subrc EQ 0.
 READ TABLE lt_dnpfields INDEX 1.
ENDIF.
MPRN blank and Post code exist
IF lt_dnpfields-fieldvalue IS INITIAL.
 IF NOT lt_dynpfields-fieldvalue IS INITIAL.
 SELECT mprn ser_num sub_bud bud_name del_pt_alias
 bud_num dep_street prin_street dbl_dep_street
 dep_locty post_town county outcode incode
 lg_site_ind file_date FROM zspa_mprn INTO
 CORRESPONDING FIELDS OF TABLE i_mprn1
 WHERE outcode LIKE ws_outcode.
 ELSE.
MPRN blank and Post code blank
 SELECT mprn ser_num sub_bud bud_name del_pt_alias
 bud_num dep_street prin_street dbl_dep_street
 dep_locty post_town county outcode incode
 lg_site_ind file_date FROM zspa_mprn INTO
 CORRESPONDING FIELDS OF TABLE i_mprn1.
 ENDIF.
ELSE.
MPRN exist and Post code exist
 IF NOT lt_dynpfields-fieldvalue IS INITIAL.
 SELECT mprn ser_num sub_bud bud_name del_pt_alias
 bud_num dep_street prin_street dbl_dep_street
 dep_locty post_town county outcode incode
 lg_site_ind file_date FROM zspa_mprn INTO
 CORRESPONDING FIELDS OF TABLE i_mprn1
 WHERE outcode LIKE ws_outcode AND
 mprn EQ lt_dnpfields-fieldvalue.
 ELSE.
MPRN exist and Post code blank
 SELECT mprn ser_num sub_bud bud_name del_pt_alias
 bud_num dep_street prin_street dbl_dep_street
 dep_locty post_town county outcode incode
 lg_site_ind file_date FROM zspa_mprn INTO
 CORRESPONDING FIELDS OF TABLE i_mprn1
 WHERE mprn EQ lt_dnpfields-fieldvalue.
 ENDIF.
ENDIF.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
 EXPORTING
 retfield = 'MPRN'
 dynpprog = sy-repid
 dynpnr = sy-dynnr
 window_title = 'Select MPRN'
 value_org = 'S'
 TABLES
 value_tab = i_mprn1 "lt_mprn
 return_tab = lt_returntab
 EXCEPTIONS
 parameter_error = 1
 no_values_found = 2
 OTHERS = 3.
IF sy-subrc EQ 0.
 READ TABLE lt_returntab INDEX 1.
 READ TABLE i_mprn1 WITH KEY mprn = lt_returntab-fieldval.
 IF sy-subrc EQ 0.
Updating post code
 CONCATENATE i_mprn1-outcode i_mprn1-incode
 INTO ws_postcode
 SEPARATED BY space.
 MOVE ws_postcode TO i_mprn-post_code.
 CLEAR : i_dnpfld,
 ws_dynpfld.
 REFRESH : i_dnpfld.
 ws_dyname = 'ZSRO_MASTER_DATA'.
 ws_dynumb = '0301'.
 ws_dynpfld-fieldname ='I_MPRN-POST_CODE'.
 ws_dynpfld-fieldvalue = ws_postcode .
 ws_dynpfld-stepl = stepl_index.
 APPEND ws_dynpfld TO i_dnpfld.
 CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = ws_dyname
 dynumb = ws_dynumb
 TABLES
 dynpfields = i_dnpfld
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 undefind_error = 7
 OTHERS = 8.
 IF sy-subrc <> 0.
 ENDIF.
Updating MPRN
 MOVE i_mprn1-mprn TO i_mprn-mprn.
 CLEAR : i_dnpfld,
 ws_dynpfld.
 REFRESH : i_dnpfld.
 ws_dyname = 'ZSRO_MASTER_DATA'.
 ws_dynumb = '0301'.
 ws_dynpfld-fieldname ='I_MPRN-MPRN'.
 ws_dynpfld-fieldvalue = i_mprn1-mprn .
 ws_dynpfld-stepl = stepl_index.
 APPEND ws_dynpfld TO i_dnpfld.
 CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = ws_dyname
 dynumb = ws_dynumb
 TABLES
 dynpfields = i_dnpfld
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 undefind_error = 7
 OTHERS = 8.
 IF sy-subrc <> 0.
 ENDIF.
 ENDIF.
ELSEIF sy-subrc EQ 2.
 MESSAGE s005(zspa) WITH ws_postcode .
ENDIF.
ENDMODULE. "PSTLZ_F4 INPUT
MODULE MPRN_F4 INPUT
MODULE mprn_f4 INPUT.
reading post code
DATA: stepl TYPE systepl,
 stepl_index TYPE systepl.
CLEAR: stepl, stepl_index.
CLEAR: lt_returntab,lt_dynpfields,i_mprn1.
REFRESH: lt_returntab,lt_dynpfields,i_mprn1.
lt_dynpfields-fieldname = 'I_MPRN-POST_CODE'.
lt_dynpfields-stepl = stepl.
APPEND lt_dynpfields. CLEAR lt_dynpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
 EXPORTING
 dyname = sy-repid
 dynumb = sy-dynnr
 translate_to_upper = c_x
 determine_loop_index = c_x
 TABLES
 dynpfields = lt_dynpfields
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 invalid_parameter = 7
 undefind_error = 8
 double_conversion = 9
 stepl_not_found = 10
 OTHERS = 11.
IF sy-subrc EQ 0.
 READ TABLE lt_dynpfields INDEX 1.
ENDIF.
ws_outcode = lt_dynpfields-fieldvalue.
stepl_index = lt_dynpfields-stepl.
REPLACE '*' WITH ' ' INTO lt_dynpfields-fieldvalue.
IF NOT lt_dynpfields-fieldvalue IS INITIAL.
 MOVE lt_dynpfields-fieldvalue TO ws_outcode.
 ws_len = STRLEN( lt_dynpfields-fieldvalue ).
 IF ws_len GE 7.
 ws_len = ws_len - 3.
 ws_icode = ws_code+ws_len(3).
 lt_dynpfields-fieldvalue = lt_dynpfields-fieldvalue+0(ws_len).
 CONCATENATE lt_dynpfields-fieldvalue '%'
 INTO ws_outcode.
 CONDENSE lt_dynpfields-fieldvalue.
 REPLACE ws_icode WITH ' ' INTO lt_dynpfields-fieldvalue.
 ELSE.
 CONCATENATE lt_dynpfields-fieldvalue+0(4) '%'
 INTO ws_outcode.
 ENDIF.
 ws_ocode = ws_code+0(3).
ENDIF.
reading MPRN
CLEAR: lt_returntab,lt_dnpfields,i_mprn1.
REFRESH: lt_returntab,lt_dnpfields,i_mprn1.
lt_dnpfields-fieldname = 'I_MPRN-MPRN'.
lt_dnpfields-stepl = stepl_index.
APPEND lt_dnpfields. CLEAR lt_dnpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
 EXPORTING
 dyname = sy-repid
 dynumb = sy-dynnr
 translate_to_upper = 'X'
 TABLES
 dynpfields = lt_dnpfields
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 invalid_parameter = 7
 undefind_error = 8
 double_conversion = 9
 stepl_not_found = 10
 OTHERS = 11.
IF sy-subrc EQ 0.
 READ TABLE lt_dnpfields INDEX 1.
ENDIF.
MPRN blank and Post code exist
IF lt_dnpfields-fieldvalue IS INITIAL.
 IF NOT lt_dynpfields-fieldvalue IS INITIAL.
 SELECT mprn ser_num sub_bud bud_name del_pt_alias
 bud_num dep_street prin_street dbl_dep_street
 dep_locty post_town county outcode incode
 lg_site_ind file_date FROM zspa_mprn INTO
 CORRESPONDING FIELDS OF TABLE i_mprn1
 WHERE outcode LIKE ws_outcode.
 ELSE.
MPRN blank and Post code blank
 SELECT mprn ser_num sub_bud bud_name del_pt_alias
 bud_num dep_street prin_street dbl_dep_street
 dep_locty post_town county outcode incode
 lg_site_ind file_date FROM zspa_mprn INTO
 CORRESPONDING FIELDS OF TABLE i_mprn1.
 ENDIF.
ELSE.
MPRN exist and Post code exist
 IF NOT lt_dynpfields-fieldvalue IS INITIAL.
 SELECT mprn ser_num sub_bud bud_name del_pt_alias
 bud_num dep_street prin_street dbl_dep_street
 dep_locty post_town county outcode incode
 lg_site_ind file_date FROM zspa_mprn INTO
 CORRESPONDING FIELDS OF TABLE i_mprn1
 WHERE outcode LIKE ws_outcode AND
 mprn EQ lt_dnpfields-fieldvalue.
 ELSE.
MPRN exist and Post code blank
 SELECT mprn ser_num sub_bud bud_name del_pt_alias
 bud_num dep_street prin_street dbl_dep_street
 dep_locty post_town county outcode incode
 lg_site_ind file_date FROM zspa_mprn INTO
 CORRESPONDING FIELDS OF TABLE i_mprn1
 WHERE mprn EQ lt_dnpfields-fieldvalue.
 ENDIF.
ENDIF.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
 EXPORTING
 retfield = 'MPRN'
 dynpprog = sy-repid
 dynpnr = sy-dynnr
 window_title = 'Select MPRN'
 value_org = 'S'
 TABLES
 value_tab = i_mprn1 "lt_mprn
 return_tab = lt_returntab
 EXCEPTIONS
 parameter_error = 1
 no_values_found = 2
 OTHERS = 3.
IF sy-subrc EQ 0.
 READ TABLE lt_returntab INDEX 1.
 READ TABLE i_mprn1 WITH KEY mprn = lt_returntab-fieldval.
 IF sy-subrc EQ 0.
Updating MPRN
 MOVE i_mprn1-mprn TO i_mprn-mprn.
 CLEAR : i_dnpfld,
 ws_dynpfld.
 REFRESH : i_dnpfld.
 ws_dyname = 'ZSRO_MASTER_DATA'.
 ws_dynumb = '0301'.
 ws_dynpfld-fieldname ='I_MPRN-MPRN'.
 ws_dynpfld-fieldvalue = i_mprn1-mprn .
 ws_dynpfld-stepl = stepl_index.
 APPEND ws_dynpfld TO i_dnpfld.
**code changed by laxman 10.08.2005
 ws_dynpfld-stepl = mprn-current_line.
**code changed by laxman 10.08.2005
 CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = ws_dyname
 dynumb = ws_dynumb
 TABLES
 dynpfields = i_dnpfld
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 undefind_error = 7
 OTHERS = 8.
 IF sy-subrc <> 0.
 ENDIF.
Updating post code
 CONCATENATE i_mprn1-outcode i_mprn1-incode
 INTO ws_postcode
 SEPARATED BY space.
 MOVE ws_postcode TO i_mprn-post_code.
 CLEAR : i_dnpfld,
 ws_dynpfld.
 REFRESH : i_dnpfld.
 ws_dyname = 'ZSRO_MASTER_DATA'.
 ws_dynumb = '0301'.
 ws_dynpfld-fieldname ='I_MPRN-POST_CODE'.
 ws_dynpfld-fieldvalue = ws_postcode .
 ws_dynpfld-stepl = stepl_index.
 APPEND ws_dynpfld TO i_dnpfld.
**code changed by laxman 10.08.2005
 break gblap0.
 ws_dynpfld-stepl = mprn-current_line.
 LOOP AT i_mprn.
 MOVE i_mprn1-mprn TO i_mprn-mprn.
 MOVE ws_postcode TO i_mprn-post_code.
 MODIFY i_mprn INDEX
 mprn-current_line." transporting MPRN POST_CODE.
 ENDLOOP.
**code changed by laxman 10.08.2005
 CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = ws_dyname
 dynumb = ws_dynumb
 TABLES
 dynpfields = i_dnpfld
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 undefind_error = 7
 OTHERS = 8.
 IF sy-subrc <> 0.
 ENDIF.
 ENDIF.
ELSEIF sy-subrc EQ 2.
 MESSAGE s006(zspa) WITH i_mprn1-mprn .
ENDIF.
ENDMODULE. "MPRN_F4 INPUT
MODULE GNTC_F4 INPUT
MODULE gntc_f4 INPUT.
DATA: BEGIN OF lt_gntc OCCURS 0,
 gntc LIKE iflot-zzgntc,
 END OF lt_gntc.
CLEAR: lt_returntab, lt_gntc.
REFRESH: lt_returntab, lt_gntc.
lt_gntc-gntc = 'DM'.
APPEND lt_gntc. CLEAR lt_gntc.
lt_gntc-gntc = 'NDM'.
APPEND lt_gntc. CLEAR lt_gntc.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
 EXPORTING
 retfield = 'ZZGNTC'
 dynpprog = sy-repid
 dynpnr = sy-dynnr
 window_title = 'Select Gas Nomination Type Code'
 value_org = 'S'
 TABLES
 value_tab = lt_gntc
 return_tab = lt_returntab
 EXCEPTIONS
 parameter_error = 1
 no_values_found = 2
 OTHERS = 3.
IF sy-subrc EQ 0.
 READ TABLE lt_returntab INDEX 1.
 i_mprn-dm_ndm = lt_returntab-fieldval.
ENDIF.
ENDMODULE. "GNTC_F4 INPUT
*& Module mprn1_f4 INPUT
 text
MODULE mprn1_f4 INPUT.
DATA: lt_f4 TYPE ddshretval OCCURS 0 WITH HEADER LINE,
 lt_returntab1 LIKE ddshretval OCCURS 0 WITH HEADER LINE,
 lt_dynpfields1 LIKE dynpread OCCURS 0 WITH HEADER LINE,
 lt_dnpfields1 LIKE dynpread OCCURS 0 WITH HEADER LINE.
DATA: stepl1 TYPE systepl,
 stepl_index1 TYPE systepl.
DATA : i_dnpfld1 LIKE dynpread OCCURS 0 WITH HEADER LINE,
 ws_dyname1 LIKE d020s-prog,
 ws_dynumb1 LIKE d020s-dnum,
 ws_dynpfld1 LIKE dynpread.
CLEAR: i_dnpfld1, ws_dyname1, ws_dynumb1, ws_dynpfld1,
 lt_f4, lt_returntab1,lt_dynpfields1, lt_f4,
 stepl1, stepl_index1.
REFRESH: i_dnpfld1, lt_returntab1,lt_dynpfields1, lt_f4.
To Determine Steploop Index
lt_dynpfields1-fieldname = 'I_MPRN-POST_CODE'.
lt_dynpfields1-stepl = stepl1.
APPEND lt_dynpfields1. CLEAR lt_dynpfields1.
CALL FUNCTION 'DYNP_VALUES_READ'
 EXPORTING
 dyname = sy-repid
 dynumb = sy-dynnr
 translate_to_upper = 'X'
 determine_loop_index = 'X'
 TABLES
 dynpfields = lt_dynpfields1
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 invalid_parameter = 7
 undefind_error = 8
 double_conversion = 9
 stepl_not_found = 10
 OTHERS = 11.
IF sy-subrc EQ 0.
 READ TABLE lt_dynpfields1 INDEX 1.
ENDIF.
stepl_index1 = lt_dynpfields1-stepl.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
 EXPORTING
 tabname = 'IFLOT'
 fieldname = 'I_MPRN-MPRN'
 searchhelp = 'ZS_MPRN_PC'
 dynpprog = sy-repid
 dynpnr = sy-dynnr
 TABLES
 return_tab = lt_f4
 EXCEPTIONS
 field_not_found = 1
 no_help_for_field = 2
 inconsistent_help = 3
 no_values_found = 4
 OTHERS = 5.
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Update tablecontrol
READ TABLE lt_f4 WITH KEY fieldname = 'MPRN'.
IF sy-subrc = 0.
 MOVE lt_f4-fieldval TO i_mprn-mprn.
 ws_dyname1 = 'ZSRO_MASTER_DATA'.
 ws_dynumb1 = '0301'.
 ws_dynpfld1-fieldname ='I_MPRN-MPRN'.
 ws_dynpfld1-fieldvalue = i_mprn-mprn.
 ws_dynpfld1-stepl = stepl_index1.
 APPEND ws_dynpfld1 TO i_dnpfld1.
 CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = ws_dyname1
 dynumb = ws_dynumb1
 TABLES
 dynpfields = i_dnpfld1
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 undefind_error = 7
 OTHERS = 8.
 IF sy-subrc <> 0.
 ENDIF.
ENDIF.
CLEAR : i_dnpfld1, ws_dynpfld1.
REFRESH: i_dnpfld1.
READ TABLE lt_f4 WITH KEY fieldname = 'ZZPSTLZ'.
IF sy-subrc = 0.
 MOVE lt_f4-fieldval TO i_mprn-post_code.
 ws_dyname1 = 'ZSRO_MASTER_DATA'.
 ws_dynumb1 = '0301'.
 ws_dynpfld1-fieldname ='I_MPRN-POST_CODE'.
 ws_dynpfld1-fieldvalue = i_mprn-post_code.
 ws_dynpfld1-stepl = stepl_index1.
 APPEND ws_dynpfld1 TO i_dnpfld1.
 CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = ws_dyname1
 dynumb = ws_dynumb1
 TABLES
 dynpfields = i_dnpfld1
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 undefind_error = 7
 OTHERS = 8.
 IF sy-subrc <> 0.
 ENDIF.
ENDIF.
ENDMODULE. " mprn1_f4 INPUT
*& Module pstlz1_f4 INPUT
 text
MODULE pstlz1_f4 INPUT.
CLEAR: i_dnpfld1, ws_dyname1, ws_dynumb1, ws_dynpfld1,
 lt_f4, lt_returntab1,lt_dynpfields1, lt_f4,
 stepl1, stepl_index1.
REFRESH: i_dnpfld1, lt_returntab1,lt_dynpfields1, lt_f4.
To Determine Steploop Index
lt_dynpfields1-fieldname = 'I_MPRN-MPRN'.
lt_dynpfields1-stepl = stepl1.
APPEND lt_dynpfields1. CLEAR lt_dynpfields1.
CALL FUNCTION 'DYNP_VALUES_READ'
 EXPORTING
 dyname = sy-repid
 dynumb = sy-dynnr
 translate_to_upper = 'X'
 determine_loop_index = 'X'
 TABLES
 dynpfields = lt_dynpfields1
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 invalid_parameter = 7
 undefind_error = 8
 double_conversion = 9
 stepl_not_found = 10
 OTHERS = 11.
IF sy-subrc EQ 0.
 READ TABLE lt_dynpfields1 INDEX 1.
ENDIF.
stepl_index1 = lt_dynpfields1-stepl.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
 EXPORTING
 tabname = 'IFLOT'
 fieldname = 'I_MPRN-POST_CODE'
 searchhelp = 'ZS_MPRN_PC'
 dynpprog = sy-repid
 dynpnr = sy-dynnr
 TABLES
 return_tab = lt_f4
 EXCEPTIONS
 field_not_found = 1
 no_help_for_field = 2
 inconsistent_help = 3
 no_values_found = 4
 OTHERS = 5.
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Update tablecontrol
READ TABLE lt_f4 WITH KEY fieldname = 'ZZPSTLZ'.
IF sy-subrc = 0.
 MOVE lt_f4-fieldval TO i_mprn-post_code.
 ws_dyname1 = 'ZSRO_MASTER_DATA'.
 ws_dynumb1 = '0301'.
 ws_dynpfld1-fieldname ='I_MPRN-POST_CODE'.
 ws_dynpfld1-fieldvalue = i_mprn-post_code.
 ws_dynpfld1-stepl = stepl_index1.
 APPEND ws_dynpfld1 TO i_dnpfld1.
 CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = ws_dyname1
 dynumb = ws_dynumb1
 TABLES
 dynpfields = i_dnpfld1
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 undefind_error = 7
 OTHERS = 8.
 IF sy-subrc <> 0.
 ENDIF.
ENDIF.
CLEAR : i_dnpfld1, ws_dynpfld1.
REFRESH: i_dnpfld1.
READ TABLE lt_f4 WITH KEY fieldname = 'MPRN'.
IF sy-subrc = 0.
 MOVE lt_f4-fieldval TO i_mprn-mprn.
 ws_dyname1 = 'ZSRO_MASTER_DATA'.
 ws_dynumb1 = '0301'.
 ws_dynpfld1-fieldname ='I_MPRN-MPRN'.
 ws_dynpfld1-fieldvalue = i_mprn-mprn.
 ws_dynpfld1-stepl = stepl_index1.
 APPEND ws_dynpfld1 TO i_dnpfld1.
 CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = ws_dyname1
 dynumb = ws_dynumb1
 TABLES
 dynpfields = i_dnpfld1
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 undefind_error = 7
 OTHERS = 8.
 IF sy-subrc <> 0.
 ENDIF.
ENDIF.
ENDMODULE. " pstlz1_f4 INPUT
Regards,
Prakash.

Difference between ALV and Table control

Hi folks,
i want to know the major differences between AlV and table controls.
i know that table control is designed in screen painter, but i want to know the major diff between Table control and ALV.
helpful answers will be rewarded.
Regards,
Naveen

Hi Naveen,
Basically ALV is a way to display the output and Table Control is designed in screen painter through which you can get entries in Table Control, can delete some records etc for further processing and its not use only for Display.
ALV is Application List viewer:-
Sap provides a set of ALV (ABAP LIST VIEWER) function modules which can be put into use to embellish the output of a report. This set of ALV functions is used to enhance the readability and functionality of any report output. Cases arise in sap when the output of a report contains columns extending more than 255 characters in length.
In such cases, this set of ALV functions can help choose selected columns and arrange the different columns from a report output and also save different variants for report display. This is a very efficient tool for dynamically sorting and arranging the columns from a report output.
TABLE CONTROL:-
ABAP offers two mechanisms for displaying and using table data in a screen. These mechanisms are table controls and step loops. Table controls and step loops are types of screen tables you can add to a screen in the Screen Painter.
Rewards if useful.
Regards,
Shilpi

Dynamic tabstrips and table control in custom infotype

Dear Experts,
I have a requirement to create a custom infotype using tabstrips and table control. The tabstripes should also be dynamically populated. For example we have infty 8(Basic pay) used table control and 24(Qualifications) for tabstripes.
Could you please tell me how to do this. Please do the needful ASAP.
Thanks,
Chaitanya.
Moderator message - Please don't just post your requirements and ask the forum to do your work for you...especially ASAP - Thread locked
Edited by: Rob Burbank on Oct 7, 2009 4:16 PM

Hi Partha,
Pls check the threads:
Best way to store a table control into an infotype
Re: Custom Infotype with table control - Overview/List Screen
Dilek

Query on ABAP List Viewer and Table Control?

Hi all,
I was trying to solve the exercises in these areas....but was unable to do as some of the concepts were not clear to me as I'm new to this field.
So Can any one help me out in giving me the Notes or attachments on the ABAP List Viewer(A.L.V.) and Table Control.
My ID: [email protected]
Waiting for a reply...
A New Entrant in ABAP.
Message was edited by:
saikumar b

Hi saikumar,
I just start to work with Abap too. All links i Know:
http://www.erpgenie.com/abap/controls/alvgrid.htm
http://www.abapfans.hpg.ig.com.br/links.htm
http://abap4.tripod.com/index..html
http://paginas.terra.com.br/educacao/abap/
http://www.sdn.sap.com/
http://www.sap-img.com/
http://www.planetsap.com/Tips_and_Tricks.htm
http://www.abap4.com.br/
http://www.erpgenie.com/sap/abap/index.htm
Good lucky

Default value for a column in Table Control

Hi friends, can i set dinamcally a default value for a column in table control?, this column is check type. This default value must appear in empty rows,
thanks

ADD A MODULE AS Module yyyy In ur PAI.
as
In PAI.
LOOP at itab.
Module YYYY
ENDLOOP.
Module YYYY.
LOOP AT SCREEN.
    IF SCREEN-NAME = 'ITAB-VAL.
      ITAB-VAL = 'XXXXXXXX'        "(DEFAULT VALUE)
      SCREEN-INPUT = 0.
      MODIFY SCREEN.
    ENDIF.
ENDLOOP.
End module.
*note
make this event work only if the previous column is filled okay.
the display will be in display mode on the screen as screen-input = 0.
see that in the table control u can get the table field for all the rows even though you are processing on some fields .
so what u do is make that particular filed masked(no i/p field and populate the field that will be better instead of populating all the columns okay.
hope this helps you out ,
regards,
vijay.

Alv Grid and Table Control

What is the difference between Alv Grid and Table Control?Explain in detail..

Table control is a screen table to display table data in a screen. You can add table control to a screen in the Screen Painter. The typical flow-logic to process table control is:
LOOP AT <internal table> CURSOR <scroll-var>
[WITH CONTROL <table-control> ]
[FROM <line1> ] [TO <line2> ].
...<actions>...
ENDLOOP.
ALV Grid is a SAP Technology to display a set of data on the output screen. For example if you have selected some SAP tables and processed these data in a way you want to display, then you can pass the internal table to the ALV Grid and it will be displayed on the result screen as ALV Grid. See example in SE16 result.

How to add a field and table control to BP transaction.

Hi,
I have a requirement to add a field and table control to the 'Control data' tab of the Transaction BP.
Can some on please help me if having a solution and with any relavant documents.
Thanks in advance.
Raj & Khader.

Also explore with EEWB tcode.
Refer this threads
Re: EEWB
Created New fields in Business Activity with EEWB
Cheers
Manohar

Search help for a field in table control based on another field value

Hi,
I want to attach the Search help for a field in table control based on another field value.
Please help me asap.
Will be highly rewarded

HI,..
Check these links
search help in table control
Re: How to create Search Help for a field in Table control !!
How to create Search Help for a field in Table control !!
F4 Help In Table Control
Control table F4 help
Problem in F4 help in screen field
check this code
DATA: BEGIN OF it_value4 OCCURS 0,
 TEXTCODE LIKE ZXX-TEXTCODE,
 TEXTDESC LIKE ZXX-TEXTDESC,
 END OF it_value4.
progname = sy-repid.
dynnum = sy-dynnr.
 SELECT TEXTCODE TEXTDESC
 FROM xxxx
 INTO CORRESPONDING FIELDS OF TABLE it_value4
 WHERE LOSS_CODE = IT_VALUE1 .
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
 EXPORTING
 retfield = 'TEXTCODE'
 dynpprog = progname
 dynpnr = dynnum
 dynprofield = 'ITVALUE-TEXTCODE' "-->UR 4 th filed value in screen
 value_org = 'S'
 TABLES
 value_tab = it_value4.
endmodule.
Message was edited by:
 veereshbabu ponnada

Can i use create function for MSSql scalar and table valude function.

Hi,
1) Can i use create function for MSSql scalar and table valued function?
2) How many type of user defined function are there in oracle 11g express?
3) And can i reture any "type" form user defined function?
yourse sincerely

944768 wrote:
Q1)That means even if i return predefined types like integer, varchar2 then also PGA is used ?The data type does not determine where the variable is stored. A string (called a varchar2 in Oracle) can be stored in stack space, heap space, on disk, in a memory mapped file, in a shared memory, in an atom table, etc.
It is the who and what is defining and using that string, that determines where and how it is stored.
The Oracle sever supports 2 languages in PL/SQL. The PL (Programming Logic) language is a procedural/declarative language. It is NOT SQL. SQL is integrated with it. The PL/SQL engine uses private process memory (PGA). So PL/SQL variables exist in the PGA (but there are exceptions such as LOBs).
Q2) So please suggest me solution in oracle.Sounds to me you are looking at how to implement a T-SQL style function as an Oracle function, and once implemented, do joins on the function.
Do not use PL/SQL in SQL in place of a SQL select. It is not T-SQL.
One cannot use PL/SQL to create functions along the style of T-SQL, where the function executes a SQL using some conditional logic, and then return as if the function was a native SQL select.
T-SQL is an extension to the SQL language - making it a hybrid and very impure language implementation. PL is based on ADA - part of the Pascal family of languages. The E-SQL (embedded SQL) approach used in languages like C/C++, Cobol and Ada, has been transparently done in PL/SQL. You can write and mix PL code and variables with SQL code. And the PL/SQL engine figures out how to make the call from the PL/SQL engine to the SQL engine.
But PL/SQL is not "part" of the SQL language and does not "extend" the SQL language in a T-SQL fashion.
So you need to check your SQL-Server preconcepts in at the door, as they are not only irrelevant in Oracle, they are WRONG in Oracle.
The correct way in Oracle, in a nutshell - Use the SQL language to do data processing. Use PL/SQL to manage conditional process flow and the handling of errors.

I hav to upload bdc for vk11 trans and table konv.

hi experts,
i m new in BDC... i hav to upload bdc for vk11 trans and table konv.
frst doubt is
i hv to run shdb transc?? or just i hv to write program??
nd cn any1 send me teps as hw to create upload..
Condition Type Sales Organisation Distribution channel Material Price Unit Valid from Valid to
KSCHL VKORG VTWEG MATNR_01 KBETR_01 KPEIN_01 DATAB_01 DATBI_01
now plz tel me hw to do this...whether to run shdb or jus to write program in se38..
or i hv to do both...bt plz tel me step by step

Please don't ignore the warnings. Read the rules of engagement.
Thread locked, again.
Thomas
wrking on ABAP OOPS, oput is coming but 1 field name wd customer name is nt

Closing INDIVIDUAL lines for input in a table control

Right, hopefully I can explain my issue clearly enough to get an answer that will help me resolve this pain in the *** issue.
My table control has a delete function but the client doesn't want the line removed from the control table they simply want the line in question to be greyed out (closed for input). Has anyone achieved this in the past? I know it's possible to grey out columns but I can't see any way of doing individual lines.
For all answers that help me I will shout a beer provided you are in either Sydney or Adelaide.

Hi,
>
Neil Gardiner wrote:
> Right, hopefully I can explain my issue clearly enough to get an answer that will help me resolve this pain in the *** issue.
>
> My table control has a delete function but the client doesn't want the line removed from the control table they simply want the line in question to be greyed out (closed for input). Has anyone achieved this in the past? I know it's possible to grey out columns but I can't see any way of doing individual lines.
>
> For all answers that help me I will shout a beer provided you are in either Sydney or Adelaide.
Refer:-
it_zekpo is my internal table w/o header line,
wa_zekpo is work area.
Name of input/output fields on screen are:-
wa_zekpo-field1,
wa_zekpo-field2, and so on...
Add a field as flag(1) type c in the internal table and work area
And keep a name of SELCOL in the attributes of table control as wa_zekpo-flag
Take the group1 for all textboxes as 'ABC' in the table control
Try using code:-
At screen logic:
PROCESS BEFORE OUTPUT.
* MODULE status_8003.
LOOP WITH CONTROL po_tb.
 MODULE read_data.
ENDLOOP.
PROCESS AFTER INPUT.
* MODULE user_command_8003.
LOOP WITH CONTROL po_tb.
 MODULE modify_data.
ENDLOOP.
In PBO
*& Module READ_DATA OUTPUT
MODULE read_data OUTPUT.
READ TABLE it_zekpo INTO wa_zekpo INDEX po_tb-current_line. "po_tab is table control name
data : line_count type i.
describe it_zekpo
lines line_count.
po_tb-lines = line_count + 10.
"to increase the number of lines in table control dynamically
if sy-ucomm = 'DELETE'. "<--when user click delete button
 if wa-zekpo-flag = 'X'. "<--if record selected
 if screen-group1 = 'ABC'.
 loop at screen.
 screen-input = 0. "disable
 screen-active = 0.
 endloop.
 modify screen.
 endif.
 else. "<--if record not selected
 if screen-group1 = 'ABC'.
 loop at screen.
 screen-input = 1. "enable
 screen-active = 1.
 endloop.
 modify screen.
 endif.
 endif.
endif.
ENDMODULE. " READ_DATA OUTPUT
In PAI
*& Module MODIFY_DATA INPUT
MODULE MODIFY_DATA INPUT.
MODIFY IT_ZEKPO FROM WA_ZEKPO INDEX po_tb-currentline.
"this will insert a new line
"and will modify the contents of existing line
ENDMODULE. " MODIFY_DATA INPUT
Hope this helps you.
Let mw know if you have any doubts.
Regards,
Tarun

How to provide F4 help for a field in table control

Hi Friends,
I have requirement like below.
1.Create one custom transaction code with header and item information.
2.In item level, we will be designed table control to enter/display the data.
3.Table controls first field will be material number and next DOT number (Material may have many DOT numbers) and so on.
4.First user will enter material number in the table controls first rows first field and go to DOT number field.
5.DOT number has drop down option. If user selects drop down box of DOT number, he gets all the DOT numbers available in database. User selects one DOT number and double clicks on it then it will be populated in DOT number field box.
But for point number 5, business wants like when ever user enters material number in table control first field then select DOT numbers drop down then they want to see the particular materials DOT numbers only in the drop down list for selection. Not all DOT numbers available in data base. Same thing should happen for all item lines in table control.
Please see below example.
Assume data base table has 10 DOT numbers. But material number has only 2 DOT numbers. When ever user enters material number in item level table control and selects DOT numbers drop down then it should show only 2 DOT numbers which are related to particular material number. Not all 10 DOT numbers.
Could you please suggest me, how can we achieve this?

Hello,
Check this :-
For POV
Input Help in Dialog Modules
You can call dialog modules in the POV event using the event keyword PROCESS ON VALUE-REQUEST.
PROCESS ON VALUE-REQUEST.
FIELD <f> MODULE <mod>.
After the PROCESS ON VALUE-REQUEST statement, you can only use the MODULE statement together with the FIELD statement. When the user chooses F4 for a field <f>, the system calls the module <mod> belonging to the FIELD <f> statement. If there is more than one FIELD statement for the same field <f>, only the first is executed. The module <mod> is defined in the ABAP program like a normal PAI module. However, the contents of the screen field <f> are not available, since it is not transported by the FIELD statement during the PROCESS ON HELP-REQUEST event. You can now program your own value lists in the module. However, this procedure is only recommended if it really is not possible to use a search help. Defining search helps is much easier than PROCESS ON VALUE-REQUEST, since the system takes over some of the standard operations, such as getting field contents from the screen. It also ensures that the F4 help has a uniform look and feel throughout the system. Furthermore, it means that you do not have to reassign input help to fields on each screen.
Despite the introduction of search helps (and search help exits), there are still cases in which you need to use parts of the standard F4 functions directly. In this case, there are some standard function modules that you can use in the POV event. They support search helps, as well as all other kinds of input help, and are responsible for data transport between the screen and the input help. These all have the prefix F4IF_. The most important are:
F4IF_FIELD_VALUE_REQUEST
Calls the input help of the ABAP Dictionary dynamically. You can pass the component names of a structure or database table of the ABAP Dictionary to the function module in the import parameters TABNAME and FIELDNAME. The function module starts the ABAP Dictionary input help for this component. All of the relevant screen fields are read. If you specify the import parameters DYNPPROG, DYNPNR, and DYNPROFIELD, the users selection is returned to the corresponding field on the screen. If you specify the table parameter RETURN_TAB, the selection is returned into the table instead.
F4IF_INT_TABLE_VALUE_REQUEST
This function module displays a value list that you created in an ABAP program. The value list is passed to the function module as the table parameter VALUE_TAB. If you specify the import parameters DYNPPROG, DYNPNR, and DYNPROFIELD, the users selection is returned to the corresponding field on the screen. If you specify the table parameter RETURN_TAB, the selection is returned into the table instead.
There are also two function modules - DYNP_VALUES_READ and DYNP_VALUES_UPDATE - that can read the values of screen fields and return values to them during the POV event. For further information, refer to the relevant function module documentation.
Input help in dialog modules
REPORT DEMO_DYNPRO_F4_HELP_MODULE.
TYPES: BEGIN OF VALUES,
CARRID TYPE SPFLI-CARRID,
CONNID TYPE SPFLI-CONNID,
END OF VALUES.
DATA: CARRIER(3) TYPE C,
CONNECTION(4) TYPE C.
DATA: PROGNAME LIKE SY-REPID,
DYNNUM LIKE SY-DYNNR,
DYNPRO_VALUES TYPE TABLE OF DYNPREAD,
FIELD_VALUE LIKE LINE OF DYNPRO_VALUES,
VALUES_TAB TYPE TABLE OF VALUES.
CALL SCREEN 100.
MODULE INIT OUTPUT.
PROGNAME = SY-REPID.
DYNNUM = SY-DYNNR.
CLEAR: FIELD_VALUE, DYNPRO_VALUES.
FIELD_VALUE-FIELDNAME = 'CARRIER'.
APPEND FIELD_VALUE TO DYNPRO_VALUES.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE VALUE_CARRIER INPUT.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
EXPORTING
TABNAME = 'DEMOF4HELP'
FIELDNAME = 'CARRIER1'
DYNPPROG = PROGNAME
DYNPNR = DYNNUM
DYNPROFIELD = 'CARRIER'.
ENDMODULE.
MODULE VALUE_CONNECTION INPUT.
CALL FUNCTION 'DYNP_VALUES_READ'
EXPORTING
DYNAME = PROGNAME
DYNUMB = DYNNUM
TRANSLATE_TO_UPPER = 'X'
TABLES
DYNPFIELDS = DYNPRO_VALUES.
READ TABLE DYNPRO_VALUES INDEX 1 INTO FIELD_VALUE.
SELECT CARRID CONNID
FROM SPFLI
INTO CORRESPONDING FIELDS OF TABLE VALUES_TAB
WHERE CARRID = FIELD_VALUE-FIELDVALUE.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
EXPORTING
RETFIELD = 'CONNID'
DYNPPROG = PROGNAME
DYNPNR = DYNNUM
DYNPROFIELD = 'CONNECTION'
VALUE_ORG = 'S'
TABLES
VALUE_TAB = VALUES_TAB.
ENDMODULE.
The next screen (statically defined) for screen 100 is itself. It has the following layout:
The input fields have been adopted from the program fields CARRIER and CONNECTION. The pushbutton has the function code CANCEL with function type E.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
MODULE INIT.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
PROCESS ON VALUE-REQUEST.
FIELD CARRIER MODULE VALUE_CARRIER.
FIELD CONNECTION MODULE VALUE_CONNECTION.
When the user chooses input help for the individual fields, the following is displayed:
For the Airline field, the POV module VALUE_CARRIER is called. The function module F4IF_FIELD_VALUE_REQUEST displays the input help for the component CARRIER1 of the structure DEMOF4HELP from the ABAP Dictionary, namely the search help DEMOF4DE. The users selection is returned to the screen field CARRIER.
For the Flight number field, the POV module VALUE_CONNECTION is called. The function module DYNP_VALUE_READ transports the value of the screen field CARRIER into the program. The program then reads the corresponding values from the database table SPFLI into the internal table VALUES_TAB using a SELECT statement, and passes the internal table to F4IF_INT_TABLE_VALUE_REQUEST. This displays the internal table as input help, and places the users selection into the screen field CONNECTION.
For POH------------
Field Help
There are three ways of displaying field help for screen elements:
Data Element Documentation
If you place a field on the screen in the Screen Painter by copying a ABAP Dictionary field, the corresponding data element documentation from the ABAP Dictionary is automatically displayed when the user chooses field help (as long as the help has not been overridden in the screen flow logic).
For further information about creating data element documentation, refer to data elements.
Data Element Supplement Documentation
If the data element documentation is insufficient, you can expand it by writing a data element supplement
Data element supplement documentation contains the heading Definition, as well as the following others:
Use
Procedure
Examples
Dependencies
To create data element supplement documentation for a screen, choose Goto ® Documentation ® DE supplement doc. from the element list of the screen. A dialog box appears in which the system proposes a number as the identified for the data element supplement. You can then enter help texts for the above headings using the SAPscript editor.
Data element supplement documentation created in this way is program- and screen-specific. Any data element supplement documentation created in the ABAP Dictionary with the same number is overridden by the screen-specific documentation. You can link existing data element supplement documentation created in the ABAP Dictionary with a screen field by using the table THLPF. To do this, crate a new row in THLPF containing the following data: Program name, screen name, field name, and number of the data element supplement documentation.
To display data element supplement documentation, you must code the following screen flow logic in the POH event:
PROCESS ON HELP-REQUEST.
FIELD <f> [MODULE <mod>] WITH <num>.
After PROCESS ON HELP-REQUEST, you can only use FIELD statements. If there is no PROCESS ON HELP-REQUEST keyword in the flow logic of the screen, the data element documentation for the current field, or no help at all is displayed when the user chooses F1. Otherwise, the next FIELD statement containing the current field <f> is executed.
If there is screen-specific data element supplement documentation for the field <f>, you can display it by specifying its number <num>. The number <num> can be a literal or a variable. The variable must be declared and filled in the corresponding ABAP program.
You can fill the variables, for example, by calling the module <mod> before the help is displayed. However, the FIELD statement does not transport the contents of the screen field <f> to the ABAP program in the PROCESS ON HELP-REQUEST event.
For further information about data element supplement documentation, refer to Data Element Supplements.
Calling Help Texts from Dialog Modules
If data element supplement documentation is insufficient for your requirements, or you want to display help for program fields that you have not copied from the ABAP Dictionary, you can call dialog modules in the POH event:
PROCESS ON HELP-REQUEST.
FIELD <f> MODULE <mod>.
After the PROCESS ON HELP-REQUEST statement, you can only use the MODULE statement together with the FIELD statement. When the user chooses F1 for a field <f>, the system calls the module <mod> belonging to the FIELD <f> statement. If there is more than one FIELD statement for the same field <f>, only the first is executed. However, the contents of the screen field <f> are not available in the module <mod>, since it is not transported by the FIELD statement during the PROCESS ON HELP-REQUEST event. The field help should not be dependent on the user input.
The module <mod> is defined in the ABAP program like a normal PAI module. The processing logic of the module must ensure that adequate help is displayed for the field in question. Instead of calling an extra screen with text fields, you should use one of the following function modules to display a suitable SAPscript document:
HELP_OBJECT_SHOW_FOR_FIELD
This function module displays the data element documentation for components of any structure or database table from the ABAP Dictionary. You pass the name of the component and structure or table to the import parameters FIELD and TABLE.
HELP_OBJECT_SHOW
Use this function module to display any SAPscript document. You must pass the document class (for example, TX for general texts, DE for data element documentation) and the name of the document to the import parameters DOKCLASS and DOKNAME. For technical reasons, you must also pass an empty internal table with the line type TLINE to the tables parameter of the function module.
For further information about how to create SAPscript documents, refer to the Documentation of System Objects documentation.
Field help on screens.
REPORT DEMO_DYNPRO_F1_HELP.
DATA: TEXT(30),
VAR(4),
INT TYPE I,
LINKS TYPE TABLE OF TLINE,
FIELD3, FIELD4.
TABLES DEMOF1HELP.
TEXT = TEXT-001.
CALL SCREEN 100.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE F1_HELP_FIELD2 INPUT.
INT = INT + 1.
CASE INT.
WHEN 1.
VAR = '0100'.
WHEN 2.
VAR = '0200'.
INT = 0.
ENDCASE.
ENDMODULE.
MODULE F1_HELP_FIELD3 INPUT.
CALL FUNCTION 'HELP_OBJECT_SHOW_FOR_FIELD'
EXPORTING
DOKLANGU = SY-LANGU
DOKTITLE = TEXT-002
CALLED_FOR_TAB = 'DEMOF1HELP'
CALLED_FOR_FIELD = 'FIELD1'.
ENDMODULE.
MODULE F1_HELP_FIELD4 INPUT.
CALL FUNCTION 'HELP_OBJECT_SHOW'
EXPORTING
DOKCLASS = 'TX'
DOKLANGU = SY-LANGU
DOKNAME = 'DEMO_FOR_F1_HELP'
DOKTITLE = TEXT-003
TABLES
LINKS = LINKS.
ENDMODULE.
The next screen (statically defined) for screen 100 is 100. It has the following layout:
The screen fields DEMOf1HELP-FIELD1 and DEMOF1HELP-FIELD2 from the ABAP Dictionary and the program fields FIELD3 and FIELD4 are assigned to the input fields. The pushbutton has the function code CANCEL with function type E.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
PROCESS ON HELP-REQUEST.
FIELD DEMOF1HELP-FIELD2 MODULE F1_HELP_FIELD2 WITH VAR.
FIELD FIELD3 MODULE F1_HELP_FIELD3.
FIELD FIELD4 MODULE F1_HELP_FIELD4.
The components FIELD1 and FIELD2 of structure DEMOF1HELP both refer to the data element DEMOF1TYPE. This data element is documented, and also has two supplements with numbers 0100 and 0200.
The following field help is displayed:
When the user chooses F1 on the input field for DEMOF1HELP-FIELD1, the data element documentation for DEMOF1TYPE is displayed, since the field does not occur in the PROCESS ON HELP-REQUEST event.
If the user chooses F1 repeatedly for the input field DEMOF1HELP-FIELD2, the data element documentation is displayed, along with the supplement documentation for either 0100 or 0200 alternately. The variable VAR is filled in the dialog module F1_HELP_FIELD2.
When the user chooses F1 on the input field for FIELD3, the data element documentation for DEMOF1TYPE is displayed, since this is called in the dialog module F1_HELP_FIELD3 by the function module HELP_OBJECT_SHOW_FOR_FIELD.
When the user chooses F1 on the input field for FIELD4, the SAPscript documentation DEMO_FOR_F1_HELP is displayed, since this is called in the dialog module F1_HELP_FIELD4 by the function module HELP_OBJECT.
Regards,
Deepu.K

The PAI Event Code to search for a record in Table Control

Logic
1. I have a position button and entry text field (search content) for a table control in my screen. Position button has the function code 'PBUT'.
2. Content of table control will be in an internal table. The entry text field is to be used for positioning.
3. I enter the search (key) field in text field & Click the position button.
4. The PAI event of button click (Module user_command) of that screen is as under.
Case sy_ucomm.
When 'PBUT'.
What will be the code to bring the row as selected in table control, that I have to write here, for this case-value.
Endcase.
Regards,

Hi Alok,
Excuse me, couldn`t catch u yesterday. Ok i`ve the code which will set the cursor on the selected entry.
Reward points if convinced.
*& Report Y131_TC_TEST *
REPORT y131_tc_test NO STANDARD PAGE HEADING.
TABLES: vbak.
DATA : BEGIN OF str_tc,
 vbeln LIKE vbak-vbeln,
 erdat LIKE vbak-erdat,
 END OF str_tc,
 it_tc LIKE TABLE OF str_tc WITH HEADER LINE,
 loopc LIKE sy-loopc,
 flag,
 lin TYPE i.
CONTROLS : my_tc TYPE TABLEVIEW USING SCREEN 9000.
CALL SCREEN 9000.
*& Module STATUS_9000 OUTPUT
* text
MODULE status_9000 OUTPUT.
* SET PF-STATUS 'xxxxxxxx'.
* SET TITLEBAR 'xxx'.
IF it_tc[] IS INITIAL.
 SELECT vbeln erdat INTO TABLE it_tc UP TO 10
 ROWS FROM vbak.
 DESCRIBE TABLE it_tc LINES lin.
 my_tc-top_line = loopc.
ENDIF.
ENDMODULE. " STATUS_9000 OUTPUT
*& Module USER_COMMAND_9000 INPUT
* text
MODULE user_command_9000 INPUT.
CASE sy-ucomm.
 WHEN 'EXIT'.
 LEAVE PROGRAM.
 WHEN 'PBUT'.
**** Now this event is triggerred when the user uses the ****Position Push button to locate the field value.
 CALL SCREEN 9001 STARTING AT 10 15.
ENDCASE.
ENDMODULE. " USER_COMMAND_9000 INPUT
*& Module USER_COMMAND_9001 INPUT
* text
MODULE user_command_9001 INPUT.
CASE sy-ucomm.
 WHEN 'OKAY' OR ' ' or 'EXIT'.
**** When the user selects values from the search help on **** position button, the itab is read and index is *****assigned
 READ TABLE it_tc WITH KEY vbeln = vbak-vbeln.
 IF sy-subrc = 0.
 loopc = sy-tabix.
 flag = 'X'.
**** the cursor is set here
 my_tc-top_line = loopc.
 SET SCREEN 0.
 LEAVE SCREEN.
 ENDIF.
ENDCASE.
ENDMODULE. " USER_COMMAND_9001 INPUT
*& Module STATUS_9001 OUTPUT
* text
MODULE status_9001 OUTPUT.
SET PF-STATUS 'MODAL'.
* SET TITLEBAR 'xxx'.
ENDMODULE. " STATUS_9001 OUTPUT
Regards

Method for dble-click and table control

Similar Messages

Maybe you are looking for