cancel
Showing results for 
Search instead for 
Did you mean: 

Equivalent for 'process on value-request' in WDA ?

Former Member
0 Kudos

Hello again,

i have one more requirement in building a wda-gui for an existing transaction.

In the flow-logic of the SAPGUI-transaction we have an event 'process on value-request', it is triggered when a user pushes the F4-Button or clicks onto the icon belonging to the InputField.

I need to have an equivalent in WDA.

Any ideas / workarounds ? Is perhaps OVS a possible way ?

Thanks a lot !

Accepted Solutions (0)

Answers (2)

Answers (2)

alejandro_bindi
Active Contributor
0 Kudos

Andreas, if you use OVS, when the user presses F4 or clicks the "matchcode" icon, the method registered to event OVS (from component WDR_OVS) with execute more than once, each time with a different phase indicator, allowing you to set titles, initialize selection screen, populate values list, etc.

That said, if what you want is just to capture the "push F4" event alone, i'd say that's not possible in WD. There's no point in using OVS just to do that.

uday_gubbala2
Active Contributor
0 Kudos

Hi Andreas,

You can achieve this functionality by specifying the Input help mode property of the attribute to which you are binding your input field. You can choose among the various possibilities as Dictionary Search Help/Object Value Selector/User-Defined Programming. You can even just leave it as Automatic to allow the system take care of the search help to be displayed. No matter which option you use among the above quoted ones you would be able to get your search help. You need to go for OVS only when,

"Say, for example, 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. "

The OVS component offers an interface that can:

1) Receive information about which input fields should be displayed on the selection screen,

2) Receive information about the initial values of these input fields

3) Hand back the user's input into these input fields

4) Receive the result from the data retrieval in order to display the list

5) Hand back the selected data set to the consumer program

(The above has been quoted from the SAP's standard guide)

Regards,

Uday