Problem with OVS

[Former Member]

Hi all,

I've read the help.sap.com regarding OVS and its usage, but still not fully clear why we need it and how to use OVS. Can any of u provide more information regarding OVS and tell how to use OVS in the Application. Sample codes or links for the codes will be very helpful.

Thanks,

[abhimanyu_lagishetti7 · Accepted solution]

Hi Chandru,

You can see the standarad example 'WDR_OVS_TEST'

inside the component check V3 View,

for context attribute AIRPFROM,

see the properties you find Object Value Selector and OVS_USage_3 which is added in the used components.

co relate the Documentation

http://help.sap.com/saphelp_nw04s/helpdata/en/77/3545415ea6f523e10000000a155106/frameset.htm

with the coding involved in Method ON_OVS

Hope this clear.

Regards

Abhimanyu L

Message was edited by:

Abhimanyu Lagishetti

[Madhu2004]

hai,

The value help should take into account or fill multiple input

fields of your view composition. However, the different input fields are related to

different value nodes, which in turn refer to different ABAP Dictionary structures.

ABAP Dictionary search helps are not able to fulfill this task, since the maximum

scope of such a search help is the structure to which it is related.

<u><b>example:</b></u>

suppose u have three input fields,carrid,connid,fldate.we have OVS on date field.

if gennerally u use seach help we get all the dates.but to improve perfomance and accuracy we need to get dates of a particular combination carrid and connid.

this is achieveable using OVS.

OVS is phase mode ,u have 4 phases in building ovs.

<u><b>sample code is as follows</b></u>

TYPES : BEGIN OF ist_fields,

carrid TYPE spfli-carrid,

countryfr TYPE spfli-countryfr,

cityfrom TYPE spfli-cityfrom,

END OF ist_fields.

DATA:

it_fields TYPE ist_fields,

it_conn TYPE table of spfli.

FIELD-SYMBOLS : <lfs_input> TYPE ist_fields,

<lfs_select> TYPE spfli.

CASE ovs_callback_object->phase_indicator.

WHEN 0.

CALL METHOD ovs_callback_object->set_configuration

EXPORTING

window_title = 'search Flights'

group_header = 'enter flight details'

• LABEL_TEXTS =

• TABLE_HEADER =

• COLUMN_TEXTS =

col_count = 1

• ROW_COUNT =

• TABLE_MULTI_SELECT =

.

WHEN 1.

CALL METHOD ovs_callback_object->set_input_structure

EXPORTING

input = it_fields

• GROUP_HEADER =

• LABEL_TEXTS =

• WINDOW_TITLE =

.

WHEN 2.

ASSIGN ovs_callback_object->query_parameters->* TO <lfs_input> CASTING.

CALL METHOD cl_wd_flight_model=>get_conns_by_carrid_cityfrom

EXPORTING

i_carrid = <lfs_input>-carrid

i_countryfr = <lfs_input>-countryfr

i_cityfrom = <lfs_input>-cityfrom

IMPORTING

ET_SPFLI_SFLIGHT = it_conn

.

CALL METHOD ovs_callback_object->set_output_table

EXPORTING

output = it_conn

• TABLE_HEADER =

• COLUMN_TEXTS =

.

when 3.

DATA:

node_flight TYPE REF TO if_wd_context_node,

elem_flight TYPE REF TO if_wd_context_element,

stru_flight TYPE if_inputview=>element_flight .

assign ovs_callback_object->selection->* to <lfs_select> casting.

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

node_flight = wd_context->get_child_node( name = if_inputview=>wdctx_flight ).

node_flight->bind_structure(

EXPORTING

NEW_ITEM = <lfs_select> ).

ENDCASE.