remote search help for webdynpro screen field

[Former Member]

Hello,

I have a requirement as follows :

1) There are two fields on a webdynpro screen - A and B

2) For field B, i need a search help, the values for which are stored in a remote system.

3) The name (RFC destination) for the remote system is stored in a table, against the value of the field A. Means, this table has the value of field A on the screen, and along with it, there is the name of the remote system.

Now the requirement is that when i press F4 for the field B, i need to pick up the value of field A (on pressing F4 only), use this value to get the remote system name from the table. Then use this remote system name to call an RFC which returns a table of values which are to be shown on the search help screen.

Alternatively, is it possible that i can create the search help in the remote system and then call it from the screen field B?

Could anyone please give any pointers? Is this a possibility using webdynpro ABAP?

regards,

Priyank

[Former Member · Accepted solution]

Hi Priyank,

Using a Search help thats present in the remote system is i think not possible with WDA.

But Your Requirement 1 ,2, 3 can be achived by creating search help dynamically. i think thats possible. i didnt get any requirement like this yet, but i think that can be done by creating f4 help dynamically.

check this

When programming with the help of interface IWD_VALUE_HELP, beware of the following:

● The method SET_VALUE_HELP_LISTENER at the interface controller of IWD_VALUE_HELP may be called only by the Web Dynpro Framework. With the help of this method, the framework passes a callback interface to the input help component. The input help component can use this interface to tell the framework that is shall be closed, for example, if data has been selected, if 'Cancel' has been applied or if an error has occurred. In addition, this interface contains the two attributes F4_CONTEXT_ELEMENT and F4_ATTRIBUTE_INFO. They describe the context element for which the F4 help has been requested.

● The events VH_WINDOW_CLOSED and VH_WINDOW_OPENED of the component interface may only be triggered by the framework. The events indicate the points in time when the input help window is closed or opened. When implementing the component interface IWD_VALUE_HELP, these events should be copied to the component interface of the input help component to make them available in the calling component and to allow its event handlers to register onto these events.

● The component interface IWD_VALUE_HELP has the interface view WD_VALUE_HELP. The views to be displayed in the input help window must be embedded into the window WD_VALUE_HELP, which belongs to the interface view.

● Once the input help component has been created by the Web Dynpro framework, method SET_VALUE_HELP_LISTENER is called (also by the framework) so that interface IF_WD_VALUE_HELP_LISTENER can be passed on to the input help component. This interface contains method CLOSE_WINDOW. This method can be used to close the input help window.

●

Attachment to a Context Attribute

You attach a freely programmed input help in analogy to the attachment of an OVS input help by following these steps:

1. Creating an input help component and implementing the component interface IWD_VALUE_HELP.

2. Creating a component usage for the input help component in your application component.

3. Attaching the component usage to the context attribute. In this case, for the input help mode choose free (either when creating the attribute or later in its properties table) and specify the respective component usage.

Context Change Log for Freely Programmed Input Help

When you work with a freely programmed input help, you can still use the function Context Change Log. Note, however, that the values selected by the user are not automatically written to the change table; you need to program this explicitly (see OVS Input Help and Context Change Log).

Regards

Sarath

[Former Member · Accepted solution]

Hi Sarath,

Thanks for the quick reply!!

The main problem i am facing is not with the search help as such but in picking up the name of the remote system from which the search help values have to come.

There is a table which has the following record :

DocNnumber ExtSystem

In this table, Doc number is the field A on the screen and against this field the remote system name is stored. So while firing the search help for B, i need to access the value of field A, access the above table to get the remote system name and then do a RFC call.

Is it possible to get the value of screen field A on pressing F4 on B??

The remote search help was just an alternative idea in mind. Ideally i would like to achieve it the normal way.

regards,

Priyank

[Former Member · Accepted solution]

Hi Priyank,

It will be very easy if u can make the field A as a dwop down so that u can fetch the value selected at the on select event of the field. As u said you already have the vales for the field A in a table, so populating that values to the drop down is not an issue.

Getting the values of another field on F4 is bit difficult , since it wont trigger any event.

Regards

Sarath

[Former Member · Accepted solution]

Hi Sarath,

can you provide more details about Search help . i want to use search help in my application.

thanks,

Raju.

[Yashpal]

Hi Priyank ,

I would suggest u to create a OVS for the same . in the OVS handler u have to first pick the value of the field A from that get the destination of the remote system.

call the RFC and get the output.

u have to code the destination name dynamically like

in some variable

call function 'function_name' destination lv_variable

then set the output for the display ..

how to create OVS see the component WDR_OVS.

Regards

Yash