cancel
Showing results for 
Search instead for 
Did you mean: 

How to bind select options type(LEDAT) to attribute?

Former Member
0 Kudos

Hi All,

I am using SHP_EXTENDED_DUE_LIST FM, in this IX_SELECT_OPTIONS node contains LEDAT, but it is of type select options.

I want to bind this to date type attribute.

Delivery date :__ to __.

while executing original FM we are giving low and high values it is giving output, but while binding i am getting only LEDAT but type is different. how to process this?? Please Help.

Thanks,

VEnky.

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

hi,

u can get the select option high and low values as well, thn u have to bind with the context attriute and pss these as parameters for the FM

suppose the select option parameter is LEDAT , then u can get the low and high values as LEDAT-low and LEDAT-high

regards,

Amit

gill367
Active Contributor
0 Kudos

HI

create two input field manually low and high in web dynpro

fetch the value sentered there and set it in one type declared of same as the attribute.

and fill it accordingly.

here is some sample code.

data val type SHP_LEDAT_RANGE_T.
  data ws_val type shp_ledat_range.
  ws_val-low = '20110101'. "fetch the value form one input field
  ws_val-high = '20110404'. "other input field
  append ws_val to val.

 data nd type ref to if_Wd_context_node.
 nd = wd_Context->PATH_GET_NODE( 'SHP_EXTENDED_DUE_LIS.IMPORTING.IX_SELECT_OPTIONS' ).
 nd->set_attribute( 
 name = 'PEDAT'
 VALUE = VAL
 
 
 ).

thanks

sarbjeet singh

Former Member
0 Kudos

Hi Sarbjeet,

I am trying like this...

DATA: r_date TYPE SHP_LEDAT_RANGE,

r_plant TYPE SHP_VSTEL_RANGE,

L_IX_SELECT_OPTIONS TYPE SHP_VL10_SELECT_OPTIONS,

L_EX_DELIVERY TYPE SHP_VL10_DELIVERY,

L_IX_PARAMETERS TYPE SHP_VL10_PARAMETERS.

DATA: ld_from_date TYPE d,

ld_to_date TYPE d.

DATA lo_nd_input TYPE REF TO if_wd_context_node.

DATA lo_el_input TYPE REF TO if_wd_context_element.

DATA ls_input TYPE wd_this->Element_input.

DATA lv_del_cdate TYPE wd_this->Element_input-del_cdate.

DATA lv_to_date TYPE wd_this->Element_input-to_date.

DATA lv_ship_point TYPE wd_this->Element_input-ship_point.

  • navigate from <CONTEXT> to <INPUT> via lead selection

lo_nd_input = wd_context->get_child_node( name = wd_this->wdctx_input ).

lo_el_input = lo_nd_input->get_element( ).

  • get single attribute

lo_el_input->get_attribute(

EXPORTING

name = `DEL_CDATE`

IMPORTING

value = lv_del_cdate ).

  • get single attribute

lo_el_input->get_attribute(

EXPORTING

name = `TO_DATE`

IMPORTING

value = lv_to_date ).

r_date-sign = 'I'.

r_date-option = 'BT'.

r_date-low = lv_del_cdate .

r_date-high = lv_to_date.

APPEND r_date to L_IX_SELECT_OPTIONS-ledat.

CLEAR r_date.

  • get single attribute

lo_el_input->get_attribute(

EXPORTING

name = `SHIP_POINT`

IMPORTING

value = lv_ship_point ).

r_plant-sign = 'I'.

r_plant-option = 'EQ'.

r_plant-low = lv_ship_point.

r_plant-high = ''.

APPEND r_plant to L_IX_SELECT_OPTIONS-VSTEL.

CLEAR r_plant.

CALL FUNCTION 'SHP_EXTENDED_DUE_LIST'

EXPORTING

IX_PARAMETERS = L_IX_PARAMETERS

IX_SELECT_OPTIONS = L_IX_SELECT_OPTIONS .

DATA lo_COMPONENTCONTROLLER TYPE REF TO IG_COMPONENTCONTROLLER .

lo_COMPONENTCONTROLLER = wd_this->get_componentcontroller_ctr( ).

lo_componentcontroller->execute_shp_extended_due_list( ).

But i am getting this error : Screen output without connection to user.

CAN U TELL ME ANY THING WRONG IN THIS??

tHANKS,

vENKY.

Edited by: venkys on Mar 8, 2011 9:52 AM

gill367
Active Contributor
0 Kudos

Are you getting this error only after doing this thing that i told you .

or it is coming without it also.

it seems something else to me some call transaction statement present in the FM.

can you poat the full code.

Former Member
0 Kudos

Hi Sarbjeet,

complete Code i am using is given above.

I checked in st22 giving error at call screen in FM 'K_KKB_LIST_DISPLAY'. but i am not using this FM in my appln. How it is giving error. i am using SHP_EXTENDED_DUE_LIST FM only. any suggestions please?

Thanks,

Venky.

Former Member
0 Kudos

Can you check at the DE level of that field if there is any SH or SH exit being used. or keep a break point in that FM, debug your application and check the call stack for the calls being made to this FM. Hope you can find some way.

thomas_jung
Developer Advocate
Developer Advocate
0 Kudos

>But i am getting this error : Screen output without connection to user.

CAN U TELL ME ANY THING WRONG IN THIS??

This function module might not be usable within WDA. It is trying to call a classic dynpro screen, which isn't allowed within Web Dynpro ABAP.